Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO 29281-1:2018 — Intelligent Transport Systems — Fast Networking and Transport Protocol (FNTP)
Localized Communications Protocol for Intelligent Transport Systems — Fast Networking and Transport Layer
Introduction
ISO 29281-1:2018, developed by ISO/TC 204, specifies the Fast Networking and Transport Protocol (FNTP) for localized communications in Intelligent Transport Systems (ITS). This second edition completely revises the first edition (2013) to align with the common message format harmonized with IEEE WAVE. FNTP provides efficient networking and transport services for ITS applications requiring low-latency, localized data exchange, such as collision avoidance, hazard warnings, and intersection management.
FNTP is designed for latency-sensitive ITS applications. Unlike TCP/IP, which requires connection establishment, FNTP supports rapid data dissemination in localized areas with minimal overhead.
Protocol Architecture and Key Components
FNTP operates within the ITS station architecture (ISO 21217) and defines three transport protocol identifier field subtypes (TPID-FS): information dissemination mode (TPID-FS zero), general session mode (TPID-FS one), and LPP support mode (TPID-FS two).
| TPID-FS | Mode | Use Case |
|---|---|---|
| Zero | Information dissemination | Broadcast safety messages, beacons |
| One | General session | Dedicated communication sessions |
| Two | LPP support | Location-based positioning protocol |
The protocol defines three NPDU subtypes (zero, one, two) for network layer handling and supports N-Extensions and T-Extensions for flexible functionality expansion. Service access points (IN-SAP, NF-SAP, MN-SAP, SN-SAP) are defined for inter-layer communication.
Engineering Design Insights
Protocol Procedures and Data Management
The standard specifies comprehensive procedures for: port management, forwarding table maintenance, communication interface priority (CIP) management, and specific transmit/receive procedures for each TPID-FS type. The ITS-AID look-up table and service look-up table enable application identification and service discovery. Forwarding tables maintain routing information for ITS station hosts and routers.
Conformance and Testing
Annex C provides a Protocol Implementation Conformance Statement (PICS) proforma, enabling manufacturers to declare which protocol features are implemented. Annex D specifies path and flow management support. ASN.1 modules in Annex A provide formal data structure definitions, ensuring interoperability between different implementations.
FNTP’s efficient design makes it suitable for hard real-time ITS applications where communication delays must be in the millisecond range, such as pre-crash sensing and cooperative adaptive cruise control.
FAQs
Q1: How does FNTP differ from conventional TCP/IP?
A: FNTP is designed for localized, low-latency communication without connection establishment overhead. It supports rapid broadcast of ITS messages in a localized geographic area.
A: FNTP is designed for localized, low-latency communication without connection establishment overhead. It supports rapid broadcast of ITS messages in a localized geographic area.
Q2: What is the relationship between ISO 29281-1 and IEEE WAVE?
A: The second edition harmonizes FNTP with IEEE WAVE (1609 family) through the common message format specified in ISO TS 16460, ensuring interoperability between the two protocol families.
A: The second edition harmonizes FNTP with IEEE WAVE (1609 family) through the common message format specified in ISO TS 16460, ensuring interoperability between the two protocol families.
Q3: What security provisions are included?
A: The standard references secure communication mechanisms, and the protocol supports authenticated and encrypted message exchange for safety-critical ITS applications.
A: The standard references secure communication mechanisms, and the protocol supports authenticated and encrypted message exchange for safety-critical ITS applications.
Q4: Can FNTP be used for non-ITS applications?
A: While designed specifically for ITS localized communications, the protocol’s efficient design could be adapted for other domains requiring low-latency localized data dissemination.
A: While designed specifically for ITS localized communications, the protocol’s efficient design could be adapted for other domains requiring low-latency localized data dissemination.
