web of thing 표준 - krnet · [email protected] web systems 16 soa functionality composition...
TRANSCRIPT
New Research Challenges for ICT
4
Internet of Things(The ongoing convergence of
evolution of devices)
ComputingClouds
(Deployment of large shared infrastructure)
Big Data(Accumulation of data fromsensors and social networks)
From IoT to WoT
5
Each Physical entity can be part of the Web.
Physical entities are marked in the real-world and become a part of the virtual world.
The integration of the physical world with the Web offers unique opportunities to enable ubiquitous computing applications.
Internet of Thing/Web of Thing/Web of Objects (IoT/WoT/WoO)
6
Web-based(RESTful API, Search, Composite,
Mashups)
Internet of Things(Smart environments)
Internet
Internet of Clouds(Computing technologies)
Web of Objects“connectivity + reality + intelligence”
Web of Things 1.0, 2.0 & 3.0WoT1.0 WoT3.0
AggregationResource Mgt.
Abstraction
Collaborative Semantics
Search
Recipes Wizards
Composition
Catalog
WoT2.0
HTTP HTTP
7
The IoT characteristics Required characteristics
Reliable Secure Scalable Interoperable Consistent Pervasive Efficient Coherent
Role for network – Integrate all kinds of objects
9
Challenges – readable, recognizable, locatable, addressable and/or controllable via the Internet
Networking and Services Evolution for the IoT
Characteristics of the IoT IP connectivity Personalization Intelligence Tagging objects Smart devices
10
Evolution of Smart Objects
The IoT using local and public clouds
11
Public resource management, QoS management, Service
invocation, Admission control
Location management, Service exposure, Billing,
Identity management, Service Support functions
Local resource management, Public cloud interaction
Resource exposure, Resource Request
Cloud Model for IoT Services
12
Virtu
alis
ation
Serv
ice m
ashup
end-users, innovators, startups, service providers, SMEs,
legacy devices CIaaSCity Infrastructure
as a Service
CPaaSCity Platform as a
Service
Middleware services
CSaaSCity application
Software as a Service
Web of Things
14Dominique Guinard, ETH / SAP Research Zurich, webofthings.com
IPv6(lowpan)
Web Cloud
Compose VisualizeSearch PhysicalMashups
Smart Gateway
RESTful API
BT Zigbee ……API1 API2
Web Cloud
Compose VisualizeSearch PhysicalMashups
Web Server
RESTful APIWeb ServerRESTful API
Web ServerEventing
MEM @ WWW 2009, Madrid
Web Engineering
15
•Physical Layer•Internet Layer•Transport Layer•Performance
•Process•Design•Implementation•Test•Operation•Maintenance
•Design & StructureInformation Space
•Navigation•Visualization•Usability•Collaboration
•Data Design, ER,...•RDBMS•Query Languages•Strg.Devices: FS,...
Web Engineering
NetworkEngineering
SoftwareEngineering Hypermedia
InformationSystems
Web Systems
16
SOA Functionality Composition Engine Federation, Security Transaction, etc.
Configuration/Context Components, End Points Semantic Web Policy, Permissions, etc.
Model-drivensupport systems
Communication
Identification Provider / Security Token Service
IP/STS
SecurityContext
Presence /Location Server
P/LS
Presence/LocationContext
Cluster:
ClassificationClassification
Web Services Universe
Classification
Discovery
HTTP/SOAP
Vision of Energy Web Web as a Platform of Smart Grid Network
Smart Metering (Advanced Measurement Infrastructure) Smart Control (Energy Management System) Smart Transportation (Energy Charging/Discharge Infrastructure) Smart Home (Green Office)
17
Vision of Health Web Web as a Platform of Health
E-Heath (Remote Diagnosis and Decision Support) Data Archiving, Processing, Inventory, and Viewing Remote Acquisition and Surgery
18
Vision of Transportation Web Web as a Platform of Transportation
Traffic management Emergency management including security monitoring Data archiving and traveler support
19
Vision of Education Web Web as a Platform of Education
Self-organized virtual learning platform Collaborative/Communicative/Individual Learning platform Virtual Experience via networked device Big Repository of Education Materials
20
ITU-T Recommendation relating to IoT/WoT Overview and terminology of the IoT/WoT
Y.2060, Overview of the Internet of things Y.2063, Framework of the web of things Y.2069: Terms and definitions for the Internet of things
Ubiquitous networking Y.2002: Overview of ubiquitous networking and of its support in NGN Y.2062: Framework of object-to-object communication for ubiquitous
networking in next generation networks Ubiquitous Sensor Networks and Sensor control networks
Y.2221: Requirements for support of ubiquitous sensor network (USN) applications and services in the NGN environment
Y.2026: Functional requirements and architecture of the next generation network for support of ubiquitous sensor network applications and services
Y.2222: Sensor control networks and related applications in a next generation network environment
22
ITU-T Recommendation relating to IoT/WoT Services using tag-based identification
Y.2213: NGN service requirements and capabilities for network aspects of applications and services using tag-based identification
Y.2016: Functional requirements and architecture of the NGN for applications and services using tag-based identification
Machine-oriented communications Y.2061: Requirements for the support of machine-oriented communication
applications in the next generation network environment 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
23
WoT Requirements General Requirements
WoT사용자정의 Web을통하여 Device를액세스하는모든대상 서비스개발자/공급자, 응용사용자, 디바이스개발자/공급자등
상호호환성 네트워크와 OS 등에관계없이Web을통한접근성제공
Location Transparency 디바이스위치와관계없이어느장소에서나 web액세스가가능
Functional Requirements Web 인터페이스의등록및발견을위한서비스프로파일관리 WoT서비스의제어및관리 (액세스제어및보안포함) Resource ID management지원 (디바이스뿐만아니라 agent포함)
24
Conceptual model of the web of things
25
. . .
Y.2063(12)_F8-1
. . .Web of things broker
Controlservice
Sensorservice
WebMash-upservice
Mash-upservice
Mash-upservice
Mash-upservice
TV controlserviceMonitoring
service Data cloudservice
Wi-Fidevice
Bluetoothdevice
Constrained devices
Bluetoothagent
Zigbeeagent
Fully-fledged devices
Applications
Agent-n
Light controlservice
IP phoneservice
Mash-upservice
Wi-Fiagent
Monitoringservice
Zigbeedevice
Zigbeedevice
(ref.) ITU-T Y.2063
WoT deployment model for fully-fledged devices
26
Y.2063(12)_F8-2
Fully-fledgeddevice
(HTTP)
(HTTP)(HTTP orproprietaryinterface) WoT
broker (HTTP)
(HTTP) (HTTP)
ApplicationMash-upservice
WoT service
Agent
Mash-up service
WoT brokerFully-fledged device
Web
Application
(ref.) ITU-T Y.2063
WoT deployment model for constrained devices
27
장비
장비Applications
Mash-upservice
(HTTP)(HTTP)
Applicationsapplication
(HTTP)
ApplicationWoT
BrokerConstrained
Devices
(Proprietary interface)
Constrained device
Agent
WoT broker
WoT Service Mash‐up service
Web (ref.) ITU-T Y.2063
Web of Things Architecture
28
Applications
WoT
Broker Service Layer
Adaptation Layer
Physical Layer
Mash‐up service WoT service WoT Agent
Constrained device
`
Web
Web service
Composite WoT service
Full‐fledged device
WoT Functions Service profile management functions
Type of services, service category name, service name Service control, composition, access functions
service registration, authentication, authorization, accounting, etc. Resource management functions
Agent control, registration, profile management (type, location, status, network ID, device ID), etc.
identifiers of resources (e.g., resource ID, agent ID)
29
Use cases
30Y.2063(12)_FI.1
http://home.tempoture.person/myhome‐Temp
Web‐based home control service
Heating Rice cooking
TV on/off Cleaning
Light controlTemperaturemonitoring
http://myhome.wot.com/home1HOME AUTO
Heating
Hometemperature
control service
Cooling
Temperaturemonitoring
Homecleaning
Homeautomation
service
TV on/off
Rice cooking
Light control
Mash-up service
Heating
H omet e mp e ra t u re
c o n t rol s e rv ic e
Cooling
Temperaturemonitoring
Homecleaning
Homeautomationservice
TV on/off
Rice cooking
Light control
Web adaptionWoT agentfor Wi-Fi
WoT agentfor Zigbee
WoT agent for Bluetooth
Heatingservice
Coolingservice
Cookingservice
Temperaturemonitoring
service
Cleaningservice
WoT service
Light controlservice
Temperaturesensor
Air-conditioner
Heater
Light controller
TV
Rice cooker
Robot cleaner
[WoT
bro
ker]
(ref.) ITU-T Y.2063
주요표준화세력
ITU-T, ITU-R 네트워크, 통신기반응용측면, 주파수할당
ISO/IEC Energy/Smartgrid, Health, Transportation, etc.
W3C/OASIS IEEE GS1/EPCglobal oneM2M OGC (Open Geospatial Consortium)
32
WoT표준화쟁점항목 Naming, Addressing 및 Identification 이슈 Data format및 Device API 이슈 Security 및 Privacy 이슈통신프로토콜이슈
기타 3D 공간정보
33
Naming, Addressing 및 Identification 이슈
산업유형에따른분류 통신및인터넷산업
Network interface ID (IPv4/v6, MAC, EUI-64, etc.), User ID (E.164), 응용ID (Email address, SNS id, etc.)
도시, 교통, 의료, 서적, 물류, 에너지산업 각자의분류체계를가지고있음.
정보저장및검색방식에따른분류 도시의지리적위치
자료분류체계에따른상대적위치
의료지식의분류체계에따른기록
지식의유형에따른분류 메타데이타유형 (비디오, 책, 파일등지식의상관관계에따른) 데이터포맷에따른 Index 및 annotation 체계
34
Technical Issues for Web-based Identification Web-based identification
URI/URL/URN DNS with device information Communication information: Email, SMS/MMS, Call id, etc.
Device information including metadata Device name, product code, serial no., location, and time, etc.
aligned with Electric Product Code like EPCglobal
Events information system level (on/off), status, date and time, etc.
Application information Query, discovery, identify, initiate, create, and terminate, etc.
Security information security code
35
Identity Management Processing
37
User Id:GDHong-Korea-
Man:LGilDongHong-19yy-mm-dd
- Certified by UN -
User ID Customer ID
Family 1
Family 2
Family 3
Family 4
MobilePhone Nr
Fixed Phone Nr
WiFiWiBro
Id
Cable/IPTV
Id
InternetId
Service ID
Line ID
E.164 ID
MAC ID
ATM/Ethernet ID
IP Address
TCP/UDP Port ID
Session ID
Media ID
Provider ID
Content Owner ID
Comm. ID
Identities in the Future Web of Things – 1 Identities as the end-point of communications
38
Data Format및 Device API 이슈 HTML5 기반
XML/RDF, HTTP, SOAP/RESTful, etc.핵심은 Data 및Metadata Format
Media object and media resource model Media Ontology, Media Annotation File Format, Microformat, RSS Device Data Format for Mashup ?
Web기반 open API효과 Open, Auto-configurable, and future flexible But, Securable and manageable is in question ?
40
WoT보안표준이슈 응용유형별단계별접근이필요
모든산업분야에서동시다발적으로진행되기때문에비즈니스요구사항을만족하는수준에따라단계적접근
초기공공, 오락,및교육등보안이필요없는마켓에서시작, 이후Niche Market으로폐쇄된 B2B 시장 (의료, 에너지등) 확대
WoT기기에 Security 탑재는초기비용감당이어려움 보안이필요없는초기 public공공마켓에한정 (공공, 교육등) 아니면 walled garden이나 B2B market에서시작
통신사업자의 Security 환경이용 통신사업자가제공하는 security 환경 (authentication, encryption,
billing, accounting, integrity verification 등) 단, 사용자보호차원에서최소한의규제가중요
41
Digital Rights Management Issue for IPTV
DRM Agent 1
Rights Issuer
unprotectedcontent “unprotected”
content
Display Device
Keys for an asset are specific to a subscription
Asset Owner
Asset Provider
rightsdefinition
keys(either direction)
request or distribute license AAA /Payment
rights request or delivery
purchase
DRM Agent 1
protectedcontent
request or distribute license
UserDisplay Device
“unprotected”content
통신프로토콜이슈
Location management 및Mobility이슈 QoS (delay, loss) 및 Availability 이슈 OAM 및 Emergency notification 이슈 E2E, P2P 및 Group communication 이슈 Short Range Physical Protocol
short range wireless communications, bluetooth, zigbee etc. MAC 및 Adaptation Protocols
Server access protocol to monitor, diagnose, authenticate, and upgrade M2M devices over such networks
Reduce collisions and provides re-transmission New terminal classes for M2M devices should be defined
44
IoT/M2M/WoT 관련국제표준 ITU-T, ITU-R ISO/IEC CEN OMA ETSI YRP ECMA GSIFI TIA GSM MSTF
48
GS1/EPCglobal OGC IEEE oneM2M W3C/OASIS Open IoT (eclipse)
Dr. Friedbert BerensFBConsulting Sarl, Luxembourg
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
49
Global Partners Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
50
Scope & Objectives• To develop: Global M2M end-to-end specifications -
using common use cases and architecture principles across multiple M2M applications to connect M2M devices with application servers worldwide with an access independent view of end-to-end services
• To define: Service Layer platform with high level / detailed service architecture including:- Protocols/APIs/standard objects (open interfaces & protocols)- Interoperability, test and conformance specifications - Common use cases, terminal/module aspects- Service Layer interfaces/APIs between:
– Application and Service Layers – Service Layer and communication functions – Security and privacy aspects - authentication, encryption, integrity verification
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
51
Vision:Interconnecting the Internet of Things;
Connecting the Un-connected
Underlying protocols
oneM2MOther M2M protocol
Hybrid protocol App
oneM2M protocol
Other M2M
protocolApp
oneM2M native App
Underlying protocol
Underlying protocol
IoTDevice
IoTDevice
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
52
Horizontal Platform Vision
Local NW
Pipe (vertical):1 Application, 1 NW,
1 (or few) type of Device
BusinessApplication
Device
CommunicationNetwork (mobile, fixed,
Powerline ..)
Gateway
Horizontal (based on common Layer)
Applications share common infrastructure, environments and network elements
CommunicationNetwork 1
CommunicationNetwork 2
Local NW
Device Device Device Device
Common Application Infrastructure/Service layer
GatewayIP
BusinessApplication #1
BusinessApplication #2
BusinessApplication #n
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
53
oneM2M simplified Architecture
AE AE AE
CSE CSE CSE
M2M Applications
M2M Service layer
Underlying Transport
Mca Mca Mca
Mcc Mcc
Mcn McnMcn Mcn
NSE NSENetwork Service Entity
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
54
oneM2M Common Service Functions
Ref: oneM2M TS: Functional Architecture
CSE is composed of Common Service Functions (CSF):
•AID – Addressing and Identification•SEC – Security•SMG – Session Management•SCA – Service Charging and Accounting•DMR Data Management Repository•DMR – Data Management Repository•CMDH – Communication Management/Delivery Handling•DIS – Discovery•LOC – Location•REG – Registration•SUB – Subscription Notification•NSE – Network Service Exposure•GMG – Group Management
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
55
oneM2M Organization
Steering Committee(Partners)
Technical Plenary(Members / Partners)
ProtocolsWG3
RequirementsWG1
ArchitectureWG2
SecurityWG4
Management,Abstraction,
Semantics WG5
Legal
Methods &Processes
Method of Work
Finance
MARCOM
WorkProgramme
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
56
OPEN PROTOCOLS FOR AN OPEN, INTEROPERABLE INTERNET OF
THINGSDr Carol Cosgrove-Sacks
Senior Advisor on International Standards Policy
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
57
• Open standards for the global info society• 5,000+ experts in 70+ tech committees
FOR AN OPENFOR AN OPENOPEN
PROTOCOLSOPEN
PROTOCOLSINTEROPERABLE INTERNET OF
THINGS
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
58
Fast open standards groups ... and solid open source projects ...
work together very well
Many open standards projects are robustly supported by free & open
source software.
Web standard FOSS browsers
Identity standard FOSS toolkits
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
59
Giant ecologies can grow from open projects, promoting widespread use and adaptation.
One open standard (UBL for e‐invoicing) generates many local profiles, regional public projects and open source tools. (7)
Fast open standards groups ... and solid open source projects ...
work together very wellExtracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
60
Giant ecologies can grow from open projects, promoting widespread use and adaptation.This works in the Internet of Things as well.
The OASIS MQTT TC standardizes this industry protocol for lightweight sensor and device coordination, complemented and
informed by Eclipse's open source implementation project. The two projects
feed each other improvements.
Fast open standards groups ... and solid open source projects ...
work together very wellExtracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
61
Key STANDARDS emerging for an Open Internet of Things
Lightweight protocols for devices to work together, communicate
OASIS MQTT, MQTT‐SN OASIS SmartGrid projects
Unique and extensible identifiers for all those billions of devices
Multiple new projects, XRI, UUIDs, etc.
Demand for API access and interoperability
SOA/Cloud orchestration and API standardization (AMQP, MQTT, OData)
Cybersecurity KMIP, SAML, XACML/JSON, PKCS11, CloudAuthZ
Privacy and Policy PMRM, PbDSE, and Personal Data Stores
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
62
OGCWhere the Internet of Things
touches Location/Space
Bart De Lathouwer,OGC, bdelathouwer [at] opengeospatial.org
Presentation based on work from SWE DWG, Dr. Mike Botts, Dr. Ingo Simonis, Dr. Arne Bröring and SW for IoT by Dr. Steve Liang
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
63
The Open Geospatial Consortium
Not-for-profit, international voluntary consensus standards organization; leading development of geospatial standards
• Founded in 1994.
• 480+ members and growing
• 33 “core” standards
• 15 extensions/profiles
• Hundreds of product implementations
• Alliances and collaborative activities with ISO and many other SDO’s
Commercial41%
Government18%
NGO10%
Research7%
University24%
64
64
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Sensor Web Desires Quickly discover sensors and sensor data (secure or public)
that can meet my needs – location, observables, quality, ability to task
Obtain sensor information in a standard encoding that is understandable by me and my software
Readily access sensor observations in a common manner, and in a form specific to my needs
Task sensors, when possible, to meet my specific needs
Subscribe to and receive alerts when a sensor measures a particular phenomenon
66
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Building Blocks: OGC SWE
Registries & Dictionaries
SensorDescription Language
PhenomenonDescription Language
Services
Observation Tasking Alerting Analysis
SensorML O&M
SOS SPS SAS WNS
CS-W
67
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Sensors Everywhere(Things or Devices)
50 billions Internet-connected things by 2020
OGC SWE-IoT Focus
68
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Why OGC ? Every thing has a location Location information needs to be carefully described. e.g., outdoor, indoor, geometry, topology, semantics, sensor
space, etc. OGC Sensor Web Enablement is widely adopted and
implemented e.g., OGC/ISO Observation and Measurements, OGC SensorML,
OGC Sensor Observation Service, etc. The OGC SensorThings API is built based on the OGC SWE
69
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Example: OGC CityGML
– Semantic 3D city and building models provide• the geometry and• a thematic differentiation of the indoor areas
(at least separation in building parts, levels and rooms)
Describe the location of a THING in a building
70
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Timeline
201420142013201320112011 20122012
Finalization and signed-off standard
Draft APIJanuary 2013
OGC IoT WorkshopBrussels
Sensors4 IoT ad hoc meeting March 2012 in
Austin, TX
Sensors4 IoT first meeting
June 2012 in Exeter UK
Use cases for Public ReviewOctober 2012
Draft API v.0.2March 2013
We are here!!
Draft SpecFebruary 2014
71
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)
Conclusions OGC and IoT
Mature SWE stack SWE Implementation Maturity ER
CityGML, IndoorGML, ARML SW for IoT
OGC SensorThings API Link to the newly formed Health DWG
72
Extracted FromITU Workshop on the “Internet of Things -Trend and Challenges in Standardization”
(Geneva, Switzerland, 18 February 2014)