WO2015005183A1 - 時刻同期システム - Google Patents
時刻同期システム Download PDFInfo
- Publication number
- WO2015005183A1 WO2015005183A1 PCT/JP2014/067584 JP2014067584W WO2015005183A1 WO 2015005183 A1 WO2015005183 A1 WO 2015005183A1 JP 2014067584 W JP2014067584 W JP 2014067584W WO 2015005183 A1 WO2015005183 A1 WO 2015005183A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- time
- terminal device
- real
- setting
- unit
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/04—Generating or distributing clock signals or signals derived directly therefrom
- G06F1/14—Time supervision arrangements, e.g. real time clock
-
- G—PHYSICS
- G04—HOROLOGY
- G04G—ELECTRONIC TIME-PIECES
- G04G5/00—Setting, i.e. correcting or changing, the time-indication
-
- G—PHYSICS
- G04—HOROLOGY
- G04G—ELECTRONIC TIME-PIECES
- G04G7/00—Synchronisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/04—Generating or distributing clock signals or signals derived directly therefrom
- G06F1/12—Synchronisation of different clock signals provided by a plurality of clock generators
Definitions
- the present invention relates to a time synchronization system that synchronizes time between terminals.
- the master seismometer transmits a time ahead of the current time to the slave seismometer in advance, and the transmitted time is synchronized with the next clock signal. Some calibrate the current time of the total (see, for example, Patent Document 2).
- the conventional information processing system does not take into account the case where there is a difference in the number of significant digits in the time unit in synchronization between the synchronization source RTC (Real Time ⁇ ⁇ Clock) and the synchronization destination CPU or IOP. .
- RTC Real Time ⁇ ⁇ Clock
- IOP the synchronization destination CPU or IOP.
- the problem to be solved by the present invention is that even when there is a difference in the number of significant digits in the time unit between the synchronization source and the synchronization destination, time synchronization can be performed accurately and clock signal reception can be performed. It is an object of the present invention to provide a time synchronization system capable of saving power by eliminating wireless communication for the purpose.
- the time synchronization system of the present invention A terminal device having a first real-time clock; A time synchronization system including a control device having a second real-time clock having a greater number of significant digits in the time unit than the first real-time clock,
- the controller is A setting time determination unit for determining a setting time for setting the first real time clock of the terminal device based on the second real time clock;
- the terminal device Waiting time from when the terminal device acquires the set time to setting the set time in the first real-time clock, in a time unit having more effective digits than the time unit of the first real-time clock About the calculated waiting time, a waiting time measuring unit that measures the progress, A time setting unit that sets the set time to the first real-time clock when the waiting time has elapsed.
- FIG. It is a figure which shows the example of the whole structure of the time synchronization system. It is a figure which shows an example of the functional block diagram of the time synchronization system. It is a figure which shows an example of the hardware constitutions which implement
- FIG. It is a figure which shows an example of the flowchart of the initial setting process in the time synchronous system. It is a figure which shows an example of the hop number management data 443.
- FIG. It is a figure which shows typically an example in the case of calculating the waiting time of the terminal device 3.
- FIG. 1 is a diagram showing an example of the overall configuration of a time synchronization system 1 according to the first embodiment of the present invention.
- the time synchronization system 1 includes, for example, one terminal control device 2, a plurality of terminal devices 3, and a plurality of relay devices 4.
- the terminal control device 2, the terminal device 3, and the relay device 4 all have a wireless communication function and can wirelessly communicate with each other.
- the terminal control device 2, the terminal device 3, and the relay device 4 are connected using a solid line for the sake of explanation, but some connection lines are not necessary when the wireless communication function is provided.
- the terminal device 3 is activated, for example, at a preset activation time, measures the operating state of the steam trap installed in the steam piping facility, and sends the measurement data to the terminal control device 2.
- the activation of the terminal device 3 may be referred to as “wake-up”.
- the terminal device 3 forms a group by one or more terminal devices 3.
- group 1 is formed from four terminal devices 3
- group 2 is formed from two terminal devices 3
- group 3 is formed from three terminal devices 3.
- the terminal control device 2 creates, for example, synchronization data for time synchronization of each terminal device 3 and transmits it to each terminal device 3. Moreover, the terminal control apparatus 2 receives measurement data from the terminal apparatus 3, for example.
- the relay device 4 operates as a repeater that relays communication data between the terminal control device 2 and the terminal device 3, for example.
- Each terminal device 3 needs to perform communication processing as efficiently as possible in order to suppress power consumption when sending measurement data for each preset measurement cycle. For this reason, in the terminal control apparatus 2 and each terminal apparatus 3, when determining starting time, the present present time used as the origin needs to synchronize. Therefore, in the present embodiment, an example will be described in which synchronization data for synchronizing the current time is transmitted from the terminal control device 2 to each terminal device 3 to synchronize the time in each terminal device 3.
- FIG. 2 is a diagram illustrating an example of a functional block diagram of the time synchronization system 1.
- the terminal control device 2 calculates a time keeping unit 21 that measures time, a set time determination unit 22 that determines a time to be set in the terminal device 3, and a waiting time when the terminal device 3 sets the set time.
- the waiting time calculating unit 23 the synchronization data transmitting unit 24 that transmits the set time data and the waiting time data to the terminal device 3 as synchronization data, and the communication for calculating the communication time between the terminal control device 2 and the terminal device 3.
- a time calculation unit 25 is a time keeping unit 21 that measures time, a set time determination unit 22 that determines a time to be set in the terminal device 3, and a waiting time when the terminal device 3 sets the set time.
- the waiting time calculating unit 23 the synchronization data transmitting unit 24 that transmits the set time data and the waiting time data to the terminal device 3 as synchronization data, and the communication for calculating the communication time between the terminal control device 2 and the terminal device 3.
- the time counting unit 21 can keep the current time even when the terminal control device 2 is powered off, for example. Further, the time counting unit 21 can measure the time up to a time unit of “milliseconds”, for example.
- the set time determination unit 22 can determine, for example, a time later than the current time as a time for setting in the terminal device 3. For example, the set time determination unit 22 determines the set time by setting the time in units of “milliseconds” to “000 milliseconds”.
- the waiting time calculation unit 23 is configured so that the terminal device 3 acquires the set time based on, for example, the elapsed time of the time synchronization process in the terminal control device 2 or the communication time between the terminal control device 2 and the terminal device 3.
- the waiting time from setting to setting can be determined.
- the synchronization data transmission unit 24 may transmit, for example, set time data indicating the set time determined by the set time determination unit 22 and wait time data indicating the wait time calculated by the wait time calculation unit 23 as synchronization data. it can.
- the communication time calculation unit 25 can calculate the communication time when the terminal control device 2, the terminal device 3, and the relay device 4 communicate based on the number of hops between the devices, for example.
- the terminal device 3 includes a time counting unit 31 that measures time, a time setting unit 32 that sets the time in the time counting unit 31 using the set time, and the terminal control device 2 using the set time data and the waiting time data as synchronization data.
- the synchronization data receiving unit 33 that receives from the terminal and the waiting time measuring unit 34 that measures the waiting time based on the waiting time data from the terminal control device 2.
- the time counting unit 31 can keep the current time even when the terminal device 3 is powered off, for example. Further, the time counting unit 31 can count the time up to the time measurement unit of “second”, for example. That is, unlike the time counting unit 21 of the terminal control device 2, the time counting unit 31 of the terminal device 3 cannot measure the time in “millisecond” timing units. Therefore, the number of significant digits in the time unit in the time counting unit 21 is larger than the number of significant digits in the time unit in the time counting unit 31.
- the time setting unit 32 can set the current time in the time counting unit 31 using the set time data indicating the set time included in the synchronization data received from the terminal control device 2, for example.
- the synchronization data receiving unit 33 is, for example, set time data indicating the set time determined by the set time determining unit 22 of the terminal control device 2 and a wait indicating the wait time calculated by the wait time calculating unit 23 of the terminal control device 2. Time data can be received as synchronization data.
- the waiting time timing unit 34 can measure the waiting time based on the waiting time data included in the synchronization data received by the synchronization data receiving unit 33, for example.
- the terminal device 3 includes a measurement unit (not shown), and can measure the surface temperature and / or ultrasonic vibration of the steam trap 5, for example.
- measurement data of the steam trap measured by the measurement unit is transmitted to the terminal control device 2 by wireless communication.
- FIG. 3 is a diagram illustrating an example of a hardware configuration in which the terminal control device 2 is realized using a CPU or the like.
- the terminal control device 2 can be configured using, for example, a notebook personal computer.
- the terminal control device 2 includes a display 40, an RTC (Real Time Clock) 41 CPU 42, a RAM (Random Access Memory) 43, a hard disk 44, a keyboard / mouse 45, and a wireless communication circuit 46.
- RTC Real Time Clock
- RAM Random Access Memory
- the display 40 can display input contents from the keyboard / mouse 45, measurement data, and the like.
- the RTC 41 can provide the current time as data (hh: mm: ss.000), for example, in milliseconds by the clock function.
- the CPU 42 can execute the time synchronization program 442 stored in the hard disk 44.
- the RAM 43 can provide an address space to the CPU 42.
- the hard disk 44 can store an OS (Operating System) 441, a time synchronization program 442, hop number management data 443, measurement data (not shown), and the like.
- the keyboard / mouse 45 can accept an input operation for controlling the terminal device 3 from the user.
- the wireless communication circuit 46 can wirelessly communicate with the terminal device 3 or the relay device 4.
- the time counter 21 that constitutes the terminal control device 2 shown in FIG. 2 is realized by the RTC 41.
- the set time determination unit 22, the waiting time calculation unit 23, the synchronization data transmission unit 24, and the communication time calculation unit 25 are realized by executing the time synchronization program 442 on the CPU 42.
- FIG. 4 is a diagram illustrating an example of a hardware configuration in which the terminal device 3 is realized using a CPU or the like.
- the terminal device 3 includes an RTC (Real Time Clock) 51, a CPU 52, a RAM 53, a measurement sensor 54, a wireless communication circuit 55, an EEPROM (Electrically Erasable and Programmable Read Only Memory) 56, and a battery 57.
- the RTC 51 can provide the current time as, for example, data (hh: mm: ss) indicating, for example, in seconds by the clock function, and activate the terminal device 3 at a time corresponding to the set activation time data 511 by the timer function. Can be made.
- the CPU 52 can execute a time setting program 561 stored in the EEPROM 56.
- the RAM 53 can provide an address space to the CPU 52 and can store set time data 531, waiting time data 532, and the like.
- the measurement sensor 54 can measure the operation state of the steam trap using, for example, a vibration sensor using a piezoelectric element or a temperature sensor using a thermocouple.
- the wireless communication circuit 55 can communicate with the terminal control device 2 or the repeater 4.
- the EEPROM 56 can store a time setting program 561.
- the battery 57 can supply power to each unit of the terminal device 3.
- the battery 57 corresponds to, for example, a dry battery or a storage battery.
- the time counter 31 constituting the terminal device 3 shown in FIG. 2 is realized by the RTC 51. Further, the time setting unit 32, the synchronous data receiving unit 33, and the waiting time measuring unit 34 are realized by executing a time setting program 561 on the CPU 52.
- FIG. 5 is a diagram illustrating an example of a flowchart of time setting processing in the time synchronization system 1.
- the CPU 42 of the terminal control device 2 can perform the time setting process of the present embodiment when performing the process of setting the startup time data 511 in the RTC 51 of the terminal device 3.
- description of the process for setting the activation time data 511 is omitted.
- the CPU 42 of the terminal control device 2 selects one group of the terminal devices 3 (step S101).
- the group selection order can be determined in the order in which the terminal device and the relay device can be operated efficiently.
- groups are selected in the order of group 1, group 2, and group 3 shown in FIG.
- the CPU42 determines the setting time for setting to RTC51 of the terminal device 3 (step S102). For example, the CPU 42 can determine the time advanced by “1 second” from the current time as the set time. Specifically, the CPU 42, for example, “00 hours 00 minutes 01 seconds 000 milliseconds”, which is a time advanced “1 second 000 milliseconds” from the current time (origin time) “00 hours 00 minutes 00 seconds 000 milliseconds”. "Is the set time.
- the CPU 42 starts counting after resetting a timer used for measuring the processing time to zero (step S103).
- the processing time is, for example, the time required to calculate the communication time after selecting a terminal device, as will be described later.
- the processing time for each terminal device will be described as “60 milliseconds”.
- processing time may include a time required to calculate a waiting time described later. Furthermore, the processing time may include a time required for transmitting the synchronization data described later.
- CPU42 selects the terminal device used as the object which transmits synchronous data (step S104). For example, the CPU 42 selects the terminal device 3a belonging to the group 1 in FIG.
- CPU42 calculates the communication time about the selected terminal device (step S105). For example, the CPU 42 extracts the hop number “5” of the terminal device 3a from the record 601 of the hop number management data 443 shown in FIG. 6, and the communication time “20 milliseconds” per hop number is added to this hop number “5”. "100 milliseconds" multiplied by is calculated as the communication time.
- the CPU 42 extracts the hop number “4” of the terminal device 3b from the record 602 of the hop number management data 443 shown in FIG. “80 milliseconds” multiplied by the communication time “20 milliseconds” is calculated as the communication time.
- the CPU 42 extracts the hop number “3” of the terminal devices 3c to 3e from any of the records 603 to 605 of the hop number management data 443 shown in FIG. “60 milliseconds” obtained by multiplying “3” by the communication time “20 milliseconds” per the number of hops is calculated as the communication time.
- the CPU 42 calculates a waiting time for the selected terminal device (step S106). For example, the CPU 42 can calculate the waiting time by adding the processing time being counted by the timer reset to 0 in step S103 and the communication time and processing time calculated in step S105. When the processing time includes the time required to calculate the waiting time and the time required to transmit synchronous data described later, these times are included in the calculated waiting time.
- FIG. 7 is a diagram schematically illustrating an example of calculating the waiting time of the terminal device 3.
- the processing time in the terminal device 3a is “60 milliseconds”
- the waiting time is obtained by subtracting the processing time “60 milliseconds” and the communication time “100 milliseconds” from 1 second (1000 milliseconds). 840 milliseconds ".
- the processing time “60 milliseconds” and the communication time “100 milliseconds” are “time required for the terminal device to acquire the set time”.
- the CPU 42 generates synchronization data by combining the data indicating the set time and the data indicating the waiting time, and transmits the generated synchronization data to the terminal device 3.
- the synchronization data is generated and transmitted by combining the data “00 hours 00 minutes 01 seconds” indicating the set time and the data “840 milliseconds” indicating the waiting time.
- the reason why the millisecond digits (000 milliseconds) are discarded from the data indicating the set time is that the valid digits of the RTC 51 of the terminal device 3 are up to the second.
- the CPU 52 of the terminal device 3 When the CPU 52 of the terminal device 3 receives the synchronization data from the terminal control device 2 (step S110), it reads data indicating the waiting time from the received synchronization data and counts the waiting time (step S111). For example, the CPU 52 of the terminal device 3a counts the waiting time until the count reaches “840 milliseconds”.
- step S112 the CPU 52 sets data indicating the set time in the received synchronization data in the set time data 511 of the RTC 51 (step S113). Specifically, the CPU 52 sets “00 hour 00 minute 01 second” in the RTC 51.
- the CPU 42 of the terminal control device 2 determines whether there is an unprocessed terminal device 3 (step S108), and if there is an unprocessed terminal device 3, returns to step S104 and repeats the processing (Yes determination in step S108). ).
- the CPU 52 of the terminal device 3 b counts the waiting time until the count reaches “700 milliseconds”, and then sets “00 hours 00 minutes 01 seconds” that is data indicating the set time to the RTC 51. Set.
- the CPU 52 of the terminal device 3c counts the waiting time until the count reaches “580 milliseconds”, and then sets “00 hours 00 minutes 01 seconds”, which is data indicating the set time, in the RTC 51.
- the CPU 52 of the terminal device 3d counts the waiting time until the count reaches “460 milliseconds”, and then sets “00 hours 00 minutes 01 seconds”, which is data indicating the set time, in the RTC 51.
- the CPU 52 of the terminal device 3 e counts the waiting time until the count reaches “340 milliseconds”, and then sets “00 hours 00 minutes 01 seconds”, which is data indicating the set time, in the RTC 51.
- step S109 the CPU 42 of the terminal control device 2 determines whether there is an unprocessed group (step S109) if there is no unprocessed terminal device 3 (No determination in step S108), and if there is an unprocessed group. Returning to step S101, the process is repeated (Yes determination in step S109).
- the CPU 42 executes the time synchronization processing for the terminal devices 3f and 3g belonging to the group 2.
- the time synchronization processing is executed for the terminal devices 3h to 3j belonging to the group 3.
- the terminal control device 2 transmits the set time data indicating the previous time and the waiting time data that differs for each terminal device, and each terminal device 3 has the waiting time indicated in the received waiting time data.
- the set time indicated in the received set time data is set in the RTC.
- the processing time for each terminal device is all “60 milliseconds”. However, the time required to calculate the waiting time may be included in the processing time. Furthermore, the time required for transmitting the synchronization data may be estimated and included in the processing time.
- the set time may be determined according to the number of terminal devices 3 in the group. Specifically, the larger the number of terminal devices 3, the longer the time interval between the current time and the set time.
- the example in which the communication time when the terminal device 3 and the relay 4 communicate with each other is calculated based on the number of hops between the devices, but the communication time may be a predetermined time. For example, all communication times in the group may be set to “50 milliseconds”. As a result, the processing for calculating the communication time can be omitted, and the processing speed can be increased.
- the difference in timing for acquiring the set time between the two terminal devices and the difference in waiting time between the two terminal devices Will match.
- the total time of the processing time and the communication time is, for example, “100 milliseconds”
- the difference in timing for acquiring the set time between the terminal devices 3a and 3b is “100 milliseconds”.
- the difference in waiting time between 3a and 3b is “100 milliseconds”.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Electric Clocks (AREA)
- Synchronisation In Digital Transmission Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
第1リアルタイムクロックを有する端末装置と、
前記第1リアルタイムクロックよりも計時単位の有効桁数が多い第2リアルタイムクロックを有する制御装置とを含む時刻同期システムであって、
前記制御装置は、
前記端末装置の前記第1リアルタイムクロックに設定するための設定時刻を、前記第2リアルタイムクロックに基づいて決定する設定時刻決定部を備え、
前記端末装置は、
前記端末装置が前記設定時刻を取得した時から前記第1リアルタイムクロックに前記設定時刻を設定するまでの待ち時間であって、前記第1リアルタイムクロックの計時単位よりも有効桁数が多い計時単位で算出された待ち時間について、その経過を計時する待ち時間計時部と、
前記待ち時間の経過時において、前記設定時刻を前記第1リアルタイムクロックに設定する時刻設定部とを備える。
[1-1.時刻同期システムの全体構成]
図1は、本発明の第1の実施形態にかかる時刻同期システム1の全体構成の例を示す図である。時刻同期システム1は、例えば、1つの端末制御装置2と、複数の端末装置3と、複数の中継機4とを含む。例えば端末制御装置2と端末装置3と中継機4は、いずれも無線通信機能を有し、相互に無線通信可能である。なお、図1においては、説明上、端末制御装置2と端末装置3と中継機4とを実線を用いて接続しているが、無線通信機能を有する場合には何らかの接続線は必要ない。
図2は、時刻同期システム1の機能ブロック図の一例を示す図である。
端末制御装置2は、時刻を計時する時刻計時部21と、端末装置3に設定するための時刻を決定する設定時刻決定部22と、端末装置3が設定時刻を設定する際の待ち時間を算出する待ち時間算出部23と、設定時刻データ及び待ち時間データを同期データとして端末装置3へ送信する同期データ送信部24と、端末制御装置2と端末装置3との間の通信時間を算出する通信時間算出部25とを備える。
端末装置3は、時刻を計時する時刻計時部31と、設定時刻を用いて時刻計時部31に時刻を設定する時刻設定部32と、設定時刻データ及び待ち時間データを同期データとして端末制御装置2から受信する同期データ受信部33と、端末制御装置2からの待ち時間データに基づく待ち時間を計時する待ち時間計時部34とを備える。
[1-3-1.端末制御装置2のハードウェア構成例]
図3は、端末制御装置2を、CPU等を用いて実現したハードウェア構成の一例を示す図である。端末制御装置2は、例えばノート型のパーソナルコンピュータを用いて構成することができる。
図4は、端末装置3を、CPU等を用いて実現したハードウェア構成の一例を示す図である。端末装置3は、RTC(Real Time Clock)51、CPU52、RAM53、計測センサ54、無線通信回路55、EEPROM(Electrically Erasable and Programmable Read Only Memory)56及び、バッテリー57を備える。
図5は、時刻同期システム1における時刻設定処理のフローチャートの一例を示す図である。
上記実施形態においては、各端末装置についての処理時間はすべて「60ミリ秒」としたが、待ち時間を算出するのに要した時間を処理時間に含めてもよい。さらに、同期データを送信するのに要する時間を予測して処理時間に含めてもよい。
22 設定時刻決定部
23 待ち時間算出部
24 同期データ送信部
25 通信時間算出部
31 時刻計時部
32 時刻設定部
33 同期データ受信部
34 待ち時間計時部
Claims (6)
- 第1リアルタイムクロックを有する端末装置と、
前記第1リアルタイムクロックよりも計時単位の有効桁数が多い第2リアルタイムクロックを有する制御装置とを含む時刻同期システムであって、
前記制御装置は、
前記端末装置の前記第1リアルタイムクロックに設定するための設定時刻を、前記第2リアルタイムクロックに基づいて決定する設定時刻決定部を備え、
前記端末装置は、
前記端末装置が前記設定時刻を取得した時から前記第1リアルタイムクロックに前記設定時刻を設定するまでの待ち時間であって、前記第1リアルタイムクロックの計時単位よりも有効桁数が多い計時単位で算出された待ち時間について、その経過を計時する待ち時間計時部と、
前記待ち時間の経過時において、前記設定時刻を前記第1リアルタイムクロックに設定する時刻設定部とを備える、
時刻同期システム。 - 前記制御装置は、
前記設定時刻から、前記端末装置が前記設定時刻を取得するのに要する時間を差し引くことにより、前記待ち時間を算出する待ち時間算出部をさらに備える、
請求項1に記載の時刻同期システム。 - 前記時刻同期システムは、前記端末装置を複数有しており、
前記制御装置は、
少なくとも2以上の端末装置に同じ設定時刻を設定する場合、2つの前記端末装置間における前記設定時刻を取得するタイミングの差と、2つの前記端末装置間における前記待ち時間の差とが合致するように、前記待ち時間を算出する、
請求項2に記載の時刻同期システム。 - 前記端末装置は、電池により駆動するものであって、前記制御装置と無線通信を行うことにより前記設定時刻及び前記待ち時間を取得する、
請求項1~3のいずれか一項に記載の時刻同期システム。 - 前記制御装置は、
前記制御装置と前記端末装置との間のホップ数に基づいて、前記端末装置が前記設定時刻を取得した時を示すタイミングを求める、
請求項1~4のいずれか一項に記載の時刻同期システム。 - 第1リアルタイムクロックを有する端末装置と、
前記第1リアルタイムクロックよりも計時単位の有効桁数が多い第2リアルタイムクロックを有する制御装置とを用いた時刻設定方法であって、
前記制御装置は、
前記端末装置の前記第1リアルタイムクロックに設定するための設定時刻を、前記第2リアルタイムクロックに基づいて決定する設定時刻決定部を備え、
前記端末装置は、
前記端末装置が前記設定時刻を取得した時から前記第1リアルタイムクロックに前記設定時刻を設定するまでの待ち時間であって、前記第1リアルタイムクロックの計時単位よりも有効桁数が多い計時単位で算出された待ち時間について、その経過を計時する待ち時間計時部と、
前記待ち時間の経過時において、前記設定時刻を前記第1リアルタイムクロックに設定する時刻設定部とを備える、
時刻設定方法。
Priority Applications (11)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
MYPI2016000034A MY174086A (en) | 2013-07-10 | 2014-07-01 | Time synchronization system |
BR112015030705-1A BR112015030705B1 (pt) | 2013-07-10 | 2014-07-01 | Sistema de sincronização de tempo e método para definir o tempo usando um dispositivo de controle |
JP2014555028A JP6280051B2 (ja) | 2013-07-10 | 2014-07-01 | 時刻同期システム |
SG11201600141WA SG11201600141WA (en) | 2013-07-10 | 2014-07-01 | Time synchronization system |
US14/903,771 US9778679B2 (en) | 2013-07-10 | 2014-07-01 | Time synchronization system |
EP14822534.5A EP2990886B1 (en) | 2013-07-10 | 2014-07-01 | Time synchronization system |
KR1020157036345A KR20160013964A (ko) | 2013-07-10 | 2014-07-01 | 시각 동기 시스템 |
MX2015016899A MX352612B (es) | 2013-07-10 | 2014-07-01 | Sistema de sincronizacion horaria. |
CN201480038647.1A CN105378568B (zh) | 2013-07-10 | 2014-07-01 | 时刻同步系统 |
ES14822534T ES2759107T3 (es) | 2013-07-10 | 2014-07-01 | Sistema de sincronización de tiempo |
AU2014288448A AU2014288448B2 (en) | 2013-07-10 | 2014-07-01 | Time synchronization system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013144913 | 2013-07-10 | ||
JP2013-144913 | 2013-07-10 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015005183A1 true WO2015005183A1 (ja) | 2015-01-15 |
Family
ID=52279869
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/067584 WO2015005183A1 (ja) | 2013-07-10 | 2014-07-01 | 時刻同期システム |
Country Status (15)
Country | Link |
---|---|
US (1) | US9778679B2 (ja) |
EP (1) | EP2990886B1 (ja) |
JP (1) | JP6280051B2 (ja) |
KR (1) | KR20160013964A (ja) |
CN (1) | CN105378568B (ja) |
AU (1) | AU2014288448B2 (ja) |
BR (1) | BR112015030705B1 (ja) |
CL (1) | CL2016000023A1 (ja) |
ES (1) | ES2759107T3 (ja) |
MX (1) | MX352612B (ja) |
MY (1) | MY174086A (ja) |
PE (1) | PE20160094A1 (ja) |
SA (1) | SA516370365B1 (ja) |
SG (1) | SG11201600141WA (ja) |
WO (1) | WO2015005183A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5896584B1 (ja) * | 2015-12-10 | 2016-03-30 | 株式会社テイエルブイ | 無線通信システム及び通信端末 |
JP2022124142A (ja) * | 2021-02-15 | 2022-08-25 | 株式会社ミヤワキ | 測定データ送信システム、測定装置及びサーバ |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111752335B (zh) * | 2020-05-23 | 2022-05-31 | 苏州浪潮智能科技有限公司 | 基于硬盘多核cpu的时间同步方法、系统、终端及存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH04184297A (ja) | 1990-11-19 | 1992-07-01 | Nec Eng Ltd | 情報処理システムの時刻同期化方式 |
JPH0895664A (ja) * | 1994-09-22 | 1996-04-12 | Toshiba Corp | 情報処理システム及びリモート保守方法 |
JP2004132925A (ja) | 2002-10-15 | 2004-04-30 | Akashi Corp | 地震計測システム |
JP2004340672A (ja) * | 2003-05-14 | 2004-12-02 | Ricoh Co Ltd | 時刻設定方法及び時刻設定装置 |
JP2007163201A (ja) * | 2005-12-12 | 2007-06-28 | Morioka Seiko Instruments Inc | 無線ネットワーク装置 |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3751571T2 (de) * | 1986-05-20 | 1996-04-11 | Mitsubishi Electric Corp | Verfahren zur Synchronisation der Echtzeituhren in einem Datenübertragungssystem. |
US5872774A (en) * | 1997-09-19 | 1999-02-16 | Qualcomm Incorporated | Mobile station assisted timing synchronization in a CDMA communication system |
JP2003298630A (ja) * | 2002-04-01 | 2003-10-17 | Mitsubishi Electric Corp | 時刻同期方法 |
JP2003309461A (ja) * | 2002-04-15 | 2003-10-31 | Nec Electronics Corp | 出力バッファ回路 |
JP4032421B2 (ja) * | 2003-02-25 | 2008-01-16 | 横河電機株式会社 | 測定データ同期システム |
JP4184297B2 (ja) | 2004-02-18 | 2008-11-19 | 株式会社大生機械 | 合流コンベア装置 |
WO2006001074A1 (ja) * | 2004-06-25 | 2006-01-05 | Mitsubishi Denki Kabushiki Kaisha | 基地局間時刻同期方法、タイミングマスタ装置、および基地局 |
JP2006195752A (ja) * | 2005-01-13 | 2006-07-27 | Fuji Xerox Co Ltd | 時刻補正機能を備えるネットワーク機器 |
US7561559B2 (en) * | 2005-03-30 | 2009-07-14 | Ixia | Hardware time stamping and processor synchronization |
US8351409B2 (en) * | 2005-04-22 | 2013-01-08 | Axiometric, Llc | Timing synchronization in wireless mesh networks |
US7844703B2 (en) * | 2006-11-02 | 2010-11-30 | International Business Machines Corporation | System and method of measurement for a distributed computer system |
JP4977534B2 (ja) * | 2007-06-07 | 2012-07-18 | 株式会社日立製作所 | センサネットシステム、及びセンサノード |
US7948833B2 (en) * | 2007-07-25 | 2011-05-24 | Computime, Ltd. | Clock setup over a network |
US8089989B2 (en) * | 2007-11-29 | 2012-01-03 | Samsung Electronics Co., Ltd. | Synchronization of nodes on a network |
US7984161B2 (en) * | 2009-06-16 | 2011-07-19 | Microsoft Corporation | Optimizing mobile device synchronization with multiple data sources |
EP2587719B1 (en) * | 2010-06-22 | 2018-08-29 | LG Electronics Inc. | Network system |
US8489775B2 (en) * | 2010-07-21 | 2013-07-16 | Dell Products L.P. | System-wide time synchronization across power management interfaces and sensor data |
WO2012057581A2 (ko) * | 2010-10-28 | 2012-05-03 | 에스케이텔레콤 주식회사 | 클라우드 컴퓨팅 시스템 및 그의 데이터 동기화 방법 |
US20130055273A1 (en) * | 2011-08-30 | 2013-02-28 | Samsung Electronics Co., Ltd. | Terminal and application management method thereof |
CN103327037B (zh) * | 2012-03-20 | 2017-09-29 | 中兴通讯股份有限公司 | 数据同步方法及装置 |
CN103581207A (zh) * | 2012-07-18 | 2014-02-12 | 富泰华工业(深圳)有限公司 | 云端数据存储系统及基于该系统的数据存储与共享方法 |
CN103856517B (zh) * | 2012-11-30 | 2017-06-23 | 英业达科技有限公司 | 同步均衡系统及其方法 |
-
2014
- 2014-07-01 US US14/903,771 patent/US9778679B2/en active Active
- 2014-07-01 JP JP2014555028A patent/JP6280051B2/ja active Active
- 2014-07-01 CN CN201480038647.1A patent/CN105378568B/zh active Active
- 2014-07-01 MX MX2015016899A patent/MX352612B/es active IP Right Grant
- 2014-07-01 KR KR1020157036345A patent/KR20160013964A/ko not_active Application Discontinuation
- 2014-07-01 EP EP14822534.5A patent/EP2990886B1/en active Active
- 2014-07-01 WO PCT/JP2014/067584 patent/WO2015005183A1/ja active Application Filing
- 2014-07-01 AU AU2014288448A patent/AU2014288448B2/en active Active
- 2014-07-01 PE PE2016000027A patent/PE20160094A1/es unknown
- 2014-07-01 BR BR112015030705-1A patent/BR112015030705B1/pt active IP Right Grant
- 2014-07-01 ES ES14822534T patent/ES2759107T3/es active Active
- 2014-07-01 MY MYPI2016000034A patent/MY174086A/en unknown
- 2014-07-01 SG SG11201600141WA patent/SG11201600141WA/en unknown
-
2016
- 2016-01-07 CL CL2016000023A patent/CL2016000023A1/es unknown
- 2016-01-07 SA SA516370365A patent/SA516370365B1/ar unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH04184297A (ja) | 1990-11-19 | 1992-07-01 | Nec Eng Ltd | 情報処理システムの時刻同期化方式 |
JPH0895664A (ja) * | 1994-09-22 | 1996-04-12 | Toshiba Corp | 情報処理システム及びリモート保守方法 |
JP2004132925A (ja) | 2002-10-15 | 2004-04-30 | Akashi Corp | 地震計測システム |
JP2004340672A (ja) * | 2003-05-14 | 2004-12-02 | Ricoh Co Ltd | 時刻設定方法及び時刻設定装置 |
JP2007163201A (ja) * | 2005-12-12 | 2007-06-28 | Morioka Seiko Instruments Inc | 無線ネットワーク装置 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5896584B1 (ja) * | 2015-12-10 | 2016-03-30 | 株式会社テイエルブイ | 無線通信システム及び通信端末 |
WO2017098645A1 (ja) * | 2015-12-10 | 2017-06-15 | 株式会社テイエルブイ | 無線通信システム及び通信端末 |
JP2022124142A (ja) * | 2021-02-15 | 2022-08-25 | 株式会社ミヤワキ | 測定データ送信システム、測定装置及びサーバ |
JP7253275B2 (ja) | 2021-02-15 | 2023-04-06 | 株式会社ミヤワキ | 測定データ送信システム及びサーバ |
Also Published As
Publication number | Publication date |
---|---|
US20160154420A1 (en) | 2016-06-02 |
EP2990886B1 (en) | 2019-09-04 |
ES2759107T3 (es) | 2020-05-07 |
AU2014288448B2 (en) | 2017-02-16 |
US9778679B2 (en) | 2017-10-03 |
MX352612B (es) | 2017-11-29 |
MX2015016899A (es) | 2016-10-21 |
SG11201600141WA (en) | 2016-02-26 |
EP2990886A1 (en) | 2016-03-02 |
JP6280051B2 (ja) | 2018-02-14 |
CN105378568B (zh) | 2018-03-23 |
CN105378568A (zh) | 2016-03-02 |
SA516370365B1 (ar) | 2017-05-29 |
PE20160094A1 (es) | 2016-03-09 |
JPWO2015005183A1 (ja) | 2017-03-02 |
EP2990886A4 (en) | 2017-01-04 |
BR112015030705B1 (pt) | 2022-05-10 |
CL2016000023A1 (es) | 2016-07-22 |
MY174086A (en) | 2020-03-09 |
AU2014288448A1 (en) | 2016-02-18 |
BR112015030705A2 (pt) | 2017-07-25 |
KR20160013964A (ko) | 2016-02-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110870229B (zh) | 用于使从设备同步的技术 | |
KR101788641B1 (ko) | 단말 제어 시스템 | |
JP4840455B2 (ja) | フィールド制御システム | |
KR102374869B1 (ko) | 센서 동기화를 위한 방법 및 장치 | |
JP6280051B2 (ja) | 時刻同期システム | |
JP4901813B2 (ja) | マルチコントローラシステム | |
JP2014003573A (ja) | 多点計測システムおよび時刻同期方法 | |
JP2011193457A (ja) | 時間同期を行うためのシステムおよび方法 | |
KR101492910B1 (ko) | 이더캣 기반의 분산 시계 동기화를 위한 방법 및 시스템 | |
JP2008187235A (ja) | ネットワークシステムおよびスレーブ同期方法 | |
JP2012128552A (ja) | 情報処理装置および情報処理装置の時刻同期方法 | |
JP2016006604A (ja) | 情報処理装置、情報処理方法、及び情報処理プログラム | |
JP7047589B2 (ja) | 同期方法、同期プログラム、及びデバイス | |
JP2018046390A (ja) | 処理装置、システム、処理方法および処理プログラム | |
JP6248502B2 (ja) | 測定システムおよび測定方法 | |
JP2014157386A (ja) | データ処理システム | |
KR20210028446A (ko) | 노드 시간 재설정 방법 | |
US10768579B2 (en) | Timer device and method for operating said timer device | |
JP2015133565A (ja) | 端末制御システム | |
JP2006065523A (ja) | 情報処理装置システム及びその負荷試験方法 | |
JP2009168764A (ja) | 時計機構の同期化方式 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2014555028 Country of ref document: JP Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14822534 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014822534 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2015/016899 Country of ref document: MX |
|
WWE | Wipo information: entry into national phase |
Ref document number: P1690/2015 Country of ref document: AE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112015030705 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 20157036345 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 16002997 Country of ref document: CO |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14903771 Country of ref document: US Ref document number: 000027-2016 Country of ref document: PE |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2014288448 Country of ref document: AU Date of ref document: 20140701 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 112015030705 Country of ref document: BR Kind code of ref document: A2 Effective date: 20151208 |