11 OceanConnect IoT Platform

OceanConnect IoT Platform
Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

Foreword
⚫ In recent years, IoT services are developing rapidly and face some
challenges. The IoT industry requires a reliable, secure platform that
supports device access decoupling and provides open capabilities.
⚫ The Huawei OceanConnect IoT Platform is leading in the industry and

provides customers with complete northbound and southbound APIs. It
pre-integrates common communication protocol plug-ins, helping
customers quickly launch services.
Page 2 Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
⚫ After completing this course, you will be able to understand:
 Requirements for the IoT platform
 Functional and logical architecture of the OceanConnect IoT Platform
 Common IoT communication protocols
 CIG functions and architecture
 IoT Agent access scenarios
 Features of the OceanConnect IoT Platform
Contents
1. Origin of the IoT Platform
2. Introduction to the Huawei OceanConnect IoT Platform

 Functional Architecture
 Logical Structure
 Device Access
 Services and Functions
 Features
Major Challenges Facing the IoT Industry
Noisy
standards Difficult
Long rollout network
period selection
⚫ Numerous devices, making it
difficult to integrate ⚫ Complex network connection
Long service rollout period Various network types:
Different device/sensor
⚫ ⚫
⚫
⚫ Fragmented applications, manufacturers and protocol 2G/3G/4G/NB-IoT

long development period, standards ⚫ Security, real-time, and QoS
and long TTM requirements
How to address these challenges in
the development of the IoT industry?
Requirements for the IoT Platform
⚫ A secure, reliable platform that supports device-application decoupling and
capability openness is required to develop IoT services.
Access decoupling
01
• Pre-integrated platform, and lightweight
development, quickly responding to market
requirements
• Leaving technical details to the IoT platform
Secure & reliable
02
• Virtualized system, and cloud
deployment
• Device access authentication and API
authentication
Open
capability
Open capability
03
• Open device access
• Open service application expansion
• Industry pre-integration and open Secure &
management reliable
Contents

 Logical Architecture
 Device Access
 Features
OceanConnect Function Architecture
Application Smart Smart

IoV Others
home metering
layer
Open application and Industry

Open APIs pre-integration
API management
Service
enablement layer Data management
Rule engine
Connectivity
and openness management
OceanConnect
Device Transmission Device management
Lightweight
connectivity protocol Device communication authentication
adaptation management
layer
IoT access
MBB access gateway FBB access gateway gateway
Access layer WLAN/WPAN Fixed access

Wireless WAN
FBB (Zigbee/Wi-Fi) (optical fibers)
(2G/3G/4G)
IoT Agent
Device layer Smart Smart Integrated with

hardware Sensor Smart Huawei LiteOS/
device
home app third-party OS
Application Layer
⚫ The IoT platform supports multiple types of open APIs and pre-integration of multiple
industry applications, including smart home, Internet of Vehicles (IoV), smart metering, and
third-party applications.
Application
Function Description
Scenario
Enables remote control of home appliances and devices for more secure
Smart home
and convenient living.
Provides vehicle occupants with traffic information, remote vehicle

IoV
diagnosis, and E-Call/B-Call services.
Embeds NB-IoT communication modules in water and electricity meters
and upgrades the meters based on existing wireless base stations to
Smart metering
provide intelligent remote metering that features low power
consumption, wide coverage, and low-cost deployment.
Third-party applications are developed by organizations or individuals
Third-party
rather than software editors. Typical third-party applications include
application
smart grid, intelligent building, and smart business.
Service Enablement Layer
⚫ The service enablement layer provides functions such as open API
gateways, data management, and rule engine.
Open application and Functioning as an independent module, the open API gateway
API management provides API searching, help, and lifecycle management.
Native device data is converted according to industry-defined data

Data management models that can be identified by the IoT platform. Based on the data,
and openness carriers can use rule engine and service orchestration modules to
define or improve their business practices.
The rule engine enables end users to use predefined rules to
Rule engine
customize rules on a user-friendly user interface (UI).
Device Connectivity Layer
⚫ The device connectivity layer provides unified access capability, asset and
device management, and SIM card connectivity management.
Carriers can manage all sensor nodes at the bottom layer, obtain
Device management
information about each node, and implement remote control.
Device communication management provides the following

functions:
Device communication ⚫ Device login
management ⚫ Data communication
⚫ Device-initiated subscription
⚫ User-initiated subscription
Transmission protocol
The supported protocols include HTTP, MQTT, and CoAP.
adaptation
Lightweight The DMP simplifies the authentication process and facilitates
authentication authentication and authorization for devices and applications.
Access Layer
⚫ The access layer supports both wireless and wired access. IoT Agents are
used to adapt to sensors from different manufacturers so that a large
number of devices can be connected.
Access Scenario Function Description
MBB (P-
Wireless wide area network (WWAN)
GW/GGSN)
FBB (BRAS) FBB and fiber to the x (FTTx)
• Wireless local area network (WLAN)

IoT (enterprise • Wireless personal area network (WPAN)
AR) • Fixed, including FTTx, hybrid fiber coaxial (HFC), and electrical power
cable
Device Layer
⚫ With the IoT Agent software, the IoT platform can quickly adapt to different OSs
and smart devices of different manufacturers. It has pre-integrated valuable NAs.
Peripheral/Device Description
Smart devices, such as smartphones, tablets, and computers, are used to remotely control
Smart device
intelligent hardware.
Intelligent hardware is connected to the Internet using various types of sensors, such as
Intelligent
RFID devices, photoacoustic or electromagnetic sensors, and laser scanners, to perform
hardware
data collection, convergence, and processing.
A sensor is a detection apparatus that responds to a stimulus and generates a signal that
Sensor can be measured or interpreted, to meet requirements for data transmission, processing,
storage, recording, and control.
Industry apps can be installed on devices, such as mobile phones, computers, and tablets,
Industry app
to control intelligent hardware in the house.
IoT Agents use various communication protocols to provide network access for devices.
The Agents isolate upper-layer applications from lower-layer OSs and hardware.
IoT Agent ⚫ The Agents provide the bottom layer with SDKs, which can be adapted to different OSs
and hardware.
⚫ The Agents provide a variety of APIs independent of underlying resources.
Contents

 Device Access
 Features
Logical Architecture
Application server (NA)
LoadBalancer
API server
SP portal Rule engine IoDM

IoCM IoBS
browser LoadBalancer
Service Bus (HA)

Operation MongoDB
portal browser
OM portal Rabbit
Plug-in CIG Plug-in
browser MQ
LoadBalancer/HAProxy
HTTP MQTT CoAP

IoT device
Contents

 Device Access
 Features
Common IoT Protocols - HTTP
⚫ The HyperText Transfer Protocol (HTTP) is an application-layer protocol used for
communications between web servers and browsers. It makes the browser more efficient
and reduces network transmission. It ensures that a computer transmits hypertext
documents properly and quickly and determines priorities of document contents to be
transmitted and displayed, for example, texts are displayed prior to images.
Client Server
SYN=1 Seq=X
SYN=1 ACK=X+1 Seq=Y
ACK=Y+1 Seq=Z
Request
Response
Common IoT Protocols - MQTT
⚫ Message Queuing Telemetry Transport (MQTT) is an instant messaging
protocol developed by IBM. MQTT adopts the subscription/publish mode.
The client subscribes to desired information from the server, and the server
pushes the information to the client.
MQTT client MQTT server
CONNECT
CONNACK
SUBSCRIBE
SUBACK (subscription
completed) After the client subscribes to a topic
from the server, the server sends a
PUBLISH PUBLISH message to the client.
Common IoT Protocols - CoAP
⚫ Constrained Application Protocol (CoAP) is designed for resource-limited devices (such as
sensor nodes) and networks (such as NB-IoT and LoRa). CoAP is developed from HTTP.
CoAP adopts the request/response mode, in which the client initiates a request and the
server responds. CoAP optimizes the packet length and offers reliable communication to
address issues that may occur on HTTP in restricted conditions.
Client Server
Header: GET (T=CON,Code=0.01,MID=0x7d34)

GET Uri-Path:"temperature"
Header: 2.05 Content

2.05 (T=ACK,Code=0.01,MID=0x7d34) Payload:"22.3C"
CIG Framework (1)
IoT platform
Deployment Model
⚫ Deployed together with the IoT platform
⚫ Independently deployed
IoT platform API
Device Connection IoT cloud IoT DMS Function
abstract protocol service
Custom Custom protocol adapter JT/T 808 adapter ⚫ Open OSGi architecture, plug-and-play
protocol
adapter
JT/T 808 handler ⚫ Access by devices using different protocols
Custom handler
Custom JT/T 808 JT/T 808 ⚫ Quick ecosystem construction
handler Custom Custom encoder decoder
encoder decoder ⚫ Dynamic plug-in loading
Custom Transport ⚫ New device access completed in at most 1
protocol
stack CoAP AMQP MQTT HTTP TCP/UDP day
OSGi framework
Infrastructure
Protocol extension framework
Third-party extension
CIG Framework (2)
DaaS IoDM IoCM
Event bus (Kafka)
Service bus (virtual bus)
Built-in CIG
MQTT plug-in HTTP plug-in JT/T 808 plug-in CoAP plug-in
Firewall
CoAP JT/T 808 HiLink MQTT MQTT
IoT Agent
Water meter T-Box Hi-Link device Edge CIG
Gateway
Introduction to IoT Agent
Converts different communication protocols used by
Description hardware and software vendors into a unified standard
protocol, and functions as middleware between networks
that use different connection modes.
Home gateway Agent, Industrial gateway Agent,

Category
AgentIPC, AgentLite, and AgentTiny Agents
⚫ Shields differences in communication protocols

used by different manufacturers.
Function ⚫ Supports access of 200+ devices using
protocols such as Z-Wave and Zigbee.
IoT Agent Architecture
Easy integration
⚫ Supports devices such as chips, gateways,
API and STBs.
⚫ Supports Linux, Windows, iOS, and Android.
IoT platform ⚫ Quick integration

⚫ End users can install the software by
themselves.
HTTP MQTT CoAP High service scalability

Security ⚫ Service priority mechanism
Data collection and Device
certificatio
Agent conversion management
n
⚫ MQTT permanent connection
IoT middleware and unified framework
(supporting OSGi) ⚫ TCP optimization
OS abstraction layer
Adaptation to multiple
Media OS/Linux communication protocols
⚫ Shields differences in communication
protocols.
⚫ Supports device access using multiple
protocols.
IoT Agent Access Scenario
IoT platform
Home gateway Industrial

Agent gateway Agent AgentLite
Home gateway AgentIPC

Industry gateway AgentTiny
Thin gateway/bridge
NB-IoT chip
Home sensor Industrial sensor
Sensor OBD Camera
AgentRich AgentLite AgentTiny
Contents

 Device Access
 Features
Services and Functions
Device Management
Using the SP portal, users can

deliver configuration
management commands to the
DMP through the RESTful
interface and HTTPS. The DMP
delivers the commands to
gateways by using CoAP/HTTPS
to complete device configuration
management.
Device Communication Management
Device login Data communication

Establishes and maintains MQTT
Enables devices/gateways to
connections between the IoT
log in to the IoT platform.
platform and devices/gateways.
User-initiated subscription Device-initiated subscription

Enables SP users or end users to initiate Enables devices/gateways to
device data subscription to the IoT initiate user data subscription to
platform to check device data. the IoT platform to check user
data.
Device Access Authentication
Access authentication for devices
After a device is powered on, the device
Access authentication for sensors sends an access request carrying the
Access device ID and password to the IoT
When a sensor connects to the IoT authentication
for device platform. The IoT platform authenticates
platform through a gateway, the
the device. If the authentication is
gateway sends a message carrying the
successful, the IoT platform returns a
valid session information allocated by
200 message carrying the valid session
the IoT platform. The IoT platform
Ocean information.
verifies the session information. If the Connect Authentication for data reporting
session information is valid, the IoT
When a sensor reports data, the gateway
platform adds the new sensor to the
Access
Authenticati
carries the valid session information
gateway. In this way, the new sensor authentication
on for data
for sensors allocated by the IoT platform. The IoT
can report data to the IoT platform reporting
platform verifies the session information.
through the gateway.
If the session information is valid, the IoT
platform records the data and reports
the data to end users.
Rule Engine
Trigger Action
Time-based trigger Action 1

Example: turning off the Instructs the sensor to turn off
corridor light at 08:00 the corridor light at 08:00.
Data-based trigger Action 2

Example: turning on the air Instructs the sensor to turn on the
conditioner when the air conditioner when the
temperature is higher than 25°C temperature is higher than 25°C.
Event-based trigger
Example: sending a Action 3
notification to a specific Instructs the sensor to send a
mobile phone if an alarm is notification to the specific mobile
generated phone when an alarm is generated.
API Exposure Management
NA management
An NA accesses the IoT platform to obtain authentication
information. Using the authentication information, the NA then calls
other APIs.
Device resource management
An NA applies for a device from the IoT platform to obtain the
device ID and verification code. After the device securely accesses
the IoT platform, the device establishes a relationship with the NA.
Device management
The device updates configuration information and reports the
information to the IoT platform.
Relay proxy
An NA sends commands to a gateway to control sensors in real
time.
Rule
An NA defines rules (conditions) and actions based on service
requirements. Users are reminded by email or SMS in real time when
the device status meets the specified rules.
Subscription and notification
An NA subscribes to the device change notification from the IoT
platform. When the device changes, the IoT platform sends a
notification message to the NA. (The NA starts initialization
subscription.) The NA distributes the message to the corresponding
service module according to the notification type.
Data Management
Rule engine
Sensor 1
Service
orchestration
IoT NA
platform
Data
management
Sensor 2
Database
Format conversion for reported data Format conversion for commands

1. module, and NA for service triggering. Sensors 1 and 2 report 1. The rule engine, service orchestration module, or NA sends
data to the data management module of the AEP through the a command to the data management module of the AEP.
DMP. 2. The data management module queries the database for
2. Based on the sensor type, manufacturer, and model, the data information about the manufacturer, model, and type of the
management module converts the reported data to the target sensor.
universal data format and stores the data in the database. 3. The data management module converts the command to
3. The data management module reports the data after corresponding commands and delivers the commands to
conversion to the rule engine, service orchestration sensors through the DMP.
Note: Sensors 1 and 2 are of the same type, but they are provided by different
manufacturers.
Multi-Tenancy Management
Physical isolation Virtual isolation Logical isolation
Application 1 Application 2 Application n

Tenant 1 Tenant 2 Tenant n Tenant 1 Tenant 2 Tenant n
Tenant 1
Application Application 1 Application 2 Application n IoT platform
Application 2 Application n
1
Tenant 2
FusionSphere Device 1 Device 2 Device n
IoT IoT IoT IoT
IoT platform IoT platform
platform platform platform platform Tenant n User
instance 1 instance 2
instance n instance 1 instance 2 instance n
Authentication
Application
User group
Resource
COTS (HP, Dell, Huawei, IBM…) COTS (HP, Dell, Huawei, IBM…) Device Asset
Device 1 Device 2 Device n Device 1 Device 2 Device n Service provision
⚫ Each tenant has an independent set ⚫ Each tenant has an independent ⚫ Each tenant owns a dedicated account to
of hardware. set of IoT platform, which is access applications and devices and
⚫ All resources are physically isolated deployed on the cloud or VM. perform authentication.
from each other. ⚫ All resources are virtually isolated ⚫ All tenants share hardware resources.
from each other.
Portal Management
OM portal SP portal
SP
⚫ Used by carriers' configuration portal ⚫ Used by SP developers to perform
and maintenance personnel to operations, including management
configure network element of applications, assets, asset-
(NE) interworking parameters, related reports, and software as
perform maintenance well as rule engine.
operations (log collection,
OceanConnect
message tracing, and alarm),
Device/
back up service data (GaussDB Controller/
Connectivity
and MongoDB data), and
management
manage licenses. Operation portal
⚫ Used by carriers' installation ⚫ Used by carriers' operation
and maintenance personnel to personnel to manage all SPs
Operation and query reports of all
install, check, and upgrade the OM portal
portal
IoT platform, back up assets connected to the IoT
configuration data, and platform.
manage processes.
Contents

 Device Access
 Features
Access Agnostic
4G
Fixed
NB-IoT broadband
Ocean
LTE CDMA
Connect
xDSL
Bluetooth
FTTx
WLAN
Accessible by any modes Accessible from any devices
Reliable
System reliability
Network reliability
The IoT platform is installed and
The 1+1 mutual backup and
deployed based on the cloud
pool modes are supported.
platform. The system reliability
includes system cluster and VM
reliability.
Service reliability Module reliability

The service reliability policy The rule engine module, API
includes flow control, data server module, and database
encryption, and sensitive module support reliability.
information shielding.
Secure
Application
Service: ID authentication, service authentication,
layer group/policy, privacy protection, integrity,
confidentiality, key security, non-repudiation, anti-
replay, availability, and AES encryption
Service
enablement layer Platform: networking security, confidentiality,
OceanConnect privacy, integrity, authentication, group/policy, key
security, availability, OAM, remote configuration
Device
connectivity layer
security, software download authorization, and
administrator grading
Access: confidentiality, data source authentication,

Access layer device authentication, integrity, availability, and
timeliness
Device layer
Sensor: physical protection, access control,
authentication, non-repudiation, confidentiality
(grading), integrity, privacy, and availability
Scalable
01 02
Flexible platform deployment Aggregated vertical capabilities

Freedom to choose the server Deployment for one industry
or cloud
or multiple shared industries
03 04
Exposure & compatibility Modularized services/Flexible

No restrictions on combination
devices from different Flexibility to deploy a single or multiple
manufacturers services
Open
Open APIs Diverse IoT Agents

Third-party NAs are now Adaptable to different OSs
integrated faster and more and hardware.
efficiently.
Open device management Pre-integrated with

Service providers use the WEB- high-value NAs
Service interface to access and Tailored for smart home, IoV,
and smart metering
remotely operate devices.
applications.
Quiz
1. In the functional architecture, in which two layers does the OceanConnect IoT
Platform provide functions?
2. What are the common IoT communication protocols?
3. What are the features of the OceanConnect IoT Platform?
Summary
⚫ Functional architecture and logical architecture of the OceanConnect IoT
Platform
⚫ Common IoT communication protocols
⚫ CIG functions and architecture
⚫ IoT Agent architecture and access scenarios
⚫ OceanConnect IoT Platform features
Thank You
www.huawei.com

11 OceanConnect IoT Platform

Uploaded by

Copyright:

Available Formats

11 OceanConnect IoT Platform

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

11 OceanConnect IoT Platform

Uploaded by

Copyright:

Available Formats

OceanConnect IoT Platform

Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

⚫ The Huawei OceanConnect IoT Platform is leading in the industry and

 Functional and logical architecture of the OceanConnect IoT Platform

 Common IoT communication protocols

 CIG functions and architecture

 IoT Agent access scenarios

 Features of the OceanConnect IoT Platform

2. Introduction to the Huawei OceanConnect IoT Platform

 Services and Functions

⚫ Fragmented applications, manufacturers and protocol 2G/3G/4G/NB-IoT

Secure & reliable

2. Introduction to the Huawei OceanConnect IoT Platform

 Services and Functions

Application Smart Smart

Open application and Industry

Access layer WLAN/WPAN Fixed access

Device layer Smart Smart Integrated with

Provides vehicle occupants with traffic information, remote vehicle

Native device data is converted according to industry-defined data

Device communication management provides the following

management ⚫ Data communication

FBB (BRAS) FBB and fiber to the x (FTTx)

• Wireless local area network (WLAN)

2. Introduction to the Huawei OceanConnect IoT Platform

 Services and Functions

SP portal Rule engine IoDM

Service Bus (HA)

HTTP MQTT CoAP

2. Introduction to the Huawei OceanConnect IoT Platform

 Services and Functions

SYN=1 ACK=X+1 Seq=Y

MQTT client MQTT server

Header: GET (T=CON,Code=0.01,MID=0x7d34)

Header: 2.05 Content

DaaS IoDM IoCM

Event bus (Kafka)

Service bus (virtual bus)

Home gateway Agent, Industrial gateway Agent,

⚫ Shields differences in communication protocols

IoT platform ⚫ Quick integration

HTTP MQTT CoAP High service scalability

Home gateway Industrial

Home gateway AgentIPC

2. Introduction to the Huawei OceanConnect IoT Platform

 Services and Functions

Using the SP portal, users can

Device login Data communication

User-initiated subscription Device-initiated subscription

Time-based trigger Action 1

Data-based trigger Action 2

Format conversion for reported data Format conversion for commands

Application 1 Application 2 Application n

Device 1 Device 2 Device n Device 1 Device 2 Device n Service provision

2. Introduction to the Huawei OceanConnect IoT Platform

 Services and Functions

Accessible by any modes Accessible from any devices

Service reliability Module reliability

Access: confidentiality, data source authentication,

Flexible platform deployment Aggregated vertical capabilities