FIG. 6A shows a process 600 for using system 300, according to one aspect of the present disclosure. Process 600 starts in block B602 when the cloud 302, PED 304 and media server 112 have been initialized. In block B604, PED 304 is connected to the media server 112. PED 304 goes through an authentication process to interface with the media server 112 by providing security credentials. Upon authentication, PED 304 retrieves an IFE system identifier that identifies the IFE system deployed at aircraft 132. The identifier may indicate the type of hardware and software that is being used by the IFE system.

In block B606, the PED 304 provides the identifier to a cloud based system via the communication interface 310. In one aspect, the cloud based system may be a cloud manager device that manages the cloud 302.

Based on the type of IFE system that is being used by the aircraft, in block B608, the VLSX image 306 is downloaded via a network connection to the PED 304. IFE data from IFE data store 308 corresponding to the IFE identifier is also provided to PED 304 and stored as IFE data 316. Thereafter, in block B610, the VLSX 314 is executed at PED 304 within VM 312.

In block B612, the IFE data 316 is provided to media server 112 via network interface 318. The media server 112 then provides the IFE data 316 to the content distribution system 104 for distribution.