Integrated display bridge

WO2025051335A1PCT designated stage expired Publication Date: 2025-03-13CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/DE2024/200101
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-09-08
Filing Date
2024-09-09
Publication Date
2025-03-13

Smart Images

  • Figure DE2024200101_13032025_PF_FP_ABST
    Figure DE2024200101_13032025_PF_FP_ABST
Patent Text Reader

Abstract

Integrated display bridge, wherein the display bridge contains the entire communication unit comprising a protocol engine and a transceiver for communicating with the image-generating remote station.
Need to check novelty before this filing date? Find Prior Art

Description

[0001]202305556 - 1 - TITLE Integrated Display Bridge TECHNICAL FIELD The invention describes the connection of displays to the corresponding image-generating processing units. BASICS According to the state of the art, display panels have data interfaces that cannot bridge large distances. Examples of these are embedded DisplayPort or OpenLDI, often colloquially referred to as LVDS. Low-voltage differential signaling is an interface for high-speed data transmission. The logical bus level is controlled via small voltage differences between two twisted wires. With LVDS, data is transmitted between two devices using small voltage differences that occur on a pair of twisted wires. A positive and a negative signal are sent simultaneously and evaluated at the receiver.The actual data value results from the difference between the two signals and not from the reference to a fixed ground level. LVDS technology is widely used in many modern electronic systems. The best known applications include SATA interfaces in computers. LVDS is also used in display technologies, network infrastructures and in communication between integrated circuits. In consumer devices such as laptops or smartphones, the distance between the display and the image-generating processing unit is so short that this interface can be used natively for a point-to-point connection. Internal 202305556 - 2 - If larger spatial distances (approx. > 30cm) have to be bridged, it is necessary to tunnel the data using a different technology. In consumer applications, this is, for example, HDMI for connecting a monitor to a personal computer.In automotive applications, the image-generating unit is usually located separately from the display due to the limitations of available space in a vehicle. The display is positioned within the interior so that it is easily accessible and legible for passengers, whereas the imaging head unit is usually concealed by several meters of cable. Specialized proprietary systems such as APIX, FPD-Link, GMSL, HD-BASE-T, etc. are used to transmit the image information. These systems "tunnel" the data between the head unit and display, i.e., package it in a dedicated protocol and transmit it via a dedicated physical layer. Furthermore, many displays in consumer and automotive applications offer the option of user input via touchscreen. The touchscreen input can be viewed as a standalone system that functions independently of the display and the content displayed.A touchscreen transmits the position and number of touched points to an external processor unit using a separate controller. This is usually the same unit that hosts the application software and generates the image information. The touch controller usually has embedded interfaces such as I2C or SPI. In the consumer case, this information is often transmitted via a separate controller and a separate data connection such as USB. In the automotive case, the data from the touch controller is also transmitted via the existing point-to-point data tunnel, but in the opposite direction to the image information. Internal 202305556 - 3 - The data transmission therefore has asymmetric transmission characteristics. Especially in the automotive use case, there are additional function blocks within a display control unit, which, for example,enable haptic feedback, as well as the generation of display overlays or the monitoring and validation of the displayed display content for safety reasons. For this purpose, a processor is usually integrated into the display control unit, which receives information from the touch input, controls the haptic feedback, generates display overlays and monitors the displayed display content. This processor can also communicate via the tunneling system or separately via a separate CAN or Ethernet interface via the vehicle network. The attached graphic shows an example of such a system. The problem is that in addition to the tunneling system for transmitting the image information, an additional processor is required to enable the various additional functions and the system has many components, making it complicated and expensive.This object is achieved by the preferred embodiments of this application. In a first preferred embodiment of the integrated display bridge (bridge), this is characterized in that the display bridge (bridge) includes a communication unit comprising a protocol engine and a transceiver for communicating with the image-generating counterpart. In a further preferred embodiment of the integrated display bridge (bridge), this is characterized in that the display bridge (bridge) includes interfaces for controlling the display panel and for receiving touch information. Internal 202305556 - 4 - A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) includes interfaces for controlling haptic feedback.A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) comprises interfaces for controlling the backlight and local dimming. A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) comprises interfaces for generating display fades. A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) comprises interfaces for monitoring the displayed content. A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) comprises interfaces for decrypting protected image content and for analyzing the image content.A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) comprises interfaces for analyzing the image content. A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) combines time synchronization and / or authentication and / or encryption in one chip in order to satisfy the requirements of the applications executed on the head unit ECU (HUECU) and / or the central control unit (CCU) for image reproduction with regard to quality of service and / or security and / or safety. Internal 202305556 - 5 - A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) transmits all information via a single data link.A further preferred embodiment of the integrated display bridge (bridge) is characterized in that the display bridge (bridge) enables the entire communication unit comprising a protocol engine and a transceiver for communication with the image-generating counterpart in the vehicle, a direct point-to-point communication connection or an indirect communication connection via a network connection. DESCRIPTION OF THE DRAWINGS Fig. 1a shows the current system approach Fig. 1b shows the system approach according to the invention DESCRIPTION The following detailed description with reference to the attached drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described here can be practiced. The detailed description contains specific details in order to provide a thorough understanding of the various concepts.However, it will be apparent to one skilled in the art that these concepts may be practiced without these specific details. In particular, although IEEE terminology may be used in this disclosure to illustrate embodiments herein, this should not be construed as limiting the scope of the invention. Some of the embodiments contemplated herein will now be described in more detail with reference to the accompanying drawings. Other embodiments, however, are included within the scope of the subject matter disclosed herein; the disclosed subject matter should not be construed as being limited only to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.In general, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly stated and / or implied from the context in which they are used. All references to an element, device, component, means, step, etc. are to be openly construed to refer to at least one instance of the element, device, component, means, step, etc., unless expressly stated otherwise. The steps of the methods disclosed herein do not need to be performed in the exact order disclosed unless a step is expressly described as following or preceding another step and / or it is implicitly required that a step must follow or precede another step.Any feature of any embodiment disclosed herein may be applied to any other embodiment wherever appropriate. Likewise, any advantage of any embodiment may apply to any other embodiment, and vice versa. Further objects, features, and advantages of the accompanying embodiments will become apparent from the following description. As one skilled in the art will appreciate, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of a fully hardware embodiment, a fully software embodiment (including firmware, resident software, microcode, etc.), or an embodiment that combines software and hardware aspects.For example, the disclosed embodiments may be implemented as a hardware circuit including custom VLSI ("Very Large-Scale Integration") circuits or gate arrays, standard semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices, such as field-programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may be organized, for example, as an object, procedure, or function. Furthermore, embodiments may take the form of a program product stored in one or more computer-readable storage devices, such asinto machine-readable code, computer-readable code, and / or program code, and is referred to below as code. The storage devices may be tangible, non-transitory, and / or non-transferable. In a particular embodiment, the storage devices use only signals to access code. Any combination of one or more computer-readable media may be used. The computer-readable medium may be a computer-readable storage medium. The computer-readable storage medium may be a storage device on which the code is stored. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing.More specific examples (a non-exhaustive list) of the storage device would be the following: an electrical connection with one or more wires, a portable computer diskette, a hard disk, random access memory ("RAM"), read-only memory ("ROM"), erasable programmable read-only memory ("EPROM" or flash memory), portable read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. For the purposes of this document, a computer-readable storage medium may be any tangible medium capable of containing or storing a program for use by or in connection with an instruction execution system, apparatus, or device.Code for performing operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages, including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages ​​such as the "C" programming language or the like, and / or machine languages ​​such as assembly languages. The code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server.In the latter scenario, the remote computer may be connected to the user's computer over any type of network, including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or the connection may be made to an external computer (e.g., over the Internet using an Internet Service Provider ("ISP")). Furthermore, the described features, structures, or features of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as example programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to enable a thorough understanding of embodiments.However, one skilled in the art will recognize that embodiments may be practiced without one or more of the specific details, or with different methods, components, materials, etc. In other instances, well-known structures, materials, or processes are not shown or described in detail to avoid obscuring aspects of an embodiment. Reference throughout this specification to "an embodiment," "an embodiment," or similar language means that a particular feature, structure, or feature described in connection with the embodiment is included in at least one embodiment.Thus, appearances of the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may all refer to the same embodiment, but do not necessarily all refer to the same embodiment, but mean "one or more, but not all, embodiments" unless expressly stated otherwise. The terms "including," "comprising," "having," and variations thereof mean "including, but not limited to," unless expressly stated otherwise. An enumerated list of elements does not imply that some or all of the elements are mutually exclusive unless expressly stated otherwise. The terms "a," "an," and "the" also refer to "one or more" unless expressly stated otherwise.Aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, devices, systems, and program products according to embodiments. It should be understood that each block of the schematic flowcharts and / or schematic block diagrams and combinations of blocks in the schematic flowcharts and / or schematic block diagrams may be implemented by code.This code may be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus for manufacturing a machine such that the instructions executing through the processor of the computer or other programmable data processing apparatus provide means for carrying out the functions / acts specified in the flowcharts and / or block diagrams Internal 202305556 - 10 - The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner such that the instructions stored in the storage device produce an article of manufacture that includes instructions that implement the function / act specified in the flowcharts and / or block diagrams.The code may also be loaded onto a computer, other programmable data processing device, or other devices to cause a series of operational steps to be performed on the computer, other programmable device, or other devices to produce a computer-implemented process, such that the code executing on the computer or other programmable device provides processes for implementing the functions / acts specified in the flowcharts and / or block diagrams. The flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments.In this context, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code containing one or more executable instructions of code for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions specified in the block may occur out of the order indicated in the figures. For example, two blocks shown in sequence may actually execute substantially concurrently, or the blocks may sometimes execute in reverse order, depending on the functionality involved. Other steps and methods may also be devised that correspond in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figures.Internal 202305556 - 11 - Although various arrow types and line types may be used in the flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the illustrated embodiment. For example, an arrow may indicate a wait or monitor time of indefinite duration between enumerated steps of the illustrated embodiment. It is also to be understood that each block of the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by special-purpose hardware-based systems that perform the specified functions or acts, or combinations of hardware and special-purpose code.The description of the elements in each figure may refer to elements in subsequent figures. Like numbers refer to like elements in all figures, including alternative embodiments of like elements. Fig. 1a shows a current display panel used in the automotive environment. Display content or information is transmitted point-to-point. Display "peripherals" such as touch, haptic feedback, displays (display panel) and overlay (overlay), etc., are exchanged via in-vehicle networks, e.g., CAN or Ethernet (in-vehicle network), which provide a variety of functions and capabilities such as the ability to upload music via USB interfaces or connect smartphones via Bluetooth. Internal 202305556 - 12 - At the core of modern infotainment solutions is a system-on-chip (SoC) SerDes Bridge (SerDes Bridge) to display these on the display panel of the Automotive Display ECU. OpenLDI or eDP is used to display information on the display panel. OpenLDI is an open standard for the digital connection of display sources and display devices. This standard is an evolution of the de facto industry standard for connecting display controllers to LCD panels in notebooks. The OpenLDI standard is based on the Video Electronics Standards Association (VESA) and the American National Standards Institute (ANSI). This standard enables a fully digital plug-and-play interface to deliver a video image available on a digital display device. However, the solution with an SoC as the central element is not always optimal. For example, GPS or cellular functions are better implemented on the exterior of the vehicle with the associated antenna as an integrated module.And for USB connectivity, the center of the vehicle or multiple distributed connection points are better suited so that passengers can charge their devices and listen to music together. Implementing such complex infotainment solutions requires a lot of cabling, which significantly impacts the vehicle's weight and costs. The invention describes a display bridge that combines the various functions and requirements of an automotive display in a single chip. Compared to the prior art, it reduces the number of required components and thus the bill of material, while transmitting all information over a single data link. A display bridge is a device or component that connects different display interfaces, thus enabling communication between incompatible video signals.Display bridges convert video signals from one interface standard to another, enabling compatibility between different display technologies. Display bridges often work with standards such as MIPI DSI, LVDS, DisplayPort, HDMI, and RGB. Display bridges are commonly used in mobile devices, tablets, laptops, and other electronic devices to connect processors to display panels that may use different interfaces. Examples: LVDS Display Bridge (LDB): Connects the Image Processing Unit (IPU) to an external LVDS display interface. MIPI Bridge: An interface circuit added to a system to convert its output to a MIPI format. In addition to converting video signals, some display bridges can also transmit commands and settings for display controllers, such as voltage settings and gamma values.Display bridges can be integrated into system-on-chip (SoC) designs or exist as separate components on a circuit board. Furthermore, interface bridge ICs are suitable for mobile peripherals, which support various display interfaces to facilitate the design of feature-rich mobile devices. Fig. 1b shows the display bridge (Bridge) according to the invention, whereby the specialized display bridge (Bridge) comprises the functions shown below. The display bridge (Bridge) contains the entire communication unit (protocol engine and transceiver) for communication with the image-generating counterpart in the vehicle (directly in a point-to-point connection or indirectly via a network), which is not shown in Fig. 1b and is an integral part of the display bridge (Bridge).The display bridge (Bridge) contains all interfaces for controlling the display panel, as well as for receiving touch information, controlling haptic feedback, controlling the backlight (also as local dimming), generating display fades, monitoring the displayed content, decrypting protected image content, and analyzing the image content, e.g. for local dimming. For this purpose, the display bridge (Bridge) can also perform functions such as time synchronization, authentication and encryption and thus masters the application requirements for image reproduction in terms of quality of service, security, safety, etc. This includes, in addition to the functionalities for audio and video reproduction already listed above, that the communication unit (protocol engine and transceiver) of the display bridge (Bridge) information, e.g.via Automotive Ethernet and other bus systems can be exchanged and the display bridge (Bridge) can process all information that is transmitted via a vehicle bus system. For this purpose, the display bridge (Bridge) can use all common bus systems in a vehicle, which control all electronic control units (ECUs) that control everything from brakes, transmission, engine, air conditioning and steering to cameras, radar and acoustic sensors as well as non-cellular and cellular wireless communication and wired communication. ECUs communicate with each other via vehicle buses, which include Controller Area Network (CAN), Media Oriented Systems Transport (MOST), Local Interconnect Network (LIN), PCI-Express, CAN FD, CAN XL and FlexRay™.Furthermore, the display bridge (Bridge) supports bus systems with higher data throughput, lower latency, and lighter weight, reducing complexity and increasing cost efficiency, such as Automotive Ethernet. The display bridge (ISAAC Bridge) thus has triggering, transmission, and decoding functionality for CAN, CAN-FD, LIN, FlexRay, CXPI, SENT, 100BASE-T1 and 1000BASE-T1, and Automotive Ethernet (10BASE-T1S, 100BASE-T1, 1000BASE-T1, 2.5 / 5 / 10GBASE-T1) according to standards such as 802.3cg, 802.3bw, 802.3bp, and 802.3ch. In a further embodiment, the display bridge can contain a memory module or an interface to an external memory module in which, for example, user configurations such as touchscreen calibration, color settings, etc. can be stored, as well as animation sequences that are executed, for example, at startup.This has the advantage that corresponding settings, overlays and animations can be carried out without the external control unit, for example when starting and booting the system or if the controlling unit fails. The interface to the image-generating unit or the vehicle network can be, for example, Automotive Ethernet in accordance with IEEE 802.3, Automotive SerDes in accordance with ASA-ML, asymmetric Automotive Ethernet (in accordance with IEEE 802.3 ISAAC Study Group) or other data interfaces. It would also be conceivable to integrate and transmit a camera data stream to an external processing unit, such as in the case of a camera integrated into the display, for example in instrument clusters with driver monitoring or mirror replacement systems. Furthermore, the display bridge (bridge) allows remote access.The invention can be applied to all displays in a motor vehicle, even those with a reduced range of functions, such as a head-up display that has no touch or haptic functions. The invention can also be applied in consumer electronics, such as connecting an external monitor to a personal computer. Furthermore, the invention can also be applied in the field of industrial automation, where input / output displays with touchscreens and haptic feedback are to be connected to a spatially distant image-generating unit. According to the invention, the display bridge (ISAAC Bridge) according to the invention enables an improvement in specifications for an Ethernet interface used for imaging systems in the automotive industry, in particular cameras.The Display Bridge (ISAAC Bridge) supports highly asymmetric data rates such as 1-10 Gbit / s from the camera, up to 100 Mbit / s. According to the invention, performance limitations in camera modules are also reduced and power supply via the data connection is enabled. This represents a cost-effective solution and forms the basis for simple integration into automotive Ethernet networks, leading to simple, standardized Ethernet solutions in a vehicle. The Display Bridge (ISAAC Bridge) according to the invention enables more efficient Ethernet solutions for asymmetric applications and also solves the problem that current IEEE 802.3 solutions are sufficient. The Display Bridge (ISAAC Bridge) takes the asymmetry in Ethernet PHYs into account and allows the adaptation of existing standards, e.g., 802.3ch Internal 202305556 - 16 - to the needs of new client interfaces for asymmetric PHYs considerations or transmissions.The display bridge (Bridge) also features asymmetric Ethernet over copper (AEoC) with various bandwidth options to accommodate new or modified PHYs, RSs, clients, and media specifications. The display bridge (Bridge) thus represents a cost-effective solution for automotive imaging systems. This approach also serves to replace proprietary solutions and improves efficiency and performance for asymmetric data flows. The display bridge (Bridge) aims to meet the specific requirements of imaging systems in the automotive industry, particularly cameras, by using Ethernet specifications that support highly asymmetric data rates while taking performance, cost, and integration requirements into account. This makes the application suitable for automotive applications as well as consumer electronics and the automation industry. Internal.

Claims

202305556 - 17 - CLAIMS 1. An integrated display bridge (bridge), characterized in that the display bridge (bridge) includes a communication unit comprising a protocol engine and a transceiver for communication with the image-generating counterpart (head unit ECU, CCU).

2. An integrated display bridge according to claim 1, characterized in that the display bridge (bridge) includes interfaces for controlling the display panel and for receiving touch information.

3. An integrated display bridge (bridge) according to claim 1 or 2, characterized in that the display bridge (bridge) includes interfaces for controlling haptic feedback.

4. An integrated display bridge (bridge) according to claims 1 to 3, characterized in that the display bridge (bridge) includes interfaces for controlling the backlight and local dimming. 5.Integrated display bridge (bridge) according to one of claims 1 to 4, characterized in that the display bridge (bridge) comprises interfaces for generating display overlays.

6. Integrated display bridge (bridge) according to one of claims 1 to 5, characterized in that the display bridge (bridge) comprises interfaces for monitoring the displayed content. 202305556 - 18 - 7. The integrated display bridge (bridge) according to one of claims 1 to 6, characterized in that the display bridge (bridge) comprises interfaces for decrypting protected image content and analyzing the image content.

8. The integrated display bridge (bridge) according to one of claims 1 to 7, characterized in that the display bridge (bridge) comprises interfaces for analyzing the image content.

9. The integrated display bridge (bridge) according to one of claims 1 to 8, characterized in that the display bridge (bridge) combines time synchronization and / or authentication and / or encryption in one chip in order to meet the requirements of the image display executed on one of the head unit ECU (HUECU) and / or the central control unit (CCU) with regard to quality of service and / or security and / or safety.The integrated display bridge (bridge) according to one of claims 1 to 9, characterized in that the display bridge (bridge) transmits all information over a single data link.

11. The integrated display bridge (bridge) according to one of claims 1 to 10, characterized in that the display bridge (bridge) enables the entire communication unit, comprising a protocol engine and a transceiver for communication with the image-generating counterpart in the vehicle, via a direct point-to-point communication connection or an indirect communication connection via a network. Internal.

Citation Information

Patent Citations

  • Multi-input multi-output video bridging chip

    CN114095669A

  • Vehicle-mounted display control terminal with multi-channel video display function

    CN211184115U

  • Display Module Having Haptic Function

    US20110193802A1