Showing posts with label QoS. Show all posts
Showing posts with label QoS. Show all posts

Tuesday, October 12, 2021

Thursday, April 20, 2017

5G: Architecture, QoS, gNB, Specifications - April 2017 Update


The 5G NR (New Radio) plan was finalised in March (3GPP press release) and as a result Non-StandAlone (NSA) 5G NR will be finalised by March 2018. The final 3GPP Release-15 will nevertheless include NR StandAlone (SA) mode as well.

NSA is based on Option 3 (proposed by DT). If you dont know much about this, then I suggest listening to Andy Sutton's lecture here.


3GPP TR 38.804: Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Interface Protocol Aspects provides the overall architecture as shown above

Compared to LTE the big differences are:

  • Core network control plane split into AMF and SMF nodes (Access and Session Management Functions). A given device is assigned a single AMF to handle mobility and AAA roles but can then have multiple SMF each dedicated to a given network slice
  • Core network user plane handled by single node UPF (User Plane Function) with support for multiple UPF serving the same device and hence we avoid need for a common SGW used in LTE. UPF nodes may be daisy chained to offer local breakout and may have parallel nodes serving the same APN to assist seamless mobility.

Hat tip Alistair Urie.
Notice that like eNodeB (eNB) in case of LTE, the new radio access network is called gNodeB (gNB). Martin Sauter points out in his excellent blog that 'g' stands for next generation.

3GPP TS 23.501: Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 provides architecture model and concepts including roaming and non-roaming architecture. I will probably have to revisit as its got so much information. The QoS table is shown above. You will notice the terms QFI (QoS Flow Identity) & 5QI (5G QoS Indicator). I have a feeling that there will be a lot of new additions, especially due to URLLC.

Finally, here are the specifications (hat tip Eiko Seidel for his excellent Linkedin posts - references below):
5G NR will use 38 series (like 25 series for 3G & 36 series for 4G).

RAN3 TR 38.801 v2.0.0 on Study on New Radio Access Technology; Radio Access Architecture and Interfaces

RAN1 TR 38.802 v2.0.0 on Study on New Radio (NR) Access Technology; Physical Layer Aspects

RAN4 TR 38.803 v2.0.0 on Study on New Radio Access Technology: RF and co-existence aspects

RAN2 TR 38.804 v1.0.0 on Study on New Radio Access Technology; Radio Interface Protocol Aspects

38.201 TS Physical layer; General description
38.211 TS Physical channels and modulation
38.212 TS Multiplexing and channel coding
38.213 TS Physical layer procedures
38.214 TS Physical layer measurements
38.21X TS Physical layer services provided to upper layer
38.300 TS Overall description; Stage-2
38.304 TS User Equipment (UE) procedures in idle mode
38.306 TS User Equipment (UE) radio access capabilities
38.321 TS Medium Access Control (MAC) protocol specification
38.322 TS Radio Link Control (RLC) protocol specification
38.323 TS Packet Data Convergence Protocol (PDCP) specification
38.331 TS Radio Resource Control (RRC); Protocol specification
37.3XX TS [TBD for new QoS]
37.3XX TS Multi-Connectivity; Overall description; Stage-2
38.401 TS Architecture description
38.410 TS NG general aspects and principles
38.411 TS NG layer 1
38.412 TS NG signalling transport
38.413 TS NG Application Protocol (NGAP)
38.414 TS NG data transport
38.420 TS Xn general aspects and principles
38.421 TS Xn layer 1
38.422 TS Xn signalling transport
38.423 TS Xn Application Protocol (XnAP)
38.424 TS Xn data transport
38.425 TS Xn interface user plane protocol
38.101 TS User Equipment (UE) radio transmission and reception
38.133 TS Requirements for support of radio resource management
38.104 TS Base Station (BS) radio transmission and reception
38.307 TS Requirements on User Equipments (UEs) supporting a release-independent frequency band
38.113 TS Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)
38.124 TS Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment
38.101 TS User Equipment (UE) radio transmission and reception
38.133 TS Requirements for support of radio resource management
38.104 TS Base Station (BS) radio transmission and reception
38.141 TS Base Station (BS) conformance testing

Note that all specifications are not in place yet. Use this link to navigate 3GPP specs: http://www.3gpp.org/ftp/Specs/archive/38_series/

Further reading:

Monday, September 26, 2016

QoS in VoWiFi

Came across this presentation by Eir from last year's LTE Voice Summit.



As the summary of the above presentation says:
  • Turning on WMM (or WME) at access point provides significant protection for voice traffic against competing wireless data traffic
  • Turning on WMM at the client makes only a small difference where there are a small number of clients on the wireless LAN. This plus the “TCP Unfairness” problem means that it can be omitted.
  • All Home gateways support WMM but their firmware may need to be altered to prioritise on DSCP rather than layer two

As this Wikipedia entry explains:

Wireless Multimedia Extensions (WME), also known as Wi-Fi Multimedia (WMM), is a Wi-Fi Alliance interoperability certification, based on the IEEE 802.11e standard. It provides basic Quality of service (QoS) features to IEEE 802.11 networks. WMM prioritizes traffic according to four Access Categories (AC): voice (AC_VO), video (AC_VI), best effort (AC_BE), and background (AC_BK). However, it does not provide guaranteed throughput. It is suitable for well-defined applications that require QoS, such as Voice over IP (VoIP) on Wi-Fi phones (VoWLAN).

WMM replaces the Wi-Fi DCF distributed coordination function for CSMA/CA wireless frame transmission with Enhanced Distributed Coordination Function (EDCF). EDCF, according to version 1.1 of the WMM specifications by the Wi-Fi Alliance, defines Access Categories labels AC_VO, AC_VI, AC_BE, and AC_BK for the Enhanced Distributed Channel Access (EDCA) parameters that are used by a WMM-enabled station to control how long it sets its Transmission Opportunity (TXOP), according to the information transmitted by the access point to the station. It is implemented for wireless QoS between RF media.

This blog post describes how the QoS works in case of WMM.



Finally, this slide from Cisco shows how it will all fit together.

Further reading:

Sunday, May 22, 2016

QCI Enhancements For Mission Critical Communications

Its been quite a while since I posted about QCI and end-to-end bearer QoS in EPC. In LTE Release-12 some new QCI values were added to handle mission critical communications.


This picture is taken from a new blog called Public Safety LTE. I have discussed about the Default and Dedicated bearers in an earlier post here (see comments in that post too). You will notice in the picture above that new QCI values 65, 66, 69 & 70 have been added. For mission critical group communications new default bearer 69 would be used for signalling and dedicated bearer 65 will be used for data. Mission critical data would also benefit by using QCI 70.


LTE for Public Safety that was published last year provides a good insight on this topic as follows:

The EPS provides IP connectivity between a UE and a packet data network external to the PLMN. This is referred to as PDN connectivity service. An EPS bearer uniquely identifies traffic flows that receive a common QoS treatment. It is the level of granularity for bearer level QoS control in the EPC/E-UTRAN. All traffic mapped to the same EPS bearer receives the same bearer level packet forwarding treatment. Providing different bearer level packet forwarding treatment requires separate EPS bearers.

An EPS bearer is referred to as a GBR bearer, if dedicated network resources related to a Guaranteed Bit Rate (GBR) are permanently allocated once the bearer is established or modified. Otherwise, an EPS bearer is referred to as a non-GBR bearer.

Each EPS bearer is associated with a QoS profile including the following data:
• QoS Class Identifier (QCI): A scalar pointing in the P-GW and eNodeB to node-specific parameters that control the bearer level packet forwarding treatment in this node.
• Allocation and Retention Priority (ARP): Contains information about the priority level, the pre-emption capability, and the pre-emption vulnerability. The primary purpose of the ARP is to decide whether a bearer establishment or modification request can be accepted or needs to be rejected due to resource limitations.
• GBR: The bit rate that can be expected to be provided by a GBR bearer.
• Maximum Bit Rate (MBR): Limits the bit rate that can be expected to be provided by a GBR bearer.

Following QoS parameters are applied to an aggregated set of EPS bearers and are part of user’s subscription data:
• APN Aggregate Maximum Bit Rate (APN-AMBR): Limits the aggregate bit rate that can be expected to be provided across all non-GBR bearers and across all PDN connections associated with the APN.
• UE Aggregate Maximum Bit Rate (UE-AMBR): Limits the aggregate bit rate that can be expected to be provided across all non-GBR bearers of a UE. The UE routes uplink packets to the different EPS bearers based on uplink packet filters assigned to the bearers while the P-GW routes downlink packets to the different EPS bearers based on downlink packet filters assigned to the bearers in the PDN connection.

Figure 1.5 above shows the nodes where QoS parameters are enforced in the EPS system.

Related links:



Thursday, October 30, 2014

Codecs and Quality across VoLTE and OTT Networks

Codecs play an important role in our smartphones. Not only are they necessary and must for encoding/decoding the voice packets but they increase the price of our smartphones too.

A $400 smartphone can have as much as $120 in IPR fees. If you notice in the picture above its $10.60 for the H.264 codec. So its important that the new codecs that will come as part of new generation of mobile technology is free, open source or costs very little.


The new standards require a lot of codecs, some for backward compatibility but this can significantly increase the costs. Its important to make sure the new codecs selected are royalty-free or free license.

The focus of this post is a presentation by Amir Zmora from AudioCodecs in the LTE Voice Summit. The presentation below may not be self-explanatory but I have added couple of links at the bottom of the post where he has shared his thoughts. Its worth a read.



A good explanation of Voice enhancement tools as follows (slide 15):

Adaptive Jitter Buffer (AJB) – Almost all devices today (Smartphones, IP phones, gateways, etc.) have built in jitter buffers. Legacy networks (which were LAN focused when designed) usually have older devices with less sophisticated jitter buffers. When designed they didn’t take into account traffic coming in from networks such as Wi-Fi with its frequent retransmissions and 3G with its limited bandwidth, in which the jitter levels are higher than those in wireline networks. Jitter buffers that may have been planned for, say, dozens of msec may now have to deal with peaks of hundreds of msec. Generally, if the SBC has nothing to mediate (assume the codecs are the same and the Ptime is the same on both ends) it just forwards the packets. But the unexpected jitter coming from the wireless network as described above, requires the AJB to take action. And even if the network is well designed to handle jitter, today’s OTT applications via Smart Phones add yet another variable to the equation. There are hundreds of such devices out there, and the audio interfaces of these devices (especially those of the Android phones) create jitter that is passed into the network. For these situations, too, the AJB is necessary.

To overcome this issue, there is a need for a highly advanced Adaptive Jitter Buffer (AJB) built into the SBC that neutralizes the incoming jitter so that it is handled without problem on the other side. The AJB can handle high and variable jitter rates.

Additionally, the AJB needs to work in what is called Tandem scenarios where the incoming and outgoing codec is the same. This scenario requires an efficient solution that will minimize the added delay. AudioCodes has built and patented solutions supporting this scenario.

Transcoding – While the description above discussed the ability to bypass the need to perform transcoding in the Adaptive Jitter Buffer context, there may very well be a need for transcoding between the incoming and outgoing packet streams. Beyond being able to mediate between different codecs on the different networks on either end of the SBC, the SBC can transcode an incoming codec that is less resilient to packet loss (such as narrowband G.729 or wideband G.722) to a more resilient codec (such as Opus). By transcoding to a more resilient codec, the SBC can lower the effects of packet loss. Transcoding can also lower the bandwidth on the network. Additionally, the SBC can transcode from narrowband (8Khz) to wideband (16Khz) (and vice versa) as well as wideband transcoding, where both endpoints support wideband codecs but are not using the same ones. For example, a wireless network may be using the AMR wideband codec while the wireline network on the other side may be using Opus. Had it not been for the SBC, these two networks would have negotiated a common narrowband codec.

Flexible RTP Redundancy – The SBC can also use RTP redundancy in which voice packets are sent several times to ensure they are received. Redundancy is used to balance networks which are characterized by high packet loss burst. While reducing the effect of packet loss, Redundancy increases the bandwidth (and delay). There are ways to get around this bandwidth issue that are supported by the SBC. One way is by sending only partial packet information (not fully redundant packets). The decoder on the receiving side will know how to handle the partial information. This process is called Forward Error Correction (FEC).

Transrating – Transrating is the process of having more voice payload ‘packed’ into a single RTP packet by increasing the packet intervals, thus changing the Packetization Time or Ptime. Ptime is the time represented by the compression of the voice signals into packets, generally at 20 msec intervals. In combining the payloads of two or more packets into one, the Transrating process causes a reduction in the overhead of the IP headers, lowering the bandwidth and reducing the stress on the CPU resources, however, it increases delay. It thus can be used not only to mediate between two end devices using different Ptimes, but also as a means of balancing the network by reducing bandwidth and reducing CPU pressure during traffic peaks.

Quality-based Routing – Another tool used by the SBC is Quality-based routing. The SBC, which is monitoring all the calls on the network all the time, can decide (based on pre-defined thresholds and parameters) to reroute calls over different links that have better quality.

Further reading:

Sunday, June 30, 2013

Multi-RAT mobile backhaul for Het-Nets

Recently got another opportunity to hear from Andy Sutton, Principal Network Architect, Network Strategy, EE. His earlier presentation from our Cambridge Wireless event is here. There were many interesting bits in this presentation and some of the ones I found interesting is as follows:

Interesting to see in the above that the LTE traffic in the backhaul is separated by the QCI (QoS Class Identifiers - see here) as opposed to the 2G/3G traffic.




This is EE's implementation. As you may notice 2G and 4G use SRAN (Single RAN) while 3G is separate. As I mentioned a few times, I think 3G networks will probably be switched off before the 2G networks, mainly because there are a lot more 2G M2M devices that requires little data to be sent and not consume lots of energy (which is an issue in 3G), so this architecture may be suited well.


Finally, a practical network implementation which looks different from the text book picture and the often touted 'flat' architecture. Andy did mention that they see a ping latency of 30-50ms in the LTE network as opposed to around 100ms in the UMTS networks.


Mark Gilmour was able to prove this point practically.

Here is the complete presentation:



Monday, June 6, 2011

Billing based on QoS and QoE

With Spectrum coming at a price the operators are keen to make as much money as possible out of the data packages being provided to the consumers. The operators want to stop users using over the top (OTT) services like Skype thereby losing potential revenue. They also want the users to stop using services that are offered by the operator thereby maximising their revenue.

A valid argument put forward by the operators is that 90% of the bandwidth is used by just 10% of the users. This gives them the reason to look at the packets and restrict the rogue users.

As a result they are now turning to deep packet inspection (DPI) to make sure that the users are not using the services they are being restricted to use. AllOt is one such company offering this service.

The following presentation is from the LTE World Summit:



They also have some interesting Videos on the net that have been embedded below. They give a good idea on the services being offered to the operators.



Finally, a term QoS and QoE always causes confusion. Here is a simple explanation via Dan Warren on twitter:

QoS = call gets established and I can hear what is being said, everything else is QoE

Friday, April 29, 2011

Service Layer Optimization element to Improve Utilisation of Network Capacity


The following is an extract from 4G Americas whitepaper, "Optimizing the Mobile Application Ecosystem":


Applications have diverse requirements on the mobile network in terms of throughput, relative use of uplink vs. downlink, latency and variability of usage over time. While the underlying IP based Layer 3 infrastructure attempts to meet the needs of all the applications, significant network capacity is lost to inefficient use of the available resources. This inefficiency stems primarily from the non-deterministic nature of the aggregate requirements on the network from the numerous applications and their traffic flows live at any time.

This reduction in network utilization can be mitigated by incorporating application awareness into network traffic management through use of Application or Service Layer optimization technologies. A Service Layer optimization solution would incorporate awareness of:

1) device capabilities such as screen size and resolution;
2) user characteristics such as billing rates and user location;
3) network capabilities such as historic and instantaneous performance and;
4) application characteristics such as the use of specific video codecs and protocols by an application such as Video on Demand (VOD) to ensure better management of network resources.

Examples of Service Layer optimization technologies include:
* Real-time transcoding of video traffic to avoid downlink network congestion and ensure better Quality of Experience (QoE) through avoidance of buffering
* Shaping of self-adapting traffic such as Adaptive Streaming traffic through packet delay to avoid downlink network congestion
* Shaping of error-compensating flows such as video conferencing through use of packet drops to avoid uplink network congestion
* Shaping of large flows such as file uploads on the uplink through packet delays to conserve responsiveness of interactive applications such as web browsing
* Explicit caching of frequently accessed content such as video files on in-network CDNs to minimize traffic to backbone
* Implicit caching of frequently accessed content such as images in web content on in-network caches to improve web page retrieval speeds

Service Layer optimization technologies may be incorporated in the data path in many locations:
1) the origin server;
2) the UE device;
3) as a cloud-hosted offering through which devices and/or applications and/or networks route traffic or;
4) as a network element embedded in a service provider’s network.

Further, in a service provider’s network the optimization function may be deployed in either the core network and/or edge aggregation locations. When Service Layer optimization entities in the network are deployed at both core and edge locations, they may operate in conjunction with each other to form a hierarchy with adequate level of processing to match the traffic volume and topology. Such a hierarchy of network entities is especially effective in the case of caching.

The 3GPP standard network architecture defines a number of elements such as QoS levels that are understood and implemented in the network infrastructure. However, much of this network capability is not known or packaged for use in the Service Layer by application developers. One approach to resolving this discrepancy may be to publish standard Service Layer APIs that enable application developers to request network resources with specific capabilities and also to get real-time feedback on the capabilities of network resources that are in use by the applications. Such APIs may be exposed by the network to the cloud or may be exposed to application clients resident on mobile devices through device application platforms and SDKs. The network APIs being defined by the Wholesale Application Community are an example of the recognition of the need for such Service Layer visibility into network capabilities. Future versions of the WAC standards will likely incorporate and expose network Quality of Service (QoS) capabilities.



Pic Source: Aria Networks


Why does Optimization matter? A good answer to this question is provided in Telecoms.com article as follows:

For many people, says Constantine Polychronopoulos, founder and chief technology officer of mobile internet infrastructure specialist Bytemobile, the definition of optimisation as it relates to mobile networks is too narrow; restricted to compressing data or to the tweaking of the radio access network in a bid to improve throughput. While these are key elements of optimisation, he says, the term ought to be interpreted far more broadly. “The best way for us to think of optimisation,” he says, “is as a set of synergistic technologies that come together to address everything that has to do with improving network and spectrum utilisation and user experience. If you stretch the argument, it includes pretty much every thing that matters. This holistic, end-to-end approach to optimisation is the hallmark of Bytemobile’s solutions. Point products tend to be costly and difficult or impossible to evolve and maintain.”

And optimisation matters, he says, because the boom in mobile data traffic experienced in some of the world’s most advanced mobile markets represents a serious threat to carrier performance and customer satisfaction. US operator and pioneer iPhone partner AT&T is a case in point, Polychronopoulos says.

“If you look at what’s been said by Ralph de la Vega (president and CEO of AT&T Mobility) and John Donovan (the firm’s CTO), they have seen a 5,000- per cent increase in data traffic over the past two years. The data points from other operators are similar,” he continues. “They see an exponential growth of data traffic with the introduction of smartphones, in particular the iPhone.”

Operators may have received what they’d been wishing for but the scale of the uptake has taken them by surprise, Polychronopoulos says. The type of usage consumers are exhibiting can be problematic as well. Bytemobile is seeing a great deal of video-based usage, which can often be a greater drain on network resource than web browsing. Given the increasing popularity of embedding video content within web pages, the problem is becoming exacerbated.

Dr. Polychronopoulos is keen to point out that there are optimisation opportunities across different layers of the OSI stack—Bytemobile offers solutions that will have an impact on layers three (the IP layer) through seven (the application layer). But he stresses that some of the most effective returns from optimisation technologies come from addressing the application layer, where the bulk of the data is to be found.

“An IP packet can be up to 1,500 bytes long,” he says. “So at layer three, while you can balance packet by packet, there is only so much you can do to optimise 1,500 bytes. At the top layer, the application can be multiple megabytes or gigabytes if you’re watching video. And when you’re dealing with those file sizes in the application layer, there is a whole lot more you can do to reduce the amount of data or apply innovative delivery algorithms to make the content more efficient,” he says.

By optimising content such as video, Polychronopoulos says, significant gains can be made in spectral and backhaul network utilisation. A range of options are open to operators, he says, with some techniques focused on optimising the transport protocol, and others designed to reduce the size of the content.

“With video, we can resize the frame, we can reduce the number of frames, we can reduce the resolution of the frame or apply a combination of the above in a way that does not affect the video quality but greatly improves network efficiencies,” he says. “So if you go to a site like YouTube and browse a video, you might download something like 100MB of data. But if you were to go through a platform like ours, you may download only 50MB when the network is congested and still experience not only the same video quality, but also fluid video playback without constant re-buffering stalls.”

It is possible, he explains, to run these solutions in a dynamic way such that data reduction engages only when the network is congested. If a user seeks to access high-volume data like video during the network’s quiet time, the reduction technologies are not applied. But when things are busier, they kick in automatically and gradually. This could have an application in tiered pricing strategies. Operators are looking at such options in a bid to better balance the cost of provisioning mobile data services with the limited revenue stream that they currently generate because of the flat rate tariffs that were used to stimulate the market in the first place. Being able to dynamically alter data reduction and therefore speed of delivery depending on network load could be a useful tool to operators looking to charge premium prices for higher quality of service, Polychronopoulos says.

If it is possible to reduce video traf- fic in such a way that data loads are halved but the end user experience does not suffer proportionally, the question arises as to why operators would not simply reduce everything, whether the network was busy or not. Polychronopoulos argues that in quiet times there are no savings to be made by reducing the size of content being transported.

“The operator has already provisioned the network one way or another,” he says, “so there is a certain amount of bandwidth and a certain amount of backhaul capacity. When the network is not congested, the transport cost is already sunk. When it becomes congested, though, you get dropped calls and buffering and stalled videos and the user experience suffers. That’s where optimisation shines. Alternatively, media optimisation can be factored in during toplevel network provisioning when the savings in CAPEX can be extremely compelling.”

While LTE is held up by some within the industry as the panacea to growing demand for more mobile broadband service, Polychronopoulos is unconvinced. If anything, he says, the arrival of the fourth generation will serve only to exacerbate the situation.

“LTE is going to make this problem far more pronounced, for a number of reasons,” he says. “As soon as you offer improved wireless broadband, you open the door to new applications and services. People are always able to come up with new ways of inundating any resource, including bandwidth. We’re going to see more data-driven applications on mobile than we see on the typical desktop, because the mobile device is always with you.” And while LTE promises greater spectral efficiency than its 3G forebears, Polychronopoulos says, the fact that spectrum remains a finite resource will prove ever more problematic as services evolve.

“We’re reaching the limits of spectral efficiency,” he says. “Shannon’s Law defines the limit as six bits per Hertz, and while we may be moving to higher-bandwidth wireless broadband, spectrum remains finite. To offer 160Mbps, you have to allocate twice the amount of spectrum than in 3G, and it’s a very scarce and very expensive resource.”

Operators have been wrong to focus exclusively on standards-based solutions to network optimisation issues, Polychronopoulos says. In restricting themselves to 3GPP-based solutions, he argues that they have missed what he describes as “the internet component of wireless data.” Internet powerhouses like Google, Yahoo and Microsoft (which he dubs ‘the GYM consortium’) have established a model that he says is a great threat to the mobile operator community in that it establishes a direct consumer relationship and disregards the “pipe” (wireless broadband connection) used to maintain that relationship.

“The operators have to accelerate the way they define their models around wireless data so that they’re not only faster than the GYM consortium in terms of enabling popular applications, but smarter and more efficient as well,” he says. Dr. Polychronopoulos then makes a popular case for the carriers’ success: “The operators have information about the subscriber that no other entity in the internet environment can have; for example, they know everything the subscriber has done over the lifetime of their subscription and the location of each event. They don’t have to let this data outside of their networks, so they are very well positioned to win the race for the mobile internet.”


Thursday, February 10, 2011

QoS Control based on Subscriber Spending Limits (QOS_SSL)

Quality of Service (QoS) is very important in LTE/LTE-A and the operators are taking extra efforts to maintain the QoS in the next generation of networks. They are resorting in some cases to Deep packet Inspections (DPI) based controlling of packets and in some cases throttling of data for bandwidth hogs.

The following is from a recent 4G Americas report I blogged about here:

This work item aims to provide a mechanism to allow a mobile operator to have a much finer granularity of control of the subscriber’s usage of the network resources by linking the subscriber’s data session QoS with a spending limit. This gives the operator the ability to deny a subscriber access to particular services if the subscriber has reached his/her allocated spending limit within a certain time period. It would be useful if, in addition, the bandwidth of a subscriber’s data session could be modified when this spending level is reached. This could be done depending on, for example, the type of service being used by the subscriber, the subscriber’s spending limit and amount already spent and operator’s charging models. This allows the operator to have an additional means of shaping the subscriber’s traffic in order to avoid subscribers monopolizing the network resource at any given time. Since support for roaming scenarios is needed, the possibility to provide support for roaming subscribers without having dedicated support in the visited network is needed.

Upon triggers based on the operator’s charging models, the subscriber could be given the opportunity to purchase additional credit that increases the spending limit.

The objective of this study is to provide use cases/service requirements and specs that allow:
* Modification of QoS based on subscriber’s spending limits
* Enforcing of spending limits for roaming subscribers without having dedicated support in the visited network

For further details see: 3GPP TS 22.115 Service aspects; Charging and billing (Release 11)

Monday, October 25, 2010

NGMN Top 10 Operational Efficiency Recommendations

Setting up and running networks is a complex task that requires many activities, including planning, configuration, Optimization, dimensioning, tuning, testing, recovery from failures, failure mitigation, healing and maintenance. These activities are critical to successful network operation and today they are extremely labour-intensive and hence, costly, prone to errors, and can result in customer dissatisfaction. This project focuses on ensuring that the operators’ recommendations are incorporated into the specification of the 3GPP O&M (and similar groups in other standardisation bodies) so that this critical task moves towards full automation.

The overall objective is to provide operators with the capability to purchase, deploy, operate and maintain a network consisting of Base Stations (BTS) and “Access Gateways (AGw)” from multiple vendors. The NGMN project Operational Efficiency OPE has taken the task to elaborate solutions and recommendations for pushing the operational efficiency in NGMN networks and has produced recommendations on standards and implementations. The NGMN OPE project also influenced strongly the setup of a TOP10 document reflecting main recommendations in operational area. This document (embedded below) binds these two sources which are anyhow strongly linked together into one common NGMN recommendation document.


Thursday, August 12, 2010

Whitepaper: Traffic Management Techniques for Mobile Broadband Networks


The report, Traffic Management Techniques for Mobile Broadband Networks: Living in an Orthogonal World,focuses on 3GPP networks and concerns itself specifically with traffic management, including the handling of traffic flows on 3GPP networks in contrast with other network management techniques that operators may deploy (such as offloading, compression, network optimization and other important mechanisms).

Mobile broadband networks are confronted by a number of challenges. In particular, the physical layer in mobile networks is subject to a unique confluence of unpredictable and unrelated, or “orthogonal,” influences. Moreover, mobile broadband networks have some important differences from their fixed brothers and sisters, which lead to different traffic management requirements. Among the most significant differences for purposes of traffic management is the need for more granular visibility to circumstances on the ground. Optimally, traffic management for mobile broadband networks requires visibility to what is occurring (by device or application) at the cell site level and in a timeframe that enables as far as feasible near-time reactions to resolve issues.

With the consumer in mind, an End-to-End (E2E) view of mobile service is critical for traffic management. For example, a consumer using a mobile phone to look up movie listings and purchase tickets considers the E2E service as the ability to see what movie is playing and execute a transaction to purchase tickets. 3GPP has endeavored to standardize increasingly more robust traffic management (Quality of Service, or QoS) techniques for mobile broadband networks with a consumer’s E2E view of QoS. It must be considered, however, that mobile operators typically do not have full control over E2E provisioning of services that depend on mobile broadband Internet access.

Global standards organizations like 3GPP play an important role in the development of traffic management through provisions for addressing QoS, particularly regarding interworking with non-3GPP access mechanisms. These are important new innovations, and the 3G Americas white paper notes that the efforts of standards development organizations should be intensified.

In addition, the configuration of end-user devices and content and applications not provisioned by the network operator not only impacts the experience of the particular user, but potentially other users in a particular cell as well. Efforts to drive further QoS innovations should be mindful of potentially adverse impacts from these sources and support and foster interoperability of third party applications with existing network platforms.

More innovations are needed throughout the mobile broadband ecosystem, in particular by application developers, in order to realize E2E quality of service. Furthermore, transparency in network management practices is important in fostering innovation, but requires a careful balancing to ensure consumer comprehension while safeguarding network reliability. Organizations with technical expertise such as 3G Americas are prepared to help to illuminate and progress the development of these new technologies.

“3G Americas stands ready to assist interested parties in the ongoing development and understanding of traffic management techniques,” said Chris Pearson, President of 3G Americas. “We are mindful that in this hemisphere and elsewhere, the industry has accepted an increasingly active role in addressing questions about service levels and innovation on mobile broadband networks.”

The white paper, Traffic Management Techniques for Mobile Broadband Networks: Living in an Orthogonal World, was written collaboratively by members of 3G Americas and is available for free download on the 3G Americas website at www.3gamericas.org.

Friday, July 23, 2010

Shunning mobiles in favour of Landlines


I guess its time to clean the cobwebs off the landlines. I was reading David Chambers analysis on Homezone tarrifs and it reminded me of the time when I would get big bundle of voice minutes to call using my mobile from home. In those days the voice quality seemed better, signal strength indicator was high and there were hardly any dropped calls.

Nowadays, the signal strength seems to have gone worse whether I am in the office or at home, the voice on the calls keeps breaking, there are too many dropped calls.

To give you an idea of what's going wrong; My phone kept stationary at the table has 4 bars strength of 3G/HSPA, it suddenly becomes 1 bar after 2-3 minutes then hands me over to what the phone says GPRS then the phone says EDGE. If the phone says EDGE then my calls drop within 2 minutes. If my phone says GPRS then I am worried that if it hands over to 3G then my call will drop. If the phone says 3G then unless there are 3 bars, the voice breaks.

Last week I used my landline phone after maybe a year or so and that reminded me how good the voice quality is. In theory the voice quality using mobile phone should be as good as the landline but in practice that may not be true. Of course the wideband AMR can offer much better HD voice but I need reliable voice more than HD voice.

So for the time being, I am going to be sticking with the landlines as far as possible due to reliable and clear communications and wait for the mobiles/networks to catch up.