TR 22.840
Study on Ambient power-enabled Internet of Things
V19.0.0 (Wzip)
2023/12 119 p.
- Rapporteur:
- Mr. Xu, Weijie
Shenzhen Heytap
full Table of Contents for TR 22.840 Word version: 19.0.0
0 Introduction
1 Scope
2 References
3 Definitions, symbols and abbreviations
4 Overview
5 Use cases
6 Traffic Scenarios
7 Consolidated potential requirements and KPIs
8 Conclusion and recommendations
A Ambient IoT availability scenarios
B Ambient power and energy storage
C Considerations when choosing harvesting source
$ Change history
0 Introduction p. 8
The present document describes use cases, traffic scenarios, device constraints of Ambient Internet of Things and identify new potential service requirements as well as new KPIs. An Ambient Internet of Things (Ambient IoT) device is an IoT device, being either battery-less or with limited energy storage capability (i.e., using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other suitable power source.
1 Scope p. 9
The present document provides Stage 1 potential 5G service requirements for ambient power-enabled Internet of Things (i.e., Ambient IoT). In the context of the present document, an Ambient power-enabled IoT device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other suitable power source. An ambient IoT device is expected to have lower complexity, smaller size and reduced capabilities and lower power consumption than previously defined 3GPP IoT devices (e.g., NB-IoT/eMTC devices). Ambient IoT devices can be maintenance free and can have long life span (e.g., more than 10 years).
The aspects addressed in the present document include:
-
Study use cases of ambient power-enabled IoT and identify potential service requirements, including:
- Security aspects, e.g., authentication and authorization, etc.
- Network selection, access control, connection, mobility and identification management
- Charging (e.g., per data volume, per message)
- Aspects related to stakeholder models (e.g., involving interactions in PLMNs, NPNs or other parties)
- Positioning
- Aspects on device life cycle management related to 3GPP system.
- Study traffic scenarios, device constraints (e.g., power consumption) and identify potential performance requirements and KPIs
- Gap analysis between the identified requirements for ambient power-enabled IoT and what is already defined by existing 3GPP requirements.
2 References p. 9
3 Definitions, symbols and abbreviations p. 13
3.1 Definitions p. 13
3.2 Abbreviations p. 14
4 Overview p. 14
5 Use cases p. 14
5.1 Use case on Ambient IoT on automated warehousing p. 14
5.1.1 Description p. 14
5.1.2 Pre-conditions p. 15
5.1.3 Service Flows p. 15
5.1.4 Post-conditions p. 16
5.1.5 Existing features partly or fully covering the use case functionality p. 16
5.1.6 Potential New Requirements needed to support the use case p. 16
5.2 Use case on medical instruments inventory management and positioning p. 17
5.2.1 Description p. 17
5.2.2 Pre-Conditions p. 17
5.2.3 Service Flows p. 18
5.2.4 Post-Conditions p. 18
5.2.5 Existing features partly or fully covering the use case functionality p. 18
5.2.6 Potential New Requirements needed to support the use case p. 18
5.3 Use Case on Ambient IoT devices in substations in smart grids p. 19
5.3.1 Description p. 19
5.3.2 Pre-conditions p. 21
5.3.3 Service Flows p. 21
5.3.4 Post-conditions p. 22
5.3.5 Existing features partly or fully covering the use case functionality p. 22
5.3.6 Potential New Requirements needed to support the use case p. 23
5.4 Use case on supporting Ambient IoT in Non-Public Network for logistics p. 24
5.4.1 Description p. 24
5.4.2 Pre-conditions p. 25
5.4.3 Service Flows p. 25
5.4.4 Post-conditions p. 26
5.4.5 Existing features partly or fully covering the use case functionality p. 26
5.4.6 Potential New Requirements needed to support the use case p. 26
5.5 Use case on intralogistics in automobile manufacturing p. 26
5.5.1 Description p. 26
5.5.2 Pre-conditions p. 27
5.5.3 Service Flows p. 28
5.5.4 Post-conditions p. 28
5.5.5 Existing features partly or fully covering the use case functionality p. 28
5.5.6 Potential New Requirements needed to support the use case p. 29
5.6 Use case on Ambient IoT sensors in smart homes p. 30
5.6.1 Description p. 30
5.6.2 Pre-Conditions p. 31
5.6.3 Service Flows p. 31
5.6.4 Post-Conditions p. 31
5.6.5 Existing features partly or fully covering the use case functionality p. 31
5.6.6 Potential New Requirements needed to support the use case p. 31
5.7 Use Case on Ambient IoT for airport terminal / shipping port p. 32
5.7.1 Description p. 32
5.7.2 Pre-conditions p. 32
5.7.3 Service Flows p. 33
5.7.4 Post-conditions p. 33
5.7.5 Existing features partly or fully covering the use case functionality p. 33
5.7.6 Potential New Requirements needed to support the use case p. 33
5.8 Use case on Finding Remote Lost Item p. 34
5.8.1 Description p. 34
5.8.2 Pre-conditions p. 34
5.8.3 Service Flows p. 34
5.8.4 Post-conditions p. 35
5.8.5 Existing features partly or fully covering the use case functionality p. 35
5.8.6 Potential New Requirements needed to support the use case p. 36
5.9 Use case on LCS for Ambient IoT p. 37
5.9.1 Description p. 37
5.9.2 Pre-conditions p. 37
5.9.3 Service Flows p. 37
5.9.4 Post-conditions p. 37
5.9.5 Existing features partly or fully covering the use case functionality p. 37
5.9.6 Potential New Requirements needed to support the use case p. 37
5.10 Use case on Relative positioning for Ambient IoT p. 38
5.10.1 Description p. 38
5.10.2 Pre-conditions p. 38
5.10.3 Service Flows p. 38
5.10.4 Post-conditions p. 39
5.10.5 Existing features partly or fully covering the use case functionality p. 39
5.10.6 Potential New Requirements needed to support the use case p. 39
5.11 Use case on online modification of medical instruments status p. 40
5.11.1 Description p. 40
5.11.2 Pre-Conditions p. 40
5.11.3 Service Flows p. 40
5.11.4 Post-Conditions p. 41
5.11.5 Existing features partly or fully covering the use case functionality p. 41
5.11.6 Potential New Requirements needed to support the use case p. 41
5.12 Use case on Ambient IoT service for personal belongings finding p. 42
5.12.1 Description p. 42
5.12.2 Pre-conditions p. 42
5.12.3 Service Flows p. 43
5.12.4 Post-conditions p. 43
5.12.5 Existing features partly or fully covering the use case functionality p. 43
5.12.6 Potential New Requirements needed to support the use case p. 43
5.13 Use case on Ambient IoT for Base Station Machine Room Environmental Supervision p. 44
5.13.1 Description p. 44
5.13.2 Pre-conditions p. 45
5.13.3 Service Flows p. 45
5.13.4 Post-conditions p. 46
5.13.5 Existing features partly or fully covering the use case functionality p. 46
5.13.6 Potential New Requirements needed to support the use case p. 46
5.14 Use case on indoor positioning in shopping centre using Ambient IoT p. 47
5.14.1 Description p. 47
5.14.2 Pre-conditions p. 47
5.14.3 Service Flows p. 47
5.14.4 Post-conditions p. 49
5.14.5 Existing features partly or fully covering the use case functionality p. 49
5.14.6 Potential New Requirements needed to support the use case of Positioning in shopping centre p. 49
5.15 Use Case on Ambient IoT enablement for smart laundry p. 50
5.15.1 Description p. 50
5.15.2 Pre-conditions p. 50
5.15.3 Service Flows p. 51
5.15.4 Post-conditions p. 51
5.15.5 Existing features partly or fully covering the use case functionality p. 52
5.15.6 Potential New Requirements needed to support the use case p. 53
5.16 Use case on Ambient IoT service for automated supply chain distribution p. 53
5.16.1 Description p. 53
5.16.2 Pre-conditions p. 54
5.16.3 Service Flows p. 54
5.16.4 Post-conditions p. 55
5.16.5 Existing features partly or fully covering the use case functionality p. 55
5.16.6 Potential New Requirements needed to support the use case p. 56
5.17 Use case on Device Activation and Deactivation p. 57
5.17.1 Description p. 57
5.17.2 Pre-conditions p. 57
5.17.3 Service Flows p. 57
5.17.4 Post-conditions p. 58
5.17.5 Existing features partly or fully covering the use case functionality p. 58
5.17.6 Potential New Requirements needed to support the use case p. 59
5.18 Use case on Fresh Food Supply Chain p. 59
5.18.1 Description p. 59
5.18.2 Pre-conditions p. 60
5.18.3 Service Flows p. 60
5.18.4 Post-conditions p. 61
5.18.5 Existing features partly or fully covering the use case functionality p. 61
5.18.6 Potential new requirements needed to support the use case p. 61
5.19 Use case on Forest Fire Monitoring using Ambient IoT devices p. 62
5.19.1 Description p. 62
5.19.2 Pre-conditions p. 62
5.19.3 Service Flows p. 63
5.19.4 Post-conditions p. 63
5.19.5 Existing feature partly or fully covering use case functionality p. 63
5.19.6 Potential New Requirements needed to support the use case p. 64
5.20 Use case on Smart Agriculture p. 64
5.20.1 Description p. 64
5.20.2 Pre-conditions p. 65
5.20.3 Service Flows p. 65
5.20.4 Post-conditions p. 65
5.20.5 Existing features partly or fully covering the use case functionality p. 66
5.20.6 Potential New Requirements needed to support the use case p. 66
5.21 Use Case on Ambient IoT for Museum Guide p. 66
5.21.1 Description p. 66
5.21.2 Pre-conditions p. 67
5.21.3 Service Flows p. 67
5.21.4 Post-conditions p. 68
5.21.5 Existing features partly or fully covering the use case functionality p. 68
5.21.6 Potential New Requirements needed to support the use case p. 68
5.22 Use case on smart grazing dairy farming enabled by Ambient IoT p. 69
5.22.1 Description p. 69
5.22.2 Pre-conditions p. 71
5.22.3 Service Flows p. 71
5.22.4 Post-conditions p. 72
5.22.5 Existing features partly or fully covering the use case functionality p. 72
5.22.6 Potential New Requirements needed to support the use case p. 72
5.23 Use case on smart pig farm enabled by Ambient IoT p. 73
5.23.1 Description p. 73
5.23.2 Pre-conditions p. 74
5.23.3 Service Flows p. 75
5.23.4 Post-conditions p. 75
5.23.5 Existing features partly or fully covering the use case functionality p. 75
5.23.6 Potential New Requirements needed to support the use case p. 76
5.24 Use case on smart manhole cover safety monitoring using Ambient IoT p. 77
5.24.1 Description p. 77
5.24.2 Pre-conditions p. 79
5.24.3 Service Flows p. 79
5.24.4 Post-conditions p. 79
5.24.5 Existing features partly or fully covering the use case functionality p. 79
5.24.6 Potential New Requirements needed to support the use case p. 80
5.25 Use case on smart bridge health monitoring using Ambient IoT p. 81
5.25.1 Description p. 81
5.25.2 Pre-conditions p. 82
5.25.3 Service Flows p. 82
5.25.4 Post-conditions p. 82
5.25.5 Existing features partly or fully covering the use case functionality p. 82
5.25.6 Potential New Requirements needed to support the use case p. 83
5.26 Use case on Elderly Health Care p. 84
5.26.1 Description p. 84
5.26.2 Pre-conditions p. 85
5.26.3 Service Flows p. 85
5.26.4 Post-conditions p. 86
5.26.5 Existing features partly or fully covering the use case functionality p. 86
5.26.6 Potential New Requirements needed to support the use case p. 86
5.27 Use case on end-to-end logistics p. 87
5.27.1 Description p. 87
5.27.2 Pre-Conditions p. 88
5.27.3 Service Flows p. 88
5.27.4 Post-Conditions p. 89
5.27.5 Existing features partly or fully covering the use case functionality p. 89
5.27.6 Potential New Requirements needed to support the use case p. 89
5.28 Use case on pressure powered switch p. 90
5.28.1 Description p. 90
5.28.2 Pre-conditions p. 90
5.28.3 Service Flows p. 90
5.28.4 Post-conditions p. 91
5.28.5 Existing features partly or fully covering the use case functionality p. 91
5.28.6 Potential New Requirements needed to support the use case p. 91
5.29 Use case on Device Permanent Deactivation p. 91
5.29.1 Description p. 91
5.29.2 Pre-conditions p. 91
5.29.3 Service Flows p. 91
5.29.4 Post-conditions p. 92
5.29.5 Existing features partly or fully covering the use case functionality p. 92
5.29.6 Potential New Requirements needed to support the use case p. 93
5.30 Use case on Ambient IoT device acting as a controller in smart agriculture p. 93
6 Traffic Scenarios p. 95
6.1 Traffic scenario on flower auction p. 95
6.1.1 Description p. 95
6.1.2 Assumptions p. 96
6.1.3 Potential Functional Requirements p. 97
6.1.4 Potential Key Performance Requirements p. 97
6.2 Traffic Scenario on cow stable p. 98
6.2.1 Description p. 98
6.2.2 Assumptions p. 99
6.2.3 Potential Functional Requirements p. 99
6.2.4 Potential Key Performance Requirements p. 99
6.3 Traffic Scenario on Electronic Shelf Label p. 100
6.3.1 Description p. 100
6.3.2 Assumptions p. 101
6.3.3 Potential Key Performance Requirements p. 101
7 Consolidated potential requirements and KPIs p. 102
7.1 Consolidated potential requirements p. 102
7.1.1 Communication aspects of Ambient IoT devices p. 103
7.1.2 Positioning/location of Ambient IoT devices p. 104
7.1.3 Management of Ambient IoT devices p. 104
7.1.4 Collected information and network capability exposure p. 105
7.1.5 Charging p. 105
7.1.6 Security and privacy p. 106
7.2 Consolidated potential KPIs p. 106
7.2.1 KPIs for inventory p. 106
7.2.2 KPI for sensor data collection p. 107
7.2.3 KPI for tracking p. 107
7.2.4 KPI for actuator control p. 108
8 Conclusion and recommendations p. 108
A Ambient IoT availability scenarios p. 109
B Ambient power and energy storage p. 109
B.1 Typical ambient power p. 109
B.2 Energy storage p. 112
C Considerations when choosing harvesting source p. 113
$ Change history p. 115
