Design Overview. We propose an acoustic device authentication and key agree- ment system, GeneWave, to meet the design goals. Overall, GeneWave system consists of the following two major steps: bidirectional initial authentication and key agreement.
Design Overview. The architectural design of the Context Management component is depicted in Figure 1. The component consists of two NBIs, namely a gRPC interface exposed to the rest of the TeraFlow OS components, and a REST interface exposed to external systems, such as Operations Support System (OSS) or Business Support System (BSS), that might have to retrieve the internal status of the resources managed by the TeraFlow OS. Both interfaces rely on a Context Servicer that dispatches the incoming requests and interacts with the Database API used to interact with a No-SQL database. The Database API enables the Context Management component to use different database backends depending on the needs of the users. Currently, a pure in-memory database backend and a Redis database backend are available. The Context Management component also incorporates publish-subscribe mechanisms over gRPC to broadcast context change events to the rest of the TeraFlow OS components. Figure 1: Architecture of the Context Management component.
Design Overview. The architecture of the Monitoring component is composed of two main blocks, the Monitoring Core and the Metrics Database, as depicted in Figure 2. • Monitoring Core
Design Overview. The TE component is composed of three sub-components, the XXX service, the PCE service, and the Smart Traffic Engineering service as shown in Figure 7.
Design Overview. The architectural design of the Device component is depicted in Figure 11. The component consists of a gRPC-based NBI exposed to the rest of TeraFlow OS components, and a set of SBIs that interact with different network equipment using appropriate protocols and data models. In between, the Device Servicer block dispatches the incoming requests and interacts with the SBI Driver API to choose the appropriate driver for each network device. Given that the Device component needs to know about the state and details of the network devices, it makes use of the Context Management component to store and retrieve up-to-date details about the devices using the Context Management gRPC interface. The SBI Driver API enables the Device component to be extended to use different protocols and data models to communicate with various types of programmable devices. The available driver plugins are listed below, with a link to the corresponding subsection: • An emulated driver plugin for testing purposes (see Section 4.1.2.1); • An OLS ONF Transport API [TR547] driver plugin (see Section 4.1.2.2); • An ONF TR-532 microwave driver plugin (see Section 4.1.2.3); • A NETCONF [15]/OpenConfig [16] driver plugin for packet routers (see Section 4.1.2.4); and • A P4 [4] driver plugin for next-generation white box switches (see Section 4.1.2.5).
Design Overview. The architectural design of the Service component is depicted in Figure 20. The component consists of a gRPC-based NBI exposed to the rest of TeraFlow OS components, a Service Servicer block that dispatches the incoming requests and interacts with the Service Handler API to choose the appropriate handler for each service type requested. Given that the Service component needs to know about the state and details of the existing connectivity services and the devices supporting them, it makes use of the Context Management component to store and retrieve up-to-date details about the devices and the services using the Context Management gRPC interface. The Service Handler interface enables network operators to extend the Service component to support different service types and use different protocols and data models to configure the devices. Currently, a L3-VPN service using OpenConfig (L3NM-OC) is under development. Figure 20: Architecture of the Service component.
Design Overview. The goal of the Automation component, also abbreviated as ZTP, is to provide zero-touch device onboarding, reconfiguration, and deletion functions to the TeraFlow OS as well as to similar SDN controllers or overlay network management tools. To meet this objective, the Automation component is designed according to Figure 22. Figure 22: Automation (ZTP) component overview.
Design Overview. The goal of the Policy Management component, also abbreviated as Policy component, is to translate a network operator’s high-level network policy statements into a correct set of low-level instructions that realize this policy across the various network elements. To meet this objective, the Policy component is designed according to Figure 29.
Design Overview. Transport network slicing is facilitated using an abstracted management architecture shown in Figure 33. <.. image(Diagram, text Description automatically generated) removed ..>
Design Overview. Motorola will enhance the security at the Xxxxxxx X. Xxxxx Center (“Xxxxx Center”) by upgrading the existing camera surveillance system and installing a Genetec Video Management System. This enhancement will include the addition of 61 cameras installed in the Lobby, Plaza, Concourse and Lower Level to provide coverage of areas designated by the Elert and Associates Security and Risk Assessment and shown on the attached drawings (“drawings”). Video from these cameras will be viewable in the Xxxxx Center Command Center and various cameras will be federated to three agencies: OEMC, Cook County Sheriff’s Office and Cook County Office of Homeland Security. In conjunction with the enhancement of the security system, Motorola will design, furnish and install a Command Center utilizing Room CL-132 for Xxxxx Center Security. The Command Center will allow two security personnel 24 hour viewing of the newly installed cameras. INTERIOR CAMERA INSTALLATION Motorola will install the following cameras in the lower level, concourse level and lobby: Axis Fixed Dome Indoor Camera with Mounting 40 Axis Indoor Mini PTZ Camera with Mounting 1 Axis Exterior Vandal Dome with Mounting 4 Camera Installation Locations per attached drawings: o Interior Fixed: ▪ Lower Level: 3, 4, 7, 8, 19, 12, 21 ▪ Concourse Level: 01, 03, 04, 05, 08, 11, 12, 16, 20, 22, 26, 27, 28, 29, 30, 31, 32, 33, 40 ▪ 1st Floor: 7, 10, 14, 15, 16, 17, 18, 19, 20, 23, 24, 26, 27, 29 o Mini PTZ - CL36 o Exterior Vandal Dome - CL13, 14, 18 and 19 All penetrations will be approved by MBRE prior to coring. IP cameras will connect to a XXX Camera CRE which will provide power and video network connectivity. Each network switch will have two (2) multi-mode transceivers modules that will provide redundant connectivity to the MDF in room CL-127. Each CRE enclosure will have backup UPS power and a 14 port input power strip for distribution to internal switches, XXX injectors, external power supplies and transcoder equipment. The Vandal Dome cameras will be installed in the Sheriff’s lockup area. Access to video from these cameras will be viewable only to the Sheriff’s office.
