CN117009317A - Metadata-driven SaaS-based service platform for managing charging station - Google Patents

Metadata-driven SaaS-based service platform for managing charging station Download PDF

Info

Publication number
CN117009317A
CN117009317A CN202310920831.XA CN202310920831A CN117009317A CN 117009317 A CN117009317 A CN 117009317A CN 202310920831 A CN202310920831 A CN 202310920831A CN 117009317 A CN117009317 A CN 117009317A
Authority
CN
China
Prior art keywords
data
service
metadata
module model
layer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310920831.XA
Other languages
Chinese (zh)
Inventor
钱中道
张晖
李明
林俊豪
郭春杰
夏晨朗
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Sicui Industrial Internet Technology Research Institute Co ltd
Original Assignee
Suzhou Sicui Industrial Internet Technology Research Institute Co ltd
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
Application filed by Suzhou Sicui Industrial Internet Technology Research Institute Co ltd filed Critical Suzhou Sicui Industrial Internet Technology Research Institute Co ltd
Priority to CN202310920831.XA priority Critical patent/CN117009317A/en
Publication of CN117009317A publication Critical patent/CN117009317A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/211—Schema design and management
    • G06F16/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/25—Integrating or interfacing systems involving database management systems
    • G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
    • 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/06—Energy or water supply

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Public Health (AREA)
  • Water Supply & Treatment (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention discloses a metadata-driven SaaS-based service platform for managing charging stations, and relates to the technical field of cloud platforms based on SaaS, comprising an application layer, a platform service layer, a metadata layer and a data storage layer; the application layer is provided with a module model of a service module model library for docking differentiated service application; the platform service layer is provided with a module model of the service module model library, provides a unified application service interface for service module model call, and completes standardized module model construction and service module model association maintenance based on the metadata layer; the metadata layer is used for carrying out metadata definition and service data perspective on the module models of the service module model library; the data storage layer stores the data generated by each layer, records the data state change of the module model, and performs data persistence on the data generated under different versions of the corresponding metadata module model. According to the invention, data analysis of charging stations under cross regions can be realized, and the data island of each charging station is opened.

Description

Metadata-driven SaaS-based service platform for managing charging station
Technical Field
The invention relates to the technical field of cloud platforms based on SaaS, in particular to a service platform of a SaaS management charging station based on metadata driving.
Background
The multi-tenant technology or the multi-tenant technology, which is called as SaaS technology for short, is a software architecture technology, and is realized to use the same set of code program under the multi-enterprise-level user environment, and the data isolation among tenants is ensured.
The standardization degree of the charging station service management platform in the current industry is not high, and the difference exists among manufacturers, so that the platforms of different manufacturers are difficult to communicate with each other, and the management and maintenance of the charging station are difficult to integrate; and a large amount of user information and transaction data are involved, if the data security measures are not in place, the problems of user information leakage, tampered transaction data and the like can be caused; the operation is relatively complex, and professional technicians are required to operate, so that the operation is not friendly to general users and the user experience is affected.
With the development of electric vehicle charging technology and SaaS service technology, charging station management is a main link in the charging industry system engineering. The traditional scheme mainly solves the charging station management problem by independently developing and managing the system, can not effectively reduce the cost of software development services in the aspect of carrying out large-scale operation of the charging station, can add additional customized development cost to operators needing to be connected with different charging piles, and can easily form a data island in the aspect of analyzing the charging station operation data of different places. If different charging stations are subjected to unified management in a SaaS mode, the following advantages exist: on one hand, the software research and development cost can be reduced, the period of constructing a charging station management system is shortened, the data analysis of charging stations under cross-regional conditions can be realized, and the scale effect of charging station operation management is realized.
In view of the above analysis, how to manage charging station data by combining SaaS service modes with metadata to implement a charging station cloud service platform is a problem to be solved.
Disclosure of Invention
When a traditional operator needs to operate a charging station in a large scale, the cost of software research and development service cannot be effectively reduced; meanwhile, extra customized research and development cost is increased when the charging pile is required to be in butt joint with different charging pile operators; in addition, data islands are easily formed when charging station operation data analysis at different sites is required. Aiming at the problems, the invention provides a metadata-driven SaaS management charging station service platform, which solves the problem of data docking of different charging pile operators, shortens the period of constructing a charging station management system, can realize charging station data analysis under the inter-regional management of the operators, and opens up the data island of each charging station due to the scale effect of charging station operation management.
The invention discloses a metadata-driven SaaS-based service platform for managing charging stations, which solves the technical problems and adopts the following technical scheme:
a metadata-driven SaaS-based charging station management service platform, comprising an application layer, a platform service layer, a metadata layer and a data storage layer, wherein:
the application layer is provided with a service provider management module, a consumer user module and an order module of a service module model library and is used for docking differentiated service application;
the platform service layer is provided with a charging pile management module, a payment module and a data analysis module of the service module model library, provides a unified application service interface and is used for service module model calling, and standardized module model building and service module model association maintenance are completed based on the metadata layer;
the metadata layer is used for carrying out metadata definition operation on the module models of the service module model library and carrying out service data perspective operation on the association relationship between the module models in the service module model library;
the data storage layer is used for storing data generated by the application layer, the platform service layer and the metadata layer, defining a module model based on metadata, recording the data state change of the module model based on the association relation between the business data perspective module models, and carrying out data persistence on the data generated under different versions of the corresponding metadata module model.
Optionally, when the module model data is changed, in the metadata layer, firstly, copying the changed module model through metadata definition, and then, changing the copied module model;
and after the module model is changed and validated, synchronizing the business data perspective and the data storage layer, and changing the use state of the original metadata definition module model after synchronization is completed.
Optionally, the metadata definition is used for managing field definition in standard objects, tenant custom objects and metadata; the metadata definition comprises an object set and a field set, and is used as a unified management area and a metadata definition area of standard object metadata definition and tenant custom object metadata definition;
and the metadata definition completes the standardized flow operation of the differentiated service requirement through standard object definition and custom object definition, describes an object model through a field set, and describes a service module model through the object set.
Further optionally, the involved business data perspective comprises a relational data area and an index area, wherein,
binding different basic service models through a relation data area by service data perspective, and constructing a complex service model, namely splitting the complex service model into a plurality of basic service models, wherein the association between the service models is the service data perspective;
the service model accelerates the retrieval of the required service model related data through the index area.
Preferably, the related business data perspective further comprises a custom area, wherein the custom area is used as an extension attribute of the relation data area and the index area and is used for custom setting of association relation and index.
Optionally, the data storage layer includes a standard data area and a non-standard data area, and is used as a tenant force service data persistence area for storing service platforms and instance data of tenant objects and fields.
Further optionally, the data storage layer involved further comprises an object system area and a field system area, wherein,
the object system area persists the MDD of the extended application model provided by the tenant service provider for the object system area, and comprises an application object unique ID, an application object attribution tenant ID, an object name and an object label set;
the field system area persists the MDD of the extended application provided by the tenant service provider, and comprises an application object attribution tenant ID, an ID of an object to which the field belongs, a field definition identification ID, a field name, a field storage location information definition, a data type supplementary association field, whether the field is necessary to select, whether the field is unique or not and an index relation mark;
from each tenant data storage perspective, it is a virtual tenant data area in a shared data area that is isolated by a unique id identified based on tenant information identification.
Further optionally, an initialized business module model instance is created in the business module model library, and the operation flow of generating metadata and dropping the metadata into the library is as follows:
performing metadata definition operation to generate corresponding metadata definition object data;
performing business data perspective operation, generating corresponding associated data, and generating a unique ID (identity) of a corresponding application object and an ID of a home tenant;
collecting the related data of the defined metadata module model, the unique ID of the application object and the ID of the home tenant;
and according to the service data generated by the currently created service module model instance, performing a hash slicing algorithm by applying the unique ID of the object and the ID of the attributive tenant, distributing different data persistence areas, and performing database dropping operation on the defined metadata module model related data.
The SaaS management charging station service platform based on metadata driving has the following beneficial effects compared with the prior art:
(1) According to the invention, the software research and development cost can be reduced, the period of constructing a charging station management system is shortened, the data analysis of charging stations under cross regions is realized, the scale effect of charging station operation management is realized, and the data island of each charging station can be opened;
(2) The invention is suitable for various charging stations, including public charging stations, special charging stations, community charging stations and the like, and can also be applied to management and data docking services of charging piles to provide services such as charging station positions, charging station states, reserved charging and payment for users.
Drawings
FIG. 1 is a diagram of a service platform rack according to a first embodiment of the present invention;
FIG. 2 is a flowchart of generating metadata for a business module model according to an embodiment of the present invention;
FIG. 3 is a flowchart of a business module model metadata database dropping in accordance with an embodiment of the present invention.
Detailed Description
In order to make the technical scheme, the technical problems to be solved and the technical effects of the invention more clear, the technical scheme of the invention is clearly and completely described below by combining specific embodiments.
Embodiment one:
with reference to fig. 1, 2 and 3, this embodiment proposes a metadata-driven SaaS-based service platform for managing charging stations, which includes an application layer, a platform service layer, a metadata layer and a data storage layer.
The application layer is provided with a service provider management module, a consumer user module and an order module of a service module model library, and is used for docking differentiated service application. Because of the differential effect on the business module models and the relevance between the business module models in different business scenes, the relevance between the business module models and business data perspective binding needs to be defined through metadata in a metadata layer, and the differential problem is solved by providing a standard flow.
The platform service layer is provided with a charging pile management module, a payment module and a data analysis module of the service module model library; as platform service function support of the application layer, the degree of coupling on the service is reduced, the platform service layer provides a unified application service interface for service module model call, and standardized module model building and service module model association maintenance are completed based on the metadata layer.
The metadata layer is used for carrying out metadata definition operation on the module models of the service module model library and carrying out service data perspective operation on the association relationship between the module models in the service module model library. Specifically, the metadata definition (english full name Meta Data definition, english abbreviation MDD) is used to manage the field definitions in SO (Standard Object) and TCO (Tenant Custom Object tenant custom Object); the metadata definition includes OS (Object Set Object) and FS (Fields Set field) as unified management areas of the platforms SO-MDD and TO-MDD, a metadata definition area (english holonomy Meta Data Define Area metadata definition area, english abbreviation MDDA). The metadata definition completes the standardized flow operation of the differentiated service requirement through standard object definition and custom object definition, describes an object model through a field set, and describes a service module model through the object set. The business data perspective involved (english full name Transaction Data Perspective, english abbreviation TDP) includes RDA (Relationship Data Area relational data Area), IA (Index Area) and OCA (Other Custom Area other custom Area), where: binding different basic service models through a relation data area by service data perspective, and constructing a complex service model, namely splitting the complex service model into a plurality of basic service models, wherein the association between the service models is the service data perspective; the service model accelerates the retrieval of the required service model related data through the index area; the custom area is used as an extension attribute of the relation data area and the index area and is used for custom setting of the association relation and the index.
When module model data is changed, in the metadata layer, firstly copying the changed module model through metadata definition, and then changing the copied module model; and after the module model is changed and validated, synchronizing the business data perspective and the data storage layer, and changing the use state of the original metadata definition module model after synchronization is completed.
The data storage layer is used for storing data generated by the application layer, the platform service layer and the metadata layer, defining a module model based on metadata and performing perspective association on service data, recording data state change of the model, performing data persistence on the data generated by different versions of the corresponding metadata module model, and positioning the data area by using unique IDs of all metadata module models according to the requirement that each metadata module model and the data generated by each metadata module model can be configured in the same data area. Specifically, the data storage layer includes SDA (Standard Data Area standard data area) and NSDA (Non-Standard Data Area Non-standard data area), and serves as a tenant physical business data persistence area for storing service platforms and instance data of tenant objects and fields. The data storage layer also includes OSA (Object System Area object system area) and FSA (Field System Area field system area), wherein: the object system area persists the MDD of the extended application model provided by the tenant service provider for the object system area, and comprises an application object unique ID, an application object attribution tenant ID, an object name and an object label set; the field system area persists the MDD of the extended application provided by the tenant service provider, and comprises an application object attribution tenant ID, an ID of an object to which the field belongs, a field definition identification ID, a field name, a field storage location information definition, a data type supplementary association field, whether the field is necessary, whether the field is unique or not and an index relation mark. From each tenant data storage perspective, it is a virtual tenant data area in a shared data area that is isolated by a unique id identified based on tenant information identification.
Referring to fig. 2 and 3, based on the service platform of the present embodiment, an initialized service module model instance is created in the service module model library, and the operation flow of generating metadata and dropping the metadata into the library is as follows:
(1) And performing metadata definition operation to generate corresponding metadata definition object data.
The data generated in the step is temporarily stored in the service platform buffer memory, and the unified database is needed to be dropped after the hash slicing algorithm is completed in the step (4). Each tenant may have a case of requiring definition of TCO (Tenant Custom Object ) in an actual service, where a difference in metadata definition caused by a difference in service between tenants is reflected. Each tenant service provider corresponds to a set of data models, the platform provides a standard application function metadata model, and each tenant service provider can be defined in a respective data model or can customize the metadata model. AM (Area Model), all Model data are implemented in the manner of mdd+ds+tdp. The AM may implement a number of customized services, such as order module model implementations, including implementations of a charging module model, a consumer user module model, an order details module model, and the like. Therefore, the problem that the standardization degree of the service management platform of the charging station in the industry is not high can be solved in a standardized way in the place of business differentiation.
(2) And performing business data perspective operation, generating corresponding association data, and generating a unique ID (identity) and a home tenant ID of the corresponding application object.
In this step, an MDD (Meta Data definition metadata definition) of an extended application model provided by a tenant server for it is defined by OSA (Object System Area object system area), including an application object unique ID (ObjectID), an application object home tenant ID (OrgID), an object name, an object tag set, and the like; MDDs (Meta Data definition metadata definitions) of extended applications provided by tenant service providers are defined through FSA (Field System Area field system area), and include application object attribution tenant IDs, field attribution object IDs, field definition identification IDs, field names, field storage location information definitions, data types, data type supplementary association fields, whether to choose, whether to be unique, index relation marks, other fields and the like. The data generated in the step is temporarily stored in the service platform buffer memory, and the unified data falling base is needed to be carried out after the hash slicing algorithm is completed in the step (4)
(3) And collecting the defined metadata module model related data, the unique ID of the application object and the home tenant ID.
(4) And according to the service data generated by the currently created service module model instance, performing a hash slicing algorithm by applying the unique ID of the object and the ID of the attributive tenant, distributing different data persistence areas, and performing database dropping operation on the defined metadata module model related data.
The hash slicing algorithm is carried out by applying the unique ID of the object and the ID of the attributive tenant, and different data persistence areas are distributed, so that the data are mainly distributed uniformly, less data are moved as much as possible when the database is expanded, new data are distributed uniformly after the expansion, and meanwhile, the problems that data analysis and data island are inconvenient for different charging stations under the same tenant service provider are solved.
And carrying out database falling operation on the related data of the defined metadata module model, wherein the database falling operation specifically comprises adding, deleting, modifying and checking. From each tenant data storage perspective, it is a virtual tenant data region in a shared data region that is isolated by a unique id (ObjectID, orgID, association between data regions) identified based on tenant information identification. By the mode, storage resources can be reasonably used, resource waste is avoided, and the aim of reducing research and development cost is achieved.
The supplementary ones are: the service platform supports large data volume in a multi-tenant scene, and the metadata-driven SaaS platform supports a huge multi-tenant database, so that not only is large data supported, but also the data stability, availability, data security and the like of each tenant are ensured. All Data, metadata and relation models of the service platform are physically partitioned through the attribution tenant ID, a database partitioning mechanism is adopted to realize the partitioning, and all Data and Meta Data can be subjected to slicing Hash through the attribution tenant ID; the data partition is a verified technology provided by the database system, and is used for physically dividing different data structures and mapping the different data structures into smaller manageable blocks, so that the partition can help to improve performance and expansibility, and particularly under the current charging station service provider environment, the expansibility is the most needed by a huge data production system. Only the relevant information of the ID of the corresponding home tenant is needed when the data is queried each time, and the relevant information is used as a query optimization filter, and only the access to the data partition containing the corresponding tenant is needed. All operations are recorded in metadata of the metadata area, structural change under a physical database is not involved, unavailability caused by adjustment of a data structure during change is avoided, and the overall performance influence on the platform multi-tenant application is reduced.
In summary, the metadata-driven SaaS-based service platform for managing charging stations solves the technical problem of how to realize standardized processes and data islands through the metadata-based SaaS-based service platform for managing charging stations.
The foregoing has outlined rather broadly the principles and embodiments of the present invention in order that the detailed description of the invention may be better understood. Based on the above-mentioned embodiments of the present invention, any improvements and modifications made by those skilled in the art without departing from the principles of the present invention should fall within the scope of the present invention.

Claims (8)

1. The utility model provides a SaaS management charging station service platform based on metadata drive which characterized in that it includes application layer, platform service layer, metadata layer and data storage layer, wherein:
the application layer is provided with a service provider management module, a consumer user module and an order module of a service module model library and is used for docking differentiated service application;
the platform service layer is provided with a charging pile management module, a payment module and a data analysis module of the service module model library, provides a unified application service interface and is used for service module model calling, and standardized module model building and service module model association maintenance are completed based on the metadata layer;
the metadata layer is used for carrying out metadata definition operation on the module models of the service module model library and carrying out service data perspective operation on the association relationship between the module models in the service module model library;
the data storage layer is used for storing data generated by the application layer, the platform service layer and the metadata layer, defining a module model based on metadata, recording the data state change of the module model based on the association relation between the business data perspective module models, and carrying out data persistence on the data generated under different versions of the corresponding metadata module model.
2. The SaaS claimed in claim 1, wherein when the module model data is changed, in the metadata layer, first, copying the changed module model by metadata definition, and then, changing the copied module model;
and after the module model is changed and validated, synchronizing the business data perspective and the data storage layer, and changing the use state of the original metadata definition module model after synchronization is completed.
3. The SaaS defined in claim 1, wherein the metadata definition is used for managing field definitions in standard objects, tenant custom objects, and metadata; the metadata definition comprises an object set and a field set, and is used as a unified management area and a metadata definition area of standard object metadata definition and tenant custom object metadata definition;
and the metadata definition completes the standardized flow operation of the differentiated service requirement through standard object definition and custom object definition, describes an object model through a field set, and describes a service module model through the object set.
4. The metadata-driven SaaS described in claim 3, wherein said business data perspective comprises a relational data area and an index area, wherein,
binding different basic service models through a relation data area by service data perspective, and constructing a complex service model, namely splitting the complex service model into a plurality of basic service models, wherein the association between the service models is the service data perspective;
the service model accelerates the retrieval of the required service model related data through the index area.
5. The metadata-driven SaaS-based charging station management service platform of claim 4, wherein the business data perspective further comprises a custom area, wherein the custom area is used as an extended attribute of the relational data area and the index area for custom setting of association relations and indexes.
6. The metadata-driven SaaS defined in claim 4, wherein the data storage layer comprises a standard data area and a non-standard data area, and the data storage layer is used as a tenant real business data persistence area for storing instance data of the service platform and tenant objects and fields.
7. The metadata-driven SaaS described in claim 6, wherein said data storage layer further comprises an object system area and a field system area, wherein,
the object system area persists the MDD of the extended application model provided by the tenant service provider for the object system area, and comprises an application object unique ID, an application object attribution tenant ID, an object name and an object label set;
the field system area persists the MDD of the extended application provided by the tenant service provider, and comprises an application object attribution tenant ID, an ID of an object to which the field belongs, a field definition identification ID, a field name, a field storage location information definition, a data type supplementary association field, whether the field is necessary to select, whether the field is unique or not and an index relation mark;
from each tenant data storage perspective, it is a virtual tenant data area in a shared data area that is isolated by a unique id identified based on tenant information identification.
8. The SaaS claimed in claim 7, wherein creating an initialized business module model instance in the business module model library, generating metadata and dropping the library comprises the following steps:
performing metadata definition operation to generate corresponding metadata definition object data;
performing business data perspective operation, generating corresponding associated data, and generating a unique ID (identity) of a corresponding application object and an ID of a home tenant;
collecting the related data of the defined metadata module model, the unique ID of the application object and the ID of the home tenant;
and according to the service data generated by the currently created service module model instance, performing a hash slicing algorithm by applying the unique ID of the object and the ID of the attributive tenant, distributing different data persistence areas, and performing database dropping operation on the defined metadata module model related data.
CN202310920831.XA 2023-07-26 2023-07-26 Metadata-driven SaaS-based service platform for managing charging station Pending CN117009317A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310920831.XA CN117009317A (en) 2023-07-26 2023-07-26 Metadata-driven SaaS-based service platform for managing charging station

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310920831.XA CN117009317A (en) 2023-07-26 2023-07-26 Metadata-driven SaaS-based service platform for managing charging station

Publications (1)

Publication Number Publication Date
CN117009317A true CN117009317A (en) 2023-11-07

Family

ID=88564820

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310920831.XA Pending CN117009317A (en) 2023-07-26 2023-07-26 Metadata-driven SaaS-based service platform for managing charging station

Country Status (1)

Country Link
CN (1) CN117009317A (en)

Similar Documents

Publication Publication Date Title
CN111061817B (en) Adaptive business construction system, method and computer readable medium
US8954480B2 (en) End-to-end interoperability and workflows from building architecture design to one or more simulations
CN102254029B (en) View-based data access system and method
US7523141B2 (en) Synchronization operations involving entity identifiers
CN101441563A (en) Automated solution for generating architectural design models for service-oriented architecture (SOA) information services
US6941309B2 (en) Object integrated management system
CN102254021A (en) Method for constructing database based on virtual machine management system
CN101916299A (en) Three-dimensional spatial data storage and management method based on file system
CN101853305A (en) Method for establishing comprehensive agricultural environmental information database
CN101763347A (en) GIS (Geographical Information System) interface platform as well as network GIS management system and management method
CN107977446A (en) A kind of memory grid data load method based on data partition
CN101360123A (en) Network system and management method thereof
CN110008272B (en) NoSQL database evaluation system for sensor data and construction method thereof
EP1091295B1 (en) Data management system using a plurality of data operation modules
CN102810115B (en) Method for implementing multi-layer distributed document management system
CN111666355B (en) Model construction method and device for field, data and scene three-layer model
CN105824905A (en) Method and device for establishing and operating electronic map aggregated layer
CN103617167A (en) Universal metadata/ relation mapping frame
CN106780157B (en) Ceph-based power grid multi-temporal model storage and management system and method
CN106951593B (en) Method and device for generating configuration file of protection measurement and control device
CN106354824A (en) Data management method and data management device
CN103107919A (en) Method and system for network resource modeling
CN103853612A (en) Method for reading data based on digital family content under distributed storage
CN116737113B (en) Metadata catalog management system and method for mass scientific data
CN117009317A (en) Metadata-driven SaaS-based service platform for managing charging station

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination