System and method for correlating keep-alive connection communications with unary connection communications
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. The bridge service establishes a unary connection with a microservice based on the selected microservice connection information, which is utilized to provide message payload information from the bridge service to the microservice.
Claims
exact text as granted — not AI-modified1 . A computer-implemented method, comprising:
sending a request to a connection broker to subscribe to a topic associated with a microservice; receiving, from the connection broker, a message having the topic that has been obtained by the connection broker via a continuous connection between the connection broker and a head unit of a vehicle; establishing an on-demand connection with the microservice in response to receipt of the message having the topic; and providing at least a portion of the message to the microservice via the on-demand connection.
2 . The computer-implemented method of claim 1 , wherein establishing the on-demand connection with the microservice, includes:
establishing a limited-duration connection with the microservice independent of the continuous connection.
3 . The computer-implemented method of claim 1 , wherein establishing the on-demand connection with the microservice includes:
establishing a single socket connection that is maintained for multiple messages transmitted by the head unit to the continuous connection and obtained by the connection broker.
4 . The computer-implemented method of claim 1 , wherein establishing the on-demand connection with the microservice includes:
establishing a REST connection with the microservice.
5 . The computer-implemented method of claim 1 , wherein establishing the on-demand connection with the microservice includes:
establishing a gRPC connection with the microservice.
6 . The computer-implemented method of claim 1 , further comprising:
storing configuration information that maps topic connection information for the continuous connection with microservice connection information for one or more microservices.
7 . The computer-implemented method of claim 1 , further comprising:
storing, for the microservice, a first topic in which to subscribe to first messages published by the head unit to the continuous connection using the first topic; and storing, for the microservice, a second topic in which to publish second messages to the continuous connection in response to the first messages.
8 . The computer-implemented method of claim 1 , further comprising:
storing, for the microservice, call information that enables establishment of a limited-duration connection with the microservice; and utilizing the call information to establish the limited-duration connection as the on-demand connection.
9 . The computer-implemented method of claim 1 , wherein providing the portion of the message to the microservice includes:
providing a payload portion of the message to a backend server configured to maintain accessory information obtained from one or more accessories on the vehicle.
10 . The computer-implemented method of claim 1 , further comprising:
receiving a response from the microservice via the on-demand connection; and forwarding the response to the head unit via the connection broker and the continuous connection.
11 . A non-transitory computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, cause the processor to:
subscribe with a connection broker to a topic associated with a microservice for messages published to a keep-alive connection between a head unit of a vehicle and the connection broker; receive, from the connection broker, a message that was published to the keep-alive connection in association with the topic; establish an on-demand connection with the microservice in response to receipt of the message being published in association with the topic; and provide at least a portion of the message to the microservice via the on-demand connection.
12 . The non-transitory computer-readable storage medium of claim 11 , wherein the execution of the computer instructions by the processor to establish the on-demand connection with the microservice further cause the processor to:
establish a limited-duration connection with the microservice independent of the keep-alive connection and independent of payload information in the message.
13 . The non-transitory computer-readable storage medium of claim 11 , wherein the execution of the computer instructions by the processor to establish the on-demand connection with the microservice further cause the processor to:
establish a single connection that is maintained for multiple messages published by the head unit to the keep-alive connection and obtained by the connection broker.
14 . A system, comprising:
a memory that stores computer instructions; a processor that is configured to execute the computer instructions to:
send a request to a connection broker to subscribe to a topic associated with a microservice;
receive, from the connection broker, a message identifying the topic that has been obtained by the connection broker via a continuous connection between a head unit of a vehicle and the connection broker;
establish a unary connection with the microservice in response to receipt of the message identifying the topic; and
provide at least a portion of the message to the microservice via the unary connection.
15 . The system of claim 14 , wherein the processor is configured to establish the continuous connection with the microservice by executing the computer instructions to:
establish a limited-duration connection with the microservice independent of the continuous connection and independent of payload information in the message.
16 . The system of claim 14 , wherein the processor is configured to establish the continuous connection with the microservice by executing the computer instructions to:
establish a single socket connection that is maintained for multiple messages transmitted by the head unit to the continuous connection and obtained by the connection broker.
17 . The system of claim 14 , wherein the processor is configured to establish the continuous connection with the microservice by executing the computer instructions to:
establish a REST connection with the microservice.
18 . The system of claim 14 , wherein the processor is configured to establish the continuous connection with the microservice by executing the computer instructions to:
establish a gRPC connection with the microservice.
19 . The system of claim 14 , wherein the processor is configured to execute the computer instructions further to:
store configuration information that maps topic connection information for the continuous connection with microservice connection information for one or more microservices.
20 . The system of claim 14 , wherein the processor is configured to execute the computer instructions further to:
store, for the microservice, call information that enables establishment of a limited-duration connection with the microservice; and utilize the call information to establish the limited-duration connection as the unary connection.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.