110 likes | 261 Views
A novel and flexible Architecture for CAHN. Marc Danzeisen. 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.
E N D
A novel and flexible Architecture for CAHN Marc Danzeisen
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 Marc Danzeisen 28.05.2003
CAHN with CANs only Marc Danzeisen 28.05.2003
Het. VPN File Transfer USSD SMS Cellular BLT WLAN Building Blocs of CAHN • CAHN GUI: • For User Interaction with • CAHN Services GUI GUI • CAHN Services: • Heterogeneous VPN • Secure File Transfer, etc. Draft! Het. VPN File Transfer Key Management Key Management • Key Management: • For CAHN Protocol • For CAHN Services • CCM: • CAHN Protocol • Identity Management • MSISDN • MAC / IP Addr. • CAHN Service Mgnt CAHN Communication Module (CCM) CAHN Communication Module (CCM) • CAHN Connectors: • Configuration of • Physical Devices • Secure Links • CAHN Adapters: • Translation of CAHN • PDUs (Messages) to the • lower layers USSD SMS Cellular BLT WLAN • Inter Module Communication: • Local or Remote Physical Communication Devices Cellular Aware Node (CAN) Marc Danzeisen 28.05.2003
GUI GUI Het. VPN File Transfer Key Management Het. VPN File Transfer Key Management CAHN Communication Module (CCM) CAHN Communication Module (CCM) USSD SMS USSD SMS Cellular BLT WLAN Cellular BLT WLAN CAHN Communication (I) 4) Pop-up of the File Transfer Service, GUI, accept of request 1) Start GUI of File Transfer Service, Invite Peer 2) Create CAHN Request (Service, MSISDN (Own / Peer), Capabilities, Devices, etc.) 3) Translation of the CAHN Request to fit the signaling channel (SMS / USSD / BLT / WLAN, etc.) 6) Secured Link establishment 5) Negotiation of Config and Security Settings Marc Danzeisen 28.05.2003
4) Pop-up of the File Transfer Service, GUI, accept of request 1) Connects to the File Transfer Service, Invite Peer GUI GUI 2) Create CAHN Service Request Het. VPN Het. VPN File Transfer File Transfer Key Management Key Management CAHN Communication Module (CCM) CAHN Communication Module (CCM) 3) Invite Peer 6) Config & Key distribution USSD USSD SMS SMS Cellular Cellular BLT BLT WLAN WLAN 7) Secured Link establishment CAHN Communication (II) 5) Calculation of Config and Security Settings CAHN Service Provider Service Management Het. VPN File Transfer Key Management CAHN Communication Module (CCM) Billing User / Session DB USSD SMS Cellular Marc Danzeisen 28.05.2003
CAHN with CANs and N-CANs Marc Danzeisen 28.05.2003
Het. VPN Het. VPN File Transfer File Transfer Key Management Key Management Protocols? USSD SMS Cellular BLT BLT Distribution of the Building Blocs (CAN / N-CAN / CAHN Server) ? • Main requirement: • CAHN should work, also if the N-CANs are not always on GUI GUI CAHN Communication Module (CCM) CAHN Communication Module (CCM) WLAN CAN N-CAN 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 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) Marc Danzeisen 28.05.2003
Questions? Thank you! Marc Danzeisen 28.05.2003