Changes between Version 22 and Version 23 of A3A8A5

Timestamp:

02/02/2012 05:44:13 AM (16 months ago)

Author:

guest

Comment:

CKSN-related update

A3A8A5

@@ -34 +34 @@
 
 === Generating Kc ===
-Kc is generated along with SRES when {{{comp128v1}}} (or any other A3/A8) is invoked.  Acquiring it is just a matter of adding a little extra string processing to {{{sipauthserve}}}.
+Kc is generated along with SRES and CKSN when {{{comp128v1}}} (or any other A3/A8) is invoked in SubscriberRegistry.  Acquiring it is just a matter of adding a little extra string processing to {{{sipauthserve}}}.
 
-=== Sending Kc to OpenBTS ===
-Kc should be communicated to {{{OpenBTS}}} in the final 200 OK response from sipauthserve.  
+=== Sending Kc and CKSN to OpenBTS ===
+Kc and CKSN should be communicated to {{{OpenBTS}}} in the final 200 OK response from sipauthserve.  
 
 ''Suggestion:''
 
-Use SIP 200 OK message with ''Authentication-Info'' header set to Kc.
+Use SIP 200 OK message with ''Authentication-Info'' header set to Kc, and ''cnonce'' value set to CKSN.
 
 Reasoning: 
@@ -55 +55 @@
  1. git clone git://github.com/zabbal/subscriberRegistry.git -b authenc
 
-=== Storing Kc Locally in OpenBTS ===
-When Kc arrives in the 200 OK, it should be stored locally in the TMSI table.  When a channel is actually using Kc, the active Kc value is also stored in the L1FEC for that channel.  A Kc value of zero will indicate that cihpering is off.  Setting the Kc value on the L1FEC results in immediate application of the new ciphering setting.  The actual Kc value should be kept in L1FEC, with accessor in the {{{L1Encoder}}} and {{{L1Decoder}}} classes and a passthrough accessor in {{{LogicalChannel}}} so that it can also be presented in the transaction table records.
+=== Storing Kc and CKSN Locally in OpenBTS ===
+When Kc and CKSN arrives in the 200 OK, they should be stored locally in the TMSI table.  When a channel is actually using Kc, the active Kc value is also stored in the L1FEC for that channel.  A Kc value of zero will indicate that cihpering is off.  Setting the Kc value on the L1FEC results in immediate application of the new ciphering setting.  The actual Kc value should be kept in L1FEC, with accessor in the {{{L1Encoder}}} and {{{L1Decoder}}} classes and a passthrough accessor in {{{LogicalChannel}}} so that it can also be presented in the transaction table records.
 
 === Cipher Stream Generation ===