Communication methods, devices, electronic equipment, and storage media based on vehicle wake-up

Abstract

This application provides a communication method, apparatus, electronic device, and storage medium based on vehicle wake-up. The method is applied to a vehicle, in which multiple domain controllers are deployed, and the domain controllers are used to execute vehicle functions; it includes: in response to a wake-up command for the vehicle, determining the peer controller of the domain controller in the vehicle; the peer controller represents other domain controllers that have subscribed to communication with the domain controller; updating the remote proxy information stored in the domain controller and the remote proxy information stored in the peer 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; the remote proxy information represents the current communication link between the domain controller and the peer controller; and based on the first initial information and the second initial information, calling a preset connection establishment port to construct a new communication link between the domain controller and the peer controller.

Description

Technical Field

[0001] This application relates to communication technology, and more particularly to a communication method, apparatus, electronic device, and storage medium based on vehicle wake-up. Background Technology

[0002] The vehicle contains multiple domain controllers. When these domain controllers are in sleep mode, the power supply relationships between them cause inconsistencies in their sleep times. This leads to discrepancies between the DDS (Data Distribution Service) information stored by each domain controller and the actual data, thus affecting the efficiency of establishing connections between domain controllers during vehicle wake-up.

[0003] How to efficiently establish a connection when a vehicle is in sleep mode and wakes up, thereby improving communication efficiency, is a problem that urgently needs to be solved. Summary of the Invention

[0004] This application provides a communication method, device, electronic device, and storage medium based on vehicle wake-up, in order to improve communication efficiency.

[0005] In a first aspect, this application provides a vehicle wake-up-based communication method, applied to a vehicle in which multiple domain controllers are deployed, the domain controllers being used to execute vehicle functions; the method includes:

[0006] In response to a sleep / wake command for the vehicle, the peer controller of the domain controller in the vehicle is determined; wherein the peer controller represents other domain controllers that have subscribed to communication with the domain controller.

[0007] The remote agent information stored in the domain controller of the vehicle and the remote agent information stored in the peer controller of the domain controller are updated respectively to obtain the first initial information corresponding to the remote agent information stored in the domain controller and the second initial information corresponding to the remote agent information stored in the peer controller; wherein, the remote agent information represents the current communication link between the domain controller and the peer controller.

[0008] Based on the first initial information and the second initial information, a preset connection establishment port is invoked to construct 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] Secondly, this application provides a vehicle wake-up-based communication device, which is applied to a vehicle in which multiple domain controllers are deployed, and the domain controllers are used to perform vehicle functions; the device includes:

[0010] The instruction response module is used to determine the peer controller of the domain controller in the vehicle in response to a sleep / wake instruction for the vehicle; wherein the peer controller represents other domain controllers that have subscribed to communication with the domain controller.

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

[0012] The link establishment module is used to call a preset link establishment interface based on the first initial information and the second initial information 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.

[0013] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0014] The memory stores computer-executed instructions;

[0015] The processor executes computer execution instructions stored in the memory to implement the method as described in the first aspect.

[0016] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in the first aspect.

[0017] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0018] This application provides a communication method, apparatus, electronic device, and storage medium based on vehicle wake-up. In response to a vehicle's sleep / wake-up command, for any domain controller in the vehicle, the peer controller of that domain controller is determined, and the remote proxy information of both the domain controller and the peer controller is obtained. The remote proxy information stored in both the domain controller and the peer controller is updated to obtain updated first and second initial information. This process clears erroneous DDS information from both the domain controller and the peer controller, preventing erroneous DDS information from affecting communication efficiency. A preset connection establishment port is invoked to establish a link between the domain controller and the peer controller, obtaining a new communication link. This allows the domain controller and the peer controller to re-enter the link establishment logic upon wake-up, achieving rapid link establishment after wake-up and improving the communication efficiency of sleep / wake-up. Attached Figure Description

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

[0020] Figure 1 A flowchart illustrating a vehicle wake-up-based communication method provided in an embodiment of this application;

[0021] Figure 2 A flowchart illustrating a vehicle wake-up-based communication method provided in an embodiment of this application;

[0022] Figure 3 A flowchart illustrating a vehicle wake-up-based communication method provided in an embodiment of this application;

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

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

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

[0026] Figure 7 This is a structural block diagram of an electronic device provided in an embodiment of this application.

[0027] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0029] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0030] In the following description, when referring to the accompanying drawings, the same numbers in different drawings denote the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0031] In the description of this application, it should be understood that the terms "first," "second," "third," etc., are used only to distinguish similar objects and are not necessarily used to describe a specific order or sequence, nor should they be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0032] It should be noted that, due to space limitations, this application specification does not exhaustively list all possible implementation methods. Those skilled in the art, after reading this application specification, should be able to deduce that, as long as the technical features do not contradict each other, any combination of technical features can constitute an optional implementation method. The following provides a detailed description of each embodiment.

[0033] The vehicle contains multiple domain controllers. When the vehicle is in sleep mode, it enters a low-power state. For example, after the cockpit domain controller goes into sleep mode, a program freeze may occur, preserving the current program state and all memory, unloading the network card for Ethernet communication, and stopping program execution. Different domain controllers within the vehicle may have power supply relationships; for example, the vehicle control domain controller can power the cockpit domain controller. Due to these power supply relationships, the sleep times of the domain controllers may differ, causing abnormal DDS (Distributed Data System) information to be saved on both controllers. The saved DDS information may not match the actual state, resulting in slow or unsuccessful connection establishment during wake-up.

[0034] When the vehicle is awakened from sleep mode without interrupting power, it is necessary to quickly update the online / offline status of services based on SOA (Service Oriented Architecture) and establish a DDS connection quickly to restore the vehicle's Ethernet communication.

[0035] This application provides a communication method, device, electronic device, and storage medium based on vehicle wake-up, which aims to solve the above-mentioned technical problems of the prior art.

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

[0037] Figure 1 This is a flowchart illustrating a vehicle wake-up-based communication method according to an embodiment of this application. This method can be executed by a vehicle wake-up-based communication device. The method is applied to a vehicle, which has multiple domain controllers deployed within it. These domain controllers are used to execute vehicle functions. Figure 1 As shown, the method includes the following steps:

[0038] S101. In response to a sleep / wake command for the vehicle, determine the peer controller of the domain controller in the vehicle; wherein the peer controller represents other domain controllers that have subscribed to communication with the domain controller.

[0039] For example, a vehicle can deploy multiple domain controllers, each capable of performing different vehicle functions. These domain controllers may include a cockpit domain controller, a vehicle control domain controller, etc. Domain controllers can subscribe to and publish messages to each other; that is, they can communicate while the vehicle is operating. Vehicle hibernation refers to a low-power state where the entire vehicle operates without interrupting power. For instance, when the cockpit domain controller enters hibernation, its program may freeze, preserving the current program state and all memory, while the network interface card for Ethernet communication is unloaded, and the program stops running.

[0040] After a vehicle enters sleep mode, a wake-up command can be issued at any time to wake it up. Upon receiving the wake-up command, for each domain controller in the vehicle, its peer controller can be determined. A peer controller refers to other domain controllers that have subscribed to communication with that domain controller; one domain controller can have one or more peer controllers. For example, for a cockpit domain controller, the peer controller is the vehicle control domain controller, and for a vehicle control domain controller, the peer controller is the cockpit domain controller. That is, domain controllers and peer controllers can be peers to each other. The peer controllers of each domain controller can be predetermined, and upon receiving the wake-up command, all peer controllers of each domain controller can be directly determined.

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

[0042] For example, each domain controller stores remote agent information, which represents the current communication link between the domain controller and its peer controller. This remote agent information may include the IP address and port number of the peer controller. In other words, the remote agent information can represent the peer controller that has subscribed to the domain controller. For instance, if controller A and controller B are peers, the remote agent information in controller A can represent the communication link between controller A and controller B, and may store the IP address and port number of controller B; similarly, the remote agent information in controller B can represent the communication link between controller A and controller B, and may store the IP address and port number of controller A.

[0043] For each domain controller, the remote agent information stored by that domain controller and the remote agent information stored by its peer controller are both updated. Specifically, the remote agent information stored by the domain controller and the remote agent information stored by its peer controller can be updated. After updating the remote agent information stored by the domain controller, a first initial information is obtained; after updating the remote agent information stored by the peer controller, a second initial information is obtained. For example, the remote agent information can be initialized to obtain processed initial information.

[0044] S103. Based on the first initial information and the second initial information, call the preset connection establishment port 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] For example, after obtaining the first and second initial information, a new link can be established between the domain controller and the peer controller. A pre-configured link establishment port is used to quickly create new communication links between all peers. The pre-configured link establishment port is invoked to send messages between the domain controller and the peer controller at a preset number of messages, achieving rapid link establishment. The preset number of messages also avoids causing a surge in network data.

[0046] During the link establishment process, the first initial information and the second initial information can be updated separately, so that the updated first initial information and the second initial information can represent the new communication link. 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, based on the first initial information and the second initial information, a preset connection establishment port is invoked to construct a new communication link between the domain controller and the peer controller. This includes: determining the connection establishment logic between the domain controller and the peer controller based on the communication protocol between the domain controller and the peer controller, and based on the association between the preset communication protocol and the connection establishment logic, which is the target logic; wherein, the connection establishment logic represents the construction rules of the communication link; based on the target logic, the preset connection establishment port is invoked to add new remote agent information to the first initial information and the second initial information respectively, thereby constructing a new communication link between the domain controller and the peer controller.

[0048] Specifically, the domain controller and the peer controller can communicate using a preset communication protocol. Different communication protocols can correspond to different link establishment logic, which represents the rules for creating the communication link. The communication protocol between the domain controller and the peer controller is determined, and based on the association between the preset communication protocol and the link establishment logic, the link establishment logic between the domain controller and the peer controller is determined as the target logic.

[0049] The system invokes a preset connection establishment interface and employs target logic to add new remote agent information to both the first and second initial information. For example, the IP address of the peer controller of the domain controller is added to the first initial information, and the same IP address is added to the second initial information. The information added to the initial information can differ depending on the target logic. Each domain controller acts as a completely new participant, establishing a connection with the peer. After obtaining the new remote agent information from both the domain controller and the peer controller, a new communication link between them is established.

[0050] The advantage of this setup is that it allows for targeted link establishment for different communication protocols, improving the accuracy of link establishment and enabling rapid communication recovery upon wake-up.

[0051] In this embodiment, in response to a sleep / wake-up command for a vehicle, for any domain controller in the vehicle, the peer controller of that domain controller is determined, and the remote proxy information of the domain controller and the peer controller is obtained. The remote proxy information stored in the domain controller and the remote proxy information stored in the peer controller are updated respectively to obtain updated first and second initial information. This clears erroneous DDS information in the domain controller and the peer controller, preventing erroneous DDS information from affecting communication efficiency. A preset connection establishment port is invoked to establish a link between the domain controller and the peer controller, obtaining a new communication link. This allows the domain controller and the peer controller to re-enter the link establishment logic upon wake-up, achieving rapid link establishment after wake-up and improving the communication efficiency of sleep / wake-up.

[0052] Figure 2 This is a flowchart illustrating a communication method based on vehicle wake-up provided in an embodiment of this application.

[0053] In this embodiment, the remote agent information stored in the domain controller of the vehicle and the remote agent information stored in the peer controller of the domain controller are updated respectively to obtain first initial information corresponding to the remote agent information stored in the domain controller and second initial information corresponding to the remote agent information stored in the peer controller. This includes: deleting the remote agent information stored in the domain controller of the vehicle to obtain the first initial information corresponding to the remote agent information stored in the domain controller; wherein the first initial information is null; and deleting the remote agent information stored in the peer controller of the domain controller to obtain the second initial information corresponding to the remote agent information stored in the peer controller; wherein the second initial information is null.

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

[0055] S201. In response to a sleep / wake command for the vehicle, determine the peer controller of the domain controller in the vehicle; wherein the peer controller represents other domain controllers that have subscribed to communication with the domain controller.

[0056] For example, this step can refer to step S101 above, and will not be repeated here.

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

[0058] For example, updating remote agent information can be done by deleting it. When updating remote agent information, the remote agent information of the domain controller can be updated first, and then the remote agent information of the peer controller can be updated. Alternatively, the remote agent information of both the domain controller and the peer controller can be updated simultaneously.

[0059] In this embodiment, the remote agent information in the domain controller can also be updated first, that is, the remote agent information stored in the domain controller can be deleted. After deletion, the first initial information corresponding to the remote agent information is obtained. If the first initial information is empty, it means that the remote agent 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 agent information stored in the domain controller in the vehicle corresponds one-to-one with the peer controller of the domain controller. The deletion process of the remote agent information stored in the domain controller in the vehicle includes: submitting the remote agent 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 piece of remote agent information stored in the domain controller in the vehicle in the preset protocol stack thread.

[0061] Specifically, a domain controller can correspond to multiple peer controllers, and the domain controller stores the remote agent information corresponding to each peer controller. That is, the remote agent information in the domain controller corresponds one-to-one with the peer controller of that domain controller.

[0062] When deleting remote agent information stored on a domain controller, the information can be sequentially submitted to a pre-defined protocol stack thread. This thread can be used to cache information to be deleted; for example, it could be a garbage collection (GC) thread. The pre-defined protocol stack thread then progressively deletes each piece of remote agent information stored on the domain controller. For instance, it can delete the reader and writer entries, as well as the agent participants represented by the remote agent information (i.e., the peer controller corresponding to the remote agent information). Each deletion of a piece of remote agent information results in an empty initial information set.

[0063] The advantage of this setting is that it submits the deletion event to the GC thread, enabling the automatic deletion of remote proxy information and improving the efficiency of re-establishing the chain.

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

[0065] For example, after a domain controller deletes its stored remote agent information, its peer controller can also delete its stored remote agent information. After deletion, the second initial information is obtained, which is also empty. The remote agent information deleted by the domain controller represents the communication link between the domain controller and the peer controller, and the remote agent information deleted by the peer controller also represents the communication link between the peer controller and the domain controller. That is, the remote agent information deleted by the domain controller corresponds to the remote agent information deleted by the peer controller. If the peer controller still stores remote agent information for other domain controllers, then the peer controller does not need to delete the remote agent information of the other domain controllers.

[0066] In this embodiment, by deleting the remote proxy information of both parties, both parties become new participants and re-enter the chain-building logic, avoiding inconsistencies in the information stored by both parties, improving the efficiency and accuracy of chain building, and thus improving the wake-up efficiency of the vehicle.

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

[0068] Specifically, a domain controller can delete all remote agent information it stores before notifying each peer controller to delete it, or it can send a message to the peer controller corresponding to each deleted remote agent information, notifying that peer controller to delete the remote agent information of that domain controller. For example, if controller A deletes the remote agent information of controller B that it stores, it can then notify controller B to delete the remote agent information of controller A that it stores.

[0069] In other words, for any remote agent information stored by a domain controller, once the remote agent information has been deleted through a preset protocol stack thread, the domain controller can send a message to the peer controller corresponding to that remote agent information. The message indicates the deletion status of the remote agent information; that is, it informs the peer controller that it needs to delete the remote agent information of the domain controller stored by the peer controller. Upon receiving the message, the peer controller determines the remote agent information to be deleted, which is the remote agent information corresponding to the domain controller that sent the message. For example, if controller A sends a message to controller B, controller B needs to delete the remote agent information of controller A that it stores. The remote agent information that the peer controller needs to delete is also submitted to a preset GC thread, where the remote agent information submitted by the peer controller is deleted, thus obtaining empty second initial information.

[0070] The advantage of this setup is that it notifies the peer to delete all proxy information of the participants on this end through message information, thereby achieving consistency of information between the peer and this end, facilitating rapid connection establishment and improving communication efficiency.

[0071] In this embodiment, it further includes: if a control command is received from the peer controller corresponding to the remote agent information stored in the vehicle domain controller when deleting the remote agent information stored in the vehicle domain controller, the control command is not executed and 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 command is executed and deleted.

[0072] Specifically, when deleting remote agent information, the vehicle may receive some control commands. Control commands are instructions issued to functions and services on the vehicle, such as commands to open windows or adjust seats. Therefore, there may be a situation where the remote agent information is being deleted while the execution logic of control commands is being matched.

[0073] If a control command is received from the peer controller corresponding to the remote agent information when deleting remote agent information stored in the domain controller, the control command will not be executed immediately. Instead, it can be cached in a preset protocol stack thread. That is, the execution of the command and the deletion of the remote agent information are submitted to the same thread for processing. Each received control command can be placed at the end of the thread. As the events in the thread complete, if the control command is at the first position in the preset protocol stack thread, it can be executed and then deleted from the thread.

[0074] The advantage of this setup is that when concurrent control commands occur during the deletion of remote proxy information, the control commands and the deletion task can be submitted to the same thread for processing, ensuring the synchronization of the protocol stack, avoiding confusion caused by executing control commands while deleting, and improving communication accuracy.

[0075] In this embodiment, after determining the peer controller of the vehicle's domain controller, the method further includes: if it is determined that the domain controller has not received information from 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 sleep state, and the remote agent information stored in the vehicle's domain controller is deleted.

[0076] Specifically, before deleting remote agent information, ensure that both the domain controller and the peer controller are in sleep mode. Upon receiving a sleep / wake command, the domain controller can verify its own sleep status. To confirm the peer controller's sleep status, a pre-set time period is used. After identifying the peer controller, check if any information is received from that peer controller within this pre-set time period. For example, the pre-set time period might be 8 seconds.

[0077] If a message is received from the peer controller, it is determined that the peer controller is not in a dormant state, and the remote agent information of the peer controller cannot be deleted. The system continues to check whether more messages are received from the peer controller within a preset time period, until no more messages are received. If no messages are 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 agent information of the peer controller stored in the domain controller can be deleted.

[0078] The advantage of this setup is that the controllers may have different power supplies, resulting in inconsistent sleep times. This setup ensures that both domain controllers are in sleep mode, avoiding interference with the normal operation of the non-sleep domain controllers and improving communication efficiency and accuracy.

[0079] S204. Based on the first initial information and the second initial information, call the preset connection establishment port 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] For example, this step can refer to step S103 above, and will not be repeated here.

[0081] In this embodiment, in response to a sleep / wake-up command for a vehicle, for any domain controller in the vehicle, the peer controller of that domain controller is determined, and the remote proxy information of the domain controller and the peer controller is obtained. The remote proxy information stored in the domain controller and the remote proxy information stored in the peer controller are updated respectively to obtain updated first and second initial information. This clears erroneous DDS information in the domain controller and the peer controller, preventing erroneous DDS information from affecting communication efficiency. A preset connection establishment port is invoked to establish a link between the domain controller and the peer controller, obtaining a new communication link. This allows the domain controller and the peer controller to re-enter the link establishment logic upon wake-up, achieving rapid link establishment after wake-up and improving the communication efficiency of sleep / wake-up.

[0082] Figure 3 This is a flowchart illustrating a communication method based on vehicle wake-up provided in an embodiment of this application.

[0083] In this embodiment, in response to a sleep / wake command for the vehicle, determining the peer controller of the domain controller in the vehicle includes: in response to a sleep / wake command for the vehicle, obtaining remote agent information stored in the domain controller in the vehicle; and determining the peer controller of the domain controller in the vehicle based on the remote agent information stored in the domain controller in the vehicle.

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

[0085] S301. In response to a wake-up command for the vehicle, obtain the remote agent information stored in the domain controller of the vehicle.

[0086] For example, a vehicle can receive a vehicle wake-up signal from the MCU (Microcontroller Unit) at any time after it has gone into sleep mode; that is, a sleep-wake command. Upon receiving the sleep-wake command for the vehicle, for any domain controller in the vehicle, all remote agent information stored in that domain controller is determined.

[0087] S302. Based on the remote agent information stored in the domain controller in the vehicle, determine the peer controller of the domain controller in the vehicle.

[0088] For example, after obtaining all remote agent information stored in the domain controller, all peer controllers corresponding to that domain controller can be obtained. Each remote agent information in the domain controller corresponds to one peer controller. For example, the remote agent information may contain an identifier that can identify a peer controller. In this embodiment, by determining the remote agent information, domain controllers that communicate with each other can be identified, thereby re-establishing the link between the two parties and enabling them to resume communication.

[0089] In this embodiment, the remote agent information includes controller identification information, which is used to characterize the peer controller of the domain controller. The controller identification information includes at least one of IP address and port number. Determining the peer controller of the domain controller in the vehicle based on the remote agent information stored in the domain controller in the vehicle includes: determining the peer controller of the domain controller in the vehicle based on the controller identification information stored in the domain controller in the vehicle.

[0090] Specifically, the remote agent information may include controller identification information, which can be used to identify 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 agent information, and based on this information, a domain controller corresponding to that controller identification information is determined as the peer controller. For example, each IP address corresponds to a unique domain controller; based on the IP address, the corresponding domain controller can be found, thus identifying the peer controller.

[0091] The advantage of this setup is that it allows for precise identification of each peer controller, avoids link establishment errors, and improves the efficiency and accuracy of re-communication.

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

[0093] For example, this step can refer to step S102 above, and will not be repeated here.

[0094] In this embodiment, the method further 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 to by the peer controller, and the subscription message includes the number of times the domain controller deletes remote agent information; obtaining the number of times the peer controller of the domain controller deletes remote agent information; if the number of times the domain controller deletes remote agent information is consistent with the number of times the peer controller of the domain controller deletes remote agent information, then the remote agent information stored in the domain controller in the vehicle is deleted, and the number of times the domain controller deletes remote agent information is updated.

[0095] Specifically, before deleting remote agent information from a domain controller and a peer controller, the domain controller can send a subscription message to the peer controller. The subscription message represents a message from a topic on the domain controller that the peer controller is subscribed to, and can include the number of times the domain controller has deleted the remote agent information from that peer controller. Each domain controller must store the number of times it has deleted the remote agent information from each peer controller, and the sent subscription message is designated as DATA(P), meaning DATA(P) contains the number of times the domain controller has deleted the remote agent information from the peer controller.

[0096] The peer controller can also store the number of times it has deleted the remote agent information of the domain controller. The number of times the domain controller deleted the remote agent information of the peer controller is determined as the first count; the number of times the peer controller deleted the remote agent information of the domain controller is determined as the second count. When the domain controller sends a subscription message, indicating that it wants to delete the remote agent information of the peer controller, the first count and the second count are retrieved. It is then determined whether the first count and the second count are the same. If they are the same, the domain controller can proceed with the deletion of the remote agent information of the peer controller and update the first count, for example, by incrementing it by one.

[0097] If the first count and the second count are inconsistent, the smaller value is determined. If the smaller value is the second count, the remote agent information stored in the peer controller of the domain controller is first deleted, and the second count is updated. For example, the second count can be incremented by one to make the first count consistent with the second count. If the smaller value is the first count, no processing is performed until the peer controller becomes the local end and the domain controller becomes the peer end, then deletion processing is performed. For example, if the deletion count in controller A is 1 less than the deletion count in controller B, when the deletion count in controller A is used as the first count, no processing is performed; when the deletion count in controller A is used as the second count, the remote agent information corresponding to controller B stored in controller A is deleted, and the second count is incremented by one.

[0098] The advantage of this setup is that each domain controller stores the number of times it has performed a deletion operation, which is used for count verification, avoiding communication errors between the two parties and improving the efficiency of link establishment.

[0099] In this embodiment, the number of deletions can be checked periodically. When two deletion counts are found to be inconsistent, deletion can be performed to ensure that the deletion counts are consistent. When the two deletion counts are consistent, frequent deletion operations are not required, thus avoiding frequent deletions from affecting communication efficiency.

[0100] In this embodiment, the method further 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 remote agent information; and obtaining the number of times the domain controller deletes remote agent information from the authentication string according to a preset character arrangement order.

[0101] Specifically, an authentication string, called a token, can be set in the subscription message. The token can be located at a preset position in the subscription message. The token can be designed as a string array, and the order of the characters in the token can be preset. That is, the specific characters in the token can be predefined to store the deletion count. For example, bytes 45 to 50 of the token can be used to store the deletion count.

[0102] After receiving the subscription message, the token is retrieved from the subscription message. Then, according to the preset character arrangement order, the position of the character storing the deletion count in the token is determined, thereby enabling the domain controller to retrieve the number of times it has deleted the remote agent information of the peer controller from the token.

[0103] The advantage of this setting is that it defines how many bytes in the TOKEN are used to store the deletion count, making it easier to obtain the deletion count for verification, improving the accuracy and efficiency of count verification, and thus improving the accuracy and efficiency of re-establishing the chain.

[0104] S304. Based on the first initial information and the second initial information, call the preset connection establishment port 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] For example, this step can refer to step S103 above, and will not be repeated here.

[0106] In this embodiment, in response to a sleep / wake-up command for a vehicle, for any domain controller in the vehicle, the peer controller of that domain controller is determined, and the remote proxy information of the domain controller and the peer controller is obtained. The remote proxy information stored in the domain controller and the remote proxy information stored in the peer controller are updated respectively to obtain updated first and second initial information. This clears erroneous DDS information in the domain controller and the peer controller, preventing erroneous DDS information from affecting communication efficiency. A preset connection establishment port is invoked to establish a link between the domain controller and the peer controller, obtaining a new communication link. This allows the domain controller and the peer controller to re-enter the link establishment logic upon wake-up, achieving rapid link establishment after wake-up and improving the communication efficiency of sleep / wake-up.

[0107] Figure 4 This is a structural block diagram of a vehicle wake-up-based communication device provided in an embodiment of this disclosure. For ease of explanation, only the parts relevant to the embodiment of this disclosure are shown. The device is applied to a vehicle, which has multiple domain controllers deployed within it. These domain controllers are used to execute vehicle functions. (Refer to...) Figure 4 The vehicle wake-up-based communication device 400 includes: an instruction response module 401, an information update module 402, and a connection establishment module 403.

[0108] The instruction response module 401 is used to determine the peer controller of the domain controller in the vehicle in response to a sleep / wake instruction for the vehicle; wherein the peer controller represents other domain controllers that have subscribed to communication with the domain controller.

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

[0110] The link establishment module 403 is used to call a preset link establishment interface based on the first initial information and the second initial information 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.

[0111] Figure 5 A structural block diagram of a vehicle wake-up-based communication device provided in this disclosure embodiment is shown below. Figure 5 As shown, the vehicle wake-up-based communication device 500 includes an instruction response module 501, an information update module 502, and a connection establishment module 503. The information update module 502 includes a first deletion unit 5021 and a second deletion unit 5022.

[0112] The first deletion unit 5021 is used to delete the remote agent information stored in the domain controller of the vehicle to obtain the first initial information corresponding to the remote agent information stored in the domain controller; wherein, the first initial information is a null value.

[0113] The second deletion unit 5022 is used to delete the remote agent information stored by the peer controller of the domain controller to obtain the second initial information corresponding to the remote agent information stored by 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 agent information stored in the domain controller in the vehicle corresponds one-to-one with the peer controller of the domain controller; the first deletion unit 5021 is specifically used for:

[0115] The remote agent information stored in the vehicle's domain controller is sequentially submitted to a preset protocol stack thread; wherein, the preset protocol stack thread is used to cache information to be deleted;

[0116] The remote agent information stored in the vehicle's domain controller is deleted from the preset protocol stack thread.

[0117] In one example, the second deletion unit 5022 is specifically used for:

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

[0119] Based on the message information, the remote proxy information stored by the peer controller is submitted to the preset protocol stack thread;

[0120] The remote proxy information stored by the peer controller is deleted from the preset protocol stack thread.

[0121] One example also includes:

[0122] The instruction caching module is used to prevent the execution of a control instruction from the peer controller corresponding to the remote agent information stored in the vehicle's domain controller when the remote agent information stored in the vehicle's domain controller is deleted, and to cache the control instruction in a preset protocol stack thread.

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

[0124] One example also includes:

[0125] The hibernation determination module is used to determine that the peer controller of the domain controller is in hibernation state after determining the peer controller of the domain controller in the vehicle. If it is determined that the domain controller has not received information from the peer controller of the domain controller within a preset time period, the peer controller of the domain controller is in hibernation state, and the module performs the deletion process on the remote agent information stored in the domain controller of the vehicle.

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

[0127] The information acquisition unit is used to acquire remote agent information stored in the domain controller of the vehicle in response to the vehicle's sleep / wake command.

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

[0129] In one example, the remote agent information includes controller identification information, which is used to characterize the peer controller of the domain controller. The controller identification information includes at least one of IP address and port number; the peer determination unit is specifically used for:

[0130] The peer controller of the domain controller in the vehicle is determined based on the controller identification information stored in the domain controller in the vehicle.

[0131] One example also includes:

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

[0133] The count acquisition module is used to acquire the number of times the peer controller of the domain controller has deleted remote agent information;

[0134] The count comparison module is used to delete the remote agent information stored in the domain controller in the vehicle and update the count of the domain controller deleting remote agent information if the number of times the domain controller deletes remote agent information is the same as the number of times the peer controller of the domain controller deletes remote agent information.

[0135] One example also includes:

[0136] The string acquisition module is used to acquire the authentication string located at a preset position from the subscription message; wherein, the authentication string includes the number of times the domain controller has deleted remote agent information;

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

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

[0139] The logic determination unit is used to determine the connection establishment logic between the domain controller and the peer controller based on the communication protocol between the domain controller and the peer controller, and based on the preset association relationship between the communication protocol and the connection establishment logic, as the target logic; wherein, the connection establishment logic represents the construction rules of the communication link;

[0140] The link establishment unit is used to call a preset link establishment interface according to the target logic, add new remote agent information to the first initial information and the second initial information respectively, and establish 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 this application, such as... Figure 6 As shown, the electronic device includes: a memory 61 and a processor 62; the memory 61 is a memory used to store instructions executable by the processor 62.

[0142] The processor 62 is configured to perform the methods provided in the above embodiments.

[0143] The electronic device also 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 7This is a block diagram illustrating a terminal device according to an exemplary embodiment. The device may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.

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

[0146] Processing component 702 typically controls the overall operation of device 700, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 702 may include one or more modules to facilitate interaction between processing component 702 and other components. For example, processing component 702 may include a multimedia module to facilitate interaction between multimedia component 708 and processing component 702.

[0147] Memory 704 is configured to store various types of data to support the operation of device 700. Examples of this data include instructions for any application or method operating on device 700, contact data, phonebook data, messages, pictures, videos, etc. 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 storage, flash memory, magnetic disk, or optical disk.

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

[0149] 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 touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 708 includes a front-facing camera and / or a rear-facing camera. When the device 700 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0150] Audio component 710 is configured to output and / or input audio signals. For example, audio component 710 includes a microphone (MIC) configured to receive external audio signals when device 700 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 704 or transmitted via communication component 716. In some embodiments, 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, home buttons, volume buttons, power buttons, and lock buttons.

[0152] Sensor assembly 714 includes one or more sensors for providing state assessments of various aspects of device 700. For example, sensor assembly 714 may detect the on / off state of device 700, the relative positioning of components such as the display and keypad of device 700, changes in the position of device 700 or a component of device 700, the presence or absence of user contact with device 700, the orientation or acceleration / deceleration of device 700, and temperature changes of device 700. Sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 714 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 714 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0153] Communication component 716 is configured to facilitate wired or wireless communication between device 700 and other devices. Device 700 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 716 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 716 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may 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 methods described above.

[0155] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 704 including instructions, which can be executed by a processor 720 of the device 700 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0156] A non-transitory computer-readable storage medium, wherein when instructions in the storage medium are executed by a processor of a terminal device, the terminal device is enabled to perform the aforementioned vehicle wake-up-based communication method of the terminal device.

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

[0158] Various embodiments of the systems and technologies described above in this 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-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0159] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or electronic device.

[0160] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, 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 for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, 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 sound input, voice input, or tactile input).

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

[0163] Computer systems can include client and electronic devices. Clients and electronic devices are generally geographically separated and typically interact via communication networks. The client-electronic device relationship is created by computer programs running on the respective computers and having a client-electronic device relationship with each other. The electronic device can be a cloud electronic device, also known as a cloud computing electronic device or cloud host, a host product within the cloud computing service system, addressing the shortcomings of traditional physical hosts and VPS services ("Virtual Private Server," or simply "VPS") in terms of management difficulty and weak business scalability. The electronic device can also be an electronic device in a distributed system or an electronic device incorporating blockchain technology. It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this application is achieved, and this is not limited herein.

[0164] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0165] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this 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 multiple domain controllers are deployed in the vehicle, and the domain controllers are used to perform vehicle functions; the method includes: In response to a sleep / wake command for the vehicle, the peer controller of the domain controller in the vehicle is determined; wherein the peer controller represents other domain controllers that have subscribed to communication with the domain controller. The remote agent information stored in the domain controller of the vehicle and the remote agent information stored in the peer controller of the domain controller are updated respectively to obtain the first initial information corresponding to the remote agent information stored in the domain controller and the second initial information corresponding to the remote agent information stored in the peer controller; wherein, the remote agent information represents the current communication link between the domain controller and the peer controller. Based on the first initial information and the second initial information, a preset connection establishment port is invoked to construct 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; The remote agent information stored in the domain controller of the vehicle and the remote agent information stored in the peer controller of the domain controller are updated respectively to obtain first initial information corresponding to the remote agent information stored in the domain controller and second initial information corresponding to the remote agent information stored in the peer controller, including: The remote agent information stored in the domain controller of the vehicle is deleted to obtain the first initial information corresponding to the remote agent information stored in the domain controller; wherein, the first initial information is a null value; The remote agent information stored in the peer controller of the domain controller is deleted to obtain the second initial information corresponding to the remote agent information stored in the peer controller; wherein, the second initial information is a null value.

2. The method according to claim 1, characterized in that, The domain controller in the vehicle corresponds to multiple peer controllers, and the remote agent information stored in the domain controller in the vehicle corresponds one-to-one with the peer controller of the domain controller. The deletion process for the remote agent information stored in the vehicle's domain controller includes: The remote agent information stored in the vehicle's domain controller is sequentially submitted to a preset protocol stack thread; wherein, the preset protocol stack thread is used to cache information to be deleted; The remote agent information stored in the vehicle's domain controller is deleted from the preset protocol stack thread.

3. The method according to claim 2, characterized in that, The deletion process for the remote agent information stored in the peer controller of the domain controller includes: If it is determined that the remote agent information stored in the vehicle domain controller is being deleted in the preset protocol stack thread, then a message is sent to the peer controller corresponding to the remote agent information stored in the vehicle domain controller; wherein, the message represents the deletion status of the remote agent information. Based on the message information, the remote proxy information stored by the peer controller is submitted to the preset protocol stack thread; The remote proxy information stored by the peer controller is deleted from the preset protocol stack thread.

4. The method according to claim 3, characterized in that, Also includes: If a control command is received from the peer controller corresponding to the remote agent information stored in the vehicle domain controller when deleting the remote agent information stored in the vehicle domain controller, the control command will not be executed, and the control command will be cached in a preset protocol stack thread. If the control instruction is located at the first position in the preset protocol stack thread, then the control instruction is executed and deleted.

5. The method according to claim 1, characterized in that, After determining the peer controller of the vehicle's domain controller, the process further includes: If it is determined that the domain controller has not received any information from the peer controller within a preset time period, then it is determined that the peer controller is in a sleep state, and the process of deleting the remote agent information stored in the domain controller in the vehicle is executed.

6. The method according to claim 1, characterized in that, In response to a sleep / wake command for the vehicle, the peer controller of the vehicle's domain controller is determined, including: In response to a sleep / wake command for the vehicle, the remote agent information stored in the domain controller of the vehicle is obtained; Based on the remote agent information stored in the domain controller in the vehicle, the peer controller of the domain controller in the vehicle is determined.

7. The method according to claim 6, characterized in that, The remote agent information includes controller identification information, which is used to characterize the peer controller of the domain controller. The controller identification information includes at least one of IP address and port number. Based on the remote agent information stored in the domain controller of the vehicle, the peer controller of the domain controller in the vehicle is determined, including: The peer controller of the domain controller in the vehicle is determined based on the controller identification information stored in the domain controller in the vehicle.

8. The method according to any one of claims 1-7, characterized in that, Also includes: The system receives a subscription message sent by the domain controller in the vehicle to the peer controller; wherein the subscription message represents a message about a topic of the domain controller that the peer controller has subscribed to, and the subscription message includes the number of times the domain controller has deleted remote agent information; Obtain the number of times the peer controller of the domain controller has deleted remote agent information; If the number of times the domain controller deletes remote agent information is the same as the number of times the peer controller of the domain controller deletes remote agent information, then the remote agent information stored in the domain controller in the vehicle is deleted, and the number of times the domain controller deletes remote agent information is updated.

9. The method according to claim 8, characterized in that, Also includes: Obtain the authentication string located at a preset position from the subscription message; wherein, the authentication string includes the number of times the domain controller has deleted the remote agent information; Based on a preset character arrangement order, the number of times the domain controller has deleted remote agent information is obtained from the authentication string.

10. The method according to claim 1, characterized in that, Based on the first initial information and the second initial information, a preset connection establishment port is invoked to construct a new communication link between the domain controller and the peer controller, including: Based on the communication protocol between the domain controller and the peer controller, and based on the association between the preset communication protocol and the link establishment logic, the link establishment logic between the domain controller and the peer controller is determined as the target logic; wherein, the link establishment logic represents the construction rules of the communication link; According to the target logic, a preset connection establishment interface is invoked, and new remote agent information is added to the first initial information and the second initial information respectively to build a new communication link between the domain controller and the peer controller.

11. A communication device based on vehicle wake-up, characterized in that, The device is applied to a vehicle, wherein multiple domain controllers are deployed in the vehicle, and the domain controllers are used to perform vehicle functions; the device includes: The instruction response module is used to determine the peer controller of the domain controller in the vehicle in response to a sleep / wake instruction for the vehicle; wherein the peer controller represents other domain controllers that have subscribed to communication with the domain controller. The information update module is used to update the remote agent information stored in the domain controller of the vehicle and the remote agent information stored in the peer controller of the domain controller, respectively, to obtain the first initial information corresponding to the remote agent information stored in the domain controller and the second initial information corresponding to the remote agent information stored in the peer controller; wherein, the remote agent information represents the current communication link between the domain controller and the peer controller. The link establishment module is used to call a preset link establishment interface based on the first initial information and the second initial information 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. The information update module includes: The first deletion unit is used to delete the remote agent information stored in the domain controller of the vehicle to obtain the first initial information corresponding to the remote agent information stored in the domain controller; wherein, the first initial information is a null value. The second deletion unit is used to delete the remote agent information stored by the peer controller of the domain controller to obtain the second initial information corresponding to the remote agent information stored by the peer controller; wherein the second initial information is a null value.

12. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-10.

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

14. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-10.

Images