KR20100030373A - Method and apparatus for providing rfid/usn integrated middleware - Google Patents

Abstract

PURPOSE: A method and an apparatus for providing RFID/USN(Ubiquitous Sensor Network) integrated middleware are provided to variously associate association methods of RFID and USN by an XML document description following a rule, thereby saving maintenance costs of a system. CONSTITUTION: A device manager(110) receives ubiquitous sensor network event data. A logic device unit generates a common type electronic tag event and a common type ubiquitous sensor network event. An event combination manager(160) generates an integrated event using a mutual association action specification.

Description

RFID / WSN integrated middleware device and method {Method and Apparatus for Providing RFID / USN Integrated Middleware}

The present invention relates to a radio frequency identification (RFID) middleware device and a ubiquitous sensor network (USN) middleware device. In particular, an RFID / USN integrated middleware device and method It is about.

The RFID middleware generally controls the RFID device, extracts information of the tag, and provides information to higher-level applications.

USN middleware analyzes and processes sensing data such as temperature, humidity, and pressure collected from sensor nodes that make up the sensor network and provides information services to users through applications.

FIG. 1 is a block diagram schematically illustrating a configuration of an RFID middleware system based on a general application interface layer (hereinafter, referred to as 'ALE').

As shown in FIG. 1, an ALE-based RFID middleware system includes an RFID event management system 10 and a local reader manager 20.

The RFID event management system 10 includes an ALE RFID event manager 12 and a pipelined RFID event manager 14.

The ALE RFID event manager 12 transmits the tag data collected from the reader to the application program by removing unnecessary tag data, collecting tag data for a predetermined time, filtering tag data, and counting tag data.

Pipeline RFID event manager 14 is composed of a valve (Valve) and a pipeline (Pipeline) to extract the event by the user directly manipulates the valve configuration and the configuration of the pipeline.

The local leader manager 20 manages information on the logical leader in order to collect tag data through the logical reader, and maintains the association between the logical leader and the physical device by creating, changing, and deleting the logical leader information.

2 is a block diagram schematically illustrating a configuration of a general server side based USN middleware system.

As shown in FIG. 2, the server side-based USN middleware system 30 may include a USN application management component 31, a USN application service query management component 32, a context aware management component 33, and sensing information integration management. Component 34, meta information management component 35, and USN gateway management component 36.

USN application management component 31 provides informational sensor events to external application applications.

USN application service query management component 32 supports queries for requesting continuous sensing data and tracking the location of sensor nodes.

The context aware management component 33 analyzes the sensing information to generate new context information.

The sensing information integrated management component 34 performs a function of caching sensing information and storing the sensing information as log data in a database.

The meta information management component 35 stores static meta information such as the name of the sensor network, the type of information sensed, the type of driver, and dynamic meta information such as the number of sensor nodes, the remaining power of the sensor node, and the communication state of the sensor network. Manage.

The USN gateway management component 36 performs physical processing on sensor node equipment through a base station (hereinafter referred to as 'BS') and performs logical sensor mapping setting for the USN environment.

RFID / USN technology in the ubiquitous environment connects RFID or sensors attached to all objects to wireless devices, and manages the profile of individual objects by collecting, processing and utilizing the surrounding environment information in real time through networking and communication with each other.

Therefore, the future integration of RFID middleware and USN middleware is expected to be a key foundation for providing a ubiquitous environment.

The interconnection between the conventional RFID device and the USN device requires a respective middleware and a separate software must be developed according to the interconnection between the RFID device and the USN device.

Therefore, the interconnection between the RFID device and the USN device has a problem in that the system reliability is lowered and the development cost is increased due to the heterogeneous middleware.

Conventional RFID middleware and USN middleware are difficult to interconnect USN sensors because they are difficult to interconnect when RFID devices must be managed in a wireless sensor network (WSN).

Conventional RFID middleware can be seen as a USN device concept of the RFID device, there is a problem that can be duplicated investment when introducing the USN middleware device in the future if only RFID middleware is introduced.

Conventional RFID middleware can be standardized by applying the ALE interface of EPCglobal, but in the case of USN middleware, there is no related standardization protocol.

In order to solve such a problem, the present invention is to provide an RFID / USN integrated middleware device and method for the middleware platform to perform the mutual interworking processing of the RFID / USN equipment in accordance with the user association rules.

RFID / USN integrated middleware device according to the characteristics of the present invention for achieving the technical problem is the ubiquitous sensor network of the base station of the ubiquitous sensor network equipment and the electronic tag event data of the radio frequency identification reader A device manager to receive event data; A logic device unit generating a common type electronic tag event and a common type ubiquitous sensor network event for common use of the received electronic tag event data and ubiquitous sensor network event data in an upper module; An electronic tag event manager configured to filter the generated electronic tag event of the common type according to a pre-stored first operation specification of the electronic tag middleware; A ubiquitous sensor network event manager for filtering the generated ubiquitous sensor network event according to a second operation specification of pre-stored ubiquitous sensor network middleware; An event synthesis manager configured to generate an integrated event using the filtered ubiquitous sensor network event and electronic tag event by using an interconnection operation specification of an electronic tag and a ubiquitous sensor network; And converting the generated integrated event, the filtered ubiquitous sensor network event, and the electronic tag event into standardized report specifications with reference to the cross-linked motion specification, the first motion specification, and the second motion specification, respectively, to an application program. It includes a standardized protocol management unit for transmitting.

RFID / USN integrated middleware method according to an aspect of the present invention is to (a) generating a feedback command for controlling the ubiquitous sensor network base station when the electronic tag event data is received from a radio frequency identification reader step; (b) receiving ubiquitous sensor network event data by reading a sensing value from the ubiquitous sensor network base station using the generated feedback command; And (c) synthesizing the electronic tag event data and the ubiquitous sensor network data by using an interconnection operation specification of the electronic tag and the ubiquitous sensor network defined by a user to generate an integrated event.

RFID / USN integrated middleware method according to an aspect of the present invention is (a) an operation specification in the form of an object instance defined by a user from an application program; the operation specification is a first operation specification of a radio frequency identification middleware, ubiquitous sensor network (Ubiquitous Sensor Network) including a second operating specification of the middleware, a cross-linking operating specification of the electronic tag and the ubiquitous sensor network; (b) Receive the electronic tag event data of the electronic tag reader and the ubiquitous sensor network event data of the base station of the ubiquitous sensor network device to generate common type electronic tag event and common type ubiquitous sensor network event for common use in the upper module. Making; (c) filtering the generated common type electronic tag event using the first operation specification and filtering the generated common type ubiquitous sensor network event using the second operation specification; (d) converting the filtered ubiquitous sensor network event and the electronic tag event into an integrated event using the cross-correlation action specification; And (e) converting the converted integration event into a standardized report specification using the cross-linking operation specification and transmitting the converted integration event to the application program.

By the above-described configuration, the present invention can save the development cost and time of a new linkage program when developing a linkage solution requiring the linkage between RFID and USN.

The present invention can also reduce the system maintenance and repair costs by enabling a variety of linkage by the XML document definition according to the rule and also the linkage method of RFID, USN.

The present invention can be expected to operate as a middleware to which RFID and USN are linked, and also to enable individual functions of RFID middleware or USN middleware.

The present invention integrates the functions of RFID middleware and USN middleware that are commercially available, thereby facilitating mutual interconnection between RFID devices and USN devices.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, without excluding other components unless specifically stated otherwise. In addition, the terms “… unit”, “… unit”, “module”, “block”, etc. described in the specification mean a unit that processes at least one function or operation, which is hardware or software or a combination of hardware and software. It can be implemented as.

The present invention integrates the functions of RFID middleware and USN middleware that are commercially available, and facilitates the mutual linkage between RFID devices and USN devices.

3 is a block diagram schematically illustrating the configuration of an RFID / USN integrated middleware device according to an embodiment of the present invention.

The RFID / USN integrated middleware device 100 according to the embodiment of the present invention includes a device manager 110, a logic device manager 120, an event conversion manager 130, an RFID event manager 140, and a USN event manager 150. , An event synthesis manager 160, a standardized protocol manager 170, and an application manager 180.

The device manager 110 performs the same functions as the general RFID middleware and the USN middleware, and transmits the sensing event data received from the BS of the USN device and the tag event data read from the RFID reader 200 to the logic device manager 120. . Hereinafter, the sensing event data and the tag event data may be used as terms and events covering both data, and may be expressed differently, such as USN event data and RFID event data.

In other words, the device manager 110 transmits the sensing event data received from the BS of the USN device to the logic device manager 120 through the control algorithm defined by the USN manager 130, and reads from the RFID reader 200. The tagged event data is transmitted to the logic device manager 120 through a control algorithm predefined by the RFID manager 120.

The logic device manager 120 functions similar to a general RFID middleware, and processes the event received from the device manager 110 to the event conversion manager 130. In addition, the logic device manager 120 generates and transmits a signal for controlling each of the signals as defined by the operation specifications of the RFID reader 200 and the USN BS 300, and generates a common format event, COM-EVENT. do.

The event conversion manager 130 converts the tag event data and the sensing event data converted to the common type according to the user's request.

In other words, the event conversion management unit 130 converts the RFID event (tag event data) into a USN event (sensing event data) data type and transmits it, or converts the tag event data or sensing event data into another value when the tag event data or sensing event data exists. Send to upper module.

If only the RFID middleware function is required, the RFID event manager 140 filters the event according to the ALE specification to generate a filtered RFID event (R-F-EVENT).

The USN event manager 150 generates a filtered USN event (U-F-EVENT) by filtering the event according to a defined operation specification when only the USN middleware function is required.

The event synthesis manager 160 synthesizes the filtered RFID event received from the RFID event manager 140 and the filtered USN event received from the USN event manager 150 by a user-defined type to generate a new type of event. For example, when a tag number found at a specific temperature and pressure is specified, a tag is found at a specific temperature and pressure, which is a valid event.

The standardization protocol manager 170 generates a reporter according to the standardized report specification and transmits the result event according to the specification defined by the user to the application manager 180.

The application management unit 180 transmits the ECReport, SCReport, MCReport generated in the standard protocol management unit to the application 400, and transmits the external request of the ECSpec, SCSpec, MCSpec type of the application 400 to the standard protocol management unit .

Here, ECSpec is the RFID middleware operation specification as the EPCglobal ALE standard, SCSpec is the USN middleware operation specification, MCSpec is the RFID / USN interworking operation specification, ECReport is the RFID operation result report as the EPCglobal ALE standard, and SCReport is the USN middleware operation MCReport is a result report of RFID / USN interworking operation. The above-described ECSpec, SCSpec and MCSpec are operation specifications defined by the user in Extensible Markup Language (hereinafter referred to as 'XML'), and ECReport, SCReport, and MCReport are XML according to the ECSpec, SCSpec, and MCSpec methods defined by the user. Refers to the standardized report specification generated in the form.

Next, the operation of the device manager 110 will be described in detail with reference to FIG. 4.

4 is a block diagram schematically showing the internal configuration of the device management unit 110 according to an embodiment of the present invention, Figure 4a is an RFID of the RFID management unit 120 of the device management unit 110 according to an embodiment of the present invention. 4B is a diagram schematically illustrating a configuration of the reader control receiver 126. FIG. 4B is a diagram illustrating a configuration of a tag event transmitter 124 of the RFID manager 120 among the device managers 110 according to an exemplary embodiment of the present invention. 4C is a diagram schematically showing the configuration of the BS control receiver 136 of the USN manager 130 of the device manager 110 according to an embodiment of the present invention, and FIG. 4D is an apparatus according to an embodiment of the present invention. The configuration of the sensing event transmitter 134 of the USN manager 130 among the manager 110 is a simplified diagram.

The device manager according to the embodiment of the present invention includes an RFID manager 120 and a USN manager 130.

The RFID manager 120 includes an RFID reader adapter 122, a tag event transmitter 124, and an RFID reader control receiver 126. The USN manager 130 includes a BS device adapter 132 and a sensing event transmitter 134. And a BS control receiver 136.

The tag event data read from the RFID reader 200 is received by the RFID reader adapter 122 regardless of the type of the RFID reader 200 and transmitted to the tag event transmitter 124, and the tag event transmitter 124 receives the tag event. The data is transmitted to the logic device manager 120.

The RFID manager 120 controls the RFID reader adapter 122 by a control signal of the logic device manager 120 to operate the actual RFID reader 200.

The sensing event data received from the BS of the USN device is received by the BS device adapter 132 regardless of the type of the USN BS 300 and transmitted to the sensing event transmitter 134, and the sensing event data is transmitted by the sensing event transmitter 134. To the logical device manager 120.

The USN manager 130 controls the BS device adapter 132 by the control signal of the logic device manager 120 to operate the actual USN BS 300.

The RFID reader control receiver 126 will now be described with reference to FIG. 4A.

The RFID reader control receiver 126 receives a control command from the logic device manager 120, generates a unit command for each RFID reader 200, and pushes the command to the first unit command queue 126a.

Thereafter, the first command execution management process 126b retrieves the unit command from the first unit command queue 126a and calls the RFID reader adapter 122 to control the RFID reader 200. At this time, the first unit command queue 126a exists in the RFID reader 200 one by one.

The RFID reader adapter 122 physically controls the RFID reader 200 regardless of the type of the RFID reader 200 according to the control of the first command execution management process 126b of the RFID reader control receiver 126.

The tag event transmitter 124 will now be described with reference to FIG. 4B.

The tag event transmitter 124 includes a tag event queue 124a and a tag event processing process 124b. The tag event queue 124a calls the RFID reader adapter 122 to queue the tag event data generated in the RFID reader 200.

The tag event processing process 124b polls the tag event data one by one from the tag event queue 124a and transmits the tag event data to the logical device manager 120.

The BS control receiver 136 will now be described with reference to FIG. 4C.

The BS control receiver 136 receives a control command from the logic device manager 120, generates a unit command for each BS, and pushes the command to the second unit command queue 136a.

Thereafter, the second command execution management process 136b retrieves the unit command from the second unit command queue 136a and calls the BS device adapter 132 to control the physical BS. In this case, one second unit command queue 136a exists per BS.

The BS device adapter 132 physically controls the BS regardless of the type of BS according to the control of the second command execution management process 136b of the BS control receiver 136.

The sensing event transmitter 134 will now be described with reference to FIG. 4D.

The sensing event transmitter 134 includes a sensing event queue 134a and a sensing event processing process 134b.

The sensing event queue 134a calls the BS device adapter 132 to queue in the sensing event data generated in the BS.

The sensing event processing process 134b polls the sensing event data one by one in the sensing event queue 134a and transmits it to the logical device manager 120.

5 is a block diagram schematically illustrating an internal configuration of the logic device manager 120 according to an exemplary embodiment of the present invention. 5A is a diagram schematically illustrating a configuration of an RFID reader control scheduling unit 121 of the logic device manager 120 according to an embodiment of the present invention, and FIG. 5B is a logic device manager 120 according to an embodiment of the present invention. FIG. 5C is a diagram schematically showing the configuration of the RFID reader physical-logical mapping unit 122, and FIG. 5C is a diagram schematically showing the configuration of the RFID reader control unit 123 of the logic device manager 120 according to an embodiment of the present invention. 5D is a diagram schematically illustrating a configuration of the USN BS control scheduling unit 124 of the logical device manager 120 according to an embodiment of the present invention, and FIG. 5E is a logic device manager according to an embodiment of the present invention. FIG. 5 is a diagram schematically showing the configuration of the USN BS physical-logical mapping unit 125, and FIG. 5F is a diagram briefly illustrating the configuration of the USN BS control unit 126 of the logic device manager 120 according to an embodiment of the present invention. 5G shows an embodiment of the invention. The configuration of the common type event converter 127 among the logical device manager 120 according to the present invention is briefly illustrated.

According to an embodiment of the present invention, the logic device manager 120 may include an RFID reader control scheduling unit 121, an RFID reader physical-logical mapping unit 122, an RFID reader control unit 123, a USN BS control scheduling unit 124, USN BS physical-logical mapping unit 125, USN BS control unit 126 and common type event conversion unit 127.

The logic device manager 120 processes the tag event data and the sensing event data received from the device manager 110 in the common type event converter 127 to be operated by the event conversion manager 130. (COM-EVENT) is generated and the generated COM-EVENT is transmitted to the event conversion management unit 130.

The logic unit manager 120 receives an operation specification of the ECSpec from the standard protocol manager and interprets the RFID part in the RFID reader control scheduling unit 121, and in the RFID reader control scheduling unit 121, physically accesses the RFID accessor to the RFID reader physical. Request by the logical mapping unit 122 and receive.

The logic device manager 120 transmits a control signal of the RFID reader 200 to the RFID reader control receiver 126 of the device manager 110 through the RFID reader controller 123 using the received physical RFID accessor.

The logical unit manager 120 receives the operation specification of the ECSpec from the standard protocol manager, interprets the USN portion in the USN BS control scheduling unit 124, and uses the USN BS access scheduler in the USN BS control scheduling unit 124. Request to the physical-logical mapping unit 125 to receive.

The logic device manager 120 transmits the control signal of the USN BS 300 to the BS control receiver 136 of the device manager 110 through the USN BS controller 126 using the received physical USN BS accessor.

The RFID reader control scheduling unit 121 will now be described with reference to FIG. 5A.

The RFID reader control scheduling unit 121 according to the embodiment of the present invention includes a first abstract command queue 121a and an RFID scheduling management process 121b.

The first abstract command queue 121a receives an operation specification of the ECSpec analyzed from the standard protocol management unit and accumulates sequentially in the abstract command.

The RFID scheduling management process 121b converts the abstract instruction stored in the first abstract instruction queue 121a into a unit instruction and transmits the converted instruction to the RFID reader controller 123.

The RFID scheduling management process 121b transmits the logical reader number to the RFID reader physical-logical mapping unit 122 and receives a physical leader number corresponding to the logical reader number from the RFID reader physical-logical mapping unit 122. Here, the physical reader number means a physical RFID accessor that can access the above-described RFID reader 200.

The RFID reader physical-logical mapping unit 122 will be described with reference to FIG. 5B.

The RFID reader physical-logical mapping unit 122 according to the embodiment of the present invention includes a first mapping management process 122a and a first mapping map 122b.

The first mapping management process 122a receives the operation specification (including the mapping information) of the ECSpec analyzed by the standard protocol manager to generate the first mapping map 122b.

The first mapping map 122b returns the physical leader number corresponding to the logical leader number requested by the first mapping management process 122a.

The RFID reader controller 123 is described with reference to FIG. 5C as follows.

The RFID reader controller 123 according to the embodiment of the present invention includes a third unit command queue 123a and a reader control process 123b.

The third unit command queue 123a queues the unit command received from the RFID scheduling management process 121b into each RFID reader command queue to control each RFID reader 200.

The reader control process 123b queues up the split unit command to the first unit command queue 126a of the RFID reader control receiver 126 of the RFID manager 120.

The USN BS control scheduling unit 124 is described with reference to FIG. 5D as follows.

The USN BS control scheduling unit 124 according to the embodiment of the present invention includes a second abstract command queue 124a and a USN scheduling management process 124b.

The second abstract command queue 124a receives an operation specification of the SCSpec analyzed from the standard protocol management unit and accumulates the abstract instructions in order.

The USN scheduling management process 124b converts the abstract instructions stored in the second abstract command queue 124a into unit instructions and then transmits them to the USN BS controller 126.

The USN scheduling management process 124b transmits the logical BS number to the USN BS physical-logical mapping unit 125 and receives a physical BS number corresponding to the logical BS number from the USN BS physical-logical mapping unit 125. Here, the physical BS number means a physical USN BS accessor that can access the aforementioned USN BS 300.

Referring to FIG. 5E, the USN BS physical-logical mapping unit 125 is as follows.

The USN BS physical-logical mapping unit 125 according to the embodiment of the present invention includes a second mapping management process 125a and a second mapping map 125b.

The second mapping management process 125a receives the operation specification (including mapping information) of the SCSpec analyzed by the standard protocol manager to generate the second mapping map 125b.

The second mapping map 125b returns the physical BS number corresponding to the logical BS number requested by the second mapping management process 125a.

The USN BS controller 126 will be described with reference to FIG. 5F as follows.

The USN BS control unit 126 according to the embodiment of the present invention includes a fourth unit command queue 126a and a BS control process 126b.

The fourth unit command queue 126a queues the unit command received from the USN scheduling management process 124b into each BS command queue to control each BS.

The BS control process 126b queues up the split unit command to the second unit command queue 136a of the BS control receiver 136 of the USN management unit 130.

The common type event converter 127 will now be described with reference to FIG. 5G.

The common type event transformation unit 127 according to an embodiment of the present invention includes an integrated event queue 127a and a common type event transformation process 127b.

The integrated event queue 127a receives and stores tag event data of the tag event transmitter 124 and sensing event data of the sensing event transmitter 134.

The common type event conversion process 127b extracts the tag event data or the sensing event data from the integrated event queue 127a and converts the tag event data or the sensing event data into a common type for common use in the upper module (common type ubiquitous sensor network event data: COM- U-EVENT, common type electronic tag event data: COM-R-EVENT).

The reason for the common type conversion process is to increase the speed efficiency of the higher process process.

The common type event converter 127 serves to stably supply an event to the event conversion manager 130.

Next, the event conversion manager 130 will be described in detail with reference to FIG. 6.

6 is a block diagram schematically showing the internal configuration of the event conversion management unit 130 according to an embodiment of the present invention.

The event conversion management unit 130 according to an embodiment of the present invention includes an integrated event reception queue 132 and an event conversion process 134.

The integrated event reception queue 132 receives and stores common type tag event data and sensing event data from the common type event converter 127 of the logic device manager 120.

The event conversion process 134 receives the operation specification of the MCSpec analyzed from the standardization protocol management unit 170, converts the event as defined to determine the destination, and then transmits the received event to the RFID event management unit 140 or the USN event management unit 150. do.

The reason for event conversion is not to write specific event value as it is, but to change it by a specific algorithm and transmit it to the upper management module to enable the user's desired processing.

Next, the RFID event manager 140 will be described in detail with reference to FIG. 7.

FIG. 7 is a block diagram schematically illustrating an internal configuration of an RFID event manager 140 according to an embodiment of the present invention, and FIG. 7A illustrates an RFID source event processor of the RFID event manager 140 according to an embodiment of the present invention. FIG. 7B is a diagram schematically illustrating the configuration of FIG. 7B.

The RFID event manager 140 according to an embodiment of the present invention includes an RFID source event processor 142 and an RFID event filter 144.

The RFID event manager 140 receives the converted tag event data from the event conversion manager 130 and filters the event according to the content defined by the user. At this time, the filtering criteria of the RFID event manager 140 conforms to the ALE specification.

The RFID event manager 140 receives the operation specification of the ECSpec analyzed from the standard protocol manager, stores the original event through the RFID source event processor 142, and generates a filtered event through the RFID event filter 144. The protocol manager or the event composition manager 160 transmits the data.

The RFID source event processor 142 will be described with reference to FIG. 7A.

The RFID source event processor 142 according to the embodiment of the present invention includes a first reception buffer 142a and an RFID source event process 142b.

The first reception buffer 142a receives and stores the tag event data COM-R-EVENT of a common type from the event conversion management unit 130.

The RFID source event process 142b receives the operation specification of the ECSpec analyzed by the standard protocol management unit and stores the tag event data of the common type received from the first reception buffer 142a as the content of the analyzed ECSpec as the content of the analyzed ECSpec. Perform the function. Here, the source event refers to an original event on which filtering is not performed.

In addition, the RFID source event process 142b transmits the tag event data of the common type received from the first reception buffer 142a to the RFID event filtering unit 144.

The RFID event filtering unit 144 will now be described with reference to FIG. 7B.

The RFID event filtering unit 144 according to the embodiment of the present invention includes an RFID event filtering process 144a and a plurality of temporary buffers 144b and 144c.

The RFID event filtering process 144a filters the tag event data of the common type received from the RFID source event processor 142 according to the contents of the analyzed ECSpec and transmits the filtered tag event data to the temporary buffer 1 144b.

If the RFID event filtering process 144a continues to have a filtering specification, the RFID event filtering process 144a refilters the filtered tag event data of the temporary buffer 1 144b and transmits the filtered tag event data to the temporary buffer 2 144c.

In this way, a large number of temporary buffers may exist and filtering may be performed several times.

Next, the USN event manager 150 will be described in detail with reference to FIG. 8.

8 is a block diagram schematically showing the internal configuration of the USN event management unit 150 according to an embodiment of the present invention, Figure 8a is a USN source event processing unit of the USN event management unit 150 according to an embodiment of the present invention ( FIG. 8B is a diagram schematically showing the configuration of FIG. 8B, and FIG. 8B is a diagram schematically illustrating the configuration of the USN event filtering unit 154 of the USN event management unit 150 according to the embodiment of the present invention.

The USN event manager 150 according to an embodiment of the present invention includes a USN source event processor 152 and a USN event filter 154.

The USN event manager 150 receives the converted sensing event data from the event conversion manager 130 and filters the event according to the user's definition. At this time, the filtering criteria of the USN event manager 150 is based on its own definition.

Referring to FIG. 8A, the USN source event processor 152 is as follows.

The USN source event processing unit 152 according to the embodiment of the present invention includes a second receive buffer and a USN source event processing process 152b.

The second reception buffer 152a receives and stores the common type sensing event data (COM-U-EVENT) from the event conversion management unit 130.

The USN source event processing process 152b receives the operation specification of the SCSpec analyzed by the standard protocol management unit and stores the sensing event data of the common type received from the second reception buffer as the content of the analyzed SCSpec as the content of the analyzed SCSpec. do.

In addition, the USN source event processing process 152b transmits the common type of sensing event data received from the second reception buffer to the USN event filtering unit 154.

Referring to FIG. 8B, the USN event filtering unit 154 will be described below.

The USN event filtering unit 154 according to an embodiment of the present invention includes a USN event filtering process 154a and a plurality of temporary buffers 154b and 154c.

The USN event filtering process 154a filters the common type of sensing event data received from the USN source event processor 152 according to the contents of the analyzed SCSpec and transmits the filtered sensing event data to the temporary buffer 1 154b.

If the USN event filtering process 154a continues to have a filtering specification, the USN event filtering process 154a filters the filtered sensing event data of the temporary buffer 1 154b again and transmits the filtered sensing event data to the temporary buffer 2 154c.

In this way, a large number of temporary buffers may exist and filtering may be performed several times.

Next, the event synthesis management unit 160 will be described in detail with reference to FIG. 9.

9 is a block diagram schematically illustrating an internal configuration of the event synthesis management unit 160 according to an embodiment of the present invention.

The event synthesis manager 160 according to an embodiment of the present invention includes an R-F-EVENT receiver 162, a U-F-EVENT receiver 164, an event synthesizer 166, and a synthesized event filter 168.

The event synthesis management unit 160 receives the operation specification of the MCSpec analyzed from the standard protocol management unit, and through the filtered RFID event (RF-EVENT) and the UF-EVENT receiver 164 received through the RF-EVENT receiver 162. The filtered USN event (RU-EVENT) is synthesized through the event synthesis unit 166 according to the operation specification of the MCSpec.

The event synthesis manager 160 re-optimizes the synthesized event to generate an optimized event (M-EVENT) and transmits it to the standard protocol manager.

The R-F-EVENT receiver 162 is a buffer for temporarily storing the filtered RFID event.

The U-F-EVENT receiver 164 is a buffer for temporarily storing the filtered USN event.

The event synthesizer 166 receives the filtered RF-EVENT from the RF-EVENT receiver 162 and the filtered UF-EVENT from the UF-EVENT receiver 164 to perform synthesis according to the operation specification of the analyzed MCSpec. Send the event (M-EVENT) to the upper module.

The event synthesizing unit 166 may control the RFID reader 200 and the BS by forming a new command for interlinking the RFID event or the USN event and feeding it back to the logic device manager 120.

For example, if the vehicle speed is detected in a specific space and the speed exceeds 20 km, the RFID reader 200 is operated to check the tag attached to the vehicle and transmit the speed and the tag number to the upper module through the composite event. Assume

When an event indicating that the speed of the vehicle is 20 km, the event synthesizing unit 166 transmits a feedback command to the logic device manager 120 requesting to read the RFID immediately. Subsequently, when the tag value is read by the RFID reader 200, an RFID event and a USN event are generated.

When the filtered RFID event and the USN event arrive, the event synthesizing unit 166 synthesizes two events indicating a speed and a vehicle tag number and transmits the two events to a higher module.

According to the embodiment of the present invention, when an algorithm for an object identified in a specific situation or condition can be applied and a function that satisfies a specific condition is required in a specific situation, the user defines using XML rather than developing a separate software. Integrated middleware functionality is possible. Therefore, the embodiment of the present invention is characterized in that it can reflect any synthesis rule defined by the user. At this time, the synthesis rule should be newly defined and upgraded to MCSpec.

In addition to sensing values, USN can incorporate location-based business logic, and RFID can also calculate location and time. Therefore, when the location and time zone of RFID and USN are analyzed, the two events occurred at the same time at the same place, so they can be defined and combined as related events.

Next, the standardization protocol manager 170 will be described in detail with reference to FIG. 10.

10 is a block diagram schematically showing the internal configuration of the standardization protocol management unit 170 according to an embodiment of the present invention.

Standardization protocol management unit 170 according to an embodiment of the present invention is RF-EVENT receiver 171, UF-EVENT receiver 172, M-EVENT receiver 173, ECSpec transmitter 174, SCSpec transmitter 175, The MCSpec transmitter 176, the ALE specification generation analyzer 177, the USN standard specification generation analyzer 178, and the synthesis event specification generation analyzer 179 are included.

The standardization protocol manager 170 generates an reporter in XML format according to a user-defined specification of an event of an object instance type received from the RFID event manager 140, the USN event manager 150, and the event synthesis manager 160, and then generates an application program. Send to the management unit 180.

At this time, the RFID event generates the ECReport by referring to the ECSpec, and the USN event generates the SCReport by referring to the SCSpec. The synthesized event generates MCReport by referring to MCSpec.

ECSpec and ECReport conform to EPCglobal's ALE Spec, while SCSpec, SCReport, MCSpec, and MCReport conform to their own defined specifications.

The R-F-EVENT receiver 171 is a buffer in which the filtered RFID event is temporarily stored.

The U-F-EVENT receiver 172 is a buffer in which the filtered USN event is temporarily stored.

The M-EVENT receiver 173 is a buffer in which the synthesized event is temporarily stored.

The ECSpec transmitter 174 is reorganized into instructions that can be analyzed and processed in each module, provided to the relevant module.

SCSpec transmitter 175 is provided to the relevant module is reorganized into instructions that can be analyzed in each module SCSpec is processed.

The MCSpec transmitter 176 is provided to the related module by reorganizing the MCSpec is analyzed into instructions that can be processed in each module.

As shown in FIG. 10A, the ALE specification generation interpreter 177 analyzes the spec temporary buffer 177a for storing ECSpecs received from the application manager 180 and the specs stored in the spec temporary buffer 177a. Receive the filtered RFID event (RF-EVENT) received from the parsing process 177b, the command batch process 177c for transmitting the analyzed specification from the parsing process 177b to the corresponding module, and the USN event manager 150; The ECReport generation unit 177d generates an ECReport and transmits the generated ECReport to the application manager 180.

The USN standard specification generation analyzer 178 functions on the same principle as the ALE specification generation analysis unit, and is subject to SCSpec and SCReport.

Synthetic event specification generation analysis unit 179 functions on the same principle as the ALE specification generation analysis unit, and is subject to MCSpec and MCReport.

Next, the application manager 180 will be described in detail with reference to FIG. 11.

11 is a block diagram schematically illustrating an internal configuration of the application manager 180 according to an exemplary embodiment of the present invention.

Application program management unit 180 according to an embodiment of the present invention is a socket transceiver 181, a web service unit 182, a file generation unit 183, a database storage unit 184, a StanAlone mode management unit ( 185 and a system authentication management unit 186.

The socket transceiver 181 transmits / receives an XML string for the specification through each specification (ECSpec, ECReport, SCSpec, SCReport, MCSpec, MCReport) through a TCP / IP based socket.

The web service unit 182 provides each specification in the form of a simple object access protocol (SOAP) based web service and transmits and receives an XML string for the specification as a parameter.

The file generator 183 stores each report (ECReport, SCReport, MCReport) in the file system when the middleware is operated independently without interworking with the application program 400.

The database storage unit 184 stores each report (ECReport, SCReport, MCReport) in the database when the middleware is operated independently without interworking with the application program 400.

The standalone mode manager 185 operates the middleware according to operating specifications (ECSpec, SCSpec, MCSpec) stored in the middleware when the middleware is operated independently without interworking with the application program 400.

The system authentication manager 186 manages authentication for access when the application 400 attempts to access the middleware.

The RFID / USN integrated middleware device 100 according to the embodiment of the present invention is provided as a middleware frame where RFID and USN are required to be connected, and it is possible to save cost and time due to the development of a new linkage program when developing a linkage solution.

The RFID / USN integrated middleware device 100 may reduce system maintenance and repair costs by enabling various linkages based on XML document definition according to a rule for linkage between RFID and USN.

The RFID / USN integrated middleware device 100 may operate as middleware anywhere where RFID and USN are linked, and in particular, individual functions of RFID or USN middleware may be possible.

Next, an operation of the RFID / USN integrated middleware device 100 according to the embodiment of the present invention will be described with reference to FIG. 12.

12 is a view for explaining the operation of the RFID / USN integrated middleware device 100 according to an embodiment of the present invention.

For example, suppose you want to develop a speeding system for a specific area. The speed regulation system can be regarded as a basic element such as a USN speed sensor for detecting vehicle speed and an RFID tag for identifying a vehicle speeding.

It is assumed that the speed enforcement system obtains a tag number of a vehicle that runs more than 20 km in a certain section.

First, the application program 400 sends the MCSpec, SCSpec, ECSpec through the socket communication to the application management unit 180.

The standardization protocol manager 170 receives the MCSpec, SCSpec, and ECSpec from the application manager 180 to form each of the management modules (logical device manager 120, event conversion manager 130, and RFID event manager) in the form of the required object instance. 140), the USN event manager 150, and the event synthesis manager 160.

As shown in FIG. 12, the event delivery process received by the RFID / USN integrated middleware device 100 when the vehicle is speeding is as follows.

The USN speed event received from the BS of the USN equipment is received by the logical device manager 120 through the device manager 110 to generate a common type of USN speed event (S100a), and the event conversion manager 130 sets the MCSpec. On the basis, the common type USN rate event is converted (S102a), and the common type USN rate event converted by the USN event manager 150 is filtered (S104a).

The RFID event received from the RFID reader 200 is received by the logic device manager 120 through the device manager 110 to generate a common type of RFID event (S100b), and the event conversion manager 130 based on the MCSpec. The common type RFID event is converted (S102b), and the USN event manager 150 filters the common type RFID event (S104b). In this case, the USN event manager 150 and the RFID event manager 140 transmit only the event when the vehicle speed is 20 km or more to the event synthesis manager 160.

The filtered RFID event and the USN rate event are synthesized using the MCSpec in the event synthesis management unit 160 to generate an integrated event (S106).

In other words, the event synthesis manager 160 synthesizes the filtered RFID event and the USN speed event by analyzing the time and place where the event occurs, and includes the identification ID (RFID event) and the speed information (USN event) of the speeding vehicle. You have a composite event.

The composite event is converted into a corresponding standardized report specification in the standardization protocol manager 170 and transmitted to the application program 400 through the application manager 180 (S108). Here, the composite event indicates that a specific vehicle is speeding at a specific location.

The synthesis method of the RFID event and the USN rate event may vary according to a user's definition and may be defined and extended in various ways.

The embodiments of the present invention described above are not implemented only by the apparatus and / or method, but may be implemented through a program for realizing a function corresponding to the configuration of the embodiments of the present invention, a recording medium on which the program is recorded, and the like. Such implementations may be readily implemented by those skilled in the art from the description of the above-described embodiments.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1 is a block diagram schematically illustrating a configuration of a general ALE based RFID middleware system.

2 is a block diagram schematically illustrating a configuration of a general server side based USN middleware system.

3 is a block diagram schematically illustrating the configuration of an RFID / USN integrated middleware device according to an embodiment of the present invention.

4 is a block diagram schematically illustrating an internal configuration of a device manager according to an exemplary embodiment of the present invention.

4A is a diagram schematically illustrating a configuration of an RFID reader control receiver of an RFID manager of a device manager according to an exemplary embodiment of the present invention.

4B is a diagram schematically illustrating a configuration of a tag event transmitter of an RFID manager of an apparatus manager according to an exemplary embodiment of the present invention.

4C is a diagram schematically illustrating a configuration of a BS control receiver of a USN manager of a device manager according to an exemplary embodiment of the present invention.

4D is a diagram schematically illustrating a configuration of a sensing event transmitter of a USN manager of a device manager according to an exemplary embodiment of the present invention.

5 is a block diagram schematically illustrating an internal configuration of a logic device manager according to an exemplary embodiment of the present invention.

FIG. 5A is a diagram schematically illustrating a configuration of an RFID reader control scheduling unit of a logic device manager according to an exemplary embodiment of the present invention.

FIG. 5B is a diagram schematically illustrating a configuration of an RFID reader physical-logical mapping unit in a logic device manager according to an exemplary embodiment of the present invention.

5C is a diagram schematically illustrating a configuration of an RFID reader controller in a logic device manager according to an exemplary embodiment of the present invention.

FIG. 5D is a diagram schematically illustrating a configuration of a USN BS control scheduling unit in a logic device manager according to an exemplary embodiment of the present invention.

FIG. 5E is a diagram schematically illustrating a configuration of a USN BS physical-logical mapping unit in a logic device manager according to an exemplary embodiment of the present invention.

FIG. 5F is a diagram briefly illustrating a configuration of a USN BS controller in a logic device manager according to an exemplary embodiment of the present invention.

FIG. 5G is a diagram schematically illustrating a configuration of a common type event conversion unit among logic device managers according to an exemplary embodiment of the present invention.

6 is a block diagram schematically illustrating an internal configuration of an event conversion management unit according to an embodiment of the present invention.

7 is a block diagram schematically showing the internal configuration of the RFID event management unit according to the embodiment of the present invention.

7A is a diagram schematically illustrating a configuration of an RFID source event processor of an RFID event manager according to an exemplary embodiment of the present invention.

FIG. 7B is a diagram briefly illustrating a configuration of an RFID event filtering unit of an RFID event management unit according to an exemplary embodiment of the present invention.

8 is a block diagram schematically illustrating an internal configuration of a USN event management unit according to an embodiment of the present invention.

8A is a diagram schematically illustrating a configuration of a USN original event processing unit among USN event management units according to an embodiment of the present invention.

8B is a diagram schematically illustrating a configuration of a USN event filtering unit in the USN event management unit according to an embodiment of the present invention.

9 is a block diagram schematically illustrating an internal configuration of an event synthesis management unit according to an embodiment of the present invention.

10 is a block diagram schematically showing the internal configuration of the standardization protocol management unit according to the embodiment of the present invention.

10A is a diagram briefly illustrating a configuration of an ALE specification generation analyzer of a standardized protocol manager according to an exemplary embodiment of the present invention.

11 is a block diagram schematically illustrating an internal configuration of an application program management unit according to an exemplary embodiment of the present invention.

12 is a view for explaining the operation of the RFID / USN integrated middleware device according to an embodiment of the present invention.

Claims (17)

A device manager configured to receive electronic tag event data of a radio frequency IDentification reader and ubiquitous sensor network event data of a base station of a ubiquitous sensor network device; A logic device unit generating a common type electronic tag event and a common type ubiquitous sensor network event for common use of the received electronic tag event data and ubiquitous sensor network event data in an upper module; An electronic tag event manager configured to filter the generated electronic tag event of the common type according to a pre-stored first operation specification of the electronic tag middleware; A ubiquitous sensor network event manager for filtering the generated ubiquitous sensor network event according to a second operation specification of pre-stored ubiquitous sensor network middleware; An event synthesis manager configured to generate an integrated event using the filtered ubiquitous sensor network event and electronic tag event by using an interconnection operation specification of an electronic tag and a ubiquitous sensor network; And The generated integrated event, the filtered ubiquitous sensor network event, and the electronic tag event are converted into standardized report specifications with reference to the cross-linked motion specification, the first motion specification, and the second motion specification, respectively, and transmitted to an application program. Standardized protocol management unit RFID / USN integrated middleware device comprising a. According to claim 1, An event conversion management unit converting the generated common type electronic tag event and the common type ubiquitous sensor network event to meet the user's requirements using the cross-linking operation specification RFID / USN integrated middleware device further comprising. The method of claim 2, And the event conversion management unit converts the generated common type electronic tag event into the generated common type ubiquitous sensor network and processes the RFID / USN integrated middleware device. The method of claim 2, And the event conversion management unit converts the generated common type electronic tag event and the common type ubiquitous sensor network event into a different value to process the RFID / USN integrated middleware device. The method of claim 2, The event conversion management unit extends the specification system of the electronic tag middleware to the specification applying to the ubiquitous sensor network middleware, and the event synthesis management unit applies the specification system of the electronic tag middleware to the integrated middleware of the electronic tag and the ubiquitous sensor network. RFID / USN integrated middleware device, characterized in that extending to. The method according to claim 1 or 2, The event synthesis management unit controls a base station of the electronic tag reader and the ubiquitous sensor network equipment by feeding back a control command for interlinking the electronic tag event data and the ubiquitous sensor network event data to the logic device manager. RFID / USN integrated middleware device, characterized in that. The method according to claim 1 or 2, And the cross-link operation specification, the first operation specification, and the second operation specification are operation specifications defined by the user in an extensible markup language. The method according to claim 1 or 2, The device manager, An electronic tag manager configured to control the electronic tag reader based on a first control signal of the logical device manager to receive the electronic tag event data from the electronic tag reader and transmit the received electronic tag event data to the logical device manager; And The ubiquitous sensor network management unit controls the base station of the ubiquitous sensor network equipment by the second control signal of the logic device manager to receive the ubiquitous sensor network event data from the base station and transmits the ubiquitous sensor network event data to the logic device manager. RFID / USN integrated middleware device comprising a. The method according to claim 1 or 2, The logic device management unit, An electronic tag control scheduling unit configured to receive the first operation specification including a logical reader number from the standard protocol manager, analyze an electronic tag portion, and request and receive an electronic tag accessor that maps to the logical reader number; An electronic tag controller which controls the device manager by using the electronic tag accessor; Ubiquitous sensor network control to receive the second operation specification including the logical base station number from the standard protocol management unit, to analyze the ubiquitous sensor network portion, and to request and receive a ubiquitous sensor network base station accessor that maps to the logical base station number. A scheduling unit; A ubiquitous sensor network controller for controlling the device manager by using the ubiquitous sensor network base station accessor; And Receives the electronic tag event data from the electronic tag reader and converts the electronic tag event data into the common type electronic tag event, and receives the ubiquitous sensor network event data from the base station of the ubiquitous sensor network device to convert the common tag to the common type ubiquitous sensor network event data. Common type event converter to convert RFID / USN integrated middleware device comprising a. The method according to claim 1 or 2, The electronic tag event management unit An electronic tag source event processor configured to store the common type electronic tag event using the first operation specification for a source event; And Electronic tag event filtering unit for filtering the common type electronic tag event using the first operation specification RFID / USN integrated middleware device comprising a. The method according to claim 1 or 2, The ubiquitous sensor network management unit A ubiquitous sensor network source event processor configured to store the common type ubiquitous sensor network event for a source event using the second operation specification; And Ubiquitous sensor network event filtering unit for filtering the common type ubiquitous sensor network event using the second operation specification RFID / USN integrated middleware device comprising a. (a) generating a feedback command to control ubiquitous sensor network base station when the electronic tag event data is received from a radio frequency identification reader; (b) receiving ubiquitous sensor network event data by reading a sensing value from the ubiquitous sensor network base station using the generated feedback command; And (c) generating an integrated event by synthesizing the electronic tag event data and the ubiquitous sensor network data by using an interconnection operation specification of the electronic tag and the ubiquitous sensor network defined by a user definition; RFID / USN integrated middleware method comprising a. The method of claim 12, After step (c), Converting the generated integrated event into a standardized report specification using the cross-linking operation specification and transmitting the same; RFID / USN integrated middleware method further comprising. The method according to claim 12 or 13, The cross-link operation specification is an operation specification defined by the user in Extensible Markup Language. (a) Operation specification in the form of an object instance defined by a user from an application program—The operation specification includes a first operation specification of a radio frequency identification middleware, a second operation specification of a ubiquitous sensor network middleware, and an electronic device. Receiving a tag and a reciprocal association specification of the ubiquitous sensor network; (b) Receive the electronic tag event data of the electronic tag reader and the ubiquitous sensor network event data of the base station of the ubiquitous sensor network device to generate common type electronic tag event and common type ubiquitous sensor network event for common use in the upper module. Making; (c) filtering the generated common type electronic tag event using the first operation specification and filtering the generated common type ubiquitous sensor network event using the second operation specification; (d) converting the filtered ubiquitous sensor network event and the electronic tag event into an integrated event using the cross-correlation action specification; And (e) converting the converted integration event into a standardized report specification using the cross-correlation action specification and transmitting the converted event to the application program; RFID / USN integrated middleware method comprising a. The method of claim 15, After step (e), Generating and feeding back a control command for performing cross-correlation between the electronic tag event data and the ubiquitous sensor network event data to control a base station of the electronic tag reader and the ubiquitous sensor network equipment; RFID / USN integrated middleware method further comprising. The method according to claim 15 or 16, And the cross-link operation specification, the first operation specification, and the second operation specification are operation specifications defined by the user in Extensible Markup Language.

Images