ARINC 653P3-2006 AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3 - CONFORMITY TEST SPECIFICATION《航空电子设备软件标准接口部分3一致性试验规格》.pdf

《ARINC 653P3-2006 AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3 - CONFORMITY TEST SPECIFICATION《航空电子设备软件标准接口部分3一致性试验规格》.pdf》由会员分享，可在线阅读，更多相关《ARINC 653P3-2006 AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3 - CONFORMITY TEST SPECIFICATION《航空电子设备软件标准接口部分3一致性试验规格》.pdf（386页珍藏版）》请在麦多课文档分享上搜索。

1、 AN DOCUMENT Prepared by AIRLINES ELECTRONIC ENGINEERING COMMITTEE Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401-7435 AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3 CONFORMITY TEST SPECIFICATION ARINC SPECIFICATION 653P3 PUBLISHED: October 16, 2006 DISCLAIM

2、ER THIS DOCUMENT IS BASED ON MATERIAL SUBMITTED BY VARIOUS PARTICIPANTS DURING THE DRAFTING PROCESS. NEITHER AEEC NOR ARINC HAS MADE ANY DETERMINATION WHETHER THESE MATERIALS COULD BE SUBJECT TO VALID CLAIMS OF PATENT, COPYRIGHT OR OTHER PROPRIETARY RIGHTS BY THIRD PARTIES, AND NO REPRESENTATION OR

3、WARRANTY, EXPRESS OR IMPLIED, IS MADE IN THIS REGARD. AEEC USES REASONABLE EFFORTS TO DEVELOP AND MAINTAIN THESE DOCUMENTS. HOWEVER, NO CERTIFICATION OR WARRANTY IS MADE AS TO THE TECHNICAL ACCURACY OR SUFFICIENCY OF THE DOCUMENTS, THE ADEQUACY, MERCHANTABILITY, FITNESS FOR INTENDED PURPOSE OR SAFET

4、Y OF ANY PRODUCTS, COMPONENTS, OR SYSTEMS DESIGNED, TESTED, RATED, INSTALLED OR OPERATED IN ACCORDANCE WITH ANY ASPECT OF THIS DOCUMENT OR THE ABSENCE OF RISK OR HAZARD ASSOCIATED WITH SUCH PRODUCTS, COMPONENTS, OR SYSTEMS. THE USER OF THIS DOCUMENT ACKNOWLEDGES THAT IT SHALL BE SOLELY RESPONSIBLE F

5、OR ANY LOSS, CLAIM OR DAMAGE THAT IT MAY INCUR IN CONNECTION WITH ITS USE OF OR RELIANCE ON THIS DOCUMENT, AND SHALL HOLD ARINC, AEEC, AND ANY PARTY THAT PARTICIPATED IN THE DRAFTING OF THE DOCUMENT HARMLESS AGAINST ANY CLAIM ARISING FROM ITS USE OF THE STANDARD. THE USE IN THIS DOCUMENT OF ANY TERM

6、, SUCH AS SHALL OR MUST, IS NOT INTENDED TO AFFECT THE STATUS OF THIS DOCUMENT AS A VOLUNTARY STANDARD OR IN ANY WAY TO MODIFY THE ABOVE DISCLAIMER. NOTHING HEREIN SHALL BE DEEMED TO REQUIRE ANY PROVIDER OF EQUIPMENT TO INCORPORATE ANY ELEMENT OF THIS STANDARD IN ITS PRODUCT. HOWEVER, VENDORS WHICH

7、REPRESENT THAT THEIR PRODUCTS ARE COMPLIANT WITH THIS STANDARD SHALL BE DEEMED ALSO TO HAVE REPRESENTED THAT THEIR PRODUCTS CONTAIN OR CONFORM TO THE FEATURES THAT ARE DESCRIBED AS MUST OR SHALL IN THE STANDARD. ANY USE OF OR RELIANCE ON THIS DOCUMENT SHALL CONSTITUTE AN ACCEPTANCE THEREOF “AS IS” A

8、ND BE SUBJECT TO THIS DISCLAIMER. 2006 BY AERONAUTICAL RADIO, INC. 2551 RIVA ROAD ANNAPOLIS, MARYLAND 21401-7435 USA Prepared by the Airlines Electronic Engineering Committee Specification 653 Adopted by the Airlines Electronic Engineering Committee October 4, 2005 ARINC SPECIFICATION 653P3 AVIONICS

9、 APPLICATION SOFTWARE STANDARD INTERFACE PART 3 CONFORMITY TEST SPECIFICATION Published: October 16, 2006i FOREWORD Aeronautical Radio, Inc., the AEEC, and ARINC Standards Aeronautical Radio, Inc. (ARINC) was incorporated in 1929 by four fledgling airlines in the United States as a privately-owned c

10、ompany dedicated to serving the communications needs of the air transport industry. Today, the major U.S. airlines remain the Companys principal shareholders. Other shareholders include a number of non-U.S. airlines and other aircraft operators. ARINC sponsors aviation industry committees and partic

11、ipates in related industry activities that benefit aviation at large by providing technical leadership and guidance and frequency management. These activities directly support airline goals: promote safety, efficiency, regularity, and cost-effectiveness in aircraft operations. The Airlines Electroni

12、c Engineering Committee (AEEC) is an international body of airline technical professionals that leads the development of technical standards for airborne electronic equipment-including avionics and in-flight entertainment equipment-used in commercial, military, and business aviation. The AEEC establ

13、ishes consensus-based, voluntary form, fit, function, and interface standards that are published by ARINC and are known as ARINC Standards. The use of ARINC Standards results in substantial benefits to airlines by allowing avionics interchangeability and commonality and reducing avionics cost by pro

14、moting competition. There are three classes of ARINC Standards: a) ARINC Characteristics Define the form, fit, function, and interfaces of avionics and other airline electronic equipment. ARINC Characteristics indicate to prospective manufacturers of airline electronic equipment the considered and c

15、oordinated opinion of the airline technical community concerning the requisites of new equipment including standardized physical and electrical characteristics to foster interchangeability and competition. b) ARINC Specifications Are principally used to define either the physical packaging or mounti

16、ng of avionics equipment, data communication standards, or a high-level computer language. c) ARINC Reports Provide guidelines or general information found by the airlines to be good practices, often related to avionics maintenance and support. The release of an ARINC Standard does not obligate any

17、airline or ARINC to purchase equipment so described, nor does it establish or indicate recognition or the existence of an operational requirement for such equipment, nor does it constitute endorsement of any manufacturers product designed or built to meet the ARINC Standard. In order to facilitate t

18、he continuous product improvement of this ARINC Standard, two items are included in the back of this volume: An Errata Report solicits any corrections to the text or diagrams in this ARINC Standard. An ARINC IA Project Initiation/Modification (APIM) form solicits any recommendations for addition of

19、substantive material to this volume which would be the subject of a new Supplement. ARINC SPECIFICATION 653 TABLE OF CONTENTS 1 INTRODUCTION.1 1.1 PURPOSE OF COMPLIANCE DEMONSTRATION .1 1.2 COMPLIANCE DEMONSTRATION CONCEPT .1 1.2.1 IMPLEMENTATION LEVELS AND SCOPE 1 1.2.2 PROPOSED PROCESS FOR DEMONST

20、RATION OF COMPLIANCE.2 1.3 Relationship to POSIX and the Open Group 5 2 GUIDELINES FOR IMPLEMENTATION OF TEST SPECIFICATION AND PROCEDURES.6 2.1 Test Procedures Determination6 2.2 ORGANIZATION OF THE DOCUMENT 7 3 Conformity Test Requirements9 3.1 ARINC 653 System Capability Requirements.9 3.1.1 Syst

21、em API/OS Compliance .9 3.1.2 Generic API/OS Management Types 10 3.2 Partition Services .10 3.2.1 Partition Management Types 11 3.2.1.1 Partition Management Types Requirements 11 3.2.1.2 Partition Management Types Test Procedures.11 3.2.2 Partition Management Services.12 3.2.2.1 GET_PARTITION_STATUS

22、.12 3.2.2.1.1 GET_PARTITION_STATUS Requirements 12 3.2.2.1.2 GET_PARTITION_STATUS Functional Test Procedures.13 3.2.2.1.3 GET_PARTITION_STATUS Robustness Test Procedures.13 3.2.2.1.4 GET_PARTITION_STATUS Service Macro13 3.2.2.2 SET_PARTITION_MODE 14 3.2.2.2.1 SET_PARTITION_MODE Requirements14 3.2.2.

23、2.2 SET_PARTITION_MODE Functional Test Procedures.17 3.2.2.2.3 SET_PARTITION_MODE Robustness Test Procedures 21 3.2.2.2.4 SET_PARTITION_MODE Service Macro .22 3.3 Process Services .22 3.3.1 Process Management Types.22 3.3.1.1 Process Management Types Requirements.22 3.3.1.2 Process Management Types

24、Test Procedures.24 3.3.2 Process Management Services.25 3.3.2.1 GET_PROCESS_ID.25 3.3.2.1.1 GET_PROCESS_ID Requirements 25 3.3.2.1.2 GET_PROCESS_ID Functional Test Procedures.26 3.3.2.1.3 GET_PROCESS_ID Robustness Test Procedures.26 3.3.2.1.4 GET_PROCESS_ID Service Macro26 3.3.2.2 Get_Process_Status

25、 27 3.3.2.2.1 GET_PROCESS_STATUS Requirements27 3.3.2.2.2 GET_PROCESS_STATUS Functional Test Procedures.28 3.3.2.2.3 GET_PROCESS_STATUS Robustness Test Procedures 28 3.3.2.2.4 GET_PROCESS_STATUS Service Macro .29 3.3.2.3 CREATE_PROCESS.30 3.3.2.3.1 CREATE_PROCESS Requirements.30 3.3.2.3.2 CREATE_PRO

26、CESS Functional Test Procedures .34 3.3.2.3.3 CREATE_PROCESS Robustness Test Procedures .35 3.3.2.3.4 CREATE_PROCESS Service Macro36 3.3.2.4 SET_PRIORITY.37 3.3.2.4.1 SET_PRIORITY Requirements.37 3.3.2.4.2 SET_PRIORITY Functional Test Procedures .39 3.3.2.4.3 SET_PRIORITY Robustness Test Procedures

27、.45 3.3.2.4.4 SET_PRIORITY Service Macro 46 3.3.2.5 SUSPEND_SELF.47 3.3.2.5.1 SUSPEND_SELF Requirements 47 3.3.2.5.2 SUSPEND_SELF Functional Test Procedures .49 ARINC SPECIFICATION 653 TABLE OF CONTENTS 3.3.2.5.3 SUSPEND_SELF Robustness Test Procedures.53 3.3.2.5.4 SUSPEND_SELF Service Macro54 3.3.2

28、.6 SUSPEND .55 3.3.2.6.1 SUSPEND Requirements.55 3.3.2.6.2 SUSPEND Functional Test Procedures56 3.3.2.6.3 SUSPEND Robustness Test Procedures58 3.3.2.6.4 SUSPEND Service Macro 59 3.3.2.7 RESUME .60 3.3.2.7.1 RESUME Requirements.60 3.3.2.7.2 RESUME Functional Test Procedures63 3.3.2.7.3 RESUME Robustn

29、ess Test Procedures .69 3.3.2.7.4 RESUME Service Macro 70 3.3.2.8 STOP_SELF 71 3.3.2.8.1 STOP_SELF Requirements71 3.3.2.8.2 STOP_SELF Functional Test Procedures.72 3.3.2.8.3 STOP_SELF Robustness Test Procedures 76 3.3.2.9 STOP.76 3.3.2.9.1 STOP Requirements 76 3.3.2.9.2 STOP Functional Test Procedur

30、es .78 3.3.2.9.3 STOP Robustness Test Procedures.81 3.3.2.9.4 STOP Service Macro82 3.3.2.10 START.82 3.3.2.10.1 START Requirements.82 3.3.2.10.2 START Functional Test Procedures .85 3.3.2.10.3 START Robustness Test Procedures.88 3.3.2.10.4 START Service Macro89 3.3.2.11 DELAYED_START.90 3.3.2.11.1 D

31、ELAYED_START Requirements 90 3.3.2.11.2 DELAYED_START Functional Test Procedures.93 3.3.2.11.3 DELAYED_START Robustness Test Procedures.103 3.3.2.11.4 DELAYED_START Service Macro103 3.3.2.12 LOCK_PREEMPTION104 3.3.2.12.1 LOCK_PREEMPTION Requirements .104 3.3.2.12.2 LOCK_PREEMPTION Functional Test Pr

32、ocedures 106 3.3.2.12.3 LOCK_PREEMPTION Robustness Test Procedures106 3.3.2.12.4 LOCK_PREEMPTION Service Macro.108 3.3.2.13 UNLOCK_PREEMPTION.109 3.3.2.13.1 UNLOCK_PREEMPTION Requirements 109 3.3.2.13.2 UNLOCK_PREEMPTION Functional Test Procedures.110 3.3.2.13.3 UNLOCK_PREEMPTION Robustness Test Pro

33、cedures.112 3.3.2.13.4 UNLOCK_PREEMPTION Service Macro113 3.3.2.14 GET_MY_ID 113 3.3.2.14.1 GET_MY_ID Requirements 113 3.3.2.14.2 GET_MY_ID Functional Test Procedures.114 3.3.2.14.3 GET_MY_ID Robustness Test Procedures.115 3.3.2.14.4 GET_MY_ID Service Macro115 3.4 TIME MANAGEMENT Services .116 3.4.1

34、 Time Management Types116 3.4.2 Time Management Services116 3.4.2.1 TIMED_WAIT.116 3.4.2.1.1 TIMED_WAIT Requirements 116 3.4.2.1.2 TIMED_WAIT Functional Test Procedures .118 3.4.2.1.3 TIMED_WAIT Robustness Test Procedures.119 3.4.2.1.4 TIMED_WAIT Service Macro121 3.4.2.2 PERIODIC_WAIT.121 3.4.2.2.1

35、PERIODIC_WAIT Requirements 121 3.4.2.2.2 PERIODIC_WAIT Functional Test Procedures .123 3.4.2.2.3 PERIODIC_WAIT Robustness Test Procedures.124 ARINC SPECIFICATION 653 TABLE OF CONTENTS 3.4.2.2.4 PERIODIC_WAIT Service Macro125 3.4.2.3 GET_TIME.126 3.4.2.3.1 GET_TIME Requirements 126 3.4.2.3.2 GET_TIME

36、 Functional Test Procedures .127 3.4.2.3.3 GET_TIME Robustness Test Procedures.127 3.4.2.3.4 GET_TIME Service Macro127 3.4.2.4 REPLENISH 128 3.4.2.4.1 REPLENISH Requirements 128 3.4.2.4.2 REPLENISH Functional Test Procedures.129 3.4.2.4.3 REPLENISH Robustness Test Procedures.130 3.4.2.4.4 REPLENISH

37、Service Macro132 3.5 Memory Management Services Requirements.133 3.6 Interpartition Communication Services Requirements133 3.6.1 Interpartition Communication Types133 3.6.1.1 Interpartition Communication Types Requirements133 3.6.1.2 Interpartition Communication Types Test Procedures135 3.6.2 Interp

38、artition Communication Services136 3.6.2.1 Sampling Port Services136 3.6.2.1.1 CREATE_SAMPLING_PORT.136 3.6.2.1.1.1 CREATE_SAMPLING_PORT Requirements .136 3.6.2.1.1.2 CREATE_SAMPLING_PORT Functional Test Procedures 138 3.6.2.1.1.3 CREATE_SAMPLING_PORT Robustness Test Procedures139 3.6.2.1.1.4 CREATE

39、_SAMPLING_PORT Service Macro.141 3.6.2.1.2 WRITE_SAMPLING_MESSAGE 142 3.6.2.1.2.1 WRITE_SAMPLING_MESSAGE Requirements.142 3.6.2.1.2.2 WRITE_SAMPLING_MESSAGE Functional Test Procedures .143 3.6.2.1.2.3 WRITE_SAMPLING_MESSAGE Robustness Test Procedures .144 3.6.2.1.2.4 WRITE_SAMPLING_MESSAGE Service M

40、acro 144 3.6.2.1.3 READ_SAMPLING_MESSAGE145 3.6.2.1.3.1 READ_SAMPLING_MESSAGE Requirements 145 3.6.2.1.3.2 READ_SAMPLING_MESSAGE Functional Test Procedures.147 3.6.2.1.3.3 READ_SAMPLING_MESSAGE Robustness Test Procedures.149 3.6.2.1.3.4 READ_SAMPLING_MESSAGE Service Macro150 3.6.2.1.4 GET_SAMPLING_P

41、ORT_ID 151 3.6.2.1.4.1 GET_SAMPLING_PORT_ID Requirements.151 3.6.2.1.4.2 GET_SAMPLING_PORT_ID Functional Test Procedures151 3.6.2.1.4.3 GET_SAMPLING_PORT_ID Robustness Test Procedures .152 3.6.2.1.4.4 GET_SAMPLING_PORT_ID Service Macro 152 3.6.2.1.5 GET_SAMPLING_PORT_STATUS153 3.6.2.1.5.1 GET_SAMPLI

42、NG_PORT_STATUS Requirements.153 3.6.2.1.5.2 GET_SAMPLING_PORT_STATUS Functional Test Procedures .154 3.6.2.1.5.3 GET_SAMPLING_PORT_STATUS Robustness Test Procedures154 3.6.2.1.5.4 GET_SAMPLING_PORT_STATUS Service Macro155 3.6.2.2 Queuing Port Services .155 3.6.2.2.1 CREATE_QUEUING_PORT.155 3.6.2.2.1

43、.1 CREATE_QUEUING_PORT Requirements .155 3.6.2.2.1.2 CREATE_QUEUING_PORT Functional Test Procedures158 3.6.2.2.1.3 CREATE_QUEUING_PORT Robustness Test Procedures159 3.6.2.2.1.4 CREATE_QUEUING_PORT Service Macro.161 3.6.2.2.2 SEND_QUEUING_MESSAGE .162 3.6.2.2.2.1 SEND_QUEUING_MESSAGE Requirements162

44、3.6.2.2.2.2 SEND_QUEUING_MESSAGE Functional Test Procedures.169 3.6.2.2.2.3 SEND_QUEUING_MESSAGE Robustness Test Procedures 174 3.6.2.2.2.4 SEND_QUEUING_MESSAGE Service Macro .182 3.6.2.2.3 RECEIVE_QUEUING_MESSAGE183 3.6.2.2.3.1 RECEIVE_QUEUING_MESSAGE Requirements 183 3.6.2.2.3.2 RECEIVE_QUEUING_ME

45、SSAGE Functional Test Procedures .187 ARINC SPECIFICATION 653 TABLE OF CONTENTS 3.6.2.2.3.3 RECEIVE_QUEUING_MESSAGE Robustness Test Procedures.191 3.6.2.2.3.4 RECEIVE_QUEUING_MESSAGE Service Macro195 3.6.2.2.4 GET_QUEUING_PORT_ID 196 3.6.2.2.4.1 GET_QUEUING_PORT_ID Requirements.196 3.6.2.2.4.2 GET_Q

46、UEUING_PORT_ID Functional Test Procedures197 3.6.2.2.4.3 GET_QUEUING_PORT_ID Robustness Test Procedures .198 3.6.2.2.4.4 GET_QUEUING_PORT_ID Service Macro 198 3.6.2.2.5 GET_QUEUING_PORT_STATUS199 3.6.2.2.5.1 GET_QUEUING_PORT_STATUS Requirements 199 3.6.2.2.5.2 GET_QUEUING_PORT_STATUS Functional Test

47、 Procedures .200 3.6.2.2.5.3 GET_QUEUING_PORT_STATUS Robustness Test Procedures.200 3.6.2.2.5.4 GET_QUEUING_PORT_STATUS Service Macro200 3.7 Intrapartition Communication Services Requirements201 3.7.1 Intrapartition Communication Types201 3.7.1.1 Intrapartition Communication Types Requirements201 3.

48、7.1.2 Intrapartition Communication Types Test Procedures204 3.7.2 Intrapartition Communication Services205 3.7.2.1 Buffer Services.205 3.7.2.1.1 CREATE_BUFFER.205 3.7.2.1.1.1 CREATE_BUFFER Requirements .205 3.7.2.1.1.2 CREATE_BUFFER Functional Test Procedures 207 3.7.2.1.1.3 CREATE_BUFFER Robustness

49、 Test Procedures207 3.7.2.1.1.4 CREATE_BUFFER Service Macro.209 3.7.2.1.2 SEND_BUFFER .210 3.7.2.1.2.1 SEND_BUFFER Requirements210 3.7.2.1.2.2 SEND_BUFFER Functional Test Procedures.215 3.7.2.1.2.3 SEND_BUFFER Robustness Test Procedures 222 3.7.2.1.2.4 SEND_BUFFER Service Macro .225 3.7.2.1.3 RECEIVE_BUFFER .227 3.7.2.1.3.1 RECEIVE_BUFFER Requirements227 3.7.2.1.3.2 RECEIVE_BUFFER Functional Test Procedures.231 3.7.2.1.3.3 RECEIVE_BUFFER Robustness Test Procedures.237 3.7.2.1.3.4 RECEIVE_BUFFER Service Macro .240 3.7.2.1.4 GET_BUFFER_ID 241 3.7.2.1.4.1 GET_BUFFER_ID Requirement