WO2018076930A1 - 一种基于时空数据库的对数据对象的检索方法 - Google Patents

一种基于时空数据库的对数据对象的检索方法 Download PDF

Info

Publication number
WO2018076930A1
WO2018076930A1 PCT/CN2017/100377 CN2017100377W WO2018076930A1 WO 2018076930 A1 WO2018076930 A1 WO 2018076930A1 CN 2017100377 W CN2017100377 W CN 2017100377W WO 2018076930 A1 WO2018076930 A1 WO 2018076930A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
time
managed
spatial
model
Prior art date
Application number
PCT/CN2017/100377
Other languages
English (en)
French (fr)
Inventor
林伟
Original Assignee
北京亚控科技发展有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from CN201610925967.XA external-priority patent/CN106294887B/zh
Priority claimed from CN201610926060.5A external-priority patent/CN106446278B/zh
Priority claimed from CN201610927538.6A external-priority patent/CN106407469B/zh
Priority claimed from CN201610925992.8A external-priority patent/CN106294888B/zh
Priority claimed from CN201610925969.9A external-priority patent/CN106407468B/zh
Priority claimed from CN201611271001.5A external-priority patent/CN106649867B/zh
Application filed by 北京亚控科技发展有限公司 filed Critical 北京亚控科技发展有限公司
Priority to US16/343,210 priority Critical patent/US11243927B2/en
Priority to CN201780020385.XA priority patent/CN108885634B/zh
Priority to EP17864325.0A priority patent/EP3531310A4/en
Publication of WO2018076930A1 publication Critical patent/WO2018076930A1/zh

Links

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/24—Querying
    • G06F16/242—Query formulation
    • G06F16/243—Natural language query formulation
    • 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/22—Indexing; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • 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/212—Schema design and management with details for data modelling 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/29—Geographical information databases

Definitions

  • the invention relates to a method for managing industrial production and monitoring based on a spatiotemporal database, in particular to a method for retrieving data objects based on a spatiotemporal database.
  • the main spatio-temporal database models are: sequence snapshot model, space-time cube model, ground state correction model, space-time composite model, etc. These models have different properties, advantages and disadvantages, but for the statistical industry, they can not meet the demand well;
  • spatio-temporal database model ideas such as object-oriented space-time model ideas, feature-based spatio-temporal database models, event-based spatio-temporal database models, etc.
  • object-oriented space-time model ideas such as object-oriented space-time model ideas, feature-based spatio-temporal database models, event-based spatio-temporal database models, etc.
  • These models use object-oriented or differential records to measure spatial variation and The relationship is recorded, but it is more or less unable to meet the numerous requirements of statistical and spatio-temporal databases and the statistical level, and it does not meet the needs of the statistical department in terms of business applicability.
  • the disaster information spatio-temporal database includes three disaster information databases: disaster current situation database, disaster process database and disaster history database.
  • the unified coding module hierarchically encodes the received disaster information data; attribute data management
  • the module and the spatial location data management module import the disaster information attribute data and the spatial location data into the corresponding disaster information database; the disaster information data is transmitted between the disaster information databases through the logic change module;
  • the spatio-temporal database index module time-spaces the disaster information space-time
  • the database establishes an update index;
  • the logic change module and the spatio-temporal database index module form the basis of the disaster information spatio-temporal database, and manage and maintain the disaster attribute, change and maintain the spatio-temporal logical index, and prepare for the warehousing, retrieval and spatio-temporal query of the statistical data.
  • the problems of the patent are: (1) the relational database cannot search for queries by directly inputting time or spatial information; (2) the retrieval method is single, and can only be searched
  • the Chinese patent CN102622349B discloses a processing method of a spatial position information database, comprising: acquiring coordinate data of a spatial position; and generating spatial position information coding corresponding to the spatial position according to the coordinate data, including: defining in China
  • the implemented spatial position information coding is divided into five sections of codes, country code-area code: subcode 1: subcode 2 - additional code, and the coding method of each section code is from top to bottom, numbered from left to right;
  • the spatial location information database is stored in the spatial location information database, and the spatial location information is encoded as an index and location information of the spatial location in the database.
  • the problems of this patent are: (1) the accuracy and accuracy of spatial description are not high enough, for example, the upper and bottom of a certain equipment in the factory cannot be accurately and differentiated; (2) spatial analysis and coding for data query and call Inconvenient, the corresponding encoding is required; (3) The database is not dynamically updated when the physical location update is changed.
  • the optimization methods for database query mainly include the following: (1) Reasonable use of index: for the data table in the relational database, create an independent and orderly storage structure according to the queried field to improve query performance; (2) redundant relational data : Redundantly store information in other related tables in a two-dimensional table to reduce the association relationship during query and improve query performance; (3) Separate and store massive data: For massive data, separate data by certain data Store storage to improve query performance.
  • Chinese patent CN100483411C discloses a method for information retrieval in a relational database, comprising the steps of: constructing a dimensional reduction strategy tree and placing it in a database system, the dimensional reduction strategy tree comprising at least one child node and at least one root node, each child node At least the node number identification information and the query condition combination information and the subordinate child node number are included; when the database is retrieved according to the user query condition, the new query condition is constructed according to the dimension reduction strategy tree; according to the new query The condition retrieves the database until the required data or query to the root node of the dimension reduction policy tree returns information without the required data.
  • the problem with this patent is that it requires specific number identification information when querying and invoking data.
  • an aspect of the present invention provides a method for retrieving a data object based on a spatiotemporal database, the retrieval method is a management model based on a management object and a spatial attribute and a model of the object to be managed.
  • the retrieval method comprises the steps of: modeling the management object for a temporal state and a spatial state of the object to be managed; and managing according to the object to be managed
  • the model sets a specific attribute of the object to be managed that is described by the natural language; searches based on the management model category of the management object and the spatial attribute and/or time attribute defined by the modeling according to the natural language description Determining the running state of the management object.
  • the method for modeling the object to be managed includes at least the following steps: modeling the object to be managed according to the spatial state of the object to be managed, and performing the object to be managed according to the time state of the object to be managed Modeling, setting a specific attribute of the object to be managed, and collecting data of the object to be managed to dynamically monitor and manage the object to be managed.
  • the management model based on the management object and the spatial attribute and/or time attribute defined by the natural language defined by the modeling are searched to determine the running state of the management object.
  • the step includes: retrieving real-time data, historical data, and/or planning data of at least one management object at the spatial location and/or the time based on the management model category, spatial location, and/or time of the management object, thereby Determining a real-time operational state, a historical operational state, and/or a planned operational state of at least one of the managed objects; or retrieving the spatial extent and/or location based on the management model category, spatial extent, and/or time range of the management object Real-time data, historical data, and/or planning data of at least one management object within a time range, thereby determining a real-time operating state, a historical operating state, and/or a planned operating state of at least one of the managed objects.
  • the step of determining the running state of the management object further comprises: determining a real-time database, a historical database, and/or a planning database storing the management object running data according to the management model category of the management object; according to the spatial attribute and/or The time attribute selects at least one version of the managed object operational data associated with the management object in a real-time database, a historical database, and/or a plan database, and determines at least one management object associated with the management model and views the management Real-time data, historical data, and/or planning data of the object to understand the real-time running state, historical running state, and/or planned running state of the managed object.
  • the management object includes a real account stored in the real-time database formed according to a time attribute classification. a data object, a historical data object stored in the history database, and a plan data object stored in the plan database; the real-time data object including at least one managed object formed by the real-time data model instantiation process a management object composed of real-time data; the historical data object includes at least one management object formed by the historical data of the management object formed by the historical data model instantiation process; the plan data object includes the plan At least one management object formed by the plan data of the management object formed by the data model instantiation process.
  • the step of modeling the management object for the temporal state and the spatial state of the object to be managed comprises: modeling the space of the object to be managed according to the spatial state of the object to be managed to establish a spatial model And modeling the time of the object to be managed according to the time state of the object to be managed to establish a time model, and establishing the management model formed by the spatial model of the object to be managed and the time model association.
  • the step of setting the specific attribute of the object to be managed by the natural language according to the management model of the object to be managed comprises: forming, by the instantiation process, the at least one management object by the instantiation process
  • the time object and the spatial object are associated with the management object; the time object of the management object is formed by the time model in the instantiation process, and the spatial object of the management object is formed by the space model in the instantiation process.
  • the step of setting the specific attribute of the object to be managed by the natural language according to the management model of the object to be managed further comprises: setting a specific attribute of the management object, the specific attribute including a temporal attribute, a spatial attribute, and/or a non-temporal attribute described by a natural language; the non-temporal attribute includes a first data type of the object to be managed and an attribute of the second data type, and the attribute of the second data type includes at least the object to be managed One or more of graphic properties, audio properties, video properties, and name properties.
  • the first data type is a regular data type, such as byte, bool, int8, short, ushort, int32, uint32, int64, uint64, float, double, string, datetime, enum, and the like.
  • the second data type is an unconventional data type, such as one or more of blob, anytime, pen, brush, font, graphics, audio, video, name, file, and the like.
  • the time attribute includes at least a time position, a start time, and an end time; when the management object is a static object, the space attribute includes at least a geospatial range, a geospatial location, and a spatial shape of the subspace, and a space. Scope and spatial location; when the management object is a dynamic object, the spatial attribute includes at least a geospatial location, a candidate geospatial location, and a spatial shape, a spatial extent, and a spatial location of the upper-level spatial model of the object to be managed.
  • the temporal model and the spatial model have a multi-level structure identified by a natural language definition name; the multi-level structure of the temporal model includes at least one parent-level temporal hierarchy and at least one associated with the natural language description The sub-level time hierarchy corresponding to the parent level time hierarchy; the multi-level structure of the space model includes at least one parent level space level by natural language description and at least one child level space level corresponding to the parent level space level.
  • the method for describing the transaction space attribute is to implement the spatial information annotation of the object to be managed according to the spatial state of the object to be managed, specifically: loading the geographic information coordinate system by the spatial object editor, and based on the geographical location of the object to be managed.
  • the position information and the spatial state information establish multi-level spatial objects through rectangles, irregular polygons, points and polylines, and realize spatial information annotation of each component of the multi-level structure to be managed object based on multi-level spatial objects.
  • the spatial information labeling process is: loading a geographic information coordinate system by using a spatial object editor, and drawing a spatial extent of a root root node based on the geographic location of the object to be managed, and using a rectangle within the root root node.
  • irregular polygon lines, points and polylines draw a spatial object to obtain the first-level spatial object of the object to be managed; based on the upper-level spatial object, use the rectangle, irregular polygonal line, point and polyline to implement the object to be managed step by step Forming a spatial drawing process of the element to obtain the hierarchical space object corresponding to the component element; matching the spatial state of the object to be managed with the spatial object of each level in the spatial object, thereby implementing the multi-level and/or multi-level object to be managed Spatial information annotation.
  • the spatial shape is a physical shape of an object to be managed, and the physical shape of the object to be managed realizes the description of the spatial shape by geometric points, lines, and faces;
  • the spatial range is an envelope of the object to be managed
  • the object to be managed is enveloped Representing a rectangle or a cube; and calculating a length, a width, and a height of a spatial range by using a spatial shape of the object to be managed;
  • the spatial location is location information describing a space to be managed by the object, the location information The precise location information and the logical location information are included; the precise location is at least a geographic coordinate location of the object to be managed, and the logical location is location information and/or relationship of each constituent element in the object to be managed, wherein the spatial object of the same level is included The positional relationship between the positional relationship and the spatial object of different levels.
  • the data of the object to be managed is collected by directly collecting historical data of the object to be managed from the object to be managed or collecting historical data of the object to be managed by calculation;
  • the sensor collects real-time data of the object to be managed or collects real-time data of the object to be managed by calculating; and generates plan data by importing a plan requirement from a third-party system interface.
  • the retrieval method prior to retrieving the data object, further comprises a method of describing an object and an event existing in the objective world based on a four-dimensional space, and the description method models the object to be managed to establish at least A history database, a real-time database, and a plan database of the time attribute of the object to be managed and the space attribute of the object to be managed are stored.
  • the retrieval method passes the management model category of the object to be managed, and the natural language
  • the described spatial attribute and/or time attribute finds a historical running state, a planned running state, and/or a real-time running state of the object to be managed.
  • the retrieval method performs a subscription through the to-be-managed object to find the to-be-managed a history running state, a planned running state, and/or a real-time running state of the object, wherein the subscribing method comprises at least the following steps: the client issues a spatial attribute including the management model category and the natural language description to the at least one data record to the spatio-temporal database And/or a subscription request of a time attribute; the time-space database actively pushes at least one data record of the object to be managed by the spatial attribute and/or the time attribute of the natural language description to the client in response to the subscription request.
  • the retrieval method of the present invention needs to determine a description method before the query of the object.
  • the present invention describes the object to be managed using a method based on four-dimensional space for describing objects and events existing in the objective world.
  • the retrieval of the objects to be managed is divided into a single query by time-space model and a subscription by time-space model. The difference between the two query methods is that after a single query by the space-time model is successful, the server will only send the query result once, and after the subscription is performed by the space-time model, the server will send the query result again after discovering the data change in the space-time scope.
  • the query and the subscription are performed by the management model category of the object to be managed, by means of spatial attributes and time attributes described by the natural language. Since there may be multiple real-time models to be managed in a real-time database, the structure of these models is different.
  • the management model class of the object to be managed, the spatial attributes and time attributes described by natural language can be used for query or subscription, which can be improved. The speed and accuracy of the query or subscription.
  • the historical database and the planning database are preferably queried or subscribed by using the management model class of the object to be managed, the spatial attribute and the time attribute described by the natural language.
  • Another aspect of the present invention also provides a data object retrieval device based on a spatiotemporal database, the retrieval device comprising at least a data collection module, at least one data calculation engine, a spatiotemporal runtime database, an engineering library server, a model library server, and a data acquisition module, configured to collect operation data of the management object, and send the operation data to the engineering database server by using the data calculation engine;
  • the model library server, the model library is disposed thereon
  • the model library is configured to model the management object for a time state and a space state of the object to be managed;
  • the engineering library server, the engineering library is disposed thereon, and the engineering library is configured to be configured according to a management model of the object to be managed sets a specific attribute of the object to be managed that is described by natural language;
  • the data calculation engine is configured to space the modeled management object according to a time level and a space level described by the natural language And time conversion;
  • the space-time running database, the space-time running database includes History database
  • Yet another aspect of the present invention also provides a method for describing an object and an event existing in an objective world based on a four-dimensional space, the method modeling a object to be managed to establish a time attribute in which at least the object to be managed is stored and The historical database, the real-time database, and the plan database of the object to be managed, wherein the method for modeling the object to be managed includes at least the following steps: modeling the object to be managed according to the spatial state of the object to be managed, The time state of the object to be managed is modeled, the specific attribute of the object to be managed is set, and the data of the object to be managed is collected to dynamically monitor and manage the object to be managed.
  • the method for modeling an object to be managed includes at least the following steps: classifying the object to be managed into a historical data model, a real-time data model, and/or a plan data model according to spatial attributes and/or time attributes, according to a to-be-managed Modeling the object to be managed according to the temporal state of the object, modeling the object to be managed according to the time state of the object to be managed, setting a specific attribute of the object to be managed, and collecting data of the object to be managed Dynamically monitoring and managing the object to be managed.
  • the modeling of the object to be managed according to the spatial state of the object to be managed includes at least the following steps: modeling the space of the object to be managed according to the spatial state of the object to be managed to establish a space a model, the spatial model of the object to be managed is instantiated to establish a spatial object; and the modeling of the object to be managed according to the time state of the object to be managed includes the following steps: according to the time state of the object to be managed The time at which the management object is described is modeled to establish a time model, and the time model of the object to be managed is instantiated to establish a time object.
  • the method for modeling the space of the object to be managed according to the spatial state of the object to be managed to establish a spatial model is to determine a multi-level space model according to the spatial state of the object to be managed; Managing the Time State of the Object Modeling the time of the object to be managed to establish a time model determines a multi-level time model based on the temporal state of the object to be managed.
  • the spatial model of the object to be managed and the temporal model of the object to be managed are associated to establish a historical data model, a real-time data model, and a plan data model.
  • the historical data model is instantiated as a historical data object, and the historical data object is associated with a spatial object instantiated by the spatial model associated with the historical data model and is associated with the historical data model
  • Temporal model instantiates the generated temporal object; instantiates the real-time data model as a real-time data object, and associates the real-time data object with a spatial object instantiated by the spatial model associated with the real-time data model and by the The time model associated with the real-time data model instantiates the generated time object; instantiates the plan data model as a plan data object, and associates the plan data object with a spatial object instantiated by the spatial model associated with the plan data model The generated time object is instantiated with the time model associated with the plan data model.
  • the historical data object is configured as a historical database after the computer space attribute is configured, the real-time data object is configured as a real-time database, and the planned data object is configured as a computer database attribute to become a plan database, and the plan data object is configured as a plan database.
  • the historical database is used to store historical data of the object to be managed, the real-time database is used to store real-time data of the object to be managed, and the plan database is used to store plan data of the object to be managed.
  • the specific attribute of the object to be managed includes at least a time attribute of the object to be managed and a space attribute of the object to be managed, and the time attribute includes at least a time position, a start time, and an end time.
  • the spatial attribute includes at least a geospatial range, a geospatial location, and a shape size profile.
  • the spatial attribute includes at least a geospatial location and a candidate geography. A spatial location and a shape size profile of the spatial extent of the object to be managed.
  • the specific attribute of the object to be managed further includes the first data type of the object to be managed and the first The properties of the two data types.
  • the attribute of the second data type includes at least one or more of a graphic attribute, an audio attribute, a video attribute, and a name attribute of the object to be managed.
  • the data of the object to be managed is collected by collecting the historical data of the object to be managed directly from the object to be managed or collecting the historical data of the object to be managed by calculating
  • the sensor collects real-time data of the object to be managed or collects real-time data of the object to be managed by calculation, and imports plan requirements from a third-party system interface and generates plan data through calculation.
  • Yet another aspect of the present invention also provides a method of describing a transaction time attribute and performing a lookup based on the description, the method modeling a object to be managed to establish a time attribute storing at least the object to be managed and the a historical database, a real-time database, and a plan database of the spatial attributes of the object to be managed, and searching for the historical running state, the planned running state, and the planned running state of the object to be managed by the management model category, the space attribute, and/or the time attribute of the object to be managed And a real-time running state, wherein the method for modeling the object to be managed includes at least the following steps: modeling the object to be managed according to the spatial state of the object to be managed, and the object to be managed according to the time state of the object to be managed Modeling, setting a specific attribute of the object to be managed, and collecting data of the object to be managed to dynamically monitor and manage the object to be managed.
  • the spatial attribute and/or time attribute of the object to be managed is a custom multi-level structure, and the time attribute is described by a natural language based on a production industrial process and/or daily life specification. of.
  • the time attribute includes at least a time position, a start time, and an end time.
  • the space attribute includes at least a geospatial range, a geospatial location, and a shape and size profile.
  • the spatial attribute includes at least a geospatial location, a candidate geospatial location, and a shape size profile of the spatial extent of the object to be managed.
  • the search range is determined by the spatial attribute of the object to be managed, and then the historical running state, the real-time running state, and/or the planned running state of the object to be managed are searched based on the time attribute of the object to be managed.
  • the method for modeling the object to be managed is: classifying the object to be managed into a historical data model, a real-time data model, and/or a plan data model according to the spatial attribute and/or the time attribute, according to the object to be managed
  • the space state is used to model the object to be managed
  • the object to be managed is modeled according to the time state of the object to be managed
  • the specific attribute of the object to be managed is set
  • the data of the object to be managed is collected to Management object dynamic monitoring and management.
  • the modeling of the object to be managed according to the spatial state of the object to be managed includes at least the following steps: modeling the space of the object to be managed according to the spatial state of the object to be managed to establish a space a model, the spatial model of the object to be managed is instantiated to establish a spatial object; and the modeling of the object to be managed according to the time state of the object to be managed includes the following steps: according to the time state of the object to be managed The time at which the management object is described is modeled to establish a time model, and the time model of the object to be managed is instantiated to establish a time object.
  • the spatial model of the object to be managed and the temporal model of the object to be managed are associated to establish a historical data model, a real-time data model, and a planning data model
  • the historical data model is instantiated as a historical data object
  • the historical data object is configured to be a computer history attribute to be a historical database storing the historical data of the object to be managed
  • the real-time data model is instantiated as a real-time data object, and the real-time data object is configured into a computer space
  • the attribute is a real-time database that stores the real-time data of the object to be managed
  • the plan data model is instantiated as a plan data object, and the plan data object is configured with a computer space attribute to become a plan for storing the plan data of the object to be managed. database.
  • the specific attribute of the object to be managed includes at least a time attribute of the object to be managed and a space attribute of the object to be managed, and a first data type and a second data type of the object to be managed An attribute, and the attribute of the second data type includes at least one or more of a graphic attribute, an audio attribute, a video attribute, and a name attribute of the object to be managed.
  • the data of the object to be managed is collected by collecting the historical data of the object to be managed directly from the object to be managed or collecting the historical data of the object to be managed by calculating Sensor acquisition
  • the real-time data of the object to be managed or the real-time data of the object to be managed is collected by calculation, and the plan data is imported from the third-party system interface and the plan data is generated by calculation.
  • Still another aspect of the present invention provides a method for describing a transaction space attribute and performing a search based on the description, and the method for describing the transaction space attribute is to implement spatial information annotation of the object to be managed according to the spatial state of the object to be managed.
  • the geographic information coordinate system is loaded by the spatial object editor, and multi-level spatial objects are established through rectangles, irregular polygons, points, and polylines based on the geographic location information and spatial state information of the object to be managed, and the multi-level spatial object is implemented based on the multi-level spatial object.
  • Hierarchical structure The spatial information of each component of the object to be managed is marked; and the object is searched according to the spatial object information of the object to be managed.
  • the spatial information labeling process is: loading a geographic information coordinate system by using a spatial object editor, and drawing a spatial extent of a root root node based on the geographic location of the object to be managed, and using the root root node range Rectangles, irregular polygon lines, points, and polylines draw a spatial object to obtain the first-level spatial object of the object to be managed; based on the upper-level spatial object, implement the object to be managed step by step with rectangles, irregular polygon lines, points, and polylines
  • the spatial drawing process of the constituent elements to obtain the hierarchical space object corresponding to the constituent elements; matching the spatial state of the object to be managed with the spatial objects of the spatial objects in the spatial object, thereby realizing multi-level and/or multi-level management objects to be managed Spatial information annotation.
  • the spatial attribute of the object to be managed is a multi-level structure based on a custom industrial process;
  • the upper spatial object is the parent of the secondary spatial object, and the secondary spatial object is the upper space a child object of an object;
  • the child object has a parent object, and the parent object includes at least one child object.
  • the spatial object is a description of a spatial property of the object to be managed, the spatial object comprising a description of the spatial shape, the spatial extent and the spatial location of the object to be managed.
  • the method for searching based on the description of the transaction space attribute is specifically: based on the spatial object information of the multi-level and/or multi-level to-be-managed object including the spatial shape, the spatial extent and the spatial location. Search.
  • the spatial shape is a physical shape of the object to be managed, and the physical shape of the object to be managed realizes the description of the spatial shape by geometric points, lines, and faces.
  • the spatial extent is an object envelope to be managed, the envelope of the object to be managed is represented by a rectangle or a cube; and the length and width of the spatial range are calculated by the spatial shape of the object to be managed. ,high.
  • the spatial location is location information describing that the object to be managed is spatially located, the location information includes precise location information and logical location information; the precise location is at least a geographic coordinate of the object to be managed a location, where the logical location is location information and/or relationship of each component element in the object to be managed, and includes a positional relationship between the spatial models of the same level and a positional relationship of the spatial model of the different levels.
  • the object to be managed includes a static object including a precise location of the object to be managed and a static location in a static and/or logical position;
  • the dynamic object includes an accurate object to be managed
  • the location is dynamic and/or the logical location is dynamic;
  • the logical location information of the to-be-managed object includes logical location definition information of the object to be managed and logical location relationship information, and the logical location of the to-be-managed object is defined as a natural language
  • a token of the object to be managed is implemented;
  • the logical location relationship information of the object to be managed includes a membership relationship and/or a hierarchical relationship of the location.
  • Still another aspect of the present invention provides a method for organizing object data
  • the method for organizing object data includes a process of defining object data and a process of running object data, and classifying objects to be managed into corresponding categories according to natural attributes of the object And assigning a category attribute corresponding to the related category to the data record corresponding to the object to be managed, at least including the time attribute and the space attribute; according to the data record including the time attribute and the space attribute of the object to be managed, Realizing that the data record is associated with the natural attribute of the object to be managed and completing the instantiation; and the data record of the object to be managed stored in the real-time database, the historical database and the plan data that is completed and instantiated is based on the spatial shape and the spatial outline including the data
  • the spatial attribute of the spatial location description implements a first update of the data record; the number of completed spatial attributes that are to be stored in the real-time database, the historical database, and the plan database
  • the second update is implemented based on the time attribute including the time position, the
  • the organizing method of the object data further comprises: retrieving the member information of the object to be managed based on the management model category of the object to be managed.
  • the retrieving comprises completing the member information retrieval of the corresponding type of the corresponding object in the corresponding spatiotemporal based on the time information, the spatial information and the management model category; the retrieving comprises completing the corresponding time based on the time information and the type of the member information.
  • the type of information completes the member information retrieval of the corresponding types of at least one object in each time period and each space.
  • the type of the member information includes at least a first data type and a second data type.
  • the first data type is a regular data type, such as byte, bool, int8, short, ushort, int32, uint32, int64, uint64, float, double, string, datetime, enum, and the like.
  • the second data type is an unconventional data type, such as one or more of blob, anytime, pen, brush, font, graphics, audio, video, name, file, and the like. More preferably, the unconventional data types may also be date types, binary, resources, pens, brushes, and fonts. That is, the object to be managed can implement multi-directional description of the object to be managed by including member information of date, binary, resource, pen, brush, and font.
  • the resource type member information includes at least 2D graphics, 3D graphics, text, pictures, subset XML under standard standard markup language, HTML, report, audio and video information related to the object to be managed.
  • the brush comprises solid colors, hatching, texture, linearity and paths.
  • the first update of the data record is a spatial attribute of the real-time database, the plan database and the history database based on the description of the object data including the spatial shape, the spatial outline and the spatial position of the data.
  • the second update of the data record is a process for classifying and storing the plan database and the history database based on time attributes of the object data, wherein the time attribute includes a time corresponding to the object data a description of the location, the start time, and the end time; the second update of the data record further includes a process of classifying and storing the real-time database based on time attributes of the object data, wherein the time attribute includes a corresponding one of the object data A description of the time position, start time, and elapsed time.
  • the state information retrieval of the data or the object to be managed is implemented based on the spatial attribute description and/or the time attribute description of the data.
  • the data-based spatial attribute description implements state information retrieval for different time periods of the specific space and/or objects included in the data corresponding to the spatial attribute description;
  • the time attribute describes a state information retrieval of a space and/or object included in the corresponding data to realize a different space at a specific time; and the data corresponding to the time attribute description and the space attribute description is implemented based on the time attribute description and the space attribute description of the data.
  • the spatial shape is a physical shape corresponding to the object data or the object to be managed, and the physical shape corresponding to the object data realizes the description of the spatial shape by geometric points, lines, and faces;
  • the contour is an envelope corresponding to the object data or the object to be managed, and the envelope corresponding to the object data is represented by a rectangle or a cube; and the origin, length, and width of the spatial contour are calculated by the spatial shape corresponding to the object data.
  • the spatial location is a description of the object data or a pair to be managed
  • the location information includes location information and logical location information
  • the precise location is at least the object data or a geographic coordinate location corresponding to the object to be managed, where the logical location is The position information and/or relationship of each component element in the object data, wherein the positional relationship between the spatial models of the same level and the positional relationship of the spatial model of different levels are included.
  • the object data or the object to be managed includes a corresponding static object and a corresponding dynamic object, the static object including the object data or the precise location of the object to be managed is in a static and/or logical position.
  • Static the dynamic object includes the object data or the precise location of the object to be managed is in a dynamic and/or logical position
  • the object data or the logical location information corresponding to the object to be managed includes the corresponding logical location definition information
  • logical location relationship information the logical location relationship information corresponding to the object data includes a membership relationship and/or a hierarchical relationship of the location.
  • Still another aspect of the present invention provides a method for subscribing to object data based on a spatiotemporal database, the method comprising the steps of: the client issuing a spatial attribute including a management model category and a natural language description to the at least one data record to the spatiotemporal database And/or a subscription request of a time attribute; the time-space database actively pushes at least one data record of the object to be managed by the spatial attribute and/or the time attribute of the natural language description to the client in response to the subscription request.
  • the subscription request is sent in a manner related to a model category of the object to be managed, and the model categories of the object to be managed are respectively to be managed in a real-time database, a historical database, and/or a plan database.
  • the properties of the object, and the data model for each category contains one or more objects.
  • the subscribing method further includes: when the client is in an open state, the spatiotemporal database records a subscription request of the client, and the spatiotemporal database detects the client subscription
  • the space-time running database actively sends at least one data record including the to-be-managed object space attribute and/or the time attribute and/or the model category to the client;
  • the client When the client is in the closed state, the client sends an unsubscribe request to the spatio-temporal running database.
  • the modeling of the spatiotemporal database includes the following steps: modeling the object to be managed according to the spatial state of the object to be managed; and managing the to-be-managed according to the time state of the object to be managed
  • the object is modeled; the specific attributes of the object to be managed are set; the modeled object to be managed is classified into a model of a specific model category according to a specific attribute.
  • the spatiotemporal database comprises a real time database, a historical database and a planning database of the objects to be managed.
  • the modeling of the object to be managed according to the spatial state of the object to be managed includes modeling the space of the object to be managed according to the spatial state of the object to be managed to establish a space. model.
  • the modeling of the object to be managed according to the time state of the object to be managed includes modeling the time of the object to be managed according to the time state of the object to be managed to establish a time model.
  • the setting the specific attribute of the object to be managed includes setting a first data type of the object to be managed and an attribute of the second data type.
  • the attribute of the second data type includes at least one or more of a graphic attribute, an audio attribute, a video attribute, and a name attribute of the object to be managed.
  • the time attribute described by the natural language is an attribute that is to be customized according to the time state of the object to be managed, and the time attribute of the object to be managed by the natural language includes at least a basis.
  • the spatial attributes described by means of natural language comprise spatial attributes that are customized according to the spatial shape, spatial extent and spatial position of the object to be managed.
  • the present invention describes data information of production monitoring management through historical, real-time and planned three-dimensional time dimensions, and the user does not need Mastering the computer language, you only need a natural space-time meta-language to view and manage the history of the object, the real-time and the running status of the three time periods.
  • the invention solves the problems of various system applications through a database, can reduce the user's investment and the maintenance cost of the system, and can retrieve the objects in the model according to space and/or time during data query and retrieval. Fast and convenient for production management.
  • FIG. 1 is a block diagram showing a device for retrieving a data object based on a spatiotemporal database according to the present invention
  • FIG. 2 is a schematic diagram of a custom space model of a preferred embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a custom time model of a preferred embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a system time model of a preferred embodiment of the present invention.
  • Figure 5 is a diagram showing the spatiotemporal transition relationship between data models in a preferred embodiment of the present invention.
  • Object to be managed 200 Data acquisition module 300: Data calculation engine
  • Run time database 410 Real-time database 420: Historical database
  • Planning Database 500 Engineering Library Server 510: Object Definition Module
  • Cache module 820 Login module
  • the four-dimensional space refers to the three-dimensional space of the object to be managed plus one-dimensional time.
  • a spatiotemporal database is a database built on data with temporal and spatial properties.
  • the spatio-temporal database includes a historical database, a real-time database, and a planning database, which respectively store modeled historical data, real-time data, and planning data of the management object.
  • Each data in the spatio-temporal database has spatial and temporal properties.
  • This embodiment provides a method for retrieving data objects based on a spatiotemporal database, and the retrieval method includes the following steps:
  • S1 The management object is modeled for the time state and the space state of the object to be managed.
  • a time model, a space model, and/or a management model are respectively established according to the time state and the space state of each object to be managed.
  • Time model is a data model used to describe the time state of an object to be managed.
  • the time granularity of the time model is a measure of the time state and time hierarchy, including time units and time parameters customized based on production conditions.
  • the time model is a model describing the time granularity of the object to be managed. For example, the time granularity is year, month, day, hour, minute, or second. You can also customize the time granularity, such as shifts or batches.
  • a spatial model is a data model used to describe the spatial state of an object to be managed.
  • the spatial granularity of a spatial model is a spatial parameter that measures spatial hierarchy and spatial location, including spatial units and spatial parameters that are customized based on production conditions.
  • the spatial granularity is the head office, branch, workshop, production line, process, station or equipment.
  • the time model and the spatial model have a multi-level structure identified by a natural language definition name.
  • the multi-level structure of the time model includes at least one parent-level time hierarchy described by natural language and at least one child-level time hierarchy corresponding to the parent-level time hierarchy.
  • the time hierarchy includes year, month, day, hour, minute, or second.
  • Year is the parent-level time level of the month
  • the month is the year Sub-level level.
  • Month is the parent-level time level of the day
  • the day is the child-level level of the month.
  • the time hierarchy can also be orders, work orders, and products that are described in natural language.
  • the order is the parent level time level of the work order, and the work order is the sub-level level of the order.
  • One work order corresponds to multiple products, and one product only corresponds to one work order.
  • the multi-level structure of the spatial model includes at least one parent level space level described by natural language and at least one child level space level corresponding to the parent level space level.
  • a management model formed by the association of the spatial model and the temporal model of the object to be managed is established.
  • the management model is a data model for describing the spatial state and temporal state of the object to be managed.
  • the data is associated with the time model and the spatial model to form a spatiotemporal model.
  • the spatio-temporal model is a data model that effectively organizes and manages temporal spatial data with more complete attributes, spatial and temporal semantics.
  • the time and space model is used to monitor the time state and space state of the object to be managed, so that the running state of the object to be managed can be fully understood.
  • the present invention refers to the space-time model of the management object as a management model.
  • Each managed object described is instantiated by the management model.
  • the management model forms at least one management object consisting of the time object of the management object and the spatial object association through the instantiation process.
  • the time object of the management object is formed by the time model in the instantiation process
  • the space object of the management object is formed by the space model in the instantiation process.
  • a device is a thing, and a device processing product is one thing.
  • the product is time, which is the time when the equipment is processed. This time has a time position, start production time and end production time. The time position is the only product number. If it is real-time data, the product number, the start of production time, and the elapsed time are changed to historical data. Elapsed time refers to the length of time the product is produced. Continue to scan the device for the next time (product) content.
  • the present invention models data based on past, present, and future time periods.
  • the data model is divided into real-time data model, historical data model, and planning data model according to the time state. According to the function, it is divided into data, alarm and event. There are more kinds of data in the combination of tense and function.
  • the data model has a version. In a system, multiple versions of the same model can exist. An example of a model corresponds to a version of the model. The model does not affect the instances that have been generated when the new version is generated. When a version of a model is modified, it affects the instance generated by that version of the model.
  • a data model is a model that describes data.
  • the data model consists of two parts: attributes, members. Attributes are specific parts of data, such as name, description, time, space, attributes are defined by the system, and users cannot be defined. Depending on the classification, the properties of the data model will vary, such as real-time data, with freshness attributes.
  • Event data has attributes such as start time, end time, duration, and so on.
  • Members are part of the data, and users can define different members to describe the data in the business.
  • Members' data can use the various types defined above. In terms of performance, the number of members is limited to a maximum of 256 members. Preferably, for the attribute name, the member name is not allowed to exceed 64 characters.
  • the management model of the present invention specifies an associated time model and spatial model.
  • the present invention simply refers to a data model including a temporal model and a spatial model as a spatiotemporal model.
  • the performance model of station processing the space attribute is the station, and the time attribute is the class.
  • Other attributes of the data may be work order number, processing quantity, number of alarms, number of rework, and the like.
  • the data of these data models is completed by a computational model that calculates and detects changes in production data and outputs statistical performance data to the performance model.
  • Factory modeling is based on the previous model for factory instantiation.
  • Real-time data models, historical data models, and planned data model distributions are instantiated as real-time data objects, historical data objects, and planning data objects.
  • the actual plant name, line name, device name, and process name which is space instantiation.
  • the affiliation of each object is also determined during the instantiation. There are several shifts a day, and how long each shift is. This is time instantiation.
  • the actual production line has several process performance data, which is the instantiation of the performance data model. Of course there is also the instantiation of calculations because of the performance data to be calculated.
  • System operation After the system is running, the system automatically detects the production information in the background, records the production status of each process, and calculates the production performance of each station in real time. At this point, the production status of a factory is recorded in real time to the space-time database. When the user needs to view, query the real-time and historical production data information in the scene model.
  • the plan will usually be formulated into a general plan, such as the entire plant year plan, and then decomposed into the whole plant month, the whole plant day, the whole plant class, Workshop month, workshop day, workshop class. Users only need to decompose the space and time to a very fine level, and then perform a time and space level to monitor whether it is executed as planned.
  • the time attribute and the spatial attribute are independent.
  • the level of the year is the year, and the precision can be either seconds or milliseconds.
  • the time object has a time position on the data record, a start time and an end time of the time position.
  • the start time of the time position is 0:00:00.000 on March 1, 2016, and the end time is 23:59:59.999 on March 31, 2016.
  • the time position can also be customized.
  • March 2016 is from a custom fiscal year (parent time level) - fiscal month (sub-time level), the start time and end time are user-defined, such as March 2 - March 15, 2016 When the user uses the March 2016 fiscal year to indicate this time period.
  • S21 classify the modeled object to be managed into a specific model according to the time attribute.
  • the management model includes real-time data objects stored in a real-time database formed according to time attribute classification, historical data objects stored in the history database, and planned data objects stored in the plan database.
  • Historical data objects, real-time data objects, and scheduled data objects contain at least time attributes and spatial attributes.
  • the historical objects in the historical data object are configured with corresponding computer space attributes, and the historical data is automatically stored in the computer's historical database.
  • the real-time objects in the real-time data objects are configured with the corresponding computer space attributes, and the real-time data is automatically stored in the real-time database of the computer.
  • the plan objects in the plan data object are configured with the corresponding computer space properties, and the plan data is automatically stored in the computer's plan database.
  • the historical database, the real-time database, and the planning database constitute the spatiotemporal database of the present invention.
  • the historical database stores the historical data of the object to be managed according to the configured conditions.
  • the real-time database is used to store real-time values of objects to be managed.
  • the planning database is used to store planning data for objects to be managed.
  • Historical databases, real-time databases, and scheduled databases do not require user configuration. When using the user, you need to specify the real-time server, history server, and schedule server through the configuration interface.
  • the spatio-temporal database system runs, and each server client automatically sends the data to the corresponding server. For example, the real-time data client will transmit the real-time data generated by the system to the real-time data server.
  • the real-time data server will automatically create a table or mapping list in the database and store the relevant data in the database of the corresponding server. The same is true for the history and planning database.
  • the storage mechanism of the present invention is not limited thereto, and includes other storage mechanisms.
  • the real-time data object includes at least one management object formed by real-time data of the management object formed by the real-time data model instantiation process.
  • the spatial model associated with the real-time data model is instantiated as a spatial object.
  • the time model associated with the real-time data model is instantiated as a time object.
  • the real-time data objects of the managed objects are associated with the spatial objects and the temporal objects, respectively.
  • a management model is instantiated into multiple management objects.
  • the data structure of real-time data of multiple management objects formed by instantiating a version of the real-time data model is the same.
  • the plurality of management objects formed after the real-time data model is instantiated are stored in the real-time database.
  • the historical data object includes at least one management object composed of historical data of the management object formed by the historical data model instantiation process. It is instantiated as a historical data object based on the historical data model.
  • the spatial model associated with the historical data model is instantiated as a spatial object.
  • the time model associated with the historical data model is instantiated as a time object.
  • the historical data objects of the managed objects are associated with the spatial objects and the temporal objects, respectively.
  • a management model is instantiated into multiple management objects.
  • the data structure of the historical data of a plurality of management objects formed by instantiating a version of the historical data model is the same.
  • the plurality of management objects formed after the historical data model is instantiated are stored in the history database.
  • the plan data object includes at least one management object formed by the plan data of the management object formed by the plan data model instantiation process. Instantiated as a plan data object based on the plan data model.
  • the spatial model associated with the plan data model is instantiated as a spatial object.
  • the time model associated with the plan data model is instantiated as a time object.
  • the plan data object of the management object is associated with the space object and the time object, respectively.
  • a management model is instantiated into multiple management objects. Multiple versions of a version of the planned data model instantiated
  • the data structure of the plan data of the object is the same.
  • a plurality of management objects formed after the plan data model is instantiated are stored in the plan database. There is a big difference between the storage of historical data, real-time data, and planning data.
  • the temporal state of real-time data is real-time, representing the current time of the data, with the characteristics of freshness, that is, the refresh cycle of its data should conform to its time granularity. For example, if the freshness of an object is 5 seconds, its refresh period should also be 5 seconds, and if it is not refreshed within 5 seconds, the object is not fresh.
  • Real-time data requires high real-time performance, and it can refresh real-time data of millions of records per second. There is a fresh limit for data that is not refreshed in time. Real-time data beyond the fresh period is transformed into historical data.
  • Historical data tenses are historical, representing data from past time. Historical data for industrial processes are mostly time series data that can be compressed. Business data in historical data can also be stored in an uncompressed manner.
  • the planned data tense is the future, representing data for future time. Plan data is calculated based on historical data and real-time data.
  • Real-time data objects stored in real-time databases are organized according to spatial characteristics for easy storage and retrieval.
  • Historical data objects and planning data objects of historical and planning databases are first organized according to spatial characteristics and then organized according to time characteristics.
  • the data objects stored in the historical database, the real-time database, and the plan database must have time attributes.
  • Time is an inseparable attribute of the object to be managed. Without time, objects cannot exist.
  • a time object is a description of the time position of the object to be managed.
  • the time attribute includes at least a time position, a start time, and an end time.
  • the time position of the management object includes at least the time level and the level precision of the object to be managed.
  • a production batch is a hierarchy. The first batch of information in a workshop is very convenient for users to use and does not need to write a certain period of time to obtain possible batch information.
  • each management model has a unique temporal hierarchy and spatial hierarchy.
  • a production line (space) class (time) plan is described.
  • the production line model and the class model are the defined space model and time model.
  • the production line model is assumed to have three production line objects in the engineering stage.
  • the class model has three classes of A, B and C. Then the data model can only instantiate a total of 9 planning data objects for 3 teams in 3 production lines, and cannot instantiate plans for other time and space levels.
  • the time and space levels of the management model are determined to be no longer modifiable, and new versions will only be generated if the attributes are modified or changed.
  • the space of the object to be managed is modeled according to the spatial state of the object to be managed to establish a space model.
  • a spatial model having a multi-level structure forms a multi-level spatial object through an instantiation process.
  • the method of instantiating a multi-level spatial object includes: loading a map through a spatial object editor or a CAD image of an object to be managed as a base map Drawing a spatial object as a first-level spatial object in the base map according to the spatial coordinates of the object to be managed, and/or drawing a spatial object as a first-level spatial object in the base map according to the customized spatial range;
  • a spatial object is drawn as a second-level spatial model in the n-1 level space model.
  • the process of drawing a spatial object is as follows.
  • S201 Load a map or a CAD drawing of the object to be managed as a base map by using a space object editor.
  • a space object editor Preferably, the Google map, the Baidu map, or the CAD drawing of the object to be managed is loaded as a base map by the space object editor.
  • S202 Draw a spatial object as a first-level spatial model in the base map.
  • the corresponding coordinate system is selected, and the spatial extent of a Root root node is drawn based on the geographical location of the factory, and rectangles, irregular polygonal lines, points, and/or polylines are used in the space range of the Root root node.
  • rectangles, irregular polygonal lines, points, and/or polylines are used in the space range of the Root root node.
  • S203 Draw a spatial object as a second-level spatial model in the first-level spatial model.
  • a spatial object is drawn within the first level space model with rectangles, irregular polygonal lines, points and/or polylines to obtain a second level spatial model.
  • a spatial object is drawn as the nth-level spatial model in the n-1th-level spatial model.
  • a spatial object is drawn with rectangles, irregular polygonal lines, points and/or polylines in the n-1th-level spatial model to obtain an nth-level spatial model.
  • Specific attributes include time attributes, spatial attributes, and/or non-temporal attributes described by natural language.
  • the object to be managed includes a custom non-time-space attribute in addition to the time attribute and the space attribute.
  • the non-temporal attributes of the object to be managed include the first data type of the object to be managed and the attribute of the second data type.
  • the attribute of the second data type includes at least one or more of a graphic attribute, an audio attribute, a video attribute, and a name attribute of the object to be managed.
  • a picture type as a member of a graphic object
  • the display device will draw the picture onto the screen.
  • file type resource objects it can be used for file transfer and storage, such as saving process files and issuing operational specifications.
  • Graphic types are also data types and can also be used as members of objects.
  • the coordinates of the graphic type are pixel coordinates.
  • the geometry type is the shape that describes the geospatial object and needs to be configured on the properties of the spatial object.
  • the time attribute includes at least a time position, a start time, and an end time.
  • the time position is relative to the parent space model.
  • the spatial attributes of each data in the database include geospatial extent, geospatial location, subspace shape, size and profile, candidate geospatial location, computer space, candidate computer space attributes, and the like.
  • the spatial attribute when the management object is a static object, includes at least a geographical space range, a geospatial location, and a spatial shape, a spatial extent, and a spatial location of the subspace.
  • the spatial attribute when the management object is a dynamic object, includes at least a geospatial location and a candidate geography. The spatial position, spatial extent, and spatial location of the spatial location and the upper-level spatial model of the object to be managed.
  • the space of the repairman is the workshop, and the space location is the equipment.
  • the space location of the repairman is described as: the repairman is next to the No. 2 equipment in the workshop.
  • the spatial extent is the parent space and the spatial location is the child space.
  • the order of the sequential steps S21 and S22 is not limited.
  • the data of the management object stored in the spatiotemporal database includes historical data directly collected from the management object site, real-time data collected by the management object by the sensor, and plan data of the object to be managed calculated according to the historical data and the real-time data. .
  • historical data and planning data are generated by calculation.
  • the data in the planning database may also be graphically edited by the interface interaction or imported from a software interface of a third party system.
  • the plan data is imported through a third-party program interface or a third-party file, and after the system recognizes the plan data, the plan data is calculated through an interface editing and calling algorithm.
  • S3 Retrieving based on the management model category of the management object and the spatial attribute and/or time attribute defined by the natural language defined by the modeling to determine the running state of the management object. Retrieving real-time data, historical data, and/or planning data of at least one management object at a spatial location and/or time based on a management model category, spatial location, and/or time of the management object to determine a real-time operational state of the at least one management object , historical operational status, and/or planned operational status.
  • the management object-based management model category and the model-defined spatial attribute and/or time attribute defined by the natural language to determine the management object running state include: determining the storage management object running data according to the management object type of the management object Real-time database, historical database and/or planning database; selecting at least one version of management object running data related to the management object in the real-time database, the historical database, and/or the planning database according to the spatial attribute and/or the time attribute; determining and managing the model Associate at least one management object and view real-time data, historical data, and/or planning data of the management object to understand the real-time running status, historical running status, and/or planned running status of the managed object.
  • the user inputs a spatial attribute of the management object, a management model category, and time attribute data.
  • the system determines the machine node based on the spatial attribute input by the user, and then determines a real-time database, a historical database, and/or a plan database storing the operational data of the management object according to the management model category, and then determines the specific data according to the time attribute. More preferably, after determining the database, selecting at least one version of the management object related to the management object in the real-time database, the historical database, and/or the plan database according to the time and/or spatial location, time range and/or spatial extent input by the user Operating data.
  • the user runs data according to the displayed management object of at least one version, determines a version of the management object running data, and views a plurality of management objects instantiated by the version management model.
  • you can view the real-time data, historical data and/or planning data of the managed object to understand the real-time running status, historical running status and/or planned running status of the managed object.
  • This embodiment is a further improvement based on the embodiment 1.
  • the planning data model establishes and updates at least one planning data model comprising different versions of the same time state and spatial state according to the user's set version. That is, there are multiple versions of the plan data model stored in the plan database. Multiple versions of the plan data model are instantiated into multiple versions of the plan data objects. Select a version of the plan data model that uses multiple versions to determine the version of the plan data object.
  • the planning data object is the management object.
  • the multi-version model of the planning data model is important.
  • a plan change will correspond to a series of sub-plan changes, and the plan can be easily found through a consistent version of the plan database.
  • the current plan needs to be issued, and the plan being executed must be a specific version of the plan data.
  • two running record versions may be created.
  • the actual production time planning data object will only select one version to execute. Therefore, there is a difference between the planned data model version and the recorded version of the planned data object.
  • the user sets up and stores multiple versions of the plan data model on the computer. Due to frequent changes to the plan record, the plan database establishes and updates multiple versions of the plan data objects for the same space and time. For example, in actual operation, scheduled run records for different scheduled data objects may be uniformly updated. For example, if the shop plan record changes, the team plan record will change. Users can unify the plan changes for easy viewing.
  • the real-time data model includes at least one different version of the real-time data model that is built and updated based on the same time state and spatial state. Different versions of the real-time data model are instantiated into different versions of the plan data objects and stored in the real-time database.
  • the same real-time data model can have multiple versions to instantiate multiple real-time data objects. For example, a shop is upgraded, new and old systems coexist, and new and old systems use two versions of a data model. Monitor the system objects in the new and old versions. If a real-time data object is upgraded, switch to the new version. When the history is stored, the history corresponding to each version will be stored.
  • the historical data model establishes and updates at least one version of the historical data model based on at least one different version of the real-time data model. Different versions of historical data models are instantiated into different versions of historical data objects and stored in the historical database.
  • Historical data objects can have multiple versions of values at the same time. There are several situations when modifying historical data objects:
  • the historical data value version is unchanged, and the data is modified to cover the original historical record.
  • the historical data value is increased by version, that is, a history is added.
  • the way the historical data is modified is set by the user. If the user sets the modification method of the historical data to not allow the original record to be modified, the historical data is modified, and a new version of the historical data record is generated.
  • Historical data playback of different versions of the historical data model can not only see the historical data of each system, but also view historical changes.
  • the shop acquisition model V1 version only supports the acquisition of two parameters of temperature and humidity.
  • the management object, the shop 1 object is established, and the values of temperature and humidity collected are stored in the history database.
  • the version of the corresponding model is also recorded in the history library.
  • On-site system after running for a period of time Upgrade in addition to collecting temperature and humidity, also need to collect pressure, then the acquisition model is upgraded to V2 version, increasing the pressure parameters.
  • shop 1 object After the shop 1 object is upgraded, shop 1 starts to collect three values of temperature, humidity and pressure, and stores the corresponding values in the database. In this way, in the history library, the historical data generated in the case of different versions of the shop 1 will be recorded.
  • the first version has only two parameters, temperature and humidity.
  • the second version includes three parameters: temperature, humidity and pressure.
  • the user After inputting the management model category, time data, and/or spatial data, the user retrieves two versions of the real-time data object, the historical data object, and the plan data object of the object. Users can select one of the versions of real-time data objects, historical data objects, and planning data objects to understand the real-time, historical, or planned operational status of the object. Users can also open two versions of real-time data objects at the same time, and check the data of two data at the same time.
  • a data object retrieval device based on a spatiotemporal database includes a data collection module 200, at least one data calculation engine 300, a spatiotemporal database 400, an engineering library server 500, a model library server 600, and at least one graphic.
  • the data collection module 200 is configured to collect data information of the object 100 to be managed.
  • the data calculation engine 300 is configured to perform data conversion on the collected data.
  • the spatiotemporal run database 400 includes a real time database 410, a historical database 420, and a plan database 430.
  • the real-time database 410, the history database 420, and the plan database 430 are respectively configured to store at least one version of real-time data objects, historical data objects, and plan data objects formed based on at least one version of the real-time data model, the historical data model, and the plan data model instantiation.
  • a model library is set on the model library server 600.
  • the model library is used to build a time model, a space model, a management model, and a calculation model, and is used by the engineering library 500.
  • An engineering library is provided on the engineering library server 500.
  • the engineering library is used to import the model related to the solution in the model library 600, and to instantiate the engineering object.
  • Instantiated objects include spatial objects, temporal objects, managed objects, and computed objects.
  • the engineering library server 500 includes an object definition module 510 and a login verification module 520.
  • the object definition module 510 is for instantiating the modeled object and making an instantiated definition by natural language description.
  • the object definition module 510 instantiates the real-time data model, the historical data model, and the plan data model into real-time data objects, historical data objects, and plan data objects, respectively.
  • the login verification module 520 is used to authenticate the user who retrieves the information.
  • the model library, the engineering library, the real-time database 410, the historical database 420, and the planning database 430 are collectively referred to as a spatio-temporal database.
  • the development process, the model and the object are object semantics
  • the model is used to instantiate the object semantics
  • the abstraction of the object type in the model and the object semantics is a description of the specific object.
  • the running process, real-time database 410, historical database 420, and planning database 430 load semantic information from the engineering library to create operational data objects.
  • the graphics calculation engine 700 is used for graphical data calculation, retrieval, and graphical interactive presentation of the client 800.
  • the graphics calculation engine 700 includes a graphics calculation module 710 and a scene processing module 720.
  • the graph calculation module 710 is configured to perform calculation on the graph data.
  • the scene processing module 720 is configured to perform data processing on the scene display.
  • the scene processing module 720 builds a scene model for all devices in the production plant. The scene model is used to display specific properties and operating states of the production equipment.
  • Client 800 is a means for computing model interactions through data retrieval.
  • the client 800 includes a cache module 810, a login module 820, and a graphics refresh and build module 830.
  • the cache module 810 is configured to perform cache processing on the retrieved data and the displayed data.
  • the login module 820 is used to input login information and retrieval information.
  • the graphics refresh and build module 830 is configured to perform parent graphics refresh processing and/or sub-graphic dynamic construction on the content displayed by the client.
  • the embodiment further provides a retrieval method for a data object retrieval device based on a spatiotemporal database.
  • the management object is modeled for the time state and space state of the object to be managed. That is, a time model, a space model, a management model, and a calculation model are established for the temporal state and the spatial state of the object to be managed within the model library on the model library server 600.
  • Multi-level spatial models include shop floor models, production line models, and equipment models.
  • the first level space model is a shop floor model
  • the second level space model is a production line model
  • the third level space model is a device model.
  • the space objects are workshops, production lines and equipment.
  • the time parameters of the work site are freely defined according to shifts, batches, etc., and the time parameters are stored in "shifts, batches".
  • the time level of the work site is freely defined according to the order, the work order, and the product.
  • the basic attributes of the time include: time name: product number; start time: product online time; end time: product offline time.
  • the object to be managed that is, the object to be managed is set as the device 100.
  • the data collection module 200 performs data collection on the management object 100.
  • the data collection module 200 includes a data collection server IOServer.
  • the data collection module 200 transmits the collected data to the data calculation engine 300.
  • the data calculation engine 300 transmits data model request information to the engineering library 500 server.
  • the engineering library server 500 in response to the request of the data calculation engine 300, imports the real-time data model-Tag (time-second) model required for real-time data to the model library server 600, and generates a tag (time second) according to the real-time data collected by the data calculation engine 300.
  • the model is instantiated as a Tag (time second) object.
  • the Tag (Time Second) object is the first real-time data object.
  • the data calculation engine 300 sends the first real-time data object to the real-time database 410 for storage.
  • the time level of the first real-time data object is a natural attribute level, including year, month, day, hour, minute, and second. That is, the real-time data in the first real-time data object includes time data of each device, for example, an online state, an offline state, a current product, a current parameter, and the like.
  • the data calculation engine 300 can also convert the first real-time data object into a second real-time data object of a different time level by calculation according to the user's custom time level.
  • the calculation engine 300 performs dynamic data processing on the real-time data of the first real-time data object according to a preset version to obtain a second real-time data object.
  • the time hierarchy in the second real-time data object is an order, a work order, a product, and thus the real-time data of the second real-time data object includes production events of the product on the device.
  • the data calculation engine 300 converts the first real-time data object into historical data objects that exceed the fresh period and sends them to the history database 420 for storage. Specifically, when the data collection module 200 detects that the device is online according to the real-time data, the first real-time data object is established. When the data collection module 200 detects that the device is offline according to the real-time data, the event state of the device is saved as a historical data object. The data calculation engine 300 processes the real-time data object calculations as historical data objects, stores them in a historical database, and sets the state of the real-time events to zero.
  • the data collection module 200 also includes a third party database 210 or a data import interface device.
  • the data calculation engine 300 calculates a plan data object of the production device based on the real-time data object and the historical data object. Or the engineering library server 500 instantiates the plan data model as the first plan data object based on the plan data imported by the third party.
  • the data calculation engine 300 performs dynamic data processing on the first plan data object according to a preset version to obtain a second plan data object describing the production event.
  • the data calculation engine 300 sends the second plan data object to the plan database 430 for storage.
  • Real-time data objects are stored in a real-time database
  • historical data objects are stored in a historical database
  • planned data objects are stored in a planning database.
  • This embodiment describes the foregoing embodiment as a specific example.
  • the user needs to implement information monitoring of the first boiler of the plant. Then the first boiler is the object to be managed. First, it is necessary to establish a relevant data model of the first boiler and establish a matching time and space model to locate or monitor the relevant data information of the boiler.
  • the relevant data information is associated with the time model and the spatial model to establish a management model.
  • the time model and the spatial model are instantiated separately, and the management model is instantiated as a management object.
  • the management object needs to select a certain spatial object of the spatial model associated with the management model, and also select a certain time object of the time model associated with the management model for association.
  • the space associated with the first boiler real-time data model is the boiler space model, and the associated time is the time model of the shift.
  • the first boiler space model will instantiate three space objects: boiler 1, boiler 2, and boiler 3.
  • Boiler 1, Boiler 2, and Boiler 3 are spatial object names that are customized by natural language.
  • the class time model will instantiate three time objects: morning shift, middle shift, and night shift. Early, middle, and evening classes are time object names that are customized with natural language.
  • the boiler real-time data model instantiates the boiler real-time data object 1.
  • Boiler real-time data object 1 The joint space object is the boiler 1, and the associated time object is the morning shift, the middle shift, and the evening shift, that is, the time model defaults to the shift model. Because boiler 1 is a real-time data object, only real-time database space can be selected when the computer is stored in configuration. Similarly, the modeling and association process of the historical database and the planning database is realized.
  • the establishment of the time model in the modeling process is the definition of the time period in which each class is completed. For example, the morning shift time is set from 6 am to 3 pm.
  • the establishment of spatial models such as the establishment of plant models and boiler models, is a description of the spatial shape, spatial extent and spatial location of the plant model and boiler model.
  • the plant model is defined as the parent model of the boiler model.
  • the storage location of real-time data objects, historical data objects, and scheduled data objects is determined by the model type: real-time database, historical database, and planning database.
  • the model type real-time database, historical database, and planning database.
  • the management model category type determine which library in the spatio-temporal database to look up data.
  • the real-time data object stores the collected values in the real-time database.
  • the information including the time information for the morning shift on October 21, 2016 is recorded.
  • the morning shift information includes spatial information, spatial extent, and spatial location information of the boiler model corresponding to the boiler 1, including the model type information of the boiler corresponding to the management model, and other attribute information of the boiler. For example, state information such as the color, temperature, and pressure in the chamber of the boiler 1.
  • the user can retrieve the state of a certain boiler at a certain time based on time information, spatial information and model category information.
  • the user selects a real-time data model.
  • the system determines the real-time database based on the real-time data model of the managed object. After determining the database, at least one version of the boiler real-time data object associated with the management object in the real-time database is selected based on the time entered by the user and/or the boiler name. After determining the version of the boiler real-time data object, one or more of the space object boiler 1, the boiler 2, and the boiler 3 after the boiler model is instantiated are selected. Open the data of boiler 1 to view the real-time data of boiler 1 to understand the real-time operating status of boiler 1.
  • the method of viewing the historical operating state and planned operating state of the boiler 1 is the same as the method of viewing the real-time operating state of the boiler 1.
  • the method of viewing other boiler states is the same as the method of viewing the operating state of the boiler 1.
  • This embodiment provides a method for describing objects and events existing in an objective world based on a four-dimensional space.
  • the specific description method refers to the foregoing embodiment.
  • the production orders of one workshop are decomposed into several production line work orders, and each production line work order is re-implemented to the products produced by the production line equipment, and the space and time are modeled.
  • the custom space model includes the shop floor model, the production line model, the device model, and the Tag model.
  • the custom time model includes an order model, a work order model, and a product model.
  • the time model that comes with the system includes year, month, day, hour, minute, second, and millisecond.
  • each order, work order, and product has a unique name. That is, the order number is unique, the work order number of an order is also unique, and the product under a certain work order is also unique.
  • an order is arranged to be produced on the shop floor and is broken down into a number of work orders, each work order being equivalent to one production lot and one batch producing a number of products.
  • the order plan is broken down into different plan data models according to the space-time granularity in Table 1 below.
  • the user can customize the members of each of the planning data models.
  • the planning data is manually entered into the system by import or by the user. After the plan data is imported or entered, the system decomposes the plan data step by step and finally decomposes it into the device product.
  • Table 1 below lists the time granularity and spatial granularity corresponding to each data model.
  • the time granularity and spatial granularity corresponding to the real-time data model 1 to the real-time data model 4, the historical data model 1 and the historical data model 2, and the planned data model 1 to the planned data model 3 are as shown in Table 1.
  • the plan data model 3 time granularity is the order, the spatial granularity is the workshop
  • the plan decomposition calculation model 1 is processed by the plan decomposition calculation model 1 to obtain the data object corresponding to the plan data model 2 (time granularity is work order, spatial granularity is production line).
  • the plan data model 2 is processed by the plan decomposition calculation model 2 to obtain a data object corresponding to the plan data model 1 (time granularity is product, space granularity is device).
  • the data of the object to be managed is collected into the spatiotemporal database by the data collection server IOServer.
  • the data exists in the form of Tag variables.
  • the Tag variable is converted into a Tag object recognizable by the spatiotemporal database.
  • a data object corresponding to the real-time data model 1 time granularity is seconds, spatial granularity is Tag
  • Each object of the Tag object has an online status, an offline status, a current product, and current parameters. The status and parameters of each device are collected into the spatio-temporal database through the Tag object.
  • the real-time event calculation model calculates the production events of the product on the device in real time, so that the real-time data model 2 is dynamically generated (time granularity is product, spatial granularity).
  • each product has information on the work order. If the product of one work order is only partially off-line in a production line, the real-time situation of the work order of the production line is recorded. If the work order product is all offline, it means that the work order of a production line completes the production history data. The analogy can be used to calculate the real-time completion of the shop order. If the user needs it, he can continue to calculate the historical completion.
  • the event storage calculation model 1 generates historical data of a product on the device based on the plan data input by the plan data model 1 and calculates the state of the product through the Tag state change, so that the historical data model 1 is dynamically generated (
  • the time granularity is the data object corresponding to the product and the spatial granularity is the device.
  • the real-time statistical calculation model 1 generates the real-time data of the work order on the production line based on the plan data input by the plan data model 2 and calculates the real-time data of the work order on the production line.
  • the time granularity is the work order and the spatial granularity is Production line) corresponding data object.
  • the event storage calculation model 2 If the work order is offline on the production line, the event storage calculation model 2 generates historical data of a work order on the production line by calculating the state change of the work order, so that the historical data model 2 is dynamically generated (time granularity is work order, spatial granularity is production line) ) the corresponding data object.
  • the real-time statistical calculation model 2 generates real-time data of an order on the shop floor by calculating the state change of the work order, so that the data object corresponding to the real-time data model 4 (time granularity is order, space granularity is workshop) is dynamically generated.
  • This embodiment provides a method of describing a transaction time attribute and performing a lookup based on the description.
  • the method is specifically described with reference to the foregoing embodiments.
  • the method models the object to be managed to establish a historical database, a real-time database, and a plan database that store at least the time attribute of the object to be managed and the space attribute of the object to be managed.
  • the historical running state, the real-time running state, and/or the planned running state of the object to be managed are searched based on the time attribute of the object to be managed.
  • the following is a specific example of how to describe the time attribute.
  • the heating season, fiscal year, season, etc. commonly used in daily life, the corresponding standard time is often the new year and / or cross-month, if the standard is used Quasi-time is not conducive to the search for information.
  • the factory uses natural language such as morning shift, middle shift, and evening shift to describe October 21, 2016. Among them, the early shift corresponds to October 21, 2016, 08:00 to 16:00. The morning shift corresponds to October 21, 2016, from 16:00 to 24:00. The evening shift corresponds to October 21, 2016, from 0:00 to 08:00. If the description is made at the industrial site using the time from 08:00 to 16:00 on October 21, 2016, it is not only cumbersome, but also does not conform to the idioms produced by the factory.
  • the invention provides a method for describing the time attribute of a thing and searching according to the description, and directly describes the time attribute of the object to be managed as a natural language conforming to daily life habits or industrial production processes, such as heating season, fiscal year, season, etc.
  • Using this kind of query method is the most familiar way for users. It does not need time conversion, and it is natural and convenient to use, which can improve the search efficiency.
  • This embodiment provides a method of describing a transaction space attribute and performing a lookup based on the description.
  • the method for describing the space attribute of the object is to implement spatial information annotation according to the spatial state of the object to be managed, specifically: loading the geographic information coordinate system by the spatial object editor, and based on the geographical location information and space of the thing to be described
  • the state information establishes multi-level spatial objects through rectangles, irregular polygons, points and polylines, and realizes spatial information annotation of each component of the multi-level structure to be described based on multi-level spatial objects; and realizes the things according to the spatial object information of the things to be described Find.
  • a spatial object is a description of a spatial property of a managed object, and the spatial object includes a description of the spatial shape, spatial extent, and spatial location of the object to be managed. That is, a description of the shape, size, and position of the object to be managed is implemented.
  • the spatial shape is the physical shape of the object to be managed, and the physical shape of the object to be managed realizes the description of the spatial shape through geometric points, lines, and faces.
  • the spatial extent is the envelope of the object to be managed, and the envelope of the object to be managed is represented by a rectangle or a cube; and the origin, length, width, and height of the spatial range are calculated by the spatial shape of the object to be managed.
  • the spatial location is information describing the location of the object to be managed in space, and the location information includes precise location information and logical location information.
  • the precise position is at least the geographic coordinate position of the object to be managed, and the logical position is the position information and/or relationship of each constituent element in the object to be managed, and includes the positional relationship between the spatial objects of the same level and the positional relationship of the spatial objects of different levels.
  • the logical location information and/or relationship of the object to be managed includes the logical location definition information storage logical location relationship information of the object to be managed, and the logical location of the object to be managed is defined as a mark of the object to be managed by the natural language, and the natural language of the object to be managed
  • the mark may be information that marks the object to be managed as the first group company, the first branch, the first workshop, the first assembly line, the first station, and the like.
  • the logical location relationship information of the object to be managed includes the affiliation and/or hierarchical relationship of the location. For example, the spatial state of the object to be managed is matched with the spatial object of the group company, and the spatial information of the production line and the mechanical equipment in the factory, the factory floor, and the workshop are marked.
  • the objects to be managed include static objects and dynamic objects, and the static objects include the exact position of the object to be managed is static and/or the logical position is static.
  • the dynamic object includes the exact location of the object to be managed being dynamic and/or logically dynamic.
  • a dynamic object can be a component on a device or device.
  • the exact location of a component on a device or device can be location information such as longitude, latitude, and altitude on the map.
  • the logical location of a component on a device or device may be that the component on the device or device is moved to or is in a production line, a certain plant, or a factory.
  • the method for searching based on the description of the transaction space attribute is specifically: searching based on the spatial object information of the multi-level and/or multi-level object to be managed. That is, the retrieval of things is achieved based on the description of the spatial shape, spatial extent, and spatial location of the multi-level and/or multi-level transactions. For example, retrieval of things is achieved by describing spatial shape information of points, lines, and faces of the geometry of the thing. The object or object retrieval is performed by the envelope information of the origin, length, width, and height of the rectangle or cube describing the range of the object space. The retrieval of things is achieved by describing the precise location information and/or logical location information in which things are spatially located.
  • the search for the location information of the transaction no longer needs to rely on the longitude, latitude and altitude information, and the query of the location of the transaction can be completed only by its name or other definition information; meanwhile, based on the logical position of the transaction Descriptive information can realize the query of its affiliation, and the invention can realize the record and update of the dynamic precise position and/or the dynamic logical position of the object, thereby realizing the historical position location query and the real-time location query function.
  • the embodiment provides an organization method of object data.
  • the organization of the object data includes a data definition process and a data running process.
  • the data definition includes realizing the definition of the model library data and the engineering library data through the spatial dimension and/or the time dimension. definition.
  • the definition of the data is a process of modeling a spatiotemporal database based on time attributes and spatial attributes of the data.
  • the specific process refers to the foregoing embodiment.
  • the running process of the data includes realizing the data update process of the real-time database, the historical database and the planning data of different data objects in the time dimension.
  • the data update process is based on the first time organization or update of the data based on the spatial characteristics of the data stored in the real-time database, the plan database, and the historical database, and the data stored in the real-time database, the plan database, and the historical database are implemented according to the data.
  • the second organization or update of the time attribute is based on the first time organization or update of the data based on the spatial characteristics of the data stored in the real-time database, the plan database, and the historical database, and the data stored in the real-time database, the plan database, and the historical database are implemented according to the data.
  • the second organization or update of the time attribute is based on the first time organization or update of the data based on the spatial characteristics of the data stored in the real-time database, the plan database, and the historical database, and the data stored in the real-time database, the plan database, and the historical database are implemented according to the data.
  • the second organization or update of the time attribute is based on the first time organization or update of the data based on the spatial characteristics of the data
  • the organizing method of the object data further comprises realizing retrieval of the member information of the object to be managed based on the type of the member information of the object to be managed.
  • the retrieval includes the member information retrieval of the corresponding type of the corresponding object in the corresponding time and space based on the type of the time information, the spatial information, and the member information.
  • the retrieving comprises: retrieving the member information retrieval of the corresponding type of the at least one object in the corresponding time point or the time period based on the time information and the type of the member information; the retrieving comprises completing the corresponding type of the corresponding object in different time segments in the corresponding space based on the type of the spatial information and the member information;
  • Member information retrieval includes retrieving member information retrievals of respective types of time periods and corresponding types of at least one object within each space based on the type of member information.
  • the specific retrieval method refers to the foregoing embodiment.
  • the type of member information of the object to be managed includes a date type, a binary, a resource, a pen, a brush, and a font. That is, the object to be managed can implement multi-directional description of the object to be managed by including member information of date, binary, resource, pen, brush, and font.
  • the resource type member information includes at least one of 2D graphics, 3D graphics, text, pictures, subset XML under standard common markup language, HTML, report, audio and video information related to the object to be managed.
  • Unconventional data type data in one or more formats. Brushes include solid colors, hatching, textures, lines, and paths. For example, you can achieve different management by different color, different virtual solid lines, different texture types, different line types, and different line paths. The description of the object's information. Similarly, different information descriptions and records of the objects to be managed can be realized by different date data, binary data, resource data, pen data and font data.
  • the boiler As the object to be managed, you need to define the name of the boiler, which can be defined by a string, for example 32 characters; the temperature of the boiler needs to be defined, which can be defined by floating point data; the height of the boiler needs to be defined, Defined by integer data.
  • the data structure is: boiler-name; boiler-temperature; boiler-height. If the boiler has image information (video), color information (color), boiler 2D graphics information, boiler 3D graphics information, it can not be structured with string, integer or floating point data. This produces unconventional data type data.
  • the technical solution introduces the unconventional data type as a member to be managed directly to the object to be managed, so that the object to be managed can also be directly described by data types such as ellipse, video, and color.
  • the data structure is: boiler-ellipse; boiler-video; boiler-color, thereby realizing a structured description of the object to be managed.
  • the time attribute data and the space attribute data are organized, and at the same time, the data information of the unconventional data type is defined as an object member in the form of a measurement point or a data record segment.
  • object members in data records include time attribute data, spatial attribute data, audio data, video data, picture data, enumerations, digital files, and the like.
  • the database does not need to be separately stored and managed by the user, and can be directly displayed on the interactive interface when used.
  • Structured data of unconventional data types Audio, video, and graphics are all members of a model, which is very convenient to use. In the existing software, these unconventional data types are handled separately. Audio and video and graphics are stored on separate servers.
  • Unconventional data type data structuring which supports these types and uses a single measuring point, a member can express unconventional data type data information related to the object.
  • the running of the data includes real-time database, history of different data objects in a time dimension.
  • the data update process is based on the first time that the data stored in the real-time database, the plan database, and the historical database is based on the spatial attributes of the data, and the data stored in the real-time database, the plan database, and the historical database are implemented according to the data.
  • the time attribute is carried out for the second time. That is, the data record of the object to be managed stored in the real-time database, the historical database, and the plan data that has been instantiated is implemented based on the spatial attribute to implement the first update of the data record.
  • the data record updated by the completion space attribute stored in the real-time database, the historical database, and the plan data is updated second based on the time attribute.
  • the first organization or update process of the data is a process of classifying and storing the real-time database, the plan database, and the history database based on the spatial attributes of the object data.
  • the second organization or update of data is the process of classifying and storing the time attributes of the plan data and the historical database based on the object data.
  • Spatio-temporal data The various data stored in the database is a description of the objective things, such as the temperature value, pressure value, and flow value of the site. These values are some specific data.
  • the spatial size, spatial location, and time information are not only defined and expressed in the form of natural language, but also graphically displayed.
  • a polygon's graphic member is used to describe the shape of the space.
  • This polygon graphic member is simply a polygon in the model stage, which does not represent any meaning, but in the stage associated with the specific data object to be described, spatio-temporal data
  • the polygon members on the object show the shape of the actual field device, because each spatial object has shape and geographic coordinates, and this set of coordinate points can determine the position and size of the data object.
  • Application scenarios with graphical members on data objects mainly use graphics to visually reflect spatial data information of data. This is why the object to be managed can support the map display, because each data has spatial information. When the data is queried, as long as the geographic mode is selected to display the data object, the data will be displayed in the form of a map.
  • other graphical members can also be used to reflect the information of other on-site process data members, thus achieving a perfect combination of map and process data.
  • the temperature value is a data member.
  • a text graphic member is defined to display the on-screen temperature information on the screen, and a circular graphic member can be defined.
  • the value can also make the circular graphic members display different colors, so that the information conveyed to the user is more intuitive. If the information received by the human brain is text, the text will first be associated with some common graphics in the industry, and then understood.
  • the use of the data audiovisual member of the present invention is taken as an example.
  • the collected audio and video data of the scene can be directly played on the display device in the form of real-time data members.
  • monitoring and management only collected data and then displayed it with some graphic images. This is like the former sensor information member just let the user have both hands to reproduce the scene information with the image on the screen, but with the audio members and video members, the user in the control room has eyes and ears, which can be seen in real time. A live image and listen to the live sound.
  • Audio and video data will be stored in real time according to the time and space granularity. For example, a temperature alarm occurs on the shift, and the audio and video information of the scene is recorded as a trigger condition when the temperature alarm occurs, and the recording is stopped after the temperature alarm disappears.
  • the empty information (which device is specific) can also be used to schedule the audio and video of the scene during the alarm occurrence process through the audio and video members.
  • the member information is stored on a historical data object. The user does not need to go to each third-party database to retrieve and view it as before, but store the data directly in the spatio-temporal database, a space-time query condition. You can check it out.
  • the use of audio and video of the planned data is generally used as the production guide plan data.
  • the audio and video and binary members are also widely used.
  • the so-called resource types cover audio and video, word, pdf, bmp pictures, etc., in specific planning data.
  • the corresponding resource type is associated or a specific resource file is imported, and the operator of the on-site station can adjust when performing the on-site assembly task. Take the information of different resource members.
  • This resource can be a video, a pdf guide, or an operation guide audio recorded beforehand.
  • Audio and video are also displayed and played through specific graphic members. For example, a live person clicks on a text member. In the graphics calculation logic, an audio play function is triggered to play the corresponding audio member information. There is a video play button, and the click also triggers. A video playback function that plays the corresponding video member information.
  • These members can be freely defined by the user, and the name can be set arbitrarily.
  • This embodiment provides a method for subscribing object data based on a spatiotemporal database.
  • the present invention adopts a database structure including at least a time attribute and a spatial attribute to a data object, so that the object has a data structure including a real-time database, a history database, and a plan database, and the database server of the object data is connected to the client database.
  • the client sends the subscription request to the time-space running database
  • the database server detects whether the behavior is a subscription behavior and determines whether it is the first initialization, if the server detects that it is a subscription behavior and is the first initialization data, then The server will query relevant data according to the time and space range and data category of the subscription and feed back to the client, so that the client receives the change of the object data, status or time in time, so that the user can know the relevant running state of the object in time.
  • the modeling of the spatiotemporal database in the subscription method comprises at least the following steps: the organization process of the data object, the organization process further includes a process of defining and running the data object, wherein the definition process comprises implementing the data in the time dimension and the spatial dimension of the object.
  • the definition of the object, the time dimension of the object includes a data structure of at least three time dimensions, thereby forming a data structure including the object model library and the engineering object library.
  • the real-time data to historical data conversion of the present invention is completed by generating a historical data calculation unit, and the historical data calculation unit is a time-space running database background calculation, and the data calculation can be a calculation of the subscription real-time data change, once the real-time data changes, real-time
  • the database sends the changed data record to the generation history data calculation unit, and the generation history data calculation unit determines whether to generate the data as historical data according to the calculation logic.
  • the background data calculation unit can define a subscribed data channel active object client subscription.
  • the spatial dimension of the object data is a data structure formed by multi-level space modeling of the object according to the spatial state of the object.
  • the subscription method is through an active subscription process of the client.
  • the client's graphical computing channel sends a subscription request containing at least a time attribute and a spatial attribute to the spatio-temporal running database.
  • the database server records the spatio-temporal range data in the subscribing request.
  • model category attributes are fed back into the graphical computing channel of the client.
  • the subscription method also includes that when the graphical calculation of the client is always turned on, the database server records the subscription request of the client, and the subscription request of the client may be the time attribute, the space attribute and the model category attribute of the object, and the server in the spatio-temporal database.
  • the time-space running database actively sends the changed data to the graphic computing channel of the client, and is stored in the channel of the graphic computing by the computing engine of the client, and the client directly calculates the channel from the graphic. Get the data for the subscription.
  • the subscription request is: the time attribute is early shift, the space attribute is boiler 1, and the model category is boiler model, wherein, for example, the time attribute has an early shift start time of 8..00 and an end time of 12..00.
  • the user sends a subscription request containing the above object attribute to the spatio-temporal database at the client, and the time-space running database detects whether the received request is a subscription request, and whether the subscription request is the first initialization data, and if so, the space-time database
  • the relevant object data within the scope of the subscription request that is, the operational status data of the boiler 1 during the morning shift, will be detected in real time in response to the above-mentioned subscription request.
  • the spatio-temporal running database actively pushes the operating state data record including the morning shift of the boiler 1 to the client.
  • the subscription behavior of the present invention may be a subscription to the real-time data of the object, and the server automatically notifies the client as long as the real-time data of the object changes.
  • the subscription behavior of the present invention may be a subscription to object history data and/or plan data as long as the data record of the space and/or time range of the subscribed request of the historical data of the object is modified, the server The modified data record will be sent to the client. And because the historical data and the modification of the plan data will produce a new version, the client will receive the full version of the data. Therefore, when there is a difference between the real-time data of each object and the corresponding data of its historical database and/or plan database, the user can know the running state of the management object in time.
  • the present invention sets the channel of the graphic calculation to the subscription mode by setting a subscription process on the graphic computing model.
  • the database server detects the corresponding time according to the time, space range and model category of the client graphics calculation. Object data, and the data is actively pushed to the client, regardless of how the client operates, unless the scene is closed and then re-initialized, the server will not send data to the client, only the data record of the object in the time and space of the subscription changes. The server will send the changed data record to the client's graphical computing channel.
  • the present invention can also perform data processing calculation on the client's subscription request by establishing a subscription-type data channel model in the time-space running database.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Remote Sensing (AREA)
  • Mathematical Physics (AREA)
  • Software Systems (AREA)
  • Artificial Intelligence (AREA)
  • Computational Linguistics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种基于时空数据库的对数据对象的检索方法，该方法为对待管理对象进行模型化后基于管理对象的管理模型类别以及空间属性和/或时间属性进行检索以确定管理对象的运行状态，步骤如下：针对待管理对象的时间状态和空间状态对管理对象进行模型化；依据待管理对象的管理模型设定待管理对象的凭借自然语言描述的特定属性；基于管理对象的管理模型类别以及由模型化所限定的凭借自然语言描述的空间属性和/或时间属性进行检索以确定管理对象的运行状态。该方法通过历史、实时和计划三段时间来描述生产监控管理的数据信息，用户只需要使用时空元语言便可以通过检索了解管理对象的时空运行状态，既节省计算机内容又便于管理。

Description

一种基于时空数据库的对数据对象的检索方法 技术领域
本发明涉及一种基于时空数据库对工业生产和监控进行管理的方法，尤其涉及一种基于时空数据库的对数据对象的检索方法。
背景技术
目前主要的时空数据库模型主要有：序列快照模型、时空立方体模型、基态修正模型、时空复合模型等，这些模型有着不同的性质和优缺点，但是对于统计行业来说都不能很好地满足需求；还有一些时空数据库模型思想，例如面向对象的时空模型思想，基于特征的时空数据库模型、基于事件的时空数据库模型等，这些模型都是利用面向对象或者差量记录的方式对空间变化情况及其相互关系进行记录，然而其或多或少地不能满足统计时空数据库纷繁复杂指标和统计级别众多的要求，并且在业务适用性方面不能很好地满足统计部门的需要。
中国专利CN103678712A公开了一种灾害信息时空数据库，灾害信息时空数据库包括灾害现势数据库、灾害过程数据库和灾害历史数据库三个灾害信息数据库，统一编码模块对接收的灾害信息数据分层次编码；属性数据管理模块和空间位置数据管理模块导入灾害信息属性数据和空间位置数据到对应的灾害信息数据库；灾害信息数据通过逻辑变更模块在各灾害信息数据库之间传输；时空数据库索引模块按时间序列对灾害信息时空数据库建立更新索引；逻辑变更模块和时空数据库索引模块构成灾害信息时空数据库的基础，对灾害属性的管理维护、时空逻辑索引的变更维护，为统计数据的入库、检索和时空查询做好准备。该专利存在的问题是：(1)该关系数据库不能通过直接输入时间或者空间信息进行检索查询；(2)检索方式单一，只能在某一时间范围进行检索，而不能在某一空间范围进行检索。
目前众多的空间数据库标识空间信息都是采用存储坐标信息来支持空间信息，加上使用一个自增长ID(Identity，序列号)来提供索引，在搜索上需要依靠空间结构算法来实现。为解决上述问题，现在很多专利通过使用更加简单的空间索引技术。
中国专利CN102622349B公开了一种空间位置信息数据库的处理方法，包括：获取一空间位置的坐标数据；根据所述坐标数据生成与所述空间位置对应的空间位置信息编码，包括：定义在中国范围内实施的空间位置信息编码分为五节代码，国家码-区域码：子码1：子码2-附加码，每节代码的编码方法原则为自上而下、自左向右进行编号；在空间位置信息数据库中存储所述空间位置信息编码，将所述空间位置信息编码作为所述空间位置在所述数据库中的索引和位置信息。该专利存在的问题是：(1)对空间描述准确度、精确度不够高，比如对工厂中某一设备上部、底部无法准确、区分描述；(2)空间解析和编码对于数据的查询和调用不方便，需要对应的编码；(3)当物理位置更新改变后，数据库没有动态更新。
在使用关系型数据库存储信息的应用系统中，存在大量的多维度查询，这类查询提供了多种维度的查询条件供使用者输入，同时使用者需要简单、快速、智能地检索到需要的信息。对数据库查询的优化方法主要有以下几种：(1)合理利用索引：对关系数据库中的数据表，按被查询字段创建独立有序的存储结构，提高查询性能；(2)冗余关系数据：在二维表中冗余存储其它相关表中信息，以减少查询时的关联关系，提高查询性能；(3)分离存放海量数据：对于海量数据，按某些数据进行分类独 立存储，提高查询性能。
中国专利CN100483411C公开了一种关系型数据库中信息检索方法，包括步骤：构造维度缩减策略树并置于数据库系统中，所述维度缩减策略树包括至少一个子节点和至少一个根节点，每个子节点至少包含本节点编号标识信息及查询条件组合信息和下级子节点编号；当按用户查询条件检索所述数据库未得到所需数据时，根据维度缩减策略树依次构造新的查询条件；按照新的查询条件检索数据库直到得到所需的数据或查询到维度缩减策略树的根节点返回无所需数据的信息。该专利存在的问题是：查询和调用数据时需要特定的编号标识信息，在工业过程控制领域，设备和过程参数的类型和数量多，使用编号查询数据很不方便。这是传统关系数据库始终存在的问题—每个对象必须通过唯一对应的标识码才能检索到对应的数据。如果有一种方法能直接通过设备的位置或者过程参数所在的时间点进行检索，检索效率会提高很多。
由此可见，目前大家通用的所有数据库结构的建立都必须经过一系列的繁杂定义或赋值。数据的输入或输出必须由程序员用程序语言编写程序。数据库的维护必须由原程序设计者提供源程序码，方可对其软件进行维护或升级。查询或调用数据库数据时必须输入特定的标识。因此，市场上需要更加便捷、高效、低成本的数据库系统，而目前还没有一种能提高现有数据库功能并且是可以组态实现的数据库系统。
发明内容
针对现有技术之不足，本发明的一个方面提供了一种基于时空数据库的对数据对象的检索方法，所述检索方法为对待管理对象进行模型化后基于管理对象的管理模型类别以及空间属性和/或时间属性进行检索以确定所述管理对象的运行状态，并且所述检索方法包括如下步骤：针对待管理对象的时间状态和空间状态对所述管理对象进行模型化；依据待管理对象的管理模型设定所述待管理对象的凭借自然语言描述的特定属性；基于管理对象的所述管理模型类别以及由所述模型化所限定的凭借自然语言描述的空间属性和/或时间属性进行检索以确定所述管理对象的运行状态。
根据一个优选实施方式，对待管理对象进行模型化的方法至少包括如下步骤：依据待管理对象的空间状态对所述待管理对象进行模型化，依据待管理对象的时间状态对所述待管理对象进行模型化，设定所述待管理对象的特定属性，采集所述待管理对象的数据以对所述待管理对象动态监测和管理。
根据一个优选实施方式，所述基于管理对象的所述管理模型类别以及由所述模型化所限定的凭借自然语言描述的空间属性和/或时间属性进行检索以确定所述管理对象的运行状态的步骤包括：基于管理对象的所述管理模型类别、空间位置和/或时间检索在所述空间位置和/或所述时间内的至少一个管理对象的实时数据、历史数据和/或计划数据，从而确定至少一个所述管理对象的实时运行状态、历史运行状态和/或计划运行状态；或者基于管理对象的所述管理模型类别、空间范围和/或时间范围检索在所述空间范围和/或所述时间范围内的至少一个管理对象的实时数据、历史数据和/或计划数据，从而确定至少一个所述管理对象的实时运行状态、历史运行状态和/或计划运行状态。
根据一个优选实施方式，确定所述管理对象的运行状态的步骤还包括：依据管理对象的管理模型类别确定储存管理对象运行数据的实时数据库、历史数据库和/或计划数据库；依据空间属性和/或时间属性选择实时数据库、历史数据库和/或计划数据库中与所述管理对象相关的至少一个版本的所述管理对象运行数据，并且确定与所述管理模型关联的至少一个管理对象并查看所述管理对象的实时数据、历史数据和/或计划数据，从而了解所述管理对象实时运行状态、历史运行状态和/或计划运行状态。
根据一个优选实施方式，所述管理对象包括依据时间属性分类形成的存储于所述实时数据库的实 时数据对象、存储于所述历史数据库的历史数据对象和存储于所述计划数据库的计划数据对象；所述实时数据对象包括经所述实时数据模型实例化过程形成的至少一个由所述管理对象的实时数据构成的管理对象；所述历史数据对象包括经所述历史数据模型实例化过程形成的至少一个由所述管理对象的历史数据构成的管理对象；所述计划数据对象包括经所述计划数据模型实例化过程形成的至少一个由所述管理对象的计划数据构成的管理对象。
根据一个优选实施方式，针对待管理对象的时间状态和空间状态对所述管理对象进行模型化的步骤包括：依据待管理对象的空间状态对所述待管理对象的空间进行模型化以建立空间模型；依据待管理对象的时间状态对所述待管理对象的时间进行模型化以建立时间模型，以及建立由所述待管理对象的所述空间模型和所述时间模型关联形成的所述管理模型。
根据一个优选实施方式，所述依据待管理对象的管理模型设定所述待管理对象的凭借自然语言描述的特定属性的步骤包括：所述管理模型经过实例化过程形成至少一个由所述管理对象的时间对象和空间对象关联构成的管理对象；所述管理对象的时间对象由所述时间模型在实例化过程中形成，所述管理对象的空间对象由所述空间模型在实例化过程中形成。
根据一个优选实施方式，所述依据待管理对象的管理模型设定所述待管理对象的凭借自然语言描述的特定属性的步骤还包括：设定所述管理对象的特定属性，所述特定属性包括凭借自然语言描述的时间属性、空间属性和/或非时空属性；非时空属性包括待管理对象的第一数据类型和第二数据类型的属性，并且第二数据类型的属性至少包括待管理对象的图形属性、音频属性、视频属性和名称属性中的一种或多种。优选地，第一数据类型为常规数据类型，如byte，bool，int8，short，ushort，int32，uint32，int64，uint64，float，double，string，datetime，enum等。第二数据类型为非常规数据类型，如blob，anytime，pen，brush，font，图形，音频，视频，名称，文件等的一种或多种。
根据一个优选实施方式，所述时间属性至少包括时间位置、开始时间和结束时间；所述管理对象为静态对象时，所述空间属性至少包括地理空间范围、地理空间位置和子空间的空间形状、空间范围及空间位置；所述管理对象为动态对象时，所述空间属性至少包括地理空间位置、候选地理空间位置和所述待管理对象的上一级空间模型的空间形状、空间范围及空间位置。
根据一个优选实施方式，所述时间模型和空间模型具有由自然语言定义名称标识的多层级结构；所述时间模型的多层级结构包括至少一个凭借自然语言描述的父级别时间层级和至少一个与所述父级别时间层级对应的子级别时间层级；所述空间模型的多层级结构包括至少一个凭借自然语言描述的父级别空间层级和至少一个与所述父级别空间层级对应的子级别空间层级。
根据一个优选实施方式，描述事物空间属性的方法为依据待管理对象的空间状态实现待管理对象的空间信息标注，具体为：通过空间对象编辑器加载地理信息坐标系，并基于待管理对象所在地理位置信息和空间状态信息通过矩形、不规则多边形、点和折线建立多级空间对象，基于多级空间对象实现多层级结构待管理对象各组成元素的空间信息标注。
根据一个优选实施方式，所述空间信息标注过程为：通过空间对象编辑器加载地理信息坐标系，并基于待管理对象所在地理位置绘制一个root根节点的空间范围，在root根节点范围内用矩形、不规则多边线、点和折线绘制一个空间对象以得到待管理对象的第一级空间对象；基于上一级空间对象，用矩形、不规则多边线、点和折线逐级实现待管理对象的组成元素的空间绘制过程以得到所述组成元素对应等级空间对象；将待管理对象的空间状态与空间对象中各级空间对象相对应匹配，从而实现对多级和/或多层次待管理对象的空间信息标注。
根据一个优选实施方式，所述空间形状是待管理对象物理形状，所述待管理对象物理形状通过几何的点、线、面实现所述空间形状的描述；所述空间范围是待管理对象包络，所述待管理对象包络通 过矩形或立方体来表示；并通过所述待管理对象的空间形状计算出空间范围的长、宽、高；所述空间位置是描述待管理对象在空间上所处的位置信息，所述位置信息包括精确位置信息和逻辑位置信息；所述精确位置至少为待管理对象的地理坐标位置，所述逻辑位置为待管理对象中各组成元素的位置信息和/或关系，其中，包括同级空间对象之间位置关系与不同级空间对象的位置关系。
根据一个优选实施方式，通过如下方法采集所述待管理对象的数据：通过从所述待管理对象现场直接采集所述待管理对象的历史数据或者通过计算采集所述待管理对象的历史数据；通过传感器采集所述待管理对象的实时数据或者通过计算采集所述待管理对象的实时数据；通过从第三方系统接口导入计划需求并通过计算生成计划数据。
根据一个优选实施方式，在对数据对象检索之前，所述检索方法还包括基于四维空间的对客观世界存在的物体和事件进行描述的方法，并且所述描述方法为对待管理对象模型化以建立至少存储有所述待管理对象的时间属性和所述待管理对象的空间属性的历史数据库、实时数据库和计划数据库。
根据一个优选实施方式，基于四维空间的对客观世界存在的物体和事件进行描述并建立历史数据库、实时数据库和计划数据库之后，所述检索方法通过所述待管理对象的管理模型类别、凭借自然语言描述的空间属性和/或时间属性查找所述待管理对象的历史运行状态、计划运行状态和/或实时运行状态。
根据一个优选实施方式，基于四维空间的对客观世界存在的物体和事件进行描述并建立历史数据库、实时数据库和计划数据库之后，所述检索方法通过所述待管理对象执行订阅以查找所述待管理对象的历史运行状态、计划运行状态和/或实时运行状态，其中，所述订阅方法至少包括如下步骤：客户端向时空数据库针对至少一个数据记录发出包含管理模型类别、凭借自然语言描述的空间属性和/或时间属性的订阅请求；所述时空数据库响应于所述订阅请求，将包含待管理对象的凭借自然语言描述的空间属性和/或时间属性的至少一个数据记录主动推送至客户端。
本发明的检索方法在对象的查询之前需要确定一种描述方法，优选地，本发明使用基于四维空间的对客观世界存在的物体和事件进行描述的方法对待管理对象进行描述。待管理对象的检索分为按时空模型的单次查询和按时空模型执行订阅。两种查询方式的区别在于：按时空模型的单次查询成功后，服务器只会发送一次查询结果，而按时空模型执行订阅后，服务器在发现该时空范围内数据变化后会再次发送查询结果。
根据一个优选实施方式，查询和订阅是通过所述待管理对象的管理模型类别，凭借自然语言描述的空间属性和时间属性进行的。由于一个实时数据库里可能有多种实时模型的待管理对象，这些模型的结构是不同的，使用待管理对象的管理模型类、凭借自然语言描述的空间属性和时间属性进行查询或订阅，可提高查询或订阅的速度以及准确性。同样的，对历史数据库和计划数据库也优选采用待管理对象的管理模型类、凭借自然语言描述的空间属性和时间属性进行查询或订阅。
本发明的另一方面还提供了一种基于时空数据库的对数据对象的检索装置，所述检索装置至少包括数据采集模块、至少一个数据计算引擎、时空运行数据库、工程库服务器、模型库服务器和客户端；所述数据采集模块，用于采集所述管理对象的运行数据并通过所述数据计算引擎将所述运行数据发送所述工程库服务器；所述模型库服务器，模型库设置于其上，所述模型库被配置用于针对待管理对象的时间状态和空间状态对所述管理对象进行模型化；所述工程库服务器，工程库设置于其上，所述工程库被配置用于依据待管理对象的管理模型设定所述待管理对象的凭借自然语言描述的特定属性；所述数据计算引擎用于依据凭借自然语言描述的时间层级和空间层级对模型化的所述管理对象进行空间和时间的转换；所述时空运行数据库，时空运行数据库包括历史数据库、实时数据库和计划数据库，所述历史数据库、实时数据库和计划数据库被配置用于储存所述管理对象的历史数据、实时数据和计 划数据；客户端用于基于管理对象的所述管理模型类别以及由所述模型化所限定的凭借自然语言描述的空间属性和/或时间属性进行检索以确定所述管理对象的运行状态。
本发明的又一方面还提供了一种基于四维空间的对客观世界存在的物体和事件的描述方法，所述方法为对待管理对象模型化以建立至少存储有所述待管理对象的时间属性和所述待管理对象的空间属性的历史数据库、实时数据库和计划数据库，其中，对待管理对象模型化的方法至少包括如下步骤：依据待管理对象的空间状态对所述待管理对象进行模型化，依据待管理对象的时间状态对所述待管理对象进行模型化，设定所述待管理对象的特定属性，采集所述待管理对象的数据以对所述待管理对象动态监测和管理。
根据一个优选实施方式，对待管理对象模型化的方法至少包括如下步骤：依据空间属性和/或时间属性将待管理对象归类至历史数据模型、实时数据模型和/或计划数据模型，依据待管理对象的空间状态对所述待管理对象进行模型化，依据待管理对象的时间状态对所述待管理对象进行模型化，设定所述待管理对象的特定属性，采集所述待管理对象的数据以对所述待管理对象动态监测和管理。
根据一个优选实施方式，所述依据待管理对象的空间状态对所述待管理对象进行模型化至少包括如下步骤：依据待管理对象的空间状态对所述待管理对象的空间进行模型化以建立空间模型，对所述待管理对象的空间模型进行实例化以建立空间对象；所述依据待管理对象的时间状态对所述待管理对象进行模型化包括如下步骤：依据待管理对象的时间状态对所述待管理对象的时间进行模型化以建立时间模型，对所述待管理对象的时间模型进行实例化以建立时间对象。
根据一个优选实施方式，所述依据待管理对象的空间状态对所述待管理对象的空间进行模型化以建立空间模型的方法为依据待管理对象的空间状态确定多层级空间模型；所述依据待管理对象的时间状态对所述待管理对象的时间进行模型化以建立时间模型的方法为依据待管理对象的时间状态确定多层级时间模型。
根据一个优选实施方式，将所述待管理对象的空间模型和待管理对象的时间模型进行关联以建立历史数据模型、实时数据模型和计划数据模型。
根据一个优选实施方式，将所述历史数据模型实例化为历史数据对象，并且所述历史数据对象关联由所述历史数据模型关联的空间模型实例化产生的空间对象和由所述历史数据模型关联的时间模型实例化产生的时间对象；将所述实时数据模型实例化为实时数据对象，并且所述实时数据对象关联由所述实时数据模型关联的空间模型实例化产生的空间对象和由所述实时数据模型关联的时间模型实例化产生的时间对象；将所述计划数据模型实例化为计划数据对象，并且所述计划数据对象关联由所述计划数据模型关联的空间模型实例化产生的空间对象和由所述计划数据模型关联的时间模型实例化产生的时间对象。
根据一个优选实施方式，将所述历史数据对象配置计算机空间属性后成为历史数据库，将实时数据对象配置计算机空间属性后成为实时数据库，将计划数据对象配置计算机空间属性后成为计划数据库，并且所述历史数据库用于存储所述待管理对象的历史数据，所述实时数据库用于存储所述待管理对象的实时数据，所述计划数据库用于存储所述待管理对象的计划数据。
根据一个优选实施方式，所述待管理对象的特定属性至少包括所述待管理对象的时间属性和所述待管理对象的空间属性，并且所述时间属性至少包括时间位置、开始时间和结束时间，所述待管理对象为静态对象时，所述空间属性至少包括地理空间范围、地理空间位置和形状尺寸轮廓，所述待管理对象为动态对象时，所述空间属性至少包括地理空间位置、候选地理空间位置和所述待管理对象的空间范围的形状尺寸轮廓。
根据一个优选实施方式，所述待管理对象的特定属性还包括所述待管理对象的第一数据类型和第 二数据类型的属性。第二数据类型的属性至少包括待管理对象的图形属性、音频属性、视频属性和名称属性中的一种或多种。根据一个优选实施方式，通过如下方法采集所述待管理对象的数据：通过从所述待管理对象现场直接采集所述待管理对象的历史数据或者通过计算采集所述待管理对象的历史数据，通过传感器采集所述待管理对象的实时数据或者通过计算采集所述待管理对象的实时数据，通过从第三方系统接口导入计划需求并通过计算生成计划数据。
本发明的又一方面还提供了一种描述事物时间属性并基于所述描述进行查找的方法，所述方法为对待管理对象模型化以建立至少存储有所述待管理对象的时间属性和所述待管理对象的空间属性的历史数据库、实时数据库和计划数据库，并且通过所述待管理对象的管理模型类别、空间属性和/或时间属性查找所述待管理对象的历史运行状态、计划运行状态和/或实时运行状态，其中，对待管理对象模型化的方法至少包括如下步骤：依据待管理对象的空间状态对所述待管理对象进行模型化，依据待管理对象的时间状态对所述待管理对象进行模型化，设定所述待管理对象的特定属性，采集所述待管理对象的数据以对所述待管理对象动态监测和管理。
根据一个优选实施方式，所述待管理对象的空间属性和/或时间属性是自定义的多层级结构，并且所述时间属性是通过基于符合生产工业过程和/或日常生活规范的自然语言来描述的。
根据一个优选实施方式，所述时间属性至少包括时间位置、开始时间和结束时间，所述待管理对象为静态对象时，所述空间属性至少包括地理空间范围、地理空间位置和形状尺寸轮廓，所述待管理对象为动态对象时，所述空间属性至少包括地理空间位置、候选地理空间位置和所述待管理对象的空间范围的形状尺寸轮廓。
根据一个优选实施方式，通过所述待管理对象的空间属性确定查找范围后再基于所述待管理对象的时间属性查找所述待管理对象的历史运行状态、实时运行状态和/或计划运行状态。
根据一个优选实施方式，所述对待管理对象模型化的方法为：依据空间属性和/或时间属性将待管理对象归类至历史数据模型、实时数据模型和/或计划数据模型，依据待管理对象的空间状态对所述待管理对象进行模型化，依据待管理对象的时间状态对所述待管理对象进行模型化，设定待管理对象的特定属性，采集待管理对象的数据以对所述待管理对象动态监测和管理。
根据一个优选实施方式，所述依据待管理对象的空间状态对所述待管理对象进行模型化至少包括如下步骤：依据待管理对象的空间状态对所述待管理对象的空间进行模型化以建立空间模型，对所述待管理对象的空间模型进行实例化以建立空间对象；所述依据待管理对象的时间状态对所述待管理对象进行模型化包括如下步骤：依据待管理对象的时间状态对所述待管理对象的时间进行模型化以建立时间模型，对所述待管理对象的时间模型进行实例化以建立时间对象。
根据一个优选实施方式，将所述待管理对象的空间模型和所述待管理对象的时间模型进行关联以建立历史数据模型、实时数据模型和计划数据模型，并且将所述历史数据模型实例化为历史数据对象，将所述历史数据对象配置计算机空间属性后成为存储所述待管理对象历史数据的历史数据库；将所述实时数据模型实例化为实时数据对象，将所述实时数据对象配置计算机空间属性后成为存储所述待管理对象实时数据的实时数据库；将所述计划数据模型实例化为计划数据对象，将所述计划数据对象配置计算机空间属性后成为存储所述待管理对象计划数据的计划数据库。
根据一个优选实施方式，所述待管理对象的特定属性至少包括所述待管理对象的时间属性和所述待管理对象的空间属性，以及所述待管理对象的第一数据类型和第二数据类型的属性，并且所述第二数据类型的属性至少包括待管理对象的图形属性、音频属性、视频属性和名称属性中的一种或多种。
根据一个优选实施方式，通过如下方法采集所述待管理对象的数据：通过从所述待管理对象现场直接采集所述待管理对象的历史数据或者通过计算采集所述待管理对象的历史数据，通过传感器采集 所述待管理对象的实时数据或者通过计算采集所述待管理对象的实时数据，通过从第三方系统接口导入计划需求并通过计算生成计划数据。
本发明的又一方面还提供了一种描述事物空间属性并基于所述描述进行查找的方法，所述描述事物空间属性的方法为依据待管理对象的空间状态实现待管理对象的空间信息标注，具体为：通过空间对象编辑器加载地理信息坐标系，并基于待管理对象所在地理位置信息和空间状态信息通过矩形、不规则多边形、点和折线建立多级空间对象，基于多级空间对象实现多层级结构待管理对象各组成元素的空间信息标注；并依据待管理对象的空间对象信息实现事物的查找。
根据一个优选的实施方式，所述空间信息标注过程为：通过空间对象编辑器加载地理信息坐标系，并基于待管理对象所在地理位置绘制一个root根节点的空间范围，在root根节点范围内用矩形、不规则多边线、点和折线绘制一个空间对象以得到待管理对象的第一级空间对象；基于上一级空间对象，用矩形、不规则多边线、点和折线逐级实现待管理对象的组成元素的空间绘制过程以得到所述组成元素对应等级空间对象；将待管理对象的空间状态与空间对象中各级空间对象相对应匹配，从而实现对多级和/或多层次待管理对象的空间信息标注。
根据一个优选的实施方式，所述待管理对象的空间属性是基于生产工业过程自定的多层级结构；上一级空间对象为次级空间对象的父对象，次级空间对象为上一级空间对象的子对象；所述子对象具有一个父对象，所述父对象包括至少一个子对象。
根据一个优选的实施方式，所述空间对象是对待管理对象的空间属性的描述，空间对象包括待管理对象的空间形状、空间范围和空间位置的描述。
根据一个优选的实施方式，所述基于事物空间属性的描述进行查找的方法具体为：基于包含空间形状、空间范围和空间位置的所述多级和/或多层次待管理对象的空间对象信息进行检索。
根据一个优选的实施方式，所述空间形状是待管理对象物理形状，所述待管理对象物理形状通过几何的点、线、面实现所述空间形状的描述。
根据一个优选的实施方式，所述空间范围是待管理对象包络，所述待管理对象包络通过矩形或立方体来表示；并通过所述待管理对象的空间形状计算出空间范围的长、宽、高。
根据一个优选的实施方式，所述空间位置是描述待管理对象在空间上所处的位置信息，所述位置信息包括精确位置信息和逻辑位置信息；所述精确位置至少为待管理对象的地理坐标位置，所述逻辑位置为待管理对象中各组成元素的位置信息和/或关系，其中，包括同级空间模型之间位置关系与不同级空间模型的位置关系。
根据一个优选的实施方式，所述待管理对象包括静态对象和动态对象，所述静态对象包括待管理对象的精确位置处于静态和/或逻辑位置处于静态；所述动态对象包括待管理对象的精确位置处于动态和/或逻辑位置处于动态；所述待管理对象的逻辑位置信息包括所述待管理对象的逻辑位置定义信息以及逻辑位置关系信息，所述待管理对象的逻辑位置定义为通过自然语言实现对待管理对象的标记；所述待管理对象的逻辑位置关系信息包括位置的隶属关系和/或层次关系。
本发明的又一方面还提供了一种对象数据的组织方法，所述对象数据的组织方法包括对象数据的定义过程与对象数据的运行过程，依据对象的自然属性将待管理对象分类至相应类别，以将与相关类别相应预定义的类别属性分配给与所述待管理对象对应的、至少预先包括时间属性和空间属性的数据记录；依据包含待管理对象的时间属性与空间属性的数据记录，实现对所述数据记录与待管理对象自然属性关联并完成实例化；将完成实例化的存储于实时数据库、历史数据库和计划数据中的待管理对象的数据记录基于包括数据的空间形状、空间轮廓和空间位置描述的空间属性实现数据记录的第一次更新；将存储于所述实时数据库、所述历史数据库和所述计划数据库中的完成空间属性更新后的数 据记录基于包括时间位置、开始时间、结束时间和/或消逝时间的时间属性实现第二次更新；将与待管理对象相关的非常规数据类型数据以一个测点的形式定义为所述待管理对象的成员信息，并将包含所述非常规数据类型数据的成员信息基于空间属性和/或时间属性储存至对应的数据记录所在数据库。
根据一个优选的实施方式，所述对象数据的组织方法还包括基于所述待管理对象的管理模型类别实现待管理对象的成员信息的检索。
根据一个优选的实施方式，所述检索包括基于时间信息、空间信息和管理模型类别完成相应时空内对应对象的对应类型的成员信息检索；所述检索包括基于时间信息、成员信息的类型完成相应时间点或时间段内至少一个对象对应类型的成员信息检索；所述检索包括基于空间信息、成员信息的类型完成相应空间内不同时间段对应对象的对应类型的成员信息检索；所述检索包括基于成员信息的类型完成各个时间段和各个空间内至少一个对象的对应类型的成员信息检索。
根据一个优选的实施方式，所述成员信息的类型至少包括第一数据类型和第二数据类型。优选地，第一数据类型为常规数据类型，如byte，bool，int8，short，ushort，int32，uint32，int64，uint64，float，double，string，datetime，enum等。第二数据类型为非常规数据类型，如blob，anytime，pen，brush，font，图形，音频，视频，名称，文件等的一种或多种。更优选地，非常规数据类型还可以是日期类型、二进制、资源、笔、画刷和字体。即是，待管理对象可以通过包括日期、二进制、资源、笔、画刷和字体的成员信息实现待管理对象的多方位的描述。
根据一个优选的实施方式，所述资源类型成员信息至少包括与待管理对象相关的2D图形、3D图形、文本、图片、标准通用标记语言下的子集XML、HTML、报表、音频和视频信息中的一种或多种格式的非常规数据类型数据；所述资源类型成员信息通过设备导入和/或底层传感单元采集获得。
根据一个优选的实施方式，画刷包括纯色、影线、纹理、线性和路径。
根据一个优选的实施方式，所述数据记录的第一次更新为所述实时数据库、所述计划数据库与所述历史数据库基于对象数据包括数据的空间形状、空间轮廓和空间位置的描述的空间属性进行分类并储存的过程。
根据一个优选的实施方式，所述数据记录的第二次更新为所述计划数据库和历史数据库基于对象数据的时间属性进行分类并储存的过程，其中所述时间属性包括所述对象数据对应的时间位置、开始时间和结束时间的描述；所述数据记录的第二次更新还包括所述实时数据库基于对象数据的时间属性进行分类并储存的过程，其中所述时间属性包括所述对象数据对应的时间位置、开始时间和消逝时间的描述。
根据一个优选的实施方式，基于数据的空间属性描述和/或时间属性描述实现对数据或待管理对象的状态信息检索。
根据一个优选的实施方式，基于数据的空间属性描述实现对所述空间属性描述对应的数据中包括的事和/或物实现特定空间不同时间段的状态信息检索；基于数据的时间属性描述实现对所述时间属性描述对应的数据中包括的事和/或物实现特定时间不同空间的状态信息检索；基于数据的时间属性描述和空间属性描述实现对所述时间属性描述和空间属性描述对应的数据中包括的事和/或物实现特定时间和特定空间的状态信息检索。
根据一个优选的实施方式，所述空间形状是对象数据或待管理对象对应的物理形状，所述对象数据对应的物理形状通过几何的点、线、面实现所述空间形状的描述；所述空间轮廓是所述对象数据或待管理对象对应的包络，所述对象数据对应的包络通过矩形或立方体来表示；并通过所述对象数据对应的空间形状计算出空间轮廓的原点、长、宽、高；所述空间位置是描述所述对象数据或待管理对 象对应的空间上所处的位置信息，所述位置信息包括精确位置信息和逻辑位置信息；所述精确位置至少为所述对象数据或待管理对象对应的地理坐标位置，所述逻辑位置为所述对象数据中各组成元素的位置信息和/或关系，其中，包括同级空间模型之间位置关系与不同级空间模型的位置关系。
根据一个优选的实施方式，所述对象数据或待管理对象包括对应的静态对象和对应的动态对象，所述静态对象包括所述对象数据或待管理对象的精确位置处于静态和/或逻辑位置处于静态；所述动态对象包括所述对象数据或待管理对象的精确位置处于动态和/或逻辑位置处于动态；所述对象数据或待管理对象对应的逻辑位置信息包括所述对应的逻辑位置定义信息以及逻辑位置关系信息；所述对象数据对应的逻辑位置关系信息包括位置的隶属关系和/或层次关系。
本发明的又一方面还提供了一种基于时空数据库的对象数据的订阅方法，该方法包括如下步骤：客户端向时空数据库针对至少一个数据记录发出包含管理模型类别、凭借自然语言描述的空间属性和/或时间属性的订阅请求；所述时空数据库响应于所述订阅请求，将包含待管理对象的凭借自然语言描述的空间属性和/或时间属性的至少一个数据记录主动推送至客户端。
根据一个优选实施方式，所述订阅请求是按照与待管理对象的模型类别相关的方式发送的，所述待管理对象的模型类别是分别建立在实时数据库、历史数据库和/或计划数据库的待管理对象的属性，并且每个类别的数据模型包含一个或多个对象。
根据本发明的一种优选实施方式，所述订阅方法还包括：在所述客户端处于开启状态时，所述时空数据库记录所述客户端的订阅请求，所述时空数据库检测到所述客户端订阅请求的数据记录发生变化时，所述时空运行数据库主动将包含所述待管理对象空间属性和/或时间属性和/或模型类别的至少一个数据记录主动发送至所述客户端；以及在所述客户端处于关闭状态时，所述客户端向所述时空运行数据库发送取消订阅请求。
根据本发明的一种优选实施方式，所述时空数据库的模型化包括如下步骤：依据待管理对象的空间状态对所述待管理对象进行模型化；依据待管理对象的时间状态对所述待管理对象进行模型化；设定待管理对象的特定属性；依据特定属性将模型化的待管理对象归类至特定的模型类别的模型中。
根据本发明的一种优选实施方式，所述时空数据库包括待管理对象的实时数据库、历史数据库和计划数据库。
根据本发明的一种优选实施方式，所述依据待管理对象的空间状态对所述待管理对象进行模型化包括依据待管理对象的空间状态对所述待管理对象的空间进行模型化以建立空间模型。所述依据待管理对象的时间状态对所述待管理对象进行模型化包括依据待管理对象的时间状态对所述待管理对象的时间进行模型化以建立时间模型。
根据本发明的一种优选实施方式，所述设定所述待管理对象的特定属性包括设定待管理对象的第一数据类型和第二数据类型的属性。所述第二数据类型的属性至少包括待管理对象的图形属性、音频属性、视频属性和名称属性中的一种或多种。
根据本发明的一种优选实施方式，所述凭借自然语言描述的时间属性是所述待管理对象依据其时间状态自定义的属性，所述待管理对象凭借自然语言描述的时间属性至少包括依据所述待管理对象的时间位置、开始时间和结束时间自定义的时间属性。
根据本发明的一种优选实施方式，凭借自然语言描述的空间属性包括依据所述待管理对象的空间形状、空间范围和空间位置自定义的空间属性。
本发明至少具有如下有益的技术效果：
(1)本发明通过历史、实时和计划三段时间维度来描述生产监控管理的数据信息，用户不需要 掌握计算机语言，只需要很自然的时空元语言就可以查看和管理对象的历史、实时和计划三个时间段的运行状态，
(2)本发明通过一个数据库解决了多种系统应用的问题，可以降低用户的投资和系统的维护成本，在数据查询和检索时，按照空间和/或时间即可检索模型中的对象，方便快捷，利于生产管理。
附图说明
图1是本发明基于时空数据库的对数据对象的检索装置的模块示意图；
图2是本发明的一个优选实施方式的自定义空间模型示意图；
图3是本发明的一个优选实施方式的自定义时间模型示意图；
图4是本发明的一个优选实施方式的系统时间模型示意图；和
图5是本发明的一个优选实施方式的数据模型间的时空转换关系图。
附图标记列表
100：待管理对象      200：数据采集模块     300：数据计算引擎
400：时空运行数据库  410：实时数据库       420：历史数据库
430：计划数据库      500：工程库服务器     510：对象定义模块
520：验证模块        600：模型库服务器     700：图形计算引擎
710：图形计算模块    720：场景处理模块     800：客户端
810：缓存模块        820：登陆模块
830：图形刷新和构建模块    210：第三方数据库
具体实施方式
下面结合附图和实施例进行详细说明。
四维空间是指待管理对象的三维空间加上一维时间。
时空数据库是指基于具有时间属性和空间属性的数据建立的数据库。
时空数据库包括历史数据库、实时数据库和计划数据库，分别存储管理对象的模型化的历史数据、实时数据和计划数据。时空数据库里的每个数据都具有空间和时间属性。
实施例1
本实施例提供了一种基于时空数据库的对数据对象的检索方法，检索方法包括如下步骤：
S1：针对待管理对象的时间状态和空间状态对管理对象进行模型化。
依据每个待管理对象的时间状态和空间状态分别建立时间模型、空间模型和/或管理模型。
时间模型：时间模型是用于描述待管理对象时间状态的数据模型。时间模型的时间粒度是衡量时间状态和时间层级的单位，包括时间单位和基于生产情况自定义的时间参数。优选的，时间模型是描述待管理对象时间粒度的模型。例如，时间粒度为年、月、日、小时、分钟或者秒等。也可以自定义时间粒度，如班或者批次等。
空间模型：空间模型是用于描述待管理对象空间状态的数据模型。空间模型的空间粒度是衡量空间层级和空间位置的空间参数，包括空间单位和基于生产情况自定义的空间参数。例如，空间粒度为总公司、分厂、车间、生产线、工序、工位或设备等。
优选的，时间模型和空间模型具有由自然语言定义名称标识的多层级结构。时间模型的多层级结构包括至少一个凭借自然语言描述的父级别时间层级和至少一个与父级别时间层级对应的子级别时间层级。例如，时间层级包括年、月、日、小时、分钟或者秒。年是月的父级别时间层级，月是年的 子级别层级。月是日的父级别时间层级，日是月的子级别层级。时间层级也可以是凭借自然语言描述的订单、工单和产品。订单是工单的父级别时间层级，工单是订单的子级别层级。一个工单对应多个产品，而一个产品只对应一个工单。空间模型的多层级结构包括至少一个凭借自然语言描述的父级别空间层级和至少一个与父级别空间层级对应的子级别空间层级。
建立由待管理对象的空间模型和时间模型关联形成的管理模型。管理模型是用于描述待管理对象的空间状态和时间状态的数据模型。数据与时间模型和空间模型关联后形成时空模型。时空模型是一种有效组织和管理时态空间数据，属性、空间和时间语义更完整的数据模型。通过时空模型监测待管理对象的时间状态和空间状态，可以充分了解待管理对象的运行状态。本发明将管理对象的时空模型简称为管理模型。
数据建模：描述的每个管理对象都是由管理模型实例化来的。管理模型经过实例化过程形成至少一个由管理对象的时间对象和空间对象关联构成的管理对象。其中，管理对象的时间对象由时间模型在实例化过程中形成，管理对象的空间对象由空间模型在实例化过程中形成。
例如，设备是一个物，设备加工产品是一件事。产品是时间，也就是记录设备加工产品的时间。这个时间有时间位置、开始生产时间和结束生产时间。时间位置是唯一的产品编号。如果是实时数据，那么产品编号，开始生产时间和消逝时间结束以后就变更为历史数据了。消逝时间是指产品生产的时长。之后继续扫描设备生产下一个时间(产品)的内容。本发明基于过去、现在和未来三个时间段对事物进行数据建模。
数据模型按照时间状态分为实时数据模型、历史数据模型、计划数据模型。按照功能又分为数据、报警、事件。时态和功能的组合会有更多种数据。数据模型具有版本。一个系统中，同一模型是可以存在多个版本的。模型的实例是对应于模型的某一版本的。模型在生成新版本时，不会影响已经生成的实例。模型某一版本被修改时，会影响该版本模型生成的实例。
数据模型是对数据进行描述的模型，数据模型由两部分组成：属性、成员。属性是数据特有的部分，比如，名字、描述、时间、空间，属性是由系统定义的，用户是不能定义的。根据分类的不同，数据模型的属性会有差别，比如实时数据，具有新鲜度的属性。事件数据具有开始时间、结束时间、持续时间等属性。成员是构成数据的组成部分，用户是可以根据需要定义不同的成员来描述业务中的数据。成员的数据可以使用上面定义的各种类型。从性能上考虑，成员个数限定为最大256个成员。优选的，对于属性名，成员名不允许超过64个字符。
本发明的管理模型指定关联的时间模型和空间模型。本发明将包含有时间模型和空间模型的数据模型简称为时空模型。例如，工位加工的绩效模型，空间属性就是工位，时间属性是班。数据的其它属性可以是工单号、加工数量、报警次数、返工次数等。这些数据模型的数据是通过计算模型来完成的，计算检测生产数据变化，定时统计绩效数据输出到绩效模型。
工厂建模：工厂建模是根据之前的模型进行工厂实例化。实时数据模型、历史数据模型和计划数据模型分布实例化为实时数据对象、历史数据对象和计划数据对象。例如，实际工厂名称、生产线名称、设备名称、工序名称，这是空间实例化。实例化的过程中也确定了各个对象的附属关系。一天有几班，每个班多长，这是时间实例化。实际生产线都有几个工序绩效数据，这是绩效数据模型的实例化。当然还有计算的实例化，因为要计算绩效数据。
系统运行：系统运行后，系统后台自动检测生产信息，记录每个工序的生产情况，实时统计每个工位的生产绩效。至此，一个工厂的生产情况就被实时记录到时空数据库。用户需要查看的时候在场景模型里去进行查询实时和历史生产数据信息。
制定计划：制定计划一般都会制定总的计划比如全厂年计划，再分解到全厂月、全厂日、全厂班， 车间月，车间日，车间班。用户只需要将空间和时间分解到非常细的层级，然后每执行一个时空层级都去监控有没有按照计划执行。
根据一个优选实施方式，时间属性和空间属性是独立的。描述时间对象时有层级和精度，比如年的层级是年，精度可以是秒也可以是毫秒。时间对象在数据记录上有时间位置、时间位置的开始时间和结束时间。比如2016年3月时间位置，该时间位置的开始时间是2016年3月1日0：00：00.000，结束时间是2016年3月31日23：59：59.999。优选地，也可以自定义时间位置。例如，2016财年三月来自自定义的财年(父时间层级)-财月(子时间层级)，开始时间和结束时间是用户自定义的，比如2016年3月2日-3月15日，当用户用2016财年三月就表示这个时间段。
S2：依据待管理对象的管理模型设定待管理对象的凭借自然语言描述的特定属性。
S21：依据时间属性将模型化的待管理对象归类至特定的模型。管理模型包括依据时间属性分类形成的存储于实时数据库的实时数据对象、存储于历史数据库的历史数据对象和存储于计划数据库的计划数据对象。
历史数据对象、实时数据对象和计划数据对象至少包含有时间属性和空间属性。将历史数据对象中的历史对象配置相应的计算机空间属性，历史数据就会自动存储在计算机的历史数据库中。将实时数据对象中的实时对象配置相应的计算机空间属性，实时数据就会自动存储在计算机的实时数据库中。将计划数据对象中的计划对象配置相应的计算机空间属性，计划数据就会自动存储在计算机的计划数据库中。
历史数据库、实时数据库和计划数据库构成了本发明的时空数据库。历史数据库根据配置的条件进行待管理对象历史数据的存储。实时数据库用于存储待管理对象的实时值。计划数据库用于存储待管理对象的计划数据。历史数据库、实时数据库和计划数据库不需要用户配置。用户使用时，需要通过配置界面指定实时服务器、历史服务器、计划服务器。时空数据库系统运行起来，各个服务器客户端会自动将数据发给对应的服务器。例如，实时数据客户端会把系统产生的实时数据传送给实时数据服务器，实时数据服务器上会自动在数据库中创建表格或映射列表，并将相关数据存储到对应的服务器的数据库中。历史和计划数据库也如此。本发明的存储机制不限于此，还包括其它存储机制。
实时数据对象包括经实时数据模型实例化过程形成的至少一个由管理对象的实时数据构成的管理对象。依据实时数据模型实例化为实时数据对象。与实时数据模型关联的空间模型实例化为空间对象。与实时数据模型关联的时间模型实例化为时间对象。管理对象的实时数据对象与空间对象和时间对象分别关联。一个管理模型实例化为多个管理对象。一个版本的实时数据模型实例化形成的多个管理对象的实时数据的数据结构是相同的。实时数据模型实例化后形成的多个管理对象存储在实时数据库中。
历史数据对象包括经历史数据模型实例化过程形成的至少一个由管理对象的历史数据构成的管理对象。依据历史数据模型实例化为历史数据对象。与历史数据模型关联的空间模型实例化为空间对象。与历史数据模型关联的时间模型实例化为时间对象。管理对象的历史数据对象与空间对象和时间对象分别关联。一个管理模型实例化为多个管理对象。一个版本的历史数据模型实例化形成的多个管理对象的历史数据的数据结构是相同的。历史数据模型实例化后形成的多个管理对象存储在历史数据库中。
计划数据对象包括经计划数据模型实例化过程形成的至少一个由管理对象的计划数据构成的管理对象。依据计划数据模型实例化为计划数据对象。与计划数据模型关联的空间模型实例化为空间对象。与计划数据模型关联的时间模型实例化为时间对象。管理对象的计划数据对象与空间对象和时间对象分别关联。一个管理模型实例化为多个管理对象。一个版本的计划数据模型实例化形成的多个管 理对象的计划数据的数据结构是相同的。计划数据模型实例化后形成的多个管理对象存储在计划数据库中。历史数据、实时数据和计划数据的存储存在很大区别。
实时数据的时态是实时的，表示当前时间的数据，具有新鲜度的特质，也就是其数据的刷新周期要符合其时间粒度。例如，如果对象的新鲜度是5秒，则其刷新周期也应该是5秒，如果5秒内不刷新则该对象为不新鲜。实时数据要求有很高的实时性，每秒要能刷新上百万条记录的实时数据，对于没有及时刷新的数据会有新鲜期的限制。超过新鲜期的实时数据转变为历史数据。历史数据时态是历史的，表示过去时间的数据。工业过程的历史数据多数是时序数据，可以进行压缩。历史数据中的业务数据也可以以非压缩的方式进行存储。计划数据时态是未来的，表示未来时间的数据。计划数据依据历史数据和实时数据计算所得。
实时数据库里存储的实时数据对象按照空间特性进行组织，方便存储和检索。历史数据库和计划数据库的历史数据对象和计划数据对象先按照空间特性进行组织，再按照时间特性组织。
根据一个优选实施方式，历史数据库、实时数据库和计划数据库中存储的数据对象必须有时间属性。时间是待管理对象不可分割的属性。没有时间，对象也不可能存在。时间对象是对待管理对象的时间位置的描述。优选地，时间属性至少包括时间位置、开始时间和结束时间。管理对象的时间位置至少包括待管理对象的时间层级、层级精度。例如，生产批次就是一个层级。某个车间第一批次的信息，用户使用起来非常方便，不需要去写某个时间段去获取可能的批次信息。
根据一个优选实施方式，每个管理模型都有唯一的时间层级结构和空间层级结构。以一个计划数据为例，描述的是一个生产线(空间)班(时间)计划，生产线模型和班模型是实现定义的空间模型和时间模型，模型确定以后在工程阶段假设生产线模型有3条生产线对象，班模型有甲乙丙三班。那么数据模型只能实例化3条生产线3个班组共计9个计划数据对象，不能实例化其他时空层级的计划。管理模型的时间层级和空间层级确定以后不能再进行修改，只有修改了属性或者变更成员才会生成新版本。
优选的，依据待管理对象的空间状态对待管理对象的空间进行模型化以建立空间模型。具有多层级结构的空间模型经过实例化过程形成多层级空间对象根据一个优选实施方式，多层级空间对象的实例化的方法包括：通过空间对象编辑器加载地图或者待管理对象的CAD图作为底图；依据待管理对象的空间坐标在底图内绘制一个空间对象作为第一级空间对象，和/或依据自定义的空间范围在底图内绘制一个空间对象作为第一级空间对象；在第一级空间模型内绘制一个空间对象作为第二级空间模型，按照同样的方式，在第n-1级空间模型内绘制一个空间对象作为第n级空间模型。具体地，绘制空间对象的过程如下步骤。
S201：通过空间对象编辑器加载地图或者待管理对象的CAD图纸作为底图。优选的，通过空间对象编辑器加载谷歌地图、百度地图或者待管理对象的CAD图纸作为底图。
S202：在底图内绘制一个空间对象作为第一级空间模型。优选的，在地图配置里选择设定相应的坐标系，基于工厂所在地理位置绘制一个Root根节点的空间范围，在Root根节点的空间范围内用矩形、不规则多边线、点和/或折线来绘制一个空间对象以获得第一级空间模型。
S203：在第一级空间模型内绘制一个空间对象作为第二级空间模型。优选的，在第一级空间模型内用矩形、不规则多边线、点和/或折线来绘制一个空间对象以获得第二级空间模型。
S204：按照同样的方式，在第n-1级空间模型内绘制一个空间对象作为第n级空间模型。优选地，在第n-1级空间模型内用矩形、不规则多边线、点和/或折线来绘制一个空间对象以获得第n级空间模型。
S22：设定待管理对象的特定属性。
特定属性包括凭借自然语言描述的时间属性、空间属性和/或非时空属性。在数据查询时，按照空间和/或时间即可检索模型中的对象，方便快捷。优选的，待管理对象除了具有时间属性和空间属性外，还包括自定义的非时空属性。
优选地，待管理对象的非时空属性包括待管理对象的第一数据类型和第二数据类型的属性。第二数据类型的属性至少包括待管理对象的图形属性、音频属性、视频属性和名称属性中的一种或多种。通过对待管理对象的“点化”，可以实现对各类非常规数据类型数据的对象管理，从而实现统一的存储和查询调用。视频文件用来播放，把视频文件作为图形对象的成员传到显示设备，显示设备会根据图形对象的轮廓建立播放区域，可通过脚本函数来控制视频的播放。音频文件用来播放，提供声音播放函数。对于图片类型作为图形对象的成员，图形对象传送到显示设备时，显示设备将绘制图片到屏幕上。对于文件类型的资源对象，可用于文件的传输和存储，比如把工艺文件保存起来，下达操作规范。图形类型也属于数据类型，也可以作为对象的成员使用。图形类型的坐标是像素坐标。几何类型是描述地理空间对象的形状，在空间对象的属性上需要配置。
优选地，时间属性至少包括时间位置、开始时间和结束时间。时间位置是相对于父空间模型的位置。数据库中每个数据的空间属性包括地理空间范围、地理空间位置、子空间的形状、尺寸及轮廓、候选地理空间位置、计算机空间、候选计算机空间属性等。
优选地，管理对象为静态对象时，空间属性至少包括地理空间范围、地理空间位置和子空间的空间形状、空间范围及空间位置，管理对象为动态对象时，空间属性至少包括地理空间位置、候选地理空间位置和待管理对象的上一级空间模型的空间形状、空间范围及空间位置。例如，维修工的空间范围是车间，空间位置是设备。则维修工的空间位置描述为：维修工在一车间的2号设备旁。此时，空间范围是父空间，空间位置是子空间。
根据一个优选实施方式，不限定顺序步骤S21与S22的顺序。
根据一个优选实施方式，时空数据库中存储的管理对象的数据包括从管理对象现场直接采集的历史数据、通过传感器采集管理对象的实时数据和依据历史数据和实时数据计算所得的待管理对象的计划数据。
优选的，历史数据和计划数据通过计算产生。优选的，计划数据库中的数据也可以是界面交互的图形编辑出来的或者从第三方系统的软件接口导入。例如，通过第三方程序接口或者第三方文件导入计划数据，系统识别为计划数据后，通过界面的编辑和调用算法来计算生成计划数据。
S3：基于管理对象的管理模型类别以及由模型化所限定的凭借自然语言描述的空间属性和/或时间属性进行检索以确定管理对象的运行状态。基于管理对象的管理模型类别、空间位置和/或时间检索在空间位置和/或时间内的至少一个管理对象的实时数据、历史数据和/或计划数据，从而确定至少一个管理对象的实时运行状态、历史运行状态和/或计划运行状态。
或者，基于管理对象的管理模型类别、空间范围和/或时间范围检索在空间范围和/或时间范围内的至少一个管理对象的实时数据、历史数据和/或计划数据，从而确定至少一个管理对象的实时运行状态、历史运行状态和/或计划运行状态。
基于管理对象的管理模型类别以及由模型化限定的凭借自然语言描述的空间属性和/或时间属性进行检索以确定管理对象运行状态的步骤包括：依据管理对象的管理模型类别确定储存管理对象运行数据的实时数据库、历史数据库和/或计划数据库；依据空间属性和/或时间属性选择实时数据库、历史数据库和/或计划数据库中与管理对象相关的至少一个版本的管理对象运行数据；确定与管理模型关联的至少一个管理对象并查看管理对象的实时数据、历史数据和/或计划数据，从而了解管理对象实时运行状态、历史运行状态和/或计划运行状态。
优选的，用户输入管理对象的空间属性、管理模型类别、时间属性数据。系统基于用户输入的空间属性确定机器节点，而后根据管理模型类别确定储存管理对象运行数据的实时数据库、历史数据库和/或计划数据库，再根据时间属性再确定具体数据。更优选地，在确定数据库后，依据用户输入的时间和/或空间位置、时间范围和/或空间范围选择实时数据库、历史数据库和/或计划数据库中与管理对象相关的至少一个版本的管理对象运行数据。用户根据显示的至少一个版本的管理对象运行数据，确定管理对象运行数据的版本并查看该版本管理模型实例化的多个管理对象。选定管理对象，打开该管理对象的运行数据就可以查看管理对象的实时数据、历史数据和/或计划数据，从而了解管理对象实时运行状态、历史运行状态和/或计划运行状态。
实施例2
本实施例是在实施例1的基础上做的进一步改进。
根据一个优选实施方式，计划数据模型根据用户的设置版本建立并更新至少一个包含同一时间状态和空间状态的不同版本的计划数据模型。即计划数据库中存储有多个版本的计划数据模型。多个版本的计划数据模型实例化为多个版本的计划数据对象。选择使用多个版本的计划数据模型中的一个版本，从而确定计划数据对象的版本。计划数据对象即管理对象。
计划数据模型的多版本模式具有重要意义。一个计划变更会对应一系列子计划变更，通过一致版本的计划数据库可以方便查出相关计划。当前制定的计划，需要下发的计划，正在执行的计划一定是某个特定的计划数据版本。例如，在实际运行的过程中，对于一个车间的生产计划，针对一个计划数据对象即将产生的计划运行记录，可能会制定两个运行记录版本。实际生产时计划数据对象只会选择一个版本执行。所以，计划数据模型版本和计划数据对象的记录版本是有差别的。
用户在计算机中设置并存储了多个版本的计划数据模型。由于计划记录的频繁变更，计划数据库对同一个空间和时间会建立并同时更新多个版本的计划数据对象。例如，在实际运行时，不同的计划数据对象的计划运行记录可能会统一更新。比如车间计划记录变了，班组计划记录也会变。用户可以将计划变更统一完成，方便查看。实时数据模型包括至少一个依据同一时间状态和空间状态建立并更新的不同版本的实时数据模型。将不同版本的实时数据模型实例化为不同版本的计划数据对象并存储在实时数据库中。
同一个实时数据模型可以有多个版本来实例化多个实时数据对象。例如，一个车间做升级，新旧系统并存，新旧系统就是用的一个数据模型的两个版本。对新旧两个版本下的系统对象进行监控，如果某个实时数据对象升级，切换到新的版本，在历史存储的时候，会存储每个版本对应的历史记录。
根据一个优选实施方式，历史数据模型基于至少一个不同版本的实时数据模型建立并更新至少一个版本的历史数据模型。将不同版本的历史数据模型实例化为不同版本的历史数据对象并存储在历史数据库中。
历史数据对象在同一时刻可以存在多个版本的值。在修改历史数据对象时，有几种情况：
1、历史数据值版本不变，数据被修改，是覆盖了原来的历史记录。
2、历史数据值增加版本，即增加了一条历史记录。
3、历史数据是不允许删除的。
历史数据的修改方式由用户设置。若用户将历史数据的修改方式设置为不允许修改原记录，则对历史数据进行修改后，就会产生新的版本的历史数据记录。对不同版本的历史数据模型记录的历史数据回放，不仅能看到每个系统的历史数据，而且还能查看历史变迁。例如，车间采集模型V1版本，只支持采集温度和湿度两个参数。在这个模型的基础上，建立了管理对象即车间1对象，采集到温度和湿度的值存储到历史数据库中。历史库中也会记录对应的模型的版本。运行一段时间后，现场系统 升级，除了要采集温度和湿度，还需要采集压力，那么采集模型升级为V2版本，增加了压力的参数。车间1对象升级后，车间1开始采集温度、湿度和压力三个值，并把对应的值存储到数据库中。这样在历史库中，就会记录车间1不同版本情况下产生的历史数据。
对于一个采集管理模型，第一个的版本只有温度、湿度两个参数。第二个版本包括温度、湿度和压力三个参数。
用户在输入管理模型类别、时间数据和/或空间数据后，检索到对象的两个版本的实时数据对象、历史数据对象、计划数据对象。用户可以选择其中一个版本的实时数据对象、历史数据对象、计划数据对象，了解对象的实时、历史或计划运行状态。用户也可以同时打开两个版本的实时数据对象，核对两个数据在同一时刻的数据。
实施例3
本实施例提供了一种基于时空数据库的对数据对象的检索装置。如图1所示，一种基于时空数据库的对数据对象的检索装置，包括数据采集模块200、至少一个数据计算引擎300、时空运行数据库400、工程库服务器500、模型库服务器600、至少一个图形计算引擎700和客户端800。数据采集模块200用于采集待管理对象100的数据信息。数据计算引擎300用于对采集的数据进行数据转换。时空运行数据库400包括实时数据库410、历史数据库420和计划数据库430。实时数据库410、历史数据库420和计划数据库430分别用于存储基于至少一个版本的实时数据模型、历史数据模型和计划数据模型实例化形成的至少一个版本的实时数据对象、历史数据对象和计划数据对象。模型库服务器600上设置有模型库。模型库用于建立时间模型、空间模型、管理模型和计算模型，备工程库500使用。工程库服务器500上设置有工程库。工程库用于导入模型库600中与解决方案相关的模型，进行工程对象实例化。实例化对象包括空间对象、时间对象、管理对象和计算对象。工程库服务器500包括对象定义模块510和登录验证模块520。对象定义模块510用于对模型化的对象进行实例化并进行凭借自然语言描述的实例化定义。对象定义模块510将实时数据模型、历史数据模型、计划数据模型分别实例化为实时数据对象、历史数据对象、计划数据对象。登陆验证模块520用于对检索信息的用户进行身份验证。
优选地，模型库、工程库、实时数据库410、历史数据库420和计划数据库430统称为时空数据库。更优选地，开发过程，模型和对象都是对象语义，模型用来实例化对象语义，模型时对象种类的抽象，对象语义是具体对象的描述。运行过程，实时数据库410、历史数据库420和计划数据库430从工程库加载语义信息创建运行数据对象。
图形计算引擎700用于图形数据计算、检索和客户端800的图形交互展示。图形计算引擎700包括图形计算模块710和场景处理模块720。图形计算模块710用于对图形数据进行计算。场景处理模块720用于对场景显示进行数据处理。场景处理模块720对生产车间的所有设备构建场景模型。场景模型用于显示生产设备的特定属性和运行状态。
客户端800是用于通过数据检索计算模型交互的装置。客户端800包括缓存模块810、登陆模块820和图形刷新和构建模块830。缓存模块810用于对检索数据和显示的数据进行缓存处理。登陆模块820用于输入登录信息和检索信息。图形刷新和构建模块830用于对客户端显示的内容进行父图形刷新处理和/或子图形动态构建。
本实施例还提供了一种基于时空数据库的对数据对象的检索装置的检索方法。针对待管理对象的时间状态和空间状态对管理对象进行模型化。即在模型库服务器600上的模型库内针对待管理对象的时间状态和空间状态建立时间模型、空间模型、管理模型和计算模型。
以生产车间为例，建立多层级空间模型。多层级空间模型包括车间模型、生产线模型和设备模型。 将多层级空间模型实例化为多层级对象。在本实施例中，第一级空间模型为车间模型，第二级空间模型为生产线模型，第三级空间模型为设备模型。空间对象分别为车间、生产线和设备。
建立时间模型。按照班次、批次等自由定义工作现场的时间参数，将时间参数以“班次、批次为单位”进行存储。优选的，按照订单、工单、产品自由定义工作现场的时间层级。此时时间的基本属性包括：时间名称：产品编号；开始时间：产品上线时间；结束时间：产品下线时间。
建立实时数据模型。如图1所示，设置待管理对象即采集对象为设备100。通过数据采集模块200对待管理对象100进行数据的采集。数据采集模块200包括数据采集服务器IOServer。数据采集模块200将采集的数据发送至数据计算引擎300。数据计算引擎300向工程库500服务器发送数据模型请求信息。工程库服务器500响应数据计算引擎300的请求，向模型库服务器600导入实时数据需要的实时数据模型-Tag(时间秒)模型，并且根据数据计算引擎300发送的实时采集数据将Tag(时间秒)模型实例化为Tag(时间秒)对象。Tag(时间秒)对象为第一实时数据对象。数据计算引擎300将第一实时数据对象发送至实时数据库410进行存储。第一实时数据对象的时间层级为自然属性层级，包括年、月、日、时、分钟、秒。即第一实时数据对象中的实时数据包括每个设备的时间数据，例如，上线状态、下线状态、当前产品、当前参数等。
数据计算引擎300还可以根据用户的自定义时间层级将第一实时数据对象通过计算转换为不同时间层级的第二实时数据对象。计算引擎300对第一实时数据对象的实时数据按照预设的版本进行动态数据处理，得到第二实时数据对象。例如，第二实时数据对象中的时间层级为订单、工单、产品，因此第二实时数据对象的实时数据包括产品在设备上的生产事件。
数据计算引擎300对第一实时数据对象转换为超过新鲜期的历史数据对象，并发送至历史数据库420进行存储。具体地，当数据采集模块200根据实时数据检测设备上线时，建立第一实时数据对象。当数据采集模块200根据实时数据检测设备下线，将设备的事件状态存为历史数据对象。数据计算引擎300将实时数据对象计算处理为历史数据对象，储存至历史数据库，将实时事件的状态设置为零。
数据采集模块200还包括第三方数据库210或数据导入接口装置。数据计算引擎300基于实时数据对象和历史数据对象计算生产设备的计划数据对象。或者工程库服务器500基于第三方导入的计划数据将计划数据模型实例化为第一计划数据对象。数据计算引擎300对第一计划数据对象按照预设的版本进行动态数据处理，得到描述生产事件的第二计划数据对象。数据计算引擎300将第二计划数据对象发送至计划数据库430进行存储。实时数据对象储存在实时数据库中，历史数据对象储存在历史数据库中，计划数据对象储存在计划数据库中。
实施例4
本实施例是以一个具体的实例对前述实施例进行说明。
用户需要实现对甲工厂的第一锅炉的信息监测。则第一锅炉为待管理对象。首先需要建立第一锅炉的相关数据模型，并建立与之匹配的时间与空间模型，来定位或监测锅炉的相关数据信息。将相关数据信息与时间模型和空间模型关联，建立管理模型。通过建立时空体系与管理模型，对时间模型和空间模型分别实例化，并将管理模型实例化为管理对象。该管理对象需要选择管理模型关联的空间模型的某个空间对象，还要选择管理模型关联的时间模型的某个时间对象进行关联。例如，第一锅炉实时数据模型关联的空间是锅炉空间模型，关联的时间是班的时间模型。第一锅炉空间模型会实例化出锅炉1，锅炉2，锅炉3三个空间对象。锅炉1，锅炉2，锅炉3是凭借自然语言自定义的空间对象名称。班时间模型会实例化出早班、中班、晚班三个时间对象。早班、中班、晚班是凭借自然语言自定义的时间对象名称。锅炉实时数据模型实例化出锅炉实时数据对象1。锅炉的实时数据对象1的关 联空间对象是锅炉1，关联时间对象是早班、中班、晚班，即时间模型默认对应的是班模型。因为锅炉1是实时数据对象，在计算机存储配置的时候只能选择实时数据库空间。同理实现对历史数据库和计划数据库的建模及关联过程。
其中，建模过程中时间模型的建立，例如班模型的建立即是完成每个班所处的时间段的定义，例如早班时间设定为早上六点至下午三点。空间模型的建立，例如厂模型及锅炉模型的建立，即是对厂模型和锅炉模型的空间形状、空间范围和空间位置的描述。同时定义厂模型为锅炉模型的父模型。建立管理模型，建立管理模型的时候，需要先设定模型类别。管理模型包括实时数据模型、历史数据模型和计划数据模型。运行后，通过模型类型来确定实时数据对象、历史数据对象和计划数据对象的存储位置：实时数据库、历史数据库、计划数据库。同理，查询的时候也是靠管理模型类别类型来判断是去时空数据库中的哪个库查找数据。系统运行后，实时数据对象将采集的值存放到实时数据库，那么在实际产生数据的时候就会记录下例如包含时间信息为2016年10月21日早班的信息。早班信息包含空间信息为锅炉1对应的锅炉模型的空间形状、空间范围和空间位置信息，包含管理模型对应着为锅炉的模型类别信息，以及锅炉的其它属性信息。例如锅炉1的颜色、温度、腔内压强等状态信息。
同时，用户可基于时间信息、空间信息和模型类别信息实现对某个时刻某个锅炉的状态检索。用户选择实时数据模型。系统根据管理对象的实时数据模型确定实时数据库。在确定数据库后，依据用户输入的时间和/或锅炉名称选择实时数据库中与管理对象相关的至少一个版本的锅炉实时数据对象。在确定锅炉实时数据对象的版本后，选择锅炉模型实例化后的空间对象锅炉1，锅炉2，锅炉3中的一个或多个。打开锅炉1的数据就可以查看锅炉1的实时数据，从而了解锅炉1的实时运行状态。查看锅炉1的历史运行状态和计划运行状态的方法与查看锅炉1的实时运行状态的方法相同。查看其它锅炉状态的方法与查看锅炉1的运行状态的方法相同。
实施例5
本实施例提供了一种基于四维空间的对客观世界存在的物体和事件的描述方法。具体描述方法参照前述实施例。
下面以一个具体的例子详细说明该描述方法。
对工业生产进行监控和管理时，将一个车间的生产订单分解为若干个生产线工单，每个生产线工单再落实到该生产线设备生产的产品上，并对空间和时间进行建模。如图2所示，自定义空间模型包括车间模型、生产线模型、设备模型和Tag模型。如图3所示，自定义时间模型包括订单模型、工单模型和产品模型。如图4所示，系统自带的时间模型包括年、月、日、时、分、秒和毫秒。
本实施例之所以将订单、工单和产品划分为时间模型，是因为在做计划时，订单有订单计划开始时间和计划完成时间，工单也有工单计划开始时间和计划完成时间，产品也有产品计划开始时间和计划完成时间。优选地，每个订单、工单和产品都有唯一的名称。即订单编号唯一，某个订单的工单编号也是唯一的，某个工单下的产品也是唯一的。
根据一个优选实施方式，一个订单会被安排在车间生产，并被分解为若干工单，每个工单相当于一个生产批，一批生产若干个产品。在对空间和时间建模时，按照下表1中的时空粒度，将订单计划按照时空分解为不同的计划数据模型。优选地，用户可以自定义每种计划数据模型关注的成员。优选地，计划数据是通过导入或者用户手工录入系统的。计划数据导入或者录入后，系统将计划数据逐级分解，最后分解到设备产品。
下表1列出了各数据模型对应的时间粒度和空间粒度。
表1
序号 模型类型 模型名称 时间粒度 空间粒度
1 实时数据模型 实时数据模型1 秒 Tag
2 实时数据模型 实时数据模型2 产品 设备
3 实时数据模型 实时数据模型3 工单 生产线
4 实时数据模型 实时数据模型4 订单 车间
5 历史数据模型 历史数据模型1 产品 设备
6 历史数据模型 历史数据模型2 工单 生产线
7 计划数据模型 计划数据模型1 产品 设备
8 计划数据模型 计划数据模型2 工单 生产线
9 计划数据模型 计划数据模型3 订单 车间
在图5中，实时数据模型1～实时数据模型4、历史数据模型1和历史数据模型2、计划数据模型1～计划数据模型3分别对应的时间粒度和空间粒度如表1所示。如图5所示，计划数据模型3(时间粒度为订单、空间粒度为车间)通过计划分解计算模型1处理后得到计划数据模型2(时间粒度为工单、空间粒度为生产线)对应的数据对象。同样地，计划数据模型2通过计划分解计算模型2处理后得到计划数据模型1(时间粒度为产品、空间粒度为设备)对应的数据对象。
本实施例通过数据采集服务器IOServer将待管理对象的数据采集到时空数据库。在数据采集服务器IOServer里，数据是以Tag变量的形式存在的。通过采集计算模型，把Tag变量转换成时空数据库可识别的Tag对象。如此可获得实时数据模型1(时间粒度为秒、空间粒度为Tag)对应的数据对象。Tag对象每个设备下都有比如上线状态，下线状态，当前产品，当前参数等。每个设备的状态和参数都是通过Tag对象采集到时空数据库，通过实时事件计算模型实时计算出产品在设备上的生产事件，如此就会动态产生实时数据模型2(时间粒度为产品、空间粒度为设备)对应的数据对象。优选地，每个产品都有所在工单的信息，如果一个工单的产品在某生产线只下线了一部分，那么就会记录生产线工单的实时情况。如果该工单产品全部下线就表示某个生产线的工单完成生产历史数据。依次类推就能计算出车间订单的实时完成情况。如果用户需要还可以继续计算出历史完成情况。具体地，如果产品在设备上下线，事件存储计算模型1基于计划数据模型1输入的计划数据并通过Tag状态变化计算产生一个产品在设备上的历史数据，如此就会动态产生历史数据模型1(时间粒度为产品、空间粒度为设备)对应的数据对象。实时统计计算模型1基于计划数据模型2输入的计划数据并通过产品状态变化计算产生一个工单在生产线上的实时数据，如此就会动态产生实时数据模型3(时间粒度为工单、空间粒度为生产线)对应的数据对象。如果工单在生产线上下线，事件存储计算模型2通过工单状态变化计算产生一个工单在生产线上的历史数据，如此就会动态产生历史数据模型2(时间粒度为工单、空间粒度为生产线)对应的数据对象。实时统计计算模型2通过工单状态变化计算产生一个订单在车间上的实时数据，如此就会动态产生实时数据模型4(时间粒度为订单、空间粒度为车间)对应的数据对象。
实施例6
本实施例提供了一种描述事物时间属性并基于描述进行查找的方法。具体地描述方法参前述实施例。优选地，该方法为对待管理对象模型化以建立至少存储有待管理对象的时间属性和待管理对象的空间属性的历史数据库、实时数据库和计划数据库。通过待管理对象的空间属性确定查找范围后再基于待管理对象的时间属性查找待管理对象的历史运行状态、实时运行状态和/或计划运行状态。下面以具体的例子说明如何对时间属性进行描述的。
日常生活中常用的供暖季、财年、赛季等，对应的标准时间往往是跨年和/或跨月的，若使用标 准时间，不利于信息的查找。例如：工厂常用早班、中班、晚班这样的自然语言来描述2016年10月21日。其中，早班对应的是2016年10月21日08:00～16:00。早班对应的是2016年10月21日16:00～24:00。晚班对应的是2016年10月21日0:00～08:00。若在工业现场使用2016年10月21日08:00～16:00的时间进行描述，不仅繁琐，而且也不符合工厂生产的习惯用语。在进行信息查找时，若用该标准时间，不利于信息的查找。本发明提供的一种描述事物时间属性并基于描述进行查找的方法，直接将待管理对象的时间属性描述为符合日常生活习惯或工业生产过程的自然语言，如供暖季、财年、赛季等，使用这种查询方式是用户最为熟悉的方式，无需进行时间转换，使用自然方便，可以提高查找效率。
实施例7
本实施例提供了一种描述事物空间属性并基于描述进行查找的方法。
根据一个优选实施方式，描述事物空间属性的方法为依据待管理对象的空间状态实现空间信息标注，具体为：通过空间对象编辑器加载地理信息坐标系，并基于待描述事物所在地理位置信息和空间状态信息通过矩形、不规则多边形、点和折线建立多级空间对象，基于多级空间对象实现多层级结构待描述事物各组成元素的空间信息标注；并依据待描述事物的空间对象信息实现事物的查找。
空间对象是对待管理对象的空间属性的描述，空间对象包括待管理对象的空间形状、空间范围和空间位置的描述。也即是实现待管理对象的形状、大小和位置的描述。空间形状是待管理对象物理形状，待管理对象物理形状通过几何的点、线、面实现空间形状的描述。空间范围是待管理对象包络，待管理对象包络通过矩形或立方体来表示；并通过待管理对象的空间形状计算出空间范围的原点，长、宽、高。空间位置是描述待管理对象在空间上所处的位置信息，位置信息包括精确位置信息和逻辑位置信息。精确位置至少为待管理对象的地理坐标位置，逻辑位置为待管理对象中各组成元素的位置信息和/或关系，其中，包括同级空间对象之间位置关系与不同级空间对象的位置关系。
待管理对象的逻辑位置信息和/或关系包括待管理对象的逻辑位置定义信息记忆逻辑位置关系信息，待管理对象的逻辑位置定义为通过自然语言实现对待管理对象的标记，对待管理对象的自然语言标记可以是将待管理对象标记为第一集团公司、第一分厂、第一车间、第一流水线、第一工位等信息。待管理对象的逻辑位置关系信息包括位置的隶属关系和/或层次关系。例如，将待管理对象的空间状态与集团化公司的空间对象相对应匹配，实现工厂、工厂下设车间、车间里的产生线和机械设备的空间信息标注。待管理对象包括静态对象和动态对象，静态对象包括待管理对象的精确位置处于静态和/或逻辑位置处于静态。动态对象包括待管理对象的精确位置处于动态和/或逻辑位置处于动态。例如，动态对象可以是设备或设备上的零部件。设备或设备上的零部件的精确位置可以是地图上的经度、纬度和海拔等位置信息。设备或设备上的零部件的逻辑位置可以是该设备或设备上的零部件移动至或正处于某一生产线、某一车间或某一工厂。
基于事物空间属性的描述进行查找的方法具体为：基于多级和/或多层次待管理对象的空间对象信息进行检索。即是，基于多级和/或多层次事物的空间形状、空间范围和空间位置的描述实现对事物的检索。例如，通过描述事物的几何的点、线、面的空间形状信息实现事物的检索。通过描述事物空间范围的矩形或立方体的原点、长、宽和高的事物包络信息进行事物或对象检索。通过描述事物在空间上所处的精确位置信息和/或逻辑位置信息实现事物的检索。通过对事物逻辑位置的描述，使得对事物位置信息的查找不再需要依靠经度、纬度和海拔信息，仅靠其名称或其它定义信息即可完成对事物位置的查询；同时，基于事物逻辑位置的描述信息，可实现其隶属关系的查询，还可通过本发明实现事物动态精确位置和/或动态逻辑位置的记录与更新，从而实现事物历史位置追溯查询和实时位置查询功能。
实施例8
本实施例提供了一种对象数据的组织方法，对象数据的组织包括数据的定义过程与数据的运行过程，数据定义包括通过空间维度和/或时间维度实现模型库数据的定义与工程库数据的定义。优选地，数据的定义即是基于数据的时间属性和空间属性进行时空数据库建模的过程。具体过程参照前述实施例。数据的运行过程包括以时间维度实现不同数据对象的实时数据库、历史数据库和计划数据的数据更新过程。数据更新过程为基于将保存于实时数据库、计划数据库与历史数据库的数据依据数据的空间特性实现数据第一次组织或更新的基础上，实现对实时数据库、计划数据库和历史数据库中保存的数据按照时间属性进行的第二次组织或更新。
根据一个优选实施方式，对象数据的组织方法还包括基于待管理对象的成员信息的类型实现待管理对象的成员信息的检索。检索包括基于时间信息、空间信息和成员信息的类型完成相应时空内对应对象的对应类型的成员信息检索。检索包括基于时间信息、成员信息的类型完成相应时间点或时间段内至少一个对象对应类型的成员信息检索；检索包括基于空间信息、成员信息的类型完成相应空间内不同时间段对应对象的对应类型的成员信息检索。检索包括基于成员信息的类型完成各个时间段和各个空间内至少一个对象的对应类型的成员信息检索。具体检索方法参照前述实施例。
根据一个优选的实施方式，待管理对象的成员信息的类型包括日期类型、二进制、资源、笔、画刷和字体。即是，待管理对象可以通过包括日期、二进制、资源、笔、画刷和字体的成员信息实现待管理对象的多方位的描述。
根据一个优选的实施方式，资源类型成员信息至少包括与待管理对象相关的2D图形、3D图形、文本、图片、标准通用标记语言下的子集XML、HTML、报表、音频和视频信息中的一种或多种格式的非常规数据类型数据。画刷包括纯色、影线、纹理、线性和路径，例如，可以通过不同颜色、不同的虚实线条、不同的纹理类型、不同的线条类型和不同的线条路径的画刷格式数据来实现不同待管理对象的信息描述。同理，可以通过不同的日期数据、二进制数据、资源数据、笔数据和字体数据实现待管理对象的不同的信息描述和记录。
例如，以锅炉为待管理对象，需要定义锅炉的名称，可以通过字符串定义，例如32个字符；需要定义锅炉的温度，可以通过浮点型数据定义；需要定义锅炉的高度为多少米，可以通过整型数据定义。当完成锅炉属性定义后，数据结构为：锅炉-名称；锅炉-温度；锅炉-高度。若锅炉还有图像信息(video)，颜色信息(color)，锅炉的2D图形信息，锅炉的3D图形信息，则无法用字符串、整型或浮点型数据进行结构化定义。由此产生非常规数据类型数据。本技术方案将非常规数据类型作为待管理对象成员直接引入到待管理对象，使得待管理对象还可以通过ellipse、video、color等数据类型进行直接描述。则数据结构为：锅炉-ellipse；锅炉-video；锅炉-color，由此实现了待管理对象的结构化描述。
对象数据组织过程中除了实现待管理对象使得时间属性数据和空间属性数据的组织，同时实现了把非常规数据类型的数据信息以一个测点或数据记录段的形式定义成了对象成员。例如，数据记录中对象成员包括时间属性数据、空间属性数据、音频数据、视频数据、图片数据、枚举、数字文件等数据类型。数据库通过直接把这些对象成员数据存储下来，不需要用户单独去存储和管理，在使用的时候直接可以在交互界面上显示出来。把非常规数据类型数据都结构化处理，音频、视频、图形都是一个点也就是模型的成员，这样使用起来就非常方便，而现有的软件里都是要单独处理这些非常规数据类型的音视频和图形，存储在单独的服务器。非常规数据类型数据结构化处理，支持了这些类型以后用一个测点，一个成员就能表达和对象相关的非常规数据类型数据信息。
根据一个优选实施方式，数据的运行过程包括以时间维度实现不同数据对象的实时数据库、历史 数据库和计划数据的数据更新过程。其中，数据更新过程为基于将保存于实时数据库、计划数据库与历史数据库的数据依据数据的空间属性实现数据第一次组织的基础上，实现对实时数据库、计划数据库和历史数据库中保存的数据按照时间属性进行的第二次组织。也即是，将完成实例化的存储于实时数据库、历史数据库和计划数据中的待管理对象的数据记录基于空间属性实现数据记录的第一次更新。将存储于实时数据库、历史数据库和计划数据中的完成空间属性更新后的数据记录基于时间属性实现第二次更新。优选地，数据的第一次组织或更新过程为实时数据库、计划数据库与历史数据库基于对象数据的空间属性进行分类并储存的过程。数据的第二次组织或更新为计划数据库和历史数据库基于对象数据的时间属性进行分类并储存的过程。
以本发明的数据图形化成员的使用为例。时空数据在数据库里存储的各种数据是对客观事物的一种描述，比如现场的温度值、压力值、流量值，这些数值都是一些具体的数据，时空数据对象本身的空间信息比如空间形状、空间大小、空间位置以及时间信息不仅用自然语言的形式定义和表达，还应该用图形化的方式形象的展示出来。
以空间为例，用一个多边形的图形成员来描述空间的形状，这个多边形图形成员在模型阶段只是简单的多边形，不代表任何含义，但是在与具体的待描述数据对象发生关联的阶段，时空数据对象上的多边形成员显示的就是实际现场设备的形状，因为每个空间对象都有形状和地理坐标，这个坐标点集可以决定数据对象的位置和大小。数据对象上有图形成员的应用场景：主要是用图形来直观反映数据的空间数据信息。这也就是待管理对象为什么可以支持地图显示，因为每个数据都有空间信息，在查询数据的时候只要选择了地理模式显示数据对象，这些数据就会以地图的形式显示出来，在数据的地理空间范围内，还可以用其他的图形成员来反应其他现场过程数据成员的信息，这样就实现了地图和过程数据的完美结合。
以检测现场的过程数据为例，温度值是一个数据成员，一般定义一个文本图形成员在屏幕上显示现场温度信息，还可以再定义一个圆形图形成员，在温度达到一定值时，不仅输出温度值，还可以让圆形图形成员显示不同的颜色，这样给用户传递的信息更直观，人的大脑接收的信息如果是文字，首先会把这些文字联想成行业的一些通用的图形，然后才理解现场出现的状况，如果直接用行业图形去反应检测的数据结果，这就降低了数据在人大脑转化为信息的过程，可以说本发明用不同行业图形信息来表达不同行业的专业数据，这些数据自动采集的以后，即可由组态配置不同的图形来加以表达。
以本发明的数据音视频成员的使用为例。通过数据采集，可以把采集到的现场的音频、视频数据以实时数据成员的形式直接在展示设备端播放。以往的监控和管理，只能采集到数据，然后用一些形象的图形展示出来。这就好比从前的传感器信息成员只是让用户有了双手，在屏幕上用形象的图形再现现场信息，但是有了音频成员和视频成员，在控制室的用户就有了眼睛和耳朵，可以实时看一个现场的图像和听现场的声音。
音频和视频数据实时采集的同时会按照时空粒度存储，比如当班发生了一个温度报警，在温度报警发生时作为一个触发条件来记录现场的音视频信息，等温度报警消失以后停止记录。用户查询温度报警事件对象的时候除了可以看到温度报警的时(几点钟报警几点钟消失)空信息(具体哪个设备)，还可以通过音视频成员，调度报警发生过程中现场的音视频资料信息，最重要的是这些成员信息都存储在一个历史数据对象上面，用户不需要像以前那样到各个第三方数据库去检索和查看，而是在时空数据库直接把这些数据存储，一个时空查询条件就可以查询出来。
计划数据的音视频的使用，一般作为现场生产指导计划数据，音视频和二进制成员的使用也非常广泛，所谓的资源类型涵盖了音视频、word、pdf、bmp图片等类型，在具体的计划数据对象上，给相应的资源类型关联或者导入具体的资源文件，现场工位的操作人员在执行现场装配任务时就可以调 取不同资源成员信息，这个资源可以是一段视频，也可以是一个pdf指导书，也可以是一段事前录制好的操作指导音频。
音视频也是通过具体的图形成员来显示和播放，比如现场人点击一个文本成员，在图形计算逻辑里会触发一个音频播放函数来播放相应的音频成员信息，有一个视频播放按钮，点击也会触发一个视频播放函数，这个函数来播放相应的视频成员信息。这些成员都可以由用户自由定义，名称任意设置。
上述说明点化的概念，即是，通过丰富数据成员的数据，可以让用户在监控和管理系统组态过程中实现各种各样的复杂功能，是一种结构化和非常规数据类型数据完美融合的解决方案，而且这套解决方案是通过组态的方式实现，而非用高级语言编程的方式去融合各家专业产品。
实施例9
本实施例提供了一种基于时空数据库的对象数据的订阅方法。本发明通过对数据对象采用至少包括时间属性和空间属性的数据库结构，使得所述对象具有包括实时数据库、历史数据库和计划数据库的数据结构，并且所述对象数据的数据库服务器与客户端数据库进行连接交互，通过客户端将订阅请求发送至时空运行数据库，数据库服务器检测这一行为是否属于订阅行为以及判断是否是第一次初始化，如若服务器检测到是属于订阅行为并且是第一次初始化数据，则服务器将按照所订阅的时空范围和数据类别查询相关数据并反馈至客户端，从而使得客户端及时接收对象数据、状态或时间的变化，以便用户及时了解对象的相关运行状态。
该订阅方法中时空数据库的建模至少包括如下步骤：对数据对象的组织过程，组织过程还包括对数据对象的定义过程和运行过程，其中定义过程包括以对象的时间维度和空间维度实现对数据对象的定义，对象的时间维度包括至少三个时间维度的数据结构，从而形成包括对象模型库和工程对象库的数据结构。具体描述方法参照前述实施例。
本发明的实时数据至历史数据的转换是通过产生历史数据计算单元完成的，产生历史数据计算单元是时空运行数据库后台计算，数据计算可以是订阅的实时数据变化的计算，一旦实时数据变化，实时数据库会将变化的数据记录发送至产生历史数据计算单元，产生历史数据计算单元根据计算逻辑来决定是否将该数据产生为历史数据。优选地，后台的数据计算单元可以通过定义一个订阅型数据通道主动对象客户端的订阅。
对象数据的空间维度是依据对象的空间状态对对象进行多层级空间模型化形成的数据结构。
根据一个优选实施方式，订阅方法是通过客户端的主动订阅过程。客户端的图形计算通道将至少包含时间属性和空间属性的订阅请求发送至时空运行数据库，待时空运行数据库检测到其属于订阅行为并且是第一次初始化，数据库服务器将记录订阅请求中的时空范围数据和模型类别属性并反馈至客户端的图形计算通道内。
订阅方法还包括在客户端的图形计算一直处于被开启的状态时，数据库服务器会记录该客户端的订阅请求，客户端的订阅请求可以是对象的时间属性、空间属性和模型类别属性，在时空数据库的服务器检测到该客户端初始化查询的数据发生变化时，时空运行数据库主动将变化的数据发送至客户端的图形计算通道，并被客户端的计算引擎存储在图形计算的通道内，客户端直接从图形计算通道内得到订阅的数据。例如：订阅请求为：时间属性为早班，空间属性为锅炉1，模型类别为锅炉模型，其中例如时间属性的早班的开始时间为8︰00，结束时间为12︰00。用户在客户端对时空数据库发送包含上述对象属性的订阅请求，时空运行数据库会检测其所接收到的上述请求是否为订阅请求，并且该订阅请求是否为第一次初始化数据，若是，则时空数据库将响应于上述订阅请求，并实时检测上述订阅请求范围内的相关对象数据，即锅炉1在早班时的运行状态数据。当锅炉1在早班时的运行状态数据记录发生变化时，时空运行数据库将包括锅炉1早班的运行状态数据记录主动推送至客户端。
根据本发明的一种优选实施方式，本发明的订阅行为可以是对对象实时数据的订阅，只要对象的实时数据发生变化，服务器就自动通知客户端。根据另一种优选实施方式，本发明的订阅行为可以是对对象历史数据和/或计划数据的订阅，只要对象的历史数据的被订阅请求的空间和/或时间范围的数据记录被修改，服务器将会把修改的数据记录发送至客户端。并且由于历史数据和计划数据的修改会产生新版本，客户端因此会接收到全部版本的数据。从而在每个对象的实时数据与其历史数据库和/或计划数据库的相应数据存在差异时，用户可以及时了解管理对象的运行状态。
具体的，本发明通过在图形计算模型上设置订阅过程，将图形计算的通道设置为订阅模式，在客户端初始化时，数据库服务器将根据客户端图形计算的时间、空间范围和模型类别去检测相应对象数据，并将数据主动推送至客户端，其余无论客户端如何操作，除非关闭场景再打开重新初始化，否则服务器不会发送数据至客户端，只有所订阅的时空范围内对象的数据记录发生变化，服务器才会将变化的数据记录发送至客户端的图形计算通道。优选地，本发明也可以通过在时空运行数据库端建立订阅型数据通道模型，从而对客户端的订阅请求进行数据处理计算。
需要注意的是，上述具体实施例是示例性的，本领域技术人员可以在本发明公开内容的启发下想出各种解决方案，而这些解决方案也都属于本发明的公开范围并落入本发明的保护范围之内。本领域技术人员应该明白，本发明说明书及其附图均为说明性而并非构成对权利要求的限制。本发明的保护范围由权利要求及其等同物限定。

Claims (17)

  1. 一种基于时空数据库的对数据对象的检索方法，其特征在于，所述检索方法为对待管理对象进行模型化后基于管理对象的管理模型类别以及空间属性和/或时间属性进行检索以确定所述管理对象的运行状态，并且所述检索方法包括如下步骤：
    针对待管理对象的时间状态和空间状态对所述管理对象进行模型化；
    依据待管理对象的管理模型设定所述待管理对象的凭借自然语言描述的特定属性；
    基于管理对象的所述管理模型类别以及由所述模型化所限定的凭借自然语言描述的空间属性和/或时间属性进行检索以确定所述管理对象的运行状态。
  2. 如权利要求1所述的基于时空数据库的对数据对象的检索方法，其特征在于，对待管理对象进行模型化的方法至少包括如下步骤：
    依据待管理对象的空间状态对所述待管理对象进行模型化，
    依据待管理对象的时间状态对所述待管理对象进行模型化，
    设定所述待管理对象的特定属性，
    采集所述待管理对象的数据以对所述待管理对象动态监测和管理。
  3. 如权利要求2所述的基于时空数据库的对数据对象的检索方法，其特征在于，所述基于管理对象的所述管理模型类别以及由所述模型化所限定的凭借自然语言描述的空间属性和/或时间属性进行检索以确定所述管理对象的运行状态的步骤包括：
    基于管理对象的所述管理模型类别、空间位置和/或时间检索在所述空间位置和/或所述时间内的至少一个管理对象的实时数据、历史数据和/或计划数据，从而确定至少一个所述管理对象的实时运行状态、历史运行状态和/或计划运行状态；或者
    基于管理对象的所述管理模型类别、空间范围和/或时间范围检索在所述空间范围和/或所述时间范围内的至少一个管理对象的实时数据、历史数据和/或计划数据，从而确定至少一个所述管理对象的实时运行状态、历史运行状态和/或计划运行状态。
  4. 如权利要求3所述的基于时空数据库的对数据对象的检索方法，其特征在于，确定所述管理对象的运行状态的步骤还包括：
    依据管理对象的管理模型类别确定储存管理对象运行数据的实时数据库、历史数据库和/或计划数据库，
    依据空间属性和/或时间属性选择实时数据库、历史数据库和/或计划数据库中与所述管理对象相关的至少一个版本的所述管理对象运行数据，并且
    确定与所述管理模型关联的至少一个管理对象并查看所述管理对象的实时数据、历史数据和/或计划数据，从而了解所述管理对象实时运行状态、历史运行状态和/或计划运行状态。
  5. 如权利要求4所述的基于时空数据库的对数据对象的检索方法，其特征在于，所述管理对象包括依据时间属性分类形成的存储于所述实时数据库的实时数据对象、存储于所述历史数据库的历史数据对象和存储于所述计划数据库的计划数据对象，
    所述实时数据对象包括经所述实时数据模型实例化过程形成的至少一个由所述管理对象的实时数据构成的管理对象，
    所述历史数据对象包括经所述历史数据模型实例化过程形成的至少一个由所述管理对象的历史数据构成的管理对象，
    所述计划数据对象包括经所述计划数据模型实例化过程形成的至少一个由所述管理对象的计划 数据构成的管理对象。
  6. 如上述权利要求之一所述的基于时空数据库的对数据对象的检索方法，其特征在于，针对待管理对象的时间状态和空间状态对所述管理对象进行模型化的步骤包括：
    依据待管理对象的空间状态对所述待管理对象的空间进行模型化以建立空间模型，
    依据待管理对象的时间状态对所述待管理对象的时间进行模型化以建立时间模型，以及
    建立由所述待管理对象的所述空间模型和所述时间模型关联形成的所述管理模型。
  7. 如权利要求6所述的基于时空数据库的对数据对象的检索方法，其特征在于，所述依据待管理对象的管理模型设定所述待管理对象的凭借自然语言描述的特定属性的步骤包括：
    所述管理模型经过实例化过程形成至少一个由所述管理对象的时间对象和空间对象关联构成的管理对象，
    所述管理对象的时间对象由所述时间模型在实例化过程中形成，所述管理对象的空间对象由所述空间模型在实例化过程中形成。
  8. 如权利要求7所述的基于时空数据库的对数据对象的检索方法，其特征在于，所述依据待管理对象的管理模型设定所述待管理对象的凭借自然语言描述的特定属性的步骤还包括：
    设定所述管理对象的特定属性，所述特定属性包括凭借自然语言描述的时间属性、空间属性和/或非时空属性，
    所述非时空属性包括待管理对象的第一数据类型和第二数据类型的属性，并且所述第二数据类型的属性至少包括待管理对象的图形属性、音频属性、视频属性和名称属性中的一种或多种。
  9. 如权利要求8所述的基于时空数据库的对数据对象的检索方法，其特征在于，所述时间属性至少包括时间位置、开始时间和结束时间，
    所述管理对象为静态对象时，所述空间属性至少包括地理空间范围、地理空间位置和子空间的空间形状、空间范围及空间位置，
    所述管理对象为动态对象时，所述空间属性至少包括地理空间位置、候选地理空间位置和所述待管理对象的上一级空间模型的空间形状、空间范围及空间位置。
  10. 如权利要求6至9之一所述的基于时空数据库的对数据对象的检索方法，其特征在于，
    所述时间模型和所述空间模型具有由自然语言定义名称标识的多层级结构，
    所述时间模型的多层级结构包括至少一个凭借自然语言描述的父级别时间层级和至少一个与所述父级别时间层级对应的子级别时间层级，
    所述空间模型的多层级结构包括至少一个凭借自然语言描述的父级别空间层级和至少一个与所述父级别空间层级对应的子级别空间层级。
  11. 如权利要求9所述的基于时空数据库的对数据对象的检索方法，其特征在于，描述事物空间属性的方法为依据待管理对象的空间状态实现待管理对象的空间信息标注，具体为：
    通过空间对象编辑器加载地理信息坐标系，并基于待管理对象所在地理位置信息和空间状态信息通过矩形、不规则多边形、点和折线建立多级空间对象，基于多级空间对象实现多层级结构待管理对象各组成元素的空间信息标注。
  12. 如权利要求11所述的基于时空数据库的对数据对象的检索方法，其特征在于，所述空间信息标注过程为：
    通过空间对象编辑器加载地理信息坐标系，并基于待管理对象所在地理位置绘制一个root根节点的空间范围，在root根节点范围内用矩形、不规则多边线、点和折线绘制一个空间对象以得到待管理对象的第一级空间对象；
    基于上一级空间对象，用矩形、不规则多边线、点和折线逐级实现待管理对象的组成元素的空间绘制过程以得到所述组成元素对应等级空间对象；
    将待管理对象的空间状态与空间对象中各级空间对象相对应匹配，从而实现对多级和/或多层次待管理对象的空间信息标注。
  13. 如权利要求12所述的基于时空数据库的对数据对象的检索方法，其特征在于，所述空间形状是待管理对象物理形状，所述待管理对象物理形状通过几何的点、线、面实现所述空间形状的描述；
    所述空间范围是待管理对象包络，所述待管理对象包络通过矩形或立方体来表示；并通过所述待管理对象的空间形状计算出空间范围的长、宽、高；
    所述空间位置是描述待管理对象在空间上所处的位置信息，所述位置信息包括精确位置信息和逻辑位置信息；
    所述精确位置至少为待管理对象的地理坐标位置，所述逻辑位置为待管理对象中各组成元素的位置信息和/或关系，其中，包括同级空间对象之间位置关系与不同级空间对象的位置关系。
  14. 如权利要求10所述的基于时空数据库的对数据对象的检索方法，其特征在于，通过如下方法采集所述待管理对象的数据：
    通过从所述待管理对象现场直接采集所述待管理对象的历史数据或者通过计算采集所述待管理对象的历史数据，
    通过传感器采集所述待管理对象的实时数据或者通过计算采集所述待管理对象的实时数据，
    通过从第三方系统接口导入计划需求并通过计算生成计划数据。
  15. 如前述权利要求之一所述的基于时空数据库的对数据对象的检索方法，其特征在于，在对所述数据对象检索之前，所述检索方法还包括基于四维空间的对客观世界存在的物体和事件进行描述的方法，并且所述描述方法为对待管理对象模型化以建立至少存储有所述待管理对象的时间属性和所述待管理对象的空间属性的历史数据库、实时数据库和计划数据库。
  16. 如权利要求15所述的基于时空数据库的对数据对象的检索方法，其特征在于，基于四维空间的对客观世界存在的物体和事件进行描述并建立历史数据库、实时数据库和计划数据库之后，所述检索方法通过所述待管理对象的管理模型类别、凭借自然语言描述的空间属性和/或时间属性查找所述待管理对象的历史运行状态、计划运行状态和/或实时运行状态。
  17. 如权利要求15所述的基于时空数据库的对数据对象的检索方法，其特征在于，基于四维空间的对客观世界存在的物体和事件进行描述并建立历史数据库、实时数据库和计划数据库之后，所述检索方法通过所述待管理对象执行订阅以查找所述待管理对象的历史运行状态、计划运行状态和/或实时运行状态，其中，所述订阅方法至少包括如下步骤：
    客户端向时空数据库针对至少一个数据记录发出包含管理模型类别、凭借自然语言描述的空间属性和/或时间属性的订阅请求；
    所述时空数据库响应于所述订阅请求，将包含待管理对象的凭借自然语言描述的空间属性和/或时间属性的至少一个数据记录主动推送至所述客户端。
PCT/CN2017/100377 2016-10-24 2017-09-04 一种基于时空数据库的对数据对象的检索方法 WO2018076930A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US16/343,210 US11243927B2 (en) 2016-10-24 2017-09-04 Method for retrieving data object based on spatial-temporal database
CN201780020385.XA CN108885634B (zh) 2016-10-24 2017-09-04 一种基于时空数据库的对数据对象的检索方法
EP17864325.0A EP3531310A4 (en) 2016-10-24 2017-09-04 METHOD FOR EXTRACTING A DATABASE BASED ON A SPATIO-TEMPORAL DATABASE

Applications Claiming Priority (12)

Application Number Priority Date Filing Date Title
CN201610925967.XA CN106294887B (zh) 2016-10-24 2016-10-24 基于四维空间的对客观世界存在的物体和事件的描述方法
CN201610926060.5A CN106446278B (zh) 2016-10-24 2016-10-24 一种基于时空数据库的对数据对象的检索方法
CN201610927538.6A CN106407469B (zh) 2016-10-24 2016-10-24 一种描述事物时间属性并基于所述描述进行查找的方法
CN201610925992.8 2016-10-24
CN201610925967.X 2016-10-24
CN201610925969.9 2016-10-24
CN201610926060.5 2016-10-24
CN201610925992.8A CN106294888B (zh) 2016-10-24 2016-10-24 一种基于时空数据库的对象数据的订阅方法
CN201610925969.9A CN106407468B (zh) 2016-10-24 2016-10-24 一种描述事物空间属性并基于所述描述进行查找的方法
CN201610927538.6 2016-10-24
CN201611271001.5 2016-12-30
CN201611271001.5A CN106649867B (zh) 2016-12-30 2016-12-30 一种对象数据的组织方法

Publications (1)

Publication Number Publication Date
WO2018076930A1 true WO2018076930A1 (zh) 2018-05-03

Family

ID=62024301

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/100377 WO2018076930A1 (zh) 2016-10-24 2017-09-04 一种基于时空数据库的对数据对象的检索方法

Country Status (4)

Country Link
US (1) US11243927B2 (zh)
EP (1) EP3531310A4 (zh)
CN (1) CN108885634B (zh)
WO (1) WO2018076930A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111026938A (zh) * 2019-12-20 2020-04-17 山东省国土测绘院 时空大数据整合分析方法、装置、设备及存储介质
CN113965592A (zh) * 2020-07-01 2022-01-21 珠海优特智厨科技有限公司 物联网设备的处理方法、装置及设备
CN117290457A (zh) * 2023-11-22 2023-12-26 湖南省第一测绘院 地理实体多模态数据管理系统及数据库和时序化管理方法
WO2024002292A1 (zh) * 2022-06-30 2024-01-04 北京亚控科技发展有限公司 模型构建及模型数据订阅方法、装置、电子设备和介质
CN113965592B (zh) * 2020-07-01 2024-06-07 珠海优特智厨科技有限公司 物联网设备的处理方法、装置及设备

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3999926A1 (en) * 2019-07-15 2022-05-25 ABB Schweiz AG A method and system for controlling performance of a batch process in an industrial plant
CN112653586B (zh) * 2019-10-12 2022-04-19 苏州工业园区测绘地理信息有限公司 基于全链路监控的时空大数据平台应用性能管理方法
CN111027199B (zh) * 2019-12-04 2022-09-09 南京国电南自电网自动化有限公司 一种变电站主辅设备全景模型及建模方法
US20230009093A1 (en) * 2019-12-13 2023-01-12 Basf Se Manufacturing system for monitoring and/or controlling one or more chemical plant(s)
CN111090669A (zh) * 2019-12-16 2020-05-01 北京明略软件系统有限公司 一种基于时空碰撞的数据查询方法及装置
CN111078755B (zh) * 2019-12-19 2023-07-28 远景智能国际私人投资有限公司 时序数据的存储查询方法、装置、服务器及存储介质
CN112330281A (zh) * 2020-11-05 2021-02-05 南京师范大学 一种面向沿革数据的中国行政区划关联方法
CN113722288A (zh) * 2021-07-27 2021-11-30 张博 一种时空数据统计的建模方法
CN115858831B (zh) * 2023-02-22 2023-06-23 珠海大横琴孵化器管理有限公司 一种数据库用数据存储方法

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102023983A (zh) * 2009-09-11 2011-04-20 首都师范大学 统计时空数据库及其管理方法
CN103425789A (zh) * 2013-08-28 2013-12-04 深圳信息职业技术学院 一种时空数据的查询方法及装置
CN103678712A (zh) * 2013-12-31 2014-03-26 上海师范大学 一种灾害信息时空数据库
US20150066903A1 (en) * 2013-08-29 2015-03-05 Honeywell International Inc. Security system operator efficiency
CN105426491A (zh) * 2015-11-23 2016-03-23 武汉大学 一种时空地理大数据的检索方法及系统
CN106294888A (zh) * 2016-10-24 2017-01-04 北京亚控科技发展有限公司 一种基于时空数据库的对象数据的订阅方法
CN106294887A (zh) * 2016-10-24 2017-01-04 北京亚控科技发展有限公司 基于四维空间的对客观世界存在的物体和事件的描述方法
CN106407469A (zh) * 2016-10-24 2017-02-15 北京亚控科技发展有限公司 一种描述事物时间属性并基于所述描述进行查找的方法
CN106407468A (zh) * 2016-10-24 2017-02-15 北京亚控科技发展有限公司 一种描述事物空间属性并基于所述描述进行查找的方法
CN106446278A (zh) * 2016-10-24 2017-02-22 北京亚控科技发展有限公司 一种基于时空数据库的对数据对象的检索方法
CN106649867A (zh) * 2016-12-30 2017-05-10 北京亚控科技发展有限公司 一种对象数据的组织方法

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040249848A1 (en) * 2003-06-06 2004-12-09 Carlbom Ingrid Birgitta Method and apparatus for intelligent and automatic alert management using multimedia database system
CN101231642A (zh) * 2007-08-27 2008-07-30 中国测绘科学研究院 时空数据库管理方法及其系统
US8302015B2 (en) * 2008-09-04 2012-10-30 Qualcomm Incorporated Integrated display and management of data objects based on social, temporal and spatial parameters
US8458177B2 (en) * 2009-02-02 2013-06-04 Yahoo! Inc. Automated search
US20110202326A1 (en) * 2010-02-17 2011-08-18 Lockheed Martin Corporation Modeling social and cultural conditions in a voxel database
CN101799835B (zh) * 2010-04-21 2012-07-04 中国测绘科学研究院 一种本体驱动地理信息检索系统和检索方法
US9053194B2 (en) * 2012-02-01 2015-06-09 Sri International Method and apparatus for correlating and viewing disparate data
KR101951417B1 (ko) * 2012-03-09 2019-02-22 엘지전자 주식회사 휴대 전자기기 및 이의 제어 방법
US20140007017A1 (en) * 2012-06-27 2014-01-02 Marinexplore Inc. Systems and methods for interacting with spatio-temporal information
US9253054B2 (en) * 2012-08-09 2016-02-02 Rockwell Automation Technologies, Inc. Remote industrial monitoring and analytics using a cloud infrastructure
US9146969B2 (en) * 2012-11-26 2015-09-29 The Boeing Company System and method of reduction of irrelevant information during search
CN103246727B (zh) * 2013-05-10 2016-09-21 四川省林业调查规划院 一种多用户森林资源时空数据库构建的方法
US10380105B2 (en) * 2013-06-06 2019-08-13 International Business Machines Corporation QA based on context aware, real-time information from mobile devices
US9495383B2 (en) * 2013-08-22 2016-11-15 Microsoft Technology Licensing Realtime activity suggestion from social and event data
CN103955511B (zh) * 2014-04-30 2017-02-15 华南理工大学 一种城市3d建筑数据的云平台数据组织和检索方法
WO2018197084A1 (en) * 2017-04-25 2018-11-01 Murex S.A.S Query plan generation and execution in a relational database management system with a temporal-relational database
US11412343B2 (en) * 2017-09-30 2022-08-09 Oracle International Corporation Geo-hashing for proximity computation in a stream of a distributed system

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102023983A (zh) * 2009-09-11 2011-04-20 首都师范大学 统计时空数据库及其管理方法
CN103425789A (zh) * 2013-08-28 2013-12-04 深圳信息职业技术学院 一种时空数据的查询方法及装置
US20150066903A1 (en) * 2013-08-29 2015-03-05 Honeywell International Inc. Security system operator efficiency
CN103678712A (zh) * 2013-12-31 2014-03-26 上海师范大学 一种灾害信息时空数据库
CN105426491A (zh) * 2015-11-23 2016-03-23 武汉大学 一种时空地理大数据的检索方法及系统
CN106294888A (zh) * 2016-10-24 2017-01-04 北京亚控科技发展有限公司 一种基于时空数据库的对象数据的订阅方法
CN106294887A (zh) * 2016-10-24 2017-01-04 北京亚控科技发展有限公司 基于四维空间的对客观世界存在的物体和事件的描述方法
CN106407469A (zh) * 2016-10-24 2017-02-15 北京亚控科技发展有限公司 一种描述事物时间属性并基于所述描述进行查找的方法
CN106407468A (zh) * 2016-10-24 2017-02-15 北京亚控科技发展有限公司 一种描述事物空间属性并基于所述描述进行查找的方法
CN106446278A (zh) * 2016-10-24 2017-02-22 北京亚控科技发展有限公司 一种基于时空数据库的对数据对象的检索方法
CN106649867A (zh) * 2016-12-30 2017-05-10 北京亚控科技发展有限公司 一种对象数据的组织方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3531310A4 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111026938A (zh) * 2019-12-20 2020-04-17 山东省国土测绘院 时空大数据整合分析方法、装置、设备及存储介质
CN111026938B (zh) * 2019-12-20 2023-03-24 山东省国土测绘院 时空大数据整合分析方法、装置、设备及存储介质
CN113965592A (zh) * 2020-07-01 2022-01-21 珠海优特智厨科技有限公司 物联网设备的处理方法、装置及设备
CN113965592B (zh) * 2020-07-01 2024-06-07 珠海优特智厨科技有限公司 物联网设备的处理方法、装置及设备
WO2024002292A1 (zh) * 2022-06-30 2024-01-04 北京亚控科技发展有限公司 模型构建及模型数据订阅方法、装置、电子设备和介质
CN117290457A (zh) * 2023-11-22 2023-12-26 湖南省第一测绘院 地理实体多模态数据管理系统及数据库和时序化管理方法
CN117290457B (zh) * 2023-11-22 2024-03-08 湖南省第一测绘院 地理实体多模态数据管理系统及数据库和时序化管理方法

Also Published As

Publication number Publication date
CN108885634B (zh) 2022-09-09
EP3531310A4 (en) 2020-04-29
CN108885634A (zh) 2018-11-23
US20190266138A1 (en) 2019-08-29
EP3531310A1 (en) 2019-08-28
US11243927B2 (en) 2022-02-08

Similar Documents

Publication Publication Date Title
WO2018076930A1 (zh) 一种基于时空数据库的对数据对象的检索方法
CN106294888B (zh) 一种基于时空数据库的对象数据的订阅方法
CN106294887B (zh) 基于四维空间的对客观世界存在的物体和事件的描述方法
CN106407469B (zh) 一种描述事物时间属性并基于所述描述进行查找的方法
CN108874988B (zh) 一种对数据对象的检索方法
CN108959353B (zh) 一种对象数据的组织方法
CN108038222B (zh) 用于信息系统建模和数据访问的实体-属性框架的系统
CN104205039B (zh) 使用兴趣驱动数据管线进行数据分析的兴趣驱动商业智能系统和方法
US20180137180A1 (en) Systems and methods for interest-driven data visualization systems utilized in interest-driven business intelligence systems
CN111680025A (zh) 面向自然资源多源异构数据时空信息智能同化的方法及系统
US20060112109A1 (en) Adaptive data warehouse meta model
US11704340B2 (en) Linking discrete dimensions to enhance dimensional analysis
CN112633822B (zh) 基于数字孪生技术的资产管理方法、存储介质和移动终端
CN108875087B (zh) 一种描述事物空间属性并基于所述描述进行查找的方法
US10552423B2 (en) Semantic tagging of nodes
CN111784192A (zh) 一种基于动态演化的工业园区应急预案可执行化系统
CN206557772U (zh) 一种事物的时间描述系统
CN206557773U (zh) 一种基于四维空间对客观世界存在的事物描述的系统
Stefanovic Designing OLAP multidimensional systems for supply chain management
CN116306662A (zh) 一种基于物联网标识的生产要素管理系统及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17864325

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2017864325

Country of ref document: EP