Results for area 13.4 ITS station architecture
functional entity, i.e. an ITS-S application process
service provided by a service provider accessing data from the IVS in a vehicle in the case of C-ITS, via a wireless communications network, or provided on-board the vehicle as the result of software (and potentially also hardware and firmware) installed by a service provider or to a service provider’s instruction
data elements and frames comprising a message, the contents of which describe the geometry of a roadway intersection
NOTE 1 to entry In the context of USDOT J2735™ SE Candidate, the MAP message provides the road geometry at an intersection.
NOTE 2 to entry It is broadcast from the infrastructure to the vehicle.
NOTE 3 to entry The MAP message contains geographic intersection description (GID) data.
sequence of type-length-value (TLV) encoded data objects
identifiable sequence of packets of a given ITS-S flow type transmitted between a source node and a destination node
uniquely addressable protocol functionality
NOTE 1 to entry Examples of ITS-S capabilities are Content Subscription Handler (CSH), Facilities Service Handler (FSH), Communication Profile Handler (CPH).
delivery of a message to a group of network destinations identified by their geographic locations
header of the “ITS-S generic data container format” uniquely identifying the data contained in the ITS-S data containers by means of data dictionary identifiers unique in the ITS domain and the number of data objects from the data dictionary in the container
header used to form an “ITS-S facilities layer protocol data unit”
identifier, being unique within the ITS station, that identifies an ITS-S flow
identifier, being unique within the ITS station that identifies an ITS-S flow type
repository used by the ‘Data Distribution subsystem’ for maintaining data publishers information including the type of data they are transmitting, frequency of that data, address, data source, etc.
communication protocol applicable in ITS
parameterized ITS-S communication protocol stack (set of protocols composing all the ITS station layers) that allows communication end points to communicate with one another
format of an ADU exchanged between an “ITS-S application process” and a Content Subscription Handler (CSH) or between two peer CSHs containing an “ITS-S data header” and followed by a number of “ITS-S data containers”
uniquely addressable entity in an ITS-S layer comprised of a set of related ITS-S capabilities
NOTE 1 to entry Examples of ITS-S managed service entities are: a communication module in the ITS-S access technologies layer (M5, cellular, etc.), a protocol suite in the ITS-S networking & transport layer (IPv6, FNTP, GeoNetworking, 6LoWPAN, etc.), and MSEGenFac, the entity comprising the generic ITS-S facilities services specified in this Technical Specification (CPH, CSH, the FSH and possibly more).
ITS-S flow that has been allocated an ITS-S-FlowID
functional entity providing security functionality for use by an ITS-S application process
set of characteristics describing a data flow
functional entity constituting endpoints of ITS-S application process activity
SAE J2735™ message from the infrastructure to the C-ITS device that contains the infrastructure’s response details to a signal request message (SRM) for requesting priority from an intersection’s traffic signal controller