1、g44g40g40g40g3g54g87g71g3g20g24g20g25g17g21g140g16g21g19g20g19g11g53g72g89g76g86g76g82g81g3g82g73g44g40g40g40g3g54g87g71g3g20g24g20g25g17g21g16g21g19g19g19g12g44g40g40g40g3g54g87g68g81g71g68g85g71g3g73g82g85g3g48g82g71g72g79g76g81g74g3g68g81g71g3g54g76g80g88g79g68g87g76g82g81g3g11g48g9g54g12g3g43g76
2、g74g75g3g47g72g89g72g79g3g36g85g70g75g76g87g72g70g87g88g85g72g3g11g43g47g36g12g178g50g69g77g72g70g87g3g48g82g71g72g79g3g55g72g80g83g79g68g87g72g3g11g50g48g55g12g3g54g83g72g70g76g191g70g68g87g76g82g81g44g40g40g40g3g38g82g80g83g88g87g72g85g3g54g82g70g76g72g87g92g54g83g82g81g86g82g85g72g71g3g69g92g3g87
3、g75g72g54g76g80g88g79g68g87g76g82g81g3g44g81g87g72g85g82g83g72g85g68g69g76g79g76g87g92g3g54g87g68g81g71g68g85g71g86g3g50g85g74g68g81g76g93g68g87g76g82g81g18g54g87g68g81g71g68g85g71g86g3g36g70g87g76g89g76g87g76g72g86g3g38g82g80g80g76g87g87g72g72g3g11g54g44g54g50g18g54g36g38g12g44g40g40g40g22g3g51g68g
4、85g78g3g36g89g72g81g88g72g3g49g72g90g3g60g82g85g78g15g3g49g60g3g20g19g19g20g25g16g24g28g28g26g15g3g56g54g36g3g3g20g27g3g36g88g74g88g86g87g3g21g19g20g19g20g24g20g25g17g21g55g48IEEE Std 1516.2-2010(Revision ofIEEE Std 1516.2-2000)IEEE Standard for Modeling and Simulation (M +1 978 750 8400. Permission
5、 to photocopy portions of any individual standard for educationalclassroom 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 HLA. It serves as one of thr
6、eerelated standards for the HLA. It defines the format and syntax for recording information in HLA objectmodels.This new version of the IEEE 1516 High Level Architecture has been produced during 20042007 by the“HLA Evolved Product Development Group” of the Simulation Interoperability Standards Organ
7、ization(SISO). It incorporates a number of updates based on practical application of earlier versions of the standard.The purpose of the new version is to better support development, deployment, and net-centricity ofdistributed simulations. Major new additions include support for Web Services commun
8、ication, modularinformation models (FOMs and SOMs), improved XML features (XML Scemas as well as extensibility),improved fault tolerance support, support for update rate reduction and dynamic link compatibility betweendifferent implementations.Notice to usersLaws and regulationsUsers of these docume
9、nts 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 responsible for observing or referring to the applicable regulatoryrequirements. IEEE does not,
10、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 IEEE. It is made available for a wide variety of both public and privateuses. These include bo
11、th 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 by public authorities and private users, the IEEE does not waive any rights incopyright to
12、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 issuance of amendments,corrigenda, or errata. An official IEEE document at any point in ti
13、me 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 been amended through the issuance ofamendments, corrigenda, or errata, visit the IEEE Standard
14、s Association website 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 development process,visit the IEEE-SA website at http:/standards.ieee.org.This introduction is no
15、t part of IEEE Std 1516.2-2010, IEEE Standard for Modeling and Simulation (M each branch connects one node class to a directly subsidiary node; there is a uniquenode called the root root class which is not subsidiary to any other node; and every node class besides theroot is directly subsidiary to e
16、xactly one other node class” (The IEEE Standards Dictionary: Glossary ofTerms instanceattribute.2ANSI publications are available from the Sales Department, American National Standards Institute, 11 West 42nd Street, 13th Floor,New York, NY 10036, USA (http:/www.ansi.org/).3IEEE publications are avai
17、lable from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854, USA(http:/standards.ieee.org/).4The IEEE standards or products referred to in this clause are trademarks of the Institute of Electrical and Electronics Engineers, Inc.5This document is available at
18、 http:/www.w3.org/.6The IEEE Standards Dictionary: Glossary of Terms each 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 j
19、oined federates known class for the object instancecontaining the instance 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 i
20、nstance attributes of object instances that have a known class at the joined 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 k
21、nownclass at the owning federate equal to the object class of the class attribute 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
22、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 have been provided,the current FOM will be equal to the FOM; and before
23、 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 Management ObjectModel (MOM) and Initialization Module (
24、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 have been provided,the current FDD will be equal to
25、 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 class attributes of a particular object class that ar
26、e 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 (FOM) as being associated with that interaction class
27、 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 region: A multidimensional region provided by the ru
28、ntime 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 refer to the default region.NOTESee 9.1 in IEEE Std
29、 1516.1-2010.HIGH-LEVEL ARCHITECTURE (HLA) OBJECT MODEL TEMPLATE (OMT) SPECIFICATION IEEE Std 1516.2-2010Copyright 2010 IEEE. All rights reserved. 7delete: To invoke the Delete Object Instance service to eliminate a particular object instance. See also:remove. NOTESee 6.10 in IEEE Std 1516.1-2010.de
30、signator: A generic view of arguments referenced in service descriptions. This view improves clarity insituations when arguments (mostly identifiers) to services have different views (implementations) due to aparticular programming language or application programmers interface (API).dimension: A nam
31、ed interval. The interval is defined by an ordered pair of values, the first being thedimension lower bound and the second being the 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 specifi
32、ed in the federation object model (FOM) Document Data (FDD). This interval provides a singlebasis for communication of all dimension-related data with an RTI. All normalized intervals communicatedto the RTI will be subsets of this interval.NOTESee 9.1 of IEEE Std 1516.1-2010.discover: To receive an
33、invocation of the Discover Object Instance 7service for a particular objectinstance.NOTESee 6.5 of IEEE Std 1516.1-2010.discovered class: The class that was an object instances candidate discovery class at a joined federate whenthat object instance was discovered by that joined federate. See also: c
34、andidate discovery class.NOTESee 5.1.2 in IEEE Std 1516.1-2010.exception: Notification of any irregularity that may occur during a service invocation.fault: An event that prevents the entire federation from executing in a High Level Architecture (HLA)compliant manner.federate: An application that ma
35、y be or is currently coupled with other software applications under afederation object model (FOM) Document Data (FDD) and a runtime infrastructure (RTI). See also:federate application; joined federate.federate application: An application that supports the High Level Architecture (HLA) interface to
36、aruntime infrastructure (RTI) and that is capable of joining a federation execution. A federate 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 joi
37、ned federate. See also: joinedfederate.federation: A named set of federate applications and 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 by
38、a runtime infrastructure (RTI).federation objectives: The statement of the problem that is to be addressed by the establishment andexecution of a federation.7All RTI-initiated services are denoted with a (printers dagger) after the service name.IEEE Std 1516.2-2010 IEEE STANDARD FOR MODELING AND SIM
39、ULATION (M discover; delete; local delete; remove.last known good logical timestamp: The last timestamp to which a lost joined federate was successfullygranted, as seen from the remaining High Level Architecture (HLA) compliant federation.local delete: To invoke the Local Delete Object Instance serv
40、ice to inform the runtime infrastructure (RTI)that it is to treat the specified object instance as if the RTI had never notified the joined federate to discoverthe object instance (however, the object instance is not to be eliminated and may be rediscovered). See also:delete.NOTESee 6.12 of IEEE Std
41、 1516.1-2010.logical time: A federates current point on the High Level Architecture (HLA) time axis. Federates makinguse of the time management services follow restrictions on what timestamps can be sent in timestamp order(TSO) messages (relative to their logical time) to ensure that federates recei
42、ving those messages receivethem in TSO.lookahead: A nonnegative value that establishes a lower value on the timestamps that can be sent intimestamp order (TSO) messages by time-regulating joined federates. Once established, a joined federateslookahead value may be changed only by using the Modify Lo
43、okahead service. Each time-regulating joinedfederate must provide a lookahead value when becoming time-regulating.lost joined federate: A previously joined federate that has been disconnected from the runtimeinfrastructure (RTI) as a result of a fault so that the joined federate can no longer contin
44、ue in the federationexecution in a High Level Architecture (HLA) compliant manner.Management Object Model (MOM): A group of predefined High Level Architecture (HLA) constructs(object and interaction classes) that provide the following:a) Access to federation execution operating informationb) Insight
45、 into the operations of joined federates and the runtime infrastructure (RTI)c) Control of the functioning of the RTI, the federation execution, and the individual joined federatesIEEE Std 1516.2-2010 IEEE STANDARD FOR MODELING AND SIMULATION (M subscribed attributes of an object class with regions.
46、b) Pertaining to an interaction class: being a subscribed interaction class or a subscribed interactionclass with regions, for some region. See also: subscribed interaction class; subscribed interactionclass with regions.subscribed attributes of an object class: The class attributes that have been a
47、rguments to Subscribe ObjectClass Attributes service invocations by a given joined federate for a given object class that have notsubsequently been unsubscribed, either individually or by unsubscribing the whole object class.NOTESee 5.1.2 and 5.6 of IEEE Std 1516.1-2010.subscribed attributes of an o
48、bject class with regions: The class attributes that have been arguments toSubscribe Object Class Attributes With Regions service invocations by a given joined federate for a givenobject class and a given region, assuming the joined federate did not subsequently invoke the UnsubscribeObject Class Att
49、ributes With Regions service for that object class and region.NOTESee 9.8 of IEEE Std 1516.1-2010.subscribed interaction class: An interaction class that, from the perspective of a given joined federate, wasan argument to a Subscribe Interaction Class or Subscribe Interaction Class With Regions serviceinvocation that was not subsequently followed by an Unsubscribe Interaction Class or UnsubscribeInteraction Class With Regions service invocation for that interaction class.NOTESee 5.1.3 and 5.8 of IEEE Std 1516.1-2010.subscribed interaction class wit
