Vehicle request processing system, method, and computer storage medium

Abstract

Embodiments of the present application provide a vehicle request processing system, method and computer storage medium. The vehicle request processing system comprises a vehicle controller, a first cloud server and a second cloud server. The vehicle controller is configured to send a first service request to the first cloud server. The first cloud server is configured to encrypt vehicle identification information in the first service request to generate a second service request, and send the second service request to the second cloud server. The vehicle identification information is used to indicate a vehicle generating the first service request. The second cloud server is configured to send a service request result to the vehicle controller through the first cloud server in response to the second service request. The embodiments of the present application can improve the information security of the vehicle controller on the vehicle when sending a service request to the second cloud server.

Description

Technical Field

[0001] This application belongs to the field of vehicle technology, and in particular relates to a vehicle request processing system, method and computer storage medium. Background Technology

[0002] In this era of rapid development of intelligent vehicles, automotive data security has increasingly attracted widespread attention from society. Intelligent vehicles typically interact extensively with cloud servers, and the security of data transmission during these interactions is a key issue that automotive data security needs to address.

[0003] Currently, when vehicles request services from cloud servers, they typically use the HTTP protocol to interact with the cloud servers. However, the HTTP protocol has poor privacy. When vehicles directly interact with the cloud via the HTTP protocol, the data exchanged (such as service requests sent by the vehicle and the results of those requests sent by the cloud server) is vulnerable to hijacking, forgery, or tampering, which seriously affects the vehicle's information security. Criminals can easily use hijacked, forged, or tampered requests and data to break into the vehicle, and may even gain control of the vehicle by tampering with the data, posing a danger to the vehicle's driving safety. Summary of the Invention

[0004] In view of this, one of the technical problems solved by the embodiments of this application is to provide a vehicle request processing system, method and computer storage medium to overcome or avoid the above problems.

[0005] To achieve the above objectives, this application provides a vehicle request processing system, comprising: a vehicle controller, a first cloud server, and a second cloud server; the vehicle controller is configured to send a first service request to the first cloud server; the first cloud server is configured to encrypt vehicle identification information in the first service request to generate a second service request, and send the second service request to the second cloud server, wherein the vehicle identification information is used to indicate the vehicle that generated the first service request; the second cloud server is configured to respond to the second service request by sending the service request result to the vehicle controller through the first cloud server.

[0006] Optionally, the vehicle controller communicates with the first cloud server via the MQTT protocol and sends a first service request to the first cloud server via the MQTT protocol.

[0007] Optionally, the vehicle controller is configured to convert the initial service request sent by the vehicle service request module of the vehicle through the vehicle communication protocol into a first service request conforming to the MQTT protocol.

[0008] Optionally, the first cloud server communicates with the second cloud server via the HTTP protocol, and converts the first service request for encrypted vehicle identification information into a second service request conforming to the HTTP protocol, and sends the second service request to the second cloud server via the HTTP protocol.

[0009] Optionally, the first cloud server is a private cloud server.

[0010] Optionally, the vehicle request processing system supports a service-oriented architecture (SOA).

[0011] This application also provides a vehicle request processing method applied to a vehicle controller. The method includes: sending a first service request to a first cloud server, so that the first cloud server encrypts the vehicle identification information in the first service request to generate a second service request, and sending the second service request to a second cloud server, wherein the vehicle identification information is used to indicate the vehicle that generated the first service request; and receiving a service request result issued by the second cloud server through the first cloud server in response to the second service request.

[0012] This application also provides a vehicle request processing method applied to a first cloud server. The method includes: receiving a first service request sent by a vehicle controller; encrypting vehicle identification information in the first service request to generate a second service request, and sending the second service request to a second cloud server, wherein the vehicle identification information is used to indicate the vehicle that generated the first service request; receiving a service request result issued by the second cloud server in response to the second service request, and sending the service request result to the vehicle controller.

[0013] This application also provides a vehicle request processing method applied to a second cloud server. The method includes: receiving a second service request sent by a first cloud server, wherein the second service request is generated by the first cloud server encrypting vehicle identification information in a first service request, the first service request is sent to the first cloud server by a vehicle controller, and the vehicle identification information is used to indicate the vehicle that generated the first service request; and in response to the second service request, sending a service request result to the vehicle controller through the first cloud server.

[0014] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a processor, implements the methods described in the above embodiments.

[0015] As can be seen from the above technical solutions, in this embodiment, by setting up a first cloud server, encrypting the vehicle identification information in the first service request sent by the vehicle controller, and then sending the encrypted second service request to the second cloud server, the second cloud server responds to the second service request and sends the service request result to the vehicle controller through the first cloud server. Thus, the technical solution of this embodiment can improve the information security of the vehicle controller when sending service requests to the second cloud server. Even if the second service request is hijacked, it is difficult to determine the vehicle that issued the first service request through the hijacked second service request. It is difficult for criminals to use hijacked, forged or tampered first service requests and data to attack the vehicle and gain control of the vehicle, thereby improving the driving safety of the vehicle. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0017] Figure 1 This is an optional schematic diagram of the vehicle request processing system according to Embodiment 1 of this application;

[0018] Figure 2 This is another optional schematic diagram of the vehicle request processing system according to Embodiment 1 of this application;

[0019] Figure 3 This is an optional flowchart of the vehicle request processing method according to Embodiment 2 of this application;

[0020] Figure 4 This is an optional flowchart of the vehicle request processing method according to Embodiment 3 of this application;

[0021] Figure 5 This is an optional flowchart of the vehicle request processing method in Embodiment 4 of this application. Detailed Implementation

[0022] To enable those skilled in the art to better understand the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art should fall within the protection scope of the embodiments of this application.

[0023] It should be noted that implementing any technical solution of the embodiments of this application does not necessarily require achieving all of the above advantages simultaneously. The specific implementation of the embodiments of this application will be further described below with reference to the accompanying drawings.

[0024] Example 1

[0025] Figure 1 This is an optional schematic diagram of the vehicle request processing system according to Embodiment 1 of this application, as shown below. Figure 1 As shown, the vehicle request processing system includes: a vehicle controller 101, a first cloud server 102, and a second cloud server 103.

[0026] The vehicle controller 101 is used to send the first service request to the first cloud server 102;

[0027] The first cloud server 102 is used to encrypt the vehicle identification information in the first service request to generate a second service request, and send the second service request to the second cloud server, wherein the vehicle identification information is used to indicate the vehicle that generated the first service request.

[0028] The second cloud server 103 is used to respond to the second service request and send the service request result to the vehicle controller 101 through the first cloud server 102.

[0029] The vehicle request processing system in this application sets up a first cloud server 102. The first cloud server 102 encrypts the vehicle identification information in the first service request sent by the vehicle controller 101, and then sends the encrypted second service request to a second cloud server 103. The second cloud server 103 responds to the second service request and sends the service request result to the vehicle controller 101 through the first cloud server 102. Thus, the technical solution of this embodiment can improve the information security of the vehicle controller 101 when sending service requests to the second cloud server 103. Even if the second service request is hijacked, it is difficult to determine the vehicle that issued the first service request through the hijacked second service request. It is difficult for criminals to use hijacked, forged or tampered second service requests and data to attack the vehicle and gain control of the vehicle, thereby improving the driving safety of the vehicle.

[0030] The vehicle request processing system in this application is described below as an example. It should be understood that it is not intended to limit any aspect of the embodiments of this application.

[0031] In this application, a vehicle controller 101 is installed on the vehicle and may include one or more processing units capable of data processing. The vehicle controller 101 can send service requests to the cloud (e.g., a second cloud server 103, which can respond to service requests from the vehicle controller 101 and send service request results back to the vehicle controller 101). The vehicle controller 101 can fulfill corresponding requirements based on the service request results, such as controlling the vehicle based on the service request results. Service requests can be determined according to requirements. For example, a service request may be a request to solve a problem, obtain a new service, acquire information, or change a current service. For instance, a service request sent by the vehicle may be a request for real-time download of a high-definition map, a request for monitoring the vehicle's engine temperature, or a request for controlling the interior ambient lighting. The specific service requests are set according to actual needs, and this application does not impose any restrictions on this.

[0032] In this embodiment, the second cloud server 103 is located in the cloud and can provide cloud services to the vehicle. Specifically, the second cloud server 103 can respond to service requests from the vehicle controller 101 and send service request results to the vehicle controller 101, so that the vehicle controller 101 can implement the corresponding service requirements based on the service request results. For example, the service request results can be control instructions, files, parameter data, etc., to implement vehicle services. The second cloud server 103 in this application can be a public cloud server.

[0033] It should be noted that when the second cloud server 103 receives the first service request sent to it by the vehicle controller 101, it can also directly respond to the first service request to obtain the service request result. This embodiment of the application addresses the drawback of this approach, so that the second cloud server 103 does not directly respond to the first service request to obtain the service request result, but instead responds to the second service request obtained by the first cloud server 102 after encrypting the vehicle identification information in the first service request, and then sends the corresponding service request result to the vehicle controller 101 through the first cloud server 102.

[0034] In this embodiment, the first cloud server 102 is located in the cloud and can receive a first service request from the vehicle controller 101. It then encrypts the vehicle identification information in the first service request to generate a second service request. In this application, the vehicle identification information can be used to indicate the vehicle that generated the first service request. Its specific form is not particularly limited here. For example, in some embodiments, the vehicle identification information can be the vehicle's VIN (Vehicle Identification Number), license plate number, etc. Encrypting the vehicle identification information in the first service request to generate the second service request can be achieved using any encryption method, and this application does not impose any particular limitation. For example, in some embodiments, an encryption algorithm can be used for encryption. When the second cloud server 103 responds to the second service request by sending the service request result from the first cloud server 102, the first cloud server 102, upon receiving the service request result, can determine the vehicle identification information using a corresponding decryption algorithm and send the service request result to the vehicle controller 101 of the corresponding vehicle. For example, the encryption algorithm can be MD5, SHA1, 3DES, etc. It should be understood that this is not intended to limit this application.

[0035] In some optional embodiments, the vehicle request processing system of this application supports a service-oriented architecture (SOA). Specifically, SOA architecture allows for the distributed deployment, combination, and use of loosely coupled, coarse-grained application components over a network as needed, supporting efficient, flexible, and adaptable solutions. It can decompose different functional units of an application (called services) and connect them through well-defined interfaces and protocols. Therefore, this embodiment can easily modularize the vehicle request processing system using SOA architecture, enabling improvements in the efficiency and flexibility of vehicle request processing while ensuring vehicle information security.

[0036] Optionally, the first cloud server 102 in this application is a private cloud server. When the first cloud server 102 in this embodiment is a private cloud server, its data, security, and service quality are better guaranteed, and the information security of the vehicle can be better improved when processing the first service request.

[0037] Therefore, encrypting the vehicle identification information in the first service request through a first cloud server in the form of a private cloud server, and sending the second service request to the second cloud server, can more effectively improve the information security of the vehicle.

[0038] In some optional embodiments, the vehicle controller 101 communicates with the first cloud server 102 via the MQTT protocol and sends a first service request to the first cloud server 102 via the MQTT protocol.

[0039] Specifically, the vehicle controller 101 sends the first service request to the first cloud server 102 according to the MQTT protocol. Here, MQTT (Message Queuing Telemetry Transport) is a message queuing transport protocol that adopts a publish-subscribe mechanism. Subscribers only receive data they have subscribed to, and do not receive non-subscribed data. This ensures the exchange of necessary data while avoiding the storage and processing of invalid data, and also prevents the leakage of user information, thereby improving the confidentiality of vehicle data transmission.

[0040] In the above implementation of this embodiment, the vehicle controller 101 and the first cloud server 102 establish a communication connection through the MQTT protocol, and send the first service request to the first cloud server 102 through the MQTT protocol, which can effectively improve the security and confidentiality of data transmission.

[0041] Optionally, in this application, the communication connection between the vehicle controller 101 and the first cloud server 102 via the MQTT protocol is a private network connection, thereby ensuring the secure and controllable data transmission between the vehicle controller 101 and the first cloud server 102, and guaranteeing the security and confidentiality of data transmission when the vehicle controller 101 sends the first service request to the first cloud server 102 via the MQTT protocol.

[0042] Optionally, in this application, when the vehicle controller 101 and the first cloud server 102 transmit data via the MQTT protocol, the data transmitted via the MQTT protocol can be encrypted to further improve the security and confidentiality of data transmission. For example, when the vehicle controller 101 sends a first service request to the first cloud server 102 via the MQTT protocol, the first service request can be encrypted to further ensure the security and confidentiality of data transmission when the vehicle controller 101 sends the first service request to the first cloud server 102 via the MQTT protocol. After receiving the encrypted first service request via the MQTT protocol, the first cloud server 102 can decrypt it according to the decryption algorithm corresponding to the encryption algorithm. The encryption method here is not specifically limited in this application, and any suitable method can be used for implementation. For example, the encryption algorithm can be MD5, SHA1, 3DES, etc.

[0043] Optionally, after the vehicle controller 101 sends the first service request to the first cloud server 102 via the MQTT protocol, the first cloud server 102 in this application can encrypt the vehicle identification information in the first service request using an encryption algorithm based on the MQTT protocol to generate a second service request. In this way, by combining the confidentiality characteristics of the MQTT protocol with the encryption algorithm to encrypt the vehicle identification information, the leakage of vehicle identification information can be better prevented. This can improve the information security of the vehicle controller 101 when sending service requests to the second cloud server 103. Even if the second service request generated after encrypting the vehicle identification information in the first service request is hijacked, it is difficult to determine the vehicle that issued the first service request through the hijacked second service request. Criminals cannot use the hijacked, forged, or tampered second service request and data to attack the vehicle and gain control of the vehicle, thus improving vehicle driving safety.

[0044] In some optional embodiments, the first cloud server 102 and the second cloud server 103 establish a communication connection via the HTTP protocol, and convert the first service request for encrypted vehicle identification information into a second service request conforming to the HTTP protocol, and send the second service request to the second cloud server 103 via the HTTP protocol.

[0045] Specifically, the HTTP (Hypertext Transfer Protocol) protocol is an application-layer transport protocol based on the TCP protocol. Simply put, it's a set of rules for data transmission between clients and servers. The HTTP protocol itself does not persist sent requests and corresponding communication states, making communication simple and fast, thus enabling the rapid processing of large volumes of transactions and achieving high efficiency.

[0046] In the above implementation of this embodiment, the first cloud server 102 and the second cloud server 103 establish a communication connection through the HTTP protocol, and convert the first service request for encrypted vehicle identification information into a second service request conforming to the HTTP protocol, and send the second service request to the second cloud server 103 through the HTTP protocol, so that the second cloud server 103 can guarantee the efficiency of the first cloud server 102 in sending the second service request to the second cloud server 103, and the efficiency of the second cloud server 103 in sending the service request result to the first cloud server 102.

[0047] Optionally, when the first cloud server 102 sends a second service request conforming to the HTTP protocol to the second cloud server 103 via the HTTP protocol, the second cloud server 103 can respond to the second service request by calling the RSTful interface of the second cloud server 103, so as to obtain the corresponding service request result.

[0048] In some optional embodiments, the vehicle controller 101 is configured to convert the initial service request sent by the vehicle service execution module of the vehicle via the in-vehicle communication protocol into a first service request conforming to the MQTT protocol. In this way, the vehicle controller 101 can effectively obtain the first service request conforming to the MQTT protocol.

[0049] Specifically, the vehicle service request module can send an initial service request to the vehicle controller 101 via the vehicle communication protocol. The initial service request can be determined based on the user's needs, and the initial service request can be different for different user needs. For example, the vehicle service request module can be a hardware module on the vehicle that can receive user operation commands, such as an on-board terminal (e.g., an on-board screen), a voice recognition module, a gesture recognition module, etc.

[0050] In this application, the vehicle service request module can send an initial service request to the vehicle controller 101 using any in-vehicle communication protocol. For example, the in-vehicle communication protocol can be the SOME / IP protocol, the CAN protocol, etc. In implementations where the vehicle request processing system supports a service-oriented architecture (SOA), using the SOME / IP protocol as the in-vehicle communication protocol to send the initial service request is more suitable for the requirements of the SOA architecture.

[0051] Optionally, in this application, the services requested by the vehicle controller 101 from the second cloud server 103 through the first cloud server 102 can all be services that have undergone security authentication. The second cloud server 103 can only provide service request results for service requests corresponding to services that have undergone security authentication, thereby improving information security. In addition, the address of the second server 103 requested by the first cloud server 102 and the sending of the second service request to the second cloud server 103 are also secure and controllable, thereby further improving information security.

[0052] To facilitate understanding, taking the vehicle service request module as an example of an in-vehicle terminal, after the vehicle service request module receives the user's operation instruction (e.g., a selection instruction in the in-vehicle terminal), the user's needs are determined. For example, the need could be to make the ambient lighting in the vehicle play a light show. The vehicle service request module can then generate an initial service request to obtain the ambient lighting light show service from the cloud based on the user's operation instruction. This initial service request is then sent to the vehicle controller 101 via an in-vehicle communication protocol (e.g., SOME / IP protocol). The vehicle controller 101 can convert the initial service request into a first service request conforming to the MQTT protocol, and then send this first service request to the first cloud server 102. The first cloud server 102 can then... The first service request is encrypted using the MQTT protocol, and then converted into a second service request conforming to the HTTP protocol. This second service request is then sent to a second cloud server 103 via HTTP. The second cloud server 103 responds to the second service request by sending the corresponding service request result to the vehicle controller 101 via the first cloud server 102. The vehicle controller 101 can then send the service request result to the vehicle terminal. Furthermore, the vehicle controller 101 can parse the service request result and, based on the parsed result, instruct the corresponding vehicle service execution module (e.g., various ambient lights) to execute a predetermined ambient light show service, thereby controlling the vehicle to achieve the desired light show effect for the interior ambient lights. It should be understood that the above example is not intended to limit this application in any way.

[0053] Figure 2 This is another optional schematic diagram of the vehicle request processing system according to Embodiment 1 of this application. Combined with... Figure 2The illustration provides an example of the vehicle request processing system in this application. This optional vehicle request processing system supports a service-oriented SOA architecture and includes: a vehicle controller 101, a first cloud server 102, and a second cloud server 103. The vehicle controller 101 is located in the vehicle and may include multiple service proxy modules 1011. The vehicle also includes multiple vehicle service request modules 104. The first cloud server 102 and the vehicle controller 101 can constitute a vehicle abstraction layer (VAL). The vehicle controller 101's service proxy module 1011 interacts with the vehicle service request module 104 via an in-vehicle communication protocol (e.g., SOME / IP protocol). The vehicle controller 101 communicates with the first cloud server 102 (which can be a private cloud server) via the MQTT protocol, and the first cloud server 102 communicates with the second cloud server 103 via the HTTP protocol. The vehicle service request module 104 sends an initial service request to the vehicle controller 101's service proxy module 1011 via an in-vehicle communication protocol (e.g., SOME / IP protocol). The vehicle controller 101's service proxy module 1011 converts the initial service request into a first service request conforming to the MQTT protocol, and then transmits the first service request conforming to the MQTT protocol via MQTT. The MQTT protocol is sent to the first cloud server 102; the first cloud server 102 encrypts the vehicle identification information in the first service request using an encryption algorithm based on the MQTT protocol, and converts the first service request with encrypted vehicle identification information into a second service request conforming to the HTTP protocol, and sends the second service request to the second cloud server 103 via the HTTP protocol; the second cloud server 103 responds to the second service request, processes the second service request, obtains the service request result, and sends the service request result back to the first cloud server 102, which then sends the service request result to the vehicle controller 101. The vehicle controller 101 can send the service request result to the vehicle service request module 104, and / or, the vehicle controller 101 can further cause the corresponding vehicle service execution module (not shown in the figure) to perform actions based on the service request result to achieve vehicle control. It should be understood that the above... Figure 2 The interpretation thereof shall not be construed as limiting the scope of this application.

[0054] In summary, in this embodiment, by setting up a first cloud server 102, encrypting the vehicle identification information in the first service request sent by the vehicle controller 101, and then sending the encrypted second service request to a second cloud server 103, the second cloud server 103 responds to the second service request by sending the service request result to the vehicle controller 101 through the first cloud server 102. Thus, the technical solution of this embodiment can improve the information security of the vehicle controller 101 when sending a service request to the second cloud server 103. Even if the second service request is hijacked, it is difficult to determine the vehicle that issued the first service request through the hijacked second service request. It is difficult for criminals to use the hijacked, forged, or tampered second service request and data to attack the vehicle and gain control of the vehicle, thereby improving the driving safety of the vehicle.

[0055] It is understood that the above embodiments are merely exemplary embodiments of the vehicle request processing system in this application and are not intended to limit the embodiments of this application.

[0056] Example 2

[0057] Figure 3 This is an optional flowchart of a vehicle request processing method according to Embodiment 2 of this application. This vehicle request processing method is applied to a vehicle controller 101, such as... Figure 3 As shown, the vehicle request processing method includes the following steps:

[0058] Step S301: Send the first service request to the first cloud server so that the first cloud server encrypts the vehicle identification information in the first service request to generate a second service request, and sends the second service request to the second cloud server, wherein the vehicle identification information is used to indicate the vehicle that generated the first service request.

[0059] Step S302: Receive the service request result issued by the first cloud server in response to the second service request from the second cloud server.

[0060] In some optional embodiments, the vehicle controller 101 establishes a communication connection with the first cloud server 102 via the MQTT protocol; sending the first service request to the first cloud server 102 includes sending the first service request to the first cloud server 102 via the MQTT protocol.

[0061] In some optional embodiments, the method further includes: receiving an initial service request sent by the vehicle service execution module of the vehicle via an in-vehicle communication protocol, and converting the initial service request into a first service request conforming to the MQTT protocol.

[0062] In some optional embodiments, the first cloud server 102 and the second cloud server 103 establish a communication connection via the HTTP protocol, and convert the first service request for encrypted vehicle identification information into a second service request conforming to the HTTP protocol, and send the second service request to the second cloud server 103 via the HTTP protocol.

[0063] In some alternative embodiments, the first cloud server 102 is a private cloud server.

[0064] In some optional embodiments, the vehicle request processing method supports a service-oriented architecture (SOA).

[0065] In this embodiment, by setting up a first cloud server 102, the vehicle identification information in the first service request sent by the vehicle controller 101 is encrypted, and then the encrypted second service request is sent to a second cloud server 103. The second cloud server 103 responds to the second service request and sends the service request result to the vehicle controller 101 through the first cloud server 102. Thus, the information security of the vehicle controller 101 in the vehicle when sending a service request to the second cloud server 103 can be improved through the technical solution of this embodiment. Even if the second service request is hijacked, it is difficult to determine the vehicle that issued the first service request through the hijacked second service request. It is difficult for criminals to use the hijacked, forged or tampered second service request and data to attack the vehicle and gain control of the vehicle, thereby improving the driving safety of the vehicle.

[0066] It should be understood that the vehicle request processing method applied to the vehicle controller 101 described above is based on the same inventive concept as the vehicle request processing system of Embodiment 1. Its various implementation methods and related beneficial effects have been described in detail in the aforementioned vehicle request processing system of Embodiment 1. For details, please refer to the aforementioned vehicle request processing system of Embodiment 1 for understanding, and will not be repeated here.

[0067] Example 3

[0068] Figure 4 This is an optional flowchart of the vehicle request processing method according to Embodiment 3 of this application. Unlike the embodiments described above, this vehicle request processing method is applied to a first cloud server 102, such as... Figure 4 As shown, the vehicle request processing method includes the following steps:

[0069] Step S401: Receive the first service request sent by the vehicle controller.

[0070] Step S402: Encrypt the vehicle identification information in the first service request to generate a second service request, and send the second service request to the second cloud server, wherein the vehicle identification information is used to indicate the vehicle that generated the first service request.

[0071] Step S403: Receive the service request result issued by the second cloud server in response to the second service request, and send the service request result to the vehicle controller.

[0072] In some optional embodiments, the vehicle controller 101 and the first cloud server 102 establish a communication connection via the MQTT protocol; step S401 includes: receiving a first service request sent by the vehicle controller 101 via the MQTT protocol.

[0073] In some alternative embodiments, the vehicle controller converts the initial service request sent by the vehicle's vehicle service execution module via the vehicle communication protocol into a first service request conforming to the MQTT protocol.

[0074] In some optional embodiments, the first cloud server 102 and the second cloud server 103 establish a communication connection via the HTTP protocol; step S402 includes: converting the first service request for encrypted vehicle identification information into a second service request conforming to the HTTP protocol, and sending the second service request to the second cloud server 103 via the HTTP protocol.

[0075] In some alternative embodiments, the first cloud server 102 is a private cloud server.

[0076] In some optional embodiments, the vehicle request processing method supports a service-oriented architecture (SOA).

[0077] In this embodiment, by setting up a first cloud server 102, the vehicle identification information in the first service request sent by the vehicle controller 101 is encrypted, and then the encrypted second service request is sent to a second cloud server 103. The second cloud server 103 responds to the second service request and sends the service request result to the vehicle controller 101 through the first cloud server 102. Thus, the information security of the vehicle controller 101 in the vehicle when sending a service request to the second cloud server 103 can be improved through the technical solution of this embodiment. Even if the second service request is hijacked, it is difficult to determine the vehicle that issued the first service request through the hijacked second service request. It is difficult for criminals to use the hijacked, forged or tampered second service request and data to attack the vehicle and gain control of the vehicle, thereby improving the driving safety of the vehicle.

[0078] It should be understood that the vehicle request processing method applied to the first cloud server 102 described above is based on the same inventive concept as the vehicle request processing system in Embodiment 1. Its various implementation methods and related beneficial effects have been described in detail in the vehicle request processing system embodiment of Embodiment 1. For details, please refer to the vehicle request processing system of Embodiment 1 described above for understanding, and will not be repeated here.

[0079] Example 4

[0080] Figure 5 This is an optional flowchart of the vehicle request processing method according to Embodiment 4 of this application. Unlike the embodiments described above, this vehicle request processing method is applied to the second cloud server 103, such as... Figure 5 As shown, the vehicle request processing method includes the following steps:

[0081] Step S501: Receive a second service request sent by the first cloud server, wherein the second service request is generated by the first cloud server encrypting the vehicle identification information in the first service request, and the first service request is sent by the vehicle controller to the first cloud server, and the vehicle identification information is used to indicate the vehicle that generated the first service request.

[0082] Step S502: In response to the second service request, the service request result is sent to the vehicle controller through the first cloud server.

[0083] In some optional embodiments, the vehicle controller 101 establishes a communication connection via the MQTT protocol and sends a first service request to the first cloud server 102 via the MQTT protocol.

[0084] In some optional embodiments, the vehicle controller 101 converts the initial service request sent by the vehicle's vehicle service execution module via the vehicle communication protocol into a first service request conforming to the MQTT protocol.

[0085] In some optional embodiments, the first cloud server 102 and the second cloud server 103 establish a communication connection through the HTTP protocol. The first cloud server 102 encrypts the vehicle identification information in the first service request and converts the first service request with encrypted vehicle identification information into a second service request that conforms to the HTTP protocol. Step S502 includes: receiving the second service request sent by the first cloud server 102 through the HTTP protocol.

[0086] In some alternative embodiments, the first cloud server 102 is a private cloud server.

[0087] In some optional embodiments, the vehicle request processing method supports a service-oriented architecture (SOA).

[0088] In this embodiment, by setting up a first cloud server 102, the vehicle identification information in the first service request sent by the vehicle controller 101 is encrypted, and then the encrypted second service request is sent to a second cloud server 103. The second cloud server 103 responds to the second service request and sends the corresponding service request result to the vehicle controller 101 through the first cloud server 102. Thus, the information security of the vehicle controller 101 in the vehicle when sending service requests to the second cloud server 103 can be improved through the technical solution of this embodiment. Even if the second service request is hijacked, it is difficult to determine the vehicle that issued the first service request through the hijacked second service request. It is difficult for criminals to use the hijacked, forged or tampered second service request and data to attack the vehicle and gain control of the vehicle, thereby improving the driving safety of the vehicle.

[0089] It should be understood that the vehicle request processing method applied to the second cloud server 103 described above is based on the same inventive concept as the vehicle request processing system in Embodiment 1. Its various implementation methods and related beneficial effects have been described in detail in the vehicle request processing system embodiment of Embodiment 1. For details, please refer to the vehicle request processing system of Embodiment 1 described above for understanding, and it will not be repeated here.

[0090] Example 5

[0091] This application also provides a computer storage medium storing a computer program that, when executed by a processor, implements the operation corresponding to any of the vehicle request processing methods in Embodiments 2, 3, and 4 above.

[0092] It should be noted that, depending on the implementation needs, the various components / steps described in the embodiments of this application can be broken down into more components / steps, or two or more components / steps or parts of the operation of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of this application.

[0093] The methods described in the embodiments of this application can be implemented in hardware, firmware, or as software or computer code that can be stored in a recording medium (such as a CD, ROM, RAM, floppy disk, hard disk, or magneto-optical disk), or as computer code originally stored on a remote recording medium or a non-transitory machine-readable medium and subsequently stored on a local recording medium, downloaded over a network. Thus, the methods described herein can be processed by software stored on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware (such as an ASIC or FPGA). It is understood that the computer, processor, microprocessor controller, or programmable hardware includes storage components (e.g., RAM, ROM, flash memory, etc.) capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods described herein. Furthermore, when a general-purpose computer accesses the code used to implement the methods shown herein, the execution of the code transforms the general-purpose computer into a dedicated computer for performing the methods shown herein.

[0094] Those skilled in the art will recognize that the units and method steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0095] The above embodiments are only used to illustrate the embodiments of this application, and are not intended to limit the embodiments of this application. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the embodiments of this application. Therefore, all equivalent technical solutions also fall within the scope of the embodiments of this application, and the patent protection scope of the embodiments of this application should be defined by the claims.

Claims

1. A vehicle request processing system, characterized in that, include: The vehicle controller, the first cloud server, and the second cloud server, wherein the first cloud server is a private cloud server; The vehicle controller is used to send a first service request to the first cloud server; The first cloud server is used to encrypt the vehicle identification information in the first service request to generate a second service request, and send the second service request to the second cloud server, wherein the vehicle identification information is used to indicate the vehicle that generated the first service request; The second cloud server is used to respond to the second service request by sending the service request result to the vehicle controller through the first cloud server.

2. The system according to claim 1, characterized in that, The vehicle controller communicates with the first cloud server via the MQTT protocol and sends a first service request to the first cloud server via the MQTT protocol.

3. The system according to claim 2, characterized in that, The vehicle controller is used to convert the initial service request sent by the vehicle service request module of the vehicle through the vehicle communication protocol into a first service request conforming to the MQTT protocol.

4. The system according to claim 1, characterized in that, The first cloud server communicates with the second cloud server via the HTTP protocol, and converts the first service request for encrypted vehicle identification information into a second service request conforming to the HTTP protocol, and sends the second service request to the second cloud server via the HTTP protocol.

5. The system according to any one of claims 1-4, characterized in that, The vehicle request processing system supports a service-oriented architecture (SOA).

6. A vehicle request processing method, characterized in that, Applied to a vehicle controller, the method includes: A first service request is sent to a first cloud server, so that the first cloud server encrypts the vehicle identification information in the first service request to generate a second service request, and sends the second service request to a second cloud server. The first cloud server is a private cloud server, and the vehicle identification information is used to indicate the vehicle that generated the first service request. Receive the service request result issued by the first cloud server in response to the second service request from the second cloud server.

7. A vehicle request processing method, characterized in that, Applied to a first cloud server, which is a private cloud server, the method includes: Receive the first service request sent by the vehicle controller; The vehicle identification information in the first service request is encrypted to generate a second service request, and the second service request is sent to the second cloud server, wherein the vehicle identification information is used to indicate the vehicle that generated the first service request; The system receives the service request result from the second cloud server in response to the second service request, and then sends the service request result to the vehicle controller.

8. A vehicle request processing method, characterized in that, Applied to a second cloud server, the method includes: The system receives a second service request sent by a first cloud server, wherein the first cloud server is a private cloud server, the second service request is generated by the first cloud server encrypting the vehicle identification information in the first service request, the first service request is sent by the vehicle controller to the first cloud server, and the vehicle identification information is used to indicate the vehicle that generated the first service request. In response to the second service request, the service request result is sent to the vehicle controller via the first cloud server.

9. A computer storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the method as described in any one of claims 6-8.

Images