Push mode transmission device and method and related computer program product

Abstract

A push mode transmission method is described, implemented by a transmitting device comprising a memory comprising software code and a processor, when the processor executes the software code, directing the device to implement the method, the method comprising: (a) triggering (201) a transmission to a receiving device of a value adapted to comprise an attribute of ordered data, the values of the data are all values or partial values, and the transmission at most comprises a value of a single selection interval of the ordered data; (b) verifying (204) whether the attribute does not contain a value to be transmitted for all N adjacent intervals of data selection from a starting point selected in data order to the end of a previous interval containing an interval of the current data collection cycle; (c) if the verification is positive, transmitting (214) at most one message in all N intervals in the push mode. An implementation apparatus and a recording carrier are also described.

Description

Technical Field

[0001] A push mode data transmission method, an apparatus for implementing the method and a related computer product are described, which can be used, without limitation, to transmit cyclically collected data. Background Art

[0002] In many applications, devices accumulate data either periodically or aperiodically, which requires the collection of data accumulated by the producer's server device by a client receiving device. This is the case, for example, with meters of various nature, such as electricity, gas, water or heat meters. The amount of data generated by such devices in a given time interval is not always predictable. Devices can generate periodic data, such as the value measured by a meter at a given moment and recorded once per cycle. However, if there are problems with the data generation, there may be periods without data. Devices can also generate aperiodic data, such as data in the form of event logs. In these cases, the amount of data is inherently unpredictable.

[0003] An efficient transmission method taking these aspects into account is needed. Summary of the invention

[0004] One or more embodiments relate to a push mode transmission method implemented by a sending device, the sending device comprising a memory containing software code and a processor, when the processor executes the software code, directing the device to implement the method, the method comprising:

[0005] (a) triggering the transmission to a receiving device of values ​​for an attribute comprising ordered data, the values ​​of said data being all or part of the values, the transmission comprising at most the value of a single selected interval of the ordered data;

[0006] (b) for all N adjacent intervals selected from the starting point selected in data order until the end of the interval preceding the interval containing the current data collection period, verify that the attribute does not contain the value to be transmitted;

[0007] (c) If the verification is positive, a single message is transmitted indicating that the N intervals have no value.

[0008] According to one or more specific embodiments, if the verification is negative, a message is transmitted to the receiving device in push mode, the message containing the value of a first non-empty interval of the value to be transmitted, and no message is transmitted for an empty interval of the value to be transmitted before the first interval.

[0009] According to one or more specific embodiments, the method comprises, after transmitting a message with a value, receiving an acknowledgement from the receiving device and receiving an information update, the information identifying the last confirmed value of the attribute.

[0010] According to one or more specific embodiments, the start point of the data sequence is adjacent to the end point of the interval containing the value most recently acknowledged by the receiving device.

[0011] According to one or more specific embodiments, the starting point of the data sequence is counted from the value most recently acknowledged by the receiving device.

[0012] According to one or more specific embodiments, the determining step is preceded by a step of filtering the attribute data according to one or more criteria to determine the value to be transmitted.

[0013] According to one or more specific embodiments, the verification involves a set of multiple attributes and corresponding intervals, wherein each attribute has no value to be transmitted, and the verification is deemed to be positive in step (c).

[0014] According to one or more specific embodiments, the only message indicating that the N intervals have no values ​​includes an empty array.

[0015] According to one or more specific embodiments, N is greater than or equal to 2.

[0016] According to one or more specific embodiments, the data is arranged in order from the oldest data to the most recent data.

[0017] According to one or more specific embodiments, the data comprises a timestamp, wherein the order is a function of the timestamp.

[0018] According to one or more specific embodiments, the selection interval is one of an interval defined by a number of values ​​or an interval defined by a duration.

[0019] According to one or more specific embodiments, the time interval includes one or more data collection cycles corresponding to the depth of data selection.

[0020] One or more embodiments relate to a readable storage medium readable by a device equipped with a processor, the carrier comprising instructions which, when the program is executed by the processor of the device, direct the device to implement at least one of the methods described.

[0021] One or more embodiments relate to a communication device comprising means capable of implementing at least one of the methods described. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Other features and advantages of the present invention will be described by reading the following specific embodiments. For ease of understanding, reference will be made to the following drawings, in which:

[0023] Figure 1 is a block diagram of a system including a server device and a client device according to one or more embodiments;

[0024] Figure 2a The first part of the algorithm diagram of the data push method according to one or more embodiments;

[0025] Figure 2b This is the second part of the algorithm diagram of the data pushing method according to one or more embodiments. DETAILED DESCRIPTION

[0026] In the following description, the same, similar or similar elements will be denoted by the same reference numerals.

[0027] The block diagrams, algorithm diagrams and message sequence line diagrams in the figure illustrate the structure, function and operation of computer systems, devices, methods and program products according to one or more embodiments. Each block of the block diagram or each stage of the algorithm diagram can represent a module or part of a software code, including instructions for implementing one or more functions. According to certain implementations, the order of the blocks or stages can be changed, and the corresponding functions can be implemented simultaneously. For all or part of the blocks or stages, circuits, software or a combination of circuits and software can be used to implement the stages of the blocks or methods in a centralized or decentralized manner. The systems, devices, methods and means described can be modified, added and / or deleted within the scope of this specification. For example, the components of the device or system can be integrated or independent. Moreover, the functions described can be implemented using more or less components or stages, or using other components or through other stages. Any suitable data processing system can be used for implementation. Suitable data processing systems or devices include, for example, a combination of software code and circuits, such as a processor, a controller or other circuits suitable for executing software code. When the software code is executed, the processor or controller guides the system or device to implement all or part of the functions of the stages of the blocks and / or methods or means according to the embodiment. The software code may be stored in a readable memory or carrier and may be accessed by a processor or controller directly or through another module.

[0028] Figure 11 is a block diagram of a communication network, which includes a device 100 and a device 110 capable of communicating in a bidirectional manner through a network. Device 100 is a device that stores accumulated data or accumulates data itself, at least some of which is to be transmitted to device 110. Device 100 is referred to as a "server" and device 110 is referred to as a "client" hereinafter. For example, server 100 is a meter for electricity, water, gas, heat energy, etc., and client 110 is a device that collects data from each server for metering by allocating network operators. Server 100 has a processor 101, a memory 102, a data source 103, a user interface 105, a communication interface 106 configured to communicate bidirectionally with client 110, a display 107 suitable for displaying data to a user of server 100, and a working memory 109. The various components of server 100 are connected via a communication bus 104. Memory 102 has software code 108. Memory 109 is used to store and manage data to be transmitted. When the processor executes the software code 108, it guides the server to implement the method according to one or more embodiments, and includes processing the empty data in the data to be transmitted, as will be explained in more detail below. For example, these data come from the data source 103. For example, the data source 103 is the metering component of the meter itself, which generates the value of the amount to be measured. For example, the metering component is responsible for measuring and recording absolute physical quantities (current intensity, gas pressure) or cumulative physical quantities (electrical energy or gas volume passed). The data can be obtained in a periodic or aperiodic manner, or include a combination of data obtained in a periodic or aperiodic manner. The fact that data is usually obtained periodically does not exclude the absence of data in a long or short time interval (power failure, failure, sleep interval or data is not representative, etc.). For example, the communication network is one of 2G / 3G / 4G / LTE NB-IoT / LTE Cat-M1 / LoRA or other types of radio media.

[0029] DLMS or "Device Language Message Specification" consists of a series of standards developed and maintained by the DLMS User Association ("DLMS UA") for standardizing the exchange of data for electricity meters, etc. DLMS UA maintains in particular the "COSEM Blue Book" (Comprehensive Semantic Model for Energy Management). In particular, the 15th edition of the "DLMS UA 1000-1" document, version 1.0 of December 21, 2021, part 2 describes the elements used in the push of data ("push") from the server to the client, and on which the client confirms the receipt or acknowledges the received data. The document introduces a mechanism that allows to select a certain amount of recorded data to be pushed based on the last confirmed data at each periodic trigger sent by push. For example, a time interval can be specified based on the last confirmed data (e.g. "three days after the last confirmed data". The various options are described in Table 9 of the referenced DLMS UA document. This allows limiting the number of single transmissions to protect the operation of the delivery network and the clients responsible for collecting and processing the data and not overload them due to long periods of lack of communication and / or a large number of devices.

[0030] According to one or more embodiments, the data accumulated by the server 100 in the memory 109 is at least partially recorded in history, i.e., sorted in time. "Sorted in time" means that, according to the selected embodiment, time information is associated with the data and the order of the data is determined by the time information, or simply put, the data is given in the order in which it is obtained or recorded. For example, the server 100 samples the metering member 103 at regular intervals and stores the value measured by the member in its memory, where the value is associated with the value of a clock, which, for example, identifies the sampling moment or the period covered by the value. For example, the period is identified by the time value at the end of the period. Thus, a load curve that changes over time, for example, is obtained. Other information can be associated with these two values.

[0031] The server may include multiple metering components that provide corresponding values ​​for different quantities, thereby associating multiple data with a unique time value (eg, the right two columns of Table 1 shown below). The data is stored in memory, for example, in an object having one or more suitable attributes.

[0032] If you select data that is generated periodically within a certain time interval (for example, an integer multiple of a day), the amount of data will always be the same. However, in some cases, the amount of data within a cycle may vary, such as

[0033] When the server is down for a long time and therefore the data generation process is not executed;

[0034] Resetting to a future time can result in a significant time jump (for example, if the server is brought back into service and the energy reserve powering the real-time clock has been depleted, or has not been set on time).

[0035] The same problem occurs when entries are created acyclically, such as is the case with event log entries.

[0036] Table 1 is an example of normal periodic data that might be generated by the meter 103 of the server 100 itself. For example, the server may generate and store thousands of entries, which may be overwritten based on a periodicity (e.g., running for months).

[0037] [Table 1]

[0038]

[0039] In Table 1, one entry is represented by one row and one structural element is represented by one column.

[0040] According to the example in the table, sampling is done every hour, and a normal day has 24 entries. In the example, no entries are stored between 2022-01-21 and 2022-06-29 because the meter was turned off. Selecting a time interval when the meter was deactivated (for example, a request from 2022-02-01 to 2022-03-01) will return an array of zero entries.

[0041] Each time the push data transmission is triggered, the server 100 estimates the values ​​associated with the specified attribute list in the attributes of the push mechanism. The retained values ​​will be connected to the so-called push buffer (tampon, English "push buffer") and encapsulated into the protocol data unit of the appropriate application layer for transmission to the client.

[0042] In DLMS, this data unit is marked as "APDU DataNotification".

[0043] The content of the push buffer is obtained by extracting the attribute values ​​in whole or in part. Partial extraction can be implemented by selecting the values ​​to be sent from the appropriate attributes by applying one or more filters, such as time criteria, such as time intervals, entry indices or structural elements.

[0044] The client generates a receipt, also called a "confirmation" of the received data. The server thus knows the "last confirmed entry" for each of the relevant attributes. This allows selecting and sending only data that has not yet been confirmed from this entry. For example, data selection is performed by specifying a data depth, which can be defined, for example, by a time interval counted from the last confirmed data, for example by a number of cycles ("depth of 3 full days after the last confirmed entry"). In some embodiments, the depth is defined by a time interval counted from the previous time interval containing the last confirmed data. This allows limiting the amount of data sent at a single time to protect the operation of the transport network and the clients responsible for processing the data and not to overload it.

[0045] For each relevant attribute, in case of a successful push, i.e. if the client confirms the send, the pointer to the last confirmed data will be updated to move to the new last confirmed data. In case of failure, the pointer will remain at the position before the send and will be the original date of the new selection, which may contain new data generated in the meantime. Therefore, the oldest data will be sent first.

[0046] The transmission is in the form of an array. An array is a data structure that contains timestamped entries. Table 1 gives an example of the structure of such an array. A transmission with no data is represented by an empty array, that is, an array with zero entries.

[0047] In the following examples, the data considered are entries containing a timestamp and filtered according to the last confirmed data. For the sake of clarity and simplicity, the case of a single attribute is considered, whose data is to be transferred, and in principle, all data recorded within an interval are to be transferred.

[0048] The first run example is as follows:

[0049] Push mode transfers are triggered on a daily basis. Transfers only concern complete days, so the first transfer is made on the second day based on the data from the previous days. In fact, the second day is always in the current cycle. In this case and at this stage of the method, there is only one day before, the first day (the day on which the data for the second day is completed).

[0050] Data selection is done at the latest within two full days after the last data confirmation (so the maximum depth is two days). According to this example, part-full days will not be selected because they are always in the current cycle.

[0051] Day 2: The day when data needs to be sent (Day 1), the data is sent successfully.

[0052] Day 3: The day when data needs to be sent (Day 2), but the sending fails.

[0053] Day 4: Data needs to be sent on two days (day 2 and day 3), but the sending fails.

[0054] Day 5: Data needs to be sent for 3 days (2nd, 3rd, 4th), but the selection is limited to (2nd, 3rd), and the sending is successful.

[0055] Day 6: Data needs to be sent on the 2 days (4th and 5th), and the data is sent successfully.

[0056] Day 7: The day when data needs to be sent (day 6), the data is sent successfully.

[0057] …

[0058] After each transmission confirmation, upon receiving the receipt from the client, the server moves the pointer of the last confirmed data forward.

[0059] The maximum depth is chosen to limit the amount of data in a push mode transfer to a reasonable size while allowing for catching up on failures of previous transfers.

[0060] The second operation example is as follows: The situation is that the time interval between the last sent data and the current time is large (for example, dozens of cycles), and the data contains a time interval in which the generated data is empty.

[0061] Trigger push mode transmissions on a daily basis.

[0062] Data selection was performed at the maximum depth of two days.

[0063] Assume that the data on day 1 is not empty (from 00:00 on day 1 to 00:00 on day 2), after the server is shut down for dozens of days, the data on day 2 and thereafter are empty, and the periodic push mode transmission method is restored on the 50th day.

[0064] Day 50: Day 1 (up to and including 00:00 on Day 2) and Day 2 (empty) are sent.

[0065] Day 51: Day 2 (excluding 00:00 on Day 2, so there is no new confirmed data on Day 2) and Day 3 (no new confirmed data) are sent.

[0066] Day 52: Day 2 (excluding 00:00 on Day 2, so there is no new confirmed data on Day 2) and Day 3 (no new confirmed data) are sent.

[0067] …

[0068] In other words, a number of empty intervals, at least equal to the depth or interval of the data selection, will cause an empty transmission cycle to run. Even if data appears on day 50 or later, it will not be transmitted because the pointer to the last confirmed data will not be able to advance.

[0069] A possible solution to this problem is to advance the pointer of the last acknowledged data to the end of the interval under consideration after each push mode transmission. In the second example above, the pointer is advanced by two days at each push mode transmission. In order to bring the pointer as close as possible to the current time, several empty transmissions are required. If the depth of the interval is chosen to be two days, the delay will not be made up until the 98th day.

[0070] According to one or more embodiments, when considering transmission of ordered data in push mode, the server will determine whether there is data to be transmitted. This determination can be done through consecutive data selection intervals.

[0071] According to a first mode of operation (hereinafter "Mode 1"), a push mode transmission will occur at the last empty interval of data to be transmitted before the interval covering the current data collection period. The transmission may include information indicating that there is no data to be transmitted, for example in the form of an empty array.

[0072] According to a second mode of operation (hereinafter "mode 2"), if it is determined that there is no data to be transmitted, then push mode transmission is not performed and the transmission is canceled.

[0073] In both cases, if an empty interval or a succession of such intervals to be transmitted is followed by an interval with data, push mode transmission is not performed for the interval to be transmitted or the succession of empty intervals, but rather for the non-empty interval.

[0074] It should be noted that data for an interval can be recorded but not transmitted, for example based on one or more selection criteria. In this case, the interval is considered "empty". If data to be transmitted are specified, these are also referred to as "values" to be transmitted.

[0075] According to mode 1, the server analyzes the content of the past interval. If no value was selected for transmission within this interval, it moves on to the next interval. However, the cursor pointing to the start of the considered interval is advanced to the end of the previously considered selection interval.

[0076] This method is iterated until the end of the selected interval is no longer in the past (in other words, until this end is later than the start of the current time interval, so that the current time interval is incomplete), or until the selected interval contains a value to be transmitted. In the latter case, a push mode transmission is performed, and the pointer to the last confirmed entry is advanced according to this transmission after positive confirmation by the client.

[0077] Therefore, the server skips empty selection intervals for values ​​to be transmitted, because no push mode transmissions can occur during these intervals.

[0078] When there is no selected interval with data to be transmitted before the current moment, a single push mode transmission containing an empty array is performed for all empty intervals. It should be noted that an empty array is mentioned here because this is the structure used for data transmission in this example, but according to other embodiments, the information indicating that no value to be transmitted has been determined can be encoded in other ways.

[0079] One advantage is that a push mode transport sending this information allows the server to inform the client that the server is still running, but has no values ​​available to be transmitted.

[0080] According to one embodiment, in Mode 1, when multiple attributes are analyzed and none of them have values ​​to be transmitted, information indicating that there is no value to be transmitted is transmitted for each attribute.

[0081] According to a second push transmission mode, hereinafter referred to as "Mode 2" also similar to Mode 1, if there are no selected intervals with values ​​to be transmitted up to the current time, no push mode transmission is performed.

[0082] The advantage is that it saves network bandwidth. This is very useful in applications where data is generated infrequently, such as entries in infrequent event logs. In addition, this mode is also suitable for servers running on a stack because it is more energy-efficient than mode 1.

[0083] Based on the above examples, examples of operations according to mode 1 or 2 are as follows:

[0084] Trigger push mode transmissions on a daily basis.

[0085] The selection of data to be transmitted is made at a maximum depth of two days.

[0086] The values ​​to be transferred start from day 1, which has data, but there is no data from day 2 to day 100.

[0087] The push mode periodic transmission method starts from the 50th day.

[0088] Day 50: Day 1 and Day 2 are sent (Day 1 is non-null).

[0089] Day 51: The pending transmission values ​​for days 3 and 4 are empty and are not sent.

[0090] Day 51: The pending transmission values ​​for days 5 and 6 are empty and are not sent.

[0091] …

[0092] Day 51: The pending transmission values ​​for days 47 and 48 are empty and are not sent.

[0093] Day 51: Days 49 and 50 are empty and either not sent (mode 2) or sent with an empty array (mode 1).

[0094] Transmission delays are thus compensated.

[0095] In the example, the compensation of the current time means that the end point of the selected interval is at the end of the complete (or completed) period before the current period at the latest, so the current period is incomplete and may be extended by new data.

[0096] According to one or more embodiments, a third operation mode is defined, referred to as "Mode 0". According to this mode, message transmission is systematically performed in a push mode after a transmission trigger - wherein the presence or absence of a value to be transmitted does not affect the transmission.

[0097] According to one or more embodiments, modes 0, 1 and 2 may be performed by the same server. Therefore, means are provided to allow the mode to be selected. The transmission mode is selected based on the context, such as automatically (e.g., wake up after a failure or shutdown, etc., and then switch to mode 1 or 2), or by the user through a user interface, which is managed by the software code 109.

[0098] According to other embodiments, the server may execute only one of modes 1 or 2, or both.

[0099] Modes 1 and 2 allow for no empty messages to be sent if the data has gone through a period without data being generated – the first message sent will contain data. Additionally, if there are no values ​​to be transmitted after the last acknowledged value, the number of empty messages sent will be 0 or 1 depending on the mode, which limits the bandwidth used.

[0100] When one of modes 1 and 2 is identified in an attribute, these modes are only performed on one or more target attributes, the target containing ordered data selected based on the last confirmed data. Other attribute values ​​of the push buffer are either transmitted in the default mode (e.g., mode 0) or not transmitted, as will be explained in more detail below.

[0101] As described above, Mode 2 can also be applied to the case where data is selected based on the number of entries (rather than the time interval) after the last confirmed data.

[0102] Figure 2a and Figure 2b The combination forms an algorithm diagram of a data push method according to one or more non-limiting embodiments and executes the above-mentioned mode.

[0103] exist Figure 2aIn 201, push mode data transmission is triggered. According to some embodiments, this triggering is periodic, according to other embodiments, the triggering is not periodic - for example it is associated with a triggering event.

[0104] In 202, a selection of target attributes to be pushed is performed. For example, this selection is based on a predefined list, one or more selection criteria, etc. The first attribute of the target attributes selected in step 202 is then analyzed in 203 to determine whether it can be processed for a given empty selection interval.

[0105] According to the present embodiment, and as previously described, this condition is satisfied if the attribute contains ordered data and said data is selectable at a specified depth after the last data is confirmed by the client.The processing of empty intervals is applied to the attributes in the left branch 210 of the algorithm diagram.

[0106] Attributes that do not meet the test criteria in 203 are evaluated in 208 in the right branch 211. The further data include, for example, historical data.

[0107] According to some embodiments, this evaluation may include the decision whether to transmit other data. In fact, these data may be ancillary data of the historical data processed in branch 210, but in the absence of historical data, it may not make sense to use bandwidth to transmit some other data.

[0108] The evaluation outputs in processing branches 210 and 208 are combined together in 209 .

[0109] According to one or more embodiments, the processing of empty intervals of attribute values ​​to be transmitted is as follows: In the case where there is a target attribute that can be processed, the content of the attribute in the first selection interval at a determined depth is analyzed to determine whether it contains the value to be transmitted (204). Determine whether the transmission should be performed in push mode 1 or 2 (test in 205). If the transmission is not performed in mode 1 or 2, proceed to step 209. Otherwise, determine in 206 whether the selection is empty. If so, consider the next selection interval (207) and re-determine whether the value to be transmitted in 206 is empty. Continue the 206 / 207 loop until the selection interval contains the value to be transmitted, or the end point of the selection interval is no longer a past time point. The exit of the 206 / 207 loop leads to test 209. In 209, evaluate whether all attributes to be pushed have been considered-if this is not the case, select the next attribute and resume processing in 203.

[0110] exist Figure 2bIn , if all attributes to be pushed are considered, it is determined whether none of the attributes processed in branch 210 contain attribute values ​​to be transmitted. If so, and if the push mode is mode 2, no sending in push mode is performed until the next trigger (213). In other cases, sending in push mode is performed in 214, which contains data to be sent from one of the two branches 210 or 211. If neither branch provides data to be transmitted, an empty transmission is performed. In the event that a client confirmation is received (the test in 215 is positive), an update of the last confirmed entry is performed for each attribute processed in branch 210 (216). If no confirmation is received, it is planned to try to send again (217).

[0111] Referring to the DLMS standard, step 202 includes, for example, checking a target attribute list to be pushed, wherein the list is defined by an attribute named "push_object_list". Step 203 includes, for example, verifying whether the target has a data buffer corresponding to the so-called "generic profile" interface level and includes data selection according to the last entry marked as confirmed, the depth of the selection interval according to the last confirmed data is defined by configuration data called "data_index" and defined by Table 9 of the aforementioned Blue Book.

[0112] Various advantages have been described above. A specific embodiment may have one or more of these advantages, but not necessarily all of them. Some embodiments may have one or more advantages not described and / or may not have the advantages described.

[0113] appendix

[0114] It is proposed to define an attribute that characterizes push mode management in a push mode transport method and this attribute may have one of the following three values:

[0115] Mode 0=SAUT_DESACTIVE (English "SKIP_DISABLED"):

[0116] Default mode. The method of skipping empty selection intervals is disabled.

[0117] Mode 1 = SAUT_ENVOIVIDE (“SKIP_EMPTYSEND”):

[0118] According to mode 1, a method of skipping empty selection intervals is enabled.

[0119] Mode 2=SAUT_PASENVOIVIDE (English "SKIP_NOEMPTYSEND"):

[0120] According to mode 2, a method of skipping empty selection intervals is enabled.

[0121] In DLMS:

[0122] An example of an ordered data structure that is selected based on the last acknowledged data is a buffer of Class 7 objects, where the selection is made based on the last acknowledged data. A DLMS / COSEM Class 7 buffer is a buffer filled with periodically or aperiodically "captured" objects that can be accumulated in order of arrival or filtered based on an object (e.g., timestamp).

[0123] Part Number

[0124] 100-Server Equipment

[0125] 101-Processor

[0126] 102-Memory

[0127] 103-Meter

[0128] 104-Communication bus

[0129] 105-User Interface

[0130] 106-Bidirectional communication interface

[0131] 107-Display

[0132] 108-Software Code

[0133] 109-Working memory

[0134] 110-Client device.

Claims

1. A push mode transmission method, implemented by a sending device, the sending device comprising a memory containing software code and a processor, when the processor executes the software code, the device is directed to implement the method, the method comprising: (a) triggering (201) transmission to a receiving device of values ​​for an attribute containing ordered data, the values ​​of the data being all or part of the values, the transmission containing at most the value of a single selected interval of the ordered data; (b) for all N adjacent intervals of the data selection from the starting point selected in the data order until the end of the interval preceding the interval containing the current data collection period, verifying (204) whether the attribute does not contain a value to be transmitted; (c) If the verification is positive, all N intervals transmit at most (214) one message in the push mode.

2. The method of claim 1, wherein if the verification is positive, transmitting at most one message in the push mode comprises, according to the first operation mode, transmitting a single message indicating that the N intervals have no value.

3. The method according to claim 1, wherein in the case where the verification is positive, transmitting at most one message in the push mode comprises, according to the second operation mode, not sending any message (213) in the N intervals.

4. According to the method described in any one of claims 1 to 3, if the verification is negative, a message is transmitted (214) to the receiving device in push mode, wherein the message contains the value of a first non-empty interval of the value to be transmitted, and no message is transmitted for the empty interval of the value to be transmitted before the first interval.

5. The method according to claim 4, comprising, after transmitting a message with a value, receiving (215) an acknowledgement from the receiving device and receiving an information update (216), the information identifying the last confirmed value of the attribute.

6. The method of claim 5, wherein the start point of the data sequence is adjacent to the end point of the interval containing the value most recently acknowledged by the receiving device.

7. The method according to any one of claims 1 to 6, wherein the determining step is preceded by a step of filtering the attribute data according to one or more criteria to determine the value to be transmitted.

8. The method according to any one of claims 1 to 7, comprising: Verify (209) whether there are other attributes that need to be processed; If so, step (b) is performed for each additional attribute to be processed, and if all processed attributes have no values ​​to be transmitted, the verification of step (c) is considered positive.

9. The method according to any one of claims 1 to 8, comprising, according to a third operating mode, performing message transmission in push mode after triggering the transmission, regardless of the result of the verification.

10. The method according to any one of claims 1 to 9, wherein N is greater than or equal to 2.

11. The method according to any one of claims 1 to 10, wherein the data is arranged in order from the oldest data to the most recent data.

12. The method of claim 11, wherein the data includes a timestamp, the order being a function of the timestamp.

13. The method according to any one of claims 1 to 12, wherein the selection interval is one of an interval defined by a number of values ​​or an interval defined by a duration.

14. A readable storage medium, readable by a device equipped with a processor, the medium comprising instructions which, when executed by the processor of the device, direct the device to implement the method according to any one of claims 1 to 13.

15. A communication device comprising means adapted to implement the method according to any one of claims 1 to 13.

Images