Communication method and device based on vehicle wakeup, electronic equipment and storage medium

Abstract

The invention provides a communication method and device based on vehicle wakeup, electronic equipment and a storage medium. The method is applied to a vehicle, a plurality of domain controllers are deployed in the vehicle, and the domain controllers are used for executing vehicle functions. Comprising the following steps: in response to a sleep wake-up instruction for a vehicle, determining an opposite-end controller of a domain controller in the vehicle; the opposite-end controller represents other domain controllers which carry out communication subscription on the domain controller; respectively updating far-end agent information stored in a domain controller in the vehicle and far-end agent information stored in an opposite-end controller to obtain first initial information corresponding to the far-end agent information stored in the domain controller and second initial information corresponding to the far-end agent information stored in the opposite-end controller; the remote agent information represents a current communication link between the domain controller and the opposite end controller; and calling a preset link establishment interface according to the first initial information and the second initial information, and establishing a new communication link between the domain controller and the opposite-end controller.

Description

Technical Field

[0001] The present application relates to communication technology, and in particular to a vehicle wake-up-based communication method, device, electronic device and storage medium. Background Art

[0002] The vehicle includes multiple domain controllers. When the domain controllers are in sleep mode, the power supply relationship between them will cause the sleep time of the domain controllers to be inconsistent, which will cause the DDS (Data Distribution Service) information saved by each domain controller to be inconsistent with the actual situation. This will affect the link establishment efficiency between domain controllers when the vehicle is awakened from sleep mode.

[0003] How to efficiently establish a link when the vehicle is asleep or awakened, thereby improving communication efficiency, is a problem that needs to be solved urgently. Summary of the invention

[0004] The present application provides a vehicle wake-up-based communication method, device, electronic device and storage medium to improve communication efficiency.

[0005] In a first aspect, the present application provides a communication method based on vehicle wake-up, the method is applied to a vehicle, wherein a plurality of domain controllers are deployed in the vehicle, and the domain controllers are used to execute vehicle functions; the method comprises:

[0006] In response to a sleep wake-up instruction for the vehicle, determining a peer controller of a domain controller in the vehicle; wherein the peer controller represents another domain controller that subscribes to communication with the domain controller;

[0007] Respectively updating the remote proxy information stored in the domain controller in the vehicle and the remote proxy information stored in the peer controller of the domain controller to obtain first initial information corresponding to the remote proxy information stored in the domain controller and second initial information corresponding to the remote proxy information stored in the peer controller; wherein the remote proxy information represents the current communication link between the domain controller and the peer controller;

[0008] According to the first initial information and the second initial information, a preset link establishment interface is called to establish a new communication link between the domain controller and the peer controller; wherein the communication link is used for communication between the domain controller and the peer controller.

[0009] In a second aspect, the present application provides a communication device based on vehicle wake-up, the device is applied to a vehicle, a plurality of domain controllers are deployed in the vehicle, and the domain controllers are used to perform vehicle functions; the device includes:

[0010] A command response module, configured to determine a peer controller of a domain controller in the vehicle in response to a sleep wake-up command to the vehicle; wherein the peer controller represents other domain controllers that subscribe to communication with the domain controller;

[0011] An information updating module, used to update the remote proxy information stored in the domain controller in the vehicle and the remote proxy information stored in the peer controller of the domain controller, respectively, to obtain first initial information corresponding to the remote proxy information stored in the domain controller and second initial information corresponding to the remote proxy information stored in the peer controller; wherein the remote proxy information represents the current communication link between the domain controller and the peer controller;

[0012] A link building module is used to call a preset link building interface according to the first initial information and the second initial information to build a new communication link between the domain controller and the peer controller; wherein the communication link is used for communication between the domain controller and the peer controller.

[0013] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0014] The memory stores computer-executable instructions;

[0015] The processor executes the computer-executable instructions stored in the memory to implement the method according to the first aspect.

[0016] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect.

[0017] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the method described in the first aspect when executed by a processor.

[0018] The present application provides a communication method, device, electronic device and storage medium based on vehicle wake-up. By responding to the sleep wake-up instruction of the vehicle, for any domain controller in the vehicle, the peer controller of the domain controller is determined, and the remote proxy information of the domain controller and the remote proxy information of the peer controller are obtained. The remote proxy information stored by the domain controller and the remote proxy information stored by the peer controller of the domain controller are updated respectively to obtain the updated first initial information and the second initial information. The erroneous DDS information in the domain controller and the peer controller is cleared to avoid the erroneous DDS information affecting the communication efficiency. The preset link establishment interface is called to establish a link between the domain controller and the peer controller to obtain a new communication link. The domain controller and the peer controller can re-enter the link establishment logic when waking up, so as to achieve fast link establishment after waking up and improve the communication efficiency of sleep wake-up. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0020] Figure 1 A flow chart of a vehicle wake-up based communication method provided in an embodiment of the present application;

[0021] Figure 2 A flow chart of a vehicle wake-up based communication method provided in an embodiment of the present application;

[0022] Figure 3 A flow chart of a vehicle wake-up based communication method provided in an embodiment of the present application;

[0023] Figure 4 A structural block diagram of a vehicle wake-up based communication device provided in an embodiment of the present application;

[0024] Figure 5 A structural block diagram of a vehicle wake-up based communication device provided in an embodiment of the present application;

[0025] Figure 6 A structural block diagram of an electronic device provided in an embodiment of the present application;

[0026] Figure 7 A structural block diagram of an electronic device provided in an embodiment of the present application.

[0027] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0028] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0029] It should be clear that the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0030] When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.

[0031] In the description of the present application, it should be understood that the terms "first", "second", "third", etc. are only used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence, nor can they be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to the specific circumstances. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0032] It should be noted that due to space limitations, this application specification does not list all optional implementation methods. After reading this application specification, those skilled in the art should be able to think that as long as the technical features do not contradict each other, any combination of technical features can constitute an optional implementation method. Each embodiment is described in detail below.

[0033] There are multiple domain controllers in the vehicle. When the vehicle is in sleep mode, the whole vehicle will be in a low-power state. For example, the domain controller in the cockpit domain will experience a program jam after sleep mode, retain the current program state and all memory, uninstall the Ethernet communication network card, and stop the program. There may be a power supply relationship between different domain controllers in the vehicle. For example, the domain controller in the vehicle control domain can supply power to the domain controller in the cockpit domain. Due to the power supply relationship between domain controllers, the sleep time is not uniform, resulting in abnormal DDS saved information of both controllers. The saved DDS information does not match the actual state, resulting in slow link establishment or failure to establish a link when waking up.

[0034] When the vehicle is in dormancy without losing power, when waking up the vehicle, it is necessary to quickly complete the service online and offline status update based on SOA (Service Oriented Architecture), and quickly establish a DDS link for the vehicle to restore the Ethernet communication of the vehicle.

[0035] The present application provides a vehicle wake-up-based communication method, device, electronic device and storage medium, which aim to solve the above technical problems in the prior art.

[0036] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0037] Figure 1 The present invention is a flow chart of a vehicle wake-up based communication method provided in an embodiment of the present application. The method can be performed by a vehicle wake-up based communication device. The method is applied to a vehicle, and a plurality of domain controllers are deployed in the vehicle, and the domain controllers are used to perform vehicle functions. Figure 1 As shown, the method comprises the following steps:

[0038] S101. In response to a sleep wake-up instruction for a vehicle, determine a peer controller of a domain controller in the vehicle; wherein the peer controller represents other domain controllers that subscribe to communication with the domain controller.

[0039] Exemplarily, multiple domain controllers can be deployed in a vehicle, and different domain controllers can be used to perform different vehicle functions. For example, domain controllers may include cockpit domain controllers, vehicle control domain controllers, and the like. Domain controllers can subscribe to and publish messages to each other, that is, when the vehicle is working, the domain controllers can communicate with each other. Vehicle hibernation means that the entire vehicle is in a low-power state without power outages. For example, the domain controller in the cockpit domain will experience a program jam after hibernation, retaining the current program state and all memory, and uninstalling the Ethernet communication network card, and the program stops running.

[0040] After the vehicle goes into sleep mode, a sleep wake-up command can be sent to the vehicle at any time to wake up the sleeping vehicle. After responding to the sleep wake-up command, for each domain controller in the vehicle, the peer controller of the domain controller can be determined. The peer controller refers to other domain controllers that subscribe to communication with the domain controller, and a domain controller can correspond to one or more peer controllers. For example, for the cockpit domain controller, the peer controller is the vehicle control domain controller, and for the vehicle control domain controller, the peer controller is the cockpit domain controller. That is, the domain controller and the peer controller can be peers to each other. The peer controller of each domain controller can be determined in advance, and after responding to the sleep wake-up command, all peer controllers of each domain controller can be directly determined.

[0041] S102. Update the remote proxy information stored by the domain controller in the vehicle and the remote proxy information stored by the peer controller of the domain controller respectively to obtain first initial information corresponding to the remote proxy information stored by the domain controller and second initial information corresponding to the remote proxy information stored by the peer controller; wherein the remote proxy information represents the current communication link between the domain controller and the peer controller.

[0042] Exemplarily, each domain controller stores remote proxy information, which represents the current communication link between the domain controller and the peer controller. The remote proxy information may include the IP address and port number of the peer controller. That is, the remote proxy information may indicate the peer controller of the domain controller that has subscribed to the domain controller. For example, controller A and controller B are peers to each other, and the remote proxy information in controller A may represent the communication link between controller A and controller B, and the remote proxy information may store the IP address and port number of controller B; the remote proxy information in controller B may also represent the communication link between controller A and controller B, and the remote proxy information may store the IP address and port number of controller A.

[0043] For each domain controller, the remote proxy information stored in the domain controller and the remote proxy information stored in the peer controller of the domain controller are updated respectively, that is, the remote proxy information stored in the domain controller can be updated, and the remote proxy information stored in the peer controller of the domain controller can be updated. After the remote proxy information stored in the domain controller is updated, the first initial information is obtained; after the remote proxy information stored in the peer controller of the domain controller is updated, the second initial information is obtained. For example, the remote proxy information can be initialized to obtain the processed initial information.

[0044] S103. According to the first initial information and the second initial information, call a preset link establishment interface to establish a new communication link between the domain controller and the peer controller; wherein the communication link is used for communication between the domain controller and the peer controller.

[0045] Exemplarily, after obtaining the first initial information and the second initial information, the domain controller and the peer controller may be re-established. A link establishment interface is pre-set, and the link establishment interface is used to quickly establish a new communication link between all peers. The preset link establishment interface is called, and messages are sent between the domain controller and the peer controller with a preset number of messages to achieve the purpose of rapid link establishment. The preset number of messages can also avoid causing a surge in network data.

[0046] In the process of link building, the first initial information and the second initial information can be updated respectively, so that the first initial information and the second initial information can represent the new communication link after the update. For example, the IP address and port number of the peer controller can be added to the first initial information to obtain the updated first initial information. In this embodiment, the process of calling the interface to re-establish the link is not specifically limited.

[0047] In this embodiment, according to the first initial information and the second initial information, the preset link establishment interface is called to build a new communication link between the domain controller and the opposite controller, including: according to the communication protocol between the domain controller and the opposite controller, based on the association between the preset communication protocol and the link establishment logic, determining the link establishment logic between the domain controller and the opposite controller as the target logic; wherein the link establishment logic represents the construction rules of the communication link; according to the target logic, calling the preset link establishment interface, adding new remote proxy information to the first initial information and the second initial information respectively, and building a new communication link between the domain controller and the opposite controller.

[0048] Specifically, the domain controller and the peer controller may communicate with each other using a preset communication protocol, and different communication protocols may correspond to different link building logics, and the link building logic represents the rules for creating a communication link. The communication protocol between the domain controller and the peer controller is determined, and the link building logic between the domain controller and the peer controller is determined as the target logic according to the association between the preset communication protocol and the link building logic.

[0049] Call the preset link establishment interface, adopt the target logic, and add new remote proxy information in the first initial information and the second initial information respectively. For example, add the IP address of the peer controller of the domain controller in the first initial information, and add the IP address of the domain controller in the second initial information, that is, add the IP address of the peer controller of the peer controller. For different target logics, the information added to the initial information may be different. Each domain controller acts as a new participant to establish a link with the peer. After obtaining the new remote proxy information in the domain controller and the new remote proxy information in the peer controller, a new communication link between the domain controller and the peer controller can be obtained.

[0050] The beneficial effect of such a setting is that targeted links are established for different communication protocols, the accuracy of link establishment is improved, and communication is quickly restored when awakened.

[0051] In an embodiment of the present application, by responding to a sleep wake-up instruction for a vehicle, for any domain controller in the vehicle, the peer controller of the domain controller is determined, and the remote proxy information of the domain controller and the remote proxy information of the peer controller are obtained. The remote proxy information stored by the domain controller and the remote proxy information stored by the peer controller of the domain controller are updated respectively to obtain the updated first initial information and the second initial information. The erroneous DDS information in the domain controller and the peer controller is cleared to prevent the erroneous DDS information from affecting the communication efficiency. The preset link establishment interface is called to establish a link between the domain controller and the peer controller to obtain a new communication link. The domain controller and the peer controller can re-enter the link establishment logic when waking up, so as to achieve rapid link establishment after waking up and improve the communication efficiency of sleep wake-up.

[0052] Figure 2 A flow chart of a vehicle wake-up based communication method provided in an embodiment of the present application.

[0053] In this embodiment, the remote proxy information stored in the domain controller in the vehicle and the remote proxy information stored in the opposite controller of the domain controller are updated respectively to obtain first initial information corresponding to the remote proxy information stored in the domain controller and second initial information corresponding to the remote proxy information stored in the opposite controller, including: deleting the remote proxy information stored in the domain controller in the vehicle to obtain first initial information corresponding to the remote proxy information stored in the domain controller; wherein the first initial information is a null value; deleting the remote proxy information stored in the opposite controller of the domain controller to obtain second initial information corresponding to the remote proxy information stored in the opposite controller; wherein the second initial information is a null value.

[0054] like Figure 2 As shown, the method includes:

[0055] S201. In response to a sleep wake-up instruction for a vehicle, determine a peer controller of a domain controller in the vehicle; wherein the peer controller represents other domain controllers that subscribe to communication with the domain controller.

[0056] Exemplarily, this step may refer to the above-mentioned step S101 and will not be described in detail.

[0057] S202, deleting the remote proxy information stored in the domain controller in the vehicle to obtain first initial information corresponding to the remote proxy information stored in the domain controller; wherein the first initial information is a null value.

[0058] Exemplarily, the update process of the remote proxy information may be a deletion process. When updating the remote proxy information, the remote proxy information of the domain controller may be updated first, and then the remote proxy information of the peer controller may be updated. Alternatively, the remote proxy information of the domain controller and the peer controller may be updated simultaneously.

[0059] In this embodiment, the remote proxy information in the domain controller may also be updated first, that is, the remote proxy information stored in the domain controller may be deleted. After deletion, the first initial information corresponding to the remote proxy information is obtained. The first initial information is empty, indicating that the remote proxy information does not exist in the domain controller.

[0060] In this embodiment, the domain controller in the vehicle corresponds to multiple peer controllers, and the remote proxy information stored in the domain controller in the vehicle corresponds one-to-one to the peer controller of the domain controller; the remote proxy information stored in the domain controller in the vehicle is deleted, including: submitting the remote proxy information stored in the domain controller in the vehicle to a preset protocol stack thread in sequence; wherein the preset protocol stack thread is used to cache the information to be deleted; and deleting each remote proxy information stored in the domain controller in the vehicle in the preset protocol stack thread.

[0061] Specifically, one domain controller may correspond to multiple peer controllers, and the domain controller stores remote agent information corresponding to each peer controller, that is, the remote agent information in the domain controller corresponds to the peer controller of the domain controller one by one.

[0062] When deleting the remote proxy information stored in the domain controller, the remote proxy information stored in the domain controller can be submitted to the preset protocol stack thread in sequence. The preset protocol stack thread can be used to cache the information to be deleted. For example, the preset protocol stack thread can be a GC (Garbage Collection) thread. In the preset protocol stack thread, each remote proxy information stored in the domain controller is gradually deleted. For example, the reader and writer in the remote proxy information can be deleted, and the proxy participant represented by the remote proxy information can be deleted. The proxy participant is the opposite controller corresponding to the remote proxy information. Each time a remote proxy information is deleted, an empty first initial information is obtained.

[0063] The beneficial effect of this setting is that the deletion event is submitted to the GC thread, the remote proxy information is automatically deleted, and the efficiency of re-establishing the chain is improved.

[0064] S203, deleting the remote proxy information stored in the peer controller of the domain controller to obtain second initial information corresponding to the remote proxy information stored in the peer controller; wherein the second initial information is a null value.

[0065] Exemplarily, after the domain controller deletes the remote proxy information stored by itself, the peer controller of the domain controller can also delete the remote proxy information stored by itself. After the deletion, the second initial information is obtained, that is, the second initial information is also empty. The remote proxy information deleted by the domain controller represents the communication link between the domain controller and the peer controller, and the remote proxy information deleted by the peer controller also represents the communication link between the peer controller and the domain controller. That is, the remote proxy information deleted by the domain controller corresponds to the remote proxy information deleted by the peer controller. If the peer controller also stores the remote proxy information of other domain controllers, the peer controller does not need to delete the remote proxy information of other domain controllers.

[0066] In this embodiment, by deleting the remote proxy information of both parties, both parties are made to re-enter the logic of link building as new participants, avoiding inconsistency of information stored by both parties, improving the efficiency and accuracy of link building, and thus improving the efficiency of waking up the vehicle.

[0067] In this embodiment, the remote proxy information stored in the peer controller of the domain controller is deleted, including: if it is determined that the remote proxy information stored in the domain controller in the vehicle is deleted in a preset protocol stack thread, a message information is sent to the peer controller corresponding to the remote proxy information stored in the domain controller in the vehicle; wherein the message information represents the deletion status of the remote proxy information; according to the message information, the remote proxy information stored in the peer controller is submitted to the preset protocol stack thread; and the remote proxy information stored in the peer controller is deleted in the preset protocol stack thread.

[0068] Specifically, the domain controller may notify each peer controller to delete all remote proxy information stored in itself after deleting it, or it may send a message to the peer controller corresponding to the remote proxy information to notify the peer controller to delete the remote proxy information of the domain controller each time the domain controller deletes the remote proxy information. For example, if controller A deletes the remote proxy information of controller B stored in itself, controller B may be notified to delete the stored remote proxy information of controller A.

[0069] That is to say, for any remote proxy information stored by the domain controller, after the remote proxy information is deleted through the preset protocol stack thread, the domain controller can send a message to the peer controller corresponding to the remote proxy information. The message information can represent the deletion of the remote proxy information, that is, inform the peer controller that the remote proxy information of the domain controller stored by the peer controller needs to be deleted. The peer controller receives the message information and determines the remote proxy information that needs to be deleted. The remote proxy information that needs to be deleted is the remote proxy information corresponding to the domain controller that sent the message information. For example, controller A sends a message to controller B, then controller B needs to delete the stored remote proxy information of controller A. The remote proxy information that needs to be deleted by the peer controller is also submitted to the preset GC thread, and the remote proxy information submitted by the peer controller is deleted in the preset GC thread, thereby obtaining an empty second initial information.

[0070] The beneficial effect of such a setting is that, through the message information, the other end is notified to delete all the proxy information of the participants on this end, so as to achieve the consistency of information between the other end and the local end, facilitate the subsequent rapid link establishment, and improve the communication efficiency.

[0071] In this embodiment, it also includes: if a control instruction is received from a peer controller corresponding to the remote proxy information stored in the domain controller in the vehicle when the remote proxy information stored in the domain controller in the vehicle is deleted, the control instruction is not executed and the control instruction is cached in a preset protocol stack thread; if the control execution is in the first position in the preset protocol stack thread, the control instruction is executed and deleted.

[0072] Specifically, when deleting the remote proxy information, the vehicle may receive some control instructions, which are instructions for functional services on the vehicle, such as instructions for opening windows, adjusting seats, etc. Therefore, there may be a situation where the remote proxy information is deleted while the execution logic matching of the control instructions is performed.

[0073] If a control instruction is received from a peer controller corresponding to the remote proxy information when deleting the remote proxy information stored in the domain controller, the control instruction will not be executed first, and the control instruction can be cached in a preset protocol stack thread, that is, the execution task of the instruction and the task of deleting the remote proxy information are submitted to the same thread for processing. The control instruction received each time can be placed at the last position in the thread. With the completion of the event in the thread, if the control instruction is in the first position in the preset protocol stack thread, the control instruction can be executed and deleted from the thread.

[0074] The beneficial effect of this setting is that when concurrent control instructions appear when deleting remote proxy information, the control instructions and the deletion tasks can be submitted to the same thread for processing, ensuring the synchronization of the protocol stack, avoiding confusion caused by deleting and executing control instructions at the same time, and improving communication accuracy.

[0075] In this embodiment, after determining the peer controller of the domain controller in the vehicle, it also includes: if it is determined that the domain controller has not received any information sent by the peer controller of the domain controller within a preset time period, then it is determined that the peer controller of the domain controller is in a dormant state, and the remote proxy information stored in the domain controller in the vehicle is deleted.

[0076] Specifically, before deleting the remote proxy information, it is necessary to ensure that both the domain controller and the peer controller are in a dormant state. After receiving the dormancy wake-up instruction, the domain controller can confirm whether it is in a dormant state. For confirming whether the peer controller is in a dormant state, a time period is preset. After determining the peer controller of the domain controller, it is determined whether information sent by the peer controller is received within the preset time period. For example, the preset time period is 8 seconds.

[0077] If information is received from the peer controller, it is determined that the peer controller is not in a dormant state, and the remote proxy information of the peer controller cannot be deleted. It is continued to be determined whether there is any information received from the peer controller within the preset time period until no information is received from the peer controller. If no information is received from the peer controller within the preset time period, it is determined that the peer controller is in a dormant state, and the remote proxy information of the peer controller stored in the domain controller can be deleted.

[0078] The beneficial effect of this setting is that the controllers may have a power supply relationship, resulting in inconsistent sleep time, ensuring that both domain controllers are in sleep mode, avoiding affecting the normal operation of the non-sleeping domain controller, and improving the efficiency and accuracy of communication.

[0079] S204. According to the first initial information and the second initial information, call a preset link establishment interface to establish a new communication link between the domain controller and the peer controller; wherein the communication link is used for communication between the domain controller and the peer controller.

[0080] Exemplarily, this step may refer to the above-mentioned step S103 and will not be described in detail.

[0081] In an embodiment of the present application, by responding to a sleep wake-up instruction for a vehicle, for any domain controller in the vehicle, the peer controller of the domain controller is determined, and the remote proxy information of the domain controller and the remote proxy information of the peer controller are obtained. The remote proxy information stored by the domain controller and the remote proxy information stored by the peer controller of the domain controller are updated respectively to obtain the updated first initial information and the second initial information. The erroneous DDS information in the domain controller and the peer controller is cleared to prevent the erroneous DDS information from affecting the communication efficiency. The preset link establishment interface is called to establish a link between the domain controller and the peer controller to obtain a new communication link. The domain controller and the peer controller can re-enter the link establishment logic when waking up, so as to achieve rapid link establishment after waking up and improve the communication efficiency of sleep wake-up.

[0082] Figure 3 A flow chart of a vehicle wake-up based communication method provided in an embodiment of the present application.

[0083] In this embodiment, in response to a sleep wake-up instruction for the vehicle, a peer controller of a domain controller in the vehicle is determined, including: in response to a sleep wake-up instruction for the vehicle, obtaining remote proxy information stored by the domain controller in the vehicle; and determining the peer controller of the domain controller in the vehicle based on the remote proxy information stored by the domain controller in the vehicle.

[0084] like Figure 3 As shown, the method includes:

[0085] S301. In response to a sleep wake-up instruction for a vehicle, remote proxy information stored in a domain controller in the vehicle is obtained.

[0086] For example, the vehicle can receive a vehicle wake-up signal from the MCU (Microcontroller Unit) at any time after sleeping, that is, a sleep wake-up instruction. After receiving the sleep wake-up instruction for the vehicle, for any domain controller in the vehicle, all remote proxy information stored in the domain controller is determined.

[0087] S302: Determine a peer controller of the domain controller in the vehicle according to the remote proxy information stored in the domain controller in the vehicle.

[0088] Exemplarily, after obtaining all remote proxy information stored in the domain controller, all peer controllers corresponding to the domain controller can be obtained. Each remote proxy information in the domain controller corresponds to a peer controller. For example, the remote proxy information may contain an identifier, which can characterize a peer controller. In this embodiment, by determining the remote proxy information, the domain controllers that communicate with each other can be determined, so that the link between the two parties can be re-established to achieve re-communication between the two parties.

[0089] In this embodiment, the remote proxy information includes controller identification information, and the controller identification information is used to characterize the peer controller of the domain controller, and the controller identification information includes at least one of an IP address and a port number; determining the peer controller of the domain controller in the vehicle according to the remote proxy information stored in the domain controller in the vehicle includes: determining the peer controller of the domain controller in the vehicle according to the controller identification information stored in the domain controller in the vehicle.

[0090] Specifically, the remote proxy information may include controller identification information, and the controller identification information may be used to characterize the peer controller of the domain controller. For example, the controller identification information includes at least one of an IP address and a port number. The controller identification information is obtained from the remote proxy information, and a domain controller corresponding to the controller identification information is determined as the peer controller according to the controller identification information. For example, each IP address corresponds to a unique domain controller, and the corresponding domain controller can be found according to the IP address, that is, the peer controller is determined.

[0091] The beneficial effect of such a setting is that each opposite-end controller can be accurately determined, link establishment errors can be avoided, and the efficiency and accuracy of re-communication can be improved.

[0092] S303, respectively updating the remote proxy information stored by the domain controller in the vehicle and the remote proxy information stored by the peer controller of the domain controller, to obtain first initial information corresponding to the remote proxy information stored by the domain controller and second initial information corresponding to the remote proxy information stored by the peer controller; wherein the remote proxy information represents the current communication link between the domain controller and the peer controller.

[0093] Exemplarily, this step may refer to the above-mentioned step S102 and will not be described in detail.

[0094] In this embodiment, it also includes: receiving a subscription message sent by a domain controller in a vehicle to a peer controller; wherein the subscription message represents a message of a topic of the domain controller subscribed by the peer controller, and the subscription message includes the number of times the domain controller deletes remote proxy information; obtaining the number of times the peer controller of the domain controller deletes the remote proxy information; if the number of times the domain controller deletes the remote proxy information is consistent with the number of times the peer controller of the domain controller deletes the remote proxy information, deleting the remote proxy information stored in the domain controller in the vehicle, and updating the number of times the domain controller deletes the remote proxy information.

[0095] Specifically, before the remote proxy information of the domain controller and the peer controller needs to be deleted, the domain controller can send a subscription message to the peer controller. The subscription message can represent the message of the topic of the domain controller subscribed by the peer controller, and the subscription message can include the number of times the domain controller deletes the remote proxy information of the peer controller. Each domain controller must store the number of times it deletes the remote proxy information of each peer controller, and set the sent subscription message to DATA(P), that is, DATA(P) contains the number of times the domain controller deletes the remote proxy information of the peer controller.

[0096] The peer controller may also store the number of times the peer controller has deleted the remote proxy information of the domain controller. The number of times the domain controller has deleted the remote proxy information of the peer controller is determined as the first number; the number of times the peer controller has deleted the remote proxy information of the domain controller is determined as the second number. When the domain controller sends a subscription message, it indicates that the domain controller wants to delete the remote proxy information of the peer. The first number and the second number are obtained, and it is determined whether the first number and the second number are consistent. If they are consistent, the domain controller can delete the remote proxy information of the peer controller and update the first number. For example, the first number can be increased by one.

[0097] If the first number and the second number are inconsistent, determine the smaller value of the first number and the second number. If the smaller value is the second number, the remote proxy information stored in the peer controller of the domain controller is first deleted, and the second number is updated. For example, the second number can be increased by one to make the first number consistent with the second number. If the smaller value is the first number, no processing is performed, and the deletion process is performed when the peer controller acts as the local end and the domain controller acts as the peer end. For example, the number of deletions in controller A is 1 less than the number of deletions in controller B. When the number of deletions in controller A is used as the first number, no processing is performed; when the number of deletions in controller A is used as the second number, the remote proxy information corresponding to controller B stored in controller A is deleted, and the second number is increased by one.

[0098] The beneficial effect of such a setting is that each domain controller stores the number of deletion operations it has performed, which is used for number verification, thereby avoiding communication errors between the two parties and improving link establishment efficiency.

[0099] In this embodiment, the number of checks can be performed periodically. When it is found that the two deletion times are inconsistent, deletion can be performed to ensure that the deletion times are consistent; when the two deletion times are consistent, there is no need to perform deletion operations frequently to avoid frequent deletions affecting communication efficiency.

[0100] In this embodiment, it also includes: obtaining an authentication string located at a preset position from a subscription message; wherein the authentication string includes the number of times the domain controller deletes the remote proxy information; and obtaining the number of times the domain controller deletes the remote proxy information from the authentication string according to a preset character arrangement order.

[0101] Specifically, an authentication string can be set in the subscription message as a TOKEN (flag), and the TOKEN can be located at a preset position in the subscription message. The TOKEN can be designed in the form of a string array, and the order of the characters in the TOKEN can be set in advance, that is, the characters from which to which in the TOKEN are used to store the number of deletions can be predefined. For example, the 45th to 50th bytes in the TOKEN are used to store the number of deletions.

[0102] After receiving the subscription message, the TOKEN is obtained from the subscription message. Then, according to the preset character arrangement order, the position of the character storing the number of deletions in the TOKEN is determined, so that the number of times the domain controller deletes the remote proxy information of the peer controller can be obtained from the TOKEN.

[0103] The beneficial effect of this setting is that it defines how many bytes in the TOKEN are used to store the number of deletions, making it easier to obtain the number of deletions for verification, thereby improving the accuracy and efficiency of the number verification, and thus improving the accuracy and efficiency of chain reconstruction.

[0104] S304. According to the first initial information and the second initial information, call a preset link establishment interface to establish a new communication link between the domain controller and the peer controller; wherein the communication link is used for communication between the domain controller and the peer controller.

[0105] Exemplarily, this step may refer to the above-mentioned step S103 and will not be described in detail.

[0106] In an embodiment of the present application, by responding to a sleep wake-up instruction for a vehicle, for any domain controller in the vehicle, the peer controller of the domain controller is determined, and the remote proxy information of the domain controller and the remote proxy information of the peer controller are obtained. The remote proxy information stored by the domain controller and the remote proxy information stored by the peer controller of the domain controller are updated respectively to obtain the updated first initial information and the second initial information. The erroneous DDS information in the domain controller and the peer controller is cleared to prevent the erroneous DDS information from affecting the communication efficiency. The preset link establishment interface is called to establish a link between the domain controller and the peer controller to obtain a new communication link. The domain controller and the peer controller can re-enter the link establishment logic when waking up, so as to achieve rapid link establishment after waking up and improve the communication efficiency of sleep wake-up.

[0107] Figure 4 This is a structural block diagram of a communication device based on vehicle wake-up provided by an embodiment of the present disclosure. For the convenience of explanation, only the parts related to the embodiment of the present disclosure are shown. The device is applied to a vehicle, and multiple domain controllers are deployed in the vehicle, and the domain controllers are used to execute vehicle functions. Figure 4 The vehicle wake-up based communication device 400 includes: a command response module 401, an information update module 402 and a link establishment module 403.

[0108] The command response module 401 is used to determine the peer controller of the domain controller in the vehicle in response to the sleep wake-up command of the vehicle; wherein the peer controller represents other domain controllers that subscribe to the communication with the domain controller;

[0109] The information updating module 402 is used to update the remote proxy information stored in the domain controller in the vehicle and the remote proxy information stored in the peer controller of the domain controller, respectively, to obtain the first initial information corresponding to the remote proxy information stored in the domain controller and the second initial information corresponding to the remote proxy information stored in the peer controller; wherein the remote proxy information represents the current communication link between the domain controller and the peer controller;

[0110] The link building module 403 is used to call a preset link building interface according to the first initial information and the second initial information to build a new communication link between the domain controller and the peer controller; wherein the communication link is used for communication between the domain controller and the peer controller.

[0111] Figure 5 A structural block diagram of a communication device based on vehicle wake-up provided in an embodiment of the present disclosure, such as Figure 5 As shown, the vehicle wake-up based communication device 500 includes a command response module 501 , an information update module 502 and a link establishment module 503 , wherein the information update module 502 includes a first deletion unit 5021 and a second deletion unit 5022 .

[0112] The first deleting unit 5021 is used to delete the remote proxy information stored by the domain controller in the vehicle, and obtain the first initial information corresponding to the remote proxy information stored by the domain controller; wherein the first initial information is a null value;

[0113] The second deleting unit 5022 is used to delete the remote proxy information stored in the peer controller of the domain controller to obtain the second initial information corresponding to the remote proxy information stored in the peer controller; wherein the second initial information is a null value.

[0114] In one example, a domain controller in a vehicle corresponds to multiple peer controllers, and the remote proxy information stored in the domain controller in the vehicle corresponds one-to-one to the peer controllers of the domain controller; the first deleting unit 5021 is specifically used to:

[0115] Submitting the remote proxy information stored in the domain controller in the vehicle to a preset protocol stack thread in sequence; wherein the preset protocol stack thread is used to cache the information to be deleted;

[0116] The remote proxy information stored in the domain controller in the vehicle is deleted in the preset protocol stack thread.

[0117] In one example, the second deleting unit 5022 is specifically configured to:

[0118] If it is determined that the remote proxy information stored in the domain controller in the vehicle is deleted in the preset protocol stack thread, a message information is sent to the opposite end controller corresponding to the remote proxy information stored in the domain controller in the vehicle; wherein the message information represents the deletion status of the remote proxy information;

[0119] According to the message information, submitting the remote proxy information stored by the opposite end controller to a preset protocol stack thread;

[0120] The remote proxy information stored in the opposite controller is deleted in the preset protocol stack thread.

[0121] In one example, it also includes:

[0122] An instruction cache module, for not executing a control instruction sent by a peer controller corresponding to the remote proxy information stored by the domain controller in the vehicle when deleting the remote proxy information stored by the domain controller in the vehicle, and caching the control instruction in a preset protocol stack thread;

[0123] The instruction execution module is used to execute and delete the control instruction if the control instruction is in the first position in the preset protocol stack thread.

[0124] In one example, it also includes:

[0125] A sleep determination module is used to, after determining the peer controller of the domain controller in the vehicle, determine that the peer controller of the domain controller is in a sleep state if it is determined that the domain controller has not received any information sent by the peer controller of the domain controller within a preset time period, and execute the deletion process of the remote proxy information stored in the domain controller in the vehicle.

[0126] In one example, the instruction response module 501 includes:

[0127] An information acquisition unit, configured to acquire remote proxy information stored in a domain controller in the vehicle in response to a sleep wake-up instruction for the vehicle;

[0128] The peer determination unit is used to determine the peer controller of the domain controller in the vehicle according to the remote proxy information stored in the domain controller in the vehicle.

[0129] In one example, the remote proxy information includes controller identification information, where the controller identification information is used to characterize a peer controller of the domain controller, and the controller identification information includes at least one of an IP address and a port number; the peer determination unit is specifically configured to:

[0130] A peer controller of the domain controller in the vehicle is determined according to the controller identification information stored in the domain controller in the vehicle.

[0131] In one example, it also includes:

[0132] A message receiving module, used to receive a subscription message sent by the domain controller in the vehicle to the peer controller; wherein the subscription message represents a message of a topic of the domain controller subscribed by the peer controller, and the subscription message includes the number of times the domain controller deletes remote proxy information;

[0133] A times acquisition module, used to acquire the times that the peer controller of the domain controller deletes the remote proxy information;

[0134] The number comparison module is used to delete the remote proxy information stored in the domain controller in the vehicle and update the number of times the domain controller deletes the remote proxy information if the number of times the domain controller deletes the remote proxy information is consistent with the number of times the peer controller of the domain controller deletes the remote proxy information.

[0135] In one example, it also includes:

[0136] A string acquisition module, used to acquire an authentication string located at a preset position from the subscription message; wherein the authentication string includes the number of times the domain controller deletes the remote proxy information;

[0137] The number determination module is used to obtain the number of times the domain controller deletes the remote proxy information from the authentication string according to a preset character arrangement order.

[0138] In one example, the link building module 503 includes:

[0139] A logic determination unit, configured to determine, according to the communication protocol between the domain controller and the peer controller, a link establishment logic between the domain controller and the peer controller, as a target logic based on an association relationship between a preset communication protocol and a link establishment logic; wherein the link establishment logic represents a construction rule of a communication link;

[0140] A link building unit is used to call a preset link building interface according to the target logic, add new remote proxy information to the first initial information and the second initial information respectively, and build a new communication link between the domain controller and the peer controller.

[0141] Figure 6 A structural block diagram of an electronic device provided in an embodiment of the present application, such as Figure 6 As shown, the electronic device includes: a memory 61 and a processor 62; the memory 61 is a memory for storing instructions executable by the processor 62.

[0142] The processor 62 is configured to execute the method provided in the above embodiment.

[0143] The electronic device further includes a receiver 63 and a transmitter 64. The receiver 63 is used to receive instructions and data sent by other devices, and the transmitter 64 is used to send instructions and data to external devices.

[0144] Figure 7It is a block diagram of a terminal device according to an exemplary embodiment. The device 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.

[0145] Device 700 may include one or more of the following components: a processing component 702 , a memory 704 , a power component 706 , a multimedia component 708 , an audio component 710 , an input / output (I / O) interface 712 , a sensor component 714 , and a communication component 716 .

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

[0147] The memory 704 is configured to store various types of data to support operations on the device 700. Examples of such data include instructions for any application or method operating on the device 700, contact data, phone book data, messages, pictures, videos, etc. The memory 704 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.

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

[0149] The multimedia component 708 includes a screen that provides an output interface between the device 700 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 708 includes a front camera and / or a rear camera. When the device 700 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.

[0150] The audio component 710 is configured to output and / or input audio signals. For example, the audio component 710 includes a microphone (MIC), and when the device 700 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 704 or sent via the communication component 716. In some embodiments, the audio component 710 also includes a speaker for outputting audio signals.

[0151] I / O interface 712 provides an interface between processing component 702 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.

[0152] The sensor assembly 714 includes one or more sensors for providing various aspects of status assessment for the device 700. For example, the sensor assembly 714 can detect the open / closed state of the device 700, the relative positioning of components, such as the display and keypad of the device 700, the sensor assembly 714 can also detect the position change of the device 700 or a component of the device 700, the presence or absence of user contact with the device 700, the orientation or acceleration / deceleration of the device 700, and the temperature change of the device 700. The sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 714 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 714 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0153] The communication component 716 is configured to facilitate wired or wireless communication between the device 700 and other devices. The device 700 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 716 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 716 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.

[0154] In an exemplary embodiment, the apparatus 700 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 methods.

[0155] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 704 including instructions, and the instructions can be executed by the processor 720 of the device 700 to perform the above method. 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.

[0156] A non-temporary computer-readable storage medium, when the instructions in the storage medium are executed by a processor of a terminal device, enables the terminal device to execute the above-mentioned terminal device's communication method based on vehicle wake-up.

[0157] The present application also discloses a computer program product, including a computer program, which implements the method described in this embodiment when executed by a processor.

[0158] Various embodiments of the systems and techniques described above in the present application can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs, which can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor, which can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0159] The program code for implementing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or electronic device.

[0160] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0161] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0162] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data electronic device), or a computing system that includes middleware components (e.g., an application electronic device), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0163] The computer system may include a client and an electronic device. The client and the electronic device are generally far away from each other and usually interact through a communication network. The relationship between the client and the electronic device is generated by computer programs running on corresponding computers and having a client-electronic device relationship with each other. The electronic device may be a cloud electronic device, also known as a cloud computing electronic device or a cloud host, which is a host product in a cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services ("Virtual Private Server", or "VPS" for short). The electronic device may also be an electronic device of a distributed system, or an electronic device combined with a blockchain. It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solution disclosed in this application can be achieved, and this document is not limited here.

[0164] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0165] It should be understood that the present application is not limited to the precise 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 application is limited only by the appended claims.

Claims

1. A communication method based on vehicle wake-up, characterized in that: The method is applied to a vehicle, wherein a plurality of domain controllers are deployed in the vehicle, and the domain controllers are used to execute vehicle functions; the method comprises: In response to a sleep wake-up instruction for the vehicle, determining a peer controller of a domain controller in the vehicle; wherein the peer controller represents another domain controller that subscribes to communication with the domain controller; Respectively updating the remote proxy information stored in the domain controller in the vehicle and the remote proxy information stored in the peer controller of the domain controller to obtain first initial information corresponding to the remote proxy information stored in the domain controller and second initial information corresponding to the remote proxy information stored in the peer controller; wherein the remote proxy information represents the current communication link between the domain controller and the peer controller; According to the first initial information and the second initial information, a preset link establishment interface is called to establish a new communication link between the domain controller and the peer controller; wherein the communication link is used for communication between the domain controller and the peer controller.

2. The method according to claim 1, characterized in that The remote proxy information stored in the domain controller in the vehicle and the remote proxy information stored in the peer controller of the domain controller are respectively updated to obtain first initial information corresponding to the remote proxy information stored in the domain controller and second initial information corresponding to the remote proxy information stored in the peer controller, including: Deleting the remote proxy information stored in the domain controller in the vehicle to obtain first initial information corresponding to the remote proxy information stored in the domain controller; wherein the first initial information is a null value; The remote proxy information stored in the peer controller of the domain controller is deleted to obtain the second initial information corresponding to the remote proxy information stored in the peer controller; wherein the second initial information is a null value.

3. The method according to claim 2, characterized in that The domain controller in the vehicle corresponds to a plurality of peer controllers, and the remote proxy information stored in the domain controller in the vehicle corresponds one-to-one to the peer controllers of the domain controller; Deleting the remote proxy information stored in the domain controller in the vehicle includes: Submitting the remote proxy information stored in the domain controller in the vehicle to a preset protocol stack thread in sequence; wherein the preset protocol stack thread is used to cache the information to be deleted; The remote proxy information stored in the domain controller in the vehicle is deleted in the preset protocol stack thread.

4. The method according to claim 3, characterized in that: Deleting the remote proxy information stored in the peer controller of the domain controller includes: If it is determined that the remote proxy information stored in the domain controller in the vehicle is deleted in the preset protocol stack thread, a message information is sent to the opposite end controller corresponding to the remote proxy information stored in the domain controller in the vehicle; wherein the message information represents the deletion status of the remote proxy information; According to the message information, submitting the remote proxy information stored by the opposite end controller to a preset protocol stack thread; The remote proxy information stored in the opposite controller is deleted in the preset protocol stack thread.

5. The method according to claim 4, characterized in that Also includes: If, when deleting the remote proxy information stored in the domain controller in the vehicle, a control instruction is received from a peer controller corresponding to the remote proxy information stored in the domain controller in the vehicle, the control instruction is not executed and the control instruction is cached in a preset protocol stack thread; If the control instruction is in the first position in the preset protocol stack thread, the control instruction is executed and deleted.

6. The method according to claim 2, characterized in that After determining the peer controller of the domain controller in the vehicle, the method further includes: If it is determined that the domain controller has not received any information sent by the peer controller of the domain controller within a preset time period, it is determined that the peer controller of the domain controller is in a dormant state, and the remote proxy information stored in the domain controller in the vehicle is deleted.

7. The method according to claim 1, characterized in that In response to a sleep wake-up instruction for a vehicle, determining a peer controller of a domain controller in the vehicle includes: In response to a sleep wake-up instruction for a vehicle, acquiring remote proxy information stored by a domain controller in the vehicle; According to the remote proxy information stored in the domain controller in the vehicle, a peer controller of the domain controller in the vehicle is determined.

8. The method according to claim 7, characterized in that The remote proxy information includes controller identification information, where the controller identification information is used to identify the peer controller of the domain controller, and the controller identification information includes at least one of an IP address and a port number; Determining a peer controller of the domain controller in the vehicle according to remote proxy information stored in the domain controller in the vehicle includes: A peer controller of the domain controller in the vehicle is determined according to the controller identification information stored in the domain controller in the vehicle.

9. The method according to any one of claims 1 to 8, characterized in that Also includes: Receiving a subscription message sent by the domain controller in the vehicle to the peer controller; wherein the subscription message represents a message of a topic of the domain controller subscribed by the peer controller, and the subscription message includes the number of times the domain controller deletes remote proxy information; Obtaining the number of times the peer controller of the domain controller deletes the remote proxy information; If the number of times the domain controller deletes remote proxy information is consistent with the number of times the peer controller of the domain controller deletes remote proxy information, the remote proxy information stored in the domain controller in the vehicle is deleted, and the number of times the domain controller deletes remote proxy information is updated.

10. The method according to claim 9, characterized in that Also includes: Obtaining an authentication string located at a preset position from the subscription message; wherein the authentication string includes the number of times the domain controller deletes the remote proxy information; The number of times the domain controller deletes the remote proxy information is obtained from the authentication character string according to a preset character arrangement sequence.

11. The method according to claim 1, characterized in that: According to the first initial information and the second initial information, calling a preset link establishment interface to establish a new communication link between the domain controller and the peer controller includes: According to the communication protocol between the domain controller and the peer controller, based on the association relationship between the preset communication protocol and the link building logic, determining the link building logic between the domain controller and the peer controller as the target logic; wherein the link building logic represents the construction rule of the communication link; According to the target logic, the preset link establishment interface is called, new remote proxy information is added to the first initial information and the second initial information respectively, and a new communication link between the domain controller and the peer controller is established.

12. A communication device based on vehicle wake-up, characterized in that: The device is applied to a vehicle, wherein a plurality of domain controllers are deployed in the vehicle, and the domain controllers are used to execute vehicle functions; the device comprises: A command response module, configured to determine a peer controller of a domain controller in the vehicle in response to a sleep wake-up command to the vehicle; wherein the peer controller represents other domain controllers that subscribe to communication with the domain controller; An information updating module, used to update the remote proxy information stored in the domain controller in the vehicle and the remote proxy information stored in the peer controller of the domain controller, respectively, to obtain first initial information corresponding to the remote proxy information stored in the domain controller and second initial information corresponding to the remote proxy information stored in the peer controller; wherein the remote proxy information represents the current communication link between the domain controller and the peer controller; A link building module is used to call a preset link building interface according to the first initial information and the second initial information to build a new communication link between the domain controller and the peer controller; wherein the communication link is used for communication between the domain controller and the peer controller.

13. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1-11.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 11 when executed by a processor.

15. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 11 when being executed by a processor.

Images