1 / 19

A first Demonstrator for a CAHN infrastructure

A first Demonstrator for a CAHN infrastructure. Bluetooth in CAHN. Reminder on Bluetooth Security. Bluetooth provides three Security Modes: No Security Authentication Authentication and Encryption Authentication is based on a PIN

kayla
Download Presentation

A first Demonstrator for a CAHN infrastructure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A first Demonstrator for a CAHN infrastructure Bluetooth in CAHN

  2. Reminder on Bluetooth Security • Bluetooth provides three Security Modes: • No Security • Authentication • Authentication and Encryption • Authentication is based on a PIN • Encryption is based on encryption keys, which are derived from the link key, which in turn is based on the PIN

  3. The Bootstrapping Problem • How can a PIN between two entities be defined, when the entities do neither know each other nor see each other? • A Service Provider can sell PINs (Pre Paid Solution, Authorization, not Authentication) • A third Entity can provide PINs on demand for registered users (all users have to have a subscription with this third party, which provides a higher level authentication) • Our suggestion: CAHN

  4. How CAHN can help to get a PIN The Scenario Service Connection Request Service Connection Response, including the PIN Secure Connection

  5. Bluetooth Goodies • InquiriesHelps to find other devices in vicinity • Service DiscoveryHelps to find services on a given device in vicinity • ProfilesServices are well defined by Profiles

  6. Example: PAN Profile, Network Access Point Service Name: Network Access Point Service RecHandle: 0x804ccf0 Service Class ID List: "Network access point" (0x1116) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 15 "BNEP" (0x000f) Version: 0x0100 SEQ16: 800 806 Profile Descriptor List: "PAN access point" (0x1116) Version: 0x0100

  7. New Profile: CAHN • Is it possible to create a new Profile for CAHN • The goal of the Profile would be to find out which devices are able to “speak” CAHN • MSISDN as Attribute

  8. The Scenario with Service Discovery 12:34:56:78:9a:bc

  9. The Scenario with Service Discovery Service Browse Request Service Browse Response 12:34:56:78:9a:bc MSISDN

  10. The Scenario with Service Discovery Connection Request Link Key Request Link Key Negative Response PIN Request PIN Negative Response Connection Negative Response 12:34:56:78:9a:bc MSISDN

  11. The Scenario with Service Discovery Service Connection Request Service Connection Request Processes Request (AC) Generates a PIN Sends back a Response Service Connection Request 12:34:56:78:9a:bc MSISDN

  12. The Scenario with Service Discovery Service Connection Response (incl. PIN) Service Connection Response (incl. PIN) Service Connection Response (incl. PIN) Connection Request Link Key Request Link Key Negative Response PIN Request PIN Positive Response Connection Positive Response 12:34:56:78:9a:bc MSISDN PIN

  13. GUI Het. VPN File Transfer Key Management CAHN Communication Module (CCM) USSD SMS Cellular BLT WLAN Implementation – Flow Chart CAHN Protocol via Cellular

  14. CAHN Communication Module (CCM) • Responsible to treat Requests and Responses and to handle the Bluetooth Connector or the Cellular Adapter • Daemon waiting for Requests • Provides a socket interface to the Cellular Adapter (local, multiplexed UNIX socket)

  15. Cellular Adapter • Translates packets from the CCM to Cellular packets and vice versa • Communicates with the local CCM via a socket interface • Communicates with the Cellular with help of the gsmlib and a serial connection to a cell phone

  16. Bluetooth Connector • Is invoked by the CCM • Responsible for • Access Control • PIN Generation • Service Configuration • PIN Database (MySQL) • (Billing Records)

  17. CAHN Protocol • Consists of three messages • CAHN Bluetooth Service Request • CAHN Bluetooth Service Response • Error Message PDU_ID P_LEN SRC_MSISDN DST_MSISDN SRC_BA DST_BA Bluetooth Service ID HDR CAHN HDR BLT HDR SVC DATA PDU_ID P_LEN SRC_MSISDN DST_MSISDN SRC_BA DST_BA Bluetooth Service ID PIN HDR CAHN HDR BLT HDR SVC DATA PDU_ID P_LEN SRC_MSISDN DST_MSISDN SRC_BA DST_BA Error Code HDR CAHN HDR BLT HDR SVC DATA (Optional)

  18. Open Issues • Bluetooth related • Can this really be a Profile? • Creation of a UUID • Attributes • Standardization through Bluetooth SIG • Cellular related • Transport Mechanism (USSD, GPRS or SMS?) • Architecture Realization (Java?) • General • GUI • Definition of Interfaces between the different modules • Further Protocol Definition • Access Control • PIN Generation by the Operator

  19. Thank you! • Questions? • Suggestions?

More Related