The roll-out and extensive coverage of 4G networks globally have been one of the key tailwinds pushing the connected vehicle ecosystem forward, including the adoption of video telematics. It can also be considered a critical prerequisite, as the data payloads for video telematics when compared to traditional telematics solutions are higher, by definition. Video and images around events having the necessary temporal and spatial resolution to provide a clear view of accidents and other incidents are bigger in size compared to location traces and other vehicle diagnostics data, even with the most advanced compression standards. The speeds supported by 4G/LTE networks ensure that videos and other data are available in near real-time for review, while also being necessary for the implementation of features like video live-streaming.
The other side of this equation is the cost of that data, which is usually bundled with the video telematics service. While rates have reduced, and pooled data plans help, excessive use beyond prescribed limits can lead to expensive overages, or drastic reductions in upload speeds – both bad outcomes for a fleet. A key concern for TSP’s and fleets as they launch and maintain a video telematics solution is the ongoing cost of data on a per device basis, which ultimately factors into the ROI they derive from it. This needs to be addressed in two ways: complete transparency around data usage at a granular (device) level, and providing a rich toolkit to configure the solution to fit within a predetermined data budget. In the following sections, we discuss how the RideView platform helps TSPs and fleets set and adhere to the data plan just right for them.
Contents [hide]
Contents
Event video configurations
Video Duration
The duration of an event video, pre, and post, has a big impact on the overall data consumption. By setting video duration to the minimum required to get the necessary context around an event, significant savings can be realized. This can be event-specific – e.g. tailgating events might need more pre-event capture duration to establish how long a driver was following dangerously close, but it might be lesser for a posted speed violation or a rolling stop.
Video Quality
This refers to the bitrate used in encoding the video and impacts the final size of the compressed video file. While the highest quality is ideal for all events, fleet managers might choose to configure different events at different quality settings, depending on the level of detail they want to see around an event.
Video Resolution
Once more, while Full HD resolution is ideal, HD, or even lower might suffice for certain categories of events. Working the numbers to find the ideal mix can go a long way towards staying within budget.
Video Format
picture-in-picture video format
This setting is relevant only for dual-camera solutions providing concurrent views of road and driver. We support the following formats:
- Side-by-side
- Picture-in-picture (with the flexibility to set either road or driver view as the major view)
- Only road
- Only cabin
Dual camera solutions are increasing in popularity due to the greater context they provide. However, fleets are often not ready to double their data consumption to avail of those benefits. The picture-in-picture format provides fleets with the option of having dual views at the same resolution as single-camera videos. The flexibility of having either road or driver view as the major view (and the other one as the inset), means that fleets can decide which view to prioritize, without adding to file sizes. ADAS based events like tailgating and rolling stops can have a road-major format, while DMS based events like driver distraction can have a driver-major format.
Enhanced DVR (E-DVR)
The Enhanced DVR functionality is probably the single most powerful tool our platform provides to help fleets stay within data budgets, while also ensuring that they get the highest quality videos for specific videos when they need them. A variant of the standard DVR functionality, instead of loop recording video on internal/SD storage, we allocate a separate buffer for storing event videos locally at the highest possible resolution. So, in the case of the only road facing cameras, videos can be stored at Full HD/HD resolution for up-to 30 days, locally. For dual-camera solutions, HD resolution videos in a side-by-side format providing maximum detail on both views are stored. For the regular upload, however, the fleet can configure upload at a lower resolution like 360p. Later, when the fleet manager is reviewing an incident on the portal, she might want to review an incident in higher detail. For example, if there is an instance where the driver was cut off by another vehicle making him brake hard, and the fleet manager wants them to review the video to check the other vehicle’s registration plates, she can make an E-DVR request at that point in time to get HD footage of the same incident.
This is in essence, ‘having the cake and eating it too’, for fleets. In regular operation, videos can be uploaded in lower resolution and quality leading to modest data usage. On-demand, and at the discretion of the fleet manager, they have access to the highest resolution videos for review.
Speed over posted limit – threshold configuration