GS1/Oliot ONS/DS and Next

Jun. 25, 2014
Auto-ID Labs, KAIST
Dept. of Computer Science, KAIST
GS1/Oliot Object Name Service &
Discovery Service
Kiwoong Kwon
kiwoong@kaist.ac.kr, http://oliot.org, http://autoidlab.kaist.ac.kr, http://resl.kaist.ac.kr http://autoidlabs.org http://gs1.org

© Auto-ID Lab Korea / KAIST
Slide 2
 Object Name Service (ONS)
– Motivation
– Architecture for ONS
– Formal specification
– Federated ONS
– Future ONS for IoT
 Discovery Service (DS)
– Motivation
– Architecture for DS
– Oliot DS
– Architecture for Oliot DS
– Future DS for IoT
Contents

Slide 3
Motivation for ONS (1)
Most medical devices in US should include an unique device
identifier (UDI) ..

Slide 4
Company?
Model No?
Googling?
Contact?
Current situation ..
I want to find
instruction sheets for
my medical devices.

Slide 5
I can get information
of medical devices
using reader !!
If a reader reads ID tags attached to medical devices ..
But, I cannot
understand what
does it mean .. An ID tag
cannot contain
large data ..
01010011
00010101
01010010

Slide 6
Is there any service to
find where the instruction
sheets for medical
devices are?
So, how can I find the instruction sheets for medical devices?
That is
Object Name Service
(ONS)

Slide 7
Concept of ONS (1)
Manual Service
Object Name Service
(ONS)
manual
html
epcis
…

Slide 8
Concept of ONS (2)
Manual Service
Object Name Service
(ONS)
If all things can get GS1 ID ..

Slide 9
Passive Tags
(e.g., passive
tags, barcode)
Sensor & Actuator Networks
(e.g., ZigBee, 6LoWPAN, Mobile phone, BLE,
AllJoyn, lwM2M etc.)
Active Tags (e.g.,
Wireless ID and Sensor
Networks)
RFID Middleware
LLRP LLRP Sensor & actuator protocols Sensor & actuator protocols
Domain-specific capturing application
Domain-specific accessing applications
Sensor Interface
Sensor interface
EPC Information Service
(static and dynamic information)
ALE
Actuation Interface
Sensor & Actuator Middleware
Object
Name
Service
Discovery
Service
ZigBee
6LoWPAN/
CoAP
MQTT
Web
service-*
REST
Other
Comm.
RFID stream processing
Logical RFID
reader
Reader
Management
Sensor stream
processing
Sensor & actuator
Management
ID-Sensor stream
processing
 Object Name Service (ONS)
– Service to lookup static information about the given GS1 Identification keys using the
Internet’s existing Domain Name System (DNS) protocol
ONS in Oliot
ONS lookup for static
information of things
(e.g., product info
services)

Slide 10
ONS Application ONS Client
EPCIS Server
ONS Peer Roots
(1)
(2)
(3)
(6) (7)
Local caching
nameserver
(5)
(8)
(4)
ONS Architecture
Federated ONS Infrastructure
GS1 ID AUS FQDN
NAPTR records

Slide 11
 Extract the desired GS1 ID Key type and GS1 ID Key from the
sequence of data
– (00)306141417782246356(02)50614141322607(37)20
Type: GTIN (02)
Key: 50614141322607
 AUS format
– language code | country code | type | key
 AUS conversion example
– GDTI 0614141665815 with serial 999888777, English service in Canada
AUS: en|ca|gdti|0614141665815
ONS Application
GS1 ID AUS
Conversion to Application Unique String
(AUS)

Slide 12
 Conversion from AUS into FQDN
Conversion to Fully Qualified Domain
Name (FQDN)
AUS
FQDN
||gtin|00614141322602
0 0614141 32260 2
indicator company prefix itemref check
00614141322602 Strip checksum
0.061414132260 Hold indicator
0.062231414160 Revers all remaining characters
0.0.6.2.2.3.1.4.1.4.1.6.0. Append a ‘.’
0.0.6.2.2.3.1.4.1.4.1.6.0.gtin Append ID key type
0.0.6.2.2.3.1.4.1.4.1.6.0.gtin.gs1.id
0.0.6.2.2.3.1.4.1.4.1.6.0.gtin.gs1.id.onsepc.com
Append ‘.gs1.id.’
Append peer root
ONS Application ONS Client
AUS FQDN

Slide 13
 ONS Query
– Query for ONS Query Responses for the Fully Qualified Domain Name (FQDN)
 ONS Query Response
– A set of Naming Authority PoinTeR (NAPTR) Records
ONS Formal Specification
- ONS Query Responses
ONS Query
ONS Query response
ONS Client
Local caching
nameserver
ONS Peer Roots
0.0.6.2.2.3.1.4.1.4.1.6.0.gtin.gs1.id.onsepc.com

Slide 14
 Nameserver (NS) delegation
– Desired name servers exists below current ONS Peer Root
 Delegation name (DNAME) delegation
– Desired name servers exists in another ONS Peer Root, not current ONS Peer Root
– Using the GS1 prefix (last three digits), identify where the query is destined.
Federated ONS
- Delegation
GS1 Prefix Domain Country
1.6.0 onsepc.com America
0.8.8 onsepc.kr Korea
0.0.3 onsepc.fr France
Korean
ONS Peer Root
American
ONS Peer Root
French
ONS Peer Root
ONS Server
In Korea
ONS Server
In America
ONS Server
In France
NS
Delegation
DNAME
Delegation
~.1.4.1.4.X.X.X.gtin.gs1.id.onsepc.XXX

Slide 15
ONS peer Roots
Local system
ONS
Application
ONS
Client
EPCIS Server
ONS
Query
ONS
Response
Korean Root
onsepc.kr
ONS Server
in Korea
American Root
onsepc.com
Local caching
nameserver
ONS Server
in America
Federated ONS
- NS Delegation
1
2
3
4
5 6
~.0.8.8.~.onsepc.kr.
Resolution
Success

Slide 16
ONS peer Roots
Local system
ONS
Application
ONS
Client
EPCIS Server
ONS
Query
ONS
Response
Korean Root
onsepc.kr
ONS Server
in Korea
American Root
onsepc.com
Local caching
nameserver
ONS Server
in America
Federated ONS
- DNAME Delegation
1
2 3
4
5
6 7
Resolution
Success

Slide 17
Globally Federated ONS Peer Roots
Deployment Plan for Federated ONS
Korea
JapanChina
Taiwan
Australia
USA
Brazil
Switzerland
England
Sunchon
Univ.
GS1 Korea
Samsung
KAIST
Local ONS Name Servers

Slide 18
Future ONS with GS1 for IoT
Desired Service
…
ONS

Slide 19
Motivation for Discovery Service (1)
Object Name Service
(ONS)
Is ONS enough to
find dynamic
information for my
things?

Slide 20
Motivation for Discovery Service (2)
Manufacturer EPCIS EPCIS B (Store)ONS EPCIS A
Retailer
I found faults for all
same typed
products
I don’t know!
Give me list of
EPCISs related
to given GS1 ID?

Slide 21
Concept of Discovery Service
Manufacturer EPCIS EPCIS B (Store)ONS EPCIS A
Retailer
Discovery Service
I know it !Give me list of
EPCISs related
to given GS1 ID?

Slide 22
Passive Tags
(e.g., passive
tags, barcode)
Sensor & Actuator Networks
(e.g., ZigBee, 6LoWPAN, Mobile phone, BLE,
AllJoyn, lwM2M etc.)
Active Tags (e.g.,
Wireless ID and Sensor
Networks)
RFID Middleware
LLRP LLRP Sensor & actuator protocols Sensor & actuator protocols
Domain-specific capturing application
Domain-specific accessing applications
Sensor Interface
Sensor interface
EPC Information Service
(static and dynamic information)
ALE
Actuation Interface
Sensor & Actuator Middleware
Object
Name
Service
Discovery
Service
ZigBee
6LoWPAN/
CoAP
MQTT
Web
service-*
REST
Other
Comm.
RFID stream processing
Logical RFID
reader
Reader
Management
Sensor stream
processing
Sensor & actuator
Management
ID-Sensor stream
processing
• Discovery Service (DS)
– The service to lookup dynamic information about the given GS1
Identification keys and provide dynamic information to DS client
Discovery Service in Oliot
DS lookup for dynamic
information of each
individual thing (e.g.,
historic locations of
things)

Slide 23
Discovery Service
Manufacturer EPCISONS EPCIS A
Client
EPCIS B
(1)(2) (3)
(5)
(4)
Discovery Service Architecture
Event Registration
GS1 ID
Service lists
DS Query
DS Response

Slide 24
 Event Registration
– Contents
 Who? GS1 ID
 When? Timestamp
 Where? EPCIS Address
Event Registration
Discovery Service
Manufacturer EPCIS EPCIS A EPCIS B
Event Registration

Slide 25
 DS Query
– Contents
 GS1 ID
 Time period
– Beginning of the time period
– End of the time period
Discovery Service Access
Discovery Service
Client
 DS Response
– Contents
 GS1 ID
 A set of EPCIS address records
DS
Query/Response

Slide 26
 Current DS is tailored to a supply chain in B2B application
– B2C should be considered in IoT.
 How to satisfy client’s demand using DS?
– Client may want to know the real locations of the stores selling the desired
products near his current location
Discovery Service from an aspect of B2C
Client
I want to buy more.
Where can I buy them?

Slide 27
Oliot Discovery Service
1km
 Oliot Discovery Service
– Find the real physical locations of the desired GS1 products inner distance
radius circle from current location

Slide 28
Oliot Discovery Service Architecture
Discovery Service
Manufacturer EPCISONS EPCIS A
Client
EPCIS B
(1)(2) (3)
(5)
(4)

Slide 29
Message formats for Oliot Discovery
Service
• JSON documentation is object type for Elasticsearch
• Event Registration
{“ID":“urn:epc:id:sgtin:0057000.123780.7788",
"EPCIS":“http://[2002:8ff8:3853::8ff8:3853]/epcis-repository-0.4.3/query",
"timestamp":"20140509003200",
"location":{"lat":36.321512,"lon":127.246547}}
• Geo-location Search
{"query":{"match":{
“ID":{"query":"urn:epc:id:sgtin:0057000.123780.7788","type":"phrase"}}},
"filter":{"and":{"filters":[{"geo_distance":{
"geo.location":{"lat":36.350412,"lon":127.38454700000001},
"distance":30,"unit":"km"}},
{"range":{"timestamp":{
"from":"20130910000000",
"to":"20141030165000",
"include_lower":true,"include_upper":true}}}]}}}
Current location
Size of the
distance radius
circle

Slide 30
Current UI for Oliot Discovery Service

Slide 31
Globally
Distributed DS
Future DS with GS1 for IoT
…
EPCISes
EPISList

Slide 32
IoT Scenario with ONS and DS
KAIST
Discovery Service
ONS
Client
My lost thing
AddressofDS

Slide 33
Q & A

Slide 34
 EPCglobal Object Name Service (ONS) 1.0.1
– http://www.gs1.org/gsmp/kc/epcglobal/ons/ons_1_0_1-standard-
20080529.pdf
 GS1 Object Name Service (ONS) Version 2.0.1
– http://www.gs1.org/gsmp/kc/epcglobal/ons/ons_1_0_1-standard-
20080529.pdf
 Federated ONS Architecture for the Internet of Things - A
Functional Evaluation
– http://www.caad.arch.ethz.ch/noolab/files/external/conferences/IoT2010_pr
oceedings/pdf/Demo/D4.pdf
 Discovery Services in the EPC Network
– http://cdn.intechopen.com/pdfs-wm/18103.pdf
 GS1 Discovery Service Standard
– http://www.gs1.org/gsmp/kc/epcglobal/discovery
References

Slide 35
Appendix

Slide 36
ONS peer Roots
Local system
ONS
Application
ONS
Client
EPCIS Server
ONS
Query
ONS
Response
Korean Root
onsepc.kr
ONS Server
in Korea
American Root
onsepc.com
ONS server
in French
French Root
onsep.fr
Local caching
nameserver
ONS Server
in America
1
2
3
Resolution
Failure
Federated ONS
- GS1 Prefix Updated Case : Not Synchronized

Slide 37
ONS peer Roots
Local system
ONS
Application
ONS
Client
EPCIS Server
ONS
Query
ONS
Response
Korean Root
onsepc.kr
ONS Server
in Korea
American Root
onsepc.com
ONS server
in French
French Root
onsep.fr
Local caching
nameserver
ONS Server
in America
1
2
3
5
6 7
4
0.0.3 onsepc.fr France
Resolution
Success
Federated ONS
- GS1 Prefix Updated Case : Synchronized

GS1/Oliot ONS/DS and Next

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (19)

En vedette

En vedette (19)

Similaire à GS1/Oliot ONS/DS and Next

Similaire à GS1/Oliot ONS/DS and Next (20)

Plus de Daeyoung Kim

Plus de Daeyoung Kim (20)

Dernier

Dernier (20)

GS1/Oliot ONS/DS and Next