Title page

Contents

Foreword 5

1. General 8

Y.4000/Y.2060: Overview of the Internet of things 9

Summary 10

1. Scope 12

2. References 12

3. Definitions 12

3.1. Terms defined elsewhere 12

3.2. Terms defined in this Recommendation 12

4. Abbreviations and acronyms 13

5. Conventions 13

6. Introduction of the IoT 13

6.1. Concept of the IoT 13

6.2. Technical overview of the IoT 14

7. Fundamental characteristics and high-level requirements of the IoT 16

7.1. Fundamental characteristics 16

7.2. High-level requirements 17

8. IoT reference model 18

8.1. Application layer 18

8.2. Service support and application support layer 18

8.3. Network layer 19

8.4. Device layer 19

8.5. Management capabilities 20

8.6. Security capabilities 20

Appendix I. IoT ecosystem and business models 21

I.1. Business roles 21

I.2. Business models 22

Bibliography 24

Y.4001/F.748.2: Machine socialization: Overview and reference model 25

Summary 26

Introduction 28

1. Scope 29

2. References 29

3. Definitions 29

3.1. Terms defined elsewhere 29

3.2. Terms defined in this Recommendation 29

4. Abbreviations and acronyms 30

5. Conventions 30

6. Overview of machine socialization 30

6.1. General overview of machine socialization 30

6.2. Relations for socialization 31

6.3. Socialization under the same ownership of machines 33

6.4. Socialization under different ownerships of machines 33

6.5. General procedures of machine socialization 33

7. Requirements for machine socialization 34

7.1. Standardized description of a machine 34

7.2. Service discovery 34

7.3. Standardized expression of relation 34

7.4. Dynamic update of relation 35

7.5. Multiple ways of establishing a relation 35

7.6. Caching of relation information 35

7.7. Fault recovery for a relation 35

7.8. Resilience of relation 35

7.9. Negotiation of QoS 35

7.10. Verification of ownership of a machine 35

8. Reference models of machine socialization 35

8.1. Service model of machine socialization 35

8.2. Functional model of machine socialization 36

Y.4002/F.748.3: Machine socialization: Relation management models and descriptions 38

Summary 39

1. Scope 41

2. References 41

3. Definitions 41

3.1. Terms defined elsewhere 41

3.2. Terms defined in this Recommendation 41

4. Abbreviations and acronyms 42

5. Conventions 42

6. Overview of relation for machine socialization 42

7. Relation management models 43

7.1. Centralized relation management model 43

7.2. Distributed relation management model 44

7.3. Nested-centralized relation management model 45

8. Relation descriptions 46

8.1. Machine profile schema 46

8.2. Relation profile schema 47

Appendix I. Use cases of relation management models 50

I.1. Booking of a movie ticket based on a centralized relation management model 50

I.2. Booking of a movie ticket based on a distributed relation management model 51

I.3. Booking of a movie ticket based on a nested-centralized relation management model 52

Bibliography 53

2. Definitions and terminologies 54

Y.4050/Y.2069: Terms and definitions for the Internet of things 55

Summary 56

1. Scope 58

2. References 58

3. Definitions 59

3.1. Terms defined elsewhere 59

4. Abbreviations and acronyms 62

Bibliography 62

3. Requirements and Use of Cases 63

Y.4100/Y.2066: Common requirements of the Internet of Things 64

Summary 65

1. Scope 67

2. References 67

3. Definitions 68

3.1. Terms defined elsewhere 68

3.2. Terms defined in this Recommendation 68

4. Abbreviations and acronyms 68

5. Conventions 69

6. General use cases of the IoT and IoT actors 69

6.1. General use cases 69

6.2. The IoT actors 71

7. Important areas for consideration from a requirement perspective 72

7.1. Implementation and operational aspects 72

7.2. Ubiquitous connectivity 72

7.3. End-to-end intelligence 72

7.4. Time synchronization 72

7.5. Human body connectivity 72

7.6. A large amount of data from things 72

7.7. Privacy protection related with things 73

8. Common requirements of the IoT 73

8.1. Categories of IoT common requirements 73

8.2. Non-functional requirements 73

8.3. Application support requirements 74

8.4. Service requirements 75

8.5. Communication requirements 76

8.6. Device requirements 77

8.7. Data management requirements 78

8.8. Security and privacy protection requirements 78

Annex A. The IoT common requirements list 80

Appendix I. Representative use cases of the IoT 86

I.1. Video surveillance 86

I.2. Emergency alerting 86

I.3. Data acquisition 86

I.4. Remote control 86

I.5. Transfer of events across different application domains 87

I.6. Data sharing across different application domains 87

I.7. Integrated operating centre for smart city 87

I.8. One detailed use case: traffic accident information collection 87

Bibliography 88

Y.4101/Y.2067: Common requirements and capabilities of a gateway for Internet of Things applications 89

Summary 90

1. Scope 92

2. References 92

3. Definitions 92

3.1. Terms defined elsewhere 92

3.2. Terms defined in this Recommendation 93

4. Abbreviations and acronyms 93

5. Conventions 93

6. Introduction to gateways for IoT applications 94

7. General characteristics of a gateway for IoT applications 95

7.1. Connection to the communication networks 95

7.2. Device access 95

7.3. Protocol translation 95

7.4. Interaction with applications 95

7.5. Adaptability 95

7.6. Management functions support 95

7.7. Security functions support 95

8. Common requirements and recommendations of a gateway for IoT applications 95

8.1. General gateway requirements and recommendations 95

8.2. Adaptation related requirements and recommendations 96

8.3. Support capabilities related requirements and recommendations 97

8.4. Application related requirements 98

8.5. Security and management related requirements 99

9. Common capabilities of a gateway for IoT applications 99

9.1. Reference technical framework and typical high-level flows of a gateway for IoT applications 99

9.2. Details on common capabilities of a gateway for IoT applications 101

Appendix I. Use cases of a gateway for IoT applications 104

I.1. Gateway in home services 104

I.2. Gateway in automotive telematics 105

I.3. Gateway in online collaborative whiteboard 106

Bibliography 107

Y.4102/Y.2074: Requirements for Internet of things devices and operation of Internet of things applications during disasters 108

Summary 109

Introduction 111

1. Scope 112

2. References 112

3. Definitions 112

3.1. Terms defined elsewhere 112

3.2. Terms defined in this Recommendation 113

4. Abbreviations and acronyms 113

5. Conventions 113

6. Requirements for IoT devices in the context of disaster 114

6.1. General requirements concerning disaster 114

6.2. Requirements for IoT devices 114

7. Requirements for operation of IoT applications during disaster 114

7.1. IoT applications with dedicated operation mode 115

7.2. IoT applications temporally providing resources to external safety systems 115

7.3. IoT applications with external control of operation during disaster 116

7.4. Switching between two or more operation strategies during disaster 117

Appendix I. Methods concerning assurance of integrity and reliability of the data produced by IoT devices during disaster 118

I.1. General overview of a monitoring and control centre for IoT devices 118

I.2. The distribution of the monitoring and control centre's responsibilities to local centres 119

I.3. The monitoring and control centre's working scenarios 119

I.4. Use of the stored data 120

Bibliography 120

Y.4103/F.748.0: Common requirements for Internet of things (IoT) applications 121

Summary 122

1. Scope 125

2. References 125

3. Definitions 125

3.1. Terms defined elsewhere 125

3.2. Terms defined in this Recommendation 126

4. Abbreviations and acronyms 126

5. Conventions 126

6. Characteristics of things in the IoT 126

6.1. Fundamental characteristics 126

6.2. Common characteristics 127

6.3. Social characteristics 127

6.4. Autonomy of things 127

6.5. Capability of self-replication or control 127

7. Characteristics of IoT applications 127

7.1. Interconnectivity 127

7.2. Things-related services 128

7.3. Heterogeneity 128

7.4. Dynamic changes 128

7.5. Enormous scale 128

7.6. Data gathering and processing by things 128

7.7. Collaborative data processing 128

7.8. Maintenance-free operation 128

7.9. Self-adaptation 129

7.10. Energy efficiency and operating lifetime 129

7.11. Embedded intelligence 129

7.12. Location considerations 129

7.13. Auto-configuring reliable information transmission over ubiquitous networks 129

7.14. Security 130

7.15. Privacy 130

7.16. Infrastructure-less versus infrastructure-based application 130

7.17. Observation and/or actuation vs. data exchanges 130

7.18. Application domains 130

8. Common requirements for IoT applications 131

8.1. Identification 131

8.2. Identification-based connectivity 131

8.3. Interoperability 131

8.4. Autonomic networking 131

8.5. Autonomic services provisioning 132

8.6. Location-based capabilities 132

8.7. Security 132

8.8. Privacy protection 132

8.9. Plug and play 132

8.10. Manageability 132

8.11. Compliance with laws and regulations 132

8.12. Awareness of service 132

8.13. Mobility support 133

8.14. Scalability support 133

8.15. Robustness against dynamic changes 133

8.16. Self-organization (re-organization) and self-healing 133

8.17. Energy efficient operation 133

8.18. Common data format for collaborative data processing 133

Bibliography 133

Y.4104/F.744: Service description and requirements for ubiquitous sensor network middleware 135

Summary 136

1. Scope 138

2. References 138

3. Definitions 138

3.1. Terms defined elsewhere 138

3.2. Terms defined in this Recommendation 139

4. Abbreviations and acronyms 139

5. Conventions 139

6. Description of USN services, USN middleware and use cases 139

6.1. Description of USN services 139

6.2. Description of USN middleware 140

6.3. Use cases of USN services 140

7. Functional model of USN middleware 145

7.1. Open application interface processing 146

7.2. Basic functions 146

7.3. Advanced functions 146

7.4. Sensor network common interface processing 147

7.5. Security service 147

8. Requirements for USN middleware 147

8.1. Interface requirements 147

8.2. Functional requirements 147

8.3. Security requirements 148

Bibliography 148

Y.4105/Y.2221: Requirements for support of ubiquitous sensor network (USN) applications and services in the NGN environment 149

Summary 150

1. Scope 153

2. References 153

3. Definitions 154

3.1. Terms defined elsewhere 154

3.2. Terms defined in this Recommendation 154

4. Abbreviations and acronyms 154

5. Conventions 155

6. USN description and characteristics 155

7. Service requirements of USN applications and services 157

7.1. Sensor network management 157

7.2. Profile management 158

7.3. Open service environment 158

7.4. Quality of service (QoS) support 159

7.5. Connectivity 160

7.6. Location-based service support 160

7.7. Mobility support 160

7.8. Security 161

7.9. Identification, authentication and authorization 161

7.10. Privacy 162

7.11. Accounting and charging 162

8. NGN capability requirements for support of USN applications and services 162

8.1. Requirements for extensions or additions to NGN capabilities 162

8.2. Requirements supported by existing NGN capabilities 164

9. Reference diagram of NGN capabilities for support of USN applications and services 165

10. Security considerations 165

Appendix I. Use-cases of USN applications and services 166

I.1. Weather information service 166

I.2. Healthcare service 169

I.3. Environmental and situational information service using public transportation 170

Appendix II. Capability requirements for support of USN applications and services not directly affecting the NGN 172

II.1. Power conservation (sensors node) 172

II.2. Network formation: auto-configuration and self-healing (sensor networks) 172

II.3. Addressing mechanisms 172

II.4. ID design 173

II.5. Sensor nodes mobility support 173

II.6. Secure control messages 173

II.7. Lightweight routing 173

II.8. Connectivity 174

Bibliography 174

Y.4106/F.747.3: Requirements and functional model for a ubiquitous network robot platform that supports ubiquitous sensor network applications and services 175

Summary 176

1. Scope 178

2. References 178

3. Definitions 178

3.1. Terms defined elsewhere 178

3.2. Terms defined in this Recommendation 179

4. Abbreviations and acronyms 179

5. Conventions 179

6. Overview of UNR-PF in terms of USN applications and services 180

6.1. General overview of UNR-PF 180

6.2. Relationships between USN and UNR-PF 181

7. Use cases of ubiquitous network robot platform 182

7.1. Health support service 182

7.2. Shopping support service 182

8. Requirements for UNR-PF 184

8.1. Abstraction of functionality 184

8.2. Inter-service collaboration 185

8.3. Service among multiple areas 186

8.4. Service execution based on customer attributes 188

9. Functional model for UNR-PF 189

9.1. Robot registry function 190

9.2. Operator registry function 191

9.3. User registry function 191

9.4. Map registry function 191

9.5. Service queue function 191

9.6. State manager function 191

9.7. Resource manager function 191

9.8. Message manager function 191

Bibliography 192

Y.4107/F.747.6: Requirements for water quality assessment services using ubiquitous sensor networks (USNs) 193

Summary 194

1. Scope 196

2. References 196

3. Definitions 196

3.1. Terms defined elsewhere 196

3.2. Terms defined in this Recommendation 197

4. Abbreviations and acronyms 197

5. Conventions 198

6. Overview of water quality assessment 198

7. Scenarios for WQA services 198

7.1. Scenario I: Real-time water quality data aggregation 198

7.2. Scenario II: Automatic WQA node control 199

7.3. Scenario III: WQA node surveillance and logging 200

7.4. Scenario IV: Water quality prediction through software sensors 201

8. Requirements of WQA services 202

8.1. Reliable data transfer 202

8.2. Real-time water quality information transfer 202

8.3. Bidirectional communication 202

8.4. Security 202

8.5. Water assessment modelling 202

9. USN-based WQA services 203

9.1. Water quality distribution service 203

9.2. Water quality prediction service 203

9.3. Service for total amount of polluted water 203

10. USN capabilities for WQA services 203

10.1. Reliable communication link in sensor networks 203

10.2. Transmission delay guarantee to the WQA server 203

10.3. Low power consumption in sensor networks 203

10.4. Bidirectional communication between WQA nodes and servers 204

10.5. Multi-hop data transfer in sensor networks 204

10.6. IP infrastructure compatibility 204

10.7. Long distance transmission support in sensor networks 204

10.8. Security services 204

10.9. Data logging 204

10.10. Maintainability of sensor networks 204

10.11. Naming and addressing in sensor networks 204

Y.4108/Y.2213: NGN service requirements and capabilities for network aspects of applications and services using tag-based identification 205

Summary 206

Introduction 209

1. Scope 210

2. References 210

3. Definitions 210

3.1. Terms defined elsewhere 210

3.2. Terms defined in this Recommendation 211

4. Abbreviations and acronyms 212

5. Conventions 213

6. Tag-based identification applications and services description and high-level reference service architecture 213

6.1. Basic characteristics of tag-based identification applications and services 213

6.2. Impact of tag-based identification applications and services on the network 214

6.3. Reference service architecture model 214

7. Service requirements of tag-based identification applications and services 215

7.1. Multi-identifier interpretation requirements 215

7.2. Identifier resolution 215

7.3. ID terminal and ID tag management 216

7.4. Content distribution control 216

7.5. Privacy management 216

7.6. Location-based services support 217

7.7. Service quality control 217

7.8. Application transaction and traffic requirements 217

8. NGN capabilities for tag-based identification applications and services 217

8.1. Requirements for extensions or additions to NGN release 1. capabilities 218

8.2. Requirements supported by existing NGN release 1. capabilities 219

Appendix I. Non-NGN high-level service requirements 220

I.1. General requirements for identifiers 220

I.2. Requirements for identification of identifier schemes 220

I.3. Requirements related to application data encoding 220

I.4. Requirements for identification service interworking 221

I.5. Requirements for location information management 221

I.6. Requirements related to management of application mobility 221

I.7. Requirements related to traceability 221

I.8. Requirements related to identifier filtering 222

Appendix II. Classification of tag-based identification applications and services 223

II.1. Overview of tag-based identification applications and services 223

II.2. Classification of tag-based identification applications and services 224

II.3. Examples of tag-based identification applications and services 224

II.4. Evaluation of tag-based identification applications and services 225

Appendix III. Example scenarios of tag-based identification applications and services 229

III.1. Closed-domain tag-based identification applications and services 229

III.2. B2B tag-based identification applications and services 230

III.3. B2C tag-based identification applications and services 231

III.4. B2B2C tag-based identification applications and services 232

III.5. C2C tag-based identification applications and services 233

Bibliography 234

Y.4109/Y.2061: Requirements for the support of machine-oriented communication applications in the next generation network environment 235

Summary 236

1. Scope 239

2. References 239

3. Definitions 240

3.1. Terms defined elsewhere 240

3.2. Terms defined in this Recommendation 240

4. Abbreviations and acronyms 241

5. Conventions 242

6. Introduction 242

6.1. Network overview 242

6.2. Types of machine-oriented communications 244

6.3. MOC ecosystem 245

7. Characteristics of MOC 246

8. Service requirements of MOC applications 247

8.1. Mobility levels 247

8.2. Time controlled network communications 247

8.3. Resource usage 248

8.4. Interoperability with proprietary devices 248

8.5. Application collaboration 248

8.6. Support of service integration and delivery environment 248

8.7. Load balancing and robustness 249

8.8. Accounting and charging 249

8.9. Management 250

8.10. Addressing and identification 251

8.11. Location-based support 251

8.12. Group-based support 252

8.13. Quality of service 252

8.14. Security 253

8.15. Device association and interaction with multiple applications 254

8.16. Communication with sleeping device 254

8.17. Differentiation and handling of collected data 254

9. Requirements of NGN capabilities 255

9.1. Requirements for extensions or additions to NGN capabilities 255

9.2. Requirements supported by existing NGN capabilities 258

10. Capability requirements of an MOC device domain 258

10.1. Application enablement 258

10.2. Mobility 258

10.3. Communication 259

10.4. QoS 259

10.5. Remote management 259

10.6. Device addressing and identification 260

10.7. Security 260

10.8. Accounting and charging 260

10.9. Data identification 260

11. Reference framework for MOC capabilities 260

11.1. High-level view 260

11.2. MOC capabilities in the NGN domain 261

11.3. MOC capabilities in the MOC device domain 264

11.4. MOC service interfaces 265

12. Security considerations 266

Appendix I. Actors and related roles in the MOC ecosystem 266

Appendix II. MOC use cases 268

II.1. e-Health 268

II.2. Tsunami warning service 270

II.3. Motorcade management 271

II.4. Smart home 272

II.5. Integration with Internet services 273

Bibliography 274

Y.4110/Y.2065: Service and capability requirements for e-health monitoring services 275

Summary 276

1. Scope 278

2. References 278

3. Definitions 278

3.1. Terms defined elsewhere 278

3.2. Terms defined in this Recommendation 279

4. Abbreviations and acronyms 279

5. Conventions 280

6. Classification of e-health monitoring services 280

6.1. EHM healthcare (EHMH) services 281

6.2. EHM rehabilitation (EHMR) services 281

6.3. EHM treatment (EHMT) services 281

7. Characteristics of e-health monitoring services 281

7.1. General characteristics 281

7.2. Specific characteristics of EHM services 282

8. Service requirements for support of e-health monitoring services 284

8.1. EHM roles 284

8.2. Service requirements of EHM customers 284

8.3. Service requirements of an EHM device provider 286

8.4. Service requirements of a network provider 286

8.5. Service requirements of a platform provider 287

8.6. Service requirements of an EHM application provider 287

9. Capability requirements for support of e-health monitoring services 288

9.1. Introduction to the EHM capabilities 288

9.2. Capabilities of the application layer 288

9.3. Capabilities of the SSAS layer 289

9.4. Capabilities of the network layer 291

9.5. Capabilities of the device layer 291

9.6. Management capabilities 293

9.7. Security capabilities 294

Appendix I. e-health monitoring service scenarios 296

I.1. Individual/family (indoor and outdoor) 296

I.2. Physical examination 297

I.3. Disaster rescue 299

I.4. Pre-hospital emergency medical service 302

I.5. Smart ward service 304

I.6. Chronic disease care 305

Y.4111/Y.2076: Semantics based requirements and framework of the Internet of Things 308

Summary 309

1. Scope 311

2. References 311

3. Definitions 311

3.1. Terms defined elsewhere 311

3.2. Terms defined in this Recommendation 312

4. Abbreviations and acronyms 312

5. Conventions 313

6. Introduction to semantic technologies for the IoT 313

7. Semantics based use cases for IoT actors 314

8. Semantics based requirements of the IoT 315

8.1. General semantics based requirements for IoT 315

8.2. Semantics based requirements for IoT with respect to the IoT reference model 317

9. Semantics based capability framework of the IoT 320

9.1. Overview 320

9.2. Application layer 322

9.3. SSAS layer 323

9.4. Network layer 324

9.5. Device layer 325

9.6. Management capabilities 325

9.7. Security capabilities 325

Appendix I. IoT application scenarios using semantic technologies 326

I.1. Semantics-enabled home automation 326

I.2. Semantics enabled location-based service 327

Bibliography 328

Y.4112/Y.2077: Requirements of the Plug and Play capability of the Internet of Things 329

Summary 330

1. Scope 332

2. References 332

3. Definitions 332

3.1. Terms defined elsewhere 332

3.2. Terms defined in this Recommendation 333

4. Abbreviations and acronyms 333

5. Conventions 333

6. Overview of the plug and play capability 334

6.1. Introduction 334

6.2. The components of the plug and play capability 334

7. Requirements of the PnP capability 336

7.1. PnP management capability related requirements 336

7.2. PnP security capability related requirements 337

7.3. Device PnP capability related requirements 338

7.4. Gateway PnP capability related requirements 338

Appendix I. Use cases of the PnP capability 339

I.1. Large scale sensor deployment: greenhouse example 339

I.2. Security protection from counterfeit device 339

I.3. Enablement of customized configuration of IoT device 340

4. Infrastructure, Connectivity and Networks 341

Y.4250/Y.2222: Sensor control networks and related applications in a next generation network environment 342

Summary 343

1. Scope 345

2. References 345

3. Definitions 345

3.1. Terms defined elsewhere 345

3.2. Terms defined in this Recommendation 346

4. Abbreviations and acronyms 347

5. Conventions 348

6. Overview of SCNs 348

7. Configurations for SCN applications 350

7.1. Basic operations for SCN applications 350

7.2. Decentralized configuration for SCN applications 351

7.3. Transitional configurations for SCN applications 354

8. Service requirements of SCN applications 357

8.1. Connectivity 357

8.2. Mobility support 357

8.3. Context awareness 358

8.4. Location awareness 358

8.5. Presence awareness 358

8.6. Traffic and load awareness 359

8.7. Fault awareness 359

8.8. Routing 359

8.9. Load balancing 359

8.10. Scalability 359

8.11. Fault tolerance 359

8.12. Quality of service (QoS) 359

8.13. Management 360

8.14. Pledging of security of decisions 360

8.15. Open service environment (OSE) support 360

8.16. NGN service integration and delivery environment (NGN-SIDE) support 361

8.17. Mass mobile user terminal support 361

8.18. Emergency management applications 361

9. Security considerations 361

Appendix I. Use case of SCN for verification 362

I.1. Errors in decisions 362

I.2. Verification 362

I.3. Examples of verification applications 364

Appendix II. Use case of SCN for emergency management 365

Bibliography 366

Y.4251/F.747.1: Capabilities of ubiquitous sensor networks for supporting the requirements of smart metering services 368

Summary 369

1. Scope 372

2. References 372

3. Definitions 372

3.1. Terms defined elsewhere 372

3.2. Terms defined in this Recommendation 373

4. Abbreviations and acronyms 373

5. Conventions 373

6. Overview of smart metering 373

6.1. Smart grids and smart metering 374

6.2. Technical overview of smart metering 375

6.3. USN-based smart metering services 375

7. Smart metering service scenarios 377

7.1. Scenario I: Regularly scheduled remote meter reading 377

7.2. Scenario II: On-demand remote meter reading 377

7.3. Scenario III: Demand response 378

7.4. Scenario IV: Tariff configuration 379

7.5. Scenario V: Meter reading data aggregation 380

8. Network and USN requirements for smart metering services 381

8.1. Time synchronization 381

8.2. Reliable information delivery 381

8.3. Minimal time delay 381

8.4. Real-time delivery of meter reading data 382

8.5. Bidirectional communication between meters and operators 382

8.6. Security support including the authorization of operator and data confidentiality 382

8.7. Authentication of smart meters 382

8.8. Meter reading data processing 382

8.9. Monitoring and management of smart meters 382

9. USN capabilities for smart metering services 383

9.1. Time synchronization 383

9.2. Reliable transmission 383

9.3. Scalability 383

9.4. Mobility support 383

9.5. Delivery latency 383

9.6. Fault detection and recovery 383

9.7. Security supporting confidentiality, integrity check, authorization and authentication 383

9.8. Connectivity 384

9.9. Unicasting and multicasting 384

9.10. Data aggregation 384

9.11. Distributed processing 384

9.12. Monitoring and management of sensor nodes 384

Bibliography 384

Y.4252/Y.2064: Energy saving using smart objects in home networks 385

Summary 386

1. Scope 388

2. References 388

3. Definitions 388

3.1. Terms defined elsewhere 388

3.2. Terms defined in this Recommendation 389

4. Abbreviations and acronyms 389

5. Conventions 390

6. Overview of energy saving using smart objects in home networks 390

7. Requirements and capabilities for saving energy using smart objects 392

7.1. High-level requirements 392

7.2. Requirements of key components in home networks 392

7.3. Required capabilities for saving energy 393

8. Functional architecture for energy saving using smart objects 394

8.1. Configuration of home networks 394

8.2. Functional architecture in home/building for saving energy 395

9. Security considerations 396

Appendix I. Use cases for saving energy through home automation and building energy management 397

I.1. Energy saving through home automation 397

I.2. Energy saving through building energy management 397

5. Frameworks, Architectures and Protocols 398

Y.4400/Y.2063: Framework of the web of things 399

Summary 400

1. Scope 402

2. References 402

3. Definitions 402

3.1. Terms defined elsewhere 402

3.2. Term defined in this Recommendation 403

4. Abbreviations and acronyms 403

5. Conventions 404

6. Overview of the web of things 404

7. Requirements for the web of things 405

7.1. General requirements for the WoT 405

7.2. Functional requirements for the WoT 406

8. Conceptual and deployment models of the web of things 406

8.1. Conceptual model 406

8.2. Deployment models 408

9. Functional architecture for the web of things 409

9.1. Overview of the WoT architecture 409

9.2. Functional architecture of the WoT broker 411

10. Security considerations 414

Appendix I. Use cases and scenarios of the web of things 415

I.1. Home control services using WoT 415

Appendix II. WoT broker service information flows 417

II.1. Service discovery 417

II.2. Service execution 418

II.3. Service composition 419

II.4. Agent registration 420

II.5. Service registration 421

Bibliography 422

Y.4401/Y.2068: Functional framework and capabilities of the Internet of Things 423

Summary 424

1. Scope 426

2. References 426

3. Definitions 426

3.1. Terms defined elsewhere 426

3.2. Terms defined in this Recommendation 427

4. Abbreviations and acronyms 427

5. Conventions 427

6. Concepts of the IoT functional framework 428

6.1. Openness and interoperability of the IoT capabilities 428

6.2. Completeness, implementability and applicability of the IoT capabilities 428

6.3. The different views of the IoT functional framework 428

7. The IoT functional framework 429

7.1. The IoT functional framework in functional view 429

7.2. The IoT functional framework in implementation view 431

7.3. The IoT functional framework in deployment view 434

8. The IoT basic capabilities 436

8.1. Service provision capabilities 436

8.2. Communication capabilities 437

8.3. Application support capabilities 438

8.4. Data management capabilities 439

8.5. Management capabilities 439

8.6. Connectivity capabilities 441

8.7. Security and privacy protection capabilities 442

9. IoT capabilities for integration of key emerging technologies 442

9.1. Capabilities for integration of cloud computing technologies 442

9.2. Capabilities for integration of big data technologies 443

10. Security considerations 445

Annex A. The IoT capabilities list 446

Appendix I. Matching analysis between requirements and capabilities of the IoT 463

I.1. Matching analysis of non-functional requirements of the IoT 463

I.2. Matching analysis of application support requirements of the IoT 464

I.3. Matching analysis of service requirements of the IoT 465

I.4. Matching analysis of communication requirements of the IoT 465

I.5. Matching analysis of device requirements of the IoT 466

I.6. Matching analysis of data management requirements of the IoT 467

I.7. Matching analysis of security and privacy protection requirements of the IoT 468

Bibliography 468

Y.4402/F.747.4: Requirements and functional architecture for the open ubiquitous sensor network service platform 469

Summary 470

Introduction 472

1. Scope 473

2. References 473

3. Definitions 473

3.1. Terms defined elsewhere 473

3.2. Terms defined in this Recommendation 474

4. Abbreviations and acronyms 474

5. Conventions 474

6. Open USN service description and characteristics 474

7. Requirements for the open USN service platform 476

7.1. Requirements to communicate with heterogeneous USN middleware 476

7.2. Requirements of the open USN service platform 476

7.3. Requirements for linking the LOD 476

7.4. Requirements for applications 476

7.5. Requirements for USN resources and sensed data/semantic data 476

8. Functional architecture of the open USN service framework 477

8.1. Functional architecture 477

8.2. Functional entities 478

Appendix I. Information flow in the open USN service framework 481

I.1. USN resource registration 481

I.2. Sensed data/semantic data access from Semantic USN repository FE 482

I.3. Sensed data access from USN resources 483

Appendix II. Use cases of the open USN service platform 485

II.1. Traffic information service using the open USN service platform 485

Bibliography 487

Y.4403/Y.2026: Functional requirements and architecture of the next generation network for support of ubiquitous sensor network applications and services 488

Summary 489

1. Scope 491

2. References 491

3. Definitions 491

3.1. Terms defined elsewhere 491

3.2. Terms defined in this Recommendation 492

4. Abbreviations and acronyms 492

5. Conventions 493

6. Functional requirements and functions of the NGN for USN applications and services 493

6.1. NGN functional requirements 493

6.2. Functional architecture model 494

6.3. Functions to support USN applications and services 495

7. Functional architecture of the NGN for USN applications and services 498

7.1. Transport processing functional entities 498

7.2. Transport control functional entities 499

7.3. Service control functional entities 499

7.4. Application support functions and service support functions 500

8. Security considerations 500

Appendix I. Analysis of service requirements and network capabilities defined in Recommendation ITU-T Y.2221 501

I.1. Requirements for extensions to NGN capabilities 501

I.2. Requirements supported by existing NGN capabilities 503

I.3. Mapping table of the requirements and the extended NGN functions 504

I.4. Mapping table of the requirements and the existing NGN functions 505

Appendix II. USN middleware functions provided by NGN 506

Bibliography 507

Y.4404/Y.2062: Framework of object-to-object communication for ubiquitous networking in next generation networks 508

Summary 509

1. Scope 511

2. References 511

3. Definitions 511

3.1. Terms defined elsewhere 511

3.2. Term defined in this Recommendation 512

4. Abbreviations and acronyms 512

5. Conventions 513

6. Ubiquitous networking in NGNs 513

6.1. Overview of ubiquitous networking 513

6.2. Architectural model for ubiquitous networking 514

7. Basic concept of object-to-object communication 517

7.1. Objects in the ubiquitous networking environment 517

7.2. Characteristics of objects 517

8. Requirements of "connecting-to-anything" capability for ubiquitous networking 518

8.1. General requirements for object-to-object communication 518

8.2. Technical considerations for object-to-object communication 518

9. A mechanism for object-to-object communication: identity processing for connecting to anything 520

10. Security considerations 521

Appendix I. Characteristics and examples of objects in the ubiquitous networking environment 522

Appendix II. Ubiquitous networking applications and examples using object-to-object communication 524

Bibliography 525

Y.4405/H.621: Architecture of a system for multimedia information access triggered by tag-based identification 526

Summary 527

Introduction 529

1. Scope 530

2. References 530

3. Definitions 530

3.1. Terms defined elsewhere 530

4. Abbreviations and acronyms 531

5. Conventions 532

6. System functional architecture 532

6.1. Functional components 533

6.2. Protocols 534

6.3. General workflow 535

Appendix I. Examples of physical level architecture 537

I.1. Configuration example of physical level architecture 537

I.2. Components 538

I.3. Implementation examples of narrow area communication between ID tag and IDterminal 539

I.4. Distributed implementation of ID resolution server 540

Appendix II. Workflow examples for multimedia information access triggered by tag-based identification 542

II.1. Location-aware multimedia information service 542

II.2. Multimedia information download via posters service 543

II.3. u-Museum 544

II.4. Business card with personal identifier 546

II.5. Presence service with multimedia information 547

II.6. Food safety check and purchase 548

II.7. Visitor identification and guidance service with multimedia information 550

Bibliography 551

Y.4406/Y.2016: Functional requirements and architecture of the NGN for applications and services using tag-based identification 552

Summary 553

1. Scope 555

2. References 555

3. Definitions 555

3.1. Terms defined elsewhere 555

3.2. Terms defined in this Recommendation 556

4. Abbreviations and acronyms 556

5. Conventions 557

6. Functional requirements and functions of the NGN for applications and services using tag-based identification 558

6.1. NGN functional requirements 558

6.2. Functional architecture model 559

6.3. Functions to support applications and services using tag-based identification 560

7. Functional architecture of the NGN for applications and services using tag-based identification 563

7.1. Transport processing functional entities 563

7.2. Transport control functional entities 564

7.3. Service control functional entities 564

7.4. Application support functions and service support functions 564

8. Security 565

Appendix I. Analysis of service requirements and network capabilities defined in [ITU-T Y.2213] 566

I.1. NGN service requirements of tag-based identification applications and services 566

I.2. Non-NGN high level service requirements of tag-based identification applications and services 567

I.3. NGN requirements supported by extensions or additions of NGN Release 1 capabilities 568

I.4. NGN requirements supported by existing NGN Release 1 capabilities 568

I.5. Non-NGN high level service requirements supported by NGN Release 1 capabilities 569

Appendix II. High-level reference architecture of ID-based applications and services in the NGN 570

Appendix III. Use-case example of applications using tag-based identification in the NGN 571

Appendix IV. Traceability mechanism and referential information flows 573

IV.1. Traceability mechanism 573

IV.2. Information flows 573

Bibliography 574

Y.4407/Y.2281: Framework of networked vehicle services and applications using NGN 575

Summary 576

Introduction 578

1. Scope 579

2. References 579

3. Definitions 579

3.1. Terms defined elsewhere 579

3.2. Terms defined in this Recommendation 580

4. Abbreviations and acronyms 580

5. Conventions 582

6. High-level view of a networked vehicle 582

7. Services and communication features of networked vehicles 583

7.1. Networked vehicle services and applications 583

7.2. Communications features 584

7.3. Relationship between networked vehicle services and applications with communication features 585

8. Requirements for networked vehicle services and applications using NGN 586

8.1. Requirements for a networked vehicle communicating with ITS infrastructure 586

8.2. NGN requirements for networked vehicle services and applications 590

9. Framework architecture of the networked vehicle and ITS infrastructure 592

9.1. Reference architecture of the NGN-capable networked vehicle and ITS infrastructure 593

9.2. Overview architecture of the NGN-capable networked vehicle and ITS infrastructure 594

10. Security considerations 595

Appendix I. Use cases of networked vehicle services and applications using NGN 596

Appendix II. Comparison between ITS station reference architecture and NGN functional architecture 598

II.1. Features and detailed functions of ITS station reference architecture 598

II.2. Analysis between two architectural models 600

II.3. Features and functions for a networked vehicle 601

Bibliography 603

Y.4408/Y.2075: Capability framework for e-health monitoring services 604

Summary 605

1. Scope 608

2. References 608

3. Definitions 608

3.1. Terms defined elsewhere 608

3.2. Terms defined in this Recommendation 609

4. Abbreviations and acronyms 609

5. Conventions 609

6. Introduction 609

7. EHM conceptual framework 610

7.1. EHM conceptual framework overview 610

7.2. EHM components 611

8. EHM capability framework 614

8.1. Distribution map of the EHM capabilities 614

8.2. Application layer capabilities of EHM components 615

8.3. SSAS layer capabilities of EHM components 616

8.4. Network layer capabilities of EHM components 618

8.5. Device layer capabilities of EHM components 618

8.6. Management capabilities of EHM components 619

8.7. Secure capabilities of EHM components 620

Annex A. Overview of EHM component capabilities 621

Appendix I. EHM service deployment technical scenarios 623

I.1. Technical scenario for community EHM services 623

I.2. Technical scenario for mobile EHM services 623

Y.4409/Y.2070: Requirements and architecture of the home energy management system and home network services 625

Summary 626

1. Scope 628

2. References 628

3. Definitions 628

3.1. Terms defined elsewhere 628

3.2. Terms defined in this Recommendation 629

4. Abbreviations and acronyms 630

5. Conventions 631

6. Overview 631

6.1. HN service architecture 631

6.2. HEMS based on HN service architecture 633

6.3. Merits of HN service architecture 635

7. Requirements 635

7.1. Requirements for the device 635

7.2. Requirements for HGW 636

7.3. Requirements for management PF 636

7.4. Requirements for security 637

8. Reference architecture 637

9. Functional architecture 639

9.1. Device 641

9.2. HGW 641

9.3. Management PF 642

9.4. Application 643

10. Functional relationship 644

10.1. Device operation 644

10.2. Application execution 646

10.3. Management 647

11. Security support 647

11.1. HEMS model for security 648

11.2. Security functions 648

Appendix I. Deployment model with WoT 650

Appendix II. Examples of HN applications 651

II.1. Home security 651

II.2. Customer support with controlling access right to device 651

II.3. Room facility coordination for better sleep 652

Appendix III. Security considerations based on [ITU-T X.1111] 653

Bibliography 656

Y.4410/Y.229: Architectural overview of next generation home networks 657

Summary 658

1. Scope 660

2. References 660

3. Definitions 660

3.1. Terms defined elsewhere 660

3.2. Terms defined in this Recommendation 661

4. Abbreviations and acronyms 661

5. Conventions 662

6. Overview of next generation home network (NGHN) 662

6.1. General characteristics of next generation home network (NGHN) 662

6.2. Connectivity to the NGHN 662

7. Overview of the NGHN architecture 663

7.1. Overview of functional framework 663

7.2. NGHN functions at transport stratum 665

7.3. NGHN functions at service stratum 666

7.4. NGHN management functions (H-MF) 666

7.5. NGHN identity management functions (H-IdM) 667

7.6. Home network terminal functions (TF) 667

8. Security considerations 667

Appendix I. Federation of NGHNs 668

Bibliography 668

Y.4411/Q.3052: Overview of application programming interfaces and protocols for the machine-to-machine service layer 669

Summary 670

1. Scope 673

2. References 673

3. Definitions 673

3.1. Terms defined elsewhere 673

3.2. Terms defined in this Recommendation 674

4. Abbreviations and acronyms 674

5. Conventions 675

6. General introduction 675

7. Component-based M2M reference model and its relationship with M2M service layer 675

7.1. Component based M2M reference model 675

7.2. M2M platforms 676

7.3. Types of M2M platforms 677

7.4. Reference points of the M2M service layer in the component-based M2M reference model 677

8. APIs and protocols for M2M 679

8.1. API overview 679

8.2. Design approach for M2M service layer APIs 680

8.3. Existing APIs and protocols for M2M service layer 681

8.4. M2M protocol structure and stacks 682

9. General requirements of APIs and protocols with respect to the M2M service layer 684

9.1. Extensibility 684

9.2. Scalability 684

9.3. Fault tolerance and robustness 685

9.4. Efficiency 685

9.5. Interoperability 685

9.6. Self-operation and self-management 685

Appendix I. Examples of attributes for APIs and protocols 686

Appendix II. Reference of other existing APIs and protocols for M2M service layer 687

Bibliography 688

Y.4412/F.747.8: Requirements and reference architecture for audience-selectable media service framework in the IoT environment 689

Summary 690

Introduction 692

1. Scope 693

2. References 693

3. Definitions 693

3.1. Terms defined elsewhere 693

3.2. Terms defined in this Recommendation 694

4. Abbreviations and acronyms 694

5. Conventions 694

6. Overview of audience-selectable media (ASM) service 694

7. Requirements of ASM service framework 696

7.1. Service requirements 696

7.2. Functional requirements 697

8. Reference architecture of ASM service framework 698

8.1. Reference architecture 698

8.2. Camera objects function 699

8.3. Camera control server function 700

8.4. Video playback terminal function 701

Appendix I. Use cases for ASM service 702

I.1. Use case for an ASM broadcasting service using multi-camera objects 702

I.2. Use case for an open screen service using multi-camera objects 703

Bibliography 704

Y.4413/F.748.5: Requirements and reference architecture of the machine-to-machine service layer 705

Summary 706

1. Scope 708

2. References 708

3. Definitions 708

3.1. Terms defined elsewhere 708

3.2. Terms defined in this Recommendation 709

4. Abbreviations and acronyms 709

5. Conventions 709

6. Definition of the ITU-T M2M service layer 710

6.1. The ITU-T M2M service layer and its relationship with the IoT reference model 710

6.2. The ETSI M2M service capabilities layer and its relationship with the ITU-T M2M service layer 711

6.3. The oneM2M common service entity and its relationship with the ITU-T M2M service layer 711

7. Requirements of the ITU-T M2M service layer 712

7.1. Common requirements 712

7.2. e-health specific requirements 714

8. Architectural framework of the ITU-T M2M service layer 715

8.1. Overview of the architectural framework of the ITU-T M2M service layer 715

8.2. The capabilities of the ITU-T M2M service layer 715

9. Reference points of the ITU-T M2M service layer 716

9.1. Overview of the reference points 716

9.2. Details on the reference points 717

Appendix I. Comparison between the capabilities of the ITU-T M2M service layer and common services functions of oneM2M 719

Appendix II. Comparison of reference points between the ITU-T M2M service layer and common services entity of oneM2M 721

Bibliography 721

Y.4414/H.623: Web of things service architecture 722

Summary 723

1. Scope 725

2. References 725

3. Definitions 725

3.1. Terms defined elsewhere 725

3.2. Terms defined in this Recommendation 727

4. Abbreviations and acronyms 727

5. Conventions 728

6. Overview of the WoT service 728

7. Functional architecture of the WoT service 729

7.1. WoT service functions 729

7.2. Web resource functions 730

7.3. Web client 730

7.4. Things 730

8. WoT service functions 731

8.1. Functional entities of the WoT service support functions (WoT-S SF) 731

8.2. Functional entities of the WoT service control functions (WoT-S CF) 732

8.3. Functional entities of the WoT resource management functions (WoT RMF) 735

9. Web resource functions 736

9.1. WoT broker functions 736

9.2. RESTful web services 737

Appendix I. WoT description model 738

I.1. Physical characteristics in WoT description 738

I.2. Service characteristics in WoT description 738

Appendix II. An example of information flows 739

II.1. Information flow between web client and things 739

Bibliography 740

Y.4450/Y.2238: Overview of Smart Farming based on networks 742

Summary 743

Introduction 745

1. Scope 746

2. References 746

3. Definitions 746

3.1. Terms defined elsewhere 746

3.2. Terms defined in this Recommendation 747

4. Abbreviations and acronyms 747

5. Conventions 748

6. Introduction of Smart Farming based on networks 748

6.1. Concept 748

6.2. General overview 748

7. Reference model of Smart Farming based on networks 749

7.1. Reference architecture 749

7.2. Service roles 750

8. Service capabilities required to support Smart Farming 751

9. Network capabilities 751

10. Security considerations 752

Appendix I. The cyclic procedures of a convergence service for agriculture 753

Appendix II. Environments and deployments of a convergence service for agriculture 754

Appendix III. Service capabilities 756

III.1. Service capabilities for the pre-production stage 756

III.2. Service capabilities for the production stage 756

III.3. Service capabilities for the post-production stage 757

Bibliography 760

6. Services, Applications, Computation and Data Processing 761

Y.4551/F.771: Service description and requirements for multimedia information acces striggered by tag-based identification 762

Summary 763

Introduction 765

1. Scope 766

2. References 766

3. Definitions 766

3.1. Terms defined elsewhere 766

3.2. Terms defined in this Recommendation 766

4. Abbreviations and acronyms 768

5. Conventions 768

6. High-level functional model and generic service description 769

6.1. High-level functional model 769

6.2. Generic service description 770

7. Requirements 771

7.1. User requirement 771

7.2. Service requirements 771

7.3. Identifier requirements 771

7.4. ID tag requirement 772

7.5. ID terminal requirements 772

7.6. ID resolution function requirements 772

7.7. Multimedia information delivery function requirements 773

7.8. Wide area public communication requirement 773

7.9. Security requirements 773

7.10. Quality of service (QoS) requirement 773

Appendix I. Service description in applications 774

I.1. u-Museum 774

I.2. Multimedia information download via posters 774

I.3. Operating manual for a product 774

I.4. Food traceability 775

I.5. Business card with personal identifier 775

I.6. Presence service with multimedia information 775

I.7. Location-aware information delivery for commercial advertisement 775

I.8. Sightseeing information delivery 776

I.9. Visitor identification and guidance service with multimedia information 776

Bibliography 777

Y.4552/Y.2078: Application support models of the Internet of Things 778

Summary 779

1. Scope 781

2. References 781

3. Definitions 782

3.1. Terms defined elsewhere 782

3.2. Terms defined in this Recommendation 782

4. Abbreviations and acronyms 782

5. Conventions 783

6. Basis of IoT application support models 783

6.1. Concepts and purpose of IoT application support models 783

6.2. Rationale for the selection of the IoT applications support models 784

6.3. The three views of IoT application support models 785

7. The configurable application support model 785

7.1. The description of the configurable application support model 785

7.2. The capabilities of the configurable application support model 788

8. The adaptable application support model 793

8.1. The description of the adaptable application support model 793

8.2. The capabilities of the adaptable application support model 795

9. The reliable application support model 797

9.1. The description of the high reliable application support model 798

9.2. The capabilities of the reliable application support model 800

10. Security considerations 804

Annex A. The list of configurable capabilities for support of IoT applications 805

Annex B. The list of adaptable capabilities for support of IoT applications 815

Annex C. The list of reliable capabilities for support of IoT applications 819

Appendix I. Use cases for the IoT applications support models from the smart home environment 826

I.1. Use case 1: Configurable remote monitoring in a smart home 826

I.2. Use case 2: Adaptable home energy management 827

I.3. Use case 3: Reliable health monitoring at home 828

Bibliography 829

Y.4553: Requirements of smartphone as sink node for IoT applications and services 830

Summary 831

Introduction 833

1. Scope 834

2. References 834

3. Definitions 834

3.1. Terms defined elsewhere 834

3.2. Terms defined in this Recommendation 835

4. Abbreviations and acronyms 835

5. Conventions 835

6. Description and characteristics of SPSN 836

6.1. Descriptions 836

6.2. General characteristics 837

7. Work modes of the SPSN 837

7.1. Local service mode 837

7.2. Remote service mode 838

8. Requirements of the SPSN 839

8.1. General requirements 839

8.2. Network connectivity 839

8.3. Local information processing 839

8.4. Devices connectivity 839

8.5. Data exchanging 840

8.6. Support of multiple communication protocols 840

8.7. DM requirements 840

8.8. Security and privacy 840

Appendix I. Use cases of the SPSN for IoT applications and services 841

I.1. SPSN for commercial merchant service 841

I.2. SPSN for home services 842

I.3. SPSN for environment-monitoring services 843

I.4. SPSN for wearable smart devices 844

Appendix II. Example of sink node related functions of an SPSN 846

7. Management, Control and Performance 848

Y.4700/F.747.2: Deployment guidelines for ubiquitous sensor network applications and services for mitigating climate change 849

Summary 850

1. Scope 852

2. References 852

3. Definitions 852

3.1. Terms defined elsewhere 852

3.2. Terms defined in this Recommendation 853

4. Abbreviations and acronyms 853

5. Conventions 853

6. Overview of climate change monitoring 853

6.1. Global greenhouse gas monitoring network 853

6.2. Local GHG monitoring network 854

7. Analysis of environmental impact by USN applications and services 854

7.1. Deployment elements of USN 854

7.2. Positive environmental impacts 855

7.3. Negative environmental impacts 858

8. Requirements for deployment of USN applications and services for mitigating climate change 858

8.1. Environmentally friendly resources 858

8.2. Energy efficiency 859

8.3. Operation conditions of GHG sensors 860

Bibliography 861

Y.4701/H.641: SNMP-based sensor network management framework 862

Summary 863

Introduction 865

1. Scope 866

2. References 866

3. Definitions 866

3.1. Terms defined elsewhere 866

3.2. Terms defined in this Recommendation 867

4. Abbreviations and acronyms 867

5. Conventions 868

6. Architecture of an SNMP-based sensor network management framework 868

7. Functional entities of SNMP-based sensor network management framework 868

7.1. SNMP manager 869

7.2. SNMP agent 869

7.3. Sensor network management protocol manager 869

7.4. Sensor network management protocol agent 870

7.5. Application level gateway 870

7.6. Managed object for sensor network 870

7.7. Managed object for sensor node 870

8. Operation of an SNMP-based sensor network management framework 870

8.1. Overview 870

8.2. Application level gateway database 872

8.3. Translation from an SNMP to a sensor network management protocol message 872

8.4. Translation from a sensor network management protocol to an SNMP message 873

8.5. Consideration of the sensor network gateway for supporting IP-based sensor networks 874

9. Object identifier allocation for MIB and object identifier translation between SNMP and sensor network management protocols 874

Annex A. Object identifier assignments 875

Appendix I. Example of object identifier translation 876

Bibliography 877

Y.4702: Common requirements and capabilities of device management in the Internet of things 878

Summary 879

1. Scope 881

2. References 881

3. Definitions 881

3.1. Terms defined elsewhere 881

3.2. Terms defined in this Recommendation 882

4. Abbreviations and acronyms 882

5. Conventions 883

6. Introduction 883

7. Requirements of device management in the IoT 885

7.1. Characteristics specific to device management in the IoT 885

7.2. Common requirements of device management in the IoT 886

8. Common capabilities of device management in the IoT 889

8.1. Configuration management capability 889

8.2. Performance management capability 889

8.3. Fault management capability 890

8.4. Security management capability 890

8.5. Connectivity management capability 891

8.6. DM protocol engine capability 891

8.7. Accounting management capability 891

8.8. Service exposure - web portal capability 892

8.9. Service exposure - API capability 892

Bibliography 893

8. Identification and Security 894

Y.4800/F.747.5: Requirements and functional architecture of an automatic location identificationsy stem for ubiquitous sensor network (USN) applications and services 895

Summary 896

Introduction 898

1. Scope 899

2. References 899

3. Definitions 899

3.1. Terms defined elsewhere 899

3.2. Terms defined in this Recommendation 900

4. Abbreviations and acronyms 900

5. Conventions 900

6. Requirements for ALI systems 900

6.1. General requirements 900

6.2. High-level requirements 901

7. Functional architecture of the ALI system for USN applications and services 902

7.1. Functional architecture 902

7.2. Functional entities 902

Appendix I. Relationship between open USN service platform and ALI capabilities 904

Appendix II. Information flow of ALI services 905

II.1. Resource registration 905

II.2. Positioning process 906

II.3. Configuration process 906

Appendix III. ALI scenarios for USN applications and services 908

III.1. Location identification for sensor nodes working in complex environments 908

III.2. Continuing location identification for sensor nodes in a changing physical environment 909

III.3. Location identification for sensor nodes using sensing and actuating techniques 910

III.4. Configuration for sensor nodes with limited processing capabilities 911

III.5. Location identification for sensor nodes in a resource-limited USN environment 911

Bibliography 912

Y.4801/F.748.1: Requirements and common characteristics of the IoT identifier for the IoT service 913

Summary 914

Introduction 916

1. Scope 917

2. References 917

3. Definitions 917

3.1. Terms defined elsewhere 917

3.2. Terms defined in this Recommendation 918

4. Abbreviations and acronyms 918

5. Conventions 919

6. Introduction of the IoT identifier 919

7. Analysis of identifiers in the existing technologies 920

8. Common characteristics of the IoT identifier 921

9. Requirements of the IoT identifier 922

9.1. Identifying anything 922

9.2. Communication between things 922

9.3. Association between physical objects and virtual objects 922

9.4. Networking technology independency 922

9.5. Mapping identifiers to objects 923

9.6. Relation between characteristics and requirements 923

10. New capability for IoT identifiers 924

11. Reference model of identification in the IoT 924

Bibliography 926

Y.4802/H.642.2: Multimedia information access triggeredtag-based identification-Registration procedures for identifiers 928

Summary 929

1. Scope 931

2. References 931

3. Definitions 931

3.1. Terms defined elsewhere 931

3.2. Terms defined in this Recommendation 932

4. Abbreviations and acronyms 932

5. Conventions 932

6. Registration authority for a second level code 932

6.1. Selection 933

6.2. Announcement 933

6.3. Change of information 933

6.4. Publication 933

7. Second level RA 933

7.1. Responsibilities 933

7.2. Criteria for acceptance 934

7.3. Detailed procedures for the operation of the second level RA 934

7.4. Transfer of register entries held by the second level RA 935

Y.4804/H.642.1: Multimedia information access triggered by tag-based identification-identification scheme 936

Summary 937

Introduction 939

1. Scope 940

2. References 940

3. Definitions 940

3.1. Terms defined elsewhere 940

3.2. Terms defined in this Recommendation 941

4. Abbreviations and acronyms 941

5. Conventions 942

6. Concept of an identification scheme for multimedia information access triggered by tag-based identification 942

6.1. Overview 942

6.2. Uniqueness of ID value 942

7. ITU-T H.642 identification scheme for multimedia information access triggered by tag-based identification 943

7.1. Structure of an ITU-T H.642 identification scheme 943

7.2. First level code 944

7.3. Second level code (2LC) 944

7.4. Class 944

7.5. Third level code (3LC) 944

7.6. Fourth level code (4LC) 944

Appendix I. Survey on identification schemes 945

I.1. Introduction 945

I.2. Need for a generic identification scheme for multimedia information access triggered by tag-based identification 945

I.3. Requirements on the identifier for multimedia information access triggered by tag basedidentification 945

I.4. Survey on existing identification schemes 946

Bibliography 950

Y.4002/F.748.3: Machine socialization: Relation management models and descriptions 46

Table 1 - Machine profile schema 46

Table 2 - Relation profile schema 48

Y.4103/F.748.0: Common requirements for Internet of things (IoT) applications 131

Table 7-1 - Example of IoT application domains 131

Y.4407/Y.2281: Framework of networked vehicle services and applications using NGN 586

Table 7-1 - Relationship between networked vehicle services and applications with communication features 586

Y.4408/Y.2075: Capability framework for e-health monitoring services 615

Table 1 - EHM components involved in the information sharing capability of application layer 615

Table 2 - EHM components and accounting-related information provision capability of the application layer 616

Table 3 - EHM components and data storage capability of SSAS layer 617

Y.4450/Y.2238: Overview of Smart Farming based on networks 750

Table 1 - Service roles 750

Y.4801/F.748.1: Requirements and common characteristics of the IoT identifier for the IoT service 924

Table 9-1 - Relation between common characteristics and requirements of IoT identifiers 924

Y.4804/H.642.1: Multimedia information access triggered by tag-based identification-identification scheme 942

Table 1 - Field name and length 943

Appendix II. Classification of tag-based identification applications and services 226

Table II.1 - Evaluation of tag-based identification applications and services 226

Appendix I. Characteristics and examples of objects in the ubiquitous networking environment 522

Table I.1 - Characteristics and examples of objects in the ubiquitous networking environment 522

Appendix I. Examples of physical level architecture 539

Table I.1 - Variations of narrow area communication between ID tag and ID tag R/W 539

Appendix I. Use cases of networked vehicle services and applications using NGN 597

Table I.1 - Use cases of networked vehicle 597

Appendix II. Comparison between ITS station reference architecture and NGN functional architecture 600

Table II.1 - Features and comparison between ITS station reference architecture and NGN functional architecture 600

Appendix III. Security considerations based on [ITU-T X.1111] 653

Table III.1 - Relationship of security threats to HEMS model 653

Table III.2 - Relationship of HEMS security requirements, threats and functions 654

Table III.3 - Relationship between security functions and model 655

Appendix I. Service description in applications 776

Table I.1 - Applications sorted by fields 776

Annex Tables

Annex A. The IoT capabilities list 446

Table A.1 - List of service provision capabilities 446

Table A.2 - List of communication capabilities 448

Table A.3 - List of application support capabilities 451

Table A.4 - List of data management capabilities 453

Table A.5 - List of management capabilities 454

Table A.6 - List of connectivity capabilities 458

Table A.7 - List of security and privacy protection capabilities 459

Table A.8 - List of capabilities for integration of cloud computing technologies 460

Table A.9 - List of capabilities for integration of big data technologies 461

Annex A. Overview of EHM component capabilities 621

Table A.1 - Overview of EHM component capabilities 621

Annex A. The list of configurable capabilities for support of IoT applications 805

Table A.1 - List of configurable service provision capabilities 805

Table A.2 - List of configurable communication capabilities 806

Table A.3 - List of configurable data management capabilities 808

Table A.4 - List of configurable connectivity capabilities 809

Table A.5 - List of configurable communication capabilities 810

Table A.6 - List of configurable application support capabilities 811

Table A.7 - List of configurable management capabilities 812

Annex B. The list of adaptable capabilities for support of IoT applications 815

Table B.1 - List of adaptable application support capabilities 815

Annex C. The list of reliable capabilities for support of IoT applications 819

Table C.1 - List of reliable application support capabilities 819

Annex A. Object identifier assignments 875

Table A.1 - Object identifier assignments 875