1. University of Bern A novel and flexible Architecture for CAHN Marc Danzeisen

2. University of Bern 2 Marc Danzeisen 28.05.2003 Outline  CAHN with CANs only –The Building Blocs, features and responsibilities  CAHN with CANs and N-CANs –Distribution of the Building Blocs  CAHN Communication –Between Nodes –With CAHN Service Provider  Open Issues / Ongoing work

3. University of Bern 3 Marc Danzeisen 28.05.2003 CAHN with CANs only

4. University of Bern 4 Marc Danzeisen 28.05.2003 USSDSMS Building Blocs of CAHN Cellular CAHN Communication Module (CCM) Het. VPNFile Transfer GUI Key Management CAHN Communication Module (CCM) Het. VPNFile Transfer Key Management GUI WLANBLT Cellular Aware Node (CAN) USSDSMS CellularWLANBLT Physical Communication Devices CCM: CAHN Protocol Identity Management MSISDN MAC / IP Addr. CAHN Service Mgnt CAHN Adapters: Translation of CAHN PDUs (Messages) to the lower layers CAHN Services: Heterogeneous VPN Secure File Transfer, etc. Key Management: For CAHN Protocol For CAHN Services CAHN Connectors: Configuration of Physical Devices Secure Links CAHN GUI: For User Interaction with CAHN Services Inter Module Communication: Local or Remote

5. University of Bern 5 Marc Danzeisen 28.05.2003 CAHN Communication (I) WLANBLTCellular USSDSMS CAHN Communication Module (CCM) Het. VPNFile Transfer GUI Key Management WLANBLTCellular USSDSMS CAHN Communication Module (CCM) Het. VPNFile Transfer GUI Key Management 1) Start GUI of File Transfer Service, Invite Peer 3) Translation of the CAHN Request to fit the signaling channel (SMS / USSD / BLT / WLAN, etc.) 2) Create CAHN Request (Service, MSISDN (Own / Peer), Capabilities, Devices, etc.) 4) Pop-up of the File Transfer Service, GUI, accept of request 5) Negotiation of Config and Security Settings 6) Secured Link establishment

6. University of Bern 6 Marc Danzeisen 28.05.2003 CAHN Communication (II) WLAN BLTCellular USSDSMS CAHN Communication Module (CCM) Het. VPN File Transfer GUI Key Management 1) Connects to the File Transfer Service, Invite Peer 5) Calculation of Config and Security Settings 7) Secured Link establishment WLAN BLTCellular USSDSMS CAHN Communication Module (CCM) Het. VPN File Transfer GUI Key Management Cellular USSDSMS CAHN Communication Module (CCM) Het. VPN File Transfer Service Management Key Management User / Session DB Billing CAHN Service Provider 2) Create CAHN Service Request 4) Pop-up of the File Transfer Service, GUI, accept of request 6) Config & Key distribution 3) Invite Peer

7. University of Bern 7 Marc Danzeisen 28.05.2003 CAHN with CANs and N-CANs

8. University of Bern 8 Marc Danzeisen 28.05.2003 Distribution of the Building Blocs (CAN / N-CAN / CAHN Server) WLAN Cellular USSDSMS BLT CAHN Communication Module (CCM) GUI Het. VPNFile TransferKey Management Main requirement: CAHN should work, also if the N-CANs are not always on BLT GUI N-CANCAN CAHN Communication Module (CCM) Het. VPNFile TransferKey Management ? Protocols?

9. University of Bern 9 Marc Danzeisen 28.05.2003 Open Issues / Ongoing Work  Inter-module Communication (Protocol, Local / Remote)  CAHN Protocol Definition  CAHN Services: –Service Definition for Service Detection / Registration –Information to be exchanged –VPN / File Transfer: Heterogeneous Network design –Service monitoring

10. University of Bern 10 Marc Danzeisen 28.05.2003 Open Issues / Ongoing Work (II)  CAHN Security –Loosely coupled security –CAHN as a pure application on top of the cellular system –No direct interaction within the key generation (CAHN Key Management) –CAHN uses the secured communication channels of the cellular system (implicit authentication) –Tightly coupled security –Reuse of SIM Security for CAHN Key Generation (CAHN Messages and Data Channels) To consider: –Operator is always man-in-the-middle (like CA) –Cellular Systems are not designed to handle inter-node security (SA only between SIM and AuC)

11. University of Bern 11 Marc Danzeisen 28.05.2003 Questions? Thank you!