KR100880883B1 - Business process management system and method in RFID middleware - Google Patents

Abstract

The present invention relates to a business process management system and method for an RFID middleware, wherein the business process management system is a system for managing a business process in an RFID middleware, wherein the RFID middleware is obtained by an external device including an RFID reader. A middleware management system that controls and manages the adapter, the filter, and the report when the adapter comprises a adapter for converting the data, a filter for filtering the data of the adapter, and a report generator for converting the filtered data to an application system; And a business management unit for storing and managing a plurality of adapters, filters, and report generators controlled and managed by the middleware management system for each business process.

According to the present invention, it is possible to independently monitor the status of the business, bringing user convenience because it does not have to stop or start the middleware engine separately to test, stop or start the business process.

Description

Business process management system and method in RFID middleware

1 is a schematic diagram illustrating an RFID management structure according to the prior art, and illustrates an independent control management structure through a program provided for each equipment company.

2 is a diagram illustrating the structure of an RFID management system.

3 is a detailed structural diagram of the RFID management apparatus 300.

4A to 4C are flowcharts illustrating operations of the reader management unit in the RFID management apparatus 300. FIG. 4A illustrates the operation of the model manager, FIG. 4B illustrates the operation of the reader manager, and FIG. 4C illustrates the operation of the reader operator.

5A to 5C are flowcharts illustrating operations of the data source manager in the RFID management apparatus 300. FIG. 5A illustrates an operation of the data source manager, FIG. 5B illustrates an operation of the data source operator, and FIG. 5C illustrates an operation of the log manager. do.

6A and 6B are flowcharts illustrating operations of the filter manager in the RFID management apparatus 300. FIG. 6A illustrates the operation of the product filter unit and FIG. 6B illustrates the operation of the condition filter unit.

7A and 7B are flowcharts illustrating operations of a user manager in the RFID management apparatus 300. FIG. 7A illustrates operations of the user search unit and FIG. 7B illustrates operations of the user manager.

8 to 17 show examples of screens displayed to the user in the RFID management system.

18 shows an example of a program for turning on / off the reader status in the leader operating unit of the leader management means.

19 shows an example of a program that registers filtering conditions in the condition filter unit of the filter management means.

20 is a block diagram illustrating a configuration of an RFID middleware and a management system to which a business process management system of the RFID middleware according to the present invention is applied.

21 is a block diagram illustrating a more detailed configuration of the user interface 2050.

22 illustrates an embodiment of a business process management system of RFID middleware according to the present invention.

23 is a flowchart illustrating a business process management method of an RFID middleware according to the present invention.

24 is a flowchart illustrating the operation of the user interface of the present invention.

As shown in FIG. 25, the present invention may control each business process.

26 is a flowchart illustrating a user interface method provided by the present invention.

27 and 28 illustrate implementation examples of the user interface method in the present invention.

The present invention relates to an RFID management system and method, and more particularly to a business process management system and method of RFID middleware.

In general, an RFID (Radio Frequency Identification) system is an RFID tag containing unique data, an RFID reader for reading the information of the RFID tag, and a series of computing systems for processing data read by the RFID reader. It is composed.

RFID tag is composed of transponder chip and antenna made of semiconductor, and receives energy from external radio signal (passive type) or energy from battery provided by itself (active type). Send.

The RFID reader can obtain desired information by decoding and decoding the signal received through the antenna. The data obtained through the RFID tag and the RFID reader is used as useful information by interworking with internal applications such as an enterprise. The information processing system using the RFID technology can be largely divided into a device layer, a middleware layer, and an application layer.

The device layer is composed of a tag for storing unique information (data) and a reader for reading and identifying the information of the tag, and collects data of the tag. The middleware layer collects and filters tag data transmitted from the device layer to be effectively used in the application layer, and manages hardware such as an RFID reader or a label printer. The application layer uses the transmitted tag data to actually apply to application software such as enterprise resource planning (ERP), supply chain management (SCM), customer relationship management (CRM), and the like. Perform the function.

On the other hand, in order to connect with an application by applying RFID in the enterprise, the client program (software) provided by the RFID reader equipment company is installed and connected to the corresponding software to control the status of the RFID reader. The manager accesses and controls the reader using each program provided by the equipment company. For example, as shown in FIG. 1, when a client program provided by a first equipment company is written in JAVA, a client program written in Java must be used in order to use a device provided by the first equipment company. do. Similarly, when a client program provided by a second equipment company uses a web user interface (UI), a web UI must be used in order to use a device provided by the second equipment company. If the client program is written in Visual Basic, the client program written in Visual Basic should be used in order to use the device provided by the third equipment company.

However, the software provided by each equipment company is different in the program environment, interface, reader control command, etc. Therefore, the user has to use a device provided by one company.

In addition, even when the device needs to be upgraded or replaced, it is inconvenient to use a device provided by another company and use only a device of a specific company. If a user wants to use a device provided by another company, he / she should learn how to use software provided by another company, and it is difficult to control each device because the compatibility between devices provided by different companies is difficult. The following problems arise.

Therefore, there is still a need for an RFID management system or method that can integrate and control different types of RFID devices provided by different companies, and in particular, a programming language (eg, JAVA, Visual) that processes identification codes. Regardless of standardization, there is a need for an RFID management system or method that can provide a convenient and consistent interface to users or administrators regardless of the standard.

In addition, the conventional RFID middleware and management tools did not have the function of independently monitoring the business situation. In building an RFID system, the middleware engine had to be stopped or started to test, stop, or start a business process. This will be described in more detail as follows.

The engine startup of the RFID middleware works in conjunction with the business process processing engine. In other words, if the middleware engine is started, the business processor processing engine is also started. Since only the business process processing engine cannot be separated and controlled, only one business process must be registered or deleted in middleware to test or monitor a specific business. And when the testing or monitoring of a specific business is finished, it is troublesome to restart the middleware engine. For example, if the tag data read by company A's reader at the factory gate contains duplicate data, it must be delivered to the ERP system by HTTP after applying the filter to remove it and the filter to select only AA products. Let's say In this case, one business process can be defined. If a reader at a specific location fails while the RFID system is constructed and operated, it is inconvenient to separate and stop only the business process defined above, and to stop the RFID middleware itself.

Therefore, various cases may occur in a business environment using RFID, and in order to flexibly cope with and monitor these cases, it is necessary to separate business process engine control.

The present invention was devised to solve the above problems of the prior art, and an object of the present invention is to start or stop for each business process without affecting the starting and stopping of the middleware engine in the RFID system, RFID It is to provide a business process management system and method of the middleware.

Business process management system of the RFID middleware according to the present invention for achieving the above technical problem, the system for managing a business process in the RFID middleware, the RFID middleware is data obtained by an external device including an RFID reader A middleware management system including an adapter for converting the data, a filter for filtering the data of the adapter, and a report generator for converting the filtered data to an application system, and controlling and managing the adapter, the filter, and the report; And a business management unit for storing and managing a plurality of adapters, filters, and report generators controlled and managed by the middleware management system for each business process.

The business management unit may include a business identifier storage unit for assigning identification information to each business process to manage all business processes, and the information of the plurality of adapters, filters, and report generators may be managed in a linked list structure. Do. In addition, the business management unit preferably further comprises a user interface for providing a tool for monitoring, modifying, deleting, adding the business processes. The user interface unit displaying a list of the business processes; If one of the businesses displayed through the business list unit is selected, it is preferable to include a business information provider for providing adapter, filter and report generator information used for the selected business. The business information providing unit may further include a business control unit that can individually modify, delete, and add adapters, filters, and report generators used in the business process.

Business process management method of the RFID middleware according to the present invention for achieving the technical problem, an adapter for converting the data obtained by an external device including an RFID reader, a filter for filtering the data of the adapter, the filtered data A method of managing a business process in an RFID middleware comprising a report generator for converting it to an application system, the method comprising: managing a business process by a middleware management system controlling and managing a plurality of the adapters, filters, and report generators step; And controlling and managing the plurality of adapters, filters, and report generators for each business process. Displaying the list of business processes when the present invention further comprises a user interface providing a tool for monitoring, modifying, deleting and adding business processes; If a business process is selected from the list of business processes, providing adapter, filter and report generator information used for the business process; If any one of the adapter, filter, and report generator is selected, providing a menu for modifying, deleting, and adding the selected adapter, filter, and report generator.

A computer readable recording medium having recorded thereon a program for executing the invention described above is provided.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings and preferred embodiments. For reference, in the following description, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention are omitted.

The present invention is an invention further improved by using an unpublished prior application filed by the applicant. For reference, the unpublished prior application has the name of the invention as a RFID management system and method, a prior application (application number 10-2005-136314, file date: October 31, 2005) and priority claims application (application number 10-2006-4543, Filing date: 2006.1.16).

Therefore, before describing the present invention in detail, first of all, the RFID management system and method used in the present application will be described.

2 is a diagram showing the structure of the above-listed RFID management system. The RFID management system may be largely classified into an RFID control apparatus 200 and an RFID management apparatus 300. The RFID controller 200 collects, filters, and transmits tag data transmitted from each reader 110, 120, and 130 to the application 500, and the RFID management apparatus 300 provides a user with It provides an interface (UI; User Interface) and interlocks with the RFID control apparatus 200 to perform reader control, data source management, filter management, and the like.

Hereinafter, an RFID management system and method according to a preferred embodiment in association with an RFID tag, an RFID reader, and an application will be described in detail.

The RFID tag 100 is attached or provided to an object requiring identification of a person, a vehicle, a product, a traffic card, and the like, and stores detailed information (tag data) of the object. RFID tags can be classified into three types according to their read / write capabilities: read only tags, write once read many tags, and read / write tags. Since it is programmed from the beginning, the information can't be changed. WORM tag allows users to program data, but not after that. Read / write tags can be changed program or data many times.

The RFID readers 110, 120, and 130 perform a function of recognizing and transmitting the tag 100 existing in the reader recognition space to the RFID control apparatus 200. The RFID reader includes one or more antennas to receive information transmitted from the RFID tag. If the RFID reader includes a plurality of antennas, each antenna individually receives tag information and transmits it to the RFID control apparatus 200. Can be implemented. Meanwhile, each RFID reader transmits tag data to the RFID control apparatus 200 using a different message format or protocol according to the reader manufacturer (equipment manufacturer) or model. In FIG. 2, a first reader (eg, Alien Reader) 110 having four antennas 111, 112, 113, and 114 is connected to the first reader adapter portion 211 of the RFID control device 200. The second reader (eg, Matrics Reader) 120 having two antennas 121 and 122 is connected to the second reader adapter 212 of the RFID control apparatus 200, and one antenna 131. The third reader (eg, Intermec Reader) 130 having the control unit is connected to the third reader adapter unit 213 of the RFID control apparatus 200 to transmit tag data in a different message form to the corresponding reader adapter unit. Illustrated.

The RFID control apparatus 200 according to the preferred embodiment is largely composed of a reader adapter 210, a core engine 220, and an application adapter 230.

The reader adapter 210 includes a reader adapter unit corresponding to each reader in order to receive tag data from heterogeneous readers. In FIG. 2, first, second, and third reader adapters corresponding to three different types of first, second, and third readers 110, 120, and 130, respectively, using different message types (protocols). The parts 211, 212, 213 are shown. In detail, the first reader adapter converts data (tag data) of the first message format transmitted from the first reader into data of the third message format. Similarly, the second reader adapter converts the data in the second message format sent from the second reader to the data in the third message format. Here, the third message format is a message format for integrating different message formats used by heterogeneous readers into one, which may be one of the message formats already used (for example, used by the third reader). The message format is defined by the RFID International Standards Organization. Meanwhile, the reader adapter may further include a reader adapter unit related to standardization, for example, a reader adapter unit for an EPC (Electronic Product Code) for further expansion, in addition to the reader adapter unit for the readers currently used, which is illustrated in FIG. 2. A fourth reader adapter 214 is shown. The reader adapter is interlocked with the reader managing means 310 of the RFID management apparatus 300 to be described later, and controlled by the reader managing means from the user, so that the user can remotely control the RFID reader. On the other hand, the tag data received from each reader adapter unit 211, 212, 213 is transmitted to the core engine 220.

The core engine 220 performs a function of collecting and filtering tag data. The core engine includes a data collector 221 for collecting tag data received through one or more readers, and a filtering unit 222 for extracting data corresponding to a condition desired by a user from the collected data. In addition, when the amount of data is large, in order to reduce the data throughput of the filtering unit, it may be implemented to include a pre-filtering unit 223 for extracting only a specific product or removing redundant tag data in advance.

The application adapter 230 provides an external service call unit 231 for passing the filtered result to an external service server defined in the filter condition, and an API for allowing the application to control the reader or reporting the result to the application. It consists of an Application Programming Interface unit 232.

The above-described RFID control apparatus may be implemented in the form of a server, and in this case, components such as the reader adapter, the core engine, and the application adapter may be implemented in the form of hardware or middleware.

On the other hand, the above-described RFID control device 200 is interlocked with the RFID management device 300, the RFID management device 300 allows a user or administrator to control the RFID control device 200 in a web environment or remotely Provide an interface. In addition, an EPC network 400 such as an ONS (Object Name Service) server that provides location information of a PML server, and a Physical Markup Language (PML) server that stores and manages static information of objects and historical information recognized through RFID technology. ) Can be linked with the component.

RFID management apparatus 300 according to the preferred embodiment is largely composed of a reader management means 310, data source management means 320, filter management means 330, user management means 340.

The leader management unit 310 performs a function of managing functions provided by equipment companies, such as operation control and status monitoring, for heterogeneous readers using the same interface. The leader management unit 310 may be subdivided into a model manager 311, a leader manager 312, and a leader operator 313.

The model manager 311 registers, modifies, deletes, and outputs detailed model information such as class, model number, manufacturer, maximum output, and number of antennas for each reader. Referring to FIG. 4A, the model manager first displays a model name input screen when there is a request for registering model information from a user (S411). Then, it is checked whether the corresponding model is registered based on the reader model name input by the user (S412). If model information corresponding to the input model name is not registered in the database, the model manager displays a model information registration screen (see FIG. 8) (S413). When the user registers detailed model information of the leader (S414), newly registered model information is displayed (S415) (see FIG. 9). On the contrary, if the corresponding model information is registered in the database, the model manager displays the registered model information (see FIG. 9). On the other hand, such a model registration process may also be performed at the request of the leader management unit 312, if the model information for the leader to be registered in the leader management unit is not registered in the database 350, the leader management unit to the model management unit Upon requesting registration, the model manager checks whether the corresponding model is registered based on the input information and registers detailed model information.

The process of modifying or deleting model information is performed by displaying a model information modification screen or a model information deletion screen when a user requests for model information modification or deletion, and corrects or deletes model information according to information input from the user. . Finally, the process of outputting the model information is a process of displaying or printing the model information so that the user can recognize the model information.

The reader manager 312 may include a reader name (reader name), model name, network setting information (reader IP address, reader port number, gateway address, netmask address, DNS address, host IP address, host port number, etc.). Performs a function to register, modify, delete, and print detailed reader information. Referring to FIG. 4B, the reader manager first displays a reader name input screen when there is a reader information registration request from the user (S421). Then, it is checked whether the leader is registered based on the reader name input by the user (S422). If the leader information corresponding to the input leader name is not registered in the database, the reader manager displays the leader information registration screen (see FIG. 10) (S423). When the user registers detailed leader information of the leader (S424), it is inquired whether model information of the newly registered leader is registered in the database (S425). In this case, if the model information of the leader is not registered, the leader manager requests model registration from the model manager and the above-described model registration process is performed (S426). When the model registration process is completed or the model information of the leader is registered from the beginning, the leader management unit displays the registered leader information (S427) (see FIG. 11). On the other hand, if the reader information corresponding to the input reader name is already registered in the database, it is inquired whether to terminate the leader information registration, modifying or deleting the reader information, and performs the corresponding function according to the information input by the user.

The process of modifying or deleting the leader information is similar to the process of modifying or deleting the above-described model information, and displays a reader information modification screen or a reader information deletion screen when a reader information correction or deletion request is made from the user, and is input from the user. This is done by modifying or deleting the leader information according to the information. In addition, the process of outputting the reader information displays or prints the reader so that the user can recognize the reader information.

The reader operating unit 313 controls the on / off status of the reader, the output strength of the radio wave, the function of changing the order of the antennas when a tag is read, and when and how many times the tag data has been read by a specific reader. Performs overall control of the reader, including monitoring functions. Referring to FIG. 4C, the reader operating unit first displays a reader control screen (see FIG. 12) when there is a request for status information of the reader from the user (S431). Then, the information of the reader registered in the database is extracted according to the reader information (eg, the reader name) input from the user (S432), and the reader adapter of the RFID control device is requested to the status information on the reader to be controlled by the user ( S433). The reader adapter checks the status of the reader through the reader adapter corresponding to the reader, and transmits the status information of the reader to the reader operator. The reader operating unit displays this (S434), and controls the reader according to the control information input from the user. For example, when a user requests a state change of a specific reader (S435), the reader operator transmits the state change request information on the corresponding reader, which is divided by company or model, to the reader adapter of the RFID control device (S436). The reader adapter unit corresponding to the corresponding reader is controlled to change the state of the reader (S437). The reader adapter transmits the result to the reader operating unit, and the reader operating unit outputs state information about the reader (S438). For reference, FIG. 18 illustrates a part of a program for turning on / off the reader state in the leader operating unit of the leader management unit.

In addition, the function of controlling the output strength of radio waves, changing the order of antennas when a tag is read, and monitoring of which tag data has been read by a particular reader at any time and similar to the above-described state control (change) It can be performed as.

The data source management unit 320 performs a function of separating or grouping each reader and antenna according to a purpose and purpose. In the present invention, such logically divided or grouped units are defined as a data source. In addition, the data source management unit 320 according to the present invention may be subdivided into a data source management unit 321, a data source operation unit 322, and a log information unit 323.

The data source manager 321 separates and / or groups each reader and antenna to define a data source. For example, if the first and second antennas 111 and 112 of the first reader 110 and the first antenna 121 of the second reader 120 are connected to the inventory management shelf, The first and second antennas 111 and 112 and the first antenna 121 of the second reader 120 may be defined as one data source. The data source management unit displays the reader and antenna information registered in the reader management means on the screen, and the user can know which reader and antenna are configured as the data source. On the other hand, the data source defined in the data source management unit may be used as a filter application unit to be used in the filter management means to be described later. 5A illustrates a process of registering a data source in the data source manager. First, the data source manager displays a data source registration screen (see FIG. 13) (S511). Then, the list of readers not included in the registered data source is searched (S512). If a reader that is not included in the data source exists (S513), data source information registration is requested, and when the corresponding reader is registered as the data source (S514), the registered data source information is displayed (S515). On the other hand, if there is no reader included in the data source, the data source registration process is terminated.

The data source operator 322 performs a function of monitoring tag data (eg, tag ID, read time, location, etc.) read through the respective data sources. In addition, the data source operator may send commands collectively to the reader or antenna grouped by the data source. 5B illustrates a process of changing a state of a specific reader in the data source operator. First, the data source operator displays a data source control screen (see FIG. 14) (S521). In operation S522, the data source information list is retrieved and displayed according to a user's request. If there is a request for controlling a specific data source (eg, changing the state of the reader) from the user (S523), the data source operation unit extracts and displays the reader information included in the corresponding data source (S524). In addition, when a user requests a state change of a specific reader, the data source operation unit requests a state change of the corresponding reader to the RFID control device (S526), and the reader adapter unit changes the state of the reader to change the state from the RFID control device. When the completion signal is transmitted (S527), the data source information is output (S528).

The log information unit 323 records the results of the tag data filtered through the data source in the form of a file or the like in a database or storage means and displays the recorded details. 5C illustrates a process of outputting log information corresponding to a specific data source in the log information unit. The log information unit first displays a data source selection screen (S531), and when selection information of a specific data source is input by a user (S532), retrieves log information of the corresponding data source (S533), and outputs log information (S5313). S534).

The filter manager 320 performs a function of managing filtering, logging, etc. of data sources defined through the data source manager. The filter managing unit 320 may be divided into a product filter unit 321 and a condition filter unit 322.

The product filter unit 321 provides a function of registering and managing conditions so that a specific reader processes only a specific product code. For example, when a plurality of readers are installed in each plant for each process or product, the product code value may be registered in advance, and the reader may control to process only a specific product code. 6A illustrates a process of registering a filtering condition for a specific product in the product filter unit. First, the product filter unit displays a product filter registration screen (see FIG. 15) (S611). When a product filter condition is input by a user (S612), the product filter unit selects a code of a product to be filtered (S613). The product filter information is registered, and the registered product filter information is output (S614).

The condition filter unit 322 provides a function of registering and managing specific conditions to be filtered. The condition filter part is mainly used to give more specific conditions in the process after the product filtering is performed. The user may assign a condition only to a specific antenna of a specific reader through the condition filter unit or condition to process only tag data read at a specific time. 6B illustrates a process of registering a filtering condition for a specific reader and / or a specific antenna in the condition filter unit. First, the condition filter unit displays the condition filter registration screen (see FIG. 16) (S621). When a data source to which the filtering condition is to be added is selected by the user (S622), the condition filter unit requests to input a specific condition. Then, the user inputs specific filtering conditions such as a filter target item, an operator, a filter value (S623), and the condition filter unit determines whether the input filtering conditions are matched (validity) (S624). If the condition is not matched (not valid), the condition filter unit requests re-entry of the filtering condition, and if the condition is matched (if appropriate), registers the condition filter information and outputs the registered condition filter information ( S625). For reference, FIG. 19 is an excerpt of a program for registering filtering conditions in the condition filter unit of the filter management means.

The user managing means 340 performs a function of managing a user of the RFID managing apparatus 300. This may be divided into a user searcher 341 and a user manager 342.

The user search unit 341 provides a function for searching a list of currently registered users. As shown in FIG. 7A, the user search unit displays a user search screen (S711), searches for user information in a database based on information input from the outside (user, administrator, etc.) (S712), and searches the searched user list. The function of outputting is performed (S713).

The user manager 342 manages (controls) the reader and the RFID control device or manages user information to be used. That is, the user manages the reader management means, data source management means, filter management means, registers, modifies, deletes users, and grants access rights. 7B illustrates a process of performing user registration in the user manager. Referring to FIG. 7B, the user manager displays a user registration screen (see FIG. 17) (S721), and when a user ID is input (S722), the user manager determines whether a user ID exists by searching a list of users stored in a database (S722). S723). As a result of the determination, if the user ID does not exist, the user ID is requested to be re-entered, and if the user ID exists, the user information input is required. When the user information is input (S724), the user manager displays the newly registered user information (S725), thereby completing the user registration process.

Meanwhile, the database 350 may be provided in the RFID management apparatus or the RFID control apparatus, and may also be implemented as an external database as shown in FIG. 2. The database 350 stores model information, reader information, data source information, user information, and the like, and the information is implemented to be integrated and stored in a single database, or the model information database, reader information database, data source information database, It may be implemented to be stored separately in a separate database such as a user information database.

Finally, the application 500 applies the transmitted tag data to actual tasks such as enterprise resource planning (ERP), supply chain management (SCM), and customer relationship management (CRM).

In the above, the RFID management system and method of the present invention of the present invention has been described. The above-described invention can provide an integrated interface for RFID management for heterogeneous readers, monitor tag data transmitted from each reader in real time, and filter only desired tag data by assigning specific conditions. have. However, there was a limitation in that it could not control the RFID middleware by business processor.

Hereinafter, the present invention will be described in detail by using the above-described invention.

20 is a block diagram illustrating a configuration of an RFID middleware and a management system to which a business process management system of the RFID middleware according to the present invention is applied. As shown in FIG. 20, the business process management system of the RFID middleware according to the present invention includes a middleware management system 2020 and a business management unit 2040, and further includes a user interface unit 2050. desirable.

Referring to FIG. 20, first, an RFID middleware 2000 to which the present invention is applied includes an adapter 2002 for converting data obtained by an external device 2060 including an RFID reader, a sensor, and a printer, and filtering the data of the adapter. Filter 2004, and a report generator 2006 for converting the filtered data to fit the application system 2080.

The middleware management system 2020 controls and manages the adapters, filters, and reports, and may be replaced with the RFID management apparatus 300 shown in FIG. 2.

 The business manager 2040 stores and manages a plurality of adapters, filters, and report generators controlled and managed by the middleware management system 2020 for each business process. The business management unit 2040 includes a business identifier storage unit 2042 for assigning identification information to each business process to manage all business processes. The business manager 2040 preferably manages the information of the plurality of adapters, filters, and report generators in a linked list data structure.

In addition, the business management unit 2040 preferably further includes a user interface unit 2050 to provide user convenience. The user interface 2050 provides a tool for monitoring, modifying, deleting, and adding the business processes. 21 is a block diagram illustrating a more detailed configuration of the user interface 2050. The user interface 2050 includes a business list unit 2100 and a business information provider 2120. The business list unit 2100 displays a list of the business processes. The business information provider 2120 provides adapter, filter, and report generator information used for the selected business when one of the businesses displayed through the business list unit 2100 is selected.

The business information provider 2120 may further include a business controller 2125 for individually modifying, deleting, and adding adapters, filters, and report generators used in the business process.

22 illustrates an embodiment of a business process management system of RFID middleware according to the present invention.

23 is a flowchart illustrating a business process management method of an RFID middleware according to the present invention. 24 is a flowchart illustrating the operation of the user interface. The operation and method of the business process management system of the RFID middleware according to the present invention will be described with reference to FIGS. 23 and 24.

First, a middleware management system 2020 that controls and manages the plurality of adapters, filters, and report generators manages a business process. (S2300) That is, adapters used in a business process are adapter-specific, filters are filter-specific, and report generator. Are managed for each report generator. (S2350) In this state, they are managed for each business process. That is, it controls and manages the adapters, filters, and report generators used in the business process for each business process.

24 is a view for explaining an implementation example of the business process management method of the RFID middleware according to the present invention. In FIG. 24, Properties 2402 indicate files that set information necessary for starting the RFID middleware engine, and XML Instances 2404 indicate overall functions of the RFID middleware such as information required for device connection such as a reader and information for application interworking. Represents XML documents containing information necessary to perform, Log Files (2406) represents a file that records useful information for monitoring among the information found while the RFID middleware is running. The main task processor 2408 represents a main method for distributing and processing a process for an initialization task and a request for an RFID middleware environment setting and the like. The configuration management unit 2410 analyzes and interprets documents related to configuration. The XML management unit 2412 manages an XML document containing configuration information regarding a device, a filter, a report, and the like, and binds and manages it as a Java object. The event management unit 2414 distributes the event data to listeners and corresponding modules for receiving and processing the event data. The device manager 2416 manages adapters for interworking with an RFID reader, a sensor printer, and the like. The filter management unit 2418 manages various types of filters and filters tag data. The report management unit 2420 manages various types of reports and reports filtered tag data in various ways.

Referring to FIG. 24, first, a main task processor 2408 of middleware called an edge server analyzes a properties file (①) related to configuration and an XML document (②) containing information necessary for interworking a device and an application. Put it in memory as an XML binding object (③). In addition, the sensor, filter, and report connection chains are analyzed among the contents specified in the binding object to create a connection chain (④) for each business case. The sensor declares a corresponding object ⑤ in the device management unit 2416, and the filter declares a corresponding object ⑥ declared in the filter management unit 2418. The report declares a corresponding object ⑦ in the report management unit 2420. When the preparation for the setting information is completed, the event management unit 2414 raises a listener and enters a waiting state ⑧ for receiving event data.

When defining by business process, each piece of information is managed separately in an XML document, and each linked business list has its own linked list for each defined business process when the middleware engine starts up, allowing you to store and manage adapter, filter, and report information, For management, store identifiers in each. When requesting control of a specific business process, the identifier, or name, of the business process is found to control the linked list.

As shown in FIG. 25, the present invention may control each business process. 25 is a conceptual diagram of a business process management method in RFID middleware according to the present invention. Here, RA1, RA2, and RA3 represent different kinds of reader adapters, F1, F2, F3, and F4 represent various kinds of filtering methods, and R1, R2, and R3 represent various kinds of report methods. And Control indicates control of start / stop / log / monitor by process.

By managing a separate linked list for each business case, you can monitor and start / stop without affecting other business processes.

26 is a flowchart illustrating a user interface method provided by the present invention. First, a list of business processes is displayed (S2600). When a business process is selected from the list of business processes (S2610), information on adapters, filters, and report generators used in the business process is provided (S2620).

If any one of the adapter, filter, and report generator is selected (S2630), a menu for modifying, deleting, and adding the selected adapter, filter, and report generator is provided. If the delete menu is selected, the delete function is performed, and if the add menu is selected, the add function is performed. (S2650)

27 and 28 illustrate implementation examples of the user interface method according to the present invention. FIG. 27 and FIG. 28 are screens provided as a user interface with a mechanism for separately controlling each business case in an RFID middleware. To see the tag data generated in the kiosk, click the 'Log' button to see the screen. Also, if you select a service, you can check the information set in the service, which reader is connected, and which filter is reported in what way through the process.

On the other hand, the present invention described above can also be embodied as computer readable codes on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disks, hard disks, optical data storage devices, and also in the form of carrier waves (e.g., transmission over the Internet). It includes what is implemented. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. And functional functional programs, codes and code segments for implementing the present invention can be easily inferred by programmers in the art to which the present invention belongs.

Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art to which the present invention pertains can implement the present invention in other specific forms without changing the technical spirit or essential features, The examples are to be understood in all respects as illustrative and not restrictive.

In addition, the scope of the present invention is specified by the appended claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts are included in the scope of the present invention. Should be interpreted as

According to the present invention, it is possible to independently monitor the status of the business, bringing user convenience because it does not need to stop or start the middleware engine separately in order to test, stop or start the business process.

Claims (10)

A system for managing business processes in RFID middleware, The RFID middleware includes an adapter for converting data acquired by an external device including an RFID reader, a filter for filtering data of the adapter, and a report generator for converting the filtered data to suit an application system. A middleware management system for controlling and managing the adapter, filter, and report generator; And Business process management system of the RFID middleware, characterized in that it comprises a business management unit for storing and managing a plurality of adapters, filters and report generators controlled and managed by the middleware management system for each business process The method of claim 1, wherein the business management unit Business process management system of the RFID middleware, characterized in that it comprises a business identifier storage unit for managing the entire business processes by assigning identification information to each business process. The method of claim 1, wherein the business management unit And the information of the plurality of adapters, filters and report generators is managed in a linked list structure. The method of claim 1, wherein the business management unit And a user interface unit for providing a tool for monitoring, modifying, deleting, and adding the business processes. The method of claim 4, wherein the user interface unit A business list unit displaying a list of the business processes; And And a business information provider for providing adapter, filter, and report generator information used for the selected business when one of the businesses displayed through the business list unit is selected. The method of claim 5, wherein the business information provider Business process management system of the RFID middleware, characterized in that it further comprises a business control unit that can individually modify, delete, and add the adapter, filter and report generator used in the business process. Manage business processes of RFID middleware including an adapter for converting data obtained by an external device including an RFID reader, a filter for filtering the data of the adapter, and a report generator for converting the filtered data to an application system. In the way, a) managing business processes by a middleware management system that controls and manages a plurality of said adapters, filters and report generators; And b) controlling and managing the plurality of adapters, filters, and report generators for each of the business processes. The method of claim 7, wherein The information of the plurality of adapters, filters and report generators are managed in a linked list structure. The method of claim 7, wherein step a) a1) displaying a list of business processes; a2) if a business process is selected from the list of business processes, providing adapter, filter and report generator information used for the business process; And a3) if any one of the adapter, filter, and report generator is selected, providing a menu for modifying, deleting, and adding the selected adapter, filter, and report generator. . A recording medium having recorded thereon a program for executing the business process management method according to any one of claims 7 to 9 on a computer.

Images