ForewordIntroductionScopeNormative referencesTerms and definitionsAbbreviated termsConformanceGeneral overview and frameworkRequirements for services using generic vehicle dataGeneralRegulated application services using only generic basic vehicle data Regulated application services using both generic vehicle data and additional regulated application specific dataConveyance identifiersApplication services that require data in addition to basic vehicle data General Concept of operations for identified regulated application services with additional data requirements using roadside sensorsGeneralStatement of the goals and objectives of the systemStrategies, tactics, policies, and constraints affecting the systemOrganizations, activities, and interactions among participants and stakeholdersClear statement of responsibilities and authorities delegatedUserApplication service providerApplication serviceOperational processes for the systemService requirements definitionSequence of operations for identified regulated application services with additional data requirementsGeneral sequence of operationsCommandsGET TARV LDTCREATE and GET CoreDataQuality of service requirementsTest requirementsMarking, labelling and packagingCommon features of regulated TARV application servicesGeneric operational processes for the systemCommon role of the userRole of the driverRole of the operatorCommon characteristics for instantiations of regulated application servicesCommon sequence of operations for regulated application servicesQuality of serviceInformation securityData naming content and qualitySoftware engineering quality systemsQuality monitoring stationAuditsData access control policyApproval of IVSs and service providerApproval of road side sensorsApplication examples (informative)GeneralRegulated heavy vehicle movement enforcement enhancement systemUse case definitionsRoadside sensors (informative)GeneralJurisdiction can use this link for many purposesProposed roadside sensor examplesMultiple functional devicesBibliography