1、 TIA-102.CABB-A (Revision of TIA-102.CABB) November 2015Project 25 Interoperability Testing for OTAR Messages and Procedures NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilit
2、ating interchangeability 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 manufa
3、cturing or 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
4、American National 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
5、 its use or 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. Any use of trademarks in this document are for information purpo
6、ses and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. TIA-PN-102.CABB-A, formulated under the cognizance of the TIA TR-8 Mobile and Personal Private Radio Standards, TR-8.3 Subcommittee on Encryption). Published by TELECOMMUNI
7、CATIONS INDUSTRY ASSOCIATION Technology (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 practi
8、ce of contents of this Document 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 cl
9、aimed and called to TIAs attention, 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 di
10、scussions of any licensing terms 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
11、 Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, spe
12、cification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or let
13、ters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of
14、 IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise i
15、nvestigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PU
16、RPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE,
17、RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED 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 CONT
18、AINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES 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
19、OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA 102.CABB-A i Foreword (This forward is not part of this stand
20、ard.) This document is a revision to the TIA.102-CABB Project 25 Interoperability Testing for OTAR Messages and Procedures specification, and has been submitted to APCO/NASTD/FED by the Telecommunications Industry Association (TIA), as provided for in a Memorandum of Understanding (MOU) dated Decemb
21、er, 1993. That MOU provides that APCO/NASTD/FED will devise a Common System Standard for digital public safety communications (the Standard) and that TIA shall provide technical assistance in the development of documentation for the Standard. This document has been developed by the TIA TR8.3 Encrypt
22、ion subcommittee and is being published to provide technical information on the emerging digital techniques for Land Mobile Radio Service. The symbol “P25” or the wording “Project 25” appearing on the cover sheet of this document when published or in the title of any TIA-102 document or Telecommunic
23、ations Service Bulletin (TSB) referenced herein, that indicates the APCO/NASTD/FED Project 25 Steering Committee has adopted the document as part of the Standard. The appearance of the abbreviation “P25” or the wording “Project 25” on the cover sheet of this document or in the title of any document
24、referenced herein does not limit the applicability of the information contained in this document to “P25” or “Project 25” implementations exclusively. TIA-102.CABB-A ii Patent Identification The readers attention is called to the possibility that compliance with this document may require the use of
25、one or more inventions covered by patent rights. By publication of this document no position is taken with respect to the validity of those claims or any patent rights in connection therewith. The patent holders so far identified have, we believe, filed statements of willingness to grant licenses un
26、der those rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such licenses. The following patent holders and patents have been identified in accordance with the TIA intellectual property rights policy: No patents have been identified. TIA shall not be re
27、sponsible for identifying patents for which licenses may be required by this document or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. TIA 102.CABB-A iii Table of Contents 1 INTRODUCTION . 1 1.1 DISCLAIMER . 1 1.2 ABBREVIATIONS 1 1.3 DE
28、FINITIONS 2 1.4 REFERENCES . 2 1.4.1 Normative References 2 1.4.2 Informative References 3 1.5 REVISION HISTORY . 3 1.6 SCOPE AND LIMITS OF TESTING 3 2 TEST PROCEDURE . 4 2.1 Overview 4 2.1.1 System Configuration . 4 2.1.2 Documentation of Procedures 7 2.2 TEST PROCEDURES 8 2.2.1 TEST SUITE: Capabil
29、ities Procedure . 8 2.2.2 TEST SUITE: Change RSI Procedure 9 2.2.3 TEST SUITE: Changeover Procedure 11 2.2.4 TEST SUITE: Delete Key Procedure 12 2.2.5 TEST SUITE: Delete Keyset Procedure . 13 2.2.6 TEST SUITE: Registration Procedure 14 2.2.7 TEST SUITE: Deregistration Procedure . 15 2.2.8 TEST SUITE
30、: Hello Procedure . 15 2.2.9 TEST SUITE: Inventory Procedure . 16 2.2.10 TEST SUITE: Key Assignment Procedure 22 TIA-102.CABB-A iv 2.2.11 TEST SUITE: Modify-Key Procedure . 23 2.2.12 TEST SUITE: Modify-Keyset-Attributes Procedure . 25 2.2.13 TEST SUITE: Rekey Procedure . 26 2.2.14 TEST SUITE: Set Da
31、te-Time Procedure 29 2.2.15 TEST SUITE: Zeroize Procedure . 30 2.2.16 TEST SUITE: Warm-Start Procedure . 31 2.2.17 TEST SUITE: Reverse Warm-Start Procedure . 32 2.2.18 TEST SUITE: Unable-to-Decrypt Response . 33 TIA 102.CABB-A v List of Tables Table 1 OTAR Procedures Traceability Matrix 8 TIA 102.CA
32、BB-A rev 2 1 1 INTRODUCTION This document has been developed with input from the TIA TR8.3 Encryption Subcommittee and is designed to provide validation of the OTAR procedures described in TIA-102.AACA-A. The impetus behind the development of this document is the public safety land mobile radio indu
33、strys and user communitys opinion that there is a need for standardized functional interoperability testing of conventional and trunked Over the Air Rekeying (OTAR) radio equipment designed to the complementing documents that comprise this suite of standards. The purpose of this document is to defin
34、e a set of functional procedures for testing the interoperability of OTAR functionality between different manufacturers, different models of the same manufacturer, and different firmware versions of the same model. 1.1 DISCLAIMER The tests described in this document are NOT intended for the purpose
35、of certifying Project 25 devices as either conforming with Project 25 specifications or providing interoperability under all conditions. The intention is to verify interoperability within the scope of testing as described in this document in section 1.6, titled Scope and Limits of Testing. 1.2 ABBRE
36、VIATIONS ALGID Algorithm Identifier ANSI American National Standards Institute APCO Association of Public-safety Communications Officials - International CAI Common Air Interface CSS Channel Selector Switch CSSID Channel Selector Switch Identifier DLD Data Link Dependent DLI Data Link Independent FN
37、E Fixed Network Equipment IEC International Electrotechnical Commission ID Identifier ISO International Organization for Standardization KEYID Key Identifier KFD Key Fill Device KMF Key Management Facility KMM Key Management Message LLID Logical Link Identifier LMR Land Mobile Radio M change an indi
38、vidual RSI, add a Group RSI, change a Group RSI, delete a Group RSI, and synchronize message numbers for a given RSI. 2.2.2.2 Expected Behavior Upon successful completion of the Change RSI procedure, the individual RSI, group RSI, or message number will have been modified in the target SU per the sp
39、ecified test case. 2.2.2.3 Initial Conditions a) Default (reference section 2.1.1.1). b) SU is programmed with Individual Address RSI1. c) Message Number MN1 is associated to RSI1. d) SU is programmed with Group Address RSI2. TIA 102.CABB-A rev 2 10 2.2.2.4 Procedures 2.2.2.4.1 Test Case 1 Change In
40、dividual RSI a) Using a manufacturer specific method (e.g. Inventory (List RSI Items) command via a KFD), obtain the SU RSIs. Verify the SU has individual address RSI1. b) Using a manufacturer specific method in the KMF, initiate the Change-RSI procedure, changing Individual address RSI1 to RSI2. c)
41、 Using a manufacturer specific method (e.g. Inventory (List RSI Items) command via a KFD), read the RSIs from the SU. d) PASS CRITERION: Use a manufacturer specific method to verify the Individual Address of the SU has changed from RSI1 to RSI2. 2.2.2.4.2 Test Case 2 Add Group RSI a) Using a manufac
42、turer specific method (e.g. Inventory (List RSI Items) command via a KFD), obtain the RSIs present in the SU. Verify the SU does NOT have Group address RSI3. b) Using a manufacturer specific method in the KMF, initiate the Change-RSI procedure addressed to the SU, adding Group RSI3. c) Using a manuf
43、acturer specific method (e.g. Inventory (List RSI Items) command via a KFD), obtain the RSIs present in the SU. d) PASS CRITERION: Use a manufacturer specific method to verify the SU now has Group address RSI3. 2.2.2.4.3 Test Case 3 Change Group RSI a) Using a manufacturer specific method (e.g. Inve
44、ntory (List RSI Items) command via a KFD), obtain the SU RSIs. Verify the SU has Group address RSI2 and does NOT have Group address RSI3. b) Using a manufacturer specific method in the KMF, initiate the Change-RSI procedure, changing the group address RSI2 to RSI3. c) Using a manufacturer specific m
45、ethod (e.g. Inventory (List RSI Items) command via a KFD), read the RSIs from the SU. TIA 102.CABB-A rev 2 11 d) PASS CRITERION: Use a manufacturer specific method to verify the SU has group address RSI3 and does NOT have group address RSI2. 2.2.2.4.4 Test Case 4 Delete Group RSI a) Using a manufact
46、urer specific method (e.g. Inventory (List RSI Items) command via a KFD), obtain the RSIs present in the SU. Verify the SU has Group address RSI3. b) Using a manufacturer specific method in the KMF, initiate the Change-RSI procedure addressed to the SU, deleting Group address RSI3. c) Using a manufa
47、cturer specific method (e.g. Inventory (List RSI Items) command via a KFD), read the RSIs present in the SU. d) PASS CRITERION: Use a manufacturer specific method to verify that the SU does NOT report Group address RSI3. 2.2.2.4.5 Test Case 5 Message Number (MN) Resynchronization a) Using a manufact
48、urer specific method (e.g. Inventory (List RSI Items) command via a KFD), read the SU RSIs and associated MNs. Verify the SU has MN1 associated to RSI1. b) Using a manufacturer specific method in the KMF, initiate the Change-RSI procedure addressed to the SU, modifying the MN of RSI1 from MN1 to MN2
49、1. c) Using a manufacturer specific method (e.g. Inventory (List RSI Items) command via a KFD), read the SU RSIs and associated MNs. d) PASS CRITERION: Use a manufacturer specific method to verify that the SU has MN2 associated to RSI1. 2.2.3 TEST SUITE: Changeover Procedure 2.2.3.1 Description This subset of interoperability tests verifies that the Changeover Procedure can be used by The KMF to assign an inactive keyset as the active keyset in a target SU. 1 MN2 is NOT equal to MN1. TIA 102.CABB-A rev 2 12 2.2.3.2 Expected Behavior Upon successful completion of the Chang
