| Direct-BT
    2.3.1
    Direct-BT - Direct Bluetooth Programming. | 
 
 
 
Go to the documentation of this file.
   25 package org.direct_bt;
 
   98     public static SMPPairingState get(
final String name) 
throws IllegalArgumentException {
 
  109             case (
byte) 0x01: 
return FAILED;
 
  110             case (
byte) 0x02: 
return REQUESTED_BY_RESPONDER;
 
  111             case (
byte) 0x03: 
return FEATURE_EXCHANGE_STARTED;
 
  112             case (
byte) 0x04: 
return FEATURE_EXCHANGE_COMPLETED;
 
  113             case (
byte) 0x05: 
return PASSKEY_EXPECTED;
 
  114             case (
byte) 0x06: 
return NUMERIC_COMPARE_EXPECTED;
 
  115             case (
byte) 0x07: 
return OOB_EXPECTED;
 
  116             case (
byte) 0x08: 
return KEY_DISTRIBUTION;
 
  117             case (
byte) 0x09: 
return COMPLETED;
 
  118             default: 
return NONE;
 
  
FEATURE_EXCHANGE_COMPLETED
Phase 1: Pairing responded by responding (slave) device via SMPPairingMsg.
PASSKEY_EXPECTED
Phase 2: Authentication (MITM) PASSKEY expected, see PairingMode#PASSKEY_ENTRY_ini.
SMPPairingState(final byte v)
FEATURE_EXCHANGE_STARTED
Phase 1: Pairing requested by initiating (master) device via SMPPairingMsg.
NONE
No pairing in process.
OOB_EXPECTED
Phase 2: Authentication (MITM) OOB data expected, see PairingMode#OUT_OF_BAND.
SMP Pairing Process state definition.
COMPLETED
Phase 3: Key & value distribution completed by responding (slave) device sending SMPIdentInfoMsg (#1)...
NUMERIC_COMPARE_EXPECTED
Phase 2: Authentication (MITM) Numeric Comparison Reply expected, see PairingMode#NUMERIC_COMPARE_ini...
REQUESTED_BY_RESPONDER
Phase 0: Pairing requested by responding (slave) device via SMPSecurityReqMsg.
KEY_DISTRIBUTION
Phase 3: Key & value distribution started after SMPPairConfirmMsg or SMPPairPubKeyMsg (LE Secure Conn...