IEEE 1499-1998 pdf download IEEE Standard Interface for Hardware Description Models of Electronic Components
3.Introduction to OMl
The OMl defines a protocol for interaction between a model and an application using that model. lt definesa set of programming interfaces and corresponding rules for their use that enable model interoperability andlimit access to internal model information.
3.1 OMI software architecture
An OMl model is a tailorable, functional representation of a device or system that is delivered in object codeformat, A model may encapsulate a simul atable specification, timing information, physical characteri sticsand other data related to the device or system. A customized version of a model that has been incorporatedinto a hardware or system desicn is called a model instance. A single model may have any number of modelinstances associated with it.
A model may be used by a variety of applications An application is a software tool that accesses one or moremodels A simulator is a special kind of application that is capable of simulating the behavior of a hardwareor system design. Throughout this standard, the use of the term “simulator” in a particular context implies thata simulation capability is required or assumed in that situation.
Privileged internal information that is associ ated with a model or an application is called intellectual property.The OMl model delivery mechanism protects intellectual property by enabling the delivery of models inobject code format and by provicing an interaction mechanism that allows a model and an application tocontrol communication through calls to a small set of interface functions The only information availableabout a model is the information at the port boundary and informati on relating to selected internal objects thatthe model supplier chooses to make visible to the external environment.
An OMI model is integrated into an application through a model manager , which coordinates the interaction between the application and the models under its control. Every model (and derived model instance) has a model manager associated with it. An application may interact with any number of model managers, as depicted in Figure 1.
A model manager performs a number of services. It provides general model packaging information (e.g., supplier, revision). It also handles information relating to the behavior of a model in a particular context, for example, by providing mechanisms for creating instances, setting parameter values and binding ports during instantiation, relaying data values, scheduling port updates, and exporting internal objects for external viewing.
All interaction between a model manager and its models is private. In addition to the essential OMI functionality described above, a model manager may supply its models with internal services, such as error handling or internal scheduling.
IEEE 1499-1998 pdf download
PS:Thank you for your support!
