KR100993309B1 - System for Modeling RFID Business Events - Google Patents

Abstract

The present invention relates to an RFID business event modeling system having a modeling function that allows a developer to easily define an RFID business event required for developing an RFID application application according to the EPC network standard. An RFID business event modeling block expressing a flow of an RFID business event; a model information verification block verifying a possibility of generating a standard specification based on information modeled by the user in the RFID business event modeling block; It includes a; Automatic specification block for generating a specification based on the information and the conversion file.

RFID, EPC Network, RFID Business Events, Statement Generation, Statement Loading

Description

RFIDD Business Event Modeling System {System for Modeling RFID Business Events}

The present invention relates to an RFID business event modeling tool, and more particularly, to an RFID business event modeling system having a modeling function that enables a developer to easily define an RFID business event required for developing an RFID application application according to an EPC network standard. It is about.

RFID (Radio Frequency IDentification) technology is a technology that can recognize information about an object by using a tag (tag) that responds to a radio signal. Such RFID technology can recognize and penetrate obstacles without directly contacting an object. In addition, it is possible to recognize information about several things at once and can recognize a lot of information stored in memory, so it is necessary to establish RFID application in various business fields such as logistics management, distribution management, and to build several application systems that support it. I am doing it.

EPCglobal, a non-profit organization currently responsible for the open standardization of RFID-related technologies, offers an international standard called the Electronic Product Code (EPC) Network.

EPC Network uses EPC tags, RFID readers, RFID middleware, EPC Information Service (EPCIS), and EPCIS DS It presents several components such as EPCIS Discovery Service (ONS) and Object Naming Service (ONS).

In other words, application systems based on RFID technology should obtain the desired information through the use of the above-mentioned EPC Network components and process it into business information.

RFID business event is an XML-formatted information that processes RFID events and information acquired from various components in the EPC network to meet the desired business rules in order to build an application system required in a rapidly changing business environment by introducing RFID technology. Indicates.

The Business Event Specification (BESpec) is an XML-based specification that supports the EPCglobal architecture, supports the development and management of RFID systems, and represents the data acquisition and processing processes in the RFID business event framework shown in FIG. Say.

As shown in FIG. 2, the BESpec can be largely composed of three parts. There are a variable declaration part, an activity part defining various kinds of processes, and a reference specification referred to for processing in the activity.

The variable declaration is used to store processing values in the middle of the activity's processing. Variables let you use the results of one activity in another. In the activity part, activities of various roles that can be combined to create an RFID business event are defined, and each activity can have different attribute values to be described internally. Reference specifications include ProviderSpec which handles interaction with RFID middleware, EPCIS QuerySpec that handles interaction with EPCIS, and EPCIS Capture Specification.

The ProviderSpec is a specification that defines interactions with event providers that provide real-time events. EPCglobal defines an Application Level Event (ALE) interface, which is an interface for RFID middleware, in ALE Specification 1.1.

The EPCIS CaptureSpec is a specification defined to store RFID history information in the EPCIS.

The EPCIS CaptureSpec (CapureSpec) references EPCIS events in the CaptureService of EPCIS Specification 1.0.

An EPCIS event refers to an object event, an aggregation event, a quantity event, and a transaction event. Each event has various properties.

The EPCIS QuerySpec is a specification for querying historical or unique information related to EPC stored in the EPCIS repository. To query information related to EPC using EPCIS, the EPCIS Query Control of EPCIS Specification 1.0 The EPCIS Query Control interface must be observed.

However, it is difficult for the developer to express the RFID business event by directly defining the conformity of the EPC network and the business expression in XML format.

Therefore, there is a need for a support tool that can be easily generated by a developer while complying with the standard of the RFID business event specification and the EPC network standard specification.

An object of the present invention is to provide a tool for modeling an RFID business event to support the development of radio frequency identification (RFID) RFID-based software.

An object of the present invention is to provide an RFID business event modeling system having a modeling function that allows a developer to easily define an RFID business event required for developing an RFID application.

The present invention provides an RFID business event modeling function and expresses the flow of RFID business events through defined model information, and enables the automatic generation of the RFID business event specification and the EPC Network standard specification and the loading function of the standard specification. Its purpose is to provide an event modeling system.

The present invention reduces the time and effort of application development by presenting an RFID business event modeling tool that can help users create various standard specifications needed to develop application applications, and reduces the time and effort of application development. The purpose of the present invention is to provide an RFID business event modeling system to increase reusability.

RFID business event modeling system according to the present invention for achieving the above object is an RFID business event modeling block for representing the interface of the RFID business event in the form of a GUI and the flow of the RFID business event; in the RFID business event modeling block Model information verification block for verifying the possibility of generating a standard specification based on the information modeled by the user; Specification automatic generation block for generating a specification based on the information and the transformation file modeled by the user; characterized in that it comprises a.

RFID business event modeling system according to the present invention for achieving another object is an RFID business event modeling block for representing the interface of the RFID business event in the form of a GUI and the flow of the RFID business event; the user in the RFID business event modeling block Model information verification block for verifying the possibility of generating a standard specification based on the modeled information; Specification automatic generation block for generating a specification based on the information and the transformation file modeled by the user; The generated specification and the previously generated specification A specification element load block for verifying whether the expression can be expressed as a modeling element; a model element transformation block for converting the specification information analyzed in the specification load block into a model element; necessary for the corresponding model element based on information obtained from the specification load block property And a model attribute information adding block for adding information.

Here, the RFID business event modeling block may be stored in a BESpec (Business Event Specification), a specification defined for storing RFID history information in an EPC Information Service (EPCIS) referenced by the BESpec, and stored in an EPCIS repository. GUI form of interface of RFID business event including specification for querying historical or unique information related to EPC, and specification for defining interaction with event provider that provides real-time event. It is characterized by the expression.

The BESpec is an XML-based specification that supports the EPCglobal architecture, supports the development and management of RFID systems, and expresses data acquisition and processing in the RFID business event framework.

The model information verification block may verify that specifications generated based on an RFID business event model modeled by a user conform to BESpec and EPCNetwork standards and express a verification result.

And the specification automatic generation block, based on the modeled information and the conversion file, the provider specification (ProviderSpec), EPCIS capture specification (Equipment Capture specification), EPCIS query specification (QuerySpec) in accordance with the standards proposed by BESpec and EPC Network Automatically generate and support the preview and save the generated specifications.

In the RFID business event modeling block, a lower model element definition and attribute information of each model element required for each model element are used as the upper model where each model element can be defined. Parent items, child models that can be defined inside each model element, and if not defined, child items that mean that there are no model elements inside, and the actual visual representation of the model It is characterized by defining the stereotype and notation items meaning notation.

The RFID business event model element list for modeling the RFID business event includes an object part representing an object that can be represented by a model element, an attribute part indicating an attribute of a model element of each model element, and The type part representing how the property can be selected by the user during the actual modeling process, the participant part in which the property information of the model element or the model element is expressed, and the model property information of the business event specification (BESpec) or the parent model. The business event specification (BESpec) part and the specification part indicating whether it is used in the specification defined in the object, the default part that indicates the basic value of the attribute information, and the specification automatically. Attribute information that should be automatically verified in the model information verification block It characterized in that it comprises a date representing Barre (Validate) part.

The meta-model diagram of the RFID business event model, which is prepared through the RFID business event model element list, expresses information about a variables model and ALE that can express definitions of variables used in an RFID business event. BESpec model, which consists of an ExternalThing model that is embodied in a Provider model, and an Initial model, Final model, and InternalThing model that represent the beginning and end of the flow of events. Characterized in that it comprises a.

In addition, the attribute of the convert element of the conversion file in the specification automatic generation block refers to a name attribute indicating a name of the XML element to be converted, and information of the XMI file of the generated RFID business event model. And a source element attribute indicating a name of an element to be referred to and a source type attribute indicating a type of the referenced element.

In addition, the convert element has a subordinate information of itself, a convert attribute, and a convert text, and a convert attribute may specify an attribute value of an XML element to be converted. ConvertText) is characterized by specifying the text value of the XML element to convert.

The user interface supported by the RFID business event modeling block includes a modeling canvas screen that provides a visual environment that can be modeled using RFID business event model elements, and contains model information currently modeled by the user. File view screen showing the files and diagram files present, Properties Editor screen for setting the properties of each model, and selection of model elements available to the user on the Modeling Canvas. It is characterized by including a provided Palette Viewer (Palette Viewer) screen.

In addition, the user can select the required model elements in the Palette Viewer and drag and drop the model elements onto the modeling canvas.The model generated by the RFID business event modeling function is an XMI type. Characterized in that the file is generated.

In addition, the user interface supported by the specification automatic generation block, the Business Event Model Information (Business Event Model Information) screen for expressing the specified RFID business event model information in a tree form, for the corresponding element when selecting a specific tree element And a property view screen for displaying property values of the selected element.

The RFID business event modeling system according to the present invention has the following effects.

First, since the user uses the business event modeling tool without directly writing the business event specification and the specifications presented by the EPC network, it is possible to easily understand the information expressed in the RFID business event and to accurately write the specifications.

Second, the model created using the business event modeling tool according to the present invention expresses the flow of RFID business events, so that not only the modeling user but also other users can understand.

Third, the auto-generated specifications have an agile response to the auto-generated specifications through the conversion file that defines the conversion rules.

Fourth, the specification load function enables reuse of not only newly created specifications but also previously written specifications and user-written specifications.

Therefore, development cost and time can be reduced when developing various RFID application applications.

Fifth, a verification block for verifying whether information for generating a specification is sufficient is included, so that accurate generation of a required specification is possible.

Hereinafter, a preferred embodiment of the RFID business event modeling system according to the present invention will be described in detail.

Features and advantages of the RFID business event modeling system according to the present invention will become apparent from the following detailed description of each embodiment.

3 is a block diagram of an RFID business event modeling system according to the present invention.

4A and 4B are flowcharts illustrating an RFID business event modeling operation according to an embodiment of the present invention.

The present invention models various RFID business events and automatically generates various specifications required for developing RFID application applications based on the modeled information, and implements a load function of various specifications.

RFID business event modeling system according to an embodiment of the present invention, as shown in Figure 3 RFID business event modeling block 30, model information verification block 31, specification automatic generation block 32, specification load block 35 , Model element conversion block 34, and model attribute information addition block 33.

The RFID business event modeling block 30 is a block that provides a GUI-type screen so that a user can input attribute information necessary for each model element for RFID business event modeling.

That is, the RFID business event modeling block 30 includes interfaces of RFID business events including BESpec and EPCIS Capture Spec, EPCIS Query Spec, and Provider Spec that are referenced by BESpec. It is expressed in GUI form and expresses the flow of RFID business event.

The model information verification block 31 checks the standard specifications presented by BESpec and EPC Network for each information necessary for the specification before automatically generating the specifications based on the information modeled by the user in the RFID business event modeling block 30. Verifies that it can be generated.

The automatic generation block 32 is an EPCIS Capture Spec and an EPCIS Query Specification according to the standards proposed by BESpec and EPC Network based on the information and transformation files modeled by the user in the RFID business event modeling block 30. (Query Spec) and Provider Spec are automatically generated to save the preview and generated specifications.

In addition, the specification automatic generation block 32 can quickly respond to the automatically generated documents through the conversion file defining the conversion rules for the automatically generated documents.

In addition, the specification load block 35 loads the specification generated automatically by using the RFID business event modeling block 30 and the specifications previously created by the user using another tool, and analyzes the specification information so that the specification is a modeling element. It verifies and analyzes whether it can be expressed and saves the information.

The model element conversion block 34 converts and represents the information of the specification analyzed from the specification load block 35 into a model element.

The model attribute information addition block 33 has a function of adding attribute information necessary for the corresponding model element based on the information obtained from the specification load block 35.

In addition, the operation progress between each component block of the RFID business event modeling system according to the present invention can be largely divided into an RFID business event specification generation function and a specification load function.

4A illustrates a process of generating a business event specification function, and illustrates a process of automatically generating various specifications through an RFID business event modeling block-> model information verification block-> automatic statement generation block.

4B illustrates a process of loading the specification load function, obtaining information from the specification load block, adding model elements through the model element transformation block, and adding necessary information to each model element.

In order to model the RFID business event, as shown in FIG. 1, through the analysis of the RFID business framework, as shown in FIG. 5, a component that can be represented as a modeling element may be defined.

5 is a table showing the components of the RFID business event model according to the present invention.

The RFID business event model component includes an element, parent, child, stereotype or notation, and comment.

The parent item refers to the upper model where each model element can be defined, and if not defined, it means the top element.

In the case of a child item, subordinate models that can be defined in each model element are defined, and in the case of undefined, there is no model element that can be defined inside.

In addition, the stereotype and notation items refer to the notation of the model that is actually visually expressed.In the case of the UML stereotype, the stereotype and notation items are expressed in the notation expressing only the stereo type defined in the form of a square with a common rounded corner. It means.

In the RFID business event modeling system according to the present invention, a model element definition necessary for a model element and analysis of attribute information of each model element are analyzed through analysis of the business event specification and the specifications presented by the EPC network. As in 6, the list of RFID business event model elements can be defined.

6A to 6C are tables showing RFID business event model element analysis lists.

In the list of RFID business event model elements, the object part represents an object that can be expressed as a model element, the "Spec" in () represents the specification to which the model element is converted, and the values in [] are the corresponding model object. Represents the model elements expressed below.

The attribute part represents an attribute of a model element of each model element, and the type represents various types of the attribute. The selection method indicates what kind of selection method the user has in the actual modeling process of the attribute of the corresponding model element, and when the type is blank, the attribute information of the corresponding model is received from the user.

Participation degree indicates the degree of participation in which the attribute information of the corresponding model element or model element is expressed. In case of [1], it is necessary model element or model attribute information, and [0 .. *] (* represents a number. ) Indicates that the model element or model attribute information may not be expressed or may be expressed in plural.

The BESpec part and the Spec part indicate whether the corresponding model property information is used in the Spec defined in the BESpec or the higher model object.

The Default part means the basic value of the property information, and the Validation part indicates information that the information verification module should verify the information when each property is automatically generated. will be.

The meta model diagram of the RFID business event model can be created through the list of the RFID business event model elements.

7 is a metamodel diagram of an RFID business event model.

As shown in FIG. 7, the meta-model diagram of the RFID business event model basically consists of an ExternalThing model and a BESpec model.

ExternalThing model is embodied as Variables model that can define the definition of variables used in RFID business event and Provider model that express information about ALE. In the case of a provider model, it is the reference information that is referenced when the provider spec is automatically generated.

The BESpec model consists of the Initial model, Final model, and InternalThing model, which represent the start and end of the flow of events. Each model contains information about the flow through the EventFlow model. Can be expressed.

After the linkage of notation for each metamodel and definition of model structure based on the metamodel defined as above, the RFID business event modeling function was implemented through automatic generation of code, and the user as shown in FIGS. 8A to 8F. Provide an interface.

8A to 8F are interface diagrams of an RFID business event modeling system according to the present invention.

Looking at the user interface of the RFID business event modeling system, the modeling canvas of FIG. 8A provides a visual environment that can be modeled using the RFID business event model elements, and the file view is the current user. Shows the file containing the model information and the diagram file, and the Property Editor provides the function to set the property information of each model.

The Palette Viewer provides the user with a choice of model elements that can be used on the Modeling Canvas. The user can select the required model elements in the Palette Viewer and drag and drop the model elements onto the modeling canvas, and the model created by the RFID business event modeling function is XMI (XML Metadata Interchange). ) File is created.

As shown in FIG. 8B, the automatic statement generation function provides a pop-up menu to the user to support the automatic statement generation function. The automatic statement generation function of the RFID business event modeling system is based on the model information generated through the RFID modeling module through the automatic RFID business event statement generation function shown in FIG. 4. Automatically generate Spec, Query Spec, and Capture Spec.

FIG. 8C is an interface configuration showing a result of verifying an RFID business event specification, and FIG. 8D is a user interface implementing an RFID business event specification automatic generation function.

8E is a pop-up menu configuration for implementing a query specification load function.

8F illustrates a configuration of a getStaticData model loaded through a specification load function.

And RFID business event modeling systems are not agile in responding to these requirements unless the specification of the structure of each specification or the change in the information to be represented and the automatic generation of additionally-formed documents are not considered.

Therefore, the present invention supports an automatic generation function of a document using a conversion file that defines a rule for the structure of each automatically generated document and a conversion relationship for RFID business event model information.

The structure of the transform file basically has an XML structure, and has a feature that is defined by reflecting the structure of the document to be converted.

9A and 9B are XML structural diagrams of transform files and transformed document information according to the present invention.

As shown in FIG. 9A, the conversion file is basically composed of ConvertElements.

Name in the attribute of ConvertElement refers to the name of the XML element to be converted, and sourceElement refers to the name of the referenced element in the XMI file information of the generated RFID business event model. The source type refers to the type of the referenced element.

In addition, the convert element can have its own, convert attribute, and convert text as sub-information. The convert attribute can specify the attribute value of the converting XML element and convert text. ) Can specify the text value of the XML element to be converted.

After the definition of each transformation element, the RFID business event modeling tool recognizes the information in the conversion file and uses the information in the RFID business event model to automatically generate the desired XML document according to the information in the conversion file.

9B illustrates an example of information of a document converted by applying a conversion rule. The defined conversion rule generates an XML element named “EPCISDS” through a name of a conversion element and generates an RFID business event. An element named "hasModel" in the model has a definition that refers to an element whose type is specified as "EPCISDS".

If the number of elements defined as “EPCISDS” is 10 in “hasModel”, all 10 elements are converted into XML elements called “EPCISDS”. Also, refer to the information of convert attribute for converting “EPCISDS” XML element to indicate that each attribute “epc”, “operation” exists and use the value of “epc”, “operation” of reference information. It is defined to be.

Also, the Text value for the “EPCISDS” transform element is defined to use the "assignValue" value of the reference information.

The conversion file used in the RFID business event modeling system according to the present invention designates a conversion rule for four automatically generated statements as a single file, so that when a user requests an automatic generation function, a conversion rule corresponding to each specification is assigned. Apply to support the creation of specifications desired by the user.

The user interface of the business event specification automatic generation function expresses the designated RFID business event model information in a tree format in the Business Event Model Information area as shown in FIG. 8D. The result of applying the conversion rule is displayed in the Preview of Generated Specification area and the property value of the selected element in the Property View.

The automatic generation of business event specifications enables the creation of all four specifications when selecting BESpec model elements, and the provider specification when selecting provider model elements and data query. Enables automatic generation of the capture specification when selecting the Query Spec model element and the selecting the Capture Query model element.

In addition, before the automatic generation of the specification, the model information verification module performs a process of verifying whether the user correctly defines the information required for the automatic generation of the specification. By expressing the relevant information in Validate View), the specification can be created correctly.

The specification loading function of the RFID business event modeling system according to the present invention is a function of loading a specification corresponding to a corresponding model element of a specification to be loaded by a user. FIG. 8E illustrates a query specification of a corresponding model element of a specification to be loaded by a user. Acquired data (getstaticdata) among the model elements of Spec), and shows a pop-up menu of a load function that can be selected by the user. FIG. 8F is a screen showing that the model elements are included through the load and corresponding information is included.

This specification load function reads the specification specified by the user, analyzes the information of the specification, obtains necessary information, adds model elements through the information represented as model elements in the obtained information, and adds attribute information of the model elements.

FIG. 10A illustrates an example of a business event model generated by the RFID business event modeling system, and FIG. 10B illustrates an example of a BESpec generated from the modeled model.

10C illustrates a provider specification generated from a modeled model, and FIG. 10D illustrates an example of a data query in a query specification.

FIG. 10E illustrates an event data query among query specifications generated from the modeled model, and FIG. 10F illustrates a capture specification generated from the modeled model.

The RFID business event modeling system according to the present invention provides an RFID business event modeling function, expresses the flow of RFID business events through defined model information, automatically generates RFID business event specification and EPC Network standard specification, and Load function can be supported.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention.

Therefore, the technical scope of the present invention should not be limited to the contents described in the embodiments, but should be defined by the claims.

1 is a configuration diagram of a framework based on RFID business

2 is a block diagram of a business event specification of the RFID business-based framework

3 is a block diagram of an RFID business event modeling system according to the present invention.

4A and 4B are flowcharts illustrating an RFID business event modeling operation according to an embodiment of the present invention.

5 is a table showing the components of the RFID business event model according to the present invention

6A to 6C are tables showing an analysis list of RFID business event model elements.

7 is a metamodel diagram of an RFID business event model

8A to 8F are interface diagrams of an RFID business event modeling system according to the present invention.

9A and 9B are XML structure and transformation document information configuration diagram of the change file according to the present invention.

10A to 10F are schematic diagrams generated by using an RFID business event modeling system according to the present invention.

Explanation of symbols for the main parts of the drawings

30. RFID business event modeling block 31. Model information verification block

32. Specification automatic block 33. Add model attribute information block

34. Model element transformation block 35. Specification load block

Claims (14)

An RFID business event modeling block representing an interface of the RFID business event in a GUI form and expressing a flow of the RFID business event; A model information verification block verifying a possibility of generating a standard specification based on information modeled by a user in the RFID business event modeling block; Based on the conversion file that supports specification generation based on the information modeled by the user by defining rules for the relationship between the information modeled by the user, the structure of the automatically generated documents, and the RFID business event model information. RFID business event modeling system comprising a; automatic generating block for generating a statement with. An RFID business event modeling block representing an interface of the RFID business event in a GUI form and expressing a flow of the RFID business event; A model information verification block verifying a possibility of generating a standard specification based on information modeled by a user in the RFID business event modeling block; Based on the conversion file that supports specification generation based on the information modeled by the user by defining rules for the relationship between the information modeled by the user, the structure of the automatically generated documents, and the RFID business event model information. A statement automatic generation block for generating a statement with; A specification load block which loads the specifications created by the user among the generated specifications and previously generated and stored specifications, reads the specifications, analyzes the information included in the specifications, and verifies whether they can be expressed as modeling elements; A model element conversion block for converting specification information analyzed in the specification load block into a model element; And a model attribute information addition block for adding attribute information required for a corresponding model element based on the information obtained from the specification load block. The method of claim 1 or 2, wherein the RFID business event modeling block, BESpec (Business Event Specification), Capture Spec defined for storing RFID history information in EPC Information Service (EPCIS) referred to by BESpec, history information related to EPC stored in EPCIS repository, or a corresponding entity of EPC (Electronic Product Code) It expresses the interface of RFID business event in GUI form including Query Spec for querying unique information possessed by the user and Provider Spec that defines the interaction with the event provider that provides the real-time event. RFID business event modeling system. The method of claim 3, wherein the BESpec (Business Event Specification), An RFID business event modeling system that supports the EPCglobal architecture, supports the development and management of RFID systems, and is an XML (Extensible Markup Language) based specification that expresses data acquisition and processing in the RFID business event framework. The method of claim 1 or 2, wherein the model information verification block, RFID business event modeling system characterized by verifying that the specifications generated based on the user-modeled RFID business event model conform to BESpec (Business Event Specification) and EPC (Electronic Product Code) network standards and expressing the verification result . The method of claim 1 or 2, wherein the automatic statement generation block, Based on the modeled information and the conversion file, the provider specification, the EPCIS capture specification, and the EPCIS query specification are matched to the standards suggested by BESpec (Business Event Specification) and EPC (Electronic Product Code) Network. RFID business event modeling system to automatically generate a support to preview and to save the generated specifications. The method of claim 1 or 2, wherein the model element definitions required for each model element and attribute information of each model element in the RFID business event modeling block, A parent item that means a parent model where each model element can be defined. If not defined, a parent item means a top element, Child items that can be defined inside each model element. If not defined, a child item means that there are no model elements inside, and RFID business event modeling system, characterized in that the definition of the stereotype (notation) and notation (notation) items that represent the notation of the model that is actually represented visually. The RFID business event model element list of claim 1, wherein the RFID business event model for modeling the RFID business event comprises: An object part representing an object that can be represented by a model element, An attribute part representing an attribute of a model element of each model element, The type part that represents how the model element's properties can be selected by the user during the actual modeling process, The participation part in which the model element or attribute information of the model element is expressed; A business event specification (BESpec) part indicating whether the corresponding model attribute information is used in a business event specification (BESpec), and whether the corresponding model attribute information is used in a specification defined in an object of a higher model. The Spec part that it represents, Default part that means the basic value of the property information, RFID business event modeling system, characterized in that it comprises a Validate portion indicating the attribute information that should be automatically verified in the model information verification block when the specification is automatically generated. The method of claim 8, wherein the meta model diagram of the RFID business event model created through the RFID business event model element list, ExternalThing model embodied as Variables model that can define the definition of variables used in RFID business event and Provider model that express information about ALE (Application Level Event). , RFID business event modeling system comprising a BESpec model consisting of an Init model, a Final model, and an InternalThing model to indicate the start and end of an event flow. The method of claim 1 or claim 2, wherein the attribute of the conversion element (ConvertElement) of the conversion file in the specification automatic generation block, Name property that refers to the name of the Extensible Markup Language (XML) element that you are actually converting. A source element attribute that indicates the name of the referenced element in the information in the XML Metadata Interchange (XMI) file of the generated RFID business event model, RFID business event modeling system comprising a sourceType attribute that indicates the type of the referenced element. The method of claim 10, wherein the convert element (Convert Element) has a sub-information of itself, the Convert attribute (ConvertAttribute), Convert Text (ConvertText), Convert Attribute (ConvertAttribute) can specify the attribute value of the Extensible Markup Language (XML) element to convert, Convert Text (ConvertText) can specify the text value of the Extensible Markup Language (XML) element to convert Event modeling system. The user interface of claim 1 or 2, wherein the user interface supported by the RFID business event modeling block includes: Modeling Canvas screen that provides a visual environment that can be modeled using RFID business event model elements, File view screen showing the file containing the model information currently modeled by the user and the diagram file, Properties Editor screen for setting property information of each model, RFID business event modeling system comprising a palette viewer screen that provides a user with a selection function for model elements that can be used in a modeling canvas. The method of claim 12, wherein the user can select a required model element in the Palette Viewer to represent the model element in a drag-and-drop form on the modeling canvas, and is generated through an RFID business event modeling function. The model is an RFID business event modeling system, characterized in that it is generated as a file in the form of XML Metadata Interchange (XMI). The user interface of claim 1 or 2, wherein the user interface supported by the specification automatic generation block comprises: Business Event Model Information screen that displays the specified RFID business event model information in tree format, Preview of Generated Specification screen that displays the results of applying transformation rules for a particular tree element when selected. And a property view screen displaying property values of the selected element.

Images