{"id":77041,"date":"2020-04-07T13:42:46","date_gmt":"2020-04-07T11:42:46","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2"},"modified":"2020-04-07T13:42:46","modified_gmt":"2020-04-07T11:42:46","slug":"podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2","title":{"rendered":"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><b>\u00davod<\/b><\/p>\n<p>Koncepcia budovania \u201eDigit\u00e1lnej podsubstanice\u201c v elektroenergetike vy\u017eaduje synchroniz\u00e1ciu s presnos\u0165ou 1 \u03bcs. Na vykon\u00e1vanie finan\u010dn\u00fdch transakci\u00ed je taktie\u017e potrebn\u00e1 presnos\u0165 v \u03bcs. V t\u00fdchto aplik\u00e1ci\u00e1ch u\u017e presnos\u0165 \u010dasu NTP nesta\u010d\u00ed.<\/p>\n<p>Protokol synchroniz\u00e1cie PTPv2, pop\u00edsan\u00fd \u0161tandardom IEEE 1588v2, umo\u017e\u0148uje dosiahnu\u0165 presnos\u0165 synchroniz\u00e1cie v nieko\u013ek\u00fdch desiatkach nanosek\u00fand. PTPv2 umo\u017e\u0148uje posiela\u0165 synchroniza\u010dn\u00e9 pakety cez L2 a L3 siete.<\/p>\n<p>Hlavn\u00fdmi oblas\u0165ami, kde sa PTPv2 pou\u017e\u00edva, s\u00fa:<\/p>\n<ul>\n<li>energetika;<\/li>\n<li>meracie a kontroln\u00e9 zariadenia;<\/li>\n<li>obrann\u00fd a priemyseln\u00fd komplex;<\/li>\n<li>telekomunik\u00e1cie;<\/li>\n<li>finan\u010dn\u00fd sektor.<\/li>\n<\/ul>\n<p>\nV tomto pr\u00edspevku sa zaober\u00e1me t\u00fdm, ako funguje protokol synchroniz\u00e1cie PTPv2.<\/p>\n<p>M\u00e1me viac sk\u00fasenost\u00ed v priemysle a \u010dasto sa stret\u00e1vame s t\u00fdmto protokolom v energetick\u00fdch aplik\u00e1ci\u00e1ch. Preto aj preh\u013ead vypracujeme s oh\u013eadom na energetiku. <noindex><a rel=\"nofollow\" href=\"https:\/\/www.phoenixcontact.com\/online\/portal\/ru?1dmy&amp;urile=wcm%3apath%3a\/ruru\/web\/main\/products\/subcategory_pages\/Managed_switches_P-08-10-16-01\/aead25f7-3319-485d-8868-126c62b77cb1\">Dodato\u010dne,<\/a><\/noindex>.<\/p>\n<p><b>Pre\u010do je potrebn\u00fd?<\/b><\/p>\n<p>V s\u00fa\u010dasnosti obsahuj\u00fa STQ 34.01-21-004-2019 PJSC \u201eRosseti\u201c a STQ 56947007-29.240.10.302-2020 PJSC \u201eFSK EES\u201c po\u017eiadavky na organiz\u00e1ciu procesu zberu \u00fadajov so zabezpe\u010den\u00edm synchroniz\u00e1cie \u010dasu pod\u013ea PTPv2.<\/p>\n<p>Je to sp\u00f4soben\u00e9 t\u00fdm, \u017ee k procesnej zbernici s\u00fa pripojen\u00e9 termin\u00e1ly rel\u00e9ovej ochrany a meracie zariadenia, ktor\u00e9 prostredn\u00edctvom procesnej zbernice, pomocou tzv. SV-pr\u00fadov (multicast pr\u00fady), pren\u00e1\u0161aj\u00fa okam\u017eit\u00e9 hodnoty pr\u00fadu a nap\u00e4tia.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Termin\u00e1ly rel\u00e9ovej ochrany vyu\u017e\u00edvaj\u00fa tieto hodnoty na realiz\u00e1ciu ochrany pripojen\u00ed. Ak bude presnos\u0165 meran\u00ed v \u010dase n\u00edzka, niektor\u00e9 ochrany m\u00f4\u017eu falo\u0161ne reagova\u0165.<\/p>\n<p>Napr\u00edklad obe\u0165ou \u201eslabej\u201c synchroniz\u00e1cie \u010dasu m\u00f4\u017eu by\u0165 ochrany absol\u00fatnej selektivity. \u010casto sa logika tak\u00fdchto ochr\u00e1n zaklad\u00e1 na porovnan\u00ed dvoch hodn\u00f4t. Ak sa hodnoty zna\u010dne l\u00ed\u0161ia, ochrana sa aktivuje. Ak sa tieto hodnoty zmeraj\u00fa s presnos\u0165ou 1 ms, m\u00f4\u017eu sa z\u00edska\u0165 ve\u013ek\u00e9 rozdiely tam, kde s\u00fa hodnoty v skuto\u010dnosti norm\u00e1lne, ak by sa merali s presnos\u0165ou 1 \u03bcs.<\/p>\n<p><b>Verzie PTP<\/b><\/p>\n<p>Protokol PTP bol p\u00f4vodne op\u00edsan\u00fd v roku 2002 v \u0161tandarde IEEE 1588-2002 a jeho n\u00e1zov bol \u201eStandard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems\u201c. V roku 2008 bol vydan\u00fd aktualizovan\u00fd \u0161tandard IEEE 1588-2008, ktor\u00fd popisuje PTP verzia 2. V tejto verzii protokolu bola vylep\u0161en\u00e1 presnos\u0165 a stabilita, ale nebola zachovan\u00e1 sp\u00e4tn\u00e1 kompatibilita s prvou verziou protokolu. Taktie\u017e, v roku 2019 vy\u0161la verzia \u0161tandardu IEEE 1588-2019, popisuj\u00faca PTP v2.1. T\u00e1to verzia prid\u00e1va mal\u00e9 vylep\u0161enia k PTPv2 a je sp\u00e4tne kompatibiln\u00e1 s PTPv2.<\/p>\n<p>In\u00fdmi slovami, m\u00e1me nasleduj\u00faci preh\u013ead verzi\u00ed:<\/p>\n<p>PTPv1<br \/>\n(IEEE 1588-2002)<\/p>\n<p>PTPv2<br \/>\n(IEEE 1588-2008)<\/p>\n<p>PTPv2.1<br \/>\n(IEEE 1588-2019)<\/p>\n<p>PTPv1 (IEEE 1588-2002)<\/p>\n<p> \u2014<br \/>\nNezlu\u010dite\u013en\u00e9<\/p>\n<p>Nezlu\u010dite\u013en\u00e9<\/p>\n<p>PTPv2 (IEEE 1588-2008)<\/p>\n<p>Nezlu\u010dite\u013en\u00e9<\/p>\n<p> \u2014<br \/>\nZlu\u010dite\u013en\u00e9<\/p>\n<p>PTPv2.1 (IEEE 1588-2019)<\/p>\n<p>Nezlu\u010dite\u013en\u00e9<\/p>\n<p>Zlu\u010dite\u013en\u00e9<\/p>\n<p> \u2014 <\/p>\n<p>\nAle, ako v\u017edy, existuj\u00fa nuansy.<\/p>\n<p>Nezlu\u010dite\u013enos\u0165 medzi PTPv1 a PTPv2 predpoklad\u00e1, \u017ee zariadenie s podporou PTPv1 sa nebude m\u00f4c\u0165 synchronizova\u0165 s presn\u00fdmi hodinami, ktor\u00e9 pracuj\u00fa na PTPv2. Na synchroniz\u00e1ciu pou\u017e\u00edvaj\u00fa r\u00f4zne form\u00e1ty spr\u00e1v.<\/p>\n<p>Ale skombinova\u0165 zariadenia s PTPv1 a zariadenia s PTPv2 v jednej sieti je predsa mo\u017en\u00e9. Na to niektor\u00ed v\u00fdrobcovia umo\u017e\u0148uj\u00fa na portoch hrani\u010dn\u00fdch hod\u00edn vybera\u0165 verziu protokolu. To znamen\u00e1, \u017ee hrani\u010dn\u00e9 hodiny sa m\u00f4\u017eu synchronizova\u0165 cez PTPv2 a pritom synchronizova\u0165 in\u00e9 pripojen\u00e9 hodiny aj cez PTPv1 a PTPv2.<\/p>\n<p><b>Zariadenia PTP. Ak\u00e9 existuj\u00fa a \u010d\u00edm sa l\u00ed\u0161ia?<\/b><\/p>\n<p>\u0160tandard IEEE 1588v2 popisuje nieko\u013eko typov zariaden\u00ed. V\u0161etky s\u00fa uveden\u00e9 v tabu\u013eke.<\/p>\n<p>Zariadenia komunikuj\u00fa medzi sebou prostredn\u00edctvom LAN pomocou PTP.<\/p>\n<p>Zariadenia PTP sa naz\u00fdvaj\u00fa hodiny. V\u0161etky hodiny ber\u00fa presn\u00fd \u010das z grandmaster hodin.<\/p>\n<p>Existuje 5 typov hod\u00edn:<\/p>\n<p>Grandmaster clock (Grandmaster hodiny)<\/p>\n<p>Hlavn\u00fd zdroj presn\u00e9ho \u010dasu. \u010casto s\u00fa vybaven\u00e9 rozhran\u00edm na pripojenie GPS.<\/p>\n<p>Ordinary Clock (Oby\u010dajn\u00e9 hodiny)<\/p>\n<p>Zariadenie s jedn\u00fdm portom, ktor\u00e9 m\u00f4\u017ee by\u0165 majstrom (ved\u00facimi hodinami) alebo sl\u00e1vom (podriaden\u00fdmi hodinami).<\/p>\n<p>Ved\u00face hodiny (majster)<\/p>\n<p>S\u00fa zdrojom presn\u00e9ho \u010dasu, pod\u013ea ktor\u00e9ho sa synchronizuj\u00fa in\u00e9 hodiny.<\/p>\n<p>Podriaden\u00e9 hodiny (sl\u00e1v)<\/p>\n<p>Kone\u010dn\u00e9 zariadenie, ktor\u00e9 sa synchronizuje s ved\u00facimi hodinami.<\/p>\n<p>Boundary Clock (Hrani\u010dn\u00e9 hodiny)<\/p>\n<p>Zariadenie s viacer\u00fdmi portami, ktor\u00e9 m\u00f4\u017ee by\u0165 majstrom alebo sl\u00e1vom.<\/p>\n<p>To znamen\u00e1, \u017ee tieto hodiny sa m\u00f4\u017eu synchronizova\u0165 s vy\u0161\u0161\u00edmi ved\u00facimi hodinami a naviac synchronizova\u0165 ni\u017e\u0161ie podriaden\u00e9 hodiny.<\/p>\n<p>End-to-End Transparent Clock (Pr\u016fhledn\u00e9 hodiny funguj\u00edc\u00ed v re\u017eimu End-to-End)<\/p>\n<p>Za\u0159\u00edzen\u00ed s n\u011bkolika porty, kter\u00e9 nen\u00ed ani vedouc\u00edmi hodinami, ani hodinami sledovac\u00edmi. P\u0159en\u00e1\u0161\u00ed data PTP mezi dv\u011bma hodinami. <\/p>\n<p>P\u0159i p\u0159enosu dat pr\u016fhledn\u00e9 hodiny opravuj\u00ed v\u0161echna PTP zpr\u00e1vy. <\/p>\n<p>Oprava prob\u00edh\u00e1 p\u0159id\u00e1n\u00edm zpo\u017ed\u011bn\u00ed \u010dasu na tomto za\u0159\u00edzen\u00ed do pole korekce v hlavi\u010dce p\u0159en\u00e1\u0161en\u00e9 zpr\u00e1vy.<\/p>\n<p>Peer-to-Peer Transparent Clock (Pr\u016fhledn\u00e9 hodiny funguj\u00edc\u00ed v re\u017eimu Peer-to-Peer)<\/p>\n<p>Za\u0159\u00edzen\u00ed s n\u011bkolika porty, kter\u00e9 nen\u00ed ani vedouc\u00edmi hodinami, ani hodinami sledovac\u00edmi. <br \/>\nP\u0159en\u00e1\u0161\u00ed data PTP mezi dv\u011bma hodinami. <\/p>\n<p>P\u0159i p\u0159enosu dat pr\u016fhledn\u00e9 hodiny opravuj\u00ed v\u0161echny PTP zpr\u00e1vy Sync a Follow_Up (o nich\u017e bude n\u00ed\u017ee v\u00edce informac\u00ed).<\/p>\n<p>Oprava se dosahuje p\u0159id\u00e1n\u00edm zpo\u017ed\u011bn\u00ed do pole korekce p\u0159en\u00e1\u0161en\u00e9ho paketu na p\u0159en\u00e1\u0161ej\u00edc\u00edm za\u0159\u00edzen\u00ed a zpo\u017ed\u011bn\u00ed na kan\u00e1lu p\u0159enosu dat.<\/p>\n<p>Management Node (\u0158\u00eddic\u00ed uzel)<\/p>\n<p>Za\u0159\u00edzen\u00ed, kter\u00e9 konfiguruje a diagnostikuje jin\u00e9 hodiny.<\/p>\n<p>Vedouc\u00ed a sledovac\u00ed hodiny se synchronizuj\u00ed pomoc\u00ed \u010dasov\u00fdch zna\u010dek v PTP zpr\u00e1v\u00e1ch. Existuj\u00ed dva typy zpr\u00e1v v PTP protokolu:<\/p>\n<ul>\n<li>Event Messages \u2013 to jsou synchronizovan\u00e9 zpr\u00e1vy, kter\u00e9 p\u0159edpokl\u00e1daj\u00ed generaci \u010dasov\u00e9 zna\u010dky v okam\u017eiku odesl\u00e1n\u00ed zpr\u00e1vy a v okam\u017eiku jej\u00edho p\u0159ijet\u00ed.<\/li>\n<li>General Messages \u2013 tyto zpr\u00e1vy nevy\u017eaduj\u00ed \u010dasov\u00e9 zna\u010dky, ale mohou obsahovat \u010dasov\u00e9 zna\u010dky pro souvisej\u00edc\u00ed zpr\u00e1vy.<\/li>\n<\/ul>\n<p><\/p>\n<p>Event Messages<\/p>\n<p>General Messages<\/p>\n<p>Sync<br \/>\nDelay_Req<br \/>\nPdelay_Req<br \/>\nPdelay_Resp<\/p>\n<p>Announce<br \/>\nFollow_Up<br \/>\nDelay_Resp<br \/>\nPdelay_Resp_Follow_Up<br \/>\nManagement<br \/>\nSignaling<\/p>\n<p>D\u00e1le budou diskutov\u00e1ny v\u0161echny typy zpr\u00e1v podrobn\u011bji.<\/p>\n<p><b>Hlavn\u00ed probl\u00e9my synchronizace<\/b><\/p>\n<p>P\u0159i p\u0159enosu synchroniza\u010dn\u00edho paketu p\u0159es m\u00edstn\u00ed s\u00ed\u0165 se zpo\u017e\u010fuje na p\u0159ep\u00edna\u010di a v kan\u00e1lu p\u0159enosu dat. Ka\u017ed\u00fd p\u0159ep\u00edna\u010d bude m\u00edt zpo\u017ed\u011bn\u00ed kolem 10 \u03bcs, co\u017e je nep\u0159ijateln\u00e9 pro PTPv2. Na koncov\u00e9m za\u0159\u00edzen\u00ed pot\u0159ebujeme dos\u00e1hnout p\u0159esnosti 1 \u03bcs. (Pokud jde o energetiku. Jin\u00e1 aplikace mohou vy\u017eadovat i v\u011bt\u0161\u00ed p\u0159esnost.)<\/p>\n<p>V IEEE 1588v2 je pops\u00e1no n\u011bkolik algoritm\u016f, kter\u00e9 umo\u017e\u0148uj\u00ed zaznamenat \u010dasov\u00e9 zpo\u017ed\u011bn\u00ed a opravit jej.<\/p>\n<p><b>Algoritmus pr\u00e1ce<\/b><br \/>\nP\u0159i norm\u00e1ln\u00edm provozu protokol funguje ve dvou f\u00e1z\u00edch.<\/p>\n<ul>\n<li>F\u00e1ze 1 \u2014 nastaven\u00ed hierarchie 'Vedouc\u00ed hodiny \u2013 Sledovac\u00ed hodiny'.<\/li>\n<li>F\u00e1ze 2 \u2014 synchronizace hodin pomoc\u00ed mechanismu End-to-End nebo Peer-to-Peer.<\/li>\n<\/ul>\n<p>\n<i>F\u00e1za 1 \u2014 Nastavenie hierarchie \u201eMaster-Slave\u201c<\/i><\/p>\n<p>Ka\u017ed\u00fd port oby\u010dajn\u00fdch alebo hrani\u010dn\u00fdch hod\u00edn m\u00e1 ur\u010dit\u00e9 mno\u017estvo stavov (ved\u00face hodiny a nasleduj\u00face hodiny). \u0160tandard opisuje algoritmus prechodu medzi t\u00fdmito stavmi. V programovan\u00ed sa tak\u00fdto algoritmus naz\u00fdva kone\u010dn\u00fd automat alebo stavov\u00fd stroj (viac v Wiki).<\/p>\n<p>Tento kone\u010dn\u00fd automat pou\u017e\u00edva algoritmus Najlep\u0161\u00ed hodiny Master Clock Algorithm (BMCA) na ur\u010denie ved\u00faceho pri pripojen\u00ed dvoch hod\u00edn.<\/p>\n<p>Tento algoritmus umo\u017e\u0148uje hodin\u00e1m prebra\u0165 z\u00e1v\u00e4zky majstrovsk\u00fdch hod\u00edn, ke\u010f nadriaden\u00e9 majstrovsk\u00e9 hodiny strata sign\u00e1lu GPS, odpojili sa od siete at\u010f.<\/p>\n<p>Prechody medzi stavmi pod\u013ea BMCA s\u00fa stru\u010dne zobrazen\u00e9 na nasleduj\u00facom sch\u00e9me:<br \/>\n<img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/add811d60135de3be9c6865a5e4493c1.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nInform\u00e1cie o hodin\u00e1ch na druhom konci \u201ek\u00e1bla\u201c s\u00fa posielan\u00e9 v \u0161peci\u00e1lnej spr\u00e1ve (Announce message). Ke\u010f s\u00fa tieto inform\u00e1cie prijat\u00e9, algoritmus stavu stroja spracov\u00e1va a vykon\u00e1va porovnanie, ktor\u00e9 hodiny s\u00fa lep\u0161ie. Port na najlep\u0161\u00edch hodin\u00e1ch sa st\u00e1va ved\u00facimi hodinami.<\/p>\n<p>Jednoduch\u00e1 hierarchia je zobrazen\u00e1 na sch\u00e9me ni\u017e\u0161ie. Cesty 1, 2, 3, 4, 5 m\u00f4\u017eu obsahova\u0165 transparentn\u00e9 hodiny (Transparent clock), ale nez\u00fa\u010dast\u0148uj\u00fa sa na ustanoven\u00ed hierarchie \u201eVed\u00face hodiny \u2013 Nasleduj\u00face hodiny\u201c.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/05831c032a2d4df286ef41c531c949a3.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>F\u00e1za 2 \u2014 Synchroniz\u00e1cia oby\u010dajn\u00fdch a hrani\u010dn\u00fdch hod\u00edn<\/b><\/p>\n<p>Ihne\u010f po nastaven\u00ed hierarchie \u201eVed\u00face hodiny \u2013 Nasleduj\u00face hodiny\u201c za\u010d\u00edna f\u00e1za synchroniz\u00e1cie oby\u010dajn\u00fdch a hrani\u010dn\u00fdch hod\u00edn.<\/p>\n<p>Na synchroniz\u00e1ciu ved\u00face hodiny posielaj\u00fa nasleduj\u00facim hodin\u00e1m spr\u00e1vu obsahuj\u00facu \u010dasov\u00fa pe\u010diatku.<\/p>\n<p>Ved\u00face hodiny m\u00f4\u017eu by\u0165:<\/p>\n<ul>\n<li>jednostup\u0148ov\u00e9;<\/li>\n<li>dvochstup\u0148ov\u00e9.<\/li>\n<\/ul>\n<p>\nJednostup\u0148ov\u00e9 hodiny pre synchroniz\u00e1ciu posielaj\u00fa jednu spr\u00e1vu Sync.<\/p>\n<p>Dvochstup\u0148ov\u00e9 hodiny pre synchroniz\u00e1ciu pou\u017e\u00edvaj\u00fa dve spr\u00e1vy \u2013 Sync a Follow_Up.<\/p>\n<p>Na f\u00e1zu synchroniz\u00e1cie m\u00f4\u017eu by\u0165 pou\u017eit\u00e9 dva mechanizmy:<\/p>\n<ul>\n<li>Mechanizmus po\u017eiadavky a odpovede oneskorenia (Delay request-response mechanism).<\/li>\n<li>Mechanizmus merania oneskorenia susedn\u00e9ho uzla (Peer delay measurement mechanism).<\/li>\n<\/ul>\n<p>\nNajprv presk\u00famame tieto mechanizmy v najjednoduch\u0161om pr\u00edpade \u2013 ke\u010f nie s\u00fa pou\u017eit\u00e9 transparentn\u00e9 hodiny.<\/p>\n<p>Mechanizmus po\u017eiadavky a odpovede oneskorenia (Delay request-response mechanism)<\/p>\n<p>Mechanizmus predpoklad\u00e1 dva kroky:<\/p>\n<ol>\n<li>Meranie oneskorenia pri prenose spr\u00e1vy medzi ved\u00facimi hodinami a nasleduj\u00facimi. Vykon\u00e1va sa pomocou mechanizmu po\u017eiadavky a odpovede oneskorenia.<\/li>\n<li>Vykon\u00e1va sa korekcia posunu presn\u00e9ho \u010dasu.<\/li>\n<\/ol>\n<p>\n<i>Meranie oneskorenia<\/i><br \/>\n<img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/3a0d534384329c6232259736995eb0bd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nt1 \u2013 \u010cas odoslania spr\u00e1vy Sync s ved\u00facimi hodinami; t2 \u2013 \u010cas prijatia spr\u00e1vy Sync so sleduj\u00facimi hodinami; t3 \u2013 \u010cas odoslania po\u017eiadavky na oneskorenie (Delay_Req) so sleduj\u00facimi hodinami; t4 \u2013 \u010cas prijatia Delay_Req s ved\u00facimi hodinami.<\/p>\n<p>Ak sleduj\u00face hodiny poznaj\u00fa \u010das t1, t2, t3 a t4, m\u00f4\u017eu vypo\u010d\u00edta\u0165 priemern\u00e9 oneskorenie pri prenose spr\u00e1vy synchroniz\u00e1cie (tmpd). Vypo\u010d\u00edta sa nasledovne:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/513eb7352a143073835fe36aedd9cb98.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPri prenose spr\u00e1vy Sync a Follow_Up sa vypo\u010d\u00edta oneskorenie \u010dasu od majstra k pas\u00edvnemu uzlu \u2013 t-ms.<\/p>\n<p>Pri prenose spr\u00e1v Delay_Req a Delay_Resp sa vypo\u010d\u00edta oneskorenie \u010dasu od pas\u00edvneho uzla k majstrovi \u2013 t-sm.<\/p>\n<p>Ak medzi t\u00fdmito dvoma hodnotami vznikne nejak\u00e1 asymetria, vznikne chyba korekcie presn\u00e9ho \u010dasu. Chyba je podmienen\u00e1 t\u00fdm, \u017ee vypo\u010d\u00edtan\u00e9 oneskorenie je priemern\u00e9 z oneskoren\u00ed t-ms a t-sm. Ak sa oneskorenia nezhoduj\u00fa, \u010das budeme korigova\u0165 nepresne.<\/p>\n<p><i>Korekcia posunu presn\u00e9ho \u010dasu<\/i><\/p>\n<p>Po tom, \u010do je zn\u00e1me oneskorenie medzi ved\u00facimi a sleduj\u00facimi hodinami, sleduj\u00face hodiny vykonaj\u00fa korekciu \u010dasu.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/27f230252126a768273b40e8c8e7cc4e.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSleduj\u00face hodiny pou\u017e\u00edvaj\u00fa spr\u00e1vu Sync a volite\u013en\u00fa spr\u00e1vu Follow_Up na v\u00fdpo\u010det posunu presn\u00e9ho \u010dasu pri prenose paketu z ved\u00facich hod\u00edn na sleduj\u00face hodiny. Posun sa vypo\u010d\u00edta pod\u013ea nasleduj\u00faceho vzorca:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/190604a9287f285e191eb26381fca52c.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Mechanizmus merania oneskorenia susedn\u00e9ho uzla (Peer delay measurement mechanism)<\/b><\/p>\n<p>Tento mechanizmus tie\u017e vyu\u017e\u00edva dva kroky na synchroniz\u00e1ciu:<\/p>\n<ol>\n<li>Zariadenia meraj\u00fa oneskorenie \u010dasu ku v\u0161etk\u00fdm susedom cez v\u0161etky porty. Na to pou\u017e\u00edvaj\u00fa mechanizmus peer delay.<\/li>\n<li>Korekcia posunu presn\u00e9ho \u010dasu.<\/li>\n<\/ol>\n<p>\n<i>Meranie oneskorenia medzi zariadeniami, ktor\u00e9 podporuj\u00fa re\u017eim peer-to-peer<\/i><\/p>\n<p>Oneskorenie medzi portami, ktor\u00e9 podporuj\u00fa mechanizmus peer-to-peer, sa meria pomocou nasleduj\u00facich spr\u00e1v:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/897c9914110e9a56f98f4fa835f524cd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKe\u010f portu 1 zn\u00e1my \u010das t1, t2, t3 a t4, m\u00f4\u017ee vypo\u010d\u00edta\u0165 priemern\u00e9 oneskorenie (tmld). Vypo\u010d\u00edta sa pod\u013ea nasleduj\u00faceho vzorca:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/17416bf3b60f86136002b27cf4987b27.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPotom port pou\u017eije t\u00fato hodnotu pri v\u00fdpo\u010dte po\u013ea korekcie pre ka\u017ed\u00fa spr\u00e1vu Sync alebo volite\u013en\u00fa spr\u00e1vu Follow_Up, ktor\u00e9 prech\u00e1dzaj\u00fa cez toto zariadenie. <\/p>\n<p>Kone\u010dn\u00e9 oneskorenie bude rovn\u00e9 s\u00fa\u010dtu oneskorenia pri prenose cez toto zariadenie, priemern\u00e9mu oneskoreniu pri prenose cez d\u00e1tov\u00fd kan\u00e1l a u\u017e existuj\u00facemu oneskoreniu v danej spr\u00e1ve, zahrnut\u00e9mu na nadriaden\u00fdch zariadeniach.<\/p>\n<p>Spr\u00e1vy Pdelay_Req, Pdelay_Resp a volite\u013en\u00fd Pdelay_Resp_Follow_Up umo\u017e\u0148uj\u00fa z\u00edska\u0165 oneskorenie od mastera k slave a od slave k masterovi (cirkul\u00e1rne).<\/p>\n<p>Ak\u00e1ko\u013evek asymetria medzi t\u00fdmito dvoma hodnotami prinesie chybu korekcie posunu presn\u00e9ho \u010dasu.<\/p>\n<p><i>Korekcia posunu presn\u00e9ho \u010dasu<\/i><\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/c9cdedffd98db044718b8bc0eef156b9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nVed\u00face hodiny pou\u017e\u00edvaj\u00fa Sync spr\u00e1vu a volite\u013en\u00fa Follow_Up spr\u00e1vu na v\u00fdpo\u010det posunu presn\u00e9ho \u010dasu pri prenose paketu z ved\u00facich hod\u00edn na ved\u00face. Posun sa vypo\u010d\u00edtava pod\u013ea nasleduj\u00faceho vzorca:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/dff497d0f5644c3591f05f99e4c8c23a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV\u00fdhody korekcie mechanizmu peer-to-peer \u2013 oneskorenie \u010dasu ka\u017edej spr\u00e1vy Sync alebo Follow_Up sa vypo\u010d\u00edtava po\u010das jej prenosu v sieti. Preto zmena trasy prenosu nijako neovplyvn\u00ed presnos\u0165 korekcie.<\/p>\n<p>Pri pou\u017eit\u00ed tohto mechanizmu synchroniz\u00e1cia \u010dasu nevy\u017eaduje v\u00fdpo\u010det oneskorenia \u010dasu na prech\u00e1dzaj\u00facej ceste synchroniza\u010dn\u00e9ho paketu, ako sa to deje pri z\u00e1kladnej v\u00fdmene. T.j. spr\u00e1vy Delay_Req a Delay_Resp sa neodosielaj\u00fa. V tejto met\u00f3de sa oneskorenie medzi ved\u00facimi hodinami a ved\u00facimi jednoducho s\u010d\u00edta do po\u013ea korekcie ka\u017edej spr\u00e1vy Sync alebo Follow_Up.<\/p>\n<p>\u010eal\u0161ou v\u00fdhodou je, \u017ee ved\u00face hodiny s\u00fa zbaven\u00e9 nutnosti spracov\u00e1va\u0165 spr\u00e1vy Delay_Req.<\/p>\n<p><b>Re\u017eimy prev\u00e1dzky transparentn\u00fdch hod\u00edn<\/b><\/p>\n<p>Zodpovedaj\u00faco, toto boli rozobrat\u00e9 jednoduch\u00e9 pr\u00edklady. A teraz predpokladajme, \u017ee na ceste synchroniz\u00e1cie sa objavia prep\u00edna\u010de.<\/p>\n<p>Ak sa pou\u017eij\u00fa prep\u00edna\u010de bez podpory PTPv2, paket synchroniz\u00e1cie sa oneskor\u00ed na prep\u00edna\u010di o pribli\u017ene 10 \u00b5s.<\/p>\n<p>Prep\u00edna\u010de s podporou PTPv2 v terminol\u00f3gii IEEE 1588v2 sa naz\u00fdvaj\u00fa transparentn\u00e9 hodiny (Transparent clock). Transparentn\u00e9 hodiny sa nesynchronizuj\u00fa od ved\u00facich hod\u00edn a neparticipuj\u00fa v hierarchii \u201eVed\u00face hodiny \u2013 Ved\u00face hodiny\u201c, ale pri prenose spr\u00e1v synchroniz\u00e1cie si zapam\u00e4taj\u00fa, o ko\u013eko sa spr\u00e1va oneskorila na nich. To umo\u017e\u0148uje korigova\u0165 oneskorenie \u010dasu.<\/p>\n<p>Transparentn\u00e9 hodiny m\u00f4\u017eu pracova\u0165 v dvoch re\u017eimoch:<\/p>\n<ul>\n<li>End-to-End.<\/li>\n<li>Peer-to-Peer.<\/li>\n<\/ul>\n<p>\n<b>End-to-End (E2E)<\/b><\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/94e5d2f343d1657f1458adcbb344d024.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTransparentn\u00e9 hodiny E2E pren\u00e1\u0161aj\u00fa spr\u00e1vy Sync a sprievodn\u00e9 spr\u00e1vy Follow_Up na v\u0161etky porty. Dokonca aj na tie, ktor\u00e9 s\u00fa zablokovan\u00e9 ak\u00fdmiko\u013evek protokolmi (napr\u00edklad RSTP).<\/p>\n<p>Prep\u00edna\u010d si pam\u00e4t\u00e1 \u010dasov\u00fa pe\u010diatku, ke\u010f bol paket Sync (Follow_Up) prijat\u00fd na port a ke\u010f bol odoslan\u00fd z portu. Na z\u00e1klade t\u00fdchto dvoch \u010dasov\u00fdch pe\u010diatok sa vypo\u010d\u00edta \u010das spracovania spr\u00e1vy prep\u00edna\u010dom. V \u0161tandarde sa tento \u010das naz\u00fdva residence time.<\/p>\n<p>\u010cas spracovania sa prid\u00e1va do po\u013ea correctionField spr\u00e1vy Sync (jednostup\u0148ov\u00e9 hodiny) alebo Follow_Up (dvojstup\u0148ov\u00e9 hodiny).<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/b04cfa6cd1a93f25222079d5bb864a6d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPrieh\u013eadn\u00e9 hodiny E2E meraj\u00fa \u010das spracovania pre spr\u00e1vy Sync a Delay_Req prech\u00e1dzaj\u00face cez prep\u00edna\u010d. Pri tom je v\u0161ak d\u00f4le\u017eit\u00e9 pochopi\u0165, \u017ee oneskorenie medzi ved\u00facimi hodinami a nasledovn\u00edkmi sa vypo\u010d\u00edtava pomocou mechanizmu syst\u00e9mu po\u017eiadaviek a odpoved\u00ed na oneskorenie. Ak sa ved\u00face hodiny zmenia alebo sa zmen\u00ed cesta od ved\u00facich hod\u00edn k nasledovn\u00edkom, oneskorenie sa meria znova. To zvy\u0161uje \u010das prechodn\u00e9ho stavu v pr\u00edpade zmien v sieti.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/5bcb72a639accf802ffba7a1fa9a4767.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPrieh\u013eadn\u00e9 hodiny P2P, okrem merania \u010dasu spracovania spr\u00e1vy prep\u00edna\u010dom, meraj\u00fa oneskorenie na kan\u00e1li prenosu d\u00e1t do najbli\u017e\u0161ieho suseda, pri\u010dom vyu\u017e\u00edvaj\u00fa mechanizmus merania oneskorenia susedn\u00e9ho uzla.<\/p>\n<p>Oneskorenie sa meria na ka\u017edom kan\u00e1li v oboch smeroch, vr\u00e1tane kan\u00e1lov, ktor\u00e9 s\u00fa zablokovan\u00e9 ak\u00fdmko\u013evek protokolom (napr\u00edklad RSTP). To umo\u017e\u0148uje okam\u017eite vypo\u010d\u00edta\u0165 nov\u00e9 oneskorenie na ceste synchroniz\u00e1cie, ak sa zmenili grandsmastersk\u00e9 hodiny alebo topol\u00f3gia siete.<\/p>\n<p>\u010cas spracovania spr\u00e1v prep\u00edna\u010dmi a \u010das oneskorenia sa akumuluj\u00fa pri prenose spr\u00e1v Sync alebo Follow_Up.<\/p>\n<p><b>Typy podpory PTPv2 pre prep\u00edna\u010de<\/b><\/p>\n<p>Prep\u00edna\u010de m\u00f4\u017eu podporova\u0165 PTPv2:<\/p>\n<ul>\n<li>softv\u00e9rovo;<\/li>\n<li>hardv\u00e9rovo.<\/li>\n<\/ul>\n<p>\nPri softv\u00e9rovej implement\u00e1cii protokolu PTPv2 prep\u00edna\u010d \u017eiada \u010dasov\u00fa pe\u010diatku od firmv\u00e9ru. Probl\u00e9m spo\u010d\u00edva v tom, \u017ee firmv\u00e9r pracuje cyklicky a bude potrebn\u00e9 po\u010dka\u0165, k\u00fdm dokon\u010d\u00ed aktu\u00e1lny cyklus, spracuje \u017eiados\u0165 a na konci nasleduj\u00faceho cyklu vygeneruje \u010dasov\u00fa pe\u010diatku. Na to v\u0161etko tie\u017e d\u00f4jde \u010das a my z\u00edskame oneskorenie, aj ke\u010f nie tak\u00e9 v\u00fdznamn\u00e9 ako bez softv\u00e9rovej podpory PTPv2.<\/p>\n<p>Zabezpe\u010di\u0165 potrebn\u00fa presnos\u0165 dok\u00e1\u017ee len hardv\u00e9rov\u00e1 podpora PTPv2. V tomto pr\u00edpade sa vyd\u00e1vanie \u010dasovej pe\u010diatky vykon\u00e1va \u0161peci\u00e1lnym ASIC-om, ktor\u00fd je umiestnen\u00fd na porte.<\/p>\n<p><b>Form\u00e1t spr\u00e1vy<\/b><\/p>\n<p>V\u0161etky spr\u00e1vy PTP pozost\u00e1vaj\u00fa z nasleduj\u00facich pol\u00ed:<\/p>\n<ul>\n<li>Header \u2013 34 bajtov.<\/li>\n<li>Telo \u2013 ve\u013ekos\u0165 z\u00e1vis\u00ed od typu spr\u00e1vy.<\/li>\n<li>Suffix \u2013 volite\u013en\u00e9.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/99086e6601dcdf8f41c10f273c4ebfdc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Header<\/b><\/p>\n<p>Pole Header je rovnak\u00e9 pre v\u0161etky spr\u00e1vy PTP. Jeho ve\u013ekos\u0165 je 34 bajtov.<\/p>\n<p>Form\u00e1t po\u013ea Header:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/e4500d7e9026d9d059b1dcd668a44e5f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>messageType <\/b>\u2013 obsahuje typ pren\u00e1\u0161anej spr\u00e1vy, napr\u00edklad Sync, Delay_Req, PDelay_Req at\u010f.<\/p>\n<p><b>messageLength<\/b> \u2013 obsahuje celkov\u00fa ve\u013ekos\u0165 spr\u00e1vy PTP, vr\u00e1tane header, body a suffix (ale bez vypl\u0148uj\u00facich bajtov).<\/p>\n<p><b>domainNumber<\/b> \u2013 ur\u010duje, ku ktor\u00e9mu <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sk\/domain\/\"   title=\"dom\u00e9ne\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"1225\">dom\u00e9ne<\/a> PTP patr\u00ed spr\u00e1va.<\/p>\n<p><b>Dom\u00e9na<\/b> \u2013 ide o nieko\u013eko r\u00f4znych hod\u00edn, ktor\u00e9 s\u00fa zoskupen\u00e9 do jednej logickej skupiny a synchronizovan\u00e9 od jedn\u00e9ho ved\u00faceho \u010dasov\u00e9ho po\u010d\u00edtadla, ale nemusia by\u0165 synchronizovan\u00e9 s hodinami patriacimi k in\u00e9mu dom\u00e9nu.<\/p>\n<p><b>flags<\/b> \u2013 toto pole obsahuje r\u00f4zne vlajky na identifik\u00e1ciu stavu spr\u00e1vy.<\/p>\n<p><b>correctionField<\/b> \u2013 obsahuje \u010dasov\u00e9 oneskorenie v nanosekund\u00e1ch. \u010casov\u00e9 oneskorenie zah\u0155\u0148a oneskorenie pri prenose cez prieh\u013eadn\u00e9 hodiny, ako aj oneskorenie pri prenose cez kan\u00e1l pri pou\u017eit\u00ed re\u017eimu Peer-to-Peer.<\/p>\n<p><b>sourcePortIdentity<\/b> \u2013 toto pole obsahuje inform\u00e1cie o tom, z ktor\u00e9ho portu bola spr\u00e1va p\u00f4vodne odoslan\u00e1.<\/p>\n<p><b>sequenceID<\/b> \u2013 obsahuje identifika\u010dn\u00e9 \u010d\u00edslo pre individu\u00e1lne spr\u00e1vy.<\/p>\n<p><b>controlField<\/b> \u2013 pole-artefakt=) Zostalo z prvej verzie \u0161tandardu a obsahuje inform\u00e1cie o type tejto spr\u00e1vy. V podstate to ist\u00e9 ako messageType, ale s men\u0161\u00edm po\u010dtom mo\u017enost\u00ed.<\/p>\n<p><b>logMessageInterval<\/b> \u2013 toto pole je definovan\u00e9 typom spr\u00e1vy.<\/p>\n<p><b>Telo<\/b><\/p>\n<p>Ako bolo diskutovan\u00e9 vy\u0161\u0161ie, existuje nieko\u013eko typov spr\u00e1v. Tieto typy s\u00fa pop\u00edsan\u00e9 ni\u017e\u0161ie:<\/p>\n<p><b>Spr\u00e1va Announce<\/b><br \/>\nSpr\u00e1va Announce sl\u00fa\u017ei na to, aby \"povedala\" in\u00fdm hodin\u00e1m v r\u00e1mci jednej dom\u00e9ny o svojich parametroch. T\u00e1to spr\u00e1va umo\u017e\u0148uje stanovi\u0165 hierarchiu \"Ved\u00face hodiny \u2013 Veden\u00e9 hodiny\".<br \/>\n<img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/054b35f0c74757d531205fa352b90f4e.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Spr\u00e1va Sync<\/b><br \/>\nSpr\u00e1va synchroniz\u00e1cie (Sync) sa odosiela ved\u00facimi hodinami a obsahuje \u010das ved\u00facich hod\u00edn v momente, ke\u010f bola spr\u00e1va Sync vytvoren\u00e1. Ak s\u00fa ved\u00face hodiny dvojstup\u0148ov\u00e9, \u010dasov\u00e1 pe\u010diatka v spr\u00e1ve Sync bude priraden\u00e1 k 0, a aktu\u00e1lna \u010dasov\u00e1 pe\u010diatka bude poslan\u00e1 v sprievodnej spr\u00e1ve Follow_Up. Spr\u00e1va Sync sa pou\u017e\u00edva pre oba mechanizmy merania oneskorenia.<\/p>\n<p>Spr\u00e1va sa pren\u00e1\u0161a pomocou Multicast. Volite\u013ene je mo\u017en\u00e9 pou\u017ei\u0165 Unicast.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/38268221aa5663ba021f225c9de01df9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Spr\u00e1va Delay_Req<\/b><\/p>\n<p>Form\u00e1t spr\u00e1vy Delay_Req je identick\u00fd so spr\u00e1vou Sync. Veden\u00e9 hodiny posielaj\u00fa Delay_Req. Obsahuje \u010das odoslania Delay_Req veden\u00fdmi hodinami. T\u00e1to spr\u00e1va sa pou\u017e\u00edva iba pre mechanizmus po\u017eiadavky-odpovede na oneskorenie.<\/p>\n<p>Spr\u00e1va sa pren\u00e1\u0161a pomocou Multicast. Volite\u013ene je mo\u017en\u00e9 pou\u017ei\u0165 Unicast.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/1e64f3902ff3364b968581ff6b6a6573.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Spr\u00e1va Follow_Up<\/b><\/p>\n<p>Spr\u00e1va Follow_Up sa volite\u013ene odosiela ved\u00facimi hodinami a obsahuje \u010das odoslania <b>spr\u00e1vy Sync<\/b> majstrom. Spr\u00e1vu Follow_Up odosielaj\u00fa len dvoj\u00farov\u0148ov\u00e9 ved\u00face hodiny.<\/p>\n<p>Spr\u00e1va Follow_Up sa pou\u017e\u00edva pre oba mechanizmy merania oneskorenia.<\/p>\n<p>Spr\u00e1va sa pren\u00e1\u0161a pomocou Multicast. Volite\u013ene je mo\u017en\u00e9 pou\u017ei\u0165 Unicast.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/00917743466b8a331922d18e0928d3db.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Spr\u00e1va Delay_Resp<\/b><\/p>\n<p>Spr\u00e1va Delay_Resp sa odosiela ved\u00facimi hodinami. Obsahuje \u010das prijatia Delay_Req ved\u00facimi hodinami. T\u00e1to spr\u00e1va sa pou\u017e\u00edva iba pre mechanizmus \u017eiadosti-o-vr\u00e1tanie oneskorenia.<\/p>\n<p>Spr\u00e1va sa pren\u00e1\u0161a pomocou Multicast. Volite\u013ene je mo\u017en\u00e9 pou\u017ei\u0165 Unicast.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/b9d0bc41f94ceee560c0c593dd9e4afd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Spr\u00e1va Pdelay_Req<\/b><\/p>\n<p>Spr\u00e1va Pdelay_Req sa odosiela zariaden\u00edm, ktor\u00e9 \u017eiada o oneskorenie. Obsahuje \u010das odoslania spr\u00e1vy z portu tohto zariadenia. Pdelay_Req sa pou\u017e\u00edva iba pre mechanizmus merania oneskorenia susedn\u00e9ho uzla.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/7eef44a2655158758cdbcfbc25fc2e48.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Spr\u00e1va Pdelay_Resp<\/b><\/p>\n<p>Spr\u00e1va Pdelay_Resp sa odosiela zariaden\u00edm, ktor\u00e9 prijalo \u017eiados\u0165 o oneskorenie. Obsahuje \u010das prijatia spr\u00e1vy Pdelay_Req t\u00fdmto zariaden\u00edm. Spr\u00e1vy Pdelay_Resp sa pou\u017e\u00edvaj\u00fa iba pre mechanizmus merania oneskorenia susedn\u00e9ho uzla.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/6a3bb44c70fc09db3025df93c4d58a3f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Spr\u00e1va Pdelay_Resp_Follow_Up<\/b><\/p>\n<p>Spr\u00e1va Pdelay_Resp_Follow_Up sa volite\u013ene odosiela zariaden\u00edm, ktor\u00e9 prijalo \u017eiados\u0165 o oneskorenie. Obsahuje \u010das prijatia spr\u00e1vy Pdelay_Req t\u00fdmto zariaden\u00edm. Spr\u00e1va Pdelay_Resp_Follow_Up sa odosiela len dvoj\u00farov\u0148ov\u00fdmi ved\u00facimi hodinami.<\/p>\n<p>Taktie\u017e sa t\u00e1to spr\u00e1va m\u00f4\u017ee pou\u017e\u00edva\u0165 pre \u010das vykon\u00e1vania namiesto \u010dasovej pe\u010diatky. \u010cas vykon\u00e1vania je \u010das od prijatia Pdelay-Req do odoslania Pdelay_Resp.<\/p>\n<p>Pdelay_Resp_Follow_Up sa pou\u017e\u00edvaj\u00fa iba pre mechanizmus merania oneskorenia susedn\u00e9ho uzla.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/523043f7a880030474098fcdc1c5822d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Riadiace spr\u00e1vy (Spr\u00e1va Management)<\/b><\/p>\n<p>Riadiace spr\u00e1vy PTP s\u00fa potrebn\u00e9 na prenos inform\u00e1ci\u00ed medzi jedn\u00fdmi alebo viacer\u00fdmi hodinami a riadiacim uzlom.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/4388d9f4b6b12f3a2cdc764c20597499.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Prenos v LV<\/b><\/p>\n<p>PTP spr\u00e1va m\u00f4\u017ee by\u0165 pren\u00e1\u0161an\u00e1 na dvoch \u00farovniach:<\/p>\n<ul>\n<li>Sie\u0165ovej \u2013 ako s\u00fa\u010das\u0165 IP d\u00e1t.<\/li>\n<li>Kana\u013eovej \u2013 ako s\u00fa\u010das\u0165 Ethernet r\u00e1mca.<\/li>\n<\/ul>\n<p>\nPrenos spr\u00e1vy PTP cez UDP cez IP cez Ethernet<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/361e008fc48396915e5e9c23cc52bd63.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPTP cez UDP cez Ethernet<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/1862a5d27931a744e75e3c5bc63d7091.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Profily<\/b><\/p>\n<p>PTP m\u00e1 dos\u0165 \u201eflexibiln\u00fdch\u201c parametrov, ktor\u00e9 je potrebn\u00e9 nastavi\u0165. Napr\u00edklad:<\/p>\n<ul>\n<li>Mo\u017enosti BMCA.<\/li>\n<li>Mechanizmus merania oneskorenia.<\/li>\n<li>Intervaly a po\u010diato\u010dn\u00e9 hodnoty v\u0161etk\u00fdch konfigurovate\u013en\u00fdch parametrov a pod.<\/li>\n<\/ul>\n<p>\nA napriek tomu, \u017ee sme predt\u00fdm hovorili, \u017ee zariadenia PTPv2 s\u00fa medzi sebou kompatibiln\u00e9, v skuto\u010dnosti to tak nie je. Zariadenia musia ma\u0165 rovnak\u00e9 nastavenia, aby mohli spolupracova\u0165.<\/p>\n<p>Preto existuj\u00fa tzv. profily PTPv2. Profily s\u00fa skupiny nakonfigurovan\u00fdch nastaven\u00ed a ur\u010den\u00fdch obmedzen\u00ed protokolu, ktor\u00e9 umo\u017e\u0148uj\u00fa implement\u00e1ciu synchroniz\u00e1cie \u010dasu pre konkr\u00e9tnu aplik\u00e1ciu.<\/p>\n<p>Samotn\u00fd \u0161tandard IEEE 1588v2 popisuje iba jeden profil - \u201eDefault Profile\u201c. V\u0161etky ostatn\u00e9 profily vytvorili a op\u00edsali r\u00f4zne organiz\u00e1cie a asoci\u00e1cie.<\/p>\n<p>Napr\u00edklad profil pre energetiku alebo PTPv2 Power Profile bol vytvoren\u00fd v\u00fdborom Power Systems Relaying Committee a v\u00fdborom Substation Committee spolo\u010dnosti IEEE Power and Energy Society. Samotn\u00fd profil m\u00e1 n\u00e1zov IEEE C37.238- 2011.<\/p>\n<p>Profil popisuje, \u017ee PTP m\u00f4\u017ee by\u0165 pren\u00e1\u0161an\u00fd:<\/p>\n<ul>\n<li>Iba prostredn\u00edctvom L2 siet\u00ed (t.j. Ethernet, HSR, PRP, nie IP).<\/li>\n<li>Spr\u00e1vy s\u00fa pren\u00e1\u0161an\u00e9 iba multicastov\u00fdm vysielan\u00edm.<\/li>\n<li>Ako mechanizmus na meranie oneskorenia sa pou\u017e\u00edva peer delay measurement mechanism.<\/li>\n<\/ul>\n<p>\nPredvolen\u00e1 dom\u00e9na je 0, doporu\u010den\u00e1 dom\u00e9na je 93.<\/p>\n<p>Vo filozofii vytv\u00e1rania C37.238- 2011 bolo \u017eelanie zn\u00ed\u017ei\u0165 po\u010det volite\u013en\u00fdch charakterist\u00edk a necha\u0165 iba nevyhnutn\u00e9 funkcie pre spo\u013eahliv\u00fa interakciu medzi zariadeniami a zlep\u0161enie stability syst\u00e9mu.<\/p>\n<p>Taktie\u017e bola ur\u010den\u00e1 frekvencia prenosu spr\u00e1v:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/117c81192ff2eb160652738bb9ecbb1d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV podstate je k dispoz\u00edcii iba jeden parameter - typ ved\u00facich hod\u00edn (jednostup\u0148ov\u00e9 alebo dvojstup\u0148ov\u00e9).<\/p>\n<p>Presnos\u0165 mus\u00ed by\u0165 maxim\u00e1lne 1 \u03bcs. In\u00fdmi slovami, v jednom synchroniza\u010dnom re\u0165azci m\u00f4\u017eu by\u0165 maxim\u00e1lne 15 transparentn\u00fdch hod\u00edn alebo tri hrani\u010dn\u00e9 hodiny.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implement\u00e1cii protokolu synchroniz\u00e1cie \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/d3f1cb822d01b8733eadb6cd75805b20.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/phoenix_contact\/blog\/495920\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u00ab\u0426\u0438\u0444\u0440\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u0446\u0438\u0438\u00bb \u0432 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0435\u0442\u0438\u043a\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c\u044e 1 \u043c\u043a\u0441. \u0414\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439 \u0442\u0430\u043a\u0436\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c \u0432 \u043c\u043a\u0441. \u0412 \u044d\u0442\u0438\u0445 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u0445 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u0438 \u0432\u0440\u0435\u043c\u0435\u043d\u0438 NTP \u0443\u0436\u0435 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e. \u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 PTPv2, \u043e\u043f\u0438\u0441\u0430\u043d\u043d\u044b\u0439 \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u043e\u043c IEEE 1588v2, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0434\u043e\u0431\u0438\u0442\u044c\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u0438 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0432 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0434\u0435\u0441\u044f\u0442\u043a\u043e\u0432 \u043d\u0430\u043d\u043e\u0441\u0435\u043a\u0443\u043d\u0434. PTPv2 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043e\u0442\u043f\u0440\u0430\u0432\u043b\u044f\u0442\u044c \u043f\u0430\u043a\u0435\u0442\u044b \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0447\u0435\u0440\u0435\u0437 L2 \u0438 L3-\u0441\u0435\u0442\u0438. \u041e\u0441\u043d\u043e\u0432\u043d\u044b\u043c\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":77042,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-77041","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u00ab\u0426\u0438\u0444\u0440\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u0446\u0438\u0438\u00bb \u0432 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0435\u0442\u0438\u043a\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c\u044e 1 \u043c\u043a\u0441. \u0414\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439 \u0442\u0430\u043a\u0436\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c \u0432 \u043c\u043a\u0441.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0432\u0440\u0435\u043c\u0435\u043d\u0438 PTPv2 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u00ab\u0426\u0438\u0444\u0440\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u0446\u0438\u0438\u00bb \u0432 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0435\u0442\u0438\u043a\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c\u044e 1 \u043c\u043a\u0441. \u0414\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439 \u0442\u0430\u043a\u0436\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c \u0432 \u043c\u043a\u0441.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-04-07T11:42:46+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-04-07T11:42:46+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Podrobnosti implement\u00e1cie protokolu synchroniz\u00e1cie \u010dasu PTPv2 | ProHoster","description":"\u00davod. Koncept v\u00fdstavby \u201eDigit\u00e1lnej podstanice\u201c v energetike vy\u017eaduje synchroniz\u00e1ciu s presnos\u0165ou 1 \u03bcs. Pre vykon\u00e1vanie finan\u010dn\u00fdch transakci\u00ed je tie\u017e potrebn\u00e1 presnos\u0165 v \u03bcs.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0432\u0440\u0435\u043c\u0435\u043d\u0438 PTPv2 | ProHoster","og:description":"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u00ab\u0426\u0438\u0444\u0440\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u0446\u0438\u0438\u00bb \u0432 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0435\u0442\u0438\u043a\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c\u044e 1 \u043c\u043a\u0441. \u0414\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439 \u0442\u0430\u043a\u0436\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c \u0432 \u043c\u043a\u0441.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-04-07T11:42:46+00:00","article:modified_time":"2020-04-07T11:42:46+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"77041","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:25:29","updated":"2026-02-09 15:52:39","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/77041","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=77041"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/77041\/revisions"}],"predecessor-version":[{"id":158469,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/77041\/revisions\/158469"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/77042"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=77041"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=77041"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=77041"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}