3rd SG13 Regional Workshop for Africa on
“ITU-T Standardization Challenges for
Developing Countries Working for a
Connected Africa”
(Livingstone, Zambia, 23-24 February 2015)
Requirements and Capabilities of the
IoT and related (ITU-T) standardization
Marco CARUGI
Consultant on ICTs and Standards
ITU-T Q2/SG13 Rapporteur and SG13 Mentor
marco.carugi@gmail.com
Livingstone, Zambia, 23-24 February 2015
Outline
Introduction to the Internet of Things
(IoT) and related standardization
Basic requirements and capabilities of
the IoT
Some critical IoT subject areas (from the
requirements and capabilities viewpoint)
Few personal considerations about
perspectives of the IoT standardization
Disclaimer: this content does not obviously intend to cover all ITU-T
standardization activities related to the IoT
2
Introduction to the IoT and
related standardization
3
The Internet of Things era: more and more
“Things” connected, high business expectations
Source: Cisco
In 2020, over 30 Billion
connected devices will be in use
Source: Gartner
One trillion connected devices
by 2015
Source: IBM Investor
Briefing ‘Making Markets: Smarter Planet’
The worldwide market for IoT solutions is expected to grow from
Source: IDC
US $1.9 trillion in 2013 to US $7.1 trillion in 2020
IoT has been the most hyped technology in 2014
Source: Gartner’s Hype Cycle for Emerging Technologies, 2014
4
The IoT is driving convergence between ICT
and Industries (the so-called Verticals)
Source: Frost & Sullivan (2012)
Some people talk about the IoT as the “Third Industrial Revolution”.
The IoT (more connectivity and more data) will profoundly transform (reinvent) industries with digitalization impacting products, processes,
business models & ecosystems, social life.
“Ultimately, digitalization is connecting all industries into a giant
ecosystem.” [source: Harvard webinar]
5
Internet of Things
but also Internet of People
More and more smart services
for people
Utilities / Smart
Transport
Security, emergency
Metering, Smart
management
Business
& Consumer
Grid
IoT
Healthcare
Smart Home
Agriculture
Sales &
Provisioning
Digital Signage
+.
6
An example of IoT application domain:
healthcare
The figure shows the key technical components involved in “Remote patient
monitoring/assisted living” healthcare application enabled by IoT technologies
[source: ITU-T Focus Group M2M Service Layer]
7
Some trends in the
Internet of Things space
Fragmented market &
vertical applications
Horizontal solutions
Integrated data analytics
B2B => B2C/B2B2C services
B2B services
Dominance of cellular
networks
Hyper-growth of Service Providers,
variety of business models
Multi-access networks
Cloud Computing (and distributed
computing)
From business market to mass market and pervasiveness
8
From vertical to horizontal integration
The current situation of technology
separation among IoT application
domains produces market separation
per application domain
VERTICAL MODEL
Service
platform
meter
Service
platform
HORIZONTAL MODEL
Service
platform
vehicles
Service platform configured
per vertical application
Other
modules and
terminals
Integrated service platform
meter
vehicles
Other
modules and
terminals
Integrated service platform supporting multiple
applications
Generic components and application specific
components
9
A number of standardization
efforts related to the IoT
Diversity of the IoT relevant standardization efforts:
•
•
•
•
principal stakeholders
IoT centrality or complementarity
IoT general coverage or specific technology areas focus
horizontal or vertical (application domain) focus
Some key efforts:
• ITU-T (Study Groups, Focus Groups)
• oneM2M (Partnership Project)
• IETF (Working Groups)
• ISO and ISO/IEC JTC1
• IEEE (Working Groups)
But numerous other efforts also relevant, including fora, alliances,
consortia, open source communities, regional initiatives
International collaboration among standardization efforts
(convergence and integration of standards) is essential, including
that one required by the intersection of ICT industry and Vertical
industries.
10
Role of standards
Some relevant issues for which standardization (and
effective operation of global standards) can play a
significant role with respect to the large scale adoption of
IoT solutions
•
Interoperability
•
Solution modularization and economies of scale
•
Openness
•
Cross-domain integration
•
Security and privacy protection
•
Affordability and added value in critical domains (e.g. health,
environment, e-government, agriculture, industrial processes,
energy, transport, disaster relief)
Timing availability of standards versus (“proprietary”) market
deployments: a number of the usual arguments apply …
11
ITU-T organizational structure for
the “main” IoT standardization activities
Joint Coordination Activity on IoT - 03/2011
IoT Standards Roadmap
•
•
Coordination on IoT, including network aspects of
identification of things (NID) and USN
Participating entities: All ITU-T SGs; ITU-R WP1A, WP1B,
WP5A; ISO TC 122, 204: ISO/IEC JTC 1 SC 6, 31, WG 7;
ETSI, CEN, OMA, GS1/EPC global, YRP, ECMA, GSIFI,
TIA, GSM MSTF, OGC, oneM2M, IEEE
On-going and published work on
IoT in ITU and other SDOs
Open to public (free download)
IoT work plan
• On-going and planned work
on IoT within ITU-T
IoT-GSI (IoT Global Standards
Initiative) - 05/2011
The actual working tool
Core Questions: Q1/2, Q1/3, Q1/11,
Q12/11, Q1/13, Q2/13, Q3/13, Q11/13,
Q25/16, Q27/16, Q28/16, Q6/17
Additional Questions have expressed
interest (but are no “core” Questions)
Focus Group on M2M Service
Layer - as an example of FGs
12
ITU-T activities related to IoT
Within the context of IoT-GSI [numerous
numerous Recommendations completed
completed]
SG11
APIs and protocols for IoT (activity started 07/2014), IoT Testing
SG13
Focus on Network Aspects of IoT
SG16
Focus on IoT applications
SG17
Security and privacy protection aspects of IoT (already published some
specs related to USN and services using tag-based identification)
Other activities
SG15
Smart Grids, Home Networks
Focus Group on Smart Sustainable Cities (FG SSC) (since 02/2013)
Focus Group on Smart Water Management (FG SWM) (since 06/2013)
Focus Group on M2M Service Layer (FG M2M) (closed 03/2014)
Collaboration on ITS Communication Standards (also some past FGs on Cars) 13
Basic requirements and
capabilities of the IoT
NOTE: this content is based on the achievements of ITU-T SG13 (where the
foundational activities on IoT requirements and capabilities have been/are
performed). Some work on specific matters has been and is also performed in other
ITU-T Study Groups (e.g. SG16 on some service-related aspects and SG17 on some
security-related aspects).
14
The ITU-T definition of “IoT”
Internet of Things [ITU-T Y.2060]:
“A global infrastructure for the information society, enabling
advanced services by interconnecting (physical and virtual)
things based on, existing and evolving, interoperable information
and communication technologies.
NOTE 1 - Through the exploitation of identification, data capture,
processing and communication capabilities, the IoT makes full
use of things to offer services to all kinds of applications, whilst
ensuring that security and privacy requirements are fulfilled.
NOTE2 - In a broad perspective, the IoT can be perceived as a
vision with technological and societal implications.”
Above definition is fundamentally aligned with the IoT concepts
and terminology developed in other key SDOs and communities
Thing: In the Internet of Things, object of the physical world (physical
thing) or of the information world (virtual thing), which is capable of
being identified and integrated into the communication networks.
IoT versus M2M (Machine to Machine): the M2M communication
technologies are “a key enabler of the IoT” (but not the only one)
15
Some basic IoT achievements of SG13
Machine-oriented communications
Y.2061: Requirements for the support of machine-oriented communication
applications in the NGN environment
Overview and terminology of the IoT
Y.2060: Overview of the Internet of things [06/2012]
Y.2069: Terms and definitions for the IoT [NOTE – revision expected]
Y.2063: Framework of the web of things
Requirements and capabilities of the IoT
Y.2066: Common requirements of the IoT [06/2014]
Y.2068: Functional framework and capabilities of the IoT [currently under AAP]
IoT application or domain specific
Y.2064: Energy saving using smart objects in home networks
Y.2281: Framework of networked vehicle services and applications using NGN
Y.2065: Service and capability requirements for e-health monitoring services
Y Suppl. 22 of ITU-T Y.2200-series: Greenhouse gas monitoring services
provided over NGN
Gateway for IoT applications
Y.2067: Common requirements and capabilities of a gateway for IoT
applications [06/2014]
16
Integration of leading technologies with IoT
The IoT is expected to benefit from the integration of
diverse leading technologies, e.g. those for
•
Machine to Machine Communications
• Autonomic Networking
• (Big) Data Management (e.g. de-noising, analysis, machine learning etc.)
• Semantics support
• Security and Privacy Protection
• Cloud Computing (and distributed computing)
• Service Delivery Platforms
• Software Defined Networking and Network Functions Virtualization
with advanced technologies for
•
Sensing and Actuation
Benefit from capabilities provided by different technologies,
reusability (economies of scale, interoperability)
17
IoT in ITU-T: Technical Overview
Source: ITU-T Y.2060
Device: In the Internet of Things, a piece of equipment with the mandatory
capabilities of communication and the optional capabilities of sensing,
actuation, data capture, data storage and data processing
18
IoT in ITU-T: IoT Reference Model
Source: ITU-T Y.2060
19
IoT reference model generalized from previous studies
USN
Services
Disaster/crisis
management
Logistics, SCM
Structural health
monitoring
USNApplications
Applications
USN
Agricultural control
Disaster Surveillance
Military Field
U-Health care
Ubiquitous
web services
USN
Directory service
USNMiddleware
Middleware
USN
Context modeling
and management
Management
Contents management
Service orchestration
NGN
Access
Network
Access
Network
Access
Network
Access
Network
USN Gateway
Mobile
RFID
Reader
USN Gateway
Access Gateway
USN Gateway
SensorNetworks
Networks
Sensor
Sensor node
RFID
Reader
Sensor
Networks
Access
Network
Sink node
Source: Y.2221 (2010) “Requirements for support of Ubiquitous
Sensor Networks (USN) applications over NGN”
(see also Y.2026 (2012) for NGN related functional aspects)
20
IoT in ITU-T: IoT Business Ecosystem(s)
Business Roles
Source: ITU-T Y.2060
This “simplified view” of business roles with their relationships has obviously
not the ambition to represent all possible roles and relationships which can be
found across the huge number of real IoT business deployments.
Main objective of this analysis: building a proactive linkage
between real deployments and technical standardization
(requirements, capabilities and functions, open interfaces)
21
IoT in ITU-T: fundamental characteristics
and high level requirements of the IoT
Characteristics
Interconnectivity
Things-related services
Heterogeneity
Dynamic changes
Enormous scale
Requirements
Identification-based
connectivity
Interoperability
Autonomic networking
Autonomic services
provisioning
Location-based capabilities
Security
Privacy protection
High quality and highly
secure human body related
services
Plug and play
Manageability
Source: ITU-T Y.2060
22
Common requirements of the IoT [Y.2066]
The common requirements of the IoT are technical
requirements independent of any specific application domain
IoT non-functional requirements: refer to the requirements
related to the implementation and operation of the IoT itself
Interoperability, scalability, reliability, high availability, adaptability,
manageability
IoT functional requirements: refer to the requirements related
to the IoT actors (i.e. entities external to/interacting with the IoT);
they have been categorized as
Application support requirements
Service requirements
Communication requirements
Device requirements
Data management requirements
Security and privacy protection requirements
NOTE: The IoT actors (specified from a requirements viewpoint) and the
general use cases of the IoT (modelled via UML and used to capture the
requirements of the involved actors) are identified in clause 6 of Y.2066;
Annex A of Y.2066 summarizes all the identified requirements.
23
Functional framework and capabilities
of the IoT [Y.2068]
Y.2068 scope:
IoT functional framework concepts and its three views
(functional view, implementation view, deployment view)
The IoT basic capabilities fulfilling the common requirements of
the IoT specified in [Y.2066] (identified via the three views)
Additional IoT capabilities for the integration of key emerging
technologies with the IoT (two technology areas addressed)
NOTE:
Annex A provides a summary of all identified capabilities
Appendix I provides an analysis of all identified capabilities in
terms of matching with common requirements of IoT [Y.2066]
The detailed specification of the identified capabilities is outside
the scope of Y.2068
24
The three views of the IoT functional framework (1 of 2)
The IoT functional framework can be described via three distinct views, reflecting
three different phases of development of the IoT (design phase, implementation
phase and deployment phase).
Each view describes IoT capabilities aiming to fulfill the requirements encountered
in different phases of development of the IoT.
Functional view of the IoT functional framework
25
The three views of the IoT functional framework (2 of 2)
Implementation view of the IoT
functional framework building over
the NGN functional architecture
Deployment view of the IoT
functional framework building
over the NGN components
26
The IoT capabilities identified in Y.2068
Basic capabilities - categorized as
Application support capabilities
Service provision capabilities
Communication capabilities
Data management capabilities
Connectivity capabilities
Management capabilities
Security and privacy protection capabilities
Additional capabilities required for integration of key
emerging technologies
Capabilities for integration of Cloud Computing technologies
Capabilities for integration of Big Data technologies
NOTE – Other additional capabilities for integration with the IoT of
other emerging technologies, such as network function virtualisation,
software defined networking etc., are for further study.
27
Gateway for IoT applications
Common requirements and capabilities of a gateway for IoT
applications [Y.2067]
• General characteristics of a gateway for IoT applications
• Common requirements and common capabilities
• Use cases (informative material)
Typical
deployment
scenario
gateways for IoT applications
of
Reference technical framework of a gateway for IoT
applications
IoT applications
Communication networks
Gateways
Devices
Y.2067(14)_F01
28
Also IoT application(s)-specific requirements have
been addressed in some studies: the example of ehealth requirements from the ITU-T FG M2M SL
Key goal of the Focus Group M2M SL [2012-03.2014]: study of the
requirements and specifications for a common M2M Service Layer
From the viewpoint of use cases and derived requirements, it
decided to focus its work on the “e-health” application domain
(remote patient monitoring and assisted living services)
Involvement of vertical market stakeholders, such as the World Health
Organization (WHO), and collaboration with M2M and e-health
communities and SDOs
It completed five deliverables (now transferred to ITU-T SGs)
E-health use cases
E-health ecosystem -> it includes e-health application-specific
requirements
M2M service layer requirements and architectural framework
Overview of M2M service layer APIs and protocols
E-health standards repository and gap analysis
29
Some critical IoT subject areas
(from the viewpoint of
requirements and capabilities)
30
Some SG13 ongoing work items
on basic aspects of the IoT
IoT network requirements (focus on network transport control)
Y.IoT-network-reqts: Network requirements of the IoT
Application support models of the IoT (modularity of the IoT
infrastructure)
Y. IoT-app-models: IoT application support models
Semantic and Big Data related capabilities (more intelligence in IoT)
Y.IoT-semantic-reqts-framework: Semantic related requirements and
framework for the IoT
Y.IoT-BigData-reqts: Specific requirements and capabilities of the IoT
for Big Data
Accounting and Charging capabilities (sustainable business models)
[newly Q2/13-agreed work item - Feb 2015 interim meeting]
Y.IoT-AC-reqts: Requirements for accounting and charging capabilities
of the IoT
NGN based architecture of the IoT (incremental deployment)
Y.NGNe-IoT-arch: Architecture of the IoT based on NGN evolution
31
IoT network requirements [Y.IoT-network-reqts]
Numerous types of IoT devices, numerous types of access technologies, an
increasing number of connected devices => it is important to investigate
detailed network requirements of the IoT, e.g. to avoid potential issues such
as service failures caused by congestion/overload in the network.
Focus : network transport functions (but service support and network
performance functions not excluded).
Network-based solution: balancing the
Example use case (issue to be solved):
Possible unbalanced load
of the ad-hoc
network from the core network point of view
topology from the core network point of view
Identified network requirements to be
supported: calculation of the optimal ad-hoc
network topology by using monitoring
information, and notification of appropriate
actions based on calculation results
Various use cases under study have generated requirements for data transmission timing
32
control, traffic route diversion, ad-hoc network topology modification
IoT and (Big) Data
The Industrial Internet Data loop
[source: GE whitepaper]
Data interoperability
throughout the cycle
is critical
(syntax and meaning)
Some analysts indicate that by 2020 40% of data will come from sensors
Raw data -> Information -> Knowledge -> Wisdom (see a following slide)
Various operations on data for the extraction of actionable intelligence (collection, dedenoising, aggregation, adaptation, analysis)
Data sources: (real-time) collected data from things and context, historical and social data
Data related concerns: Volume, Variety, Velocity, Variability, Veracity, as well as (semantic)
interoperability, security and privacy, ownership
The right data, at the right time, at the right place (cloud computing versus distributed
computing)
33
ITU-T developments related to IoT Data aspects
Completed studies
Y.2066: Common requirements of the IoT
It includes requirements on data aspects
Y.2068: Functional framework and capabilities of the IoT
It includes IoT capabilities for data management and for integration of Big Data
technologies and Cloud Computing technologies with IoT
Ongoing developments specific to IoT Data aspects
Y.IoT-BigData-reqts: Specific requirements and capabilities of the IoT for
Big Data
Y.IoT-semantic-reqts-framework: Semantic related requirements and
framework for the IoT
General roadmap of Big Data Standardization [first version, 11/2014]
ITU-T Study Groups been tasked to build a standards landscape in the telecom
sector and related industries;
IoT (and Cloud Computing) identified as relevant Technical Area for Big Data
34
IoT and Big Data [Y.IoT-BigData-reqts]
Initial discussions on challenges of Big Data in the context of IoT
•
•
•
•
Increasing
Generated
Generated
Generated
number of connected things generates huge amounts of data
data are mainly semi-structured or even unstructured
data may have different confidence and precision levels
data are generally not useful until adequately processed
IoT Data processing phases
[work in progress, including terminology
and relationship among processing steps]
Steps of the work item development
[specific requirements and capabilities of
the IoT for Big Data]
35
Semantics and IoT: example of the usage of
semantic technologies in IoT Data transformation
The knowledge hierarchy
applied in IoT Data processing
Source: Barnaghi and al.,
“Semantics for the IoT: early
progress and back to the future”
(IJSWIS, 2012)
Things generate raw data
Additional information enables creation of structured metadata (first
step of enriching IoT Data) –> semantic technologies can be used
Abstractions and perceptions give detailed insights by reasoning using
knowledge (ontologies, rules) of different domains (second step of
enriching IoT Data ) –> semantic technologies can be used
Actionable intelligence allows decision making
36
Semantic related requirements and framework
for the IoT [Y.IoT-semantic-reqts-framework]
The outstanding features of semantic technologies for applicability to IoT
Semantic technologies are good candidates to fulfill essential IoT requirements
Concerning data and services, they enable efficient description, consistency,
scalability, reusability, interoperability, improved human-machine interaction,
automatic operations
Semantic technologies are applicable to the different layers and cross-capabilities
of the IoT reference model [Y.2060]
General semantic requirements for the IoT
Semantic annotation, semantic interoperability, semantic discovery, semantic
reasoning, semantic composition
Layered semantic requirements for IoT
The semantic requirements specific to the different layers and cross-capabilities
of the IoT reference model [Y.2060]
IoT semantic framework
The IoT semantic related capabilities which can be used in the different IoT
technical components, including devices, networks, platforms and applications
Based on the identified IoT semantic requirements and existing semantic
technologies
37
Accounting and charging capabilities of the IoT
Y.IoT-AC-reqts: Requirements for accounting and charging capabilities of the IoT [newly
Q2/13-agreed work item, Feb 2015 interim meeting]
Building on requirements and framework for accounting and charging capabilities in NGN [ITU-T Y.2233]
Identification of specific requirements derived from analysis of business use cases specific to the IoT
Work scope:
Business use cases specific to the IoT
IoT accounting and charging requirements
IoT accounting and charging capability framework
NGN A&C functional architecture [Y.2233, 2010]
Target of IoT accounting and charging
capability framework
38
Some initial efforts on IoT
architectural aspects
39
The ongoing effort of another SDO related to IoT
architecture: oneM2M PP’s Common Service Layer
Pipe (vertical):
1 Application, 1 NW,
1 (or few) type of Device
Point to point communications
Horizontal (based on common Layer)
Applications share common service and network infrastructure
Multipoint communications
Business
Application
Application
Application
Application
Common
Service Layer
Common Service Layer
Communication
Network (wireline, wireless,
Powerline ..)
Things
representations
Communication
Network 2
Communication
Network 1
IP
Gateway
Gateway
S
Local NW
Local NW
A
Device
Things
A
A
Device
Device
A
S
Device
S
A
AA
S
Device
Common Service Layer
Application
40
The oneM2M Common Service Functions provided by
the Common Service Layer
Registration
Discovery
Security
Group
Management
Data
Management &
Repository
Subscription &
Notification
Device
Management
Application &
Service
Management
Communication
Management
Network
Service
Exposure
Location
Service
Charging &
Accounting
NOTE – The oneM2M Functional Architecture Release 1 deliverable has
been issued on 4 February 2015 as part of the oneM2M Release 1
specifications.
41
The capabilities identified by the ITU-T FG M2M Service Layer
In line with the IoT Reference Model of ITU-T Y.2060, the ITU-T M2M service
layer capabilities include those common to the support of different application
domains and the specific ones required for support of each application domain
42
Incremental deployment: a new SG13 work item (Nov 2014)
about architecture of the IoT based on NGN evolution
Y.NGNe-IoT-Arch scope:
an architecture of the IoT based on enhancements to
the NGNe functional entities, reference points and components (as described in Y.2012,
Y.2301, Y.2302 and other related Recs), taking into account the IoT reference model, IoT
common requirements and IoT basic capabilities (Y.2060, Y.2066, Y.2068)
This study has just started and extended discussions are expected.
The basic idea behind its launch is to study if, how and at which extent the
common requirements and basic capabilities of the IoT can be supported by
43
an evolving NGN infrastructure.
Few personal considerations
about perspectives of the IoT
standardization
44
IoT standardization perspectives:
some personal considerations
The current situation of technology separation among IoT application domains results
in market separation per application domain (hindering technical innovation and
investments in the IoT business)
It is necessary to standardize common technologies of the IoT across the
different application domains
In addition to the standardization of specific technologies, the future
standardization of the IoT should:
1) build over a standardized new architecture reference model for the IoT as
guidance for whole standardization process (including specification at both logical
and physical levels, and verification of correctness and completeness)
2) focus on the interactions among functional entities or deployable
components of the IoT, in order to simplify the standardization work and impose
minimum constraints on future technical innovations
3) progress about the deployment of the IoT in specific application domains
(appl. domain profiles ?) as well as the integration of emerging
technologies with the IoT (e.g. cloud computing, big data, SDN, NFV),in order to
strengthen the applicability and value of IoT standards
Considering that the IoT builds on existing information and communication systems,
the IoT standardization work should be conducted in an evolutionary way in
order to enable the integration of existing ICT at the greatest possible extent.
[S. Shen,
Shen, M. Carugi - ITUITU-T Kaleidoscope 2014 and Rivers Journal of ICT Standardization] 45
Thank you very much
for your attention
46
Some relevant ITU-T links on IoT
IoT-GSI
http://www.itu.int/en/ITUT/gsi/iot/Pages/default.aspx
JCA-IoT
http://www.itu.int/en/ITUT/jca/iot/Pages/default.aspx
ITU-T Recommendations
http://www.itu.int/en/ITUT/publications/Pages/recs.aspx
Focus Group on M2M Service Layer
http://www.itu.int/en/ITUT/focusgroups/m2m/Pages/default.aspx
47
Marco Carugi
Marco Carugi works as consultant on advanced ICTs and associated standardization,
representing ITU-T members in ITU-T standards development activities (requirements and
architectures for advanced services and networks).
Marco began his career in Solvay as telecommunication system engineer, worked for 7 years
in France Telecom/Orange Labs as research engineer on Broadband Data Services and
Network Technologies and then for 8 years in Nortel CTO organization as Senior Advisor on
NGN and emerging services. More recently, he has worked for 3 years in ZTE R&D division,
Technology Strategy department, as Senior Expert on future service and network
technologies and associated standardization.
Marco participates actively since 1998 in several standard development organizations, and
has held numerous leadership positions, including vice-chair of ITU-T SG13, Rapporteur in
last three ITU-T study periods, WG chair in ITU-T Focus Group on Cloud Computing, member
of OIF Board, co-chair of IETF Provider Provisioned VPN WG.
Currently, he is Rapporteur for Q.2/13 (“Requirements for NGN evolution (NGN-e) and its
capabilities including support of IoT and SDN”) inside ITU-T SG13 (Future networks including
cloud computing, mobile and NGN). NGN evolution, SDP, SDN, Cloud Computing and
IoT/M2M are technical areas in which he is involved at present.
As Rapporteur for Q.2/13, he is currently participating in the ITU-T IoT Global Standards
Initiative where he leads the development of technical specifications on requirements,
capabilities and services for IoT/M2M , and has acted as vice-chair of the ITU-T Focus Group
on M2M Service Layer.
He is a regular participant as ITU-T representative in the meetings of the European
Commission’s Internet of Things Research Cluster.
Marco has led the development of numerous standards specifications and published in
technical journals and books.
Marco holds an Electronic Engineering degree in Telecommunications from University of Pisa
in Italy, a M.S. in Engineering and Management of Telecommunication Networks from
National Institute of Telecommunications (INT) in France and a Master in International
Business Development from ESSEC Business School in Paris.
48