BSI PD ISO/TR 17427-3:2015
$215.11
Intelligent transport systems. Cooperative ITS – Concept of operations (ConOps) for ‘core’ systems
| Published By | Publication Date | Number of Pages |
| BSI | 2015 | 110 |
This Technical Report provides the high-level generic requirements for the “Concept of operations” for a ‘Core System’ (CorSys) (3.10) to support C-ITS service delivery. It is intended as an input to the planning and development elaboration of core functions that will support the deployment of cooperative intelligent transport systems (C-ITS) in a connected vehicle-highway paradigm
The objective of this Technical Report is to raise awareness of and consideration of such issues and to give pointers, where appropriate, to standards existing that provide specifications for all or some of these aspects. This Technical Report does not provide specifications for solutions of these issues.
This Technical Report is agnostic in respect of technology and operates with whatever (and probably
multiple) communications technologies and hardware technologies that can support its functionalities.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 8 | Foreword |
| 10 | Introduction |
| 12 | 1 Scope 2 Normative references 3 Terms and definitions |
| 15 | 4 Abbreviated terms |
| 16 | 5 Using this Technical Report 6 Overview of the role of a ‘Core System’ in C-ITS 6.1 What is a Concept of operations? |
| 17 | 6.2 What are the core functions? 6.3 Functional subsystems |
| 18 | 6.4 Institutional context |
| 19 | 6.5 Specific service features characterizing C-ITS service provision |
| 21 | 6.6 C-ITS and communication technologies 6.6.1 General 6.6.2 VANETs, MANETs and ‘latency’ |
| 24 | 6.6.3 Hybrid communications |
| 26 | 6.6.4 Short and medium range communication |
| 27 | 6.6.5 Long range communication 6.6.6 Wide area broadcast 6.6.7 Positioning services |
| 28 | 6.6.8 Digital road map data 6.7 Actors involved in C-ITS service provision |
| 31 | 6.8 C-ITS enabling data |
| 33 | 6.9 Cooperative ITS applications and services |
| 34 | 6.9.1 System of systems 6.10 C-ITS Privacy and anonymity 6.10.1 Privacy overview |
| 35 | 6.10.2 Data messages and privacy |
| 36 | 6.10.3 Security 6.10.4 Data management (including capture, storage and access) |
| 37 | 7 ‘Core’ systems 7.1 Core system overview 7.1.1 General |
| 38 | 7.1.2 Single core systems 7.1.3 Multiple core systems 7.1.4 Other ‘Central’ systems |
| 39 | 7.1.5 Facilitate a platform for sharing of information and efficient use of resources 7.2 Justification for ‘Core Systems’ 7.2.1 Vision, drivers and objectives |
| 40 | 7.2.2 Key strategic objectives for the deployment of core system support 7.2.3 Key technical objectives for the deployment of core system support |
| 41 | 7.2.4 Principal elements of a core system |
| 42 | 7.2.5 Proposed features of C-ITS core systems |
| 46 | 7.2.6 Main mission of the ‘Core System’ |
| 47 | 7.2.7 Scope of ‘Core System’ services 7.2.8 Exclusions from CorSys 7.2.9 Probe data storage |
| 48 | 7.2.10 Roadside equipment (RSE) 7.2.11 External support systems (ESS) 7.2.12 Communications options |
| 49 | 7.2.13 Authority/jurisdiction databases |
| 50 | 7.2.14 Core system stakeholders 7.2.15 Core system communications |
| 53 | 7.2.16 Applications 7.2.17 Core system interactions |
| 54 | 7.2.18 Core system operational goals |
| 55 | 7.3 ‘Core system’ overview of requirements 7.3.1 Definition of a requirement 7.3.2 ‘Core System’ requirements identification process |
| 60 | 7.3.3 Functional components |
| 61 | 7.4 Background, objectives and scope of a ‘Core System’ |
| 62 | 7.5 Operational policies and constraints 7.5.1 Certification |
| 63 | 7.5.2 Operations and maintenance 7.5.3 Security management 7.5.4 Data provision/ownership 7.5.5 System performance management |
| 64 | 7.5.6 Flexibility 7.5.7 Core system characteristics and environment |
| 65 | 7.5.8 Deployment configurations 7.5.9 Deployment footprint |
| 68 | 7.5.10 Subsystems 7.5.11 Subsystem descriptions |
| 73 | 7.6 Modes of operation |
| 75 | 7.7 User types and other involved personnel |
| 76 | 7.8 Operational scenarios |
| 77 | 7.9 Vehicle-originated broadcast |
| 80 | 7.10 Infrastructure-vehicle-unicast |
| 82 | 7.11 Support environment |
| 83 | 7.11.1 Subsystems 7.11.2 Personnel 7.11.3 Processes 7.12 Disadvantages and limitations |
| 84 | 8 Example use cases 8.1 General |
| 85 | 8.2 Example Use Case (1): User data exchange |
| 86 | 8.3 Example Use Case (2): Certificate distribution 8.4 Example Use Case (3): Certificate revocation list distribution |
| 87 | 8.5 Example Use Case (4): Misbehaviour action: Certificate revocation list addition |
| 88 | 8.6 Example Use Case (5): Data subscription |
| 89 | 8.7 Example Use Case (6): Remote services |
| 90 | 8.8 Example Use Case (7): Core service status distribution |
| 91 | 8.9 Example Use Case (8): ‘Core System’ operations 8.10 Example Use Case (9): System expansion |
| 92 | 8.11 Example Use Case (10): Core discovery |
| 93 | 8.12 Example Use Case (11): Service data backup 8.13 Example Use Case (12): Service takeover |
| 94 | 9 Summary of impacts 9.1 Operational impacts 9.1.1 Policy |
| 95 | 9.1.2 System management |
| 96 | 9.1.3 System operation 9.1.4 Service receipt |
| 98 | 9.2 Organizational impacts 9.2.1 Policy |
| 99 | 9.2.2 System management |
| 100 | 9.2.3 System operation 9.3 Impacts during the deployment phases |
| 101 | 9.3.1 System management 9.4 Measuring the impacts |
| 102 | 10 Cooperative vehicle and highway systems policy and institutional issues 11 Funding and governance |
| 105 | Bibliography |
Related products
-
BSI PD ISO/TR 17427-3:2015
Intelligent transport systems. Cooperative ITS – Concept of operations (ConOps) for ‘core’ systems Published By…
-
BSI PD ISO/TR 17427-3:2015
Intelligent transport systems. Cooperative ITS – Concept of operations (ConOps) for ‘core’ systems Published By…
