WO2022193103A1 - 数据传输方法、装置及系统 - Google Patents

数据传输方法、装置及系统 Download PDF

Info

Publication number
WO2022193103A1
WO2022193103A1 PCT/CN2021/080885 CN2021080885W WO2022193103A1 WO 2022193103 A1 WO2022193103 A1 WO 2022193103A1 CN 2021080885 W CN2021080885 W CN 2021080885W WO 2022193103 A1 WO2022193103 A1 WO 2022193103A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
controller
sensor
protocol
electronic device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/080885
Other languages
English (en)
French (fr)
Inventor
夏兵
秦弦
帅勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2021/080885 priority Critical patent/WO2022193103A1/zh
Priority to EP21930699.0A priority patent/EP4297305B1/en
Priority to JP2023556551A priority patent/JP2024511005A/ja
Priority to CN202180001435.6A priority patent/CN113170004B/zh
Publication of WO2022193103A1 publication Critical patent/WO2022193103A1/zh
Priority to US18/467,470 priority patent/US12452336B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/765—Media network packet handling intermediate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/756—Media network packet handling adapting media to device capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/48—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for in-vehicle communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
    • G08G1/0112—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from the vehicle, e.g. floating car data [FCD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1046—Call controllers; Call servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • the present application relates to the technical field of Internet of Vehicles, and in particular, to a data transmission method, device and system.
  • a controller can acquire and utilize data from one or more sensors. However, for a sensor, its data interface may not be able to adapt to multiple controllers. If the data protocol supported by a controller may not be compatible with the data interface of the sensor, this will cause the controller to fail to obtain the sensor's data interface. data.
  • the embodiments of the present application provide a data transmission method and system.
  • the present application provides a data transmission method, comprising: a first controller receiving a data acquisition request from a second controller, the data acquisition request being used to request acquisition of data of a first sensor, the first controller receiving a data acquisition request from a second controller.
  • the controller supports the data interface corresponding to the first sensor, and the second controller does not support the data interface corresponding to the first sensor;
  • the first controller receives first data from the first sensor
  • the first controller sends the converted first data to the second controller according to the first communication protocol.
  • the first controller may respond to the data acquisition request sent by the second controller, and send the converted data obtained according to the data of the first sensor to the second controller according to the first protocol, so that the second controller
  • the controller can obtain the data from the first sensor from the first controller, which helps to simplify the hardware configuration of the vehicle-mounted system and avoid redundant settings of the sensors.
  • the second controller does not support the communication protocol adopted by the data interface corresponding to the first sensor.
  • the first communication protocol is a communication protocol supported by both the first controller and the second controller.
  • Sensor data may be communicated between the first controller and the second controller based on a first communication protocol.
  • the second controller may receive data from the first sensor from the first controller and parse the received data according to the first communication protocol.
  • the first communication protocol may be, but is not limited to, one of a real-time streaming protocol, a real-time transmission protocol, a user datagram protocol or a transmission control protocol.
  • the first controller may first determine that the second controller Whether the data interface corresponding to the first data is supported.
  • the first controller determines that the second controller does not support the data interface corresponding to the first data, the first controller receives the first data from the first sensor, and sends the converted data to the second controller according to the first communication protocol .
  • the first controller may send an instruction to the second controller to instruct the second controller to use the data interface corresponding to the first data to solve the problem from the first
  • the transmitter receives data from the first sensor.
  • the first controller determines that the second controller supports the data interface corresponding to the first data
  • the first sensor sends an instruction to the first resolver, instructing the first resolver to send the data of the first sensor to the second controller .
  • the second controller when the second controller does not support the data interface corresponding to the first data, the second controller obtains the data from the first sensor through the first controller, and the first controller can be understood as "Intermediaries" for data transfer.
  • the second controller can use the data interface corresponding to the first data to directly receive data from the first sensor from the first resolver connected to the first sensor.
  • the receiving, by the first controller, the first data from the first sensor includes: the first controller obtaining the data from the first solver by using a data interface corresponding to the first sensor.
  • the first data is obtained by the first solver by performing calculation processing on the data collected by the first sensor.
  • the first resolver can process the data output by the first sensor into data that can be supported by the first controller, so that the first controller can obtain the data of the first sensor.
  • the present application also provides a data transmission method, comprising:
  • the second controller sends a data acquisition request to the first controller, where the data acquisition request is used to request acquisition of data of the first sensor, the first controller supports the data interface corresponding to the first sensor, and the second controller supports the data interface corresponding to the first sensor.
  • the controller does not support the data interface corresponding to the first sensor;
  • the second controller receives data sent from the first controller according to the first communication protocol.
  • the second controller when the second controller does not support the data interface corresponding to the first sensor, it can obtain the data from the first sensor from the first controller by sending a data acquisition request to the first controller, which is helpful for streamlining Hardware configuration of in-vehicle systems to avoid redundant sensor settings.
  • the first communication protocol is a communication protocol supported by both the first controller and the second controller.
  • Sensor data may be communicated between the first controller and the second controller based on a first communication protocol.
  • the second controller may receive data from the first sensor from the first controller and parse the received data according to the first communication protocol.
  • the first communication protocol may be, but is not limited to, one of a real-time streaming protocol, a real-time transmission protocol, a user datagram protocol or a transmission control protocol.
  • the present application also provides a data transmission method for a communication system, where the communication system includes a first controller, a second controller and a first sensor.
  • the first controller supports a data interface corresponding to the first sensor, and the second controller does not support a data interface corresponding to the first sensor.
  • Data transfer methods include:
  • the second controller sends a data acquisition request to the first controller, where the data acquisition request is used to request to acquire data of the first sensor;
  • the first controller acquires the first data from the first sensor in response to the data acquisition request
  • the first controller sends the converted first data to the second controller according to the first communication protocol.
  • the second controller when the second controller does not support the data interface corresponding to the first sensor, it can obtain the data from the first sensor from the first controller by sending a data acquisition request to the first controller, which is helpful for streamlining Hardware configuration of in-vehicle systems to avoid redundant sensor settings.
  • the first communication protocol may be, but is not limited to, one of a real-time streaming protocol, a real-time transmission protocol, a user datagram protocol or a transmission control protocol.
  • the communication system also includes a first resolver.
  • the acquiring, by the first controller, the first data from the first sensor in response to the data acquisition request includes: the first controller acquiring the data from the first solver by using a data interface corresponding to the first sensor.
  • the first data is obtained by the first solver by performing calculation processing on the data collected by the first sensor.
  • the first resolver can process the data output by the first sensor into data that can be supported by the first controller, so that the first controller can obtain the data of the first sensor.
  • the present application further provides a data transmission device, including a transceiver unit and a processing unit, where the processing unit is used to control the transceiver unit:
  • the data transmission device supports the data interface corresponding to the first sensor, and the second controller does not supporting the data interface corresponding to the first sensor;
  • the converted first data is sent to the second controller according to the first communication protocol.
  • the data transmission device can respond to the data acquisition request sent by the second controller, and send the converted data obtained according to the data of the first sensor to the second controller according to the first protocol, so that the second controller
  • the data from the first sensor can be obtained from the first controller, which helps to simplify the hardware configuration of the vehicle-mounted system and avoid redundant settings of the sensors.
  • the data transmission device can be or can be deployed in the first controller in the above-mentioned communication system.
  • the transceiver unit in terms of receiving the first data from the first sensor, is specifically configured to:
  • the first data is obtained from the first solver by using the data interface corresponding to the first sensor, and the first data is that the first solver performs calculation processing on the data collected by the first sensor owned.
  • the first communication protocol is one of Real Time Streaming Protocol, Real Time Transport Protocol, User Datagram Protocol or Transmission Control Protocol.
  • the present application further provides a data transmission device, comprising a transceiver unit and a processing unit, where the processing unit is used to control the transceiver unit:
  • the first controller sends a data acquisition request to the first controller, where the data acquisition request is used to request acquisition of the data of the first sensor, the first controller supports the data interface corresponding to the first sensor, and the data transmission device does not support all the data interface corresponding to the first sensor;
  • Data is received from the first controller according to the first communication protocol.
  • the data transmission device when it does not support the data interface corresponding to the first sensor, it can obtain the data from the first sensor from the first controller by sending a data acquisition request to the first controller, which helps to simplify the on-board The hardware configuration of the system to avoid redundant setup of sensors.
  • the data transmission device may be or may be deployed in the second controller in the above-mentioned communication system.
  • the first communication protocol is one of Real Time Streaming Protocol, Real Time Transport Protocol, User Datagram Protocol or Transmission Control Protocol.
  • the present application further provides a first electronic device, including a first interface circuit, a second interface circuit and a controller.
  • the first electronic device may be the above-mentioned first controller, a chip or a chip system, or an independent electronic device.
  • the first interface circuit is configured to receive a data acquisition request from a second electronic device, where the data acquisition request is used to request to acquire data of a first sensor, and the second electronic device does not support the first sensor protocol of the data interface.
  • the second interface circuit is used for receiving the first data from the first sensor.
  • the controller is configured to enable the first interface circuit to send the converted first data to the second electronic device according to a first communication protocol.
  • the controller is configured to convert the first data into the second data according to the first communication protocol, wherein the second electronic device supports the protocol corresponding to the second data; the first data
  • the interface circuit is further configured to send the second data to the second electronic device.
  • the first electronic device may respond to a data acquisition request sent by the second electronic device, and send the second data or the converted data obtained according to the data of the first sensor to the second electronic device according to the first protocol.
  • the second electronic device can obtain the data from the first sensor from the first electronic device, which helps to simplify the hardware configuration of the in-vehicle system and avoid redundant setting of sensors.
  • the first communication protocol may be, but is not limited to, one of a real-time streaming protocol, a real-time transmission protocol, a user datagram protocol or a transmission control protocol.
  • the second interface circuit is specifically configured to use the data interface corresponding to the first sensor to obtain the first data from the first resolver, so The first data is obtained by the first solver performing processing on the data collected by the first sensor.
  • the present application further provides a second electronic device, including a controller and an interface circuit.
  • the second electronic device may be the above-mentioned second controller, a chip or a chip system, or an independent electronic device.
  • the controller is used for enabling the interface circuit to send a data acquisition request to the first electronic device, where the data acquisition request is used for requesting acquisition of data of the first sensor.
  • the first electronic device supports the data interface corresponding to the first sensor, and the second electronic device does not support the data interface corresponding to the first sensor.
  • the controller is further configured to receive data from the first sensor according to the first communication protocol using the interface circuit.
  • the second data or the converted first data is received from the first electronic device.
  • the second electronic device when it does not support the data interface corresponding to the first sensor, it can obtain the data from the first sensor from the first electronic device by sending a data acquisition request to the first electronic device, which is helpful for streamlining Hardware configuration of in-vehicle systems to avoid redundant sensor settings.
  • the present application further provides a communication system including the first electronic device of the fourth aspect and the second electronic device of the fifth aspect.
  • the present application further provides an electronic device, comprising a processor, wherein the processor is coupled to a memory, the memory is used for storing computer instructions, and the processor executes the computer instructions, so that the communication device executes the above
  • an electronic device comprising a processor, wherein the processor is coupled to a memory, the memory is used for storing computer instructions, and the processor executes the computer instructions, so that the communication device executes the above
  • the present application further provides a computer program product
  • the computer program product includes: a computer program (also referred to as code, or instructions), when the computer program is executed, the computer executes the first aspect or the second aspect. method in any of the possible implementations.
  • the present application provides a computer-readable storage medium, where the computer-readable medium stores a computer program (also referred to as code, or instruction) when it runs on a computer, so that the computer executes the above-mentioned first aspect or the method in any possible implementation manner of the second aspect.
  • a computer program also referred to as code, or instruction
  • FIG. 1A is a schematic diagram of a network architecture of a system of a vehicle involved in an embodiment of the application
  • 1B is a schematic diagram of the architecture of a communication system
  • FIG. 1C is a schematic diagram of the architecture of the communication system implemented in the present application.
  • FIG. 2 is a schematic diagram of a software architecture of a controller according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of another communication system according to an embodiment of the present application.
  • FIG. 5 is another schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 6 is another schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another communication system according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a first electronic device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a second electronic device according to an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of a data transmission apparatus according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another module of the data transmission device according to the embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of an electronic device according to an embodiment of the application.
  • FIG. 1A is a schematic diagram of a system architecture of an exemplary vehicle 100 .
  • the vehicle 100 includes a plurality of vehicle integration units (VIUs) 11, a communication box (telematic box, T-BOX) 12, a cockpit domain controller (CDC), a mobile data center (mobile data center, MDC) ) 14, the vehicle domain controller (Vehicle domain controller, VDC) 15.
  • VIPs vehicle integration units
  • T-BOX communication box
  • CDC cockpit domain controller
  • MDC mobile data center
  • VDC vehicle domain controller
  • the vehicle 100 also includes various types of sensors disposed on the vehicle body, such as: lidar, millimeter-wave radar, ultrasonic radar, and camera.
  • sensors disposed on the vehicle body, such as: lidar, millimeter-wave radar, ultrasonic radar, and camera.
  • Each type of sensor can include more than one. It should be understood that those skilled in the art can reasonably select the type, quantity and location layout of the sensors according to requirements.
  • FIG. 1A Four VIUs are shown in FIG. 1A . It should be understood that the number and position of the VIUs in FIG. 1A is only an example, and those skilled in the art can select an appropriate number and position of VIUs according to actual needs.
  • the vehicle integration unit VIU 11 provides a plurality of vehicle components with some or all of the data processing functions or control functions required by the vehicle components.
  • a VIU can have one or more of the following functions.
  • Electronic control function that is, the VIU is used to realize the electronic control function provided by the electronic control unit (ECU) inside some or all of the vehicle parts.
  • ECU electronice control unit
  • the control function required by a certain vehicle component and another example, the data processing function required by a certain vehicle component.
  • the same function as the gateway that is, the VIU may also have some or all of the same functions as the gateway, for example, a protocol conversion function, a protocol encapsulation and forwarding function, and a data format conversion function.
  • the data involved in the above functions may include the operation data of the actuators in the vehicle parts, for example, the motion parameters of the actuators, the working states of the actuators, and the like.
  • the data involved in the above functions can also be data collected by a data collection unit (for example, a sensitive element) of the vehicle parts, for example, the road information of the road on which the vehicle travels collected by the sensitive element of the vehicle, or the weather information, etc., This embodiment of the present application does not specifically limit this.
  • the vehicle 100 can be divided into multiple domains, each of which has an independent domain controller.
  • FIG. 1A two types of domains are shown Controllers: Cockpit Domain Controller CDC 13 and Vehicle Domain Controller VDC 15.
  • the cockpit domain controller CDC 13 may be used to implement functional control of the cockpit area of the vehicle 100, and the vehicle components in the cockpit area may include a head up display (HUD), an instrument panel, a radio, a central control screen, a navigation, a camera, and the like.
  • HUD head up display
  • instrument panel a radio
  • central control screen a navigation, a camera, and the like.
  • the vehicle domain controller VDC 15 can be used to coordinately control the power battery and the engine 141 of the vehicle to improve the dynamic performance of the vehicle 100.
  • the vehicle controller 132 in FIG. 1A can implement various VDC Function.
  • the T-BOX 12 can be used to realize the communication connection between the vehicle 100 and the internal and external devices of the vehicle.
  • the T-BOX can obtain in-vehicle device data through the bus of the vehicle 100, and can also communicate with the user's mobile phone through a wireless network.
  • the T-BOX 12 can be included in the communication system 111 of FIG. 1A.
  • the mobile data center MDC 13 is used for core control algorithms such as environment perception positioning, intelligent planning decision-making, and vehicle motion control, and outputs execution control commands such as drive, transmission, steering, and braking to realize automatic control of the vehicle 100.
  • the interactive interface realizes the human-computer interaction of vehicle driving information.
  • computing platform 150 in FIG. 1A may implement various functions of MDC 13.
  • the four VIUs 11 in FIG. 1A form a ring topology connection network, each VIU 11 is communicatively connected to its neighboring sensors, and the T-BOX 12, CDC 13, MDC 14, and VDC 15 are communicatively connected to the VIU's ring topology connection network.
  • the VIU 11 can acquire information from each sensor and report the acquired information to the CDC 13 , MDC 14 and VDC 15 .
  • T-BOX 12, CDC 13, MDC 14 and VDC 15 can also communicate with each other.
  • connection between VIUs can be, for example, Ethernet (ethernet), and the connection between the VIU and T-BOX 12, CDC 13, MDC 14, and VDC 15 can be, for example, Ethernet or peripheral component interconnect express (PCIe) Technology, the connection between the VIU and the sensor can be adopted such as controller area network (CAN), local interconnect network (LIN), FlexRay, media oriented system transport (MOST, MOST) )Wait.
  • CAN controller area network
  • LIN local interconnect network
  • FlexRay media oriented system transport
  • MOST media oriented system transport
  • FIG. 1B is a schematic diagram of a network architecture of a communication system in an embodiment.
  • the communication system 100 can be deployed in the system shown in FIG. 1A .
  • the communication system 100 includes a first controller 110 , a second controller 120 and a first sensor 111 .
  • the first controller 110 supports the data interface corresponding to the first sensor 111 .
  • the second controller 120 does not support the data interface corresponding to the first sensor 111 .
  • the first controller 110 may be, for example, the VDC15 in FIG. 1A
  • the second controller 120 may be, for example, the CDC13 in FIG. 1A .
  • the communication system 100 may further include a first resolver 112 , the data collected by the first sensor 111 is processed by the first resolver 112 into first data, and the first data is consistent with the correspondence of the first sensor. Data of the data type of the data interface.
  • the first controller 110 uses the data interface corresponding to the first sensor 111 to acquire the first data from the first sensor 111 output by the resolver 112 .
  • the communication system 100 may further include a second sensor 121 and a second resolver 122.
  • the data collected by the second sensor 121 is processed by the second resolver 122 as data of a data interface corresponding to the second sensor. type of data.
  • the second controller 120 supports the data interface corresponding to the second sensor.
  • the first controller 110 does not support the data interface corresponding to the second sensor.
  • the second controller 120 can acquire the data from the second sensor 121 output by the resolver 122 by using the data interface corresponding to the second sensor.
  • the first controller 110 supports a data interface corresponding to the first sensor 111 , and can obtain data from the first sensor 111 from the first resolver 112 .
  • the second controller 120 does not support the data interface corresponding to the first sensor 111 , and the second controller 120 cannot obtain data from the first sensor 111 from the first resolver 112 .
  • the first controller 110 cannot obtain data from the second sensor 121 from the second resolver 122 .
  • the first sensor 111 is a camera
  • the second controller 120 needs to use the data of the camera data, but since the second controller 120 does not support the data interface corresponding to the first sensor 111, a camera needs to be rearranged.
  • the camera can Referred to as the second sensor, the data interface corresponding to the second sensor is supported by the second controller 120 .
  • 2 cameras are repeatedly arranged in an in-vehicle system, which will lead to sensor redundancy.
  • the first controller 110 can send the data of the first sensor 111 to the second controller 120 based on the first communication protocol.
  • the second controller 120 may also send the data of the second sensor 121 to the first controller 110 based on the first communication protocol.
  • the first communication protocol is a communication protocol supported by both the first controller 110 and the second controller 120 .
  • the second controller can obtain the data of the first sensor from the first controller, and the first controller can also obtain the data of the second sensor from the second controller, which helps to avoid redundant sensors. moreover, there is no need to modify the hardware of the in-vehicle system.
  • the first controller 110 and the second controller 120 may be controllers corresponding to two different control domains in the system of FIG. 1A , respectively.
  • the first controller 110 may be any one of MDC, CDC, or VDC
  • the second controller 120 may be a different one of MDC, CDC, or VDC from the first controller 110 .
  • first controller 110 and the second controller 120 are not limited to the types exemplified above, and may also be of other types.
  • FIG. 2 A schematic diagram of the software architecture of the controller is shown in FIG. 2 .
  • This architecture can be used for the first controller and/or the second controller.
  • the software architecture of the controller can be divided into system software layer, support software layer and application software layer.
  • the system software layer includes the operating system and the compiler that the hardware system of the controller runs.
  • the support software layer includes some interface software, tool software, compiler and so on.
  • the application software layer includes multiple application programs for implementing some business functions.
  • the data transmission method of the embodiment of the present application includes:
  • the second controller sends a data acquisition request to the first controller.
  • the data acquisition request is used to request to acquire data of the first sensor.
  • the first controller supports the data interface corresponding to the first sensor, and the second controller does not support the data interface corresponding to the first sensor.
  • the first controller receives a data acquisition request from the second controller.
  • the first controller receives first data from the first sensor.
  • the first controller may receive the first data from the first sensor from the first resolver.
  • the first solver is connected to the first sensor.
  • the first data is obtained by the first solver performing processing on the data collected by the first sensor.
  • the first resolver processes the data collected by the first sensor into data consistent with the data interface corresponding to the first sensor.
  • the first controller can obtain the first data from the first sensor from the first resolver by using the data interface corresponding to the first sensor.
  • the first controller may obtain the first data from the first solver by using a data interface corresponding to the first sensor.
  • the first controller sends the converted first data to the second controller according to the first communication protocol.
  • the second controller receives data from the first sensor from the first controller according to the first communication protocol.
  • the data from the first sensor received by the second controller from the first sensor is the converted first data.
  • the converted first data is obtained by converting the first data by the first controller according to the first communication protocol.
  • the first communication protocol is a communication protocol supported by both the first controller and the second controller. Sensor data may be communicated between the first controller and the second controller based on a first communication protocol.
  • the second controller receives data from the first sensor from the first controller and parses the received data according to the first communication protocol.
  • the first communication protocol can be, for example, a general streaming media protocol, but is not limited to a real-time streaming protocol (RTSP), such as specifically, but not limited to: a real-time transport protocol (RTP), a user One of the datagram protocol (user datagram protocol, UDP) or transmission control protocol (transmission control protocol, TCP).
  • RTSP real-time streaming protocol
  • UDP user datagram protocol
  • TCP transmission control protocol
  • the first controller supports the data interface corresponding to the first sensor, and when the second controller does not support the data interface corresponding to the first sensor, the second controller sends the data interface corresponding to the first sensor to the first controller.
  • the controller sends a data acquisition request, and the first controller may, in response to the data acquisition request sent by the second controller, send the data obtained according to the data collected by the first sensor to the second controller according to the first protocol, so that the second control
  • the controller can receive data from the first sensor from the first controller, which helps to simplify the hardware configuration of the vehicle-mounted system and avoid redundant settings of the sensors.
  • Such a solution enables both the first controller and the second controller to use the data of the first sensor. It can also be understood that multiple controllers can use the data collected by the same sensor, which can avoid the repeated arrangement of the same or the same type of sensors, which can effectively reduce the number of sensors and reduce hardware costs.
  • the first controller may first determine whether the second controller supports the data interface corresponding to the first data.
  • steps 302 and 303 are executed.
  • the first controller receives the first data from the first sensor, and sends the data to the second controller according to the first communication protocol. Send the converted data.
  • the first controller may send an instruction to the second controller to instruct the second controller to use the data interface corresponding to the first data to solve the problem from the first
  • the transmitter receives data from the first sensor.
  • the first controller determines that the second controller supports the data interface corresponding to the first data
  • the first sensor sends an instruction to the first resolver, instructing the first resolver to send the data of the first sensor to the second controller .
  • the second controller when the second controller does not support the data interface corresponding to the first data, the second controller obtains the data from the first sensor through the first controller, and the first controller can be understood as "Intermediaries" for data transfer.
  • the second controller can use the data interface corresponding to the first data to directly receive data from the first sensor from the first resolver connected to the first sensor.
  • the first controller and the second controller may transmit data based on the first communication protocol.
  • a client is running on the second controller.
  • the client can be understood as a client for data transmission, or, if the first communication protocol is a general streaming media protocol, the client can be understood as a client based on a general streaming media protocol (RTSP client).
  • RTSP client general streaming media protocol
  • a server is deployed on the first controller.
  • the server may be understood as a data transmission server, or may be understood as an RTSP-based server (RTSP server).
  • the client is used to listen for requests sent by the application to get data.
  • the application program is an application program running on the first controller. In other embodiments, the application program may also be an application program running on other electronic devices that have established a communication connection with the second controller.
  • the server is used to process the data acquisition request sent by the client.
  • a data transmission method includes:
  • the client obtains a first request sent by an application, where the first request is used to request to obtain data of a first sensor.
  • the data of the first sensor may be data collected by the first sensor, or may be data obtained according to the data collected by the first sensor.
  • the first sensor may be, for example, but not limited to, a camera.
  • the second controller may be a smart cockpit domain controller (CDC), and the application may be a driving recorder application, a smart camera application, or the like.
  • CDC smart cockpit domain controller
  • the CDC can run an operating system, as shown in the schematic flowchart in Figure 6, the smart cockpit domain controller (CDC) starts the operating system, and the operating system can be, for example, but not limited to, Hongmeng, Android, Linux, and the like.
  • the first request may include indication information indicating the first data, or indication information indicating the first sensor.
  • the client sends a data acquisition request to a server deployed on the first controller, where the data acquisition request is used to request to acquire data of the first sensor.
  • the client running on the second controller sends a data acquisition request to the server according to the first request.
  • the data acquisition request may include indication information indicating the first data, or indication information indicating the first sensor.
  • the client can first determine whether the second controller supports the data interface corresponding to the first sensor requested by the first request.
  • the client sends a data acquisition request to the server deployed in the first controller, requesting to acquire the data of the first sensor from the first controller.
  • the client can instruct the application to directly obtain the data of the first sensor from the solver of the first sensor through the data interface corresponding to the first sensor; After the data interface corresponding to a sensor acquires the data of the first sensor from the solver of the first sensor, the data of the first sensor is sent to the application program.
  • the first controller may be, for example, but not limited to, an autonomous driving domain controller (MDC).
  • MDC autonomous driving domain controller
  • the server receives the first data from the first sensor.
  • a server deployed at the first controller may receive the first data from the first sensor from the first resolver.
  • the first solver is connected to the first sensor.
  • the first data is obtained by the first solver performing processing on the data collected by the first sensor.
  • the first resolver processes the data collected by the first sensor into data consistent with the data interface corresponding to the first sensor.
  • the server may obtain the first data from the first solver by using a data interface corresponding to the first sensor.
  • the server sends the converted first data to the client based on the first communication protocol.
  • the server deployed in the intelligent driving domain controller obtains the first data obtained according to the data output by the first sensor, and then converts the first data based on the first communication protocol to obtain the converted first data, and then sends the converted first data to the client.
  • the converted first data is sent.
  • the data transmission method further includes:
  • the client sends the first data to the application.
  • the driving recorder application needs to obtain data from the camera, and the driving recorder application can send a first request to the client.
  • the client sends a data acquisition request to the server deployed on the first controller according to the first request.
  • the server deployed in the first controller obtains the data of the camera from the first solver according to the data interface corresponding to the camera, and then converts the data of the camera according to the general streaming media protocol, and sends the converted data of the camera. to the client.
  • the client dash cam application sends the converted camera data. In this way, the driving recorder application obtains the data from the camera from the first controller through the client, so that repeated deployment of the camera can be avoided.
  • An embodiment of the present application further provides a communication system 700, which is a schematic diagram of the architecture of the communication system shown in FIG. 7 .
  • the communication system 700 in this embodiment of the present application includes a first electronic device 800 and a second electronic device 900 .
  • the first electronic device 800 includes a first interface circuit 801 , a second interface circuit 802 and a controller 803 .
  • the first electronic device 800 may be the first controller 110 in the above-mentioned embodiment corresponding to FIG. 2 , or the first electronic device 800 may include the first controller 110 .
  • the first electronic device 800 may also be a chip or a chip system, or may be an independent electronic device.
  • the first interface circuit 801 and the second interface circuit 802 may also be transceiver units or deployed in transceivers.
  • the first interface circuit 801 and the second interface circuit 802 may also be communication interfaces.
  • the first interface circuit 801 is configured to receive a data acquisition request from the second electronic device 900, where the data acquisition request is used to request to acquire data of a first sensor, and the second electronic device 900 does not support the data of the first sensor interface protocol.
  • the second interface circuit 802 is used for receiving the first data from the first sensor.
  • the controller 803 is configured to enable the first interface circuit 801 to send the converted first data to the second electronic device 900 according to the first communication protocol.
  • the controller 803 is configured to convert the first data into the second data according to the first communication protocol, and the second electronic device 900 supports the protocol corresponding to the second data.
  • the first interface circuit 801 is also used for sending second data to the second electronic device 900 .
  • the first electronic device 800 may, in response to a data acquisition request sent by the second electronic device 900, send the second data to the second electronic device according to the first protocol or the converted data obtained according to the data of the first sensor.
  • the data may be obtained from the first sensor from the first electronic device, which helps to simplify the hardware configuration of the in-vehicle system and avoid redundant setting of sensors.
  • the second electronic device 900 includes a controller 901 and an interface circuit 902 .
  • the second electronic device 900 package may be the second controller 120 in the above-mentioned embodiment corresponding to FIG. 2 , or the second electronic device 900 package may include the second controller 120 .
  • the second electronic device 900 may also be a chip or a chip system, and may also be an independent electronic device.
  • the controller 901 is configured to enable the interface circuit 902 to send a data acquisition request to the first electronic device 800 .
  • the data acquisition request is used to request to acquire data of the first sensor, and the second electronic device 900 does not support the protocol of the data interface of the first sensor.
  • the controller 901 is further configured to receive the converted first data or the second data from the first electronic device 800 through the interface circuit 902 .
  • the second electronic device 900 when the second electronic device 900 does not support the data interface corresponding to the first sensor, it can obtain the data from the first sensor from the first electronic device 800 by sending a data acquisition request to the first electronic device 800 , Helps to simplify the hardware configuration of the in-vehicle system and avoid redundant sensor settings.
  • the solution of the above data transmission method can be applied to the first electronic device 800 and the second electronic device 900 , or the steps of the above data transmission method can be implemented by the first electronic device 800 and the second electronic device 900 .
  • a data acquisition request may be sent by the controller 901 of the second electronic device 900 to the first electronic device 800 .
  • the first interface circuit 801 of the first electronic device 800 receives the data acquisition request from the controller 901 .
  • the first data from the first sensor may be received by the second interface circuit 802 of the first electronic device 800 .
  • the first interface circuit 801 can be enabled by the controller 803 of the first electronic device 800 to send the converted first data to the second electronic device 900 according to the first communication protocol; or the controller 803 can send the converted first data to the second electronic device 900 according to the first communication protocol;
  • the communication protocol converts the first data into the converted first data (ie, the second data), and sends the converted first data to the second electronic device 900 by the first interface circuit 801 .
  • the converted first data is obtained by converting the first data from the first sensor, so the converted first data can also be understood as the data of the first sensor.
  • the second electronic device 900 that does not support the data interface corresponding to the first sensor can obtain the data of the first sensor through the first electronic device 800 that supports the data interface corresponding to the first sensor, thereby Ability to avoid repeated deployment of sensors.
  • FIG. 10 is a block diagram of the data transmission device 1000, the present application also provides a data transmission device 1000, including a transceiver unit 1002 and a processing unit 1001, and the processing unit 1001 is used to control the transceiver unit 1002:
  • the data transmission device 1000 supports a data interface corresponding to the first sensor, and the second controller The data interface corresponding to the first sensor is not supported;
  • the converted first data is sent to the second controller according to the first communication protocol.
  • the data transmission apparatus 1000 may respond to the data acquisition request sent by the second controller, and send the converted data obtained according to the data of the first sensor to the second controller according to the first protocol, so that the second controller The controller can obtain the data from the first sensor from the first controller, which helps to simplify the hardware configuration of the vehicle-mounted system and avoid redundant settings of the sensors.
  • the data transmission apparatus 1000 can be or can be deployed in the first controller in the above-mentioned communication system.
  • the transceiver unit 1002 is specifically configured to:
  • the first data is obtained from the first solver by using the data interface corresponding to the first sensor, and the first data is that the first solver performs calculation processing on the data collected by the first sensor owned.
  • the first communication protocol is one of Real Time Streaming Protocol, Real Time Transport Protocol, User Datagram Protocol or Transmission Control Protocol.
  • FIG. 11 is a schematic block diagram of the data transmission device 1100, the present application also provides a data transmission device 1100, including a transceiver unit 1102 and a processing unit 1101, the processing unit 1101 is used to control the transceiver unit 1102:
  • the first controller sends a data acquisition request to the first controller, where the data acquisition request is used to request to acquire the data of the first sensor, the first controller supports the data interface corresponding to the first sensor, and the data transmission device 1100 does not support a data interface corresponding to the first sensor;
  • Data is received from the first controller according to the first communication protocol.
  • the data transmission device 1100 when the data transmission device 1100 does not support the data interface corresponding to the first sensor, it can obtain the data from the first sensor from the first controller by sending a data acquisition request to the first controller, which is helpful for streamlining Hardware configuration of in-vehicle systems to avoid redundant sensor settings.
  • the data transmission apparatus 1100 may be or may be deployed in the second controller in the above-mentioned communication system.
  • the first communication protocol is one of Real Time Streaming Protocol, Real Time Transport Protocol, User Datagram Protocol or Transmission Control Protocol.
  • FIG. 12 is a schematic structural diagram of an electronic device 1200 according to an embodiment of the present application.
  • the electronic device 1200 may include: a processor 1201 , a transceiver 1205 , and optionally a memory 1202 .
  • the transceiver 1205 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function.
  • the transceiver 1205 may include a receiver and a transmitter, the receiver may be called a receiver, a receiving circuit or a receiving unit, etc., for implementing a receiving function; the transmitter may be called a transmitter, a transmitting circuit or a transmitting unit, and the like.
  • the processor 1201 Stored in memory 1202 may be a computer program or software code or instructions 1204, which may also be referred to as firmware.
  • the processor 1201 can control the MAC layer and the PHY layer by running the computer program or software code or instruction 1203 therein, or by calling the computer program or software code or instruction 1204 stored in the memory 1202, so as to realize the following aspects of the present application.
  • the processor 1201 may be a central processing unit (central processing unit, CPU), and the memory 1202 may be, for example, a read-only memory (read-only memory, ROM), or a random access memory (random access memory, RAM).
  • the processor 1201 and transceiver 1205 described in this application may be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application specific integrated circuits (ASICs), printed circuits board (printed circuit board, PCB), electronic equipment, etc.
  • ICs integrated circuits
  • RFICs radio frequency integrated circuits
  • ASICs application specific integrated circuits
  • PCB printed circuits board
  • electronic equipment etc.
  • the modules included in the electronic device 1200 are only illustrative, and are not limited in this application.
  • the electronic device 1200 in the description of the above embodiments may be the first controller or the second controller, but the scope of the electronic device described in this application is not limited to this, and the structure of the electronic device may not be the same as shown in the figure. 12 limit.
  • the electronic device may be a stand-alone device or may be part of a larger device.
  • the implementation form of the electronic device may be:
  • Independent integrated circuit IC or chip, or, chip system or subsystem
  • a set of one or more ICs, optionally, the IC set may also include storage for storing data and instructions components; (3) modules that can be embedded in other devices; (4) receivers, smart terminals, wireless devices, handsets, mobile units, in-vehicle devices, cloud devices, artificial intelligence devices, etc.; (5) others, etc. .
  • the chip includes a processor and an interface.
  • the number of processors may be one or more, and the number of interfaces may be multiple. Interfaces are used for signal reception and transmission.
  • the chip or chip system may include memory. The memory is used to store the necessary program instructions and data of the chip or chip system.
  • the electronic device 1200 is the first controller in the above method embodiments, and the electronic device 1200 can implement any one of the methods executed by the first controller in the embodiments of the present application through a processor and a transceiver Some or all of the steps, such as a processor may be used to control the transceiver 1205:
  • a data acquisition request from a second controller, where the data acquisition request is used to request acquisition of data from a first sensor, the first controller supports a data interface corresponding to the first sensor, and the second controller The data interface corresponding to the first sensor is not supported;
  • the converted first data is sent to the second controller according to the first communication protocol.
  • the electronic device 1200 is the second controller in the above method embodiments, and the electronic device 1200 can implement any one of the second controller in the embodiments of the present application through the processor and the transceiver. Some or all of the steps of a method, such as a processor, may be used to control the transceiver 1205:
  • Data is received from the first controller according to the first communication protocol.
  • the present application provides a computer-readable storage medium, where computer instructions are stored in the computer-readable storage medium, and the computer instructions instruct the server to execute the data transmission method provided in any of the foregoing embodiments.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .
  • the modules in the apparatus of the embodiment of the present application may be combined, divided and deleted according to actual needs.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Communication Control (AREA)
  • Computer And Data Communications (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请提供了一种数据传输方法、装置及系统。数据传输方法包括第一控制器接收来自于第二控制器的数据获取请求，数据获取请求用于请求获取第一传感器的数据，第一控制器支持第一传感器对应的数据接口，第二控制器不支持第一传感器对应的数据接口；第一控制器接收来自于第一传感器的第一数据；第一控制器根据第一通信协议向第二控制器发送转换后的第一数据。这样第二电子装置能够从第一电子装置获得来自第一传感器的数据，有助于避免传感器冗余设置。

Description

数据传输方法、装置及系统 技术领域
本申请涉及车联网技术领域，尤其涉及一种数据传输方法、装置及系统。
背景技术
随着智能汽车的不断发展，智能汽车上安装的传感器种类和数量越来越多。为了更好地实现智能汽车的车载系统的内部控制，智能汽车中可设置多个控制器。一个控制器可获取并利用一个或多个传感器的数据。然而，对于一个传感器，其数据接口可能无法适配多个控制器，如果一个控制器所支持的数据协议与传感器的数据接口可能并不兼容，这就会导致该一个控制器无法获得该传感器的数据。
发明内容
本申请实施方式提供了一种数据传输方法及系统。
第一方面，本申请提供一种数据传输方法，包括：第一控制器接收来自于第二控制器的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
所述第一控制器接收来自于所述第一传感器的第一数据；
所述第一控制器根据第一通信协议向所述第二控制器发送转换后的第一数据。
本申请的技术方案，第一控制器可以响应于第二控制器发送的数据获取请求，根据第一协议向第二控制器发送根据第一传感器的数据得到的转换后的数据，这样第二控制器能够从第一控制器获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可以理解，第二控制器不支持第一传感器对应的数据接口采用的通信协议。本申请中，第一通信协议为第一控制器和第二控制器均支持的通信协议。第一控制器和第二控制器之间可基于第一通信协议传输传感器的数据。
第二控制器可从第一控制器接收来自第一传感器的数据，并根据第一通信协议，解析该接收到的数据。
可选的，第一通信协议可以是但不限于实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
可选的，在第一控制器接收来自于所述第一传感器的第一数据之前，第一控制器接收到第二控制器的数据获取请求之后，第一控制器可先判断第二控制器是否支持第一数据对应的数据接口。
若第一控制器确定第二控制器不支持第一数据对应的数据接口，第一控制器接收来自第一传感器的第一数据，根据第一通信协议向第二控制器发送转换后的已数据。
若第一控制器确定第二控制器支持第一数据对应的数据接口，第一控制器可向第二控制器发送指令，指示第二控制器利用第一数据对应的数据接口从第一解算器接收来自第一传感器的数据。
或者，若第一控制器确定第二控制器支持第一数据对应的数据接口，第一传感器向第 一解算器发送指令，指示第一解算器向第二控制器发送第一传感器的数据。
可以看出这样的方案中，当第二控制器不支持第一数据对应的数据接口时，第二控制器通过第一控制器，来获得来自第一传感器的数据，第一控制器可理解为数据传输的“中介”。当第二控制器支持第一数据对应的数据接口时，第二控制器则可以利用第一数据对应的数据接口直接从与第一传感器连接的第一解算器接收来自第一传感器的数据。
在一些实施方式中，所述第一控制器接收来自于所述第一传感器的第一数据包括：所述第一控制器利用所述第一传感器对应的数据接口从第一解算器获取所述第一数据，所述第一数据是所述第一解算器对所述第一传感器采集到的数据进行解算处理得到的。这样，第一解算器能够将第一传感器输出的数据处理为第一控制器能够支持的数据，以使得第一控制器能够获得第一传感器的数据。
第二方面，本申请还提供一种数据传输方法，包括：
第二控制器向第一控制器发送数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
所述第二控制器根据第一通信协议，接收来自第一控制器发送的数据。
本申请的技术方案，第二控制器不支持第一传感器对应的数据接口时，能够通过向第一控制器发送数据获取请求，从第一控制器获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可以理解，第一通信协议为第一控制器和第二控制器均支持的通信协议。第一控制器和第二控制器之间可基于第一通信协议传输传感器的数据。
第二控制器可从第一控制器接收来自第一传感器的数据，并根据第一通信协议，解析该接收到的数据。
可选的，第一通信协议可以是但不限于实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
第三方面，本申请还提供一种数据传输方法，用于通信系统，该通信系统包括第一控制器、第二控制器和第一传感器。所述第一控制器支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口。数据传输方法包括：
第二控制器向第一控制器发送数据获取请求，所述数据获取请求用于请求获取第一传感器的数据；
所述第一控制器响应于数据获取请求，获取来自于所述第一传感器的第一数据；
所述第一控制器根据第一通信协议向所述第二控制器发送转换后的第一数据。
本申请的技术方案，第二控制器不支持第一传感器对应的数据接口时，能够通过向第一控制器发送数据获取请求，从第一控制器获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可选的，第一通信协议可以是但不限于实时流传输协议，实时传输协议，用户数据报 协议或传输控制协议中的一种。
在一些实现方式中，通信系统还包括第一解算器。所述第一控制器响应于数据获取请求，获取来自于所述第一传感器的第一数据包括：所述第一控制器利用所述第一传感器对应的数据接口从第一解算器获取所述第一数据，所述第一数据是所述第一解算器对所述第一传感器采集到的数据进行解算处理得到的。这样，第一解算器能够将第一传感器输出的数据处理为第一控制器能够支持的数据，以使得第一控制器能够获得第一传感器的数据。
第四方面，本申请还提供一种数据传输装置，包括收发单元和处理单元，处理单元用于控制收发单元：
接收来自于第二控制器的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述数据传输装置支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
接收来自于所述第一传感器的第一数据；
根据第一通信协议向所述第二控制器发送转换后的第一数据。
本申请的技术方案，数据传输装置可以响应于第二控制器发送的数据获取请求，根据第一协议向第二控制器发送根据第一传感器的数据得到的转换后的数据，这样第二控制器能够从第一控制器获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可以理解，该数据传输装置可以为或可以部署在上述通信系统中的第一控制器。
在某些实施方式中，所述接收来自于所述第一传感器的第一数据方面，所述收发单元具体用于：
利用所述第一传感器对应的数据接口从第一解算器获取所述第一数据，所述第一数据是所述第一解算器对所述第一传感器采集到的数据进行解算处理得到的。
在某些实施方式中，所述第一通信协议是实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
应理解，上述关于数据传输方法的相关补充说明和技术效果也是用于数据传输装置，此处不再重复说明。
第五方面，本申请还提供一种数据传输装置，包括收发单元和处理单元，所述处理单元用于控制收发单元：
向第一控制器发送数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述数据传输装置不支持所述第一传感器对应的数据接口；
根据第一通信协议，接收来自第一控制器的数据。
本申请的技术方案，数据传输装置不支持第一传感器对应的数据接口时，能够通过向第一控制器发送数据获取请求，从第一控制器获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可以理解，该数据传输装置可以为或可以部署在上述通信系统中的第二控制器。
在某些实施方式中，所述第一通信协议是实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
应理解，上述关于数据传输方法的相关补充说明和技术效果也是用于数据传输装置，此处不再重复说明。
第六方面，本申请还提供一种第一电子装置，包括第一接口电路、第二接口电路和控制器。该第一电子装置可以是上述的第一控制器，也可以是芯片或芯片系统，还可以是独立的电子设备。
其中，所述第一接口电路，用于接收来自第二电子装置的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第二电子装置不支持所述第一传感器的数据接口的协议。所述第二接口电路，用于接收来自于所述第一传感器的第一数据。
关于控制器，在一种可能的实现方式中，所述控制器用于使能所述第一接口电路，根据第一通信协议向所述第二电子装置发送转换后的第一数据。
在另一种可能的实现方式中，控制器用于根据第一通信协议，转换第一数据为第二数据，其中，所述第二电子装置支持所述第二数据对应的协议；所述第一接口电路，还用于向所述第二电子装置发送所述第二数据。
本申请的技术方案，第一电子装置可以响应于第二电子装置发送的数据获取请求，根据第一协议向第二电子装置发送第二数据或者根据第一传感器的数据得到的转换后的数据。这样第二电子装置能够从第一电子装置获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可选的，第一通信协议可以是但不限于实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
可选的，在接收来自于所述第一传感器的第一数据方面，第二接口电路具体用于利用所述第一传感器对应的数据接口从第一解算器获取所述第一数据，所述第一数据是所述第一解算器对所述第一传感器采集到的数据进行解算处理得到的。
应理解，上述关于数据传输方法的相关补充说明以及技术效果，也适用于本申请的第一电子装置，此处不再重复说明。
第七方面，本申请还提供一种第二电子装置，包括控制器和接口电路。该第二电子装置可以是上述的第二控制器，也可以是芯片或芯片系统，还可以是独立的电子设备。
其中，控制器用于使能接口电路向第一电子装置发送数据获取请求，该数据获取请求用于请求获取第一传感器的数据。所述第一电子装置支持所述第一传感器对应的数据接口，所述第二电子装置不支持所述第一传感器对应的数据接口。
控制器还用于利用接口电路，根据第一通信协议，接收来自第一传感器的数据。例如接收来自第一电子装置的第二数据或转换后的第一数据。
本申请的技术方案，第二电子装置不支持第一传感器对应的数据接口时，能够通过向第一电子装置发送数据获取请求，从第一电子装置获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
应理解，上述关于数据传输方法的相关补充说明以及技术效果，也适用于本申请的第二电子装置，此处不再重复说明。
第八方面，本申请还提供一种通信系统，该通信系统包括第四方面的第一电子装置和第五方面的第二电子装置。
第九方面，本申请还提供一种电子设备，包括处理器，所述处理器与存储器耦合，所述存储器用于存储计算机指令，所述处理器执行该计算机指令，使得所述通信设备执行上述第一方面或第二方面中任一种可能实现方式中的方法
第十方面，本申请还提供一种计算机程序产品，计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当计算机程序被运行时，使得计算机执行上述第一方面或第二方面中任一种可能实现方式中的方法。
第十一方面，本申请提供了一种计算机可读存储介质，计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面或第二方面中任一种可能实现方式中的方法。
附图说明
图1A为本申请实施例涉及的车辆的系统的网络架构示意图；
图1B为通信系统的架构示意图；
图1C为本申请实施的通信系统的架构示意图；
图2为本申请实施例的控制器的软件架构示意图；
图3为本申请实施例的数据传输方法的流程示意图；
图4为本申请实施例的另一通信系统的架构示意图；
图5为本申请实施例的数据传输方法的另一流程示意图；
图6为本申请实施例的数据传输方法的另一流程示意图；
图7为本申请实施例的另一通信系统的架构示意图；
图8为本申请实施例的第一电子装置的结构示意图；
图9为本申请实施例的第二电子装置的结构示意图；
图10为本申请实施例的数据传输装置的模块示意图；
图11为本申请实施例的数据传输装置的另一模块示意图；
图12为申请实施例的电子设备的结构示意图。
具体实施方式
下面结合本发明实施例中的附图对本发明实施例进行描述。
图1A为一种示例性的车辆100的系统架构示意图。车辆100包括多个车辆集成单元(vehicle integration unit，VIU)11，通信盒子(telematic box，T-BOX)12，座舱域控制器(cockpit domain controller，CDC)，移动数据中心(mobile data center，MDC)14，整车控制器(vehicle domain controller，VDC)15。
车辆100还包括设置在车身上的多种类型的传感器，例如：激光雷达，毫米波雷达， 超声雷达，摄像装置。每种类型的传感器可以包括多个。应当理解的是，本领域人员可以依据需要合理地选择传感器的种类、数量和位置布局。
在图1A中示出了四个VIU，应当理解的是，图1A中的VIU的数量和位置仅为一种示例，本领域技术人员可以依据实际需求选择合适的VIU的数量和位置。
车辆集成单元VIU 11为多个车辆零部件提供车辆零部件所需的部分或全部的数据处理功能或控制功能。VIU可以具有以下多种功能中的一种或多种。
1、电子控制功能，即VIU用于实现部分或全部车辆零部件内部的电子控制单元(electronic control unit，ECU)提供的电子控制功能。例如，某一车辆零部件所需的控制功能，又例如，某一车辆零部件所需的数据处理功能。
2、与网关相同的功能，即VIU还可以具有部分或全部与网关相同的功能，例如，协议转换功能、协议封装并转发功能以及数据格式转换功能。
3、跨车辆零部件的数据的处理功能，即对从多个车辆零部件的执行器获取的数据进行处理、计算等。
需要说明的是，上述功能中涉及的数据，可以包括车辆零部件中执行器的运行数据，例如，执行器的运动参数，执行器的工作状态等。上述功能中涉及的数据还可以是通过车辆零部件的数据采集单元(例如，敏感元件)采集的数据，例如，通过车辆的敏感元件采集的车辆所行驶的道路的道路信息，或者天气信息等，本申请实施例对此不做具体限定。
在图1A的车辆100示例中，车辆100可以分为多个域(domain)，每个域都有独立的域控制器(domain controller)，具体地，在图1A中，示出了两种域控制器：座舱域控制器CDC 13和整车域控制器VDC 15。
座舱域控制器CDC 13可用于实现车辆100座舱区域的功能控制，在座舱区域的车辆部件可以包括抬头显示装置(head up display，HUD)、仪表盘、收音机、中控屏幕、导航、摄像头等。
整车域控制器VDC 15可用于对车辆的动力电池和引擎141进行协调控制，以提升车辆100的动力性能，在于一些实施例中，图1A中的整车控制器132可以实现VDC的各种功能。
图1A中还示出了车联网设备T-BOX 12和移动数据中心MDC 13。T-BOX 12可用于实现车辆100和车辆内部以及外部设备的通信连接。T-BOX可以通过车辆100的总线获取车内设备数据，也可以通过无线网络和用户的手机通信连接，在一些实施例中，T-BOX 12可以被包括在图1A的通信系统111中。移动数据中心MDC 13用于基于环境感知定位、智能规划决策和车辆运动控制等核心控制算法，输出驱动、传动、转向和制动等执行控制指令，实现车辆100的自动控制，还能够通过人机交互界面，实现车辆驾驶信息的人机交互。在一些实施例中，图1A中的计算平台150可以实现MDC 13的各种功能。
在图1A中的四个VIU 11形成环形拓扑连接网络，每个VIU 11与其近邻位置的传感器通信连接，T-BOX 12、CDC 13、MDC 14以及VDC 15与VIU的环形拓扑连接网络通信连接。VIU 11可以从各传感器获取信息，并将获取的信息上报给CDC 13、MDC 14以及VDC 15。借由环形拓扑网络，T-BOX 12、CDC 13、MDC 14以及VDC 15之间也可以实现相互的通信。
应当理解的是，上述环形拓扑连网络接仅是一种示意，本领域技术人员可以依据需求选择其它合适的VIU连接方式。
VIU之间的连接可以采用例如以太网(ethernet)，VIU和T-BOX 12、CDC 13、MDC 14以及VDC 15的连接可以采用例如以太网或快捷外围部件互连(peripheral component interconnect express,PCIe)技术，VIU和传感器之间的连接可以采用例如控制器局域网络(controller area network，CAN)，局域互联网络(local interconnect network，LIN)，FlexRay，面向媒体的系统传输(media oriented system transport，MOST)等。
图1B为一种实施例中的通信系统的网络架构示意图。该通信系统100可以部署在图1A所示的系统。该通信系统100包括第一控制器110，第二控制器120以及第一传感器111。第一控制器110支持所述第一传感器111对应的数据接口。第二控制器120不支持第一传感器对应111的数据接口。第一控制器110例如可以是图1A中的VDC15，第二控制器120例如可以是图1A中的CDC13。
可选的，该通信系统100还可包括第一解算器112，第一传感器111采集到的数据，经第一解算器112处理为第一数据，该第一数据为符合第一传感器对应的数据接口的数据类型的数据。第一控制器110利用该第一传感器111对应的数据接口获取解算器112输出的来自第一传感器111的第一数据。
可选的，该通信系统100还可包括第二传感器121以及第二解算器122，第二传感器121采集到的数据，经第二解算器122处理为第二传感器对应的数据接口的数据类型的数据。第二控制器120支持该第二传感器对应的数据接口。第一控制器110不支持该第二传感器对应的数据接口。
第二控制器120能够利用该第二传感器对应的数据接口获取解算器122输出的来自第二传感器121的数据。
可以看出，在这样的架构中，第一控制器110支持第一传感器111对应的数据接口，能够实现从第一解算器112获得来自第一传感器111的数据。然而，第二控制器120不支持第一传感器对应111的数据接口，第二控制器120不能从第一解算器112获得来自第一传感器111的数据。类似地，第一控制器110不能从第二解算器122获得来自第二传感器121的数据。
例如，第一传感器111是摄像头，如果第二控制器120需要使用摄像头数据的数据，但是由于第二控制器120不支持第一传感器111对应的数据接口，就需要重新布置一个摄像头，该摄像头可以称为第二传感器，该第二传感器对应的数据接口是第二控制器120所支持的。显然，这样的方案中，在一个车载系统中重复布置了2个摄像头，这就会导致传感器冗余。
如图1C所示的通信系统的架构示意图，本申请的技术方案中，第一控制器110可基于第一通信协议将第一传感器111的数据发送给第二控制器120。对应的，第二控制器120也可以基于第一通信协议将第二传感器121的数据发送给第一控制器110。第一通信协议是第一控制器110和第二控制器120均支持的通信协议。
可以看出，这样的方案第二控制器可以实现从第一控制器获得第一传感器的数据，第一控制器也可以实现从第二控制器获得第二传感器的数据，有助于避免传感器冗余设置，而且，也不需要对车载系统的硬件进行改造。
第一控制器110和第二控制器120可分别是图1A的系统中的两个不同的控制域对应的控制器。
例如，第一控制器110可以是MDC，CDC，或者VDC中的任一种，第二控制器120可以是MDC，CDC，或者VDC中与第一控制器110不同的一个。
当然第一控制器110和第二控制器120不限于上述举例的类型，也可以是其他类型。
如图2所示的控制器的软件架构示意图。该架构可用于第一控制器和/或第二控制器。控制器的软件架构可分为系统软件层、支持软件层、应用软件层。系统软件层包括控制器的硬件系统所运行的操作系统以及编译程序等。支持软件层包括一些接口软件、工具软件、编译程序等。应用软件层包括多个应用程序，用于实现一些业务功能。
下面结合本申请实施例的数据传输方法详细阐述本申请的技术方案。
如图3所示的流程示意图，本申请实施例的数据传输方法包括：
301、第二控制器向第一控制器发送数据获取请求。
该数据获取请求用于请求获取第一传感器的数据。第一控制器支持第一传感器对应的数据接口，第二控制器不支持第一传感器对应的数据接口。
对应的，第一控制器接收来自于第二控制器的数据获取请求。
302、第一控制器接收来自第一传感器的第一数据。
可选地，第一控制器可从第一解算器接收来自第一传感器的第一数据。
第一解算器与第一传感器连接。第一数据是第一解算器对所述第一传感器采集到的数据进行解算处理得到的。例如，第一解算器将第一传感器采集到的数据处理为与第一传感器对应的数据接口相符的数据。这样，第一控制器能够利用第一传感器对应的数据接口，从第一解算器获得来自第一传感器的第一数据。
第一控制器可利用第一传感器对应的数据接口从第一解算器获取该第一数据。
303、第一控制器根据第一通信协议向第二控制器发送转换后的第一数据。
对应的，第二控制器根据第一通信协议，从第一控制器接收来自第一传感器的数据。
可以理解，第二控制器从第一传感器接收的来自第一传感器的数据，是转换后的第一数据。该转换后的第一数据，是第一控制器根据第一通信协议，对第一数据进行转换处理得到的。
第一通信协议为第一控制器和第二控制器均支持的通信协议。第一控制器和第二控制器之间可基于第一通信协议传输传感器的数据。
第二控制器从第一控制器接收来自第一传感器的数据，并根据第一通信协议，解析该接收到的数据。
第一通信协议例如可以是通用流媒体协议是但不限于实时流传输协议(real time streaming protocol，RTSP)，例如具体可以是但不限于：实时传输协议(real-time transport  protocol，RTP)，用户数据报协议(user datagram protocol，UDP)或传输控制协议(transmission control protocol,TCP)中的一种。
可以看出，本申请实施例的数据传输方法，第一控制器支持第一传感器对应的数据接口，第二控制器不支持第一传感器对应的数据接口的情况下，第二控制器向第一控制器发送数据获取请求，第一控制器可以响应于第二控制器发送的数据获取请求，根据第一协议向第二控制器发送根据第一传感器采集到的数据得到的数据，这样第二控制器能够从第一控制器接收来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
这样的方案能够实现第一控制器和第二控制器都可以使用第一传感器的数据。也可以理解为，多个控制器可以使用同一个传感器采集的数据，这样可以避免重复布置相同或类型相同的传感器，这样能够有效减少传感器的数量，降低硬件成本。
可选的，在步骤302之前，第一控制器接收到第二控制器的数据获取请求之后，第一控制器可先判断第二控制器是否支持第一数据对应的数据接口。
若第一控制器确定第二控制器不支持第一数据对应的数据接口，执行步骤302和303，第一控制器接收来自第一传感器的第一数据，根据第一通信协议向第二控制器发送转换后的已数据。
若第一控制器确定第二控制器支持第一数据对应的数据接口，第一控制器可向第二控制器发送指令，指示第二控制器利用第一数据对应的数据接口从第一解算器接收来自第一传感器的数据。
或者，若第一控制器确定第二控制器支持第一数据对应的数据接口，第一传感器向第一解算器发送指令，指示第一解算器向第二控制器发送第一传感器的数据。
可以看出这样的方案中，当第二控制器不支持第一数据对应的数据接口时，第二控制器通过第一控制器，来获得来自第一传感器的数据，第一控制器可理解为数据传输的“中介”。当第二控制器支持第一数据对应的数据接口时，第二控制器则可以利用第一数据对应的数据接口直接从与第一传感器连接的第一解算器接收来自第一传感器的数据。
如图4所示的通信系统的架构示意图，第一控制器和第二控制器可基于第一通信协议传输数据。第二控制器上运行有客户端。该客户端例如可以理解为数据传输的客户端，或者，若第一通信协议为通用流媒体协议，该客户端可理解为基于通用流媒体协议的客户端(RTSP client)。第一控制器上部署有服务器。该服务器可理解为数据传输的服务器，或者可理解为基于RTSP的服务器(RTSP server)。客户端用于监听应用程序发送的用于获取数据的请求。
图4所示的实施例中，应用程序是运行在第一控制器上的应用程序。在其他实施例中，应用程序也可以是运行在与第二控制器建立有通信连接的其他电子设备上运行的应用程序。服务器用于处理客户端发送的数据获取请求。
如图5所示的流程示意图，本申请另一实施例的数据传输方法包括：
501、客户端获取到应用程序发送的第一请求，第一请求用于请求获取第一传感器的数 据。
第一传感器的数据可以是第一传感器采集的数据，也可以是根据第一传感器采集的数据得到的数据。
例如，第一传感器例如可以是但不限于摄像头。第二控制器可以是智能座舱域控制器(CDC)，应用程序可以是行车记录仪应用程序、智能相机应用程序等。
CDC可运行有操作系统，如图6所示的流程示意图，智能座舱域控制器(CDC)启动操作系统，操作系统例如可以是但不限于鸿蒙、安卓、Linux等。
第一请求中可包括指示第一数据的指示信息，或者指示第一传感器的指示信息。
502、客户端向部署在第一控制器的服务器发送数据获取请求，数据获取请求用于请求获取第一传感器的数据。
第二控制器上运行的客户端根据第一请求，向服务器发送数据获取请求。该数据获取请求中可包括指示第一数据的指示信息，或者指示第一传感器的指示信息。
客户端在收到第一请求时，可先判断第二控制器是否支持第一请求所请求的第一传感器对应的数据接口。
若第二控制器不支持第一传感器对应的数据接口，则客户端向部署在第一控制器的服务器发送数据获取请求，请求从第一控制器获取第一传感器的数据。
若第二控制支持第一传感器对应的数据接口，则客户端可指示应用程序通过第一传感器对应的数据接口直接从第一传感器的解算器获取第一传感器的数据；或者客户端可通过第一传感器对应的数据接口从第一传感器的解算器获取第一传感器的数据之后，将第一传感器的数据发送给应用程序。
第一控制器例如可以是但不限于自动驾驶域控制器(MDC)。
503、服务器接收来自第一传感器的第一数据。
可选地，部署在第一控制器的服务器可从第一解算器接收来自第一传感器的第一数据。
第一解算器与第一传感器连接。第一数据是第一解算器对所述第一传感器采集到的数据进行解算处理得到的。例如，第一解算器将第一传感器采集到的数据处理为与第一传感器对应的数据接口相符的数据。
服务器可利用第一传感器对应的数据接口从第一解算器获取该第一数据。
504、服务器基于第一通信协议向客户端发送转换后的第一数据。
例如，部署在智能驾驶域控制器的服务器获取根据第一传感器输出的数据得到的第一数据，然后基于第一通信协议对第一数据进行转换，得到转换后的第一数据，再向客户端发送转换后的第一数据。
可选的，数据传输方法还包括：
505、客户端向应用程序发送第一数据。
可以看出，这样的方案中，第二控制器运行的应用程序，或者与第二控制器建立有通信连接的应用程序，需要获得第一传感器的数据时，可通过向运行在第二控制器的客户端发送第一请求，再由客户端向部署在第一控制器的服务器请求第一传感器的数据。
例如，第一传感器是摄像头，若第二控制器运行有行车记录仪应用程序，行车记录仪应用程序需要获得摄像头的数据，行车记录仪应用程序可向客户端发送第一请求。客户端 根据第一请求，向部署在第一控制器的服务器发送数据获取请求。部署在第一控制器的服务器根据与该摄像头对应的数据接口，从第一解算器获得该摄像头的数据，然后根据通用流媒体协议转换该摄像头的数据之后，将转换后的摄像头的数据发送给客户端。客户端行车记录仪应用程序发送该转换后的摄像头的数据。这样，行车记录仪应用程序通过客户端从第一控制器获得了来自摄像头的数据，从而可以避免重复地部署摄像头。
本申请实施例还提供一种通信系统700，如图7所示的通信系统的架构示意图。本申请实施例的通信系统700包括第一电子装置800和第二电子装置900。
如图8所示的第一电子装置800的结构示意图，第一电子装置800包括第一接口电路801、第二接口电路802和控制器803。第一电子装置800可以为上述图2对应的实施例中的第一控制器110，或者第一电子装置800可以包括第一控制器110。第一电子装置800也可以是芯片或芯片系统，还可以是独立的电子设备。
第一接口电路801和第二接口电路802也可以是收发单元或者部署在收发器。
第一接口电路801和第二接口电路802也可以为通信接口。
第一接口电路801用于接收来自第二电子装置900的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第二电子装置900不支持所述第一传感器的数据接口的协议。
第二接口电路802用于接收来自于所述第一传感器的第一数据。
关于控制器803，在一种可能的实现方式中，控制器803用于使能所述第一接口电路801，根据第一通信协议向第二电子装置900发送转换后的第一数据。
在另一种可能的实现方式中，控制器803用于根据第一通信协议，转换第一数据为第二数据，第二电子装置900支持第二数据对应的协议。第一接口电路801还用于向第二电子装置900发送第二数据。
本申请的实施例中，第一电子装置800可以响应于第二电子装置900发送的数据获取请求，根据第一协议向第二电子装置发送第二数据或者根据第一传感器的数据得到的转换后的数据。这样第二电子装置能够从第一电子装置获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
如图9所示的第二电子装置900的结构示意图，第二电子装置900包括控制器901和接口电路902。第二电子装置900包可以为上述图2对应的实施例中的第二控制器120，或者第二电子装置900包可以包括第二控制器120。第二电子装置900也可以是芯片或芯片系统，还可以是独立的电子设备。
控制器901用于使能接口电路902向第一电子装置800发送数据获取请求。数据获取请求用于请求获取第一传感器的数据，所述第二电子装置900不支持所述第一传感器的数据接口的协议。
控制器901还用于通过接口电路902从第一电子装置800接收转换后的第一数据或第二数据。
本申请的实施例中，第二电子装置900不支持第一传感器对应的数据接口时，能够通 过向第一电子装置800发送数据获取请求，从第一电子装置800获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可以看出，上述数据传输方法的方案可通过可用于该第一电子装置800和第二电子装置900，或者说上述数据传输方法的步骤可通过第一电子装置800和第二电子装置900实现。
例如，关于上述步骤301，可由第二电子装置900的控制器901向第一电子装置800发送数据获取请求。对应的，第一电子装置800的第一接口电路801接收来自控制器901的数据获取请求。关于上述步骤302，可由第一电子装置800的第二接口电路802接收来自第一传感器的第一数据。关于上述步骤303，可由第一电子装置800的控制器803使能第一接口电路801，根据第一通信协议向第二电子装置900发送转换后的第一数据；或者由控制器803根据第一通信协议，转换第一数据为转换后的第一数据(也即，第二数据)，由第一接口电路801向第二电子装置900发送转换后的第一数据。
可以理解，转换后的第一数据，是由来自第一传感器的第一数据转换得到的，那么转换后的第一数据也可以理解为第一传感器的数据。
可以看出，这样的方案中，不支持第一传感器对应的数据接口的第二电子装置900，可通过支持第一传感器对应的数据接口的第一电子装置800，获得第一传感器的数据，从而能够避免重复部署传感器。
应理解，上述数据传输方法的实施例相关补充说明以及技术效果，也适用于本实施例的第一电子装置800和第二电子设备900，此处不再重复说明。
如图10所示的数据传输装置1000的模块示意图，本申请还提供一种数据传输装置1000，包括收发单元1002和处理单元1001，处理单元1001用于控制收发单元1002：
接收来自于第二控制器的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述数据传输装置1000支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
接收来自于所述第一传感器的第一数据；
根据第一通信协议向所述第二控制器发送转换后的第一数据。
本申请的技术方案，数据传输装置1000可以响应于第二控制器发送的数据获取请求，根据第一协议向第二控制器发送根据第一传感器的数据得到的转换后的数据，这样第二控制器能够从第一控制器获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可以理解，该数据传输装置1000可以为或可以部署在上述通信系统中的第一控制器。
在某些实施方式中，所述接收来自于所述第一传感器的第一数据方面，所述收发单元1002具体用于：
利用所述第一传感器对应的数据接口从第一解算器获取所述第一数据，所述第一数据是所述第一解算器对所述第一传感器采集到的数据进行解算处理得到的。
在某些实施方式中，所述第一通信协议是实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
应理解，上述关于数据传输方法的相关补充说明和技术效果也适用于数据传输装置1000，此处不再重复说明。
如图11所示的数据传输装置1100的模块示意图，本申请还提供一种数据传输装置1100，包括收发单元1102和处理单元1101，所述处理单元1101用于控制收发单元1102：
向第一控制器发送数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述数据传输装置1100不支持所述第一传感器对应的数据接口；
根据第一通信协议，接收来自第一控制器的数据。
本申请的技术方案，数据传输装置1100不支持第一传感器对应的数据接口时，能够通过向第一控制器发送数据获取请求，从第一控制器获得来自第一传感器的数据，有助于精简车载系统的硬件配置，避免传感器冗余设置。
可以理解，该数据传输装置1100可以为或可以部署在上述通信系统中的第二控制器。
在某些实施方式中，所述第一通信协议是实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
应理解，上述关于数据传输方法的相关补充说明和技术效果也适用于数据传输装置，此处不再重复说明。
本申请实施例中的第一控制器，或者第二控制器的相关功能可以通过图12中的电子设备1200来实现。图12所示为本申请实施例提供的电子设备1200的结构示意图。如图12所示，该电子设备1200可包括：处理器1201、收发器1205，可选的还包括存储器1202。
所述收发器1205可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1205可以包括接收器和发送器，接收器可以称为接收机、接收电路或接收单元等，用于实现接收功能；发送器可以称为发送机、发送电路或发送单元等。
存储器1202中可存储计算机程序或软件代码或指令1204，该计算机程序或软件代码或指令1204还可称为固件。处理器1201可通过运行其中的计算机程序或软件代码或指令1203，或通过调用存储器1202中存储的计算机程序或软件代码或指令1204，对MAC层和PHY层进行控制，以实现本申请下述各实施例提供的信号传输方法。其中，处理器1201可以为中央处理器(central processing unit，CPU)，存储器1202例如可以为只读存储器(read-only memory，ROM)，或为随机存取存储器(random access memory，RAM)。
本申请中描述的处理器1201和收发器1205可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。
该电子设备1200所包括的各模块仅为示例说明，本申请不对此进行限制。
如前所述，以上实施例描述中的电子设备1200可以是第一控制器或第二控制器，但本申请中描述的电子设备的范围并不限于此，而且电子设备的结构可以不受图12的限制。电子设备可以是独立的设备或者可以是较大设备的一部分。例如所述电子设备的实现形式可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，指令的存储部件；(3)可嵌入在其 他设备内的模块；(4)接收机、智能终端、无线设备、手持机、移动单元、车载设备、云设备、人工智能设备等等；(5)其他等等。
对于电子设备的实现形式是芯片或芯片系统的情况，其中，芯片包括处理器和接口。其中，处理器的数量可以是一个或多个，接口的数量可以是多个。接口用于信号的接收和发送。可选的，该芯片或芯片系统可以包括存储器。存储器中用于保存芯片或芯片系统必要的程序指令和数据。
本申请实施例并且不限制权利要求书的保护范围和适用性。本领域技术人员可以在不脱离本申请实施例范围的情况下对本申请涉及的元件的功能和部署进行适应性更改，或酌情省略、替代或添加各种过程或组件。
在一种实现方式中，电子设备1200为上述方法实施例中的第一控制器，电子设备1200可通过处理器和收发器，实现本申请实施例中由第一控制器执行的任意一种方法的部分或全部步骤，例如处理器可用于控制收发器1205：
接收来自于第二控制器的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
接收来自于所述第一传感器的第一数据；以及
根据第一通信协议向所述第二控制器发送转换后的第一数据。
在另一种实现方式中，电子设备1200为上述方法实施例中的第二控制器，电子设备1200可通过处理器和收发器，实现本申请实施例中由第二控制器执行的任意一种方法的部分或全部步骤，例如处理器可用于控制收发器1205：
向第一控制器发送数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；以及
根据第一通信协议，接收来自第一控制器的数据。
应理解，上述关于数据传输方法实施例的相关补充说明也适用于本实施例的电子装置1200，此处不再重复说明。
本申请提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机指令，该计算机指令指示该服务器执行上述任一实施方式提供的数据传输方法。
还应理解，本文中涉及的第一、第二、第三、第四以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请的范围。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以 硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删减。
本申请实施例装置中的模块可以根据实际需要进行合并、划分和删减。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (15)

  1. 一种数据传输方法，其特征在于，所述方法包括：
    第一控制器接收来自于第二控制器的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
    所述第一控制器接收来自于所述第一传感器的第一数据；
    所述第一控制器根据第一通信协议向所述第二控制器发送转换后的第一数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一控制器接收来自于所述第一传感器的第一数据包括：
    所述第一控制器利用所述第一传感器对应的数据接口从第一解算器获取所述第一数据，所述第一数据是所述第一解算器对所述第一传感器采集到的数据进行解算处理得到的。
  3. 根据权利要求1所述的方法，其特征在于，所述第一通信协议是实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
  4. 一种数据传输方法，其特征在于，所述方法包括：
    第二控制器向第一控制器发送数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
    所述第二控制器根据第一通信协议，接收来自第一控制器的数据。
  5. 根据权利要求4所述的方法，其特征在于，所述第一通信协议是实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
  6. 一种数据传输装置，其特征在于，包括收发单元和处理单元，处理单元用于控制收发单元：
    接收来自于第二控制器的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述数据传输装置支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
    接收来自于所述第一传感器的第一数据；
    根据第一通信协议向所述第二控制器发送转换后的第一数据。
  7. 根据权利要求6所述的数据传输装置，其特征在于，所述接收来自于所述第一传感器的第一数据方面，所述收发单元具体用于：
    利用所述第一传感器对应的数据接口从第一解算器获取所述第一数据，所述第一数据是所述第一解算器对所述第一传感器采集到的数据进行解算处理得到的。
  8. 根据权利要求6所述的数据传输装置，其特征在于，所述第一通信协议是实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
  9. 一种数据传输装置，其特征在于，包括收发单元和处理单元，所述处理单元用于控制收发单元：
    向第一控制器发送数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第一控制器支持所述第一传感器对应的数据接口，所述第二控制器不支持所述第一传感器对应的数据接口；
    根据第一通信协议，接收来自第一控制器的数据。
  10. 根据权利要求9所述的装置，其特征在于，所述第一通信协议是实时流传输协议，实时传输协议，用户数据报协议或传输控制协议中的一种。
  11. 一种第一电子装置，其特征在于，包括第一接口电路、第二接口电路和控制器；
    所述第一接口电路，用于接收来自第二电子装置的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据，所述第二电子装置不支持所述第一传感器的数据接口的协议；
    所述第二接口电路，用于接收来自于所述第一传感器的第一数据；
    所述控制器用于使能所述第一接口电路，根据第一通信协议向所述第二电子装置发送转换后的第一数据。
  12. 一种第一电子装置，其特征在于，包括第一接口电路、第二接口电路和控制器；
    所述第一接口电路，用于接收来自第二电子装置的数据获取请求，所述数据获取请求用于请求获取第一传感器的数据；
    所述第二接口电路，用于接收来自于所述第一传感器的第一数据，所述第二电子装置不支持第一数据对应的协议；
    所述控制器用于根据第一通信协议，转换第一数据为第二数据，其中，所述第二电子装置支持所述第二数据对应的协议；
    所述第一接口电路，还用于向所述第二电子装置发送所述第二数据。
  13. 一种第二电子装置，其特征在于，包括控制器和接口电路，
    所述控制器用于使能所述接口电路向第一电子装置发送数据获取请求，该数据获取请求用于请求获取第一传感器的数据，所述第一电子装置支持所述第一传感器对应的数据接口，所述第二电子装置不支持所述第一传感器对应的数据接口；
    所述控制器还用于利用接口电路，根据第一通信协议，接收来自第一传感器的数据。
  14. 一种电子设备，其特征在于，包括处理器，所述处理器与存储器耦合，所述存储器 用于存储计算机指令，所述处理器执行该计算机指令，使得所述通信设备执行权利要求1-5任一项所述的方法。
  15. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机指令，所述计算机指令指示电子装置执行如权利要求1-5中任一项所述的方法。
PCT/CN2021/080885 2021-03-15 2021-03-15 数据传输方法、装置及系统 Ceased WO2022193103A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2021/080885 WO2022193103A1 (zh) 2021-03-15 2021-03-15 数据传输方法、装置及系统
EP21930699.0A EP4297305B1 (en) 2021-03-15 2021-03-15 Data transmission method, apparatus and system
JP2023556551A JP2024511005A (ja) 2021-03-15 2021-03-15 データ伝送方法、装置及びシステム
CN202180001435.6A CN113170004B (zh) 2021-03-15 2021-03-15 数据传输方法、装置及系统
US18/467,470 US12452336B2 (en) 2021-03-15 2023-09-14 Data transmission method, apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/080885 WO2022193103A1 (zh) 2021-03-15 2021-03-15 数据传输方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/467,470 Continuation US12452336B2 (en) 2021-03-15 2023-09-14 Data transmission method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2022193103A1 true WO2022193103A1 (zh) 2022-09-22

Family

ID=76876014

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/080885 Ceased WO2022193103A1 (zh) 2021-03-15 2021-03-15 数据传输方法、装置及系统

Country Status (5)

Country Link
US (1) US12452336B2 (zh)
EP (1) EP4297305B1 (zh)
JP (1) JP2024511005A (zh)
CN (1) CN113170004B (zh)
WO (1) WO2022193103A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115185253A (zh) * 2022-07-04 2022-10-14 潍柴动力股份有限公司 域控制器操作系统的构建方法及装置
WO2026020281A1 (zh) * 2024-07-22 2026-01-29 深圳引望智能技术有限公司 控制装置、控制系统和智能驾驶设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN205017457U (zh) * 2015-08-20 2016-02-03 济南东方科艺科技发展有限公司 一种智能通风的柜远程控制系统
CN111432356A (zh) * 2018-12-26 2020-07-17 上海伴我科技有限公司 数据转换装置
US10885728B1 (en) * 2019-10-02 2021-01-05 William H. Havins Cognitively optimized user interface for motor vehicle

Family Cites Families (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8863256B1 (en) * 2011-01-14 2014-10-14 Cisco Technology, Inc. System and method for enabling secure transactions using flexible identity management in a vehicular environment
JP5825100B2 (ja) * 2011-05-31 2015-12-02 富士通株式会社 センサデータ収集システム
DE102012215765A1 (de) * 2012-09-05 2014-05-15 Robert Bosch Gmbh Gateway-Modul für ein Kommunikationssystem, Kommunikationssystem und Verfahren zur Übertragung von Daten zwischen Teilnehmern eines Kommunikationssystems
US10178206B2 (en) * 2015-11-10 2019-01-08 Microsoft Technology Licensing, Llc Multi-protocol gateway for connecting sensor devices to cloud
JP6890025B2 (ja) * 2016-05-27 2021-06-18 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカＰａｎａｓｏｎｉｃ Ｉｎｔｅｌｌｅｃｔｕａｌ Ｐｒｏｐｅｒｔｙ Ｃｏｒｐｏｒａｔｉｏｎ ｏｆ Ａｍｅｒｉｃａ 電子制御ユニット、フレーム生成方法及びプログラム
CN106454225A (zh) 2016-09-08 2017-02-22 深圳华汽车科技有限公司 Adas设备摄像头的非独占式接入系统及方法
CN206100302U (zh) 2016-09-08 2017-04-12 深圳华一汽车科技有限公司 Adas设备摄像头的非独占式接入系统
CN110291362B (zh) * 2016-12-06 2020-09-29 日产北美公司 生成用于自主车辆的解决方案数据以克服问题状况
US10430603B2 (en) * 2017-02-28 2019-10-01 GM Global Technology Operations LLC Systems and processes for managing access to vehicle data
US10268203B2 (en) * 2017-04-20 2019-04-23 GM Global Technology Operations LLC Calibration validation for autonomous vehicle operations
CN109428773B (zh) * 2017-08-22 2022-04-22 深圳市道通智能航空技术股份有限公司 一种通信方法和装置
CN109729040B (zh) * 2017-10-27 2022-04-29 伊姆西Ip控股有限责任公司 协议的选择的方法、设备以及计算机可读介质
US10740266B2 (en) * 2017-11-17 2020-08-11 Intel IP Corporation Sensor data pipelining
KR102030012B1 (ko) * 2017-12-27 2019-11-08 주식회사 에이치티씨시스템 통신 프로토콜을 변환하는 인터페이스 장치 및 방법
US10750339B2 (en) * 2018-01-12 2020-08-18 Ford Global Technologies, Llc System for dynamically allocating services between controllers in an automobile
US20190235521A1 (en) * 2018-02-01 2019-08-01 GM Global Technology Operations LLC System and method for end-to-end autonomous vehicle validation
US11163303B2 (en) * 2018-02-13 2021-11-02 Nvidia Corporation Sharing sensor data between multiple controllers to support vehicle operations
WO2020021713A1 (ja) * 2018-07-27 2020-01-30 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ 不正検知方法および不正検知電子制御装置
CN110831062B (zh) * 2018-08-10 2022-02-25 华为技术有限公司 一种通信方法及相关设备
US10798183B2 (en) * 2018-12-13 2020-10-06 Sap Se Tunneling protcol and gateway for distributed computing environments
JP7229783B2 (ja) * 2019-01-10 2023-02-28 エヌ・ティ・ティ・コミュニケーションズ株式会社 車載型情報処理装置、車両情報通信システム、情報処理方法およびプログラム
JP6789333B2 (ja) * 2019-03-01 2020-11-25 三菱電機株式会社 制御装置および通信システム
DE112020001663T5 (de) * 2019-03-29 2022-03-24 Intel Corporation Autonomes Fahrzeugsystem
US10778812B1 (en) * 2019-05-09 2020-09-15 Alibaba Group Holding Limited Data encapsulation conversion and transmission
EP4024244A4 (en) * 2019-08-30 2022-10-19 Panasonic Intellectual Property Corporation of America AUTHENTICATION METHOD, AUTHENTICATION SYSTEM AND AUTHENTICATION DEVICE
US11380147B2 (en) * 2019-09-04 2022-07-05 Pony Ai Inc. System and method for determining vehicle navigation in response to broken or uncalibrated sensors
US11734473B2 (en) * 2019-09-27 2023-08-22 Zoox, Inc. Perception error models
CN110868336B (zh) * 2019-11-11 2021-11-02 北京明略软件系统有限公司 数据管理方法、装置和计算机可读存储介质
CN210745353U (zh) 2019-11-29 2020-06-12 北京新能源汽车技术创新中心有限公司 一种车内摄像单元数据复用的实现装置及汽车
CN111163147A (zh) * 2019-12-24 2020-05-15 深圳供电局有限公司 网关设备、多协议数据传输方法和计算机设备
CN111600909B (zh) * 2020-06-24 2023-06-23 腾讯科技（深圳）有限公司 数据处理方法、装置、协议转换设备及存储介质
CN112165480B (zh) * 2020-09-22 2022-11-11 北京字跳网络技术有限公司 信息获取方法、装置和电子设备
CN112243002B (zh) * 2020-10-10 2023-07-04 腾讯科技（深圳）有限公司 数据转发方法、装置、电子设备以及计算机可读介质
US11743074B2 (en) * 2020-11-09 2023-08-29 Argo AI, LLC Systems and methods for obtaining data from multiple internal vehicle networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN205017457U (zh) * 2015-08-20 2016-02-03 济南东方科艺科技发展有限公司 一种智能通风的柜远程控制系统
CN111432356A (zh) * 2018-12-26 2020-07-17 上海伴我科技有限公司 数据转换装置
US10885728B1 (en) * 2019-10-02 2021-01-05 William H. Havins Cognitively optimized user interface for motor vehicle

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4297305A4 *

Also Published As

Publication number Publication date
JP2024511005A (ja) 2024-03-12
EP4297305A4 (en) 2024-01-24
EP4297305A1 (en) 2023-12-27
CN113170004B (zh) 2023-01-06
CN113170004A (zh) 2021-07-23
EP4297305B1 (en) 2026-02-11
US12452336B2 (en) 2025-10-21
US20240007532A1 (en) 2024-01-04

Similar Documents

Publication Publication Date Title
US20230289174A1 (en) Vehicle upgrade method and apparatus
US11972247B2 (en) Software upgrading method, apparatus, and system
WO2023023975A1 (zh) 一种芯片、芯片制造方法、以及相关装置
US20240127635A1 (en) Expansion unit, in-vehicle device unit, and vehicle system
CN106230678A (zh) 基于车载网关控制器的信息处理方法及网关控制器
CN217435657U (zh) 自动驾驶车辆的电气系统和自动驾驶车辆
US12452336B2 (en) Data transmission method, apparatus, and system
WO2021202244A1 (en) System and method for correlating keep-alive connection communications with unary connection communications
CN116500940A (zh) 应用于车辆的域控制器以及车辆
US20150046342A1 (en) System and method for telematics service of vehicle
WO2023124354A1 (zh) 一种车辆控制器、车辆和车辆控制方法
CN112671547B (zh) 车内业务切片的资源配置方法及装置、系统
CN117130788B (zh) 一种数据处理方法、域控制器、设备及存储介质
US20250202980A1 (en) Information processing method, communication system, and information processing program
CN117692486A (zh) 一种车联网设备控制系统及方法
WO2024026593A1 (zh) 一种协同控车方法及相关装置
CN217279314U (zh) 一种车载数据处理系统
US20240127637A1 (en) Data processing method and communication system
US12335732B2 (en) Detecting spoofed ethernet frames within an autosar communication stack
US20250219900A1 (en) In-vehicle device, information processing method, and information processing program
US20250311017A1 (en) In-vehicle device, information processing method, and information processing program
CN117022303A (zh) 自动驾驶扩展接口控制系统及其控制方法和相关设备
WO2026063925A1 (en) Adaptive diagnostic message routing
CN118612289A (zh) 一种数据处理方法、装置及车载设备
CN118227820A (zh) 数据同步方法和装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2023556551

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2021930699

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 202317064316

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2021930699

Country of ref document: EP

Effective date: 20230921

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 2021930699

Country of ref document: EP