The mVision architecture (refer to diagram above) can be broken down into 3 portions. On the left would be the Video Source, Servers in the center and Mobile Access on the right.

The mVision is capable of receiving feeds from sources such as IP Camera, Web Cameras, CCTV Cameras and even alternative video file formats. Via a slave server application, videos can be compressed into H.264 format for uploading to the server and subsequently streaming to mobile or desktop users. Alternatively, the server is capable of receiving feeds directly from IP Cameras as well as remote feeds via GPRS/CDMA from the mBox.

The mVision server caters for full user provisioning and adminstrative functions. Control access to video feeds, provide WAP access and also desktop access to video feeds all via the mVision server.

The Mobile Access includes access from the desktop, as desktop application is not compulsory, users can access the same video feeds from anywhere as long as they an internet capable PC. But mVisions primary capability is to stream video feeds onto mobile phones, and depending on the mobile device available, H.264 or Motion Jpeg feeds can be viewed with reasonable framrates (starting from 1 frame/sec).

For mobile access, there are 2 options available for access; Wap or Mobile Client. Wap access would be simpler as users may access the video feeds via an internet WAP site. However, a Mobile Client (J2ME) will offer more security (encryption options) and also tighter user control.