Communication task processing method and device, equipment, storage medium and program product

Abstract

The invention relates to a communication task processing method and device, equipment, a storage medium and a program product, and the method comprises the steps: obtaining a first message table and a second message table preset by a target communication node in response to a to-be-processed communication task, the first message table being configured with independent communication parameters required by the target communication node, and the second message table being configured with independent communication parameters required by the target communication node; common communication parameters of a plurality of communication nodes are configured in the second message table, and the plurality of communication nodes comprise the target communication node; and processing the communication task according to the first message table and the second message table. According to the method and the device, each node only needs to call own unique communication parameters and a shared public parameter set when processing the communication task, and does not need to store all communication parameters of all nodes, so that the memory occupation of each communication node is reduced, and the resource utilization rate is improved.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication task processing method, apparatus, device, storage medium, and program product. Background Technology

[0002] In intelligent vehicles, the Controller Area Network (CAN) bus, as a core communication protocol, is widely used for data interaction between various electronic control units (ECUs) within the vehicle. Taking the four door control units (DCUs) of an intelligent vehicle as an example, these controllers typically need to communicate in real time with other modules (such as the body control module, door lock module, sensors, etc.) via the CAN bus.

[0003] The four door controllers typically use the same hardware architecture and basic software framework. The software framework of the door controllers usually adopts a statically configured CAN protocol stack architecture. For example, the four door controllers share the same set of static message tables, which use preset communication parameters of the door controllers.

[0004] In real-world scenarios, due to the different installation locations of the four car doors, the communication parameters required between different door controllers may also differ. For example, the front door controller may need to control the rearview mirror motor, while the rear door controller may not. Therefore, based on the installation location of the door controllers (e.g., front left, front right, rear left, rear right), all CAN communication parameters for the four door controllers need to be pre-set in a static message table. Each door controller needs to store a copy of this static message table. During operation, the controller will use its own subset of communication parameters based on its installation location, while the other three sets of communication parameters will be idle, resulting in resource waste. Especially in multi-node co-line scenarios, because each door controller needs to pre-store the communication parameters of all door controllers, the amount of redundant data grows exponentially, leading to a significant increase in memory usage and very low resource utilization. Summary of the Invention

[0005] To overcome the problems existing in related technologies, this disclosure provides a communication task processing method, apparatus, device, storage medium, and program product, which enables each node to only call its own unique communication parameters and a shared public parameter set when processing communication tasks, without having to store all the communication parameters of all nodes, thereby reducing the memory occupation of each communication node and improving resource utilization.

[0006] In a first aspect, embodiments of this disclosure provide a communication task processing method, comprising: in response to a communication task to be processed, obtaining a first message table and a second message table preset by a target communication node, wherein the first message table is configured with unique communication parameters required by the target communication node, and the second message table is configured with shared communication parameters of multiple communication nodes, the multiple communication nodes including the target communication node; and processing the communication task according to the first message table and the second message table.

[0007] Secondly, embodiments of this disclosure provide a communication task processing apparatus, comprising: an acquisition module, configured to acquire, in response to a communication task to be processed, a first message table and a second message table preset by a target communication node, wherein the first message table is configured with unique communication parameters required by the target communication node, and the second message table is configured with shared communication parameters of multiple communication nodes, the multiple communication nodes including the target communication node; and a processing module, configured to process the communication task according to the first message table and the second message table.

[0008] Thirdly, embodiments of this disclosure provide a vehicle, including:

[0009] At least one processor; and

[0010] A memory that is communicatively connected to the at least one processor;

[0011] The memory stores instructions executable by the at least one processor, which is configured to execute the instructions to implement the method described in any of the above aspects.

[0012] Fourthly, embodiments of this disclosure provide an electronic device, including:

[0013] At least one processor; and

[0014] A memory that is communicatively connected to the at least one processor;

[0015] The memory stores instructions executable by the at least one processor, which is configured to execute the instructions to implement the method described in any of the above aspects.

[0016] Fifthly, embodiments of this disclosure provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the method described in any of the above aspects.

[0017] Sixthly, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the methods described in any of the above aspects.

[0018] The communication task processing method, apparatus, device, storage medium, and program product provided in this disclosure splits a traditional single static message table into a first message table for a target communication node and a second message table for multiple communication nodes. The first message table stores the unique communication parameters of the target node, and the second message table stores the common communication parameters of multiple communication nodes. This allows each node to only call its own unique communication parameters and a shared set of common parameters when processing communication tasks, without having to store all communication parameters of all collinear nodes. This avoids storing redundant communication parameters in a single node, thereby significantly reducing the memory usage of each communication node, solving the problem of storage resource waste caused by parameter redundancy in multi-node scenarios, and improving resource utilization. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It will be apparent that the drawings described below are some embodiments of this disclosure, and that those skilled in the art can derive other drawings from these drawings without any inventive effort.

[0020] Figure 1 A flowchart illustrating a communication task processing method provided in an embodiment of this disclosure;

[0021] Figure 2 This is a schematic diagram of an application communication architecture for a communication task processing method provided in an embodiment of the present disclosure;

[0022] Figure 3 This is a schematic diagram of a communication architecture application process provided in an embodiment of the present disclosure;

[0023] Figure 4 This is a schematic diagram of the structure of a communication task processing device provided in an embodiment of the present disclosure;

[0024] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure;

[0025] Figure 6 This is a schematic diagram illustrating an application scenario of a communication task processing system provided in an embodiment of this disclosure;

[0026] Figure 7 This is a schematic diagram of the structure of a vehicle provided in an embodiment of the present disclosure.

[0027] The accompanying drawings have illustrated specific embodiments of this disclosure, 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 concepts of this disclosure to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0028] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0029] In this article, the term "and / or" is used to describe the relationship between related objects. Specifically, it means that there can be three kinds of relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, or B exists alone.

[0030] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0031] In order to clearly describe the technical solutions of the embodiments of this disclosure, the terms involved in this disclosure are first defined as follows:

[0032] CAN: Controller Area Network.

[0033] ID: Identity document, identification information.

[0034] ECU: Electronic Control Unit.

[0035] CAN node: refers to a node in the CAN controller. A CAN node can be connected to one CAN bus.

[0036] CAN IF: CAN Interface, CAN interface layer.

[0037] COM CAN: Communication CAN, a local area network for communication controllers.

[0038] GPIO: General-Purpose Input / Output.

[0039] DCM: Data Communication Module.

[0040] The communication task processing method of this disclosure can be applied to any communication field where multiple nodes are collinear.

[0041] In intelligent vehicles, the Controller Area Network (CAN) bus, as a core communication protocol, is widely used for data interaction between various electronic control units (ECUs) within the vehicle. Taking the four door controllers of an intelligent vehicle as an example, these controllers typically need to communicate in real time with other modules (such as the body control module, door lock module, sensors, etc.) via the CAN bus.

[0042] The four door controllers typically use the same hardware architecture and basic software framework. The software framework of the door controllers usually adopts a statically configured CAN protocol stack architecture. For example, the four door controllers share the same set of static message tables, which use preset communication parameters for the four door controllers.

[0043] Because the four doors are installed in different locations, the communication parameters required between the different door controllers may also differ. For example, the front door controller may need to control the rearview mirror motor, while the rear door controller may not. Therefore, based on the installation location of the door controllers (e.g., front left, front right, rear left, rear right), all CAN communication parameters for the four door controllers need to be pre-set in a static message table. Each door controller needs to store a copy of this static message table. During operation, the controller will use its own subset of communication parameters based on its installation location, while the other three sets of communication parameters will be idle, resulting in wasted resources. Especially in multi-node co-line scenarios, because each door controller needs to pre-store the communication parameters of all door controllers, the amount of redundant data grows exponentially, leading to a significant increase in memory usage and very low resource utilization.

[0044] To address at least one of the aforementioned problems, this disclosure provides a communication task processing scheme. By splitting a traditional single static message table into a first message table for a target communication node and a second message table for multiple communication nodes, the first message table stores the unique communication parameters of the target node, while the second message table stores the shared communication parameters of multiple communication nodes. This allows each node to only call its own unique communication parameters and a shared set of common parameters when processing communication tasks, without needing to store all communication parameters of all nodes. This avoids storing redundant communication parameters in a single node, significantly reducing the memory usage of each communication node, solving the problem of wasted storage resources due to parameter redundancy in multi-node scenarios, and improving resource utilization.

[0045] The following detailed description of some embodiments of this disclosure is provided in conjunction with the accompanying drawings. Where there is no conflict between the embodiments, the following embodiments and features can be combined with each other. Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0046] Please refer to Figure 1 This is a communication task processing method according to an embodiment of the present disclosure, which can be made by... Figure 5 The electronic device 5 shown is used to perform this function and can be applied to... Figure 6 In the communication task processing application scenario shown, the goal is to reduce the memory footprint of each communication node and improve resource utilization. This embodiment uses a terminal as the execution end as an example, and the method includes the following steps:

[0047] Step 101: In response to the communication task to be processed, obtain the first message table and the second message table preset by the target communication node. The first message table is configured with the unique communication parameters required by the target communication node, and the second message table is configured with the common communication parameters of multiple communication nodes, including the target communication node.

[0048] In this step, the communication node can refer to a CAN node, and multiple communication nodes can co-connect. Unique communication parameters are those specifically required by the target communication node when processing communication tasks; these parameters are not shared with other nodes. Shared communication parameters are those used by multiple nodes and can be shared. By dividing communication parameters into unique communication parameters for the target communication node and shared communication parameters for multiple communication nodes, each node only needs to call its own unique communication parameters and a shared set of common parameters when processing communication tasks. It does not need to store all communication parameters of all co-connected nodes, avoiding redundant communication parameters stored by a single node. This significantly reduces the memory footprint of each communication node and improves resource utilization.

[0049] In one embodiment, the unique communication parameters include one or more of the following: message identifier, node identifier, and message filtering rules; the common communication parameters include one or more of the following: physical layer parameters, data frame format, and communication baud rate.

[0050] In this embodiment, structured hierarchical management of configuration data is achieved by scientifically dividing communication parameters into unique communication parameters closely related to node functions (such as message identifiers, node identifiers, and filtering rules) and shared communication parameters bound to network physical characteristics and communication specifications (such as physical layer parameters, data frame formats, and baud rates). On the one hand, the independent configuration of unique communication parameters enables each communication node to accurately adapt to its specific role and message processing needs, ensuring functional differentiation and flexibility. On the other hand, the centralized configuration of shared communication parameters ensures strict consistency and interoperability of all communication nodes in the same network at the physical layer and data link layer, fundamentally avoiding communication failures or conflicts caused by inconsistent basic parameters. With this division, each communication node only needs to store one set of common parameters and its own unique parameters, which not only greatly reduces the storage burden on each node, but also improves the clarity and maintainability of the configuration through parameter classification management. This allows network adjustments (such as uniformly modifying the baud rate) to take effect globally simply by updating the shared communication parameter table, significantly enhancing the overall reliability and engineering applicability of the system.

[0051] Step 102: Process the communication task according to the first message table and the second message table.

[0052] In this step, when the target communication node processes a communication task, the target parameters required for the communication task are first determined. The target parameters may include communication parameters unique to the target communication node itself and / or communication parameters shared with other co-line nodes. The unique communication parameters required for this communication task can be read directly from the first message table, and the shared communication parameters required for this communication task can be read from the second message table. The communication task is processed based on the read communication parameters. This allows each node to only call its own unique communication parameters and a shared set of common parameters when processing a communication task, without having to store all the communication parameters of all co-line nodes. This avoids storing redundant communication parameters on a single node and improves resource utilization.

[0053] In one embodiment, the communication task includes a processing task related to receiving messages; unique communication parameters include unique receiving parameters required by the target communication node to process the received messages, and shared communication parameters include shared receiving parameters required by multiple communication nodes to process the received messages; processing the communication task according to a first message table and a second message table includes: processing the received messages according to the unique receiving parameters and the shared receiving parameters.

[0054] In this embodiment, the communication task to be processed can be the processing of received messages. Unique receiving parameters refer to the unique parameters required by the target communication node to process a specific received message, such as a specific received message ID, node identifier, and node-specific filtering rules. Taking a door controller as an example, each door controller needs to listen for instruction or status request messages specifically sent to it. Therefore, the target address or message ID assigned to the left front door controller, right front door controller, left rear door controller, and right rear door controller must be unique and different. The main control unit uses these specific message IDs to send control commands (such as "unlock the left front door" or "lower the right rear window") to each door. On the bus network, each door controller, as an independent communication node, must have a unique logical address or node identifier to identify the sender and receiver at the network layer, ensuring that messages can be correctly routed to the target door controller and avoiding conflicts.

[0055] Shared receive parameters refer to common parameters that all communication nodes, including the target communication node, must follow when processing any received message. These parameters include physical layer parameters, standard data frame formats, common check rules, and communication baud rates. Taking a car door controller as an example, all nodes on the same physical bus (including each door controller) must be configured with the same communication rate; otherwise, they cannot correctly decode each other's signals. Physical layer parameters can include bus level standards (dominant / recessive levels in CAN), terminating resistor matching requirements, etc., and must be consistent on the same bus. Data frame format: The frame structure used (such as CAN standard frame / extended frame format identifiers, data field length limits), check mechanisms (such as CAN CRC check), and other protocol specifications are unified.

[0056] For target communication nodes, the parameters required for message processing tasks are pre-defined into unique receiving parameters and shared receiving parameters. This allows each node to ensure the correctness and consistency of physical layer decoding and link layer parsing based on shared parameters, avoiding bit errors or communication interruptions caused by differences in basic receiving standards. Simultaneously, it can rely on unique parameters to quickly and accurately filter and respond to messages relevant to its own node, improving the efficiency and relevance of message processing. This not only reduces the total number of parameters stored by each node to implement the receiving function, eliminating redundant configurations, but also enhances the overall stability and maintainability of the multi-node communication system by uniformly managing the basic rules of the receiving process. When the network communication basic standards need to be adjusted, only the shared parameters need to be updated to achieve global effect, greatly reducing the complexity and risk of system upgrades.

[0057] In one embodiment, the communication task includes a message sending task; the unique communication parameters include unique sending parameters required by the target communication node to process and send messages, and the shared communication parameters include shared sending parameters required by multiple communication nodes to process and send messages; processing the communication task according to the first message table and the second message table includes: obtaining the message content of the message sending task; configuring the message content according to the unique sending parameters and the shared sending parameters to generate a target message, and sending the target message.

[0058] In this embodiment, the communication task to be processed can be a message sending task. Unique sending parameters refer to the unique communication parameters required by the target communication node to organize and send messages, including but not limited to source address identifiers, message data content, specific sending priorities, and node-specific payload formats. Taking a door controller as an example, the source address identifier can be represented by a message identifier. Each door controller's message identifier must be unique, used to identify: the sending node's identity (e.g., distinguishing between left and right front door controllers) and the message function type (e.g., lock status reporting, window position feedback). Furthermore, the data content sent by each controller is completely independent, containing its own status information (e.g., window opening degree, door lock status) or the result of a response command.

[0059] Shared transmission parameters refer to the common parameters that all collinear nodes, including the target communication node, must follow when sending messages, such as physical layer driving timing, common frame header and footer formats, and network agreed baud rates.

[0060] In this embodiment, the required parameters are pre-classified into unique sending parameters and shared sending parameters. For the sending process, the message content corresponding to this sending task is first obtained. Then, the message content is configured and processed according to the unique sending parameters and shared sending parameters to generate the target message, which is then sent. In this way, when a node sends a message, it can ensure that the sent message conforms to the unified specifications of the entire network at the physical layer and link layer based on the shared sending parameters, ensuring that the message can be correctly decoded and received by all nodes. At the same time, it can endow the message with the node's identity characteristics and the specificity of the sending logic based on the unique sending parameters. This allows the node to only call its own unique sending parameters and a set of shared basic parameters during the sending preparation phase, avoiding the huge redundancy of pre-storing all the sending configurations of the entire network for each node, and greatly saving storage resources. At the same time, the shared parameters centrally manage the basic sending rules, ensuring the consistency of the sending behavior of the entire network, reducing the risk of network conflicts or communication anomalies caused by incorrect configuration of individual sending parameters of nodes. When it is necessary to adjust the basic network sending configuration, global synchronization can be achieved simply by updating the shared parameter table, which significantly improves the maintainability and upgrade efficiency of the system.

[0061] In one embodiment, before step 101, the method further includes: determining all communication parameters required by each of the multiple communication nodes when processing a communication task; dividing all communication parameters into unique communication parameters required by each communication node when processing a communication task and common communication parameters required by all multiple communication nodes when processing a communication task; storing the unique communication parameters into the first message table corresponding to each communication node, and storing the common communication parameters into the second message table corresponding to each communication node.

[0062] In this embodiment, before executing communication tasks, a systematic analysis and intelligent partitioning of all required communication parameters for multiple communication nodes are performed to construct a structured parameter storage system. First, by determining all parameters required by each node to process communication tasks, the integrity and completeness of the parameter set are ensured, laying the foundation for subsequent optimization. Then, by dividing all parameters into node-specific communication parameters and network-wide shared communication parameters, and storing the partitioned node-specific and shared communication parameters in the corresponding first and second message tables for each node, the physical solidification of the optimized configuration is completed. This preprocessing process advances the resource optimization logic from real-time calculation during the communication process to the system configuration or initialization stage, ensuring that each node has a minimized and optimized local parameter library upon going online, thus completely avoiding the performance and storage overhead of processing all parameters at runtime. Furthermore, this process standardizes the parameter configuration generation steps, improving the repeatability and maintainability of system construction.

[0063] like Figure 2 The diagram shown illustrates the application communication architecture of a communication task processing method provided in this embodiment of the present disclosure. Taking a door controller scenario supporting the CAN protocol stack as an example, the system includes a service layer, a CAN IF layer, and a driver layer. Assuming the door includes four controllers, and one software version covers all four door controllers, based on the characteristics of CAN communication and the automotive CAN communication protocol stack, and maintaining multi-node collinearity, the overall solution is as follows:

[0064] At the service layer, for each door controller, the original CAN communication receive message table is split into a first message table and a second message table. The first message table stores the unique communication parameters of the corresponding door controller, and the second message table stores the common communication parameters of the four door controllers.

[0065] For example, for the receiving (RX) task, a common receiving parameter table can be configured, along with a unique receiving parameter table for the front left door controller (FLDCM), a unique receiving parameter table for the front right door controller (FRDCM), a unique receiving parameter table for the rear left door controller (RLDCM), and a unique receiving parameter table for the rear right door controller (RRDCM).

[0066] For transmit (TX) tasks, a shared transmit parameter table, a unique transmit parameter table for the front left door controller (FLDCM), a unique transmit parameter table for the front right door controller (FRDCM), a unique transmit parameter table for the rear left door controller (RLDCM), and a unique transmit parameter table for the rear right door controller (RRDCM) can be configured.

[0067] Optionally, for controllers that do not support configuring dedicated communication parameters, the dedicated communication parameter table of the controller can be configured to be empty, thereby improving the flexibility of the solution.

[0068] The CAN IF layer, as the interface layer in the CAN communication protocol stack, connects the upper communication service layer with the lower hardware driver layer. The driver layer can determine the current installation location of the controller based on specific pin potentials.

[0069] In one embodiment, prior to step 101, the method further includes: determining the installation location and / or target function of the target communication node on the vehicle when the target communication node is powered on; and preloading a second message table and a first message table adapted to the installation location and / or target function.

[0070] In this embodiment, by dynamically determining the physical installation location or target function of the target communication node during the power-on initialization phase, and accurately preloading a unique parameter table (first message table) and a unified common parameter table (second message table) adapted to the installation location information or target function requirements, efficient collaboration between hardware normalization and software configuration differentiation is achieved at the implementation level. This allows communication nodes using the same hardware (such as four door controllers) to be installed as universal modules without the need for pre-programming different software on the production line. They automatically register their identities upon power-up through location identification (e.g., reading hard-wired codes, querying preset port status, or receiving assignments from the main control module) or function identification. This significantly simplifies production, inventory, and logistics management processes, and reduces manufacturing costs and complexity. In addition, the on-demand loading mechanism based on identity recognition ensures that each node retains only unique parameters that strictly correspond to its function and a set of shared parameters across the entire network in its memory after initialization. This completely eliminates memory redundancy caused by pre-storing all node parameters to cope with multiple possible locations or functions. Furthermore, it improves the flexibility and maintainability of system deployment. For example, after replacing a controller, there is no need to manually rewrite specific software; the system automatically adapts upon power-up.

[0071] In one embodiment, determining the installation location of the target communication node on the vehicle includes: acquiring the interface potential corresponding to the target communication node, and determining the installation location of the target communication node on the vehicle based on the interface potential.

[0072] In this embodiment, the "interface potential," a hardware-distinguishable physical quantity, can be used as the basis for position determination, transforming position identification into identification based on specific circuit states. In terms of hardware design, different interface potentials are preset for different installation locations within the vehicle. For example, different resistor voltage division values ​​or dedicated grounding pin combinations are assigned to the front left, front right, rear left, and rear right doors. This allows a universal target communication node to instantly and uniquely determine its physical installation location upon power-up by detecting the voltage or logic level on specific pins of its connector. This purely hardware-based identification mechanism does not rely on complex software protocols or additional communication interactions. The judgment process can be completed within microseconds, significantly shortening system initialization time and completely avoiding the risk of misjudgment due to software configuration errors or communication interference. Furthermore, this solution eliminates the need for expensive dedicated sensors or encoding chips, utilizing only existing vehicle wiring harnesses and interfaces, significantly reducing the overall system cost and complexity.

[0073] Alternatively, assuming a smart car has four door controllers using the same hardware and software, but deployed on different doors, the installation location of each controller is determined by the GPIO pin levels (the high / low level combination of PIN1 and PIN2). The correspondence between the installation location of different controllers and their corresponding pin potentials is shown in the table below:

[0074]

[0075] The above-mentioned communication task processing method can enable a single hardware and software version to support the functions of multiple nodes, reduce the consumption of system flash memory, cache and other storage resources, and support multiple nodes to share a set of COM CAN protocol stack code, thereby reducing maintenance costs.

[0076] like Figure 3 The diagram shown is a schematic representation of a communication architecture application process according to an embodiment of this disclosure. Figure 2 Taking the communication architecture shown as an example, it may include the following steps:

[0077] Step 301: Power on the controller;

[0078] Step 302: GPIO driver initialization;

[0079] Step 303: The GPIO driver reads the level states of PIN1 and PIN2. Based on the combination of PIN1 and PIN2 levels (e.g., high-high corresponds to the front left gate, high-low corresponds to the rear left gate, etc.), the current DCM branch is determined, and the interface function Set_Current_DCM(g_Current_DCM) is called to set the current DCM branch identifier.

[0080] Step 304: CAN driver initialization;

[0081] Step 305: The CAN driver uses the function Get_Current_DCM() to obtain the current controller branch identifier, determine the current controller's installation location, and appropriately set the received message filtering table.

[0082] Step 306: Configure the CAN IF as a union of the four door controller messages.

[0083] Step 307: COM CAN initialization;

[0084] Step 308: The COM CAN protocol stack uses the function Get_Current_DCM() to obtain the current controller branch identifier, load the unique and shared receive parameter tables corresponding to the RX messages of the current controller branch, and the unique and shared receive parameter tables corresponding to the TX messages.

[0085] Step 309: COM CAN processes the received message according to the unique and common receive parameter tables corresponding to the RX message, and processes the message transmission task according to the unique and common receive parameter tables corresponding to the TX message.

[0086] For details of each step of the above method, please refer to the relevant descriptions of the above embodiments, which will not be repeated here.

[0087] Please refer to Figure 4 This is a communication task processing device 600 according to an embodiment of the present disclosure. This device can be applied to electronic device 5 and can be applied to... Figure 6 In the communication task processing application scenario shown, the goal is to reduce the memory footprint of each communication node and improve resource utilization. The device includes an acquisition module 601 and a processing module 602, and the functional principles of each module are as follows:

[0088] The acquisition module 601 is used to acquire a first message table and a second message table preset by the target communication node in response to the communication task to be processed. The first message table is configured with the unique communication parameters required by the target communication node, and the second message table is configured with the common communication parameters of multiple communication nodes, including the target communication node.

[0089] The processing module 602 is used to process communication tasks according to the first message table and the second message table.

[0090] In one embodiment, the communication task includes a processing task related to receiving messages; the unique communication parameters include unique receiving parameters required by the target communication node to process the received messages, and the shared communication parameters include shared receiving parameters required by multiple communication nodes to process the received messages.

[0091] The processing module 602 is used to process received messages based on unique receiving parameters and common receiving parameters.

[0092] In one embodiment, the communication task includes a message sending task; the unique communication parameters include unique sending parameters required by the target communication node to process and send messages, and the shared communication parameters include shared sending parameters required by multiple communication nodes to process and send messages.

[0093] The processing module 602 is used to obtain the message content of the message sending task; configure and process the message content according to the unique sending parameters and the common sending parameters, generate the target message, and send the target message.

[0094] In one embodiment, the device further includes: a preset module, configured to determine all communication parameters required by each of the multiple communication nodes when processing a communication task before obtaining the first message table and the second message table preset by the target communication node; divide the all communication parameters into unique communication parameters required by each communication node when processing a communication task and common communication parameters required by the multiple communication nodes when processing a communication task; store the unique communication parameters into the first message table corresponding to each communication node, and store the common communication parameters into the second message table corresponding to each communication node.

[0095] In one embodiment, the unique communication parameters include one or more of the following: message identifier, node identifier, and message filtering rules; the common communication parameters include one or more of the following: physical layer parameters, data frame format, and communication baud rate.

[0096] In one embodiment, the device further includes: a preloading module, configured to determine the installation location and / or target function of the target communication node on the vehicle when the target communication node is powered on, before acquiring the first message table and the second message table preset by the target communication node; and preload the second message table and the first message table adapted to the installation location and / or target function.

[0097] In one embodiment, a preloading module is used to obtain the interface potential corresponding to the target communication node and determine the installation position of the target communication node on the vehicle based on the interface potential.

[0098] For a detailed description of the communication task processing device 600 described above, please refer to the description of the relevant method steps in the above embodiments. The implementation principle and technical effect are similar, and will not be repeated here in this embodiment.

[0099] like Figure 5 As shown, this embodiment provides an electronic device 5, including: at least one processor 51 and a memory 52. Figure 5Taking a processor as an example, processor 51 and memory 52 are connected via bus 50. Memory 52 stores instructions that can be executed by processor 51. The instructions are executed by processor 51 to enable electronic device 5 to perform all or part of the process of the method in the following embodiments, so that each node only needs to call its own unique communication parameters and a shared public parameter set when processing communication tasks, without having to store all the communication parameters of all nodes, thereby reducing the memory occupation of each communication node and improving resource utilization.

[0100] In one embodiment, the electronic device 5 may be an in-vehicle device, such as an in-vehicle controller, or a mobile phone, tablet computer, laptop computer, desktop computer, or a large computing system composed of multiple computers.

[0101] Figure 6 This is a schematic diagram of an application scenario 600 of a communication task processing system provided in an embodiment of this disclosure. For example... Figure 6 As shown, the system includes: a server 610 and a terminal 620, wherein:

[0102] Server 610 can be a data center providing communication task processing services, such as a vehicle service data center. In a real-world scenario, a vehicle service data center may have multiple servers 610. Figure 6 Taking one server (610) as an example.

[0103] Terminal 620 can be an electronic device that interacts with the vehicle service data center, such as a vehicle, vehicle controller, computer, mobile phone, tablet, or other device used to access the vehicle service data center. There can also be multiple terminals 620. Figure 6 The following example uses two terminals, 620, for illustration.

[0104] Terminal 620 and server 610 can transmit information via the Internet, enabling terminal 620 to access data on server 610. Both terminal 620 and / or server 610 can be implemented by electronic device 5.

[0105] The communication task processing scheme of this embodiment can be deployed on server 610, on terminal 620, or partially on server 610 and partially on terminal 620. The appropriate deployment method can be chosen based on actual needs in a real-world scenario, and this embodiment does not impose any limitations.

[0106] When the communication task processing scheme is deployed entirely or partially on the server 610, the call interface can be opened to the terminal 620 to provide algorithm support to the terminal 620.

[0107] The method provided in this embodiment can be implemented by an electronic device 5 executing corresponding software code, and is achieved through data interaction with a server. The electronic device 5 can be a local terminal device. When the method runs on a server, it can be implemented and executed based on a cloud interaction system, which includes a server and client devices.

[0108] In one possible implementation, the method provided in this disclosure provides a graphical user interface through a terminal device, wherein the terminal device may be the aforementioned local terminal device or a client device in the aforementioned cloud interaction system.

[0109] In one embodiment, this disclosure also provides a vehicle, which may include:

[0110] At least one processor. And

[0111] A memory that is communicatively connected to at least one processor.

[0112] The memory stores instructions that can be executed by at least one processor, which is configured to execute the instructions to implement the method of any of the foregoing embodiments.

[0113] Figure 7 This is a block diagram illustrating a vehicle 700 according to an exemplary embodiment. For example, vehicle 700 may be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other types of vehicles.

[0114] Reference Figure 7 The vehicle 700 may include various subsystems, such as an infotainment system 710, a perception system 720, a decision control system 730, a drive system 740, and a computing platform 750. The vehicle 700 may also include more or fewer subsystems, and each subsystem may include multiple components. Furthermore, each subsystem and each component of the vehicle 700 can be interconnected via wired or wireless means.

[0115] In some embodiments, the infotainment system 710 may include a communication system, an entertainment system, and a navigation system, etc.

[0116] The perception system 720 may include several sensors for sensing information about the environment surrounding the vehicle 700. For example, the perception system 720 may include a global positioning system (which may be GPS, BeiDou, or other positioning systems), an inertial measurement unit (IMU), lidar, millimeter-wave radar, ultrasonic radar, and a camera device.

[0117] The decision control system 730 may include a computing system, a vehicle controller, a steering system, a throttle, and a braking system.

[0118] The drive system 740 may include components that provide powered motion to the vehicle 700. In one embodiment, the drive system 740 may include an engine, an energy source, a transmission system, and wheels. The engine may be one or a combination of internal combustion engines, electric motors, and compressed air engines. The engine is capable of converting energy provided by the energy source into mechanical energy.

[0119] Some or all of the functions of vehicle 700 are controlled by computing platform 750. Computing platform 750 may include at least one processor 751 and memory 752, and processor 751 may execute instructions 753 stored in memory 752.

[0120] Processor 751 can be any conventional processor, such as a commercially available CPU. Processors may also include graphics processing units (GPUs), field-programmable gate arrays (FPGAs), systems-on-chips (SoCs), application-specific integrated circuits (ASICs), or combinations thereof.

[0121] The memory 752 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.

[0122] In addition to instruction 753, memory 752 can also store data, such as road maps, route information, vehicle position, direction, speed, and other data. The data stored in memory 752 can be used by computing platform 750.

[0123] In this embodiment of the disclosure, processor 751 may execute instructions 753 to complete all or part of the steps of the method of any of the above embodiments.

[0124] In some embodiments of this disclosure, a computer-readable storage medium including instructions is also provided, such as a memory including instructions that can be executed by a processor of an electronic device to perform the methods of any of the above embodiments. For example, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0125] This disclosure also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the method of any of the foregoing embodiments.

[0126] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the methods of any of the foregoing embodiments.

[0127] In the several embodiments provided in this disclosure, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed.

[0128] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this disclosure.

[0129] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor. The memory may include high-speed RAM (Random Access Memory), and may also include non-volatile memory (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk, or optical disc, etc.

[0130] The aforementioned storage media can be implemented from 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. The storage media can be any available medium accessible to general-purpose or special-purpose computers.

[0131] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. Both the processor and the storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic device or host device.

[0132] Furthermore, the term “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous compared to other aspects or designs. Rather, the use of the term “exemplary” is intended to present the concept in a concrete manner. As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise specified or clear from the context, “X applies A or B” is intended to mean any of the natural inclusive arrangements. That is, “X applies A or B” satisfies any of the foregoing instances if X applies A. X applies B. or both X applies A and B. Additionally, unless otherwise specified or clear from the context to refer to the singular form, the articles “a” and “an” as used in this application and the appended claims are generally understood to mean “one or more.”

[0133] Similarly, although this disclosure has been shown and described with respect to one or more implementations, equivalent variations and modifications will occur to those skilled in the art upon reading and understanding this specification and the accompanying drawings. This disclosure includes all such modifications and variations and is limited only by the scope of the claims. In particular, with respect to the various functions performed by the components described above (e.g., elements, resources, etc.), unless otherwise indicated, the terminology used to describe such components is intended to correspond to any component (functionally equivalent) that performs the specific function of the described component, even if structurally not equivalent to the disclosed structure. Furthermore, although specific features of this disclosure may have been disclosed with respect to only one of several implementations, such features may be combined with one or more other features of other implementations, as may be desired and advantageous to any given or particular application. Moreover, with regard to the terms “comprising,” “owning,” “having,” “having,” or variations thereof as used in the detailed description or claims, such terms are intended to be inclusive in a manner similar to the term “including.”

[0134] The sequence numbers of the embodiments disclosed above are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0135] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods of the various embodiments of this disclosure.

[0136] The collection, storage, use, processing, transmission, provision, and disclosure of user data and other information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0137] The above are merely exemplary embodiments of this disclosure and do not limit the patent scope of this disclosure. Any equivalent structural or procedural transformations made using the content of this disclosure and its drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this disclosure.

Claims

1. A communication task processing method, characterized in that, include: In response to a communication task to be processed, a first message table and a second message table preset by the target communication node are obtained. The first message table is configured with the unique communication parameters required by the target communication node, and the second message table is configured with the common communication parameters of multiple communication nodes, including the target communication node. The communication task is processed according to the first message table and the second message table.

2. The method according to claim 1, characterized in that, The communication task includes a processing task related to receiving messages; the unique communication parameters include unique receiving parameters required by the target communication node to process the received messages, and the shared communication parameters include shared receiving parameters required by the multiple communication nodes to process the received messages. The step of processing the communication task according to the first message table and the second message table includes: The received message is processed according to the unique receiving parameters and the common receiving parameters.

3. The method according to claim 1, characterized in that, The communication task includes a message sending task; the unique communication parameters include unique sending parameters required by the target communication node to process and send messages, and the shared communication parameters include shared sending parameters required by the multiple communication nodes to process and send messages. The step of processing the communication task according to the first message table and the second message table includes: Obtain the message content of the message sending task; The message content is configured and processed according to the unique sending parameters and the shared sending parameters to generate a target message, and then the target message is sent.

4. The method according to claim 1, characterized in that, Before obtaining the first and second message tables preset by the target communication node, the method further includes: Determine all communication parameters required by each of the plurality of communication nodes when processing communication tasks; All communication parameters are divided into unique communication parameters required by each communication node when processing communication tasks and shared communication parameters required by all communication nodes when processing communication tasks. The unique communication parameters are stored in the first message table corresponding to each communication node, and the shared communication parameters are stored in the second message table corresponding to each communication node.

5. The method according to any one of claims 1-4, characterized in that, The unique communication parameters include one or more of the following: message identifier, node identifier, and message filtering rules; the shared communication parameters include one or more of the following: physical layer parameters, data frame format, and communication baud rate.

6. The method according to claim 1, characterized in that, Before obtaining the first and second message tables preset by the target communication node, the method further includes: When the target communication node is powered on, determine the installation location and / or target function of the target communication node on the vehicle; The second message table and the first message table adapted to the installation location and / or the target function are preloaded.

7. The method according to claim 6, characterized in that, Determining the installation location of the target communication node on the vehicle includes: Obtain the interface potential corresponding to the target communication node, and determine the installation position of the target communication node on the vehicle based on the interface potential.

8. A communication task processing device, characterized in that, include: The acquisition module is used to acquire a first message table and a second message table preset by the target communication node in response to the communication task to be processed. The first message table is configured with the unique communication parameters required by the target communication node, and the second message table is configured with the common communication parameters of multiple communication nodes, including the target communication node. The processing module is used to process the communication task according to the first message table and the second message table.

9. The apparatus according to claim 8, characterized in that, The communication task includes a processing task related to receiving messages; the unique communication parameters include unique receiving parameters required by the target communication node to process the received messages, and the shared communication parameters include shared receiving parameters required by the multiple communication nodes to process the received messages. The processing module is used to process the received message according to the unique receiving parameters and the common receiving parameters.

10. The apparatus according to claim 8, characterized in that, The communication task includes a message sending task; the unique communication parameters include unique sending parameters required by the target communication node to process and send messages, and the shared communication parameters include shared sending parameters required by the multiple communication nodes to process and send messages. The processing module is used to obtain the message content of the message sending task; configure and process the message content according to the unique sending parameters and the common sending parameters to generate a target message and send the target message.

11. The apparatus according to claim 8, characterized in that, Also includes: The preset module is used to determine all communication parameters required by each of the plurality of communication nodes when processing communication tasks before obtaining the first message table and the second message table preset by the target communication node; divide the total communication parameters into unique communication parameters required by each communication node when processing communication tasks and common communication parameters required by all the communication nodes when processing communication tasks; store the unique communication parameters into the first message table corresponding to each communication node, and store the common communication parameters into the second message table corresponding to each communication node.

12. The apparatus according to any one of claims 8-11, characterized in that, The unique communication parameters include one or more of the following: message identifier, node identifier, and message filtering rules; the shared communication parameters include one or more of the following: physical layer parameters, data frame format, and communication baud rate.

13. The apparatus according to claim 8, characterized in that, Also includes: The preloading module is used to determine the installation location and / or target function of the target communication node on the vehicle when the target communication node is powered on, before the first message table and the second message table preset by the target communication node are obtained. The second message table and the first message table adapted to the installation location and / or the target function are preloaded.

14. The apparatus according to claim 13, characterized in that, The preloading module is used to obtain the interface potential corresponding to the target communication node and determine the installation position of the target communication node on the vehicle based on the interface potential.

15. A vehicle, characterized in that, include: At least one processor; as well as A memory that is communicatively connected to the at least one processor; The memory stores instructions executable by the at least one processor, which is configured to execute the instructions to implement the method according to any one of claims 1-7.

16. An electronic device, characterized in that, include: At least one processor; as well as A memory that is communicatively connected to the at least one processor; The memory stores instructions executable by the at least one processor, which is configured to execute the instructions to implement the method according to any one of claims 1-7.

17. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a processor of an electronic device, enable the electronic device to perform the method described in any one of claims 1-7.

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

Images