Jump to content

Shentel issue with load balancing?


prophead

Recommended Posts

Been reading over Shentel's Q4 2014 results and came across this quote from Earle MacKenzie...

 

We have 800 megahertz voice service on 94% of our cell sites, only 15% of the voice traffic is on 800 megahertz as we continue to have software issues on certain phones that prevent us from activating cross band loading balancing on our network. Our vendors are working to address this issue.

 

Curious if anyone here has any technical information as to what these issues might be.

Link to comment
Share on other sites

Been reading over Shentel's Q4 2014 results and came across this quote from Earle MacKenzie...

 

We have 800 megahertz voice service on 94% of our cell sites, only 15% of the voice traffic is on 800 megahertz as we continue to have software issues on certain phones that prevent us from activating cross band loading balancing on our network. Our vendors are working to address this issue.

 

Curious if anyone here has any technical information as to what these issues might be.

I do not have the answer to your question, but I am in Shentel Territory almost all the time.  I have a Galaxy S-5.  It has always tended to hang onto 800, both 1X and LTE most of the time even when it might not have been needed.  It would go over to 1900 at times, but it was sort of rare.   But in the last month, I seem to be finding myself to be on 1900 quite often. I believe that a change has been made, but it is only a good guess.  I still go onto 800 when it is appropriate, but it seems that something is determining that I would be ok on 1900 and places me on 1900 sometimes. 

I find that I might be on 1900 LTE and when I drop to a level around -113, it is very likely that I am going to be switched to 800 LTE.

I have not been able to determine what causes me to be switched back to 1900 LTE. I have not been able to determine a pattern to this.  

Link to comment
Share on other sites

I didn't know the network could get a device to change bands on CDMA, I thought it was determined solely by the phone/PRL.

 

PRL affects scan behavior by device.  The network can be set up to control band/channel switching.  Sounds like Sprint is trying to do eactly that now.

Link to comment
Share on other sites

PRL affects scan behavior by device.  The network can be set up to control band/channel switching.  Sounds like Sprint is trying to do eactly that now.

 

So if my phone is idling on 1X 1900, the network can switch it over to 1X 800 or vice versa (just like LTE)?

 

Or is this load balancing only when a device is ready to drop LTE for a phone call?

Link to comment
Share on other sites

So if my phone is idling on 1X 1900, the network can switch it over to 1X 800 or vice versa (just like LTE)?

 

Or is this load balancing only when a device is ready to drop LTE for a phone call?

 

The network, when fully configured for it, can do it because of quality or load balancing.

Link to comment
Share on other sites

I was just in a Shentel market as well and noticed my phone preferred band 26 most of the time too. Perhaps band 25 was clogged up with single band devices and the load balancing was working as it should.

 

And yes, I believe devices can switch between voice bands (800 and 1900) during a call if the network is set up for it.

 

In any case, this market was the best Sprint experience I've ever had.

Link to comment
Share on other sites

I was just in a Shentel market as well and noticed my phone preferred band 26 most of the time too. Perhaps band 25 was clogged up with single band devices and the load balancing was working as it should.

 

And yes, I believe devices can switch between voice bands (800 and 1900) during a call if the network is set up for it.

 

In any case, this market was the best Sprint experience I've ever had.

 

I think the "load balancing" issue here is related specifically to 1xRTT, not LTE.

Link to comment
Share on other sites

 

 

And yes, I believe devices can switch between voice bands (800 and 1900) during a call if the network is set up for it.

I live in the Shentel market. I have seen calls switch from 1x1900 to 1x800 right in the middle of a call. I don't think I've ever seen it go the other direction but I assume it's possible. I often see it happen within the first 30 seconds of a call. This is when I have very good signal too, not just when I'm about to drop a call on 1x1900.

 

Sent from my Note 4.

  • Like 2
Link to comment
Share on other sites

I live in the Shentel market. I have seen calls switch from 1x1900 to 1x800 right in the middle of a call. I don't think I've ever seen it go the other direction but I assume it's possible. I often see it happen within the first 30 seconds of a call. This is when I have very good signal too, not just when I'm about to drop a call on 1x1900.

 

Sent from my Note 4.

Shentelians are lucky!   I have never experienced a hyper band handoff from 1900 to 800 during a call.   In my market my experience is that the call will drop on 1900 before ever being handed off to 800 even as of late.    Usually as quickly as i can redial the number my phone has acquired 1X 800 and the call will stay on 800 for the duration.    

Link to comment
Share on other sites

Shentelians are lucky!   I have never experienced a hyper band handoff from 1900 to 800 during a call.   In my market my experience is that the call will drop on 1900 before ever being handed off to 800 even as of late.    Usually as quickly as i can redial the number my phone has acquired 1X 800 and the call will stay on 800 for the duration.    

I have seen this reported here and I THINK I have seen it too, but I am not ready to declare it as a fact.

I have seen Signal check Pro show a call originate on 1900 but switch to 800 before the called party can answer.  It happened fast.

I am not sure if I saw a transfer of an established call or maybe a transfer as the call was setting up and then a slow update of the displayed data.  My 1900 1x is so good that I find it very hard to get into a situation that will cause the loss of a 1900 1X signal thanks to Shentel's great work. As I get some free time someday, I am going to work on this and try to prove if it does or does not transfer a working call from 1900 1x to 800 without a drop.

Link to comment
Share on other sites

I have never seen a transfer from 1900 to 800. My call will drop then the phone will switch to 800 and I can start the call again. This is maddening, the failure to hand off to 800 kind of defeats the purpose (maybe my phone is one of the ones with software issues :( )

 

I do however, experience successful hand offs from 800 to 1900 anytime when I start a call on 800 in the Shentel market then drive into the Sprint market. I have rarely connected to 800 in the Berks County Sprint market even though the S4GRU Maps would indicate 800 is complete. The exception would along the route 422 corridor where I have occasionally connected to 800.

 

Out of curiosity I created a PRL without 1900 to see if I could connect to 800 in the Berks County Sprint market. When restarting my phone it would briefly connect 800 then switch to no service. This would seem to indicate 800 is turned on but Sprint is blocking access for some reason.

Link to comment
Share on other sites

I have never seen a transfer from 1900 to 800. My call will drop then the phone will switch to 800 and I can start the call again. This is maddening, the failure to hand off to 800 kind of defeats the purpose (maybe my phone is one of the ones with software issues :( )

 

I do however, experience successful hand offs from 800 to 1900 anytime when I start a call on 800 in the Shentel market then drive into the Sprint market. I have rarely connected to 800 in the Berks County Sprint market even though the S4GRU Maps would indicate 800 is complete. The exception would along the route 422 corridor where I have occasionally connected to 800.

 

Out of curiosity I created a PRL without 1900 to see if I could connect to 800 in the Berks County Sprint market. When restarting my phone it would briefly connect 800 then switch to no service. This would seem to indicate 800 is turned on but Sprint is blocking access for some reason.

 

Is this on your DuraXT?

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

    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
    • So how does this whole direct to satellite thing fit in with the way it works now? Carriers spend billions for licenses for specific areas. So now T-Mobile can offer service direct to customers without having a Terrestrial license first?
  • Recently Browsing

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