WO2013082901A1 - Procédé et système de gestion de message d'événement 1588 - Google Patents

Procédé et système de gestion de message d'événement 1588 Download PDF

Info

Publication number
WO2013082901A1
WO2013082901A1 PCT/CN2012/073611 CN2012073611W WO2013082901A1 WO 2013082901 A1 WO2013082901 A1 WO 2013082901A1 CN 2012073611 W CN2012073611 W CN 2012073611W WO 2013082901 A1 WO2013082901 A1 WO 2013082901A1
Authority
WO
WIPO (PCT)
Prior art keywords
timestamp
receiving
sending
message
event
Prior art date
Application number
PCT/CN2012/073611
Other languages
English (en)
Chinese (zh)
Inventor
张波
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013082901A1 publication Critical patent/WO2013082901A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method and system for processing an IEEE 1588 protocol event message. Background technique
  • the Institute of Electrical and Electronics Engineers has developed the IEEE 1588 standard, the precision clock synchronization protocol standard for network measurement and control systems.
  • the standard defines a Precision Time Protocol (PTP) for obtaining precise time through network packets.
  • PTP Precision Time Protocol
  • the protocol works in conjunction with hardware and software to enable accurate time synchronization of nodes on the network.
  • the synchronization accuracy can reach microseconds. This method of obtaining synchronization through the network protocol simplifies the system networking connection, reduces the cost, and ensures the accuracy requirement, so it is widely used in the fields of test instruments, industry, network communication and the like.
  • a PTP system is a distributed network system consisting of PTP devices or non-PTP devices.
  • the PTP protocol details how the real-time clocks in the system are synchronized with each other.
  • the system is a hierarchical structure of master-slave synchronization.
  • the reference master clock of the whole system is at the top of the hierarchical structure.
  • the PTP timing messages are exchanged to obtain synchronization between devices.
  • the slave devices adjust their clocks according to the acquired timing messages. , to reach the same time as the hierarchical master device.
  • the PTP protocol defines event messages and general messages.
  • the event message is an accurate timestamp message containing the transmission and reception, while the ordinary message does not require an accurate timestamp.
  • the event message includes a synchronization message (Sync), a delay request message (Dday_Req), a peer delay request message (Pdelay_Req), and a peer delay response message (Pdelay_Resp).
  • Sync synchronization message
  • Dday_Req delay request message
  • Pdelay_Req peer delay request message
  • Pdelay_Resp peer delay response message
  • the PTP protocol synchronization mechanism is: The main clock port of the network sends a Sync message, and the transmission time t1 of the packet is recorded. When it is a one-step mode, the timestamp tl is added to the Sync message. When the channel is sent, in the two-step mode, the timestamp tl is sent in the next normal message FollowJJp; after receiving the Sync message, the slave clock port of the network records the receiving time t2 of the message, and stores the timestamp t2 and The corresponding packet identifier transmits the timestamp t2 to the software for processing. The software obtains the timestamps tl and t2 of the packet by searching for the packet identifier corresponding to the timestamp t2.
  • a Dday_Req message is sent from the clock port, and the transmission time t3 of the message is recorded.
  • the master clock port After receiving the Dday_Req packet, the master clock port records the receiving time t4 of the packet, and sends the timestamp t4 to the slave clock port through the ordinary packet Delay_Resp.
  • the PTP protocol peer-to-peer delay measurement method is as follows: The A port of the network sends a Pdelay_Req message, and the transmission time of the message is recorded. The B port of the other end of the network receives the Pdday_Req message and records the receiving time of the packet. T2, the timestamp t2 is read out to hardware processing or software processing. Then, the B port sends a Pdday_Resp message, and records the sending time t3 of the packet. When it is a one-step mode, the timestamps t3 and t2 are added to the Pdelay-Resp message to be sent in the same way.
  • the timestamp t2 is added to the Pdday_Resp message, and the timestamp t3 is sent in the normal message Pdelay_Resp_Follow_Up (the following message of the peer delay request response).
  • Pdelay_Resp_Follow_Up the following message of the peer delay request response.
  • the software After receiving the A port Pdday- Resp message, note the reception time T4 the packet, and reads out the time stamp t 4 to software processing or hardware processing.
  • the software has several different methods.
  • the timestamps t3 and t2 are directly added to the calibration field correctionField of the Pdday_Resp message.
  • the timestamp is set.
  • the time difference between t3 and t2 is added to the Pdelay_Resp_Follow_Up message, or t2 is added to the Pdelay_Resp message, and t3 is added to the Pdday_Resp_Follow_Up message.
  • Tdday [(t2-tl)+(t4-t3)]/2.
  • the PTP protocol When processing the received event packet, the PTP protocol needs to process the timestamp of the received event packet, temporarily store the timestamp and the corresponding packet identifier, and read it to the hardware or software through a dedicated interface. Reason. This process requires additional software and hardware resources, and the processing is complicated. Summary of the invention
  • the technical problem to be solved by the embodiment of the present invention is to provide a method and system for processing 1588 event messages, so as to solve the problem that the current time stamp processing method consumes additional software and hardware resources and the processing process is complicated.
  • the embodiment of the present invention provides a method for processing a 1588 event packet, including:
  • the sending processing module identifies the 1588 event packet, and obtains the timestamp of the current time as the sending timestamp, and adds the sending timestamp and the receiving timestamp reserved field to the 1588 event packet for sending.
  • the receiving processing module identifies the 1588 event packet, obtains the timestamp of the current time, and adds the obtained timestamp to the receiving timestamp reservation field.
  • the sending processing module identifies that the 1588 event message is specifically:
  • the sending processing module After the 1588 event packet is written in the buffer area, the sending processing module reads the 1588 event packet from the sending buffer and parses and identifies the packet as a 1588 event packet.
  • the timestamp of the current time is obtained as the sending timestamp.
  • the request time management module obtains the current timestamp as the sending timestamp.
  • the receiving processing module obtains the timestamp of the current time, and adds the obtained timestamp to the receiving timestamp reserved field, specifically:
  • the receiving processing module receives the data, and when the SFD is detected, requests the timestamp of the current time, parses and identifies the received packet as a 1588 event packet, and replaces the received timestamp reservation field of the 1588 event packet with the obtained timestamp; The 1588 event message is written to the receive buffer.
  • the synchronization message Sync, the delay request message Delay_Req, and the peer delay request message Pdday_Req in the 1588 event message add a 10 byte reception report after the transmission timestamp field.
  • Peer-to-peer response packet in the 1588 event packet The Pdday_Resp format does not reserve the timestamp field for receiving Pdelay_Res packets. Add 10 bytes to receive the packet time field requestingPortReceiptTimestamp at the end of the packet.
  • the embodiment of the present invention further provides a processing system for a 1588 event message, including: a sending processing module, configured to: after identifying a 1588 event message, obtain a timestamp of the current time as a sending timestamp, and send The timestamp and receive timestamp reserved fields are added to the 1588 event message for transmission;
  • a sending processing module configured to: after identifying a 1588 event message, obtain a timestamp of the current time as a sending timestamp, and send The timestamp and receive timestamp reserved fields are added to the 1588 event message for transmission;
  • the receiving processing module is configured to: after identifying the 1588 event packet, obtain a timestamp of the current time, and add the obtained timestamp to the receiving timestamp reserved field;
  • a time management module configured to generate a sending timestamp and a receiving message timestamp.
  • the above system further comprises
  • the PTP protocol stack is configured to generate a 1588 event message, and send the 1588 event message to the sending buffer by using a sending communication interface; and configured to read the received message data from the receiving buffer through the receiving communication interface to obtain the 1588 event.
  • Sending a communication interface which is used to write 1588 event message data generated by the PTP protocol stack into the sending buffer;
  • a sending buffer configured to store a 1588 event message generated by the PTP protocol stack, and read the buffered message data when the sending processing module needs data, complete management and control of the buffer; and receive buffer for receiving and receiving Processing 1588 event packets received by the module;
  • the receiving communication interface is configured to read the 1588 event message from the receiving buffer, and transmit the 1588 event message to the PTP protocol stack for processing;
  • a time management module for calibrating time according to the PTP protocol stack.
  • the sending processing module is specifically configured to:
  • the network When the network is idle, if there is a packet in the transmission buffer that needs to be sent, it enters the sending state.
  • the frame preamble preamble and the frame start flag SFD are generated.
  • the data sent by the buffer is read at the same time, and the sent message is parsed. If the sent message is a 1588 event message, after the SFD is sent, the current transmission module is obtained from the time management module.
  • the timestamp is used as the sending timestamp, and the sending timestamp and the receiving timestamp reserved field are added to the 1588 event message.
  • the sending processing module is further configured to:
  • the receiving processing module is specifically configured to:
  • the time management module acquires the receiving time stamp of the received data, and writes the received data into the receiving buffer, and the receiving processing module parses
  • the data packet is a 1588 event packet
  • the receiving timestamp is used to replace the receiving timestamp reserved field of the 1588 event message
  • the CRC is calculated when the data is received, and the verification result information is written into the receiving buffer.
  • the technical solution provided by the embodiment of the present invention saves software and hardware resources, reduces processing complexity, and can be compatible with current technical solutions to ensure interoperability between devices. . DRAWINGS
  • Figure 1 is a flow chart of a first embodiment of the present invention
  • 2 is a format of a 1588 event message Sync, Delay_Req, and Pdelay_Req message according to an embodiment of the present invention
  • FIG. 3 is a format of a 1588 event message Pdday_Resp message according to an embodiment of the present invention.
  • FIG. 4 is a structural diagram of a second embodiment of the present invention. detailed description
  • a 10 byte reception timestamp field is added at the end of each 1588 event message field.
  • the last received receive timestamp field of the 1588 event message field is the same as the message format defined in the embodiment of the present invention.
  • FIG. 1 it is a flowchart of a first embodiment of the present invention, which provides a method for processing a 1588 event packet, which specifically includes
  • Step S101 When the data is sent, the sending processing module identifies the 1588 event packet, obtains the timestamp of the current time, and uses the timestamp of the current time as the sending timestamp (TxTimestamp) data and the receiving timestamp (RxTimestamp) reserved field. It is added to the 1588 event packet and sent out. When the current standard 1588 event packet format is compatible, the receiving reservation timestamp field is not added.
  • the upper layer module writes a 1588 event message to the sending buffer
  • the sending processing module reads the 1588 event message from the sending buffer, parses and recognizes that the message is a 1588 event message, and sends the message.
  • the start time of the 1588 event packet is sent by the request processing module when the 1588 event packet is sent.
  • (TxTimestamp) field is sent out; after the sending processing module sends the sending timestamp (TxTimestamp) field, it sends a 10-byte receiving timestamp (RxTimestamp) reserved field.
  • TxTimestamp sending timestamp
  • RxTimestamp 10-byte receiving timestamp
  • Step S102 After receiving the data, the receiving processing module identifies the 1588 event message, obtains the timestamp of the current time, and adds the acquired timestamp to the receiving reserved timestamp reserved field.
  • the receiving processing module receives the data, and when the SFD is detected, requests to acquire the timestamp of the current time; the receiving processing module parses and identifies the received packet as a 1588 event packet, and replaces the 1588 event packet with the obtained timestamp.
  • the receiving time stamp (RxTimestamp) field the receiving processing module writes the 1588 event message to the receiving buffer area; the upper layer module reads the message from the receiving buffer area, and extracts the timestamp information of the 1588 event message and processes it.
  • FIG. 2 it is a format of the event 1588 event Sync, Delay_Req, Pdelay_Req message in the embodiment of the present invention.
  • the event message Sync and Delay_Req formats only send the message timestamp field TxTimestamp.
  • the message field is extended in hardware and software processing, and 10 bytes are received after the TxTimestamp field. Timestamp RxTimestamp.
  • the last 10 bytes of the event packet Pdelay_Req are reserved fields, which are redefined in the hardware and software processing to receive the message timestamp RxTimestamp.
  • the timestamp field of the Pdelay_Resp packet is not reserved in the event packet Pdelay_Resp format.
  • the field is extended in hardware and software processing, and 10 bytes are received at the end of the packet. Poke the field requestPortReceiptTimestamp.
  • FIG. 4 it is a structural diagram of a second embodiment of the present invention, which provides a processing system for a 1588 event message, specifically including a PTP protocol stack 400, a transmission communication interface 401, a transmission buffer 402, a transmission processing module 403, and a time. a management module 404, a receiving processing module 405, a receiving buffer 406, and a receiving communication interface 407, where
  • the PTP protocol stack 400 implements the 1588 protocol, completes time synchronization protocol processing between networks, line delay measurement, and 1588 maintenance management functions. Specifically, the PTP protocol stack 400 is configured to generate a 1588 event message, write the message data into the sending buffer 402 through the sending communication interface 401, and read the received message from the receiving buffer 406 through the receiving communication interface 407. Data, obtained Take the 1588 event packet and the corresponding timestamp.
  • the sending communication interface 401 is configured to write the packet data of the PTP protocol stack 400 into the sending buffer 402, and complete the conversion function of the sending interface.
  • the sending buffer 402 is configured to write a message to be sent to the cache, and read the message data in the buffer when the sending processing module 403 needs data, and complete management and control of the buffer.
  • the sending processing module 403 mainly performs the network port media access control (MAC) sending function, and is used to generate a frame preamble and a SFD if a packet needs to be sent in the sending buffer 402 when the network is idle.
  • the data of the sending buffer 402 is read at the same time, and the sent message is parsed.
  • MAC network port media access control
  • the timestamp module 404 obtains the current timestamp sent as the sending timestamp, and The sending timestamp and the receiving timestamp reserved field (RxTimestamp or requestingPortReceiptTimestam field) are added to the 1588 event message; if the sending message is a user data packet (UDP) message, the 1588 message can be encapsulated in the layer. In the Layer 2 and Layer 4 Ethernet packets, when the packet is encapsulated in the packet of layer 4, it is a UDP packet. Then, the checksum added to the sending timestamp is recalculated, and the sending timestamp is replaced in the 1588 event. Send the timestamp field TxTimestamp and send it out;
  • the difference between the sending time t3 of the Pdday_Resp event message and the time t2 received by the event message Pdelay_Req needs to be calculated, and the correction field is replaced by the difference field.
  • the RxTimestamp or requestingPortReceiptTimestam field is written to all 0s. This field should not be added when compatible with the standard 1588 message format. All transmitted data is calculated to generate a Cyclic Redundancy Check (CRC), and the CRC data is added to the last of the transmitted data and sent out.
  • CRC Cyclic Redundancy Check
  • the time management module 404 is responsible for the management of the local time for generating the time for transmitting and receiving messages, while calibrating the time according to the PTP protocol stack 400.
  • the receiving processing module 405 mainly performs the MAC receiving function of the network port. When the data is valid, the data is received and the validity of the data is determined. When the received data is SFD, the receiving time stamp of the received data is obtained by the time management module. 405, the received data is written into the receive buffer 406; when the receive processing module 405 parses the data packet into a 1588 event message, the RxTimestamp or requestPortReceiptTimestamp field of the 1588 event message is replaced with the receive timestamp, or in the standard 1588 event message field.
  • the receiving time stamp (RxTimestamp) data is added and written into the receiving buffer 406; meanwhile, the receiving processing module 405 calculates a CRC check on the data when receiving the data, and writes the check result information into the receive buffer 406.
  • the receive buffer 406 manages a buffer for receiving data, and is used by the receive and receive processing module 405 to write the data into the cache;
  • the receiving communication interface 407 reads the data from the receiving buffer 406, transfers the data to the PTP protocol stack 400 for processing, and completes the conversion of the receiving interface.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)

Abstract

La présente invention appartient au domaine technique des communications réseau. Elle se rapporte à un procédé de gestion de message d'événement 1588. Le procédé selon l'invention comprend les étapes suivantes : lors de la transmission de données, un module de gestion de transmission identifie un message d'événement 1588 ; il acquiert l'estampille temporelle du moment actuel en tant qu'une estampille temporelle de transmission ; et il ajoute une estampille temporelle de transmission ainsi qu'un champ de réservation d'estampille temporelle de réception dans le message d'événement 1588 en vue de la transmission. D'un autre côté, lors de la réception de données, un module de gestion de réception identifie le message d'événement 1588 ; il acquiert l'estampille temporelle du moment actuel et il ajoute l'estampille temporelle acquise dans le champ de réservation d'estampille temporelle de réception. La présente invention se rapporte d'autre part à un système de gestion de message d'événement 1588. La solution technique décrite dans la présente invention permet : d'économiser encore plus de ressources logicielles et matérielles ; et de réduire la complexité de la gestion. D'autre part, comme cette solution technique peut également être compatible avec la solution technique actuelle, elle garantit l'interopérabilité entre les dispositifs.
PCT/CN2012/073611 2011-12-05 2012-04-06 Procédé et système de gestion de message d'événement 1588 WO2013082901A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110398599.5 2011-12-05
CN201110398599.5A CN103138887B (zh) 2011-12-05 2011-12-05 一种1588事件报文的处理方法及系统

Publications (1)

Publication Number Publication Date
WO2013082901A1 true WO2013082901A1 (fr) 2013-06-13

Family

ID=48498253

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/073611 WO2013082901A1 (fr) 2011-12-05 2012-04-06 Procédé et système de gestion de message d'événement 1588

Country Status (2)

Country Link
CN (1) CN103138887B (fr)
WO (1) WO2013082901A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230537A (zh) * 2016-07-18 2016-12-14 广东电网有限责任公司电力调度控制中心 一种智能变电站的数据同步方法及装置

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103346853B (zh) * 2013-07-12 2015-06-17 武汉中元华电科技股份有限公司 一种基于IEEE1588v2协议的主时钟及其产生方法
CN105027489B (zh) * 2013-12-20 2018-08-21 华为技术有限公司 精确时钟协议同步方法和节点
CN107294633A (zh) * 2016-04-12 2017-10-24 中兴通讯股份有限公司 时间同步方法和装置
EP3482521B1 (fr) * 2016-07-06 2020-09-02 Telefonaktiebolaget LM Ericsson (publ) Transmission et réception d'informations d'indicateur temporel
CN106788842B (zh) * 2016-11-30 2019-03-26 瑞斯康达科技发展股份有限公司 一种ptp报文的处理方法及soc
CN106982103B (zh) * 2017-05-05 2019-01-18 烽火通信科技股份有限公司 在100g以上光传输芯片中控制ptp报文的方法及系统
CN108429596B (zh) * 2018-01-26 2019-08-02 武汉中元华电电力设备有限公司 一种用于IEEE 1588v2协议的以太网MAC模块实现装置及实现方法
CN108599887A (zh) * 2018-04-24 2018-09-28 新华三技术有限公司 一种时差计算方法和转发设备
CN112511376B (zh) * 2020-11-12 2022-04-15 鹏城实验室 一种tsn网络转发时间特性的测量方法及终端
CN116112402B (zh) * 2023-01-04 2024-10-18 北京晟芯网络科技有限公司 一种带宽监控方法、系统、ptp设备及带宽计算设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1874298A (zh) * 2005-12-13 2006-12-06 华为技术有限公司 一种边缘到边缘伪线仿真多跳伪线的检验方法
CN101447861A (zh) * 2008-12-29 2009-06-03 中兴通讯股份有限公司 Ieee 1588时间同步系统及其实现方法
CN101834712A (zh) * 2010-04-19 2010-09-15 浙江大学 利用ieee1588协议实现精确时间同步的方法
CN101977104A (zh) * 2010-11-13 2011-02-16 上海交通大学 基于ieee1588精确时钟同步协议系统及其同步方法
WO2011154217A1 (fr) * 2010-06-09 2011-12-15 Abb Research Ltd Synchronisation d'horloge sécurisée

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100994128B1 (ko) * 2008-09-23 2010-11-15 한국전자통신연구원 고정밀 네트워크 동기를 위한 타임 스탬핑 방법 및 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1874298A (zh) * 2005-12-13 2006-12-06 华为技术有限公司 一种边缘到边缘伪线仿真多跳伪线的检验方法
CN101447861A (zh) * 2008-12-29 2009-06-03 中兴通讯股份有限公司 Ieee 1588时间同步系统及其实现方法
CN101834712A (zh) * 2010-04-19 2010-09-15 浙江大学 利用ieee1588协议实现精确时间同步的方法
WO2011154217A1 (fr) * 2010-06-09 2011-12-15 Abb Research Ltd Synchronisation d'horloge sécurisée
CN101977104A (zh) * 2010-11-13 2011-02-16 上海交通大学 基于ieee1588精确时钟同步协议系统及其同步方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230537A (zh) * 2016-07-18 2016-12-14 广东电网有限责任公司电力调度控制中心 一种智能变电站的数据同步方法及装置
CN106230537B (zh) * 2016-07-18 2018-12-28 广东电网有限责任公司电力调度控制中心 一种智能变电站的数据同步方法及装置

Also Published As

Publication number Publication date
CN103138887B (zh) 2018-01-30
CN103138887A (zh) 2013-06-05

Similar Documents

Publication Publication Date Title
WO2013082901A1 (fr) Procédé et système de gestion de message d'événement 1588
CN101951312B (zh) 基于e1链路的双向时频同传方法及主从装置
CN103929293B (zh) 非对称延迟的时间同步方法及系统
WO2018221238A1 (fr) Dispositif sans fil et procédé de traitement pour dispositif sans fil
CN102006157B (zh) 一种时间同步的方法和系统
WO2019036943A1 (fr) Procédé de traitement de paquets et dispositif de réseau
JP5518191B2 (ja) 光伝送網が時刻同期プロトコルをキャリングする方法及びシステム
WO2011120262A1 (fr) Procédé et dispositif pour la réalisation d'une opération de synchronisation temporelle
WO2012151808A1 (fr) Procédé et système permettant d'améliorer la précision de synchronisation sur la base d'un protocole ptp (precision time protocol)
CN101977104A (zh) 基于ieee1588精确时钟同步协议系统及其同步方法
KR20070070299A (ko) 레지덴셜 이더넷 시스템에서의 시간 동기화 방법
CN104602141A (zh) 一种otn网络中实现时间同步的方法、设备和系统
CN102299788A (zh) 自动发送ieee1588协议报文的控制方法及装置
WO2010057398A1 (fr) Dispositif et procédé de mise en oeuvre de transmission transparente d'horloge
WO2012009987A1 (fr) Dispositif, système et procédé permettant une mesure de délai de propagation de trame
CN101753578B (zh) Ethernet/e1协议转换方法及协议转换器
WO2015196685A1 (fr) Procédé et appareil de synchronisation d'horloge
WO2012065334A1 (fr) Procédé, dispositif et système permettant de réaliser une synchronisation temporelle dans un réseau à multiplexage par répartition dans le temps
CN105027489B (zh) 精确时钟协议同步方法和节点
CN102013931A (zh) 时间同步方法及系统、从属定时设备及主定时设备
CN102469377A (zh) 一种epon系统以及系统中实现端到端透明时钟的方法
CN110572230A (zh) 一种用于实现时间同步的修正方法及装置
CN111628914B (zh) 一种周期通信网络的链路延时测量方法、系统及fpga
WO2018120549A1 (fr) Procédé et dispositif de traitement d'indicateur temporel dans un réseau optique passif ethernet, et support d'informations
WO2013155944A1 (fr) Horloge limite, horloge transparente, et procédé pour la transmission d'une horloge

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12855530

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12855530

Country of ref document: EP

Kind code of ref document: A1