LBO or not, I want to break out...
This article was written by Peter Nas, Senior Solution Architect of F5's Traffix SDC solution For more than 10 years, the technology to offer local breakout (commonly known as LBO) exists, allowing the data use by roaming customers to be supported by the visited operator’s network. This is in contrast to the scenario in which data requests are sent back to the roamer’s home network, which of course, costs more. But despite the obvious fact that many people would like to get lower data roaming rates, a wish not limited to Europeans traveling in the EU, sadly it is not offered yet. I can definitely understand some key arguments why mobile operators are not inclined to offer LBO, particularly when it applies to their subscriber. I also understand (a bit) that visited networks don't want to offer LBO, but let's see if we are about to see a change. After all, roaming has been a significant source of revenue for operators on both sides for some time now. When I worked at a MNO over 10 years ago, I did some testing myself to see if and how LBO works. At the time, I became very enthusiastic and never expected it would take so long before this technology would be deployed on a large scale. In the early days of GPRS, indeed data roaming rates were also very high. However in those days, roamers used their mobile phones for data much more infrequently than when in their home network. And if you have been observing the investments that have been made by mobile operators and GRX operators (GPRS roaming operators) to allow good quality data roaming, I can understand that these investments need to be earned back before the business could consider offering LBO. In the meanwhile, I believe that many things have changed and surveys have shown that customers consider data roaming far too expensive. As a result, roamers typically switch off their data while traveling abroad (some recent figures show 73% of the roamers as silent roamers, meaning while abroad but disabled their device for data roaming). Now the EU Roaming Regulations, in effect since July 2014, is explicitly mandating EU citizens to have the right to use LBO (when offered by the visited EU network), and VoLTE (Voice over LTE) is expected to be available. Therefore, we are approaching the inflection point during which LBO will be a realistic option for roamers. If I was an IPX carrier how should I approach LBO? Today all users’ data is backhauled via IPX carriers to the home network. IPX carriers have various sources of revenues and transporting users’ data is one important source of revenues. Currently, the main advantage to use IPX carriers seems to be the ease of connectivity among MNOs. However, people expect prices for pure transport to decrease making new and differentiating services the way IPX carriers can stay competitive and valuable. It is simply a matter of time that IPX carriers will offer a wide range and the right destinations of roaming agreements that will bring prices down. So while anticipating that operators are willing to pay less per transported bit... and remaining confident in the escalating trend of high data growth in the future, would I advise MNOs to invest heavily in more transport capacity or try to be innovative by leveraging wide-scale LBO usage? Let’s look at it this way. Assume an MNO can achieve service differentiation by looking at what opportunities LBO would bring. Well similarly, there are opportunities around LBO for IPX carriers which must be looked at as LBO will reduce revenues from backhauled data. One interesting aspect of LBO is that the signaling for two additional Diameter interfaces, S9 for policy and Gy for charging, could be exchanged between visited and home networks, and if so, this will be done via an IPX network as per GSMA guidelines (IR.88). There are different views on whether or not using the S9 interface to exchange policy information between the visited PCRF and home PCRF, will be massively used once LBO is offered, but let's assume it will be used. In this case, an IPX carrier can offer various services around Diameter interworking, security and perhaps also screening, overload control, prioritization and potentially adapting policy rules and more. People who doubt the uptake of using the S9 interface might be more interested if IPX carriers could offer services that help visited networks control which policies can be applied in the home network or in the visited network. The offering around S9 signaling can be the same as what is currently offered for transporting and managing S6a signaling (for authentication and mobility management), but offers security, quality, and many more differentiating features. Another very interesting Diameter interface is the Gy, related to charging. Once LBO is offered, the visited network will have primary control of charging the visitor (for example to offer various ways how a customer can be charged, like per credit card, voucher, scratch card, loyalty points, other credits from OTT applications, etc.) but there is also interest by the home network to receive charging information. Again, an IPX carrier can offer various innovative services beyond just transporting Gy charging information between visited network and home network. As we discuss charging information, what comes to mind are the potential of services in the areas of security, priority, firewalling, interworking, overload control, enriching, for example. If you think about other creative services that a mobile customer like myself would like to have while roaming, there are more services that an IPX carrier is well positioned to offer. For instance, perhaps I’d like to choose the visited network that best fits to my needs (there could be static rules but also dynamic rules). For instance, intelligent steering in roaming could be a service offered by the home network, but perhaps might be offered by an IPX carrier, at least as an outsourcing partner for the various aspects of having a new Diameter based solution next to potentially existing SS7 steering. Some other ideas are in the area of OTT apps, such as enabling an IPX carrier to provide value add to the QoE of the apps that I am using while abroad. Also when looking at LBO, it might be an IPX carrier that hosts other parties who want to offer LBO, or the IPX carrier itself can provide its 'own' LBO services via a local breakout gateway that reduces the costs (in region or on the other side of the world). Also IPX carriers can start to offer MVNE services that enable MVNOs to operate in their specific niche by providing the infrastructure and other services around it. Much more value-add can be added by IPX carriers, and some will become a commercial success and others maybe not.... but if you don't explore, you'll never know. Let’s discuss some other value-add ideas in more detail in a next post, so stay tuned.518Views0likes1CommentWhy do you need a Diameter Routing Agent (DRA) in a VoLTE deployment?
This article was written by Peter Nas, Senior Solution Architect for the Traffix SDC Operators have begun to get more and more serious around deploying VoLTE (Voice over LTE) in their networks. Since the announcements of VoLTE services from some Korean and US operators, others, particularly in Asia, North America and EMEA, have launched or are about to launch VoLTE (see GSA announcement of 17th Sep 2014: 71 operators in 36 countries investing in VoLTE deployments, studies or trials, 10 operators commercially launched HD voice using VoLTE). More often than not, operators use a Diameter Routing Agent (DRA) to support correct routing and control of the Diameter signaling related to VoLTE. Basic session binding In 3GPP, a DRA is defined for session binding in IP-CAN sessions (equivalent to PDP context in 3G) towards a PCRF server. This was designed for multiple Diameter sessions in VoLTE in order to control the LTE and the IMS parts of the VoLTE service. To maintain an efficient and scalable network rollout, it is important that the LTE parts of an IMS VoLTE call, together with the IMS parts, are controlled by one and the same PCRF (server). Similarly, consistent policy rules need to be applied to the session that are related to the same VoLTE call. Let's explore in some more detail what needs to be managed by the same PCRF server and why. When using a VoLTE-enabled device, the mobile subscriber first needs to register to the network and establish the default data bearer to exchange data with the network or applications. This is followed by the authentication and authorization procedures, and mobility management communication between an MME and the HSS where the subscriber profile is stored. (Incidentally, the signaling for these procedures typically uses the Diameter S6a interface that is also often routed with help of a DRA). Now this device can establish the always-on LTE default user data bearer. In order to do so the device communicates with the PGW and establishes a user data session. For that user data session, in this case still the default bearer, the PGW needs to contact the PCRF via the Diameter Gx interface and receive the policy and charging rules for this customer's data session. Once the policies have been exchanged and applied by the PGW and sometimes there are other involved PCEFs (Policy and Charging Enforcement Function), the mobile user can either use Internet services via the established default bearer or in our scenario, opts to continue to establish a VoLTE call. To do so the VoLTE application on the handset will communicate (via SIP, over the established default LTE bearer) with the IMS network and its embedded VoLTE application server. First a SIP signaling bearer needs to be established after policy for that bearer is applied. To apply the policy, the IMS's P-CSCF needs to communicate via the Diameter Rx interface with a PCRF server. Actually, it needs to communicate with the same PCRF server that was already involved in managing the related LTE default bearer. This is exactly where the added-value of a DRA's session binding functionality becomes necessary, because the DRA has to search its memory for the same PCRF server that was used in the Gx session for that specific customer (e.g. specific IMSI and session ID). It has to match the unique and related information in the Rx signaling in order to make the same routing decision and end up at the same PCRF server. The relevant IMS information is the Framed-IP address because IMSIs are not usually required in IMS. A smart DRA has stored in its memory the association between an IMSI and Session-ID plus the Framed-IP address used by the device. If now that same Framed-IP address shows up in an IMS Diameter Rx message, a match can be made and the same routing decision can be applied. Now once the Diameter Gx for the LTE part and the Diameter Rx for the IMS part are bound to the same PCRF server we are almost there. Next comes the exchange and application of the policy and charging rules for the SIP Signaling bearer. And now we can move to the third key component of the VoLTE call and that is the SIP signaled voice. For voice signaling, the same PCRF server needs to be addressed, and the related IMS signaling is again exchanged via the Diameter Rx interface. Finally, once the policies and charging have been exchanged and applied, the VoLTE call can be made successfully. If there is a need for changing the policy or charging rules (for instance, if a customer reaches a certain threshold), than the same PCRF server can communicate via Gx to the LTE's PCEFs and via Rx to the involved IMS elements like the P-CSCF. In this way, the various sessions that are related to the same VoLTE service are managed consistently. Also when the VoLTE call is terminated the various sessions need to be released, except for the LTE default bearer, and the correlation between the LTE and IMS part of this VoLTE call can be cancelled. Other DRA added-value in VoLTE There’s additional value to the fundamental session binding functionality of a DRA. A DRA can enable optimal call management ensuring higher quality-of-service VoLTE calls. For instance, think of all the different vendors’ equipment that is needed to exchange Diameter Gx and Rx signaling. One example is when the LTE PGW has a different Gx implementation than the PCRF. In turn that PCRF can have a different Diameter Rx implementation than the IMS's P-CSCF node. Typically inside an operator's network, there will be various vendors for LTE, PCRF and IMS core network elements. And this is the norm in roaming use cases where the visited LTE network is out of control (meaning a different vendor) than the home IMS network, where the P-CSCF (and other elements) will be involved. In addition, once VoLTE takes off more substantially, the quantity of signaling also will take off and increase dramatically. Therefore, a DRA will play the most significant role in providing load balancing and overload control, both in normal circumstance but clearly also under special circumstances like when network elements went down and recover or other heavy signaling loads are occurring. A DRA could also prioritize VoLTE related signaling, over all the various Diameter interfaces. When serving this function, operators can provide a higher quality VoLTE service over other services, particularly when other services load the network. In this case, a network without this DRA functionality of prioritization, would experience degraded VoLTE service. There are more added-value functionalities – all made possible by a DRA, like VoLTE specific KPI generation. As time goes on and we experience increased use of VoLTE, we will learn more and more about how a DRA can improve the quality and efficiency of VoLTE and its related services. Peter Nas serves as Senior Solution Architect for the Traffix SDC team at F5 Networks and draws from more than 20 years of telecom experience to advise operators how to leverage Diameter signaling solutions to enable the optimal LTE experience. Peter joined F5 with the company’s acquisition of Traffix where he was responsible for global business development. Prior to joining Traffix, he worked at Tekelec focusing on market development for Diameter and SIP routing. In his days before Tekelec, he served as Core Network Engineering Manager at a prominent mobile operator in the Netherlands.4.7KViews0likes2CommentsDiameter - SS7 IWF - Bridging the Signals between New and Old Worlds
This is written by a Guest Blogger,Ohad Ramot, Principal Software Engineer at F5 Indeed, LTE (4G) networks are spreading rapidly and are being deployed all over the globe. However, most of the networks out there are based on 2G/3G technology, and it seems they’re here to stay for awhile. This requires operators and roaming mediators (IPX) to face the challenge of maintaining and interacting with both network architectures in parallel. 4G networks are growing, while 2G/3G networks still serve most of the subscribers as they have been doing successfully for the last decades. 4G and 2G/3G network architectures differ in many aspects. One of these differences is the signals mechanism which allows network nodes to interact with each other for authentication, billing, subscriber profile provisioning and more. While 2G/3G signaling mechanism is based on SS7 protocol stack, 4G networks use the relatively modern Diameter protocol on top of TCP/SCTP/IP stacks. Although both signaling methods provide solution to the same set of problems, they stem from different architectures and design philosophies. As a result, many 2G/3G network elements cannot interact directly and seamlessly with 4G network elements. A solution is needed for all those cases where this inter-network communication is required. Common examples for such scenarios could be: A 4G subscriber who roams to a foreign 3G network. In this case, the hosting 3G network needs to interact with the home 4G network of this subscriber. The same could be if a 3G subscriber who owns a device supporting 4G roams to a 4G network. The device will connect locally to the 4G hosting network, which will need to interact with the home 3G network. An operator which starts deploying a new 4G network, but still didn’t cover all areas while its 4G subscribers might be in geographical areas where only 3G coverage is available. An interworking Function (IWF) solution enables an LTE network to have an extension towards an SS7 network. It provides the capability to translate Diameter signals to their corresponding signals on MAP and vice versa. This translation is based on 3GPP organization specification. However, the challenges faced during the development were not only “translate this attribute on MAP to that AVP on Diameter” but involved the different behavior of the application, for example, a DRA like our F5 Signaling Delivery Controller (SDC) has to behave like a 4G network node when it interacts with a 4G network, while simultaneously behaving like a 2G/3G network node, on its other interface. An example for this “behavioral translation” (which is beyond mere protocol conversion) are some flows of simple Diameter transaction of Request-Answer, which turn into complex flows containing several requests and answers dialog between IWF and its SS7 peer. Some of these different behavioral aspects were not even covered or defined in any spec and we had to invent our own ways to implement them. And as always, keeping the future in mind, our current design of the solution has enough flexibility to be enhanced for some more SS7-wise applications besides mere Diameter-SS7 interworking. One example of such enhancement is enabling our SDC to act as an enhancement of 3G STP for smart manipulations of MAP messages, which the latter cannot do. Another example is to make SDC translate RADIUS authentication on requests from Wi-Fi domain to 3G HLR on traditional telephony domain. To summarize, the development process of such an application gives developers the opportunity to be pioneers, creatively think of solutions and overcome new challenges. We believe that having the F5 SDC act as a bridge between the new and the old worlds of telephony signaling enables F5 to enlarge and strengthen our footprint in this very important domain.213Views0likes0CommentsNeutered net-neutrality and Diameter signaling
Some parts of the media and concerned internet users are up in arms about the recent ruling on the FCC’s net-neutrality regulations, preventing the agency from ensuring that all web traffic is treated equally. Their concern is understandable. No one wants to be in a situation where service providers routinely throttle traffic based on commercial agreements or even political views. The nightmare scenario is that ISPs become de facto dictators of the internet and control the flow of information unimpeded. However, if handled sensitively, there is a great opportunity for service providers to make use of policy enforcement and Diameter signalling management solutions to enhance the quality of service to users. There are always mobile consumers who would be very willing to pay for ensured quality as their communications are of premium value to them. Yet, although service quality is one thing, they are not interested in a service provider influencing the content that they view. And their fears aren’t entirely unfounded, particularly when we look at how operators have treated OTT services in the past – throttling traffic that was competitive to their own offers. However we have seen, anecdotally at least, that service providers are starting to take another look at OTT services as potential partners; either to attract customers with bundled subscription deals (for example Spotify premium membership) or for revenue sharing deals. It’s this approach which I think is more indicative of which way service providers will fall on their treatment of net-neutrality. Imagine, for example, that you frequently use mobile Skype video calls for work purposes. Unfortunately Skype calls do occasionally lose resolution or drop out altogether, which would be a terrible experience and loss for businesses and consumers that depend on it. For subscribers in this position it may be worth the extra expense to ensure that Skype data is treated differently to the rest of the data they use. Paying for assured quality of service (QoS) can make enormous sense for some services without deliberately hindering other data. Paying for a premium service which guarantees a higher Quality of service according to a specific paid-for policy is made possible by a combination use of Diameter signalling controllers and policy enforcement.. In conjunction, they enable the network to identify the subscriber and level of policy, and ensure the subscriber receives the quality of service provisioned for. An approach like this is a compelling value proposition for subscribers and provides a strong business case for service providers while, at the same time, respecting the central principles of net-neutrality. Net-neutrality is an important concept for a censorship free and open internet, but there is no reason that it cannot co-exist as a philosophy with the benefits that enhanced quality of service can provide.231Views0likes0Comments