Abstract: Embodiments are directed towards a system and method of anonymizing vehicle location data by using a centralized location of entities near the vehicle instead of the actual vehicle location. One or more entities are selected within a threshold radius around the vehicle. The centralized location is determined based on publicly available entity location information for the selected entities. The centralized location is stored or transmitted to third parties as the vehicle's location. A characteristic of the vehicle or a time range associated with capturing the actual vehicle location may be associated with the centralized location without including an identifier of the vehicle.

Abstract: Embodiments are directed towards a system and method of anonymizing vehicle location data by using a centralized location of entities near the vehicle instead of the actual vehicle location. One or more entities are selected within a threshold radius around the vehicle. The centralized location is determined based on publicly available entity location information for the selected entities. The centralized location is stored or transmitted to third parties as the vehicle's location. A characteristic of the vehicle or a time range associated with capturing the actual vehicle location may be associated with the centralized location without including an identifier of the vehicle.

Abstract: Embodiments are directed towards a system and method of anonymizing vehicle location data by using a centralized location of entities near the vehicle instead of the actual vehicle location. One or more entities are selected within a threshold radius around the vehicle. The centralized location is determined based on publicly available entity location information for the selected entities. The centralized location is stored or transmitted to third parties as the vehicle's location. A characteristic of the vehicle or a time range associated with capturing the actual vehicle location may be associated with the centralized location without including an identifier of the vehicle.

Abstract: Embodiments are directed towards a system and method of employing a bridge service to coordinate messages from a keep-alive connection between a head unit of a vehicle and a connection broker with microservices via unary connections. The bridge service stores configuration information that maps topic connection information for the keep-alive connection with microservice connection information. The bridge service subscribes with the connection broker to topics associated with the microservices based on the configuration information. A message that is published to the keep-alive connection having a published topic that corresponds to a subscribed topic is received from the connection broker. The microservice connection information that maps to the published topic is selected based on the configuration information.

Abstract: Embodiments are directed towards a system and method of employing a bridge service to coordinate messages from a keep-alive connection between a head unit of a vehicle and a connection broker with microservices via unary connections. The bridge service stores configuration information that maps topic connection information for the keep-alive connection with microservice connection information. The bridge service subscribes with the connection broker to topics associated with the microservices based on the configuration information. A message that is published to the keep-alive connection having a published topic that corresponds to a subscribed topic is received from the connection broker. The microservice connection information that maps to the published topic is selected based on the configuration information.

Abstract: Embodiments are directed towards a system and method of employing a bridge service to coordinate messages from a keep-alive connection between a head unit of a vehicle and a connection broker with microservices via unary connections. The bridge service stores configuration information that maps topic connection information for the keep-alive connection with microservice connection information. The bridge service subscribes with the connection broker to topics associated with the microservices based on the configuration information. A message that is published to the keep-alive connection having a published topic that corresponds to a subscribed topic is received from the connection broker. The microservice connection information that maps to the published topic is selected based on the configuration information.

Abstract: A Web service request is received that is constructed according to a first Web service technology and that targets an activation file constructed according to the first Web service technology. When the Web service request is received, it is modified to target an activation file constructed according to a second Web service technology. Binding properties associated with the Web service request and binding properties supported by a targeted Web service may also be identified. Binding properties for use in forwarding the Web service request to the Web service are then selected based upon the binding properties associated with the Web service request and the binding properties supported by the Web service. The Web service request is then forwarded to the Web service using a binding having the selected binding properties.

Abstract: A Web service request is received that is constructed according to a first Web service technology and that targets an activation file constructed according to the first Web service technology. When the Web service request is received, it is modified to target an activation file constructed according to a second Web service technology. Binding properties associated with the Web service request and binding properties supported by a targeted Web service may also be identified. Binding properties for use in forwarding the Web service request to the Web service are then selected based upon the binding properties associated with the Web service request and the binding properties supported by the Web service. The Web service request is then forwarded to the Web service using a binding having the selected binding properties.

Abstract: A secondary database query is registered for a change notification with a database server. The secondary database query is a database query that is eligible for a change notification from the database server and that is configured to return a superset of the data returned by a corresponding complex database query that is ineligible for a change notification. If a change notification is received from the database server for the secondary database query, an entry in a database query result cache corresponding to the complex database query is invalidated.