NaviConnect is a platform for content delivery and IoT in fixed and mobile scenarios
NaviConnect is an integrated scalable platform that provides content delivery and IoT services. It works both in fixed and mobile environments and provides the service even with limited connectivity, thanks to local caching technologies and edge computing capabilities.
Discover our offer for content delivery and IoT!
NaviConnect, installed in fixed locations, offers access to pre-loaded content in events (congresses, exhibitions, etc.) libraries, hotels, construction sites, etc. All heavy content such as videos, tutorials, communication materials, internal documentation, magazines and newspapers can be accessed in a secure manner by many users simultaneously without degrading the overall quality of internet connection. NaviConnect can support local applications as well such as event management services, collaborative apps, etc. Users have access to the content via fully customised web portal.
NaviConnect, installed in vehicles, offers access to pre-loaded content in public transport (buses and trains), cruise ships and boats. Passengers can browse through movies, music, newspapers and tourist information. NaviConnect welcomes publicity content by local merchants as well.
Smart city iot Platform
NaviConnect for Smart City is an integrated and secure smart city platform. It consists of intelligent gateways (IGW) installed in vehicles (bus, car, drone) that collect data from sensors installed across the city. Any network of vehicles can be used, including drones. The smart city platform can be installed in fixed locations as well. The data is collected when the vehicle passes by, thus allowing for cheaper sensors sending data without using expensive network connection across large areas. The collected data is pre-processed on the edge and then sent to a central cloud service for further analysis and display. NaviConnect support of a wide array of sensor communication protocols (WiFi, Bluetooth, LoRa, 3G/4G/5G) and adding more.
Enables the use of low cost and low range sensors
Supports high traffic rates upstream from sensors
Improve territory coverage : Sensors can be deployed over large areas with no adequate coverage of 3G/4G, WiFi or LPWAN
Limits the number of fixed antennas to deploy on the territory
Intelligent gateway (IGW) which caches, processes and distributes content
NaviConnect Manager – admin console for content providers to dinamically manage the cache in the Gateways via API.
Dashboards – console for the monitoring of the service and for the display of data analytics
Sensors detecting the fullness of trashcans are installed throughout a city area. Their readings are collected by our Intelligent Gateways installed in public transport vehicles. As the public transport network covers the whole city, the sensor data collection can be done on regular intervals across large areas by just a few gateways at minimal cost. No need to ensure specific LPWAN area coverage or pay expensive 3G/4G subscriptions. The collected readings are sent to a cloud application when the buses enter a cheap connectivity area (like WiFi in bus depot).
The smart city platform NaviConnect can cover very successfully video surveillance applications. As video/photo content is very heavy to send to the cloud, it usually poses limitations to smart video services. NaviConnect installed on vehicles passing close to installed cameras can collect their recordings using WiFi/Bluetooth, making it an interesting option in surveillance and undercover missions over large areas or « blind spots ». As another scenario of this use case, we can consider cameras installed on the vehicle itself, whose video flux is treated locally in our Intelligent Gateways before being sent to the cloud.
REMOTE SENSOR DATA COLLECTION
NaviConnect is designed to challenge the paradigm that sensor data collection must be done through static infrastructure. in many remote areas, between cities, in the mountain or the sea shore, coverage by LPWAN, 3G/4G is not an option. Yet multitude of applications in agriculture, sea shore analysis, etc. Call for cheap and reliable way of collecting sensor data. NaviConnect can use any type of vehicle, including drones, to reach even the most remote sensors with the heaviest content like images or video, in the cheapest possible way, making the total cost of ownership of these services very low.
NaviConnect Intelligent Gateway is a product for ad-hoc, customizable and low-cost internet traffic optimization, aiming to deliver dramatically improved end-user experience in industries where available internet connectivity is of poor quality, unreliable or upgrades are expensive.
Intelligent Gateways provides reduction of overhead, can determine content’s popularity, socially-aware caching, prefetching…
The general architecture consists of two major components namely the cache controller (CC) and the Cache Node (CN).
Internet access: The CN has wlan0 virtual interface of radio0, that provides a communication between MBs (mesh network)
Redirection to the FON portal: The CN has wpub, virtual interface of radio1, that provides an open access to the user that has a login and password and weap, virtual interface of radio0, that provides a limited access to fonap registered members.
Reduction of overhead, through the use of Bloow Filters fully integrated in the CN, so they can collect the cached content and send them to the CC (Cache Controller). Bloom Filters are also integrated in the CC to get an overview of all the CN and provide the analysis of the content to imrpove the prefetching procedure.
Caching: The CN provides a caching feature to overcome network congestion and reduces traffic load and latency.
Remote management: CC is the remote manager or the rendez-vous point of all the differents CN in the network. The communication between CNs and CC is enabling by the Netconf protocol. The aim of the CC is to send prefetching command to specific CNs case by case thanks to the analysis of the content with the Bloom Filter algorithm and disconnection predictor. The CC also configures remotely the network params of the CNs.
The general Multi-access Edge Computing (MEC) caching architecture shown below, where MEC vCache application instantiated on the virtualization infrastructure of the MEC host. The virtualization infrastructure entity provides compute, storage, and network resources to run the vCache and other applications on the MEC host. The vCache works in-line mode, where session connectivity is maintained with the original Internet server while all traffic traverses the vCache application. The Cache Controller (CC) element of the caching system may reside either on the mobile core network or on the public Internet. However, the Content Server (CS) is available on the public Internet .
When the vCache application receives a content’s request that is stored in its local cache, the vCache immediately sends the requested content to the destined mobile end-user. This will result in savings in the backhaul capacity as well as improves the user QoE, as content can be transferred without the additional delays caused by the core network and public internet.
Maximize the user Quality of Experience (QoE) by bringing the applications and content closer to the network edge.
Provide the ultra low latency service.
vCache plays a key role to potimize and effectively using the network resources especially in video streaming applications which is resource-hungry and most used service in today’s mobile wireless systems
Save the Backhaul bandwidth
Virtual Cache (vCache)
Cache controller (CC)
MEC Orchestrator (OSS/MEO)
The caching system entities are described in the context of MEC architecture which will be demonstrated by setting a testbed using available wireless communication networks. Based on the Content Caching concept, JCP-C proposes a content caching system by considering the MEC architecture. The proposed content caching consists of MEC vCache Application running on the virtual infrastructure of the MEC Host. The vCache acts as a Content Caching server that caches the content at the edge network. In case of the absence of requested content in the local cache, the request is forwarded to the remote Content Server (CS) on the public Internet, and on reply, the copy of received content is stored locally and forward to the destined user. The Cache Controller (CC) plays a vital role in the content caching system. It is responsible for keeping track of all content cached status as well as instructing prefetching when needed. The CC interacts with a number of vCaches based on the managed object creation by MEC Platform Manager (MEPM). A user may be subject to handoverduring data transmission, and CC needs to detect the user’s possible next communication MEC host in order to provide seamless service to manage any handover (vertical or horizontal).
The Operations Support System (OSS) and MEC Application Orchestrator (MEAO) belong to the MEC system level, which is responsible to instruct the MEC Platform Manager (MEPM) for creating the vCache application instance in the MEC host. The envisioned Service Based Architecture (SBA) of 5G network will be based on functions that consume services and those that produce services using the request-response model, in other words subscribe-notify model. The ETSI MEC API framework does for the MEC application in the same as SBA framework doeas for network functions and their services. An example of resource application creation is given below.
Create New Resource
Client (e.g. MEA Orchestrator) requests to create an application instance resource for specific resource (E.G. vCache) type using HTTP POST requests.
MEC platform manager (MEPM)responds by response code 201 (Created) and the new created resources indentifier in the response body.
The MEC caching system will be demonstrated by using the MEC system with its communication system. The vCache application will be provided either in the container form by using a Docker-based containerization approach or set up in the virtual machine. The vCache application will contain the required capability to cache the contents, have an external interface with Cache Controller (CC), and session connectivity that will be maintained with the original Internet Content Server (CS). The vCache will work in the in-line mode, where all traffic traverses the vCache application, and it will also maintain the connectivity session with the CS and CC servers on the Internet.
When the vCache application will receive a request for content that is sotred in its local cache, the application will start directing the requested content to the destined user equipment. This will result in savings in the backhaul capacity as well as improves the user QoE, as content can be transferred without the additional delays caused by the core network and public internet.