Interdigital's Chordant IoT Platform Overview v3.0

Chordant™ IoT Platform – Overview
Copyright 2017 InterDigital, Inc. All Rights Reserved

Contents
• Chordant™ IoT Platform – Introduction

• IoT Deployment Architecture with Chordant™
• Chordant™ Solution Architecture
• Supported Features
• Deployments
• Recognitions from across the Globe
• Scalable Deployment Architecture
• Performance Benchmarks
Copyright 2017 InterDigital, Inc. All Rights Reserved 2

Chordant™ IoT Platform - Introduction
Interdigital’s Chordant™ solution is a Cloud ready, standards-

based IoT Platform with a scalable architecture, comprehensive
feature support to enable deployment as an end to end IoT
solution for Smart City, Industrial IoT and other IoT verticals with
an Application Development Kit.

Chordant™ Platform – Services Based Architecture
Operator Console for Application

Monitoring &
Configuration
Development Kits
oneM2M Standards based
Grafana based KPI Chordant™ CSE
monitoring interface, C based ADK
ELK, Sensu Application and Security Service
Service Layer Java based ADK
Mgmt Registration
Device / Application Data Mgmt &
Resource Tree Viewer Repository Subscription and
Notification
NSSE/Service
Exposure+ Service
Management Console
Triggering Service Charging
for device
management Others.. and Accounting
Others.. Mongo Database
Configuration Utility Horizontally scalable, service based architecture - ready to be Scalable Non SQL database for
deployed on enterprise cloud platform / Gateway devices to enable data persistence
end to end IoT solution(s)
4
End to End IoT Deployment Architecture with Chordant™
 IoT server deployable on Cloud /

COTS x86 platform(s)
 Aggregated connectivity over
Chordant™ Gateway for
constrained device(s)
 Standards based (Mca/Mcc)
Interface support alongside
Interworking proxy support
towards non oneM2M platforms,
applications and devices
 Support for Cellular IoT with
direct interface (with out a
Gateway) towards LTE capable
devices

Supported IoT features
Functionality Status
oneM2M standards - Release1 Certification and Compliance 
oneM2M standards – Release2 Compliance* 
IoT Device/Application Registration and Deregistration 
Subscribe and Notify events between Devices and Applications 
Persistently store custom device/application data with heterogeneous data types and sizes 
Authentication and Authorization of Devices and Applications 
Configurable Access Control for all operations on applications/devices and their corresponding data 
Discover registered applications/devices and their corresponding data 
*Detailed Rel2 Feature Support Matrix captured in a subsequent slide

Supported IoT features
Functionality Status
oneM2M Compliant Interfaces (Mca, Mcc) with support for HTTP(S), CoAP(S) and MQTT(S) Protocols 
Group based handling of application and device operations to increase efficiency 
LWM2M standard based Device Management server and client support 
Horizontally scalable architecture to enable dynamic scaling of CSE Instances 
Quick deployment using Docker Containers 
Generate Charging Data Records for Monitoring, Billing and Auditing 
Advanced Message Handling & Control (Store and Forward, Scheduling) 

Supported IoT features – contd.
Functionality Support Status
Integration with 3GPP LTE network for Cellular IoT support via T8 interface, NIDD support,
Device triggering and Monitoring Event(s) 
Advanced/Other T8 interface procedures (Network status monitoring, background data
Under Development
transfer, communication pattern assistance etc..)
Support for oneM2M Location based service functionality Roadmap
Advanced Message Handling & Control (Prioritization, policy based network selection) Roadmap
Role-based & Dynamic Authorization Roadmap
Support for interoperability with non-oneM2M (proprietary) communication technologies

Under Development
(Framework to support Zwave, Bluetooth complete)

Platform Management Capabilities
Provisioning services to enable deployment and management of Chordant platform services on a IaaS cloud 
Configuration Management and Container Management service to configure and deploy Chordant Platform
services (wot.io daemon)

Performance KPI measurement and visualization using Graphite / Grafana, Tessera, 
ELK – Elastic Search, Logstash, Kibana for platform log management to enable deployment support 
Platform monitoring services, Fault Management (using Sensu, Uchiwa and PagerDuty) 
LDAP based platform Authentication and Authorization 
Protocol Adaptors (HTTP, WebSocket, MQTT, AMQP, CoAP over UDP, TCP, UDP, Stomp, JDBC and DDS ) for
communication with IoT device(s), application(s) and internal services

Service Adaptors framework for translation and routing into and out of the Chordant Environment 
Web based Management Console for device management 
Resource tree viewer to visualize resources corresponding to application(s) and device(s) registered with the 
platform

Application Development Kit
ADK with Java APIs to develop HTTP(S), CoAP(S) or MQTT(S) applications 
ADK with C APIs to develop HTTP(S), CoAP(S) or MQTT(S) applications 

Chordant™ - oneM2M Certified Platform
 ChordantTM was the first product to be certified

by oneM2M’s global certification body
 The Chordant platform has been tested by TTA,

and has passed, both the existing oneM2M
certification test suite and the latest version of
the TTCN-3 oneM2M test suite

Recognitions from across the Globe

Chordant™ Deployment – OneTransport, UK
• Interdigital’s Chordant™ platform deployed as an end to end Solution for the oneTransport
IoT use case
• oneTRANSPORT™ Data Marketplace offers an open data sharing service for the UK
Intelligent Transport sector
• oneTransport - An open, standardized platform where multi-modal travel data is published
by data owners with the below objectives:
• Enable local authorities to consolidate and share real time traffic data
• Enable independent data analytics and thereby allow application developers to build
value added services and end user applications
• Successfully deployed for Buckinghamshire County, Oxford shire County and Hertfordshire
Counties.
• The solution has enabled more than 300 different datasets across eleven public and private
partners, recognized with 9 global awards.


oneTRANSPORT™ data marketplace

technology enables:
• The distribution of real-time
transport data from any system,
device or organisation
• UK-cloud-based storage for your
real-time and historical data (not just
a catalogue or front-end to another
system)
• The extended platform capabilites
that enable end-to-end Internet-of-
Things (IoT) solutions
• Monetisation of intrinsically-valuable
real-time data
oneTRANSPORT™ data marketplace is
powered by the Chordant™ Platform

Data Publishers
oneTransport – Data publishers are public or private sector
organizations and individuals looking to share data
How it Works within their organizations or with others. Such data may
be offered “free” or assigned a “fee” of data publisher’s
choosing. Data may be in its raw or refined forms.
Data Enhancers
Data enhancers are service providers that take existing
data in the oneTRANSPORT data marketplace and
enhance it to provide more value. For example, they
may clean it up to remove anomalies, combine it with
other data, or apply specific data schemas or analytics.
Data Consumers
Data consumers are public or private sector
oneTRANSPORT data marketplace is a organizations, individuals, universities, and other
growing ecosystem of connected educational and not-for-profit organizations that can
organizations from different sectors, public purchase or download for free the available data. Those
and private, that are sharing data to enable organizations and individuals may consume data in
Smart City collaborative services. order to deliver solutions and services.

oneTRANSPORT Consortium partners
The oneTRANSPORT initiative
was conceived in 2013 in
response to a UK government
call for innovative new
solutions to tackle the
challenges present in the UK
transport sector that are
preventing the advent of new
Intelligent Mobility services.
Field trials began in October
2015, supported by InnovateUK
and led by a consortium
comprising Local Authorities,
transport industry experts,
Internet of Things (IoT)
technology providers, and
thought leaders in big data and
analytics.
Chordant – Scalable Deployment Architecture
App/Devices  Horizontally scalable (HSC) deployment
(Node-1)
to aid increase in throughput
NGinx
(transactions per second) with addition
of CSE and Mongo slices.
(Node-2) (Node-3) (Node-4)
CSE CSE CSE
MongoS MongoS MongoS

(Node-11)
 The HSC deployment allows the operator
Mongo Mongo Mongo
Arbiter
MongoC
to scale CSE instances and Mongo
Arbiter Arbiter
(Node-12) Components based on the load (number
MongoC of devices transacting with the Platform)
(Node-14) (Node-5) (Node-6) (Node-7)
(Node-13)
Monitoring Services
Sensu MongoD MongoD MongoD

MongoC  HSC deployment validated on the
Graphite
(Node-9) (Node-10)
Microsoft Azure Platform for scaling of
(Node-8)
ELK
MongoD MongoD MongoD
CSE instances up to 10x
 Redundancy and High Availability using

Data Data Data Data Data Data
MongoDb Data Replication
Journal Journal Journal Journal Journal Journal
SSD (File System - XFS) *3x deployment architecture depicted as a reference

Performance Benchmarking Results
Chordant - Performance Bench Marks

Transactions per second Throughput (Transactions/Sec)
12000 11250
10000 7938
8000
6000 4536 5670
4000 2268 3402
2000 1134
0
Throughput w.r.t Device / Application content create operation scales linearly with addition of CSE and Database
slices, validation up to 10x so far, Architecture supports scaling beyond which shall be eventually validated.

Hardware requirements – HA deployment up to 10x
Num Num Num
Service Compute Type Node Configuration Nodes Nodes
Nodes 1x 5x 10x
CSE, Database Router, CPU: 4 Cores, Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz
Compute Type-1 14 GB RAM 1 5 10
Database Arbiter 20 GB SSD HDD
CPU: 8 Cores, Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

Database Shards Compute Type-2
24 GB RAM 2* 10* 20*
128 GB(Data), SSD HDD
20 GB (Journal), SSD HDD
Database Configuration CPU: 4 Cores, Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

Server
Compute Type-3 14 GB RAM 3 3 3
20 GB SSD HDD

Nginx Compute Type-4 14 GB RAM 1 1 1
20 GB SSD HDD

Monitoring Services Compute Type-5 14 GB RAM 1 1 1
120 GB SSD HDD
Minimum deployable Unit @

1X with HA support
* Number of nodes hosting Database

Copyright doubled
2017 InterDigital, Inc. All for
RightsHigh Availability [Data Replication]
Reserved 20
Hardware requirements –
HA deployment for 100k transaction per second support
Service Compute Type Node Configuration Num Nodes
CSE, Database Router, CPU: 4 Cores of Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz
Database Arbiter
Compute Type-1 14 GB RAM 95
20 GB SSD HDD, 10G ETH
CPU: 8 Cores of Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz
Database Shards 24 GB RAM 190*
Compute Type-2 128 GB(Data), SSD HDD
20 GB (Journal), SSD HDD, 10G ETH
Database Configuration CPU: 8 Cores of Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

Compute Type-3 32 GB RAM 3
Server 100 GB SSD HDD, 10G ETH
Nginx Compute Type-4 32 GB RAM 1
Monitoring Services Compute Type-5 32 GB RAM 1
Hardware requirements theoretically extrapolated based on validation done with 10x scaling
* Number of nodes hosting Database doubled for High Availability [Data Replication]
Key Notes – 100k TPS support
 The number of servers calculated are based upon current unit of hardware on
which the performance benchmark tests were carried out
 The Number of servers to hit 100k TPS (transactions per second) can be
significantly reduced with vertical scaling of the Hardware Unit (server),
specifically CSE and Mongo Shard servers
 Chordant platform architecture is flexible to extend the TPS support with
addition of relevant units beyond 100k
 Nginx can scale beyond 250K TPS on 8 core machine, alternatively, hardware
based load balancers such as F5 can also be deployed.

Chordant Feature Roadmap for 2H 2018
3Q 2018 4Q 2018
• Platform Performance – Optimize Scalability, • Platform Performance - Scalability

Throughput and latencies optimizations with CoAP @ Mca/Mcc
• Deployment grade Interworking Proxy Entity • Interworking Proxy Entity (IPE) Enhancements
(IPE) with integrated LWM2M – oneM2M - Blutetooth, Zwave and ZigBee device support
translation
• Interworking with 3GPP network – Background
• ACP based security at IPE Data Transfer and Network Status Reporting
procedures over T8 interface
• Interworking with 3GPP network – Support
of Network Parameter Configuration and • oneM2M Time Series Data Capability
Communication Pattern Assistance
• oneM2M Constrained Device API
procedures over T8 interface
Enhancement.
23

oneM2M Standards – Feature Compliance
Release 1 Certified solution, Industry’s First oneM2M certified IoT platform.
Golden reference for development of the oneM2M Conformance Suite
Chordant Robot based interop test framework deployed by TTA for oneM2M Release 1 certification.
I1042
Subsequent Slides captures a detailed Feature Compliance Matrix of the Chordant Solution in reference to
the following oneM2M Specifications:
 TS0001 – Version 2.19.0 – Functional Architecture Specification

 TS0003 – Version 2.4.1 – Security Solutions Specification

oneM2M Standards Compliance Matrix
oneM2M Feature Status Comments
Reference Points - Mca Supported Supported over http(s), coap(s), Mqtt(s)
Reference Points - Mcc Supported Supported over http(s), coap(s), Mqtt(s)
Details in the subsequent set of slides.

Reference Points - Mcn Partially Supported
“3GPP Interworking feature support matrix”
I1042
Reference Points – Mcc’ Supported Supported over http(s), coap(s), Mqtt(s)
Application and Service Layer Management /

Roadmap Store and Forward is supported.
CMDH
Container, Flex Container Functionality
Data Management and Repository Supported
Supports
Semantics Roadmap
Time Series Data Roadmap

Device Management Supported LWM2M based device management support
Discovery of registered devices and

Discovery Supported
applications based on specific filters
Register, exercise operations on devices in a

Group Management Supported
batch
I1042 Details in the subsequent set of slides.
Location Supported
“3GPP Interworking feature support matrix”
Network Service Exposure, Service Execution Details in the subsequent set of slides.
Partially Supported
and Triggering “3GPP Interworking feature support matrix”
Registration Supported Application and Device registrations
Details in the subsequent set of slides.

Security Partially Supported
“Security feature support matrix”
Service Charging And Accounting Supported Offline Charging Supported

Intra-M2M SP Communication Supported Intra-M2M Service Provider Communication
Inter M2M SP Communication Supported Inter-M2M Service Provider Communication
Subscriptions supported over HTTP, CoAP and

M2M Service Subscription Supported
MQTT
All identifiers that are fully defined by the
M2M Identifiers Supported
I1042 Release2 Specifications are supported.
Communication Flow Scheme on Mcc and Mca Supported Exchange of messages across reference points
Procedures for Accessing Resources Supported Support for Blocking and Non-Blocking requests
Procedure for interaction with Underlying Partially Details in the subsequent set of slides.
Networks Supported “3GPP Interworking feature support matrix”
Resource Addressing Supported All formats are supported.
Hierarchical and Non-Hierarchical resource

Resource Structure Supported
structure support

Detailed list of resources not supported in
Partially
Resource Types present subsequent slides. ”oneM2M
Supported
Resource Support Matrix”
Basic Procedures / Resource Type – Specific For All resources that are supported, this
Supported
procedures is supported.
Notifications supported over HTTP, CoAP
Notification Procedures Supported
I1042 and MQTT
Partially Details in subsequent slides. “Security
Trust Enabling
supported feature support matrix”
Charging and Accounting Functionality
Information Recording Supported
Supported
Offline Charging feature functionality
Offline Charging Supported
support

oneM2M Resource Support Matrix
oneM2M Resource Status Comments
Delivery Roadmap
locationPolicy Supported
semanticfanoutPoint Roadmap
The CRUD of the resource is supported.

SemanticDescriptor I1042
Roadmap Basic testing done at oneM2M 2018
Interop event
Optional features of the Subscription
notificationTargetMgmtPolicyRef Roadmap
resource
notificationTargetPolicy Roadmap
resource
policyDeletionRules Roadmap
resource
notificationTargetSelfReference Roadmap
resource

oneM2M Resource Support Matrix
oneM2M Resource Status Comments

timeSeries Roadmap
timeSeriesInstance Roadmap
role Roadmap
I1042
token Roadmap
trafficCharacteristics Not Supported Removed in Release3 Specifications
trafficPattern Not Supported Removed in Release3 Specifications
dynamicAuthorizationConsultation Roadmap

Security feature support matrix
PSK and Certificate based D/TLS security association for
Supported
authentication of AEs and CSEs
Authorization of AEs and CSEs to register via oneM2M service
Supported
subscription rules
authorization of AEs and CSEs to access oneM2M resources
I1042 via
Supported
oneM2M access control policies
Remote Security Provisioning Framework for bootstrapping of PoC implementation

Roadmap available. Productization @
credentials via MEF/MAF
roadmap
Dynamic Authorization Roadmap
Role-based Authorization Roadmap

Security feature support matrix

E2E security of oneM2M primitives (ESPRIM) or oneM2M data
Roadmap
(ESData)
GBA based security Roadmap
Secure Trusted Environment / UICC framework I1042 Roadmap

3GPP Interworking feature(T8 Interface) support
matrix
Device Triggering Procedure Supported
Monitoring Events – Location tracking Supported
Monitoring Events – UE Reachability Supported

I1042
Non-IP Data Delivery configuration and Data transfer Supported
Other 3GPP interworking procedures such as Network Parameter

Configuration, Background Data Transfer, Communication Pattern
Roadmap
Assistance, Monitoring Events for IMSI-IMEI Change,
Communication failure, etc

Chordant CSF compliance matrix
Application Entity (AE)
 Application and Service Layer Management.
Mca Reference Point  Core Functionality supported
 Following advanced features are on the road
map/under development
Application and Communication
Data Management o Prioritization, policy based network
Service Layer Management Device Management
Management Delivery Handling & Repository selection
o Semantics
 Communication Management and Delivery Handling
Network Service
Discovery Group Management Location Exposure/Service • Core Functionality supported
Ex+ Triggering • Prioritization, policy based network selection is on
the roadmap
 Data Management and Repository:
Service Charging & Subscription and
Registration Security • Core Functionality supported
Accounting Notification
• Semantics functionality is under development
 Security (Partially Supported):
Mcc Mcn Reference Point  Details of supported security features present in
Supported slide “Security feature support matrix”.
Underlying Network Service  Location, Network Service Exposure – Details of
Under Development
Entity (NSE) supported security features present in slide “3GPP
Roadmap Interworking feature support matrix”.

Chordant – oneM2M Resource Support
Resource Create Retrieve Update Delete
<accessControlPolicyResource> Yes Yes Yes Yes
<accessControlPolicyResourceAnnc> Yes Yes Yes Yes
<CSEBase> NA Yes Yes NA
<remoteCSE> Yes Yes Yes Yes
<remoteCSEAnnc> Yes Yes Yes Yes
<AE> Yes Yes Yes Yes
<AEAnnc> Yes Yes Yes Yes
<Container> Yes Yes Yes Yes
<ContainerAnnc> Yes Yes Yes Yes
<ContentInstance> Yes Yes NA Yes
<ContentInstanceAnnc> Yes Yes NA Yes
<subscription> Yes Yes Yes Yes
<schedule> Yes Yes Yes Yes
<scheduleAnnc> Yes Yes Yes Yes
<locationPolicy> Yes Yes Yes Yes
<locationPolicyAnnc> Yes Yes Yes Yes
Chordant – oneM2M Resource Support – Contd..
<delivery> RoadMap RoadMap RoadMap RoadMap
<Request> NA Yes NA Yes
<group> Yes Yes Yes Yes
<groupAnnc> Yes Yes Yes Yes
<fanOutPoint> Yes Yes Yes Yes
<semanticFanOutPoint> Yes Yes Yes Yes
<mgmtObj>
The <mgmtObj> resource represents a general
structure to map to technology specific data
models. There are multiple specializations of Refer to Slide#27,28 Refer to Slide#27,28 Refer to Slide#27,28 Refer to Slide#27,28
<mgmtObj>. There is no separate schema file just
for <mgmtObj>. Separate oneM2M Management
Functions as per Annexure D of TS-0001 are
supported
<mgmtCmd> Yes Yes Yes Yes

<execInstance> Yes Yes Yes Yes

<node> Yes Yes Yes Yes
<nodeAnnc> Yes Yes Yes Yes
<m2mServiceSubscriptionProfile> Yes Yes Yes Yes
<serviceSubscribedNode> Yes Yes Yes Yes
<pollingChannel> Yes Yes Yes Yes
<pollingChannelURI> NA Yes NA NA
<statsConfig> Yes Yes Yes Yes
<eventConfig> Yes Yes Yes Yes
<statsCollect> Yes Yes Yes Yes
<battery> Yes Yes Yes Yes
<latest> NA Yes NA Yes
<oldest> NA Yes NA Yes
<serviceSubscribedAppRule> Yes Yes Yes Yes
<semanticDescriptor> Yes Yes Yes Yes
<notificationTargetMgmtPolicyRef> No No No No
<notificationTargetPolicy> No No No No
<policyDeletionRules> No No No No

<notificationTargetSelfReference> No No No No
<flexContainer> Yes Yes Yes Yes
<flexContainerAnnc> Yes Yes Yes Yes
<timeSeries> RoadMap RoadMap RoadMap RoadMap
<timeSeriesAnnc> RoadMap RoadMap RoadMap RoadMap
<timeSeriesInstance> RoadMap RoadMap RoadMap RoadMap
<timeSeriesInstanceAnnc> RoadMap RoadMap RoadMap RoadMap
<role> RoadMap RoadMap RoadMap RoadMap
<token> RoadMap RoadMap RoadMap RoadMap
<policyDecisionPoint> No No No No
<trafficCharacteristics> NA NA NA NA
<trafficCharacteristicsAnnc> NA NA NA NA
<trafficPattern> NA NA NA NA
<trafficPatternAnnc> NA NA NA NA
<dynamicAuthorizationConsultation> RoadMap RoadMap RoadMap RoadMap
<triggerRequest> Yes Yes Yes Yes

ANNEXURE -D
<firmware> Yes Yes Yes Yes
<FirmwareAnnc> Yes Yes Yes Yes
<Software> Yes Yes Yes Yes
<SoftwareAnnc> Yes Yes Yes Yes
<memory> Yes Yes Yes Yes
< MemoryAnnc> Yes Yes Yes Yes
<areaNwkInfo> No No No No
<areaNwkDeviceInfo> No No No No
<battery> Yes Yes Yes Yes
<BatteryAnnc> Yes Yes Yes Yes
<deviceInfo> Yes Yes Yes Yes
<DeviceInfoAnnc> Yes Yes Yes Yes
<deviceCapability> Yes Yes Yes Yes
<DeviceCapabilityAnnc> Yes Yes Yes Yes
<reboot> Yes Yes Yes Yes
<RebootAnnc> Yes Yes Yes Yes

ANNEXURE -D
<EventLog> Yes Yes Yes Yes
<EventLogAnnc> Yes Yes Yes Yes
<cmdhPolicy> RoadMap RoadMap RoadMap RoadMap
<activeCmdhPolicy> RoadMap RoadMap RoadMap RoadMap
<cmdhDefaults> RoadMap RoadMap RoadMap RoadMap
<cmdhDefEcValue> RoadMap RoadMap RoadMap RoadMap
<cmdhEcDefParamValues> RoadMap RoadMap RoadMap RoadMap
<cmdhLimits> RoadMap RoadMap RoadMap RoadMap
<cmdhNetworkAccessRules> RoadMap RoadMap RoadMap RoadMap
<cmdhNwAccessRule> RoadMap RoadMap RoadMap RoadMap
<cmdhBuffer> RoadMap RoadMap RoadMap RoadMap

Thank You!
About ChordantTM New York
2 Huntington Quadrangle
Chordant, an InterDigital business, is part of a global company passionate about innovation and a standards-based Melville, NY 11747
approach that stimulates thriving global ecosystems. Solutions powered by the Chordant platform address the
fundamental challenges in Smart City deployments. Like a perfect chord of musical notes, the Chordant platform brings
harmony to diverse devices, data and services. We have created one of the largest Smart City deployments integrating London
hundreds of transport data sources into a transport data marketplace. Our Smart City solutions have also been 64 Great Eastern Street,
recognized by leading analyst firms and organizations.
London, UK EC2A 3QR
We invite you to experience our standard-based future-proof platform and meet our experienced and friendly team!
sales@chordant.io
www.chordant.io
41

Interdigital&#39;s Chordant IoT Platform Overview v3.0

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

Interdigital&#39;s Chordant IoT Platform Overview v3.0

Uploaded by

Copyright:

Available Formats

Chordant™ IoT Platform – Overview

Copyright 2017 InterDigital, Inc. All Rights Reserved

• Chordant™ IoT Platform – Introduction

Copyright 2017 InterDigital, Inc. All Rights Reserved 2

Interdigital’s Chordant™ solution is a Cloud ready, standards-

Copyright 2017 InterDigital, Inc. All Rights Reserved 3

Operator Console for Application

 IoT server deployable on Cloud /

Copyright 2017 InterDigital, Inc. All Rights Reserved 5

*Detailed Rel2 Feature Support Matrix captured in a subsequent slide

Copyright 2017 InterDigital, Inc. All Rights Reserved 6

Copyright 2017 InterDigital, Inc. All Rights Reserved 7

Support for oneM2M Location based service functionality Roadmap

Role-based & Dynamic Authorization Roadmap

Support for interoperability with non-oneM2M (proprietary) communication technologies

Copyright 2017 InterDigital, Inc. All Rights Reserved 8

Copyright 2017 InterDigital, Inc. All Rights Reserved 9

Copyright 2017 InterDigital, Inc. All Rights Reserved 10

 ChordantTM was the first product to be certified

 The Chordant platform has been tested by TTA,

Copyright 2017 InterDigital, Inc. All Rights Reserved 11

Copyright 2017 InterDigital, Inc. All Rights Reserved 12

Copyright 2017 InterDigital, Inc. All Rights Reserved 13

Copyright 2017 InterDigital, Inc. All Rights Reserved 14

oneTRANSPORT™ data marketplace

Copyright 2017 InterDigital, Inc. All Rights Reserved 15

Copyright 2017 InterDigital, Inc. All Rights Reserved 16

CSE CSE CSE

MongoS MongoS MongoS

Sensu MongoD MongoD MongoD

 Redundancy and High Availability using

SSD (File System - XFS) *3x deployment architecture depicted as a reference

Copyright 2017 InterDigital, Inc. All Rights Reserved 18

Chordant - Performance Bench Marks

Copyright 2017 InterDigital, Inc. All Rights Reserved 19

CPU: 8 Cores, Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

Database Configuration CPU: 4 Cores, Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

CPU: 4 Cores, Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

CPU: 4 Cores, Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

Minimum deployable Unit @

* Number of nodes hosting Database

Service Compute Type Node Configuration Num Nodes

Database Configuration CPU: 8 Cores of Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz

Copyright 2017 InterDigital, Inc. All Rights Reserved 22

• Platform Performance – Optimize Scalability, • Platform Performance - Scalability

Copyright 2017 InterDigital, Inc. All Rights Reserved 23

Release 1 Certified solution, Industry’s First oneM2M certified IoT platform.

Golden reference for development of the oneM2M Conformance Suite

 TS0001 – Version 2.19.0 – Functional Architecture Specification

Copyright 2017 InterDigital, Inc. All Rights Reserved 24

Reference Points - Mcc Supported Supported over http(s), coap(s), Mqtt(s)

Details in the subsequent set of slides.

Application and Service Layer Management /

Time Series Data Roadmap

Copyright 2017 InterDigital, Inc. All Rights Reserved 25

Discovery of registered devices and

Register, exercise operations on devices in a

Registration Supported Application and Device registrations

Details in the subsequent set of slides.

Service Charging And Accounting Supported Offline Charging Supported

Copyright 2017 InterDigital, Inc. All Rights Reserved 26

Inter M2M SP Communication Supported Inter-M2M Service Provider Communication

Subscriptions supported over HTTP, CoAP and

Resource Addressing Supported All formats are supported.

Interdigital's Chordant IoT Platform Overview v3.0

Interdigital's Chordant IoT Platform Overview v3.0