US 7,345,585 B2Grant
Network based device for providing RFID middleware functionality
Issue Date:2008-03-18
•20 Claims
•13 Drawing Sheets
Abstract
Some embodiments of the present invention provide middleware functionality integrated into a module of a network device, such as a router or switch, that is configured to provide application-oriented network (“AON”) services. Some preferred implementations of the invention provide policy-based application services for RFID data, such as conditional routing, security (encryption, identification, authentication and authorization), data translation and/or transformation, data compression, data caching, etc. Some preferred implementations can interpret an application request and route to an appropriate network address of an RFID reader. Preferably, ALE (application-level event) aggregation and filtering can also be performed on behalf of the application. Some methods of the invention allow event data to be sent to applications (including but not limited to business applications) as request-response messages. Other methods of the invention allow event data to be sent to applications in the form of asynchronous notifications.
Metadata
Assignee
- Cisco Technology, Inc.
Inventors
- Rajiv Singhal
- Christopher Wiborg
Application Information
Application Number:US 11/195,160
Filing Date:2005-08-01
Priority Date:2005-08-01
Art Unit:2612
Classifications
IPC:
G08B13/14
Patent Drawings (13 sheets)
Description
Cross-References to Related Applications
[0001] This application is related to U.S. patent application Ser. No. 11/005,978, entitled “Performing Message Payload Processing Functions in a Network Element on Behalf of an Application” and filed on Dec. 6, 2004, in U.S. patent application Ser. No. 11/089,794, entitled “Method and Apparatus Providing High-Speed Processing of Structured Application Messages in a Network Device” and filed on Mar. 24, 2005 and in U.S. patent application Ser. No. 11/090,920, entitled “Method and Apparatus for Generating a Network Topology Representation Based on Inspection of Application Messages at a Network Device” and filed on Mar. 24, 2005 (collectively, the “AON Applications”), which are hereby incorporated by reference for all purposes.
Background of the Invention
[0002] 1. Field of the Invention
[0003] The present invention relates intermediate-level devices in networks involving multiple data reads over time, including but not limited to sensor networks and RFID networks. More particularly, the invention relates to middleware servers in RFID networks.
[0004] 2. Description of the Related Art
[0005] “Smart labels,” generally implemented by RFID tags, have been developed in an effort to address the shortcomings of bar codes and add greater functionality. RFID tags have been used to keep track of items such as airline baggage, items of clothing in a retail environment, cows and highway tolls. As shown in FIG. 1 , an RFID tag 100 includes microprocessor 105 and antenna 110. In this example, RFID tag 100 is powered by a magnetic field 145 generated by an RFID reader 125. The tag's antenna 110 picks up the magnetic signal 145. RFID tag 100 modulates the signal 145 according to information coded in the tag and transmits the modulated signal 155 to the RFID reader 125.
[0006] Most RFID tags use one of the Electronic Product Code (“EPC” or “ePC”) formats for encoding information. EPC codes may be formed in various lengths (common formats are 64, 96 and 96+ bits) and have various types of defined fields, which allow for identification of, e.g., individual products as well as associated information. These formats are defined in various documents in the public domain. One such document is EPC Tag Data Standards Version 1.1 Rev 1.24 (EPCglobal® 2004), which is hereby incorporated by reference for all purposes.
[0007] One exemplary RFID tag format is shown in FIG. 1 . Here, EPC 120 includes header 130, EPC Manager field 140, Object class field 150 and serial number field 160. EPC Manager field 140 contains manufacturer information. Object class field 150 includes a product's stock-keeping unit (“SKU”) number. Serial number field 160 is a 40-bit field that can uniquely identify the specific instance of an individual product i.e., not just a make or model, but also down to a specific “serial number” of a make and model.
[0008] In theory, RFID tags and associated RFID devices (such as RFID readers and printers) could form part of a network for tracking a product (or a group of products) and its history. However, various difficulties have prevented this theory from being realized. One problem that has required considerable time and energy from RF engineers is the development of lower-cost RFID tags with acceptable performance levels. RFID devices have only recently been deployed with network interfaces.
[0009] In part because of the significant efforts that have been expended in solving the foregoing problems, prior art systems and methods for networking RFID devices are rather primitive. Many uncertainties remain regarding the functionality and implementation of RFID networks. Although EPCglobal has emerged as a de facto standards body, data standards are still evolving and form factors for many solutions are unclear.
[0010] However, some general outlines of a solution appear to be taking shape. It is envisioned that a single facility (e.g., a warehouse, factory, retail outlet, etc.) may have a large number of RFID readers. Such RFID readers may be installed on or near shipping/receiving dock doors, forklifts, shelves, etc. Each RFID reader may transmit a large number of “reads,” many of which will be redundant. Due to the nature of the data gathering and sharing process, a hierarchy of middleware, edge servers/event processing engines and information services are likely to be deployed for all large RFID networks. “The EPCglobal Architecture Framework” (EPCglobal Final Version of 1 Jul. 2005) is hereby incorporated by reference for all purposes.
[0011] Accordingly, it is generally agreed that it would be desirable for most RFID networks to use “middleware” to perform functions such as data collection, filtering, aggregation and reporting of tag reads from physical RFID readers to higher-level applications. It would appear to be generally desirable that filtering and processing of information (e.g., of RFID reads) should occur as close to the network edge as possible, for bandwidth optimization, manageability, security, etc. However, many RFID devices and related network devices are deployed in a hostile industrial environment (such as a warehouse or factory) by relatively unskilled “IT” personnel. RFID devices and related network devices may not perform well in such rugged environments. Moreover, existing RFID middleware servers generally provide low levels of data security (if any).
[0012] It would be desirable to address at least some of these shortcomings of the prior art.
Summary of the Invention
[0013] Some embodiments of the present invention provide middleware functionality integrated into a module of a network device, such as a router or switch, that is configured to provide application-oriented network (“AON”) services. Some such implementations include two interface types. The first type is a downstream interface with multiple Readers in a warehouse, a store, etc. The second type is an upstream interface with business applications, a Warehouse Management Server (“WMS”) and/or an EPC information services (“EPCIS”) server. Some preferred implementations of the invention provide policy-based application services for RFID data, such as conditional routing, security (encryption, identification, authentication and authorization), data translation and/or transformation, data compression, data caching, etc.
[0014] Some preferred embodiments of the invention can abstract out vendor-specific reader implementations and can provide reader service virtualization (e.g., virtualization of a plurality of RFID readers at or near a particular location). Some preferred implementations can interpret an application request and route to an appropriate network address of an RFID reader. Preferably, ALE (application-level event) aggregation and filtering can also be performed on behalf of the application. Some methods of the invention allow event data to be sent to applications (including but not limited to business applications) as request-response messages. Other methods of the invention allow event data to be sent to applications in the form of asynchronous notifications. Preferred implementations route and deliver event information to application subscribers in the appropriate format.
[0015] Some implementations of the invention provide methods for controlling a network. One such method includes these steps: receiving a message relating to an RFID device network or a sensor network; determining an application layer protocol that was used to transmit the message; determining a message termination technique that is associated with the application layer protocol; determining the message contents, based at least in part on the message termination technique; and performing at least one action according to the message contents.
[0016] The method may include the step of determining a message classification that is associated with criteria satisfied by the message. At least one action may be performed according to the message classification. For example, the action may involve applying a rule to initiate a predetermined sequence of operations. The predetermined sequence of operations may be performed at a predetermined time interval.
[0017] The action may involve obtaining information from the RFID network. For example, the action may involve making an RFID read request to at least one RFID reader. The information may pertain to an indicated manufacturer, an indicated location, an indicated product type and/or an indicated time period. The method may include the steps of identifying and authenticating a sender of the message.
[0018] The methods of the present invention may be implemented, at least in part, by hardware and/or software. For example, some embodiments of the invention provide computer programs embodied in machine-readable media. The computer programs include instructions for controlling one or more devices to perform the methods described herein.
[0019] For example, some embodiments of the invention provide a network device, comprising: a first plurality of network interfaces configured for communication with a plurality of RFID readers; an application layer event (“ALE”) adapter for processing reads from the RFID readers; a second network interface configured for communication with networked devices executing RFID-related applications; and an AON module. The AON module may be implemented, for example in a line card. The AON module may be configured to perform the following steps: receive a first ALE request from one of the networked devices; preprocess the first ALE request; issue a second ALE request to the ALE adapter; and process an ALE response from the ALE adapter.
[0020] The ALE adapter may be further configured to make read requests to one or more selected RFID readers of the plurality of RFID readers and to create the ALE response according to at least one RFID read.
[0021] The preprocessing step may involve identifying and authenticating a sender of the first ALE request. The step of processing the ALE response may include generating a notification to one or more of the networked devices when the ALE response comprises one of a set of predetermined ALE responses.
[0022] The AON module may be further configured to perform the following steps: determining a first application layer protocol that was used to transmit the first ALE request; determining a message termination technique that is associated with the first application layer protocol; and determining message contents of the first ALE request, based at least in part on the message termination technique. The AON module may be further configured to form the second ALE request according to a second application layer protocol different from the first application layer protocol. The first ALE request may be classified based on a uniform resource identifier of the first ALE request.
Brief Description of the Drawings
[0023] FIG. 1 is a diagram illustrating an RFID tag.
[0024] FIG. 2A is a flow chart that illustrates one example of a method that can be used to implement the present invention.
[0025] FIG. 2B is a block diagram that illustrates one embodiment of a network device that can be configured to perform some methods of the present invention.
[0026] FIGS. 3A and 3B illustrate a flow chart that outlines another method that can be used to implement the present invention.
[0027] FIG. 4 is a flow chart that outlines still another method that can be used to implement the present invention.
[0028] FIG. 5 is a flow chart that outlines a filtering method that can be used to implement the present invention.
[0029] FIG. 6 illustrates an RFID edge server architecture and network traffic flow according to some implementations of the present invention.
[0030] FIG. 7 illustrates some components of a network device configured according to some implementations of the present invention and examples of how these components can communicate with other devices.
[0031] FIG. 8 illustrates an internal message flow for ALE Request/Response messages in a network device configured according to some implementations of the present invention.
[0032] FIG. 9 illustrates an internal message flow for ALE notification messages in a network device configured according to some implementations of the present invention.
[0033] FIG. 10 illustrates another example of a network device that may be configured to implement some methods of the present invention.
Detailed Description of the Invention
[0034] In this application, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be obvious, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order not to obscure the present invention.
[0035] A number of other applications filed on behalf of the present assignee, including U.S. patent application Ser. No. 10/866,506, entitled “Methods and Devices for Uniquely Provisioning RFID Devices” and filed on Jun. 9, 2004, to U.S. patent application Ser. No. 10/866,507, entitled “Methods and Devices for Locating and Uniquely Provisioning RFID Devices” and filed on Jun. 9, 2004, to U.S. patent application Ser. No. 10/866,285, entitled “Methods and Devices for Assigning RFID Device Personality” and filed on Jun. 9, 2004, to U.S. patent application Ser. No. 11/010,089, entitled “Methods and Devices for Providing Scalable RFID Networks” and filed on Dec. 9, 2004, to U.S. patent application Ser. No. 11/119,169, filed on Apr. 29, 2005 , entitled “Locating and Provisioning Devices in a Network” and to U.S. patent application Ser. No. 11/129,709, filed on May 12, 2005 , entitled “Locating, Provisioning and Identifying Devices in a Network” (collectively, the “RFID Applications”), describe subject matter relevant to this application. Accordingly, all of the RFID Applications are hereby incorporated by reference for all purposes.
[0036] While the present invention involves methods and devices that may be employed in RFID networks, many aspects of the present invention can be applied to other types of networks. For example, the present invention may also be used in manufacturing networks, sensor device networks, etc. Similarly, although much of the discussion herein applies to network devices that are implemented as described in one or more of the AON Applications, the present invention is not device-specific.
[0037] However, many preferred implementations of the invention are based on AON methods and devices, some of which are described in detail in the AON Applications that have been incorporated by reference herein. Because this technology is fundamental to many such implementations of the invention, a brief overview of AON methods and devices is set forth in the following paragraphs. Please note that the AON Applications use the phrase Application-Oriented Network Systems or the corresponding acronym “AONS” instead of the acronym “AON”; accordingly, these terms and acronyms will be used synonymously herein.
[0038] AON is a technology foundation for building a class of products that embed intelligence into the network to better meet the needs of application deployment. AON complements existing networking technologies by providing a greater degree of awareness of what information is flowing within the network and helping customers to integrate disparate applications by routing information to the appropriate destination, in the format expected by that destination; enforce policies for information access and exchange; optimize the flow of application traffic, both in terms of network bandwidth and processing overheads; provide increased manageability of information flow, including monitoring and metering of information flow for both business and infrastructure purposes; and provide enhanced business continuity by transparently backing up or re-routing critical business data.
[0039] AON provides this enhanced support by understanding more about the content and context of information flow. As such, AON works primarily at the message rather than at the packet level. In some implementations, AON processing of information terminates a TCP connection to inspect the full message, including the “payload” as well as all headers. AON also understands and assists with popular application-level protocols such as HTTP, FTP, SMTP and MOM protocols.
[0040] AON differs from middleware products running on general-purpose computing systems in that AON's behavior is more akin to a network appliance, in its simplicity, manageability, total cost of ownership and performance. Furthermore, AON integrates with network-layer support to provide a more holistic approach to information flow and management, mapping required features at the application layer into low-level networking features implemented by routers, switches, firewalls and other networking systems.
[0041] In one embodiment, an underlying “AON foundation platform of subsystem services” (AOS) provides a range of general-purpose services including support for security, compression, caching, reliability, policy management and other services. On top of this platform, AON then offers a range of discreet functional components that can be wired together to provide the overall processing of incoming data traffic. These “bladelets™” are targeted at effecting individual services in the context of the specific policy or action demanded by the application or the information technology (IT) manager. A series of access method adapters ensure support for a range of ingress and egress formats. Finally, a set of user-oriented tools enable managers to appropriately view, configure and set policies for the AON solution. These four categories of functions combine to provide a range of end-customer capabilities including enhanced security, infrastructure optimization, business continuity, application integration and operational visibility.
[0042] The enhanced visibility and enhanced responsiveness enabled by AON solutions provides a number of intelligent, application-oriented network services. These intelligent services can be summarized in four primary categories:
[0043] Enhanced security and reliability: enabling reliable message delivery and providing message-level security in addition to existing network-level security.
[0044] Infrastructure optimization: making more efficient use of network resources by taking advantage of caching and compression at the message level as well as by integrating application and network quality-of-service (QoS).
[0045] Business and infrastructure activity monitoring and management: by reading information contained in the application layer message, AON can log, audit, and manage application-level business events, and combine these with network, server, and storage infrastructure events in a common, policy-driven management environment.
[0046] Content-based routing and transformation: message-based routing and transformation of protocol, content, data, and message formats (e.g., XML transformation). Some individual features belonging to each of these primary categories are described elsewhere herein and are described in greater detail in the AON Applications.
[0047] Flow chart 200 of FIG. 2A illustrates an overview of one embodiment of a method of performing message payload processing functions at a network element on behalf of a client application. Such a method may be performed, for example, by one or more blades of a middleware server that is in communication with a plurality of RFID readers and one or more networked devices that are running applications, e.g., one or more application servers, host devices, etc. According to some implementations of the invention, the “network element” may be a middleware server, one or more blades of a middleware server, etc. However, the method outlined by flow chart 200 and other methods described herein have broad applicability outside of the RFID context. For example, the methods may be performed by a variety of network devices that are in communication with devices (including but not limited to host devices) running client applications and other devices running server applications, as described with reference to FIG. 1 of U.S. patent application Ser. No. 11/005,978, the parent AON Application. The methods described herein are also particularly useful for devices that are in communication with a sensor network and with devices running applications relating to the sensor networks and/or that could be alerted, informed, take action, etc., according to input from the sensor network.
[0048] In block 202, a network element receives user-specified input. The user-specified input indicates a message classification and one or more actions that are associated with the message classification. For example, a middleware server may receive such user-specified input from a network administrator, from a host device or from an application.
[0049] The message classification defines a category or class of messages. In one example, all purchase orders belong to the same message classification. In an RFID-related example, a class of messages could pertain to a particular product type, manufacturer ID, etc., that could be determined from RFID reads. In another RFID-related example, a class of messages could pertain to RFID reads from a particular location. Other such examples will be described below. Messages that satisfy user-specified criteria or rules associated with the message classification belong to the message classification, while messages that do not satisfy these criteria or rules do not belong to the message classification.
[0050] In block 204, the network element receives one or more data units, such as data packets. As used herein the terms “packet,” “data packet” and the like will include not only such data units as TCP/IP packets but will also include data units from an RFID reader (also referred to herein as “raw reads” and the like). For example, a network element may intercept one or more data packets that are destined for another device in the network. For another example, a network element may receive one or more data packets that are directed to that network element.
[0051] The network element is preferably capable of determining application layer message boundaries. In one embodiment, a network element may perform operations on an application layer message contained in a stream, or portions thereof, even if the network element has not yet received all of the data packets that contain all of the portions of the application layer message.
[0052] In block 206, based on the data packets, it is determined that an application layer message collectively contained in payload portions of the data packets belongs to the particular message classification. For example, a network element may assemble at least some of the data packets. The network element may inspect the contents of the payload portions of the assembled data packets to determine at least a portion of an application layer message that a client application is trying to send. The message may be, for example, formatted according to XML and transmitted using HTTP. As such, the message may contain HTTP and XML headers. Based on the message content and/or information in the data packet headers, the network element may determine that the message belongs to the particular message classification indicated in the user-specified input. For example, the network element may determine, based on a portion of the message, that the message is a purchase order. In another example, the network element may determine that the message pertains to information desired by an application from an RFID network or a sensor network.
[0053] In block 208, at least a portion of the message is processed via the performance, relative to at least the portion of the message, of the actions that are associated with the particular message classification. For example, in response to determining that the message belongs to the “purchase order” message classification, the network element may perform one or more specified actions that are associated with the “purchase order” message classification. The specified actions may include, for example, modifying the message's format (e.g., from XML to EDI) and sending the message toward a server application using a different application layer protocol (e.g., FTP) than the protocol that a client application used to send the message. Examples of other possible actions are described below.
[0054] According to one embodiment, an AON blade in a router or a switch performs at least some of the actions discussed above. FIG. 2B is a block diagram that illustrates one embodiment of a router 250 in which a supervisor blade 252 directs some of packet flows 210A-B to an AON blade and/or other blades 256N. Router 250 comprises supervisor blade 252, AONS blade 254, and other blades 256A-N. Each of blades 252, 254, and 256A-N is a single circuit board populated with components such as processors, memory, and network connections that are usually found on multiple boards. Blades 252, 254, and 256A-N are designed to be addable to and removable from router 250. The functionality of router 250 is determined by the functionality of the blades therein. Adding blades to router 250 can augment the functionality of router 250, but router 250 can provide a lesser degree of functionality with fewer blades at a lesser cost if desired. One or more of the blades may be optional.
[0055] Router 250 receives packet flows such as packet flows 210A-B. More specifically, in one embodiment, packet flows 210A-B received by router 250 are received by supervisor blade 252. Supervisor blade 252 may comprise a forwarding engine and/or a route processor such as those commercially available from Cisco Systems, Inc. In an alternative embodiment, router 250 comprises one or more network I/O modules that may comprise a forwarding engine; in such an alternative embodiment, the operations described below as being performed by supervisor blade 252 are performed instead by a forwarding engine that is not situated within supervisor blade 252, so that packets may be forwarded to AONS blade 254 without ever going through supervisor blade 252.
[0056] In one embodiment, supervisor blade 252 classifies packet flows 210A-B based on one or more parameters contained in the packet headers of those packet flows. If the parameters contained in the packet header of a particular packet match specified parameters, then supervisor blade 252 sends the packets to a specified one of AONS blade 254 and/or other blades 256A-N. Alternatively, if the parameters contained in the packet header do not match any specified parameters, then supervisor blade 252 performs routing functions relative to the particular packet and forwards the particular packet on toward the particular packet's destination.
[0057] For example, supervisor blade 252 may determine that packet headers in packet flow 210B match specified parameters. Consequently, supervisor blade 252 may send packets in packet flow 210B to AONS blade 254. Supervisor blade 252 may receive packets back from AONS blade 254 and/or other blades 256A-N and send the packets on to the next hop in a network path that leads to those packets' destination. For another example, supervisor blade 252 may determine that packet headers in packet flow 210A do not match any specified parameters. Consequently, without sending any packets in packet flow 210A to AONS blade 254 or other blades 256A-N, supervisor blade 252 may send packets in packet flow 210A on to the next hop in a network path that leads to those packets' destination.
[0058] AONS blade 254 and other blades 256A-N receive packets from supervisor blade 252, perform operations relative to the packets, and return the packets to supervisor blade 252. Supervisor blade 252 may send packets to and receive packets from multiple blades before sending those packets out of router 250. For example, supervisor blade 252 may send a particular group of packets to other blade 256A. Other blade 256A may perform firewall functions relative to the packets and send the packets back to supervisor blade 252. Supervisor blade 252 may receive the packet from other blade 256A and send the packets to AONS blade 254. AONS blade 254 may perform one or more message payload-based operations relative to the packets and send the packets back to supervisor blade 252.
[0059] According to one embodiment, the following events occur at an AON router such as router 250. First, packets, containing messages from clients to servers, are received. Next, access control list-based filtering is performed on the packets and some of the packets are sent to an AON blade or module. Next, TCP termination is performed on the packets. Next, Secure Sockets Layer (SSL) termination is performed on the packets if necessary. Next, Universal Resource Locator (URL)-based filtering is performed on the packets. Next, message header-based and message content-based filtering is performed on the packets. Next, the messages contained in the packets are classified into AON message types. Next, a policy flow that corresponds to the AON message type is selected. Next, the selected policy flow is executed. Then the packets are either forwarded, redirected, dropped, copied, modified, or fanned-out as specified by the selected policy flow. As with other flows illustrated herein, the foregoing steps are not necessarily performed in the order indicated.
[0060] FIGS. 3A and 3B depict a flow diagram 300 that illustrates one embodiment of a method of performing message payload processing functions at a network element on behalf of an application. For example, AONS blade 254 may perform one or more steps of such a method. Other embodiments may omit one or more of the operations depicted in flow diagram 300. Other embodiments may contain operations additional to the operation depicted in flow diagram 300. Other embodiments may perform the operations depicted in flow diagram 300 in an order that differs from the order depicted in flow diagram 300.
[0061] Referring first to FIG. 3A , in block 302, user-specified input is received at a network element. The user-specified input indicates the following: one or more criteria that are to be associated with a particular message classification, and one or more actions that are to be associated with the particular message classification. The user-specified input may indicate an order in which the one or more actions are to be performed. The user-specified input may indicate that outputs of actions are to be supplied as inputs to other actions. For example, AONS blade 254 may receive such user-specified input from a network administrator.
[0062] The user-specified input may indicate multiple sets of criteria that are to be associated, respectively, with multiple separate message classifications, and multiple sets of actions that are to be associated with the multiple message classifications. For example, the user-specified input may indicate a first set of criteria that is to be associated with a first message classification, a second set of criteria that is to be associated with a second message classification, a first set of actions that are to be associated with the first message classification, and a second set of actions that are to be associated with the second message classification.
[0063] In block 304, an association is established, at the network element, between the particular message classification and the one or more criteria. For example, AONS blade 254 may establish an association between a particular message classification and one or more criteria. For example, the criteria may indicate a particular string of text that a message needs to contain in order for the message to belong to the associated message classification. For another example, the criteria may indicate a particular path that needs to exist in the hierarchical structure of an XML-formatted message (or based in an XPath Boolean expression) in order for the message to belong to the associated message classification. For another example, the criteria may indicate one or more source IP addresses and/or destination IP addresses from or to which a message needs to be addressed in order for the message to belong to the associated message classification.
[0064] Multiple associations may be established between separate sets of criteria and separate message classifications. For example, AONS blade 254 may establish a first association between a first set of criteria and a first message classification, and a second association between a second set of criteria and a second message classification.
[0065] In block 306, an association is established, at the network element, between the particular message classification and the one or more actions. One or more actions that are associated with a particular message classification comprise a “policy” that is associated with that particular message classification. A policy may comprise a “flow” of one or more actions that are ordered according to a particular order specified in the user-specified input, and/or one or more other actions that are not ordered. For example, AONS blade 254 may establish an association between a particular message classification and one or more actions. Collectively, the operations of blocks 302-306 comprise “provisioning” the network element.
[0066] Multiple associations may be established between separate sets of actions and separate message classifications. For example, AONS blade 254 may establish a first association between a first set of actions and a first message classification, and a second association between a second set of actions and a second message classification.
[0067] In block 308, one or more data packets that are destined for a device other than the network element are received by the network element. The data packets may be, for example, data packets that contain IP and TCP headers. The IP addresses indicated in the IP headers of the data packets may differ from the network element's IP address; thus, the data packets may be destined for a device other than the network element. For example, supervisor blade 252 may intercept data packets that a client application originally sent. The data packets might be destined for a server application, for example.
[0068] In block 310, based on one or more information items indicated in the headers of the data packets, an application layer protocol that was used to transmit a message contained in the payload portions of the data packets (hereinafter “the message”) is determined. The information items may include, for example, a source IP address in an IP header, a destination IP address in an IP header, a TCP source port in a TCP header, and a TCP destination port in a TCP header. For example, a network element, and more specifically AONS blade 254, may store mapping information that maps FTP (an application layer protocol) to a first combination of IP addresses and/or TCP ports, and that maps HTTP (another application layer protocol) to a second combination of IP addresses and/or TCP ports. Based on this mapping information and the IP addresses and/or TCP ports indicated by the data packets, network element may determine which application layer protocol (FTP, HTTP, Simple Mail Transfer Protocol (SMTP), etc.) was used to transmit the message.
[0069] In block 312, a message termination technique that is associated with the application layer protocol used to transmit the message is determined. For example, AONS blade 254 may store mapping information that maps FTP to a first procedure, that maps HTTP to a second procedure, and that maps SMTP to a third procedure. The first procedure may employ a first message termination technique that can be used to extract, from the data packets, a message that was transmitted using FTP. The second procedure may employ a second message termination technique that can be used to extract, from the data packets, a message that was transmitted using HTTP. The third procedure may employ a third message termination technique that can be used to extract, from the data packets, a message that was transmitted using SMTP. Based on this mapping information and the application layer protocol used to transmit the message, a network element may determine which procedure should be called to extract the message from the data packets.
[0070] In block 314, the contents of the message are determined based on the termination technique that is associated with the application layer protocol that was used to transmit the message. For example, AONS blade 254 may provide the data packets as input to a procedure that is mapped to the application layer protocol determined in block 312. The procedure may use the appropriate message termination technique to extract the contents of the message from the data packets. The procedure may return the message as output to AONS blade 254. Thus, in one embodiment, the message extracted from the data packets is independent of the application layer protocol that was used to transmit the message.
[0071] In one embodiment, determining the contents of the message involves assembling the contents of the payload portions of two or more of the data packets. For example, a network element may determine the proper order of two or more TCP data packets (based on TCP sequence numbers, for example), extract the contents of the payload portions of the TCP data packets, and concatenate the contents according to the proper order to form at least a portion of the message. The message may be a multi-part (MIME) message, and each part may be handled separately as though it were a separate message; each part may be associated with a different message classification.
[0072] In block 316, a message classification that is associated with criteria that the message satisfies is determined. For example, a network element may store mapping information that maps different criteria to different message classifications. The mapping information indicates, among possibly many different associations, the association established in block 304. The network element may determine whether the contents of the message satisfy criteria associated with any of the known message classifications. In one embodiment, if the contents of the message satisfy the criteria associated with a particular message classification, then it is determined that the message belongs to the particular message classification.
[0073] Although, in one embodiment, the contents of the message are used to determine a message's classification, in alternative embodiments, information beyond that contained in the message may be used to determine the message's classification. For example, in one embodiment, a combination of the contents of the message and one or more IP addresses and/or TCP ports indicated in the data packets that contain the message is used to determine the message's classification. For another example, in one embodiment, one or more IP addresses and/or TCP ports indicated in the data packets that contain the message are used to determine the message's classification, regardless of the contents of the message.
[0074] In block 318, one or more actions that are associated with the message classification determined in block 316 are performed. If two or more of the actions are associated with a specified order of performance, as indicated by the user-specified input, then those actions are performed in the specified order. If the output of any of the actions is supposed to be provided as input to any of the actions, as indicated by the user-specified input, then the output of the specified action is provided as input to the other specified action.
[0075] A variety of different actions may be performed relative to the message. For example, an action might indicate that the message is to be dropped. In this case, the message is prevented from being forwarded out of the network element toward that message's destination. For another example, an action might indicate that a message is to be compressed using a specified compression technique before being forwarded out of the network element.
[0076] For another example, an action might indicate that the content of the message is to be altered in a specified manner. For example, an action might indicate that specified text is to be inserted into a specified location in the message. A path in an XML hierarchical structure of the message might specify such a location, for example, or a specified string of text occurring in the message might specify such a location. For another example, an action might indicate that specified text is to be deleted from the message. For another example, an action might indicate that specified text is to be substituted for other specified text in the message. Text inserted into the message might be obtained dynamically (“on the fly”) from a database that is external to the network element.
[0077] For another example, an action might indicate that the message format of a message is to be altered in a specified manner. For example, an action might indicate that a message's format is to be changed from XML to some other format such as EDI. For another example, an action might indicate that a message's format is to be changed from some format other than XML into XML. The message format may be altered without altering the core content of the message, which is independent of the message format.
[0078] For another example, an action might indicate that the message is to be forwarded using a specified application layer protocol other than the application layer protocol that the message's origin used to transmit the message. For example, a client application might have used a first application layer protocol, such as HTTP, to transmit the message. Thus, when intercepted by supervisor blade 252, the message might have contained an HTTP header. However, in accordance with a specified action, before the network element forwards the message towards the message's destination, the network element, and more specifically AONS blade 254, may modify the message so that the message will be carried using an application layer protocol other than HTTP (such as FTP, SMTP, etc.).
[0079] For another example, an action might indicate that the message's destination is to be altered so that the message will be forwarded towards a device that is different from the device that the message's source originally specified. For example, in accordance with a specified action, a network element, and more specifically AONS blade 254, might encapsulate the message in one or more new IP data packets that indicate a new destination IP address that differs from the destination IP address that originally intercepted IP data packets indicated. The network element may then forward the new IP data packets toward the new destination. In this manner, message content-based routing may be achieved.
[0080] For another example, an action might indicate that a specified event is to be written into a specified log that might be external to the network element. For example, in accordance with a specified action, AONS blade 254 might write at least a portion of the message, along with the IP address from which the message was received, to a log file.
[0081] For another example, an action might indicate that the message is to be encrypted using a specified key before being forwarded to a destination. For example, in accordance with a specified action, AONS blade 254 might encrypt at least a portion of the message using a specified key and then forward data packets that contain the encrypted message towards the message's destination. Encryption also places a constraint on the subsequent action (e.g., a constraint that the encrypted portion cannot be modified).
[0082] For another example, an action might indicate that a response cached at the network element is to be returned to the device from which the message originated, if such a response is cached at the network element. For example, a network element may determine whether a response to the message is cached at the network element; such a response might have be cached at the network element at the time a previous response to the same message passed through the network element. If the network element determines that such a response is cached, then the network element may return the response to the message's origin. For read-only operations without any persistent state change, the network element does not need to forward the message to the message's destination and the message's destination does not need to issue another response to the message.
[0083] For another example, an action might indicate that some authentication information in the message, such as a user identifier and associated password, is to be used to authenticate the message. For example, AONS blade 254 might authenticate a message by comparing authentication information in the message with trusted information stored by router 250.
[0084] If the message was modified in some way (e.g., content, format, or protocol modification) during the performance of the actions, and if the modified message is supposed to be forwarded out of the network element, then the network element encapsulates the modified message into new data packets and sends the new data packets towards the modified message's destination which also might have been modified.
[0085] A message might not belong to any known message classification. In this case, according to one embodiment, the network element does not perform any user-specified actions relative to the message. Instead, the network element simply forwards the data packets to the next hop along the path to the data packets' indicated destination.
[0086] The method illustrated in flow diagram 300 may be performed relative to multiple sets of data packets, each set carrying a separate message. For example, a network element may perform the method illustrated relative to a first set of data packets that carry a first message, and then may perform the method relative to a second set of data packets that carry a second message. The first message might satisfy a first set of criteria associated with a first message classification, and the second message might satisfy a second set of criteria associated with a second message classification. Thus, a network element might perform a first set of actions relative to the first message and a second set of actions relative to the second message.
[0087] As a result of the method illustrated in flow diagram 300, applications can communicate with each other as though no network elements acted as intermediaries and as though each other application communicated using the same message format and application layer protocol.
[0088] FIG. 4 depicts a sample flow 400 that might be associated with a particular message classification. Flow 400 comprises, in order, actions 402-414; other flows may comprise one or more other actions. Action 402 indicates that the content of the message should be modified in a specified manner. Action 404 indicates that a specified event should be written to a specified log. Action 406 indicates that the message's destination should be changed to a specified destination. Action 408 indicates that the message's format should be translated into a specified message format. Action 410 indicates that the application layer protocol used to transmit the message or content should be changed to a specified application layer protocol. Action 412 indicates that the message or content should be encrypted using a particular key. Action 414 indicates that the message should be forwarded towards the message's destination. Other actions might include signing and verification actions, for example.
[0089] In other embodiments, any one of actions 402-414 may be performed individually or in combination with any others of actions 402-414.
[0090] Typically, inspecting, parsing, and modifying an application layer message is a processing resource-intensive operation that cannot be performed as quickly as routing operations that are based only on information in TCP and IP packet headers. Referring again to FIG. 2B , using packet level processing rather than message level processing, supervisor blade 252 might be able to process and send packets to AONS blade 254 faster than AONS blade 254 can process application layer messages contained within those packets. Indeed, there might be some packets that contain application layer messages that AONS blade 254 does not need to process at all. Sending such packets to AONS blade 254 would only waste processing resources and cause packet buffers of AONS blade 254 to become backed up with packets.
[0091] Therefore, in one embodiment, supervisor blade 252 sends only some selected packets to AONS blade 254. The technique by which supervisor blade 252 selects these packets may be referred to as “filtering.” As a result of filtering, AONS blade 254 does not receive as many packets with which AONS blade 254 is likely to do nothing.
[0092] FIG. 5 depicts a flow diagram 550 that illustrates one embodiment of a method of filtering packets for which message level processing is to be performed. In block 552, it is determined whether information contained in a layer 2-4 header of a packet or frame satisfies specified criteria. The criteria might specify particular sources and/or particular destinations that packets need to be coming from and/or going to in order to merit message level processing. For example, supervisor blade 252 might determine whether a combination of one or more of a packet's source IP address, source TCP port, destination IP address, and destination TCP port match any user-specified combinations of these addresses and ports. If the header information satisfies the specified criteria, then control passes to block 554. Otherwise, control passes to block 556.
[0093] In block 554, the packet is sent to an AONS blade. For example, supervisor blade 252 may direct the packet to AONS blade 254. AONS blade 254 may then perform more resource-intensive message level processing on an application layer message that is at least partially contained in the packet.
[0094] Alternatively, in block 556, the packet is forwarded on towards the packet's destination. For example, supervisor blade 252 may route the packet toward the packet's next hop without sending the packet to AONS blade 254. Message level processing is not performed on the packet.
[0095] FIG. 6 illustrates a simplified portion of an RFID network that depicts one exemplary implementation of the present invention. Here, supplier headquarters 600 includes host devices 602 and network device 604. Supplier headquarters 600 has transmitted an advance shipping notice 605 to retailer headquarters 650. In this example, advance shipping notice 605 was transmitted via network 607 (which is the Internet in this example) via the EDI AS2 standard. Here, retailer headquarters 650 includes host devices 652 and network device 654. These devices may be used, inter alia, to implement enterprise resource planning (“ERP”) applications for retailer headquarters 650.
[0096] Pallet 610 has been delivered to dock door 612 of retailer distribution center 615. Pallet 610 includes a number of products, each bearing an RFID tag 615. RFID tags 615 have been read by RFID readers 620. Accordingly, reader events 625 have been transmitted via switches 630 to AON-enabled network device 635. Some exemplary embodiments of device 635 will be discussed in more detail below.
[0097] Device 635 may perform various important functions as an intermediary between the RFID readers and various applications. For example, device 635 may be configured to provide logical to physical RFID reader location resolution for the applications. In one such example, all of the RFID readers 620 that are positioned near dock door 612 may be virtualized into a single virtual RFID reader. This provides a convenient method for applications to request all reads from dock door 612. Preferred embodiments of device 635 also provide application level event (“ALE”) filtering. Such virtualization and filtering may be provided by an ALE adapter provided by a vendor such as ConnecTerra, Inc. Alternatively, such virtualization and filtering may be provided according to novel methods of the invention.
[0098] Device 635 may also perform message translation/transformation, security services, application protocol switching and/or other methods according to the present invention. Examples of some such methods are described below.
[0099] Accordingly, device 635 transmits application events for use by applications at retailer headquarters 650 and elsewhere. For example, such application events may be used as input for applications running on warehouse management server (“WMS”) 660 and/or host 662. Host 662 may be, for example, a monitoring console suitable for monitoring events that take place in retailer distribution center 615. Application events from device 635 may also be used as input for applications running on EPC information services (“EPCIS”) server 670 and/or host 672.
[0100] FIG. 7 is a block diagram that illustrates tasks performed by modules of device 635 according to one implementation of the invention. In this example, device 635 includes modules 705 and 725, which may be deployed on the same physical component (e.g., the same line card) or on separate physical components. In this embodiment, module 705 includes RFID reader drivers 710 for controlling networked RFID readers 720. For example, RFID reader drivers 710 may control one or more of RFID readers 720 according to RFID event cycle specifications received from business applications 740 running on an enterprise network.
[0101] Moreover, module 705 includes ALE adapter 715 for providing various types of ALE functionality. In this example, ALE adapter 715 is configured to perform tasks that include, but are not limited to, filtering of raw RFID reads and RFID reader virtualization. For example, referring again to FIG. 6 , suppose device 635 received a request from retailer headquarters 650 to obtain information regarding the products in pallet 610. ALE adapter 715 could virtualize all physical RFID readers 620 at dock door 612, the dock door to which pallet 610 was delivered, into a single virtual RFID reader for the purpose of obtaining all reads from dock door 612, then use RFID reader drivers 710 to control readers 620 accordingly. The raw RFID reads could then be filtered by ALE adapter 715 according to the information desired.
[0102] Module 725 includes modules, such as conditional routing service module 730 and security service module 735, to provide an interface between devices running business applications 740, monitoring console 750, etc. In this example, security service module 735 can identify and authenticate the sender of a communication, e.g., from one of the business applications 740. In some implementations, security service module 735 can provide encryption and decryption services.
[0103] Conditional routing service module 730 can be configured, for example, to selectively route information to business applications 740 and to monitoring console 750. For example, conditional routing service module 730 may send an alert to monitoring console 750 if certain predetermined conditions are (or are not) occurring. One such condition may be that a valuable item (e.g. a product or a piece of equipment) should not be leaving facility 700. Alternatively, the condition may be that the item should not be leaving in a particular manner, e.g., that the item should not be moved through a particular exit, through an open window, etc. Conditional routing service module 730 can also route RFID event cycle reports from RFID ALE adapter 715 to business applications 740, e.g., based on content. The content may pertain to a location, a product type, a manufacturer type and/or to other criteria that may be indicated, for example, in a prior message from one of business applications 740. For example, the prior message may have included a request for all RFID reads of items on a particular shelf. Alternatively, or additionally, the prior message may have requested of all products in a particular area that were made by a particular manufacturer and/or are a particular product type, as indicated on the RFID tag of the product. For example, the message may have requested information only regarding dishwashing detergent made by Proctor & Gamble.
[0104] In this example, module 725 provides other functions such as the parsing and translating of messages from the devices running business applications 740. In some preferred implementations of the invention, module 725 is also configured to communicate with business applications 740 according to a first application protocol and to communicate with ALE adapter 715 according to a second protocol. For example, messages from business applications 740 may be provided according to the first application protocol and responsive communications with ALE adapter 715 may be formed according to a second application protocol. The RFID devices may provide raw reads to ALE adapter 715 according to a third protocol. Although some such methods may be performed generally as described above (e.g., with reference to AONS blade 254), more specific examples are provided below.
[0105] FIG. 8 is a block diagram that indicates the flow of an exemplary ALE request/response according to some implementations of the invention. Here, inbound ALE request 805 is received by module 725 from a business application according to a first application protocol, which is the Simple Object Access Protocol (“SOAP”) in this example. Module 725 terminates request 805 according to the SOAP protocol and classifies request 805, in this example based on the uniform resource identifier. Here, request 805 seeks to determine how much Quaker State™ WD-40 motor oil is currently in stock at a particular store. Module 725 applies a rule to launch a flow that will obtain an appropriate response to request 805.
[0106] In this example, no encryption or decryption is used. However, security service module 735 authenticates request 805 and identifies the sender of request 805.
[0107] Here, module 725 also includes HTTP Adapter 810, which is configured to make an HTTP call to the ALE adapter of module 705 according to request 805. Module 705 makes read requests to the appropriate RFID readers in the vicinity of the shelves of the store where containers of Quaker State™ WD-40 motor oil are stored. The ALE adapter of module 705 aggregates and filters the responsive raw RFID reads received from the RFID readers. The ALE adapter then sends an ALE response, which is once again according to the HTTP protocol, to module 725.
[0108] Conditional routing service module 730 then determines how to route the ALE response, according to information contained in the response. For example, if conditional routing service module 730 determines that a predetermined pattern or condition exists (e.g., that there are more than a certain number of containers of Quaker State™ WD-40 motor oil missing but not paid for), conditional routing service module 730 may send an alert via an IP phone. An HTTP bladelet may be used for this purpose. Outbound ALE response 850 will be sent to the requesting device according to the protocol of the request, which is the SOAP protocol in this instance.
[0109] These steps (as with other flows depicted herein) are not necessarily performed in the sequence indicated in FIG. 8 . For example, the identification and authentication steps may be performed before any other actions are taken.
[0110] FIG. 9 illustrates a flow for processing ALE notification messages according to alternative methods of the invention. The flow illustrated in FIG. 9 may be initiated, for example, according to a standing request. The request could be from a network manager, from a business application, etc. For example, the request could be for RFID reads to occur in a specified area on a periodic basis, e.g., every 5 minutes, once per day, etc. Read request 905 has been sent according to one such procedure, utilizing RFID reader drivers of device 635.
[0111] Responsive RFID tag reads are received, aggregated and filtered by ALE adapter 915. In this example, message execution controller 920 finds a pattern that indicates a reporting condition. Accordingly, an alert is sent to an IP phone using an HTTP bladelet. In this example, device 635 also encrypts a reporting message and sends the reporting message to an application. Here, the application is running on a device in an enterprise network at another location.
[0112] FIG. 10 illustrates one example of a network device that may be configured to implement some methods of the present invention. Network device 1060 includes a master central processing unit (CPU) 1062, interfaces 1068, and a bus 1067 (e.g., a PCI bus). Generally, interfaces 1068 include ports 1069 appropriate for communication with the appropriate media. In some embodiments, one or more of interfaces 1068 includes at least one independent processor 1074 and, in some instances, volatile RAM. Independent processors 1074 may be, for example ASICs or any other appropriate processors. According to some such embodiments, these independent processors 1074 perform at least some of the functions of the logic described herein. In some embodiments, one or more of interfaces 1068 control such communications-intensive tasks as media control and management. By providing separate processors for the communications-intensive tasks, interfaces 1068 allow the master microprocessor 1062 efficiently to perform other functions such as routing computations, network diagnostics, security functions, etc.
[0113] The interfaces 1068 are typically provided as interface cards (sometimes referred to as “line cards”). Generally, interfaces 1068 control the sending and receiving of data packets over the network and sometimes support other peripherals used with the network device 1060. Among the interfaces that may be provided are Fibre Channel (“FC”) interfaces, Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided, such as fast Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces, ASI interfaces, DHEI interfaces and the like.
[0114] When acting under the control of appropriate software or firmware, in some implementations of the invention CPU 1062 may be responsible for implementing specific functions associated with the functions of a desired network device. According to some embodiments, CPU 1062 accomplishes all these functions under the control of software including an operating system (e.g. Linux, VxWorks, etc.), and any appropriate applications software.
[0115] CPU 1062 may include one or more processors 1063 such as a processor from the Motorola family of microprocessors or the MIPS family of microprocessors. In an alternative embodiment, processor 1063 is specially designed hardware for controlling the operations of network device 1060. In a specific embodiment, a memory 1061 (such as non-volatile RAM and/or ROM) also forms part of CPU 1062. However, there are many different ways in which memory could be coupled to the system. Memory block 1061 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, etc.
[0116] Regardless of network device's configuration, it may employ one or more memories or memory modules (such as, for example, memory block 1065) configured to store data, program instructions for the general-purpose network operations and/or other information relating to the functionality of the techniques described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example.
[0117] Because such information and program instructions may be employed to implement the systems/methods described herein, the present invention relates to machine-readable media that include program instructions, state information, etc. for performing various operations described herein. Examples of machine-readable media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM) and random access memory (RAM). The invention may also be embodied in a carrier wave traveling over an appropriate medium such as airwaves, optical lines, electric lines, etc. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter.
[0118] Although the system shown in FIG. 10 illustrates one specific network device of the present invention, it is by no means the only network device architecture on which the present invention can be implemented. For example, an architecture having a single processor that handles communications as well as routing computations, etc. is often used. Further, other types of interfaces and media could also be used with the network device. The communication path between interfaces/line cards may be bus based (as shown in FIG. 10 ) or switch fabric based (such as a cross-bar).
Other Embodiments
[0119] Although illustrative embodiments and applications of this invention are shown and described herein, many variations and modifications are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those of ordinary skill in the art after perusal of this application.
[0120] Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
We claim:
1. A method of controlling a network, the method comprising:
receiving a message relating to an RFID device network or a sensor network;
determining an application layer protocol that was used to transmit the message;
determining a message termination technique that is associated with the application layer protocol;
determining the message contents, based at least in part on the message termination technique; and
performing at least one action according to the message contents.
2. The method of claim 1, further comprising the step of determining a message classification that is associated with criteria satisfied by the message, wherein at least one action is performed according to the message classification.
3. The method of claim 1, wherein the action comprises applying a rule to initiate a predetermined sequence of operations.
4. The method of claim 1, wherein the action comprises obtaining information from the RFID network.
5. The method of claim 1, further comprising the steps of identifying and authenticating a sender of the message.
6. The method of claim 1, wherein the action comprises making an RFID read request to at least one RFID reader.
7. The method of claim 3, wherein the predetermined sequence of operations are performed at a predetermined time interval.
8. The method of claim 4, wherein the information pertains to least one of an indicated manufacturer, an indicated location, an indicated product type and an indicated time period.
9. A network device, comprising:
a first plurality of network interfaces configured for communication with a plurality of RFID readers;
an application layer event (“ALE”) adapter for processing reads from the RFID readers;
a second network interface configured for communication with networked devices executing RFID-related applications; and
an AON module configured to perform the following steps:
receive a first ALE request from one of the networked devices;
preprocess the first ALE request;
issue a second ALE request to the ALE adapter; and
process an ALE response from the ALE adapter;
wherein the ALE adapter is further configured to make read requests to one or more selected RFID readers of the plurality of RFID readers and to create the ALE response according to at least one RFID read.
10. The network device of claim 9, wherein the step of processing the ALE response comprises generating a notification to one or more of the networked devices when the ALE response comprises one of a set of predetermined ALE responses.
11. The network device of claim 9, wherein the preprocessing step comprises identifying and authenticating a sender of the first ALE request.
12. The network device of claim 9, wherein a line card comprises the AON module.
13. The network device of claim 9, wherein a message of the first ALE request is classified based on a uniform resource identifier of the first ALE request.
14. The network device of claim 9, wherein the AON module is further configured to perform the following steps:
determining a first application layer protocol that was used to transmit the first ALE request;
determining a message termination technique that is associated with the first application layer protocol; and
determining message contents of the first ALE request, based at least in part on the message termination technique.
15. The network device of claim 14, wherein the AON module is further configured to form the second ALE request according to a second application layer protocol different from the first application layer protocol.
16. A device for controlling a network, the device comprising:
means for receiving a message relating to an RFID device network or a sensor network;
means for determining an application layer protocol that was used to transmit the message;
means for determining a message termination technique that is associated with the application layer protocol;
means for determining the message contents, based at least in part on the message termination technique; and
means for performing at least one action according to the message contents.
17. The device of claim 16, further comprising means for determining a message classification that is associated with criteria satisfied by the message, wherein the performing means performs at least one action according to the message classification.
18. The device of claim 16, wherein the action comprises applying a rule to initiate a predetermined sequence of operations.
19. The device of claim 16, wherein the action comprises obtaining information from the RFID device network.
20. The device of claim 16, wherein the information pertains to least one of an indicated manufacturer, an indicated location, an indicated product type and an indicated time period.
Patent Citations (88)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4688026(A) | 1987-08-01 | Scribner et al. | Applicant |
| US5339073(A) | 1994-08-01 | Dodd et al. | Applicant |
| US5646616(A) | 1997-07-01 | Komatsu | Applicant |
| US5850187(A) | 1998-12-01 | Carrender et al. | Applicant |
| US5887176(A) | 1999-03-01 | Griffith et al. | Applicant |
| US6021135(A) | 2000-02-01 | Ishihara et al. | Applicant |
| US6111517(A) | 2000-08-01 | Atick et al. | Applicant |
| US6115079(A) | 2000-09-01 | McRae | Applicant |
| US6145079(A) | 2000-11-01 | Mitty et al. | Applicant |
| US6300903(B1) | 2001-10-01 | Richards et al. | Applicant |
| US6510464(B1) | 2003-01-01 | Grantges et al. | Applicant |
| US6539281(B2) | 2003-03-01 | Wan et al. | Applicant |
| US6553489(B1) | 2003-04-01 | Osler et al. | Applicant |
| US6587431(B1) | 2003-07-01 | Almulhem et al. | Applicant |
| US6597918(B1) | 2003-07-01 | Kim | Applicant |
| US6678827(B1) | 2004-01-01 | Rothermel et al. | Applicant |
| US6683881(B1) | 2004-01-01 | Mijares et al. | Applicant |
| US6718326(B2) | 2004-04-01 | Uga et al. | Applicant |
| US6745041(B2) | 2004-06-01 | Allison et al. | Applicant |
| US6772223(B1) | 2004-08-01 | Corl, Jr. et al. | Applicant |
| US6792002(B2) | 2004-09-01 | Tezuka et al. | Applicant |
| US6963282(B1) | 2005-11-01 | Yeates et al. | Applicant |
| US7057511(B2) | 2006-06-01 | Shanks et al. | Examiner |
| US7064660(B2) | 2006-06-01 | Perkins et al. | Applicant |
| US7075412(B1) | 2006-07-01 | Reynolds et al. | Applicant |
| US7081819(B2) | 2006-07-01 | Martinez de Velasco Cortina et al. | Examiner |
| US7103886(B2) | 2006-09-01 | Haller et al. | Examiner |
| US7111076(B2) | 2006-09-01 | Abjanic et al. | Applicant |
| US7126907(B2) | 2006-10-01 | Carpini et al. | Applicant |
| US7129837(B2) | 2006-10-01 | Shannon et al. | Examiner |
| US7205897(B2) | 2007-04-01 | Lin | Examiner |
| US2001/0028308(A1) | 2001-10-01 | De La Huerga | Applicant |
| US2002/0016739(A1) | 2002-02-01 | Ogasawara | Applicant |
| US2002/0126672(A1) | 2002-09-01 | Chow et al. | Applicant |
| US2002/0161907(A1) | 2002-10-01 | Moon | Applicant |
| US2003/0028599(A1) | 2003-02-01 | Kolsky | Applicant |
| US2003/0095569(A1) | 2003-05-01 | Wengrovitz et al. | Applicant |
| US2003/0115448(A1) | 2003-06-01 | Bouchard | Applicant |
| US2004/0021569(A1) | 2004-02-01 | Lepkofker et al. | Applicant |
| US2004/0054886(A1) | 2004-03-01 | Dickinson et al. | Applicant |
| US2004/0061646(A1) | 2004-04-01 | Andrews et al. | Applicant |
| US2004/0069852(A1) | 2004-04-01 | Seppinen et al. | Applicant |
| US2004/0088585(A1) | 2004-05-01 | Kaler et al. | Applicant |
| US2004/0100383(A1) | 2004-05-01 | Chen et al. | Applicant |
| US2004/0108795(A1) | 2004-06-01 | Meek et al. | Applicant |
| US2004/0121789(A1) | 2004-06-01 | Lindsey | Applicant |
| US2004/0128389(A1) | 2004-07-01 | Kopchik | Applicant |
| US2004/0133775(A1) | 2004-07-01 | Callas et al. | Applicant |
| US2004/0167986(A1) | 2004-08-01 | Gilfix et al. | Applicant |
| US2004/0170182(A1) | 2004-09-01 | Higashida et al. | Applicant |
| US2004/0257202(A1) | 2004-12-01 | Coughlin et al. | Applicant |
| US2005/0021626(A1) | 2005-01-01 | Prajapat et al. | Applicant |
| US2005/0071508(A1) | 2005-03-01 | Brown et al. | Applicant |
| US2005/0093679(A1) | 2005-05-01 | Zai et al. | Applicant |
| US2005/0099270(A1) | 2005-05-01 | Diorio et al. | Applicant |
| US2005/0165828(A1) | 2005-07-01 | Lango et al. | Applicant |
| US2005/0199716(A1) | 2005-09-01 | Shafer et al. | Applicant |
| US2005/0209947(A1) | 2005-09-01 | Shafer | Applicant |
| US2005/0216727(A1) | 2005-09-01 | Chattapadhyay et al. | Applicant |
| US2005/0252957(A1) | 2005-11-01 | Howarth et al. | Applicant |
| US2005/0252970(A1) | 2005-11-01 | Howarth et al. | Applicant |
| US2005/0252971(A1) | 2005-11-01 | Howarth et al. | Applicant |
| US2005/0253717(A1) | 2005-11-01 | Howarth et al. | Applicant |
| US2005/0253718(A1) | 2005-11-01 | Droms et al. | Applicant |
| US2005/0253722(A1) | 2005-11-01 | Droms et al. | Applicant |
| US2005/0264420(A1) | 2005-12-01 | Vogel et al. | Applicant |
| US2006/0005035(A1) | 2006-01-01 | Coughlin | Applicant |
| US2006/0010086(A1) | 2006-01-01 | Klein | Applicant |
| US2006/0033606(A1) | 2006-02-01 | Howarth et al. | Applicant |
| US2006/0044111(A1) | 2006-03-01 | Kollar et al. | Applicant |
| US2006/0091999(A1) | 2006-05-01 | Howarth | Applicant |
| US2006/0106941(A1) | 2006-05-01 | Singhal et al. | Applicant |
| US2006/0123226(A1) | 2006-06-01 | Kumar et al. | Applicant |
| US2006/0123425(A1) | 2006-06-01 | Ramarao et al. | Applicant |
| US2006/0123467(A1) | 2006-06-01 | Kumar et al. | Applicant |
| US2006/0123477(A1) | 2006-06-01 | Raghavan et al. | Applicant |
| US2006/0123479(A1) | 2006-06-01 | Kumar et al. | Applicant |
| US2006/0129650(A1) | 2006-06-01 | Ho et al. | Applicant |
| US2006/0129689(A1) | 2006-06-01 | Ho et al. | Applicant |
| US2006/0146879(A1) | 2006-07-01 | Anthias et al. | Applicant |
| US2006/0155862(A1) | 2006-07-01 | Kathi et al. | Applicant |
| US2006/0167975(A1) | 2006-07-01 | Chan et al. | Applicant |
| US2006/0168334(A1) | 2006-07-01 | Potti et al. | Applicant |
| US2006/0253590(A1) | 2006-11-01 | Nagy et al. | Applicant |
| US2006/0266832(A1) | 2006-11-01 | Howarth et al. | Applicant |
| US2007/0013518(A1) | 2007-01-01 | Howarth | Applicant |
| US2007/0080784(A1) | 2007-04-01 | Kim et al. | Applicant |
| WO3/021465(A1) | 2003-03-01 | Applicant |
Non-Patent Literature (59)
- “EPCgl, Frequently Asked Questions”, Retrieved from the internet: http://www.epcglobalinc.com/about/faqs.html, [Retrieved Mar. 24, 2005], 9 pages.Applicant
- “EPC™ Tag Data Standards Version 1.1 Rev.1.24”, EPCglobal, Standard Specification, Apr. 1, 2004, 78 pages.Applicant
- “The Global Language of Business”, Retrieved froom the internet: http://www.ean-int.org/locations.html, [Retrieved Mar. 24, 2005], 5 pages.Applicant
- “Cisco Application-Oriented Networking: A Network-Based Intelligent Message Routing System”, http://www.cisco.com/en/US/products/ps6438/products—data—sheet0900aecd802c1f9c.html Data Sheet, Cisco Systems, Inc., Jul. 13, 2005, pp. 1-7.Applicant
- “Cisco Catalyst 6500 Series Application-Oriented Networking Module”, http://www.cisco.com/en/US/products/ps6438/products—data—sheet0900aecd802c1fe9.html Data Sheet, Cisco Systems, Inc. Jul. 13, 2005, pp. 1-3.Applicant
- “Cisco Application-Oriented Networking—A Network Embedded Intelligent Message Routing System”, http://www.cisco.com/en/US/products/ps6438/prod—bulletin0900aecd802c201b.html Product Bulletin No. 2886, Cisco Systems, Inc. Jul. 13, 2005, pp. 1-3.Applicant
- “Cisco Catalyst 6500 Series Application-Oriented Networking Module: Large Photo”, Photo, Retrieved from the internet: http://www.cisco.com/en/US/products/ps6448/prod—view—selector.html [Retrieved Jul. 13, 2005], Cisco Systems, Inc. 1 page.Applicant
- “The EPCglobal Architecture Framework” EPCglobal Final Version of Jul. 1, 2005, pp. 1-53.Applicant
- Marc Girardot and Neel Sundaresan. “Millau: an encoding format for efficient representation and exchange of XMl over the web” [Retrieved Jan. 31, 2005]. Retrieved from the internet: http://www9.org/w9cdrom/154/154.html 25 pages.Applicant
- Fujitsu Limited, et al., “Web Services Reliability (WS-Reliability) Ver1.0”, Jan. 8, 2003. pp. 1-45.Applicant
- Ruslan Bilorusets et al., “Web Services Reliable Messaging Protocol (WS-ReliableMessaging)”, Mar. 2004, pp. 1-40.Applicant
- International Search Report dated Feb. 17, 2006, from related International Application No. PCT/US05/15322, 5 pp. including Notification of Transmittal.Applicant
- Written Opinion of the International Searching Authority dated Feb. 17, 2006, from related International Application No. PCT/US05/15322, 3 pp.Applicant
- Droms, R., Dynamic Host Configuration Protocol, RFC 2131, Mar. 1997, 43 pages.Applicant
- Alexander, S., et al., DHCP Options and BOOTP Vendor Extensions, RFC 2132, Mar. 1997, 32 pages.Applicant
- Stump, G., et al., The User Class Option for DHCP, RFC 3004, Nov. 2000, 6 pages.Applicant
- T'Joens, Y., DHCP Reconfigure Extension, RFC 3203, Dec. 2001, 6 pages.Applicant
- Patrick, M., DHCP Relay Agent Information Option, RFC 3046, Jan. 2001, 14 pages.Applicant
- Lonvick, C., The BSD Syslog Protocol, RFC 3164, Aug. 2001, 28 pages.Applicant
- Johnston, M., DHCP Preboot Execution Environment (PXE) Options draft-ietf-dhc-pxe-options-01.txt, Internet-Draft, Jan. 21, 2005, 7 pages.Applicant
- Johnson, R., TFTP Server Address DHCP Option draft-raj-dhc-tftp-addr-option-00.txt, Internet-Draft, Feb. 6, 2005, 7 pages.Applicant
- Littlefield, J., Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DPHCPv4), RFC 3925, Oct. 2004, 9 pages.Applicant
- Schulzrinne, H., Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information, draft-ietf-geopriv-dhcp-civil-05, Internet-Draft, Feb. 19, 2004.Applicant
- Polk, J., et al., Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information, RFC 3825, Jul. 2004, 15 pages.Applicant
- AeroScout Visibility System: Bridging the Gap Between Wi-Fi, Active RFID and Telemetry, AeroScout Enterprise Visibility Solutions, http://www.aeroscout.com/content.asp?page=SystemOverview, printed Apr. 16, 2005, 3 pages.Applicant
- WhereNet, Products, http://wherenet.com/products—main.html, printed Apr. 16, 2005, 2 pages.Applicant
- Simple Network Management Protocol, Internetworking Technologies Handbook, Chapter-56, printed Jul. 14, 2005, 12 pages.Applicant
- International Search Report dated Oct. 13, 2005, from (related) International Application No. PCT/US05/16484, 6 pp. including Notification of Transmittal.Applicant
- Written Opinion of the International Searching Authority dated Oct. 13, 2005, from (related) International Application No. PCT/US05/16484, 5 pp.Applicant
- Harrington, D., et al, An Architecture for DescribingSimple Network Management Protocol (SNMP) Management Frameworks, RFC 3411, Dec. 2002, 64 pages.Applicant
- Presuhn, R., Editor, Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP), RFC 3416, Dec. 2002, 31 pages.Applicant
- Global Location Number (GLN) Implementation Guide, Uniform Code Council, Inc., May 2002, 13 pages.Applicant
- Mockapetris, P., “Domain Names—Concepts and Facilities”, RFC 1034, Nov. 1987, 43 pages.Applicant
- Mockapetris, P., “Domain Names—Implementation and Specification”, RFC 1035, 55 pages.Applicant
- International Search Report dated Jul. 13, 2006, from (related) International Application No. PCT/US05/16319, 5 pp. including Notification of Transmittal.Applicant
- Written Opinion of the International Searching Authority dated Jul. 13, 2006, from (related) International Application No. PCT/US05/16319, 5 pp.Applicant
- US Office Action mailed Aug. 9, 2006 from (related) U.S. Appl. No. 10/866,507.Applicant
- US Office Action mailed Oct. 6, 2006 from (related) U.S. Appl. No. 10/866,506.Applicant
- US Office Action mailed Oct. 6, 2006 from (related) U.S. Appl. No. 10/866,285.Applicant
- US Office Action mailed Nov. 13, 2006 from (related)U.S. Appl. No. 11/073,245, 12 pp.Applicant
- US Office Action mailed Jan. 18, 2007 from (related) U.S. Appl. No. 10/866,507, 4 pp.Applicant
- US Office Action mailed Mar. 22, 2007 from (related) U.S. Appl. No. 10/866,506.Applicant
- US Office Action mailed Apr. 4, 2007 from (related) U.S. Appl. No. 10/866,285.Applicant
- US Office Action mailed Jun. 18, 2007 from (related) U.S. Appl. No. 11/010,089.Applicant
- International Searching Authority, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” PCT/US05/43599, dated Feb. 28, 2007, 8 pages.Applicant
- Current Claims, PCT/US05/43599, 8 pages.Applicant
- International Searching Authority, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” PCT/US05/41254, dated Mar. 28, 2007, 7 pages.Applicant
- Current Claims, PCT/US05/41254, 12 pages.Applicant
- International Searching Authority, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” PCT/US05/44171, dated Nov. 30, 2006, 7 pages.Applicant
- Current Claims, PCT/US05/44171, 12 pages.Applicant
- International Searching Authority, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” PCT/US2006/024375, dated Oct. 17, 2006, 10 pages.Applicant
- Current Claims, PCT/US2006/024375, 5 pages.Applicant
- OA U.S. Appl. No. 11/007,421, filed Dec. 7, 2004 Mailed on Oct. 16, 2006.Applicant
- OA U.S. Appl. No. 10/991,792, filed Nov. 17, 2004 Mailed on Oct. 20, 2006.Applicant
- International Searching Authority, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” PCT/US05/45625, dated Oct. 20, 2006, 7 pages.Applicant
- Current Claims PCT/US05/45625, 8 pages.Applicant
- International Searching Authority, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” PCT/US05/40861, dated Nov. 17, 2006, 7 pages.Applicant
- Current Claims PCT/US05/40861, 5 pages.Applicant
- Decasper, Dan et al., “Router Plugins: A Software Architecture for Next Generation Routers,” IEEE ACM Transactions on Networking, vol. 9, No. 1, Feb. 2000, XP011038838, 14 pages.Applicant