MIM: Machine Identity Module - M2M SIM

Evolution of Machine Type Communications (MTC)

Standardisation on M2M at ETSI M2M platform

Standardisation on M2M at ETSI M2M platform

View more presentations from Zahid Ghadialy

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

LTE for Mobile Consumer Devices

LTE for Mobile Consumer Devices

View more presentations from Zahid Ghadialy

From the 2nd ETSI M2M Workshop, Oct. 2011. All presentations available here.

Related posts:

• 6th ETSI Security Workshop
• 1st ETSI M2M Workshop summary and conclusions

Three quick 3GPP Videos

Balazs Bertenyi, Dealing with the data explosion: Speaking about how 3GPP manages Releases and giving details of some of the key LTE features and some new work on the horizon.

Andrew Howell, GERAN and LTE Interworking: Andrew Howell, 3GPP GERAN Chairman, gives some background on the work of the GSM/EDGE RAN groups, including GELTE and the impact of machine type communications over legacy networks in the LTE age.


See also my earlier post on GELTE here.

Atle Monrad is Chairman of the 3GPP Core Network and Terminals group. In this short film, he explains the role of the protocol groups and gives a snap shot of the latest priorities for his group.

If you want to learn more about 3GPP, see earlier blog post here.

Smart Meters Data and Privacy

I have in the past discussed about Smart Grids and Smart meters in this post and have mentioned some of the privacy concerns. Each electrical device has its signature which could be exploited by some rogue elements to find out if there are any people in the household or itss empty. If its empty they could take advantage by breaking in the house, etc.

Last week I heard a presentation by Onzo in a Cambridge Wireless event about Smart meters (embedded below). This was the most detailed presentation I saw that explained how this data from the smart meters

If you browse the slides you will notice that the device signatures can be used to pinpoint the type of device and in most cases also the make and model of the device. It can even point out if a device is malfunctioning or about to breakdown. The customers can get a detailed summary of the main appliances in the house and how much electricity they consume and this would be without any physical intervention in the electrical circuit in the place.

I am sure that are many positive uses of this data and can be used by various governmental agencies to learn more about people behaviour, use it for monitoring crimes (think CSI) and many other advanced services that may not yet be imaginable but the privacy concerns and worries will remain.

The presentation below starts from slide 21 that shows the data part but feel free to view the previous slides.

The First 50 Billion Data Points

View more presentations from Zahid Ghadialy

Finally, I would like to mention that most of the information I have seen about Smart meters actually only include Electric meters. I find it difficult to foresee how we would have smart meters for Gas, Water and Sewage and how the data can be exploited in a positive way.

Smart people, dumb objects, networked environments

Nice presentation explaining Internet of Things (IoT).Smart people, dumb objects, networked environments

View more presentations from Zahid Ghadialy

Smart Grids: Beyond their remit

I blogged about the Smart Grid developments, nearly 2 years back here. Since then we have started talking about the 50 Billion connected M2M devices. Though Smart Grids as such can be just limited to distributing the electricity efficiently and dynamically, it has been said that they can be used for doing more than what they have been created for.

One such discussion in a recently concluded Cambridge Wireless Event on "Avoiding Cellular Gridlock: Finding New Ways Forward in Radio" was to use these smart grids for collecting the information about its surrounding.

It is well known that quite a few whitespace exist in radio communication in every country. We can build a cognitive radio that can use these whitespace and accordingly harness these free spectrum to the advantage of the users. Now since these whitespace would be different in each country and would also change depending on if a certain frequency is allocated in one area but not in another, there would need to be a database that the devices could use to find which spectrum is available or not.

Smart grids can be used to collect this information and update the database as they would have a wide footprint, probably encompassing the whole country. Though this is just an idea that came up in discussion, there could be more similar uses of smart grids.

For those of you who do not know much about smart grids, I have embedded couple of presentation from different chapters of The IET.

Smart Grids: Beyond the technical challenges

View more presentations from Zahid Ghadialy

The Role of New Technologies: A Power Engineering Equipment Supply Base Perspective

View more presentations from Zahid Ghadialy

One thing worth mentioning is that, there is already a concern that Smart Grids could be an invasion of privacy and could also be exploited by highly skilled theives.

Picture Source: Washington Post

If you look at the picture above, an expert in smart grids could be able to point out the different signatures of power consumption match to a particular event related generally to a device. So for example of you have used a kettle that means you have not gone on holidays, or something like that.

This also gives opportunity for new devices that can randomize these signatures :)

Interesting M2M Video by ETSI

Machine-to Machine Communications - David Boswarthick (15/02/2011) from ETSI – World Class Standards on Vimeo.

ETSI M2M: Building the Internet of Things

Presented by: David Boswarthick, ETSI Technical Expert

Live Presentation during MWC 2011: ETSI stand, Monday, 15 February 2011

_ _ _ _ _ _ _

About the presenter:

David Boswarthick, Technical Officer, ETSI

David has been extensively involved for over 10 years in the standardization activities of mobile, fixed and convergent networks in both the European Telecommunications Standards Institute (ETSI) and the 3rd Generation Partnership Project (3GPP). He is currently involved in the M2M standards group which is defining an end to end architecture and requirements for multiple M2M applications including Smart Metering, healthcare and enhanced home living. David holds a Bachelor's Honours Degree in Telecommunications from the University of Plymouth, and a Master's Degree in Networks and Distributed systems from the University of Nice and Sophia Antipolis, France.

6th ETSI Security Workshop

6th ETSI Security workshop was held last month. There were some very interesting areas of discussion including Wireless/Mobile Security, Smart Grids Security, etc.

Security in 3GPP

View more presentations from Zahid Ghadialy

Embedded SIMs and M2M Communications

View more presentations from Zahid Ghadialy

All presentations are available to download from here.

RAN mechanisms to avoid CN overload due to MTC

Machine-to-Machine (M2M) is the future and Machine-type communications (MTC) will be very important once we have billions of connected devices. I have talked in the past about the 50 Billion connected devices by 2050 and the Internet of Things.

One of the challenges of today's networks is to handle this additional signalling traffic due to MTC. One of the very important topics being discussed in 3GPP RAN meetings is 'RAN mechanisms to avoid CN overload due to MTC'. Even though it has not been finalised, its interesting to see the direction in which things are moving.

The above figure from R2-106188 shows that an extended wait time could be added in the RRC Connection Reject/Release message in case if the eNodeB is overloaded. The device can reattempt the connection once the wait time has expired.

In R2-110462, another approach is shown where Core Network (CN) is overloaded. Here a NAS Request message is sent with delay tolerant indicator a.k.a. low priority indicator. If the CN is overloaded then it can reject the request with a backoff timer. Another approach would be to send this info to the eNodeB that can do a RRC Connection Reject when new connection request is received.

All Documents from 3GPP RAN2 #72-bis are available here. Search for NIMTC for M2M related and overload related docs.

ETSI M2M Workshop summary and conclusions

As I mentioned earlier about the M2M workshop held in Paris, the following are the highlights from press release after the event:

ETSI's first Open Machine-to-Machine Workshop broke all records for attendance, laying out the next steps for achieving M2M applications worldwide, and confirming a leading role for the standards organisation.

'Machine-to-Machine (M2M) communications need standards – and ETSI is taking the lead to make sure that the standards are in place.' This was the main conclusion from ETSI's M2M workshop which took place on 19 and 20 October. With over 220 attendees from across the world, this was the most popular ETSI workshop to date, with the high degree of interest reflecting the enormous potential that is foreseen for M2M applications and technologies.

Participants heard how existing and evolving communication technologies networks (mostly wireless (cellular and low-power), but also fixed networks, including power line communications) provide a firm basis for connecting M2M sensors and applications. Specification of appropriate interfaces that allow network technology neutrality is a priority, and one that ETSI is already addressing.

The workshop included two live demonstrations organised by InterDigital Inc. These demonstrated an M2M gateway and core network, and an M2M Wireless Personal Area Network (sensors connecting via low-power wireless devices to a database, simulating e-Health, home automation and security application scenarios). The implementations were based on current specifications from ETSI's M2M Technical Committee and confirmed both the effectiveness of the implications and of the ETSI specifications. In addition, poster sessions presented the work of six research and development projects related to M2M and the Future Internet, part of the European Commission's 7th Framework Programme (FP7).

The standards work of ETSI's M2M Technical Committee is reaching an advanced stage, and many network operators are encouraging a first release of M2M standards by early 2011. The committee is currently finalising the architecture for the service platform that will enable the integration of multiple vertical M2M applications. The workshop confirmed that ETSI is well placed to address a vital aspect of standardisation in support of M2M – the specification of interfaces that will facilitate the interconnection and interoperability of the diverse applications and of the networks that will underlie them.

Marylin Arndt of France Telecom, Chairman of ETSI's M2M Technical Committee, said: 'The committee will continue in its role of creating standards that build on what we already have, to ensure that the emerging 'vertical' M2M applications can be supported effectively. At the same time, the committee (and ETSI in general) has a vital responsibility to co-ordinate and direct the wider work on M2M. We are here to lead the way.'

All presentations could be downloaded from here.

The conclusions from the meeting is summarised in the presentation embedded below:

ETSI M2M Workshop Oct. 2010 Conclusions

View more presentations from Zahid Ghadialy

Network Improvements for Machine Type Communications (NIMTC)

I have blogged about M2M before here.

The Release 10 work item Network Improvements for Machine Type Communications – Stage 1 for NIMTC specified a number of requirements to make the network more suitable for machine type communications. Additional aspects need to be studied before proceeding with their potential inclusion in the normative work.

In the course of the Release 10 work item, it was decided to leave out MTC Device to MTC Device communications from Release 10. This because it was felt it was not possible to do it justice within the Release 10 time frame. Nevertheless, MTC Device to MTC Device communications are expected to become of major importance, especially with consumer devices communicating directly to each other. Therefore, this work item aims to study the network improvements requirements of MTC Device to MTC Device scenarios. A particular aspect of MTC Device to MTC Device scenarios is the identification and functionality needed to set up a connection towards a MTC Device. The IMS domain may provide a solution for this required functionality. In this case the impacts and requirements of MTC on IMS needs to be studied.

Additionally MTC Devices often act as a gateway for a capillary network of other MTC Devices or non-3GPP devices. These gateway MTC Devices may have specific requirements on the mobile network, which have not yet been taken into account in the Release 10 NIMTC work item. Study is needed to determine to what extent improvements are needed and can be specified by 3GPP for MTC Devices that act as a gateway for 'capillary networks' of other devices. Also alignment with what is specified by ETSI TC M2M on this aspect is needed.

Further optimisations may be possible for (groups of) MTC Devices that are co-located. An example of this could be a car with a number of different MTC Devices that always move along together. Optimisations for these kind of scenarios have been suggested, but have not yet been taken into account in the Release 10 NIMTC. Study is needed to determine to what extent network improvements can be specified for co-located MTC Devices.

Because of the different characteristics of Machine-Type Communications, the optimal network for MTC may not be the same as the optimal network for human to human communications. Optimisations of network selections and steering of roaming may be needed. Study is needed to determine to what extent improvements are needed on network selection and steering of roaming for MTC.

Many MTC applications use some kind of location tracking. E.g. the existing LCS framework could be used to provide location information for these kinds of MTC applications. Study is needed to determine to what extent improvements are needed for MTC location tracking.

MTC brings a new concept of a MTC User and MTC Server. So far little attention has been given to service requirements on the communication between the network and the MTC User/MTC Server. Also alignment with what is specified by ETSI TC M2M on that aspect is needed. Study is needed on what kind of service requirements are needed and can be specified by 3GPP.

The Objective of Study on enhancements for Machine-Type Communications item is to study additional requirements, use cases and functionality beyond that specified by the Release 10 NIMTC work item on the following aspects:

• network improvements for MTC Device to MTC Device communications via one or more PLMNs. Note: direct-mode communication between devices is out of scope.

• possible improvements for MTC Devices that act as a gateway for 'capillary networks' of other devices. Note: capillary networks themselves are out of scope of 3GPP.

• network improvements for groups of MTC Devices that are co-located with other MTC Devices

• improvements on network selection mechanisms and steering of roaming for MTC devices

• possible enhancements to IMS to support MTC

• possible improvements for location tracking of MTC Devices

• service requirements on communications between PLMN and the MTC User/MTC Server (e.g. how the MTC User can set event to be monitored with MTC Monitoring);

• possible service requirements to optimize MTC Devices

• possible New MTC Features to further improve the network for MTC

The results of the study will be recorded in a Technical Report. Work ongoing in external standard organization shall be considered (e.g. ETSI M2M, CCSA TC 10).

The European Telecommunications Standards Institute (ETSI) now has a Technical Committee exclusively focused on M2M; the Chinese Communications Standards Association (CCSA) is currently exploring the definition of M2M standards for China and the Geneva-headquartered International Telecommunications Union (ITU) is working on “mobile wireless access systems providing telecommunications for a large number of ubiquitous sensors and/or actuators scattered over wide areas in the land mobile service,” which are at the center of the M2M ecosystem.

Closer to us, the US Telecommunications Industry Association (TIA) has also launched a new engineering committee centered on Smart Device Communications (TIA TR-50). Incidentally, at Global Standards Collaboration 15 (GSC-15), which will be held on August 30- September 2, 2010 in Beijing and hosted by CCSA, the world’s leading telecommunications and radio standards organizations will meet to promote innovation and collaboration on a broad spectrum of standards topics among which M2M has been identified as a “High Interest Subject.”

Related subject on 3GPP here.

M2M workshop is happening in ETSI next week. More details here.

Definitions:

MTC Device: A MTC Device is a UE equipped for Machine Type Communication, which communicates through a PLMN with MTC Server(s) and/or other MTC Device(s).

Local-Access Device: A Local-Access Device is a device in MTC Capillary Network, which has no 3GPP mobile communication capability.

MTC Capillary Network: An MTC Capillary Network is a network of devices that provides local connectivity between devices within its coverage and MTC Gateway Device.

MTC Gateway Device: An MTC Gateway Device is an MTC device equipped for Machine Type Communication, which acts as a gateway for a group of co-located MTC Devices or to connect MTC Devices and/or Local-Access Devices in an MTC Capillary Network to communicate through a PLMN with MTC Server(s), and/or other MTC Device(s).

Further Interesting Reading:

The M2M Switch - turning the wireless business model upside down

MARKET FOR M2M APPLICATIONS EXPLODES

Embedded Mobile M2M Modem Market on Track to More Than Triple in 2010

Quick preview of 3GPP Release-11 Features and Study items

Release 11 Features

Advanced IP Interconnection of Services

The objective is to specify the technical requirements for carrier grade inter-operator IP Interconnection of Services for the support of Multimedia services provided by IMS and for legacy voice PTSN/PLMN services transported over IP infrastructure (e.g. VoIP). These technical requirements should cover the new interconnect models developed by GSMA (i.e. the IPX interconnect model) and take into account interconnect models between national operators (including transit functionality) and peering based business trunking. Any new requirements identified should not overlap with requirements already defined by other bodies (e.g. GSMA, ETSI TISPAN). Specifically the work will cover:

• Service level aspects for direct IP inter-connection between Operators, service level aspects for national transit IP interconnect and service level aspects for next generation corporate network IP interconnect (peer-to-peer business trunking).

• Service layer aspects for interconnection of voice services (e.g. toll-free, premium rate and emergency calls).

• Service level aspects for IP Interconnection (service control and user plane aspects) between Operators and 3rd party Application Providers.

To ensure that requirements are identified for the Stage 2 & 3 work to identify relevant existing specifications, initiate enhancements and the development of the new specifications as necessary.


Release 11 Studies

Study on IMS based Peer-to-Peer Content Distribution Services

The objectives are to study IMS based content distribution services with the following aspects:

- Identifying the user cases to describe how users, operators and service providers will benefit by using/deploying IMS based content distribution services. such as with the improvement of Peer-to-Peer technology. The following shall be considered:

- Mobile access only (e.g. UTRAN, E-UTRAN, I-WLAN);

- Fixed access only (e.g. xDSL, LAN);- Fixed and mobile convergence scenarios;

- Identifying service aspects where IMS network improvements are needed to cater for content distributed services for above accesses;

- Evaluating possible impacts and improvements on network when IMS based content distribution services are deployed;

- Identifying QoS, mobility, charging and security related requirements in the case of content distribution services on IMS;

- Identifying potential copyright issues;

Study on Non Voice Emergency Services

The Non Voice Emergency Services could support the following examples of non-verbal communications to an emergency services network:

1. Text messages from citizen to emergency services

2. Session based and session-less instant messaging type sessions with emergency services

3. Multi-media (e.g., pictures, video clips) transfer to emergency services either during or after other communications with emergency services.

4. Real-time video session with emergency services

In addition to support the general public, this capability would facilitate emergency communications to emergency services by individuals with special needs (e.g., hearing impaired citizens).

The objectives of this study include the following questions for Non Voice Emergency Services with media other than or in addition to voice:

1. What are the requirements for Non Voice Emergency Services?

2. What are the security, reliability, and priority handling requirements for Non Voice Emergency Services?

3. How is the appropriate recipient emergency services system (e.g., PSAP) determined?

4. Are there any implications due to roaming?

5. Are there any implications to hand-over between access networks

6. Are there any implications due to the subscriber crossing a PSAP boundary during Non Voice Emergency Services communications (e.g., subsequent text messages should go to the same PSAP)?

7. Do multiple communication streams (e.g., voice, text, video emergency services) need to be associated together?

8. What types of “call-back” capabilities are required?9. Investigate the load impact of Non Voice Emergency Services in the case of a large scale emergency event or malicious use.

Non Voice Emergency Services will be applicable to GPRS (GERAN, UTRAN) and to EPS (GERAN, UTRAN, E-UTRAN and non-3GPP).

Study on UICC/USIM enhancements

The intent of this study item is to identify use cases and requirements enabling Mobile Network Operators to distribute new services based on the USIM, to improve the customer experience and ease the portability and customisation of operator-owned and customer-owned settings from one device to another (such as APN and other 3G Notebook settings, graphical user interface, MNO brand, Connection Manager settings,…), and help in reducing operation costs and radio resources usage.

Objectives of this study item are:

-To identify use cases and requirements for new USIM

-based services taking into account the GSMA Smart SIM deliverables;

- To identify use cases and requirements for the USIM used inside terminals with specialised functionalities (e.g. radio modems, 3G Notebook terminals) taking into account the GSMA 3GNBK deliverables;

- To identify use cases and requirements to drive the evolution from the traditional USAT to a multimedia USIM toolkit support, with a particular aim to the Smart Card Web Server;

Study on Alternatives to E.164 for Machine-Type Communications

M2M demand is forecast to grow from 50M connections to over 200M by 2013. A large number of these services are today deployed over circuit-switched GSM architectures and require E.164 MSISDNs although such services do not require "dialable" numbers, and generally do not communicate with each other by human interaction.

Without technical alternative to using public numbering resources as addresses, and considering the current forecasts and pending applications for numbers made to numbering plan administration agencies, there is a significant risk that some national numbering/dialling plans will run out of numbers in the near future, which would impact not only these M2M services but also the GSM/UMTS service providers in general.

The Objective is to determine an alternative to identify individual devices and route messages between those devices. Requirements for this alternative include:

- Effectively identify addressing method to be used for end point devices

- Effectively route messaging between those devices

- Support multiple methods for delivering messages, as defined by 22.368

- Support land-based and wireless connectivity

- Make use of IP-based network architectures

- Addressing/identifiers must support mobility and roaming- support on high speed packet

-switched networks when available and on circuit-switched networks

- Consider if there are security issues associated with any alternatives

A quick Introduction to M2M Communications

Machine-to-Machine (M2M) communications is a healthy sector that' s expanding rapidly and generating significant revenues for mobile network operators (MNOs). Devices outnumber subscribers by an order of magnitude, but the term doesn' t do justice to the concept and the market it represents.

The following is from 3G Americas report on 3GPP standards and their evolution to 4G:

By leveraging connectivity, Machine-to-Machine (M2M) communication would enable machines to communicate directly with one another. In so doing, M2M communication has the potential to radically change the world around us and the way that we interact with machines.

In Rel-10, 3GPP is in the process of establishing requirements for 3GPP network system improvements that support Machine-Type Communications (MTC). The objective of this study is to identify 3GPP network enhancements required to support a large number of MTC devices in the network and to provide necessary network enablers for MTC communication service. Specifically, transport services for MTC as provided by the 3GPP system and the related optimizations are being considered as well as aspects needed to ensure that MTC devices and/or MTC servers and/or MTC applications do not cause network congestion or system overload. It is also important to enable network operators to offer MTC services at a low cost level, to match the expectations of mass market machine-type services and applications.

The 3GPP study on M2M communications has shown potential for M2M services beyond the current "premium M2M market segment." The example of applications for mass M2M services include machine type communications in smart power grid, smart metering, consumer products, health care, and so forth. The current mobile networks are optimally designed for Human-to-Human communications, but are less optimal for M2M applications.

A study item on M2M communications (3GPP TR 22.868) was completed in 2007; however, no subsequent normative specification has been published. For Rel-10 and beyond, 3GPP intends to take the results on network improvements from the study item forward into a specification phase and address the architectural impacts and security aspects to support MTC scenarios and applications. As such, 3GPP has defined a work item on Network Improvements for Machine-Type Communication (NIMTC). The following goals and objectives are described in the work item:

The goal of this work item is to:

• Provide network operators with lower operational costs when offering machine-type communication services

• Reduce the impact and effort of handling large machine-type communication groups

• Optimize network operations to minimize impact on device battery power usage

• Stimulate new machine-type communication applications by enabling operators to offer services tailored to machine-type communication requirements

The objectives of this work item include:

• Identify and specify general requirements for machine-type communications

• Identify service aspects where network improvements (compared to the current H2H oriented services) are needed to cater for the specific nature of machine-type communications

• Specify machine-type communication requirements for these service aspects where network improvements are needed for machine-type communication

• Address system architecture impacts to support machine-type communication scenarios and applications

A RAN study item to investigate the air interface enhancements for the benefit of M2M communication has also been recently approved. The study will be initiated in early 2010.

Further Reading:

• 3GPP TR 22.868: Study on Facilitating Machine to Machine Communication in 3GPP Systems; (http://www.3gpp.org/ftp/Specs/archive/22_series/22.868/)
• 3GPP TR 33.812: Feasibility Study on the Security Aspects of Remote Provisioning and Change of Subscription for M2M Equipment; (http://www.3gpp.org/ftp/Specs/archive/33_series/33.812/)
• 3GPP's initial thoughts on Machine to Machine communication (http://docbox.etsi.org/workshop/2008/2008_06_M2MWORKSHOP/3GPPs_SWETINA_M2MWORKSHOP.pdf)
• M2M Activities in ETSI (http://www.pole-scs.org/index.php?m=6&l=en&x=file.download&h=0&fileid=57063)
• ETSI Workshop on M2M STANDARDIZATION 4th and 5th of June 2008: Agenda (http://docbox.etsi.org/Workshop/2008/2008_06_M2MWORKSHOP/00M2Magenda_FINALVERSION.pdf)
• ETSI Workshop on M2M STANDARDIZATION 4th and 5th of June 2008: Presentations (http://docbox.etsi.org//Workshop/2008/2008_06_M2MWORKSHOP/)
• M2M: the Internet of 50 billion devices, Jan 2010, Win-Win (http://www.huawei.com/publications/view.do?id=6083&cid=11392&pid=10664)
• 5 Myths about M2M (http://www.slideshare.net/blueslice/5-myths-about-m2m-presentation)
  

M2M will become really big

From Carl Weinschenk Blog:

It seems kind of odd to call a prediction that an industry segment will reach $18.9 billion an understatement, but in this case it may be so.

This week, Juniper Research pegged the mobile and embedded M2M industry at that amount worldwide by 2014. The press release says that consumer and commercial telematics – vehicle-bound M2M -- will represent more than a third of the total.

Nineteen billion dollars is a lot of money. But even that pot of gold pales in comparison to the promise of M2M. M2M covers smart grid, telematics and a mind-boggling number of other consumer and business services and applications. Indeed, the specter of M2M -- thousands of gadgets talking to millions of widgets -- is one of the reasons that Internet Protocol version 6 is being pushed so hard in some quarters.

Another example of the potential size of the market comes from Berg Insight. The firm says the European M2M module market will grow from 2.3 million last year to 22 million in 2014. Systems under surveillance – alarm systems and tracking devices watched from a monitoring center – will grow from 10 million to 34 million during the same period. The site goes into some detail on the composition of the market.

M2M provides a deeper look into smart meters, the element of the smart grid industry that has been around the longest. The story quotes ABI Research numbers that 76 million smart meters were deployed worldwide by the end of last year. That number will jump to 212 million by 2014. Lux Research, the story says, predicts that the value of the smart grid market overall will grow from $4.5 billion now to $15.8 billion in 2015. The advanced metering infrastructure and smart meters will represent more than $5 billion of that.

The only thing that is certain is that growth will be significant. The dangers of making precise predictions are evident in the recent findings: Juniper says that the mobile and embedded M2M market will reach $18.9 billion by 2014, while Lux says the smart grid market alone will finish 2015 only $3.1 billion short of that figure. One thing that these firms would agree on, however, is that this is a giant opportunity.

You can also read Juniper Research's paper, 'M2M ~ Rise of the Machines' here.

UICC and USIM in 3GPP Release 8 and Release 9

In good old days of GSM, SIM was physical card with GSM "application" (GSM 11.11)

In the brave new world of 3G+, UICC is the physical card with basic logical functionality (based on 3GPP TS 31.101) and USIM is 3G application on a UICC (3GPP TS 31.102). The UICC can contain multiple applications like the SIM (for GSM), USIM and ISIM (for IMS). There is an interesting Telenor presentation on current and future of UICC which may be worth the read. See references below.

UICC was originally known as "UMTS IC card". The incorporation of the ETSI UMTS activities into the more global perspective of 3GPP required a change of this name. As a result this was changed to "Universal Integrated Circuit Card". Similarly USIM (UMTS Subscriber Identity Module) changed to Universal Subscriber Identity Module.

The following is from the 3G Americas Whitepaper on Mobile Broadband:

UICC (3GPP TS 31.101) remains the trusted operator anchor in the user domain for LTE/SAE, leading to evolved applications and security on the UICC. With the completion of Rel-8 features, the UICC now plays significant roles within the network.

Some of the Rel-8 achievements from standards (ETSI, 3GPP) are in the following areas:

USIM (TS 31.102)
With Rel-8, all USIM features have been updated to support LTE and new features to better support non-3GPP access systems, mobility management, and emergency situations have been adopted.

The USIM is mandatory for the authentication and secure access to EPC even for non-3GPP access systems. 3GPP has approved some important features in the USIM to enable efficient network selection mechanisms. With the addition of CDMA2000 and HRPD access technologies into the PLMN, the USIM PLMN lists now enable roaming selection among CDMA, UMTS, and LTE access systems.

Taking advantage of its high security, USIM now stores mobility management parameters for SAE/LTE. Critical information like location information or EPS security context is to be stored in USIM rather than the device.

USIM in LTE networks is not just a matter of digital security but also physical safety. The USIM now stores the ICE (In Case of Emergency) user information, which is now standardized. This feature allows first responders (police, firefighters, and emergency medical staff) to retrieve medical information such as blood type, allergies, and emergency contacts, even if the subscriber lies unconscious.

3GPP has also approved the storage of the eCall parameters in USIM. When activated, the eCall system establishes a voice connection with the emergency services and sends critical data including time, location, and vehicle identification, to speed up response times by emergency services. ECalls can be generated manually by vehicle occupants or automatically by in-vehicle sensors.

TOOLKIT FEATURES IMPROVEMENT (TS 31.111)
New toolkit features have been added in Rel-8 for the support of NFC, M2M, OMA-DS, DM and to enhance coverage information.

The contactless interface has now been completely integrated with the UICC to enable NFC use cases where UICC applications proactively trigger contactless interfaces.

Toolkit features have been updated for terminals with limited capabilities (e.g. datacard or M2M wireless modules). These features will be notably beneficial in the M2M market where terminals often lack a screen or a keyboard.

UICC applications will now be able to trigger OMA-DM and DS sessions to enable easier device support and data synchronization operations, as well as interact in DVB networks.

Toolkit features have been enriched to help operators in their network deployments, particularly with LTE. A toolkit event has been added to inform a UICC application of a network rejection, such as a registration attempt failure. This feature will provide important information to operators about network coverage. Additionally, a UICC proactive command now allows the reporting of the signal strength measurement from an LTE base station.

CONTACT MANAGER
Rel-8 defined a multimedia phone book (3GPP TS 31.220) for the USIM based on OMA-DS and its corresponding JavaCard API (3GPP TS 31.221).

REMOTE MANAGEMENT EVOLUTION (TS 31.115 AND TS 31.116)
With IP sessions becoming prominent, an additional capability to multiplex the remote application and file management over a single CAT_TP link in a BIP session has been completed. Remote sessions to update the UICC now benefit from additional flexibility and security with the latest addition of the AES algorithm rather than a simple DES algorithm.

CONFIDENTIAL APPLICATION MANAGEMENT IN UICC FOR THIRD PARTIES
The security model in the UICC has been improved to allow the hosting of confidential (e.g. third party) applications. This enhancement was necessary to support new business models arising in the marketplace, with third party MVNOs, M-Payment and Mobile TV applications. These new features notably enable UICC memory rental, remote secure management of this memory and its content by the third party vendor, and support new business models supported by the Trusted Service Manager concept.

SECURE CHANNEL BETWEEN THE UICC AND TERMINAL
A secure channel solution has been specified that enables a trusted and secure communication between the UICC and the terminal. The secure channel is also available between two applications residing respectively on the UICC and on the terminal. The secure channel is applicable to both ISO and USB interfaces.

RELEASE 9 ENHANCEMENTS: UICC: ENABLING M2M AND FEMTOCELLS
The role of femtocell USIM is increasing in provisioning information for Home eNodeB, the 3GPP name for femtocell. USIMs inside handsets provide a simple and automatic access to femtocells based on operator and user-controlled Closed Subscriber Group list.

Work is ongoing in 3GPP for the discovery of surrounding femtocells using toolkit commands. Contrarily to macro base stations deployed by network operators, a femtocell location is out of the control of the operator since a subscriber can purchase a Home eNodeB and plug it anywhere at any time. A solution based on USIM toolkit feature will allow the operator to identify the femtocells serving a given subscriber. Operators will be able to adapt their services based on the femtocells available.

The upcoming releases will develop and capitalize on the IP layer for UICC remote application management (RAM) over HTTP or HTTPS. The network can also send a push message to UICC to initiate a communication using TCP protocol.

Additional guidance is also expected from the future releases with regards to the M2M dedicated form factor for the UICC that is currently under discussion to accommodate environments with temperature or mechanical constraints surpassing those currently specified by the 3GPP standard.

Some work is also expected to complete the picture of a full IP UICC integrated in IP-enabled terminal with the migration of services over EEM/USB and the capability for the UICC to register on multicast based services (such as mobile TV).

Further Reading:

• Business perspective and Mobile service offer through Future SIM - Telenor (http://www.ux.uis.no/atc08/workshop/Larsen.pdf)
• The role of the UICC in Long Term Evolution all IP networks - Gemalto (http://www.gemalto.com/telecom/download/lte_gemalto_whitepaper.pdf)
• Technical White Paper: Smart Card in IMS - 3G Americas (http://www.3gamericas.org/documents/GEM_WP_IMS.pdf)
• 3GPP TS 31.101: UICC-terminal interface; Physical and logical characteristics (http://www.3gpp.org/ftp/Specs/archive/31_series/31.101/)
• 3GPP TS 31.102: Universal Subscriber Identity Module (USIM) application (http://www.3gpp.org/ftp/Specs/archive/31_series/31.102/)
• 3GPP TS 31.111: Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) (http://www.3gpp.org/ftp/Specs/archive/31_series/31.111/)
• 3GPP TS 31.115: Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.115/)
• 3GPP TS 31.116: Remote APDU Structure for (U)SIM Toolkit applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.116/)
• 3GPP TS 31.220: Characteristics of the Contact Manager for 3GPP UICC applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.220/)
• 3GPP TS 31.221: Contact Manager Application Programming Interface (API); Contact Manager API for Java Card™ (http://www.3gpp.org/ftp/Specs/archive/31_series/31.221/)