EP1244083A1 - Procédé de collecte de données de consommation - Google Patents

Procédé de collecte de données de consommation Download PDF

Info

Publication number
EP1244083A1
EP1244083A1 EP01810287A EP01810287A EP1244083A1 EP 1244083 A1 EP1244083 A1 EP 1244083A1 EP 01810287 A EP01810287 A EP 01810287A EP 01810287 A EP01810287 A EP 01810287A EP 1244083 A1 EP1244083 A1 EP 1244083A1
Authority
EP
European Patent Office
Prior art keywords
radio
modules
module
data
level
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP01810287A
Other languages
German (de)
English (en)
Inventor
Urs Augsburger
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Metrix Systems AG
Original Assignee
Metrix Systems AG
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 Metrix Systems AG filed Critical Metrix Systems AG
Priority to EP01810287A priority Critical patent/EP1244083A1/fr
Publication of EP1244083A1 publication Critical patent/EP1244083A1/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
    • G08C17/00—Arrangements for transmitting signals characterised by the use of a wireless electrical link
    • G08C17/02—Arrangements for transmitting signals characterised by the use of a wireless electrical link using a radio link

Definitions

  • the present invention relates to a method for Acquisition of data, especially measurement data such as Consumption data, according to the preamble of claim 1.
  • a such a method is known from DE-A-199 11 657.
  • a wireless data transmission is just in the Building services, e.g. when recording heat consumption, then of particular interest if existing installations are moved or need to be retrofitted by any wiring eliminated.
  • the aim of the invention is the transmission and reception times and thus the energy requirement and the occupancy of the available To keep the frequency band as low as possible. That goal will achieved according to the characterizing part of claim 1.
  • the Sending and receiving times of the individual radio modules can be kept very short by the short time one for sending the collected data immediately short reception follows during which the Confirmation of receipt is given, which if necessary only can consist of a synchronization command. With that is in short time and with correspondingly low energy consumption clarified that the job is done and that Radio module until the next data transmission due date does not have to be ready to send or receive.
  • advantageous Refinements of the method according to the invention result from the following description, the drawings and the Claims.
  • radio module 1 shows the base station 1, also called ComServer in the following, which is directly or indirectly connected to a number of radio modules 2 by radio. All radio modules are preferably constructed identically, ie they have a transmitter and a receiver, memory for storing collected data and also either a measuring device for recording data or a connection via a suitable interface with a measuring device, for example an existing one, installed meter. As shown in FIG. 1, the radio modules are hierarchically arranged in those that have a direct connection to the base station 1 and are assigned to a level 0 (2 0 ), radio modules 2 1 to a level 1, which have one or more radio modules of level 1 are connected and radio modules 2 2 of a stage 2. This is to indicate that the base station 1 has only a connection with some of the radio modules assigned to it or subordinate to it, and that the relay function of intermediate modules 2 0 and 2 1 required.
  • FIG. 1 clearly shows the hierarchical structure of the system, but not an optimal structure, because in levels 0 and 1 each carries a single radio module the load of Relay function for all subordinate radio modules.
  • Fig. 2 indicates that communication between the individual radio modules and the base station over several Paths can be made, a distinction being made between in bold lines denote primary communication paths and secondary or denoted in thin lines alternative communication paths. It means that one each during commissioning Communication path is determined, via which in operation the data are transmitted. Will this be primary Communication path interrupted during operation to Example because a tenant changes the furniture changes the system automatically switches to an alternative Communication path. The alternative communication paths are searched for when installing the system and bookmarked. The system can also be used at any time Look for alternative communication paths, as explained earlier becomes.
  • the system is largely commissioned automatically.
  • Each radio module 2 is installed before ComServer 1 logged on. Every radio module receives automatically an identification address and one Initial send time assigned by the ComServer. Either Identification address and initial send time come in entire system only once. After logging in on ComServer the radio module is in initialization mode. In this mode the module transmits every time A message with when his initial sending time is reached his identification address.
  • the fully automatic Commissioning is now described in more detail.
  • Each module that is in the initial state sends its identification (address that was assigned when logging on to the ComServer) at its initial send time. If the server has received the module's telegram, it gives it the subaddress 0 and a time of transmission. The radio module now changes to the operating state. In the operating state, the radio module contacts the ComServer each time the transmission time is reached. Remarks: The server knows all modules of level 0 after one day. This procedure can already be carried out during the installation.
  • the server addresses the level 0 modules and indicates the initial send times of missing radio modules. At these times, the modules of level 0 should listen. Then a day passes. Each level 0 module listens at the specified times and registers each module from which the identification can be received. Each level 0 module tells the ComServer from which other modules the identification could be received; this takes place the next time the transmission time is reached.
  • the ComServer now determines the communication paths and instructs the level 0 modules, which are to be used as a relay station, to put the level 1 modules into operation.
  • the ComServer instructs the level 0 modules to put the level 1 modules into operation: The level 0 module waits for the initial end of the level 1 module to be put into operation. This reports at the time of initialization.
  • the module of level 0 answers and announces the new subaddress and the reception time window for the module of level 1. If the module of level 0 has received the receipt of the level 1 module, this can be communicated to the ComServer the next day. Comment: The server knows all level 1 modules after two days.
  • the ComServer must ask the level 1 modules whether they can receive a telegram at the initial send time of a missing module. For this purpose, inquiries are sent to the level 1 modules. The command is passed from level 0 modules to level 1 modules. These listen to a telegram in the specified time window. One day is needed for this. Two days pass before the results return to the ComServer. Another day is required to provide the level 2 modules with a subaddress and reception time window. Confirmation of successful commissioning is due after a further 2 days. Note: The server knows all level 2 modules after six days.
  • the radio system can be supplemented with additional modules at any time become. To do this, the modules only have to be registered on the ComServer commissioning takes place exactly the same as this is described in the paragraph "Fully automatic commissioning" is.
  • the network structure, the reception time windows and the initial transmission times of the individual modules are stored in the ComServer. So that a connection to the radio modules can be established when the ComServer is replaced, at least the initial transmission times of the modules must be saved on a non-volatile storage medium. If the ComServer is replaced, the storage medium is removed from the old ComServer and used in the new one. The radio module of the old ComServer must also be used in the new one, otherwise the synchronization between the ComServer and the level 0 modules will be lost. If the radio module of the ComServer also has to be replaced, the synchronization with the modules of level 0 is also lost. In this case, the ComServer must be ready to receive until it receives the message from a module. Thanks to the data stored in the storage medium, the timer of the ComServer can then be synchronized.
  • a module After a module has sent a telegram, it switches ready to receive a response from the Receive ComServers. Since the ComServer the time of transmission knows each radio module, it can determine the deviation, with which the module sent the telegram. This Deviation will be the level 0 module as part of the answer sent back. The level 0 module can now use its timer correct according to the deviation.
  • level 1 or level 2 module The synchronization of a level 1 or level 2 module is the same as a level 0 module, except that instead of the ComServer a relay station (level 0 resp. Level 1 module) occurs.
  • the meter data is read out via the interface according to ISO 7816 (smart card).
  • the data is stored in the radio module cached and at agreed times, e.g. transmitted to the ComServer once a week.
  • the data are read out regularly at defined times. It but there is also the possibility that by a command an additional reading is triggered on the ComServer.
  • the frequency of the quartz can be measured precisely during production (final test). A deviation from the target frequency can now be approximately compensated during operation, since the actual frequency is known.
  • the current consumption of the Receiver relatively large. To be as long as possible To be able to realize the battery life would have to be the reception readiness should be set as short as possible. So that the inaccuracies due to the temperature-related Drifts of the quartz frequency can be reliably absorbed the receiver must be open for as long as possible So there has to be a compromise between energy needs and Compensation ability can be found.
  • the quartz temperature of the transmitter module deviates more from the calibration temperature than that of the receiver module.
  • the frequency of the quartz is therefore lower, the timer of the transmitter lags behind the timer of the receiver.
  • the quartz temperature of the transmitter module deviates less from the calibration temperature than that of the receiver module.
  • the transmitter's timer precedes the receiver's timer.
  • the duration of the reception window must not be shorter than that prescribed transmission pause can be selected. In order to it is ensured that at least one attempt Establish connection within a reception window takes place, the interval of the connection establishment be shorter than the reception window. To determine the minimum duration of the reception window, the time must still are added, which is required for communication. Assuming that for the telegram (including switching on of the transmitter) 30ms are required, the Willingness to receive last at least 750ms. If another Small reserve should be provided, the duration of the Willingness to receive is about 800 to 900ms long. Accordingly, the interval of connection establishment between approx. 760 and 860ms long. Now become the well-known Values used in the graphic Fig. 3, the 4 derive:
  • a module cannot establish a connection for any reason, it cannot be synchronized. So that the connection can be established in the next allocated time range, the number of attempts to establish a connection must be increased. The number of these attempts is therefore a function of the time that has elapsed since the last successful synchronization. The number of attempts is increased by 4 for each day on which synchronization was not possible. The attempts to establish a connection are distributed symmetrically in time around the time T 0 .
  • the time window in which a connection is established can, grows by 4 times 760ms every day, i.e. by 3.04s. this time window (from the second day) increases by approx 10% stronger than this for the assumed values for the Deviation of the quartz frequency would actually be necessary.
  • the connection is always established by a "UpStream telegram". Communication is always from initiated at a subordinate level. Would Communication started with a "DownStream telegram", the number of modules of the lower level would have to be due to the Restriction of the duty cycle can be severely restricted. In addition, during commissioning and operation, the same procedures are used.
  • the module of higher level After the module of higher level has received the telegram, answers it with an instruction to the module that communicates initiated. The answer includes next to the Command (s) also the synchronization data to align the Module timer.
  • the timer of a radio module is on the Timer of the module of the higher level synchronized. Since this transmission time of this answer is very short, a radio module has a very large number of subordinate ones "Operate" modules. This is especially true for the ComServer significant.
  • the maximum system size can be determined.
  • Each module is assigned its own time range in which it contacts the higher-level module.
  • the duration this time period is chosen so that there are two Do not overlap time periods even if an or multiple modules on multiple consecutive days are not can be synchronized:
  • the level 0 modules are in direct contact with the ComServer. Since the duty cycle is also restricted for the ComServer applies, the number of level 0 modules is determined by the length of the DownStream telegrams from the ComServer to the level 0 modules certainly.
  • the ComServer has 474 level 0 modules 182ms available for each DownStream telegram. In These 182ms can both synchronization signals as well Commands are transmitted. Because in the direction of the ComServer no consumption data are transmitted to the radio modules, broadcast time is no longer required. This should be for this Function should be sufficient.
  • a radio module Since the data that has to be passed from a module of level 1 or 2 via at least one relay station, it can take up to two days before the data arrives at the ComServer. Therefore, a radio module should only be assigned to level 1 or 2 if it is outside the range of the ComServer.
  • the modules of levels 1 and 2 use different radio modules as relay stations. Since the storage capacity and computing power of the radio modules is limited, the number of "sub-modules" that a single radio module can have must be limited.
  • Offer one level 1 or 2 radio module several Communication paths to the ComServer are the primary Select communication paths so that each relay station receives as few sub-modules as possible.
  • the radio module sends out its identification address each time the initial transmission time is reached.
  • the telegram with the identification address including CRC, interleaving etc. is 16 bytes long.
  • the identification address takes 26.7ms to be sent.
  • the radio module must establish the connection as described above. Every day on which no connection can be established, the initial send time and the receive window of potential communication partners can drift apart. The time window in which communication can take place increases every day according to the chapter "Tolerances of the quartz frequency" 1.35 s for a total of 2.7s. So that the radio module can be registered even after several days, it must increase the number of telegrams sent every day.
  • Each module may not transmit its transmitter for longer than 3.6 s turn on within an hour. If the Frequency band during 30 ms per UpSream telegram may be in a maximum of 120 telegrams can be sent per hour. This enough for one radio module for 30 days in the initial state to be able to operate. The 120 telegrams are in Intervals of at least 720 ms sent. All Telegrams can therefore be sent from a radio module within it allocated time range. Should be more than 30 days in the initial state can be bridged (e.g. because a relay station has failed and none offers alternative communication path), the module additional reception windows at the higher level allocated or the reception window extended so that the module in the initial state the time between two Transmissions of the telegram can extend. But it has to care is taken that the allotted Do not overlap time periods of two modules.
  • FIG. 2 only shows the example shows the available connection options.
  • Fig. 2 also does not show that one can Possibility of designing the network so that the Relay station serving radio modules about the same number of via modules communicating with them, so all modules have similar loads and are therefore roughly the same Have operating time without changing the battery.
  • the radio network can also be expanded in the sense that the base station via radio with a parent Data processing center is connected. It can do that local radio network shown here and described above 1, 2 that for example for recording the heating energy or - A similar, more powerful radio network serves costs be parent, which is also an existing one Modbilfunknetz can act.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
EP01810287A 2001-03-21 2001-03-21 Procédé de collecte de données de consommation Withdrawn EP1244083A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP01810287A EP1244083A1 (fr) 2001-03-21 2001-03-21 Procédé de collecte de données de consommation

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP01810287A EP1244083A1 (fr) 2001-03-21 2001-03-21 Procédé de collecte de données de consommation

Publications (1)

Publication Number Publication Date
EP1244083A1 true EP1244083A1 (fr) 2002-09-25

Family

ID=8183805

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01810287A Withdrawn EP1244083A1 (fr) 2001-03-21 2001-03-21 Procédé de collecte de données de consommation

Country Status (1)

Country Link
EP (1) EP1244083A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1705620A1 (fr) * 2005-03-24 2006-09-27 ista Shared Services GmbH Procédé de synchronisation de noeuds du réseau en réseau correspondant
EP2150084A3 (fr) * 2008-08-01 2017-08-09 Techem Energy Services GmbH Procédé et dispositif de transmission de données
US11509977B2 (en) 2017-05-20 2022-11-22 Diehl Metering Systems Gmbh Method for operating a supply system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4455453A (en) * 1979-01-26 1984-06-19 Metretek, Incorporated Apparatus and method for remote sensor monitoring, metering and control
EP0629098A2 (fr) * 1993-05-17 1994-12-14 Logica Uk Limited Compteur domestique
WO1999065169A1 (fr) * 1998-06-09 1999-12-16 Abb Power T & D Company Inc. Synchronisation temporelle d'un compteur de reseau public de distribution via un reseau radio

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4455453A (en) * 1979-01-26 1984-06-19 Metretek, Incorporated Apparatus and method for remote sensor monitoring, metering and control
EP0629098A2 (fr) * 1993-05-17 1994-12-14 Logica Uk Limited Compteur domestique
WO1999065169A1 (fr) * 1998-06-09 1999-12-16 Abb Power T & D Company Inc. Synchronisation temporelle d'un compteur de reseau public de distribution via un reseau radio

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1705620A1 (fr) * 2005-03-24 2006-09-27 ista Shared Services GmbH Procédé de synchronisation de noeuds du réseau en réseau correspondant
EP2150084A3 (fr) * 2008-08-01 2017-08-09 Techem Energy Services GmbH Procédé et dispositif de transmission de données
US11509977B2 (en) 2017-05-20 2022-11-22 Diehl Metering Systems Gmbh Method for operating a supply system

Similar Documents

Publication Publication Date Title
DE60030363T2 (de) Funknetzwerksteuerung
DE102014012518A1 (de) Mesh-relais
DE102005049931B4 (de) Sende-/Empfangsvorrichtung
DE102009003724A1 (de) Verfahren zur Optimierung von Netzwerkstrukturen in Funknetzwerken
EP1759537B1 (fr) Procede d'etablissement d'un reseau de communication auto-organise sans fil et transfert de fonctionnalite de station de base
DE102021103225A1 (de) LoRaWAN-Gateway-Netzwerk und Verfahren
EP1282094B1 (fr) Méthode de transmission hertzienne dans un système d'alarme
DE19905316A1 (de) Datenübertragungssystem, insbesondere zur Verbrauchsdatenerfassung
EP1037185B1 (fr) Méthode de transmission de données
DE102005036255B4 (de) Datenübertragungssystem und Verfahren zum Betreiben eines Datenübertragungssystems
EP1860830B1 (fr) Procédé d'installation d'un réseau hiérarchique
EP3477961A1 (fr) Procédé de transfert des données et collecteur de données
EP1244083A1 (fr) Procédé de collecte de données de consommation
WO2008034676A1 (fr) Procédé de radiotransmission dans un système avertisseur de danger
EP3525476B1 (fr) Procede de determination de topologie d'un site de communication mobile et un site de communication mobile correspondant
DE102005036250B4 (de) Funkübertragungssystem
DE102017119629B4 (de) Verfahren zur Funkübertragung von Daten in einem Erfassungssystem sowie Sensorsende- und Empfangsgerät
DE102017005625B4 (de) Verfahren zum Betrieb eines elektronischen Datenerfassungsgeräts und Datenerfassungsgerät
EP2413299B1 (fr) Procédé d'alerte pour systèmes de communication radio
EP1653677B1 (fr) Système radio pour transmission de données et collecteur de données
EP0536539B1 (fr) Réseau d'appel radio pour la transmission de signaux d'appel radio relatifs aux abonnés et méthode pour son exploitation
DE102018131560B4 (de) Selbstorganisiertes Datensammlernetzwerk
DE102021120702A1 (de) Lorawan-gateway-netzwerk und verfahren
EP2637459B1 (fr) Procédé destiné à l'organisation et/ou à la mise en service d'un réseau de communication et n'uds de réseau
EP1282095B1 (fr) Procédé de communication radio dans un système d'alarme

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

AKX Designation fees paid
REG Reference to a national code

Ref country code: DE

Ref legal event code: 8566

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20030326