pkreddy04
commented
6 years ago There is a statement in the spec 'When reporting the Tx Data or Rx Data, the LwM2M Client reports the total KB transmitted/received over IP bearer(s), including all protocol header bytes up to and including the IP header' So, this clarifies that all IP bearers should be used for reporting.
(e.g. OMA-TS-LightweightM2M-V1_0-20160802-C): OMA-TS-LightweightM2M-V1_0_1-20170704-A(e.g. section: 6.2): E.8 LwM2M Object: Connectivity StatisticsFor resources 'Tx Data', 'Rx Data', 'Max Message Size' and 'Average Message Size'. There can be multiple network bearer's which may be active on the device side, the spec does not clarify if cumulative stats should be collected for all interfaces or just the network bearer used for the LwM2M communication(4/0/0) be used for stats collection? There is a no correlation element between network bearer and stats collections.
Intermediate suggestion is that we can add that the connectivity stats be collected on the network bearer which is used by the LwM2M for communication when the ‘start’ operation is invoked. So, that leaves the ambiguity out that if a network interface is switched after 'start' is invoked. Cumulative stats may make sense for 'Tx Data', 'Rx Data' but does not make sense 'Max Message Size' and 'Average Message Size'. Also, sometimes that user may just be interested in data for one network bearer if there are multiple bearers. Ex. WiFi and Cellular can be under different payment plans, then user may just want to know how much data is being used by Cellular for a certain period and do necessary control.
But long term another resource should be introduced in this object which explicitly tells the network bearer for which the stats are to be collected.