biggest device manufacturing giants. But what happens when embedded OS'es like e-linux mature hitting the cost implication substantially. As most of the major players own a stake there (Symbian), and a free alternative to OS which is much matured than Symbian is bound to make a news.

On the hardware side, ARM enjoys the dominance. And the other players are far behind, the way in which R&D in hardware industry are on, looks as if there is bound to be some competition to get gener

This was the book written by none other than Bill Gates, who has undisputedly been the king of the IT. This is irrespective of anyone accepts it or not. Sounds as if a lot is going to happen in the Wireless domain in the near future.

There was a company’s vision that stated “Inventing is better than predicting”. Its easier said than done.

Its just a generic view with respect to the subject intended for the Wireless/Wireline Networks and the future associated ahead. As they say, that “necessity is the mother of invention”, and would dictate the terms/future. But hey, out here the technology has been moving so fast that there is absolutely no scope of collecting the necessities (Requirements, as we call it). And so many bigger giants are changing/cutting-short their turnaround cycle time to meet the customer demands. The biggest issues that are stopping growth as of today are due to the lack of standardization and inter- operatibility.

Specifics with respect to Carrier dependencies especially in the CDMA networks where the Software Applications are very closely associated to the revenue models of the carriers. And the technical support guys in the associated carriers do not understanding a bit of it. And in the worst case scenario, if the frequency itself is not supported in the deployment area.

The revenue models so far have mostly been dictated by the carrier/service providers. In fact, so many mobile manufacturing companies are facing this challenge, and putting in a lot of R & D to reduce this monopoly of the network service providers.

What is the Road ahead, where are we headed towards. As a user, as a developer, as a carrier service provider, or as an Application provider/Content Aggregator/Content provider. The device manufacturing firms are already feeling the heat due to carrier dependencies, but still they have a big pie as the hardware as well as OS is owned by a stake of most of the biggest device manufacturing giants. But what happens when embedded OS'es like e-linux mature hitting the cost implication substantially. As most of the major players own a stake there (Symbian), and a free alternative to OS which is much matured than Symbian is bound to make a news.

On the hardware side, ARM enjoys the dominance. And the other players are far behind, the way in which R&D in hardware industry are on, looks as if there is bound to be some competition to get gener

say, that “necessity is the mother of invention”, and would dictate the terms/future. But hey, out here the technology has been moving so fast that there is absolutely no scope of collecting the necessities (Requirements, as we call it). And so many bigger giants are changing/cutting-short their turnaround cycle time to meet the customer demands. The biggest issues that are stopping growth as of today are due to the lack of standardization and inter- operatibility.

Specifics with respect to Carrier dependencies especially in the CDMA networks where the Software Applications are very closely associated to the revenue models of the carriers. And the technical support guys in the associated carriers do not understanding a bit of it. And in the worst case scenario, if the frequency itself is not supported in the deployment area.

The revenue models so far have mostly been dictated by the carrier/service providers. In fact, so many mobile manufacturing companies are facing this challenge, and putting in a lot of R & D to reduce this monopoly of the network service providers.

What is the Road ahead, where are we headed towards. As a user, as a developer, as a carrier service provider, or as an Application provider/Content Aggregator/Content provider. The device manufacturing firms are already feeling the heat due to carrier dependencies, but still they have a big pie as the hardware as well as OS is owned by a stake of most of the biggest device manufacturing giants. But what happens when embedded OS'es like e-linux mature hitting the cost implication substantially. As most of the major players own a stake there (Symbian), and a free alternative to OS which is much matured than Symbian is bound to make a news.

On the hardware side, ARM enjoys the dominance. And the other players are far behind, the way in which R&D in hardware industry are on, looks as if there is bound to be some competition to get gener

th respect to Carrier dependencies especially in the CDMA networks where the Software Applications are very closely associated to the revenue models of the carriers. And the technical support guys in the associated carriers do not understanding a bit of it. And in the worst case scenario, if the frequency itself is not supported in the deployment area.

The revenue models so far have mostly been dictated by the carrier/service providers. In fact, so many mobile manufacturing companies are facing this challenge, and putting in a lot of R & D to reduce this monopoly of the network service providers.

What is the Road ahead, where are we headed towards. As a user, as a developer, as a carrier service provider, or as an Application provider/Content Aggregator/Content provider. The device manufacturing firms are already feeling the heat due to carrier dependencies, but still they have a big pie as the hardware as well as OS is owned by a stake of most of the biggest device manufacturing giants. But what happens when embedded OS'es like e-linux mature hitting the cost implication substantially. As most of the major players own a stake there (Symbian), and a free alternative to OS which is much matured than Symbian is bound to make a news.

On the hardware side, ARM enjoys the dominance. And the other players are far behind, the way in which R&D in hardware industry are on, looks as if there is bound to be some competition to get gener

anies are facing this challenge, and putting in a lot of R & D to reduce this monopoly of the network service providers.

What is the Road ahead, where are we headed towards. As a user, as a developer, as a carrier service provider, or as an Application provider/Content Aggregator/Content provider. The device manufacturing firms are already feeling the heat due to carrier dependencies, but still they have a big pie as the hardware as well as OS is owned by a stake of most of the biggest device manufacturing giants. But what happens when embedded OS'es like e-linux mature hitting the cost implication substantially. As most of the major players own a stake there (Symbian), and a free alternative to OS which is much matured than Symbian is bound to make a news.

On the hardware side, ARM enjoys the dominance. And the other players are far behind, the way in which R&D in hardware industry are on, looks as if there is bound to be some competition to get gener

biggest device manufacturing giants. But what happens when embedded OS'es like e-linux mature hitting the cost implication substantially. As most of the major players own a stake there (Symbian), and a free alternative to OS which is much matured than Symbian is bound to make a news.

On the hardware side, ARM enjoys the dominance. And the other players are far behind, the way in which R&D in hardware industry are on, looks as if there is bound to be some competition to get generated here also.

Would this result in the device manufacturing companies giving application support directly and also tailoring the functionalities so that the dominance of carriers is reduced. To the engineer's, its definitely going to be an enjoyable experience.