Jump to content

Handoff Native to Roaming?


owensri2

Recommended Posts

An interesting thing happened while I was leaving work today and heading home. I just recently moved to Charlotte, NC (Matthews, suburb). I started a call on the Sprint network in Hartsville, SC, and figured that it would drop once I drove out of Sprint native coverage and the call continued. I decided to look at the display, and it showed that I was roaming! I didn't know that it was possible.

 

The roaming area I drove into is US Cellular. Any ideas? This is the first time that I didn't drop a call while going from Native coverage to Roaming. :lol:

Link to comment
Share on other sites

Are u positive you started the call in sprint coverage and were not roaming when rhe call started? Ive seen my galaxies roam and hang on to the roaming network even once they are back in native.

Link to comment
Share on other sites

Are u positive you started the call in sprint coverage and were not roaming when rhe call started? Ive seen my galaxies roam and hang on to the roaming network even once they are back in native.

 

I am 100% positive. I looked at the signal, and I was near the Sprint tower in Hartsville when I initiated the call.

Link to comment
Share on other sites

I can't say I've ever had that happen, however, my roaming in MI is Verizon 850, so the switch from Sprint 1900 is most likely a hard handoff. Perhaps it is a soft handoff due to US Cellular using 1900 spectrum in your area?

 

We need AJ to chime in here :)

Link to comment
Share on other sites

In my area, the only PCS roaming is Cricket and Commnet. I cannot ever handoff to Sprint or vice versa on these. If I start a conversation on any of these two, I will stay connected to that network, even if I drive into Sprint coverage.

 

It's extremely problematic on Commnet, as they have poor coverage inside Sprint coverage areas. They tend to place sites outside of Verizon/Sprint coverage to sell roaming to them. So I will get dropped when the roaming signal finally runs out, and then I have to wait for my device to scan and connect to Sprint native or another roaming carrier to call back and continue.

 

Also, in my area, we have old Alltel and Verizon roaming on 850 Cellular. These never hand off to anything.

 

When making an outgoing call when roaming, I have to check which carrier I'm on first. Then I have to decide if that carrier has continuous coverage along my route, knowing it will not handoff to another roaming carrier or to Sprint. In many instances while roaming, I will cycle airplane mode to get a better carrier. Because Commnet is really bad for me as none of their sites overlap. So I cannot keep a phone call from one site to the next. I try to get Verizon as much as possible so I can keep the conversation as long as I need to.

 

When I get an incoming call while roaming, there is nothing I can do. I just warn the caller that I may lose service and that I'll call them back. I pretty much know every roaming seam in all of Northern New Mexico.

 

Robert via Nexus 7 with Tapatalk HD

Link to comment
Share on other sites

I can't say I've ever had that happen, however, my roaming in MI is Verizon 850, so the switch from Sprint 1900 is most likely a hard handoff. Perhaps it is a soft handoff due to US Cellular using 1900 spectrum in your area?

 

We need AJ to chime in here :)

 

No, soft handoff is possible only on the very same carrier channel. Plus, USCC has substantial Cellular 850 MHz footprint in the Carolinas.

 

So, if this handoff really did happen as described, it was almost certainly an inter band, inter MSC hard handoff. I would like to see it demonstrated again to show that it is repeatable. Then, we could examine how it is possible.

 

AJ

  • Like 1
Link to comment
Share on other sites

When making an outgoing call when roaming, I have to check which carrier I'm on first. Then I have to decide if that carrier has continuous coverage along my route, knowing it will not handoff to another roaming carrier or to Sprint. In many instances while roaming, I will cycle airplane mode to get a better carrier. Because Commnet is really bad for me as none of their sites overlap. So I cannot keep a phone call from one site to the next. I try to get Verizon as much as possible so I can keep the conversation as long as I need to.

 

Robert via Nexus 7 with Tapatalk HD

 

How can you tell what carrier you are on before cycling airplane mode to another?

Link to comment
Share on other sites

 

How can you tell what carrier you are on before cycling airplane mode to another?

 

I use NetMonitor. It's the fastest way to find out.

 

Robert via Nexus 7 with Tapatalk HD

  • Like 1
Link to comment
Share on other sites

How can you tell what carrier you are on before cycling airplane mode to another?

 

Gotta know your local SIDs, baby. And that, appropriately enough, is going to be the focus of my next engineering screen article. I am thinking of calling it "SID and NIDsy." Anybody get this music reference?

 

AJ

  • Like 3
Link to comment
Share on other sites

Gotta know your local SIDs, baby. And that, appropriately enough, is going to be the focus of my next engineering screen article. I am thinking of calling it "SID and NIDsy." Anybody get this music reference?

 

AJ

 

I'm guessing its a Sid Vicious/Sex Pistols reference?

  • Like 1
Link to comment
Share on other sites

Just reproduced the handoff again on my way home. I started the call on Sprint, and it handed off to US Cellular!

 

I'd love to see engineering screenshots before, during, after handoff, and hangup

Link to comment
Share on other sites

Just reproduced the handoff again on my way home. I started the call on Sprint, and it handed off to US Cellular!

 

The only way that is possible is if their MSCs are harmonized. And I am not aware of that elsewhere, so it seems out of place here.

 

I suppose one possibility is that -- because this area outside of Charlotte is a former affiliate market -- AirGate PCS could have contracted to use USCC's MSC as its own. But even if that were the case, I would have expected Sprint to take that in house with its affiliate acquisitions several years back.

 

AJ

  • Like 1
Link to comment
Share on other sites

When Sprint 800 Mhz CDMA is launched for us to use' date=' will the voice calls change from 800 to 1900 to 800 on the fly?[/quote']

 

Robert observed this when doing his field testing in Austin

 

Sent from my cm_tenderloin using Forum Runner

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

Happened again today.  Started on Sprint, 6 bars near the tower.  I initiated a call and it ended up on US Cellular.  I looked at the screen after I had figured the call would have dropped, and the little roaming triangle appeared as soon as the display turned on.  The SID before the call was 4376.  I checked SignalCheck during the call after it had switched to roaming and it was 1648.  Any ideas on who the SID's belong to?  I would assume 4376 is Sprint, but not sure about the 1648 (US Cellular). 

Link to comment
Share on other sites

Any ideas on who the SID's belong to?  I would assume 4376 is Sprint, but not sure about the 1648 (US Cellular). 

 

Are you sure that you did not read it incorrectly?  SID 1643 is USCC.

 

AJ

Link to comment
Share on other sites

The only way that is possible is if their MSCs are harmonized. And I am not aware of that elsewhere, so it seems out of place here.

 

I suppose one possibility is that -- because this area outside of Charlotte is a former affiliate market -- AirGate PCS could have contracted to use USCC's MSC as its own. But even if that were the case, I would have expected Sprint to take that in house with its affiliate acquisitions several years back.

 

AJ

 

Perhaps related to the Sprint/USCC customer and spectrum transaction? Just throwing it out there as a possible reason, no idea myself.

Link to comment
Share on other sites

In my area, the only PCS roaming is Cricket and Commnet. I cannot ever handoff to Sprint or vice versa on these. If I start a conversation on any of these two, I will stay connected to that network, even if I drive into Sprint coverage.

 

It's extremely problematic on Commnet, as they have poor coverage inside Sprint coverage areas. They tend to place sites outside of Verizon/Sprint coverage to sell roaming to them. So I will get dropped when the roaming signal finally runs out, and then I have to wait for my device to scan and connect to Sprint native or another roaming carrier to call back and continue.

 

Also, in my area, we have old Alltel and Verizon roaming on 850 Cellular. These never hand off to anything.

 

When making an outgoing call when roaming, I have to check which carrier I'm on first. Then I have to decide if that carrier has continuous coverage along my route, knowing it will not handoff to another roaming carrier or to Sprint. In many instances while roaming, I will cycle airplane mode to get a better carrier. Because Commnet is really bad for me as none of their sites overlap. So I cannot keep a phone call from one site to the next. I try to get Verizon as much as possible so I can keep the conversation as long as I need to.

 

When I get an incoming call while roaming, there is nothing I can do. I just warn the caller that I may lose service and that I'll call them back. I pretty much know every roaming seam in all of Northern New Mexico.

 

Robert via Nexus 7 with Tapatalk HD

Make a custom PRL that lowers priority or gets rid of the Commet towers altogether.

 

 

I might be making a quick tut on that soon.

 

 

Link to comment
Share on other sites

  • 3 months later...

Well, since about the beginning of August, I am no longer able to handoff from native to roaming.  The call drops like it did before.  Strange...

 

The mysterious handoff over the summer must have been due to sunspots, a coronal mass ejection.

 

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

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their BRS/EBS licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well.  — — — — — Edit: Turns out this is a spectrum swap where T-Mobile is basically giving them DoD spectrum in a bunch of markets in exchange for all of SoniqWave's BRS/EBS. SoniqWave will likely turn around and sell the DoD spectrum to AT&T whenever the FCC removes the 40MHz cap.
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

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