KR102342000B1 - Method and apparatus for playing contents based on presentation time in automotive network - Google Patents

Abstract

Disclosed are a method and apparatus for reproducing content based on a presentation time in a vehicle network. A method of operating a first communication node in a vehicle network includes generating a header including a count field indicating a count of round-up with respect to a reproduction time of a content and a timestamp field indicating the reproduction time of the content; generating a payload field including the header field, and transmitting a frame including the header and the payload field to a second communication node belonging to the vehicle network. Accordingly, the performance of the vehicle network may be improved.

Description

Method and apparatus for playing content based on presentation time in vehicle network

The present invention relates to a communication technology in a vehicle network, and more particularly, to a technology for reproducing content (eg, audio, video) based on a presentation time in a vehicle network.

2. Description of the Related Art As electronic components for vehicles are rapidly becoming electronic, the types and numbers of electronic devices (eg, electronic control units (ECUs)) mounted on vehicles are greatly increased. The electronic device may be largely used in a power train control system, a body control system, a chassis control system, a vehicle network, a multimedia system, and the like. The powertrain control system may refer to an engine control system, an automatic shift control system, or the like. The body control system may refer to a body electronic device control system, a convenience device control system, a lamp control system, and the like. The chassis control system may mean a steering system control system, a brake control system, a suspension control system, or the like. The vehicle network may refer to a controller area network (CAN), a FlexRay-based network, a media oriented system transport (MOST)-based network, and the like. The multimedia system may mean a navigation device system, a telematics system, an infotainment system, or the like.

These systems and electronic devices constituting each of the systems are connected through a vehicle network, and a vehicle network for supporting the respective functions of the electronic devices is required. CAN can support a transmission rate of up to 1Mbps, and can support automatic retransmission of a collided frame and error detection based on a cycle redundancy check (CRC). A FlexRay-based network can support a transmission rate of up to 10 Mbps, and can support simultaneous data transmission through two channels, synchronous data transmission, and the like. The MOST-based network is a communication network for high-quality multimedia and can support transmission rates of up to 150Mbps.

A vehicle's telematics system, infotainment system, and improved safety system require high transmission speed and system scalability, and CAN and FlexRay-based networks do not fully support this. A MOST-based network can support a higher transmission speed than a CAN- and FlexRay-based network, but it consumes a lot of cost to apply the MOST-based network to all vehicle networks. Due to these problems, an Ethernet-based network may be considered as a vehicle network. An Ethernet-based network can support bidirectional communication through a pair of windings, and can support transmission rates of up to 10 Gbps.

Meanwhile, the Ethernet-based network may support a protocol (eg, audio video bridging (AVB) protocol) defined in the IEEE (Institute of Electrical and Electronics Engineers) 1722 standard. In this case, the transmitting communication node may generate a frame including content (eg, audio, video), a timestamp field indicating a presentation time of the content, and the like, and the generated frame can be transmitted. The receiving communication node may receive the frame from the transmitting communication node, and may reproduce the content included in the frame at a presentation time indicated by a timestamp field included in the frame.

However, since the unit of presentation time indicated by the timestamp field is ns (nanosecond), the time that can be expressed by the timestamp field may be limited. In addition, the size of the timestamp field included in the frame is 32 bits (bits), the maximum value of the presentation time indicated by the timestamp field is 4.3 s (second), and the presentation time is round-up (round-up). up) is calculated based on the method. In this case, by the difference between the count of round-up in the transmitting communication node and the count of round-up in the receiving communication node, the reproduction time of the content recognized in the receiving communication node is the reproduction time of the content set in the transmitting communication node may be different from Therefore, the content included in the frame may be played at an inappropriate time.

An object of the present invention to solve the above problems is to provide a method and apparatus for reproducing content for preventing an error in presentation time in a vehicle network.

In order to achieve the above object, a method of operating a first communication node in a vehicle network according to a first embodiment of the present invention for achieving the above object includes a count field indicating a count of round-up with respect to a reproduction time of a content and a count field indicating the reproduction time generating a header including a timestamp field, generating a payload field including the content, and transmitting a frame including the header and the payload field to a second communication node belonging to the vehicle network includes steps.

Here, the header may further include a unit field indicating a unit of the reproduction time, and the unit field may be set to indicate ns, s, ms, or s.

Here, when the unit field indicates ns, the timestamp field may indicate a specific time from 0 to 4.3s, and when the unit field indicates μs, the timestamp field may indicate a specific time from 0 to 4300s Time may be indicated, and when the unit field indicates ms, the timestamp field may indicate a specific time from 0 to 4300000s, and when the unit field indicates s, the timestamp field is 0 A specific time may be indicated from among to 4300000000s.

Here, the frame may be generated based on the IEEE 1722 protocol, and 2 bits among the spare fields included in the header of the frame may be used for the unit field, and among the spare fields, used for the unit field. The remaining bits except for 2 bits may be used for the count field.

Here, the content may be reproduced in _{T A of the following equation,}

T _max may be a maximum value configurable by the timestamp field, C may be the count indicated by the count field, and T _P may be the playback time indicated by the timestamp field.

Here, the vehicle network may include a plurality of end nodes, a plurality of switches, and at least one gateway, and the first communication node may be a first end node among the plurality of end nodes, and the second The second communication node may be a second end node among the plurality of end nodes.

In order to achieve the above object, there is provided a method of operating a first communication node in a vehicle network according to a second embodiment of the present invention, the method comprising: receiving a frame including a header and a payload field from a second communication node belonging to the vehicle network; , confirming a unit of playback time of the content included in the payload field based on the unit field included in the header, and counting round-up for the playback time based on the count field included in the header confirming, confirming the playback time based on a timestamp field included in the header, and playing the content at a time indicated by the unit of the playback time, the count of round-up and the playback time including the steps of

Here, the unit field may indicate ns, μs, ms, or s.

Here, when the unit field indicates ns, the timestamp field may indicate a specific time from 0 to 4.3s, and when the unit field indicates μs, the timestamp field may indicate a specific time from 0 to 4300s Time may be indicated, and when the unit field indicates ms, the timestamp field may indicate a specific time from 0 to 4300000s, and when the unit field indicates s, the timestamp field is 0 A specific time may be indicated from among to 4300000000s.

Here, the frame may be generated based on the IEEE 1722 protocol, and 2 bits among the spare fields included in the header of the frame may be used for the unit field, and among the spare fields, used for the unit field. The remaining bits except for 2 bits may be used for the count field.

Here, the content may be reproduced in _{T A of the following equation,}

T _max may be a maximum value configurable by the timestamp field, C may be the count indicated by the count field, and T _P may be the playback time indicated by the timestamp field.

In order to achieve the above object, in the vehicle network according to the third embodiment of the present invention, the first communication node includes a processor and a memory in which at least one instruction executed by the processor is stored, and the at least one instruction is content reproduction. generating a header including a count field indicating a count of round-up with respect to time and a timestamp field indicating the playback time, generating a payload field including the content, and the header and the payload and transmit a frame including the field to a second communication node belonging to the vehicle network.

Here, the header may further include a unit field indicating a unit of the reproduction time, and the unit field may be set to indicate ns, s, ms, or s.

Here, when the unit field indicates ns, the timestamp field may indicate a specific time from 0 to 4.3s, and when the unit field indicates μs, the timestamp field may indicate a specific time from 0 to 4300s Time may be indicated, and when the unit field indicates ms, the timestamp field may indicate a specific time from 0 to 4300000s, and when the unit field indicates s, the timestamp field is 0 A specific time may be indicated from among to 4300000000s.

Here, the frame may be generated based on an Institute of Electrical and Electronics Engineers (IEEE) 1722 protocol, and 2 bits among reserved fields included in the header of the frame are the unit fields. may be used for , and bits other than 2 bits used for the unit field among the spare fields may be used for the count field.

Here, the content may be reproduced in _{T A of the following equation,}

T _max may be a maximum value configurable by the timestamp field, C may be the count indicated by the count field, and T _P may be the playback time indicated by the timestamp field.

Here, the vehicle network may include a plurality of end nodes, a plurality of switches, and at least one gateway, and the first communication node may be a first end node among the plurality of end nodes, and the second The second communication node may be a second end node among the plurality of end nodes.

According to the present invention, a unit of presentation time indicated by a timestamp field included in a frame is set to s (second), ms (millisecond), s (microsecond) or ns (nanosecond). Therefore, various times may be expressed by the timestamp field. In addition, since the frame transmitted by the transmitting communication node may include a field indicating the count of round-up, the problem of recognition error for the count of round-up in the receiving communication node is solved can be Thus, the receiving communication node can reproduce the content (eg, audio, video) included in the frame at the time dictated by the transmitting communication node. In addition, the performance of the vehicle network can be improved.

1 is a block diagram illustrating a first embodiment of a vehicle network.
2 is a block diagram illustrating a first embodiment of a communication node belonging to a vehicle network.
3 is a block diagram illustrating a second embodiment of a communication node belonging to a vehicle network.
4 is a timing diagram illustrating a first embodiment of a communication method in a vehicle network.
5 is a block diagram illustrating a frame format in a vehicle network.
6 is a timing diagram illustrating a second embodiment of a communication method in a vehicle network.
7 is a timing diagram illustrating a third embodiment of a communication method in a vehicle network.
8 is a timing diagram illustrating a fourth embodiment of a communication method in a vehicle network.

Since the present invention can have various changes and can have various embodiments, specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and it should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention.

Terms such as first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.

When an element is referred to as being “connected” or “connected” to another element, it is understood that it may be directly connected or connected to the other element, but other elements may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that the other element does not exist in the middle.

The terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present application, terms such as “comprise” or “have” are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the accompanying drawings. In describing the present invention, in order to facilitate the overall understanding, the same reference numerals are used for the same components in the drawings, and duplicate descriptions of the same components are omitted.

1 is a block diagram illustrating a first embodiment of a vehicle network.

Referring to FIG. 1 , a communication node constituting a vehicle network may mean a gateway, a switch (or a bridge), an end node, or the like. The gateway 100 may be connected to at least one switch 110 , 110 - 1 , 110 - 2 , 120 , and 130 , and may connect different networks. For example, the gateway 100 includes a switch supporting a controller area network (CAN) (or FlexRay, media oriented system transport (MOST), local interconnect network (LIN), etc.) protocol and Ethernet (ethernet). You can connect between switches that support the protocol. Each of the switches 110 , 110 - 1 , 110 - 2 , 120 , and 130 may be connected to at least one end node 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , and 133 . Each of the switches 110, 110-1, 110-2, 120, and 130 may interconnect the end nodes 111, 112, 113, 121, 122, 123, 131, 132, 133, and an end connected thereto The nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 and 133 may be controlled.

The end nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , and 133 may refer to an electronic control unit (ECU) that controls various devices included in the vehicle. For example, the end nodes 111 , 112 , 113 , 121 , 122 , 123 , 131 , 132 , 133 may include an infotainment device (eg, a head unit, a display device, a navigation device). It may mean an ECU constituting a navigation device, an around view monitoring device, and the like.

On the other hand, communication nodes (ie, gateways, switches, end nodes, etc.) constituting the vehicle network include a star topology, a bus topology, a ring topology, a tree topology, and a mesh. It can be connected by topology or the like. In addition, each of the communication nodes constituting the vehicle network may support a CAN protocol, a FlexRay protocol, a MOST protocol, a LIN protocol, an Ethernet protocol, and the like. Embodiments according to the present invention may be applied to the network topology described above, and the network topology to which embodiments according to the present invention are applied is not limited thereto and may be configured in various ways.

2 is a block diagram illustrating a first embodiment of a communication node belonging to a vehicle network.

Referring to FIG. 2 , the communication node 200 constituting the vehicle network may include a PHY layer unit 210 and a controller unit 220 . In addition, the communication node 200 may further include a regulator (not shown) for supplying power. In this case, the controller unit 220 may be implemented including a medium access control (MAC) layer. The PHY layer unit 210 may receive signals from, or transmit signals to, other communication nodes. The controller unit 220 may control the PHY layer unit 210 and may perform various functions (eg, an infotainment function, etc.). The PHY layer unit 210 and the controller unit 220 may be implemented as one SoC (System on Chip) or may be configured as separate chips.

The PHY layer unit 210 and the controller unit 220 may be connected through a media independent interface (MII) 230 . The MII 230 may mean an interface specified in Institute of Electrical and Electronics Engineers (IEEE) 802.3, and may be configured as a data interface and a management interface between the PHY layer unit 210 and the controller unit 220 . Instead of the MII 230 , one interface among reduced MII (RMII), gigabit MII (GMII), reduced GMII (RGMII), serial GMII (SGMII), and XGMII (10 GMII) may be used. The data interface may include a transmit channel and a receive channel, and each of the channels may have an independent clock, data, and control signal. The management interface may be configured as a two-signal interface, one signal for the clock and the other signal for data.

The PHY layer unit 210 may include a PHY layer interface unit 211 , a PHY layer processor 212 , and a PHY layer memory 213 . The configuration of the PHY layer unit 210 is not limited thereto, and the PHY layer unit 210 may be configured in various ways. The PHY layer interface unit 211 may transmit a signal received from the controller unit 220 to the PHY layer processor 212 , and may transmit a signal received from the PHY layer processor 212 to the controller unit 220 . The PHY layer processor 212 may control the operation of each of the PHY layer interface unit 211 and the PHY layer memory 213 . The PHY layer processor 212 may perform modulation of a signal to be transmitted or demodulation of a received signal. The PHY layer processor 212 may control the PHY layer memory 213 to input or output a signal. The PHY layer memory 213 may store the received signal, and may output the stored signal according to the request of the PHY layer processor 212 .

The controller unit 220 may perform monitoring and control for the PHY layer unit 210 through the MII 230 . The controller unit 220 may include a controller interface unit 221 , a controller processor 222 , a main memory 223 , and an auxiliary memory 224 . The configuration of the controller unit 220 is not limited thereto, and the controller unit 220 may be configured in various ways. The controller interface unit 221 may receive a signal from the PHY layer unit 210 (ie, the PHY layer interface unit 211 ) or an upper layer (not shown), and transmit the received signal to the controller processor 222 . and may transmit a signal received from the controller processor 222 to the PHY layer unit 210 or an upper layer. The controller processor 222 may further include independent memory control logic or integrated memory control logic for controlling the controller interface unit 221 , the main memory 223 and the auxiliary memory 224 . The memory control logic may be implemented by being included in the main memory 223 and the auxiliary memory 224 , or may be implemented by being included in the controller processor 222 .

Each of the main memory 223 and the auxiliary memory 224 may store a signal processed by the controller processor 222 , and may output the stored signal according to a request of the controller processor 222 . The main memory 223 may refer to a volatile memory (eg, random access memory (RAM)) that temporarily stores data required for the operation of the controller processor 222 . The auxiliary memory 224 includes operating system code (eg, a kernel and a device driver) and an application program code for performing a function of the controller processor 220 , etc. This may mean a non-volatile memory in which it is stored. A flash memory having a fast processing speed may be used as the non-volatile memory, or a hard disk drive (HDD), compact disc-read only memory (CD-ROM), etc. for storing a large amount of data this can be used The controller processor 222 may typically be configured as a logic circuit including at least one processing core. As the controller processor 222 , an ARM (Advanced RISC Machines Ltd.)-based core, an atom-based core, or the like may be used.

3 is a block diagram illustrating a second embodiment of a communication node belonging to a vehicle network.

Referring to FIG. 3 , the communication node 300 constituting the vehicle network includes a hardware layer 310 , a hardware abstraction layer (HAL) 330 , a middleware layer 350 and an application layer. (370). The hardware layer 310 may include a PHY layer unit 311 and a MAC layer unit 312 . The PHY layer unit 311 may support the Ethernet protocol, and may be the PHY layer unit 210 described with reference to FIG. 2 . The MAC layer unit 312 may support an Ethernet protocol (eg, IEEE 802.3, etc.), and may be the controller unit 220 described with reference to FIG. 2 .

The hardware layer 310 may support an audio video bridging (AVB) protocol. For example, the hardware layer 310 may support an IEEE 802.1AS time stamping protocol, an IEEE 802.1Q stream reservation protocol (SRP), and an IEEE 802.1Q forwarding & queuing for time-sensitive stream (FQTSS) protocol. IEEE 802.1 AS time stamping protocol is IEEE802. It is possible to support a stamping operation for the transmission/reception time of the message according to the AS. IEEE 802.1Q SRP may support a reservation operation of a stream resource, a reservation operation of a traffic shaper, and the like. The IEEE 802.1Q FQTSS protocol may support a shaping operation of a transmitted message. The hardware layer 310 may support the HAL 330 so that the middleware layer 350 may operate.

The hardware layer 310 may largely support three state modes. For example, the hardware layer 310 may support a normal mode, a sleep mode, and a power off mode. Ethernet communication may be performed in the normal mode. When the state of the hardware layer 310 is the normal mode, the PHY layer unit 311 may operate in a normal mode (eg, INH pin (pin) active state), and the MAC layer unit 312 may operate in an active state (eg, a state in which messages can be transmitted and received). In the sleep mode, Ethernet communication can be performed in a limited manner using minimal power. When the state of the hardware layer 310 is a sleep mode, the PHY layer unit 311 may operate in a sleep mode (eg, INH pin inactive state), and a remote event is detected. It may wake up. Also, the MAC layer unit 312 may operate in an inactive state (eg, a state in which messages cannot be transmitted/received), and may wake up when a local event is detected.

When the state of the hardware layer 310 is the power off mode, the PHY layer unit 311 may operate in a sleep mode (eg, INH pin inactive state), and may wake up when a remote event is detected. have. Also, the MAC layer unit 312 may operate in an inactive state, and power may not be supplied to the MAC layer unit 312 . That is, the MAC layer unit 312 cannot be woken up by a local event. The configuration of the hardware layer 310 is not limited to the above description, and the hardware layer 310 may be configured in various ways.

The HAL 330 may be located between the hardware layer 310 and the middleware layer 350 , and may be used to ensure independence between the plurality of hardware layers 310 . The HAL 330 may be configured as a unit independent of an operating system abstraction layer (OSAL) 351 to be described later, or the HAL 330 may be configured as a unit together with the OSAL 351 .

The middleware layer 350 may include an IP middleware layer operating based on transfer control protocol/internet protocol (TCP/IP), AVB middleware operating based on the AVB protocol, and OSAL 351 . The IP middleware layer may include a diagnostics over internet protocol (DoIP) unit 352 , an EthCC unit 353 , an EthNM unit 354 , and the like. The DoIP unit 352 may be configured to perform diagnostic communications. The EthCC unit 353 may be configured to send and receive control messages. The EthNM unit 354 may be configured to perform network management. The IP middleware layer may support IPv4, internet control message protocol (ICMP), address resolution protocol (ARP), TCP, user datagram protocol (UDP), and the like.

The AVB middleware layer may include a talker unit 355 , a listener unit 356 , and the like. The talker unit 355 may be configured to perform transmission of an AVB stream based on an AVB protocol. The listener unit 356 may be configured to perform reception of the AVB stream based on the AVB protocol. The AVB middleware layer may support IEEE 802.1AS generalized precision time protocol (gPTP), IEEE 1722 AVB transport protocol (AVTP), and the like. IEEE 802.1AS gPTP may support an operation for selecting a grand master based on BMCA (best master clock algorithm), an operation for clock synchronization, and an operation for calculating link delay. IEEE 1722 AVTP may support an operation of generating an Ethernet message including an audio data unit and a video data unit, and the like.

The application layer 370 may include a software interface 371 , an application 372 , and the like. Software interface 371 may support input operation and output operation of signals to application 372 . For example, the software interface 371 may support Scalable Service-Oriented Middleware on Ethernet/Internet Protocol (SOME/IP). The application 372 may include an application operating based on TCP/IP, an application operating based on the AVB protocol, and the like.

On the other hand, in communication between the communication nodes shown in FIG. 2 or FIG. 3 , the first communication node includes content (eg, audio, video) and a timestamp field indicating a presentation time of the content. field) may be generated, and the generated frame may be transmitted. The second communication node may receive the frame from the first communication node, and may reproduce the content included in the frame at a presentation time indicated by a timestamp field included in the frame. Here, the presentation time may be referred to as a “playback time”.

However, since the unit of presentation time indicated by the timestamp field is ns (nanosecond), the time that can be expressed by the timestamp field may be limited. In addition, the size of the timestamp field included in the frame is 32 bits (bits), the maximum value of the presentation time indicated by the timestamp field is 4.3 s (second), and the presentation time is round-up (round-up). up) is calculated based on the method. In this case, by the difference between the count of round-up in the first communication node and the count of round-up in the second communication node, the reproduction time of the content recognized in the second communication node is set in the first communication node. It may be different from the content playback time. Therefore, the content included in the frame may be played at an inappropriate time.

Next, content reproduction techniques for preventing an error in presentation time in a vehicle network will be described. Hereinafter, even when a method (eg, transmission or reception of a frame) performed in the first communication node is described, the second communication node corresponding thereto is a method (eg, a method corresponding to the method performed in the first communication node) For example, reception or transmission of a frame) may be performed. That is, when the operation of the first communication node is described, the corresponding second communication node may perform the operation corresponding to the operation of the first communication node. Conversely, when the operation of the second communication node is described, the corresponding first communication node may perform the operation corresponding to the operation of the switch.

4 is a timing diagram illustrating a first embodiment of a communication method in a vehicle network.

Referring to FIG. 4 , the vehicle network may support the Ethernet protocol and may include a plurality of communication nodes (eg, gateways, switches, bridges, and end nodes). The first communication node may be the first end node 111 illustrated in FIG. 1 , and the second communication node may be the second end node 112 illustrated in FIG. 1 . The first communication node may be referred to as a “transmitting communication node” that transmits a frame including content, and the second communication node may be referred to as a “receiving communication node” that receives the frame from the first communication node. The frame may be generated based on a protocol specified in the IEEE 1722 standard. Each of the first communication node and the second communication node may be configured the same as or similar to the communication node 200 illustrated in FIG. 2 . In addition, each of the first communication node and the second communication node may be configured the same as or similar to the communication node 300 illustrated in FIG. 3 .

The first communication node may generate frame #1 401 including content (eg, audio, video). Frame #1 (401) generated by the first communication node may be configured as follows.

5 is a block diagram illustrating a frame format in a vehicle network.

Referring to FIG. 5 , a frame 500 may include a header and an AVTP payload field 516 . The header may include a subtype data field, a stream identifier field 511 , an AVTP timestamp field 512 , a format specific field, and a packet information field. The subtype data field includes a subtype field 501, a stream identifier valid (SV) field 502, a version field 503, a media clock restart (MR) field 504, and a R (reserved) field. Field 505, gateway information field valid (GV) field 506, AVTP timestamp valid (TV) field 507, sequence number field 508, format specific data field #1 509 and a timestamp uncertainty (TU) field 510 may be included.

The size of the TV field 507 may be 1 bit, and the TV field 507 may indicate a unit of reproduction time (eg, presentation time) set by the AVTP timestamp field 512 . For example, the TV field 507 set to “1” may indicate ns. The TV field 507 set to “0” may indicate that the AVTP timestamp field 512 is not defined. The size of the format specific data field #1 509 may be 7 bits, and the format specific data field #1 509 may be used as a reserved field. The size of the AVTP timestamp field 512 may be 32 bits, and the AVTP timestamp field 512 may indicate the playback time of content (eg, audio, video) included in the AVTP payload field 516 . can When the TV field 507 is set to “1”, the playback time indicated by the AVTP payload field 516 may be a specific time from 0 to 4.3 s (second).

The format specific field may include format specific data field #2 (513). The packet information field may include a stream data length field 514 and a format specific data field #3 515 . The stream data length field 514 may indicate the size (eg, octet) of the AVTP payload field 516 . AVTP payload field 516 may include content (eg, audio, video).

Referring back to FIG. 4 , when the playback time of the content included in the AVTP payload field 516 of frame #1 401 is 1.0 s, the TV of frame #1 401 generated by the first communication node The field 507 may be set to “1”, and the AVTP timestamp field 512 may be set to indicate 1.0s. The first communication node may transmit frame #1 (401). The second communication node may receive the frame #1 401 from the first communication node, and may check information included in the frame #1 401 . For example, the second communication node may determine the content included in the AVTP payload field 516 of frame #1 401 based on the AVTP timestamp field 512 and the TV field 507 of frame #1 401 . It can be seen that the playback time of is 1.0s. Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #1 401 at 1.0s.

Also, the first communication node may generate frame #2 402 including the content. Frame #2 402 may be set to be the same as or similar to frame 500 shown in FIG. 5 . When the playback time of the content included in the AVTP payload field 516 of frame #2 402 is 2.0s, the TV field 507 of frame #2 402 generated by the first communication node is "1" ", and the AVTP timestamp field 512 may be set to indicate 2.0s. The first communication node may transmit frame #2 (402). The second communication node may receive frame #2 (402) from the first communication node, and may check information included in frame #2 (402). For example, the second communication node may determine the content included in the AVTP payload field 516 of frame #2 402 based on the AVTP timestamp field 512 and the TV field 507 of frame #2 402 . It can be seen that the playback time of is 2.0s. Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #2 402 at 2.0s.

Also, the first communication node may generate frame #3 403 including the content. Frame #3 403 may be set to be the same as or similar to frame 500 shown in FIG. 5 . When the playback time of the content included in the AVTP payload field 516 of frame #3 403 is 3.0 s, the TV field 507 of frame #3 403 generated by the first communication node is "1" ", and the AVTP timestamp field 512 may be set to indicate 3.0s. The first communication node may transmit frame #3 (403). The second communication node may receive frame #3 (403) from the first communication node, and may check information included in frame #3 (403). For example, the second communication node may determine the content included in the AVTP payload field 516 of frame #3 403 based on the TV field 507 and the AVTP timestamp field 512 of frame #3 403 . It can be seen that the playback time of is 3.0s. Accordingly, the second communication node can reproduce the content included in the AVTP payload field 516 of frame #3 403 at 3.0s.

Also, the first communication node may generate frame #4 404 containing the content. Frame #4 404 may be set to be the same as or similar to frame 500 shown in FIG. 5 . If the playback time of the content included in the AVTP payload field 516 of frame #4 404 is 4.0s, the TV field 507 of frame #4 404 generated by the first communication node is "1" ", and the AVTP timestamp field 512 may be set to indicate 4.0s. The first communication node may transmit frame #4 (404). The second communication node may receive frame #4 (404) from the first communication node, and may check information included in frame #4 (404). For example, the second communication node may determine the content included in the AVTP payload field 516 of frame #4 404 based on the AVTP timestamp field 512 and the TV field 507 of frame #4 404 . It can be seen that the playback time of is 4.0s. Accordingly, the second communication node can reproduce the content included in the AVTP payload field 516 of frame #4 404 at 4.0s.

Also, the first communication node may generate frame #5 405 including the content. Frame #5 405 may be set to be the same as or similar to frame 500 illustrated in FIG. 5 . When the playback time of the content included in the AVTP payload field 516 of frame #5 405 is 5.0 s, since the maximum value indicated by the AVTP timestamp field 512 is 4.3 s, the first communication node may set the AVTP timestamp field 512 indicating 0.7s (ie, 4.3s + 0.7s) based on the round-up method. Here, the TV field 507 of frame #5 405 may be set to “1”. The first communication node may transmit frame #5 (405).

The second communication node may receive frame #5 (405) from the first communication node, and may check information included in frame #5 (405). For example, the second communication node may confirm that the time unit indicated by the AVTP timestamp field 512 is ns based on the TV field 507 of the frame #5 405 . Also, the playback time (i.e., 0.7 s) indicated by the AVTP timestamp field 512 of frame #5 405 is entered in the AVTP timestamp field 512 of the previous frame (i.e., frame #4 404). Since it is smaller than the reproduction time indicated by (ie, 4.0s), the second communication node may determine that the count of round-up for frame #5 (405) has increased. In this case, the second communication node determines the content included in the AVTP payload field 516 of frame #5 405 based on the TV field 507 and the AVTP timestamp field 512 of frame #5 405. It can be determined that the playback time is 5.0s (ie, 4.3s + 0.7s). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #5 405 at 5.0s.

Also, the first communication node may generate frame #6 (403) including the content. Frame #6 406 may be set to be the same as or similar to frame 500 shown in FIG. 5 . When the playback time of the content included in the AVTP payload field 516 of frame #6 406 is 6.0 s, the TV field 507 of frame #6 406 generated by the first communication node is "1" ", and the AVTP timestamp field 512 may be set to indicate 1.7s. The first communication node may transmit frame #6 (406). The second communication node may receive frame #6 (406) from the first communication node, and may check information included in frame #6 (406). For example, the second communication node may determine the content included in the AVTP payload field 516 of frame #6 406 based on the AVTP timestamp field 512 and the TV field 507 of frame #6 406 . It can be seen that the playback time of is 6.0s. Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #6 406 at 6.0s.

6 is a timing diagram illustrating a second embodiment of a communication method in a vehicle network.

Referring to FIG. 6 , the vehicle network may support the Ethernet protocol and may include a plurality of communication nodes (eg, gateways, switches, bridges, and end nodes). The first communication node may be the first end node 111 illustrated in FIG. 1 , and the second communication node may be the second end node 112 illustrated in FIG. 1 . The first communication node may be referred to as a “transmitting communication node” that transmits a frame including content, and the second communication node may be referred to as a “receiving communication node” that receives the frame from the first communication node. The frame may be generated based on a protocol specified in the IEEE 1722 standard. Each of the first communication node and the second communication node may be configured the same as or similar to the communication node 200 illustrated in FIG. 2 . In addition, each of the first communication node and the second communication node may be configured the same as or similar to the communication node 300 illustrated in FIG. 3 .

The first communication node may generate frame #1 (601) including the content. Frame #1 601 may be set to be the same as or similar to frame 500 shown in FIG. 5 . When the playback time of the content included in the AVTP payload field 516 of the frame #1 601 is 1.0 s, the TV field 507 of the frame #1 601 generated by the first communication node is "1" ", and the AVTP timestamp field 512 may be set to indicate 1.0s. The first communication node may transmit frame #1 (601). The second communication node may receive the frame #1 (601) from the first communication node, and may check information included in the frame #1 (601). For example, the second communication node may determine the content contained in the AVTP payload field 516 of frame #1 601 based on the TV field 507 and the AVTP timestamp field 512 of frame #1 601 . It can be seen that the playback time of is 1.0s. Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #1 601 at 1.0s.

Also, the first communication node may generate frame #2 602 including the content. Frame #2 602 may be set to be the same as or similar to frame 500 shown in FIG. 5 . When the playback time of the content included in the AVTP payload field 516 of frame #2 602 is 2.0s, the TV field 507 of frame #2 602 generated by the first communication node is "1" ", and the AVTP timestamp field 512 may be set to indicate 2.0s. The first communication node may transmit frame #2 (602). The second communication node may receive frame #2 (602) from the first communication node, and may check information included in frame #2 (602). For example, the second communication node may determine the content contained in the AVTP payload field 516 of frame #2 602 based on the TV field 507 and the AVTP timestamp field 512 of frame #2 602. It can be seen that the playback time of is 2.0s. Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #2 602 at 2.0s.

Also, the first communication node may generate frame #3 603 including the content. Frame #3 603 may be set to be the same as or similar to frame 500 illustrated in FIG. 5 . When the playback time of the content included in the AVTP payload field 516 of frame #3 603 is 6.0 s, since the maximum value indicated by the AVTP timestamp field 512 is 4.3 s, the first communication node may set the AVTP timestamp field 512 indicating 1.7s (ie, 4.3s + 1.7s) based on the round-up method. Here, the TV field 507 of frame #3 603 may be set to “1”. The first communication node may transmit frame #3 (603).

The second communication node may receive frame #3 (603) from the first communication node, and may check information included in frame #3 (603). For example, the second communication node may confirm that the time unit indicated by the AVTP timestamp field 512 is ns based on the TV field 507 of the frame #3 603 . Also, the playback time (i.e., 1.7s) indicated by the AVTP timestamp field 512 of frame #3 (603) is entered in the AVTP timestamp field 512 of the previous frame (i.e., frame #2 (602)). Since it is smaller than the playback time indicated by (ie, 2.0s), the second communication node may determine that the count of round-up for frame #3 ( 603 ) has increased. In this case, the second communication node determines the content included in the AVTP payload field 516 of frame #3 603 based on the TV field 507 and the AVTP timestamp field 512 of frame #3 603. It can be determined that the playback time is 6.0s (ie, 4.3s + 1.7s). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #3 603 at 6.0s.

Also, the first communication node may generate frame #4 604 containing the content. Frame #4 604 may be set to be the same as or similar to frame 500 shown in FIG. 5 . When the playback time of the content included in the AVTP payload field 516 of frame #4 604 is 12.0s, since the maximum value indicated by the AVTP timestamp field 512 is 4.3s, the first communication node may set the AVTP timestamp field 512 indicating 3.4s (ie, 4.3s + 4.3s + 3.4s) based on the round-up method. Here, the TV field 507 of frame #4 604 may be set to “1”. The first communication node may transmit frame #4 (604).

The second communication node may receive frame #4 (604) from the first communication node, and may check information included in frame #4 (604). For example, the second communication node may confirm that the time unit indicated by the AVTP timestamp field 512 is ns based on the TV field 507 of frame #4 604 . Also, the playback time (i.e., 3.4s) indicated by the AVTP timestamp field 512 of frame #4 (604) is entered in the AVTP timestamp field 512 of the previous frame (i.e., frame #3 (603)). Because it is greater than the playback time indicated by (i.e., 1.7 s), the second communication node determines that the count of round-up for frame #4 (604) is equal to the count of round-up for frame #3 (603). can judge In this case, the second communication node determines the content contained in the AVTP payload field 516 of frame #4 604 based on the TV field 507 and the AVTP timestamp field 512 of frame #4 604. It can be determined that the playback time is 7.7s (ie, 4.3s + 3.4s). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #4 604 at 7.7s.

In this case, the playback time (ie, 7.7 s) of the content included in frame #4 604 at the second communication node is the playback time (ie, 7.7s) of the content included in frame #4 604 set by the first communication node That is, it may be different from 12.0s). That is, due to an error in recognition of the round-up count of frame #4 (604), the playback time of the content included in frame #4 (604) may be different in each of the first communication node and the second communication node. In order to solve the problem of recognition error for the count of round-up, communication between communication nodes in the vehicle network may be performed as follows.

7 is a timing diagram illustrating a third embodiment of a communication method in a vehicle network.

Referring to FIG. 7 , the vehicle network may support the Ethernet protocol and may include a plurality of communication nodes (eg, gateways, switches, bridges, and end nodes). The first communication node may be the first end node 111 illustrated in FIG. 1 , and the second communication node may be the second end node 112 illustrated in FIG. 1 . The first communication node may be referred to as a “transmitting communication node” that transmits a frame including content, and the second communication node may be referred to as a “receiving communication node” that receives the frame from the first communication node. The frame may be generated based on a protocol specified in the IEEE 1722 standard. Each of the first communication node and the second communication node may be configured the same as or similar to the communication node 200 illustrated in FIG. 2 . In addition, each of the first communication node and the second communication node may be configured the same as or similar to the communication node 300 illustrated in FIG. 3 .

Here, each of the frames 701 , 702 , 703 , and 704 may be set to be the same as or similar to the frame 500 shown in FIG. 5 . However, the format-specific data field #1 509 (eg, a reserved field) of each of the frames 701 , 702 , 703 , and 704 may indicate a round-up count. In this case, the format specific data field #1 509 of each of the frames 701 , 702 , 703 , 704 may be referred to as a “count field” and is included in each of the frames 701 , 702 , 703 , 704 . The playback time of the content can be calculated based on Equation 1 below.

T _A may indicate a time at which content is reproduced, and T _max may indicate a maximum value configurable by the AVTP timestamp field 512 . When the unit of the reproduction time indicated by the AVTP timestamp field 512 is ns, T _max may be 4.3s. C may be a value indicated by the count field, and may be an integer greater than or equal to 0. T _P may be the playback time indicated by the AVTP timestamp field 512 .

The first communication node may generate frame #1 701 including the content. For example, the first communication node may check the reproduction time of the content to be included in the frame #1 701 . When it is confirmed that the reproduction time of the content to be included in the frame #1 701 is 1.0s, the first communication node may determine the unit of the reproduction time of the content. When the unit of the content reproduction time is determined to be ns, the first communication node may set the TV field 507 of the frame #1 701 to 1. Since the count of round-up with respect to the reproduction time of the content to be included in the frame #1 701 is 0, the first communication node may set the count field of the frame #1 701 to indicate 0. Based on each set value of the TV field 507 and the count field, the first communication node may set the AVTP timestamp field 512 of frame #1 701 to indicate 1.0s. The first communication node may generate a header including a TV field (507), a count field, an AVTP timestamp field (512), etc., and frame #1 (701) including a header and an AVTP payload field (516). can be generated, and frame #1 701 can be transmitted.

The second communication node may receive the frame #1 (701) from the first communication node, and may check information included in the frame #1 (701). For example, the second communication node may identify the unit (ie, ns) of the reproduction time of the content included in the frame #1 701 based on the TV field 507 of the frame #1 701, and Based on the count field of #1 ( 701 ), a count (ie, 0) of round-up with respect to the reproduction time of content included in frame #1 ( 701 ) may be checked. In addition, the second communication node transmits the information contained in the AVTP payload field 516 of frame #1 701 based on the TV field 507, the count field, and the AVTP timestamp field 512 of frame #1 701. It can be seen that the content playback time is 1.0s. For example, the second communication node may confirm that the content reproduction time is 1.0s based on the calculation result of Equation 1 (ie, (4.3×0)+1.0). Accordingly, the second communication node can reproduce the content included in the AVTP payload field 516 of the frame #1 701 at 1.0s.

The first communication node may generate frame #2 702 containing the content. For example, the first communication node may check the reproduction time of the content to be included in the frame #2 ( 702 ). When it is confirmed that the reproduction time of the content to be included in the frame #2 702 is 2.0s, the first communication node may determine the unit of the reproduction time of the content. When the unit of the content reproduction time is determined to be ns, the first communication node may set the TV field 507 of the frame #2 702 to 1. Since the count of round-up with respect to the reproduction time of the content to be included in frame #2 702 is 0, the first communication node may set the count field of frame #2 702 to indicate 0. Based on the set values of the TV field 507 and the count field, respectively, the first communication node may set the AVTP timestamp field 512 of frame #2 702 to indicate 2.0s. The first communication node may generate a header including a TV field 507 , a count field, an AVTP timestamp field 512 , and the like, and frame #2 702 including the header and AVTP payload field 516 . may be generated, and frame #2 702 may be transmitted.

The second communication node may receive frame #2 (702) from the first communication node, and may check information included in frame #2 (702). For example, the second communication node may identify the unit (ie, ns) of the reproduction time of the content included in the frame #2 ( 702 ) based on the TV field ( 507 ) of the frame #2 ( 702 ), and the frame Based on the count field of #2 ( 702 ), a count (ie, 0) of round-up with respect to the reproduction time of the content included in frame #2 ( 702 ) may be checked. In addition, the second communication node sends a message to the AVTP payload field 516 of frame #2 702 based on the TV field 507, the count field, and the AVTP timestamp field 512 of frame #2 702. It can be seen that the content playback time is 2.0s. For example, the second communication node may confirm that the content reproduction time is 2.0s based on the calculation result of Equation 1 (ie, (4.3×0)+2.0). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #2 702 at 2.0s.

The first communication node may generate frame #3 703 containing the content. For example, the first communication node may check the reproduction time of content to be included in frame #3 ( 703 ). When it is confirmed that the reproduction time of the content to be included in frame #3 703 is 6.0s, the first communication node may determine the unit of the content reproduction time. When the unit of the content reproduction time is determined to be ns, the first communication node may set the TV field 507 of the frame #3 703 to 1. The maximum value of the playback time indicated by the AVTP timestamp field 512 of frame #3 (703) is 4.3 s, and since the playback time of content to be included in frame #3 (703) is 6.0 s, the first communication node It may be determined that the count of round-up with respect to the reproduction time of content to be included in frame #3 703 (ie, 4.3s (Round-up#1) + 1.7s) is 1. Accordingly, the first communication node may set the count field of frame #3 703 to indicate 1. Based on the set values of the TV field 507 and the count field, respectively, the first communication node may set the AVTP timestamp field 512 of frame #3 703 to indicate 1.7s. The first communication node may generate a header including a TV field 507 , a count field, an AVTP timestamp field 512 , and the like, and frame #3 703 including the header and AVTP payload field 516 . can be generated, and frame #3 (703) can be transmitted.

The second communication node may receive frame #3 (703) from the first communication node, and may check information included in frame #3 (703). For example, the second communication node may identify the unit (ie, ns) of the reproduction time of the content included in frame #3 ( 703 ) based on the TV field ( 507 ) of frame #3 ( 703 ), and the frame Based on the count field of #3 ( 703 ), a count (ie, 1) of round-up with respect to the reproduction time of the content included in frame #3 ( 703 ) may be checked. In addition, the second communication node sends a message to the AVTP payload field 516 of frame #3 703 based on the TV field 507, the count field, and the AVTP timestamp field 512 of frame #3 703. It can be seen that the content playback time is 6.0s (ie, 4.3s (Round-Up #1) + 1.7s). For example, the second communication node may confirm that the content reproduction time is 6.0s based on the calculation result of Equation 1 (ie, (4.3×1)+1.7). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #3 703 at 6.0s.

The first communication node may generate frame #4 704 containing the content. For example, the first communication node may check the reproduction time of content to be included in frame #4 704 . When it is confirmed that the reproduction time of the content to be included in the frame #4 704 is 12.0s, the first communication node may determine the unit of the reproduction time of the content. When the unit of the reproduction time of the content is determined to be ns, the first communication node may set the TV field 507 of the frame #4 704 to 1. Since the maximum value of the playback time indicated by the AVTP timestamp field 512 of frame #4 704 is 4.3 s, and the playback time of the content to be included in frame #4 704 is 12.0 s, the first communication node It is determined that the count of round-up with respect to the playback time (ie, 4.3s (Round-up#1) + 4.3s (Round-up#2) + 3.4s) of the content to be included in frame #4 (704) is 2 can do. Accordingly, the first communication node may set the count field of frame #4 704 to indicate two. Based on each set value of the TV field 507 and the count field, the first communication node may set the AVTP timestamp field 512 of frame #4 704 to indicate 3.4s. The first communication node may generate a header including a TV field (507), a count field, an AVTP timestamp field (512), etc., and frame #4 (704) including a header and an AVTP payload field (516). may be generated, and frame #4 (704) may be transmitted.

The second communication node may receive frame #4 704 from the first communication node, and may check information included in frame #4 704 . For example, the second communication node may identify a unit of playback time (ie, ns) of the content included in frame #4 704 based on the TV field 507 of frame #4 704, Based on the count field of #4 (704), the count (ie, 2) of round-up with respect to the reproduction time of the content included in frame #4 (704) may be confirmed. In addition, the second communication node determines the AVTP payload field 516 of frame #4 704 based on the TV field 507, the count field, and the AVTP timestamp field 512 of frame #4 704. It can be seen that the content playback time is 12.0s (ie, 4.3s (Round-up#1) + 4.3s (Round-up#2) + 3.4s). For example, the second communication node may confirm that the content reproduction time is 12.0s based on the calculation result of Equation 1 (ie, (4.3×2)+3.4). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #4 704 at 12.0s.

8 is a timing diagram illustrating a fourth embodiment of a communication method in a vehicle network.

Referring to FIG. 8 , the vehicle network may support the Ethernet protocol and may include a plurality of communication nodes (eg, gateways, switches, bridges, and end nodes). The first communication node may be the first end node 111 illustrated in FIG. 1 , and the second communication node may be the second end node 112 illustrated in FIG. 1 . The first communication node may be referred to as a “transmitting communication node” that transmits a frame including content, and the second communication node may be referred to as a “receiving communication node” that receives the frame from the first communication node. The frame may be generated based on a protocol specified in the IEEE 1722 standard. Each of the first communication node and the second communication node may be configured the same as or similar to the communication node 200 illustrated in FIG. 2 . In addition, each of the first communication node and the second communication node may be configured the same as or similar to the communication node 300 illustrated in FIG. 3 .

Here, each of the frames 701 , 702 , 703 , and 704 may be set to be the same as or similar to the frame 500 shown in FIG. 5 . However, 2 bits among the format-specific data field #1 509 (eg, a spare field) of each of the frames 701 , 702 , 703 , and 704 may be used to indicate a unit of reproduction time. A field used to indicate a unit of playback time may be referred to as a “unit field”, and the unit field may be set as shown in Table 1 below.

For example, when the unit field is set to "00", the playback time indicated by the AVTP timestamp field 512 of each of the frames 701, 702, 703, 704 may be a specific time from 0 to 4.3 s. have. When the unit field is set to “01”, the playback time indicated by the AVTP timestamp field 512 of each of the frames 701 , 702 , 703 , 704 may be a specific time from 0 to 4300s. When the unit field is set to “10”, the playback time indicated by the AVTP timestamp field 512 of each of the frames 701 , 702 , 703 and 704 may be a specific time from 0 to 4300000s. When the unit field is set to “11”, the playback time indicated by the AVTP timestamp field 512 of each of the frames 701 , 702 , 703 , 704 may be a specific time from 0 to 4300000000s.

When the unit field is used, the TV field 507 in each of the frames 701 , 702 , 703 , and 704 may not be used. In addition, the remaining 5 bits among the format specific data field #1 509 of each of the frames 701 , 702 , 703 , and 704 may be used to indicate the count of round-up. A field used to indicate the count of round-up may be referred to as a “count field”. The reproduction time of content included in each of the frames 701, 702, 703, and 704 may be calculated based on Equation 1, and when the unit field is set to “00”, T _max of Equation 1 is 4.3s one can, the unit and the field be a T _max of equation (1) when set to "01" 4300s, T _max in the equation (1) if the unit field is set to "10" may be a 4300000s, Wide field When is set to "11", T _max of Equation 1 may be 4300000000s.

The first communication node may generate frame #1 801 including the content. For example, the first communication node may check the reproduction time of content to be included in frame #1 801 . When it is confirmed that the reproduction time of the content to be included in the frame #1 701 is 1.0s, the first communication node may determine the unit of the reproduction time of the content. When the unit of the content reproduction time is determined to be μs, the first communication node may set the unit field of the frame #1 701 to “01”. Based on the set value of the unit field, the first communication node may set the AVTP timestamp field 512 of the frame #1 801 to indicate 1.0s. Alternatively, when not only the unit field but also the count field is used, the first communication node may set the count field of frame #1 801 to indicate 0, and 1.0s based on the set value of each of the unit field and the count field The AVTP timestamp field 512 of frame #1 801 may be set to indicate The first communication node may generate a header including a unit field, an AVTP timestamp field 512, etc. (or a header including a unit field, a count field, an AVTP timestamp field 512, etc.), the header and Frame #1 801 including the AVTP payload field 516 may be generated, and frame #1 801 may be transmitted.

The second communication node may receive the frame #1 801 from the first communication node, and may check information included in the frame #1 801 . For example, the second communication node may identify the unit (ie, μs) of the reproduction time of the content included in the frame #1 ( 801 ) based on the unit field of the frame #1 ( 801 ). In addition, when the count field is present in the frame #1 801, the second communication node performs a round- You can check the up count (ie, 0). The second communication node sends the AVTP of frame #1 801 based on the unit field and AVTP timestamp field 512 (or unit field, count field, and AVTP timestamp field 512) of frame #1 801. It can be seen that the playback time of the content included in the payload field 516 is 1.0s. For example, the second communication node may confirm that the content reproduction time is 1.0s based on the calculation result of Equation 1 (ie, (4300×0)+1.0). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of the frame #1 801 at 1.0s.

The first communication node may generate frame #2 802 containing the content. For example, the first communication node may check the reproduction time of content to be included in frame #2 (802). When it is confirmed that the reproduction time of the content to be included in the frame #2 (802) is 2.0s, the first communication node may determine the unit of the reproduction time of the content. When the unit of the content reproduction time is determined to be μs, the first communication node may set the unit field of frame #2 (802) to “01”. Based on the set value of the unit field, the first communication node may set the AVTP timestamp field 512 of frame #2 802 to indicate 2.0s. Alternatively, when not only the unit field but also the count field is used, the first communication node may set the count field of frame #2 802 to indicate 0, and based on the set value of each of the unit field and the count field, 2.0s The AVTP timestamp field 512 of frame #2 802 may be set to indicate The first communication node may generate a header including a unit field, an AVTP timestamp field 512, etc. (or a header including a unit field, a count field, an AVTP timestamp field 512, etc.), the header and Frame #2 802 including the AVTP payload field 516 may be generated, and frame #2 802 may be transmitted.

The second communication node may receive frame #2 (802) from the first communication node, and may check information included in frame #2 (802). For example, the second communication node may identify the unit (ie, μs) of the reproduction time of the content included in the frame #2 (802) based on the unit field of the frame #2 (802). In addition, if the count field exists in frame #2 (802), the second communication node performs a round-about for the playback time of the content included in frame #2 (802) based on the count field of frame #2 (802). You can check the up count (ie, 0). The second communication node sends the AVTP of frame #2 802 based on the unit field and AVTP timestamp field 512 (or unit field, count field and AVTP timestamp field 512) of frame #2 802. It can be seen that the playback time of the content included in the payload field 516 is 2.0s. For example, the second communication node may confirm that the content reproduction time is 2.0s based on the calculation result of Equation 1 (ie, (4300×0)+2.0). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #2 802 at 2.0s.

The first communication node may generate frame #3 803 containing the content. For example, the first communication node may check the reproduction time of the content to be included in the frame #3 (803). When it is confirmed that the reproduction time of the content to be included in the frame #3 803 is 22.0s, the first communication node may determine the unit of the reproduction time of the content. When the unit of the content reproduction time is determined to be μs, the first communication node may set the unit field of frame #3 803 to “01”. Based on the set value of the unit field, the first communication node may set the AVTP timestamp field 512 of frame #3 803 to indicate 22.0s. Alternatively, if not only the unit field but also the count field is used, the first communication node may set the count field of frame #3 803 to indicate 0, and 22.0s based on the set value of each of the unit field and the count field The AVTP timestamp field 512 of frame #3 803 may be set to indicate The first communication node may generate a header including a unit field, an AVTP timestamp field 512, etc. (or a header including a unit field, a count field, an AVTP timestamp field 512, etc.), the header and Frame #3 (803) including the AVTP payload field (516) may be generated, and frame #3 (803) may be transmitted.

The second communication node may receive frame #3 (803) from the first communication node, and may check information included in frame #3 (803). For example, the second communication node may check the unit (ie, μs) of the reproduction time of the content included in the frame #3 (803) based on the unit field of the frame #3 (803). In addition, if the count field exists in frame #3 (803), the second communication node performs a round about the playback time of the content included in frame #3 (803) based on the count field of frame #3 (803) You can check the up count (ie, 0). The second communication node sends the AVTP of frame #3 803 based on the unit field and AVTP timestamp field 512 (or unit field, count field, and AVTP timestamp field 512) of frame #3 803. It can be seen that the playback time of the content included in the payload field 516 is 22.0s. For example, the second communication node may confirm that the content reproduction time is 22.0s based on the calculation result of Equation 1 (ie, (4300×0)+22.0). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #3 803 at 22.0s.

The first communication node may generate frame #4 804 containing the content. For example, the first communication node may check the reproduction time of the content to be included in frame #4 (804). When it is confirmed that the reproduction time of the content to be included in the frame #4 804 is 137.0s, the first communication node may determine the unit of the reproduction time of the content. When the unit of the content reproduction time is determined to be μs, the first communication node may set the unit field of frame #4 804 to “01”. Based on the set value of the unit field, the first communication node may set the AVTP timestamp field 512 of frame #4 804 to indicate 137.0s. Alternatively, when not only the unit field but also the count field is used, the first communication node may set the count field of frame #4 804 to indicate 0, and based on the set value of each of the unit field and the count field, 137.0s The AVTP timestamp field 512 of frame #4 804 may be set to indicate The first communication node may generate a header including a unit field, an AVTP timestamp field 512, etc. (or a header including a unit field, a count field, an AVTP timestamp field 512, etc.), the header and Frame #4 (804) including the AVTP payload field (516) may be generated, and frame #4 (804) may be transmitted.

The second communication node may receive frame #4 (804) from the first communication node, and may check information included in frame #4 (804). For example, the second communication node may identify the unit (ie, μs) of the reproduction time of the content included in the frame #4 (804) based on the unit field of the frame #4 (804). In addition, if the count field is present in frame #4 (804), the second communication node rounds to the playback time of the content included in frame #4 (804) based on the count field of frame #4 (804) - You can check the up count (ie, 0). The second communication node sends the AVTP of frame #4 804 based on the unit field and AVTP timestamp field 512 (or unit field, count field, and AVTP timestamp field 512) of frame #4 804. It can be seen that the playback time of the content included in the payload field 516 is 137.0s. For example, the second communication node may determine that the content reproduction time is 137.0s based on the calculation result of Equation 1 (ie, (4300×0)+137.0). Accordingly, the second communication node may reproduce the content included in the AVTP payload field 516 of frame #2 802 at 137.0s.

The methods according to the present invention may be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the computer-readable medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software.

Examples of computer-readable media include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as at least one software module to perform the operations of the present invention, and vice versa.

Although it has been described with reference to the above embodiments, it will be understood by those skilled in the art that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. will be able

Claims (17)

A method of operating a first communication node in a vehicle network, comprising:
content playback time

A count field indicating a count C of round-up for

generating a header including a timestamp field indicating
generating a payload field including the content; and
transmitting a frame including the header and the payload field to a second communication node belonging to the vehicle network,
The count C of the round-up is the playing time

is the maximum value of the timestamp indicated by the timestamp field

Indicate the number of round-ups for
The content is the maximum value of the timestamp indicated by the timestamp field.

, the count C of the round-up indicated by the count field and the playback time indicated by the timestamp field

The method of operation of the first communication node, which is reproduced at the time indicated by The method according to claim 1,
The header is the playing time

Further comprising a unit field indicating a unit of , wherein the unit field is set to indicate ns (nanosecond), microsecond (microsecond), ms (millisecond) or s (second), the operating method of the first communication node. 3. The method according to claim 2,
When the unit field indicates ns, the timestamp field indicates a specific time from 0 to 4.3s, and when the unit field indicates μs, the timestamp field indicates a specific time from 0 to 4300s, and , when the unit field indicates ms, the timestamp field indicates a specific time from 0 to 4300000s, and when the unit field indicates s, the timestamp field indicates a specific time from 0 to 4300000000s , a method of operation of the first communication node. 3. The method according to claim 2,
The frame is generated based on an Institute of Electrical and Electronics Engineers (IEEE) 1722 protocol, and 2 bits among reserved fields included in the header of the frame are used for the unit field, The remaining bits except for 2 bits used for the unit field among the spare fields are used for the count field, the operating method of the first communication node. The method according to claim 1,
The content is _{reproduced in T A} of the following equation,

A method of operation of the first communication node. In claim 1,
The vehicle network includes a plurality of end nodes, a plurality of switches and at least one gateway, wherein the first communication node is a first end node among the plurality of end nodes. and the second communication node is a second end node among the plurality of end nodes. A method of operating a first communication node in a vehicle network, comprising:
receiving a frame including a header and a payload field from a second communication node belonging to the vehicle network;
Playback time of contents included in the payload field based on the unit field included in the header

checking the units of;
The playing time based on a count field included in the header

ascertaining a count C of round-up to ;
The playback time based on a timestamp field included in the header

to confirm; and
The playback time indicated by the unit field

unit of, the count C of the round-up indicated by the count field and the playback time indicated by the timestamp field

Playing the content at a time indicated by
The count C of the round-up is the playing time

is the maximum value of the timestamp indicated by the timestamp field

Indicating the number of round-up with respect to, the operating method of the first communication node. 8. The method of claim 7,
The unit field indicates ns (nanosecond), microsecond (microsecond), ms (millisecond) or s (second), the operating method of the first communication node. 9. The method of claim 8,
When the unit field indicates ns, the timestamp field indicates a specific time from 0 to 4.3s, and when the unit field indicates μs, the timestamp field indicates a specific time from 0 to 4300s, and , when the unit field indicates ms, the timestamp field indicates a specific time from 0 to 4300000s, and when the unit field indicates s, the timestamp field indicates a specific time from 0 to 4300000000s , a method of operation of the first communication node. 9. The method of claim 8,
The frame is generated based on an Institute of Electrical and Electronics Engineers (IEEE) 1722 protocol, 2 bits among reserved fields included in the header of the frame are used for the unit field, and the unit among the reserved fields The remaining bits except for 2 bits used for the field are used for the count field, the operating method of the first communication node. 8. The method of claim 7,
The content is _{reproduced in T A} of the following equation,

A method of operation of the first communication node. As a first communication node in a vehicle network,
processor; and
At least one instruction executed by the processor comprises a memory (memory) stored,
The at least one command is
content playback time

A count field indicating a count C of round-up for

generating a header including a timestamp field indicating
generate a payload field including the content; and
is executed to transmit a frame including the header and the payload field to a second communication node belonging to the vehicle network,
The count C of the round-up is the playing time

is the maximum value of the timestamp indicated by the timestamp field

indicate the number of round-ups against
The content is the maximum value of the timestamp indicated by the timestamp field.

, the count C of the round-up indicated by the count field and the playback time indicated by the timestamp field

Replayed at the time indicated by the first communication node. 13. The method of claim 12,
The header is the playing time

The first communication node further comprises a unit field indicating a unit of , wherein the unit field is set to indicate ns (nanosecond), microsecond (microsecond), ms (millisecond) or s (second). 14. The method of claim 13,
When the unit field indicates ns, the timestamp field indicates a specific time from 0 to 4.3s, and when the unit field indicates μs, the timestamp field indicates a specific time from 0 to 4300s, and , when the unit field indicates ms, the timestamp field indicates a specific time from 0 to 4300000s, and when the unit field indicates s, the timestamp field indicates a specific time from 0 to 4300000000s , the first communication node. 14. The method of claim 13,
The frame is generated based on an Institute of Electrical and Electronics Engineers (IEEE) 1722 protocol, and 2 bits among reserved fields included in the header of the frame are used for the unit field, The remaining bits except for 2 bits used for the unit field among the reserved fields are used for the count field. 13. The method of claim 12,
The content is _{reproduced in T A} of the following equation,

first communication node. 13. The method of claim 12,
The vehicle network includes a plurality of end nodes, a plurality of switches and at least one gateway, wherein the first communication node is a first end node among the plurality of end nodes. and the second communication node is a second end node among the plurality of end nodes.

Images