<..Because of their "utility-like" status, RBOCs would probably cut capital expenditures for DSL roll-out in order to preserve their dividend...>
Hi Bernard-
I think the RBOCs have dragged their feet for about as long as they can. I can't imagine any scenario where 1999 would NOT be the year for telco DSL rollout.
They KNOW there will be major obstacles but they will push on. As I've previously opined, I think ADSL will be the telco's Vietnam - but it's a war they HAVE to fight or else become obsolete. [And most haven't really even started on the challenges of ADSL *networking* (though Ascend and Paradyne have taken some shots: techweb.com ) - but for the most part, only recently having achieved some degree of OSI layer 1 consensus, they will likely be grappling for some time with the substantial physical layer implementation obstacles.]
<..This would just widen the opportunity for the subset of CLECS which
have strong financial resources, such as Winstar and perhaps even TGNT...>
I don't see ADSL as competition for fixed wireless. ADSL will not fill the bill for most corporate needs. In fact, IMO the rollout of ADSL will fan the fire of public and corporate bandwidth demand, and so INCREASE the focus on *serious* BBLL such as fixed wireless.
fwiw, from last month's Communication News (hardcopy - OCR'd):
============
"Controlling Microwave Links in a Wireless Environment" by Robert Ma
Network management is just as necessary in wireless networks as in wireline networks, but there are some important differences.
As microwave radio becomes more widely deployed throughout the world, there is a growing need for network management. Many of the requirements of wireline network management--fault and configuration management, performance, security, and accounting monitoring--carry over to the wireless world. But there are significant differences between wireline and wireless networks, so managers should take several factors into consideration before settling on a management solution.
A distinct difference between a wireline and a wireless network is a unit's lack of accessibility in a wireless topology. In a wireline LAN (local area network), each network component is easily accessible through an in-band connection at the data port, or through the PSTN (public switched telephone network) or a private network so connectivity to the network device is easily available.
Common topologies are bus, star, tree, and ring, all of which are easily traversed with existing bridge or routing algorithms externally provided in the wired network by individual bridges and routers.
In contrast, a microwave radio, by definition, is connected only to other radios for the express purpose of carrying user traffic. Point-to-point radios are connected in a serial trunk configuration, with repeater nodes connecting terminal ends. Access to a specific radio from any location is possible only through another radio, and access to a remote terminal is restricted to the one hop next to it. Repeater locations can be accessed from more than one spur direction in what is known as trunk and spur topology.
A network of microwave radios typically spans a large geographic area, and the network may connect to the PSTN or a wireline private network at various access points, or not at all. This makes accessibility of individual radios an interesting problem.
This topology is unique to a wireless network, and an effective network management system must address the accessibility problem. The most effective way of addressing any midpoint radio without affecting system performance is using a wayside management channel and an IP router to maximize delivery of IP datagrams to IP-addressable radios.
The IP router provides basic IP connectivity, so that a radio IP network can be created from multiple radios. Each radio is represented by an IP address that is assigned by the network manager. Each radio knows which "route" or "path" to take to get to any other radio.
MANAGEMENT CHANNELS
The microwave network topology creates another problem requiring subtlety of radio design. Since the microwave radios are the elements that create a wireless network, they also function as the "wireless cable" that connects each network element. All access to a radio is only through another radio, so a management channel must be created in the "wireless cable" to move management messages across the microwave hop from radio to radio.
This channel can exist either within the main traffic channel or outside that channel. Stealing part of the main channel for management messages decreases the pipe available for revenue-bearing traffic, a problem that is compounded if the main channel is small (T1 or less).
Additionally, an integral multiplexer within the radio is required to select certain DS0s (digital service, level zero, a worldwide standard of 64 Kbps for digitizing one voice conversation) or a fixed bandwidth channel out of the main channel. Unless a specific DS0 or robbed bit is coordinated with the user, any selection of bandwidth will conflict with the user's channel plans for the main channel.
A simpler solution is to accomodate the management Channel in the radio's overhead channel. Although this adds to the radio's aggregate data rate, it can be accommodated within bandwidth efficiency requirements of the FCC by stepping up the radio's modem to a higher complexity modulation scheme.
So any solution requires the design of the radio to include a management pipe (or data link) that is integral to the design of the radio. Depending on the capacity of the radio and the amount of overhead capacity available, the radio design is critical to providing the bandwidth needed for management messages.
That leaves us with some inherent limitations within the SNMP (simple network management protocol). First, SNMP is generally implemented in IP networks, limiting the network to IP devices only and preserving the management bandwidth for only IP-addressable devices. Second, assigned IP addresses can be used to restrict devices on the network. And third, SNMP version 1 can be inefficient in retrieving large tables of data.
Therefore, careful design of the MIB (management information base) database and clever use of polling and traps must be used to overcome the third limitation, and the first two limitations must be accepted by network managers.
Network management is a necessary function to ensure the highest use and proper operation of microwave networks. Furthermore, any solution must be crafted to accommodate equipment from various vendors. Network administrators are requiring that equipment comply with industry standards and protocols so that they can be managed by a single and simple network management system.
TCP/IP (transmission control protocol/Internet protocol) networks are the most common types of networks today, and SNMP is the communications architecture and protocol standard for TCP/IP network management.
===================================
and some convergence reading:
"Networks find voice"
news.com
On ATT and high speed access:
news.com
On telco convergence M&A:
news.com |
