SNIP_ADAPTIVE_CAN_FIGURE_Figure_4_3_AUTOMOTIVEAPI

Figure 4.3: The Automotive API Gateway Connecting VSS data to in-vehicle services. In general, it can be assumed that most, if not all data is already available within the vehicle. That means that there are existing Vehicle Internal Services with OEM proprietary Interface definitions. They have to be connected to the VSS derived Service Interfaces of the Automotive API Gateway . This requires mapping. Since the definitions of the vehicle internal Service Interfaces are proprietary , the mapping can also only be a proprietary solution. However, this concept aims to support the mapping efforts. These approaches can be mixed, so that for each signal the appropriate solution can be chosen. Although in the above figure the mapping is shown as part of the Gateway Composite SWC, it can also be deployed outside of the Gateway .