A Flatrate For Calling All EU Fixed Lines And Mobiles From Anywhere In The EU

I travel a lot in Europe and I call lots of people in different countries not only when I'm in my home country but also while traveling. In other words, without a good tariff for international calling and data use, it's no fun. A new mobile EU-Flat tariff introduced by my mobile network operator last year has, for the first time, enabled me to use my monthly mobile data volume anywhere in the EU and to call back home without per minute fees for a modest additional monthly fee of 5 euros. This has helped a lot and apart from one exception I didn't have to use local SIM cards anymore.

One thing that the offer didn't include, however, was making calls from my home country or while traveling in the EU to fixed and mobile phones of other EU countries. At prices of well over a euro a minute this had remained prohibitively expensive. But things have moved on since then and my fixed and mobile network operator of choice has made me a bundle offer to extend my current EU-flat to also include voice calls from anywhere in the EU to anywhere in the EU to both fixed and mobile devices. Yes, that's what I've been waiting for for some many years. The 'everything inclusive anywhere EU-Flat' now costs an extra 10 euros on top of my normal fixed line and mobile contracts instead of the 5 euros I paid before but with my usage pattern that's a deal I was more than willing to take.

No longer waiting to make some calls only until I'm back home or in the office or by using complicated dial-in numbers, no nightmares about costs spiraling out of control because that conference call only offers an international dial-in number, it's definitely my tariff add-on of the year!

P.S.: No, this is not an advertisement for a particular fixed and mobile network operator which is why I haven't named the company in the first place. This blog entry is about documenting a very positive change in the telecommunication market and to encourage other network operators to follow.

32C3 – Congress Infrastructure Review And A Plea for GSM ARFCNs for 2016

Like ever year at the end of the Congress one of the last sessions is the Infrastructure Review. Here, the people who built the congress data network, the DECT network, the GSM network and the Seidenstraße talk about the technology they used this year. It always interesting to hear how much data, calls and packets have been shuffled through the networks and how that compares to last year, how many people used the network, how many wireless devices were used, which networking equipment was used and so on and so on. For anyone interested in networks this talk is a must see and fun to watch not only because of the interesting numbers but also because the presentation contains a lot of hacker fun and sarcasm. This year was certainly no exception. The cut video of the session is not yet on the congress streaming server but the raw-uncut version can be found here in the meantime.

One important message I also want to repeat here: So far, the GSM network of the Congress used the 1800 MHz DECT/GSM guard band. This won't be possible in 2016 anymore as that part of the spectrum has been auctioned in 2015 so one of the network operators in Germany has to be kind enough to loan the Congress GSM network organizers a couple of ARFCNs for the week. So if you are working in spectrum planning at a network operator and think you can spare a couple of channels for a week at the Congress location please think about it and get in touch with the organizers. If you don't know how to do that, let me know, I'll be glad to help!

32C3 – Vehicle2Vehicle Communication with IEEE 802.11p

One feature some proponents are pushing for future 5G networks are ultra short reaction times for ultra critical communication, for example between cars. What I failed to understand so far in this discussion was why for car to car communication a fixed network infrastructure and a backhaul network was necessary!? After all, car to car communication mainly makes sense for cars that are in close proximity to exchange information about potential dangers such as emergency braking, breakdowns and their current status such speed, direction etc., etc. It seems that my skepticism was not unfounded because unknown to me and perhaps also to the 1 ms 5G proponents, decentralized solutions not requiring a network infrastructure already exist.

While Europe and the US seem to be on different paths (once again) on higher layers of the protocol stack, both approaches are based on the IEEE 802.11p extension of the Wi-Fi standard. In this "Wi-Fi" flavor, there are no central access points, no fixed equipment and no backhaul of any kind. On top of this physical layer, event and context information is exchanged. An interesting challenge is how to ensure that messages are sent from "real" vehicles and not from rouge devices that want to disrupt traffic, e.g. by sending messages about emergency breaking etc. while at the same time ensuring privacy, i.e. to send messages anonymously to prevent tracking.

The concept that car companies have come up with is a public key infrastructure and cars equipped with a master certificate by car manufacturer. Based on the master certificate, temporary certificates are signed by a certificate authority which are then included in 802.11p messages sent by cars. Vehicles receiving messages can then validate the message by checking the temporary certificate which does not contain the car's identity and which are changed frequently. Rouge devices that do not have a master certificate can't get temporary certificates, at least in theory, and therefore can't include proper temporary certificates in their messages. That makes me wonder of course how hard it might be in the future to get a valid certificate by extracting it from an on-board computer of a vehicle. SIM cards of mobile devices have provided pretty good security over the past decades so there is at least some hope that the master certificates can be stored safely.

For more details, here's the talk on this topic from 32C3.

32C3 – A One Chip Retro Console For Assembly Programming

Voja-single-chip-cpuMy 32C3 discovery of the day: I’m not quite at the end of my Nibbler discoveries yet but I’ve just figured out how I want to continue my hardware adventures by climbing up the CPU ladder just a bit to something with interrupts and a real hardware stack: Voja Antonic’s ‘DIY Single-chip 2D Retro Game Console’!

I’ve already discovered the project a couple of days ago on the 32C3 Workshop page and yesterday I met them by chance in one of the hardware assembly and soldering areas of the Congress. After talking to them for a while I was intrigued enough that I had a look at the assembly code provided online over night. After that I was pretty much hooked…

One thing that particularly grabbed my attention was that the PIC doesn’t have a traditional VGA screen output or graphics unit. Instead, the VGA connector is connected to three D/A converters four digital outputs and an assembly program triggered by horizontal and vertical timings required for the VGA output invoke routines to paint the screen. Great, not only will I stay very close to to the real hardware, this way I will also learn a lot of how a bitmap and moving sprites stored somewhere in memory can be converted into a video signal.

Voja the creator of the board and Milos, who’s organized the BalCCon hacking conference in Novi Sad this year and the presentation of the project at 32C3, thanks very much for coming with this great project. I’m sure I’ll not be the only one who will be massively inspired by this!

32C3 – Approaching 20 Gbit/s of Outbound Traffic

Approaching-20-gbit12.000 people have bought tickets for the 32C3 and while they consumer a lot of data from the Internet it's easily dwarfed by the amount of data that is flowing from the congress to the outside world. How much of that are the live and recorded video streams is hard to tell but I guess it might be a fair amount. The screenshot on the left shows the state of affairs at 6 pm on day 2 of the congress:

  • Outgoing traffic keeps growing and now approaches 20 Gbit/s.
  • Incoming traffic is at 5.6 Gbit/s, 3 Gbit/s flowing to 7800 wireless devices over 146 Wi-Fi access points.

Amazing numbers and the 5 GHz Wifi is working just great for me! Only once did I have to fall back to the LTE network coverage so far which was during the intro session and key note in the huge conference hall during day 1 which can hold 3000 people. There are at least 8 Wifi access points in there which handle the load just fine at other times.

32C3 – Recommended Videos of Day 1

It's day 2 of the 32C3 in Hamburg and I'm really happy that I was able to attend in person this year. My previous tip to use a 5 GHz Wifi capable Android phone as a WiFi USB dongle for my notebook has paid out as the 2.4 GHz range is hopelessly overloaded in most places as promised. With 12.000 people attending and more streams going on in parallel than one could ever hope to follow it's total information overload so my pre-planning of what to attend paid out. In the meantime the video streams from day one are online and I can personally recommend the following ones I attended:

Towards (reasonably) trustworthy x86 laptops: Ever felt save by running Linux on your notebook? No? Well, then you probably have Coreboot as a Bios replacment and fell much better. Yes? No, have a look at the video of this session to get an idea of how Intel ME and the little microprocessors and flash in many other components of your notebook make it very hard to have trust in your hardware.

Running your own 3G/3.5G network: GSM and Osmocom are old friends and LaF0rge is working hard to bring 3G femtocells into the mix. He's almost there and if you ever wondered if you were just a bit dumb or whether ASN.1 is just a bit hard to understand, the talk will give you an answer as well. The stream's not yet online at the time of writing this but I'm sure you'll find it here by the time you read this.

How the (not so) Great Firewall discovers hidden circumvention servers: Very interesting presentation on research is presented here on how the Chinese Internet firewall actively reaches out to find out if a web server is really a web server or a hidden TOR gateway.

The Ultimate Amiga 500 Talk: For computer historians who had an Amiga of their own this 60 minute talk is a great refresher on the Amiga 500 hardware and programming. Those were the days 🙂

Lots and lots of other stuff was presented on day one is now online which will keep me busy once I'm back home as it's impossible to follow it all in real time. So head over and enjoy.

Things That Moved Me In 2015

It’s become almost a tradition for me in December each year to have a look back at what happened in the previous 12 months in the telecoms industry and in my private technology endeavors that have left long lasting impression or have marked the start of something new.  And so here we go again, in the 10th year of this blog’s existence. Yes, it has already been a decade, time passes quickly!

First lets have a look at the telecoms sector. Early in 2015, 3GPP announced that they have embarked on their voyage to 5G and have published a time table that shows what they intend to do right into the 2020s. Everybody is talking about it but nobody seems to know what it really is. NGNM has published a whitpaper containing use cases and 3GPP now looks how specifications can be enhanced and newly created to fulfill those visions. I had quite a number of posts on various aspects of 5G, such as thinking about what 5G is in the first place, debunking the 1 ms 5G myth and two looks at the use of super high frequencies beyond 5 GHz, stating that such frequency bands are only usable for transmitting data over very short distances and an opposite statement made in a very interesting IEEE paper.

On the other end of the spectrum, GSM networks are starting to be switched-off and many announcing a switch-off in the years to come. 3G also has limited lifetime left with some network operators thinking about a 2020 switch-off date. Personally, I can’t wait for GSM to be switched-off.

In recent years we have seen quite a number of network operators merging in different parts of Europe, thus reducing competition which made me wonder if Free in France will keep the title as last launched 4th network operator in Europe forever. There are certainly no signs they are going to lose that tile anytime soon.

Speaking of evolution I had a look back of how mobiles looked like a couple of years ago to show what has changed in mobile computing in the last 5 years and how that compares to the (few) changes in the desktop computer industry. Quite a contrast. And speaking of change, we are now officially past peak telephony in many countries in Europe including Germany when fixed line and mobile phone minutes are combined.

Over the clouds we haven’t peaked anywhere yet when it comes to connectivity. I had a number of positive ‘over the cloud’ connectivity experiences this year but with LTE ground to air it is likely to be topped in the future.

Back on earth with wires attached, I’ve been migrated from VDSL+ISDN at home to an all-IP connection with fixed line VoIP. Not that it had been my free will but I got quite a number of advantages from the move, including an upgrade from 25 to 50 Mbit/s in the downlink direction, from 5 to 10 Mbit/s in the uplink direction and HD-voice speech quality between fixed line and mobile.

Staying for a moment longer in the voice call domain, despite moving past peak telephony, I was really glad to get rid of Skype on the PC and to put it on a tablet where this proprietary piece of software will hopefully do less harm. On the other hand, I learned to like Skype while traveling to Asia as Skype over LTE is significantly cheaper than circuit switched voice for me while voice quality is significantly better. Not that I would install it on my mobile device that contains my private data but I rarely travel with only a single mobile device.

On the hardware side there have been a number of really important projects for my private development this year. The most important one, no doubt, has been the 4-Bit Nibbler CPU project about which I had many blog entries and on which I spend many weeks to put it together and finally realizing my dream understanding how computers really work by actually building a CPU from several chips.

On a more global scale, I was rocked by the announcement of the Raspberry Pi Zero, the first fully working computer that has been shipped as a magazine complement. This is a milestone in computing history not only for being small and cheap enough to fit onto the cover of a computer magazine. If you’ve lived under a stone for the past few months and haven’t heard of it, this is the story to check out!

When it comes to vintage computing, 2015 has also been an interesting year for me in that area, too. I’m a proud owner again of a Commodore C64 and an Amiga 500 and disk drives that take today’s SD cards instead of real 5.25 or 3.5 floppy disks have greatly helped me to explore my personal computing history and home computing history in general. The culmination in my vintage adventure has certainly been the 30th anniversary celebration of the Amiga in Neuss, Germany and the many people I met there with a similar passion for the home computers that had a significant impact on them when they were teenagers.

Before I get too nostalgic let’s better get back to 2015. My software discovery of the year has certainly been ‘Conversations’ an open source XMPP client app for Android that looks and feels very much like Whatsapp but offers privacy and confidentiality without compromising usability. I’m using it for about half a year now and in the meantime I’ve been able to convince quite a number of my friends that this is the way to communicate not only with me but also with their friends. Further on the software side, the Selfoss RSS reader continues to be an important tool I user several times a day to keep up to date with what is going on in the world. As it’s open source, I contributed some code for it as part of keeping myself current with PHP and database programming.

And last, but not least, I’ve read a couple of great books about computing this year, especially to better understand computing history and the history of free and open source software. ‘The Innovators‘ and ‘Fire in the Valley‘ comes to mind as well as ‘Rebel Code‘,  ‘Commodore – A Company on the Edge’,  ‘Amiga – The Future was here’ and ‘Diary of an 80s Computer Geek‘. And on the fiction side, I very much enjoyed ‘Chronos‘ and ‘The Martian‘, both excellent reads. As far as ‘The Martian’ is concerned, there’s a movie based on the book now, which I haven’t seen because in my opinion there’s no way it can be even half as good as the book has been. So if you haven’t seen it either, my advice is not to go for the DVD but to read the book.

There we go, this has been 2015 for me on the technology side. What a great year!

No 5 GHz Wifi in Your Notebook For 32C3? Use Your Smartphone As A Wi-Fi Dongle over USB!

Usb-tethering-wifiIt almost time for the 32C3 now and I'm on my way to attend in person this year. One thing the organizers have kept pointing out over the last few years is that due to the very limited spectrum available in the 2.4 GHz band, the network experience will be rather mediocre in this band. To get much better throughput, participants are advised to use the 5 GHz band instead. That's all nice and well but my notebook, and I guess the notebooks of many others, does not support the 5 GHz band with the built-in Wi-Fi PCI card. But there's an elegant solution!

These days even medium-priced smartphones come with 2.4 + 5 GHz Wi-Fi built in. What many people don't know is that the smartphones Internet connectivity, no matter whether it is over cellular or over Wi-Fi can be shared with a PC over USB. It's called USB tethering and can be activated in the tethering menu as shown on the left.

To make sure Wi-Fi is used as the backhaul, go to flight mode and only enable Wi-Fi on the smartphone. On the PC, disable Wi-Fi connectivity. Once the smartphone is connected to the Wi-Fi network, connect it to the PC and activate USB tethering if not already done. And that's it, your smartphone is now acting as a USB Wi-Fi dongle for your PC.

Note: I'm not sure if Windows requires a driver for this to work but on Ubuntu this works out of the box. But who uses Windows at the 32C3 anyway…

The 4-Bit Nibbler CPU and Bitscope for Layer 1 Logic Analysis Fun

Nibbler-bitscope-smAfter a closer look at how to program the 4-Bit Nibbler CPU and how to cope with its intentional limitations it was time to go one step further and have a closer look at how the hardware works one layer further down. To see the signals and how they propagate through the system a logic analyzer is needed with as many inputs as possible to trace digital signals at different places. Unfortunately, most logic analyzers I found are not cheap, costing several hundred euros even for entry level models. Another alternative would have been to buy a cheap clone hardware from China and then use it with software from the original vendor. As I don't think that's fair I never considered that approach either. But thanks to the January 2016 edition of the Linux Voice magazine I stumbled across the Bitscope Micro, a 2 channel low cost oscilloscope and 8 channel logic analyzer that costs around 120 Euros, tax and shipping included. That's quite in the range of what I was willing to spend. In addition they offer their software for Windows, the Mac and also for Linux. In other words, a perfect match for my needs.

Bitscope screenshotThe logic analyzer can sample digital signals at a rate of up to 40 MSamples/s, enough to have a decent resolution for my Nibbler board running at 2.4 MHz. Any channel can be used as a trigger with rising and falling flanks or a high and low signal level so it's possible to capture signals at a specific moment. The picture and screenshot on the left shows the Bitscope Micro connected to the Nibbler and a commented screenshot that shows how instructions are read from the ROM and put into the instruction register two clock cycles later. For the screenshot I used the blinking LED program that just uses 5 instructions to switch the LED on and off again and then jumps back to the beginning of the program. In total that is exactly 10 clock cycles in which the instructions repeat over and over. This way it's easy to find the beginning and the end of the loop when looking at the signal levels. I spent many hours analyzing traces of signals from many different parts to confirm my theoretical knowledge of how the control unit, clock and phase make the system "come alive". A wonderful exercise during which I once again learnt a lot about what makes a computer really tick.

VoLTE Roaming – S8HR in 3GPP S8HR TR 23.749

In Ocotober 2015, NTT Docomo was the first network operator who has started VoLTE Roaming based on a pre-standard implementation of the S8 Home Routing (S8HR) concept. I wrote about it at the time and speculated how they might have implemented the service as there was little official technical documentation available. In the meantime, 3GPP has continued their investigation of what is necessary to fully standardize the S8-HR concept and the details can be found in Technical Report (which is not a specification, it's just a report) TR 23.749 for 3GPP Release 14 (!). In December 2015, version 1.0.0. of the document was published that contains a number of interesting insights into what is already available and what is still missing in the specifications depending on which features an operator wants to use for VoLTE S8HR Roaming.

Dedicated Bearers for voice packets possible: At the time I wrote that if a network operator wants to play things purely on his own, VoLTE Roaming can be deployed without any interaction with the visited network operator except for the need, of course, to have a general LTE roaming requirement in place. If some more cooperation between home and visited network is put in place it is even possible to assign a dedicated bearer for voice packets by the IMS system in the home network to prefer voice packets in the network and especially on the air interface.

As shown in TR 23.749 in figure 4-2.1 this works without any additional specification work as the PCRF (Packet Control Resource Function) in the home network is told by the VoLTE IMS system in the home network to establish a dedicated bearer. The PCRF then talks to the Packet Gateway (P-GW) in the home network which in turn forwards the request to the Serving Gateway (S-GW) in the visited network. From there it goes to the LTE base station (eNodeB) and from there to the mobile device. In principle it is the same message flow as in a non-roaming scenario but the roaming interconnect has to let such configuration messages pass between P-GW and S-GW. The big advantage of the approach is that the VoLTE client on the mobile device does not have to behave differently when roaming abroad, i.e. there is no need for it to decide whether it has to wait for a dedicated bearer for the voice packets or not before proceeding the call.

Single Radio Voice Call Continuity: One of the main drawbacks off S8-HR VoLTE roaming that it is more difficult to put a mechanism in place to switched over from an IP-based LTE bearer to a circuit switched 2G or 3G channel at the edge of LTE coverage. TR. 23.749 points out that from an architectural point of view, no additional specifications are necessary for SR-VCC to work across borders in a Release 8 SR-VCC configuration. I presume, however, that quite a number of network operators have already gone to a post-Release 8 SR-VCC implementation in the network which has a number of additional components to speed up the process. For this setup, SR-VCC across borders is not possible with the current specification. Interestingly enough the 3GPP technical report excludes discussions of potential solutions from the document. In other words, it seems to be complicated enough to be put into a separate TR. It would be interesting to know of Docomo has actually implemented SR-VCC for their S8HR VoLTE roaming with Korea or if they just went ahead without it as LTE coverage is said to be pretty much deployed everywhere in Korea in the meantime anyway so there's no need for it in the first place.

There are two other topics discussed in the technical report, how emergency calls could be made properly and how to best signal to the VoLTE IMS system that the device is not at home but roaming in another country. Falling back to 2G or 3G cellular for emergency calls is a quick and working solution but the report also gives some details of how it could be done over VoLTE. If you are interested have a look at the document.

While the document had a few positive surprises for me it by and large confirms that S8HR VoLTE roaming should not be too difficult to implement and I wonder how long it will take for other network operators to follow Docomo's lead!?