Jump to content

Nokia moves to purchase Alcatel-Lucent

EvanA

By EvanA
in General Topics

 Share

Recommended Posts

lilotimz Member Level: LTE Advanced

lilotimz

Posted
Posted

Will be troubling times for existing Alcatel-Lucent markets in the short term but an exciting time for the future as the weakest NV vendor regions get cannibalized by Samsung, Ericson, and Nokia.

 

Lots of question marks will be have have over the existing deployments from both Nokia and alu territory.

 

Sent from my Nexus 5

  • Like 1
Link to comment
Share on other sites
nexgencpu Member Level: LTE Advanced

nexgencpu

Posted
Posted

Will be troubling times for existing Alcatel-Lucent markets in the short term but an exciting time for the future as the weakest NV vendor regions get cannibalized by Samsung, Ericson, and Nokia.

 

Lots of question marks will be have have over the existing deployments from both Nokia and alu territory.

 

Sent from my Nexus 5

:td:

  • Like 1
Link to comment
Share on other sites
ericdabbs Member Level: LTE Advanced

ericdabbs

Posted
Posted

I am not so sure how I feel about this right now.  I mean Nokia seems to be doing pretty well with its network equipment but I just don't know how much impact this has on LTE deployment especially in markets that use their equipment for B25/B26/B41 LTE.

Link to comment
Share on other sites
shaferz Member Level: eHRPD

shaferz

Posted
Posted

I don't understand why this is a bad thing. Did another source indicate they were immediately shutting down equipment manufacturing for the Alcatel side of the house? My assumption (while probably incorrect) is that nothing will change in the near term other than AP/AR header information saying Nokia now instead of Alcatel - and the back office updates to make that happen. Did I miss something that indicated Alcatel was going to be effectively shut down?

  • Like 1
Link to comment
Share on other sites
miguell2 Member Level: 3G EVDO

miguell2

Posted
Posted

I am not so sure how I feel about this right now.  I mean Nokia seems to be doing pretty well with its network equipment but I just don't know how much impact this has on LTE deployment especially in markets that use their equipment for B25/B26/B41 LTE.

 

I don't imagine it would have any impact in the short term. Legacy equipment will remain for as long as they are in their useful lives. I imagine that interoperability between ALU and Nokia equipment will be improved over time.

  • Like 1
Link to comment
Share on other sites
miguell2 Member Level: 3G EVDO

miguell2

Posted
Posted

I don't understand why this is a bad thing. Did another source indicate they were immediately shutting down equipment manufacturing for the Alcatel side of the house? My assumption (while probably incorrect) is that nothing will change in the near term other than AP/AR header information saying Nokia now instead of Alcatel - and the back office updates to make that happen. Did I miss something that indicated Alcatel was going to be effectively shut down?

I seriously doubt that. Also they can't just shutdown equipment, they deployed it and it is run by whomever and ALU simply supports it. Sprint could ALU equipment forever as long as they keep paying for support. It will be ALU equipment regardless of who owns them, its just who you call for support that will change.

  • Like 1
Link to comment
Share on other sites
centermedic Member Level: 4G WiMax

centermedic

Posted
Posted

Wouldnt it be better for output? 2x the people making the same thing, rather than 2 different pieces.

These mergers rarely come without layoffs, especially when major overlap in products/services exists.

  • Like 1
Link to comment
Share on other sites
Rawvega Member Level: 4G LTE

Rawvega

Posted
Posted

http://online.barrons.com/articles/sprint-may-have-spurred-nokia-alcatel-lucent-deal-1429282538

 

 

Speculation of a Nokia-Alcatel-Lucent wireless-asset merger first surfaced about one and a half years ago but receded. We think the latest round of talks was spurred on by Sprint ( S), which wanted to see the wireless assets combine so that it could rely on the new entity as its primary or even sole wireless equipment vendor going forward. 

 

Interesting speculation

  • Like 1
Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
Posted

 

I have heard internal rumors that Sprint (via Masa) was considering a move to just two network vendors from here forward.  For a good year or so.  Dumping Ericsson.  But not feeling good about ALU as the only other partner with Samsung.  But going to two vendors with Samsung and Nokia (via an ALU buyout) may not be so bad.  So Sprint being part of the catalyst for this marriage is plausible when put into context with the rumors I've heard.

  • Like 2
Link to comment
Share on other sites
lilotimz Member Level: LTE Advanced

lilotimz

Posted
Posted

I have heard internal rumors that Sprint (via Masa) was considering a move to just two network vendors from here forward. For a good year or so. Dumping Ericsson. But not feeling good about ALU as the only other partner with Samsung. But going to two vendors with Samsung and Nokia (via an ALU buyout) may not be so bad. So Sprint being part of the catalyst for this marriage is plausible when put into context with the rumors I've heard.

The cdma portfolio from Alcatel-Lucent may be all that Nokia needs. Their cdma offerings are far inferior as it currently exists.

 

Sent from my Nexus 5

  • Like 1
Link to comment
Share on other sites
  • 3 months later...
EvanA Member Level: 4G WiMax

EvanA

Posted
  • Author
Posted

 

 

The transaction is expected to close in the first half of 2016.

 

Faster Nokia, faster!

  • Like 1
Link to comment
Share on other sites
WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

s6gru.com is still open!

 

Let the sex guru jokes commence...

 

AJ

  • Like 1
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.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • CalebM
      SignalCheck Beta Crew Forum

      By CalebM · Posted

      Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 

  • Recently Browsing

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