<Insert Picture Here> Integration of the SIM card via TCP/IP

Transcription

1

2 <Insert Picture Here> Integration of the SIM card via TCP/IP Sebastian Hans Principal Member of Technical Staff

3 Agenda Challenges of M2M connected Devices The SIM card in M2M networks Limitation of current protocols SIM integration into IP networks <Insert Picture Here> 3

4 Challenges of connected M2M devices Diversity of purpose/application domains (healthcare, automation, environment monitoring, utilities...) Diversity of hardware platforms and footprints Deployed in Billions Local or Remote location Inter-networking Interconnection between devices Internetworking platform and secure remote management of the platform and applications Local and remote post-deployment management (installation/deletion) of applications 4

5 The SIM card in M2M networks Some M2M devices will be connected to the mobile network, therefore they have a SIM card The SIM card provides a high secure trusted environments that can be remotely managed It can provide security services to the local connected devices The SIM card itself acts as a secure application platform with post issuances management capabilities If everything else is inter-connected via IP in the M2M space it is a natural step to integrate the SIM via TCP/IP in such device network for local and remote connectivity 5

6 Advantages of SIM integration via IP technology Standardized ways to address devices and applications in devices via TCP/IP Standardized ways to allocate IP addresses and get integrated into IP networks without user-interaction Standardized ways to publish and to find services in the network 6

7 Limitations of legacy protocols for the SIM card The currently deployed protocols for the SIM card are to limited ISO 7816 APDU over T=0 for the SIM card (TS ) has a size limitation and can only work between the terminal and the SIM card SIM/CAT Toolkit (TS ) is based on APDU (so limited by this underlying protocol) and can only address the terminal in which the SIM card is inserted Based on these legacy protocols it is not possible to address from the SIM card localy connected devices to the terminal application in the terminal or in local connected devices 7

8 First steps for the integration via IP ETSI, GlobalPlatform and Java Card Forum have already started to define standards to integrate the SIM card or the smartcard into All-IP networks ETSI SCP has defined in TS the IP connectivity of the SIM card integration of the card into the local IPv4 and IPv6 network of the terminal GloblPlatform has defined the Network Framework to manage smartcard remotly based on HTTP over TCP/IP networks ETSI SCP and GlobalPlatform have in their specs a migration from SMS/CAT-TP based SIM management to HTTP/HTTPS/TCP/IP based management defined Java Card 3.0 delivers the secure Runtime Environment such connected SIM or smartcard by adopting the OMA Smartcard Webserver Spec 8

9 Next Steps ETSI SCP is currently working on two aspects to move the integration of SIM cards into IP networks to the next level A framework to allow the secure communication between devices and application in devices over IP network with the SIM card Leveraging technology like zeroconf and dns-sd and technology that is usually known as web 2.0 ETSI SCP is working in a Next generation runtime environment based on Java Card 3 technolgy for such connected SIM card platforms GlobalPlatform is looking into the issues of integrating the smartcard into a generic IP network documenting the benefits, and existing technologies analysing the risk of such an integration 9

10 Summary And Conclusion The SIM card is one possible way to integrate a secure temper resistant hardware token into a M2M network Standards to integrate the SIM card via TCP/IP in such network and to manage the SIM in a secure way are already defined by ETSI and GlobalPlatform With the Runtime Environments currently defined by ETSI SCP the card can act as a secure server and client via TCP/IP in such networks 10

11 The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle. 11

12

13 13