EP2932636A1 - Synchronization of data packets in a data communication system of a vehicle - Google Patents
Synchronization of data packets in a data communication system of a vehicleInfo
- Publication number
- EP2932636A1 EP2932636A1 EP13802919.4A EP13802919A EP2932636A1 EP 2932636 A1 EP2932636 A1 EP 2932636A1 EP 13802919 A EP13802919 A EP 13802919A EP 2932636 A1 EP2932636 A1 EP 2932636A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- clock
- clocked
- data packets
- communication network
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
- H04J3/062—Synchronisation of signals having the same nominal but fluctuating bit rates, e.g. using buffers
- H04J3/0632—Synchronisation of packets and cells, e.g. transmission of voice via a packet network, circuit emulation service [CES]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L7/00—Arrangements for synchronising receiver with transmitter
- H04L7/0008—Synchronisation information channels, e.g. clock distribution lines
- H04L7/0012—Synchronisation information channels, e.g. clock distribution lines by comparing receiver clock with transmitter clock
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
- H04J3/0635—Clock or time synchronisation in a network
- H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40052—High-speed IEEE 1394 serial bus
- H04L12/40091—Bus bridging
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
- H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/414—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
- H04N21/41422—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance located in transportation means, e.g. personal vehicle
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/4302—Content synchronisation processes, e.g. decoder synchronisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/4363—Adapting the video or multiplex stream to a specific local network, e.g. a IEEE 1394 or Bluetooth® network
- H04N21/43632—Adapting the video or multiplex stream to a specific local network, e.g. a IEEE 1394 or Bluetooth® network involving a wired protocol, e.g. IEEE 1394
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
- H04J3/0635—Clock or time synchronisation in a network
- H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
- H04J3/0658—Clock or time synchronisation among packet nodes
- H04J3/0661—Clock or time synchronisation among packet nodes using timestamps
- H04J3/0664—Clock or time synchronisation among packet nodes using timestamps unidirectional timestamps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40267—Bus for use in transportation systems
- H04L2012/40273—Bus for use in transportation systems the transportation system being a vehicle
Definitions
- the invention relates to a method for synchronizing data packets, or applications and systems, from an untagged, event-controlled or non-time-controlled data communication network with a clocked data communication network and a data communication system for
- Electronic systems of a vehicle can be subdivided into subsystems. For example, engine and transmission control are assigned to the driveline (powertrain), the electronic brake to the chassis (chassis), and comfort functions such as air conditioning to the body area.
- powertrain powertrain
- chassis chassis
- comfort functions such as air conditioning to the body area.
- Subsystem-spanning functions typically require networking of electronic subsystems across subsystem boundaries; This can be realized by one or more system interfaces or gateways.
- Ethernet can also be used in the vehicle.
- High bandwidth Ethernet, high flexibility, and worldwide standardization will be an important system interface of an automobile and such a gateway controller over the next few years.
- ether net-based data communication networks previously used only spora ⁇ disch in automobiles.
- gateways can mediate between the above communication buses.
- the quality and temporal assignability of the data are lost during data transport or data exchange from one communication bus to the other.
- the challenge may be that the clock cycles of the clocked or timed bus system such as MOST should not be lost during transport via the gateway. If, for example, data from an Ethernet network is to be fed into a MOST network, this can mean a high outlay on memory and / or sample rate conversion. a. can lead to a latency of the data transport. As a result, the quality of the data may be worse and the data may no longer be usable in the event of a disaster.
- gateways For vehicle data communication systems, there are implementations referred to as gateways, inter alia, equipped for switching between a clocked and an un-clocked data communication network.
- the time information is lost, that is, while data originating in a timed data communication network is sent to an unpitched data communication network, and vice versa, the temporal synchronization of the data is lost.
- a quality of service of data is not given by these implementations as soon as they leave a switched data communication network. For example, the mapping of data packets to fixed timestamps would have to be preserved. For example, parameters such as delay and jitter can be used to evaluate the quality of service of data.
- Ethernet / Ethernet AVB is currently not used in the vehicle as a network technology, but the bus system MOST is used exclusively in this industry.
- One aspect of the invention relates to a method for synchronizing data packets and a clock from an untimed data communication network to a switched data communication network.
- the timed data communication network may be a MOST Net.
- MOST 150 ie the third generation of MOST, can be used as such kommu ⁇ nikationsnetztechnik.
- the untimed or non-timed data communication network may be an Ethernet Net.
- Ethernet-AVB can be used as the protocol.
- the method comprises the steps of: receiving clocked data packets from the timed data communication network in a gateway at timings of the timed data communication network;
- (first) data from MOST data packets can be sent to the receiver node via Ethernet.
- the receiver node then decodes the received Ethernet packets and reconstructs their clocks. It should be understood that a clock may periodically have clock cycles at which data packets are sent.
- the receiver is to send (second) data into the MOST network, this data is then synchronized with the reconstructed data.
- structured time clock from the receiver node (for first data), which in this case is a transmitter node (for second data). It is also possible to create data packets from this data synchronized to the reconstructed time cycle in the receiver node.
- the receptions and seminars ⁇ ger node outgoing (second) data synchronized by means of the clock pulse of the received (first) data or data stream.
- the time information may be transmitted from the timed data communication network to the untimed data communication network.
- This time information can be used to send data from the non-clocked kommunika ⁇ tion network synchronous to the clocked data communication network, and then synchronized this data then fed into the clocked data communication ⁇ network.
- the unscheduled data communications ⁇ network may operate so transparent that the quality of service scheduling data is not distorted.
- an untimed data communications network such as MOST
- an inherently untimed data communications network such as IEEE 802.3 Ethernet
- the gateway or the interface between the two data communication networks can be regarded as a QoS gateway that can mediate between different clocked data communication networks and non-clocked data communication networks. Due to the nature of the data exchange, the quality of service of the respective transmitting data communication network (or of the data to be transmitted) is not violated during transport into the other data communication network.
- the timing of the clocked data communication network for example, in the case of a MOST Net zwerkes be a MOST clock with 44.1 kHz or 48 kHz.
- This time clock can be transmitted to the receiver node via a suitable transport protocol.
- the time clock is recovered in the receiver node and is thus available to various services.
- the reproduction of data from the MOST network in the Ethernet network can thus take place synchronously with the MOST network.
- the method further comprises the step of: synchronizing a clock of the gateway and a clock of the receiver node via the Unmated data communications network.
- synchronization of the clocks or clocks of both network technologies may be necessary before the data transmission , 1 kHz or 48 kHz) as a house clock in the AVB network and thus to clock the data streams.
- the MOST time clock derived from the MOST-Net zwerk and then through an AVB transport protocol in the Ethernet -Net zwerk be transferred.
- the method further comprises the steps of: collecting a plurality of clocked data packets; Packaging the data of the collected data packets in an untimed data packet. It is not necessary that every non-synchronized data packet is exactly ordered a clocked data packet to ⁇ .
- the transport volume of the non-synchronized data communication network may be larger than that of the kommuni ⁇ cation network, the data of several DA can tenvolutione from the clocked data communication network at the same time are transmitted via the unswitched data communications network.
- the method further comprises the steps of: receiving the second non-clocked one
- Data packets in the gateway Creating clocked data packets from data of the second uncatched data packets; Feeding the clocked data packets into the clocked data communication network at clocks that are synchronous at the time clock at which the second idle data packets were generated in the receiver node.
- the method makes it possible for the data sent by the receiver node to be fed into the timed data communication network synchronously for transmission, without this data having to be buffered and / or that the data packets have to be recoded in a complicated manner.
- data transported with the data packets is part of a stream of media data, for example audio and / or video data.
- the reconstructed clock can then be used to clock the playback of audio and / or video streams.
- this clock cycle can be used to clock audio and / or video streams of an Ethernet device (ie a device connected to the Ethernet node) and / or to feed it into the Ethernet network in synchronism with the MOST clocking.
- the gateway and / or receiver node comprises a codec which generates (non-clocked and / or clocked) data packets of a stream of media data in synchronism with the clock of the clocked data communication network, or converts from analog to digital and vice versa ,
- the analog media stream can be generated with a codec, using the reconstructed timing clock from the digital media stream.
- the gateway includes a codec that generates the clocked from the received data packets un- clocked data packets syn ⁇ chron can be fed without any intermediate storage to the time clock.
- Another aspect of the invention relates to a kommuni- cation system for a vehicle, such as a car, truck or bus.
- the data communication system comprises a gateway for connecting a clocked data communication network and a non-synchronized data ⁇ communication network and a receiver node in unge ⁇ clocked data communication network, wherein the gateway and the receiver node are configured to perform the method as it is described above and below.
- FIG. 1 shows schematically a data communication system according to an embodiment of the invention.
- FIG. 2 is a diagram explaining a method for synchronizing data packets according to an embodiment of the invention.
- 3 schematically shows a data communication system according to an embodiment of the invention.
- FIG. 4 is a diagram explaining a method of synchronizing data packets according to an embodiment of the invention.
- Fig. 1 shows schematically a data communication system 10, which includes a MOST Net zwerk 12 as a clocked data communication network 12 and an Ethernet Net zwerk 14 as ungetaktetes kommu ⁇ nikationsnetztechnik 14.
- the MOST Net zwerk 12 which has the topology of a ring is thereby operated with a MOST time clock, d. H.
- MOST time clock d. H.
- data packets are sent between the MOST nodes 16, which may each be part of a vehicle control unit 18.
- the Ethernet Net zwerk 14 includes a plurality of nodes 20, which may include ⁇ example, a switch 22 or an Ethernet interface 24 of a vehicle control unit 26.
- the two networks 12, 14 are connected by means of a gateway 28 which comprises both a MOST node 16 and an Ethernet node 20, for example in the form of a switch.
- the MOST ring 12 is characterized by a temporal synchronicity with a clock rate of 44.1 kHz (audio clock rate a CD) or 48 kHz (clock rate of a DVD-Audio).
- this clock is provided by a timing master and all participants of the MOST Net zwerkes 12 synchronize to this clock, ie all work in sync to this master clock. Therefore, it is possible to set up a synchronous data stream between source and sink, for example between two of the controllers 18.
- the gateway 28 may be the master providing the master clock. However, if data streaming is to be performed by the controller 26 to one of the controllers 18, then synchrony issues may occur.
- control unit 26 can also generate a working cycle of, for example, 44.1 kHz (eg by means of oscillator circuits, etc.), the cycle generally does not have to be synchronized with the MOST network 12, ie deviations may occur this clock and the
- MOST network clock for example MOST: 44.101 kHz, control unit 44.099 kHz.
- MOST network clock for example MOST: 44.101 kHz, control unit 44.099 kHz.
- Fig. 2 is a diagram explaining a method for synchronizing data packets.
- the gateway 28 receives MOST data packets from the clocked MOST network 12, each arriving at times defined by the MOST clock.
- the MOST data packets may be based on a first audio or video data stream.
- the gateway then packages the data from the clocked data packets into Ethernet data packets and provides them with a time stamp from which the time at which the respective MOST data packet arrives at the gateway can be reconstructed.
- step 32 the Ethernet data packets are sent over the Ethernet network 14 to the receiver node 24.
- the encoded in the Ethernet data packets MOST clock is transported over the Ethernet Net zwerk 14.
- the receiver node reads the timestamps from the Ethernet data packets together with the transmission frequency of the Ethernet data, the number of packets received and the local clock and reconstructs the MOST clock of the MOST Net 12 zwerkes from this data, for example by means of Timestamp, the transmission frequency and / or the number of packets. In this way, the MOST clock in the controller 26 and in the receiver node 24 can be recovered.
- the Ethernet node 24 In step 36, the Ethernet node 24 generates Ethernet data packets that are based for example on a further, second audio ⁇ or video data stream, which is for example sent from the controller 26 to a controller 18 which is connected to the MOST Net 12 zwerk. These second Ethernet data packets are provided with a time stamp which is based on the re ⁇ constructed MOST clock.
- the second Ethernet data packets are synchronized based on a timing synchronous with the reconstructed MOST clock. In this way, the second Ethernet data packets are sent with a derived time clock that is synchronous to the MOST clock.
- the gateway 38 receives the second Ethernet data packets and obtains the time clock of these data packets on the basis of their time stamp, transmission rate, number of packets and / or access time. help with his local tact.
- the data contained in the second Ethernet data packets can be fed synchronously to the MOST clock of the MOST Net 12 zwerkes without caching in the MOST Net 12 zwerk.
- Fig. 2 illustrates the transport of the MOST clock in the accounts 24 of the Ethernet Net zwerkes 14.
- the MOST clock can be restored there and used there to synchronize other applications.
- the data communication system 10 may be in a MOST clock domain 40 and a
- Ethernet clock domain 42 are divided.
- the MOST clock domain 40 extends virtually over the MOST Net zwerk 12 to the receiving node 24. If, as just described, the timing of the MOST network 12 is transmitted via the gateway 28 to the controller 28 and the controller 28 this time clock used to generate the data streaming ⁇ works, the source (receiving node 24 and control unit 28) with the same time clock as the sink, or parts of the sink (control unit 18). Therefore, it is possible, without the use of mechanisms such as insertion or omission of audio data or a clock rate conversion, the data streaming of the controller 28 via the gateway 28 in the time-controlled MOST Net zwerk 12 bring and send to the sink.
- Ethernet Net zwerk 14 for example, IEEE802.1AS in combination with IEEE1722 to synchronize the clock rates (the timer of the gateway and the node 24) and IEEE1722 to transfer the data.
- the Ethernet data packets can be transmitted with the IEEE1722 protocol, which has a fixed transmission cycle. Audio data is typically transmitted in a regular 8 kHz cycle. These fixed transmission cycles allow a planning of the data transport. Fig. 3 shows parts of the data communication system 10 de ⁇ tailored. The statements made below regarding audio data also apply to video data or streamed data in general.
- the MOST clock (for example 48 kHz) and the uncompressed audio data are transmitted to the A / V codec 52 of the gateway 28 via the I2S -BU S 50 of the MOST node 16 or MOST controller 16.
- the MOST controller 16 of the gateway 28 as the I2S master before the clock to the A / V codec 52 and thus clocks it finally.
- the audio data is packaged by a packetizer 54 in IEEE1722 data packets and sent via the Ethernet interface 20 in synchronism with the I2S-BU S 50 via an Ethernet clock (which originates from a system clock 56).
- the controller 26 receives this data and regenerates the timing of the audio data.
- the system clock 58 of the controller 26 previously synchronized with the gateway 28
- the data from the audio stream are used.
- the audio data of an application 62 can also be made available analogously via the DAC (Digital to Analog) converter and can be reproduced synchronously with the MOST clock.
- the regenerated timing clock may now also be used to trigger audio data output from the controller 26. This data can in turn be transmitted back to the gateway 28 and fed into the MOST Net 12 zwerk.
- An application 64 thereby generates analog audio data which are packaged by an audio codec 66 into data packets which are sent from the Ethernet interface 24 to the gateway 28.
- the packaging and sending of the data packets is controlled by a clock module 68 which reconstructs 12 of the data packets with the data from the MOST Net 12 the MOST clock and has restored.
- the clock module 68 thus provides the Ethernet data packets with a derived MOST clock.
- Ethernet data packets are received in the Ethernet interface 20 in the gateway 28, and by means of the in the Ethernet-Da ⁇ tenzige encoded derived MOST clock processed ketene to MOST pa- (for example, with an IC codec 52) and in the MOST-Net zwerk 12 fed.
- a clock module 70 evaluates the Ethernet data packets to the derived MOST clock processed ketene to MOST pa- (for example, with an IC codec 52) and in the MOST-Net zwerk 12 fed.
- a clock module 70 evaluates the Ethernet data packets to the derived
- the MOST clock transmitted to the Ethernet network 14 may be referred to as "house clock” and is available to the audio systems and video systems within the Ethernet Net 12 as drivers of data processing and data transfer
- a “sample clock” may indicate the sample rate used to convert an analog to the digital signal in the codec 66 and also to restore the analog signal in the DAC converter 60 after digital transmission.
- FIG. 4 shows a diagram with data packets that can be sent in the two networks 12 and 14. In the diagram of FIG. 4, the time is plotted to the right.
- the data packets 72 of the MOST network 12 are shown, which are each sent to a MOST clock 70.
- the bus frequency or the time clock 70 and thus the transmission rate of the MOST network 12 is 48 kHz.
- the clock of 48 kHz was chosen.
- the second line of the diagram shows data packets 74 of the
- the clock frequency 76 of the IEEE1722 protocol is 8 kHz in the first version of the standard, ie exactly six times slower than the MOST clock 70.
- the data of six data packets 72 can thus be transmitted in an IEEE 1722 cycle in a data packet 74.
- the third row of the diagram shows reconstructed data packets 78, which are generated in the control unit 26 from the Ethernet data packets 74 and which at the same time provide a reconstructed time clock 80.
- the fourth row of the diagram shows data packets 82 which have a derived clock 84 which has been synchronized with the MOST clock 70 via the reconstructed clock 80.
- the fifth line of the diagram shows data packets 88 having an asynchronous timing 90 that has not been synchronized with the MOST clock 70.
- FIG. 4 also shows three data streams 92, 94, 96 which may be analog audio streams and which are explained below.
- the data flow through the gateway 28 is shown in the first two lines.
- the MOST data packets 72 are received by the gateway 28, and the data stream 92 is transmitted to the control unit 26 by the IEEE 1722 transport protocol into the Ethernet network 12, as explained above.
- This data stream 72 is thus provided by means of QoS guarantees (provided by AVB)
- the controller 26 restores the clock 70 of the MOST Net 12 and thus generates the reconstructed clock 80, with which the DAC converter 60 is operated to restore the data stream 92.
- the data stream 92 restored in the control unit 26 is now synchronous with the original MOST clock 70.
- the data packets 78 are delayed due to the processing and implementation in the gateway 28 in comparison to the data packets 72.
- the clock 80 can now be used in the control unit 26 as already mentioned "house clock", in order to derive therefrom a clock 84 which controls the generation of the data stream 94.
- the data stream 94 is then synchronous with the data stream 92 and thereby also synchronous with the MOST Clock 70.
- the data stream 96 is shown as an example of a data stream that is not in sync with the "house clock” and therefore the MOST clock 70.
- the frequency 90 of the data stream 96 is almost 48 kHz, for example 47.9 kHz data stream
- the gateway 28 Since the data stream 96 is not synchronous with the clock 70 and thus the transmission frequency of the IEEE1722 protocol, in part only five data packets 88 can be collected and transmitted in the cycle of 8 kHz (125 ps). As a result, a data packet 88 '(temporally) is lost, as shown by way of example. If the data stream 96 is an audio stream, this effect will be reflected in the streaming of the data
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102012223307.5A DE102012223307B4 (en) | 2012-12-14 | 2012-12-14 | Synchronizing data packets in a data communication system of a vehicle |
PCT/EP2013/075215 WO2014090612A1 (en) | 2012-12-14 | 2013-12-02 | Synchronization of data packets in a data communication system of a vehicle |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2932636A1 true EP2932636A1 (en) | 2015-10-21 |
Family
ID=49759273
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13802919.4A Ceased EP2932636A1 (en) | 2012-12-14 | 2013-12-02 | Synchronization of data packets in a data communication system of a vehicle |
Country Status (5)
Country | Link |
---|---|
US (1) | US20150333899A1 (en) |
EP (1) | EP2932636A1 (en) |
CN (1) | CN104871461A (en) |
DE (1) | DE102012223307B4 (en) |
WO (1) | WO2014090612A1 (en) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101542016B1 (en) * | 2014-09-17 | 2015-08-05 | 성균관대학교산학협력단 | Gateway apparatus and method for synchronizing heterogeneous network domains in vehicle |
DE102014114883A1 (en) * | 2014-10-14 | 2016-04-14 | Beckhoff Automation Gmbh | Method and system for monitoring a first subscriber of a communication network |
DE102015206051A1 (en) * | 2015-04-02 | 2016-10-06 | Robert Bosch Gmbh | Method and device for data transmission in a computer network |
WO2016177661A1 (en) * | 2015-05-05 | 2016-11-10 | Continental Teves Ag & Co. Ohg | Connecting control devices and the v2x unit via wlan or bluetooth, and v2x unit which has update memory |
DE102015212561B4 (en) * | 2015-07-06 | 2017-06-14 | Continental Automotive Gmbh | Synchronizing clocked and non-clocked data communication networks |
US10074066B2 (en) * | 2016-01-16 | 2018-09-11 | International Business Machines Corporation | Two phase predictive approach for supply network optimization |
DE102016007576B3 (en) * | 2016-06-21 | 2017-11-02 | Audi Ag | Transmission of TDM-coded data over a communication channel according to the I²S protocol |
US10958576B2 (en) * | 2019-02-14 | 2021-03-23 | GM Global Technology Operations LLC | Systems and methods for data processing and storage in vehicles having a zone-based, central computing in-vehicle communications network architecture |
DE102021202188A1 (en) * | 2021-03-08 | 2022-09-08 | Robert Bosch Gesellschaft mit beschränkter Haftung | Method and device for time synchronization of a first vehicle and a second vehicle |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2001271632A1 (en) * | 2000-07-26 | 2002-02-05 | Thomson Licensing S.A. | Multi-media jitter removal in an asynchronous digital home network |
US6970481B2 (en) * | 2001-04-17 | 2005-11-29 | Microsoft Corporation | Methods and systems for distributing multimedia data over heterogeneous networks |
CN101385264B (en) * | 2006-02-17 | 2012-11-07 | 标准微体系有限公司 | Receiver circuit, transmitter circuit and communication network |
JP4926648B2 (en) * | 2006-10-27 | 2012-05-09 | 富士通セミコンダクター株式会社 | In-vehicle gateway device |
EP2073448B1 (en) * | 2007-12-17 | 2020-06-17 | Avago Technologies International Sales Pte. Limited | Method and system for a centralized vehicular electronics system utilizing Ethernet with audio video bridging |
DE102008049600A1 (en) * | 2008-09-30 | 2010-04-01 | Bayerische Motoren Werke Aktiengesellschaft | Ethernet media oriented systems transport gateway unit for use in motor vehicle, has integrated service or resource reservation protocol service quality requirement that is received particularly by Ethernet network nodes |
DE102009028645B4 (en) * | 2009-08-19 | 2014-04-03 | Raumfeld Gmbh | Method and arrangement for the synchronization of data streams in networks and a corresponding computer program and a corresponding computer-readable storage medium |
DE102010003248B4 (en) * | 2010-03-25 | 2024-01-18 | Bayerische Motoren Werke Aktiengesellschaft | Method and device for processing data in a network of a vehicle |
US20120158990A1 (en) * | 2010-12-17 | 2012-06-21 | Cisco Technology, Inc. | Transporting a CBR Data Stream Over a Packet Switched Network |
US8775681B2 (en) * | 2011-04-27 | 2014-07-08 | GM Global Technology Operations LLC | Cross-network synchronization of application S/W execution using flexray global time |
DE102012204586A1 (en) * | 2012-03-22 | 2013-10-17 | Bayerische Motoren Werke Aktiengesellschaft | Gateway, node and method for a vehicle |
-
2012
- 2012-12-14 DE DE102012223307.5A patent/DE102012223307B4/en active Active
-
2013
- 2013-12-02 EP EP13802919.4A patent/EP2932636A1/en not_active Ceased
- 2013-12-02 WO PCT/EP2013/075215 patent/WO2014090612A1/en active Application Filing
- 2013-12-02 CN CN201380065462.5A patent/CN104871461A/en active Pending
- 2013-12-02 US US14/652,411 patent/US20150333899A1/en not_active Abandoned
Non-Patent Citations (2)
Title |
---|
None * |
See also references of WO2014090612A1 * |
Also Published As
Publication number | Publication date |
---|---|
US20150333899A1 (en) | 2015-11-19 |
DE102012223307B4 (en) | 2021-03-04 |
WO2014090612A1 (en) | 2014-06-19 |
DE102012223307A1 (en) | 2014-06-18 |
CN104871461A (en) | 2015-08-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE102012223307B4 (en) | Synchronizing data packets in a data communication system of a vehicle | |
DE102018132290B4 (en) | In-vehicle system, gateway, relay, non-transitory computer-readable medium storing a program, information processing method, information processing system and vehicle | |
DE69933594T2 (en) | Improvements in time synchronization in distributed systems | |
DE102005018837A1 (en) | Method and device for synchronizing two bus systems and arrangement of two bus systems | |
EP3706340A1 (en) | Method for synchronisation of clocks in nodes of a vehicle network and node adapted to carry out the method | |
DE60316758T2 (en) | System for the synchronization of commands, as well as a method, a control device and a target device for the same system | |
EP2893672A1 (en) | Data recording device for a vehicle network | |
DE102013226977B3 (en) | Communication node for a packet-switched data network and method for its operation | |
WO2014090448A1 (en) | Synchronizing of data packages in a data communication system of a vehicle | |
DE102015212561B4 (en) | Synchronizing clocked and non-clocked data communication networks | |
DE102014100628B4 (en) | Bus system and method for transmitting data in real time | |
WO2015155333A1 (en) | Method for operating a subscriber of a communication network | |
DE102010003248B4 (en) | Method and device for processing data in a network of a vehicle | |
EP3042473A1 (en) | Method for transmitting messages in a computer network and computer network | |
DE10327548A1 (en) | Method, device and system for exchanging data via a bus system | |
DE102019219475B4 (en) | Method for optimizing the time synchronization between network devices connected via a communication network | |
WO2018215305A1 (en) | Bus converter | |
DE102004009889A1 (en) | Synchronous multi-cluster network architecture involves transmission of individual data frames with defined temporal relationship between sub-networks for real-rime-compatible transmission | |
DE102004062683A1 (en) | Method for controlling a transmission with short data telegrams | |
DE102010027167B4 (en) | Communication system and method for isochronous data transmission in real time | |
DE102017011458A1 (en) | Subscriber of a bus system, method of operation and a bus system | |
WO2021099585A1 (en) | Method, system, and gateway for linking time-sensitive fieldbuses | |
DE102008046914A1 (en) | Method for synchronizing a receiver and a transmitter in a communication system, and a transmitting station and receiving station adapted for use in the method according to the invention | |
WO2019016299A1 (en) | Timestamp unit and communication control unit for a subscriber station of a communication network | |
DE102013020768A1 (en) | Method for time synchronization in cycle-based bus network movement e.g. motor car bus network movement, involves sending reference bus time to bus network, and determining bus time based on reference bus time |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20150714 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20191216 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: CONTINENTAL AUTOMOTIVE GMBH |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20200521 |