Jump to content

FCC Announces Two Spectrum-Sharing Agreements With Mexico


irev210

Recommended Posts

Public release by fcc:

http://transition.fc...OC-314532A1.txt

 

 

Washington D.C. – Today, FCC Chairman Julius Genachowski participated in high-level discussions

with U.S. and Mexican telecommunications officials at the State Department where the United States

signed two Protocols with Mexico for sharing spectrum in the 800 MHz and 1.9 GHz bands along the

U.S.-Mexican border. The signing of these documents marks the beginning of the final phase for

rebanding in the 800 MHz band across the country. These actions will help support commercial

broadband services and public safety mission-critical voice communications along the U.S.-Mexico

border and throughout the United States.

 

“These agreements with Mexico will unleash investment and benefit consumers near the borders by

enabling the rollout of advanced wireless broadband service and advanced systems for critical public

safety and emergency response communications,” Chairman Julius Genachowski stated. “I appreciate

the commitment and dedication of agency staff and those at the State Department who made these

important agreements possible.”

 

The United States and Mexico also signed a high-level expression of support, or “Joint Statement,” for

continued coordination of spectrum along the border and cooperation on telecommunications policy issues as

well as an ambitious work plan, or “Directory of Bilateral Issues,” for 2012-2014.

Specifically, the new 800 MHz Protocol: (1) allots band segments between the United States and

Mexico, (2) specifies the technical parameters for operation on these band segments within 110

kilometers (68 miles) of the common border, and (3) creates a bi-national Task Force to support the

transition of incumbent operators along the border to the new allotment plan.

 

The Protocol for 800 MHz replaces a previous agreement and paves the way for completion of 800

MHz rebanding by U.S. public safety and commercial licensees operating along the U.S.-Mexico

border. The FCC ordered rebanding to alleviate interference to public safety licensees in the band

caused by commercial cellular licensees.

 

The new Protocol for the 1.9 GHz band allows Sprint Nextel Corporation to deploy CDMA service

along the border with Mexico. Sprint obtained access to the 1.9 GHz band in 2004 as compensation for

vacating its spectrum holding in the lower segment of the 800 MHz band in accordance with the

rebanding project.

 

 

cliff notes:

Allows for sprint to deploy "G" block along the border

800MHz is in "final" phase of rebanding

Edited by S4GRU
Put FCC Press Release in quotation bubble for readability.
  • Like 1
Link to comment
Share on other sites

Depending upon the specifics of the agreement, this new spectrum sharing protocol with Mexico could allow Sprint to deploy the full complement of 5 MHz x 5 MHz LTE in near border markets, specifically San Diego, where Sprint is currently limited at best to 3 MHz x 3 MHz LTE.

 

AJ

  • Like 1
Link to comment
Share on other sites

Depending upon the specifics of the agreement, this new spectrum sharing protocol with Mexico could allow Sprint to deploy the full complement of 5 MHz x 5 MHz LTE in near border markets, specifically San Diego, where Sprint is currently limited at best to 3 MHz x 3 MHz LTE.

 

AJ

 

That's immediately where my mind went to. I would like to know more details about if Sprint would get to access more of its spectrum along the border. This release is short on that info. :(

 

Robert

Link to comment
Share on other sites

WiWavelength, is that in the G Block or in ESMR that they would otherwise be limited to 3x3?

 

Only ESMR. Sprint will be able to deploy a single CDMA1X 800 carrier everywhere, including the international border coordination zones. However, under current guidelines, Sprint may be able to deploy only a 3 MHz x 3 MHz LTE carrier in the Mexican border zone and no LTE at all in certain areas (e.g. Seattle) of the Canadian border zone. The reason for this is that 800 MHz public safety rebanding is a US endeavor, not necessarily conducted in parallel by Canada and Mexico. In short, within a specified distance of the international boundary, Sprint cannot operate broadband LTE across the same frequencies that Canadian or Mexican carriers/agencies operate iDEN or other narrowband airlinks. Otherwise, Sprint LTE could interfere with those narrowband operations.

 

I have no idea what Mexico is doing (if anything at all) with its equivalent to the PCS G block. In the US, the PCS G used to be part of BAS (Broadcast Auxiliary Service), which provides microwave link style spectrum for TV broadcasters' remote pick ups. Sprint had to foot the bill for relocating BAS from ~2000 MHz up to ~2100 MHz as one of its conditions of being granted the PCS G block nationwide.

 

AJ

Link to comment
Share on other sites

That's immediately where my mind went to. I would like to know more details about if Sprint would get to access more of its spectrum along the border. This release is short on that info. :(

 

Robert

 

Press release points us here:

http://transition.fcc.gov/ib/sand/agree/

 

Hopefully they will post the agreement soon.

Link to comment
Share on other sites

Only ESMR. Sprint will be able to deploy a single CDMA1X 800 carrier everywhere, including the international border coordination zones. However, under current guidelines, Sprint may be able to deploy only a 3 MHz x 3 MHz LTE carrier in the Mexican border zone and no LTE at all in certain areas (e.g. Seattle) of the Canadian border zone. The reason for this is that 800 MHz public safety rebanding is a US endeavor, not necessarily conducted in parallel by Canada and Mexico. In short, within a specified distance of the international boundary, Sprint cannot operate broadband LTE across the same frequencies that Canadian or Mexican carriers/agencies operate iDEN or other narrowband airlinks. Otherwise, Sprint LTE could interfere with those narrowband operations.

 

I have no idea what Mexico is doing (if anything at all) with its equivalent to the PCS G block. In the US, the PCS G used to be part of BAS (Broadcast Auxiliary Service), which provides microwave link style spectrum for TV broadcasters' remote pick ups. Sprint had to foot the bill for relocating BAS from ~2000 MHz up to ~2100 MHz as one of its conditions of being granted the PCS G block nationwide.

 

AJ

 

Let me rephrase: can Sprint use a G-block 5x5 carrier nationwide, even near border areas (sounds like that's a question mark at this point)? If not, does this agreement change that? I'm aware of the ESMR issues.

Link to comment
Share on other sites

Let me rephrase: can Sprint use a G-block 5x5 carrier nationwide, even near border areas (sounds like that's a question mark at this point)?

 

For Sprint, the 3 MHz x 3 MHz LTE carrier possibility is relevant only to SMR 800 MHz (bands 18/26), not to PCS 1900 MHz (G block; band 25). Ask Robert to confirm, but I know of no Network Vision sites anywhere that are precluded from LTE 1900 in the G block.

 

AJ

Link to comment
Share on other sites

For Sprint, the 3 MHz x 3 MHz LTE carrier possibility is relevant only to SMR 800 MHz (bands 18/26), not to PCS 1900 MHz (G block; band 25). Ask Robert to confirm, but I know of no Network Vision sites anywhere that are precluded from LTE 1900 in the G block.

 

AJ

 

I do not know of any. I would assume there is no such preclusion. And I think my assumption is solid. For instance, I have seen several Sprint documents and maps relating to limitations to LTE 800 deployment because of spectrum/border area limitations, etc. But I have not once seen any mitigation plans or maps relating to issues deploying LTE 1900 in border areas.

 

Robert

Link to comment
Share on other sites

Depending upon the specifics of the agreement, this new spectrum sharing protocol with Mexico could allow Sprint to deploy the full complement of 5 MHz x 5 MHz LTE in near border markets, specifically San Diego, where Sprint is currently limited at best to 3 MHz x 3 MHz LTE.

 

AJ

 

I hope this is true. I would love to see 5 MHz x 5 MHz LTE in San Diego. Now all that needs to happen is for the FCC to sign the same sharing agreement with Canada so that those cities near the Canadian border can get in on this action.

  • Like 1
Link to comment
Share on other sites

I hope this is true. I would love to see 5 MHz x 5 MHz LTE in San Diego. Now all that needs to happen is for the FCC to sign the same sharing agreement with Canada so that those cities near the Canadian border can get in on this action.

 

People live on the canadian border?

 

I kid, I kid...

  • Like 1
Link to comment
Share on other sites

People live on the canadian border?

 

I kid, I kid...

 

Yes I am worried about cities like Detroit, Cleveland, Buffalo, Seattle, etc that won't be able to get 800 MHz LTE. Seattle might just be limited to 3x3 MHz LTE but who knows.

Link to comment
Share on other sites

People live on the canadian border?

 

Someone who lives in St. Cloud, MN making fun of people who live near the Canadian border is like someone with an IQ of 80 calling a person with an IQ of 75 a "dummy."

 

:P

 

AJ

  • Like 2
Link to comment
Share on other sites

Public release by fcc:

http://transition.fc...OC-314532A1.txt

 

 

 

 

 

cliff notes:

Allows for sprint to deploy "G" block along the border

800MHz is in "final" phase of rebanding

 

great news for San Diego, I can look out from the hills and see Mexico where I am standing at the moment

Link to comment
Share on other sites

Hey, I'm at least a 3 or 4 hour drive from the border. :D

 

Sent from my Galaxy Nexus using Tapatalk 2

 

I think this is where we need one of our 49th staters to chime in and tell us how they can see Russia from their house :D

Link to comment
Share on other sites

Yes I am worried about cities like Detroit, Cleveland, Buffalo, Seattle, etc that won't be able to get 800 MHz LTE. Seattle might just be limited to 3x3 MHz LTE but who knows.

 

Isn't Cleveland across lake Erie from Canada? And Seattle is a LONG way from the border. How far from the border do they have to worry about interference? Anyone know?

Link to comment
Share on other sites

Isn't Cleveland across lake Erie from Canada?

 

Lake Erie is part of the issue -- no obstructions, signals can propagate a long way. Plus, the spectrum sharing zone extends from the international boundary, which is in the middle of the lake, not at the shore. So, Cleveland is really only ~20 miles from the border.

 

Interesting aside, US cellphone users along the south shore of Lake Erie have been known to pick up unintended international roaming charges from Rogers or Bell sites on the north shore.

 

And Seattle is a LONG way from the border.

 

Not as far as you think. You are forgetting Vancouver Island. And, again, the international boundary is in the middle of the Strait of Juan de Fuca, not at the shore.

 

AJ

Link to comment
Share on other sites

Lake Erie is part of the issue -- no obstructions, signals can propagate a long way. Plus, the spectrum sharing zone extends from the international boundary, which is in the middle of the lake, not at the shore. So, Cleveland is really only ~20 miles from the border.

 

Interesting aside, US cellphone users along the south shore of Lake Erie have been known to pick up unintended international roaming charges from Rogers or Bell sites on the north shore.

 

 

 

Not as far as you think. You are forgetting Vancouver Island. And, again, the international boundary is in the middle of the Strait of Juan de Fuca, not at the shore.

 

AJ

 

Hmm, well I guess I stand corrected. I thought with careful planning and downtilt, cities like Cleveland would be fine.

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

  • Similar Content

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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