13
•JCA‐IoT/IoT‐GSI•JCA‐NID played the coordination role since 2006.
Background
•ITU‐T has a long history of IoT discussion over many years.
[NID/RFID(since 2006)]
•NID spec. study in collaboration with JTC1•F.771, H.621 (NID req & arch)
[USN(since 2008)]
•F.OpenUSN•F.744 (USN MW)
[e‐health by Q.28/16(since 2008)]
[ITS]
•FG‐CarCOM(2009‐)•FG‐FITCar (2008‐2009)
•Q27/16 (2008‐)
JCA‐SG&HN
•FG‐Smart Grid(2010‐2011)
IoT‐GSI/JCA
•Originally created as JCA‐NID and played the coordination role within ITU and with SDOs.
•Technical study was carried out by each Questions such as Q3/13, 5/13, 12/13, 21/16, 22/16, 25/16.•No consolidated technical study platform for NID/IoT.
•TSAG (February 2011) changed JCA‐NID to JCA‐IoT.•After transition to JCA‐IoT, the JCA created IoT‐GSI.
•GSI, collocated Rapporteur meeting, provides a platform for technical study.•Participation of Questions from different Study Groups stimulates discussions and new ideas.
IoT‐GSI /JCAand participating Questions
Q Questions participating IoT‐GSI
1/3 Development of charging and accounting/settlement mechanisms for international telecommunications services using the Next Generation Networks (NGNs) and any possible future development, including adaptation of existing D‐series Recommendations to theevolving user needs
12/11 NID and USN test specification
3/13 Requirements and implementation scenarios for emerging services and capabilities in an evolving NGN
4/13 Requirements and frameworks for QoS enablement in the NGN
5/13 Principles and functional architecture for NGN (including ubiquitous networking)
7/13 Impact of IPv6 to an NGN
12/13 Evolution towards integrated multi‐service networks and interworking
16/13 Security and identity management
25/13 Coordination, Planning, and Terminology
21/16 Multimedia architecture
22/16 Multimedia applications and services
25/16 USN Applications and Services
6/17 Security aspects of ubiquitous telecommunication services
IoT Definition
•IoT is too broad, difficult to capture key characteristics.•Philosophy or technology? ITU‐T tried to make a technical definition.
Internet of Things: In a broad perspective, the IoT can be perceived as a vision with technological and societal implications. From the perspective of technical standardization, IoT can be viewed as 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. 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 maintaining the required privacy.
Thing: In the Internet of Things, a physical or virtual object of the physical or information world which is capable of being identified and integrated into the information and communication networks.
NID architecture
•NID is a traditional type of IoT. This enables user to take information related to the object regardless of its communication capability.•NW is just for information delivery.
Functional architecture of NID [H.621]
USN Platform
•Variety of USN devices will be available for USN applications.•USN platform allows the development of USN applications without particular knowledge of each USN devices.
One of use cases of USN [F.OpenUSN]
IoT Overview
•SG13 recently produced Rec. Y.2060(Y.IoT‐overview).•“Things” locating in the physical world are mapped to the information world so that they become communication capable objects.
Overview of IoT [Y.2060]
Service capability/MW/SDP
•MW/SDP provides an interface to applications.•A key feature of IoT/M2M.
USN Middleware [F.744]
USN application
Sensor NW, RFID reader
OSE(SDP)
USN MW
OSE (SDP) in NGN [Y.2020]
Collaboration with stakeholders
•Stakeholder industries (car manufacturer, electricity etc) is the key driver.•Need to be “telecom‐oriented‐standard”?•How to establish the collaboration with them?
Conclusions
•IoT is NOT a new idea for ITU‐T.•It has a long history since NID and USN.
•Scope of IoT is too broad. •Is it really technology? This may be more like a philosophical concept.•This may be a collection of use cases which has few common aspects.
•Need participation of/collaboration with external experts•Need flexibility (e.g. Focus Group).•Do not expect a quick result.
[Appendix]List of IoT related RecommendationsRec Title Q/SG Note
Y.2221 Requirements for support of ubiquitous sensor network (USN) applications and services in the NGN environment
SG13
Y.EHM‐reqts Requirements and network capabilities for E‐health monitoring applications
Q3/13 E‐health
Y.I2060 Overview of Internet of Things Q3/13
Y.2061 Requirements for support of machine oriented communication applications in the NGN environment
Q3/13
Y.USN‐arch Q5/13
Y.NGN‐IoT‐arch
Architecture of NGN for support of the Internet of Things Q5/13 Living List
Y.energy‐hn Energy saving using smart objects in next generation home network Q12/13
Y.2062 Framework of object‐to‐object communication for ubiquitous networking
Q12/13
Y.WoT Framework of Web of Things Q12/13
Y.terms‐IoT Terminology of the Internet of Things Q25/13
F.744 Service description and requirements for ubiquitous sensor network middleware
SG16
F.771 Service description and requirements for multimedia information access triggered by tag‐based identification
SG16
H.621 Architecture of a system for multimedia information access triggered by tag‐based identification
SG16
[Appnedix]List of IoT related RecommendationsRec Title Q/SG Note
H.ID‐RA Information technology –UII scheme and encoding format for Mobile AIDC services –Part 2: Registration procedures
Q22/16 ISO/IEC JTC1とのcommon text
H.IDscheme Information technology –UII scheme and encoding format for Mobile AIDC services –Part 1: Identifier scheme for multimedia information access triggered by tag‐based identification
Q22/16 ISO/IEC JTC1とのcommon text
H.IRP Information technology – Automatic identification and data capture technique –Identifier resolution protocol for multimedia information access triggered by tag‐based identification
Q22/16 ISO/IEC JTC1とのcommon text
H.snmf SNMP‐based sensor network management framework Q25/16
F.usn‐cc Deployment guidance on USN applications and services for mitigating climate change
Q25/16
F.usn‐nrp Requirements of Network Robot Platform for USN application and services
Q25/16
F.usn‐sm Capabilities of ubiquitous sensor network (USN) for supporting requirements of smart metering services
Q25/16
F.OpenUSN Requirements and reference architecture for open USN service framework
Q25/16
X.unsec‐1 Security requirement and framework of ubiquitous networking Q6/17
X.usnsec‐3 Security requirements for wireless sensor network routing Q6/17
