Summary of changes to 683B with relation to the processing of OTAPA/OTASP messages:

1
(No Transcript)
2
Summary of changes to 683B with relation to the
processing of OTAPA/OTASP messages 1. Added a
new feature Secure Mode (Table 3.5.1.7-1) and
new terms and definition for secure mode and
associated parameters 2. Added a new message
Secure Mode Request Message(Sections 4.3.1.14,
4.5 and 4.5.1.14) and added Section 4.3.5 which
included Secure Mode Key Generation(Section
4.3.5.1) and Encryption/Decryption (Section
4.3.5.2) 3. Added a new message Secure Mode
Response Message and processing of Secure Mode
Request Message (Sections 3.3.1.14, 3.5 and
3.5.1.14) and added Section 3.3.8 which included
Secure Mode Key Generation (Section 3.3.8.1) and
Encryption/Decryption (Section 3.3.8.2) 4. Added
encryption processing for PARAM_DATA blocks of
Configuration Response Message and a new
crypto-sync parameter FRESH at end of message
(Sections 3.3.1.1 and 3.5.1.1) 5. Added
encryption processing for PARAM_DATA blocks of
SSPR Configuration Response Message and a new
crypto-sync parameter FRESH at end of message
(Sections 3.3.1.8 and 3.5.1.8) 6. Added
encryption processing for PARAM_DATA blocks of
PUZL Configuration Response Message and a new
crypto-sync parameter FRESH at end of message
(Sections 3.3.1.12 and 3.5.1.12) 7. Added
encryption processing for PARAM_DATA blocks of
Download Request Message and a new crypto-sync
parameter FRESH at end of message (Section
4.5.1.2) 8. Added decryption processing for
PARAM_DATA blocks of Download Response Message
and a new crypto-sync parameter FRESH at end of
message (Section 3.3.1.2) 9. Added encryption
processing for PARAM_DATA blocks of SSPR Download
Request Message and a new crypto-sync parameter
FRESH at end of message (Section 4.5.1.9) 10.
Added decryption processing for PARAM_DATA blocks
of SSPR Download Response Message and a new
crypto-sync parameter FRESH at end of message
(Section 3.3.1.9) 11. Added encryption
processing for PARAM_DATA blocks of PUZL Download
Request Message and a new crypto-sync parameter
FRESH at end of message (Section 4.5.1.12) 12.
Added decryption processing for PARAM_DATA blocks
of PUZL Download Response Message and a new
crypto-sync parameter FRESH at end of message
(Section 3.3.1.12)
3
Summary of IS-683-B Changes to Support Secure Mode

• New Secure Mode is defined as a tunnel between
  mobile and OTAF.
• Mobile identifies support for Secure Mode in
  Protocol Capability Response Message by setting
  new Feature-ID and Feature_P_REV.
• OTAF invokes the Secure Mode for the Unlocked
  Mobile by new message Secure Mode Request
  Message
• With START indicator ON
• With RAND_SM value used for computing the Secure
  Mode Ciphering Key (SMCK) the SHA-1 algorithm
  is used.
• While secure Mode is ON, all PARAM_DATA fields of
  all Parameter Blocks transmitted by network or
  mobile are encrypted Rijndael algorithm is
  used.
• Encrypting side appends the FRESH field to all
  messages containing the ciphered data.
• FRESH can be random, or a counter with values
  unique for the messages while Secure Mode is on.
• Secure Mode ends when Secure Mode Request Message
  carries the STOP indicator, or when OTASP/OTAPA
  session ends.