tech-invite   World Map
3GPP     Specs     Glossaries     UICC       T+       IETF     RFCs     Groups     SIP     ABNFs       Search     Home
Top        in Index        Prev        Next

TR 33.812 (SA3)
Feasibility study on the security aspects of
Remote Provisioning and Change of Subscription
for Machine to Machine (M2M) equipment

|   ToC   |   3GPP‑Page   |   Help   |

(W-zip) V9.2.0    2010/06    87 p.


Rapporteur:  Mr. Lehtovirta, Vesa
See also:  –


Machine to Machine (M2M) Communication is seen as a form of data communication between entities that may have no human interaction. One of the challenges with M2M communication is that deployed M2M equipments are managed remotely without any direct human interaction with the device.

This Technical Report considers the M2M Equipment as a device that could be a fully self-contained device or a device with interfaces to attach, for example, sensors and on-site service equipment. The current 3GPP system defines the use of a USIM/ISIM application in a UICC as a means of protecting users (until now mostly human users of mobile terminals) and network operators from fraudulent use of the network. Since some of the original assumptions on the use of a USIM/ISIM application in a UICC did not take into account the requirements of M2M Equipment and users, the current UICC based solution needs to be reviewed against the new assumptions that arise from M2M.

The scope of this Technical Report is to study the remote subscription management for M2M Equipment (M2ME) when the Machine Communications Identity Module (MCIM) application resides in the UICC and when the MCIM application resides in the M2M equipment. The remote subscription management includes tasks such as remote subscription provisioning and/or remote change of subscription.

The scope of this study includes the definition of a trust model for remote subscription management for M2ME. Security threats and security requirements are identified, and an evaluation of the candidate solutions is presented.


 

Here        Top        None        None        Next
part:    1     2

 

 

1   Scope   Word-p. 7
2   References
3   Definitions, symbols and abbreviations   Word-p. 8
4   Use cases and requirements   Word-p. 10
5   Candidate solutions   Word-p. 15
5.1   Alternative 1a: TRE based solution with remote subscription provisioning and change
5.1.1   MCIM
5.1.2   Trusted Environment (TRE)
5.1.3   Network architecture   Word-p. 19
5.1.3.1   Introduction
5.1.3.2   Principles of the Network Architecture
5.1.3.3   Services
5.1.3.4   Technical Functions (in alphabetical order)
5.1.3.5   Roles   Word-p. 23      Up
5.1.3.6   Network Interactions for Remote Provisioning      Up
5.1.3.7   How to change to a new operator
5.2   Alternative 2: UICC based solution with no remote subscription provisioning and change
5.3   Alternative 3: UICC based solution with remote subscription change
6   Analysis

Up        Top        ToC