Monday, 13 February 2012

Fast Dormancy Timings

Nearly a year and half back, I posted a blog about Fast Dormancy here. This issue has surely been fixed in most of the devices and the networks are able to handle the issue even if the handsets have not been fixed. I found an interesting table in a Huawei journal that shows the timings used by different devices that are being reproduced for people who may be interested.

Sunday, 12 February 2012

Discussion on 'Offload' and 'Onload'



An interesting discussion on Twitter about Offload and Onload that is reproduced below. Discussions have been edited for clarity:


@StevenJCrowley: Exhibit 1: In last year's VNI, Cisco estimated that in 2014, 23% of US mobile data would be offloaded. It's close to 50% today.


@dmavrakis: it depends how you define offload. Some of this 50% may be simple WiFi access rather than offload.

@StevenJCrowley: From what I see I'd suggest Wi-Fi (or femto) access is offload if the device is 2,3,4G capable but does not access a macrocell


@dmavrakis: So if I buy a SIM-only handset and not even put a SIM in and use WiFi, it's considered offload?


@StevenJCrowley: Seems to me that's not considered offload because without a SIM it's not a 2,3,4G capable device.


@StevenJCrowley: BTW my old AT&T iPhone 3G won't work as a Wi-Fi-only device without an old inactive SIM still in it. Don't know about iPhone 4.


@disruptivedean: I agree with @dmavrakis . Most smartphone WiFi use if "private WiFi", not offload. Some may even be onload (or "OTT WiFi")

@disruptivedean: Easy way to think of it: anything you'd do on an iPod Touch isn't offload WiFi if you do the same thing on iPhone


@disruptivedean: Other example: if I use WiFi to connect my phone to my printer (or corp WLAN) = traffic never destined for 2G/3G


@simonchapman: app downloads (500MB+ for some games), AirPlay etc are much greater than 2/3/4G use. Where is 50% figure from? 


@SteveLightley: the actual presence of decent connectivity encourages higher capacity activity. Is that offload?


@disruptivedean: I refer to extra use as "elastic". See chart on p18 of my Carrier WiFi paper http://www.scribd.com/doc/61910980/Disruptive-Analysis-Carrier-WiFi


@StevenJCrowley: Decent connectivity / more use is offload, as 3G4G w/o Wi-Fi is onload. U.S./FCC/Cisco perspective


@StevenJCrowley: I define "onload" as a 2nd operator capturing traffic via WiFi, eg Vodafone handset + O2 WiFi app


@dmavrakis: Also core network onload via WLAN gateways without local breakout.


@disruptivedean: A thought about "offload". I only "onloaded" to 3G data on my PC in the first place because WiFi wasn't everywhere I needed it. Now it is.


@StevenJCrowley: 50% rough estimate. AT&T said 40% of iPhone traffic on Wi-Fi in early 2010. Its Wi-Fi network data tripled since


@StevenJCrowley: Does not include femto offload. See also "#2" from this blog post bit.ly/wxHvRl


@StevenJCrowley: AT&T recently said macrocell data growth down to 40% a year.


@StevenJCrowley: I like Dean's chart. Offloading important in U.S. from 4G spectrum requirements issue.


@StevenJCrowley: And here spectrum debate is more political than technical, thus broad brushes.


@StevenJCrowley: It's basically, "We need spectrum to stream NetFlix." "No, you're inside and can use Wi-Fi."


@StevenJCrowley: Dean's and Ofcom's analyses are the types of things current FCC should be doing but doesn't


@disruptivedean: The whole spectrum reqts issue likely to take a hit as data growth << expected on many networks. S-curve not exponential


@disruptivedean: To be fair, Cisco is between a rock & a hard place with VNI. Scared people into making sure it didn't come true. Self-denying


@Gabeuk: To everyone discussing offload on my Twitter today, the premise seems wrong... connectivity & access is the start point. Will elaborate l8er


@SteveLightley: I struggle to understand how if it would never have happened how it can be classed as offloaded


@SteveLightley: a VoIP call on an ott or mno app IS offload but Netflix in Starbucks over wifi is not


@SteveLightley: looking forward to gabe's view on access etc when he gets here! 


@TMFAssociates: AT&T seems to have changed its tune over the last year as well http://gigaom.com/broadband/atts-vanishing-spectrum-crisis/


@StevenJCrowley: AT&T will spin it. "If only we had more spectrum we could have sent more data." Etc.


@dmavrakis: Arguably spectrum is the MNO's most valuable possession. Isn't it natural that they want more?


@StevenJCrowley: More spectrum than needed is an idle asset that costs the company money.


@TMFAssociates: But if you corner the market then you can foreclose the possibility of competition


@dmavrakis: I agree conditionally. Twitter is again not the best medium for this discussion

Couple of interesting posts related to the above:



What is your opinion?

Friday, 10 February 2012

Men are like Bluetooth, Women are like...

One for the weekend:


Is this true?

Thursday, 9 February 2012

Evolution towards ALL-IP Single RAN (SRAN)




Presented by Matthias Sauder and Dr. Volker Sebastian, VodafoneD2 GmbH in the 2nd FOKUS FUSECO Forum 2011, Berlin 17-18 Nov. 2011

Saturday, 4 February 2012

Adding new dimensions to the future phones - Smell

I am going to be involved in two events in the coming months to discuss about Evolution of Devices in the future. The first of them is the LTE World Summit that I have been going to for years and have recommended to lots of clients, colleagues and friends. In there I will be discussing about 'The Future Device' in the Breakfast briefing. In June I am chairing a session on 'Where Next For Devices' in The Future of Wireless International Conference. As a result I would be discussing some ideas on the blog with the intention of getting some valuable feedback and comments.

Smell has been associated with the mobile devices for a long time. There are two concepts floating around. The first is a phone that can smell the environment for certain odour or harmful gases and depending on what it smells, alerts the user or some authority. An example of this are the phones being developed by US Department of Homeland Security to smell poisonous gases. Another example is the e-nose concept developed by Imec, Belgium. There are other concepts being developed around m-health to help people with Asthma.

The second of these concepts are the devices that can emit smell. The simplest form of this would be like the Sony phones that emit fragrance for a few months and then a new sheet can be inserted for them to keep emitting a fragrance. A while back it was reported that Samsung has filed a patent for something similar.


Nokia had shown years back the 'Scentsory Concept' mobile that can transmit smell based on the environment to the other party who can get the feeling of where the other person is. Since then they have shown other concepts but I dont recall seeing much on smell. The 'HumanForm' concept I blogged about last year showed that we would be able to feel the environment but it was surprisingly quiet about smell part.

There is an interesting TEDx video in which Jenny Tillotson, who would be presenting her latest research in the Future Wireless conference mentioned abaove, is explaining some of these concepts on transmitting smell electronically. Video embedded below:



I would be very interested in hearing more on this topic from the readers.

Wednesday, 1 February 2012

The intelligent pipe and next-generation billing


Presented by Marc Price, VP of Technology, CTO Americas in the LTE North America 2011 conference

See also the earlier posts on Policy and Charging here and here.

Monday, 30 January 2012

More on Policy and Charging in LTE

Continuing on the Policy and Charging in LTE from the previous post here.




Presented by Erik P. Neitzel, DMTS, Technology Development Group, U.S. Cellular in the LTE North America 2011 conference

Sunday, 29 January 2012

Standardisation on M2M at ETSI M2M platform

Presented by Marylin Arndt, ETSI TC M2M Vice-Chairman in the 2nd FOKUS FUSECO Forum 2011, Berlin 17-18 Nov. 2011

Saturday, 28 January 2012

Thursday, 26 January 2012

Diameter Infrastructure Required for LTE (Data) Roaming


Diameter protocol seems interesting especially since we are moving to All IP Networks. This old post gives a comparison of SS7 and Diamater protocol.

You can learn more about Diameter at the Diameter Learning Center.

Wednesday, 25 January 2012

Introduction of HSS in the LTE

Click on the pic to enlarge

Interesting slides from E-Plus Mobilfunk GmbH & Co. KG presented in FUSECO Forum 17th-18th November 2011, Berlin.

Tuesday, 24 January 2012

LTE Base station equipment


If interested, more details available in the NTT Docomo whitepaper here.

Monday, 16 January 2012

HSPA vs LTE

Interesting report to remind the differences between HSPA and LTE available here.

Monday, 9 January 2012

Overview of LTE Handovers


From the NTT Docomo Technical journal:


The LTE handover is broadly divided into a backward handover (PS handover) and forward handover. In the former, the network performs cell switching and notifies the mobile terminal of the destination cell, and in the latter, the mobile terminal performs autonomous switching to pick up the destination cell.


To control packet loss due to a momentary cutoff at the time of radio switching, PS handover supports a data forwarding process that transfers undelivered data from the switching-source eNodeB to the switching-destination eNodeB and a reordering process that corrects sequencing mistakes between forwarded data and new data.


The forward handover can be classified into Release with Redirection triggered by a cutoff signal from the network and Non Access Stratum (NAS) Recovery in which the mobile terminal autonomously performs a NAS recovery, either of which is accompanied by data loss due to a momentary cutoff. From a different perspective, handover can be classified in the following two ways according to whether it is accompanied by Radio Access Technology (RAT) or frequency switching or by eNodeB or EPC switching (Figure 7).


1) Intra-RAT handover: This is a handover that occurs within the LTE system in which node transition occurs between sectors within an eNodeB, between eNodeBs within an EPC switch, or between EPC switches. 


A handover between eNodeBs within an EPC switch may be an X2 or S1 handover. In an X2 handover, signal processing is performed by the X2 logical interface between eNodeBs, while in an S1 handover, signal processing is performed by the S1 logical interface between an eNodeB and the EPC switch. There is a tradeoff between the cost of maintaining an X2 link and the cost incurred by an S1 handover, and operations are configured accordingly.


Handover can also be classified by whether the center frequency is the same before and after handover, that is, whether the handover occurs within the same frequency or between frequencies.


2) Inter-RAT handover: This is a handover that occurs between RATs either as a transition from LTE to 3G or from 3G to LTE.

A detailed post on LTE to 3G Inter-RAT handover is available here.

Thursday, 5 January 2012

IEEE standards impacting the future home


Interesting graphic from IEEE-SA depicting various IEEE standards impacting the home - via Steven Crowley on Twitter

Friday, 16 December 2011

Release 12 study item on Continuity of Data Sessions to Local Networks (CSN)

LIPA was defined as part of Release-10 that I have already blogged about. Imagine the situation where a user started accessing local network while camped on the Home eNode B (aka Femtocell) but then moved to the macro network but still wants to continue using the local network. Release 12 defines this feature and is called Continuity of Data Sessions to Local Networks (CSN). This study item was originally part of Release 11 but has now been moved to Rel-12.



From SP-100885:


Justification
Basic functionality for Local IP Access (LIPA) has been specified in Rel-10.
LIPA signifies the capability of a UE to obtain access to a local residential/enterprise IP network (subsequently called a local network) that is connected to one or more H(e)NBs.
The current study item investigates extending LIPA functionality to allow access to the local network when a UE is under coverage of the macro network and provide related mobility support.

LIPA allows a UE to work with devices in the local network – e.g. printers, video cameras, or a local web-server. If the local network offers services that enable exchange of digital content (e.g. UPnP) LIPA allows the UE to discover supporting devices and to be discovered.
Examples for services that become available by LIPA are:
·         The pictures stored in a UE’s digital camera may be uploaded to a local networked storage device or printed out at a local printer.
·         A portable audio player in the UE may fetch new content from a media centre available on the local network.
·         A UE may receive video streams from local surveillance cameras in the home.
·         A local web-server in a company’s intranet may be accessed by the UE.
·         Support of VPN.
LIPA does not require the local network to be connected to the Internet but achieves IP connectivity with the UE through one or more H(e)NBs of the mobile operator.
In Release 10  3GPP has only specified the support of LIPA when the UE accesses the local network via H(e)NB.
On the other hand an operator may, e.g. as a chargeable user service, wish to provide access to the local network also to a UE that is under coverage of the macro network. Access to the local network when a UE is under coverage of the macro network should be enabled in Rel-11.

In Rel-10 it had been required for a UE to be able to maintain IP connectivity to the local network when moving between H(e)NBs within the same local network.
However, access to the local network may be lost as a UE moves out of H(e)NB coverage into the macro network, even if other services (e.g. telephony, data services, SIPTO) survive a handover to the macro network and are continued. This may result in an unsatisfactory user experience.
The current study item will allow continuation of data sessions to the local network when the UE moves between H(e)NB and the macro network.

Therefore, in Rel-11, the 3GPP system requires additional functionality to allow
·         A UE to access the local network from the macro network
·         A UE to maintain continuity of data sessions to the local network when moving between a H(e)NB and the macro network

Objective:              to propose requirements and study feasibility for the following scenarios:
Provide a capability to the mobile operator to allow or restrict
­        Access to an enterprise/residential IP network when a UE is under coverage of the macro network, assuming that the IP address of the local IP network (e.g. residential/enterprise gateway) is available to the UE.
­        Continuity of data session(s) to an enterprise/residential IP network when a UE moves between a H(e)NB in an enterprise/residential environment and the macro network.
The support of Continuity of Data Sessions to Local Networks should be an operator option that may or may not be provided by individual PLMNs.

Service Aspects
The user should be able to decline access to the local network from the macro network. The user should also be able to decline continuity of data sessions to local networks when moving between H(e)NB and the macro network (e.g. in the case when data sessions to local networks is charged differently if accessed from macro coverage or via the H(e)NB).
A difference in QoS may be noticeable by the user when the local network is accessed from the macro network or via the H(e)NB.

Wednesday, 14 December 2011

ETSI INT IMS/EPC Interoperability Standardisation: Motivation, Roadmap & First Results

INT = IMS Network Testing. ETSI INT website here. More details below the presentation:

This was presented by Giulio Maggiore, Telecom Italia, ETSI TC INT Chairman in the 2nd FOKUS FUSECO Forum 2011, Berlin 17-18 Nov. 2011

From the ETSI leaflet (note that this is quite old information but still on the ETSI website here):

IMS interoperability is a key issue for boosting IMS (IP Multimedia Subsystem) roll-out and more specifically network interconnection between operators. Only through thorough testing in practical scenarios can operators ensure operational excellence in a multi-vendor and multi-provider environment.


IMS comprises a set of specifications designed to enable network operators to implement IP-based networks that can carry services for both fixed and mobile customers simultaneously.


IMS was developed originally in the mobile world (specifically in the specifications created by the 3rd Generation Partnership Project, 3GPP), and was adopted for fixed networks by ETSI’s TISPAN Technical Committee (Telecoms & Internet Converged Services & Protocols for Advanced Networks).


However this promise of advanced communications over the next generation network will only be delivered if those same networks can interconnect.


ETSI’s Technical Committee INT: IMS Network Testing


ETSI is bridging the existing gap between 3GPP IMS Core Network standards and the initial industry IMS implementations through the organization of IMS interoperability events in connection with ETSI’s Centre for Testing & Interoperability (CTI) and Plugtests™ interoperability testing service.


Our Technical Committee for IMS Network Testing (TC INT) is actively establishing close contact with a number of industry fora and organizations dealing with IMS interoperability, including 3GPP, GSMA, MSF (Multi Service Forum), IMS Forum and the ITU-T. TC INT develops IMS test specification according to conformance, network integration and interoperability testing methodologies. Other ongoing work includes development of tests for Supplementary Services based on regulatory requirements and IMS tests with legacy networks (e.g. SIP-I).


ETSI has already held two IMS interoperability events. The first examined interconnection aspects of 3GPP IMS Release 6, including such issues as basic call on the Mw interface. The second event had a wider scope that included the testing of 3GPP IMS Release 7 interworking, roaming, border control, and integration of application servers executing selected Multimedia Telephony supplementary services.


Future ETSI activities and events will go even deeper towards bridging 3GPP IMS standards and industry implementations. These will include the organization of further IMS interoperability events designed to boost the roll-out and take-off of IMS services and operators’ network interconnections.

AT&T on Distributed Antenna System (DAS)


From the 4th LTE North America Conference, 8 - 9 November 2011, Dallas, Texas, USA

More about DAS on Wikipedia here.

Sunday, 11 December 2011

How Mobile Broadband users use their data allowance


Interesting picture of what MBB users use their data allowance on. Interesting to see that Social Networking is far popular in the North America whereas Real-time entertainment is much more popular in APAC. It is understandable that the downstream Real-time entertainment would contain of VOD services like Youtube and Hulu but not sure what Upstream would consist of. 

Tuesday, 6 December 2011

Proximity-based Services (ProSe) - New Study Item in 3GPP Rel-12


There is a new Rel-12 WI "Study on Proximity-based Services" with Qualcomm being the main proponent of this. This was earlier known as D2D (Device-to-device). From the 3GPP SP-110638:

Justification: Proximity-based applications and services represent a recent and enormous socio-technological trend. The principle of these applications is to discover instances of the applications running in devices that are within proximity of each other, and ultimately also exchange application-related data. In parallel, there is interest in proximity-based discovery and communications in the public safety community.


Current 3GPP specification are only partially suited for such needs, since all such traffic and signalling would have to be routed in the network, thus impacting their performance and adding un-necessary load in the network. These current limitations are also an obstacle to the creation of even more advanced proximity-based applications.


In this context, 3GPP technology, has the opportunity to become the platform of choice to enable proximity-based discovery and communication between devices, and promote a vast array of future and more advanced proximity-based applications.


Objective: The objective is to study use cases and identify potential requirements for an operator network controlled discovery and communications between devices that are in proximity, under continuous network control, and are under a 3GPP network coverage, for:
1. Commercial/social use
2. Network offloading
3. Public Safety
4. Integration of current infrastructure services, to assure the consistency of the user experience including reachability and mobility aspects
Additionally, the study item will study use cases and identify potential requirements for
5. Public Safety, in case of absence of EUTRAN coverage (subject to regional regulation and operator policy, and limited to specific public-safety designated frequency bands and terminals)


Use cases and service requirements will be studied including network operator control, authentication, authorization, accounting and regulatory aspects.


The study does not apply to GERAN or UTRAN.

In the past I have mentioned about Qualcomm's proprietary Flashlinq technology that seems to contain lots of similarities. There is also this AllJoyn technology that Qualcomm has been showing off since MWC. Here is a video of that:



There is a lot of potential of this proximity marketing technology mostly for marketing purposes and games. In the end it would depend of the Apps, services and charging based around this. There is also a big possibility for TV and VoD services where you start watching something on your device but then transfer it onto a TV or just a bigger screen.

Monday, 5 December 2011

A Golden Next-Gen Hetrogeneous Device


From the 4th LTE North America Conference, 8 - 9 November 2011, Dallas, Texas, USA
Presented by Joe Lawrence, Vice President, CDMA Development Group (CDG)

UE Antenna Sizes on different frequencies


The biggest problem with Antennas for mobiles and now the tablets have been how to arrange antennas for MIMO since the wavelength needs to be λ/4. The picture gives an idea how the antenna size changes with different frequencies. Higher frequencies are better for having multiple antennas as their length and the distance between then decreases.

From a presentation by Shirook M. Ali, RIM in the 4th LTE North America Conference, 8 - 9 November
2011, Dallas, Texas, USA.

Wednesday, 30 November 2011

Reducing CSFB Timing with RRC R9 Optimisations

While in the initial testing CSFB timing used to be between 6-8 seconds, most Rel-8 phones can complete the CSFB procedure between 4-4.5 seconds. Unfortunately this is still a lot in terms of signalling. To reduce this in Rel-9 there is a simple optimisation that has been done.
In the RRC Connection Release message, there is a possibility to add UTRAN/GERAN System Information messages. In the picture above, I have only shown UTRA System Information but a similar picture can be drawn for GERAN.

Once all the Mandatory SIB's are sent to the UE then it can immediately camp on without the need to read any other additional system info. This will reduce the CSFB time between 1-2 seconds.

The lesser the CSFB time, the better the Quality of end user experience

Tuesday, 29 November 2011

Nice Pie Chart on different Android Devices

Click to enlarge

I guess Pie charts like these can convey more information then writing about the percentages of devices sold. Maybe we should use them more often to represent information.

Source: From a presentation by Deutsche Bank in the 4th LTE North America Conference, 8 - 9 November 2011, Dallas, Texas, USA