DSL Gets ‘Base Stations’

While doing some research on how capacity will grow in fixed line and wireless networks in the future I stumbled over the following thing right in my neighborhood: Future bandwidth increases on the last
mile to the subscriber come with an additional cost in comparison with today’s
standard ADSL or ADSL2+ deployments because of extra hardware that has to be installed close the the subscriber.

Vdslpic
For ADSL2+ the DSLAM is usually installed
in the telephone exchange and the cable length to the subscriber can be up to 8
km for a 1 MBit/s service. For VDSL, which offers data rates of 50 MBit/s
in downlink, the cable length must not exceed 500m. Thus, DSLAMs can no longer
be only installed in central telephone exchanges but equipment has to be
installed in cabinets on the street. The cabinets themselves are quite large (about half the size of a GSM or UMTS base station),
require power, active cooling, and create noise. For the installation
of the cabinets earthworks are necessary to lay the additional fiber
and power
cables required to backhaul the data traffic. The picture on the left shows a VDSL DSLAM cabinet that
has been installed alongside a ‘legacy’ small telecom cabinet as part of the current VDSL build out in my region.

To connect a
new subscriber a technician is required to manually rewire the customer’s line
to one of the ports. Different sources currently
specify the maximum capacity of such cabinets from about 50 to 120 VDSL
ports. To support 500 VDSL connections per km², several cabinets are thus
required. I wonder what happens when 5 different companies put such DSL ‘base stations’ in place!?

What are Secondary PDP Contexts Good For?

I often wondered in the past what ‘Secondary PDP Contexts’ are good for in UMTS networks. I had a vague idea but never had the time to look up the details. These days I had and here’s a short explanation:

‘Secondary PDP contexts’ can be used to separate the real time data traffic from background or signaling traffic into different streams on the air interface while keeping a single IP address on the mobile device. This is done by an application providing the network with a list of IP addresses in a Traffic Flow Template. The mobile device and gateway router (GGSN) in the network will then screen all incoming packets and handle packets with the specified IP addresses differently, like not repeating them on the RLC layer after an air interface transmission error. This is transparent to the IP stack and the applications on both ends of the connection.

External providers of speech services such as Skype, however, do not have access to this functionality. A big advantage for operator controlled IMS services when things get wild on the air interface!?

Resources:

  • Secondary PDP Context Activation: 3GPP TS 23.060, Chapter 9.2.2.1.1 (Rel 6)
  • Traffic Flow Template Description: 3GPP TS 24.008, Chapter 10.5.6.12 (Rel 6)

Wifi Layer 1 Tracing with Wi-Spy – Part 3

For those interested in getting a feeling of how Wifi works on the physical layer, Metageek’s Wi-Spy is the ideal tool. I’ve already reported about my first experiences here and here. Wifi has become very popular in Paris due to DSL being quite cheap. So it should thus probably not be surprising that I can see 13 access points in my Paris apartment. As there are only three non-overlapping Wifi channels on the 2.4 GHz ISM band the question is what kind of impact such a high number of access points has on throughput.

Wifiparis
Matters are made worse by the fact that some of the networks I can see are used for TV and video streaming. This is quite popular in Paris as this is offered by most DSL ISP’s and one even offers video streaming over Wifi to a remote set top box. The picture on the left shows a trace taken with Wi-Spy under these conditions. The lower graph in the figure shows the frequency range of the ISM band between 2400 and 2480 MHz. Instead of showing the frequency in MHz the x-axis labs show the 13 available Wifi channels. On the y-axis the amplitude of the signal received over the band is shown. The color of the peak depends on the intensity of the signal received during 60 minutes. Bright color indicates high activity. The graph shows five partially overlapping networks with their center frequency on channel 1 (only little traffic so the arch is not very well visible), channel 3, 5,6 and 11.The most activity can be observed in the wireless network that is centered around channel 11.

The upper graph shows a time graph over the frequency range. On the y-axis I’ve chosen a resolution of 60 minutes to show the activity in the ISM band in the course of one hour. The Wifi networks on channel 5 and 11 were most likely used from streaming as there is uninterrupted activity throughout the test period. The Wifi networks on 3 and 6 were also used for streaming. Streaming was stopped on the Wifi network on channel 6 after about 12 minutes while streaming was started on the Wifi network on channel 3 about 40 minutes into the trace.

To see what the impact of that streaming has on throughput in my network I used two notebooks, one connected via Ethernet, the other via Wifi and Iperf, a UDP and TCP throughput measurement tool. With a fully overlapping Wifi network which is used for TV streaming, capacity of the Wifi network under test was reduced to 72%. Partial overlapping entails an even bigger speed penalty and performance was reduced to 59%.

Here are the absolute values:

  • No interference: 22.5 MBit/s
  • Full Overlapping: 16.3 MBit/s
  • Partial Overlapping: 13.4 MBit/s

Looks like it is time equipment manufacturers are taking the 5 GHz band a bit more seriously…

For more traces take a look at my previous traces or head over to Metageek where you can download the software and check out some sample traces yourself.

T-Mobile activates EDGE in Southern Germany

T-Mobile has announced a couple of months ago that it will upgrade most parts of its GSM/GPRS network in Germany to EDGE. Since then I’ve seen reports that EDGE has been activated here and there but not where I live. Today, I noticed that T-Mobile has also switched to EDGE in the South of Germany near the Lake of Constance where I live. Not that we wouldn’t have excellent 3G coverage here already by all network operators but since the first iPhone won’t be 3G capable and we’ve still got a good number of rural spots in this part of Germany without 3G coverage it’s a welcome move.

Looks like T-Mobile is quite active of continuously improving their 2.5G network.

Wifi Ueber-Geek Question Result

Back in mid September I reported on using my Linksys WRT54 Access Point in "Access Point Client Mode" to create a wireless link to another access point for a number of notebooks which are connected via Ethernet to the Linksys. The traces which I took on the Linksys and on the notebooks indicated that the Linksys replaces the MAC addresses of the notebooks with its own before it sends the packets over the wireless link. Equally it replaced its own MAC address in incoming packets with the MAC address of the real recipient. This is neither layer 2 bridging nor layer 3 IP switching but something in between. I couldn’t quite believe it.

Arp
In the meantime thanks to the suggestions I received I made some further tests and I can now confirm that the Linksys really does replace the MAC addresses. Take a look on the picture on the left which shows the ARP table of a PC connected wirelessly to the real access point. The notebooks connected to the Linksys Client AP both have the same MAC address. The MAC address is that of the access point! Quite sophisticated! (Note: All devices in the network are in the same IP subnet)

I am not sure how this feature should be called. It’s not really ‘Layer 3 switching’ which is already a highly overloaded term anyway. I’d prefer the term ‘MAC masquerading’ although the term is also already used for something else as well.

Thanks to all who sent their comments and suggestions!

DSL Oversubscription Vs. 3G Capacity

A fierce competition is raging in Austria between DSL and 3G operators positioning 3G data cards as an alternative for DSL connectivity. Prices are interesting too, so many people are going wireless these days. Which leaves the question of how much capacity mobile networks could have compared to DSL.

Certainly not an easy question to answer so let’s take a couple of assumptions:

Austria has 4 HSDPA networks today. Let’s say in a city like Vienna the average cell inter distance is 1km. Usage is still in it’s early stages so only a single 5 MHz channel is used in a 3 sector cell. Per sector throughput is assumed to be 2.5 MBit/s. Since the cell covers an area of 1 km², the capacity in that area per operator is thus 2.5 * 3 = 7.5 MBit/s. All 4 operators together would thus create a capacity per km² of 30 MBit/s.

On the fixed line side I would say that DSL today offers a speed of on average of 4 MBit/s to housholds in cities like Vienna. Vienna has a a population density of 4000 inhabitants per km². Let’s say the average household has 3 people and DSL penetration is 40%. Thus there are (4000 / 3) * 0.4 = 533 DSL lines per km². With an average speed of 4 MBit/s per DSL line that would be 2.113 GBit/s. Sounds like a lot more than what the 3G calculation results in above. But wait, there’s a catch. The 4 MBit/s are only valid between a subscriber and the DSLAM (DSL Access Multiplexer). The connection to the core network is usually much smaller. I’ve heard the ‘oversubscription’ is anywhere between 1:20 and 1:50. Let’s assume the oversubscription is 1:30. As a result, the DSL capacity per km² would be 71 MBit/s.

30 MBit/s wireless vs. 71 MBit/s via DSL

The example stands or falls with the DSL oversubscription ratio. If you have more details on this please let me know!

Direct Tunnel – GPRS Core Network Streamlining

While work is ongoing on 3GPP LTE (Long Term Evolution) and SAE (System Architecture Evolution), current 3G networks continue to be enhanced as well. Since the 3G air interface is in the process continues to evolve with HSPA (High Speed Packet Access) it was felt in the standards groups that the 3G core network should be streamlined to handle the increasing network traffic more efficiently.

One part of the network in particular has been waiting for optimization for quite some time. In today’s 3G packet core architecture the SGSN (Serving GPRS Support Node) which is the gateway between the radio network and the core network handles both signaling traffic (e.g. to keep track of a users location) and the actual data packets exchanged between the user and the Internet. Since the users location can change at any time, data packets are tunneled (encapsulated) from the gateway to the Internet (The Gateway GPRS Support Node, GGSN) via the SGSN over the radio network to the mobile device. The current architecture uses a tunnel between the GGSN and the SGSN and another one between the SGSN and the Radio Network Controller (RNC). All data packets thus have to pass the SGSN which has to terminate one tunnel, extract the packet and put it into another tunnel. This requires both time and processing power.

Since both the RNC and the GGSN are IP routers this process is not really required in most circumstances. The one tunnel approach now standardized in 3GPP thus foresees that the SGSN can create a direct tunnel between the RNC and the GGSN and thus remove itself from the chain. Mobility Management remains on the SGSN, however, which means for example that it continues to be responsible to modify the tunnel in case the mobile device is moved to an area served by another RNC.

The approach does not work for international roaming since the SGSN has to be in the loop in order to count the traffic for inter-operator billing purposes. Another case where the one tunnel option can not be used is in case the SGSN is asked for example by a prepaid system to count the traffic flow. A small limitation since in practice it’s also possible to connect such a system to the GGSN (via Diameter).

For the details have a look at the following documents:

  • Direct Tunnel 3GPP Work Item Description SP-060142_S2-060545
  • The TR (Technical Recommendation) describing the overall design and impact on existing functionalities: TR 23.809
  • The Change Request (CR) for 3GPP TS 23.060
  • And the latest version of the ‘GPRS Service Description;  Stage 2’ which contains the enhancements. TS 23.060 7.4.0

The Downside for Verizon of picking LTE

It’s been THE news of the week for the wireless industry that Verizon has selected to go for LTE as their next generation network rather than UMB, the successor technology of their current CDMA1x EvDO network. I put down my initial thoughts on the deal here. In the meantime there are two additional important points which came to my mind: Multimode terminals and backwards compatibility!

UMTS operators that are upgrading to LTE will have a smooth migration path especially since mobile devices are likely to be GSM/UMTS/HSDPA/LTE compatible. LTE makes this especially easy since the air interface has been designed to be able reuse oscillators etc. from HSDPA. Also the software stack on higher layers will probably be partly reusable as I expect that high level (NAS) signaling will be similar.

CDMA operators such as Verizon will have a much more difficult story to tell their subscribers. I kind of doubt that there will be CDMA/LTE mobile devices since there won’t be many operators taking this path. Also from the core network point of view LTE won’t be able to interconnect with a CDMA network as easily as with a UMTS network. For UMTS, the LTE specification already contains all information of how to do handovers back and forth between the two worlds.

A small comfort for Verizon: Sprint will have a similar experience moving from CDMA to WiMAX…

Mobile Web 2.0 Ressources

It’s good to see that not only wireless network technology is advancing but also the applications space. Rudy de Waele over from m-trends recently gave a great presentation at the Mobile Web 2.0 conference in London about the Mobile 2.0 Start-Up Ecosystem which is now available online. A great presentation if you are interested in the latest Mobile Web 2.0 developments from a technical perspective and also to find out who gets bought by whom and who gets money from whom.

If you are new to Mobile Web 2.0 or wonder what the difference is to Web 2.0 here is some further background material:

Verizon and LTE: All Over IP Is Shaking Up The Wireless World

Recent reports (here and here) that Verizon has chosen LTE as a successor technology of its current CDMA 1xEVDO Rev A. instead of UMB is likely to be a big blow for Qualcom and the CDMA industry as a whole. While the other big CDMA network operator Sprint has decided to go for WiMAX and a lot of global CDMA operators have already jumped ship and went to UMTS/HSDPA, Verizon is the latest addition to the list.

UMB, LTE and WiMAX are all ‘IP only’ technologies that strictly separate the wireless network from the applications running above. This is not only beneficial for users (as discussed here) but also allows network operators to jump ship when going to the next technology. Just as in the case of Verizon and Sprint. No UMTS operators have so far shown their interest to do the same, except for the threats of Vodafone that the LTE timeline is too slow for them and that they are looking what WiMAX can do for them. Might the tight integration of LTE into the already existing 2G/3G GSM/UMTS ecosystem keep operators at bay?

So while UMB is not dead yet, the hill they have to climb just got a lot steeper.