Bearer 0 vs 1 - G.INP Stats

Hi guys,

Please can someone explain what the difference between 'Bearer 0' and 'Bearer 1' is in the G.INP section of the line stats? I'll post you an example of my stats here, where it's shown.

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 6853 Kbps, Downstream rate = 54180 Kbps
Bearer: 0, Upstream rate = 7517 Kbps, Downstream rate = 51893 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 3.7 5.6
Attn(dB): 26.8 0.0
Pwr(dBm): 12.1 6.5

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 223
M: 1 1
T: 0 42
R: 10 0
S: 0.1397 0.9466
L: 13625 1893
D: 4 1
I: 238 112
N: 238 224
Q: 4 0
V: 0 0
RxQueue: 125 0
TxQueue: 25 0
G.INP Framing: 18 0
G.INP lookback: 25 0
RRC bits: 0 24
Bearer 1
MSGc: 122 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 8.0000 0.0000
L: 32 0
D: 1 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0

Counters
Bearer 0
OHF: 0 671297
OHFErr: 4 9
RS: 190121832 28185059
RSCorr: 2214698 0
RSUnCorr: 0 0
Bearer 1
OHF: 415190 0
OHFErr: 0 0
RS: 3321027 0
RSCorr: 644 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 1206290 0
rtx_c: 1142892 0
rtx_uc: 13 0

G.INP Counters
LEFTRS: 603 0
minEFTR: 50919 0
errFreeBits: 5143405 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 648634319 0
Data Cells: 5955687 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 3 9
SES: 0 0
UAS: 198 198
AS: 6671

Bearer 0
INP: 55.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 9.97
OR: 0.01 25.65
AgR: 52006.93 7542.53

Bearer 1
INP: 2.00 0.00
INPRein: 2.00 0.00
delay: 0 0
PER: 16.06 0.01
OR: 63.75 0.01
AgR: 63.75 0.01

Bitswap: 1131/1475 39/40

Total time = 1 hours 54 min 29 sec
FEC: 2214698 0
CRC: 4 9
ES: 3 9
SES: 0 0
UAS: 198 198
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 9 min 29 sec
FEC: 215621 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 368732 0
CRC: 4 1
ES: 3 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 1 hours 54 min 29 sec
FEC: 2214698 0
CRC: 4 9
ES: 3 9
SES: 0 0
UAS: 198 198
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 1 hours 51 min 11 sec
FEC: 2214698 0
CRC: 4 9
ES: 3 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
>

Thanks,

William

Edited by WilliamGrimsley (Mon 16-Jul-18 10:31:03)

RobertoS possibly can as he posted about it here

Edited by ian72 (Mon 16-Jul-18 11:34:45)

Thanks, Ian. But, does anyone know what Bearer 0 actually does?

I think you'll find bearer 0 carries your data backwards and forwards - it is the transport layer for your connection.

EDIT : To expand. Bearer 0 carries the data for the connection. Bearer 1 only exists where retransmission is turned on (eg with G.INP). When retransmission is on bearer 1 looks to be used to carry the management messages for the link leaving bearer 0 to carry the data. Because bearer 1 is only carrying management messages it is relatively low bandwidth (usually showing as 0 because it is rounded down).

Edited by ian72 (Mon 16-Jul-18 14:13:18)

Ah, so that is why there's less FECs on bearer 1. Thanks for the explanation.

Edited by WilliamGrimsley (Wed 18-Jul-18 10:53:12)