KR100635290B1 - Method to supply multi-code directory service for the global rfid network - Google Patents

Abstract

The present invention relates to a service providing method for finding a URL address for storing information on a tagged object in an RFID network structure. The tag ID code is mapped and managed in a hierarchical tree structure, but the reader is attached to the object. Reading the tag ID code and transmitting it to a local server; The local server transmitting the received tag ID code to an MDS resolver; Checking, by the MDS resolver, a method of applying a received tag ID code and processing the received tag ID code; The MDS resolver converting a tag ID code into a URI form; The MDS resolver converting the tag ID code in the converted URI into a domain name; The MDS resolver transmitting a tag ID code in the form of a converted domain name to an MDS server; Extracting, by the MDS server, NAPTR data corresponding to a received tag ID code in the form of a domain name; The MDS transmitting the extracted NAPTR data to an MDS resolver; The MDS resolver converting the received NAPTR data into a URI form; Extracting, by the MDS resolver, a URL address of a corresponding information server through NAPTR data of a converted URI type; And transmitting the extracted URL address of the information server to the local server.

Global Environment, RFID, Multiple Code, Directory Service, Tags, URIs, URLs, NAPTR

Description

Multi-Code Directory Service Method for RFID Networks in Global Environments             

1 is a conceptual diagram of a general RFID network,

2 is a flowchart illustrating a directory service method through a general RFID network;

3 is a structural example of an EPC code,

4 is a structural example of an ISO / IEC code,

5 is an example of a ucode structure;

6 is a conceptual diagram of an RFID network to which an MDS resolver and an MDS server are applied to implement the invention;

7 is a flowchart illustrating a multiple code directory service method according to the present invention;

8 is an example mapping structure of a tag ID code according to the present invention;

9 is a priority filter algorithm according to the present invention,

10 is a conceptual diagram of an RFID network based on DNS according to the present invention;

11 is a flowchart illustrating a multi-code directory service method based on DNS according to the present invention.

* Explanation of symbols for main parts of the drawings

110: tag 120: reader

130: local server 140: DS server

150: information server 610: tags

620: Reader 630: Local Server

640: MDS Resolver 650: MDS Server

660: Information Server 1010: Tags

1020: Reader 1030: Local Server

1040: MDS Resolver 1050: Cache

1060: Root DNS 1070: Authoritative DNS

1080: Information Server

The present invention relates to an RFID network in a global environment, and in particular, a global environment capable of providing URL information for storing information on an object using a tag code regardless of a tag code policy that is individually assigned to and used for a physical object. A multi-code directory service method for an RFID network of the present invention.

Ubiquitous refers to an information and communication environment in which a user can freely access a network regardless of a location without being aware of a network or a computer. For ubiquity, Radio Frequency Identification (RFID) systems will operate on a wide range of networks, such as the World Wide Web.

RFID is a technology that aims to recognize a physical object and find out information about the object. The identification code assigned to each object is called a tag code and is encoded in an RFID tag. These codes are the basis for using information services for objects.

1 is a conceptual diagram of a general RFID network, and includes a tag 110, a reader 120, a local server 130, a directory service server 140, an information server 150, and the like. 2 is a flowchart illustrating a directory service method through a general RFID network.

Referring to FIG. 2, when the tag 110 attached to an object is located within the recognition range, the reader 120 reads the tag 110 and transmits the read tag ID code to the local server 130 (S210 and S212). .

Subsequently, when the local server 130 transmits the tag ID code to the directory service server (DS server) 140, the DS server 140 searches for one or more URL addresses that store information about the object, and then local The server 130 transmits the data to the server 130 (S214 and S216). Finally, the local server 130 accesses the information server 150 corresponding to the URL address (S218).

On the other hand, the tag ID code attached to the object has been developed by various standardization organizations such as EPCglobal, ISO / IEC, and Japanese ubiquitous center, and various forms coexist.

The code of EPCglobal consists of a fixed length header followed by consecutive numbers as shown in FIG. The structure of this EPC code and its role are determined by the header value.

The next field in the header identifies the administrator for the EPC code with the Domain Manager (DM). Therefore, this field is assigned to the organization or company managing the Object Class (OC) and Serial Number (SN). An OC represents a group or class of individuals and the agency of the DM assigns the number of the OC so that the OC number under the DM number is unique.

In addition, the agency of the DM number assigns the SN number so that the final general EPC code under the OC number has a unique number. 11 encoding schemes are defined in Table 1 below.

The tag ID code defined in ISO / IEC is as shown in FIG. 4. The first field is Allocation Class (AC), which is used to identify the registration authority for the tag ID issuer number. ID issuer registration number and serial number have size dependent on AC value.

The size of AC is 8 bits and the five classes are defined in the following table.

The second field, ID issuer registration number, is assigned by the registration authority, and the serial number is assigned by the ID issuer to manage the uniqueness of the tag ID code.

ucode (ubiquitous code) is a tag ID code structure restricted by the Japanese Ubiquitous ID center. It has a 128 bit size and can be extended to 256-bit, 384 or 512 bits in 128-bit units as necessary. ucode can contain existing identification codes, which can accept Japanese Article Number (JAN), Universal Product Code (UPC) barcodes, ISBNs and ISSN publication IDs.

5 shows an embodiment of a ucode structure using JAN. As shown in FIG. 5, the first 12 bits are used as code identifiers. Here, the code identifier indicates that the tag ID code is a JAN code. The second 52 bits contain the JAN code value. The JAN code identifies the type of product. The last unique ID field is 64 bits used to assign a unique number to each product.

However, as described above, since various tag ID code policies are under development, it may take a long time to establish a tag ID code structure of a single standard system globally, and may evolve as various types of tag ID code structures coexist. There will be.

Therefore, in a global RFID network, a service that provides the same service value for various types of code policies will be needed, rather than providing a service limited to any one code policy.

Accordingly, the present invention has been devised to meet the above necessity, and can provide URL information for storing information on an object using a tag code regardless of a tag code policy that is individually assigned to and used for a physical object. An object of the present invention is to provide a multi-code directory service method for an RFID network in a global environment.

In order to achieve the above object, information about an object to which a tag is attached regardless of a tag ID code type through a multi-code directory service (MDS) resolver and an MDS server in a radio frequency identification (RFID) network structure according to the present invention. A method of providing a service for finding a URL address storing a tag includes: managing a tag ID code mapped to a hierarchical tree structure, the reader reading a tag attached to an object; The reader sending the read tag ID code to a local server; The local server transmitting the received tag ID code to an MDS resolver; Checking, by the MDS resolver, a method of applying a received tag ID code and processing the received tag ID code; Converting the tag ID code into a Uniform Resource Identifier (URI) after processing by the MDS resolver; The MDS resolver converting the tag ID code in the converted URI into a domain name; The MDS resolver transmitting a tag ID code in the form of a converted domain name to an MDS server; Extracting, by the MDS server, Naming Authority Pointer (NAPTR) data corresponding to a tag ID code in the form of a received domain name; The MDS transmitting the extracted NAPTR data to an MDS resolver; The MDS resolver converting the received NAPTR data into a URI form; Extracting, by the MDS resolver, a Uniform Resource Locator (URL) address of a corresponding information server through NAPTR data of a converted URI type; And transmitting the extracted URL address of the information server to the local server.

At this time, the MDS resolver checks and processes the tag ID code granting method according to the priority of the frequency for the tag ID code granting method using the recognition algorithm, and the process recognizes the tag ID code. Checking whether a header value is present; Checking whether the code length is 64 bits or 96 bits if the EPC header value; If the code length is 64 bits or 96 bits, processing the EPC process; If it is not an EPC header value or the code length is not 64 bits or 96 bits, confirming whether an ISO AC (Allocation Class) value; An ISO process process if it is an ISO AC value; Checking whether the ucode code identifier is an ISO AC value; checking if the code length is 128 bits if the ucode code identifier; Processing the ucode process if the code length is 128 bits; And if it is not a ucode code identifier, or if the code length is not 128 bits, it is preferable to include the step of checking the process according to the code.

Meanwhile, according to the present invention, an IP address that stores information on a tagged object regardless of a tag ID code type through a reader, a local server, an MDS resolver, a cache, a root DNS, and an authoritative DNS in an RFID network structure. The method of providing a service for searching for the tag ID code is mapped and managed in a hierarchical tree structure, wherein the reader reads a tag attached to the object; The reader sending the read tag ID code to a local server; The local server transmitting the received tag ID code to an MDS resolver; The MDS resolver searches for the cache, and if the IP address of the mapped information server exists for the received tag ID code, transmits the IP address of the information server to the local server, and receives the IP address of the mapped information server if it does not exist. Querying the Root DNS for an IP address for the tagged tag ID code; The root DNS transmitting an address of an established authoritative DNS to an MDS resolver; The MDS resolver querying an Authoritative DNS for an IP address for a received tag ID code; The Authoritative DNS transmitting the retrieved IP address to the MDS resolver; The MDS resolver sending the received IP address to a local server; And accessing an information server having information of a tag ID by using the obtained IP address.

Hereinafter, with reference to the accompanying drawings will be described in detail the present invention.

First, according to the present invention, as a precondition for providing a multi-code directory service (MDS) for an RFID network in a global environment, the number of physical objects is much larger than the number of hosts existing on the Internet. Therefore, it is necessary to satisfy the following points.

First, MDSs must efficiently store information about things. This means that the mapping information between the tag ID and the information server has a tree structure as in DNS, so that the mapping information can be accessed efficiently.

Second, MDSs must be able to accept more requests than DNS. Therefore, the MDS needs to be able to cache mapping information as it does in DNS, and an efficient caching mechanism is needed to give the MDS only a reasonable amount of overhead.

Third, MDSs must be as reliable as DNS. In addition, the same mapping information should be stored in additional information servers such as DNS. For example, if one information server becomes inoperable, the MDS should be available through another server with the same information.

Fourth, the MDS must be able to handle any tag ID assignment method. The purpose of the MDS is to provide transparency for different tag ID assignment methods. Therefore, the MDS must be adaptable to the new tag ID assignment method. This means that MDS should provide the same directory service without modifying the system even if a completely new form of tag ID is introduced.

Finally, MDS must be able to run on the existing Internet infrastructure. In the evolving RFID network, the RFID network is expected to coexist with the Internet.

6 is a conceptual diagram of an RFID network to which an MDS resolver and an MDS server are applied to implement the present invention. The tag 610, the reader 620, the local server 630, the MDS resolver 640, the MDS server 650, and information are illustrated. Server 660. 7 is a flowchart illustrating a multi-code directory service method according to the present invention, in which a tag 610 is attached to the RFID network structure regardless of the tag ID code type through the MDS resolver 640 and the MDS server 650. Indicates the provision of a service to find one or more URL addresses that store information about an object.

First, referring to FIG. 8, the mapping structure of the tag ID code according to the present invention shows a hierarchical tree structure in which the MDS can efficiently store information about objects. These tag ID codes are mapped and managed in a hierarchical tree structure. The MDS root (mdsroot.org) is the top level domain name of the public tag ID namespace. This tree structure is similar to that of ENUM.

As a result, all global lookup processes begin with the MDS root, which is used to reduce the number of times MDS local caches are queried on the root. When the MDS resolver 640 receives one tag ID, the MDS resolver 640 checks the tag ID assignment method and searches the MDS root tree according to the result value. If a new standard for tag ID is created or the current standard is changed, a new node is added.

6 and 7, the multi-code directory service method according to the present invention will be described. First, the reader 620 reads the tag 610 attached to an object, and then reads the read tag ID code in the local server 630. In step S710 and S712. Then, the local server 630 transmits the received tag ID code to the MDS resolver 640 (S714).

Subsequently, the MDS resolver 640 checks the directory service, that is, the method of granting the received tag ID code, and processes the identified code with respect to the received tag ID code, and then processes the tag ID code into a suitable URI (Uniform Resource). Identifier) (S716, S718).

Subsequently, the MDS resolver 640 converts the tag ID code of the converted URI into a domain name, and then transmits the tag ID code of the converted domain name to the MDS server 650 (S720 and S722). The reason for the conversion to domain name format is to use DNS technology.

Subsequently, the MDS server 650 extracts NAPTR (Naming Authority Pointer) data corresponding to the received tag ID code in the form of a domain name and transmits the data to the MDS resolver 640 (S724 and S726). In other words, it performs a lookup service. The NAPTR data contains the Uniform Resource Locator (URL) address of the information server that holds the tag ID code.

Subsequently, the MDS resolver 640 converts the received NAPTR data into a URI form and extracts the URL address of the corresponding information server through the converted NAPTR data in the URI form (S728 and S730).

Finally, when the MDS resolver 640 transmits the extracted URL address of the information server to the local server 630, the local server 640 accesses the corresponding information server 660 (S732, S734).

However, when the MDS resolver 640 receives a bit sequence of one tag ID, it is necessary to first identify which tag ID granting method takes precedence over another in processing the global lookup service.

The EPC (Electric Product Code) and the ISO / IEC tag ID assignment scheme have an 8-bit header item. In both of these standards, header entries refer to the encryption scheme used by those standards. Therefore, when EPC or ISO / IEC code is used, there is no need to go through the entire tag code checking process. Therefore, the MDS only needs to check the first 8 bits to distinguish the codes of EPC and ISO / IEC.

However, in the case of ucode, the length of the previous two code methods is 68 bits, but it is 128 bits. Therefore, it is expected that this problem can be solved by analyzing the total length by distinguishing ucode from other codes. .

Because the EPC and ISO standards are expected to become commonplace in the future, it is advisable to use a method to check whether MDS is such a code before other codes.

The pseudo-code shown in Table 3 below shows how the priority filter algorithm works.

The pseudo-code in Table 3 distinguishes the tag code assignment method used by comparing the previous 8 bits of the tag code with the total length. The lines 01 through 18 show the distinction between EPC and ISO / IEC codes by examining the 8-bit header part.

Currently, the tag code standardization process of EPC and ISO / IEC is progressing rapidly and accordingly, it is expected to be used most widely in the future, so the first thing is to distinguish between EPC and ISO / IEC.

Lines 06 through 08 are the only processing part for the SGTIN-64 scheme, in which the header is 2 bits long in the EPC tag code scheme. Of the 11 EPC code schemes shown in Table 1, the remaining parts except SGTIN-64 are identified in lines 10 and 12.

In the case of ISO / IEC, since all codes start with '1110 ××××', checking only the preceding 4 bits can be sufficiently determined. This is shown in lines 14 through 17 of the algorithm in Table 3. In the case of ucode, unlike EPC or ISO / IEC, since it has a 128-bit length, it can be expected to be determined by the total tag length.

9 is a recognition algorithm called a priority filter algorithm according to the present invention, and shows a process of confirming a tag ID code granting method according to a priority of a frequency for a tag ID code granting method and then performing a process process.

Referring to FIG. 9, first, it is checked whether a received tag ID code is an EPC header value, and if it is an EPC header value, it is checked whether a code length is 64 bits or 96 bits (S910, S920, S922).

As a result, if the code length is 64 bits or 96 bits, the EPC process is processed (S924). However, if it is not an EPC header value or if the code length is not 64 bits or 96 bits, it is checked whether it is an ISO AC (Allocation Class) value (S930).

If it is confirmed that the ISO AC value, the ISO process (S932). However, if it is not an ISO AC value, it is checked whether it is a ucode code identifier (S940).

As a result of the check, if the code length is a ucode identifier, it is checked whether the code length is 128 bits (S942). As a result, if the code length is 128 bits, the ucode process is processed (S944). However, if it is not a ucode code identifier or if the code length is not 128 bits, it checks whether it is another code value and processes it according to the corresponding code (S950). Therefore, even if various types of RFID code standard systems appear in the future, tag ID codes may be accommodated accordingly.

On the other hand, the ISO / IEC standard for RFID tags presumes the value of '1100010' to mean the code assigned by EAN.UCC. However, EAN.UCC claims to use the EPC standard and there is a possibility of using tags that use only EPC methods such as GID. MDS resolver 640 should be designed to distinguish between EPC codes.

FIG. 10 is a conceptual diagram of a RFID network based on DNS according to the present invention, and includes a tag 1010, a reader 1020, a local server 1030, an MDS resolver 1040, a cache 1050, and a root DNS (Domain Name). Server: 1060, Authoritative DNS 1070, and Information Server 1080.

11 is a flowchart illustrating a DNS-based multi-code directory service method according to an embodiment of the present invention, in which an MDS resolver 1040, a cache 1050, a root DNS 1060, and an orthogonal DNS 1070 are used in an RFID network structure. The method of providing a service for finding one or more IP addresses storing information on an object to which the tag 1010 is attached regardless of the form of a tag ID code is provided.

Referring to FIGS. 10 and 11, a method of multi-code directory service based on DNS according to the present invention will be described. First, a reader 1020 reads a tag 1010 attached to an object, and then reads the read tag ID code in a local server 1030. (S1110, S1112). Then, the local server 1030 transmits the received tag ID code to the MDS resolver 1040 (S1114).

Subsequently, when the MDS resolver 1040 searches the cache 1050 and the IP address of the information server 1080 mapped to the received tag ID code is present, the MDS resolver 1040 receives the IP address of the information server 1080 from the local server 1030. If the IP address of the mapped information server 1080 does not exist, the IP address of the received tag ID code is queried to the root DNS 1060 (S1116 and S1118). In other words, if there is no appropriate IP address in the cache, the MDS resolver 1040 performs a DNS query to the root DNS 1060 on the NAPTR record for that domain.

Subsequently, when the address of the authoritative DNS 1070 having authority in the root DNS 1060 is transmitted to the MDS resolver 1040, the MDS resolver 1040 orchestrate the IP address for the received tag ID code. The query is made to the latent DNS 1070 (S1120, S1122).

Finally, when the orthodox DNS 1070 transmits the retrieved IP address to the MDS resolver 1040, the MDS resolver 1040 transmits the received IP address to the local server 1030, and furthermore, the local server ( 1030 accesses the information server 1080 having the information of the tag ID using the obtained IP address (S1124, S1126, S1128).

As described above, the multi-code directory service method for an RFID network in a global environment may provide a lookup service that searches for URL information that stores information about an object using a tag code regardless of various types of tag code policies. Can be.

Claims (3)

A method of providing a service for finding a URL address that stores information on an object to which a tag is attached regardless of a tag ID code type through an MDS resolver and an MDS server in an RFID network structure, Tag ID codes are mapped and managed in a hierarchical tree structure. Reading, by the reader, a tag attached to the object; The reader sending the read tag ID code to a local server; The local server transmitting the received tag ID code to an MDS resolver; Checking, by the MDS resolver, a method of applying a received tag ID code and processing the received tag ID code; The MDS resolver converts a tag ID code into a URI after processing; The MDS resolver converting the tag ID code in the converted URI into a domain name; The MDS resolver transmitting a tag ID code in the form of a converted domain name to an MDS server; Extracting, by the MDS server, NAPTR data corresponding to a received tag ID code in the form of a domain name; The MDS transmitting the extracted NAPTR data to an MDS resolver; The MDS resolver converting the received NAPTR data into a URI form; Extracting, by the MDS resolver, a URL address of a corresponding information server through NAPTR data of a converted URI type; The MDS resolver transmitting the extracted URL address of the information server to a local server; And And accessing, by the local server, an information server having information of a tag ID using the obtained URL address. The method of claim 1, The MDS resolver processes a process by identifying a tag ID code granting method according to a priority of a frequency for a tag ID code granting method using a recognition algorithm. The recognition algorithm, Checking whether the received tag ID code is an electric product code (EPC) header value; Checking whether the code length is 64 bits or 96 bits if the EPC header value; If the code length is 64 bits or 96 bits, processing the EPC process; If it is not an EPC header value or the code length is not 64 bits or 96 bits, confirming whether an ISO AC (Allocation Class) value; An ISO process process if it is an ISO AC value; Checking whether it is an ucode (ubiquitous code) code identifier if it is not an ISO AC value; checking if the code length is 128 bits if the ucode code identifier; Processing the ucode process if the code length is 128 bits; And A method of multi-code directory service for an RFID network in a global environment, comprising the step of checking whether the code is not a ucode code identifier or a code value other than 128 bits and processing a code according to the corresponding code. In the RFID network structure, readers, local servers, MDS resolvers, caches, root Domain Name Servers (DNS), and authoritative DNS, etc. In the method of providing a service to find the IP address that stores the information, Tag ID codes are mapped and managed in a hierarchical tree structure. Reading, by the reader, a tag attached to the object; The reader sending the read tag ID code to a local server; The local server transmitting the received tag ID code to an MDS resolver; The MDS resolver searches for the cache, and if the IP address of the mapped information server exists for the received tag ID code, transmits the IP address of the information server to the local server, and receives the IP address of the mapped information server if it does not exist. Querying the root DNS for an IP address for the tagged tag ID code; The root DNS transmitting an established orthogonal DNS address to an MDS resolver; The MDS resolver querying the orthodox DNS for an IP address for the received tag ID code; The authoritative DNS sending the retrieved IP address to an MDS resolver; The MDS resolver sending the received IP address to a local server; And And the local server accessing an information server having the information of the tag ID by using the obtained IP address.

Images