forked from w3c/wot-usecases
-
Notifications
You must be signed in to change notification settings - Fork 3
/
index.html
6906 lines (5533 loc) · 253 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<link rel="stylesheet" href="tablestyle.css">
<title>Web of Things (WoT): Use Cases and Requirements</title>
<script class="remove" src="https://www.w3.org/Tools/respec/respec-w3c"></script>
<script class="remove">
var respecConfig = {
lint: {
"no-headingless-sections": false,
},
specStatus: "ED",
noRecTrack: "true",
maxTocLevel: 6,
processVersion: 2019,
shortName: "wot-use-cases-requirements",
copyrightStart: 2020,
group: "ig/wot",
edDraftURI: "https://w3c.github.io/wot-usecases/",
githubAPI: "https://api.github.com/repos/w3c/wot-usecases/",
issueBase: "https://www.github.com/w3c/wot-usecases/issues",
editors: [{
name: "Michael Lagally",
w3cid: "47166",
company: "Oracle Corp.",
companyURL: "https://www.oracle.com/"
},
{
name: "Michael McCool",
w3cid: "93137",
company: "Intel Corp.",
companyURL: "https://www.intel.com/"
},
{
name: "Ryuichi Matsukura",
w3cid: "64284",
company: "Fujitsu Ltd.",
companyURL: "https://www.fujitsu.com/"
},
{
name: "Tomoaki Mizushima",
w3cid: "98915",
company: "Internet Research Institute, Inc.",
companyURL: "https://www.iri.co.jp/"
}
],
otherLinks: [
{
key: "Contributors",
data: [{
value: "In the GitHub repository",
href: "https://github.com/w3c/wot-security/graphs/contributors"
}]
}, {
key: "Repository",
data: [{
value: "We are on GitHub",
href: "https://github.com/w3c/wot-usecases/"
}, {
value: "File a bug",
href: "https://github.com/w3c/wot-usecases/issues"
}, {
value: "Contribute",
href: "https://github.com/w3c/wot-usecases/pulls"
}]
}],
localBiblio: {
"JSON-SCHEMA": {
title: "JSON Schema Validation: A Vocabulary for Structural Validation of JSON",
href: "https://tools.ietf.org/html/draft-handrews-json-schema-validation-01",
authors: ["Austin Wright", "Henry Andrews", "Geraint Luff"],
status: "Internet-Draft",
date: "19 March 2018",
publisher: "IETF"
},
"ISO-6709": {
title: "ISO-6709:2008 : Standard representation of geographic point location by coordinates",
href: "https://www.iso.org/standard/39242.html",
status: "Published",
date: "2008-07",
publisher: "ISO"
},
"Hybridcast": {
title: "Hybridcast",
href: "...",
authors: ["..."],
status: "...",
date: "..",
publisher: "..."
},
"NMEA": {
title: "National Marine Electronics Association",
href: "https://www.nmea.org",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"WGS84": {
title: "WGS84",
href: "https://en.wikipedia.org/wiki/World_Geodetic_System",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"Basic Geo Vocabulary": {
title: "W3C Semantic Web Interest Group",
href: "https://www.w3.org/2003/01/geo/",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"W3C Geolocalization API": {
title: "Geolocation API Specification 2nd Edition",
href: "https://www.w3.org/TR/geolocation-API/",
authors: ["Andrei Popescu"],
status: "Published",
date: "8 Nov 2016",
publisher: "W3C"
},
"Open Geospatial Consortium": {
title: "Open Geospatial Consortium",
href: "http://docs.opengeospatial.org/as/18-005r4/18-005r4.html",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"ISO19111": {
title: "ISO19111",
href: "https://www.iso.org/standard/74039.html",
authors: ["..."],
status: "Published",
date: "Jan 2019",
publisher: "ISO"
},
"SSN": {
title: "Semantic Sensor Network Ontology",
href: "https://www.w3.org/TR/vocab-ssn/",
authors: [
"Armin Haller",
"Krzysztof Janowicz",
"Simon Cox",
"Danh Le Phuoc",
"Kerry Taylor",
"Maxime Lefrançois"
],
status: "Published",
date: "19 Oct 2017",
publisher: "W3C"
},
"Timestamps": {
title: "Timestamps",
href: "https://w3c.github.io/hr-time/#dom-domhighrestimestamp",
authors: ["Ilya Grigorik"],
status: "...",
date: "06 Oct 2020",
publisher: "W3C"
},
"MMI UC3.1": {
title: "MMI UC3.1",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"MMI UC3.2": {
title: "MMI UC3.2",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"ICE F2761-09(2013)": {
title: "ICE F2761-09(2013)",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"OpenICE": {
title: "OpenICE",
href: "https://www.openice.info",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"MDIRA": {
title: "MDIRA",
href: "https://secwww.jhuapl.edu/mdira/documents",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"MQTT": {
title: "MQTT Version 3.1.1 Plus Errata 01",
href: "http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html",
authors: ["Andrew Banks", "Rahul Gupta"],
status: "...",
date: "December 2015",
publisher: "OASIS Standard"
},
"OPC UA": {
title: "OPC Unified Architecture",
href: "https://opcfoundation.org/about/opc-technologies/opc-ua/",
authors: ["..."],
status: "...",
date: "...",
publisher: "OPC"
},
"BACnet": {
title: "BACnet",
href: "http://www.bacnet.org",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"CoAP": {
title: "The Constrained Application Protocol (CoAP)",
href: "https://tools.ietf.org/html/rfc7252",
authors: [
"Z. Shelby",
"K. Hartke",
"C. Bormann"
],
status: "Published",
date: "June 2014",
publisher: "IETF"
},
"MMI UC5.1": {
title: "MMI UC5.1",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"MMI UC5.2": {
title: "MMI UC5.2",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
".MMI UC1.1": {
title: "MMI UC1.1",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"MMI UC1.2": {
title: "MMI UC1.2",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"MMI UC2.1": {
title: "MMI UC2.1",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"IEC 61850": {
title: "IEC 61850",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"IEEE 1574": {
title: "IEEE 1574",
href: "...",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"KNX": {
title: "KNX",
href: "https://www.knx.org/knx-en/for-professionals/index.php",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"Modbus": {
title: "Modbus",
href: "https://modbus.org",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"OGC Sensor Things": {
title: "OGC Sensor Things API",
href: "https://www.ogc.org/standards/sensorthings",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"OneM2M": {
title: "OneM2M",
href: "https://www.onem2m.org",
authors: ["..."],
status: "...",
date: "...",
publisher: "..."
},
"LWM2M": {
title: "Lightweight Machine to Machine Technical Specification: Core",
href: "http://openmobilealliance.org/release/LightweightM2M/V1_1-20180710-A/OMA-TS-LightweightM2M_Core-V1_1-20180710-A.pdf",
authors: ["..."],
status: "...",
date: "Aug 2018",
publisher: "OMA SpecWorks."
},
"OCF": {
title: "OCF Core Specification",
href: "https://openconnectivity.org/developer/specifications",
authors: ["..."],
status: "...",
date: "April 2019",
publisher: "Open Connectivity Foundation"
},
}
};
</script>
</head>
<body>
<section id="abstract">
<p>
The Web of Things is applicable to multiple IoT domains,
including Smart Home, Industrial, Smart City, Retail, and Health
applications, where usage of the W3C WoT standards can simplify the
development of IoT systems that combine devices from multiple vendors
and ecosystems.
During the last charter period of the WoT Working Group several
specifications were developed to address requirements for
these domains.
</p>
<p>
This Use Case and Requirements Document is created
to collect new IoT use cases from various domains
that have been contributed by various stakeholders.
These serve as a baseline for identifying requirements
for the standardisation work in the W3C WoT groups.
</p>
</section>
<section id="sotd">
</section>
<section id="intro">
<h2>Introduction</h2>
<p>
The World Wide Web Consortium (W3C) has published the Web of Things
(WoT) Architecture and Web of Things (WoT) Thing Description (TD) as
official W3C Recommendations in May 2020. These specifications enable
easy integration across Internet of Things platforms and applications.
</p>
<p>The W3C Web of Thing Architecture [[wot-architecture]] defines an
abstract architecture, the WoT Thing Description [[wot-thing-description]]
defines a format to describes a broad spectrum of very different devices,
which may be connected over various protocols.
</p>
<p>
During the inception phase of the WoT 1.0 specifications in 2017-2018
the WoT IG collected use cases and requirements to enable
interoperability of Internet of Things (IoT)
services on a worldwide basis.
Thes released specifications have been created to address the
use cases and requirements for the first version of the WoT specifications,
which are documented in <a href="https://w3c.github.io/wot/ucr-doc/">
https://w3c.github.io/wot/ucr-doc/</a>
<p>
The present document gathers and describes new use cases and requirements
for future standardisation work in the WoT standard.
</p>
<section id="document-status" class="ednote" Disclaimer:>
<p> This document is an early work in progress and is currently under significant editorial and content rework.
It is currently an aggregation of use case descriptions that were contributed in a different
file format (Markdown)</p>
<p>Before it can be published as a IG note,
it will undergo major restructuring and cleanup in due course.
</section>
<section id="structure" class="ednote">
TODO: Describe document structure, template headings, ...
</section>
<section id="domains" class="ednote">
TODO: Give a domain overview, explain different horizontals and verticals.
</section>
</section>
<section id="conformance"></section>
<section id="definitions">
<h2>Definitions: Terminology, Stakeholders and Actors</h2>
<section id="terminology">
<h2>Terminology</h2>
The present document uses the terminology as the WoT Architecture [[wot-architecture]].
<section id="new-terminology" class="ednote">TODO: Define additional terminology.</section>
</section>
<section id="stakeholders">
<h2>Stakeholders</h2>
<section id="stakeholders" class="ednote">TODO: Describe stakeholder roles and tasks.
</section>
<ul>
<li>device owners</li>
<li>device user</li>
<li>cloud provider</li>
<li>service provider</li>
<li>device manufacturer</li>
<li>gateway manufacturer</li>
<li>identity provider</li>
<li>directory service operator?</li>
</ul>
</section>
</section>
<section id="use-cases">
<h2>Application Domains and Use Cases</h2>
<!-- Categories of new use cases -->
<section id="retail">
<h2>Retail</h2>
<dl>
<dt>Submitter(s)</dt>
<dd>
David Ezell, Michael Lagally, Michael McCool
</dd>
<dt>Reviewer(s)</dt>
<dd>
</dd>
<dt>Tracker Issue ID</dt>
<dd>
</dd>
<dt>Category</dt>
<dd>
</dd>
<dt>Class</dt>
<dd>
</dd>
<dt>Status</dt>
<dd>
</dd>
<dt>Target Users</dt>
<dd>
Retailers, customers, suppliers.
</dd>
<dt>Motivation</dt>
<dd>
Integrating and interconnecting multiple devices into the common retail workflow
(i.e., transaction log) drastically improves retail business operations at multiple levels.
It brings operational visibility,including consumer behavior and environmental information,
that was not previously possible or viable in a meaningful way.
It drastically speeds up the process of root cause analysis of operational issues and
simplifies the work of retailers.
</dd>
<dt>Expected Devices</dt>
<dd>
Connected sensors, such as people counters, presence sensors, air quality, room ocupancy, door sensors.
Cloud services. Video analytics edge services.
</dd>
<dt>Expected Data</dt>
<dd>
Inventory data, supply chain status information, discrete sensor data or data streams.
</dd>
<dt>Dependencies</dt>
<dd>
tbd
</dd>
<dt>Description</dt>
<dd>
Falling costs of sensors, communications, and handling of very large volumes of data combined with cloud
computing enable retail business operations with increased operational efficiency, better customer
service,
and even increased revenue growth and return on investment.
Accurate forecasts allow retailers to coordinate demand-driven outcomes that deliver connected customer
interactions.
They drive optimal strategies in planning, increasing inventory productivity in retail supply chains,
decreasing operational costs and driving customer satisfaction from engagement, to sale, to fulfilment.
Understanding of store activity juxtaposed with traditional information streams can boost worker and
consumer safety,
comply better with work safety regulations, enhance system and site security, and improve worker
efficiency
by providing real-time visibility into worker status, location, and work environment.
</dd>
<dt>Variants</dt>
<dd>
<ul>
<li>Use edge computing, in particular video analytics, in combination with IoT devices to deliver an
enhanced
customer experience, better manage inventory, or otherwise improve the store workflow.</li>
</dd>
<dt>Security Considerations</dt>
<dd>
<ul>
<li>In retail, replay attacks can cause monetary loss, customers may be incorrectly charged or
over-charged.</li>
<li>To avoid replay attacks, "Things" should implement a sequence number for each message and digital
signature.</li>
<li>Servers ("Things" or "Cloud") should verify the signature and disallow for duplicated messages.</li>
<li>For "Things" relying on electronic payments, "Things" must comply with PCI-DSS requirements.</li>
<li>"Things" must never store credit card information.</li>
<li>Customer satisfaction and trust depends on availability, so attacks such as Denial-of-Service (DoS)
need to be prevented or mitigated.</li>
<li>To prevent DoS, implement "Things" with early DoS detection.</li>
<li>Have an automated DoS system that will notify the controlling unit of the problem.</li>
<li>Implement IP white list, that could be part of the DoS early detection system.</li>
<li>Make sure your network perimeter is defended with up to date firewall software.</li>
</ul>
</dd>
<dt>Privacy Considerations</dt>
<dd>
As a general rule, personal consumer information should not be stored.
That is especially true in the retail industry where a security breach could cause financial, reputation,
and brand damage.
If personal or information that can identify a consumer is to be stored,
it should be to conduct business and with the explicit acknowledgment of the consumer.
WoT vendors and integrators should always have a privacy policy and make it easily available.
By default, devices should adopt an opt-out policy.
That means, unless the consumer explicitly allowed for the data capture and storage, avoid doing it.
</dd>
<dt>Gaps</dt>
<dd>
<section id="todo-gaps-x" class="ednote">
TODO: Describe any gaps that are not addressed in the current WoT work
items.
</section>
</dd>
<dt>Existing standards</dt>
<dd>
<section id="todo-references-x" class="ednote">TODO: Provide links to relevant standards that
are relevant for this use case</section>
</section>
<section id="audio_video">
<h2>Audio/Video</h2>
<section id="media-information-references">
<h2>Media Use Case Information Bucket</h2>
<dl>
This section is not a full use case description. It is rather a collection of
thoughts and ideas to capture information and provide references and have a common discussion basis.
The intention is to trigger new ideas and collect them in a single document at this point.
The document is work in progress.
<dt>Submitter(s)</dt>
<dd>
</dd>
<dt>Reviewer(s)</dt>
<dd>
</dd>
<dt>Tracker Issue ID</dt>
<dd>
</dd>
<dt>Category</dt>
<dd>
</dd>
<dt>Class</dt>
<dd>
</dd>
<dt>Status</dt>
<dd>
</dd>
<dt>Target Users</dt>
<dd>
</dd>
<dt>Motivation</dt>
<dd>
</dd>
<dt>Expected Devices</dt>
<dd>
</dd>
<dt>Expected Data</dt>
<dd>
</dd>
<dt>Dependencies - Affected WoT deliverables and/or work items</dt>
<dd>
</dd>
<dt>Description</dt>
<dd>
<ul>
<li>Sync of media across different devices:</li>
<li>people in different homes watch the same content at the same time. Conversation about content.</li>
<li>Multi-room sync playback</li>
<li>Multi-camera angles </li>
<li>Voice control of a media playback device (integration of smart speakers from multiple vendors)
Describe proprietary (vendor specific) device control interfaces to control media playback on TV set.
(proprietary implementations exist, open protocol is proposed?)</li>
</ul>
</dd>
<dt>Variants</dt>
<dd>
</dd>
<dt>Gaps</dt>
<dd>
<section id="todo-gaps-1" class="ednote">
TODO: Provide links to relevant standards that are relevant for this use case</section>
</dd>
<dt>Existing standards & related information</dt>
<dd>
<section id="todo-references-x" class="ednote">TODO: Provide links to relevant standards that are
relevant for this use case.
<p>There are MANY TV standards and this would be a long list. Rather leave blank unless a very specific
standard provides more insight.</p>
</section>
</dd>
<dt>Comments</dt>
<dd>
Further information and resources:
<ul>
<li><a
href="https://www.w3.org/2011/webtv/wiki/images/d/d1/MediaTimedEventsInHybridcast_TPAC20190916.pdf">NHK
Hybridcast updates</a></li>
<li><a
href="https://www.w3.org/2011/webtv/wiki/images/d/d1/MediaTimedEventsInHybridcast_TPAC20190916.pdf">MediaTimedEvents
in Hybridcast</a></li>
<li><a href="https://2immerse.eu/motogp-at-home/">BC Moto GP at Home</a></li>
</ul>
</dd>
</dl>
</section>
<section id="nhk-device-tv-sync">
<h2>Home WoT devices work according to TV programs</h2>
<dl>
<dt>Submitter(s)</dt>
<dd>
Hiroki Endo,
Masaya Ikeo,
Shinya Abe,
Hiroshi Fujisawa
</dd>
<dt>Reviewer(s)</dt>
<dd>
</dd>
<dt>Tracker Issue ID</dt>
<dd>
</dd>
<dt>Category</dt>
<dd>
</dd>
<dt>Class</dt>
<dd>
</dd>
<dt>Status</dt>
<dd>
</dd>
<dt>Target Users</dt>
<dd>
Person watching TV, Broadcasters
</dd>
<dt>Motivation</dt>
<dd>
A lot of home devices, such as TV, cleaner, and home lighting, connect to an IP network.
When you watch a content program, these devices should coorperate for enhancing your expereence.
If the cleaning robot makes a loud noise while watching the TV program, it will hinder viewing.
Also, even if you set up the theater environment with smart lights, it is troublesome to operate it
yourself each time the TV program switches.
Therefore, by WoT device to operate in accordance with the TV program being viewed, thereby improving the
user experience.
WoT devices work according to TV programs:
<ul>
<li>Cleaning robot stops at an important situation,</li>
<li>Color of smart lights are changed according to TV programs,</li>
<li>Smart Mirror is notified that favorite TV show will start.</li>
</ul>
</dd>
<dt>Expected Devices</dt>
<dd>
<ul>
<li>Hybridcast TV</li>
<li>Hybridcast Connect application (in a smartdevice such as smartphone)</li>
<li>Cleaning Robot</li>
<li>Smart Light (such as Philips Hue)</li>
<li>Smart Mirror</li>
</ul>
</dd>
<dt>Expected Data</dt>
<dd>
The trigger value of the scene of the TV program.
Hybridcast connect application know the Thing Description of the devices in home. (Discovery?)
</dd>
<dt>Dependencies</dt>
<dd>
</dd>
<dt>Description</dt>
<dd>
Home smart devices behave according to TV programs.
Hybridcast applications in TV emit information about TV programs for smart home devices.
(Hybridcast is a Japanese Integrated Broadcast-Broadband system. Hybridcast applications are HTML5
applications that work on Hybridcast TV.)
Hybridcast Contact application receives the information and controlls smart home devices.
<br>
<br>
<img src="images/scenario_nhk.png" width="100%" height=100%>
<br>
</dd>
<dt>Variants</dt>
<dd>
</dd>
<dt>Gaps</dt>
<dd>
</dd>
<dt>Existing standards</dt>
<dd>
Hybridcast and Hybridcast Connect: a Japanese Integrated Broadcast-Broadband system (<a href="http://www.iptvforum.jp/download/input.html">IPTVFJ STD-0013 "Hybridcast Operational Guideline Version 2.8" (Application Forms)</a>, <a href="https://github.com/nhkrd">Reference Implementations</a>),
HbbTV,
ATSC 3.0,
...etc.
</dd>
<dt>Comments</dt>
<dd>
</dd>
</dl>
</section>
</section>
<section id="agriculture">
<h2>Agriculture</h2>
<section id="smart-agriculture">
<h2>Smart Agriculture (Greenhouse Horticulture)</h2>
<dl>
<dt>Submitter(s)</dt>
<dd>
Ryuichi Matsukura, Takuki Kamiya
</dd>
<dt>Reviewer(s)</dt>
<dd>
</dd>
<dt>Tracker Issue ID</dt>
<dd>
</dd>
<dt>Category</dt>
<dd>
</dd>
<dt>Class</dt>
<dd>
</dd>
<dt>Status</dt>
<dd>
</dd>
<dt>Target Users</dt>
<dd>
Agricultural corporation, Farmer, Manufacturers (Sensor, other facilities), Cloud provider
</dd>
<dt>Motivation</dt>
<dd>
Greenhouse Horticulture controlled by computers can create an optimal environment for growing plants. This
enables to improve productivity and ensure stable vegetable production throughout the year, independent of
the weather. This is the result of research on the growth of plants in the 1980s. For example, in
tomatoes, switching to hydroponics and optimizing the temperature, humidity and CO2 concentration required
for photosynthesis resulted in a five times increase in yield. The growth conditions for other vegetables
also have been investigated, and this control system is applied now.
</dd>
<dt>Expected Devices</dt>
<dd>
Sensors ( temperature, humidity, brightness, UV brightness, air pressure, and CO2)
Heating, CO2 generator, open and close sunlight shielding sheet.
</dd>
<dt>Expected Data</dt>
<dd>
Sensors’ values to clarify the gaps between conditions for maximizing photosynthesis and the current
environment.
Following sensors values at one or some points in the greenhouse: temperature, humidity, brightness, and
CO2.
</dd>
<dt>Dependencies</dt>
<dd>
WoT Architecture、WoT Thing Description
</dd>
<dt>Description</dt>
<dd>
Sensors and some facilities like heater, CO2 generator, sheet controller are connected to the gateway via
wired or wireless networks. The gateway is connected to the cloud via the Internet. All sensors and
facilities can be accessed and controlled from the cloud.
To maximize photosynthesis, the temperature, CO2 concentration, and humidity in the greenhouse are mainly
controlled. When the sunlight comes in the morning and CO2 concentration inside decreases, the application
turns on the CO2 generator to keep over 400 ppm, the same as the air outside. The temperature in the
greenhouse is adjusted by controlling the heater and the sunlight shielding sheet.
The cloud gathers all sensor data and the status of the facilities. The application makes the best
configuration for the region of the greenhouse located.
</dd>
<dt>Variants</dt>
<dd>
</dd>
<dt>Gaps</dt>
<dd>
In the case of the wireless connection to the sensors, the gateway should keep the latest value of the
sensors since the wireless connection is sometimes broken. The gateway can create a virtual entity
corresponding to the sensor and allow the application to access this virtual entity having the actual
sensor status like sleeping.
</dd>
<dt>Existing standards</dt>
<dd>
</dd>
<dt>Comments</dt>
<dd>
</dd>
</dl>
</section>
<section id="smart-agriculture-openfield">
<h2>Smart Agriculture: open-field agriculture</h2>
<dl>
<dt>Submitter(s)</dt>
<dd>
Cristiano Aguzzi
</dd>
<dt>Reviewer(s)</dt>
<dd>
</dd>
<dt>Tracker Issue ID</dt>
<dd>
</dd>