Personal Information Device --> Multi-Access Edge Computing:
personal signal service request
This flow may also be implemented by
Personal Information Device --> Connected Vehicle Roadside Equipment: personal signal service request Definitions
personal signal service request (Information Flow): A request for right of way from a personal device that indicates the type of traveler (pedestrian, special needs pedestrian, bicyclist, etc.), anticipated time of arrival, travel path, and crossing duration.
Personal Information Device (Source Physical Object): 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.
Multi-Access Edge Computing (Destination Physical Object): 'Multi-Access Edge Computing' ((MEC) previously known as mobile edge computing) represents computing devices that operate and are managed like a cloud server, but are deployed at the edge of a network (typically a cellular network, but it could be any network). While not in strict proximity to the transportation network, these systems do benefit from vastly decreased distances to the roadway compared to central systems, and so can provide lower latency than strictly backoffice systems
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
| None |
Communication Solutions
-
US: SAE Other J2735 - Secure Wireless Internet (ITS) (12)
-
(None-Data) - Secure Wireless Internet (ITS) (43)
-
(None-Data) - Secure Wireless Internet (EU) (43)
Selected Solution
(None-Data) - Secure Wireless Internet (ITS)Solution Description
|
ITS Application Entity
  
Development needed  |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
Development needed |
Security
|
|
|
TransNet
|
|||
|
Access
  
|
|||
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| Interoperability | Description |
|---|---|
| National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Low | Moderate | Low | |
| Basis | Info is not confidential and there is little to be gained by observing it. | Requests should be accurate and not tampered with, otherwise incorrect or malicious requests could be granted which could lead to delays. | Requests should be timely and available immediately but availability cannot be guaranteed over a wireless medium; also worst case scenario is the vehicle or pedestrian has to wait for the appropriate signal | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |