Technical Report Document Number
Download 0.83 Mb.
|
- Navigate this page:
- Contents 3 1 Scope 10 2 References 10
- 6 Enterprise Use Cases 45
- 7 Healthcare Use Cases 48
- 8 Public Services Use Cases 73
- 9 Residential Use Cases 102
- 10 Transportation Use Cases 123
- 11 Other Use Cases 140
- 12 History 182
This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification. The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices. About oneM2M The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. More information about oneM2M may be found at: http//www.oneM2M.org Copyright Notification No part of this document may be reproduced, in an electronic retrieval system or otherwise, except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © 2013, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC). All rights reserved. Notice of Disclaimer & Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ContentsContents 3 1 Scope 10 2 References 10 Normative references 11 Informative references 11
Wide area Energy related measurement/control system for advanced transmission and distribution automation 15 Description 15 Source 15 Actors 15 Pre-conditions 16 Triggers 16 Normal Flow 16 Alternative flow 19 Post-conditions 19 High Level Illustration 19 Potential Requirements 20 Analytics Use Case for M2M 21 Description 21 Source 23 Actors 23 Pre-conditions 23 Triggers 23 Normal Flow 23 Alternative Flow 1 24 Post-conditions 24 High Level Illustration 24 Concrete Example Oil and Gas 24 Potential requirements 27 Smart Meter Reading 28 Description 28 Source 28 Actors 28 Pre-conditions 28 Triggers 28 Normal Flow 28 Alternative flow 31 Post-conditions 31 High Level Illustration 32 Potential Requirements 32 Environmental Monitoring of Remote Locations to Determine Hydropower 33 Description 33 Source 33 Actors 33 Pre-conditions 33 Triggers 34 Normal Flow 34 Alternative flow 35 Post-conditions 35 High Level Illustration 36 Potential Requirements 36 Oil and Gas Pipeline Cellular/Satellite Gateway 37 Description 37 Source 37 Actors 37 Pre-conditions 37 Triggers 37 Normal Flow 37 Alternative flow 38 Post-conditions 41 High Level Illustration 41 Potential Requirements 42 6 Enterprise Use Cases 45 Smart Building 45 Description 45 Source 45 Actors 45 Pre-conditions 45 Triggers 45 None 45
Normal Flow 46 Alternative flow 47 None 47
Post-conditions 47 None 47
High Level Illustration 47 47
Potential Requirements 48 7 Healthcare Use Cases 48 M2M Healthcare Gateway 48 Description 48 Source 48 Actors 48 Pre-conditions 49 Triggers 49 Normal Flow 50 Alternative flow 51 Post-conditions 58 High Level Illustration 58 Potential Requirements 59 Use Case on Wellness Services 62 Description 62 Source 62 Actors 62 Pre-conditions 62 Triggers 62 Normal Flow 63 Alternative flow 63 Post-conditions 65 High Level Illustration 65 Potential Requirements 65 Secure remote patient care and monitoring 66 Description 66 Source 68 Actors 68 Pre-conditions 68 Triggers 69 Normal Flow 69 Alternative flow 70 Alternative flow No 1 70 Alternative flow No 2 70 Alternative flow No 3 70 Post-conditions 70 Normal flow 70 Alternative flow No 3 70
Street Light Automation 73 Description 73 Source 73 Actors 74 Pre-conditions 74 Triggers 74 Normal Flow 74 Alternative flow 78 Post-conditions 79 High Level Illustration 79 Potential Requirements 80 Use Case on Devices, Virtual Devices and Things 81 Description 81 Source 81 Actors 81 Pre-conditions 82 Triggers 82 Normal Flow 82 Alternative flow 82 Post-conditions 82 High Level Illustration 82 Potential Requirements 83 Car/Bicycle Sharing Services 83 Description 83 Source 83 Actors 84 Pre-conditions 84 Triggers 84 Normal Flow 84 Alternative flow 90 Post-conditions 90 High Level Illustration 90 Potential Requirements 91 Smart Parking 91 Description 91 Source 91 Actors 91 Pre-conditions 92 Triggers 92 Normal Flow 92 Alternative flow 94 Post-conditions 95 High Level Illustration 95 Potential Requirements 96 Information Delivery service in the devastated area 96 Description 96 Source 96 Actors 96 Pre-conditions 97 Triggers 97 Normal Flow 97 Alternative flow 98 Post-conditions 99 High Level Illustration 99 Potential Requirements 100 9 Residential Use Cases 102 Home Energy Management 102 Description 102 Source 102 Actors 102 Pre-conditions 103 Triggers 103 Normal Flow 103 Alternative flow 104 Post-conditions 104 High Level Illustration 104 Potential Requirements 105 Home Energy Management System (HEMS) 106 Description 106 Source 106 Actors 106 Pre-conditions 106 Triggers 106 Normal Flow 106 Alternative flow 107 Post-conditions 107 High Level Illustration 107 Potential Requirements 108 Plug-In Electrical Charging Vehicles and power feed in home scenario 109 Description 109 Source 109 Actors 109 Pre-conditions 110 Triggers 110 Normal Flow 110 Alternative flow 112 Post-conditions 112 High Level Illustration 112 Potential Requirements 112 Real-time Audio/Video Communication 114 Description 114 Source 115 Actors 115 Pre-conditions 115 Triggers 115 Normal Flow 115 Alternative flow 116 Post-conditions 116 High Level Illustration 116 Potential Requirements 116 Event Triggered Task Execution Use Case 117 Description 117 Source 117 Actors 117 Pre-conditions 117 Triggers 117 Normal Flow 118 Alternative flow 118 Post-conditions 118 High Level Illustration 118 Potential Requirements 119 Semantic Home Control 119 Description 119 Source 120 Actors 120 Pre-conditions 120 Triggers 120 Normal Flow 120 Alternative flow 120 Post-conditions 121 High Level Illustration 121 Potential Requirements 121 Semantic Device Plug and Play 121 Description 121 Source 121 Actors 121 Pre-conditions 121 Triggers 122 Normal Flow 122 Alternative flow 122 Post-conditions 122 High Level Illustration 122 Potential Requirements 122 10 Transportation Use Cases 123 Vehicle Diagnostic & Maintenance Report 123 Description 123 Source 123 Actors 123 Pre-conditions 123 Triggers 123 Normal Flow 123 Alternative flow 125 Post-conditions 125 High Level Illustration 125 Potential Requirements 126 Use Case on Remote Maintenance Services 126 Description 126 Source 126 Actors 126 Pre-conditions 128 Triggers 128 Normal Flow 128 Alternative flow 128 Post-conditions 128 High Level Illustration 128 Potential Requirements 130 Traffic Accident Information Collection 130 Description 130 Source 130 Actors 130 Pre-conditions 131 Triggers 131 Normal Flow 131 Alternative flow 132 Post-conditions 132 High Level Illustration 132 Potential Requirements 134 Fleet Management Service using DTG (Digital Tachograph) 134 Description 134 Source 134 Actors 134 Pre-conditions 136 Triggers 136 Normal Flow 136 Alternative flow 139 Post-conditions 139 High Level Illustration 139 Potential Requirements 140 11 Other Use Cases 140 Extending the M2M Access Network using Satellites 140 Description 140 Source 140 Actors 141 Pre-conditions 141 Triggers 141 Normal Flow 141 Alternative flow 141 Post-conditions 142 High Level Illustration 142 Potential Requirements 142 M2M Data Traffic Management by Underlying Network Operator 143 Description 143 Source 143 Actors 143 Pre-conditions 144 Triggers 144 Normal Flow 144 Alternative flow 146 Post-conditions 146 High Level Illustration 146 Potential Requirements 146 Optimized M2M interworking with mobile networks (Optimizing connectivity management parameters) 147 Description 147 Source 148 Actors 148 Pre-conditions 149 Triggers 149 Normal Flow 149 Alternative flow 150 Post-conditions 150 High Level Illustration 150 Potential Requirements 151 Optimized M2M interworking with mobile networks (Optimizing mobility management parameters) 151 Description 151 Source 152 Actors 152 Pre-conditions 153 Triggers 153 Normal Flow 153 Alternative flow 154 Post-conditions 154 High Level Illustration 154 Potential Requirements 156 Sleepy Node Use Case 156 Description 156 Source 157 Actors 157 Pre-conditions 158 Triggers 158 Normal Flow 158 Alternative flow 160 Post-conditions 160 High Level Illustration 160 Potential Requirements 160 Use Case on collection of M2M System data 163 Description 163 Source 163 Actors 163 Pre-conditions 163 Triggers 163 Normal Flow 164 Alternative flow 164 Post-conditions 164 High Level Illustration 164 Potential Requirements 165 Leveraging Broadcasting/Multicasting Capabilities of Underlying Networks 166 Description 166 Source 166 Actors 167 Pre-conditions 167 Triggers 167 Normal Flow 167 The request contains the payload to be delivered to vehicles. It can contain for example the alert level (how serious and urgent), the location and time of the accident, and directions to the driver (e.g. go slow or change routes). 167 The request also defines targeted receivers of the message and specifies alert options. They can contain for example the area to be covered, the type of devices to be alerted, the option whether the alerting should be repeated, the repetition interval, and stopping conditions. 167 The alert message is the payload to be delivered to vehicles. The contents are the same as from ABC Corp. but the format and encoding of the message may be different from AA Wireless and CC Mobile. 168 The broadcast parameters define targeted receivers of the message and specify broadcast options. They can contain for example the area to be covered, the type of devices to be alerted, the option whether the broadcast should be repeated, the repetition interval, and stopping conditions. The format of the parameters can be different between AA Wireless and CC Mobile. 168 ABC Corp. may need to cover a part of the broadcasting functions for some communication network service providers. For example, if CC Mobile does not have the functionality to repeat broadcasting periodically, ABC Corp. repeatedly requests CC Mobile to broadcast the message, in order to meet the request from XYZ Corp. 168 Alternative flow 168 Post-conditions 168 High Level Illustration 168 Potential Requirements 169 That request SHALL encapsulate the message (payload) from the M2M Application, relevant parameters (options) and optionally credentials for authentication and authorization. 169 The M2M System SHALL support that request to be independent of the types of the Underlying Networks. 170 oneM2M System SHALL authenticate the M2M Application. 170 oneM2M System SHALL validate and authorize the request. 170 oneM2M System SHALL support accounting on handling the request. 170 Leveraging Service Provisioning for Equipment with Built-in M2M Device 171 Description 171 Source 172 Actors 172 Pre-conditions 173 Triggers 173 Normal Flow 173 High Level Illustration 180 Service Model 180 Entity Model 180 Potential requirements 181 12 History 182 Directory: Deliverables Deliverables -> ArtistDesign Noe jpia year 4 Deliverables -> Cluster: Hardware Platform and mpsoCs D13- 2)-Y4 Deliverables -> Cluster: Modeling and Validation D6- 2)-Y4 Deliverables -> Version number: Version 0 Final Deliverables -> European Holocaust Research Infrastructure Theme [infra-2010 4] ga no. 261873 D19. 2 Metadata Registry Deliverables -> Technical Report Document Number Deliverables -> Project acronym: oversee project title: Open Vehicular Secure Platform Deliverables -> Eco report 03 the licensing of ‘mobile bands’1 in cept 26 January 2015 Deliverables -> Version number: Version 4 Main author Deliverables -> University of central florida project management plan Download 0.83 Mb. Share with your friends:
| |||||||||||
