Supply Chain Discovery Services

• US 20080109411A1
• Filed: 10/24/2007
• Published: 05/08/2008
• Est. Priority Date: 10/24/2006
• Status: Active Grant

• Current Assignee: Afilias PLC.
• Original Assignee: Afilias PLC.
• Inventors: Young, Michael, Thompson, Frank
• Granted Patent: US 8,170,900 B2
• Time in Patent Office: Days
• US Class Current: 707/3
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A discovery server is provided for tracking an object in a supply chain in accordance with a plurality of predefined events. The object is identifiable by an object identifier. The discovery server comprises the following elements. A communication interface is configured to communicate with each of a plurality of partners in the supply chain using a predefined protocol. A data store is configured to store events for the object, the events being received from the plurality of partners. Each event stored in the data store an object identifier, a life cycle step, a partner identifier and an timing identifier. Also, a processor is configured to search the data store in response to an inquiry regarding the object.

Claims

1. A discovery server for tracking an object, identifiable by an object identifier, in a supply chain in accordance with a plurality of predefined events, the discovery server comprising:

a communication interface configured to communicate with each of a plurality of partners in the supply chain using a predefined protocol;

a data store configured to store events for the object, the events being received from the plurality of partners, wherein each stored event comprises an object identifier, a life cycle step, a partner identifier and an timing identifier; and

a processor configured to search the data store in response to an inquiry regarding the object.

2. The discovery server of claim 1, wherein the event further comprises additional information sources for providing further details about the event.

3. The discovery server of claim 1, wherein the data store is configured to be partitioned periodically in accordance with a classification of the object.

4. The discovery server of claim 3, wherein the classification of the object can be modified dynamically.

5. The discovery server of claim 3, wherein the classification of the object is determined in accordance with one or both of a frequency at which events are submitted for the object or an expected life cycle of the object.

6. The discovery server of claim 1, wherein the processor is further configured to implement a rules engine for applying rules to determine partner access to the events.

7. The discovery server of claim 6, wherein events are hidden from partners who do not have access to the events.

8. The discovery server of claim 1, wherein discovery server identifies the partner submitting the events and injects the partner identifier to the event once the event is received.

9. The discovery server of claim 1 wherein the processor is further configured to provide a notifications of the event in accordance with predefined criteria.

10. The discovery server of claim 9, wherein the notification is sent to an Object Naming Service when the life cycle step of the event matches a predefined life cycle step.

11. The discovery server of claim 9, further comprising a messaging queue, wherein the notification is placed in the messaging queue to be transmitted to one of the partners in response to a subscription request the one of the partners.

12. The discovery server of claim 1, wherein the processor is further configured to apply a security policy to the events in order to control access thereto.

13. The discovery server of claim 12, wherein security policy can be defined on at least one of a user level, a partner level, or a supply chain level.