Data center address switching method, device and equipment of vehicle

By sending candidate request and response messages in the vehicle, ensuring the connectivity of the domain controller and then switching the data center address, the domain controller synchronization problem in vehicle data center address switching is solved, and efficient and accurate data center address switching is achieved.

CN119052209APending Publication Date: 2024-11-29BEIJING CO WHEELS TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310622764.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-29
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

During the process of vehicle data center address switching, how to ensure that all domain controllers complete data center address switching synchronously, avoid data transmission errors, and achieve high-efficiency and high-accuracy data center address switching.

Method used

After receiving the instruction information sent by the cloud server, a candidate request for testing connectivity is sent to the multiple domain controllers designated in the vehicle, and a first response message from the domain controller is received and responds to the domain controller. After determining that the domain controller has connectivity, the domain controller has connection , switch the current data center address to the target data center address, and generate a target request based on the target data center address and the domain name of the domain controller, instructing the domain controller to switch the data center address.

Benefits of technology

Ensure that all domain controllers in the vehicle complete data center address switching synchronously, avoid data transmission errors, and realize data center address switching with high efficiency and high accuracy among devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119052209A_ABST
    Figure CN119052209A_ABST
Patent Text Reader

Abstract

The invention provides a data center address switching method, device and equipment of a vehicle, and relates to the technical field of data processing. The method comprises the specific steps that after indication information sent by a cloud server is received, candidate requests used for testing connectivity are sent to multiple domain controllers designated in a vehicle; for any one of the plurality of domain controllers, receiving a first response message sent by the domain controller; switching the current data center address to a target data center address in response to determining that the plurality of domain controllers have connectivity according to the received first response message; and generating a target request according to the target data center address and the domain name of the domain controller, and sending the target request to the domain controller. According to the embodiment of the invention, high-efficiency and high-accuracy data center address switching between equipment can be realized, all domain controllers in a vehicle are ensured to synchronously complete data center address switching, and data transmission errors are avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, and in particular to a method, device and equipment for switching a data center address of a vehicle. Background Art

[0002] The data center accessed by the vehicle refers to a self-contained set that can complete all business operations. This set contains all services required for all businesses and data assigned to this data center. The data center is a global collaborative network of specific devices used to transmit, accelerate, display, calculate, and store data information on the network infrastructure. In related technologies, when the vehicle's data center is switched, the vehicle data in the data center needs to be migrated first. After the data migration is completed in the data center, the vehicle's data center address needs to be switched to ensure subsequent communication transmission between vehicles, cloud servers, and gateways. At this time, it is necessary to ensure that all domain controllers in the vehicle complete the data center address switching synchronously, otherwise it may cause data transmission errors, making it difficult to achieve efficient and accurate data center address switching between devices.

[0003] Therefore, how to ensure that all domain controllers in the vehicle complete data center address switching synchronously, avoid data transmission errors, and achieve high-efficiency and high-accuracy data center address switching between devices has become one of the important research directions. Summary of the invention

[0004] The present disclosure provides a method, device and apparatus for switching a data center address of a vehicle. The technical solution of the present disclosure is as follows:

[0005] According to a first aspect of an embodiment of the present disclosure, a method for switching a data center address of a vehicle is provided, comprising:

[0006] After receiving the indication information sent by the cloud server, a candidate request for testing connectivity is sent to multiple domain controllers specified in the vehicle, where the indication information includes the address of the target data center to be switched;

[0007] For any domain controller among the multiple domain controllers, receiving a first response message sent by the domain controller, where the first response message is generated by the domain controller according to the received candidate request;

[0008] In response to determining that the plurality of domain controllers have connectivity according to the received first response message, switching the current data center address to the target data center address;

[0009] A target request is generated according to the target data center address and the domain name of the domain controller, and the target request is sent to the domain controller. The target request is used to instruct the domain controller to switch its own data center address to the target data center address.

[0010] According to a second aspect of an embodiment of the present disclosure, a data center address switching device for a vehicle is provided, comprising:

[0011] A transceiver module, configured to send candidate requests for testing connectivity to multiple domain controllers specified in the vehicle after receiving the indication information sent by the cloud server, wherein the indication information includes the address of the target data center to be switched;

[0012] A receiving module, configured to receive a first response message sent by any domain controller among the multiple domain controllers, where the first response message is generated by the domain controller according to the received candidate request;

[0013] a switching module, configured to switch a current data center address to a target data center address in response to determining that the multiple domain controllers have connectivity according to the received first response message;

[0014] The sending module is used to generate a target request according to the target data center address and the domain name of the domain controller, and send the target request to the domain controller, wherein the target request is used to instruct the domain controller to switch its own data center address to the target data center address.

[0015] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, including:

[0016] processor;

[0017] a memory for storing processor-executable instructions;

[0018] Wherein, the processor is configured to execute instructions to implement a data center address switching method for a vehicle as described in any one of the first aspects above.

[0019] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute a data center address switching method for a vehicle as described in any one of the first aspects above.

[0020] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements a data center address switching method for a vehicle according to any one of the above-mentioned first aspects.

[0021] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0022] In an embodiment of the present application, a candidate request for testing connectivity is sent to multiple domain controllers specified in the vehicle; for any domain controller among the multiple domain controllers, a first response message sent by the domain controller is received, and in response to determining that the multiple domain controllers have connectivity based on the received first response message, the current data center address is switched to the target data center address, which can ensure that all domain controllers in the vehicle complete the data center address switching synchronously to avoid data transmission errors, generate a target request based on the target data center address and the domain name of the domain controller, and send the target request to the domain controller, which can achieve efficient and high-accuracy data center address switching between devices.

[0023] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0025] Figure 1 is a flow chart showing a method for switching a data center address of a vehicle according to an exemplary embodiment;

[0026] Figure 2 is a flow chart showing a method for switching a data center address of a vehicle according to an exemplary embodiment;

[0027] Figure 3 is a flow chart showing a method for switching a data center address of a vehicle according to an exemplary embodiment;

[0028] Figure 4 is a schematic diagram showing a method for switching a data center address of a vehicle according to an exemplary embodiment;

[0029] Figure 5 is a block diagram of a data center address switching device for a vehicle according to an exemplary embodiment;

[0030] Figure 6 is a block diagram of a device according to an exemplary embodiment;

[0031] Figure 7 It is a block diagram of a device according to an exemplary embodiment. DETAILED DESCRIPTION

[0032] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0034] It should be noted that the user information involved in this disclosure (including but not limited to user device information, user personal information, etc.) is all information authorized by the user or fully authorized by all parties.

[0035] Figure 1 is a flow chart showing a method for switching a data center address of a vehicle according to an exemplary embodiment. Figure 1 As shown, the method includes the following steps, which can be specifically executed by a domain controller with a vehicle-side routing service.

[0036] Step 101, after receiving the indication information sent by the cloud server, a candidate request for testing connectivity is sent to multiple domain controllers specified in the vehicle, and the indication information includes the address of the target data center to be switched.

[0037] It should be noted that the vehicle in the embodiment of the present disclosure is a multi-domain controller vehicle series. The domain controllers of the vehicle include the in-vehicle entertainment HU domain controller, the vehicle control XCU domain controller, and the intelligent driving FSD domain controller. Each domain controller is responsible for different functions, and each domain controller has a vehicle signal specification (VSS) service and a vehicle proxy service for sending / receiving interactive information between domain controllers. Among them, the HU domain controller is mainly responsible for the in-vehicle entertainment system; the XCU domain controller is responsible for the vehicle control system; and the FSD domain controller is mainly responsible for intelligent driving related functions. In some embodiments, the HU domain controller has two domain controller components according to different chips, namely the first HU domain controller and the second HU domain controller, and the FSD domain controller has two domain controller components according to different chips, namely the first FSD domain controller and the second FSD domain controller.

[0038] Optionally, the cloud server exchanges information with the vehicle's domain controller through the vehicle-side routing service. In an embodiment of the present application, the domain controller with the vehicle-side routing service is taken as the first HU domain controller as an example. The multiple domain controllers specified in the vehicle are other domain controllers that do not have the vehicle-side routing service, namely the second HU domain controller, the XCU domain controller, the first FSD domain controller and the second FSD domain controller.

[0039] In an embodiment of the present application, the cloud server migrates the data of the data center. For example, the vehicle data can be migrated from the initial data center to the target data center. If the data migration is completed, the address of the target data center is determined, and an indication message is generated and sent to the domain controller with the vehicle-side routing service, that is, the first HU domain controller. After receiving the indication message, the first HU domain controller needs to switch the data center address of the vehicle's domain controller. However, in order to avoid data transmission errors caused by inter-domain asynchrony, in an embodiment of the present application, before executing the data center address switching, it is necessary to detect whether there is connectivity between the domain controllers of the vehicle. Optionally, in an embodiment of the present application, multiple domain controllers specified in the vehicle send candidate requests for testing connectivity. That is, before executing the data center address switching, the first HU domain controller sets a key for testing connectivity based on the vehicle-side routing service.

[0040] Alternatively, the candidate request may be requestkey=Vehicle.LiMesh.IcnRouter.AddressInfoTest.

[0041] Step 102: For any domain controller among the multiple domain controllers, a first response message sent by the domain controller is received, where the first response message is generated by the domain controller according to the received candidate request.

[0042] Other domain controllers except the first HU domain controller listen to this key and give a receipt immediately after receiving it, which is the first response message. Optionally, the first response message can be ${requestkey}-${domain}-ack, where domain is the domain name of the domain controller sending the first response message, such as xcu represents the XCU domain controller, hu-r represents the second HU domain controller, fsd-a represents the first FSD domain controller, fsd-b represents the second FSD domain controller, and ack is a confirmation character.

[0043] Step 103: In response to determining that the multiple domain controllers have connectivity according to the received first response message, the current data center address is switched to the target data center address.

[0044] After receiving the first response messages respectively sent by the second HU domain controller, the XCU domain controller, the first FSD domain controller and the second FSD domain controller, the first HU domain controller determines that the multiple domain controllers have connectivity and switches its own data center address to the target data center address.

[0045] Step 104: Generate a target request according to the target data center address and the domain name of the domain controller, and send the target request to the domain controller. The target request is used to instruct the domain controller to switch its own data center address to the target data center address.

[0046] After the first HU domain controller switches the data center address, it is also necessary to instruct the second HU domain controller, the XCU domain controller, the first FSD domain controller, and the second FSD domain controller to complete the switching of their respective data center addresses. Optionally, in an embodiment of the present application, for other domain controllers except the first HU domain controller, that is, any one of the aforementioned multiple domain controllers specified, a target request is generated according to the domain name of the domain controller and the target data center address, and sent to the domain controller. Taking the XCU domain controller as an example, a target request corresponding to the XCU domain controller is generated according to the domain name of the XCU domain controller and the address of the target data center, and the target request is sent to the XCU domain controller to instruct the XCU domain controller to switch the data center address according to the target data center address. For the data center address switching process of the second HU domain controller, the first FSD domain controller, and the second FSD domain controller, refer to the switching process of the XCU domain controller mentioned above, which will not be repeated here.

[0047] In an embodiment of the present application, a candidate request for testing connectivity is sent to multiple domain controllers specified in the vehicle; for any domain controller among the multiple domain controllers, a first response message sent by the domain controller is received, and in response to determining that the multiple domain controllers have connectivity based on the received first response message, the current data center address is switched to the target data center address, which can ensure that all domain controllers in the vehicle complete the data center address switching synchronously to avoid data transmission errors, generate a target request based on the target data center address and the domain name of the domain controller, and send the target request to the domain controller, which can achieve efficient and high-accuracy data center address switching between devices.

[0048] Figure 2 is a flow chart showing a method for switching a data center address of a vehicle according to an exemplary embodiment. Figure 2 As shown, the method includes the following steps, which can be specifically executed by a domain controller with a vehicle-side routing service.

[0049] Step 201, after receiving the indication information sent by the cloud server, a candidate request for testing connectivity is sent to multiple domain controllers specified in the vehicle, and the indication information includes the address of the target data center to be switched.

[0050] Step 202: For any domain controller among the multiple domain controllers, a first response message sent by the domain controller is received, where the first response message is generated by the domain controller according to the received candidate request.

[0051] The contents of step S201 to step S202 can be found in the introduction of the above embodiment and will not be described again here.

[0052] Step 203, obtaining a first number of domain controllers that the vehicle has.

[0053] In the embodiment of the present application, the domain controllers on the vehicle include a first HU domain controller, a second HU domain controller, an XCU domain controller, a first FSD domain controller, and a second FSD domain controller. The first number of domain controllers in the vehicle is 5.

[0054] Step 204: Record the second number of received first response messages.

[0055] In an embodiment of the present application, the first HU domain controller is a domain controller with a vehicle-side routing service. Therefore, after the first HU domain controller sends candidate requests to the second HU domain controller, the XCU domain controller, the first FSD domain controller and the second FSD domain controller respectively, it is necessary to listen to the second number of first response messages received.

[0056] Step 205: In response to the difference between the first number and the second number being a preset number threshold, it is determined that the plurality of domain controllers have connectivity.

[0057] Since the first HU domain controller does not need to send a response message to itself, after receiving the first response messages sent by the second HU domain controller, the XCU domain controller, the first FSD domain controller, and the second FSD domain controller, it is determined that the multiple domain controllers have connectivity. That is, in the embodiment of the present application, the preset number threshold is 1, and when the second number is 4, it is determined that the multiple domain controllers have connectivity.

[0058] Step 206, switching the current data center address to the target data center address.

[0059] The first HU domain controller switches its own data center address to the target data center address.

[0060] Step 207: Generate a first request according to the target cloud proxy service address and the domain name of the domain controller, and send the first request to the domain controller. The first request is used to instruct the domain controller to switch its own cloud proxy service address to the target cloud proxy service address.

[0061] It should be noted that, in the embodiment of the present application, the target data center address includes a target cloud proxy service address and a target gateway service address, and the target request includes a first request and a second request.

[0062] Taking the XCU domain controller as an example, a first request is generated according to the target cloud proxy service address and the domain name of the XCU domain controller, and the first request is sent to the XCU domain controller, wherein the first request sent to the XCU domain controller can be expressed as Vehicle.LiMesh.CloudProxy.AddressInfoSHS-xcu.

[0063] Taking the second HU domain controller as an example, a first request is generated according to the target cloud proxy service address and the domain name of the second HU domain controller, and the first request is sent to the second HU domain controller, wherein the first request sent to the second HU domain controller can be expressed as Vehicle.LiMesh.CloudProxy.AddressInfoSHS-hu-r.

[0064] Taking the first FSD domain controller as an example, a first request is generated according to the target cloud proxy service address and the domain name of the first FSD domain controller, and the first request is sent to the first FSD domain controller, wherein the first request sent to the first FSD domain controller can be expressed as Vehicle.LiMesh.CloudProxy.AddressInfoSHS-fsd-a.

[0065] Taking the second FSD domain controller as an example, a first request is generated according to the target cloud proxy service address and the domain name of the second FSD domain controller, and the first request is sent to the second FSD domain controller, wherein the first request sent to the second FSD domain controller can be expressed as Vehicle.LiMesh.CloudProxy.AddressInfoSHS-fsd-b.

[0066] Step 208: Generate a second request according to the target gateway service address and the domain name of the domain controller, and send the second request to the domain controller. The second request is used to instruct the domain controller to switch its own gateway service address to the target gateway service address.

[0067] Taking the XCU domain controller as an example, a second request is generated according to the target gateway service address and the domain name of the XCU domain controller, and the second request is sent to the XCU domain controller, wherein the second request sent to the XCU domain controller can be expressed as Vehicle.LiMesh.IcnRouter.ApiGateway.AddressInfo-xcu.

[0068] Taking the second HU domain controller as an example, a second request is generated according to the target gateway service address and the domain name of the second HU domain controller, and the second request is sent to the second HU domain controller, wherein the second request sent to the second HU domain controller can be expressed as Vehicle.LiMesh.IcnRouter.ApiGateway.AddressInfo-hu-r.

[0069] Taking the first FSD domain controller as an example, a second request is generated according to the target gateway service address and the domain name of the first FSD domain controller, and the second request is sent to the first FSD domain controller, wherein the second request sent to the first FSD domain controller can be expressed as Vehicle.LiMesh.IcnRouter.ApiGateway.AddressInfo-fsd-a.

[0070] Taking the second FSD domain controller as an example, a second request is generated according to the target gateway service address and the domain name of the second FSD domain controller, and the second request is sent to the second FSD domain controller, wherein the second request sent to the second FSD domain controller can be expressed as Vehicle.LiMesh.IcnRouter.ApiGateway.AddressInfo-fsd-b.

[0071] In an embodiment of the present application, whether there is connectivity between vehicle domain controllers is determined based on the number of received response messages, and when there is connectivity, the cloud proxy service address and the gateway service address are switched, which can shield the influence of cloud server and control plane gateway scheduling; achieve high-efficiency and high-accuracy data center address switching between devices, ensure that all domain controllers in the vehicle complete the data center address switching synchronously, and avoid data transmission errors.

[0072] Figure 3 is a flow chart showing a method for switching a data center address of a vehicle according to an exemplary embodiment. Figure 3 As shown, the method includes the following steps, which can be specifically executed by a domain controller with a vehicle-side routing service.

[0073] Step 301, after receiving the indication information sent by the cloud server, a candidate request for testing connectivity is sent to multiple domain controllers specified in the vehicle, and the indication information includes the address of the target data center to be switched.

[0074] Step 302: For any domain controller among the multiple domain controllers, a first response message sent by the domain controller is received, where the first response message is generated by the domain controller according to the received candidate request.

[0075] Step 303: In response to determining that the multiple domain controllers have connectivity according to the received first response message, the current data center address is switched to the target data center address.

[0076] Step 304: Generate a target request according to the target data center address and the domain name of the domain controller, and send the target request to the domain controller. The target request is used to instruct the domain controller to switch its own data center address to the target data center address.

[0077] The contents of step S301 to step S304 can be found in the introduction of the above embodiment and will not be repeated here.

[0078] Step 305: Receive a second response message sent by the domain controller, where the second response message is sent by the domain controller after completing data center address switching.

[0079] Optionally, in an embodiment of the present application, after receiving the first request, the second HU domain controller, the XCU domain controller, the first FSD domain controller or the second FSD domain controller switches the cloud proxy service address according to the first request, and after completing the cloud proxy service address switching, sends the first request plus a confirmation character as a second response message to the first HU domain controller.

[0080] Optionally, in an embodiment of the present application, after receiving the second request, the second HU domain controller, the XCU domain controller, the first FSD domain controller or the second FSD domain controller switches the gateway service address according to the second request, and after completing the gateway service address switching, sends the second request plus a confirmation character as a second response message to the first HU domain controller.

[0081] Step 306, in response to determining that all of the multiple domain controllers have completed the data center address switch based on the received second response message, sending a third indication message to the cloud server to instruct the vehicle to complete the data center address switch.

[0082] In some implementations, the second response message includes a domain name and a target data center address, and the domain name in the second response message is parsed to determine a target domain controller to send the second response message.

[0083] Optionally, the target data center address in the second response message is parsed to determine that the second response message indicates that the target domain controller completes the switching of the target cloud proxy service address or indicates that the target domain controller completes the switching of the target gateway service address. In response to each of the multiple domain controllers completing the switching of the target cloud proxy service address and the switching of the target gateway service address, it is determined that all the multiple domain controllers have completed the switching of the data center addresses.

[0084] Taking the XCU domain controller as an example, after the cloud proxy service address is switched according to the first request, the second response message sent to the first HU domain controller can be expressed as Vehicle.LiMesh.CloudProxy.AddressInfoSHS-xcu-ack. After the gateway service address is switched according to the second request, the second response message sent to the first HU domain controller can be expressed as Vehicle.LiMesh.IcnRouter.ApiGateway.AddressInfo-xcu-ack.

[0085] Taking the second HU domain controller as an example, after the cloud proxy service address is switched according to the first request, the second response message sent to the first HU domain controller can be expressed as Vehicle.LiMesh.CloudProxy.AddressInfoSHS-hu-r-ack. After the gateway service address is switched according to the second request, the second response message sent to the first HU domain controller can be expressed as Vehicle.LiMesh.IcnRouter.ApiGateway.AddressInfo-hu-r-ack.

[0086] Taking the first FSD domain controller as an example, after the cloud proxy service address is switched according to the first request, the second response message sent to the first HU domain controller can be expressed as Vehicle.LiMesh.CloudProxy.AddressInfoSHS-fsd-a-ack. After the gateway service address is switched according to the second request, the second response message sent to the first HU domain controller can be expressed as Vehicle.LiMesh.IcnRouter.ApiGateway.AddressInfo-fsd-a-ack.

[0087] Taking the second FSD domain controller as an example, after completing the switching of the cloud proxy service address according to the first request, the second response message sent to the first HU domain controller can be expressed as Vehicle.LiMesh.CloudProxy.AddressInfoSHS-fsd-b-ack. After completing the switching of the gateway service address according to the second request, the second response message sent to the first HU domain controller can be expressed as Vehicle.LiMesh.IcnRouter.ApiGateway.AddressInfo-fsd-b-ack.

[0088] In the embodiment of the present application, after receiving the above 8 second response messages, the first HU domain controller determines that all multiple domain controllers have completed the data center address switching, and sends a third indication message to the cloud server to instruct the vehicle to complete the data center address switching.

[0089] In some embodiments, the message sent by the domain controller or the message received by the domain controller is forwarded by the vehicle-side proxy service and the vehicle signal service in the domain controller. For example, the first HU domain controller sends the candidate request and the target request through its own vehicle-side proxy service and the vehicle signal service. For another example, the XCU domain controller receives the candidate request and the target request sent by the first HU domain controller through its own vehicle signal service and the vehicle-side proxy service, and sends the first response message and the second response message through its own vehicle-side proxy service and the vehicle signal service.

[0090] In some implementations, the candidate request carries a first request identifier, the target request carries a second request identifier, the first response message carries a request identifier and is consistent with the first request identifier, and the second response message carries a request identifier and is consistent with the second request identifier. The request identifier (Request ID) is used to distinguish the request message to which the response message belongs. If the request identifier carried by the first response message is consistent with the first request identifier, it means that the current first response message is the response of the domain controller to the candidate request; if the request identifier carried by the first response message is inconsistent with the first request identifier, it means that the current first response message is not the response of the domain controller to the candidate request, and the first response message corresponding to the candidate request continues to be monitored.

[0091] Similarly, if the request identifier carried by the second response message is consistent with the second request identifier, it means that the current second response message is the response of the domain controller to the target request; if the request identifier carried by the second response message is inconsistent with the second request identifier, it means that the current second response message is not the response of the domain controller to the target request, and the second response message corresponding to the target request continues to be monitored. The embodiment of the present application distinguishes the request message to which the response message belongs through the request identifier, which can improve the accuracy of data center address switching and realize high-efficiency and high-accuracy data center address switching between devices.

[0092] In an embodiment of the present application, a second response message sent by a domain controller is received, and in response to determining that multiple domain controllers have all completed the data center address switching based on the received second response message, a third indication message is sent to the cloud server to instruct the vehicle to complete the data center address switching. This can shield the influence of the cloud server and the control plane gateway scheduling; achieve high-efficiency and high-accuracy data center address switching between devices, ensure that all domain controllers in the vehicle complete the data center address switching synchronously, and avoid data transmission errors.

[0093] Figure 4 is a flow chart showing a method for switching a data center address of a vehicle according to an exemplary embodiment. Figure 4As shown, in the embodiment of the present application, the domain controllers in the vehicle include a first HU domain controller, a second HU domain controller, an XCU domain controller, a first FSD domain controller, and a second FSD domain controller. After the first HU domain controller receives the indication information sent by the cloud server, it sends candidate requests to the second HU domain controller, the XCU domain controller, the first FSD domain controller, and the second FSD domain controller respectively. After the second HU domain controller, the XCU domain controller, the first FSD domain controller, and the second FSD domain controller receive the candidate requests, they send a first response message to the first HU domain controller. After the first HU domain controller receives the first response messages sent by the second HU domain controller, the XCU domain controller, the first FSD domain controller, and the second FSD domain controller respectively, it determines that multiple domain controllers The device has connectivity, switches the current data center address to the target data center address, generates a target request according to the target data center address and the domain name of any domain controller, and sends the target request to the domain controller. After receiving the target request, the second HU domain controller, the XCU domain controller, the first FSD domain controller and the second FSD domain controller respectively switch the cloud proxy service address and the gateway service address according to the target request, and send a second response message to the first HU domain controller after completing the switching. In response to determining that the second HU domain controller, the XCU domain controller, the first FSD domain controller and the second FSD domain controller have all completed the switching of the cloud proxy service address and the gateway service address according to the received second response message, a third indication message for instructing the vehicle to complete the data center address switching is sent to the cloud server.

[0094] Figure 5 1 is a block diagram of a data center address switching device for a vehicle according to an exemplary embodiment. Figure 5 , the data center address switching device 500 of the vehicle includes:

[0095] The transceiver module 510 is used to send candidate requests for testing connectivity to multiple domain controllers specified in the vehicle after receiving the indication information sent by the cloud server, where the indication information includes the address of the target data center to be switched;

[0096] The receiving module 520 is configured to receive a first response message sent by any domain controller among the multiple domain controllers, where the first response message is generated by the domain controller according to the received candidate request;

[0097] A switching module 530, configured to switch a current data center address to a target data center address in response to determining that the multiple domain controllers have connectivity according to the received first response message;

[0098] The sending module 540 is used to generate a target request according to the target data center address and the domain name of the domain controller, and send the target request to the domain controller. The target request is used to instruct the domain controller to switch its own data center address to the target data center address.

[0099] In some implementations, the target data center address includes a target cloud proxy service address and a target gateway service address, the target request includes a first request and a second request, and the sending module 540 is further configured to:

[0100] Generate a first request according to the target cloud proxy service address and the domain name of the domain controller, and send the first request to the domain controller, the first request is used to instruct the domain controller to switch its own cloud proxy service address to the target cloud proxy service address;

[0101] A second request is generated according to the target gateway service address and the domain name of the domain controller, and the second request is sent to the domain controller. The second request is used to instruct the domain controller to switch its own gateway service address to the target gateway service address.

[0102] In some implementations, the transceiver module 510 is further configured to:

[0103] receiving a second response message sent by the domain controller, where the second response message is sent by the domain controller after completing the data center address switching;

[0104] In response to determining that all of the multiple domain controllers have completed the data center address switching according to the received second response message, a third indication message is sent to the cloud server to instruct the vehicle to complete the data center address switching.

[0105] In some embodiments, the candidate request carries a first request identifier, the target request carries a second request identifier, the first response message carries a request identifier and is consistent with the first request identifier, and the second response message carries a request identifier and is consistent with the second request identifier, wherein the request identifier is used to distinguish the request message to which the response message belongs.

[0106] In some implementations, the second response message includes a domain name and a target data center address, and the transceiver module 510 is further configured to:

[0107] Resolve the domain name in the second response message to determine a target domain controller for sending the second response message;

[0108] Parsing the target data center address in the second response message, and determining that the second response message instructs the target domain controller to complete the switching of the target cloud proxy service address or instructs the target domain controller to complete the switching of the target gateway service address;

[0109] In response to each of the multiple domain controllers completing the switching of the target cloud proxy service address and the switching of the target gateway service address, it is determined that all of the multiple domain controllers have completed the data center address switching.

[0110] In some implementations, the switching module 530 is further configured to:

[0111] Obtain a first number of domain controllers that the vehicle has;

[0112] Recording a second number of received first response messages;

[0113] In response to a difference between the first number and the second number being a preset number threshold, it is determined that the plurality of domain controllers have connectivity.

[0114] In some implementations, messages sent to a domain controller or messages received from a domain controller are forwarded by a vehicle-side proxy service and a vehicle signal service in the domain controller.

[0115] The embodiments of the present application can shield the influence of cloud server and control plane gateway scheduling; realize high-efficiency and high-accuracy data center address switching between devices, ensure that all domain controllers in the vehicle complete data center address switching synchronously, and avoid data transmission errors.

[0116] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0117] Figure 6 6 is a block diagram of an apparatus 600 according to an exemplary embodiment. For example, the apparatus 600 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0118] Reference Figure 6 , the device 600 may include one or more of the following components: a processing component 602 , a memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input / output (I / O) interface 612 , a sensor component 614 , and a communication component 616 .

[0119] The processing component 602 generally controls the overall operation of the device 600, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 602 may include one or more modules to facilitate the interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate the interaction between the multimedia component 608 and the processing component 602.

[0120] The memory 604 is configured to store various types of data to support operations on the device 600. Examples of such data include instructions for any application or method operating on the device 600, contact data, phone book data, messages, pictures, videos, etc. The memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0121] The power supply component 606 provides power to the various components of the device 600. The power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 600.

[0122] The multimedia component 608 includes a screen that provides an output interface between the device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front camera and / or a rear camera. When the device 600 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0123] The audio component 610 is configured to output and / or input audio signals. For example, the audio component 610 includes a microphone (MIC), and when the device 600 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 604 or sent via the communication component 616. In some embodiments, the audio component 610 also includes a speaker for outputting audio signals.

[0124] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0125] The sensor assembly 614 includes one or more sensors for providing various aspects of status assessment for the device 600. For example, the sensor assembly 614 can detect the open / closed state of the device 600, the relative positioning of components, such as the display and keypad of the device 600, and the sensor assembly 614 can also detect the position change of the device 600 or a component of the device 600, the presence or absence of user contact with the device 600, the orientation or acceleration / deceleration of the device 600, and the temperature change of the device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 614 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0126] The communication component 616 is configured to facilitate wired or wireless communication between the device 600 and other devices. The device 600 can access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 616 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0127] In an exemplary embodiment, the apparatus 600 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0128] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 604 including instructions, and the instructions can be executed by a processor 620 of the device 600 to complete the above method. Optionally, the storage medium can be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0129] Figure 7 is a block diagram of a data center address switching device 700 for a vehicle according to an exemplary embodiment. For example, the device 700 may be provided as a server. Figure 7 , the apparatus 700 includes a processing component 722, which further includes one or more processors, and a memory resource represented by a memory 732 for storing instructions, such as an application, that can be executed by the processing component 722. The application stored in the memory 732 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 722 is configured to execute the instructions to perform the above method.

[0130] The device 700 may also include a power supply component 726 configured to perform power management of the device 700, a wired or wireless network interface 750 configured to connect the device 700 to a network, and an input / output (I / O) interface 758. The device 700 may operate based on an operating system stored in the memory 732, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0131] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0132] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for switching a data center address of a vehicle, characterized in that: include: After receiving the indication information sent by the cloud server, sending a candidate request for testing connectivity to multiple domain controllers specified in the vehicle, wherein the indication information includes an address of a target data center to be switched; For any domain controller among the multiple domain controllers, receiving a first response message sent by the domain controller, where the first response message is generated by the domain controller according to the received candidate request; In response to determining that the plurality of domain controllers have connectivity according to the received first response message, switching a current data center address to the target data center address; A target request is generated according to the target data center address and the domain name of the domain controller, and the target request is sent to the domain controller, wherein the target request is used to instruct the domain controller to switch its own data center address to the target data center address.

2. The method according to claim 1, characterized in that The target data center address includes a target cloud proxy service address and a target gateway service address, the target request includes a first request and a second request, and the target request is generated according to the target data center address and the domain name of the domain controller, and the target request is sent to the domain controller, and further includes: Generate the first request according to the target cloud proxy service address and the domain name of the domain controller, and send the first request to the domain controller, wherein the first request is used to instruct the domain controller to switch its own cloud proxy service address to the target cloud proxy service address; The second request is generated according to the target gateway service address and the domain name of the domain controller, and the second request is sent to the domain controller, where the second request is used to instruct the domain controller to switch its own gateway service address to the target gateway service address.

3. The method according to claim 2, characterized in that After sending the target request to the domain controller, the method further includes: receiving a second response message sent by the domain controller, where the second response message is sent by the domain controller after completing data center address switching; In response to determining that all of the multiple domain controllers have completed the data center address switching according to the received second response message, a third indication message is sent to the cloud server to instruct the vehicle to complete the data center address switching.

4. The method according to claim 3, characterized in that The candidate request carries a first request identifier, the target request carries a second request identifier, the first response message carries a request identifier and is consistent with the first request identifier, and the second response message carries a request identifier and is consistent with the second request identifier, wherein the request identifier is used to distinguish the request message to which the response message belongs.

5. The method according to claim 3, characterized in that: The second response message includes the domain name and the target data center address, and determining that all of the multiple domain controllers have completed data center address switching according to the received second response message includes: Resolving the domain name in the second response message to determine a target domain controller for sending the second response message; Parsing the target data center address in the second response message, and determining that the second response message instructs the target domain controller to complete the switching of the target cloud proxy service address or instructs the target domain controller to complete the switching of the target gateway service address; In response to each of the multiple domain controllers completing the switching of the target cloud proxy service address and the switching of the target gateway service address, it is determined that all of the multiple domain controllers have completed the data center address switching.

6. The method according to any one of claims 1 to 5, characterized in that: The determining, according to the received first response message, that the multiple domain controllers have connectivity includes: Obtaining a first number of domain controllers of the vehicle; Recording a second number of the first response messages received; In response to a difference between the first number and the second number being a preset number threshold, it is determined that the multiple domain controllers have connectivity.

7. The method according to claim 6, characterized in that Messages sent to the domain controller or messages received from the domain controller are forwarded by the vehicle-side proxy service and the vehicle signal service in the domain controller.

8. A data center address switching device for a vehicle, characterized in that: include: A transceiver module, configured to send candidate requests for testing connectivity to multiple domain controllers specified in the vehicle after receiving indication information sent by the cloud server, wherein the indication information includes an address of a target data center to be switched; A receiving module, configured to receive, for any domain controller among the multiple domain controllers, a first response message sent by the domain controller, where the first response message is generated by the domain controller according to the received candidate request; a switching module, configured to switch a current data center address to the target data center address in response to determining that the multiple domain controllers have connectivity according to the received first response message; A sending module is used to generate a target request according to the target data center address and the domain name of the domain controller, and send the target request to the domain controller, wherein the target request is used to instruct the domain controller to switch its own data center address to the target data center address.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the data center address switching method for a vehicle as described in any one of claims 1 to 7. 10 . A computer-readable storage medium, when instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the data center address switching method for a vehicle as claimed in any one of claims 1 to 7.