Metadata Model for Smart City IoE Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current infrastructure management systems are silo-based and lack integration across systems, requiring custom solutions for trained operators, and fail to adapt to the evolving needs of smart cities, which are complex and require intuitive user interfaces and real-time responses.

Innovation Solution

A metadata model of a city's Internet of Everything (IoE) is implemented, enabling user journeys and system intelligence through automated response logic, allowing system integrators to build a framework that integrates devices, systems, and people, and dynamically modifies metadata models based on changing city needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a metadata model of a city's Internet of Everything (IoE) is implemented to integrate devices, systems, and people, then system integration and operational intelligence are improved, but device complexity and implementation difficulty increase

Engineering Contradiction:
Improvesystem integration capabilityVSAvoidmetadata model complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the complex IoE integration task into manageable metadata components including device metadata, system metadata, and relationship metadata. Each metadata type handles specific aspects of integration, allowing the overall system to manage complexity through modular organization of information structures.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The metadata model acts as an intermediary layer between diverse IoE devices, systems, and users. It provides a standardized interface that translates between different device protocols and system requirements, enabling integration without direct complex point-to-point connections between all components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If automated response logic and user journeys are implemented, then response time and user engagement are improved, but system complexity and development effort increase

Engineering Contradiction:
Improveresponse timeVSAvoidautomation system complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system implements pre-configured response logic and automated user journeys that are established in advance through the metadata model. When events occur, the system executes pre-defined actions and notification sequences without requiring real-time complex decision-making, thereby reducing response time while managing complexity through prior preparation.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If custom solutions are created for trained operators, then operational precision is improved, but ease of operation and accessibility for general users deteriorate

Engineering Contradiction:
Improveoperational precisionVSAvoiduser interface accessibility
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The metadata-driven system creates universal interfaces that serve multiple user types including trained operators and general citizens. The same metadata model supports both detailed operational views for experts and simplified citizen-facing views, allowing one system to fulfill multiple functional requirements without requiring separate custom solutions for each user group.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP4148589A1Integration platform to enable operational intelligence and user journeys for smart cities and the internet of things
Publication Date: 2023.03.15 EUTECH CYBERNETICS PTE
  • EP4148589A1 patent drawingFigure 1
  • EP4148589A1 patent drawingFigure 2
  • EP4148589A1 patent drawingFigure 3

AI summary

An apparatus for management of infrastructures of a community is described. The apparatus includes a number of infrastructure systems, one or more mobile phone devices, and end-user enterprise software applications. A computer-readable database includes a user-defined metadata model database comprising predefined metadata node template data structures defining metadata structures for each of the infrastructure systems, mobile phone devices, and software applications. The apparatus communicates with and collect metadata from the infrastructure systems, mobile phone devices, and software applications; to populate metadata node template data structures using said metadata; to generate and update a dynamic metadata model database and pre-defined operation sequences; to transform said pre-defined operation sequences into commands in a format specific to respective ones of the infrastructure systems, mobile phone devices, and software applications; and to send said commands to carry out an action to one or more of the infrastructure systems, mobile phone devices, and software applications.