👉 DOCSIS 3.1 understanding capacity

Поділитися
Вставка
  • Опубліковано 30 вер 2024
  • Embark on an enlightening journey with our latest episode of Get Your Tech On! Hosted by Brady Volpe, Founder of VolpeFirm and Chief Product Officer at OpenVault, and featuring John Downey, DOCSIS Industry Technical Expert, this livestream is a treasure trove for cable and telecom enthusiasts.
    In this captivating episode, we unravel the complexities of DOCSIS 3.1 capacity issues and explore the best strategies to comprehend and maximize them:
    Topic Highlights:
    Estimating OFDM Capacity in DOCSIS 3.1 / 4.0: Discover the intricacies of estimating data capacity on an OFDM channel in DOCSIS 3.1 networks. While the question may be simple, the answer certainly isn't! We break down the background, offer practical calculations, and even share a Python script for your convenience.
    Whether you're a seasoned network professional, a tech wizard, or someone keen on staying updated with the latest in DOCSIS, this episode is your gateway to valuable insights and practical wisdom. Don't miss out-hit the like button, subscribe, and ring the bell for future content notifications! 🚀🔔
    #DOCSIS31 #CableNetworks #Telecommunications #TechTalk #OFDM
    👉 For a Python-based OFDM estimator, check out my Github page:
    github.com/Bra...
    👉 Link to Karthik's SCTE Expo paper on Accurately Estimating D3.1 Channel Capacity:
    www.nctatechni...
    ---
    volpefirm.com/...
    Links / Upcoming events: volpefirm.com/...
    DOCSIS Gear: all-things-doc...

КОМЕНТАРІ • 10

  • @Todd.T
    @Todd.T 27 днів тому +2

    Upgrading to 2 ghz passives and going ESD with 204mhz/1.2ghz and two OFDM/OFDMA Then moving to 1.8ghz...supposedly. RPhy with a mix of N+0 to N+5. Analog nodes with a mix of N+0 to N+5. We can speed test to the subsciber to see how/if they are impacted. You can see how many modems are on each return and when the OFDMA becomes compromised you can see the modems move. We can see packet loss, utilization, profiles usage which is stored for 14 days. If a tech swaps a modem and changes the cabling I can look at how the old modem reacted and how the new modem is reacting.

    • @Volpefirm
      @Volpefirm  27 днів тому +1

      That's great! What monitoring system?

    • @Todd.T
      @Todd.T 27 днів тому +1

      @@Volpefirm NXT and our in house software. Techs that dig deep use NXT. Techs that don’t, use the in house software. Both draw off the same database but the in house is what is used for immediate diagnosis and NXT is used for historical diagnosis. I can force NXT to refresh for the node or I can live monitor someone while I sweep. I pick the worst customers with the identical issues and live monitor. At some point you will disconnect something and the SNR will increase or the CER drops. On intermittent issues with a large node, I pick a modem after each active and let NXT monitor them for a few days. Then I call up the data with an overlay of all the modems. Then you see which segment you should play with because that modem after one of the amps is impacted the most.
      I’d be dangerous if I read the manual.

  • @svdleer
    @svdleer 6 місяців тому +2

    Reactive maintenance is indeed where everyone is at his best. We calculate the effective capacity of our fibernodes based on IUC efficiency of the OFDMA modems in that fibernode, next to the regular SC-QAM calculations (we run 2x OFDMA (lowsplit / highsplit), 32 QAM SC-QAM 256QAM, 128Mhz 4K QAM OFDM, 4US @ 64QAM) this is the migration path to 204Mhz with 2x OFDMA (and later even more) We have enough challenges, but we will get there :)

    • @Volpefirm
      @Volpefirm  6 місяців тому +2

      Thanks for the details!

  • @usernameredacted4731
    @usernameredacted4731 6 місяців тому +2

    The number of -unrealized- million dollar ideas thrown around on this channel is unreal. I'd steal & patent them but fortunately for you, I work in the cable industy and became a proud thousandair many years ago 🤷‍♂️

    • @Volpefirm
      @Volpefirm  6 місяців тому +2

      And that's why we give away all of our patentable top secret ideas. So everyone can become thousandairs in our industry. 🤣

  • @sragga
    @sragga 6 місяців тому +3

    reactive maintenance is the thing that pissed me off the most when i worked in the city. when there were periods that there where no big fires, and i would get on to some proactive maintenance, i was accused of not doing anything by my tech manager. i would be out fixing rf issues before we got calls, leakage patrols, and doing rf by street to find taps and drops full of water. we were so use to constant sdmh issues all over that they couldn't comprehend me going out and fixing issues proactively. i actually got demoted back to service as there was no paper trail for pwm, and was accused of not doing anything. i only lasted for about 2 months as things started to go to hell, and the manager had to come up with an excuse to get me back on maintenance, and save face after finding out what pwm does. i transferred out of that shit show to where i am now at the first opportunity i got.

    • @Volpefirm
      @Volpefirm  6 місяців тому +1

      Thanks for your efforts. It is hard to change companies culturally hopefully it will come sooner than later.

    • @Todd.T
      @Todd.T 27 днів тому

      35% PNM 65% reactive.when it's busy. Probably the reverse when it's not busy. Network redesign, power supply load balancing, non responder power supplies, damaged facilities, cellular ingress impacting SNR, cable egress impacting cellular, need to be done when it isn't busy. With a proper software tool, I can look up impairments the customer isn't impacted from...yet.