Showing posts with label M2M. Show all posts
Showing posts with label M2M. Show all posts

Friday, 16 November 2012

Evolution of 'Internet of Things' to 'Internet of Everything' #IoE



Will the 'Internet of Humans' and the 'Internet of Things' (IoT) evolve into 'Internet of Everything' (IoE). This is certainly what Dave Evans, the Cisco Futurist thinks. This is from his blog:


From the Internet of Things (IoT), where we are today, we are just beginning to enter a new realm: the Internet of Everything (IoE), where things will gain context awareness, increased processing power, and greater sensing abilities. Add people and information into the mix and you get a network of networks where billions or even trillions of connections create unprecedented opportunities and give things that were silent a voice.

As more things, people, and data become connected, the power of the Internet (essentially a network of networks) grows exponentially. This thinking (“Metcalfe’s law”) comes from Robert Metcalfe, well-known technologist and founder of 3Com, who stated that the value of a network increases proportionately to the square of the number of users. In essence, the power of the network is greater than the sum of its parts, making the Internet of Everything, incredibly powerful.


You can read more here.

See Also:


Tuesday, 16 October 2012

Extended Access Barring (EAB) in Release 11 to avoid MTC overload

M2M is going to be big. With the promise of 50 Billion devices by 2020, the networks are already worried about the overloading due to signalling by millions of devices occurring at any given time. To counter this, they have been working on avoiding overloading of the network for quite some time as blogged about here.

The feature to avoid this overload is known as Extended Access Barring (EAB). For E-UTRAN, in Rel-10, a partial solution was implemented and a much better solution has been implemented in Rel-11. For GERAN a solution was implemented in Rel-10. The following presentation gives a high level overview of EAB for E-UTRAN and GERAN.



In Rel-11, a new System Information Block (SIB 14) has been added that is used specifically for EAB. Whereas in Rel-10, the UE would still send the RRCConnectionRequest, in Rel-11, the UE does not even need to do that, thereby congesting the Random Access messages.

The following is from RRC 36.331 (2012-09)
***

–                SystemInformationBlockType14

The IE SystemInformationBlockType14 contains the EAB parameters.
SystemInformationBlockType14 information element
-- ASN1START

SystemInformationBlockType14-r11 ::= SEQUENCE {
    eab-Param-r11                        CHOICE {
       eab-Common-r11                       EAB-Config-r11,
       eab-PerPLMN-List-r11                 SEQUENCE (SIZE (1..6)) OF EAB-ConfigPLMN-r11
    }                                                  OPTIONAL, -- Need OR
    lateNonCriticalExtension             OCTET STRING          OPTIONAL, -- Need OP
    ...
}

EAB-ConfigPLMN-r11 ::=               SEQUENCE {
    eab-Config-r11                   EAB-Config-r11            OPTIONAL -- Need OR
}

EAB-Config-r11 ::=               SEQUENCE {
    eab-Category-r11                 ENUMERATED {a, b, c, spare},
    eab-BarringBitmap-r11            BIT STRING (SIZE (10))
}

-- ASN1STOP

SystemInformationBlockType14 field descriptions
eab-BarringBitmap
Extended access class barring for AC 0-9. The first/ leftmost bit is for AC 0, the second bit is for AC 1, and so on.
eab-Category
Indicates the category of UEs for which EAB applies. Value a corresponds to all UEs, value b corresponds to the UEs that are neither in their HPLMN nor in a PLMN that is equivalent to it, and value c corresponds to the UEs that are neither in the PLMN listed as most preferred PLMN of the country where the UEs are roaming in the operator-defined PLMN selector list on the USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN, see TS 22.011 [10].
eab-Common
The EAB parameters applicable for all PLMN(s).
eab-PerPLMN-List
The EAB parameters per PLMN, listed in the same order as the PLMN(s) occur in plmn-IdentityList in SystemInformationBlockType1.

***

Here is my attempt to explain the difference in overload control mechanism in Rel-8, Rel-10 and Rel-11. Please note that not actual message names are used.





As usual, happy to receive feedback, comments, suggestions, etc.

Monday, 15 October 2012

Machine Type Communications (MTC): Architecture, Features, Standards in 3GPP Rel-10



The following 14 MTC Features have been identified during the 3GPP Release-10 timelines:


  • Low Mobility
  • Time Controlled
  • Time Tolerant
  • Packet Switched (PS) Only
  • Small Data Transmissions
  • Mobile Originated Only
  • Infrequent Mobile Terminated
  • MTC Monitoring
  • Priority Alarm Message (PAM)
  • Secure Connection
  • Location Specific Trigger
  • Network Provided Destination for Uplink Data
  • Infrequent Transmission
  • Group Based MTC Features




In Rel 10, 3GPP will focus on the general functionality required to support these features:

  • Overload control (Radio Network Congestion use case, Signalling Network Congestion use case and Core Network Congestion use case)
  • Addressing
  • Identifiers
  • Subscription control
  • Security



The following specifications are associated with the MTC work

Spec   - Specifications associated with or affected by MTC work
22.011 - Service accessibility
22.368 - Service requirements for Machine-Type Communications (MTC); Stage 1
23.008 - Organization of subscriber data
23.012 - Location management procedures
23.060 - General Packet Radio Service (GPRS); Service description; Stage 2
23.122 - Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
23.203 - Policy and charging control architecture
23.401 - General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access
23.402 - Architecture enhancements for non-3GPP accesses
23.888 - System improvements for Machine-Type Communications (MTC)
24.008 - Mobile radio interface Layer 3 specification; Core network protocols; Stage 3
24.301 - Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3
24.368 - Non-Access Stratum (NAS) configuration Management Object (MO)
25.331 - Radio Resource Control (RRC); Protocol specification
29.002 - Mobile Application Part (MAP) specification
29.018 - General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification
29.060 - General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface
29.118 - Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification
29.274 - 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3
29.275 - Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3
29.282 - Mobile IPv6 vendor specific option format and usage within 3GPP
31.102 - Characteristics of the Universal Subscriber Identity Module (USIM) application
33.868 - Security aspects of Machine-Type Communications
36.331 - Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification
37.868 - RAN Improvements for Machine-type Communications
43.868 - GERAN Improvements for Machine-type Communications
44.018 - Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol
44.060 - General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol
45.002 - Multiplexing and multiple access on the radio path


Here are couple of presentations I have extracted the above information from:



Tuesday, 25 September 2012

LTE, M2M Device Addressing and IMSI


I was made aware of the following statement on the Verizon wireless brochure:

LTE’s inherent support for IPV6 addressing and IMSI-based telephone number identifiers makes mass deployments over LTE more easily achievable. The deployment of large numbers of mobile devices (think tens of thousands) becomes much more feasible because of LTE’s use of 15-digit IMSI telephone number identifiers for large-scale deployments, such as M2M or embedded wireless applications. 3G network technologies were limited by their use of 10-digit telephone number identifiers, which made large-scale deployments more difficult. With LTE, mass deployment of wireless services and applications, such as VoIP, smart metering, vending, and telematics, is now practical.

Now we know about the much touted 50 Billion connections by 2025 of which the majority would be M2M devices. So how are we going to handle the issue of addressing these many devices.

In the earlier presentation here, there was a mention of the direction for the solution as below:





The IMSI structure is as shown above. So depending on how it is used this can help alleviate the number shortage problem. 3GPP TR 23.888 gives the following information:


5.13      Key Issue - MTC Identifiers

5.13.1    Use Case Description

The amount of MTC Devices is expected to become 2 orders of magnitude higher than the amount of devices for human to human communication scenarios. This has to be taken into account for IMSI, IMEI and MSISDN. Regulatory bodies indicate shortages of IMSIs and MSISDNs.
The MTC Feature PS Only in TS 22.368 [2] includes a requirement that PS Only subscriptions shall be possible without an MSISDN. In principle an MSISDN is not used in any of the PS based signalling procedures. However, it will have to be assured that all PS procedures indeed work and subscriptions can be uniquely identified without providing an MSISDN. Furthermore, TS 22.368 [2] specifies that remote MTC Device configuration shall be supported for PS only subscriptions without an MSDISDN assigned. Current remote MTC Device configuration solutions (i.e. Device Management and Over-the-Air configuration) are based on SMS, which assumes the use of MSISDNs. So a solution to support remote MTC Device configuration that does not require the use of MSISDNs is needed.
The identifiers can be categorised into:
-     Internal Identifiers: used within the 3GPP system to identify a UE using a subscription (or the subscription itself e.g. when the UE is not registered).
-     External Identifiers: used from outside the 3GPP system (e.g. at the MTCsp interface), to refer to a UE using a subscription (or the subscription itself e.g. when the UE is not registered).

5.13.2    Required Functionality

-     It shall be possible to uniquely identify the ME.
NOTE 1:   This requirement relates to the ME which is generally identified by the IMEI.
-     It shall be possible to uniquely identify the UE using a subscription or the subscription itself.
NOTE 2:   The two requirements above also apply to human-to-human communications. However, for Machine-Type Communication identifiers will have to be able to cater for a number of identifiers up to two orders of magnitude higher than for human-to-human communications.
-     It shall be possible to use the following identifiers:
1.       IMSI, for internal usage within the 3GPP operator domain, and either
2.       E.164 MSISDN, for usage outside the 3GPP operator domain, or
3.       Unique identifier (e.g. FQDN), other than E.164 MSISDN, for usage outside the 3GPP operator domain.
NOTE 3: Use of IMSI outside the 3GPP operator domain is an operator option (i.e. not subject to standardization)
-     If no (unique or common) MSISDN is assigned to a PS only subscription, the Internal Identifier (IMSI) shall be used as charging identifier.
-     It shall be possible to associate one or more External Identifiers to the same Internal Identifier (e.g. several MSISDNs associated with the same IMSI).
-     Globally unique External Identifiers shall be supported for identifying UEs used for MTC that must be globally reachable (i.e. irrespective of which mobile operator owns the subscription)
-     Operator specific External Identifiers (e.g. based on a private numbering plan) may be supported for identifying UEs used for MTC that have to be reachable only from the operator domain to which they are subscribed.
-     The Internal Identifier shall be globally unique.
-     Remote MTC Device configuration shall still be supported for subscriptions without an MSISDN.
NOTE 4:   Current remote MTC Device configuration solutions (i.e. Device Management and Over-the-Air configuration) are based on SMS, which assumes the use of MSISDNs.


Any more information on this subject, more than welcome.

Monday, 9 July 2012

#FWIC Summary in Tweets with Pics, Presentations and Videos

Here is my summary from The 4th Future of Wireless International Conference (#FWIC). I created a OTT Stats, Facts and Figures presentation for the conference which is available here.


DAY 1

@zahidtg: #FWIC has started



@marekpawlowski: Full house for #fwic, sign of thriving, continually expanding mobile industry in Cambridge





@Qualcomm_UK: "Mobile is the largest technology platform in history" – #Qualcomm’s Joe Barrett at #FWIC keynote

@JawadAbbassi: Globally: 1 million new 3G connections are added on a daily basis. Source: @Qualcomm_IAR

@najeebster: 3.2bn 3G connections by 2016 Joe Barrett from Qualcomm at #FWIC

@geoffmccormick: data traffic to grow over 1000% in the next decade.

@Qualcomm_UK: “Consumers expect the amazing” – Joe Barrett of Qualcomm

@cambwireless: Joe Barrett from @Qualcomm_UK keynote 3.4 billion 3G connections by 2016, 1000 x growth in data by 2020

@Qualcomm_UK: #Snapdragon processors are used by 50+ manufacturers, in 340+ devices with a further 400+ in development – Joe Barrett, Qualcomm

@ndahad: The significance of mobile technologies globally, particularly emerging markets, & more smartphones to the masses http://ow.ly/i/IVvF

@Alliantus: Interesting first session. Powershift. New spectrum. More base stations - smaller & deployed to offload traffic - bring net closer.

@marekpawlowski: Does Qualcomm's Alljoyn hold possibility of internet of things network which meshes to become stronger the more entities which join?

@marekpawlowski: Qualcomm's Halo transferring kw power wirelessly over air gaps to charge cars. A final untethering of humans from power sockets?

@ndahad: Mobile - the digital 6th sense





@Alliantus: very interesting scene setting by #joebarrett #qualcomm one of best conference starts ever - on the button and no sales pitch. FAB.

@dw2: Note to self: learn more about http://www.qualcommhalo.com/ the Qualcomm Halo wireless charging system for cars mentioned by Joe Barrett

@geoffmccormick: biggest challenge for wireless auto charging is not the tech but the system. New behaviours and challenges abound.

@RichardTraherne: Further support for small cells to solve cellular access problems, at Future Wireless International Conference

@zahidtg: Connected car by Qualcomm at #FWIC




@Qualcomm_UK: Hey, @CambWireless #fwic and want to see the video #Qualcomm’s Joe Barrett talked about this morning?:



Joe Baratt's presentation is available here and the video is here.



@bensmithuk: Listening to Olaf Swantee (Everything Everywhere CEO)

@Alliantus: everything everywhere #Olafswantec CEO. Partnering for #4G. Built for data. More speed 4-6 times faster in lab. Latency improved.

@najeebster: Olaf Swantee, CEO, Everything Everywhere reckons this 4G stuff can provide connectivity equal to fixed-line broadband, hmm

@Alliantus: 4G tool for proving connectivity. Part of solution. Data growth rates 250 times in past year - smart phones and smart data.

@roryponeill: CEO Everything Everywhere Olaf Swantee "I'm staggered by the continuing growth of data. We can't cope with 3G...we must go 4G"

@cambwireless: Olaf Swantee, CEO, Everything Everywhere speaks at #fwic "Growth rates of 250% in data on the network every year"

@Alliantus: UK more dependent on services than any other because of service culture. Infrastructure needs to be improved - UK early adopters.

@kumithiru: wonder what percentage of EE's UK customer base using data hungry devices use them at home? 50% 60% 70% ?

@najeebster: 4G carries a stronger signal even cell edge, will help to solve rural broadband issues

@rob_symes: olaf swantee says there would huge job creation by next gen 4G network

@roryponeill: Olaf continues "Britain is reliant on digital service industry - no.1 contributor to GDP - yet 40 other countries have 4G already"

@Alliantus: #fwic reason delay because industry is sweating assets in UK. Big capital expenditure has not come. ROI? Not enough profit? Hard to believe.

@BrianIsATwit: Olaf Swantee #fwic 4G use cases are video, TV and real time gaming. B2B cloud services. M2M also driving new apps.

@BrianIsATwit: Olaf Swantee at #fwic inferring UK economy impacted by poor fixed and mobile broadband. 4G positive investment impact £5bn & 125K new jobs.

@Alliantus: #fwic ironically really poor O2 service here. Blocking tweet on everything everywhere? Or just because it is about #4G?

@Alliantus: role of lawyers in causing delay? Are we destined to be laggards and not leaders because of cyclical nature of Tech adoption?

@Alliantus: can be back on track quickly. Already have a 3G network? Many users think they are on 4G already.

@Alliantus: thought provoking talk. Really believes in focusing on customers. Passion. Making experience better. Good operator perspective.

@marekpawlowski: Refreshing to hear Olaf Swantee prioritising fundamental improvements to network quality over 'tariff gimmicks & loyalty points'

@marekpawlowski: However, concerned by Swantee's faith in 4G to solve rural access. Unlikely economics will be any different than any proceeding 'G'

@marekpawlowski: Challenge for Swantee will be moving from sales culture of pushing 'broadband' & 'smartphone' SKUs, getting closer to customer reality

@cambwireless: Olaf Swantree stresses the economy is dependent on digital infrastructure. 40 countries rolled out 4g already - uk falling behind

@BrianIsATwit: as a rural dweller my fixed and mobile experience terrible. don't doubt 4G capability but do doubt deployment and economics.

No Slides. Video of Olaf Swantee is available here


@Alliantus: #paultaylor #google. Text to speech. Can't tweet because of sensitivity. Confidentiality works both ways Google.

@geoffmccormick: is there an irony in google asking for privacy ??? Txt to voice google insider info coming soon (I hope).

@eurocomms: Interesting... Google engineering manager asks #fwic if his speech can remain confidential ahead of upcoming developer conference

@geoffmccormick: voice input needs visual confirmation. Interesting point made by google.

@eurocomms: Apologies to all those asking re Google at #fwic - WiFi ironically pretty poor... – talk was mainly about developments in speech technology

@Lautarinho: Amusing efforts by Google to keep information at a major conference private it seems.

@Brill_Brum: Muppet!... Google engineering manager asks #fwic if his speech can remain confidential ahead of upcoming developer conference

@rpctelecom: Paul Taylor of Google gave an interesting talk whose title he doesn't want mentioned and said some interesting unreportable things

@rpctelecom: By the way, Paul Taylor of Google needs @connectifyme to solve his hotel Internet multiple-device problems

No Video or Slides for presentation by Paul Taylor, Engineering Manager, Google

ZG: Since the Google I/O 2012 is already over, I dont see why this cannot be shared now. I will add the pictures at the end of this post.

@Alliantus: Interesting panel discussion. Femtocell for capacity? Will we as consumers spend the money themselves?

@cambwireless: Panel session @DavidCleevely pushes femtocell opportunity for new business model

@rupert_baines: @davidcleavely at #fwic on need for #smallcell how femtocells create opportunity & new business model for carriers: economics view not tech

@cambwireless: Panel Session Olaf Swantree says femtocells are part of the equation

@marekpawlowski: Good point about expediting uptake of femto cells by operators recognising & discounting femto use in tariffs. Few currently do.

@JawadAbbassi: 50% of #cellular users in the #UK still do not use a #smartphone

@roryponeill: Olaf "we still have 50% of our customers in the UK who don't have smartphones" <--this game is not over ;)

@marekpawlowski: Swantee: As internet becomes personal, people resist advertising. Digital advertising works only when it helps users complete missions

Video of Panel discussion here




@Alliantus: Chewing on ideas surrounding the evolution of the device. Rory O'Neill RIM.

@najeebster: Future of wireless by speaker from RIM. Vaguely ironic?

@najeebster: RIM - there are still CIOs that think response time to an email in over 48 hrs is OK

@Alliantus: predictive conversations can impact on way we communicate. Conversations will be written across multiple devices. Simplifying life?

@zahidtg: Is this the industry challenge?





@kumithiru: @roryponeill that's a big percentage. Vodafone recently referenced only 27% of European customer base are smartphone users

@geoffmccormick: great talk by @roryponeill of rim. Concise explanation of the role of device innovation and associated experiences. Well done !

@Alliantus: plenty of room for innovation in the market. Incredible growth potential. More of a bb pitch than generic piece about industry.

@najeebster: very decent spiel by @roryponeill that there's room for more than 2 players in a $1.4Tr mkt

@Alliantus: global market is aggregation of lots of local markets. Interesting concept worth noting.

@marekpawlowski: A vision of Blackberry at heart of internet of things, using back end to predict, mediate conversations & transactions by @roryponeill

@marekpawlowski: Not sure I agree with @roryponeill that digital simplifies conversations. Rather allows us to deal with more simultaneous complexity

@JawadAbbassi: According to #Blackberry, globally #smartphones make up 23% of total cellular handsets.

Rory O’Neill, Vice President of Software and Services EMEA, RIM presentation here and video here




@Alliantus: RichardJacklin #anite my god its full of stars. iPhone created new form factor. Much reduced range of models. Is this a trend?

@Alliantus: Model range dip in 2011. Seen across all devices as shift in vendors.

@rob_symes: data prices must rise by 40 percent to make up for loss of voice and messaging

@dw2: Liked the Arthur C Clarke 2001 references in Richard Jacklin's #fwicinnovation talk. I'll have some more in my debate pitch tomorrow :-)

@mattablott: Some interesting studies on operator 'device ranging' by Anite

@dw2: Richard Jacklin's summary of Samsung's recipe for device success: experiment rapidly with multiple approaches + smartly observe market

@marekpawlowski: Hearing how differentiation moved to software. Is it that users don't want differentiated hardware or just it is currently uneconomic?

@sdfriedner: Hot topics at #FWIC How will devices, particularly smartphones evolve in the future and what will be the differentiator?

@marekpawlowski: Asked: is great RF performance a UX differentiator? Yes, but not at point of sale! Becomes relevant once you own, when it's too late!

@marekpawlowski: Revealing reaction to Q about improving sustainability by keeping, upgrading handsets longer. "Our industry is based on consumption."

@zahidtg: Interesting analysis of cost/defect by Richard Jacklin of Anite


Richard Jacklin, Business Development Director, Anite; presentation here, video here



@rpctelecom: Of the around 40 speakers and panelists at #fwic as far as I can see only 3 are women. Hmmm says something about our industry I fear.


Track 1: Four Pathways to International Business Growth - Chaired by John Davies, UKTI

@cambwireless: Finbarr Moynihan at Mediatek says smartphones will have 60-70% of market with 100 dollar smartphone possible

Presentations:



Track 2: Utility or Valued Brand - Chaired by Mark Neild, Nokia Siemens Network


@cambwireless: Track 2 at #fwic Looking at value based pricing - mobile operators need to focus on core bus. Partner with OTT - don't compete

@cambwireless: Mark Neild, Nokia Siemens networks: Up to third of revenue on handset subsidy

@cambwireless: iPhone put more focus on network quality. Customers care more about quality of their networks

@cambwireless: Mark Neild, Nokia Siemens Network says operators need to stick to what they are good at - delivering access

Presentations:



Track 3: Bandwidth Hogs or Experience Innovators - Chaired by Reginald Kipke, Velocix

@marekpawlowski: Terrifyingly prehistoric to be sitting in a session about 'threats and opportunities' of OTT

@marekpawlowski: Myriad's @MWJ encourages operators to do *something* with digital service innovation. Doesn't need to be perfect first time, just try

@marekpawlowski: Good point by @mwj about how forgiving customers can be of experimentation if it meets certain needs. Good UX isn't about perfection.

Presentations:


Track 4: Where Next for Devices - Chaired by Zahid Ghadialy, Explanotech


@zahidtg: Wow! Track 4 at #FWIC is completely packed. Everyone loves to hear about device evolution.

@JawadAbbassi: The Future #Internet of things will need a machine 2 machine gateway to be scaleable


@zahidtg: Lol. Ian Davidsons slide



@zahidtg: Arm did an analysis that even though your phone may be 2GHz and 4 core, most of the time its running on 200MHz

@zahidtg: Science fiction here...transmission of Smell @ track4


@zahidtg: From a presentation by Jenny Tillotson



@zahidtg: Who has tried transmitting smells


@zahidtg: Interesting slide by @BrianIsATwit



Presentations: 






Track 5: The continuing role of Intellectual Property - Chaired by John Haine, Cognovo

Presentations:



Dinner in St. John's college


Day 2

@zahidtg: Cambridge consultants showing their Small cells reference design with Mindspeed tech inside


@zahidtg: Freescale and Arkessa showing M2M for the next 50 billion devices at#FWIC



@cambwireless: Day two of #fwic well under way with Matthew Postgate, Head of R & D, BBC talking “How is mobile broadband changing broadcasting?”

@dw2: Found a jackpot of fascinating videos about the future of wireless tech at http://3g4g.blogspot.co.uk/search/label/Videos courtesy of @zahidtg

@ndahad: the opportunities for mhealthcare. Professor Chris Lowe presenting on 2nd day of conference



@ndahad: what physicians typically looking for patients to track or monitor at home. Thousands of apps already available



@marekpawlowski: Perhaps there's no such thing as mHealth, just millions of distinct design challenges which, we hope, have some common tech solutions?

@ndahad: mhealthcare - the mhealth ecosystem




@marekpawlowski: Wealth of healthcare insights from Chris Lowe. Particularly the interest in doctors for using digital to facilitate more collaboration

@marekpawlowski: Also how greater self monitoring by patients could aid resource planning and epidemic response in the health system

@ndahad: big opportunity for mhealthcare solutions is in diabetes monitoring, 400 million affected worldwide, figure set to double in 10 years

@Alliantus: everyone saying what a fantastic job #ChrisLowe from Uni. Cambridge did this morning. Talking about mHealth

Prof. Chris Lowe, Director, University of Cambridge; slides here, video here




@kumithiru: Given voice to text keynote at yesterday's #FWIC fun to see@MatthewPostgate start with a Siri slide today

@Alliantus: How is mobile broadband changing broadcasting. A personal journey. Key enabler to redefine operating context. Industrial revolution.

@Alliantus: Towards a new broadcasting system. Universal. Live & on demand. Creation & curation. Immersive & pervasive. Shared and personal.

@Alliantus: Trend towards immersive and pervasive Tv. People want to be part of the service. Aunties view not the only one.

@Alliantus: Mobile equalised productisation with BBC content. No longer after thought.

@kumithiru: BBC 1-4-10 strategy for online service provision

@zahidtg: The 1 10 4 concept by BBC at #FWIC - 4 stands for 4 screens




@zahidtg: 50% of iPlayer access is now on 3G

@bensmithuk: BBC working on companion apps to play-out live in sync with programming including shows like Frozen Planet.

@Alliantus: is the broadcaster creator or curator? What is its role with user generated news, eg?

@BrianIsATwit: BBC #fwic future tech roadmap for broadcasting. LTE broadcast mode important.




@kumithiru: a lot of talk about e-MBMS in the US LTE networks good to see@MatthewPostgate of BBC deal with issue

@zahidtg: eMBMS is a research area by BBC :-)

@bensmithuk: BBC approaches for syncing 2nd screen: pure time sync, audio watermarking & syncing API interfaces (in order of 'frame accuracy')

@evolaris: Matthew Postgate, BBC: eMBMS interesting technology for broadcasters

@marekpawlowski: Matthew Postgate setting out immersive (3D, HD) & pervasive (new touchpoints) as tenets of BBC strategy

@marekpawlowski: BBC using Web sync, audio tags & home network API to link linear broadcast & companion devices. All must degrade gracefully

@marekpawlowski: Being able to link linear & companion content with frame accuracy is priority for BBC to try more creative multi-touchpoint experience

@marekpawlowski: Since iPlayer made accessible over cellular, has grown to 50/50 mix with Wifi on iPhone, but has not cannibalised Wifi at all

@marekpawlowski: However iPlayer iPad usage remains primarily Wifi, suggesting predominance of home usage

@marekpawlowski: I wonder if BBC will experiment beyond just multi-screen & start to build contextual experiences responsive to sensors & behaviour?

Matthew Postgate, Head of Research & Development, BBC; No Slides but Video is available here.




@zahidtg: Test challenges of connected car by Rohde&Schwarz


@zahidtg: We are also talking of VoLTE testing. The small note at the bottom has always worried me



Anton MessmerDirector of Subdivision, Mobile Radio Teseters, Rohde and Schwarz; slides here.




Innovation Hothouse - Chaired by Kevin Coleman, Project Director, 'Discovering Start-Ups'
Video here.




Policy Panel - Chaired by Stuart Revell, Chairman, ICT KTN Wireless Technology & Spectrum Working Group

@Alliantus: Airwave: spectrum is important to secure channels. Following global trends. Public safety network is minute in comparison to public.

@Alliantus: Small network for emergency response is expensive for small net. What price safety? Spectrum is important.

@Alliantus: Motorola. What do you want you phone 911? Someone who knows we ring 999. Cultural differences are interesting.

@zahidtg: Interesting. Emergency services use 0.9% of all spectrum between UHF and 6Ghz.

@RichardTraherne: Joe Butler, Ofcom, at Future #Wireless Conference #FWIC says radio spectrum access/use strategy must change

@Alliantus: International countries will not wait for Europe to make decisions. Sharing of infrastructure and services. LTE allows opportunity.

@Alliantus: How do we as a society value spectrum.

@Alliantus: voda. 15 year decisions regarding infrastructure. Where is the money? People don't care how they connect. How do we accommodate?

@cambwireless: Andy Hudson, Vodafone, head of spectrum policy, says that the most efficient use of spectrum is overall aim

@Alliantus: LTE not the soln for public safety. USA have made decisions that they will use it on the back of disasters such as Katrina and 911.

@Alliantus: Control will be driver for two networks. Could have sharing but only if emergency had control.

@zahidtg: I absolutely disagree that broadcasting is a complete waste of spectrum. If there were no broadcast ppl would try VOD, overwhelming nw

@cambwireless: Andy Hudson, Head of Spectrum Policy, Vodafone: "Biggest challenge is to make low cost high performance filter for handsets"

@rpctelecom: Jeppe Jepson of Motorola "broadcasting is the most wasteful use of the radio spectrum" - I'm not sure many would agree with him!

@rpctelecom: Ofcom wants a flexible spectrum map but will only "enable" not "regulate" for it. But will incumbents release spectrum if not pushed?

@rpctelecom: Andy Hudson of Vodafone says that Vodafone and O2 will share network infrastructure to give 98% indoor coverage in UK

Video of Policy Panel here.




@Alliantus: Colin Brereton #PwC Mobile enabler of global change. Interesting slide deck. Worth a download. Opportunity in Devoping World.

@bensmithuk: Don’t we need to stop marvelling at how the ‘young people’ are able to multi-screen and discuss / understand what all consumers want?

@bensmithuk: Tired of hearing ‘developed world’ & ‘emerging markets’ as binary distinction in mobile. Don’t we need a more granular description?

@Alliantus: New generation different mobile use. Apps 10Bn user market. See slides for other.

@cambwireless: Pwc - planet needs to be more productive. Mobile can become the primary enabler of social and economic development

@Peter_Whale: Thanks to Colin Bererton #PwC for laying challenge to focus creative energies on application of wireless to massively benefit society

Colin Brereton, Partner, Global Communications Industry Practice, PwC; slides here video here.

The Cambridge Debate

@zahidtg: #FWIC debate:This house believes that the future of Innovation in the wireless industry is within the Virtual rather than the Physical World

Video here.


@Peter_Whale: really stimulating 2 days. Head full of insights. Now the fun of connecting the dots; finding the takeaways; turning ideas into action

@vectafrank: well done@cambwireless - best yet!


Participants:
@cambwireless = Cambridge Wireless official twitter account
@zahidtg = Zahid Ghadialy
@marekpawlowski = Marek Pawlowski
@Qualcomm_UK = Qualcomm UK
@JawadAbbassi = Jawad J. Abbassi
@najeebster = Najeeb Khan
@geoffmccormick = geoff mccormick
@ndahad = Nitin Dahad
@Alliantus = Kevin Coleman
@dw2 = David Wood
@RichardTraherne = Richard Traherne
@bensmithuk = Ben Smith
@roryponeill = Rory O'Neill
@rob_symes = Rob Symes
@BrianIsATwit = Brian Robertson
@eurocomms = eurocomms
@rupert_baines = Rupert Baines
@mattablott = Matt Ablott
@sdfriedner = Saul Friedner
@Brill_Brum = Stu
@rpctelecom = RPC Telecom
@evolaris = evolaris
@RichardTraherne = Richard Traherne
@Peter_Whale = Peter Whale
@vectafrank = Frank Morris

In case you enjoyed my effort in collecting the tweets please let me know by clicking the 'Very Useful' checkbox below.


xoxoxoxoxoxoxoxo Additional Information xoxoxoxoxoxoxoxo 

As I mentioned in the beginning, Paul Taylor, Engineering Manager, Google, gave us a presentation and requested that we dont share information because of the Google developer conference. As this is over now, I am sharing the pics I took for his presentation. If anyone from Google raises an objection, I will take them down :-) 
















Monday, 18 June 2012

3GPP Release-12 and beyond


3GPP Recently held a workshop on "Release 12 and Onward" to identify common requirements for future 3GPP radio access technologies. The goal of the workshop is to investigate what are the main changes that could be brought forward to evolve RAN toward Release 12 and onward. It is recommended that presentations in the workshop include views on:
- Requirements
- Potential technologies
- Technology roadmap for Releases 12, 13 and after

The discussions from the workshop should be used to define the work plan for Release 12 and onward in TSG-RAN.

The list of presentations and links, etc. are below and I have also embedded the Summary and Draft report, both of which can be downloaded from 3GPP website or slideshare. Here is a list of different topics and the presentations that covered them:


AdHoc Networks
AdHoc Networks - RWS-120035


Antennas, Beamforming, Transmitters, Receivers
3D-beamforming - RWS-120002
Vertical sectorization/3D beamforming via AAS - RWS-120005
Advanced receivers and joint Tx/Rx optimisation - RWS-120005
Network assistance for IC receivers - RWS-120005
Support of Active Antenna Systems - RWS-120006
Advanced transmitter beamforming - RWS-120010
Advanced receiver cancellation - RWS-120010
Vertical and 3D beamforming - RWS-120011
MIMO Enhancements - RWS-120014
New antenna configurations and 3D MIMO - RWS-120014
UE AAS (Active Antenna System) [Detailed] - RWS-120015 / RWS-120049
Cloud of Antennas (CoA) Concept - RWS-120016
Support of Massive MIMO Technology - RWS-120016
Full Dimension MIMO (FD-MIMO) System [Detailed] - RWS-120021 / RWS-120046
Cloud-RAN: Benefits and Drawbacks - RWS-120021 / RWS-120046
Further Enhanced Receivers - RWS-120022
Multiple antenna evolution - RWS-120025
3D beamforming - RWS-120026
Vision of 3D MIMO - RWS-120029
Massive MIMO & 3D MIMO - RWS-120034
Potential MIMO Enhancements - RWS-120035
Advanced Antenna Technology - RWS-120035
DL MIMO Enhancement - RWS-120037
Performance Requirement for 8Rx at eNB - RWS-120037
UE Receiver Enhancements - RWS-120039
DL MU-MIMO Enhancement - RWS-120039
Enhancement of MIMO, CoMP - RWS-120040
Advanced MIMO - RWS-120040
MIMO and COMP - RWS-120041
Role of Advanced Receivers - RWS-120041
Advanced Interference Handling - RWS-120041
Interference Suppression Subframes (ISS) and IRC Receiver [Detailed] - RWS-120051


Applications (Apps)
Efficiency for diverse small data applications - RWS-120011
Device Service/Application Awareness - RWS-120018
I-Net:”I”-centric mobile network design philosophy - RWS-120024
Application Aware Comm - RWS-120036 / RWS-120050


Backhaul and Relay
Relay backhaul enhancement - RWS-120011
LTE Backhaul - RWS-120013
Relay - RWS-120025
CoMP, backhaul and X2 interface - RWS-120027 / RWS-120048
Mobile Relay And Relay Backhaul Enhancement - RWS-120029


Baseband
Baseband resource pooling and virtualization - RWS-120011


Capacity and Coverage
Higher system capacity - RWS-120010
Capacity for Mobile Broadband: Requirements and Candidate technologies - RWS-120012
Increase N/W capacity by 1000 times - RWS-120020
Coverage Enhancement - RWS-120037
Capacity Enhancement - RWS-120038 / RWS-120047
Cell-edge Throughput Improvement - RWS-120038 / RWS-120047


Carrier Aggregation, Flexible Bandwidths and Multiflow
LTE multiflow / Inter-site CA - RWS-120002
LTE/HSDPA Carrier Aggregation - RWS-120002
Multiflow Enhancements - RWS-120002
Multi-Stream Aggregation - RWS-120006
Provide mechanisms for Flexible Bandwidth Exploitation - RWS-120008
Carrier aggregation enhancement - RWS-120019
Inter-eNB Carrier Aggregation - RWS-120021 / RWS-120046
Evolution of Carrier Aggregation - RWS-120036 / RWS-120050
CA of Alternative Spectra - RWS-120042


Cells, Carriers, C/U Planes
C/U plane split & Phantom cell - RWS-120010
Phantom cell by single/separate nodes - RWS-120010
Phantom cell: Other topics - RWS-120010
New Carrier Type for Primary Component Carrier - RWS-120011
Flexible/Reconfigurable Cells - RWS-120023
New carrier-type (NCT) enhancements - RWS-120026
Amorphous cells - RWS-120034
New Carrier Types - RWS-120035
Non-Orthogonal Access - RWS-120039
Dynamic Area Construction for UE - RWS-120040


Cognitive Radio
Cognitive radio - RWS-120034
Cognitive Networking - RWS-120036 / RWS-120050


Coordinated MultiPoint (CoMP)
CoMP Enhancements - RWS-120014
CoMP/ICIC enhancement - RWS-120019
CoMP Enhancements - RWS-120023
CoMP enhancements - RWS-120026
CoMP Technologies - RWS-120027 / RWS-120048
Enhanced CoMP - RWS-120029
Potential CoMP Enhancements - RWS-120035
CoMP - RWS-120037
CoMP Enhancement for Indoor Environment - RWS-120040
Overhauling DL CoMP - RWS-120042


Device, Handsets, UE's
Additional UE Enhancements - RWS-120018
Coordination : Multi-mode UE - RWS-120024


D2D / Device-to-Device
Device-to-Device - RWS-120003
LTE Device to Device - Proximity Based Services - RWS-120004
LTE device to device - RWS-120007
LTE direct communication - RWS-120007
Device-to-Device Communications - RWS-120014
D2D Discovery/Communication - RWS-120016
3GPP Proximity Services (ProSe) / D2D - RWS-120022
Device-to-Device communications - RWS-120026
Device-to-Device communication - RWS-120036 / RWS-120050


Data Rates and Throughputs
Higher data rate and user-experienced throughput - RWS-120010
Fairness of user throughput - RWS-120010


Deployments
LTE in Local Area Deployments & Enhancements - RWS-120004
Energy Efficient Local Area Deployments - RWS-120004
Scaling for Mass Deployment - RWS-120008
Flexible and cost-efficient NW deployments - RWS-120010
Considerations on dense NW deployment - RWS-120019


Energy Consumption, Efficiency and Savings
Energy efficiency - RWS-120005
Reduce energy consumption - RWS-120008
Energy Saving - RWS-120014
UE Power Saving - RWS-120036 / RWS-120050
NB Power Saving - RWS-120036 / RWS-120050
Energy Saving Enhancements with CoMP - RWS-120040
Energy Saving with Centralized eNB - RWS-120040


Herogeneous Networks (HetNets)
Optimisation of Het Nets performance - RWS-120005
Improved Support for Heterogeneous Networks - RWS-120006
Network hyper-densification: LTE HetNet2.0 - RWS-120007
Multi-layer HetNet Deployments - RWS-120016
HetNet for HSPA - RWS-120017
HetNet Enhancements - RWS-120023
HetNet Mobility - RWS-120029
Small cells & HetNet - RWS-120031
HetNet - RWS-120037
HetNet Enhancements for HeNB - RWS-120040


HSDPA / HSUPA / HSPA+ Enhancements
HSPA UL Enhancements - RWS-120003
Uplink Enhancements - RWS-120006
UMTS evolution: enhancing CS voice on DCH - RWS-120007
High Speed Packet Access - RWS-120012
HSPA RRM enhancement - RWS-120024
HSPA+ further evolution - RWS-120034


Interworking (HSPA, LTE)
Coordination : HSPA/LTE e-interworking - RWS-120024
Inter-RAT Coordination/CA - RWS-120037


Local-Area Access (Small Cells)
Local-Area Access - RWS-120003
LTE in Local Area Deployments & Enhancements - RWS-120004
LTE Local Area Enhancements - RWS-120004
LTE Local Area Enhancement Areas - RWS-120004
enhanced Local Area (eLA) - RWS-120010
Local Area Enhancements - RWS-120022
Improved Local Area Mobility - RWS-120022


LTE
LTE for Nomadic and Fixed Use - RWS-120018
E-PDCCH enhancement - RWS-120019
Efficiency : Paging Optimization - RWS-120024


LTE Hotspot and Indoor Enhancements (LTE-Hi)
Hotspot and Indoor Enhancements (LTE-Hi) - RWS-120006
Hotspot/indoor Scenario (LTE-Hi) - RWS-120025
Indoor & Hotspot Enhancements (LTE-Hi) [Detailed] - RWS-120029
Possible Study Items for Indoor Environment - RWS-120040


M2M / Machine Type Communications (MTC)
Machine Type Communications - RWS-120003
Improved Support for MTC - RWS-120006
Machine-to-Machine: The Internet of Things - RWS-120014
Machine Type Communications: a new ecosystem - RWS-120014
Wireless MTC and RAN optimizations for MTC - RWS-120016
Low-Cost MTC UE - RWS-120017
MTC + eDDA (enhanced Diverse data application) - RWS-120019
Further Enhancements to Support MTC - RWS-120023
MTC - RWS-120025
MTC enhancements - RWS-120026
M2M - RWS-120029
MTC and migration of traffic from 2G - RWS-120031
Machine Type Communications enhancements - RWS-120034
Machine Type Communications - RWS-120035
Extension triggered by growing M2M traffic - RWS-120038 / RWS-120047
LTE-based M2M - RWS-120041


MBMS / eMBMS
eMBMS Enhancements - RWS-120007
eMBMS - RWS-120013
UHD Multimedia Broadcast/Multicast Service - RWS-120036 / RWS-120050


Mesh Networks
Mesh Networks - RWS-120018


Network Density
Network density: Scenarios - RWS-120010


Network Architecture and Operation
Easier network operation, tolerance to failure - RWS-120005
System Architecture - RWS-120032
Evolution of LTE Networks - RWS-120034


Positioning
Positioning Enhancements - RWS-120006


Public Safety
Public Safety - RWS-120030
Operation of Public Safety System via LTE - RWS-120031
Public safety’s future in LTE [Detailed] - RWS-120033


Self Organising Networks (SON) and Minimisation of Drive Testing (MDT)
SON Evolution - RWS-120002
Enhanced MDT - RWS-120011
Network Self-Optimisation - RWS-120014
SON and MDT - RWS-120017
HetNet SON - RWS-120029
MDT & Energy Saving - RWS-120029
Autonomous Interference Coordination - RWS-120029
Large scale multi-layer centralized cooperative radio - RWS-120034
MDT Enhancement - RWS-120036 / RWS-120050
SON Enhancements - RWS-120036 / RWS-120050
MDT and eDDA - RWS-120041


Small Cells (HNB/HeNB)
UMTS evolution: small cells - RWS-120007
Wide & Local area enhancements - RWS-120010
Small Cells - RWS-120014
Small Cell Enhancement in Rel-12 - RWS-120021 / RWS-120046
HeNB Enhancement - RWS-120036 / RWS-120050
Efficient Usage of Macro and Small Cells - RWS-120038 / RWS-120047
Low-cost Low Power Nodes (LC-LPN) - RWS-120038 / RWS-120047
Small-Cell Improvements: System Aspects - RWS-120041


Spectrum
Enhanced spectrum efficiency - RWS-120005
Spectrum efficiency: eLA topics - RWS-120010
Scenarios for spectrum extension - RWS-120010
Spectrum and spectrum usage - RWS-120012
Wider Spectrum Utilization - RWS-120016
Spectral efficiency for LTE - RWS-120017
New Spectrum for Mobile Broadband Access - RWS-120021 / RWS-120046
Enabling Technologies for New Spectrum - RWS-120021 / RWS-120046
Radio Propagation - RWS-120021 / RWS-120046
Opportunistic Use of Unlicensed Spectrum for D2D Local Traffic - RWS-120023
Flexible Spectrum Utilization - RWS-120024
Spectrum Related: New Bands And CA Band Combinations - RWS-120029
Spectrum - RWS-120032
Hybrid access scheme - RWS-120034
Spectrum - RWS-120035
Spectrum and Transmission Efficiency - RWS-120039
Spectrum-Agile LTE - RWS-120041


TDD / TD-LTE
TD-LTE - RWS-120014
TDD-specific aspects - RWS-120014
TDD adaptive reconfiguration - RWS-120034
Efficient Usage of Dual Duplex Modes - RWS-120038 / RWS-120047
LTE TDD Small-Cell versus WiFi - RWS-120041


Testing
Testing and Certification - RWS-120022


Traffic and Signalling Overhead
Efficient support of diverse traffic characteristics - RWS-120005
Efficient support for variety of traffic types - RWS-120010
Enhancements for variety of traffic types - RWS-120010
Very high traffic (and signalling) scenarios - RWS-120017
Control Plane Overhead Reduction - RWS-120021 / RWS-120046
Further Enhancements to Support Diverse Data Applications - RWS-120023
Efficiency : Small data services in high mobility - RWS-120024


User Experience
Improve User experience - RWS-120009
User Challenges - RWS-120032


Video streaming, call
RAN Enhancements for Video Streaming QoE - RWS-120023
RAN Enhancements for Internet Video Call - RWS-120023


WiFi / WLAN
Cooperation between LTE/HSPA and WiFi - RWS-120005
Unlicensed spectrum: LTE & WLAN - RWS-120007
LTE integration with other RATs - RWS-120014
WiFi integration: For Beyond Rel-12 - RWS-120017
LTE-WLAN Interworking - RWS-120023
Coordination With WiFi - RWS-120029
Smarter opportunistic usage of Wi-Fi - RWS-120031
LTE TDD Small-Cell versus WiFi - RWS-120041


Others
Other identified techniques for LTE - RWS-120005
Efficient Transactions - RWS-120035
Link Enhancement Considerations - RWS-120035
Intra-RAT cooperation / Inter-RAT cooperation - RWS-120036 / RWS-120050


Here is the summary from the workshop:

Complete list of Presentations

RWS-120002Release 12 and beyond for C^4 (Cost, Coverage, Coordination with small cells and Capacity)NSN
RWS-120003Views on Rel-12Ericsson & ST-Ericsson
RWS-120004LTE evolving towards Local Area in Release 12 and beyondNokia Corporation
RWS-120005Views on Release 12Orange
RWS-120006Views on Rel-12 and onwards for LTE and UMTSHuawei Technologies, HiSilicon
RWS-1200073GPP RAN Rel-12 & BeyondQualcomm
RWS-120008New Solutions for New Mobile Broadband ScenariosTelefonica
RWS-120009Telecom Italia requirements on 3GPP evolutionTelecom Italia
RWS-120010Requirements, Candidate Solutions & Technology Roadmap for LTE Rel-12 OnwardNTT DOCOMO, INC.
RWS-120011Where to improve Rel-12 and beyond: Promising technologiesNEC
RWS-120012Deutsche Telekom Requirements and Candidate TechnologiesDeutsche Telekom
RWS-120013Release 12 Prioritization ConceptsDish Networks
RWS-120014Towards LTE RAN EvolutionAlcatel-Lucent
RWS-120015UE AAS (Active Antenna System)Magnolia Broadband
RWS-120016Requirements and Technical Considerations for RAN Rel.12 & OnwardsFujitsu Limited
RWS-120017Operator requirements on future RAN functionalityTeliaSonera
RWS-120018AT&T View of Release 12 in the North America MarketplaceAT&T
RWS-120019Major drivers, requirements and technology proposals for LTE Rel-12 OnwardPanasonic
RWS-120020Efficient spectrum resource usage for next-generation N/WSK Telecom
RWS-120021Technologies for Rel-12 and onwardsSamsung Electronics
RWS-120022LTE Rel-12 and BeyondRenesas Mobile Europe
RWS-120023LTE Rel-12 and Beyond: Requirements and Technology ComponentsIntel
RWS-120024Considerations on further enhancement and evolution of UMTS/LTE network in R12 and onwardsChina Unicom
RWS-120025Views on LTE R12 and BeyondCATT
RWS-120026A proposal for potential technologies for Release 12 and onwardsETRI
RWS-120027A view on requirements on Rel-12 and onwards from an operator’s viewpointSoftbank Mobile
RWS-120028India market Requirements for Rel. 12 and beyondCEWiT
RWS-120029Views on LTE Rel-12 & BeyondCMCC
RWS-120030LTE addressing the needs of the Public Safety CommunityIPWireless
RWS-120031Vodafone view on 3GPP RAN Release 12 and beyondVodafone
RWS-120032An Operator’s View of Release 12 and BeyondSprint
RWS-120033Public Safety Requirements for Long Term Evolution REL-12U.S. Department of Commerce
RWS-120034Views on 3GPP Rel-12 and BeyondZTE
RWS-120035Considerations for LTE Rel-12 and beyondMotorola Mobility
RWS-120036LG’s view on evolution of LTE in Release 12 and beyondLG Electronics
RWS-120037Views on REL-12 and OnwardsChina Telecom
RWS-120038KDDI’s Views on LTE Release 12 onwardsKDDI
RWS-120039Evolving RAN Towards Rel-12 and BeyondSHARP
RWS-120040Views on enhancement of system capacity and energy efficiency toward Release12 and onwardHitachi
RWS-120041Beyond LTE-A: MediaTek’s view on R12MediaTek
RWS-120042Potential Technologies and Road Map for LTE Release 12 and BeyondITRI, HTC
RWS-120043New concept to maximize the benefit of interference rejection at the UE receiver: interference suppression subframes (ISS)Broadcom
RWS-120046Technologies for Rel-12 and onwardsSamsung Electronics
RWS-120047KDDI’s Views on LTE Release 12 onwardsKDDI
RWS-120048A view on Rel-12 and onwards from an operator’s viewpointSoftbank Mobile
RWS-120049UE AAS (Active Antenna System)Magnolia Broadband
RWS-120050LG’s view on evolution of LTE in Release 12 and beyondLG Electronics
RWS-120051New concept to maximize the benefit of interference rejection at the UE receiver: interference suppression subframes (ISS)Broadcom

More technically minded people want to explore the 3GPP website for the workshop links here: http://3gpp.org/ftp/workshop/2012-06-11_12_RAN_REL12/

Draft report that gives more insight into the presentations as follows: