Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The whole architecture, shown below, consists of two parts the front end and the backend.

  • For the front end, the minimal requirements are two clients, one for the teacher and the other one for the student. The client device could be a cellphone, tablets, wearable devices,personal computers, etc.  The client collects information from the real world and transfers the data to the backend for calculation. Beyond data transfer and calculation, render is another function run on the front end client-side.
  • For the backend,

...

  • we deploy the backend in two virtual machines in the Cloud.  
    1. To make the VR backend works well, we deploy IEC in the IaaS Layer, Tars framework in PaaS Layer, Virtual Classroom Backend in SaaS Layer.
    2. To make CI/CD available, we deploy Jenkins Master in one Virtual Machine.  The Jenkins master issues command to tiger the script run on the dedicated VM.   

Image Added

Image Removed

The client device could be a cellphone, tablets, wearable devices,personal computers, etc.

The following picture depicts the architecture of the Connect Vehicle Blueprint, which consists of the following key components:

  • Commodity Hardware, Arm/X86 Physical Server.
  • IaaS Software, like Openstack, IaaS and so on
  • Tars Microservice Platform
  • Connected Vehicle Applications  

The combination of Commodity Hardware and IaaS Software provides flexible deployments, like Bare Metal, Virtual Machine as well as Container. 

Tars is a microservice framework that can manage/monitor/deploy the connected vehicle applications in the edge and data center. Tars can be flexibly deployed in Bare Metal, Virtual Machine as well as Container.

Connected Vehicle Applications are some different applications that fulfill Accurate Location, Smarter Navigation, Safe Drive Improvement and Reduce traffic violations.

The following is the general architecture of Tars, which is a major component in R2.

Image Removed

Refer to the enclosed PDF document for the detail Tars introduction. 

 PDF



Main Progresses for Release 2

Release 2 is the first release for Connected Vehicle BlueprintIEC Type 4. So everything is new.


Build Of Materials (BOM) / Hardware requirements

Connected Vehicle Blueprint can be flexibly deployed in Bare Metal, Virtual Machine as well as the container.

For R2, we deploy it in Amazon Web Service Tencent Cloud for Release.  The detailed hardware is itemized below:

...