F3.1.2.13.5 Manage Inter-urban Traffic Commands & Messages

Header Image
Project:
F3.1.2.13.5 Manage Inter-urban Traffic Commands & Messages : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:26
Modified: 08.09.2021 11:24:30
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to provide traffic control facilities that enable the traffic to be managed so that the most efficient use is made of the inter-urban road network.<br/>(2) The ability to manage the implementation of traffic management strategies for the inter-urban road network in a planned sequence according to the time of day and day of week.<br/>(3) The ability for the traffic management strategies to include control of access to the inter-urban network (ramp metering), plus commands to manage the use of lanes in the carriageway (including the hard shoulder) and the maximum speeds for vehicles in each lane.<br/>(4) The ability for these strategies to be overridden by the Road Network Operator through the functionality providing their interface, as well as by inputs from the incident, demand and access management functionality.<br/>(5) The ability to use current, historic and predicted traffic data from the inter-urban network and to change in real-time the actual traffic management commands being sent for output to take account of variations in this data.<br/>(6) The ability to provide details of the current and previous implemented traffic management strategies on some or all parts of the inter-urban road network to the Road Network Operator through the functionality that provides their interface.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mt_inter-urban_strategy_details_for_ramp_metering
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tmms.mmc-inter-urban_crossing_inhibit
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F3.1.2.13 Manage Inter-urban Traffic Strategies
FRAME_High_Level_Function «Componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_bridge_inputs
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_traffic_data_for_ramp_metering
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_selected_inter-urban_strategy_details
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.ptja_inter-urban_recommended_routes
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_operator_inter-urban_management_response
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_to_urban_traffic_commands
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_speed_and_headway_settings
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_lane_management_requests
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_zone_access_vehicle_list
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_tunnel_inputs
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_strategies_in_use
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tors.iutms-inter-urban_traffic_management_strategy
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_User_Need» 7.1.0.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.4.5.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.0.6
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.5.8
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.5.1.5
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_urban_to_inter-urban_traffic_commands
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.0.13
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_traffic_flow_management_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.5.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_network_long-term_prediction_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_environmental_inputs
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_operator_inter-urban_management_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.5.1.10
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.0.5
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_zoning_strategy
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.5.5
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_planned_inter-urban_traffic_management_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_bridge_inter-urban_inputs
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.5.7
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fors.iutms-inter-urban_traffic_management_strategy
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_tunnel_inter-urban_inputs
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_static_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_demand_management_strategy
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.4.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.0.11
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.5.9
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_strategy_command_response_failure
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.4.9
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.0.12
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 2.1.2.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.0.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.4.8
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) continuously monitor for receipt of any of the input data flows;<br/>(b) when the planned inter-urban traffic management request data flow is received in (a), action the strategy that it contains, by sending all or part of its contents in the inter-urban tunnel inputs, inter-urban bridge inputs, inter-urban crossing inhibit, inter-urban strategy details, inter-urban strategies in use, inter-urban strategy details for ramp metering, inter-urban zone access vehicle list, inter-urban lane management requests, inter-urban speed and headway settings, or inter-urban traffic management strategy, inter-urban to urban traffic commands data flows;<br/>(c) when the data flow containing inter-urban static data is received in (a), store its contents for internal use;<br/>(d) when the inter-urban zoning strategy data flow is received in (a), output its contents to the Check Access to Inter-urban Zones function in the inter-urban zone access vehicle list data flow;<br/>(e) when any of the bridge inter-urban inputs, tunnel inter-urban inputs, inter-urban environmental inputs, or inter-urban demand management strategy data flows are received in (a), use their contents to modify the current traffic management strategy, and repeat (b);<br/>(f) when the data flow containing predicted inter-urban network data is received in (a), store its contents for internal use in calculating recommended routes and send these in the inter-urban recommended routes data flow to the Plan Trip Details function;<br/>(g) when either of the urban to inter-urban commands, or inter-urban traffic management strategy data flows are received in (a), use their contents to modify the current traffic management strategy, and repeat (b);<br/>(h) when the operator inter-urban management request data flow is received in (a), use their contents to modify the current traffic management strategy, repeat (b) and output the response to the Provide Inter-urban Road Operator Mgt Interface function in the operator inter-urban management response data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0