**5.2.2 Architecture**

As mentioned before, this service is integrated with the previously described connectivity architecture via heavy communications scheme. So, when the terrestrial Remote-AMS generate tasks which involve downloading or uploading information from and to trains, it have to communicate with Broadband Communications Manager (BCM), because this is the entity who arbitrates heavy communications between ground and train applications. In this case, BCM arbitrates communications between terrestrial and on board Remote-AMS application. For proper integration with BCM, Remote-AMS (more specifically the terrestrial one) shall be compliant with the protocol of communication established by this management entity.

At this point it is important to remember that BCM does not interfere between final applications communication. The Fig. 7 shows Remote-AMS service architecture and its integration with the train-to-earth wireless communication technology.

Fig. 7. Remote Application Management Service (Remote-AMS) and how it interoperates with the Broadband Communication Manager (BCM).

So, whenever terrestrial Remote-AMS schedules a task it has to send to the BCM a connection message. Once connected, there will be many communication requests as required. When BCM determines that a Remote-AMS request should be addressed, sends a notification to terrestrial Remote-AMS indicating to perform the service task corresponding to this request. Once the communication is completed, terrestrial Remote-AMS sends a notification to BCM which sets this request as completed and removes it from the corresponding communication prioritization queue. This same pattern is followed for all terrestrial Remote-AMS communication requests.
