Draft ETSI

TR 102 897 V<0.1.1> (2010-01)

Technical Report

Machine to Machine Communications (M2M); Use cases of M2M applications for City Automation

CAUTION: This DRAFT document is provided for information and is for future development work within the ETSI Technical Committee M2M only. ETSI and its Members accept no liability for any further use/implementation of this Specification.

Approved and published Specifications and reports for implementation of the M2M system shall be obtained exclusively via the ETSI Documentation Service at http://pda.etsi.org/pda/queryform.asp

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

Reference
DTR/M2M-00007

Keywords
Security, User

ETSI
650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88

Important notice
Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp

Copyright Notification
No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute yyyy. All rights reserved. DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. TM 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners.
TM TM TM TM

ETSI

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

Contents
Intellectual Property Rights ................................................................................................................................4 Foreword.............................................................................................................................................................4 Introduction ........................................................................................................................................................4 1 2
2.1 2.2

Scope ........................................................................................................................................................5 References ................................................................................................................................................5

Normative references ......................................................................................................................................... 5 Informative references ........................................................................................................................................ 5

3
3.1 3.2 3.3

Definitions, symbols and abbreviations ...................................................................................................6

Definitions .......................................................................................................................................................... 6 Symbols .............................................................................................................................................................. 6 Abbreviations ..................................................................................................................................................... 6

4
4.1 4.2

M2M Applications for City Automation ..................................................................................................6

General description of M2M applications for City Automation......................................................................... 6 Specific examples for M2M applications for City Automation.......................................................................... 6

Use cases for City Automation .................................................................................................................7

5.1 Overview ............................................................................................................................................................ 7 5.2 Detailed use cases ............................................................................................................................................... 7 5.2.1 Use Case 1 .................................................................................................................................................................. 7 5.2.1.1 General Use Case Description ................................................................................................................................. 7 5.2.1.2 Stakeholders ............................................................................................................................................................ 7 5.2.1.3 Scenario ................................................................................................................................................................ 7 5.2.1.4 Information Exchanges............................................................................................................................................ 7 5.3 Requirements resulting from use cases .............................................................................................................. 7

Annex <A>: Title of annex ...............................................................................................................................8 A.1

A.1.1

First clause of the annex ...........................................................................................................................8

First subdivided clause of the annex................................................................................................................... 8

History ................................................................................................................................................................9

ETSI

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

Intellectual Property Rights

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Foreword
This Technical Report (TR) has been produced by ETSI Technical Committee Machine to Machine Communications (M2M). The present document may be referenced by other TRs and Technical Standards (TS) developed by ETSI TC M2M. The present document is a TR and therefore, the content is informative, but when this TR is referenced by a TS, the referenced clauses may become normative with respect to the content of the referencing TS.

Introduction
This clause is optional. If it exists, it is always the third unnumbered clause. Clause numbering starts hereafter. PLEASE AVOID USING AUTOMATIC NUMBERING AS IT IS UNSTABLE. Check http://portal.etsi.org/edithelp/other/EDRs_Navigator.chm clauses 5.2.3 and A.4 for help. <PAGE BREAK>

ETSI

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

Scope

The present document includes Use Case descriptions for City Automation applications in context of Machine-toMachine (M2M) communications. The described Use Cases will be used to derive service requirements and capabilities of the functional architecture specified in ETSI TC M2M.

References
For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; for informative references.

References are either specific (identified by date of publication and/or edition number or version number) or non-specific.

Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.

2.1

Normative references

The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] [2] ETSI EN xxx xxx-y: "title". ETSI EN zzz zzz: "title".

2.2

Informative references

The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] [i.2] ETSI TR xxx xxx: "zzzzzzzzzzzzzzzzzzzzzzzzzz". .

ETSI

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

3
3.1

Definitions, symbols and abbreviations

Definitions

For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply: <defined term>: <definition> example 1: text used to clarify abstract rules by applying them literally NOTE: This may contain additional information.

3.2

Symbols
<Explanation> <2nd Explanation> <3rd Explanation>

For the purposes of the present document, the [following] symbols [given in ... and the following] apply: <symbol> <2nd symbol> <3rd symbol>

3.3

Abbreviations

For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply: <ACRONYM1> <Explanation> <ACRONYM2> <Explanation> <ACRONYM3> <Explanation>

4
<Text>

M2M Applications for City Automation

General description of M2M applications for City Automation

4.1
<Text>

4.2

Specific examples for M2M applications for City Automation

ETSI

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

5
<Text>

Use cases for City Automation

Overview

5.1
<Text>

5.2

Detailed use cases

5.2.1 Use Case 1 Traffic Flow Management System in combination with Dynamic Traffic Light Control
5.2.1.1 General Use Case Description
Editors note: List element, individual use case is detailed. Describe objective/goals of this use case in a high level but clear terms and list major issues that are highlighted. The flow of road traffic within cities depends on different criteria; the number of vehicles, the time and the day, the traffic situation on other roads within and in the surrounding of a city, current traffic jams and accidents as well as construction works on and along roads. The traffic situation can only be roughly forecasted based on historical traffic flow data only. The connection of traffic flow sensors on city roads with traffic flow management systems which are able to control traffic flow information displays as well as dynamically changeable traffic signs and the integration of traffic results in a system which is able manage the traffic more efficient and which can help to reduce fuel consumption, air pollution, congestions, and the time spend in traffics.

5.2.1.2 Stakeholders
Editors note: In this clause, a set of definitions for who or what the use case is referring to

5.2.1.3 Scenario
Editors note: In this clause, descriptive text of the use case is provided showing how the stakeholders use the system. Describe detailed stepwise description. First of all the current traffic flow (number of vehicles within time and vehicle speed) on the main and side roads is measured and transmitted in (nearby) real-time to the traffic flow management system. The traffic flow management system is able to calculate a traffic model and to control the traffic flow in a more efficient way. The traffic control can be achieved by traffic flow information displays informing the driver early about traffic jams and congested roads, by dynamically changeable traffic signs which can display speed limits to reduction following traffic, traffic signs with drive directions to guide the traffic via less used roads, and by controllable traffic lights to extend or to reduce the green light period to increase the vehicle throughput on heavy used roads.

5.2.1.4 Information Exchanges

Editors note: In this clause, definitions are provided for any information flows such as registration, Data Retrieval, or data delivery implied by the use case. Provide description for each type of information flow.

ETSI

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

5.2.1.5 Requirements

5.2.2 Street Light Control

5.2.2.1 General Use Case Description
Street lights in cities do not need to shine always the same. It depends on the time and other conditions like moonlight or snow whether it is sufficient to switch on only some street lights or to reduce their light intensity. This helps to reduce the energy consumption and CO2 emission.

5.2.2.2 Stakeholders

5.2.2.3 Scenario
The street light controller of each street light segment is connected with the central street light managing and control system. Based on local information measured by local sensors the control system can dim the corresponding street lights of a segment remotely or is able to switch street lights on and off.

5.2.2.4 Information Exchanges

5.2.2.5 Requirements

5.2.3 Passenger Information System for Public Transport

5.2.3.1 General Use Case Description
Public transport vehicles, like busses, street cars, subways and other types of city trains, are not always in time. Passenger need to know when their next connection is available so that the passengers can spend the real remaining time best. This kind of information serves also passengers to select alternative connections in the case of longer delays.

5.2.3.2 Stakeholders

5.2.3.3 Scenario
The current locations of the different public transport vehicles are provided to the central system which is able to match the current location with the forecasted location at each time or at specific check points, like bus stops. Based on the time difference the system is able to calculate the current delay and the expected arrival time at the next following stops. The vehicle location can be captured via check points on the regular track or via GPS/GPRS tracking devices which provide the position information in regular intervals. For some vehicles, like subways, GPS/GPRS is not proper due to tunnels without satellite connection. Check point sensors on the other hand have to be able to differentiate for instance different bus lines which are servicing the same bus stop. Therefore simple sensors which just recognise that it is a public transport vehicle are in most scenarios not sufficient. Not only the sensors but also the passenger displays has to be connected with the central system.

5.2.3.4 Information Exchanges

a) Check Point based

ETSI

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

The line number (of the bus or the street car) has to be captured at each station where the vehicle stops regularly or at defined check point in between. Due to the fact that the sensor at a specific station has provided the data to the central system the delay can easily be calculated to due to the information of the scheduled arrival time and the actual arrival time. This change can be add to the arrival time displayed at each following station. each vehicle has to be equipped with a kind of transponder (based on infrared, RFID, short-range communication, or optical recognition. In addition each station has to be equipped with one or more check point system which are able to readout or to receive the line number information of the vehicle. In case of larger stations with several platforms multiple systems are needed. b) GPS/GPRS based Each vehicle has to be equipped with a GPS/GPRS tracking device which provide beside the current position also the information which can be directly or indirectly matched to the serviced line number. Based on the regular position/time pattern the system is able to calculate the actual time difference and to provide the expected time on the passenger display. Each vehicle has to be equipped with a tracking device. A combination of check point based and GPS/GPRS based solution is suitable to integrate railed vehicles (like subways and street cars) and road vehicles (like busses) and to eliminate technical restrictions or disadvantages of the one or the other solution.

5.2.3.5 Requirements

ETSI

10

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

Annex <A>: Title of annex

A.1
<Text>

First clause of the annex

First subdivided clause of the annex

A.1.1
<Text>

ETSI

11

Draft ETSI TR 102 897 V<0.1.1> (2010-01)

History
Document history
<Version> 0.0.1 0.0.2 0.1.1 <Date> 01-2010 01-2010 03-2010 <Milestone> First Draft First Draft (only cosmetic changes) Second Draft M2M#09 output

ETSI