Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD ISO TR 17427 โ Intelligent Transport Systems Cooperative ITS (C-ITS) Technical Report Series
Intelligent transport systems โ Cooperative ITS (C-ITS) (PD ISO/TR 17427)
๐ PD ISO TR 17427 is the British Standards Institution’s Published Document (PD) adoption of ISO/TR 17427, “Intelligent transport systems โ Cooperative Intelligent Transport Systems (C-ITS)”. Through real-time information exchange between vehicles (V2V), vehicles and infrastructure (V2I), and vehicles and people, C-ITS upgrades “single-vehicle intelligence” into “transport-system intelligence”, improving road safety, traffic efficiency, and the traveller experience. Published as a series of technical reports, it sets out the framework, roles and responsibilities, concept of operations (ConOps), and key applications of C-ITS. It is maintained by Technical Committee EPL/278 (Intelligent transport systems).
๐ก The essential difference between C-ITS and single-vehicle perception is “cooperation”: a vehicle does not just “see” its surroundings but, through communication, “knows” about traffic conditions, signal phases, and incidents kilometres ahead. The 17427 series provides the conceptual and framework foundation for this cooperative system.
1. Series Overview and the C-ITS Framework ๐
Part 2 (Framework overview) is the series’ key document, defining the overall C-ITS framework: the participating entities (vehicles, infrastructure, central platforms, third-party service providers), the types of interaction (V2V, V2I, I2V, etc.), the characteristics of communication and data exchange, and the base capabilities a “Core System” must provide. Part 3 (ConOps for ‘core’ systems) develops the Concept of Operations of the core system using systems-engineering methods: it defines the system mission, stakeholders, operational scenarios, and key performance requirements โ the common baseline for discussing “how the system operates” in all later parts.
โ ๏ธ C-ITS is a classic “multi-party, multi-system” engineering effort: vehicle-side, roadside, cloud platforms, and regulators all participate. Without unified terminology and roles, cross-project collaboration easily loses coherence. The Part 2 framework and the Part 3 ConOps are where alignment starts.
2. Series Composition and Key Points ๐ง
| Part | Subject | Key Content | Readability |
|---|---|---|---|
| PD ISO/TR 17427-2 | Framework overview | Framework overview: entities, interaction types, and core-system capabilities | Readable |
| PD ISO/TR 17427-3 | ConOps for ‘core’ systems | Concept of Operations of the core system | Readable |
| PD ISO/TR 17427-4 | Applications and services | Typical C-ITS applications and services (scanned, summarised from public-domain knowledge) | Scanned |
| PD ISO/TR 17427-6 | Data exchange and roles | Data exchange and stakeholder roles/responsibilities (scanned, summarised from public-domain knowledge) | Scanned |
| PD ISO/TR 17427-7 | Deployment and architecture | Deployment and architecture considerations (scanned, summarised from public-domain knowledge) | Scanned |
| PD ISO/TR 17427-8 | Standards landscape | Survey of relevant standards and regulatory framework (scanned, summarised from public-domain knowledge) | Scanned |
| PD ISO/TR 17427-9 | Policy and privacy | Policy, privacy, and security-related content (scanned, summarised from public-domain knowledge) | Scanned |
| PD ISO/TR 17427-10 | Driver distraction and information display | Driver distraction and information display | Readable |
๐จ Scanned-version note: Parts 4, 6, 7, 8, and 9 are derived from scanned originals. The descriptions in this article are written from public-domain knowledge; the official BSI published version takes precedence.
3. Key Technical Requirements: ConOps and Driver Distraction ๐ฅ
Part 3 (core-system ConOps) is the key to understanding C-ITS engineering implementation. Following the standard ConOps structure, it answers “why the system exists, whom it serves, how it operates, and what performance it needs”: mission and goals, principal stakeholders and their concerns, operational scenarios (motorways, urban intersections, adverse weather), system capabilities (sensing, communication, decision-making, human-machine interface), and key operational constraints (latency, reliability, coverage). When authorities develop national C-ITS deployment plans, this ConOps is commonly used as the template.
Part 10 (driver distraction and information display) addresses the safety-critical HMI (human-machine interface) stage: it sets out the principles for presenting C-ITS information to the driver, including the trade-off of information priority and timing, display location and modality (acoustic/visual/tactile), avoiding information overload and attention diversion, and methods for assessing distraction risk. It is the last interface that turns “technical information” into “safe driving behaviour”.
โ
Good information display is “an interruption that is just right”: time-critical information (e.g. sudden braking ahead, incidents) is presented prominently and promptly, while non-urgent information (e.g. service-area notices) is delivered quietly. The priority and presentation principles of Part 10 are central to C-ITS HMI design.
4. Engineering Practice ๐ ๏ธ
- ๐ Pilot-project planning: cities and connected-vehicle pilots can write their Concept-of-Operations documents using the Part 3 template, defining goals, scenarios, and acceptance criteria.
- ๐ง System architecture design: allocate vehicle-side, roadside, and platform responsibilities per the Part 2 framework, and follow the overall idea of the scanned Part 7 (architecture considerations) to define the layered architecture (summarised from public-domain knowledge).
- ๐ HMI design: design the priority, timing, and presentation of alerts per the Part 10 principles, and run distraction-risk assessment and on-vehicle testing.
- ๐ Policy and compliance: together with the scanned Parts 8 (standards landscape) and 9 (policy and privacy), survey relevant standards and regulatory requirements to guide project initiation and data compliance (summarised from public-domain knowledge).
5. Frequently Asked Questions โ
โ Q: What is the relationship between C-ITS and autonomous driving?
A: C-ITS is the cooperative transport infrastructure that provides autonomous driving with information beyond single-vehicle perception (e.g. signal-phase timing, remote incidents); autonomous driving focuses on single-vehicle decision-making. The two are complementary, and V2X communication is often considered necessary support for higher-level automated driving.
A: C-ITS is the cooperative transport infrastructure that provides autonomous driving with information beyond single-vehicle perception (e.g. signal-phase timing, remote incidents); autonomous driving focuses on single-vehicle decision-making. The two are complementary, and V2X communication is often considered necessary support for higher-level automated driving.
โ Q: Why is a “Concept of Operations” document needed?
A: C-ITS involves many parties; first unifying in natural language “whom the system serves, what it does, and how it runs” (Part 3) before detailed design significantly reduces requirement divergence and rework โ a standard systems-engineering practice.
A: C-ITS involves many parties; first unifying in natural language “whom the system serves, what it does, and how it runs” (Part 3) before detailed design significantly reduces requirement divergence and rework โ a standard systems-engineering practice.
โ Q: Why is Part 10 important?
A: If C-ITS information is presented poorly, it can actually distract the driver and increase accident risk. Part 10 specifies the principles of presentation priority, timing, and modality, forming the basis for in-vehicle HMI compliance and safety assessment.
A: If C-ITS information is presented poorly, it can actually distract the driver and increase accident risk. Part 10 specifies the principles of presentation priority, timing, and modality, forming the basis for in-vehicle HMI compliance and safety assessment.
๐ Q: To what extent can the scanned parts be referenced?
A: The descriptions of the scanned parts in this article are written from public-domain knowledge and marked “scanned version”. For specific framework elements or clauses, follow the official BSI published version.
A: The descriptions of the scanned parts in this article are written from public-domain knowledge and marked “scanned version”. For specific framework elements or clauses, follow the official BSI published version.