I was rather hoping so!
Here goes with the parts I understand...
Part 1: Getting counters from modem to DSLAMThe VDSL2 specification includes a lot of stuff on "operation and management", which both controls the setup of the connection and extracts information from it. (Section 11 of the VDSL2 specification).
Part of the protocol overhead of VDSL2 is to allow the two sides to send messages back and forth as part of this protocol: there are time -critical "indicator bits" and a non-time-critical "EOC channel" (embedded operations channel). I've attached a picture that shows the model
- VTU-O is the modem in the DSLAM
- VTU-R is the modem in the subscriber endpoint
One of the commands that can be sent on the EOC channel is one to query the management counters at the far end; the response includes the current counters for
- FEC
- CRC
- FEC errored seconds (a counter we never see normally!)
- Errored seconds
- Severely errored seconds
- LOS errored seconds
- Unavailable errored seconds
So the DSLAM can query your modem's counters at any time, as can your modem. Undoubtedly your modem does this in order to collect the upstream statistics that it keeps in 15 minute and 24 hour buckets.
Part 2: Getting counters out of DSLAMYou'll note, from that model, there is mention of "MIBs" and a "Q-interface". This is the mechanism by which a centralised "DLM process" can extract data for each line from the DSLAM. The Q-interface is achieved using SNMP, and the MIB's are standard SNMP data structures that hold a variety of data. In this case, one of the MIBs will be designed to hold the counters.
DLM just needs to use an SNMP query at regular intervals (presumable every 15 minutes) to extract the data.