Distribution system and distribution method for automobile digital key service request and medium

Abstract

The invention provides an automobile digital key service request distribution system and method and a medium, and the system comprises a cloud server which receives a digital key service request sent by a client; a plurality of service nodes are deployed under the digital key service private clouds; the global flow manager is in communication connection with the cloud server and the digital key service private cloud; the global flow manager is used for regularly checking the health degrees of all service nodes; performing domain name resolution on the digital key service request to obtain address information; acquiring a private cloud matched with the client according to the address information and the health degree of the service node, and representing the private cloud as a target private cloud; and sending the IP address of one service node in the target private cloud to the client according to the load balancing strategy. According to the invention, normal operation of the automobile digital key service can be ensured, and the user experience is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle networking, and in particular to a distribution system, distribution method and medium for automobile digital key service requests. Background Art

[0002] With the advancement of Internet of Vehicles technology, the client's demand for car keys is no longer limited to traditional physical keys. In order to meet the growing needs of clients, the Internet of Vehicles TSP cloud platform has launched the 3C digital key service, referred to as KTS service. However, with the rapid growth in the number of clients, the KTS service faces challenges brought by high concurrent requests, such as increased service pressure and even service downtime. To solve these problems, a common practice is to perform load balancing by adding service Pod nodes.

[0003] However, adding Pod nodes relieves service pressure, but there is still a risk of high availability. When a KTS service node under the VPC in the same region fails due to a large number of requests, other nodes will be under higher load, which may lead to regional service avalanche downtime. Therefore, there is room for improvement. Summary of the invention

[0004] In view of the shortcomings of the prior art described above, the purpose of the present invention is to provide a system, method and medium for distributing automobile digital key service requests, so as to solve the technical problem in the prior art that digital key services have the risk of regional service avalanche downtime.

[0005] To achieve the above objectives and other related objectives, the present invention provides a system for allocating automobile digital key service requests, comprising:

[0006] The cloud server is used to receive the digital key service request sent by the client;

[0007] A plurality of digital key service private clouds are respectively located in different regions, and a plurality of service nodes are deployed under the digital key service private cloud, and the service nodes are used to execute digital key services;

[0008] A global traffic manager, communicatively connected between the cloud server and the plurality of digital key service private clouds;

[0009] Wherein, the global traffic manager is used to regularly check the health of each of the digital key service private clouds;

[0010] The global traffic manager is further used to perform domain name resolution processing on the digital key service request to obtain address information of the client;

[0011] The global traffic manager is further used to obtain a digital key service private cloud matching the client according to the address information and the health of the digital key service private cloud, and indicate it as a target private cloud;

[0012] The global traffic manager is also used to send the IP address of a service node in the target private cloud to the client according to the load balancing strategy.

[0013] In one embodiment of the present invention, the global traffic manager detects the response of the service node, and when the service node responds normally, marks its health as available; when the service node does not respond or the response times out, marks its health as unavailable.

[0014] In one embodiment of the present invention, the global traffic manager is also used to mark the status of the digital key service private cloud as a normal state when the number of unavailable service nodes under the digital key service private cloud is less than a preset threshold, and to mark the status of the digital key service private cloud as a fault state when the number of unavailable service nodes under the digital key service private cloud is greater than or equal to a preset threshold.

[0015] In one embodiment of the present invention, the global traffic manager is also used to change the digital key service private cloud to a normal state when the number of unavailable service nodes in the digital key service private cloud in a faulty state recovers to less than a preset threshold.

[0016] In one embodiment of the present invention, the global traffic manager is further used to set the digital key service private cloud that is closest to the client and in normal state as the target private cloud of the client based on the address information.

[0017] In one embodiment of the present invention, the global traffic manager is also used to obtain the current weight value of each of the service nodes in the target private cloud, and send the IP address of a service node whose current weight value is lower than a preset weight ratio to the client.

[0018] In one embodiment of the present invention, the global traffic manager is further configured to select a service node according to a polling rule, and send the IP address of the service node to the client.

[0019] In one embodiment of the present invention, the cloud server receives the digital key service request by accessing the domain name.

[0020] In one embodiment of the present invention, the distribution system also includes a shared service private cloud, which is peer-to-peer connected to multiple digital key service private clouds and is communicatively connected to the in-vehicle service platform. The shared private cloud is used to provide vehicle data of the in-vehicle service platform to the digital key service cloud to execute the corresponding digital key service.

[0021] The present invention also provides a method for allocating a vehicle digital key service request, comprising:

[0022] Receive the digital key service request sent by the client;

[0023] Regularly check the health of each of the Digital Key Service Private Clouds;

[0024] Performing domain name resolution processing on the digital key service request to obtain address information of the client;

[0025] According to the address information and the health of the digital key service private cloud, a digital key service private cloud matching the client is obtained and indicated as a target private cloud;

[0026] According to the load balancing strategy, the IP address of a service node in the target private cloud is sent to the client.

[0027] The present invention also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the method for allocating automobile digital key service requests as described above are implemented.

[0028] As described above, the system, method and medium for distributing automobile digital key service requests of the present invention have the following beneficial effects: the present invention constantly monitors the survival status and resource usage of service nodes, and ensures the normal operation of the service based on a preset load balancing strategy, thereby ensuring the normal operation of the digital key service and enhancing the user's experience and sense of identity in using digital keys. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 A schematic diagram of the structure of a system for distributing automobile digital key service requests provided by an embodiment of the present invention;

[0030] Figure 2 A flowchart of a method for allocating a vehicle digital key service request provided by an embodiment of the present invention.

[0031] In the figure:

[0032] 100. Cloud server;

[0033] 200, global traffic manager;

[0034] 300, regional cloud; 310, digital key service private cloud; 311, digital key service node; 320, shared service private cloud; 321, shared service node;

[0035] 400, Client. DETAILED DESCRIPTION

[0036] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0037] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0038] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0039] First of all, it should be noted that TSP (Telematics Service Provider) is a business model that provides connection, management and application services for vehicle-related data. Telematics TSP services usually include installing sensors, communication equipment and software systems in the vehicle to monitor, collect and transmit vehicle data in real time, and use this data for various purposes, such as vehicle tracking, remote diagnosis, vehicle safety, driving analysis, navigation and entertainment. 3C Digital Key Service is a car key solution based on the Telematics TSP platform. It combines modern communication technology and security mechanisms to provide clients with a more convenient and secure vehicle access experience.

[0040] VPC (Virtual Private Cloud) is a cloud computing service that allows users to build their own private network environment on top of the cloud provider's infrastructure. In VPC, users can create and manage their own virtual networks, including subnet division, IP address segments, routing tables, security groups and other configurations, thereby achieving a high degree of control and isolation of network resources. VPC Peering Connection is a technology that allows a direct network connection to be established between two virtual private clouds (VPCs). This connection allows resources in different VPCs to communicate with each other as if they were in the same VPC, without having to be transmitted over the Internet or public networks.

[0041] The present invention provides a distribution system, distribution method and medium for automobile digital key service requests, which relates to the field of vehicle network technology and can be specifically used to solve the problem that a single service node crashes, causing a sudden increase in pressure on other service nodes, and then causing a regional service node avalanche crash, making the automobile digital key service unusable and affecting the customer experience. The present invention adopts the method of adding a remote network and performing resource management on the service nodes under multiple VPCs through global traffic management, and ensures the normal operation of the service based on a preset load balancing strategy. The following is a detailed description through specific embodiments.

[0042] See also Figure 1 In one embodiment of the present invention, a distribution system for automobile digital key service requests may include a cloud server 100, a global traffic manager 200, and multiple digital key service private clouds 310. Among them, the global traffic manager 200 is communicated with the cloud server 100. Multiple digital key service private clouds 310 can be communicated with the global traffic manager 200 respectively. Multiple service nodes are deployed under the digital key service private cloud 310, and the service nodes can be used to perform digital key services. The global traffic manager 200 can be used to create one or more address pools (Pool). Multiple address pools can be used to store the IP (Internet Protocol) addresses of all service nodes under multiple digital key service private clouds 310 respectively.

[0043] In this embodiment, the cloud server 100 can be used to receive a digital key service request sent by the client 400. The global traffic manager 200 can be used to periodically check the health of all service nodes in each digital key service private cloud 310. The global traffic manager 200 can also be used to first perform domain name resolution processing on the digital key service request sent by the client 400 to obtain the address information of the client 400; then, based on the address information and the health of each digital key service private cloud 310, obtain a private cloud that matches the client 400, which can be represented as a target private cloud; finally, according to the load balancing strategy, send the IP address of a service node in the target private cloud to the client 400. The service node can be used to perform digital key services.

[0044] See also Figure 1 In one embodiment of the present invention, multiple digital key service private clouds 310 are respectively arranged in multiple regional clouds 300. Multiple regional clouds 300 are deployed in multiple different geographical regions. Each regional cloud 300 is responsible for providing low-latency, high-performance cloud services to customers in a specific geographical area. For example, regional clouds 300 serving users in my country can be respectively set up in regional geographical center locations such as Beijing, Hangzhou, and Guangzhou. A variety of service nodes are deployed under the regional cloud 300 to improve the availability and response speed of the service. Multiple regional clouds 300 are independent of each other, that is, a failure in a regional cloud 300 will not affect other regional clouds 300. Each regional cloud 300 contains one or more data centers, in which various cloud services and resources are deployed. Multiple private clouds can be constructed in the regional cloud 300 to form a Cloud Enterprise Network (CEN).

[0045] See also Figure 1 In one embodiment of the present invention, the distribution system also includes a shared service private cloud 320. In this embodiment, the shared service private cloud 320 is respectively connected to multiple digital key service private clouds 310 in a peer-to-peer manner. In addition, the shared service private cloud 320 can also be connected to the communication of the vehicle-mounted service platform. The shared private cloud 320 can provide the vehicle data of the vehicle-mounted service platform to the digital key service cloud 310 to execute the corresponding digital key service. The present invention enables peer-to-peer connections between private clouds in different regions through a VPC routing forwarder, and can connect the digital key services of remote private clouds and the authentication, security and other microservices under the Internet of Vehicles TSP (Telematics Service Provider, automotive remote service provider) cloud platform, thereby ensuring the high availability of digital key services. In the face of an avalanche of downtime in the digital key service in the same area, the normal operation of the service can be guaranteed, which improves the user experience.

[0046] See also Figure 1 In one embodiment of the present invention, a plurality of digital key service nodes 311, namely KTS nodes, are deployed under the digital key service private cloud 310. The digital key service node 311 can be used to process the request of the client 400 and provide the automobile digital key service. A plurality of shared service nodes 321 are deployed under the shared service private cloud 320. The shared service node 321 can be used to provide the vehicle data required for services such as vehicle tracking, remote diagnosis, vehicle safety, driving analysis, navigation and entertainment according to the request of the client 400.

[0047] In one embodiment of the present invention, the global traffic manager 200 may create an address pool for each geographic area, which may store the IP addresses of all service nodes in the corresponding digital key service private cloud 310, that is, one address pool represents a group of nodes that provide the same application service. In this embodiment, the global traffic manager 200 is also used to associate multiple address pools with a unified access domain name. The cloud server 100 can receive the digital key service request sent by the client 400 through the access domain name. It should be noted that the request sent by the client 400 is to access this access domain name, rather than directly accessing a specific IP address.

[0048] In one embodiment of the present invention, the global traffic manager 200 can be used to check the health of each service node according to a preset health check rule. The health check rule may include: a health check cycle (e.g., a check every 10 seconds), a check timeout (e.g., no response within 1 second is considered a failure), and a check failure threshold (e.g., 5 consecutive check failures are considered unavailable). In this embodiment, according to the preset health check rules, regular health checks are performed on the IP addresses in each address pool, that is, all service nodes, and when a certain IP address is unavailable, the IP address is automatically isolated. The global traffic manager 200 can verify whether the service node is operating normally through a ping command or an HTTP / HTTPS request. If it is detected that the service node corresponding to a certain IP address does not respond or the response times out, the service node is marked as unavailable. If the IP address is successfully checked several times in a row, its health is marked as available. When a certain IP address is marked as unavailable, the global traffic manager 200 will no longer forward requests to it until the address becomes available again.

[0049] In one embodiment of the present invention, when the number of unavailable service nodes under a digital key service private cloud 310 is less than a preset threshold, the global traffic manager 200 may mark the status of the digital key service private cloud 310 as normal. The preset threshold may be set to, for example, half of the number of all service nodes. When the number of unavailable service nodes under the digital key service private cloud 310 is greater than or equal to the preset threshold, the global traffic manager 200 may mark the status of the digital key service private cloud as a faulty state. Furthermore, after the digital key service private cloud 310 in a faulty state is restored, that is, after the number of unavailable service nodes under it is restored to less than the preset threshold, the global traffic manager 200 may change the digital key service private cloud to a normal state.

[0050] In one embodiment of the present invention, the global traffic manager 200 performs domain name resolution processing on the digital key service request sent by the client 400 to obtain the address information of the client 400. Specifically, the global traffic manager 200 can obtain the IP address of the client 400 and determine its approximate geographical location based on the IP address of the client 400. The request of the client 400 is then directed to the service node closest to the geographical location of the client 400 to reduce network latency and improve user experience. In this embodiment, the global traffic manager 200 can set a digital key service private cloud 310 that is closest to the client 400 and in a normal state as the target private cloud of the client 400.

[0051] In one embodiment of the present invention, the global traffic manager 200 determines which service node in the target private cloud to assign the service request to according to a preset load balancing strategy, that is, to which IP address in the address pool the user's request is routed. In this embodiment, the global traffic manager 200 uses a weighted load balancing strategy or a polling strategy to assign the service request to a suitable service node, that is, to send the IP address of the service node to the client 400. Among them, the weighted load balancing strategy requires the global traffic manager 200 to assign a weight value to each service node according to the processing capacity of the service node. Service nodes with higher weights will receive more requests, while service nodes with lower weights will receive fewer requests. For example, two digital key service nodes 311 are deployed under the digital key service private cloud 310, and their weights are 8 and 2 respectively. Among them, the first service node will accept 80% of the requests, and the second service node will accept 20% of the requests. When the cloud server 100 receives a service request, the global traffic manager 200 will distribute the request to a service node whose current weight value is lower than the preset weight ratio according to the current weight value of each IP address. The weighted load balancing strategy of the present invention can better utilize the capabilities of high-performance service nodes and perform dynamic adjustments according to the actual load conditions of the service nodes.

[0052] In this embodiment, the polling strategy requires the global traffic manager 200 to distribute requests to different service nodes in sequence, in turn, without the need for performance differences between service nodes. When the cloud server 100 receives a service request, the global traffic manager 200 sends the request to the service node corresponding to each IP address in the address pool in sequence. For example, three digital key service nodes 311 are deployed under the digital key service private cloud 310. The first request will be sent to the first service node, the second request will be sent to the second service node, and so on, until all service nodes receive the request and then start the cycle from the beginning. The polling strategy of the present invention has the advantages of simple implementation, easy understanding and deployment, and is suitable for load distribution when the server performance is similar.

[0053] See also Figure 2 The present invention also provides a method for allocating a digital car key service request, which can be applied to the system for allocating a digital car key service request described in any of the above embodiments. In one embodiment of the present invention, the allocation method may include the following steps:

[0054] Step S100: receiving a digital key service request sent by a client;

[0055] Step S200: Regularly check the health of each digital key service private cloud;

[0056] Step S300: performing domain name resolution processing on the digital key service request to obtain the address information of the client;

[0057] Step S400: According to the address information and the health of the digital key service private cloud, a digital key service private cloud matching the client is obtained and indicated as a target private cloud;

[0058] Step S500: According to the load balancing strategy, the IP address of a service node in the target private cloud is sent to the client.

[0059] In one embodiment of the present invention, when step S100 is executed, a digital key service request sent by a client is received. Specifically, the cloud server 100 receives the digital key service request sent by the client 400 through the access domain name. The digital key service request includes the IP address of the client 400.

[0060] In one embodiment of the present invention, when step S200 is executed, the health of each digital key service private cloud is checked regularly. Specifically, the health of each service node is checked according to the preset health check rules. The health check rules may include: the health check cycle (for example, check once every 10 seconds), the check timeout time (for example, if there is no response within 1 second, it is considered to be a failure), and the threshold for check failure (for example, if there are 5 consecutive check failures, it is considered unavailable). In this embodiment, first, according to the preset health check rules, regular health checks are performed on the IP addresses in each address pool, that is, all service nodes, and when a certain IP address is unavailable, the IP address is automatically isolated. The global traffic manager 200 can verify whether the service node is operating normally through a ping command or an HTTP / HTTPS request. If it is detected that the service node corresponding to a certain IP address does not respond or the response times out, the service node is marked as unavailable. If the IP address is checked successfully for several consecutive times, its health is marked as available. When an IP address is marked as unavailable, the global traffic manager 200 will no longer forward requests to it until the address becomes available again. Then, it is determined whether the number of unavailable service nodes in the digital key service private cloud has reached a preset threshold to determine the health of the digital key service private cloud.

[0061] In one embodiment of the present invention, when step S300 is executed, the domain name resolution process is performed on the digital key service request to obtain the address information of the client. Specifically, the digital key service request sent by the client 400 includes the IP address of the client 400. Therefore, the IP address of the client 400 can be obtained through the global traffic manager 200, and its approximate geographical location can be determined based on the IP address of the client 400.

[0062] In one embodiment of the present invention, when executing step S400, a digital key service private cloud matching the client is obtained based on the address information and the health of the digital key service private cloud, and is represented as the target private cloud. Specifically, the request of the client 400 is directed to the service node closest to the geographical location of the client 400 to reduce network delay and improve user experience.

[0063] In this embodiment, when selecting a target private cloud, the health of the digital key service private cloud 310 must also be considered. When the number of unavailable service nodes under a digital key service private cloud 310 is less than a preset threshold, the global traffic manager 200 can mark the state of the digital key service private cloud 310 as normal. The preset threshold can be set to, for example, half of the number of all service nodes. When the number of unavailable service nodes under the digital key service private cloud 310 is greater than or equal to the preset threshold, the global traffic manager 200 can mark the state of the digital key service private cloud as a fault state. Further, after the digital key service private cloud 310 in the faulty state is restored, that is, after the number of unavailable service nodes under it is restored to less than the preset threshold, the global traffic manager 200 can change the digital key service private cloud to a normal state. Therefore, the global traffic manager 200 can set a digital key service private cloud 310 that is closest to the client 400 and is in a normal state as the target private cloud of the client 400.

[0064] In one embodiment of the present invention, when step S500 is executed, the IP address of a service node in the target private cloud is sent to the client according to the load balancing strategy. Specifically, the global traffic manager 200 determines which service node in the target private cloud to assign the service request to according to the preset load balancing strategy, that is, to which IP address in the address pool the user's request is routed. In this embodiment, the global traffic manager 200 uses a weighted load balancing strategy or a polling strategy to assign the service request to a suitable service node, that is, to send the IP address of the service node to the client 400. Among them, the weighted load balancing strategy requires the global traffic manager 200 to assign a weight value to each service node according to the processing capacity of the service node. Service nodes with higher weights will receive more requests, while service nodes with lower weights will receive fewer requests. For example, two digital key service nodes 311 are deployed under the digital key service private cloud 310, and their weights are 8 and 2 respectively. Among them, the first service node will accept 80% of the requests, and the second service node will accept 20% of the requests. When the cloud server 100 receives a service request, the global traffic manager 200 distributes the request to a service node whose current weight value is lower than the preset weight ratio according to the current weight value of each IP address. The weight load balancing strategy of the present invention can better utilize the capabilities of high-performance service nodes and dynamically adjust according to the actual load conditions of the service nodes.

[0065] In this embodiment, the polling strategy requires the global traffic manager 200 to distribute requests to different service nodes in sequence, in turn, without the need for performance differences between service nodes. When the cloud server 100 receives a service request, the global traffic manager 200 sends the request to the service node corresponding to each IP address in the address pool in sequence. For example, three digital key service nodes 311 are deployed under the digital key service private cloud 310. The first request will be sent to the first service node, the second request will be sent to the second service node, and so on, until all service nodes receive the request and then start the cycle from the beginning. The polling strategy of the present invention has the advantages of simple implementation, easy understanding and deployment, and is suitable for load distribution when the server performance is similar.

[0066] The present invention also provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the following steps are implemented:

[0067] Receive the digital key service request sent by the client;

[0068] Regularly check the health of each Digital Key Service private cloud;

[0069] Perform domain name resolution on digital key service requests to obtain client address information;

[0070] According to the address information and the health of the digital key service private cloud, a digital key service private cloud matching the client is obtained and indicated as a target private cloud;

[0071] According to the load balancing strategy, the IP address of a service node in the target private cloud is sent to the client.

[0072] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can refer to the relevant description of the system for distributing automobile digital key service requests in the aforementioned method embodiment. In order to avoid repetition, they will not be described one by one here.

[0073] In summary, the present invention discloses a distribution system, distribution method and medium for automobile digital key service requests, which can reduce the risk of regional service avalanche downtime of digital key services. The present invention adopts a cloud service keep-alive mechanism under a foreign network, by adding a foreign private cloud, and using global traffic management to manage resources for service nodes of multiple service requests, constantly monitoring the survival status and resource usage of service nodes, and ensuring the normal operation of services based on a preset load balancing strategy, thereby ensuring the normal operation of digital key services and enhancing the user's experience and sense of identity when using 3c digital keys. The present invention also uses a VPC routing forwarder peer-to-peer connection to interconnect private clouds and private clouds for services under different regional clouds, ensuring that network interconnection between services is available. Therefore, the present invention effectively overcomes the various shortcomings in the prior art and has a high industrial utilization value.

[0074] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. A system for distributing automobile digital key service requests, characterized in that: include: The cloud server is used to receive the digital key service request sent by the client; A plurality of digital key service private clouds are respectively located in different regions, and a plurality of service nodes are deployed under the digital key service private cloud, and the service nodes are used to execute digital key services; A global traffic manager, communicatively connected between the cloud server and the plurality of digital key service private clouds; Wherein, the global traffic manager is used to regularly check the health of each of the digital key service private clouds; The global traffic manager is further used to perform domain name resolution processing on the digital key service request to obtain address information of the client; The global traffic manager is further used to obtain a digital key service private cloud matching the client according to the address information and the health of the digital key service private cloud, and indicate it as a target private cloud; The global traffic manager is also used to send the IP address of a service node in the target private cloud to the client according to the load balancing strategy.

2. The system for distributing automobile digital key service requests according to claim 1, characterized in that: The global traffic manager detects the response of the service node, and when the service node responds normally, marks its health as available; when the service node does not respond or the response times out, marks its health as unavailable.

3. The system for distributing automobile digital key service requests according to claim 2, characterized in that: The global traffic manager is also used to mark the status of the digital key service private cloud as a normal state when the number of unavailable service nodes under the digital key service private cloud is less than a preset threshold, and to mark the status of the digital key service private cloud as a fault state when the number of unavailable service nodes under the digital key service private cloud is greater than or equal to the preset threshold.

4. The system for distributing automobile digital key service requests according to claim 3, characterized in that: The global traffic manager is also used to change the digital key service private cloud to a normal state when the number of unavailable service nodes in the faulty digital key service private cloud recovers to less than a preset threshold.

5. The system for distributing automobile digital key service requests according to claim 3, characterized in that: The global traffic manager is also used to set the digital key service private cloud that is closest to the client and in normal status as the target private cloud of the client according to the address information.

6. The system for distributing automobile digital key service requests according to claim 1, characterized in that: The global traffic manager is also used to obtain a current weight value of each of the service nodes in the target private cloud, and send an IP address of a service node whose current weight value is lower than a preset weight ratio to the client.

7. The system for distributing automobile digital key service requests according to claim 1, characterized in that: The global traffic manager is further configured to select a service node according to a polling rule, and send the IP address of the service node to the client.

8. The system for distributing automobile digital key service requests according to claim 1, characterized in that: The cloud server receives the digital key service request by accessing the domain name.

9. The system for distributing automobile digital key service requests according to claim 1, characterized in that: The distribution system also includes a shared service private cloud, which is peer-to-peer connected to multiple digital key service private clouds and communicates with the in-vehicle service platform. The shared private cloud is used to provide vehicle data of the in-vehicle service platform to the digital key service cloud to execute the corresponding digital key service.

10. A method for allocating a vehicle digital key service request, characterized in that: include: Receive the digital key service request sent by the client; Regularly check the health of each of the Digital Key Service Private Clouds; Performing domain name resolution processing on the digital key service request to obtain address information of the client; According to the address information and the health of the digital key service private cloud, a digital key service private cloud matching the client is obtained and indicated as a target private cloud; According to the load balancing strategy, the IP address of a service node in the target private cloud is sent to the client.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for allocating a vehicle digital key service request as claimed in claim 10 are implemented.

Images