Jump to content

Another Günther AMA on reddit tomorrow (12-15-16)


halcyoncmdr
 Share

Recommended Posts

In case you all have missed it. Günther Ottendorfer is doing another AMA on reddit tomorrow 12/15 between 11am-12pm Pacific. I've copied below the /r/Sprint announcement from about a week ago for those that haven't seen it:

 

Günther was named Technical Chief Operating Officer at Sprint in August 2015. In this role, he is responsible for overseeing the company’s network, technology and IT organizations, including related strategy, network operations and performance, as well as partnerships with network, technology and IT vendors.

As his bio states, Günther has a substantial amount of industry experience having started his international career in the telecommunication sector over 20 years ago. In 1996 he became a founding member of mobile operator, max.mobil, in Austria. He then served as Chief Operating Officer (COO) and Chief Technology Officer (CTO) for T-Mobile Austria, as CTO for T-Mobile Germany and as European Technology Director at Group level for T-Mobile International. In 2011, Günther became Managing Director, Networks at Optus Singtel, Australia’s second largest telecommunications provider. He also led the nationwide introduction of LTE and TD-LTE which Optus pioneered as one of the first providers globally. In 2013, he joined Telekom Austria Group as Group CTIO, and drove major wireless expansion, convergence and network function virtualization projects across the countries of the group.

Günther looks forward to answering more of your questions on Sprint's pioneering efforts, network performance, LTE Plus network, network technology and roadmap, LTE Advanced, 5G, Network Function Virtualization (NFV), spectrum, and its Densification & Optimization strategy.

Please join us in giving Günther another warm welcome to /r/Sprint!

 

Link to comment
Share on other sites

No time lines on anything really.

Mostly things we already knew. He did mention Sprint is currently testing Band 25 Carrier Aggregation in a few cities. That's pretty awesome.

 

But ultimately I would have loved if someone had asked him if they were still on track in using BRS/EBS for download and PCS for upload (pretty much a new LTE band).

  • Like 1
Link to comment
Share on other sites

Finally had a chance to review all the questions and answers.... at this point I don't think we will get VoLTE until2018/2019, it all depends how much they can densify and optimize next year

 

Also I wish someone asked him about the sattelite LTE backhaul

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Let me take a look tonight. 
    • Actually, I notice it says whole clusters were skipped because of invalid TAC values.  It says "File exported for inspection."  I do have Log Sites with Missing TAC checked. Robert
    • I was able to figure this out by looking at your diagnostic reports -- you're seeing n7 because your Galaxy A32 is reporting it natively as n7.. Samsung will have to fix that on their end unfortunately. Do the engineering screens report it correctly? I have an A32 test device but I have not seen it connect to n41 (or "n7") yet. If I do, I'll try to troubleshoot and nag Samsung. EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.
    • I appreciate the feedback today -- another new is SCP beta rolling out right now! It should resolve the force closes that started with yesterday's beta release; I also made additional improvements that hopefully(?) will reduce ongoing issues with overall app stability.
    • I'm noticing a spike in instability while driving around testing the app today also.. more freeze-ups than crashes, but it's probably all related. Hopefully any crash reports that are collected can shed some light on it for me. I'll be looking into it later tonight.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...