1	"September 20-22" September 20-22, 2011 San Jose, CA Day 3 Systems Engineering Team connected vehicle Core System Architecture/Requirements Workshop #2
2	"Welcome to Day 3" Welcome to Day 3
3	Agenda – Thursday 9/22
4	Core System provides services that… Enable data transfers between System Users Mobile Field Center Are in a secure, trusted environment Enabling trust between parties that have no direct relationship Enabling secure data exchange between parties that have no direct relationship Enabling the exchange of data between parties that have data and parties that want data
5	Core System in the context of the connected vehicle environment
6	Core System’s 8 Subsystems
7	"Views that will describe the..." Views that will describe the layered communications protocols
8	Communications Layered communications protocols between nodes Links are traceable to interface requirements
9	Communications Views Defined Mobile DSRC Device and Core Mobile Wide-Area Wireless User and Core Fixed Point Center/Field User and Core, Core2Core Core Routing
10	Communications View 4.4.1 – Mobile DSRC Device and Core Description: 1^st of 2 views showing how Mobile Users can communicate with the Core Shows the intermediary steps to go from Mobile to Core Based on 5.9 GHz DSRC using IEEE 1609.x, 802.11p standards
11	Communications View 4.4.1 – Mobile DSRC Device and Core
12	Communications View 4.4.1 – Mobile DSRC Device and Core
13	Communications View 4.4.1 – Mobile DSRC Device and Core
14	Communications View 4.4.1 – Mobile DSRC Device and Core
15	Communications View 4.4.1 – Mobile DSRC Device and Core
16	Communications View 4.4.2 – Mobile Wide-Area Wireless User and Core Description: 2^nd of 2 views showing how Mobile Users can communicate with the Core Shows the intermediary steps to go from Mobile to Core Based on WiFi, cellular, other wireless communications
17	Communications View 4.4.2 – Mobile Wide-Area Wireless User and Core
18	Communications View 4.4.2 – Mobile Wide-Area Wireless User and Core
19	Communications View 4.4.2 – Mobile Wide-Area Wireless User and Core
20	Communications View 4.4.2 – Mobile Wide-Area Wireless User and Core
21	Communications View 4.4.3 – Fixed Point Center/Field User and Core, Core2Core Description: Shows how non-mobile systems (Field, Center, External Support Systems, and other Cores) communicate with the Core Wired connections through the Internet or private networks May use wireless (see 4.4.2) Uses IP protocols
22	Communications View 4.4.3 – Fixed Point Center/Field User and Core, Core2Core
23	Communications View 4.4.3 – Fixed Point Center/Field User and Core, Core2Core
24	Communications View 4.4.4 – Core Routing
25	Communications View 4.4.4 – Core Routing Description: Shows the communications involved when the Core is used as a router when a private network is used to connect mobile, field, or center systems Fixed devices connected to the Core by a private network can use the Core Access Node to provide connectivity between them Could also provide connectivity for mobile users to a Center user
26	Communications View 4.4.4 – Core Routing
27	Communications View 4.4.4 – Core Routing
28	Communications View 4.4.4 – Core Routing
29	Communications View 4.4.4 – Core Routing
30	Communications View 4.4.4 – Core Routing
31	"Views that will describe the..." Views that will describe the data object structures and relationships
32	Information Defines the Data objects: structure, relationships, metadata, and constraints Related to interface requirements, referenced by the functional requirements
33	Information Views Defined Top Level External Objects Top Level Internal Objects
34	Information View 4.5.1 – Top Level External Objects Description: Objects that are exchanged, sent, and received over the Core System’s external interfaces Includes objects between Cores Organized by the originating or terminating subsystem External interfaces are candidates for standardization
35	Information View 4.5.1 – Top Level External Objects
36	Information View 4.5.1 – Top Level External Objects
37	Information View 4.5.1 – Top Level External Objects
38	Information View 4.5.2 – Top Level Internal Objects Description: Objects that are exchanged, accepted, and sent between subsystems over the Core System’s internal interfaces Organized by the originating or terminating subsystem
39	Information View 4.5.2 – Top Level Internal Objects
40	Information View 4.5.2 – Top Level Internal Objects
41	Information View 4.5.2 – Top Level Internal Objects
42	"How will the Core be..." How will the Core be ‘rolled-out’
43	Core System Deployment Recall from Day 1’s background of the Core System Core System Needed Support diverse implementations Extensible, scalable over time Support Diverse deployments Standalone Collocated Distributed
44	Core System Deployment Core System Architecture supports those goals: Enterprise Objects like Core Certification Authority Interfaces like Core2Core Ability to vary how software is assigned to nodes
45	"Deployment Considerations as multiple Cores..." Deployment Considerations as multiple Cores are developed and fielded
46	Single Standalone Core Core #1 provides all services for the area. Some areas provide DSRC communications to Core, resulting in different service delivery profiles.
47	Multi Core – One Dominant Core #2 provides all services for the area it covers, all by nG cellular. Core #1 provides all services for the area it covers, some by nG, some by DSRC. Overlap requires agreement, and Core #2 provides services in the overlap areas here.
48	Multi Core – Shared Dominance Core #2 provides all services for the area it covers, all by nG, except for the shared area. Core #1 provides all services for the area it covers, some by nG, some by DSRC. Overlap requires agreement; Core #1 and Core #2 both provide services. Each service provided by only one Core, except for DSRC users that can get all services from Core #1.
49	Multi Core – Peers Core #2 provides all services for the area it covers, all by nG, except for the shared area. Core #1 provides all services for the area it covers, some by nG, some by DSRC. Overlap requires agreement; Core #1 and Core #2 both provide services. Overlap area defaults to Core #2, except for DSRC users that go to Core #1. Users can override and access Core #1 with 3G if they wish
50	Core System Deployment Activities 1^st Steps (take care of the higher risk items) Setup the Core Certification Authority to establish: Governance policies Certification standards and procedures Security credentials (root CA) Establish the External Support Systems (the CAs and RAs)
51	Core System Deployment Activities Incorporate Lessons from Test Bed, Safety/Certification Pilots Work with Standards organizations to incorporate Core System interfaces into industry standards Begin to work with Deployers to establish operating agreements What else?
52	Discussion – Likely Deployers Who is likely to deploy a Core System? States Locals 3^rd Party Data Warehouse Providers System Integrator Auto Industry May affect how relationships are defined by the Core Certification Authority
53	"Barriers to Deployment" Barriers to Deployment
54	Risk to Success of the Core System What may happen to prevent the Core System from succeeding – and to some extent, affect the overall connected vehicle environment Types of Risks Technically – Core System is straightforward, using current technologies Institutional Issues always take longer Programmatic – cost/schedule Levels: individual Core, collectively
55	Preliminary Risks to Success of the Core System Timely Deployment Relationships between Core Systems and external Enterprises Role and Makeup of the Core Certification Authority External Support System (ESS) for Security Operations and Maintenance of the Security External Support System (ESS) More for the connected vehicle environment Security Management Data Provisioning/Ownership
56	"For Core System and related..." For Core System and related activities
57	Core System Timeline
58	Next Steps System Engineering Team will finalize ConOps Requirements Architecture Risk Standards Recommendations DOT leading other activities where Core System Contact Walt Fehr – 202-366-0278, walt.fehr@dot.gov
59	"Thank you all for your..." Thank you all for your Time