NXDN NXDN Technical pecifications Part 2: onformance Test ub-part E: Trunking Operation Test (Type-D) NXDN T 2-E Version 1.0 November 2012 NXDN orum
ontents 1.ntroduction... 1 2.References... 1 3.Abbreviations... 1 4.Outline... 2 5.Test Procedures... 3 5.1.U Testing... 4 5.1.1.ink Tests... 4 5.1.1.1.ink Accept Test... 4 5.1.1.2.ink Refuse... 5 5.1.1.3.ink of Traffic Repeater... 6 5.1.2.Group Voice all Tests... 10 5.1.2.1.onference Group all Test... 10 5.1.2.2.Broadcast Group all Test... 12 5.1.3.ndividual Voice all Tests... 13 5.1.3.1.ndividual all Test... 13 5.1.4.All all Tests... 14 5.1.4.1.Testing the alling U... 14 5.1.4.2.Testing the alled U... 14 5.1.5.hort Data all Tests... 15 5.1.5.1.Broadcast hort Data all Test... 16 5.1.5.2.Unit to Unit hort Data all Test... 18 5.1.6.Data all Tests... 20 5.1.6.1.Broadcast Data all Test... 20 5.1.6.2.Unit to Unit Data all Test... 21 5.1.7.tatus all Tests... 24 5.1.7.1.Broadcast tatus all Test... 24 5.1.7.2.tatus all Test... 25 5.1.8.tatus nquiry Tests... 27 5.1.8.1.Testing the alling U... 27 5.1.8.2.Testing the alled U... 28 5.1.9.Remote ontrol Tests... 29 5.1.9.1.Testing the alling U... 29 5.1.9.2.Testing the alled U... 29 5.1.10.Paging Tests... 31 5.1.10.1.Testing the alling U... 31 5.1.10.2.Testing the alled U... 31 5.1.11.Emergency Tests... 32 5.1.11.1.Emergency all... 32 5.1.11.2.Emergency Alert... 32 5.1.12.ate Entry Test... 33 5.1.12.1.onference Group all... 33 5.1.13.Priority Monitor Test... 34 5.1.14.Transmission Trunking Test... 35 5.1.15.Message Trunking Test... 36 5.1.16.Encryption Tests... 37 5.1.16.1.Encrypted Voice all Tests... 37 opyright 2007-2012 com ncorporated and JV KENWOOD orporation i
5.1.16.2.Encrypted hort Data all Tests... 37 5.1.16.3.Encrypted Data all Tests... 38 5.1.17.Registration Test... 41 5.1.17.1.Registration Accept... 41 5.1.17.2.Registration ail... 42 5.1.17.3.Registration Refuse... 42 5.1.18.Registration ommand Test... 45 5.1.19.Registration lear Test... 45 5.1.19.1.Registration lear Accept... 46 5.1.19.2.Registration lear ail... 46 5.1.19.3.Registration lear Refuse... 46 5.1.20.Group Registration Test... 48 5.1.20.1.Group Registration Accept... 48 5.1.20.2.Group Registration ail... 49 5.1.20.3.Group Registration Refuse... 49 5.1.21.Authentication Tests... 50 5.1.21.1.Authentication during Registration Process... 50 5.1.21.2.Authentication nquiry by Trunking Repeater... 51 5.1.22.ystem Data Write Tests... 52 5.1.22.1.ystem Data Write during Registration Process... 52 5.1.22.2.ystem Data Write by Trunking Repeater... 52 5.1.23.ite Roaming Test... 54 5.1.24.Halt Repeater Test... 55 5.1.25.D Validation Test... 55 5.2.TR Testing... 56 5.2.1.dle Message Test... 56 5.2.1.1.dle Repeater Message Test... 56 5.2.1.2.ite D Message Test... 57 5.2.2.ink Tests... 59 5.2.2.1.ink Accept Test... 59 5.2.2.2.ink Refuse... 60 5.2.2.3.ink of Traffic Repeater... 60 5.2.3.Group Voice all Tests... 65 5.2.3.1.onference Group all Test... 65 5.2.3.2.Broadcast Group all Test... 66 5.2.4.ndividual Voice all Tests... 68 5.2.4.1.ndividual all Test... 68 5.2.5.All all Test... 68 5.2.6.hort Data all Tests... 69 5.2.6.1.Broadcast hort Data all Test... 69 5.2.6.2.Unit to Unit hort Data all Test... 69 5.2.7.Data all Tests... 71 5.2.7.1.Broadcast Data all Test... 71 5.2.7.2.Unit to Unit Data all Test... 71 5.2.8.tatus all Tests... 73 5.2.8.1.Broadcast tatus all Test... 73 5.2.8.2.ndividual tatus all Test... 74 5.2.9.tatus nquiry Test... 76 5.2.9.1.tatus nquiry uccess... 76 opyright 2007-2012 com ncorporated and JV KENWOOD orporation ii
5.2.10.Remote ontrol Test... 78 5.2.10.1.Remote ontrol uccess... 78 5.2.11.Emergency Test... 80 5.2.11.1.Emergency all... 80 5.2.11.2.Emergency Alert... 80 5.2.12.Transmission Trunking Test... 81 5.2.13.Message Trunking Test... 81 5.2.14.Encryption Test... 82 5.2.15.Registration Test... 83 5.2.15.1.Registration Accept... 83 5.2.16.Registration ommand Test... 86 5.2.17.Registration lear Test... 86 5.2.17.1.Registration lear Accept... 86 5.2.18.Group Registration Test... 88 5.2.18.1.Group Registration Accept... 88 5.2.19.Authentication Tests... 89 5.2.19.1.Authentication during Registration Process... 89 5.2.19.2.Authentication nquiry by Trunking Repeater... 90 5.2.20.ystem Data Write Tests... 91 5.2.20.1.ystem Data Write during Registration Process... 91 5.2.20.2.ystem Data Write by Trunking Repeater... 91 5.2.21.ite Roaming Test... 93 5.2.22.Halt Repeater Test... 94 5.2.23.D Validation Test... 94 6.Appendix... 95 6.1.amples of Test rame... 95 6.1.1.rame Data for ingle Trunked ystem... 96 6.1.1.1.rame Data for ink... 96 6.1.1.2.rame Data for Voice all... 98 6.1.1.3.rame Data for hort Data all... 102 6.1.1.4.rame Data for Data all... 106 6.1.1.5.rame Data for tatus all... 110 6.1.1.6.rame Data for cramble Encrypted Voice all... 114 6.1.1.7.rame Data for cramble Encrypted hort Data all... 116 6.1.1.8.rame Data for cramble Encrypted Data all... 118 6.1.2.rame Data for Multi Trunked ystem... 120 6.1.2.1.rame Data for ink... 120 6.1.2.2.rame Data for Voice all... 122 6.1.2.3.rame Data for hort Data all... 126 6.1.2.4.rame Data for Data all... 130 6.1.2.5.rame Data for tatus all... 134 6.1.2.6.rame Data for cramble Encrypted Voice all... 138 6.1.2.7.rame Data for cramble Encrypted hort Data all... 140 6.1.2.8.rame Data for cramble Encrypted Data all... 142 7.Revision History... 144 opyright 2007-2012 com ncorporated and JV KENWOOD orporation iii
igures igure 5.1-1 ink Tests etup... 4 igure 5.1-2 hort Data all Tests etup... 15 igure 5.1-3 Priority Monitor Test... 34 igure 5.1-4 et up for U Test... 41 igure 5.1-5 ite Roaming Test etup... 54 igure 5.2-1 dle Message Tests etup... 56 igure 5.2-2 ink Tests etup... 59 igure 5.2-3 ite Roaming Test etup... 93 igure 6.1-1 rame tructure for ink (nbound)... 96 igure 6.1-2 rame tructure for ink (Outbound)... 97 igure 6.1-3 rame tructure for ink (Outbound)... 97 igure 6.1-4 rame tructure for Voice all (nbound)... 98 igure 6.1-5 rame tructure for Voice all (Outbound)... 100 igure 6.1-6 rame tructure for hort Data all (nbound)... 102 igure 6.1-7 rame tructure for hort Data all (Outbound)... 104 igure 6.1-8 rame tructure for Data all (nbound)... 106 igure 6.1-9 rame tructure for Data all (Outbound)... 108 igure 6.1-10 rame tructure for Data all using (nbound)... 110 igure 6.1-11 rame tructure for Data all using AH3 (nbound)... 110 igure 6.1-12 rame tructure for Data all using (Outbound)... 112 igure 6.1-13 rame tructure for Data all using AH3 (Outbound)... 112 igure 6.1-14 rame tructure for ink (nbound)... 120 igure 6.1-15 rame tructure for ink (Outbound)... 121 igure 6.1-16 rame tructure for ink (Outbound)... 121 igure 6.1-17 rame tructure for Voice all (nbound)... 122 igure 6.1-18 rame tructure for Voice all (Outbound)... 124 igure 6.1-19 rame tructure for hort Data all (nbound)... 126 igure 6.1-20 rame tructure for hort Data all (nbound)... 128 igure 6.1-21 rame tructure for Data all (nbound)... 130 igure 6.1-22 rame tructure for Data all (Outbound)... 132 igure 6.1-23 rame tructure for tatus all using (nbound)... 134 igure 6.1-24 rame tructure for tatus all using AH3 (nbound)... 134 igure 6.1-25 rame tructure for tatus all using (Outbound)... 136 igure 6.1-26 rame tructure for tatus all using AH3 (Outbound)... 136 Tables Table 5.1-1 M NO4 / NO2 message... 6 Table 5.1-2 OM NO4 / NO2 (Busy Repeater Message) message... 6 Table 5.1-3 OM NO4 / NO2 (ree Repeater Message) message... 7 Table 5.1-4 OM NO4 / NO2 (ite D Message Message) message... 7 opyright 2007-2012 com ncorporated and JV KENWOOD orporation iv
Table 5.1-5 M / OM NO4 (EOT) message... 7 Table 5.1-6 A_REQ message... 7 Table 5.1-7 A_ONN_REP message... 8 Table 5.1-8 A_REP message... 8 Table 5.1-9 TX_RE(nbound) message... 8 Table 5.1-10 TX_RE (Outbound) message... 9 Table 5.1-11 M NO3 message... 11 Table 5.1-12 M NO1 message... 11 Table 5.1-13 OM NO3 message... 11 Table 5.1-14 OM NO1 message... 12 Table 5.1-15 VA message... 12 Table 5.1-16 DA_REQ(Header) message... 17 Table 5.1-17 DA_REP message... 17 Table 5.1-18 DA (Header) message... 23 Table 5.1-19 DA_AK message... 23 Table 5.1-20 TAT_REQ message... 26 Table 5.1-21 TAT_REP message... 26 Table 5.1-22 TAT_NQ_REQ message... 28 Table 5.1-23 TAT_NQ_REP message... 28 Table 5.1-24 REM_ON_REQ message... 30 Table 5.1-25 REM_ON_REP message... 30 Table 5.1-26 VA message (Encryption)... 39 Table 5.1-27 Encryption Tests ondition for Voice all... 39 Table 5.1-28 DA_REQ(Header) message (Encryption)... 39 Table 5.1-29 Encryption Tests ondition for hort Data all / Data all... 39 Table 5.1-30 DA(Header) message (Encryption)... 40 Table 5.1-31 M NO4 message... 43 Table 5.1-32 OM NO4 (Busy Repeater Message) message... 43 Table 5.1-33 OM NO4 (ree Repeater Message) message... 43 Table 5.1-34 OM NO4 / NO2 (ite D Message) message... 43 Table 5.1-35 M / OM NO4 (EOT) message... 43 Table 5.1-36 A_REQ message... 43 Table 5.1-37 A_REP message... 44 Table 5.1-38 REG_REQ message... 44 Table 5.1-39 REG_REP message... 44 Table 5.1-40 TX_RE (nbound) message... 44 Table 5.1-41 OM NO4 (REG_OM) message... 45 Table 5.1-42 REG REQ message... 47 Table 5.1-43 REG REP message... 47 Table 5.1-44 GRP_REG_REQ message... 49 Table 5.1-45 GRP_REG_REP message... 49 Table 5.1-46 AUTH_NQ_REQ message... 51 Table 5.1-47 AUTH_NQ_REP message... 51 Table 5.1-48 DWR (Header) message... 53 Table 5.1-49 DWR_AK message... 53 Table 5.1-50 ite Parameter... 54 Table 5.1-51 OM NO4 (Halt Repeater Message) message... 55 opyright 2007-2012 com ncorporated and JV KENWOOD orporation v
Table 5.2-1 OM NO4 (dle Repeater Message) message... 57 Table 5.2-2 DE message... 57 Table 5.2-3 TX_RE(Outbound) message... 57 Table 5.2-4 OM NO4 (ite D Message) message... 58 Table 5.2-5 RV_NO message... 58 Table 5.2-6 ADJ_TE_NO message... 58 Table 5.2-7 M NO4 / NO2 message... 61 Table 5.2-8 OM NO4 / NO2 (Busy Repeater Message) message... 61 Table 5.2-9 OM NO4 / NO2 (ree Repeater Message) message... 61 Table 5.2-10 OM NO4 / NO2 (ite D Message) message... 61 Table 5.2-11 M / OM NO4 (EOT) message... 62 Table 5.2-12 A_REQ message... 62 Table 5.2-13 A_ONN_REP message... 62 Table 5.2-14 A_REP message... 63 Table 5.2-15 TX_RE(nbound) message... 63 Table 5.2-16 TX_RE(Outbound) message... 64 Table 5.2-17 M NO3 message... 66 Table 5.2-18 M NO1 message... 66 Table 5.2-19 OM NO3 message... 66 Table 5.2-20 OM NO1 message... 66 Table 5.2-21 VA message... 67 Table 5.2-22 DA_REQ(Header) message... 70 Table 5.2-23 DA_REP message... 70 Table 5.2-24 DA(Header) message... 72 Table 5.2-25 DA_AK message... 72 Table 5.2-26 TAT_REQ message... 75 Table 5.2-27 TAT_REP message... 75 Table 5.2-28 TAT_NQ_REQ message... 77 Table 5.2-29 TAT_NQ_REP message... 77 Table 5.2-30 REM_ON_REQ message... 79 Table 5.2-31 REM_ON_REP message... 79 Table 5.2-32 VA message (Encryption)... 82 Table 5.2-33 M NO4 message... 83 Table 5.2-34 OM NO4 (Busy Repeater Message) message... 83 Table 5.2-35 OM NO4 (ree Repeater Message) message... 84 Table 5.2-36 OM NO4 / NO2 (ite D Message) message... 84 Table 5.2-37 M / OM NO4 (EOT) message... 84 Table 5.2-38 A_REQ message... 84 Table 5.2-39 A_REP message... 84 Table 5.2-40 REG_REQ message... 84 Table 5.2-41 REG_REP message... 85 Table 5.2-42 TX_RE (nbound) message... 85 Table 5.2-43 TX_RE (Outbound) message... 85 Table 5.2-44 REG REQ message... 87 Table 5.2-45 REG REP message... 87 Table 5.2-46 GRP_REG_REQ message... 88 Table 5.2-47 GRP_REG_REP message... 88 opyright 2007-2012 com ncorporated and JV KENWOOD orporation vi
Table 5.2-48 AUTH_NQ_REQ message... 90 Table 5.2-49 AUTH_NQ_REP message... 90 Table 5.2-50 DWR (Header) message... 92 Table 5.2-51 DWR_AK message... 92 Table 5.2-52 ite Parameter... 93 Table 6.1-1 Ds etup for ample rame Data... 95 Table 6.1-2 Encryption etup for ample rame Data... 95 Table 6.1-3 Packet nformation for hort Data all... 102 Table 6.1-4 Packet nformation for Data all... 106 Table 6.1-5 Packet nformation for hort Data all... 126 Table 6.1-6 Packet nformation for Data all... 130 opyright 2007-2012 com ncorporated and JV KENWOOD orporation vii
Disclaimer The information presented here is intended to be for clarification and/or information purpose only, and care has been taken to keep the contents as neutral and accurate as possible. The use or practice of contents of the information may involve the use of intellectual property rights ( PR ), including pending or issued patents, or copyrights, owned by one or more parties. The NXDN orum makes no search or investigation for PR, nor the NXDN orum makes no arrangement of licensing negotiation for PR between the user and the owner of PR. 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 purpose or use, its merchantability and its non-infringement of any third party s PR. The NXDN orum expressly disclaims any and all responsibilities for the accuracy of the contents and makes no representations or warranties regarding the content s compliance with any applicable statute, rule or regulation. The NXDN orum 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 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 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 the NXDN orum without such limitations. Document opyrights This document is copyrighted by JV KENWOOD orporation and com ncorporated ( copyright holder ). No duplication, alteration or distribution of this document or any portion thereof shall take place without the express permission of the copyright holder except downloading from the NXDN orum worldwide web. Reproduction, distribution, or transmission for any purpose in any form or by any means, electronic or mechanical, shall only be allowed with the express permission of the copyright holder. Trademarks NXDN is a registered trademark of com ncorporated and JV KENWOOD orporation. AMBE+2 is a trademark of Digital Voice ystems, nc. opyright 2007-2012 com ncorporated and JV KENWOOD orporation viii
1. ntroduction This test specification provides a test procedure and determination criteria for trunking operations interoperability for radio equipment designed in accordance with Air nterface specifications of NXDN Type-D (Distributed ogic Trunked ystem). This interoperability testing enables verification of interoperability among radio equipment manufactured by different manufacturers, or among different radio equipment manufactured by the same manufacturer, or of radio equipment of which the firmware is updated. Defining test items for all of functions and conditions defined in the Air nterface specifications results in an enormous amount of documents and is unrealistic. Additionally defining the test procedures and related determination criteria for the system dependent functions is difficult. Hence, test items presented in this document do not contain all of functions and conditions and are limited to the scope that enables guarantee of a minimum interoperability. As well as conducting test items described in this document, it is recommended that every radio manufacturer verifies that radio equipment including items undefined by this document are in conformity with the NXDN specifications by conducting more detailed testing by referring to the Air nterface specifications. The ommon Air nterface Test as presented in RE [3] shall take place prior to this testing. 2. References Reference documents are listed below. RE [1] Part 1-E ommon Air nterface (Type-D) RE [2] Part 1- Trunking Procedures RE [3] Part 2-B ommon Air nterface Test RE [4] Part 2- Basic Operation Test 3. Abbreviations To help understand this document, abbreviations are listed below. A ommon Air nterface ast Associated ontrol hannel 1 AH3 ast Associated ontrol hannel 3 W rame ync Word M nbound ignaling Message ink nformation hannel OM Outbound ignaling Message RTH2 R Traffic hannel 2 RU Repeater Unit H ignaling ontrol hannel U ubscriber Unit T Trunking ontroller TR Trunking Repeater TR Trunking Repeater ite UDH2 User Data hannel 2 U User pecific hannel Voice hannel opyright 2007-2012 com ncorporated and JV KENWOOD orporation 1
4. Outline There are two types of test methods available for interoperability testing of trunking operation as below: Method 1: A method where an U (or a TR) to be tested is tested by an interoperability tester Method 2: A method where a testing takes place between an U and TR Method 1 is a test method using an interoperability tester. By verifying that the unit under test conforms to the specifications specified in ommon Air nterface of the RE [1] and in Trunking Procedures of the RE [2], method 1 indirectly verifies that the unit under test has interoperability with other radio equipment which also conforms to the specifications. Method 2 is a test method under the actual operation condition. This method allows testing without using an interoperability tester required by Method 1. f neither U nor TR that has been verified in accordance with this document is available, both U and TR shall be treated as units under test. Therefore, in the event that any test item fails, it is essential to specify which has nonconformity, either U or TR. Also, even if a test item passes, it is necessary to fully verify that both U and TR are in conformity with the specifications specified in RE [1] and RE [2]. A configuration diagram for testing is described in the configuration for Method 1; however, unless otherwise specified, either of two test methods can be employed. onfiguration of an interoperability tester is not specified in this document; hence, the configuration shall be prepared using an appropriate method by the respective manufacturer that performs the test. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 2
5. Test Procedures n this section, test methods and judging criterions are presented. Test methods for all functions are not described in this document. unctions not specified in this document shall be tested by the respective manufacturer using an appropriate test method. Each test method shall verify that the contents of messages exchanged between an U and TR are correct and the U and TR behave according to proper procedure upon transmit or receipt of these messages. A way of checking the data string of the layer 3 message is not specified in this document. or example, it can be verified by outputting the received log data from a unit under test or interoperability tester, or by preparing a monitoring receiver which can receive both inbound signals from the unit under test and outbound signals from the interoperability tester. Unless otherwise specified, the receive signal input level of the unit under test shall be -47 dbm or shall be equal to a significantly high level. The data string is, in principle, described in the hexadecimal format; however, the letter b shall be suffixed in the case that the data string is described in the binary format. n the transmit sequence of a data string, transmission begins with the leftmost value, and the rightmost value is sent at the end. The setting values of ource D and Destination D used by tests are not defined in particular, so they can be selected in the range specified in RE [1]. A Tone Test Pattern or actual audio signals can be applied to the voice signals to be used for voice call testing. ontents of User Data to be used for data call testing are arbitrary. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 3
5.1. U Testing 5.1.1. ink Tests n this test, we evaluate the validity of the description of the messages used in ink establishment operation prior to other operations including all, and verify whether or not U operates as intended in response to those messages. The connection configuration of this test is shown in igure 5.1-1. uppose a calling U as U No.1, a called U as U No.2. U No.1 nteroperability Tester U NO.2 igure 5.1-1 ink Tests etup ollowing 10 varieties of messages will be used. Table 5.1-1 : M NO4 / NO2 messages Table 5.1-2 : OM NO4 / NO2 (Busy Repeater Message) message Table 5.1-3 : OM NO4 / NO2 (ree Repeater Message) message Table 5.1-4 : OM NO4 / NO2 (ite D Message Message) message Table 5.1-5 : M / OM NO4 (EOT) message Table 5.1-6 : A_REQ message from U Table 5.1-7 :A_ONN_REP message from nteroperability Tester Table 5.1-8 : A_REP message from nteroperability Tester Table 5.1-9 : TX_RE(nbound) message from U Table 5.1-10 : TX_RE(Outbound) message from an nteroperability Tester 5.1.1.1. ink Accept Test This ection shows the case in which a link is established successfully. 5.1.1.1.1. alling U (1) Turn the power of U No.1 ON, and make this U be in an idle (transmitting) mode. (2) Transmit a message OM NO4 / NO2 (ree Repeater Message) shown in Table 5.1-3 from nteroperability Tester, whereby informs the U that the Home repeater for the U is ree Repeater. (3) When a PTT switch of U No.1 is turned ON, verify that TR on transmits A_REQ message shown in Table 5.1-6 that includes NO4 message shown in Table 5.1-1 in H. (4) When a message A_ONN_REP shown in Table 5.1-7 indicating a queue not specifying any other cause that includes any of NO4 messages shown in Table 5.1-2 to Table 5.1-4 in H has been transmitted from an nteroperability Tester, verify that the U becomes an idle mode. (5) When a A_REP message shown in Table 5.1-8 that includes NO4 message shown in Table 5.1-2 has been transmitted from nteroperability Tester to H, verify that U No.1 starts operations such as all. 5.1.1.1.2. alled U (1) Turn the power of U No.2 ON, and make this U be in an idle (receiving) mode. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 4
(2) When a message A_ONN_REP shown in Table 5.1-7 indicating a queue not specifying any other cause that includes any of NO4 messages shown in Table 5.1-2 to Table 5.1-4 in H has been transmitted from an nteroperability Tester, verify that the U, verify that the U remains to be an idle mode. (3) When a A_REP message shown in Table 5.1-8 that includes NO4 message shown in Table 5.1-2 has been transmitted from nteroperability Tester to H, verify that U No.2 becomes standby mode for receiving any Messages including all which will be transmitted subsequently. 5.1.1.2. ink Refuse This ection shows the case in which link establishment is rejected. 5.1.1.2.1. alling U (1) Turn the U No. 1 ON and keep it in the idle state. (2) Transmit a message OM NO4 / NO2 (ree Repeater Message) shown in Table 5.1-3 from nteroperability Tester, whereby informs the U that the Home repeater for the U is ree Repeater. (3) When a PTT switch of U No.1 is turned ON, verify that TR on transmits A_REQ message shown in Table 5.1-6 that includes NO4 message shown in Table 5.1-1 to H. (4) When a message TX_RE(Outbound) indicating that the communication permission request is refused shown in Table 5.1-7 that includes any one of NO4 (EOT) messages shown in Table 5.1-2 to Table 5.1-4 in H has been transmitted from an nteroperability Tester, verify that U No.1 transmits TX_RE (nbound) message shown in Table 5.1-9 that includes NO4 (EOT) message shown in Table 5.1-5, and shifts its channel frequency to the channel frequency of the Home repeater. 5.1.1.2.2. alled U (1) Turn the U No. 2 ON and keep it in the idle state. (2) When a message A_ONN_REP shown in Table 5.1-7 indicating refused that includes any of NO4 messages shown in Table 5.1-2 to Table 5.1-4 in H has been transmitted from an nteroperability Tester, verify that the U, verify that the U remains to be an idle mode. (3) When a message TX_RE(Outbound) shown in (4) Table 5.1-10 that includes NO4 (EOT) message shown in Table 5.1-5 has been transmitted from an nteroperability Tester, verify that U No.2 remains to be in the idle mode. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 5
5.1.1.3. ink of Traffic Repeater This ection shows a test method in which ink operation is performed via any of repeaters other than the Home repeater. 5.1.1.3.1. alling U (1) Turn the U No. 1 ON and keep it in the idle state. (2) Transmit a message OM NO4 / NO2 (ree Repeater Message) shown in Table 5.1-3 from nteroperability Tester, whereby informs the U that the non-home repeater for the U is ree Repeater. (3) When a PTT switch of U No.1 is turned ON, verify that the U transmits a A_REQ message shown in Table 5.1-6 that includes a NO4 message shown in Table 5.1-1 to H, and changes its channel frequency to that of ree Repeater instructed at step (1) that is not the of the U. (4) When a message A_ONN_REP shown in Table 5.1-7 indicating a queue not specifying any other cause that includes any of NO4 messages shown in Table 5.1-2 to Table 5.1-4 in H has been transmitted from an nteroperability Tester, verify that the U becomes an idle mode. (5) When a A_REP message shown in Table 5.1-8 which includes NO4 message shown in Table 5.1-2 in H from nteroperability Tester, verify that the U No.1 shifts its channel frequency to that of the communication channel. 5.1.1.3.2. alled U (1) Turn the U No. 1 ON and keep it in the idle state. (2) When OM NO4 / NO2 (Busy Repeater Message) shown in Table 5.1-2 has been transmitted from an nteroperability Tester, verify that the U No.2 shifts its channel frequency to the channel frequency of the non-home repeater, and then, becomes standby mode for receiving any Messages including all which will be transmitted subsequently. tructure Area Repeater in Use Destination G/U Table 5.1-1 ingle Trunked ystem 00b (NO4) 10b (NO2) Value of Area Value of Use Repeater number Value of number Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) Group=0b/Unit=1b (Destination D) M NO4 / NO2 message Multi Trunked ystem Destination Prefix Value of Destination Prefix Table 5.1-2 tructure Area Go to Repeater Destination G/U OM NO4 / NO2 (Busy Repeater Message) message ingle Trunked ystem 00b (NO4) 10b (NO2) Value of Area Value of Go to Repeater number Value of number Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) Group=0b/Unit=1b (Destination D) Multi Trunked ystem Destination Prefix Value of Destination Prefix opyright 2007-2012 com ncorporated and JV KENWOOD orporation 6
Table 5.1-3 tructure Area ree Repeater1 ree Repeater2 D OM NO4 / NO2 (ree Repeater Message) message ingle Trunked ystem Multi Trunked ystem 00b (NO4) 10b (NO2) Value of Area Value of ree Repeater number (NOTE: use a channel frequency which is idle for communication) Value of ree Repeater number (NOTE: use a channel frequency which is idle for communication) 7 Table 5.1-4 OM NO4 / NO2 (ite D Message Message) message ingle Trunked ystem Multi Trunked ystem tructure 00b (NO4) - 10b (NO2) Area - Value of Area ite Type - Value of ite Type ite ode - Value of ite ode D - 79 tructure Area Repeater in Use / Go to Repeater Destination G/U Table 5.1-5 ingle Trunked ystem 00b (NO4) 10b (NO2) Value of Area 11111b M / OM NO4 (EOT) message Value of number Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) Group=0b/Unit=1b (Destination D) Multi Trunked ystem Destination Prefix Value of Destination Prefix Table 5.1-6 A_REQ message ingle Trunked ystem Multi Trunked ystem Option 00 (ndividual all, Group all, All all) 80 (Emergency all) 10 (ndividual all, Group all, All all) 90 (Emergency all) all Type 100b (ndividual all) 001b (onference Group all / All all) 000b (Broadcast all) ource ource Prefix Value of number Value of ource Prefix Unit D of U No.1 Destination Value of number Destination Prefix Value of Destination Prefix Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) ystem D Option - 10000b / 01000b ystem D - Value of ystem D opyright 2007-2012 com ncorporated and JV KENWOOD orporation 7
Option all Type ource Destination ause (VD) Table 5.1-7 A_ONN_REP message ingle Trunked ystem 00 (ndividual all, Group all, All all) 80 (Emergency all) 100b (ndividual all) 001b (onference Group all / All all) 000b (Broadcast all) Value of number Unit D of U No.1 Value of number Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) 0111111b (a queue not specifying any other cause) 0010010b (a service of a calling U is not allowed.) Multi Trunked ystem 10 (ndividual all, Group all, All all) 90 (Emergency all) ource Prefix Prefix of U No.1 Destination Prefix Value of Destination Prefix ystem D Option - 10000b / 01000b ystem D - Value of ystem D Option all Type ree Repeater ource Table 5.1-8 A_REP message ingle Trunked ystem 00 (ndividual all, Group all, All all) 80 (Emergency all) 100b (ndividual all) 001b (onference Group all / All all) 000b (Broadcast all) Any value in the range of 00001b-11110b Value of number Unit D of U No.1 Multi Trunked ystem 10 (ndividual all, Group all, All all) 90 (Emergency all) ource Prefix Prefix of U No.1 Destination Value of number Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) Destination Prefix Value of Destination Prefix ystem D Option - 10000b / 01000b ystem D - Value of ystem D Option all Type ource Table 5.1-9 TX_RE(nbound) message ingle Trunked ystem 00 (ndividual all, Group all, All all) 80 (Emergency all) 100b (ndividual all) 001b (onference Group all / All all) 000b (Broadcast all) Value of number Unit D of U No.1 Multi Trunked ystem 10 (ndividual all, Group all, All all) 90 (Emergency all) ource Prefix Prefix of U No.1 Destination Value of number Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) Destination Prefix Value of Destination Prefix opyright 2007-2012 com ncorporated and JV KENWOOD orporation 8
Option all Type ree Repeater ource Table 5.1-10 TX_RE (Outbound) message ingle Trunked ystem 00 (ndividual all, Group all, All all) 80 (Emergency all) 100b (ndividual all) 001b (onference Group all / All all) 000b (Broadcast all) Any value in the range of 00001b-11110b Value of number Unit D of U No.1 Multi Trunked ystem 10 (ndividual all, Group all, All all) 90 (Emergency all) ource Prefix Prefix of U No.1 Destination Value of number Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) Destination Prefix Value of Destination Prefix opyright 2007-2012 com ncorporated and JV KENWOOD orporation 9
5.1.2. Group Voice all Tests This test shall verify that contents of messages used for Group Voice all are correct, that the unit under test correctly responds to these messages, and that a receiving unit outputs normal received audio signal. This test includes the test methods for the following two modes: (1) onference Group all (2) Broadcast Group all igure 5.1-1shows the configuration diagram for testing. U No. 1 and U No. 2 shall be tested as the calling unit and the called unit respectively. The following 15 types of messages shall be applied. Table 5.1-1 : M NO4 / NO2 messages Table 5.1-2 : OM NO4 / NO2 (Busy Repeater Message) message Table 5.1-3 : OM NO4 / NO2 (ree Repeater Message) message Table 5.1-4 : OM NO4 / NO2 (ite D Message Message) message Table 5.1-5 : M / OM NO4 (EOT) message Table 5.1-6 : A_REQ message from U Table 5.1-7 : A_ONN_REP message from nteroperability Tester Table 5.1-8 : A_REP message from nteroperability Tester Table 5.1-9 : TX_RE(nbound) message from U Table 5.1-10 : TX_RE(Outbound) message from an nteroperability Tester Table 5.1-11 : M NO3 message Table 5.1-12 : M NO1 message Table 5.1-13 : OM NO3 message Table 5.1-14 : OM NO1 message Table 5.1-15 : VA message from U 5.1.2.1. onference Group all Test n this test, parameters for messages to be used shall apply the values for onference Group all. 5.1.2.1.1. Testing the alling U 5.1.2.1.1.1. Group all uccess (1) ink connection will be shown in ection 5.1.1. (2) When A_REP message shown in Table 5.1-8 has been transmitted from an nteroperability Tester, verify that the called U sends a VA message shown in Table 5.1-815 which includes NO4 message shown in Table 5.1-1 to H. (3) Verify that the called U sends a vocal data() after transmitting a VA message. Be sure that H sequentially includes NO1 to NO4 messages shown in Table 5.1-1, Table 5.1-11 and Table 5.1-12, respectively. (4) After a PTT switch has been released, verify that the called U transmits a "TX_RE(nbound)" massage shown in Table 5.1-9 that includes " NO4 (EOT)" message shown in Table 5.1-5. (5) After a final frame that includes TX_RE message has been transmitted at step (4), verify that the U ends the transmission, and returns its channel frequency to the channel frequency of the Home repeater. 5.1.2.1.2. Testing the alled U (1) Turn the U No. 2 ON and keep it in the idle state. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 10
(2) When a VA message shown in Table 5.1-15 that includes any of NO4 messages shown in Table 5.1-2 to Table 5.1-4 in H, and vocal data() that sequentially includes any of NO4 / NO2 messages shown in Table 5.1-2 to Table 5.1-4, NO3 shown in Table 5.1-13, and NO1 shown in Table 5.1-14, verify that U No.2 remains to be in the channel frequency of the Home Repeater, and becomes a receiving mode. The procedural steps to follow when including Busy Repeater Message shown in Table 5.1-2, ree Repeater Message shown in Table 5.1-3 and ite D Message shown in Table 5.1-4 on NO2 and NO4 messages will not be stipulated. (3) Verify that U No. 2 outputs normal received audio signal when an interoperability tester makes a voice call transmission. (4) When a TX_RE(Outbound) message shown in (5) Table 5.1-10 that includes NO4 (EOT) message shown in Table 5.1-5 has been transmitted from an nteroperability Tester, verify that the U removes vocals timely and shifts its channel frequency to the channel frequency of the Home repeater. tructure Area Repeater in Use ource Table 5.1-11 ingle Trunked ystem 01b Value of Area Value of Use Repeater number Value of number Unit D of U No.1 M NO3 message Multi Trunked ystem ource Prefix Prefix of U No.1 tructure Area Repeater in Use Pass haracter all Option ipher Type Key D Table 5.1-12 ingle Trunked ystem 11b Value of Area Value of Use Repeater number 11111b 000b (ndividual all, Group all, All all) 100b (Emergency all) 00b 000000b M NO1 message Multi Trunked ystem 010b (ndividual all, Group all, All all) 110b (Emergency all) tructure Area ree Repeater1 ource Table 5.1-13 ingle Trunked ystem 01b Value of Area Value of ree Repeater number Value of number Unit D of U No.1 OM NO3 message Multi Trunked ystem ource Prefix Prefix of U No.1 opyright 2007-2012 com ncorporated and JV KENWOOD orporation 11
tructure Area ree Repeater1 ree Repeater2 all Option ipher Type Key D Table 5.1-14 ingle Trunked ystem 11b Value of Area Value of ree Repeater number Value of ree Repeater number 000b (ndividual all, Group all, All all) 100b (Emergency all) 00b 000000b OM NO1 message Multi Trunked ystem 010b (ndividual all, Group all, All all) 110b (Emergency all) Option all Type ource Table 5.1-15 VA message ingle Trunked ystem 00 (ndividual all, Group all, All all) 80 (Emergency all) 100b (ndividual all) 001b (onference Group all / All all) 000b (Broadcast all) Value of number Unit D of U No.1 Multi Trunked ystem 10 (ndividual all, Group all, All all) 90 (Emergency all) ource Prefix Prefix of U No.1 Destination Value of number Group D (Group all) Unit D of U No.2 (ndividual all) D=7 (All all) Destination Prefix Value of Destination Prefix ipher Type Key D 00b 000000b 5.1.2.2. Broadcast Group all Test n this test, parameters for messages to be used shall apply the values for Broadcast Group all. Tests for the calling U shall be identical to those specified in ection 5.1.2.1.1 and tests for the called U shall be identical to those specified in ection 5.1.2.1.2. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 12
5.1.3. ndividual Voice all Tests This test shall verify that contents of messages used for ndividual Voice all are correct that the unit under test correctly responds to these messages, and that a receiving unit outputs normal received audio signal. igure 5.1-1 shows the configuration diagram for testing. U No. 1 and U No. 2 shall be tested as the calling unit and the called unit respectively. The following 15 types of messages shall be applied. Table 5.1-1 : M NO4 / NO2 message Table 5.1-2 : OM NO4 / NO2 (Busy Repeater Message) message Table 5.1-3 : OM NO4 / NO2 (ree Repeater Message) message Table 5.1-4 : OM NO4 / NO2 (ite D Message Message) message Table 5.1-5 : M / OM NO4 (EOT) message Table 5.1-6 : A_REQ message from U Table 5.1-7 : A_ONN_REP message from nteroperability Tester Table 5.1-8 : A_REP message from nteroperability Tester Table 5.1-9 : TX_RE(nbound) U from U Table 5.1-10 : TX_RE(Outbound) message from nteroperability Table 5.1-11 : M NO3 message Table 5.1-12 : M NO1 message Table 5.1-13 : OM NO3 message Table 5.1-14 : OM NO1 message Table 5.1-15 : VA message from U Values for ndividual all shall be applied to parameters for each Table. 5.1.3.1. ndividual all Test 5.1.3.1.1. Testing the alling U 5.1.3.1.1.1. ndividual all uccess Testing Procedures for these five cases shall be identical to those tests for onference Group all as described in ection 5.1.2.1.1. 5.1.3.1.2. Testing the alled U Testing Procedures shall be identical to those tests for onference Group all as described in ection 5.1.2.1.2. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 13
5.1.4. All all Tests This test shall verify that contents of messages used for All all are correct, that the unit under test correctly responds to these messages, and that receiving unit outputs normal received audio signal. igure 5.1-1 shows the configuration diagram for testing. U No. 1 and U No. 2 shall be tested as the calling unit and the called unit respectively. The following 15 types of messages shall be applied. Table 5.1-1 : M NO4 / NO2 message Table 5.1-2 : OM NO4 / NO2 (Busy Repeater Message) message Table 5.1-3 : OM NO4 / NO2 (ree Repeater Message) message Table 5.1-4 : OM NO4 / NO2 (ite D Message Message) message Table 5.1-5 : M / OM NO4 (EOT) message Table 5.1-6 : A_REQ message from U Table 5.1-7 : A_ONN_REP message from nteroperability Tester Table 5.1-8 : A_REP from nteroperability Tester Table 5.1-9 : TX_RE(nbound) message from U Table 5.1-10 : TX_RE(Outbound) message from nteroperability Tester Table 5.1-11 : M NO3 message Table 5.1-12 : M NO1 message Table 5.1-13 : OM NO3 message Table 5.1-14 : OM NO1 message Table 5.1-15 : VA message from U Values for All all shall be applied to parameters for each Table. 5.1.4.1. Testing the alling U 5.1.4.1.1. All all uccess Testing Procedures for this case shall be identical to those tests for onference Group all as described in ection 5.1.2.1.1. 5.1.4.2. Testing the alled U Testing Procedures shall be identical to those tests for onference Group all as described in ection 5.1.2.1.2. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 14
5.1.5. hort Data all Tests This test shall verify that contents of messages used for hort Data all are correct, that the unit under test correctly responds to these messages, and that the called unit outputs normal received data. This test includes the test methods for the following two modes. (1) Broadcast hort Data all (2) Unit to Unit hort Data all U No.1 nteroperability Tester U No.2 P No.1 P No.2 igure 5.1-2 hort Data all Tests etup igure 5.1-2 shows the configuration diagram for testing. n the event that an U by itself cannot realize the hort Data all functions, testing can be done by connecting peripheral equipment such as a P to the U. The following 12 types of messages shall be applied. Table 5.1-1 : M NO4 / NO2 message Table 5.1-2 : OM NO4 / NO2 (Busy Repeater Message) message Table 5.1-3 : OM NO4 / NO2 (ree Repeater Message) message Table 5.1-4 : OM NO4 / NO2 (ite D Message Message) message Table 5.1-5 : M / OM NO4 (EOT) message Table 5.1-6 : A_REQ message from U Table 5.1-7 : A_ONN_REP message from nteroperability Tester Table 5.1-8 : A_REP message from nteroperability Tester Table 5.1-9 : TX_RE(nbound) message from U Table 5.1-10 : TX_RE(Outbound) message from nteroperability Tester Table 5.1-16 : DA_REQ(Header) message Table 5.1-17 : DA_REP message DA_REQ (User Data) messages are recommended to be constructed with User Data not exceeding 100 bytes. No contents of User Data are specified in this document. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 15
5.1.5.1. Broadcast hort Data all Test n this test, parameters for messages to be used shall apply the values for Group all. 5.1.5.1.1. Testing the alling U 5.1.5.1.1.1. hort Data uccess (1) ink connection will be shown in ection 5.1.1. (2) When U No.1 has started hort Data all, verify that the U transmits a DA_REQ(Header) message shown in Table 5.1-16 that includes NO4 message shown in Table 5.1-1 in H, and DA_REQ(User Data) message. (3) After transmitting (2) abovementioned messages, verify that the U transmits a TX_RE(nbound) message shown in Table 5.1-9 that includes NO4 (EOT) message shown in Table 5.1-5, and shifts its channel frequency to the channel frequency of the Home repeater. 5.1.5.1.2. Testing the alled U (1) U No.2 shifts its frequency channel based on the procedure shown in ection 5.1.1. (2) When a DA_REQ(Header) message shown in Table 5.1-16 that includes any of NO4 message shown in Table 5.1-2 to Table 5.1-4 in H, DA_REQ(User Data) message, and TX_RE(Outbound) message shown in (3) Table 5.1-10 that includes NO4 (EOT) message shown in Table 5.1-5 have been transmitted from an nteroperability Tester, verify that U No.2 receives User Data properly and shifts its channel frequency to the channel frequency of the Home repeater. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 16
Table 5.1-16 DA_REQ(Header) message ingle Trunked ystem Multi Trunked ystem Option 00 10 all Type 100b (ndividual all) 001b (Group all) ource Value of number ource Prefix Prefix of U No.1 Unit D of U No.1 Destination Value of number Unit D of U No.2 (ndividual all) Group D (Group all) Destination Prefix Value of Destination Prefix ipher Type Key D Packet nformation 00b 000000b Except for the following, depends on the format to be used for testing. Delivery lag = 0 (Group all, ndividual all) Unconfirmed Delivery lag = 1 (ndividual all) onfirmed Table 5.1-17 DA_REP message ingle Trunked ystem Multi Trunked ystem Option 00 10 all Type 100b ource ource Prefix Value of number Prefix of U No.2 Unit D of U No.2 Destination ause () Error Block lag Value of number Unit D of U No.1 01 (Receive uccess) / 08 (ull Retry) Depends on the format to be used for testing. Destination Prefix Value of Destination Prefix opyright 2007-2012 com ncorporated and JV KENWOOD orporation 17
5.1.5.2. Unit to Unit hort Data all Test n this test, parameters for messages to be used shall apply the values for ndividual all. The procedure for Unit to Unit hort Data all is different between onfirmed format and Unconfirmed format. To verify the interoperability, a unit under test shall pass the test item for at least either of the onfirmed format or the Unconfirmed format. n the case of the onfirmed format, a unit under test shall pass the test items specified in ection 5.1.5.2.1.1 and ection 5.1.5.2.2.1. n the case of the Unconfirmed format, a unit under test shall pass the test items specified in ection 5.1.5.2.1.2 and ection 5.1.5.2.2.2. 5.1.5.2.1. Testing the alling U 5.1.5.2.1.1. hort Data uccess - (onfirmed) (1) ink connection will be shown in ection 5.1.1. (2) When U No.1 has started hort Data all, verify that the U transmits a DA_REQ(Header) message shown in Table 5.1-16 that includes NO4 message shown in Table 5.1-1 in H, and DA_REQ(User Data) message. (3) When a DA_REP message shown in Table 5.1-17 indicating Receive uccess that include any of NO4 messages shown in Table 5.1-2 to Table 5.1-4 (the instructed Destination is U No.1) in H has been transmitted from an nteroperability Tester, verify that U No.1 transmits TX_RE(nbound) shown in Table 5.1-9 that includes NO4(EOT) message shown in Table 5.1-5, and shifts its channel frequency to the channel frequency of the Home repeater. 5.1.5.2.1.2. hort Data uccess - (Unconfirmed) (1) ink connection will be shown in ection 5.1.1. (2) When U No.1 has started hort Data all, verify that the U transmits a DA_REQ(Header) message shown in Table 5.1-16 that includes NO4 message shown in Table 5.1-1 in H, DA_REQ(User Data) message, and TX_RE(nbound) shown in Table 5.1-9 that includes NO4(EOT) message shown in Table 5.1-5, and shifts its channel frequency to the channel frequency of the Home repeater. 5.1.5.2.1.3. ull Retry Testing procedures for this case shall be common to the onfirmed format and Unconfirmed format, as follow: (1) ink connection will be shown in ection 5.1.1. (2) When U No.1 has started hort Data all, verify that the U transmits a DA_REQ(Header) message shown in Table 5.1-16 that includes NO4 message shown in Table 5.1-1 in H, and DA_REQ(User Data) message. (3) When a DA_REP message shown in Table 5.1-17 indicating re-transmission of all the messages that include any of NO4 messages shown in Table 5.1-2 to Table 5.1-4 (the instructed Destination is U No.1) in H has been transmitted by using an nteroperability Tester, verify that the U No.1 transmits a DA_REQ(Header) message shown in Table 5.1-16 that includes NO4 message shown in Table 5.1-1, and DA_REQ(User Data) message to H. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 18
5.1.5.2.2. Testing the alled U 5.1.5.2.2.1. Receive uccess - (onfirmed) (1) U No.2 shifts its frequency channel based on the procedure shown in ection 5.1.1. (2) When a DA_REQ(Header) message shown in Table 5.1-16 that includes any of NO4 message shown in Table 5.1-2 to Table 5.1-4 in H, and DA_REQ(User Data) message have been transmitted from an nteroperability Tester, verify that U No.2 receives User Data properly, and transmits a DA_REP message shown in Table 5.1-17 indicating Receive uccess that include any of NO4 messages shown in Table 5.1-2 (the instructed Destination is U No.1) to H. (3) When the nteroperability Tester transmits a TX_RE(Outbound) message shown in Table 5.1-9 that includes NO4 (EOT) message shown in Table 5.1-5, verify that the U shifts its channel frequency to the channel frequency of the Home repeater. 5.1.5.2.2.2. Receive uccess - (Unconfirmed) (1) U No.2 shifts its frequency channel based on the procedure shown in ection 5.1.1. (2) When an nteroperability Tester transmits a DA_REQ (Header) message shown in Table 5.1-16 that includes any of NO4 message shown in Table 5.1-2 to Table 5.1-4 in H, DA_REQ(User Data) message, verify that U No.2 receives User Data properly. (3) When an nteroperability Tester transmits a TX_RE(Outbound) message shown in Table 5.1-9 that includes NO4 (EOT) message shown in Table 5.1-5, verify that the U shifts its channel frequency to the channel frequency of the Home repeater. 5.1.5.2.2.3. ull Retry - (onfirmed) (1) U No.2 shifts its frequency channel based on the procedure shown in ection 5.1.1. (2) When an nteroperability Tester has transmitted DA_REQ(Header) message shown in Table 5.1-16 that includes any of NO4 messages shown in Table 5.1-2 to Table 5.1-4 in H, and DA_REQ(User Data) message that includes an invalid Message R from an nteroperability Tester, verify that the U No.2 transmits a DA_REP message shown in Table 5.1-17 indicating re-transmission of all the messages that include NO4 message shown in Table 5.1-2 (the instructed Destination is U No.1) in H. opyright 2007-2012 com ncorporated and JV KENWOOD orporation 19
5.1.6. Data all Tests This test shall verify that contents of messages used for Data all are correct, that the unit under test correctly responds to these messages, and that the called unit outputs normal received data. This test includes the test methods for the following two modes. (1) Broadcast Data all (2) Unit to Unit Data all igure 5.1-2 shows the configuration diagram for testing. n the event that an U by itself cannot realize the Data all functions, testing can be done by connecting peripheral equipment such as a P to the U. The following 12 types of messages shall be applied. Table 5.1-1 : M NO4 / NO2 message Table 5.1-2 : OM NO4 / NO2 (Busy Repeater Message) message Table 5.1-3 : OM NO4 / NO2 (ree Repeater Message) message Table 5.1-4 : OM NO4 / NO2 (ite D Message Message) message Table 5.1-5 : M / OM NO4 (EOT) message Table 5.1-6 : A_REQ message from U Table 5.1-7 : A_ONN_REP message from nteroperability Tester Table 5.1-8 : A_REP message from nteroperability Tester Table 5.1-9 : TX_RE(nbound) message from U Table 5.1-10 : TX_RE(Outbound) message from nteroperability Tester Table 5.1-18 : DA (Header) message Table 5.1-19 : DA_AK message from nteroperability Tester t is recommended that DA (User Data) messages are constructed using User Data having a data length that is divided into multiple packets. No contents of User Data are specified in this document. 5.1.6.1. Broadcast Data all Test n this test, parameters for messages to be used shall apply the values for Group all. 5.1.6.1.1. Testing the alling U 5.1.6.1.1.1. Group all uccess (1) ink connection will be shown in ection 5.1.1. (2) When U No.1 has started Data all, verify that the U transmits DA (Header) message shown in Table 5.1-18 that includes NO4 message shown in Table 5.1-1 in H, and DA(User Data) message. (3) (2)After transmitting abovementioned messages, verify that the U transmits a TX_RE(nbound) message shown in Table 5.1-9 that includes NO4 (EOT) message shown in Table 5.1-5, and shifts its channel frequency to the channel frequency of the Home repeater. 5.1.6.1.2. Testing the alled U (1) U No.2 shifts its frequency channel based on the procedure shown in ection 5.1.1. (2) When a DA_REQ(Header) message shown in Table 5.1-18 that includes any of NO4 message shown in Table 5.1-2 to Table 5.1-4 in H, DA_REQ(User Data) message, and TX_RE(Outbound) shown in (3) Table 5.1-10 that includes NO4 (EOT) message shown in Table 5.1-5, verify that U No.2 receives User Data properly and shifts its channel frequency to the opyright 2007-2012 com ncorporated and JV KENWOOD orporation 20