Jump to content

Interesting piece re 800mhz in general


BenChase7

Recommended Posts

I dont really know much about spectrum, other then the bits and pieces I gain here; however, I came across this article regarding 800mhz spectrum and, of course, Sprint came to mind. Would the discussions in this article have any positive effect on how Sprint uses their 800mhz spectrum?

 

http://www.engadget.com/2012/02/15/fcc-seeks-to-streamline-800mhz-band/

  • Like 2
Link to comment
Share on other sites

No, the elimination of site based coverage determination affects Cellular 850 MHz (sometimes referred to as 800 MHz), but not SMR 800 MHz.

 

To this point, Cellular 850 MHz licensees have had to register the cell sites and their service contours that form the Service Area Boundaries (SAB) of their Cellular Geographic Service Areas (CGSA). More or less, this is a vestige of the AMPS days.

 

For example, here is an FCC ULS map of my home CMA with the VZW Cellular A-side registered sites marked:

 

http://wireless2.fcc...s+%28VAW%29+LLC

 

(The ULS-GIS is notoriously slow to load, so give it a few moments.)

 

Additionally, here is an actual SAB and CGSA map that VZW filed with the FCC prior to a modification of its Los Angeles CMA Cellular B-side license. The image quality is not great. But, again, note the registered sites marked on the map:

 

http://people.ku.edu...52118079408.gif

 

(Oddly enough, when I ran a Google image query on "CGSA," the map image that popped up was one that I had posted to Howard Forums six years ago. How is that for unintended self reference?!)

 

Parts of the Howard Forums thread containing the map above are also a good read about SAB and CGSA determination:

 

http://www.howardfor...76&page=4&pp=15

 

Finally, here is the FCC notice of proposed rulemaking released today:

 

http://transition.fc...FCC-12-20A1.pdf

 

AJ

  • Like 2
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

    • https://www.fiercewireless.com/wireless/t-mobile-gets-little-closer-accessing-its-25-ghz-spectrum-auction-108 Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile.  This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start)  and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
    • I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.   Haha me and you both wish this!!!
    • Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value.  I saw a lot of "no service" because it apparently does it a lot.  I'll check again on the train ride home later. Assuming I'm correct, is it possible to have some kind of middle ground on this?  I think it was showing other legitimate values, like the TA, even when it was showing -44/-3.  I'd prefer it show the data it has but at -140 dBm in those cases.  I recognize this could be a pain to implement, and if it is, then no worries, mostly curious. EDIT:  But now I'm sitting here thinking "what if the PCI is bad and I don't know it?"  But that can just as easily be the case on other phones that aren't caught.  I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option.  Bleh, I wish this stuff just worked properly! - Trip
    • Forgot to follow up on this. The service was once again abysmal .
  • Recently Browsing

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