Developers

Architecture of smart cities

Smart city services like smart water management, smart energy, smart mobility, smart buildings etc..are based on a centralized system. A web of sensors that are spread across the city feed data to this centralized system or central control center by sensing activities in the physical environment. At the control center the data is processed and stored as meaningful information. This information is shared across various departments of the city government for better coordination and making data-driven decisions.

This sounds pretty easy to implement, doesn’t it?

But practically it is not easy. Why?

Integrating various devices with different technologies with the existing communication infrastructure is one of the biggest challenges in developing a sustainable and efficient smart city.

The Information and Communication Technology (ICT) architecture of a smart city has 4 layers:

  • Sensing
  • Communication
  • Data
  • Service

Sensing layer

The sensing layer has a varied set of IoT nodes that are spread across an urban area. These nodes collect data about various activities in the physical environment. An IoT node is a package that comprises sensors, microchips, power supply, and network elements. IoT nodes are categorized into 2 different categories based on their operating conditions:

  • Constrained node: These nodes operate in a low-power environment. They have low processing power and a low data-transfer rate.
  • Unconstrained node: These nodes have no operational constraints in terms of power consumption, processing rate, and data-transfer rate.

A node can act as both constrained or unconstrained depending on the operational environment and conditions. For example, a proximity sensor node in a small office parking complex may be constrained, while the same proximity sensor node in big parking complexes can be unconstrained.

IoT nodes with the help of sensors, sense the activities in the environment around them and send data to data centers in the data layer. In this data-exchange process, unconstrained nodes send data in an eXtensible Markup Language (XML) format. However, this format is not compatible with constrained nodes, because the overhead in describing the transferred data makes it too long to parse. Additionally, the textual nature of an XML representation makes parsing difficult for CPU-limited nodes.

As a solution to this problem, the World Wide Web Consortium (W3C) proposed the Efficient XML Interchange (EXI) format. This allows constrained nodes to natively support and generate messages by using an open-data format that is compatible with XML.

EXI has 2 types of encoding methods:

  • Schema less encoding: Data is encoded directly from the XML data and then decoded by any EXI processor without any prior knowledge about the data.
  • Schema-informed encoding: Before the encoding or decoding process begins the XML schema is shared between 2 EXI processors. This shared schema allows EXI processor to assign numeric identifiers to the XML tags and build EXI grammar upon such coding.

The schema-informed EXI processor can be seamlessly integrated with any constrained IoT node. This enables the constrained IoT node to not just read an EXI format but also evolve into a multipurpose IoT node.

Communication layer

Every smart city system has a billion IoT nodes that are spread across the city. These IoT nodes should be addressed individually. This is made possible with IPv6, which provides a 128-bit address field.

However, the overheads that are introduced by IPv6 (in addressing the IoT nodes) are not compatible with constrained devices, and therefore 6LoWPAN (Low Power personal Area Network) was adopted.

For seamless translation from IPv6 to 6LoWPAN and vice versa, a bridge router is attached to the 6LoWPAN network. An IPv6 packet that is intended for a node in 6LoWPAN gets converted into 6LoWPAN with the help of a bridge router and vice versa.

As a large number of IoT nodes are spread across a city, the setup requires a robust communication technology that covers a wide geographical area and can handle a huge amount of data traffic. But a single communication technology is not compatible with both constrained and unconstrained nodes. For the unconstrained IoT nodes we use the traditional LAN, MAN, and WAN communication technologies such as WiFi, optic fiber, ethernet, broadband powerline communication, and mobile communication technologies like UMTS and LTE. These communication technologies have a higher reliability, high transfer rate, and low latency.

On the other hand, the constrained nodes have transfer rates of less than 1 mbit/sec. The more reliable communication technologies for constrained nodes are IEEE 802.11 Low Power, Bluetooth Low Energy, IEEE 802.15.4, Bluetooth, PLC, RFID, and NFC.

Data layer

This is the intelligence layer of smart-city architecture. A mega smart city can work effectively and efficiently only if the data about the city is organized systematically. To do this a database of the following information is maintained separately:

  • All the IoT nodes
  • All the departments that control the nodes (for example, nodes related to water management)
  • Corresponding data for each department

At the root of this layer are data servers that process data by applying different statistical models. These models include the following:

  • Predictive models: This model is a type of data-mining technology. It works by analyzing both past and current data and helps in predicting the future.
  • Descriptive models: This model describes the relationship between real-world events and the factors that are responsible for them.
  • Decision models: This model predicts the outcome of a decision by establishing the relationship between elements of the decision and predicted results.

These predictions help the city government to take proactive and data-driven decisions.

This layer also includes Enterprise Resource Planning (ERP) systems that control the flow of data across different organizations under the city government.

Service layer

This layer acts as a cross-department operation center. Various city boards such as, water-supply board, power-supply board, pollution-control board, transport department etc.. share information by using web portals/mobile applications that are built on this layer. This layer will not just serve government departments by sharing information but also the general public that has access to a subset of all the data. By using this data the public can build services to enhance the operations of the city.

Many cities that are trying to overcome everyday problems and sustain themselves have found perfect solutions by embracing technology. Smart city projects in Barcelona, Tel Aviv, Amsterdam, Seoul, and Stockholm are some success stories.

Vasudhendra Badami

Vasudhendra Badami is a category head (IoT) at HackerEarth. A writer by day and a reader by night. Covers topics like Internet of Things, electronics and analytics. You can find Vasudhendra on Twitter (@BadamiVasu)

Share
Published by
Vasudhendra Badami

Recent Posts

Recruitment Workflow Process: A Complete Guide

Finding the perfect fit for your team can feel like searching for a unicorn. But…

9 hours ago

Conquer Your Hiring Challenges: Top Recruiting Software Picks for Small Businesses in 2024

In today's competitive job market, attracting and keeping top talent is crucial for small businesses…

4 days ago

How To Become A Technical Recruiter: Your Guide to Launching a Rewarding Career

The tech industry thrives on innovation, and at the heart of that innovation lies a…

4 days ago

How To Use Live Coding Interviews in Tech Recruiting?

In the fast-paced world of tech recruiting, finding the perfect candidate can feel like searching…

4 days ago

Building a Strong Talent Pipeline: Strategies for Effective Sourcing and Engagement

Struggling to find the perfect candidate when a position opens up? Build a strong talent…

4 days ago

How to Build a High-Performance Team

A high-performance team thrives by fostering trust, encouraging open communication, and setting clear goals for…

2 weeks ago