180 likes | 336 Views
Definition of C-ITS. How do the WGs fit together?. (Based on a design concept of AustRoads, 2010). Cooperative System: ISO/CEN Definition. Co-operative ITS is a subset of the overall ITS that communicates and shares information between ITS stations * to give advice or facilitate actions
E N D
How do the WGs fit together? (Based on a design concept of AustRoads, 2010)
Cooperative System: ISO/CEN Definition • Co-operative ITS is a subset of the overall ITS that • communicates and • shares information • between ITS stations* to • give advice or • facilitate actions • with the objective of improving • safety, sustainability, efficiency and comfort • beyond the scope of stand-alone systems. * The term ITS Station is defined in ISO 21217 / ETSI EN 302 665 and includes units installed in vehicles, at the road side, in traffic control/management centers, in service centers, and hand-held units.
Network perspective Legacy Network Legacy Stand-alone subsystem Cooperative ITS Domain ITS-S ITS-S ITS-S Communications Network
Network perspective • A cooperative ITS domain: • consists of a dynamic network of mutually reachable ITS Stations, that • implements cooperative ITS applications and services, and • may link to legacy ITS networks, applications and services
Service/application perspective • Overall ITS includes the full set of ITS related applications, services and operations • Cooperative ITS is a subset that shares necessary information across application areas, e.g. info generated for safety purposes can be used for efficiency applications
Cooperative Activity Perspective • Cooperative ITS is a concept of collaboration where • one or more ITS stations (ITS-S) belong to a “cooperative ITS domain” • and these ITS-Ss engage in “cooperative ITS activities” • A cooperative ITS activity includes exchange of information to improve safety, sustainability, efficiency and comfort. Examples include: • Road cone transmitting safety related info • ITS stations exchanging CAMs • Bus ITS-S and Intersection ITS-S exchanging realtime status info for intersection prioritization.
Activities that are NOT Cooperative • Examples of ITS activities that are NOT cooperative ITS activities include: • ITS stations exchanging information using proprietary applications that do NOT make the information available for other applications and services involved in improving safety, sustainability, efficiency and comfort. • A vehicular ITS-S exchanging proprietary EFC information with a roadside ITS-S toll collection unit where the information is NOT shared with other applications and services involved in improving safety, sustainability, efficiency and comfort. • A regulatory agency central ITS-S collecting information from vehicular ITS-Ss in regulated vehicles where that information is NOT used or shared with other applications and services involved in improving safety, sustainability, efficiency and comfort. NOTE: ALL these example can be made cooperative ITS activities simply by sharing the information being exchanged with other applications and services involved in improving safety, sustainability, efficiency and comfort. 8
Activities that are NOT Cooperative • A more complex example of an ITS activity that is NOT a cooperative ITS activity: • A legacy vehicular toll tag exchanging proprietary EFC information with a legacy roadside DSRC toll collection unit where the information CAN NOT be shared with any ITS-S applications and services involved in improving safety, sustainability, efficiency and comfort BECAUSE the legacy system can neither be managed nor trusted by an ITS-S. NOTE: To make this activity cooperative the legacy equipment must be incorporated into an ITS-S where it can be managed and secured AND then the information exchanged can be shared with ITS-S applications and services involved in improving safety, sustainability, efficiency and comfort. 9
Cooperative ITS implementation • Target ITS-S implementation scenario (or Profile Set) combines: • active safety, • sustainable and efficient transport, • “app-store market place” • ITS-S definition includes: • A common platform* that allows • Applications to be downloaded and remotely managed, based on a • Common data set, security features and flexible communications, • A platform is characterized by testable/verifiable: • Communications interface(s) • API for portable applications • Facilities functionalities • Application processing performance level • Security implementation
What should SDOs do? • Whatever else, SDOs need to avoid creating new silos “competing” with current work
Challenge • The current SDOs (WGs) mostly work on a WG-internal mix of: • Technical Base Standards (data, protocol, link, HMI,…) • Application/Use Case standards using the base stds. • We need to facilitate a split, where • the Base Standard experts coordinate a common set • Application/UC experts generate new profile standard sets. • How do we do that?
C-ITS Standards Development Use Case / Application Profile Standards App 4 App 3 ISO 12345 App 2 Cooperative base standards C-ITS Data Set .1 X C-ITS Security Set C-ITS Conformance Testing .2 C-ITS Interface Set .3 C-ITS Protocol Set .4 C-ITS Identifier Set X .5 C-ITS API Set