Vehicle-mounted data transmission method and system and electronic equipment

Abstract

The embodiment of the invention relates to a vehicle-mounted data transmission method and system and electronic equipment. The method comprises the following steps: acquiring request data generated by a vehicle-mounted domain controller on a vehicle; determining a virtual network card corresponding to the request data based on the source of the request data; determining a network port corresponding to the virtual network card; performing domain name resolution on the request data to obtain a target server address; and sending the request data to the target server through the network port according to the target server address. According to the embodiment of the invention, the corresponding relation between the virtual network card and the network port is constructed, the network data transmission capability is provided for the vehicle-mounted domain controller on the vehicle, the domain controller can fully utilize the network to carry out more data processing, the vehicle-mounted terminal does not need to carry out excessive data processing on the data received and transmitted by the vehicle-mounted domain controller, and the data transmission efficiency is improved. Therefore, the utilization rate of vehicle-mounted hardware resources is improved, and the data transmission efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of intelligent vehicle technology, and in particular to an in-vehicle data transmission method, system and electronic device. Background Technology

[0002] In intelligent vehicles, the domain controller, as a module providing intelligent driving functions, typically sends data to the vehicle's infotainment system controller via Ethernet. The operating system (e.g., Android) on the infotainment system controller processes the data and uploads it to the network. This approach involves significant data computation on the Android side, a long data upload link, and high resource consumption on the Android side. Furthermore, the Android side needs to send DNS IPs (Domain Name System IP addresses) to the domain controller, requiring the domain controller to perform domain name resolution internally. Therefore, providing the domain controller with internet access, enabling internal network data synchronization and analysis, and reducing the resource consumption of the vehicle's infotainment system controller, has become a pressing issue. Summary of the Invention

[0003] In view of this, in order to solve some or all of the above-mentioned technical problems, embodiments of this application provide a vehicle data transmission method, system and electronic device.

[0004] In a first aspect, embodiments of this application provide a method for transmitting data in a vehicle. The method includes: acquiring request data generated by an on-board domain controller in a vehicle; determining a virtual network interface card (NIC) corresponding to the request data based on the source of the request data; determining a network port corresponding to the virtual NIC; performing domain name resolution on the request data to obtain a target server address; and sending the request data to the target server via the network port according to the target server address.

[0005] In one possible implementation, determining the virtual network interface card (NIC) corresponding to the request data based on the source of the request data includes: determining a virtual local area network (VLAN) segment pre-configured for the source of the request data; and determining the virtual NIC corresponding to the VLAN segment based on a pre-configured routing table.

[0006] In one possible implementation, the step of resolving the domain name of the request data to obtain the target server address includes: resolving the domain name of the request data to obtain the target server address based on a pre-configured Domain Name System proxy service.

[0007] In one possible implementation, determining the network port corresponding to the virtual network card includes: determining the network address corresponding to the virtual network card from a preset configuration file; and determining the corresponding network port based on the network address.

[0008] Secondly, embodiments of this application provide an in-vehicle data transmission system, comprising: an in-vehicle domain controller, an in-vehicle infotainment controller, and an in-vehicle communication terminal; wherein the in-vehicle domain controller and the in-vehicle communication terminal are both communicatively connected to the in-vehicle infotainment controller; the in-vehicle domain controller is configured to: send request data to the in-vehicle infotainment controller; the in-vehicle infotainment controller is configured to: determine the virtual network interface card (NIC) corresponding to the request data based on the source of the request data; and send the request data to the in-vehicle communication terminal using the virtual NIC; the in-vehicle communication terminal is configured to: determine the network port corresponding to the virtual NIC; perform domain name resolution on the request data to obtain a target server address; and send the request data to the target server through the network port according to the target server address.

[0009] In one possible implementation, the vehicle controller is further configured to: determine a virtual local area network segment pre-configured for the source of the requested data; and determine the virtual network card corresponding to the virtual local area network segment based on a pre-configured routing table.

[0010] In one possible implementation, the vehicle controller is further configured to: determine the status of the Ethernet on the vehicle after power-on; if the status is inactive, perform the operation of configuring the routing configuration table to set different virtual local area network segments and corresponding data transmission channels in the routing configuration table.

[0011] In one possible implementation, the vehicle-mounted communication terminal is further configured to: perform network registration and dialing operations after power-on to obtain at least two network addresses; bind the at least two network addresses to their corresponding network ports respectively; write the at least two network addresses into a preset configuration file, and perform Domain Name System Service proxy operations based on the configuration file.

[0012] Thirdly, embodiments of this application provide an electronic device, including: a memory for storing a computer program; and a processor for executing the computer program stored in the memory, wherein when the computer program is executed, it implements the method of any embodiment of the vehicle data transmission method of the first aspect of this application.

[0013] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, it implements the method of any embodiment of the vehicle data transmission method of the first aspect described above.

[0014] Fifthly, embodiments of this application provide a computer program comprising computer-readable code, which, when executed on a device, causes a processor in the device to implement the method of any embodiment of the in-vehicle data transmission method of the first aspect described above.

[0015] The vehicle data transmission method, system, and electronic device provided in this application embodiment acquire request data generated by the vehicle's onboard domain controller; determine the virtual network interface card (NIC) corresponding to the request data based on its source; determine the network port corresponding to the virtual NIC; perform domain name resolution on the request data to obtain the target server address; and send the request data to the target server through the network port according to the target server address. This application embodiment establishes a correspondence between virtual NICs and network ports, providing a separate network communication link for the vehicle's onboard domain controller and enabling network data transmission. The domain controller can fully utilize the network for more data processing, eliminating the need for excessive data processing by the vehicle's onboard unit, thereby improving the utilization rate of onboard hardware resources and increasing data transmission efficiency. Attached Figure Description

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

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0019] Figure 1 A flowchart illustrating a vehicle data transmission method provided in an embodiment of this application;

[0020] Figure 2 A flowchart illustrating the second vehicle data transmission method provided in this application embodiment;

[0021] Figure 3 A flowchart illustrating the third vehicle data transmission method provided in this application embodiment;

[0022] Figure 4 This is a schematic diagram of the structure of an in-vehicle data transmission system provided in an embodiment of this application;

[0023] Figure 5A schematic diagram of an exemplary data transmission link provided for an embodiment of this application;

[0024] Figure 6 This is a schematic diagram of a vehicle data transmission structure provided in an embodiment of this application;

[0025] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0026] Various exemplary embodiments of this application will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of this application.

[0027] Those skilled in the art will understand that the terms "first" and "second" in the embodiments of this application are only used to distinguish different steps, devices or modules, and do not represent any specific technical meaning, nor do they indicate the logical order between them.

[0028] It should also be understood that in this embodiment, "multiple" can refer to two or more, and "at least one" can refer to one, two or more.

[0029] It should also be understood that any component, data or structure mentioned in the embodiments of this application can generally be understood as one or more unless explicitly defined or given contrary guidance in the context.

[0030] Furthermore, the term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship.

[0031] It should also be understood that the description of the various embodiments in this application emphasizes the differences between the various embodiments, and the similarities or similarities can be referred to each other. For the sake of brevity, they will not be described in detail.

[0032] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the scope of this application and its application or use.

[0033] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0034] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0035] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. To facilitate understanding of the embodiments of this application, the application will be described in detail below with reference to the accompanying drawings and embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0036] To address the technical problems of low in-vehicle data transmission efficiency and high resource consumption of the vehicle terminal in existing technologies, this application provides an in-vehicle data transmission method that can provide networking capabilities for the domain controller, thereby enabling the time domain controller to perform more data transmission and processing based on the network, reducing the resource pressure on the vehicle terminal, and improving data transmission efficiency.

[0037] Figure 1 This is a flowchart illustrating a vehicle-mounted data transmission method provided in an embodiment of this application. This method can be applied to a vehicle and executed by a controller on the vehicle. Furthermore, the executing entity of this method can be hardware or software. When the executing entity is hardware, it can be one or more of the aforementioned controllers. For example, a single controller can execute this method, or multiple controllers can cooperate with each other to execute this method. When the executing entity is software, this method can be implemented as multiple software programs or software modules, or as a single software program or software module. No specific limitations are imposed here.

[0038] like Figure 1 As shown, the method specifically includes:

[0039] Step 101: Obtain the request data generated by the vehicle's onboard domain controller.

[0040] In some embodiments, an in-vehicle domain controller is an electronic device on a vehicle that controls a specific functional module. For example, an in-vehicle domain controller may include a powertrain domain controller, a driver assistance domain controller, etc. In some scenarios, the in-vehicle domain controller needs to send or receive data over a network. The aforementioned request data refers to the data sent by the domain controller to the network.

[0041] Step 102: Determine the virtual network interface card corresponding to the requested data based on the source of the requested data.

[0042] In some embodiments, the correspondence between the source of requested data and the virtual network interface card (NIC) can be pre-configured. The source of the requested data can be determined by the virtual LAN segment to which the domain controller belongs, or it can be represented by setting an identifier.

[0043] The aforementioned virtual network interface card (virtio-net) is a virtual Ethernet interface card that supports multi-queue network packet transmission and reception and can process Ethernet data frames containing MAC addresses. Multiple virtual network interfaces can be used, and different virtual network interfaces can correspond to different network ports.

[0044] Step 103: Determine the network port corresponding to the virtual network card.

[0045] In some embodiments, the network port is a port for communicating with an external network of the vehicle. For example, the network port can be CCMNIX (China Communication Mobile Network Interface) (including CCMNI1 and CCMNI2).

[0046] Step 104: Perform domain name resolution on the requested data to obtain the target server address.

[0047] In some embodiments, the controller executing this method may pre-configure a Domain Name System (DNS) proxy service to perform domain name resolution on the requested data. After resolution, the address of the target server to receive the requested data can be obtained.

[0048] Step 105: Based on the target server address, send the request data to the target server through the network port.

[0049] In some embodiments, the network port can establish its connection with an external network by performing a pre-installation network operation. For example, there may be two network ports, CCMNI1 and CCMNI2, where CCMNI1 may correspond to a public DNS IP address returned by the network operator, and CCMNI2 may correspond to a private DNS IP address returned by the network operator. Request data can be sent to a base station connected to the vehicle via the network port, and then further forwarded to the target server.

[0050] The vehicle data transmission method provided in this application involves: acquiring request data generated by the vehicle's in-vehicle domain controller; determining the virtual network interface card (NIC) corresponding to the request data based on its source; determining the network port corresponding to the virtual NIC; performing domain name resolution on the request data to obtain the target server address; and sending the request data to the target server via the network port according to the target server address. This application implements the mapping between virtual NICs and network ports, providing a separate network communication link for the vehicle's in-vehicle domain controller and enabling network data transmission. The domain controller can fully utilize the network for more data processing, eliminating the need for excessive data processing by the vehicle's onboard unit, thereby improving the utilization rate of in-vehicle hardware resources and increasing data transmission efficiency.

[0051] In some optional implementations of this embodiment, such as Figure 2 As shown, step 102 includes:

[0052] Step 1021: Determine the virtual local area network segment pre-configured for the source of the requested data.

[0053] The Virtual Local Area Network (VLAN) segment can be pre-configured using a configuration script. This means that different domain controllers can be pre-configured with corresponding VLAN segments. The controller executing this method can determine the corresponding VLAN segment from its configuration file.

[0054] Step 1022: Based on the pre-configured routing table, determine the virtual network interface card corresponding to the virtual LAN segment.

[0055] The routing configuration table records the addresses of virtual LAN segments and the identifiers of virtual network adapters. Based on the address of the virtual LAN segment, the corresponding virtual network adapter can be determined from the routing configuration table.

[0056] This embodiment can accurately and efficiently determine the virtual network interface card (NIC) corresponding to the requested data by pre-setting a routing configuration table in the controller, and then forward the requested data by the virtual NIC, thereby improving the efficiency of data transmission.

[0057] In some optional implementations of this embodiment, step 104 may be performed as follows:

[0058] Based on a pre-configured Domain Name System (DNS) proxy service, the requested data is resolved to obtain the target server address.

[0059] Specifically, the DNS proxy service can be implemented in advance by establishing a dnsmsq process. The DNS proxy service can be used as a local DNS server, assigning internal IP addresses and providing routing for the vehicle's local area network.

[0060] This embodiment enables domain name resolution of request data sent by the domain controller by setting up a Domain Name System proxy service, thereby providing a network communication foundation for the domain controller.

[0061] In some optional implementations of this embodiment, such as Figure 3 As shown, step 103 includes:

[0062] Step 1031: Determine the network address corresponding to the virtual network card from the preset configuration file.

[0063] The network addresses pre-written in the configuration file can be IP addresses returned by the network operator during the network registration process. These IP addresses include public IP addresses and private IP addresses, each corresponding to a different virtual network interface card (NIC). For example, the virtual NIC address corresponding to a public IP address is labeled eth1, and the virtual NIC address corresponding to a private IP address is labeled eth2.

[0064] Step 1032: Determine the corresponding network port based on the network address.

[0065] The mapping between network addresses and network ports can be preset. For example, the network port corresponding to a public IP address is CCMNI1, and the network port corresponding to a private IP address is CCMNI2.

[0066] This embodiment improves data transmission efficiency by pre-setting the correspondence between virtual network cards, network addresses, and network ports, enabling more targeted data transmission to different domain controllers according to the corresponding data transmission links.

[0067] Figure 4 This is a schematic diagram of an in-vehicle data transmission system provided in an embodiment of this application. The system specifically includes: an in-vehicle domain controller 401, an in-vehicle infotainment system controller 402, and an in-vehicle communication terminal 403. Both the in-vehicle domain controller 401 and the in-vehicle communication terminal 403 are communicatively connected to the in-vehicle infotainment system controller 402. The in-vehicle domain controller 401 can be connected to the in-vehicle infotainment system controller 402 via an Ethernet cable. The in-vehicle communication terminal 403 is a dedicated communication device in the vehicle, such as a T-box. The in-vehicle communication terminal 403 is connected to the in-vehicle infotainment system controller 402 via a cable.

[0068] The aforementioned vehicle domain controller 401 is an electronic device in a vehicle that controls a specific functional module. For example, the vehicle domain controller 401 may include a powertrain domain controller, a driver assistance domain controller, etc.

[0069] The vehicle domain controller 401 is used to send request data to the vehicle infotainment controller 402. In some scenarios, the vehicle domain controller 401 needs to send or receive data over a network. The aforementioned request data refers to the data sent by the domain controller to the network.

[0070] The vehicle controller 402 is used to: determine the virtual network card corresponding to the requested data based on the source of the requested data; and use the virtual network card to send the requested data to the vehicle communication terminal 403.

[0071] Specifically, the mapping between the source of requested data and the virtual network interface card (NIC) can be pre-configured. The source of the requested data can be determined by the virtual LAN segment to which the domain controller belongs, or it can be represented by setting an identifier.

[0072] The aforementioned virtual network interface card (virtio-net) is a virtual Ethernet interface card that supports multi-queue network packet transmission and reception and can process Ethernet data frames containing MAC addresses. Multiple virtual network interfaces can be used, and different virtual network interfaces can correspond to different network ports.

[0073] The vehicle infotainment controller 402 is typically equipped with an operating system (such as Android), which allows for the configuration of its functions.

[0074] The vehicle-mounted communication terminal 403 is used to: determine the network port corresponding to the virtual network card; perform domain name resolution on the request data to obtain the target server address; and send the request data to the target server through the network port according to the target server address.

[0075] A dedicated operating system tool, such as yocto, can be set on the vehicle communication terminal 403 to configure its functions.

[0076] The aforementioned network ports are for communication with external networks outside the vehicle. For example, the network port can be CCMNIX (including CCMNI1 and CCMNI2). The vehicle communication terminal 403 can be pre-configured with a Domain Name System (DNS) proxy service to perform domain name resolution on requested data. After resolution, the address of the target server receiving the requested data can be obtained.

[0077] The aforementioned network ports are located on the vehicle-mounted communication terminal 403. The vehicle can pre-execute a network registration operation to establish a connection between the network ports and external networks. For example, there may be two network ports, CCMNI1 and CCMNI2. CCMNI1 may correspond to a public DNS IP address returned by the network operator, and CCMNI2 may correspond to a private DNS IP address returned by the network operator. Request data can be sent to a base station connected to the vehicle via the network ports, and then further forwarded to the target server.

[0078] After establishing the communication link between the vehicle domain controller 401 and the target server using this method, the opposite data transmission direction can be adopted. The vehicle communication terminal 403 receives data from the target server and forwards the received data to the vehicle domain controller 401 through the vehicle controller 402.

[0079] The vehicle data transmission system provided in this application uses the vehicle controller as a data relay channel and establishes a correspondence between virtual network cards and network ports in the system. Data sent by the domain controller is processed by the vehicle communication terminal and sent to the outside world, thereby providing a separate network communication link for the vehicle domain controller and providing network data transmission capability for the vehicle domain controller. The vehicle domain controller can make full use of the network to perform more data processing without the vehicle controller having to perform excessive data processing on the data sent and received by the domain controller, which helps to improve the utilization rate of vehicle hardware resources and improve the efficiency of data transmission.

[0080] In one possible implementation, the vehicle controller 402 is also used for:

[0081] Determine the virtual LAN segment pre-configured for the source of the requested data: Based on the pre-configured routing table, determine the virtual network interface card corresponding to the virtual LAN segment.

[0082] The Virtual Local Area Network (VLAN) segment can be pre-configured via a script. This means that different domain controllers can be pre-configured with corresponding VLAN segments. Configuration files can be set in the vehicle control unit 402 to assign corresponding VLAN segments to different domain controllers.

[0083] The routing configuration table records the addresses of virtual LAN segments and the identifiers of virtual network adapters. Based on the address of the virtual LAN segment, the corresponding virtual network adapter can be determined from the routing configuration table.

[0084] In this embodiment, by pre-setting a routing configuration table in the vehicle controller 402, the virtual network card corresponding to the requested data can be accurately and efficiently determined, and the virtual network card forwards the requested data to the vehicle communication terminal 403, thereby improving the efficiency of data transmission.

[0085] In one possible implementation, the vehicle controller 402 is also used for:

[0086] After power-on, determine the status of the Ethernet on the vehicle; if the status is inactive, perform the operation of configuring the routing configuration table to set different virtual LAN segments and corresponding data transmission channels in the routing configuration table.

[0087] After the vehicle control unit 402 powers on, it runs a startup script. This script executes a local process called netlink_monitor, which monitors the Ethernet card's status. The Ethernet status can be either active (up) or inactive (down). If the Ethernet is in the down state, a configuration script can be run to configure the Ethernet routing information and NAT (Network Address Translation) configuration. After configuration, the aforementioned routing configuration table will be obtained. If the Ethernet is in the up state, it means that the Ethernet is already active, and no configuration operation is necessary.

[0088] In this embodiment, after the vehicle controller 402 is powered on, it performs a routing configuration operation based on the Ethernet status. This allows the vehicle domain controller 401 to perform data link configuration operations before network communication, enabling the vehicle domain controller 401 to efficiently perform network communication.

[0089] In one possible implementation, the vehicle-mounted communication terminal 403 is also used for:

[0090] After power-on, perform network registration and dial-up operations to obtain at least two network addresses; bind the at least two network addresses to their corresponding network ports; write the at least two network addresses to a preset configuration file; and perform Domain Name System (DNS) proxy operations based on the configuration file.

[0091] The aforementioned network registration and dialing operations are used to connect the vehicle-mounted communication terminal 403 to the external network. After performing the network registration and dialing operations, the network operator can return the public IP address and private IP address, as well as the public DNS and private DNS. The public IP address, public DNS, private IP address, and private-public DNS are the network addresses in this embodiment.

[0092] As an example, network ports can include CCMNI1 and CCMNI2. A public IP address and public DNS are bound to the CCMNI1 network interface card, and a private IP address is bound to the CCMNI2 network interface card. The bound public and private IP addresses, network ports, and virtual network interface card addresses are written into a configuration file, and the dnsmsq program is run to act as a local DNS proxy.

[0093] This embodiment, by associating network addresses, network ports, and virtual network cards in the vehicle-mounted communication terminal 403 and setting up a Domain Name System (DNS) proxy, enables the vehicle-mounted communication terminal 403 to configure the network access of the vehicle-mounted domain controller 401 and to perform more targeted data transmission according to the corresponding data transmission link, thereby improving the efficiency of data transmission.

[0094] like Figure 5 The diagram illustrates an exemplary data transmission link. The vehicle domain controller 401 generates C2L data and transmits it to the vehicle infotainment controller 402 via Ethernet cable, based on pre-configured virtual LAN segments (five VLANs are shown in the diagram). The vehicle infotainment controller 402 runs an Android system and can use a pre-configured routing table to determine the virtual network interface cards (eth1, eth2) corresponding to the VLAN segments. Using the virtual network interface cards, data can be transmitted to the public or private network (tap2, tap3) in the vehicle communication terminal 403. The dashed lines in the diagram represent the data transmission link implemented based on the virtual network interface cards. Through the bound network ports (CCMNI1, CCMNI2), the vehicle communication terminal 403 transmits data to the Internet. The data transmission link from the vehicle communication terminal 403 is the reverse of the transmission link.

[0095] Figure 6 This is a schematic diagram of the structure of a vehicle-mounted data transmission device provided in an embodiment of this application. Specifically, it includes:

[0096] The acquisition module 601 is used to acquire request data generated by the vehicle's on-board domain controller.

[0097] The first determining module 602 is used to determine the virtual network interface card corresponding to the request data based on the source of the request data;

[0098] The second determining module 603 is used to determine the network port corresponding to the virtual network card;

[0099] The 604 resolution module is used to resolve the domain name of the requested data to obtain the target server address;

[0100] The sending module 605 is used to send request data to the target server through a network port based on the target server address.

[0101] In one possible implementation, the first determining module includes: a first determining unit, configured to determine a virtual local area network segment pre-configured for the source of the requested data; and a second determining unit, configured to determine the virtual network interface card corresponding to the virtual local area network segment based on a pre-configured routing table.

[0102] In one possible implementation, the resolution module is further used to: perform domain name resolution on the requested data based on a pre-configured Domain Name System proxy service to obtain the target server address.

[0103] In one possible implementation, the second determining module includes: a third determining module, used to determine the network address corresponding to the virtual network card from a preset configuration file; and a fourth determining module, used to determine the corresponding network port based on the network address.

[0104] The vehicle data transmission device provided in this embodiment can be as follows: Figure 6 The vehicle-mounted data transmission device shown can execute all the steps of the above-mentioned vehicle-mounted data transmission methods, thereby achieving the technical effects of the above-mentioned vehicle-mounted data transmission methods. For details, please refer to the relevant descriptions above. For the sake of brevity, further details are omitted here.

[0105] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7 The illustrated electronic device 700 includes at least one processor 701, a memory 702, at least one network interface 704, and other user interfaces 703. The various components in the electronic device 700 are coupled together via a bus system 705. It is understood that the bus system 705 is used to implement communication between these components. In addition to a data bus, the bus system 705 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 7 The general labeled all buses as Bus System 705.

[0106] The user interface 703 may include a display, keyboard, or clicking device (e.g., mouse, trackball, touchpad, or touchscreen).

[0107] It is understood that the memory 702 in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 702 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0108] In some implementations, memory 702 stores elements, executable units or data structures, or subsets thereof, or extended sets thereof: operating system 7021 and application program 7022.

[0109] The operating system 7021 includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 7022 includes various applications, such as a media player and a browser, used to implement various application functions. The program implementing the method of the embodiments of this application can be included in the application program 7022.

[0110] In this embodiment, by calling the program or instructions stored in memory 702, specifically the program or instructions stored in application program 7022, processor 701 executes the method steps provided in each method embodiment, including, for example:

[0111] Obtain request data generated by the vehicle's onboard domain controller; determine the virtual network interface card (NIC) corresponding to the request data based on its source; determine the network port corresponding to the virtual NIC; perform domain name resolution on the request data to obtain the target server address; and send the request data to the target server via the network port according to the target server address.

[0112] The methods disclosed in the embodiments of this application can be applied to or implemented by processor 701. Processor 701 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 701 or by instructions in the form of software. The processor 701 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software units in the decoding processor. The software units may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 702. Processor 701 reads the information in memory 702 and, in conjunction with its hardware, completes the steps of the above method.

[0113] It is understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described above in this application, or combinations thereof.

[0114] For software implementation, the techniques described herein can be implemented by units that perform the functions described above. The software code can be stored in memory and executed by a processor. The memory can be implemented within the processor or external to the processor.

[0115] The electronic device provided in this embodiment may be as follows: Figure 7 The electronic device shown can execute all the steps of the above-described vehicle data transmission methods, thereby achieving the technical effects of the above-described vehicle data transmission methods. For details, please refer to the above descriptions. For the sake of brevity, further details are omitted here.

[0116] This application also provides a storage medium (computer-readable storage medium). This storage medium stores one or more programs. The storage medium may include volatile memory, such as random access memory; it may also include non-volatile memory, such as read-only memory, flash memory, hard disk, or solid-state drive; and it may also include combinations of the above types of memory.

[0117] When one or more programs in the storage medium can be executed by one or more processors to implement the above-described vehicle data transmission method executed on the electronic device side.

[0118] The processor described above is used to execute a program stored in memory to implement the following steps of the in-vehicle data transmission method executed on the electronic device side:

[0119] Obtain request data generated by the vehicle's onboard domain controller; determine the virtual network interface card (NIC) corresponding to the request data based on its source; determine the network port corresponding to the virtual NIC; perform domain name resolution on the request data to obtain the target server address; and send the request data to the target server via the network port according to the target server address.

[0120] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0121] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented in hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0122] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0123] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A vehicle-mounted data transmission method, characterized in that, The method includes: Obtain request data generated by the vehicle's onboard domain controller; Based on the source of the requested data, determine the virtual network interface card corresponding to the requested data; Determine the network port corresponding to the virtual network card; Perform domain name resolution on the requested data to obtain the target server address; Based on the target server address, the request data is sent to the target server through the network port.

2. The method according to claim 1, characterized in that, Determining the virtual network interface card corresponding to the request data based on its source includes: Determine the virtual local area network segment pre-configured for the source of the requested data: Based on the pre-configured routing table, the virtual network interface card corresponding to the virtual local area network segment is determined.

3. The method according to claim 1, characterized in that, The step of resolving the domain name of the requested data to obtain the target server address includes: Based on the pre-configured Domain Name System proxy service, the requested data is resolved to obtain the target server address.

4. The method according to claim 1, characterized in that, Determining the network port corresponding to the virtual network card includes: The network address corresponding to the virtual network card is determined from the preset configuration file; Determine the corresponding network port based on the network address.

5. A vehicle-mounted data transmission system, characterized in that, The system includes: an in-vehicle domain controller, an in-vehicle infotainment controller, and an in-vehicle communication terminal; wherein, the in-vehicle domain controller and the in-vehicle communication terminal are both communicatively connected to the in-vehicle infotainment controller; The vehicle domain controller is used to: send request data to the vehicle infotainment controller; The vehicle controller is used to: determine the virtual network card corresponding to the request data based on the source of the request data; and use the virtual network card to send the request data to the vehicle communication terminal. The vehicle-mounted communication terminal is used to: determine the network port corresponding to the virtual network card; perform domain name resolution on the request data to obtain the target server address; and send the request data to the target server through the network port according to the target server address.

6. The system according to claim 5, characterized in that, The vehicle controller is also used for: Determine the virtual local area network segment pre-configured for the source of the requested data: Based on the pre-configured routing table, the virtual network interface card corresponding to the virtual local area network segment is determined.

7. The system according to claim 6, characterized in that, The vehicle controller is also used for: After power-on startup, determine the status of the vehicle's Ethernet network; If the state is inactive, the operation of configuring the routing configuration table is performed to set different virtual local area network segments and corresponding data transmission channels in the routing configuration table.

8. The system according to claim 5, characterized in that, The vehicle-mounted communication terminal is also used for: After power-on startup, perform network registration and dialing operations to obtain at least two network addresses; Bind each of the at least two network addresses to its corresponding network port; Write the at least two network addresses into a preset configuration file, and perform Domain Name System Service proxy operations based on the configuration file.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor is configured to execute a computer program stored in the memory, wherein when the computer program is executed, it implements the vehicle data transmission method according to any one of claims 1-4.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the vehicle data transmission method according to any one of claims 1-4.

Images