In one aspect, the remote virtual loader is executed within a virtual machine (e.g., 402) of a cloud based system (302). The IFE data is provided by the electronic device to a server (e.g., 112) for distribution, using a distribution network (e.g., 200). The application provides an IFE system identifier to the remote virtual loader for the IFE data. The remote virtual loader retrieves the IFE data based on the IFE system identifier. The virtual tunnel links the remote virtual loader with a port (e.g., 318) of the electronic device, the port used to transfer the IFE data to the IFE system.

FIG. 6C shows a process 640 for using system 500 of FIG. 5, according to one aspect of the present disclosure. The process begins in block B642, when the cloud 302, PED 304 and media server 112 are initialized and operational.

In block B644, certificates 506 and 508 are loaded onto PED 304 so that the PED 304 can communicate with both the cloud 302 and the media server 112. In block B646, browser 502 is initialized using API 510 and certificates 506. In block B648, browser 502 connects to VM 402 and provides the certificate 506 to VLSX 404 for authentication. The browser 502 also provides an identifier associated with the IFE system and browser 504 to VLSX 404.

In block B650, browser 504 is initialized using API 510. Thereafter, browser 504 connects to media server 112 using certificate 508.