IEEE 1516 1-2010 en Modeling and Simulation (M&S) High Level Architecture (HLA) Federate Interface Specification (IEEE Computer Society)《建模和模拟(M&S)高层次体系结构(HLA) .pdf

1、g44g40g40g40g3g54g87g71g3g20g24g20g25g17g20g140g16g21g19g20g19g11g53g72g89g76g86g76g82g81g3g82g73g44g40g40g40g3g54g87g71g3g20g24g20g25g17g20g16g21g19g19g19g12g44g40g40g40g3g54g87g68g81g71g68g85g71g3g73g82g85g3g48g82g71g72g79g76g81g74g3g68g81g71g3g54g76g80g88g79g68g87g76g82g81g3g11g48g9g54g12g3g43g76

2、g74g75g3g47g72g89g72g79g3g36g85g70g75g76g87g72g70g87g88g85g72g3g11g43g47g36g12g178g41g72g71g72g85g68g87g72g3g44g81g87g72g85g73g68g70g72g3g54g83g72g70g76g191g70g68g87g76g82g81g44g40g40g40g3g38g82g80g83g88g87g72g85g3g54g82g70g76g72g87g92g54g83g82g81g86g82g85g72g71g3g69g92g3g87g75g72g54g76g80g88g79g68g

3、87g76g82g81g3g44g81g87g72g85g82g83g72g85g68g69g76g79g76g87g92g3g54g87g68g81g71g68g85g71g86g3g50g85g74g68g81g76g93g68g87g76g82g81g18g54g87g68g81g71g68g85g71g86g3g36g70g87g76g89g76g87g76g72g86g3g38g82g80g80g76g87g87g72g72g3g11g54g44g54g50g18g54g36g38g12g44g40g40g40g22g3g51g68g85g78g3g36g89g72g81g88g72

4、g3g49g72g90g3g60g82g85g78g15g3g49g60g3g20g19g19g20g25g16g24g28g28g26g15g3g56g54g36g3g3g20g27g3g36g88g74g88g86g87g3g21g19g20g19g20g24g20g25g17g20g55g48IEEE Std 1516.1-2010(Revision ofIEEE Std 1516.1-2000)IEEE Standard for Modeling and Simulation (M +1 978 750 8400. Permission to photocopy portions of

5、any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center.iv Copyright 2010 IEEE. All rights reserved.IntroductionThis document has been developed to record an international standard for the High Level Architecture(HLA). It serves as one of thr

6、ee related standards for the HLA. It defines the services and interfaces to beused by federates when participating in a federation execution.This new version of the IEEE 1516 HLA was produced in 2004 through 2007 by the HLA Evolved ProductDevelopment Group of the Simulation Interoperability Standard

7、s Organization (SISO). It incorporates anumber of updates based on practical application of earlier versions of the standard. The purpose of the newversion is to better support development, deployment, and net-centricity of distributed simulations.Major new additions include support for Web Services

8、 communication, modular information modelsfederation object models (FOMs) and simulation object models (SOMs), improved extensible markuplanguage (XML) features (XML Schemata as well as extensibility), improved fault tolerance support,support for update rate reduction, and dynamic link compatibility

9、 between different implementations.Notice to usersLaws and regulationsUsers of these documents should consult all applicable laws and regulations. Compliance with theprovisions of this standard does not imply compliance to any applicable regulatory requirements.Implementers of the standard are respo

10、nsible for observing or referring to the applicable regulatoryrequirements. IEEE does not, by the publication of its standards, intend to urge action that is not incompliance with applicable laws, and these documents may not be construed as doing so. CopyrightsThis document is copyrighted by the IEE

11、E. It is made available for a wide variety of both public and privateuses. These include both use, by reference, in laws and regulations, and use in private self-regulation,standardization, and the promotion of engineering practices and methods. By making this documentavailable for use and adoption

12、by public authorities and private users, the IEEE does not waive any rights incopyright to this document.Updating of IEEE documentsUsers of IEEE standards should be aware that these documents may be superseded at any time by theissuance of new editions or may be amended from time to time through the

13、 issuance of amendments,corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of thedocument together with any amendments, corrigenda, or errata then in effect. In order to determine whethera given document is the current edition and whether it has bee

14、n amended through the issuance ofamendments, corrigenda, or errata, visit the IEEE Standards Association web site at http:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously.For more information about the IEEE Standards Association or the IEEE standards devel

15、opment process,visit the IEEE-SA web site at http:/standards.ieee.org.This introduction is not part of IEEE Std 1516.1-2010, IEEE Standard for Modeling and Simulation (M therefore, it is not shown in the servicedescriptions. Also, for the RTI-initiated services, some implicit preconditions are not s

16、tated explicitlybecause the RTI is assumed to be well behaved. For many RTI-initiated services, the “Federate is joined”precondition presumes the “Federate is connected” precondition.As mentioned earlier, all RTI-initiated services are denoted with a (printers dagger) after the servicename.1.4.4 Org

17、anization of this documentThe seven HLA service groups are specified in Clause 4 through Clause 10. Each service is described usingseveral components: Name and description: service name and narrative describing the functionality of the service. Supplied arguments: arguments supplied to the service R

18、eturned arguments: arguments returned by the service. Preconditions: conditions that shall exist for the service to execute correctly. Postconditions: conditions that shall exist once the service has executed correctly. Exceptions: notifications of any irregularity that may occur during service invo

19、cation. Whereverpossible (excepting situations like RTI internal error), exceptions are side-effect free. Exceptions arelisted in order of increasing precedence. That is, if the conditions for more than one exception aremet simultaneous, the RTI shall throw whichever of those exceptions comes later

20、in the exceptionlist. Reference state charts: reference to state chart(s) that are germane to the service.After the clauses describing each of the service groups are a clause describing the MOM and then a clausethat ties the service narratives with the APIs.IEEE Std 1516.1-2010 IEEE STANDARD FOR MOD

21、ELING AND SIMULATION (M instanceattribute.attribute ownership: The property of an instance attribute that gives a joined federate the capability tosupply values for that instance attribute to its federation execution. See also: instance attribute.available attributes: The set of declared attributes

22、of an object class in union with the set of inheritedattributes of that object class. available dimensions: a) Pertaining to an attribute: the dimensions associated with the class attribute in the federation objectmodel (FOM). The available dimensions of an instance attribute are the available dimen

23、sions of thecorresponding class attribute. b) Pertaining to an interaction class: the dimensions associated with that interaction class in the FOM.The available dimensions of a sent interaction are the available dimensions of the interaction classspecified in the Send Interaction With Regions servic

24、e invocation. NOTESee 9.1.4available parameters: The set of declared parameters of an interaction class in union with the set ofinherited parameters of that interaction class. base object model (BOM): A piece-part of a conceptual model, simulation object model (SOM), orfederation object model (FOM)

25、that can be used as a building block in the development and/or extension ofa simulation or federation.best effort: A transportation type that does not provide any guarantee regarding delivery (messages may beout of order, duplicate, or dropped).3The IEEE Standards Dictionary: Glossary of Terms each

26、instance attribute may have at most one value associated with it.corresponding class attribute of an instance attribute: The class attribute that, from the perspective of agiven joined federate, is the class attribute of the joined federates known class for the object instancecontaining the instance

27、 attribute that has the same attribute designator as the instance attribute.corresponding instance attributes of a class attribute: The instance attributes that, from the perspectiveof a given joined federate, are a) Unowned instance attributes of object instances that have a known class at the join

28、ed federate equalto the object class of the class attribute and that have the same attribute designator as the classattribute, orb) Instance attributes owned by the joined federate that belong to object instances that have a knownclass at the owning federate equal to the object class of the class at

29、tribute and that have the sameattribute designator as the class attribute.current federation object model (FOM): The union of the FOM modules and one Management ObjectModel (MOM) and Initialization Module (MIM) that have been specified in the creation of the federationexecution or by any federate th

30、at has joined the federation execution. The sum operation is carried outaccording to the rules as prescribed in IEEE Std 1516.2-2010. When all FOM modules have been provided,HIGH LEVEL ARCHITECTURE (HLA)FEDERATE INTERFACE SPECIFICATION IEEE Std 1516.1-2010Copyright 2010 IEEE. All rights reserved. 11

31、the current FOM will be equal to the FOM; and before this step has happened, the current FOM will be atrue subset of the FOM.current federation object model (FOM) Document Data (FDD): The data and information used toconfigure the federation execution that is the union of the FOM modules and one Mana

32、gement ObjectModel (MOM) and Initialization Module (MIM) that have been specified in the creation of the federationexecution or by any federate that has joined the federation execution. The sum operation is carried outaccording to the rules as prescribed in IEEE Std 1516.2-2010. When all FOM modules

33、 have been provided,the current FDD will be equal to the FDD; and before this step has happened, the current FDD will be a truesubset of the FDD.datatype: A representation convention for a data element establishing its format, resolution, cardinality, andordinality. declared attributes: The set of c

34、lass attributes of a particular object class that are listed in the federationobject model (FOM) as being associated with that object class in the object class hierarchy tree. declared parameters: The set of parameters of a particular interaction class that are listed in the federationobject model (

35、FOM) as being associated with that interaction class in the interaction class hierarchy tree. default range: A range lower bound and a range upper bound, defined in the federation object model(FOM) Document Data (FDD) and specified in terms of 0, the dimensions upper bound), for a dimension.default

36、region: A multidimensional region provided by the runtime infrastructure (RTI) that is composed ofone range for each dimension found in the federation object model (FOM) Document Data (FDD). Thebounds of each of these ranges are 0, the ranges dimensions upper bound). There is no way for a federateto

37、 refer to the default region.NOTESee 9.1.delete: To invoke the Delete Object Instance service to eliminate a particular object instance. See also:remove. NOTESee 6.14.designator: A generic view of arguments referenced in service descriptions. This view improves clarity insituations when arguments (m

38、ostly identifiers) to services have different views (implementations) due to aparticular programming language or application programmers interface (API).dimension: A named interval. The interval is defined by an ordered pair of values, the first being thedimension lower bound and the second being th

39、e dimension upper bound. A runtime infrastructure (RTI)provides a predefined interval, whose lower and upper bounds are fixed as 0, the dimensions upper bound)as specified in the federation object model (FOM) Document Data (FDD). This interval provides a singlebasis for communication of all dimensio

40、n-related data with an RTI. All normalized intervals communicatedto the RTI will be subsets of this interval.NOTESee 9.1.discover: To receive an invocation of the Discover Object Instance 5service for a particular objectinstance.NOTESee 6.9.5All RTI-initiated services are denoted with a (printers da

41、gger) after the service name.IEEE Std 1516.1-2010 IEEE STANDARD FOR MODELING AND SIMULATION (M joined federate.federate application: An application that supports the High Level Architecture (HLA) interface to aruntime infrastructure (RTI) and that is capable of joining a federation execution. A fede

42、rate application mayjoin the same federation execution multiple times or may join multiple federation executions. However, eachtime a federate application joins a federation execution, it is creating a new joined federate. See also: joinedfederate.federation: A named set of federate applications and

43、 a common federation object model (FOM) that areused as a whole to achieve some specific objective.federation execution: The actual operation, over time, of a set of joined federates that are interconnected bya runtime infrastructure (RTI).federation objectives: The statement of the problem that is

44、to be addressed by the establishment andexecution of a federation.federation object model (FOM): A specification defining the information exchanged at runtime to achievea given set of federation objectives. This information includes object classes, object class attributes,interaction classes, intera

45、ction parameters, and other relevant information. The FOM is specified to theruntime infrastructure (RTI) using one or more FOM modules. The RTI assembles a FOM using these FOMmodules and one Management Object Model (MOM) and Initialization Module (MIM), which is providedautomatically by the RTI or,

46、 optionally, provided to the RTI when the federation execution is created. federation object model (FOM) Document Data (FDD): The data and information in a FOM that are usedby the Create Federation Execution service and successive Join Federation Execution service invocations toconfigure the federat

47、ion execution. federation object model (FOM) module: A partial FOM (containing some or all object model template(OMT) tables) that specifies a modular component of a FOM. A FOM module may contain classes notinherent to it but upon which the FOM module depends, i.e., superclasses to the modular compo

48、nents. Thesesuperclasses will be included in the FOM module as either complete or scaffolding definitions.federation requirements: A statement that identifies a federation characteristic, constraint, process, orproduct that is unambiguous and testable and that is necessary for a federation to be acc

49、eptable for itsintended use.federation scenario: A set of initial conditions and timeline of significant events used within a federationexecution to achieve federation objectives.handle: An identifier originated/created by the runtime infrastructure (RTI) that is unique to a federationexecution.HIGH LEVEL ARCHITECTURE (HLA)FEDERATE INTERFACE SPECIFICATION IEEE Std 1516.1-2010Copyright 2010 IEEE. All rights reserved. 13High Level Architecture (HLA) time axis: A totally ordered sequence of values in which each valuetypically represents an HLA instant of t