Troubleshooting DOCSIS 3 1 Karl Oberlin Systems Engineer
Troubleshooting DOCSIS 3. 1 Karl Oberlin Systems Engineer November 23, 2020
CONFIDENTIALITY • The information in this presentation is confidential and proprietary to Trilithic and may not be disclosed without the permission of Trilithic has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and Trilithic's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by Trilithic at any time for any reason without notice. The information on this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. Trilithic assumes no responsibility for errors or omissions in this document, except if such damages were caused by Trilithic intentionally or grossly negligent • All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions
1. What is DOCSIS 3. 1 and how is it different from DOCSIS 3. 0 2. Recognizing impairments 3. Troubleshooting techniques
DOCSIS 3. 1 • DOCSIS 3. 1 uses OFDM – Orthogonal Frequency Division Multiplexing – Using subcarriers that are offset by 90 degrees – 4 k mode allows for 4096 carriers when spaced 50 k. Hz – Modulation can vary
DOCSIS 3. 1 • D 3. 1 signal is made up of Pilots, PLC channel and many sub carriers • Channel width can vary from 24 MHz to 192 MHz • PLC channel is used to lock modem and provide config info • Data stream is divided up to use all carriers if needed
DOCSIS 3. 1 • PLC channel does not have to be at center frequency • PLC contains 8 BPSK pilots used to lock modem • Modem info is contained inside 400 k. Hz PLC data channel at the center of the PLC
DOCSIS 3. 1 • PLC frequency • P/V on PLC channel • Tilt • Power levels are measured in 6 MHz segments • Channel scans group segments
DOCSIS 3. 1 • Ability to make multiple MER measurements across entire channel • MER’s can be plotted as function of frequency for given channel
DOCSIS 3. 1 • PLC constellation • Plotting BPSK pilots
DOCSIS 3. 1 • Displaying profiles • Showing exclusion zones, pilots, sub carriers, modulation and PLC
Impairments Suck outs
Impairments
Impairments Tilt
Impairments Reflections
Impairments
Impairments Noise
Impairments Noise
Impairments Lower level profiles
Troubleshooting • Troubleshooting challenges • Lack of training • Lack of effective tools • Time consuming processes • Cost of equipment and repairs
Troubleshooting • Keys to effective troubleshooting – Modern tools • Meters • Monitoring tools for both forward and return plant – Proper training • At all levels – Effective program for identifying issues • Consistent methods to identify problems
Troubleshooting
Troubleshooting Forward and return spectrums present new issues with limited abilities to sweep
Troubleshooting Reference sweep on forward and CM sweep on return are non-invasive
Troubleshooting Return monitoring and ingress alarm reporting
Troubleshooting Utilizing tools that minimize impact to customers
Troubleshooting Using proactive network maintenance tools becomes critical
Troubleshooting
Conclusion Thank you for your time
- Slides: 29