TIA-102 CACD-C-2014 Project 25 Inter-RF Subsystem Interface Interoperability Test Procedures for Trunked Voice Operation Involving the ISSI.pdf

《TIA-102 CACD-C-2014 Project 25 Inter-RF Subsystem Interface Interoperability Test Procedures for Trunked Voice Operation Involving the ISSI.pdf》由会员分享，可在线阅读，更多相关《TIA-102 CACD-C-2014 Project 25 Inter-RF Subsystem Interface Interoperability Test Procedures for Trunked Voice Operation Involving the ISSI.pdf（206页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-102.CACD-C (Revision of TIA-102.CACD-B) November 2014Project 25 Inter-RF Subsystem Interface Interoperability Test Procedures for Trunked Voice Operation Involving the ISSI NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderst

2、andings between manufacturers and purchasers, facilitating 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

3、 preclude any member or non-member of TIA from manufacturing 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 Pu

4、blications are adopted by TIA in accordance with the 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 p

5、urport to address all safety problems associated with 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

6、trademarks in this document are for information purposes 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.CACD-C, formulated under the cognizance of the TIA TR-8 Mobile and Personal Private Radio TR-8.19 Subcommitt

7、ee on Wireline System Interfaces). Published by TELECOMMUNICATIONS 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 stan

8、dards development or any editing process. The use or practice 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

9、of patents and published pending patent applications are claimed 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 valid

10、ity of any claims of IPR. TIA will neither be a party to discussions 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 represen

11、t that procedures or practices suggested or provided in the 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 publ

12、ication of standards (whether designated as a standard, specification, 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

13、 or investigate the records of any other SSO for IPR or letters 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 appl

14、ications shall apply; and (iii) Information as to claims of 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 D

15、ocument. 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 OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE C

16、ONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE 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 REGA

17、RDING 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 PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIREC

18、T, 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 DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH O

19、F 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 THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-10

20、2.CACD-C i FOREWORD (This foreword is not part of this TIA standard.) This document has been created in response to a request by the APCO/NASTD/FED Project 25 Steering Committee as provided for in a Memorandum of Understanding (MOU) dated April 1992 and amended December 1993. That MOU states APCO/NA

21、STD/FED shall devise a common system standard for digital public safety communications (the Standard) commonly referred to as Project 25 or P25, and that TIA, as agreed to by the membership of the appropriate TIA Engineering Committee, will provide technical assistance in the development of document

22、ation for the Standard. If the symbol “P25” or the wording “Project 25” appears on the cover sheet of this document when published that indicates the APCO/NASTD/FED Project 25 Steering Committee has adopted this document as part of the Standard. The appearance of the abbreviation “P25” or the wordin

23、g “Project 25” on the cover sheet of this document or in the title of any document referenced herein should not be interpreted as limiting the applicability of the information contained in any document to “P25” or “Project 25” implementations exclusively. The TIA makes no claims as to the applicabil

24、ity of the information contained in this document for any purpose although it is believed that the information will prove to be useful to designers of Inter-Radio Frequency Subsystem Interface (ISSI) compliant equipment. Some aspects of the specifications contained in this document may not have been

25、 fully operationally tested; however, a great deal of time and good faith effort has been invested in the preparation of this document to ensure the accuracy of the information it contains. The purpose of this standard is to extend the interoperability test procedures in 102CABC from a single RFSS t

26、o multiple RFSSs connected by a G interface between each RFSS. For the end-to-end test procedures described here, the ISSI is treated as a network cloud from the perspective of the radio user which is the perspective from which the interoperability tests defined in this standard have been designed.

27、The Test Suites that are provided are similar to the Test Suites described in 102CABC. Each Test Suite provides a description of the test, applicable RFSS role combinations, expected behavior, call configuration, and initial conditions. Test cases for the individual test suites are then described. A

28、 general ISSI interoperability model is presented in Annex A. Annex B provides interoperability test pre-configuration data. TIA-102.CACD-C ii Table of Contents 1 INTRODUCTION 1 1.1 DISCLAIMER . 2 1.2 ABBREVIATIONS 2 1.3 DEFINITIONS 3 1.4 REFERENCES 4 1.4.1 Normative References 5 1.4.2 Informative R

29、eferences 5 1.5 REVISION HISTORY . 5 1.6 SCOPE AND LIMITS OF TESTING . 6 1.6.1 FDMA and TDMA Test Applicability . 7 2 TEST PROCEDURE 8 2.1 OVERVIEW 8 2.2 Test System Information 13 2.2.1 Unit Registration Role Combinations 13 2.2.2 Group Call Role Combinations . 13 2.2.2.1 Group Call Role Combinatio

30、ns with Two Identical RFSSs of Each Type . 14 2.2.2.1.1 Group Call Combinations with Two Identical RFSSs of Each Type and Possible vocoder mode combinations 15 2.2.2.2 Group Call Role Combinations with One RFSS of Each Type . 19 2.2.2.2.1 Group Call Combinations with One RFSS of Each Type and Possib

31、le Vocoder mode combinations . 20 2.2.3 Unit-to-Unit Call Role Combinations . 24 2.2.3.1 Unit-to-Unit Call Role Combinations with Two Identical RFSSs of Each Type . 25 2.2.3.1.1 Unit-to-Unit Call Combinations with Two Identical RFSSs of Each Type and Possible Vocoder mode combinations . 26 2.2.3.2 U

32、nit-to-Unit Call Role Combinations with One RFSS of Each Type . 36 2.2.3.2.1 Unit-to-Unit Call Combinations with One RFSS of Each Type and Possible Vocoder mode combinations . 37 2.2.4 Group Registration Role Combinations 41 TIA-102.CACD-C iii 2.2.5 RFSS Configuration . 42 2.2.6 SU Configuration 45

33、2.2.7 Documentation of Procedures 46 2.3 TEST PROCEDURES 47 2.3.1 TEST SUITE: Unit Registration using an ISSI 49 2.3.1.1 Description 49 2.3.1.2 Expected Behavior 49 2.3.1.3 Unit Registration Configuration using an ISSI 49 2.3.1.3.1 Unit Registration Test Configuration. 50 2.3.1.3.2 Unit Registration

34、 RFSS and SU Configuration . 50 2.3.1.4 Initial conditions . 51 2.3.1.5 Procedure 51 2.3.1.5.1 Test case 1 - Valid registration . 52 2.3.1.5.2 Test case 2 - Denied or refused registration . 52 2.3.1.5.3 Test case 3 Successful SU Home Query with Force parameter enabled. 52 2.3.1.5.4 Test case 4 Succe

35、ssful SU Home Query with Confirm parameter enabled . 53 2.3.1.5.5 Test case 5 Successful SU De-registration . 53 2.3.1.5.6 Test case 6 SU Roamed Procedure 54 2.3.2 TEST SUITE: Group Voice Call using an ISSI 54 2.3.2.1 Description 54 2.3.2.2 Expected behavior . 54 2.3.2.3 Group Call Configuration usi

36、ng an ISSI . 55 2.3.2.3.1 Group Call Test Configuration with Two Identical RFSSs of Each Type . 55 2.3.2.3.2 Group Call Test Environment with One RFSS of each Type 57 2.3.2.3.3 Group Call RFSS and SU Configuration with Two Identical RFSSs of Each Type. 59 2.3.2.3.4 Group Call RFSS and SU Configurati

37、on with One RFSS of Each Type . 63 2.3.2.4 Initial conditions . 65 2.3.2.5 Procedure 66 2.3.2.5.1 Test case 1 - Group Call granted Unconfirmed All Units Roaming . 66 2.3.2.5.2 Test Case 2 Group Call granted Unconfirmed No Units Roaming . 67 2.3.2.5.3 Test Case 3 Group Call granted Confirmed All Unit

38、s Roaming 67 2.3.2.5.4 Test Case 4 - Group Call granted Confirmed No Units Roaming 68 2.3.2.5.5 Test Case 5 Confirmed Group Voice Call Granted After RF Resources Become Available All Units Roaming 68 2.3.2.5.6 Test Case 6 Confirmed Group Voice Call Granted After RF Resources Become Available No Unit

39、s Roaming 70 2.3.2.5.7 Test case 7 - Group Call denied All Units Roaming and No Units Roaming 71 2.3.2.5.8 Test case 8 Heartbeat Verification - Group Call granted Unconfirmed All Units Roaming 71 2.3.2.5.9 Test Case 9 Heartbeat Verification - Group Call granted Unconfirmed No Units Roaming 72 2.3.2.

40、5.10 Test case 10 Group Call granted Unconfirmed All Units Roaming Home RFSS Initially Has RTP Resources 72 TIA-102.CACD-C iv 2.3.2.5.11 Test case 11 Group Call granted Unconfirmed No Units Roaming Home RFSS Initially Has RTP Resources . 73 2.3.2.5.12 Test case 12 - Group call interrupt (Dispatcher

41、Audio Takeover) No Units Roaming 74 2.3.2.5.13 Test case 13 - Group call routing All Units Roaming . 74 2.3.2.5.14 Test case 14 - Group call routing No Units Roaming 75 2.3.2.5.15 Test Case 15 Console Takeover of another Console - No Units Roaming . 75 2.3.3 TEST SUITE: Unit-to-Unit Voice Call 76 2.

42、3.3.1 Description 76 2.3.3.2 Expected behavior 76 2.3.3.3 Unit-to-Unit Call Configuration using an ISSI . 77 2.3.3.3.1 Unit-to-Unit Call Test Configuration with Two Identical RFSSs of Each Type . 77 2.3.3.3.2 Unit-to-Unit Call Test Environment with One RFSS of each Type 82 2.3.3.3.3 Unit-to-Unit Cal

43、l RFSS and SU Configuration with Two Identical RFSSs of Each Type . 84 2.3.3.3.4 Unit-to-Unit Call RFSS and SU Configuration with One RFSS of Each Type . 87 2.3.3.4 Initial conditions . 88 2.3.3.5 Procedure . 90 2.3.3.5.1 Test case 1 - Unit-to-Unit Call with Target Availability Check . 91 2.3.3.5.2

44、Test case 2 - Unit-to-Unit Call with Target Availability Check refused by target . 91 2.3.3.5.3 Test case 3 Unit-to-Unit Call with Target Availability Check queued FNE Implementation Checks the Availability of the Traffic Channel After Availability Check. 92 2.3.3.5.4 Test case 4 Unit-to-Unit Call w

45、ith Target Availability Check queued FNE Implementation Checks the Availability of the Traffic Channel Before Availability Check. 93 2.3.3.5.5 Test case 5 - Unit-to-Unit Call without Target Availability Check 94 2.3.3.5.6 Test case 6 - Unit-to-Unit Call without Target Availability Check queued . 94

46、2.3.3.5.7 Test case 7 - Unit-to-Unit Call denied 95 2.3.3.5.8 Test case 8 - Unit-to-Unit Call Unable to Allow Protected Mode Request 96 2.3.3.5.9 Test case 9 - Unit-to-Unit Call Unable to Allow Unprotected Mode Request 96 2.3.3.5.10 Test case 10 - Unit-to-Unit Call Setup denied due to lack of RTP Re

47、sources at Called Serving RFSS . 97 2.3.3.5.11 Test case 11 - Unit-to-Unit Call with Target Availability Check, Called SU Roams to New Called Serving RFSS . 98 2.3.3.5.12 Test case 12 - Unit-to-Unit Call without Target Availability Check and Called SU Roams to new Called Serving RFSS . 98 2.3.3.5.13

48、 Test case 13 - Unit-to-Unit Call with Target Availability Check, Calling SU Roams to New Calling Serving RFSS 99 2.3.3.5.14 Test case 14 - Unit-to-Unit Call without Target Availability Check and Calling SU Roams to a new Calling Serving RFSS 100 2.3.3.5.15 Test case 15 - Unit-to-Unit Call with Targ

49、et Availability Check, Called SU Roams to New Called Serving RFSS with no Traffic Channels 101 2.3.3.5.16 Test case 16 - Unit-to-Unit Call without Target Availability Check and Called SU Roams to new Called Serving RFSS with no Traffic Channels . 101 2.3.3.5.17 Test case 17 - Unit-to-Unit Call with Target Availability Check, Calling SU Roams to New Calling Serving RFSS with no Traffic Channels . 102 2.3.3.5.18 Test case 18 - Unit-to-Unit Call without Target Availability Check and Calling SU Roams to a new Ca