Jump to content

Band 38 and MFBI


Recommended Posts

Hi all,

 

I know AJ responded to this question about a year and a half ago, but I wanted to see if anything had changed, especially considering the SoftBank acquisition, etc, etc. 

 

Since I know Softbank places a premium on international roaming ability and seems to be more open to more device support, I was wondering if people thought there might have been changes in terms of Sprint being willing to support Band 38 devices and enabling MFBI. What do you all think? There seem to be a good number of band 38 devices out there that aren't band 41 compatible, and at least some level of data roaming might be beneficial if it could be offered in the US.

 

Thanks for your thoughts,

 

Tommy

Link to comment
Share on other sites

Good question, Thomas. I've wondered about this myself. Generating incoming roaming revenue could only be beneficial to the bottom line. For that matter, perhaps they should also enable Band 2 LTE via MFBI when they inevitably begin to re-farm their PCS spectrum for LTE.

Link to comment
Share on other sites

No, enabling band 38 MFBI would be largely ineffectual.

 

Compared to band 41, which is 2496-2690 MHz, band 38 is only 2570-2620 MHz.  Even then, only 2572-2614 MHz in the BRS/EBS bandplan is available to Sprint.  So, subtract 8 MHz.  Moreover, take away any BRS/EBS licenses in that 42 MHz range that Sprint does not hold in a given market.

 

At best, two band 41 carriers could be also band 38 MFBI compatible.  More likely, though, only one or zero band 41 carriers would fall entirely within that range.  Not a good solution.

 

Instead, the right solution is for other network operators and device OEMs to start supporting band 38 as a subset of band 41 capability, too.  That would be easy peasy.  If they do not, then they are just being AT&T like stubborn or stupid.

 

AJ

  • Like 4
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.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

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