Abstract: A telematics server manages meeting request messages sent from, and to, a vehicle-coupled device. The server performs authentication services when a subscriber logs in to the server from the vehicle-coupled device, or with a device associated with the subscriber's telematics services account. Upon login, the server may append a session identifier to the request message. After the message passes through the server, an application running on a device remote from the vehicle receives the request message and accepts user input that permits the remote device to transmit its current location to the vehicle-coupled device in a confirmation message according to the session identifier. The telematics server can use the session identifier to determine the destination address of the vehicle-coupled device to forward the confirmation message to. The vehicle-coupled device displays the remote user device location on a map. The request and confirmation messages may include a media content file.

Abstract: A user device application transmits the device's location and unique identifier with a message requesting location information that corresponds to a vehicle associated with the user device's unique identifier. The application sends the request message over a communication network to a central computer. The central computer obtains location information corresponding to the vehicle from a device proximate the vehicle. The central computer compares the locations of the user device and telematics device and generates a location differential value corresponding to the distance between them. If the differential value meets predetermined criteria, the central computer causes an action, for example forwarding the location information corresponding to the vehicle to the requesting user device. Or, the central computer sends the requesting device a request denied message. The central computer may also deny the request when the vehicle is moving, or if the user device has requested the vehicle's location too frequently.

Abstract: A telematics server manages meeting request messages sent from, and to, a vehicle-coupled device. The server performs authentication services when a subscriber logs in to the server from the vehicle-coupled device, or with a device associated with the subscriber's telematics services account. Upon login, the server may append a session identifier to the request message. After the message passes through the server, an application running on a device remote from the vehicle receives the request message and accepts user input that permits the remote device to transmit its current location to the vehicle-coupled device in a confirmation message according to the session identifier. The telematics server can use the session identifier to determine the destination address of the vehicle-coupled device to forward the confirmation message to. The vehicle-coupled device displays the remote user device location on a map. The request and confirmation messages may include a media content file.

Abstract: A telematics server manages meeting request messages sent from, and to, a vehicle-coupled device. The server performs authentication services when a subscriber logs in to the server from the vehicle-coupled device, or with a device associated with the subscriber's telematics services account. Upon login, the server may append a session identifier to the request message. After the message passes through the server, an application running on a device remote from the vehicle receives the request message and accepts user input that permits the remote device to transmit its current location to the vehicle-coupled device in a confirmation message according to the session identifier. The telematics server can use the session identifier to determine the destination address of the vehicle-coupled device to forward the confirmation message to. The vehicle-coupled device displays the remote user device location on a map. The request and confirmation messages may include a media content file.

Abstract: A telematics server manages meeting request messages sent from, and to, a vehicle-coupled device. The server performs authentication services when a subscriber logs in to the server from the vehicle-coupled device, or with a device associated with the subscriber's telematics services account. Upon login, the server may append a session identifier to the request message. After the message passes through the server, an application running on a device remote from the vehicle receives the request message and accepts user input that permits the remote device to transmit its current location to the vehicle-coupled device in a confirmation message according to the session identifier. The telematics server can use the session identifier to determine the destination address of the vehicle-coupled device to forward the confirmation message to. The vehicle-coupled device displays the remote user device location on a map. The request and confirmation messages may include a media content file.

Abstract: A telematics server manages meeting request messages sent from, and to, a vehicle-coupled device. The server performs authentication services when a subscriber logs in to the server from the vehicle-coupled device, or with a device associated with the subscriber's telematics services account. Upon login, the server may append a session identifier to the request message. After the message passes through the server, an application running on a device remote from the vehicle receives the request message and accepts user input that permits the remote device to transmit its current location to the vehicle-coupled device in a confirmation message according to the session identifier. The telematics server can use the session identifier to determine the destination address of the vehicle-coupled device to forward the confirmation message to. The vehicle-coupled device displays the remote user device location on a map. The request and confirmation messages may include a media content file.

Abstract: A telematics server manages meeting request messages sent from, and to, a vehicle-coupled device. The server performs authentication services when a subscriber logs in to the server from the vehicle-coupled device, or with a device associated with the subscriber's telematics services account. Upon login, the server may append a session identifier to the request message. After the message passes through the server, an application running on a device remote from the vehicle receives the request message and accepts user input that permits the remote device to transmit its current location to the vehicle-coupled device in a confirmation message according to the session identifier. The telematics server can use the session identifier to determine the destination address of the vehicle-coupled device to forward the confirmation message to. The vehicle-coupled device displays the remote user device location on a map. The request and confirmation messages may include a media content file.

Abstract: A user device application transmits the device's location and unique identifier with a message requesting location information that corresponds to a vehicle associated with the user device's unique identifier. The application sends the request message over a communication network to a central computer. The central computer obtains location information corresponding to the vehicle from a device proximate the vehicle. The central computer compares the locations of the user device and telematics device and generates a location differential value corresponding to the distance between them. If the differential value meets predetermined criteria, the central computer causes an action, for example forwarding the location information corresponding to the vehicle to the requesting user device. Or, the central computer sends the requesting device a request denied message. The central computer may also deny the request when the vehicle is moving, or if the user device has requested the vehicle's location too frequently.