![]() |
![]() |
![]() |
![]() |
![]() |
Last edited by i0wnj00; 05-19-2015 at 01:33 PM. Reason: Updated to show Band 12 in San Yisdro.
Band 12 is active in Lansing, MI! I could tell because my MetroPCS phone only has B12 not B17.
I could tell it was AT&T because BW was 10 Mhz whereas Tmo has 5. I roamed onto it inside a building where Tmo doesn't have B12 (they do in surrounding buildings, rollout is underway here). SignalCheckPro has not updated their app for AT&T MBFI yet since it shows B17 in it.
![]()
Band 12 through AT&T MFBI is active up here in Mendocino County in NW CA as well. So, we have Band 12 from three carriers in our area, T-Mobile, U.S. Cellular and AT&T.
Sent from my Nexus 6 using Tapatalk
http://www.nwprailroad.com
http://www.northcoastrailroad.org
Http://www.nwprr.net
http://www.sonomamarintrain.org
http://www.cahighspeedrail.ca.gov
http://www.xpresswest.com/
http://www.skunktrain.com
http://www.freightrailworks.org
http://www.amtrakcalifornia.com
http://www.amtrak.com
http://www.bnsf.com
http://www.up.com
http://www.metrolinktrains.com
http://www.isu.edu (Idaho State University)
Is MFBI pretty much universal across AT&T's Band 17 LTE network by now? Are Band 12 devices now compatible nationwide with AT&T's Band 17 LTE network or is MFBI still an isolated exception?
My ears must have been tingling, some news has just come out:
http://www.wirelessweek.com/news/201...4&location=top
AT&T said that the feature has been fully deployed on its macro-cell network.
Correction, AT&T does not have license for Band 12. They are not legally broadcasting Band 12 (A,B,C), only through MFBI (B,C, blocks). It is like renaming their band 17 as band 12. Devices that only supports band 12 can see band 17 in AT&T but it is still Band 17. The only reason AT&T agrees to interoperate the signal is to have roaming agreement, which FCC forces at&t to do so. Now AT&T selling Band 12 devices only because it can see band 17 perfectly and can roam to other networks as well. But AT&T only has license spectrum to broadcast Band 17.
This is very precise it is like your wireless router if you rename the router your phone will no longer be connected. So means MFBI has to broadcast 12/17 together so devices can connect at the same time. Even though Band 17 covers B,C blocks if the network not broadcasting Band 17 MFBI it will not connect.
Here are some of the AT&T UARFCN's broadcast in most areas:
2200 = 10MHz Band 4
2175 = 5MHz Band 4
675 = 15MHz Band 2
800 = 10Mhz Band 2
9890 = 10MHz Band 30
5780= 10MHz Band 17
5760 = 5MHz Band 17 lower B block
5815 = 5MHz Band 17 lower C block 700MHz
5110 = 10MHz Band 12 ( 5110(12) and 5780(17) broadcast on exact same frequencies this is MFBI 5110 for B12 Lower B Block) I dont know about lower C block on B17 if they have MFBI active
T-mobile Band 12 broadcast in 5010 block A and 5035 block B/C i believe.
Figuring UARFCN what band it's on go visit www.cellmapper.net/arfcn
I dont think so look at my UARFCN's lists Band 17 has 5760, 5780, 5815 they are in different frequencies but the same band name some tower broadcast 5760 and some 5780 but i am sure they also have MFBI in those towers.
2200 = 10MHz Band 4
2175 = 5MHz Band 4
675 = 15MHz Band 2
800 = 10Mhz Band 2
9890 = 10MHz Band 30
5780= 10MHz Band 17
5760 = 5MHz Band 17 lower B block
5815 = 5MHz Band 17 lower C block 700MHz
5110 = 10MHz Band 12 ( 5110(12) and 5780(17) broadcast on exact same frequencies this is MFBI 5110 for B12 Lower B Block) I dont know about lower C block on B17 if they have MFBI active
T-mobile Band 12 broadcast in 5010 block A and 5035 block B/C i believe.
Figuring UARFCN what band it's on go visit www.cellmapper.net/arfcn
That should get interesting here, we have AT&T broadcasting Band 17, and both U.S. Cellular and T-Mobile broadcasting Band 12.
Bookmarks