< < VS18 : VS19 : WX01 > >

VS19: Vulnerable Road User Clustering

This service package supports the exchange of messages between surrounding equipped travelers (pedestrians, cyclists, etc.) using their personal information device or on equipped micromobility vehicles to support the platooning or clustering of the travelers. This short-range communications between MMVs operating as a group, platoon or 'strings' of VRUs can coordinate to establish a lead vehicle and following vehicles for better path trajectory prediction by other equipped vehicles.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements
Implementations

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Micromobility Vehicle OBE Developer	Micromobility Vehicle OBE	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Micromobility Vehicle OBE Developer	Other Micromobility Vehicle OBEs Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Micromobility Vehicle OBE Developer	Personal Information Device Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Micromobility Vehicle OBE Developer	Transportation Information Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Other Micromobility Vehicle OBEs Developer	Micromobility Vehicle OBE Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Other Micromobility Vehicle OBEs Developer	Other Micromobility Vehicle OBEs	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Other PIDs Developer	Other PIDs	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Other PIDs Developer	Personal Information Device Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Personal Information Device Developer	Micromobility Vehicle OBE Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Personal Information Device Developer	Other PIDs Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Personal Information Device Developer	Personal Information Device	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Personal Information Device Developer	Transportation Information Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Transportation Information Center Developer	Transportation Information Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Micromobility Vehicle OBE Installer	Micromobility Vehicle OBE	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Micromobility Vehicle OBE Owner	Micromobility Vehicle OBE Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Micromobility Vehicle OBE Owner	Micromobility Vehicle OBE Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Other Micromobility Vehicle OBEs Installer	Other Micromobility Vehicle OBEs	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Other Micromobility Vehicle OBEs Owner	Other Micromobility Vehicle OBEs Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other Micromobility Vehicle OBEs Owner	Other Micromobility Vehicle OBEs Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Other PIDs Installer	Other PIDs	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Other PIDs Owner	Other PIDs Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other PIDs Owner	Other PIDs Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Personal Information Device Installer	Personal Information Device	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Personal Information Device Owner	Personal Information Device Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Personal Information Device Owner	Personal Information Device Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Transportation Information Center Installer	Transportation Information Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Transportation Information Center Owner	Transportation Information Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transportation Information Center Owner	Transportation Information Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Micromobility Vehicle OBE Maintainer	Micromobility Vehicle OBE	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Micromobility Vehicle OBE Manager	Micromobility Vehicle OBE	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Micromobility Vehicle OBE Manager	MMV User	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Micromobility Vehicle OBE Owner	Micromobility Vehicle OBE Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Micromobility Vehicle OBE Owner	Micromobility Vehicle OBE Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Micromobility Vehicle OBE Owner	Other Micromobility Vehicle OBEs Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Micromobility Vehicle OBE Owner	Other Micromobility Vehicle OBEs Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Micromobility Vehicle OBE Owner	Other Micromobility Vehicle OBEs User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Micromobility Vehicle OBE Owner	Pedestrian	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Micromobility Vehicle OBE Owner	Pedestrian	Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Micromobility Vehicle OBE Owner	Personal Information Device Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Micromobility Vehicle OBE Owner	Personal Information Device Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Micromobility Vehicle OBE Owner	Personal Information Device User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Micromobility Vehicle OBE Owner	Transportation Information Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Micromobility Vehicle OBE Owner	Transportation Information Center Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Micromobility Vehicle OBE Owner	Transportation Information Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Micromobility Vehicle OBE Supplier	Micromobility Vehicle OBE Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
MMV User	Micromobility Vehicle OBE	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Other Micromobility Vehicle OBEs Maintainer	Other Micromobility Vehicle OBEs	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Other Micromobility Vehicle OBEs Manager	Other Micromobility Vehicle OBEs	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Other Micromobility Vehicle OBEs Owner	Micromobility Vehicle OBE Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Other Micromobility Vehicle OBEs Owner	Micromobility Vehicle OBE Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Other Micromobility Vehicle OBEs Owner	Micromobility Vehicle OBE User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Other Micromobility Vehicle OBEs Owner	MMV User	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Other Micromobility Vehicle OBEs Owner	MMV User	Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Other Micromobility Vehicle OBEs Owner	Other Micromobility Vehicle OBEs Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Other Micromobility Vehicle OBEs Owner	Other Micromobility Vehicle OBEs Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Other Micromobility Vehicle OBEs Supplier	Other Micromobility Vehicle OBEs Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Other PIDs Maintainer	Other PIDs	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Other PIDs Manager	Other PIDs	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Other PIDs Owner	Other PIDs Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Other PIDs Owner	Other PIDs Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Other PIDs Owner	Pedestrian	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Other PIDs Owner	Personal Information Device Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Other PIDs Owner	Personal Information Device Owner	Information Provision and Action Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Other PIDs Owner	Personal Information Device User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Other PIDs Supplier	Other PIDs Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Pedestrian	Personal Information Device	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Personal Information Device Maintainer	Personal Information Device	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Personal Information Device Manager	Pedestrian	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Personal Information Device Manager	Personal Information Device	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Personal Information Device Owner	Micromobility Vehicle OBE Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Personal Information Device Owner	Micromobility Vehicle OBE Owner	Information Provision and Action Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personal Information Device Owner	Micromobility Vehicle OBE User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Personal Information Device Owner	MMV User	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Personal Information Device Owner	Other PIDs Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Personal Information Device Owner	Other PIDs Owner	Information Provision and Action Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personal Information Device Owner	Other PIDs User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Personal Information Device Owner	Personal Information Device Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Personal Information Device Owner	Personal Information Device Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Personal Information Device Owner	Transportation Information Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Personal Information Device Owner	Transportation Information Center Owner	Information Provision and Action Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personal Information Device Owner	Transportation Information Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Personal Information Device Supplier	Personal Information Device Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Transportation Information Center Maintainer	Transportation Information Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Transportation Information Center Manager	Transportation Information Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Transportation Information Center Owner	Transportation Information Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Transportation Information Center Owner	Transportation Information Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Transportation Information Center Supplier	Transportation Information Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Micromobility Vehicle OBE	MMV Cooperative Information	3.7.1	Manage MMV Safety Communications
	MMV Cooperative Information	3.7.3	Provide MMV User Safety Interface
	MMV Safety Communication	3.7.1	Manage MMV Safety Communications
	MMV Safety Communication	3.7.3	Provide MMV User Safety Interface
Personal Information Device	Personal Cooperative Information	6.8.3.6	Provide Personal Safety Messages
	Personal Cooperative Information	6.8.4.3	Provide Traveler Personal Wayfinding Interfaces
	Personal Pedestrian Safety	6.8.1.3	Process Personal Portable Device Location Data
		6.8.2.3	Monitor Pedestrian Safety Status
		6.8.2.4	Provide Pedestrian Personal Interface
		6.8.3.3	Provide Traveler Personal Interface
		6.8.3.6	Provide Personal Safety Messages
Transportation Information Center	TIC Data Collection	6.2.1	Collect Misc Traveler Information
		6.2.2	Collect Traffic Data
		6.2.3	Collect Transit Operations Data
		6.2.4	Collect Multimodal Data
		6.2.5	Collect Situation and Sensor Data From Vehicles
		6.2.6	Collect Emergency Traveler Data
		6.5.4	Process Travel Services Provider Data
		6.6.2.3	Provide Route Segment Data for Other Areas
		7.4.2	Collect Price Data for Traveler Information Use

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram

Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object	Class	Description
Micromobility Vehicle OBE	Vehicle	The Micromobility Vehicle On-Board Equipment (MMV OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The MMV OBE includes general capabilities that apply to bicycles and other low-powered mobility devices such as e-scooters, powered wheelchairs, and power assisted bicycles. The MMV OBE includes the common interfaces and functions that could apply to any low-powered mobility device. The radio(s) supporting V2V and V2I communications are a key component of the MMV OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, and enhanced traveler interfaces (through PIDs), complement traveler information services so that, in addition to making informed mode and route selections, the vulnerable road user travels these routes in a safer and more consistent manner.
MMV User	Personal	The 'MMV User' represents the person that operates a micromobility vehicle (MMV). Included are cyclists and operators of other low-powered mobility devices such as e-scooters, powered wheelchairs, and power assisted bicycles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The MMV User participates in ITS services that support safe, shared use of the transportation network by motorized and non-motorized transportation modes. Representing those using non-motorized travel modes, and in particular bicyclists that sometimes share motor vehicle lanes, these MMV users provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by ITS services to improve safety. The MMV User originates requests and receives information that reflects the interactions which might be useful to all users, regardless of vehicle type.
Other Micromobility Vehicle OBEs	Vehicle	'Other Micromobility Vehicle OBEs' represents other connected low-powered mobility devices that are communicating with a host micromobility vehicle OBE. This includes all connected PIDs, personnel devices, and micromobility vehicles that supports communications among vulnerable road users (P2P). This object provides a source and destination for information transfers between connected vulnerable road users. The host micromobility vehicle OBE sends information to, and receives information from the micromobility vehicle OBE to model communications between connected micromobility vehicles in ARC-IT.
Other PIDs	Personal	'Other PIDs' represents other personal information devices (PIDs) that are communicating with the device. This includes all connected personal information devices that support wireless short-range communications, including those used by pedestrians, cyclists, and other vulnerable road users (VRUs). This object provides a source and destination for information transfers between connected personal devices. The host device, represented by the Personal Information Device physical object, sends information to, and receives information from the Other PIDs to model all connected personal-to-personal (P2P) communications in ARC-IT.
Pedestrian	Personal	The 'Pedestrian' represents a person traveling on foot. Pedestrians participate in ITS services that support safe, shared use of the transportation network. Included are visually impaired travelers who travel through portions of the transportation network and interact with ITS systems. They provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by ITS services to improve safety
Personal Information Device	Personal	The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Transportation Information Center	Center	The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

Includes Functional Objects:

Functional Object	Description	Physical Object
MMV Cooperative Information	'MMV Cooperative Information' uses personal-to-vehicle (P2V) communications to share speeds and coordinate maneuvers with adjacent MMVs or VRUs on the same path (a 'string') so other connected devices recognize path predictions with other vulnerable road users in the string, thus improving safety.	Micromobility Vehicle OBE
MMV Safety Communication	'MMV Safety Communication' exchanges the current location and motion information of the MMV with other connected devices in the vicinity, uses that information to calculate traveler and vehicles paths, and warns the traveler when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of connected devices in the vicinity. Information from the infrastructure, e.g., a TIC or CVRE, can be used to detect non-equipped travelers. MMV location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications	Micromobility Vehicle OBE
Personal Cooperative Information	'Personal Cooperative Information' uses personal-to-vehicle (P2V) communications to share speeds and coordinate maneuvers with adjacent micromobility vehicles (MMVs) or other vulnerable road users (VRUs) equipped with their own personal information devices (PIDs) on the same path (a 'string') so other connected devices recognize path predictions with other VRUs in the string, thus improving safety.	Personal Information Device
Personal Device Coordination	'Personal Device Coordination' coordinates with the vehicle on-board equipment (Vehicle OBE), micromobility vehicle (MMV) OBE or similar vehicle class equipment so that the PID for the traveler is not broadcasting conflicting information or is interfering with the OBE for the vehicle that the traveler is traveling on.	Personal
Personal Pedestrian Safety	'Personal Pedestrian Safety' improves pedestrian, cyclist, and other vulnerable road user safety by providing personal location information to the infrastructure that can be used to avoid collisions involving vulnerable road users. It may also alert the vulnerable road user of unsafe conditions, augmenting or extending information provided by signals and signs. The information provided and the user interface delivery mechanism (visual, audible, or haptic) can also be tailored to the needs of the user that is carrying or wearing the device that hosts the application.	Personal Information Device
TIC Data Collection	'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers.	Transportation Information Center
Vehicle Device Coordination	'Vehicle Device Coordination' coordinates with the personal information device (PID) to transition between modes when the device used by the traveler or personnel no longer needs to broadcast safety and other information as well as when it is time to transition back to the personal device. This function also supports cases in which the PID will serve as the proxy for the vehicle onboard equipment and will act as a bridge to provide the vehicle’s status and operating conditions to the PID.	Vehicle

Includes Information Flows:

Information Flow	Description
device configuration coordination	A handshake between two different devices in the same vehicle or conveyance so the devices don't interfere with each or send conflicting information. This coordination may result in a personal information device (PID) carried by a traveler not transmitting its current location while on board vehicle, a transit vehicle, or a micromobility vehicle transmitting its vehicle profile and current location. For example, in the carry-in scenario, the personal device might go into a 'quiet' mode when carried into the vehicle that is already equipped with an integrated system that can broadcast safety messages.
MMV profile	Information about the micromobility vehicle such as type of micromobility vehicle, size and weight, vehicle performance (acceleration, top speed, turning radius) or other data that can be used to classify vehicle eligibility for access to specific lanes or road segments, or its projected path trajectory.
personal input	User input to a personal device. This flow may request traveler information, request right of way, summon assistance, make a reservation, or request any other traveler service. This flow also establishes the settings that tailor each application to suit the user's needs.
personal location	The current location (latitude, longitude, and elevation) reported by the personal information or safety device
personal updates	Personal information, alerts, and warnings provided to pedestrians, micromobility vehicle (MMV) users, work crew members, and other individuals in a mixed use area. This includes visual, audio, and haptic outputs that may be customized to support individual needs.
traveler sourced updates	Traveler posts on traffic and road conditions, parking availability, transit services, traveler services, shelter information, hazards, debris, obstacles, and other real-time crowd-sourced data that may be shared with other travelers.
VRU cluster information	Information indicating the formation and management of strings of VRUs and micromobility vehicles, which includes human powered vehicles such as bicycles, that may follow each other towards a common destination. This flow also supports identification of the lead MMV in the string so other MMVs can opt-in to join the string. The indication of participating in a string provides better predicted path trajectory prediction for all participating MMVs, enhancing safety. This flow also supports dissolution of MMV strings as MMVs depart from the string.
VRU hazard event	Notification of a potential hazard or event that is detected or reported by the traveler or vulnerable road user (VRU) using a PID or riding a micromobility vehicle (MMV). Potential hazards may be determined by sudden movements by travelers, such as movements around a location which may indicate foreign objects (people, animals, debris, other obstacles) in the travel lanes. Hazards may also be manually entered by the traveler into a personal information device (e.g., crowdsourcing) to be shared with other travelers.
VRU path prediction	The predicted future path of travel by the VRUs equipment. This flow includes an indication of the future positions of the transmitting traveler that can be used by receiving connected devices to support coordinated travel maneuvers and enhance collision avoidance.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users;	Reduce fatalities and injuries

Associated Objective Categories

Objective Category
Safety: Vehicle Crashes and Fatalities

Associated Objectives and Performance Measures

Objective	Performance Measure
Reduce crashes due to driver errors and limitations	Number of crashes and fatalities related to driver inattention and distraction
Reduce crashes due to driver errors and limitations	Number of crashes and fatalities related to driving while intoxicated
Reduce the number of pedestrian fatalities by X percent by year Y.	Number of pedestrian fatalities
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y.	Total crashes involving bicycles.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y.	Total crashes involving pedestrians.

Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need		Functional Object	Requirement
01	The Traveler needs to be warned about the proximity of other travelers, micromobility vehicles, and other vehicles in order to avoid a crash.	MMV Cooperative Information	02	The micromobility vehicle shall share information about hazards, debris, or obstacles with other MMVs or traveler information.
		MMV Safety Communication	01	The micromobility vehicle shall send location and motion information of the vehicle to nearby micromobility vehicles to warn the micromobility vehicle user about the potential for an impending collision.
		MMV Safety Communication	02	The micromobility vehicle shall receive location and motion information from nearby micromobility vehicles so that the micromobility vehicle can identify if a collision is imminent.
		Personal Device Coordination	04	The personal device shall receive a notification from a micromobility vehicle that the device is now on a moving micromobility vehicle and should transition to a mode where it does not provide personal safety notifications.
		Personal Pedestrian Safety	08	The personal traveler device shall share its location with other personal traveler devices to support safe movement among vulnerable road users.
		Personal Pedestrian Safety	09	The personal traveler device shall share information about hazards, debris, or obstacles with other traveler devices or traveler information.
02	Travelers, including pedestrians and users of micromobility vehicles (MMVs), need to be able to safely join or separate from a platoon or group of similar vehicle device types, including coordination of direction, speed and policies with other vehicles/conveyances in the platoon.	MMV Cooperative Information	01	The micromobility vehicle shall share location and motion information with adjacent micromobility vehicles or vulnerable road users on the same path (a 'string') in order to coordinate maneuvers.
		Personal Cooperative Information	01	The personal traveler devices shall share location and motion information with adjacent micromobility vehicles (MMVs) or other vulnerable road users (VRUs) equipped with their own personal information devices (PIDs) on the same path (a 'string') in order to coordinate maneuvers.
		Vehicle Device Coordination	02	The vehicle shall notify a personal device that the traveler is in a micromobility vehicle so that the traveler device can transition modes to one that receives personal safety information relevant to the micromobility vehicle.
03	Travelers need to be able to provide wayfinding information updates based on information collected by travelers or micromobility vehicles.	TIC Data Collection	24	The center shall collect, process, and store pathway information.

Related Sources

Document Name	Version	Publication Date
FHWA-JPO-23-986 - Enhancing the Safety of Vulnerable Road Users at Intersections	Final	2/1/2023
ISO 13111-1:2017: Intelligent transport systems (ITS) - The use of personal ITS station to support ITS service provision for travellers - Part 1: General information and use case definitions	Final	6/1/2017

Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Micromobility Vehicle OBE	Moderate	High	Moderate	Class 3
Other Micromobility Vehicle OBEs	Low	High	Moderate	Class 3
Other PIDs	Low	High	Moderate	Class 3
Personal Information Device	Moderate	High	Moderate	Class 3
Transportation Information Center	Moderate	Moderate	Low	Class 2

In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source	Destination	Information Flow	Confidentiality	Integrity	Availability
Source	Destination	Information Flow	Basis	Basis	Basis
Micromobility Vehicle OBE	MMV User	personal updates	Not Applicable	Moderate	Moderate
Micromobility Vehicle OBE	MMV User	personal updates	This data is informing the pedestrian about the safety of the intersections. It should not contain anything sensitive, and does not matter if another person can observe it.	This is the information that is presented to the individual. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights.	If this information is not made available to the pedestrian, then the system has not operated correctly.
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	MMV profile	Not Applicable	Moderate	Moderate
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	MMV profile	Information is partially observable, and is unlikely to compromise the vehicle user in any sense.	Some level of assurance that the information is correct is necessary as the information may be used to grant access to limited-access pathways.	Limited access pathways dedicated to particular types of MMVs should be generally available so as to ensure use of the asset.
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	personal location	Not Applicable	High	Moderate
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	personal location	This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators.	An incorrect location message could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity.	There are other visual indicators about the geofenced areas. PID users in dynamic environments (incident and work zones) should know when they are leaving a geofenced area. As long as they remain in the geofenced area, this information is not as necessary. Not all pedestrians will carry a personal information device, and the system should be able to operate without this information.
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	VRU cluster information	Low	High	Moderate
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	VRU cluster information	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	VRU hazard event	Low	High	Moderate
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	VRU hazard event	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	VRU path prediction	Low	High	Moderate
Micromobility Vehicle OBE	Other Micromobility Vehicle OBEs	VRU path prediction	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Micromobility Vehicle OBE	Personal Information Device	MMV profile	Not Applicable	Moderate	Moderate
Micromobility Vehicle OBE	Personal Information Device	MMV profile	Information is partially observable, and is unlikely to compromise the vehicle user in any sense.	Some level of assurance that the information is correct is necessary as the information may be used to grant access to limited-access pathways.	Limited access pathways dedicated to particular types of MMVs should be generally available so as to ensure use of the asset.
Micromobility Vehicle OBE	Transportation Information Center	traveler sourced updates	Moderate	Moderate	Low
Micromobility Vehicle OBE	Transportation Information Center	traveler sourced updates	This is likely to include the traveler location and may include traveler identity as well. This PII could be used by an attacker to the detriment of the traveler.	Quality of social media inputs may be highly variable, but no publicly distributable data should be exchanged without some protection over its transmission.	While a widespread and widely used dissemination channel, social media tends to be cluttered with lots of other information, so it is not a primary dissemination channel for this information.
MMV User	Micromobility Vehicle OBE	personal input	Not Applicable	Moderate	Low
MMV User	Micromobility Vehicle OBE	personal input	Personal input similar to pressing the button on a pedestrian call at a stop light, nothing that could not be otherwise observed.	This data does have to be correct, so the signal receives the pedestrian call. Given that the pedestrian should still not enter the intersection without feedback, this could be considered LOW.	There are generally other ways to accomplish this flow. Depending on the pedestrian this might be MODERATE, for example for pedestrians unable to easily access the call button.
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	MMV profile	Not Applicable	Moderate	Moderate
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	MMV profile	Information is partially observable, and is unlikely to compromise the vehicle user in any sense.	Some level of assurance that the information is correct is necessary as the information may be used to grant access to limited-access pathways.	Limited access pathways dedicated to particular types of MMVs should be generally available so as to ensure use of the asset.
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	personal location	Not Applicable	High	Moderate
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	personal location	This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators.	An incorrect location message could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity.	There are other visual indicators about the geofenced areas. PID users in dynamic environments (incident and work zones) should know when they are leaving a geofenced area. As long as they remain in the geofenced area, this information is not as necessary. Not all pedestrians will carry a personal information device, and the system should be able to operate without this information.
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	VRU cluster information	Low	High	Moderate
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	VRU cluster information	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	VRU hazard event	Low	High	Moderate
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	VRU hazard event	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	VRU path prediction	Low	High	Moderate
Other Micromobility Vehicle OBEs	Micromobility Vehicle OBE	VRU path prediction	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Other PIDs	Personal Information Device	personal location	Not Applicable	High	Moderate
Other PIDs	Personal Information Device	personal location	This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators.	An incorrect location message could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity.	There are other visual indicators about the geofenced areas. PID users in dynamic environments (incident and work zones) should know when they are leaving a geofenced area. As long as they remain in the geofenced area, this information is not as necessary. Not all pedestrians will carry a personal information device, and the system should be able to operate without this information.
Other PIDs	Personal Information Device	VRU cluster information	Low	High	Moderate
Other PIDs	Personal Information Device	VRU cluster information	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Other PIDs	Personal Information Device	VRU hazard event	Low	High	Moderate
Other PIDs	Personal Information Device	VRU hazard event	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Other PIDs	Personal Information Device	VRU path prediction	Low	High	Moderate
Other PIDs	Personal Information Device	VRU path prediction	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Pedestrian	Personal Information Device	personal input	Not Applicable	Moderate	Low
Pedestrian	Personal Information Device	personal input	Personal input similar to pressing the button on a pedestrian call at a stop light, nothing that could not be otherwise observed.	This data does have to be correct, so the signal receives the pedestrian call. Given that the pedestrian should still not enter the intersection without feedback, this could be considered LOW.	There are generally other ways to accomplish this flow. Depending on the pedestrian this might be MODERATE, for example for pedestrians unable to easily access the call button.
Personal Information Device	Other PIDs	personal location	Not Applicable	High	Moderate
Personal Information Device	Other PIDs	personal location	This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators.	An incorrect location message could lead to a false warning or lack of warning. A lack of warning can have obvious catastrophic consequences, while a false warning could lead to users ignoring warnings due to perceived inaccuracy. Given that this triple may apply to highly dynamic environments (such as work zones), its accuracy is paramount, and thus if sent, must have HIGH integrity.	There are other visual indicators about the geofenced areas. PID users in dynamic environments (incident and work zones) should know when they are leaving a geofenced area. As long as they remain in the geofenced area, this information is not as necessary. Not all pedestrians will carry a personal information device, and the system should be able to operate without this information.
Personal Information Device	Other PIDs	VRU cluster information	Low	High	Moderate
Personal Information Device	Other PIDs	VRU cluster information	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Personal Information Device	Other PIDs	VRU hazard event	Low	High	Moderate
Personal Information Device	Other PIDs	VRU hazard event	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Personal Information Device	Other PIDs	VRU path prediction	Low	High	Moderate
Personal Information Device	Other PIDs	VRU path prediction	Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.	MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.
Personal Information Device	Pedestrian	personal updates	Not Applicable	Moderate	Moderate
Personal Information Device	Pedestrian	personal updates	This data is informing the pedestrian about the safety of the intersections. It should not contain anything sensitive, and does not matter if another person can observe it.	This is the information that is presented to the individual. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights.	If this information is not made available to the pedestrian, then the system has not operated correctly.
Personal Information Device	Transportation Information Center	traveler sourced updates	Moderate	Moderate	Low
Personal Information Device	Transportation Information Center	traveler sourced updates	This is likely to include the traveler location and may include traveler identity as well. This PII could be used by an attacker to the detriment of the traveler.	If this information is not correct the end user of the TIC will likely find othe avenues for obtaining this information.	If this interface is not available the traveler will likely find other means to acquire the necessary information.

Standards

Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

System Requirements

System Requirement		Need
001	The system shall collect, process, and store pathway information.	03	Travelers need to be able to provide wayfinding information updates based on information collected by travelers or micromobility vehicles.
002	The system shall share location and motion information with adjacent micromobility vehicles (MMVs) or other vulnerable road users (VRUs) equipped with their own personal information devices (PIDs) on the same path (a 'string') in order to coordinate maneuvers.	02	Travelers, including pedestrians and users of micromobility vehicles (MMVs), need to be able to safely join or separate from a platoon or group of similar vehicle device types, including coordination of direction, speed and policies with other vehicles/conveyances in the platoon.
003	The system shall receive a notification from a micromobility vehicle that the device is now on a moving micromobility vehicle and should transition to a mode where it does not provide personal safety notifications.	01	The Traveler needs to be warned about the proximity of other travelers, micromobility vehicles, and other vehicles in order to avoid a crash.
004	The system shall share its location with other personal traveler devices to support safe movement among vulnerable road users.	01	The Traveler needs to be warned about the proximity of other travelers, micromobility vehicles, and other vehicles in order to avoid a crash.
005	The system shall share information about hazards, debris, or obstacles with other traveler devices or traveler information.	01	The Traveler needs to be warned about the proximity of other travelers, micromobility vehicles, and other vehicles in order to avoid a crash.
006	The system shall share location and motion information with adjacent micromobility vehicles or vulnerable road users on the same path (a 'string') in order to coordinate maneuvers.	02	Travelers, including pedestrians and users of micromobility vehicles (MMVs), need to be able to safely join or separate from a platoon or group of similar vehicle device types, including coordination of direction, speed and policies with other vehicles/conveyances in the platoon.
007	The system shall share information about hazards, debris, or obstacles with other MMVs or traveler information.	01	The Traveler needs to be warned about the proximity of other travelers, micromobility vehicles, and other vehicles in order to avoid a crash.
008	The system shall send location and motion information of the vehicle to nearby micromobility vehicles to warn the micromobility vehicle user about the potential for an impending collision.	01	The Traveler needs to be warned about the proximity of other travelers, micromobility vehicles, and other vehicles in order to avoid a crash.
009	The system shall receive location and motion information from nearby micromobility vehicles so that the micromobility vehicle can identify if a collision is imminent.	01	The Traveler needs to be warned about the proximity of other travelers, micromobility vehicles, and other vehicles in order to avoid a crash.
010	The system shall notify a personal device that the traveler is in a micromobility vehicle so that the traveler device can transition modes to one that receives personal safety information relevant to the micromobility vehicle.	02	Travelers, including pedestrians and users of micromobility vehicles (MMVs), need to be able to safely join or separate from a platoon or group of similar vehicle device types, including coordination of direction, speed and policies with other vehicles/conveyances in the platoon.

Implementations

VS19.1 Vulnerable Road User Clustering Implementation

Display: Implementation legend or Service Package legend

VS19.1 Vulnerable Road User Clustering Implementation Implementation

This 'implementation' is a holistic view of the VS19 service package, including all Physical Objects, Functional Objects, and Triples associated with the service package. It distinguishes between items that are fundamental to the service and items that are optional. Your specific implementation is likely to include the fundamental items and selected optional items, based on your specific project requirements.

Vulnerable Road User Clustering Implementation Implementation Flows

Information Flow	Description	Inclusion Status
device configuration coordination	A handshake between two different devices in the same vehicle or conveyance so the devices don't interfere with each or send conflicting information. This coordination may result in a personal information device (PID) carried by a traveler not transmitting its current location while on board vehicle, a transit vehicle, or a micromobility vehicle transmitting its vehicle profile and current location. For example, in the carry-in scenario, the personal device might go into a 'quiet' mode when carried into the vehicle that is already equipped with an integrated system that can broadcast safety messages.	Fundamental
MMV profile	Information about the micromobility vehicle such as type of micromobility vehicle, size and weight, vehicle performance (acceleration, top speed, turning radius) or other data that can be used to classify vehicle eligibility for access to specific lanes or road segments, or its projected path trajectory.	Fundamental
personal input	User input to a personal device. This flow may request traveler information, request right of way, summon assistance, make a reservation, or request any other traveler service. This flow also establishes the settings that tailor each application to suit the user's needs.	Fundamental
personal location	The current location (latitude, longitude, and elevation) reported by the personal information or safety device	Fundamental
personal updates	Personal information, alerts, and warnings provided to pedestrians, micromobility vehicle (MMV) users, work crew members, and other individuals in a mixed use area. This includes visual, audio, and haptic outputs that may be customized to support individual needs.	Fundamental
traveler sourced updates	Traveler posts on traffic and road conditions, parking availability, transit services, traveler services, shelter information, hazards, debris, obstacles, and other real-time crowd-sourced data that may be shared with other travelers.	Optional
VRU cluster information	Information indicating the formation and management of strings of VRUs and micromobility vehicles, which includes human powered vehicles such as bicycles, that may follow each other towards a common destination. This flow also supports identification of the lead MMV in the string so other MMVs can opt-in to join the string. The indication of participating in a string provides better predicted path trajectory prediction for all participating MMVs, enhancing safety. This flow also supports dissolution of MMV strings as MMVs depart from the string.	Fundamental
VRU hazard event	Notification of a potential hazard or event that is detected or reported by the traveler or vulnerable road user (VRU) using a PID or riding a micromobility vehicle (MMV). Potential hazards may be determined by sudden movements by travelers, such as movements around a location which may indicate foreign objects (people, animals, debris, other obstacles) in the travel lanes. Hazards may also be manually entered by the traveler into a personal information device (e.g., crowdsourcing) to be shared with other travelers.	Optional
VRU path prediction	The predicted future path of travel by the VRUs equipment. This flow includes an indication of the future positions of the transmitting traveler that can be used by receiving connected devices to support coordinated travel maneuvers and enhance collision avoidance.	Fundamental

Vulnerable Road User Clustering Implementation Implementation Functional Objects

Functional Object
MMV Cooperative Information
MMV Safety Communication
Personal Cooperative Information
Personal Device Coordination
Personal Pedestrian Safety
TIC Data Collection
Vehicle Device Coordination

Back to Implementation List