Protocol scope and method
The tool splits TLVs and names a small set of common IDs. Vendor extensions remain visible as raw hex.
record = id(1) + length(1) + value(length).
Diagnostic scenario
Take only the optional bytes after the fixed 0x0200 base body. Walk each ID-length-value record, compare the declared length with remaining bytes and retain unknown IDs as raw hex for later lookup in the selected edition or vendor profile.
How to interpret the result
Successful splitting establishes record boundaries, not the semantic type of every value. Common IDs may have fixed widths, while vendor records can reuse or extend the namespace. Stop at the first truncated record rather than shifting the remaining stream.
Input reference
- Extra information hex
- Example default: Sample input included
Common mistakes
- Using an unredacted production capture with vehicle, credential or network identifiers.
- Continuing after a declared length exceeds the remaining bytes.
- Treating a successfully parsed sample as standards compliance or interoperability proof.
Before using the result
- Confirm the protocol edition, transport framing and vendor profile before interpreting fields.
- Confirm known ID widths and preserve unknown values unchanged.
- Keep a redacted known-good and known-bad sample as a regression pair.
Questions to check during diagnosis
Does the JT/T 808 Extra Information TLV Decoder leave my browser?
No application upload is used. Avoid putting sensitive production data in shareable URLs.
Is this a standards compliance test?
No. Confirm the edition and vendor profile with licensed documents and your target platform.
Offline diagnostic aid. Verify fields, version and vendor extensions before production use.