KR20090032642A - System and method for administration of physical distribution information based on rfid - Google Patents

Abstract

A system and a method for administration of physical distribution information based on RFID are provided to enable an operator to manage the distribution of specific articles systematically by providing the information at which RFID event related EPC information, B2B information and import/export clearance distribution information are integrated. A tracking sever registers the EPC history information and the B2B information that occur at an international distribution base. If there is a request for the inquiry of distribution history information, the tracking sever integrates the previously stored EPC history information, B2B history information and the import/export clearance distribution information collected through an import/export clearance distribution management network-associated module(410), processes the integrated information and provides the processed information. A key mapping sever(300) verifies and registered a distribution information key value transmitted from a client application sever(500), and extracts a key for the inquiry of the distribution history information.

Description

System and Method for Administration of Physical Distribution Information Based on RFID

The present invention relates to a system and method for managing RFID-based international logistics information, and more particularly, to an RFID-based international system for integrating and tracking / managing EPC history information, B2B history information, and import / export customs clearance logistic information related to international logistics. It relates to a logistics information management system and method.

Recently, due to the proliferation of the Internet and the activation of e-commerce, sellers are selling their products to buyers on a daily basis, while products between shippers, warehouses, and transporters are increasing. Most shipping and delivery work is still done offline.

On the other hand, RFID Tag (Radio Frequency Identification Tag) is an IC (Integrated Circuit) chip that can transmit / receive non-contact wireless data and contains information on the whole process of product production, distribution, storage and consumption. For example, the RFID reader may read RFID information through an antenna and provide various additional services by linking the RFID information with an information processing system through at least one or more communication means.

The above-mentioned RFID technology is used in various fields. For example, in an international logistics transaction, an RFID tag is attached to the logistics and the EPC information corresponding to the identification information of the logistics is received from the RFID tag. To manage the flow.

In addition to EPC information, the form of information for logistics transactions includes B2B information generated from client side such as aviation international logistics solution, maritime international logistics solution, corporate international logistics solution, customs international logistics solution, and import and export managed by the import and export customs clearance logistics network. There is customs logistics information.

Each of the information contains different key values and identification information. At present, since such information is not systematically managed, a lot of manual work is required for operators or related personnel to grasp information on specific logistics. Doing.

Accordingly, in managing international logistics, a technology for integrating and managing EPC information related to RFID events, B2B information, and import and export customs clearance logistics information is required.

The present invention has been made to solve the above-described problems, and can be provided with all the EPC history information, B2B history information, import and export customs clearance logistics history information for the corresponding logistics based on any key input by the information inquiry requester. There is a technical problem to provide an RFID-based international logistics information management system and method.

In addition, an object of the present invention is to provide a combination of EPC history information, B2B history information, import and export customs clearance logistics information associated with the RFID event.

The present invention for achieving the above object is connected through the import and export customs clearance logistics management network linkage module providing the import and export customs clearance logistics history information relaying service and the import and export customs clearance logistics history information relaying service provides the customer information inquiry service As an international logistics information management system for connecting to a client application server to provide logistics history information,

It is connected to the national electronic trade network that provides import and export customs clearance logistic information, and through the import and export customs clearance logistic management network linkage module, which provides the relay service of import and export customs clearance log history information, and to the client application server that provides customer information inquiry service. As an international logistics information management system for providing information,

Register the EPC history information and B2B history information generated at the international logistics base, and if there is a request for inquiry of the logistics history information from the international logistics monitoring server, the pre-stored EPC history information and B2B history information and the import / export customs clearance logistics network linkage module Tracking server that integrates and processes the import and export customs clearance logistics history information collected through; A key mapping server for verifying and registering a logistics information key value transmitted from the client application server and extracting a key for inquiring specific logistics history information; And an international logistics monitoring server configured to communicate with the key mapping server and the tracking server to provide logistic history information corresponding to the input key value to the corresponding information inquiry requester, when a key value is input from the information inquiry requester. .

Another embodiment of the present invention provides a tracking server, comprising: a database storing information related to a tracking server, including EPC history information and B2B history information; An RFID event query unit for searching logistic history information of RFID-attached cargoes moving on the international logistics SCM; An import / export logistics event query unit for searching any one of B2B history information or import / export customs clearance logistic information related to the international logistics RFID SCM; A B2B event registration unit for registering B2B history information related to RFID business processing in the database; An RFID event registration unit that registers base station-specific EPC history information in the database or deletes registered EPC history information; An authority manager configured to set an access authority list for the EPC history information and then check an access authority for the information inquiry requester; An authentication manager that receives an ID and password of an information inquiry requester attempting to access the tracking server for the first time and returns an authentication key, and thereafter identifies an information inquiry requester based on the authentication key; And an integrated processing unit for receiving the logistic history information request transmitted from the RFID event query unit and the import / export logistic event query unit, integrating and processing EPC history information, B2B history information, and import / export clearance logistic history information into one result. do.

Another embodiment of the present invention is a client application server connected to the national electronic trading network providing the import and export customs clearance logistics history information and the import and export customs clearance logistics management network linkage module providing a relay service for import and export customs clearance logistics information, providing a customer information inquiry service Connected with, the key mapping server for managing the key value for each logistics,

A database for storing information related to the key mapping server: a register configured to perform a procedure related to registration of key values for each logistic, including verification of logistic information key values; And an inquiry unit for extracting a key value for generating logistic history information on the key value received by the information inquiry requester.

The registration unit performs a verification procedure including checking whether or not the logistics information key value transmitted from the client application server is in a correct format and whether or not it is registered and in the correct format before registering the key value registered in the national electronic trading network. Key validity checking means; Logistics information mapping means for extracting a representative key value associated with the corresponding key value from the database for registration of the logistics information key value; And logistics information registering means for registering the key value transmitted from the client application server in the database in association with the representative key value extracted by the logistics information mapping means.

The inquiry unit comprises: key selection means for selecting a type of corresponding logistics key value from a plurality of types of logistics key values by analyzing a format of a key value received by the information inquiry requester; Key extracting means for extracting a representative key value associated with a key value input by an information inquiry requester for logistics information inquiry from the database; And logistics information inquiry means for extracting the key value required by the information inquiry requester in association with the representative key value extracted by the key extraction means.

Another invention provides a tracking server that collects and stores EPC history information and B2B history information, provides logistics information on received key values, a key mapping server that provides key values for querying specific logistics history information, and logistics. As a method for providing international logistics information in an international logistics information management system including an international logistics monitoring server providing historical information,

a) when the international logistics monitoring server receives the key value input by the information inquiry requester, forwarding it to the key mapping server to request a key mapping inquiry; b) selecting, by the key mapping server, a type of the received key value by comparing it with a preset type, and retrieving a representative key value matched with the received key value; c) retrieving a plurality of inquiry key values associated with the representative key value from a key mapping server to the international logistics monitoring server; d) an international logistics monitoring server generates an inquiry query using a specific inquiry key value selected by a user among a plurality of inquiry key values received from the key mapping server, and transmits it to the tracking server to request logistics information inquiry. step; e) when the tracking server receives the logistics information inquiry request from the international logistics monitoring server, collecting EPC history information, B2B history information and import / export clearance logistic history information based on the inquiry key value; And f) the tracking server processes the EPC history information collected in step e), combines the B2B history information with the import and export customs clearance logistic information, and then combines the processed EPC history information with the B2B history information and the import and export customs clearance logistic information. Mapping to generate the logistic history information, and deliver it to the international logistics monitoring server to provide to the information query requester; includes.

As described above, the RFID-based international logistics information management system and method of the present invention receives an arbitrary inquiry key by the information inquiry requester, obtains the logistics key mapping information associated with the key mapping system, and obtains EPC information related to the RFID event and B2B. By providing technology to integrate and manage information and import and export customs clearance logistics information, it has the advantage of synchronizing paper flow and physical movement information of international logistics and eliminating disconnection / dispersion of information by complex logistics keys.

In addition, since the present invention is provided by integrating the EPC history information, B2B history information and import and export customs clearance logistics information related to the RFID event, it can be managed more systematically for a specific logistics in terms of operators, logistics in terms of requesting information inquiry There is an advantage that can be provided with an easier way to receive the relevant information, including the state of.

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

First, Figure 1 is a view showing the configuration of the international logistics information management system according to the present invention.

As shown, the international logistics information management system is a server that provides cargo flow information and container cargo security information by air / sea, export / import, and logistics from the server according to the request of the information inquiry requester for logistics information. Registers the international logistics monitoring server 100, which requests and receives logistic information including history information, EPC history information and B2B (business-to-business) history information generated at international logistics bases, and requests logistic history information inquiry. As received, the tracking server 200 and the client application server to integrate and process the pre-stored EPC history information and B2B history information and import and export clearance logistics history information collected through the import and export clearance logistics management network linkage module 410. Keys for verifying and registering the logistics information key value transmitted from 500, and for querying specific logistics history information It includes a key mapping server 300 to extract.

The EPC (Electronic Product Code) is an identification code system for RFID, and consists of a company code, a product item code, and a product serial number, and identifies almost all objects such as general products, cases, pallets, and logistics assets.

Meanwhile, B2B history information consists of aviation bonded warehouse solution, aviation bonded carrier solution, forwarder solution, aviation terminal solution, etc., aviation international logistics server and maritime terminal that handles aviation international logistics business based on EPC network at each logistics base. Offshore Container Logistics (ODCY), Offshore Container Carrier Solution, Offshore Container Carrier Solution, Shipping Management Solution, etc. It is collected from the client server 500 including the international logistics server in charge of the RFID-based international logistics business processing and the customs company international logistics server in charge of the RFID-based international logistics business operating in a customs company.

In addition, the import and export customs clearance logistics management network linkage module 410 provides the import and export customs clearance logistics history information services, such as import and export progress information, notification information, in conjunction with the import and export customs clearance logistics management network, the import and export customs clearance logistics management network (430) It is responsible for relaying customs related EDI documents of related companies.

In more detail, when the key value is input from the information inquiry requester, the international logistics monitoring server 100 communicates with the key mapping server 300 and the tracking server 200 to provide logistic history information corresponding to the input key value. To the requester of the information inquiry.

For example, when the international logistics monitoring server 100 receives a key value input by the information inquiry requester, the international logistics monitoring server 100 requests an inquiry key for inquiring logistics history information mapped to a key value received from the key mapping server 300. And it receives, and receives the logistic history information combined with the corresponding EPC history information, B2B history information and import and export customs clearance logistic information from the tracking server 200 using the inquiry key.

Tracking server 200 is RFID event query unit 210, import and export logistics event query unit 220, B2B event register unit 230, RFID event register unit 240, authorization manager 250, authentication manager 260, integration The processor 270 and the database 280 are included. First, the RFID event query unit 210 inquires logistic history information of an RFID-attached cargo in motion on an international logistics supply chain management (SCM).

 The import and export logistics event querying unit 220 inquires any one of B2B history information or import and export clearance logistics history information related to the international logistics RFID SCM.

The B2B event registration unit 230 registers B2B history information related to RFID business processing in the database 280.

The B2B history information is registered before or after the B2B document is sent to the trading partner by the sender who created the B2B document. The event type, event name, time of occurrence, sender, receiver, recording time, document type, and document are shown in Table 1. Include a number.

The RFID event register 240 registers base station-specific EPC history information in the database 280 or deletes the registered EPC history information.

The EPC history information registered by the RFID event register 240 is an international logistics multifunctional / intelligent integrated middleware 610 that collects / filters a large amount of tag data transmitted from an RFID reader (not shown), and an international logistics SCM. It provides EPCIS event information capture / query standard interface and storage management function by providing infrastructure and access infrastructure for sharing EPC information among participating actors (corporate, customs company, forwarder, bonded carrier, bonded warehouse, shipping company, airline, etc.) International Logistics EPCIS server 630 and ONS (Object Naming Service) server (not shown) that provide reliable communication method through EPC network protection mechanism for EPC history information inquiry service of various systems constituting EPC network. RFID software configured and working with RFID hardware systems that conforms to the architecture framework specifications of higher EPCglobal organizations A control system configuration information is transmitted through the EPC network 650.

EPC history information is automatically registered at the event registration in the international logistics EPCIS server 630 of the logistics base, EPC, EPCIS location, event type, BIZLOCATION, event occurrence time, event recording time, BIZSTEP, DISPOSITION, access as shown in Table 2 Includes authorization check, registrant ID, Biz transaction type, Biz transaction value.

The RFID event registration unit 240 registers EPC history information generated at each base (company, customs company, import / export agency forwarder, bonded carrier, terminal, etc.) in the database 280, which is registered from the company side. The registration key values are representative key, invoice number (Invoice No), customs clearance number, waybill / vehicle number, export report number, S / R (Shipping Request), container number, e-Seal (Container Electronic Seal).

In the case of an enterprise, an RFID tag is issued to an item to be released and an order is issued, the representative key (order number) and the tag are mapped before shipment, and registered in the international logistics EPCIS server 630 in the form of a transaction event, and then key mapping (Key Mapping). Information is transmitted to the tracking server 200. Thereafter, the generated key is mapped to the representative key and transmitted to the tracking server 200.

Meanwhile, the customs company registers the export declaration number registered on the basis of the customs clearance number after the export declaration on the tracking server 200, and the forwarder generates the B / L based on the invoice number when B / L (Bill of Lading) is issued. Register the number, etc., and add other keys when they occur, and the bonded carrier forwards the waybill and vehicle information to the company or the forwarder for registration.When the container import / export information occurs, the key (bus code / port) is based on the waybill number. The terminal registers the container number and the e-Seal number by matching the representative key with the container Freight Station (CFS) after importing the goods.

The key registered to the tracking server 200 on the forwarder side is B / L, S / R, Manifest Reference No. (MRN), MBL (Master B / L No), Waybill / Vehicle Number, AMS ( Automated Manifest System (HSN), House B / L Sequence No (HSN), Container Number, and D / O (Delivery Order).

The authority manager 250 sets the access authority list for the EPC history information, and then checks the access authority for the information inquiry requester.

The authority manager 250 checks the ACL information among the registered EPC history information to check the access authority for the logistics information. The ACL information includes an EPC, an EPCIS location, an event type, BIZLOCATION, BIZSTEP, and an accessor ID as shown in Table 3, and an accessor ID means an identifier list to which information is accessible.

The authentication manager 260 receives the ID and password of the information inquiry requester attempting to access the tracking server 200 for the first time, returns an authentication key, and then identifies the information inquiry requester based on the authentication key.

When the integrated processing unit 270 receives a request for logistical history information transmitted from the RFID event querying unit 210 and the import / export logistical event querying unit 220, the result of the EPC history information, the B2B history information, and the import / export clearance logistic history information are one result. Integrate and process

Logistic history information retrieved and extracted through the RFID event query unit 210 and the import and export logistics event query unit 220 is in the form of XML as shown below. For B2B history information, the event type, event name, time of occurrence, sender, receiver , Record time, document type and document number, and for EPC history information, include EPC, EPCIS location, event type, BIZLOCATION, event occurrence time, event record time, BIZSTEP, DISPOSITION, and Biz transaction type. Here, BIZSTEP is a business processing step of an EPCIS event and represents a procedure (eg, goods receipt, storage, release, etc.) in which an RFID-tagged item is performed at a specific location.

<? xml version = "1.0" encoding = "utf-8"?>

- <TSQueryDocument xmlns: xsi = " http://www.w3.org/2001/XMLSchema-instance " creationDate = " 2005-07-11T11: 30: 47.0Z " schemaVersion = " 1 ">

- <TSBody>

- <QueryResults xmlns = " urn : uglp : ts - query : xsd : 1 ">

　 <queryName xmlns = ""> SimpleEPCTrackingQuery </ queryName>

　 <subscriberID> uglp - user01 </ subscriberID>

　 <timeStamp> 2007-05-03 14:59:55 </ timeStamp>

- <resultsBody xmlns = "">

- <EPCTrackingList>

- <EPCTracking epc = " urn : epc : id : sgtin : 0111111.111111.2 ">

- <bizTransactionList>

　 <bizTransaction type = " urn : epcglobal : uglp : btt : po "> urn : epcglobal : uglp : btt : po : order123456789 </ bizTransaction>

　 <bizTransaction type = " urn: epcglobal: uglp: btt: hbl "> urn: epcglobal: uglp: btt: hbl: 4959XMG99 </ bizTransaction>

　 </ bizTransactionList>

- <EPCStepList>

- <EPCStep>

　 <eventTime> 2007-04-23 16:06:06 </ eventTime>

　 <bizStep> urn : epcglobal : epcis : bizstep : uglp : shipping </ bizStep>

　 <disposition> urn : epcglobal : epcis : disp : uglp : in _ transit </ disposition>

　 <readPoint> urn : epcglobal : uglp : loc : 0614141.07346.40. RP -1529 </ readPoint>

　 <bizLocation> urn : epcglobal : uglp : loc : 0614141.201.401 </ bizLocation>

　 </ EPCStep>

- <EPCStep>

　 <eventTime> 2007-04-23 15:59:40 </ eventTime>

　 <bizStep> urn : epcglobal : epcis : bizstep : uglp : received </ bizStep>

　 <disposition> urn : epcglobal : epcis : disp : uglp : in _ transit </ disposition>

　 <readPoint> urn : epcglobal : uglp : loc : 0723141.07346.40. RP -1529 </ readPoint>

　 <bizLocation> urn : epcglobal : uglp : loc : 0723141.202.402 </ bizLocation>

　 </ EPCStep>

- <EPCStep>

　 <eventTime> 2007-04-24 21:52:28 </ eventTime>

　 <bizStep> urn : epcglobal : epcis : bizstep : uglp : shipped </ bizStep>

　 <disposition> urn : epcglobal : epcis : disp : uglp : in _ transit </ disposition>

　 <readPoint> urn : epcglobal : uglp : loc : 0723141.07346.40. RP -1529 </ readPoint>

　 <bizLocation> urn : epcglobal : uglp : loc : 0723141.202.402 </ bizLocation>

　 </ EPCStep>

　 </ EPCStepList>

　 </ EPCTracking>

- <EPCTracking epc = " urn : epc : id : sgtin : 0111111.111111.3 ">

- <bizTransactionList>

　 <bizTransaction type = " urn : epcglobal : vtype : BizTransactionType : 011111.111111.1 "> epcglobal : vtype : BizTransactions: 011111.111111.1 </ bizTransaction>

　 <bizTransaction type = " urn : epcglobal : vtype : BizTransactionType : po "> epcglobal : vtype : BizTransactions : 0123456789ABCDEF </ bizTransaction>

　 </ bizTransactionList>

- <EPCStepList>

- <EPCStep>

　 <eventTime> 2007-04-23 16:06:06 </ eventTime>

　 <bizStep> urn : epcglobal : epcis : bizstep : uglp : shipping </ bizStep>

　 <disposition> urn : epcglobal : epcis : disp : uglp : in _ transit </ disposition>

　 <readPoint> urn : epcglobal : uglp : loc : 0614141.07346.40. RP -1529 </ readPoint>

　 <bizLocation> urn : epcglobal : uglp : loc : 0614141.201.401 </ bizLocation>

　 </ EPCStep>

- <EPCStep>

　 <eventTime> 2007-04-23 15:59:40 </ eventTime>

　 <bizStep> urn : epcglobal : epcis : bizstep : uglp : received </ bizStep>

　 <disposition> urn : epcglobal : epcis : disp : uglp : in _ transit </ disposition>

　 <readPoint> urn : epcglobal : uglp : loc : 0723141.07346.40. RP -1529 </ readPoint>

　 <bizLocation> urn : epcglobal : uglp : loc : 0723141. 202.402 </ bizLocation>

　 </ EPCStep>

- <EPCStep>

　 <eventTime> 2007-04-24 21:52:28 </ eventTime>

　 <bizStep> urn : epcglobal : epcis : bizstep : uglp : shipped </ bizStep>

　 <disposition> urn : epcglobal : epcis : disp : uglp : in _ transit </ disposition>

　 <readPoint> urn : epcglobal : uglp : loc : 0723141.07346.40. RP -1529 </ readPoint>

　 <bizLocation> urn : epcglobal : uglp : loc : 0723141.202.402 </ bizLocation>

　 </ EPCStep>

　 </ EPCStepList>

　 </ EPCTracking>

　 </ EPCTrackingList>

- <DocumentTrackingList>

- <DocumentStepList>

- <DocumentStep>

　 <EVENT_TYPE> SippingRequest Document Sended </ EVENT_TYPE>

　 <EVENT_NAME> test .. </ EVENT_NAME>

　 <EVENT_TIME> 2007-04-23 16:06:05 </ EVENT_TIME>

　 <RECORD_TIME> 2007-04-23 16:06:06 </ RECORD_TIME>

　 <FROM> urn : epcglobal : uglp : loc : 0614141.201.401 </ FROM>

　 <TO> urn : epcglobal : uglp : loc : 0723141.202.402 </ TO>

　 <DOCUMENT_TYPE> s / r </ DOCUMENT_TYPE>

　 <DOCUMENT_NUMBER> 0123456789 ABCDEF </ DOCUMENT_NUMBER>

　 </ DocumentStep>

- <DocumentStep>

　 <EVENT_TYPE> SippingRequest Document Received </ EVENT_TYPE>

　 <EVENT_NAME> test .. </ EVENT_NAME>

　 <EVENT_TIME> 2007-04-24 12:08:02 </ EVENT_TIME>

　 <RECORD_TIME> 2007-04-24 12:08:03 </ RECORD_TIME>

　 <FROM> urn : epcglobal : uglp : loc : 0614141.201.401 </ FROM>

　 <TO> urn : epcglobal : uglp : loc : 0723141.202.402 </ TO>

　 <DOCUMENT_TYPE> s / r </ DOCUMENT_TYPE>

　 <DOCUMENT_NUMBER> 0123456789 ABCDEF </ DOCUMENT_NUMBER>

　 </ DocumentStep>

　 </ DocumentStepList>

　 </ DocumentTrackingList>

　 </ resultsBody>

　 </ QueryResults>

　 </ TSBody>

　 </ TSQueryDocument>

The database 280 stores information related to the tracking server, including the EPC history information and the B2B history information.

2 is a diagram illustrating a configuration of a key mapping server according to the present invention.

The key mapping server 300 is a register 310 for performing the procedure related to the registration of the key value for each logistic, including verification of the logistic information key value, and for generating logistic history information on the key value received by the information inquiry requester. Receiving a key value input by the information inquiry requester through the international logistics monitoring server 100, including a query unit 330 for extracting the key value and a database 350 for storing information related to the key mapping server, Select the type of key through the type of the received key value, look up the representative key value matched with the received key value for the logistics information inquiry, and retrieve a plurality of search key values associated with the representative key value Transfer to tracking server 200.

The registration unit 310 includes a key validity check means 311, a logistics information mapping means 313, and a logistics information register 315. First, the key validity check means 311 is transmitted from the client application server 500. Verification procedures are performed, including checking whether they are in the correct format for the logistics information key values, and whether they are registered and in the correct format before registering the key values registered in the national electronic trade network.

The logistics information mapping means 313 extracts a representative key value associated with the corresponding key value from the database 350 to register the logistics information key value.

The logistics information registration unit 315 registers the key value transmitted from the client application server in the database 350 in association with the representative key value extracted by the logistics information mapping means 313.

The inquiry unit 330 includes a key sorting means 331, a key extracting means 333, and a logistics information searching means 335, and the key sorting means 331 is a key value received by an information inquiry requester. The type of corresponding logistics key value is selected from the plurality of types of logistics key values by analyzing the format of.

Here, the type of the key value is a private key, a manifest number, a cargo management number, export report number, B / L, AWB, container number that is arbitrarily set, such as the waybill number, customs clearance number, etc. It is divided into formatting keys that have digits, formats, etc. set.

For example, the manifest number (MRN) of the formalization key is Alphanumeric, length (11..11), CheckDigit, and the export declaration number is Numeric (Alphanumeric), length (15), CheckDigit, and the cargo management number MSN and HSN. Are Positive Numeric, length (1..4) and Positive Numeric, length (1..3), Master B / L is Alphanumeric, length (1..16), House B / L is Alphanumeric, length (1. .16), Master Air way Bill is Alphanumeric, length (1..11), House Air way Bill is Alphanumeric, length (1..12), ShipSign is length (1..6), Navigation (VoageNo) consists of length (1..7) and the container number consists of Upper Alphanumeric, length (1..11).

In the case of a standardized key, the key sorting means 331 selects a key type based on a preset number generation system, or selects a key type based on a preset scheme such as length, letters, and numbers.

Private keys can be used when the information inquiry requester is aware of the key type or not.In the case where the information inquiry requester is aware of the key type, the key type (for example, manifest control number) If you enter together, freight management number, etc., the key screening means 331 is designated as the type.

The key extracting means 333 extracts the representative key value associated with the key value input by the information inquiry requester from the database 350 for logistics information inquiry.

The logistics information inquiry means 335 extracts a plurality of inquiry keys associated with the representative key value extracted by the key extraction means 333 to provide a key value requested by the information inquiry requester.

3 is a flowchart illustrating a method of registering EPC history information according to the present invention.

First, the RFID event registration unit 240 of the tracking server 200 generates RFID event information (EPC) generated from each base (logistic entities such as companies, customs agencies, forwarders, bonded carriers, etc.) and transmitted via the EPC network 650. History information) (S101).

The RFID event register 240 corresponds to one of an event type of an object event (ObjectEnvet), an aggregation event (AggregationEvent), and a transaction event (TrasactionEvent) in order to check the validity of the EPC history information received in step S101. Check (S103).

Here, the object event refers to event information including one or more physical objects identified as EPCs, and is mainly considered as an actual observation of the EPC, and collects and observes the EPC code of a specific business step at a specific time and place. Contains information. For example, an object event is a collection of EPC codes recognized at the gate 9 at 10:01 am.

An aggregation event refers to an event in which an object is physically included in another object. The aggregation event includes EPC code set information included in a parent EPC of a specific business stage at a specific time and at a specific place. For example, an aggregation event is a collection of EPC codes on palette 27 at 12:32 pm.

In addition, a transaction event refers to an event in which a physical object is connected or separated from one or more business transactions, and includes EPC code set information belonging to a business transaction. For example, the transaction event is order number 123 with EPC codes 3014, 3015 and 3016.

As a result of checking in step S103, if the EPC history information is valid, the RFID event registration unit 240 checks whether the event type of the EPC history information is a transaction event type (TransactionEvent) (S105).

As a result of checking in step S105, when the EPC history information is not the transaction event type, the authority management unit 250 checks the ACL information in the EPC history information to determine whether the access authority information for the logistics information is included (S107). .

As a result of checking in step S107, when the access authority information for the EPC history information is not included, the RFID event registration unit 240 stores the EPC history information in the database 280 (S109). The ACL information includes an EPC, an EPCIS location, an event type, BIZLOCATION, BIZSTEP, and an accessor ID as shown in Table 3, and an accessor ID means an identifier list to which information is accessible.

On the other hand, if the confirmation EPC history information of step S103 is invalid, the tracking server 200 performs a step before step S101.

On the other hand, when the check result of step S105, the EPC history information is a transaction event type, RFID event register 240 matches the transaction value and the EPC list information associated with the EPC history information and stores in the database 280, Step S109 is performed.

In addition, when the check result of step S107, the access authority information on the EPC history information is included in the ACL information, the authority management unit 250 sets the access authority list for the corresponding EPC history information and stores in the database 280 (S113), step S109 is performed.

4 is a flowchart illustrating a B2B history information registration method according to the present invention.

First, when the B2B event register 230 receives the B2B history information related to the RFID business process generated from the client application server 500 (S201), whether the B2B history information includes all information to be included in the B2B history information and the database In operation 203, the controller may check whether the registration information is valid by checking whether the information is duplicated with the B2B history information previously stored in operation 280.

Here, the B2B history information is registered before or after sending the B2B document to the trading partner at the sender side that generated the B2B document, and as shown in Table 1, the event type, event name, occurrence time, sender, receiver, recording time, and document. Include the type and document number.

If the B2B history information is valid as a result of checking in step S203, the B2B event register 230 stores the corresponding B2B history information in the database 280 (S205).

On the other hand, when it is determined in step S203 that the information to be included in the B2B history information does not include or is determined to be invalid information as the same as the previously stored B2B history information, the B2B event registration unit 230 proceeds to step S201. Perform

5 is a flowchart illustrating a method for querying logistics history information according to the present invention.

First, when the international logistics monitoring server 100 receives a key value input by the information inquiry requester (S301), it transmits it to the key mapping server 300 and requests a key mapping inquiry (S303).

Subsequently, when the key mapping server 300 receives the key mapping inquiry request received from the international logistics monitoring server 100, the key mapping server 300 compares the type of the received key value with a preset key type and selects the corresponding type (S305). The representative key value matched with the received key value for the logistics information inquiry is queried (S307).

Thereafter, the key mapping server 300 searches for a plurality of inquiry key values associated with the representative key value and transmits the searched key values to the international logistics monitoring server 100 (S309 and S311).

The international logistics monitoring server 100 generates an inquiry query by using a specific inquiry key value selected by the user among a plurality of inquiry key values transmitted from the key mapping server 300, and transmits the inquiry query to the tracking server 200 for logistics. Request information inquiry (S313, S315).

When the tracking server 200 receives the logistics information inquiry request received from the international logistics monitoring server 100, the tracking server 200 collects EPC history information and B2B history information from the database 280 based on the inquiry key value, and manages import and export clearance logistics. The import and export customs clearance logistics history information managed by the import and export customs clearance logistics management network 430 through the network linkage module 410 is collected (S317).

Thereafter, the tracking server 200 processes the EPC history information, and combines the B2B history information and the import and export clearance logistic history information (S319).

Referring to step S319 in more detail, the tracking server 200 generates an EPCStep object based on the collection result of the EPC history information, and generates and initializes an EPC tracking object. Process EPC history information by sorting data in order of EventTime, creating an EPC tracking list object, and creating an EPC tracking list object by adding the corresponding EPC tracking object to the EPC tracking list object. do.

Here, the EPC step is a business processing step of the event, and represents a procedure (eg, goods receipt, storage, release, etc.) in which an RFID-tagged item is performed at a specific location, and EPC tracking is a higher concept of the EPC step. Represents a movement path of an article to which an RFID tag is attached.

For example, if item A is Goods Receipt / Storage / Release at position 1, Goods Receipt / Storage / Release at position 2, EPC step means Goods Receipt / Storage / Release at each position (No. 1, 2) , EPC tracking means 1, 2 movement paths.

At the same time, tracking server 200 combines the B2B history information and import and export clearance logistics history information.

Thereafter, the integrated processing unit 270 of the tracking server 200 maps the B2B history information and the import and export clearance logistic history information combined with the processed EPC history information (S321).

The tracking server 200 transmits the logistics history information mapped in step S321 to the international logistics monitoring server 100 to provide the information inquiry requester (S323 and S325).

Although not shown, in the process of providing the logistics history information of FIG. 5, the tracking server 200 determines whether the information inquiry requester has the authority to receive the logistics history information based on the access authority list set in the logistics history information. Check it.

As such, those skilled in the art will appreciate that the present invention can be implemented in other specific forms without changing the technical spirit or essential features thereof. Therefore, the above-described embodiments are to be understood as illustrative in all respects and not as restrictive. The scope of the present invention is shown by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

1 is a view showing the configuration of an international logistics information management system according to the present invention;

2 is a diagram showing the configuration of a key mapping server according to the present invention;

3 is a flowchart illustrating a method of registering EPC history information according to the present invention;

4 is a flowchart illustrating a B2B history information registration method according to the present invention;

5 is a flowchart illustrating a method for querying logistics history information according to the present invention.

<Explanation of symbols for the main parts of the drawings>

100: international logistics monitoring server 200: tracking server

210: RFID event query unit

220: import and export logistics event query unit

230: B2B event register 240: RFID event register

250: authority management unit 260: authentication management unit

270: integrated processing unit 280: database

300: key mapping server 310: register

330: query 350: database

410: import and export clearance logistics network linkage module

430: import and export clearance logistics network 500: client application server

610: International Logistics Multi-functional / Intelligent Integrated Middleware

630: International Logistics EPCIS Server 650: EPC Network

Claims (6)

It is connected to the national electronic trade network that provides import and export customs clearance logistic information, and through the import and export customs clearance logistic management network linkage module, which provides the relay service of import and export customs clearance log history information, and to the client application server that provides customer information inquiry service. As an international logistics information management system for providing information, Register the EPC history information and B2B history information generated at the international logistics base, and if there is a request for inquiry of the logistics history information from the international logistics monitoring server, the pre-stored EPC history information and B2B history information and the import / export customs clearance logistics network linkage module Tracking server that integrates and processes the import and export customs clearance logistics history information collected through; A key mapping server for verifying and registering a logistics information key value transmitted from the client application server and extracting a key for inquiring specific logistics history information; And An international logistics monitoring server configured to communicate with the key mapping server and the tracking server to provide logistic history information corresponding to the input key value to the information inquiry requester when a key value is input from the information inquiry requester; International logistics information management system comprising a. The method of claim 1, The tracking server, A database that stores information related to the tracking server, including EPC history information and B2B history information; An RFID event query unit for searching logistic history information of RFID-attached cargoes moving on the international logistics SCM; An import / export logistics event query unit for searching any one of B2B history information or import / export customs clearance logistic information related to the international logistics RFID SCM; A B2B event registration unit for registering B2B history information related to RFID business processing in the database; An RFID event registration unit that registers base station-specific EPC history information in the database or deletes registered EPC history information; An authority manager configured to set an access authority list for the EPC history information and then check an access authority for the information inquiry requester; An authentication manager that receives an ID and password of an information inquiry requester attempting to access the tracking server for the first time and returns an authentication key, and thereafter identifies an information inquiry requester based on the authentication key; And An integrated processing unit for receiving the logistic history information request transmitted from the RFID event query unit and the import / export logistic event query unit, integrating and processing EPC history information, B2B history information, and import / export clearance logistic history information into one result; International logistics information management system comprising a. It is connected to the national electronic trade network that provides import and export customs clearance history information, and through the import and export customs clearance logistics management network linkage module, which provides the relay service of import and export customs clearance history information, and is connected to the client application server that provides customer information inquiry service. A key mapping server for managing star key values. Database that stores information related to the key mapping server: A registration unit that performs a procedure related to registration of key values for each logistic, including verification of logistic information key values; And An inquiry unit for extracting key values for generating logistic history information on key values received by the information inquiry requester; Key mapping server comprising a. The method of claim 3, The registration unit, Key validity checking means for performing a verification procedure including checking whether the logistic information key value transmitted from the client application server is in the correct format and whether the key value registered in the national electronic trading network is registered and whether it is in the correct format. ; Logistics information mapping means for extracting a representative key value associated with the corresponding key value from the database for registration of the logistics information key value; And Logistics information registration step of registering in the database the key value transmitted from the client application server in association with the representative key value extracted by the logistics information mapping means; Key mapping server comprising a. The method of claim 3, The inquiry unit, Key sorting means for analyzing the format of the key value received by the information inquiry requester to sort the corresponding kind of logistics key value from the plurality of types of logistics key values; Key extracting means for extracting a representative key value associated with a key value input by an information inquiry requester for logistics information inquiry from the database; And Distribution information inquiry means for extracting a key value required by the information inquiry requester in association with the representative key value extracted by the key extraction means; Key mapping server comprising a. A tracking server that collects and stores EPC history information and B2B history information, provides logistics information on received key values, provides a key mapping server that provides key values for searching specific logistics history information, and provides logistic history information. As a method for providing international logistics information in an international logistics information management system including an international logistics monitoring server, a) when the international logistics monitoring server receives a key value input by the information inquiry requester, forwarding it to the key mapping server to request a key mapping inquiry; b) selecting, by the key mapping server, the type of the received key value by comparing the type with the preset type, and retrieving the representative key value matched with the received key value; c) retrieving a plurality of inquiry key values associated with the representative key value from a key mapping server to the international logistics monitoring server; d) an international logistics monitoring server generates an inquiry query using a specific inquiry key value selected by a user among a plurality of inquiry key values received from the key mapping server, and transmits it to the tracking server to request logistics information inquiry. step; e) when the tracking server receives the logistics information inquiry request from the international logistics monitoring server, collecting EPC history information, B2B history information and import / export clearance logistic history information based on the inquiry key value; And  f) The tracking server processes the EPC history information collected in step e), combines the B2B history information with the import and export customs clearance log information, and then imports the B2B history information and the import and export customs clearance log history information combined with the processed EPC history information. Generating logistic history information by mapping and delivering the logistic history information to an international logistics monitoring server to provide the information inquiry requester; International logistics information management method comprising a.

Images