1、 TIA STANDARD Project 25 Digital Land Mobile Radio Key Fill Device (KFD) Interface Protocol TIA-102.AACD February 2005 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecommunications Industry Association Provide
2、d by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating inter
3、changeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or
4、selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American Na
5、tional Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or
6、 all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Standards Proposal No. 3-0130, formulated under the cognizance of the
7、 TIA TR-8.3 Subcommittee on Encryption.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2004 Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBL
8、ICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) or search online at http:/www.tiaonline.org/standards/search_n_order.cfm All rights reserved Printed in U.S.A. Copyright Telecommunications Industry Association Provided by IHS under license w
9、ith EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyr
10、ight permission to reproduce portions of this document, please contact TIA Standards Department or go to the TIA website (www.tiaonline.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/about/faqDetail.cfm?id=18 OR Telecommunications Industry Association
11、Standards (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Documen
12、t may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs atten
13、tion, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing ter
14、ms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied wit
15、h as respects the Document or its contents. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS
16、OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCL
17、AIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PR
18、ODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGE
19、S FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF
20、 THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA 102.AACD i Conten
21、ts 1 INTRODUCTION.1 1.1 Purpose .1 1.2 Scope.1 1.3 Revision History.1 1.4 References2 1.5 Definitions, Acronyms, and Abbreviations .2 2 MANUAL REKEYING OVERVIEW 3 2.1 KFD Based Key Management.3 2.2 KMF Based Key Management.3 2.3 Manual Rekeying Features 4 2.3.1 Mandatory Features .4 2.3.1.1 Keyload
22、4 2.3.1.2 Key Erase 5 2.3.1.3 Erase All Keys .5 2.3.1.4 View Key Info 5 2.3.2 Optional Features .5 2.3.2.1 View Individual RSI5 2.3.2.2 Load Individual RSI5 2.3.2.3 View KMF RSI.6 2.3.2.4 Load KMF RSI.6 2.3.2.5 View MNP 6 2.3.2.6 Load MNP 6 2.3.2.7 View Keyset Info .6 2.3.2.8 Activate Keyset .6 3 IN
23、TERFACE PROTOCOL DEFINITION7 3.1 KFD-MR Interface7 3.2 Physical Layer (Three Wire Half Duplex Interface) 7 3.2.1 K/F Line Description.7 3.2.2 Keyload* Line Description .8 3.2.3 GND Line Description 8 3.3 Sending a Key Signature8 3.4 Link Layer (4kbps Transfer Protocol) .9 3.4.1 4kbps Transfer Protoc
24、ol Byte Format9 3.4.2 4kbps Transfer Protocol Flow Control.10 3.4.3 4kbps Transfer Protocol Line Turnaround 10 3.4.4 Timeout Considerations .11 3.4.5 Transmitting a Byte (TXBYTE) .11 3.4.6 Receiving a Byte (RXBYTE) .12 3.5 Application Layer (KFD-P25 Interface Protocol).12 3.5.1 KFD-P25 Interface Pro
25、tocol OPCODES.13 3.5.2 KMM Frame .13 3.5.2.1 Length.14 3.5.2.2 Control14 3.5.2.3 Destination RSI.15 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA 102.AACD ii 3.5.2.4 Body1
26、5 3.5.2.4.1 Body-Esync Block Format 15 3.5.2.4.2 KMM.15 3.5.2.5 CRC 15 3.5.3 Exchange Procedure15 3.6 Application Layer (P25 Manual Rekeying Application) 18 3.6.1 Keyload.18 3.6.2 Load Individual RSI19 3.6.3 Load KMF RSI.20 3.6.4 Load MNP 21 3.6.5 Erase Keys.22 3.6.6 Erase All Keys .23 3.6.7 View Ke
27、y Info.24 3.6.8 View Individual RSI.25 3.6.9 View KMF RSI.26 3.6.10 View MNP 27 3.6.11 View Keyset Info .28 3.6.12 Activate Keyset29 3.7 KMMs.30 3.7.1 KMM Header Definition31 3.7.2 KMM Body Definitions 32 3.7.2.1 Change-RSI-Command .32 3.7.2.2 Change-RSI-Response .32 3.7.2.3 Changeover-Command .32 3
28、.7.2.4 Changeover-Response32 3.7.2.5 Inventory-Command (List Active Kset IDs) 32 3.7.2.6 Inventory-Response (List Active Kset IDs).32 3.7.2.7 Inventory-Command (List RSI Items)32 3.7.2.8 Inventory-Response (List RSI Items) 32 3.7.2.9 Inventory-Command (List Keyset Tagging Info)32 3.7.2.10 Inventory-
29、Response (List Keyset Tagging Info) 33 3.7.2.11 Inventory-Command (List Active Keys).33 3.7.2.12 Inventory-Response (List Active Keys) .34 3.7.2.13 Inventory-Command (List MNP).34 3.7.2.14 Inventory-Response (List MNP).34 3.7.2.15 Inventory-Command (List KMF RSI) .34 3.7.2.16 Inventory-Response (Lis
30、t KMF RSI)34 3.7.2.17 Modify-Key-Command .35 3.7.2.18 Negative-Acknowledgment .37 3.7.2.19 Rekey-Acknowledgment37 3.7.2.20 Zeroize-Command38 3.7.2.21 Zeroize-Response 38 3.7.2.22 Load-Config-Command .38 3.7.2.23 Load-Config-Response38 Annex A: CRC Generation (Register US 5,146,497; US 5,185,795 Copy
31、right Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA 102.AACD 1 1 INTRODUCTION 1.1 Purpose This document describes the protocols, procedures, and features required for a manual rekey
32、ing function in an APCO Project 25 system. The manual rekeying function resides in a Key Fill Device (KFD) which interfaces to a Mobile Radio (MR). Manual rekeying involves the exchange of Key Management Messages between a KFD and an MR for the purposes of provisioning an MR with encryption keys or
33、other key management related information, erasing keys in an MR, or viewing key management related information in an MR. Manual rekeying can be used as the sole means for provisioning mobile radios with traffic encryption keys or it can be used in conjunction with OTAR rekeying procedures. When used
34、 with OTAR rekeying procedures, manual rekeying can be used to provision an MR with key management parameters required for OTAR operation in addition to provisioning encryption keys. The manual rekeying function is a standard option with respect to the APCO project 25 standard. Within the manual rek
35、eying standard option, some minimum set of features/ procedures are required and are considered mandatory while other features/procedures are not absolutely needed and are considered optional. This document defines all of the possible manual rekeying KFD features and procedures and designates which
36、are mandatory and which are optional. At a minimum, an APCO Project 25 compliant KFD and MR should implement the mandatory set of features and procedures. 1.2 Scope This document addresses the manual rekeying interface between a KFD and an MR only. Although some system level overview is provided, sy
37、stem level definition is not fully covered. 1.3 Revision History July 28, 2000, Working Draft 1 January 12, 2001, Initial Draft Release. May 17, 2001, Working Draft 2. May 24, 2001, Working Draft 3. October 1, 2001, Working Draft 4. November 5, 2001, Working Draft 5. December 7, 2001, Working Draft
38、6. Draft 7, July 26, 2002, Comment resolution from the Encryption Task Group. Draft 8, July 31, 2003, Added support for Block Encryption Algorithms PN-3-0130, October 14, 2003, Ballot Version Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo rep
39、roduction or networking permitted without license from IHS-,-,-TIA 102.AACD 2 TIA 102.AACD, July 20, 2004, Changes made incorporating ballot comment resolution 1.4 References The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At
40、the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ANSI and TIA maintain registers of
41、currently valid national standards published by them. 1. TIA/EIA-102.AACA, Project 25 Over-The-Air-Rekeying (OTAR) Protocol, April 2001 2. TIA/EIA 102.AACA-1 Addendum 1 Key Management Security Requirements for Type 3 Block Encryption Algorithms, November 2002 1.5 Definitions, Acronyms, and Abbreviat
42、ions $ Designates a number as a hexadecimal integer AES Advanced Encryption Standard DES Data Encryption Standard BJT Bipolar Junction Transistor CRC Cyclic Redundancy Code kbps kilo-bits per second K/F KeyFail line KMF Key Management Facility KMM Key Management Message KFD Key Fill Device MNP Messa
43、ge Number Period MR Mobile Radio OTAR Over The Air Rekeying P25 Project 25 RSI Radio Set Identifier SLN Storage Location Number TDES Triple Data Encryption Standard TEK Traffic Encryption Key UKEK Unique Key Encryption Key VILmax Voltage Input Low Maximum VIHmin Voltage Input High Minimum VOLmax Vol
44、tage Output Low Maximum Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA 102.AACD 3 2 MANUAL REKEYING OVERVIEW For purposes of this section, P25 systems will be classified as
45、 either KFD based or KMF based. KFD based systems are those that rely exclusively on the Key Fill Device for provisioning MRs with encryption keys. KMF based systems utilize a KMF and OTAR procedures in conjunction with a KFD. 2.1 KFD Based Key Management KFD based key management can be used for sys
46、tems that utilize encryption for voice or data security but do not employ a KMF or use OTAR procedures for the distribution of encryption keys. In such systems, a KFD provides the only means for managing encryption keys in the system. All traffic encryption keys (TEKs) used in a KFD based system are
47、 entered and stored in one or more KFDs. The KFDs are then used to load the appropriate TEKs into each of the MRs in the system. As long as two MRs wishing to communicate securely have been loaded with a common TEK, secure communications can take place. Keeping track of which MRs should be loaded wi
48、th which TEKs is a manual process and is the responsibility of the KFD operator. There are four basic manual rekeying features that must be supported by the KFD in a KFD based system. See section 2.3 for a description of these manual rekeying KFD features. Keyload Key Erase Erase All Keys View Key I
49、nfo These four manual rekeying KFD features provide the basis for managing a simple P25 secure system and, as such, are considered mandatory. 2.2 KMF Based Key Management KMF based systems utilize a Key Management Facility for centralized key management. The KMF distributes keys to MRs in the system primarily through the use of OTAR procedures but manual rekeying procedures can also be utilized. Furthermore, manual rekeyin
