SU15: Vulnerable Road User Device Transition Support

This service package supports the transition of a device used by a vulnerable road user (VRU) when they change from one mode in which they are vulnerable - walking, cycling, using a wheelchair, etc., to one in which they are less vulnerable, e.g., riding or driving a car, truck, emergency vehicle, transit vehicle, etc. This also supports the transition back to a more vulnerable mode. This service package represents a scenario where an aftermarket carry-in device, the PID, is carried into a vehicle that is already equipped with one of the Vehicle OBE implementations. In this scenario, there are two different devices with possibly two different radios and two different user interfaces that must be coordinated to avoid interference or conflicts.

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

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

Enterprise

Development Stage Roles and Relationships

(hide)

Source	Destination	Role/Relationship
Personal Developer	Personal	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 Developer	Vehicle 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.
Vehicle Developer	Personal 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.
Vehicle Developer	Vehicle	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
Personal Installer	Personal	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 Owner	Personal Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Personal Owner	Personal 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.
Vehicle Installer	Vehicle	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.
Vehicle Owner	Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Vehicle Owner	Vehicle 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
Driver	Vehicle	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 Maintainer	Personal	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 Manager	Personal	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 Owner	Driver	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 Owner	Personal 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 Owner	Personal 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 Owner	Vehicle 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 Owner	Vehicle 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 Owner	Vehicle 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 Supplier	Personal Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Vehicle Maintainer	Vehicle	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.
Vehicle Manager	Driver	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.
Vehicle Manager	Vehicle	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.
Vehicle Owner	Personal 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.
Vehicle Owner	Personal 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.
Vehicle Owner	Personal User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Vehicle Owner	Vehicle 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.
Vehicle Owner	Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Vehicle Supplier	Vehicle 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
Personal Information Device	Personal Device Coordination	10.6.3.3	Provide Personal Device Coordination
Vehicle	Vehicle Device Coordination	10.6.3.2	Provide Vehicle Device Coordination

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

Hide Legend

Includes Physical Objects:

Physical Object	Class	Description
Driver	Vehicle	The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Personal	Personal	The 'Personal' physical object is used to model core capabilities that are common to more than one physical object in the 'Personal' class. It provides the general executive, management, and utility functions that may be shared by different types of personal devices.
Traveler	Personal	The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
Vehicle	Vehicle	This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. 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, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Includes Functional Objects:

Functional Object	Description	Physical Object
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
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.
driver input	Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver updates	Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
traveler input	User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service.
traveler interface updates	Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler.

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
C. Increase the security of the transportation system for motorized and nonmotorized users;	Improve security
D. Increase the accessibility and mobility of people and for freight;	Reduce congestion

Associated Objective Categories

Objective Category
Safety: Vehicle Crashes and Fatalities
Transit Operations and Management: Safety

Associated Objectives and Performance Measures

Objective	Performance Measure
Decrease the number of personal safety incidents by X percent within Y years.	Number of reported personal safety incidents.
Increase the number of closed circuit television (CCTV) cameras installed by X percent in Y years on platforms, park-n-ride lots, vehicles, and other transit facilities.	Number of CCTV cameras on platforms, park-n-ride lots, vehicles, and other transit facilities.
Reduce crashes at intersections	Number of crashes and fatalities at signalized intersections
Reduce crashes at intersections	Number of crashes and fatalities at unsignalized intersections
Reduce crashes at intersections	Number of crashes and fatalities related to red-light running
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 crashes due to red-light running	Number of crashes and fatalities related to red-light running
Reduce speed differential	Number of crashes and fatalities related to excessive speeding
Reduce speed differential	Number of speed violations
Reduce the number of pedestrian fatalities by X percent by year Y.	Number of pedestrian fatalities
Reduce the rate fatalities in the region by X percent by year Y.	Rate of fatalities (rate per vehicle miles travelled (VMT))
Reduce the total number of crashes in the region by X percent by year Y.	Total crashes per X VMT.
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	Travelers need to be protected from collisions while in the transportation environment.	Personal Device Coordination	01	The personal device shall provide safety advisories or warnings to the traveler when the traveler is not inside of a vehicle.
02	Travelers need to be kept informed of the status of their connected devices in order to know when they transition from one mode to another and that they are still transmitting and receiving pertinent safety information as applicable.	Personal Device Coordination	02	The personal device shall inform travelers of the mode of their device and whether they are currently receiving pertinent safety advisories or warnings.
			03	The personal device shall receive a notification from a vehicle that the device is now on a moving vehicle and should transition to a mode where it does not provide personal safety notifications.
		Vehicle Device Coordination	01	The vehicle shall notify a personal device that the traveler is in a moving vehicle so that the traveler device can transition modes to one that does not receive personal safety information.

Related Sources

Document Name	Version	Publication Date
ISO/TR 22085-1:2019: Intelligent transport systems (ITS) - Nomadic device service platform for micro-mobility	Final	5/1/2019

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
Personal	Low	High	Moderate	Class 3
Vehicle	Low	High	Moderate	Class 3

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
			Basis	Basis	Basis
Driver	Vehicle	driver input	Moderate	High	High
			Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy.	Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner	Commands must always be able to be given or the driver has no control.
Personal	Traveler	traveler interface updates	Not Applicable	Moderate	Moderate
			Personalized data that includes directions and guidance for an individual, but eventually evident anyway.	Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral.	Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.
Personal	Vehicle	device configuration coordination	Low	High	Moderate
			Unlikely that any personal or not observable information is included here.	Misconfiguration could cause a malfunction or lead to undesireable vehicle behavior. Will only affect the one vehicle, but could be dangerous to the MMV operator.	Service cannot operate without this flow, and there is no alternative integrated solution. Listed as 'MODERATE' and not 'HIGH' only because loss of these services would be inconvenient and disadvantageous, particulary to vulnerable road users, but not catastrophic.
Traveler	Personal	traveler input	Not Applicable	Moderate	Low
			This data is informing the vehicle of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it.	While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans.	Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Vehicle	Driver	driver updates	Not Applicable	Moderate	Moderate
			This data is informing the driver about the safety of a nearby area. 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 driver. 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 driver, then the system has not operated correctly.
Vehicle	Personal	device configuration coordination	Low	High	Moderate
			Unlikely that any personal or not observable information is included here.	Misconfiguration could cause a malfunction or lead to undesireable vehicle behavior. Will only affect the one vehicle, but could be dangerous to the MMV operator.	Service cannot operate without this flow, and there is no alternative integrated solution. Listed as 'MODERATE' and not 'HIGH' only because loss of these services would be inconvenient and disadvantageous, particulary to vulnerable road users, but not catastrophic.

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.

System Requirements

System Requirement		Need
001	The system shall provide safety advisories or warnings to the traveler when the traveler is not inside of a vehicle.	01	Travelers need to be protected from collisions while in the transportation environment.
002	The system shall inform travelers of the mode of their device and whether they are currently receiving pertinent safety advisories or warnings.	02	Travelers need to be kept informed of the status of their connected devices in order to know when they transition from one mode to another and that they are still transmitting and receiving pertinent safety information as applicable.
003	The system shall receive a notification from a vehicle that the device is now on a moving vehicle and should transition to a mode where it does not provide personal safety notifications.	02	Travelers need to be kept informed of the status of their connected devices in order to know when they transition from one mode to another and that they are still transmitting and receiving pertinent safety information as applicable.
004	The system shall notify a personal device that the traveler is in a moving vehicle so that the traveler device can transition modes to one that does not receive personal safety information.	02	Travelers need to be kept informed of the status of their connected devices in order to know when they transition from one mode to another and that they are still transmitting and receiving pertinent safety information as applicable.