Transmission method of various vehicle-mounted data and related equipment thereof

Abstract

The invention discloses a transmission method of various vehicle-mounted data and a related device thereof, which are applied to the vehicle-mounted field. The method comprises the steps of determining target data to be sent currently, determining that the target data does not exist in cached data in a real-time operation environment or a basic software component, the cached data being cached sent data, and then sending the target data to a second communication device. Or, target data to be sent currently is determined, and when the timer exceeds a period threshold, the target data is sent to the second communication device, and the period threshold is greater than the period of the determined application operation. According to the method and the device, the target data is determined, and the target data and the cache data are determined not to be repeated and then are sent. Or when the timer exceeds the threshold period, the target data is sent, so that the quantity of the sent target data can be reduced, the quantity of Ethernet messages is reduced, the quantity of communication information is reduced, the overhead of communication processing is reduced, the processing load of a vehicle-mounted processor can be reduced, and the processing resources of the processor can be saved.

Description

Method for transmitting various vehicle-mounted data and related equipment Technical Field

[0001] The embodiments of the present application relate to the vehicle field, and in particular to a method for transmitting various vehicle data and related devices. Background Art

[0002] A large number of systems in the Internet industry are implemented based on the service-oriented architecture (SOA framework). Nowadays, the SOA architecture is also used in the automotive field to accelerate the interconnection between vehicles and the Internet.

[0003] The automotive industry is gradually evolving from a signal-based approach to an Ethernet-based SOA architecture. This signal-based approach primarily uses the Controller Area Network (CAN) to implement signal exchange between individual electronic control unit (ECU) nodes. CAN communication couples multiple signals within the same message for transmission. However, the current SOA architecture uses Ethernet interface cards to transmit signals, decoupling coupled messages. Logically independent events receive independent messages, achieving decoupling of communication signals.

[0004] However, the SOA architecture decouples coupled messages to obtain multiple messages and transmits them in the Ethernet network, which will cause a surge in the number of communication messages and increase the processing load.

[0005] Summary of the Invention

[0006] This application provides a variety of vehicle-mounted data transmission methods and related devices for use in the vehicle field. This reduces the number of Ethernet messages, thereby reducing the amount of communication information and communication processing overhead, and can also reduce the processing load of the vehicle processor, saving processor processing resources.

[0007] In a first aspect, a method for transmitting vehicle-mounted data is provided, comprising:

[0008] The first communication device determines the target data to be sent and determines, within the real-time operating environment or the basic software component, that the target data does not exist in the cached data. The cached data is the cached, already-sent data. The target data is then sent to the second communication device. For example, the first communication device may be an in-vehicle system or an in-vehicle device, and the second communication device may be an in-vehicle system, a mobile phone, a tablet, a server, a cloud, or other device that communicates with the in-vehicle system.

[0009] It should be noted that the first communication device sends the target data to the second communication device by sending a message carrying the target data.

[0010] In the embodiments of the present application, the first communication device determines the target data and sends it only after confirming that the target data does not overlap with the cached data. This enables the transmission of in-vehicle data over the Ethernet network, reduces the transmission of duplicate data, and thus reduces the number of sent messages, thereby reducing the use of processing resources and saving processing resources.

[0011] In a possible implementation manner of the first aspect, the first communication device determines, in the real-time operating environment or the basic software component, that the target data does not exist in the cache data based on a difference between a payload of the target data and a payload of the cache data.

[0012] In an implementation of the present application, it is determined that the target data does not exist in the cache data based on the difference between the payload of the target data and the payload in the cache data, which provides a specific implementation method for clarifying duplicate data and can accurately determine whether the target data is duplicate data, thereby increasing the reliability of the solution.

[0013] In a possible implementation manner of the first aspect, the first communication device stores the target data in a real-time runtime environment or a basic software component.

[0014] In the implementation manner of the present application, the target data to be sent is stored in a real-time operating environment or a basic software component, and the cached data can be updated in real time, thereby further avoiding the sending of duplicate data and reducing the processing load.

[0015] In a possible implementation of the first aspect, the target data is obtained by running the application. When the timer exceeds a period threshold, the first communication device sends the currently stored target data to the second communication device, and the period threshold is greater than the period for determining the application running.

[0016] In an embodiment of the present application, when the timer exceeds the period threshold, the currently cached target data is sent to the second communication device. This can avoid the problem of not sending messages to the second communication device for a long time due to abnormal determination that the current target data is always determined to be duplicate data, thereby avoiding long-term data asynchrony and improving robustness.

[0017] In a possible implementation manner of the first aspect, the cycle threshold is determined based on a current load state of the processor.

[0018] In the implementation manner of the present application, the period threshold may be determined by the first communication device based on the load status of the processor, which reflects the real-time and flexibility of the solution.

[0019] In a possible implementation manner of the first aspect, the first communication device determines that the target data is important data based on the identifier, and retransmits the target data to the second communication device.

[0020] In an embodiment of the present application, when the target data is important data, retransmitting the target data can increase the reliability of data synchronization.

[0021] Secondly, a method for transmitting vehicle-mounted data is provided, comprising:

[0022] The first communication device determines target data to be sent currently, which is obtained by running an application, and sends the target data to the second communication device when the timer exceeds a period threshold, which is greater than the period of determining the application running.

[0023] In an embodiment of the present application, the first communication device determines the target data and sends the target data to the second communication device when the timer exceeds the period threshold, and the period threshold is greater than the period for determining the operation of the application. This can reduce the number of messages sent in the same time period, thereby reducing the number of communication messages, thereby reducing the processing burden and saving processing resources.

[0024] In a possible implementation manner of the second aspect, the first communication device determines the period threshold based on a current load status of the processor.

[0025] In the implementation manner of the present application, the period threshold may be determined by the first communication device based on the load status of the processor, which reflects the real-time and flexibility of the solution.

[0026] In a possible implementation manner of the second aspect, the first communication device determines that the target data is important data based on the identifier, and retransmits the target data to the second communication device.

[0027] In an embodiment of the present application, when the target data is important data, retransmitting the target data can increase the reliability of data synchronization.

[0028] In a third aspect, a communication device is provided, which has the function of implementing the method of the first aspect or any possible implementation of the first aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0029] In the implementation manner of the present application, the communication device of the third aspect executes the method described in the first aspect of the present application or any possible implementation manner of the first aspect.

[0030] In a fourth aspect, a communication device is provided, which has the function of implementing the method of the second aspect or any possible implementation of the second aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0031] In the implementation manner of the present application, the communication device of the fourth aspect executes the method described in the second aspect of the present application or any possible implementation manner of the second aspect.

[0032] In a fifth aspect, a communication device is provided, which may include a processor coupled to a memory, wherein the memory is used to store instructions, and the processor is used to execute the instructions in the memory so that the communication device performs the method described in the first aspect of this application or any possible implementation of the first aspect.

[0033] In a sixth aspect, another communication device is provided, comprising a processor for executing a computer program (or computer executable instructions) stored in a memory, wherein when the computer program (or computer executable instructions) is executed, the method as in the first aspect, each possible implementation of the first aspect, the second aspect, or each possible implementation of the second aspect is executed.

[0034] In one possible implementation, the processor and memory are integrated together; alternatively, in another possible implementation, the memory is located outside the communication device. The communication device also includes a communication interface, which is used for the communication device to communicate with other devices, such as sending or receiving data and / or signals. Exemplarily, the communication interface can be an optical transceiver or other type of communication interface.

[0035] The seventh aspect provides a computer-readable storage medium, including computer-readable instructions. When the computer-readable instructions are run on a computer, the method described in the first aspect, any possible implementation of the first aspect, the second aspect, or each possible implementation of the second aspect of this application is executed.

[0036] In an eighth aspect, a computer program product is provided, comprising computer-readable instructions, which, when executed on a computer, causes the method described in the first aspect, any possible implementation of the first aspect, the second aspect, or each possible implementation of the second aspect of this application to be executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] FIG1 is a schematic diagram of an Ethernet service architecture for communication devices;

[0038] Figure 2 is a schematic diagram of service decoupling;

[0039] FIG3 is a schematic diagram of a method for transmitting in-vehicle data provided by an embodiment of the present application;

[0040] FIG4 is a schematic diagram of an application architecture for communication interaction provided in an embodiment of the present application;

[0041] FIG5 is another schematic diagram of a method for transmitting in-vehicle data provided by an embodiment of the present application;

[0042] FIG6 is a schematic structural diagram of a communication device provided in an embodiment of the application. DETAILED DESCRIPTION

[0043] The embodiments of the present application provide various vehicle-mounted data transmission methods and related devices for use in the vehicle field. These methods reduce the number of Ethernet messages, thereby reducing the amount of communication information and communication processing overhead, and can also reduce the processing load of the vehicle-mounted processor, thereby conserving processor processing resources.

[0044] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0045] To facilitate understanding of the subsequent embodiments of the present application, the Ethernet service-based communication architecture of the communication device is briefly described below.

[0046] For example, please refer to FIG1 , which is a schematic diagram of an Ethernet service-based architecture for a communication device. The communication device includes application layer software components (SWC), a real-time runtime environment (RTE), and basic software components, including large data communication (LDCom), a socket adaptation layer (SoAd), a protocol data unit route (PDUR), a transmission control protocol (TCP) or an internet protocol (IP), an Ethernet interface (Eth-IF) module, and Ethernet (Ethernet, eth) communication. The functions of each module are described below:

[0047] SWC: A SWC can contain multiple runnable entities. In the vehicle system, the runnable can be run periodically or triggered by an event. Usually, the runnable is run periodically to obtain the data to be sent and send it to the RTE for transmission to the target device.

[0048] RTE: RTE encapsulates the communication and services of the basic software layer, providing standardized basic software and communication interfaces for the software components of the application layer. This allows the application layer to call the basic software services through API functions. For example, RTE calls LDCom to send the data to be sent obtained by SWC.

[0049] LDCom: Provides an optional layered communication mechanism between the RTE and the PduR. It provides an efficient communication implementation without local buffering for autonomous, non-serialized, acyclic communication.

[0050] PDUR: Located at the core of the communication module, it provides static routing for the PDU data of the communication module.

[0051] SoAd: It is the entrance of Ethernet stack communication and provides conversion from static PDU to TCP / IP dynamic connection for upper-layer communication SWC.

[0052] TCP / IP: Provides TCP / IP protocol stack functions for IP data sending and receiving functions.

[0053] Eth-IF module: Belongs to the communication hardware abstraction layer and provides an interface independent of Ethernet communication system hardware. This interface includes multiple wired or wireless Ethernet controllers and transceivers.

[0054] Eth communication: Transmits upper-layer data packets to the peer end through Eth.

[0055] To facilitate subsequent understanding of the embodiments of the present application, a brief introduction to the SOA architecture is given below.

[0056] SOA has become a prominent architectural approach in the internet industry in recent years, with numerous internet systems based on it. A key reason for adopting SOA in the automotive sector is its ability to accelerate interoperability between vehicles and the internet. This includes: flexibly integrating new features with the internet without requiring signal-to-service conversion; significantly improving autonomous driving capabilities by facilitating the creation and updating of high-definition maps, route prediction, and the uploading of vehicle information and the issuance of cloud-based commands; rapidly enhancing system and software upgrades by enabling more efficient onboard diagnostic systems and over-the-air software upgrades, enabling various remote diagnostic and pre-diagnostic functions; significantly enhancing the user experience with audio and video entertainment, enabling more convenient networking, and enabling the sharing of applications across different platforms; and facilitating platform architecture upgrades, effectively reducing the complexity associated with such upgrades.

[0057] The automotive industry is evolving from a signal-based approach to an Ethernet-based SOA architecture. This signal-based approach primarily uses CAN communication to implement signal interaction between individual ECO nodes, coupling multiple signals within the same message for transmission, thus reducing the number of messages. Currently, SOA architectures transmit signals via Ethernet interfaces. Based on the service-oriented concept of SOA, coupled messages need to be decoupled, ensuring that logically independent events have independent messages, thus decoupling communication signals.

[0058] However, the service decoupling of the SOA architecture splits the original CAN communication transmission message into multiple service-oriented service control messages and transmits them in the Ethernet network, which will lead to a surge in the number of communication messages. For example, as shown in Figure 2, Figure 2 is a schematic diagram of service decoupling. Among them, the CAN message is a message transmitted by CAN communication, which includes information on multiple independent events such as battery status, charging gun status, charging request, reservation signal and fault information. Through decoupling, the messages corresponding to each service interface are obtained respectively, including the message corresponding to the battery status service interface, namely the battery status, the message corresponding to the charging gun status service interface, namely the charging gun status, the message corresponding to the charging service interface, namely the charging request, the message corresponding to the battery fault service interface, namely the fault information, and the message corresponding to the charging reservation service interface, namely the reservation signal.

[0059] In summary, the SOA architecture can decouple coupled messages to obtain multiple messages and transmit them in the Ethernet network, which will lead to a surge in the number of communication messages and increase the processing load.

[0060] To address the aforementioned issues, the present application first provides a variety of vehicle-mounted data transmission methods and related devices for use in the vehicle-mounted field. A first communication device determines the target data currently to be sent, and determines in a real-time operating environment or basic software component that the target data does not exist in the cached data, which is the cached sent data, and then sends the target data to a second communication device. This avoids sending duplicate data, thereby reducing the number of messages generated, the number of communication messages, and the overhead of communication processing, greatly reducing the processing load and saving processing resources.

[0061] Alternatively, the first communication device determines target data to be sent, obtained by running an application, and sends the target data to the second communication device when a timer exceeds a period threshold, where the period threshold is greater than the period during which the application is run. This can reduce the number of packets sent, thereby reducing the number of communication messages and lowering communication processing overhead, significantly reducing processing load and conserving processing resources.

[0062] To better understand the embodiments of the present application, the following first describes in detail the various vehicle data transmission methods provided by the embodiments of the present application in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0063] For ease of understanding, the following describes a method for transmitting in-vehicle data provided by an embodiment of the present application. For details, please refer to FIG3 , which is a schematic diagram of a method for transmitting in-vehicle data provided by an embodiment of the present application. Specifically, the method includes:

[0064] A1. The first communication device determines target data to be sent.

[0065] The first communication device determines target data to be transmitted.

[0066] For example, the application scenario example of FIG4 is used for specific description. FIG4 is a schematic diagram of the application architecture of the communication interaction provided in an embodiment of the present application. In particular, the communication architecture of the first communication device and the second communication device respectively includes at least SWC, RTE, LDCom, PDUR, SoAd, and TCP / IP modules.

[0067] A periodic runnable runs on the SWC of the first communication device and calls the RTE_write operation to write data to the RTE. This means that the first communication device periodically determines the target data to be sent based on the SWC and sends it to the RTE layer. The RTE then stores the data in a pending buffer area, awaiting transmission. For example, the first communication device determines that the runnable is periodic and continuously updates interaction information with other ECUs to maintain awareness of the current vehicle status. This period can be 5 milliseconds, 10 milliseconds, 20 milliseconds, or other time periods, which are not limited here.

[0068] A2. The first communication device determines in the real-time operating environment or the basic software component that the target data does not exist in the cached data.

[0069] The first communication device determines in the real-time operating environment or the basic software component that target data does not exist in the cached data, where the cached data is cached and sent data.

[0070] Exemplarily, the explanation continues based on the example of Figure 4 above, wherein, after receiving the target data sent by the SWC, the RTE in the first communication device caches the target data in the to-be-sent cache area of ​​the RTE and compares it with the cached data in the cache area, where the cached data is the data that has been cached in the cache area and has been sent.

[0071] In a possible implementation, in the real-time runtime environment or the basic software component, it is determined that the target data does not exist in the cache data based on the difference between the payload of the target data and the payload of the cache data.

[0072] For example, in FIG4 , the RTE checks whether the payload of the target data to be sent within the cache area is identical to the payload of each cached data within the cache area. If the payload is identical, the RTE determines that the target data exists in the cache data and is a duplicate. The target data will not be sent and, optionally, the duplicate may be discarded. If the payload of the target data differs from the payload of the cache data, the RTE determines that the target data does not exist in the cache data, i.e., it is not a duplicate. The RTE then executes step A3 to send the target data. This avoids sending duplicate data and reduces the number of sent messages.

[0073] In an implementation of the present application, it is determined that the target data does not exist in the cache data based on the difference between the payload of the target data and the payload in the cache data, which provides a specific implementation method for clarifying duplicate data and can accurately determine whether the target data is duplicate data, thereby increasing the reliability of the solution.

[0074] It is understandable that in other application scenarios or future technical environments, other methods may be used to determine whether the target data has been sent, that is, whether it is duplicate data, which is not specifically limited here.

[0075] A3. The first communication device sends target data to the second communication device.

[0076] The first communication device transmits target data to the second communication device.

[0077] For example, in Figure 4, if the target data sent by the SWC differs from the cached data in the RTE cache area, LDCom is called to send the target data to the second communication device. Specifically, LDCom is called in collaboration with other modules to send a message carrying the target data to the LDCom of the second communication device via the Ethernet network. The RTE of the second communication device receives the message carrying the target data obtained by the LDCom of the second communication device and caches the target data in the receive cache area of ​​the RTE of the second communication device. The SWC of the second communication device then obtains the target data currently cached in the RTE of the second communication device through the RTE_read operation.

[0078] In the embodiment of the present application, the first communication device determines the target data and determines that the target data is not duplicate data before sending it. This enables the transmission of vehicle data via the Ethernet network, reduces the transmission of duplicate data, and further reduces the number of sent messages, thereby reducing the occupation of processing resources and saving processing resources.

[0079] In a possible implementation manner, the first communication device ensures that the target data is in an implementation runtime environment or a basic software component.

[0080] A4. The first communication device saves the target data in the implementation environment or basic software component.

[0081] The target data are stored in the first communication device in the execution environment or the basic software component.

[0082] For example, when the RTE in FIG4 calls LDCom to send a message carrying target data, it saves the currently sent target data into the cache area, that is, saves the target data as cache data.

[0083] In the implementation manner of the present application, the target data to be sent is stored in a real-time operating environment or a basic software component, and the cached data can be updated in real time, thereby further avoiding the sending of duplicate data and reducing the processing load.

[0084] It should be noted that there is no limitation on the order of executing step A4 and the aforementioned step A3.

[0085] In a possible implementation, when the timer exceeds a period threshold, the first communication device sends the currently stored target data to the second communication device, where the period threshold is greater than a period for determining the running of the application.

[0086] A5. When the timer exceeds the period threshold, the first communication device sends the currently stored target data to the second communication device.

[0087] For example, as shown in Figure 4, the target data is obtained by the application execution, i.e., data periodically output by the Runnable. The first communication device initially starts a periodic timer. When the periodic timer expires, i.e., when the periodic threshold is exceeded, the first communication device calls LDCom to send the most recently saved target data from the cached data in the RTE cache area to the second communication device. Specifically, the periodic threshold is greater than the application execution period determined by the first communication device, i.e., the period of the Runnable. For example, if the Runnable period is 5 milliseconds, the periodic threshold can be set to 1 minute or half a minute. It should be noted that this example is for illustrative purposes only. In actual situations, the periodic threshold can be determined based on specific circumstances and is not limited here.

[0088] In an embodiment of the present application, when the timer exceeds the period threshold, the currently cached target data is sent to the second communication device. This can avoid the problem of not sending data to the second communication device for a long time due to abnormal determination that the current target data is always determined to be duplicate data, thereby avoiding long-term data asynchrony and improving robustness.

[0089] Optionally, the first communication device determines the cycle threshold based on the current load state of the processor. Alternatively, the cycle threshold is preset according to a cycle of determining the application operation.

[0090] Exemplarily, the cycle threshold can be a dynamic cycle, and the first communication device detects the current proportion of the processing load state of the processor (such as a central processing unit (CPU) or a microcontroller unit (MCU)) corresponding to different cycle thresholds, for example, according to a table, the specific table includes the correspondence between different MCU processing load proportions and different cycles, or calculated according to an algorithm, for example, the cycle threshold will be increased by 10 seconds for every 10% increase in processing load.

[0091] The period threshold value is preset according to the period of application operation, which is similar to the aforementioned setting of the period threshold value according to the Runnable period, and will not be described in detail here.

[0092] It is understandable that the example of determining the periodic threshold here is only used to understand the embodiments of the present application and does not impose any substantial limitation on the present application. In actual situations, the periodic threshold can also be determined according to other methods, which are not specifically limited here.

[0093] In the implementation manner of the present application, the period threshold may be determined by the first communication device based on the load status of the processor, which reflects the real-time and flexibility of the solution.

[0094] In addition, in a possible implementation, the first communication device determines that the target data is important data based on the identifier, and retransmits the target data to the second communication device.

[0095] For example, as shown in FIG4 , the first communication device identifies the target data as important data using an identifier. The identifier can be a preset letter, number, character, or combination thereof, which is not limited herein. The first communication device can transmit the target data using the TCP protocol, or can retransmit the target data multiple times during transmission to achieve retransmission of the target data. It is understood that in actual situations, other methods can also be used to retransmit the target data, which is not limited herein.

[0096] In an embodiment of the present application, when the target data is important data, retransmitting the target data can increase the reliability of data synchronization.

[0097] Next, another in-vehicle data transmission method provided by an embodiment of the present application is described in detail. Specifically, please refer to FIG5 , which is another schematic diagram of an in-vehicle data transmission method provided by an embodiment of the present application. Specifically, it includes:

[0098] S1. A first communication device determines target data to be sent.

[0099] The first communication device determines target data to be sent, where the target data is obtained by running an application.

[0100] It should be noted that the details are similar to those described in step A1 in FIG3 , and will not be repeated here.

[0101] S2. When the timer exceeds the period threshold, the first communication device sends target data to the second communication device.

[0102] When the timer exceeds a period threshold, the first communication device sends target data to the second communication device, and the period threshold is greater than a period for determining the running of the application.

[0103] For example, after the SWC in Figure 4 sends target data to the RTE, the target data is cached in the RTE's cache area as cached data. When the first communication device is initialized, a timer is started. When the timer exceeds a period threshold, the RTE calls LDCom to send the currently cached target data to the second communication device. The details are similar to those described in step A5 of Figure 3 above and are not further described here.

[0104] In an embodiment of the present application, the first communication device determines the target data and sends the target data to the second communication device when the timer exceeds the period threshold, and the period threshold is greater than the period for determining the operation of the application. This can reduce the number of messages sent in the same time period, thereby reducing the number of communication messages, thereby reducing the processing burden and saving processing resources.

[0105] In one possible implementation, the first communication device determines the cycle threshold based on the current processor load state. It should be noted that the first communication device determines the cycle threshold based on the current processor load state similar to that described in step A5 in FIG3 , and will not be described in detail here.

[0106] In the implementation manner of the present application, the period threshold may be determined by the first communication device based on the load status of the processor, which reflects the real-time and flexibility of the solution.

[0107] In a possible implementation, the first communication device determines that the target data is important data based on the identifier and resends the target data to the second communication device. For example, as shown in the following steps S3 and S4:

[0108] S3. The first communication device determines that the target data is important data based on the identifier.

[0109] S4. The first communication device resends the target data to the second communication device.

[0110] It should be noted that step S3 and step S4 are similar to those described in FIG3 , and will not be described in detail here.

[0111] In an embodiment of the present application, when the target data is important data, retransmitting the target data can increase the reliability of data synchronization.

[0112] It should be noted that the aforementioned RTE as a real-time operating environment or basic software component is only used as an example to understand the embodiments of the present application. It is understandable that it can also be implemented in LDCom, SoAd or other other components that can be implemented, which are not specifically limited here.

[0113] It should be noted that the example in the aforementioned Figure 4 is only used to understand the embodiments of the present application and does not impose any substantial limitation on the embodiments of the present application. It is understandable that in the future or in other technical fields, the communication device may also be other communication architectures, which are not specifically limited here.

[0114] The above describes in detail the various vehicle data transmission methods provided in the embodiments of the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is intended only to help understand the methods and core concepts of the present application. At the same time, those skilled in the art will appreciate that, based on the concepts of the present application, there may be variations in the specific implementation methods and scope of application. In summary, the contents of this specification should not be construed as limiting the present application.

[0115] To implement the various functions of the methods provided in the embodiments of the present application, the communication device may include hardware structures and / or software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular one of the aforementioned functions is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0116] As shown in Figure 6, an embodiment of the present application also provides a communication device, which is applied to the field of communications. Please refer to Figure 6 for details. Figure 6 is a structural diagram of the communication device provided in the embodiment of the application. In one possible implementation, the communication device may include a module or unit that performs the method / operation / step / action corresponding to the first communication device in Figure 3 or Figure 5 in the above method embodiment. The unit can be a hardware circuit, or software, or a hardware circuit combined with software. In one possible implementation, the communication device 600 may include: a processor 601 and a transceiver 602. The processor 601 can be used to execute step A1 and step A2 and / or step A4 in the method embodiment shown in Figure 3 above, and the transceiver 602 can be used to execute step A3 and / or step A5 in the method embodiment shown in Figure 3 above.

[0117] In another possible design, communication device 600 further includes memory 604 and one or more storage media 605 (e.g., one or more storage devices). Memory 604 and storage media 605 may be either transient or persistent storage. The program stored in storage medium 605 may include one or more modules (not shown), each of which may include a series of instructions for operating on communication device 600.

[0118] The communication device 600 may also include one or more power supplies 603 .

[0119] In other possible designs, the processor 601 and the transceiver 602 may execute the methods / operations / steps / actions in various possible implementations of the first communication device in the method embodiment shown in FIG. 3 , one by one.

[0120] In one possible design, the processor 601 executes the step of determining that the target data does not exist in the cache data based on the difference between the payload of the target data and the payload of the cached data in the real-time running environment or basic software component as described in the method embodiment in FIG3 .

[0121] In a possible design, the processor 601 executes the steps of saving the target data in the real-time operating environment or basic software component as in the method embodiment in FIG3 .

[0122] In one possible design, the processor 601 is further configured to execute the step of determining a cycle threshold based on a current processor load state as in the method embodiment shown in FIG3 .

[0123] For the beneficial effects of the various designs of the communication devices mentioned above in this application, please refer to the beneficial effects of the various corresponding implementation methods in the method embodiment in Figure 3 above, and the details will not be repeated here.

[0124] In addition, in one possible implementation, the processor 601 included in the communication device 600 can be used to execute steps S1 and / or step S3 in the method embodiment shown in Figure 5 above, and the transceiver 602 can be used to execute steps S2 and / or step S4 in the method embodiment shown in Figure 5 above.

[0125] In other possible designs, the processor 601 and the transceiver 602 may execute the methods / operations / steps / actions in various possible implementations of the first communication device in the method embodiment shown in the above figure one by one.

[0126] In one possible design, the processor 601 is further configured to execute the step of determining a cycle threshold based on a current processor load state as in the method embodiment shown in FIG5 .

[0127] For the beneficial effects of the various designs of the communication devices mentioned above in this application, please refer to the beneficial effects of the various corresponding implementation methods in the method embodiment of Figure 5 above, and the details will not be repeated here.

[0128] It should be noted that the information interaction, execution process, etc. between the modules / units in the communication device of the embodiment corresponding to Figure 6 are based on the same concept as the first communication device in the method embodiment corresponding to Figure 3 or 5 in this application. For specific contents, please refer to the description in the method embodiment shown above in this application, and will not be repeated here.

[0129] Another communication device provided in an embodiment of the present application includes a processor, which is coupled to a memory, the memory stores instructions, and the processor is used to execute the instructions, so that the communication device executes any one of the implementation methods shown in the aforementioned method embodiments.

[0130] An embodiment of the present application also provides a computer-readable storage medium, including computer-readable instructions. When the computer-readable instructions are executed on a computer, the computer executes any one of the implementation methods shown in the aforementioned method embodiments.

[0131] An embodiment of the present application also provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run on a computer, the computer executes any one of the implementation methods shown in the aforementioned method embodiments.

[0132] The present application also provides a chip or chip system, which may include a processor. The chip may also include a memory (or storage module) and / or a transceiver (or communication module), or the chip is coupled to a memory (or storage module) and / or a transceiver (or communication module), wherein the transceiver (or communication module) can be used to support the chip for wired and / or wireless communication, and the memory (or storage module) can be used to store a program or a set of instructions, and the processor calls the program or the set of instructions to implement the above-mentioned method embodiment, the operation performed by the terminal or communication device in any possible implementation of the method embodiment. The chip system may include the above chip, and may also include the above chip and other separate devices, such as memory (or storage module) and / or transceiver (or communication module).

[0133] It should also be noted that the device embodiments described above are merely illustrative, in which the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

[0134] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general-purpose hardware, and of course can also be implemented by dedicated hardware including application-specific integrated circuits, dedicated CPUs, dedicated memories, dedicated components, etc. In general, all functions performed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits, or dedicated circuits. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc., and includes a number of instructions for causing a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods of each embodiment of the present application.

[0135] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0136] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, training equipment or data center to another website, computer, training equipment or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state drive (SSD)).

Claims

1. A method for transmitting vehicle-mounted data, characterized in that: include: Determine the target data to be sent currently; Determining in the real-time operating environment or the basic software component that the target data does not exist in the cached data, the cached data being the cached sent target data; The target data is sent to the second communication device.

2. The method according to claim 1, characterized in that The step of determining in the real-time operating environment or the basic software component that there is no data to be sent in the cached data includes: In the real-time operating environment or the basic software component, it is determined that the target data does not exist in the cache data based on the fact that the payload of the target data is different from the payload of the cache data.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: The target data is stored in the real-time operating environment or the basic software component.

4. The method according to claim 3, characterized in that The target data is obtained by running the application, and the method further includes: When the timer exceeds a period threshold, the currently stored target data is sent to the second communication device, and the period threshold is greater than a period for determining the operation of the application.

5. The method according to claim 4, characterized in that The method further comprises: The cycle threshold is determined based on a current processor load status.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Determining, based on the identification, that the target data is important data; The target data is retransmitted to the second communication device.

7. A method for transmitting vehicle-mounted data, characterized in that: include: Determine the target data to be sent currently, where the target data is obtained by running the application; When the timer exceeds a period threshold, the target data is sent to the second communication device, and the period threshold is greater than a period for determining the operation of the application.

8. The method according to claim 7, characterized in that The method further comprises: The cycle threshold is determined based on a current processor load status.

9. The method according to claim 7 or 8, characterized in that: The method further comprises: Determining, based on the identification, that the target data is important data; The target data is retransmitted to the second communication device.

10. A communication device, characterized in that: The communication device comprises a processor and a transceiver: The processor is used to determine the target data to be sent currently; The processor is further used to determine in the real-time operating environment or the basic software component that the target data does not exist in the cached data, the cached data being the cached sent data; The transceiver is used to send the target data to the second communication device.

11. The device according to claim 10, characterized in that The processor is specifically configured to determine, in the real-time operating environment or the basic software component, that the target data does not exist in the cache data based on the fact that a payload of the target data is different from a payload of the cache data.

12. The device according to claim 10 or 11, characterized in that The processor is further configured to store the target data in the real-time operating environment or the basic software component.

13. The device according to claim 12, characterized in that The target data is obtained by running the application, and the transceiver is further used to send the currently stored target data to the second communication device when the timer exceeds a period threshold, and the period threshold is greater than the period for determining the running of the application.

14. The device according to claim 13, characterized in that The processor is further configured to determine the cycle threshold based on a current load state of the processor.

15. The device according to claim 14, characterized in that The processor is further configured to determine, based on the identifier, that the target data is important data; The transceiver is further configured to retransmit the target data to the second communication device.

16. A communication device, characterized in that: The communication device includes a processor and a transceiver; The processor is used to determine the target data to be sent currently, where the target data is obtained by running the application; The transceiver is used to send the target data to the second communication device when the timer exceeds a period threshold, and the period threshold is greater than a period for determining the operation of the application.

17. The device according to claim 16, characterized in that The processor is used to determine the cycle threshold based on a current load state of the processor.

18. The device according to claim 16 or 17, characterized in that The processor is further configured to determine, based on the identifier, that the target data is important data; The transceiver is further configured to retransmit the target data to the second communication device.

19. A communication device, characterized in that: A processor, the processor is coupled to a memory, the memory stores instructions, and the processor is used to execute the instructions so that the communication device executes the method according to any one of claims 1 to 9.

20. A computer-readable storage medium comprising computer-readable instructions, characterized in that: When the computer-readable instructions are executed on a computer, the method according to any one of claims 1 to 9 is executed.

Images