US7389295B2 - Using federated mote-associated logs - Google Patents
Using federated mote-associated logs Download PDFInfo
- Publication number
- US7389295B2 US7389295B2 US10/877,109 US87710904A US7389295B2 US 7389295 B2 US7389295 B2 US 7389295B2 US 87710904 A US87710904 A US 87710904A US 7389295 B2 US7389295 B2 US 7389295B2
- Authority
- US
- United States
- Prior art keywords
- mote
- log
- content
- logs
- accepting
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
Definitions
- the present application is related to, claims the earliest available effective filing date(s) from (e.g., claims earliest available priority dates for other than provisional patent applications; claims benefits under 35 USC ⁇ 119(e) for provisional patent applications), and incorporates by reference in its entirety all subject matter of the following listed application(s); the present application also claims the earliest available effective filing date(s) from, and also incorporates by reference in its entirety all subject matter of any and all parent, grandparent, great-grandparent, etc. applications of the following listed application(s):
- the present application relates, in general, to motes.
- a method includes but is not limited to: accepting input defining a mote-appropriate network search; and searching at least one federated log in response to said accepted input.
- related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
- a method includes but is not limited to: loading at least one federated log to a computer system external to a mote-appropriate network; accepting input defining a search of the mote-appropriate network; and searching the loaded at least one federated log in response to said input.
- related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
- a method includes but is not limited to: loading at least one mote-addressed content log of a federated log to a computer system external to a mote-appropriate network; accepting input defining a search of the mote-appropriate network; and searching the loaded at least one mote-addressed content log of the federated log in response to said input.
- related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
- a method includes but is not limited to: loading at least one multi-mote content log of a federated log to a computer system external to a mote-appropriate network; accepting input defining a search of the mote-appropriate network; and searching the loaded at least one multi-mote content log of the federated log in response to said input.
- related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
- a method includes but is not limited to: loading at least one aggregation of content logs wherein the at least one aggregation forms a part of at least one federated log to a computer system external to a mote-appropriate network; accepting input defining a search of the mote-appropriate network; and searching the loaded at least one aggregation of content logs wherein the at least one aggregation forms a part of the at least one federated log in response to said input.
- other method aspects are described in the claims, drawings, and/or text forming a part of the present application.
- related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
- FIG. 1 shows an example of mote 100 of mote-appropriate network 150 that may serve as a context for introducing one or more processes and/or devices described herein.
- FIG. 2 depicts an exploded view of mote 200 that forms a part of a mote-appropriate network (e.g., as shown in FIGS. 3 , 4 , 5 , 7 , 8 , 10 , 11 and/or 12 ).
- FIG. 3 depicts an exploded view of mote 300 forming a part of mote-appropriate network 350 that may serve as a context for introducing one or more processes and/or devices described herein.
- FIG. 4 shows a high-level diagram of a network having a first set of motes addressed 1 A through MA (M is an integer greater than 1; A is the letter A and in some instances is used herein to help distinguish differently administered networks such as shown/described in relation to FIGS. 10 , 11 , and/or 12 ), which may form a context for illustrating one or more processes and/or devices described herein.
- FIG. 5 depicts an exploded view of mote 500 forming a part of mote-appropriate network 550 that may serve as a context for introducing one or more processes and/or devices described herein.
- FIG. 6 depicts an exploded view of mote 600 forming a part of mote-appropriate network 550 ( FIG. 5 ) that may serve as a context for introducing one or more processes and/or devices described herein.
- FIG. 7 shows a high-level diagram of an exploded view of a mote appropriate network that depicts a first set of motes addressed 1 A through MA (M is an integer greater than 1; A is the letter A and in some instances is used herein to help distinguish differently administered networks as in FIGS. 11 and/or 12 ), which may form an environment for process(es) and/or device(s) described herein.
- FIG. 8 shows an exploded view of aggregation 710 of content logs of FIG. 7 .
- FIG. 9 depicts an exploded view of aggregation 710 of content logs of FIG. 7 .
- FIG. 10 shows a high-level diagram of first-administered set 1000 of motes addressed 1 A through MA, and second-administered set 1002 of motes addressed 1 B through NB (M and N are integers greater than 1; A and B are letters used herein to help distinguish differently administered networks as in FIGS. 10 , 11 and 12 ) that may form an environment for process(es) and/or device(s) described herein.
- FIG. 11 shows a high-level diagram of first-administered set 1000 of motes and second-administered set 1002 of motes modified in accordance with teachings of subject matter described herein.
- FIG. 12 shows the high-level diagram of FIG. 11 , modified to show first-administered set 1000 of motes and second-administered set 1002 of motes wherein each mote is illustrated as having log(s) (e.g., mote-addressed and/or multi-mote) and associated reporting entity(ies).
- log(s) e.g., mote-addressed and/or multi-mote
- FIG. 13 shows an exemplary exploded view of federated log 916 .
- FIG. 14 depicts a perspective cut-away view of a hallway that may form an environment of processes and/or devices described herein.
- FIGS. 15 , 16 , and 17 shows three time-sequenced views of a person transiting wall 1400 and floor 1402 of the hallway of FIG. 14 .
- FIG. 18 depicts a perspective view of the hallway of FIG. 14 , modified in accord with aspects of the subject matter described herein.
- FIG. 19 illustrates that first set 400 of the physical motes of wall 1400 may be treated as mapped into a conceptual x-y coordinate system.
- FIG. 20 shows a partially schematic diagram that pictographically illustrates the coordinating of the conceptual mapping of the motes of wall 1400 with the logs of first set 400 of the motes of wall 1400 .
- FIGS. 21 , 22 , and 23 show time-stamped versions of aggregation 710 associated with the state of first set 400 of motes.
- FIG. 24 depicts a high-level logic flowchart of a process.
- FIG. 25 illustrates a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 24 .
- FIG. 26 illustrates a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 24 .
- FIG. 27 shows a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 26 .
- FIG. 28 shows a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 27 .
- FIG. 29 illustrates the perspective cut-away view of the hallway of FIG. 14 modified in accord with aspects of the subject matter described herein.
- FIG. 30 shows that first-administered set 1000 and second-administered set 1002 of the physical motes of wall 1400 may be treated as mapped into a conceptual x-y coordinate system.
- FIG. 31 shows a partially schematic diagram that pictographically illustrates the coordinating of the conceptual mapping of the motes of wall 1400 with the logs of first-administered set 1000 and second-administered set 1002 of the physical motes of wall 1400 .
- FIG. 32 shows time-stamped versions of aggregation 910 of first-administered content logs associated with the state of first-administered set 1000 of motes.
- FIG. 33 depicts time-stamped versions of aggregation 912 of second-administered content logs associated with the state of second-administered set 1002 of motes.
- FIGS. 34 , 35 , and 36 illustrate different versions of federated content log 916 .
- FIG. 37 depicts a high-level logic flowchart of a process.
- FIG. 38 illustrates a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 37 .
- FIG. 39 illustrates a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 37 .
- FIG. 40 shows a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 39 .
- FIG. 41 shows a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 39 .
- FIG. 42 shows a high-level logic flowchart depicting several alternate implementations of the high-level logic flowchart of FIG. 39 .
- mote 100 of mote-appropriate network 150 may serve as a context for introducing one or more processes and/or devices described herein.
- a mote is typically composed of sensors, actuators, computational entities, and/or communications entities formulated, in most cases at least in part, from a substrate.
- the term “mote” typically means a semi-autonomous computing, communication, and/or sensing device as described in the mote literature (e.g., Intel Corporation's mote literature), as well as equivalents recognized by those having skill in the art (e.g., Intel Corporation's smart dust projects).
- Mote 100 depicts a specific example of a more general mote.
- Mote 100 is illustrated as having antenna 102 , physical layer 104 , antenna entity 119 , network layer 108 (shown for sake of example as a mote-appropriate ad hoc routing application), light device entity 110 , electrical/magnetic device entity 112 , pressure device entity 114 , temperature device entity 116 , volume device entity 118 , and inertial device entity 120 .
- Light device entity 110 electrical /magnetic device entity 112 , pressure device entity 114 , temperature device entity 116 , volume device entity 118 , antenna entity 119 , and inertial device entity 120 are depicted to respectively couple through physical layers 104 with light device 140 , electrical/magnetic device 142 , pressure device 144 , temperature device 156 , volume device 158 , antenna 102 , and inertial device 160 .
- light device 140 electrical/magnetic device 142 , pressure device 144 , temperature device 156 , volume device 158 , antenna 102 , and inertial device 160 .
- light device 140 is implemented using one or more light transmitters (e.g., coherent light transmission devices or non-coherent light transmission devices) and/or one or more light receivers (e.g., coherent light reception devices or non-coherent light reception devices) and/or one or more supporting devices (e.g., optical filters, hardware, firmware, and/or software).
- light transmitters e.g., coherent light transmission devices or non-coherent light transmission devices
- light receivers e.g., coherent light reception devices or non-coherent light reception devices
- supporting devices e.g., optical filters, hardware, firmware, and/or software
- electrical/magnetic device 142 is implemented using one or more electrical/magnetic transmitters (e.g., electrical/magnetic transmission devices) and/or one or more electrical/magnetic receivers (e.g., electrical/magnetic reception devices) and/or one or more supporting devices (e.g., electrical/magnetic filters, supporting hardware, firmware, and/or software).
- electrical/magnetic device 142 is implemented using one or more electrical/magnetic transmitters (e.g., electrical/magnetic transmission devices) and/or one or more electrical/magnetic receivers (e.g., electrical/magnetic reception devices) and/or one or more supporting devices (e.g., supporting hardware, firmware, and/or software).
- temperature device 156 is implemented using one or more temperature transmitters (e.g., temperature transmission devices) and/or one or more temperature receivers (e.g., temperature reception devices) and/or one or more supporting devices (e.g., supporting hardware, firmware, and/or software).
- volume device 158 is implemented using one or more volume transmitters (e.g., gas/liquid transmission devices) and/or one or more volume receivers (e.g., gas/liquid reception devices) and/or one or more supporting devices (e.g., supporting hardware, firmware, and/or software).
- inertial device 160 is implemented using one or more inertial transmitters (e.g., inertial force transmission devices) and/or one or more inertial receivers (e.g., inertial force reception devices) and/or one or more supporting devices (e.g., supporting hardware, firmware, and/or software).
- inertial transmitters e.g., inertial force transmission devices
- inertial receivers e.g., inertial force reception devices
- supporting devices e.g., supporting hardware, firmware, and/or software
- OSI Open System Interconnection
- OSI layers 4 - 6 transport-presentation layers
- mote 200 that forms a part of a mote-appropriate network (e.g., as shown in FIGS. 3 , 4 , 5 , 7 , 8 , 10 , 11 and/or 12 ).
- Mote 200 is illustrated as similar to mote 100 ( FIG. 1 ), but with the addition of log creation agent 202 , mote-addressed sensing/control log 204 , and mote-addressed routing/spatial log 252 .
- Mote-addressed sensing/control log 204 is shown in FIG. 2 as having illustrative entries of light device information, electrical/magnetic device information, pressure device information, temperature device information, volume device information, inertial device information, and antenna information.
- light device information include measures of brightness, saturation, intensity, color, hue, power (e.g., watts ), flux (e.g., lumens), irradiance (e.g., Watts/cm 2 ), illuminance (lumens/m 2 , lumens/ft 2 ), pixel information (e.g., numbers of pixels (e.g., one for a very small mote image capture device), relative pixel orientation)), etc.
- Examples of electrical/magnetic device information include measures of field strength, flux, current, voltage, etc.
- Examples of pressure device information include measures of gas pressure, fluid pressure, radiation pressure, mechanical pressure, etc.
- Examples of temperature device information include measures of temperature such as Kelvin, Centigrade, and Fahrenheit, etc.
- Examples of inertial device information include measures of force, measures of acceleration, deceleration, etc.
- Examples of antenna information include measures of signal power, antenna element position, relative phase orientations of antenna elements, delay line configurations of antenna elements, beam directions, field of regard directions, antenna types (e.g., horn, biconical, array, Yagi, log-periodic, etc.), etc.
- FIG. 2 does not show illustrative entries for mote-addressed routing/spatial log 252 .
- a mote-addressed routing/spatial log might contain, see the mote-addressed routing/spatial logs shown internal to multi-mote content log 504 of FIG. 5 . As shown in FIG.
- a mote-addressed routing/spatial log will contain a listing of mote addresses directly accessible from a mote (e.g., via direct radio transmission/reception from/by antenna 102 ), an assessment of qualities of data communications service on the data communication links to such directly accessible motes, and/or a listing of relative and/or absolute spatial coordinates of such directly accessible motes.
- log creation agent 202 is a computer program—resident in mote 200 —that executes on a processor of mote 200 and that constructs and/or stores mote-addressed sensing/control log 204 , and/or mote-addressed routing/spatial log 252 in memory of mote 200 .
- log creation agent 202 is pre-installed on mote 200 prior to mote 200 being added to a mote-appropriate network, while in other implementations log creation agent 202 crawls and/or is transmitted to mote 200 from another location (e.g., a log creation agent at another mote or another networked computer (not shown) clones itself and sends that clone to mote 200 ). In yet other implementations, log creation agent 202 is installed at a proxy (not shown) for mote 200 .
- the inventors point out that in some applications the systems and/or processes transfer their instructions in a piecewise fashion over time, such as is done in the mote-appropriate Mate′ virtual machine of the related art.
- motes are low-power and/or low bandwidth devices, and thus in some implementations the system(s) and process(es) described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and/or processes to migrate to and establish themselves at various motes. The same may also hold true for transmission of information among motes in that in some implementations such transmission may be done over the course of hours, days, or even weeks depending upon bandwidth, power, and/or other constraints. In other implementations, the migrations and/or transmissions are accomplished more rapidly, and in some cases may be accomplished as rapidly as possible.
- reporting entities For sake of clarity, some implementations shown/described herein include various separate architectural components. Those skilled in the art will appreciate that the separate architectural components are so described for sake of clarity, and are not intended to be limiting. Those skilled in the art will appreciate the herein-described architectural components, such reporting entities, logs, and/or device entities, etc. are representative of substantially any architectural components that perform in a similar manner. For example, while some implementations show reporting entities obtaining information from logs created with device entity data, those skilled in the art will appreciate that such implementations are representative of reporting entities obtaining the data directly from the device entities.
- implementations show reporting entities obtaining information produced by device entities
- implementations are representative of queries executing at the mote that extract and/or transmit similar information as that described in the relation to the reporting entities and/or device entities (e.g., some multi-mote creation agent making a query of a database entity resident at a mote, where the database entity would perform in a fashion similar to that described in relation to reporting entities, logs, and/or device entities, etc.).
- some multi-mote creation agent making a query of a database entity resident at a mote, where the database entity would perform in a fashion similar to that described in relation to reporting entities, logs, and/or device entities, etc.
- the architectural components described herein are representative of virtually any grouping of architectural components that perform in a similar manner.
- Mote 200 of FIG. 2 can serve as a context in which one or more processes and/or devices may be illustrated.
- log creation agent 202 communicates with device entity registry 210 to receive device identifiers indicative of device entities present at mote 200 (e.g., light device entity 110 , electrical /magnetic device entity 112 , pressure device entity 114 , etc.).
- device entities of mote 200 register their presences with device entity registry 210
- the operating system of mote 200 registers the device entities when the operating system installs the device entities and/or their associated drivers (if any).
- device entity registry 210 receives device identifiers from an external source (e.g., receiving the device identifiers from a multi-mote creation agent, an aggregation agent, or a federation agent that transmits over a wireless link).
- log creation agent 202 once log creation agent 202 becomes aware of what device entities are present, log creation agent 202 communicates with the device entities (e.g., light device entity 110 , electrical/magnetic entity 112 , pressure entity 114 , etc.) to find out what sensing/control functions are present and/or available at their various respectively associated devices (e.g., light device 140 , electrical/magnetic device 142 , pressure device 144 , etc.).
- the device entities e.g., light device entity 110 , electrical/magnetic entity 112 , pressure entity 114 , etc.
- log creation agent 202 also communicates with routing/spatial log 252 to find out the mote-network address of mote 200 (e.g., mote-network address 6 A) as well as other spatial information (e.g., mote-network addresses and/or spatial locations of the motes that can be reached directly by wireless link from mote 200 ; spatial locations may be absolute and/or relative to some marker, such as mote 200 itself).
- log creation agent 202 communicates with the device entities using a common application protocol which specifies standard interfaces that allow log creation agent 202 to garner the necessary information without knowing the internal workings and/or architectures of each specific device entity. In other implementations, such a common application protocol is not used.
- log creation unit 202 contemporaneous with and/or subsequent to log creation agent 202 communicating with the device entities, log creation unit 202 creates one or more mote-addressed content logs.
- the one or more mote-addressed content logs are associated with the mote-network address of the mote at which log creation unit 202 resides.
- the inventors point out that examples of the term “log,” and/or phrases containing the term “log,” exist in the text (e.g., independent claims, dependent claims, detailed description, and/or summary) and/or drawings forming the present application and that such term and/or phrases may have scopes different from like terms and/or phrases used in other contexts.
- the one or more mote-addressed content logs are time stamped with the time the log was created.
- Mote 200 is depicted for sake of illustration as having a mote-address of 6 A. Accordingly, a specific example of more general mote-addressed content logs is shown in FIG. 2 as mote 6 A-addressed sensing/control log 204 .
- Mote 6 A-addressed sensing/control log 204 is depicted as listing the sensing and/or control information in association with device-identifiers associated with devices present and/or available at mote 200 .
- Mote 6 A-addressed sensing/control log 204 is also depicted for sake of illustration as having been created at the current time, and thus is shown stamped with the denotation “tcurrent.”
- mote 6 A-addressed routing/spatial log 252 typically contains a listing of mote-network addresses of those motes directly accessible from mote 200 and such directly accessible motes' spatial orientations relative to mote 200 and/or some other common spatial reference location (e.g., GPS).
- Mote 6 A-addressed routing/spatial log 252 is also depicted as having a time stamp of “tcurrent,”
- log creation unit 202 creates one or more extensible mote-addressed content logs (e.g., creating the one or more extensible logs in response to a type of content being logged).
- mote addressing is shown and described herein for sake of clarity (e.g., mote-appropriate network addresses), the mote addressing described herein may also entail indirect addressing, dependent upon context.
- Examples of indirect addressing include approaches where a mote-address encodes an address of an agent that in turn produces the address of the mote (analogous to the Domain Name System in the Internet), or where the mote-address directly or indirectly encodes a route to a mote (analogous to explicit or implicit routable addresses.).
- a mote-address encodes an address of an agent that in turn produces the address of the mote (analogous to the Domain Name System in the Internet), or where the mote-address directly or indirectly encodes a route to a mote (analogous to explicit or implicit routable addresses.).
- a content log may have a device identifier which in various implementations may include an implicit and/or explicit indicator used to reference the specific device at that mote.
- a device identifier which in various implementations may include an implicit and/or explicit indicator used to reference the specific device at that mote.
- ways in which such may be achieved include the use of a structured name.
- mote-local devices may also have global addresses, which may be substituted or allowed to “stand in” for mote addresses.
- mote 300 forming a part of mote-appropriate network 350 that may serve as a context for introducing one or more processes and/or devices described herein.
- Mote 300 is illustrated as similar to mote 200 ( FIG. 2 ), but with the addition of reporting entity 302 .
- reporting entity 302 is a computer program—resident in mote 300 —that executes on a processor of mote 300 and that transmits all or a part of mote-addressed sensing/control log 204 , and/or mote-addressed routing/spatial log 252 to another entity (e.g., through antenna 102 to a multi-mote log creation agent such as shown/described in relation to FIG. 5 or through a mote-network to a designated gateway such as shown/described in relation to FIGS. 7 , 8 , 11 , and/or 12 ).
- reporting entity 302 is pre-installed on mote 300 prior to mote 300 being added to a mote-appropriate network, while in other implementations reporting entity 302 crawls and/or is transmitted to mote 300 from another location (e.g., a reporting entity at another mote or another networked computer (not shown) clones itself and sends that clone to mote 300 ).
- another location e.g., a reporting entity at another mote or another networked computer (not shown) clones itself and sends that clone to mote 300 .
- the inventors point out that in some applications the crawling and/or transmissions described herein are performed in a piecewise fashion over time, such as is done in the mote-appropriate Mate′ virtual machine of the related art.
- motes are low-power and/or low bandwidth devices, and thus in some implementations the crawling and/or transmissions described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and/or processes to migrate to and establish themselves at various motes. The same may also hold true for transmission of information among motes in that in some implementations such transmission may be done over the course of hours, days, or even weeks depending upon bandwidth, power, and/or other constraints. In other implementations, the migrations and/or transmissions are accomplished more rapidly, and in some cases may be accomplished as rapidly as possible.
- Mote 300 of FIG. 3 can serve as a context in which one or more processes and/or devices may be illustrated.
- reporting entity 302 transmits at least a part of a content log to another entity either resident within or outside of mote network 350 (e.g., through antenna 102 to a multi-mote log creation agent such as shown/described in relation to FIG. 5 or through a mote-network to a designated gateway-proximate mote as shown/described in relation to FIGS. 5 , 6 , 7 , 8 , 9 , 11 and/or 12 ).
- reporting entity 302 transmits in response to a received schedule (e.g., received from multi-mote log creation agent 502 of FIG.
- reporting entity 302 transmits in response to a derived schedule.
- the schedule is derived in response to one or more optimized queries.
- the schedule is derived in response to one or more stored queries (e.g., previously received or generated queries).
- reporting entity 302 transmits in response to a received query (e.g., received from multi-mote log creation agent of FIG. 5 and/or federated log creation agent of FIG. 9 or 10 ). In various implementations, reporting entity 302 transmits using either or both public key and private key encryption techniques. In various other implementations, reporting entity 302 decodes previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.
- a received query e.g., received from multi-mote log creation agent of FIG. 5 and/or federated log creation agent of FIG. 9 or 10 .
- reporting entity 302 transmits using either or both public key and private key encryption techniques.
- reporting entity 302 decodes previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.
- FIG. 4 shown is a high-level diagram of a network having a first set 400 of motes addressed 1 A through MA (M is an integer greater than 1; A is the letter A and in some instances is used herein to help distinguish differently administered networks such as shown/described in relation to FIGS. 10 , 11 , and/or 12 ), which may form a context for illustrating one or more processes and/or devices described herein.
- Each mote is shown as having a mote-addressed content log that includes a sensing/control log and/or a routing/spatial log respectively associated with the sensing/control information at each such mote and/or the spatial locations (relative and/or absolute) of motes that can be reached by direct transmission from each such mote.
- the motes' various logs are created and/or function in fashions similar to logs shown/described elsewhere herein (e.g., in relation to FIG. 3 ).
- the motes of FIG. 4 include reporting entities that are created and/or function in ways analogous to the creation and/or functioning of reporting entities as shown and described elsewhere herein (e.g., in relation to FIG. 3 ).
- one or more of the motes of FIG. 4 may include log creation agents that are created and/or function in ways analogous to the creation and/or functioning of log creation agents as shown and described elsewhere herein (e.g., in relation to FIG. 2 ).
- the reporting entities at each mote transmit all or a part of their mote-addressed content logs (e.g., mote-addressed sensing/control logs, and/or mote-addressed routing/spatial logs) to one or more entities (e.g., multi-mote log creation agent 502 such as shown/described in relation to FIG. 5 and/or multi-mote log creation agent 716 such as shown/described in relation to FIGS. 7 , 9 and 10 ).
- such transmissions are done in response to a schedule, and in other implementations such transmissions are done in response to queries from the one or more entities.
- Such transmissions may be in response to received schedules, in response to schedules derived at least in part from optimized queries, in response to schedules derived at least in part from received queries, and/or in response to received queries such as described here and/or elsewhere herein.
- mote 500 forming a part of mote-appropriate network 550 that may serve as a context for introducing one or more processes and/or devices described herein.
- Mote 500 is illustrated as similar to mote 300 ( FIG. 3 ), but with the addition of multi-mote log creation agent 502 , multi-mote content log 504 , and multi-mote registry 510 (e.g., a registry of motes under the aegis of multi-mote log creation agent 502 and/or from which multi-mote content log 504 is to be constructed).
- Multi-mote content log 504 typically contains at least a part of content logs from at least two differently-addressed motes.
- multi-mote content log 504 is shown containing sensing/control mote-addressed logs and mote-addressed routing/spatial logs for two differently addressed motes: a mote having mote-network address of 1 A and a mote having a mote-network address of 3 A.
- the sensing/control logs and/or routing/spatial logs function more or less analogously to mote-addressed sensing/content log 204 , and/or mote-addressed routing/spatial log 252 of mote 200 (e.g., as shown/described in relation to FIG. 2 ).
- multi-mote log creation agent 502 is a computer program—resident in mote 500 —that executes on a processor of mote 500 and that constructs and stores multi-mote content log 504 in memory of mote 500 .
- multi-mote log creation agent 502 is pre-installed on mote 500 prior to mote 500 being added to a mote-appropriate network, while in other implementations multi-mote log creation agent 502 crawls and/or is transmitted to mote 500 from another location (e.g., a multi-mote log creation agent at another mote or another networked computer (not shown) clones itself and sends that clone to mote 500 ).
- the inventors point out that in some applications the crawling and/or transmissions described herein are performed in a piecewise fashion over time, such as is done in the mote-appropriate Mate′ virtual machine of the related art.
- motes are low-power and/or low bandwidth devices, and thus in some implementations the crawling and/or transmissions described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and/or processes to migrate to and establish themselves at various motes. The same may also hold true for transmission of information among motes in that in some implementations such transmission may be done over the course of hours, days, or even weeks depending upon bandwidth, power, and/or other constraints. In other implementations, the migrations and/or transmissions are accomplished more rapidly, and in some cases may be accomplished as rapidly as possible.
- Mote 500 of FIG. 5 can serve as a context in which one or more processes and/or devices may be illustrated.
- multi-mote log creation agent 502 obtains a listing of motes from which multi-mote content log 504 is to be constructed (e.g., a listing of motes making up a part of mote network 550 ).
- multi-mote log creation agent 502 obtains the listing of motes from which multi-mote content log 504 is to be constructed by communicating with multi-mote registry 510 to learn what mote-network addresses multi-mote log creation agent 502 is to consult to create multi-mote content log 504 .
- various log creation agents at various respective motes register their mote addresses with multi-mote registry 510
- an administrator e.g., either at or remote from mote 500
- a system administrator places various motes under the aegis of particular multi-mote log creation agents based on a single criterion or combined criteria such as spatial locations, bandwidths, qualities of service of data communication links, and/or contents of data captured at various particular motes.
- multi-mote log creation agent 502 is pre-loaded with knowledge of the listing of motes from which multi-mote content log 504 is to be constructed.
- the listing of motes from which multi-mote content log 504 is to be constructed is obtained from various motes that inform multi-mote log creation agent 502 that such various motes are to be included in the listing.
- multi-mote log creation agent 502 once multi-mote log creation agent 502 becomes aware of the mote-addresses for which it (multi-mote log creation agent 502 ) is responsible, multi-mote log creation agent 502 communicates with the various respective reporting entities at the various motes for which multi-mote log creation agent 502 is responsible and receives all or part of various respective mote-addressed content logs (e.g., at least a part of one or more sensing/control logs and/or one or more routing/spatial logs such as shown and described elsewhere herein).
- multi-mote log creation agent 502 communicates with the various respective reporting entities at the various motes for which multi-mote log creation agent 502 is responsible and receives all or part of various respective mote-addressed content logs (e.g., at least a part of one or more sensing/control logs and/or one or more routing/spatial logs such as shown and described elsewhere herein).
- multi-mote log creation agent 502 uses the various reported mote-addressed content logs to construct and/or save multi-mote content log 504 by aggregating at least a part of mote-addressed content logs from two separately addressed and/or actually separate motes.
- multi-mote content log 504 is shown as an aggregate of sensing/control and routing/spatial logs for motes having mote-network addresses of 1 A and 3 A, although typically multi-mote content logs will log more than just two motes.
- multi-mote log creation agent 502 receives all or part of various respective mote-addressed content logs from various respective reporting entities at various motes which transmit in response to a schedule (e.g., once every 18 minutes).
- the schedule may be received, pre-stored, and/or derived (e.g., such as shown/described in relation to other transmissions described elsewhere herein).
- multi-mote log creation agent 502 receiving all or part of various respective mote-addressed content logs from the various respective reporting entities at the various motes (e.g., mote 1 A and/or mote 3 A), those having skill in the art will appreciate that in other implementations multi-mote log creation agent 502 receives all or part of such logs from one or more motes representing the first set of motes.
- multi-mote log creation agent 502 receives mote-addressed content logs transmitted by reporting entities of various motes from which multi-mote log creation agent 502 creates multi-mote content log 504 . In other implementations, multi-mote log creation agent 502 receives one or more previously-created multi-mote content logs transmitted by multi-mote reporting entities at various motes from which multi-mote log creation agent 502 creates multi-mote content log 504 .
- multi-mote log creation agent 502 creates multi-mote content log 504 , at least in part, from a previously generated aggregate of mote-addressed content logs (e.g., from a previously generated multi-mote content log).
- a previously generated aggregate of mote-addressed content logs e.g., from a previously generated multi-mote content log.
- received multi-mote content logs have been created by other multi-mote log creation agents resident at other motes throughout a mote network (e.g., a mote network such as shown in FIG. 4 ).
- multi-mote log creation agent 502 then aggregates the multi-mote content logs to form another multi-mote content log.
- multi-mote log creation agent 502 aggregates both mote-addressed content logs and multi-mote content logs respectively received from various reporting entities to create a multi-mote content log.
- motes are low-power and/or low bandwidth devices, and thus in some implementations the systems and processes described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and processes to migrate to and establish themselves at various motes (e.g., by transferring their instructions in a piecewise fashion over time). The same may also hold true for transmission of information among motes.
- mote 600 forming a part of mote-appropriate network 550 ( FIG. 5 ) that may serve as a context for introducing one or more processes and/or devices described herein.
- Mote 600 is illustrated as similar to mote 500 ( FIG. 5 ), but with the addition of multi-mote reporting entity 602 .
- multi-mote reporting entity 602 is a computer program—resident in mote 600 —that executes on a processor of mote 600 .
- multi-mote reporting entity 602 is a computer program that is pre-installed on mote 600 prior to mote 600 being added to a mote-appropriate network, while in other implementations multi-mote reporting entity 602 is a computer program that crawls and/or is transmitted to mote 600 from another location (e.g., a reporting entity at another mote or another networked computer (not shown) clones itself and sends that clone to mote 600 ).
- the inventors point out that in some applications the crawling and/or transmissions described herein are performed in a piecewise fashion over time, such as is done in the mote-appropriate Mate′ virtual machine of the related art.
- motes are low-power and/or low bandwidth devices, and thus in some implementations the crawling and/or transmissions described herein allow many minutes (e.g., hours, days, or even weeks) for herein described agents and/or processes to migrate to and establish themselves at various motes. The same may also hold true for transmission of information among motes in that in some implementations such transmission may be done over the course of hours, days, or even weeks depending upon bandwidth, power, and/or other constraints. In other implementations, the migrations and/or transmissions are accomplished more rapidly, and in some cases may be accomplished as rapidly as possible.
- FIG. 7 shown is a high-level diagram of an exploded view of a mote appropriate network that depicts a first set of motes addressed 1 A through MA (M is an integer greater than 1; A is the letter A and in some instances is used herein to help distinguish differently administered networks as in FIGS. 11 and/or 12 ), which may form an environment for process(es) and/or device(s) described herein.
- Each mote is shown as having a mote-addressed content log that includes a sensing/control log and/or a routing/spatial log respectively associated with the sensing/control functions of devices at each such mote and/or the spatial locations (relative and/or absolute) of motes that can be reached by direct transmission from each such mote.
- the motes' various logs are created and/or function in fashions similar to mote-addressed logs shown and described herein (e.g., in relation to FIGS. 2 , 3 , and/or FIG. 4 ). In some implementations, the motes' various logs are created and/or function in fashions similar to multi-mote content logs shown and described herein (e.g., in relation to FIGS. 5 and/or 6 ). For example, mote 1 A (i.e., mote having mote-network address 1 A) and mote 6 A (i.e., mote having mote-network address 6 A) are shown having multi-mote content logs 750 and 752 respectively. The multi-mote content logs are created and/or function in ways analogous to those shown and/or described elsewhere herein.
- Mote 4 A is shown in FIG. 7 as proximate to gateway 704 onto WAN 714 (e.g., the Internet).
- Multi-mote log creation agent 716 is depicted as executing on the more powerful computational systems of gateway 704 (e.g., a mini and/or mainframe computer system) to create aggregation 710 of content logs.
- gateway 704 e.g., a mini and/or mainframe computer system
- aggregation 710 of content logs may be composed of multi-mote content logs and/or individual mote-addressed content logs.
- aggregations of multi-mote content logs in themselves may be considered aggregates of one or more individual mote-addressed content logs and thus types of multi-mote content logs.
- multi-mote content logs in themselves may be considered aggregates of one or more individual mote-addressed content logs and thus types of aggregations of content indexes.
- FIG. 8 shown is an exploded view of aggregation 710 of content logs of FIG. 7 .
- the time entries correspond with and/or are derived from time stamps of one or more mote-addressed logs such as those described elsewhere herein.
- FIG. 9 depicted is an exploded view of aggregation 710 of content logs of FIG. 7 .
- the time entries of the table correspond and/or are derived from time stamps of mote-addressed logs as described elsewhere herein.
- reporting entities that function analogously to other reporting entities described herein (e.g., multi-mote reporting entity 602 and/or reporting entity 302 ).
- reporting entities are computer programs that execute on processors of the motes wherein such reporting entities are resident and that transmit all or a part of logs at their motes (e.g., mote-addressed content logs and/or multi-mote content logs) to other entities (e.g., multi-mote log creation agents at designated mote addresses and/or designated gateway-proximate motes).
- the reporting entities are pre-installed on the motes prior to such motes' insertion to a mote-appropriate network, while in other implementations such reporting entities crawl and/or are transmitted to their respective motes from other locations (e.g., a reporting entity at another mote or another networked computer (not shown) clones itself and sends that clone to another mote).
- one or more of the reporting entities is given access to the content logs of the motes and thereafter use such access to report on the content of the motes.
- the multi-mote content logs and/or mote-addressed content logs may be as shown and/or described both here and elsewhere herein, and such elsewhere described material is typically not repeated here for sake of clarity.
- various reporting entities at various motes transmit in response to a schedule (e.g., once every 24 hours).
- a reporting entity transmits in response to a received schedule (e.g., received from multi-mote log creation agent 716 and/or from federated log creation agent 914 of FIGS. 11 and/or 12 ).
- a reporting entity transmits in response to a derived schedule.
- the schedule is derived in response to one or more optimized queries.
- the schedule is derived in response to one or more stored queries (e.g., previously received and/or generated queries).
- the reporting entities transmit in response to received queries (e.g., received from multi-mote log creation agents or federated log creation agents). In various implementations, the reporting entities transmit using either or both public key and private key encryption techniques. In various other implementations, the reporting entities decode previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.
- multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 to another entity (e.g., another multi-mote log creation agent at a designated mote address, or a designated gateway-proximate mote or a federated log creation agent such as shown and/or described in relation to FIGS. 7 , 8 , 9 , 11 , and/or 12 ).
- another entity e.g., another multi-mote log creation agent at a designated mote address, or a designated gateway-proximate mote or a federated log creation agent such as shown and/or described in relation to FIGS. 7 , 8 , 9 , 11 , and/or 12 .
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of transmitting at least a part of one or more multi-mote content logs of the first set of motes.
- multi-mote reporting entity 602 transmits at least a part of at least one of a mote-addressed sensing/control log of multi-mote content log 504 to another entity (e.g., another multi-mote log creation agent at a designated mote address or a designated gateway-proximate mote or a federated log creation agent such as shown and/or described in relation to FIGS. 11 and/or 12 ).
- another entity e.g., another multi-mote log creation agent at a designated mote address or a designated gateway-proximate mote or a federated log creation agent such as shown and/or described in relation to FIGS. 11 and/or 12 .
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of transmitting at least a part of a mote-addressed routing/spatial log.
- multi-mote reporting entity 602 transmits at least a part of a mote-addressed routing/spatial log of multi-mote content log 504 to another entity (e.g., another multi-mote log creation agent at a designated mote address, or a designated gateway-proximate mote, or a federated log creation agent such as shown and/or described in relation to FIGS. 7 , 8 , 9 , 11 and/or 12 ).
- another entity e.g., another multi-mote log creation agent at a designated mote address, or a designated gateway-proximate mote, or a federated log creation agent such as shown and/or described in relation to FIGS. 7 , 8 ,
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of effecting the transmitting with a reporting entity.
- multi-mote reporting entity 602 is a logical process at mote 600 that transmits a part of an aggregate of one or more mote-addressed content logs (e.g., multi-mote logs and/or aggregations of other logs such as mote-addressed and multi-mote logs).
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of obtaining access to the one or more mote-addressed content logs of the first set of motes.
- multi-mote reporting entity 602 is granted the access by an entity such as a system administrator.
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of effecting the transmitting in response to a schedule.
- multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 in response to a schedule (e.g., once every 24 hours).
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of receiving the schedule.
- multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 in response to a received schedule (e.g., received from multi-mote log creation agent 718 and/or a federated log creation agent 914 of FIGS. 11 and/or 12 ).
- a received schedule e.g., received from multi-mote log creation agent 718 and/or a federated log creation agent 914 of FIGS. 11 and/or 12 .
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of deriving the schedule.
- multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 in response to a derived schedule (e.g., derived in response to an optimized query and/or one or more stored queries).
- a derived schedule e.g., derived in response to an optimized query and/or one or more stored queries.
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of effecting the transmitting in response to a query.
- multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 in response to a received query (e.g., received from a multi-mote log creation agent or a federated log creation agent).
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of encrypting utilizing at least one of a private or a public key.
- multi-mote reporting entity 602 transmits at least a part of multi-mote content log 504 using either or both public key and private key encryption techniques.
- the operation of transmitting at least a part of an aggregate of one or more mote-addressed content logs of a first set of motes includes but is not limited to the operation of decoding at least a part of one or more mote-addressed content logs utilizing at least one of a public key or a private key.
- multi-mote reporting entity 602 decodes previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting of at least a part of multi-mote content log 504 .
- FIG. 10 shown is a high-level diagram of first-administered set 1000 of motes addressed 1 A through MA, and second-administered set 1002 of motes addressed 1 B through NB (M and N are integers greater than 1; A and B are letters used herein to help distinguish differently administered networks as in FIGS. 10 , 11 , and 12 ) that may form an environment for process(es) and/or device(s) described herein.
- first-administered set 1000 of motes constitutes all or part of a network under a first administrator and second-administered set 1002 of motes constitutes all or part of a network under a second administrator, where the first and/or second administrators tend not to have any significant knowledge of the internal operations of networks they don't administer. Examples in which this may be the case are where first-administered set 1000 and second-administered set 1002 are owned by different business entities, and where first-administered set 1000 and second-administered set 1002 have been constructed for two separate purposes (e.g., one set to monitor crops and the other set to monitor building systems, and thus the systems were not designed to interact with each other).
- first-administered set 1000 of motes constitutes all or part of a network under a first administrator and second-administered set 1002 of motes constitutes all or part of a network under a second administrator, where either or both of the first administrator and the second administrator has some knowledge of the networks they don't administer, but the networks are administered separately for any of a variety of reasons such as security, current employment, permissions, job function distinction, organizational affiliation, workload management, physical location, network disconnection, bandwidth or connectivity differences, etc.
- first-administered set 1000 of motes constitutes all or part of a network under a first transient administration and second-administered set 1002 of motes constitutes all or part of a network under a second transient administration, where either or both the first and second transient administrations are those such as might exist when a network partitions or a signal is lost.
- the inventors have noticed that in some instances it could be advantageous for one or more systems to use resources from first-administered set 1000 of motes and second-administered set 1002 of motes.
- the inventors have devised one or more processes and/or devices that allow systems to use resources in such a fashion.
- first-administered set 1000 of motes and second-administered set 1002 of motes modified in accordance with teachings of subject matter described herein. Shown respectively proximate to first-administered set 1000 of motes and second-administered set 1002 of motes are gateways 704 , 706 onto WAN 714 . Gateways 704 , 706 are respectively shown as having resident within them multi-mote log creation agents 716 , 718 and aggregations 910 , 912 of first-administered set 1000 of motes and second-administered set 1002 of motes.
- the gateways, multi-mote log creation agents, and aggregations are created and/or function substantially analogously to the gateways, log creation agents, and aggregations of logs described elsewhere herein (e.g., in relation to Figures), and are not explicitly described here for sake of clarity.
- aggregation 910 of first-administered logs and aggregation 912 of second-administered logs can be composed of either or both mote-addressed and/or multi-mote content logs and in themselves can be considered instances of multi-mote content logs.
- log creation agents e.g., multi-mote or other type
- logs e.g., multi-mote or other type
- reporting entities e.g., multi-mote or other type
- the functioning and/or creation of such logs, agents, and/or entities is under the control of federated log creation agent 914 .
- federated log creation agent 914 on an as-needed basis, disperses and/or activates various log creation agents and/or their associated reporting entities (e.g., as shown and described in relation to FIGS.
- first-administered set 1000 of motes and second-administered set 1002 of motes are pre-programmed.
- dispersals and/or activations are done on an as-needed basis, while in other implementations such dispersals and activations are pre-programmed.
- the agents, logs, and/or entities are pre-programmed.
- federated log creation agent 914 and federated log 916 resident within mainframe computer system 990 , which in some implementations are dispersed, created, and/or activated in fashions similar to other log creation agents and logs described herein.
- federated log creation agent 914 generates federated log 916 by obtaining at least a part of one or more logs (e.g., multi-mote or mote-addressed logs) from both first-administered set 1000 of motes and second-administered set 1002 of motes.
- federated log 916 typically includes at least a part of a content log from two differently-administered mote networks, such as first-administered set 1000 of motes and second-administered set 1002 of motes
- federated log 916 has one or more entries denoting one or more respective administrative domains of one or more content log entries (e.g., see federated log 916 of FIG. 12 ).
- federated log 916 has access information to one or more content logs for an administered content log (e.g., in some implementations, this is actually in lieu of a content log).
- federated log 916 has information pertaining to a currency of at least one entry of an administered content log. In other implementations, federated log 916 has information pertaining to an expiration of at least one entry of an administered content log. In other implementations, federated log 916 has metadata pertaining to an administrative domain, wherein the metadata includes at least one of an ownership indicator, an access right indicator, a log refresh indicator, or a predefined policy indicator. In other implementations, federated log 916 has an administrative domain-specific query string generated for or supplied by an administrative domain to produce an updated content log for that domain.
- aggregation 910 of first-administered log and aggregation 912 of second-administered log are shown as respectively interfacing with first-administered reporting entity 902 and second-administered reporting entity 904 .
- First-administered reporting entity 902 and/or second-administered reporting entity 904 typically are dispersed, created, and/or activated in fashions analogous to the dispersal, creation, and/or activation of other reporting entities as described elsewhere herein (e.g., in relation to FIGS. 3 and/or 6 ), and hence such dispersals, creations, and/or activations are not explicitly described here for sake of clarity.
- first-administered reporting entity 902 and/or second-administered reporting entity 904 transmit all/part of their respective multi-mote content logs to federated log creation agent 914 , from which federated log creation agent creates federated log 916 .
- First-administered reporting entity 902 and/or second-administered reporting entity 904 transmit in manners analogous to reporting entities discussed elsewhere herein. For example, transmitting in response to schedules received, schedules derived, and/or queries received from federated log creation agent 914 , and/or transmitting using either or both public key and private key encryption techniques and/or decoding previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.
- federated log creation agent 914 was described as obtaining portions of aggregations of first-administered and second-administered network logs from which federated log 916 was constructed. In other implementations, federated log creation agent 914 obtains portions of first-administered and second-administered network logs from various reporting entities dispersed throughout the first-administered and second-administered mote networks 1000 , 1002 (e.g., multi-mote or other type reporting entities such as those described in relation to FIGS. 3 , 6 , and/or elsewhere herein). Such reporting entities and logs are implicit in FIG.
- reporting entities dispersed throughout the networks report directly to federated log creation agent 914 .
- One example of such implementations is shown and described in relation to FIG. 12 .
- FIG. 12 shown is the high-level diagram of FIG. 11 , modified to show first-administered set 1000 of motes and second-administered set 1002 of motes wherein each mote is illustrated as having log(s) (e.g., mote-addressed and/or multi-mote) and associated reporting entity(ies).
- the reporting entities may be of substantially any type described herein (e.g., multi-mote or other type) and the logs may also be of substantially any type described herein (e.g., multi-mote or mote-addressed content log).
- various reporting entities dispersed throughout first-administered set 1000 of motes and second-administered set 1002 of motes transmit all/part of their respective logs (multi-mote or otherwise) to federated log creation agent 914 , from which federated log creation agent creates federated log 916 .
- the various reporting entities transmit in manners analogous to reporting entities discussed elsewhere herein. For example, transmitting in response to schedules received, schedules derived, and/or queries received from federated log creation agent 914 , and/or transmitting using either or both public key and private key encryption techniques and/or decoding previously encrypted data, using either or both public key and private key encryption techniques, prior to the transmitting.
- Federated log 916 is shown to contain aggregations of content logs drawn from first-administered set 1000 of motes and second-administered set 1002 of motes. Shown is that federated log 916 contains aggregated sensing/control and routing/spatial logs for motes addressed 1 A and 2 A under the administration of a first network administrator. Depicted is that federated log 916 contains aggregated sensing/control and routing/spatial logs for motes addressed 3 A and 4 A under the administration of a second network administrator.
- aggregations for only two administered networks are shown, those having skill in the art will appreciate that in some implementations the number of administered networks logged could be several.
- each individual administrator-specific aggregation is shown containing entries for only three motes, those having skill in the art will appreciate that in most implementations the number of motes in the aggregations will run to the hundreds, thousands, and/or higher.
- Some exemplary processes include the operations of obtaining at least a part of a first-administered content log from a first set of motes; obtaining at least a part of a second-administered content log from a second set of motes; and creating a federated log from at least a part of the first-administered content log and at least a part of the second-administered content log.
- Other more general exemplary processes of the foregoing specific exemplary processes are taught at least in the claims and/or elsewhere in the present application.
- the operation of obtaining at least a part of a first-administered content log from a first set of motes includes but is not limited to the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes.
- federated log creation agent 914 receiving at least a part of the multi-mote content log 752 of mote 6 A (e.g., such as shown and described in relation to FIGS. 7 , 8 , . . . , and/or 13 ).
- the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing/control log from at least one aggregation of one or more first-administered logs.
- federated log creation agent 914 receiving at least a part of aggregation of first-administered log(s) 910 as transmitted by first-administered reporting entity 902 for first-administered set 1000 of motes (e.g., as shown and/or described in relation to FIGS. 7 , 8 , . . . , and/or 13 ).
- the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from at least one aggregation of one or more first-administered logs.
- federated log creation agent 914 receiving at least a part of aggregation of first-administered log(s) 910 as transmitted by first-administered reporting entity 902 for first-administered set 1000 of motes (e.g., as shown and/or described in relation to FIGS. 7 , 8 , . . . , and/or 13 ).
- the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing log or a mote-addressed control log from a multi-mote reporting entity at a mote of the first set of motes.
- federated log creation agent 914 receiving at least a part of one or more multi-mote content logs of first-administered set 1000 of motes from one or more multi-mote content logs' associated multi-mote reporting entities (e.g., such as shown and/or described in relation to the multi-mote content logs and/or associated reporting entities of first-administered set 800 of motes of FIGS. 7 , 8 , . . . , and/or 13 ).
- multi-mote content logs of first-administered set 1000 of motes from one or more multi-mote content logs' associated multi-mote reporting entities (e.g., such as shown and/or described in relation to the multi-mote content logs and/or associated reporting entities of first-administered set 800 of motes of FIGS. 7 , 8 , . . . , and/or 13 ).
- the operation of receiving at least a part of one or more multi-mote content logs of the first set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from a multi-mote reporting entity at a mote of the first set of motes.
- federated log creation agent 914 receiving at least a part of a mote-addressed routing/spatial log from a multi-mote reporting entity at a mote of the first-administered set 1000 of motes (e.g., such as shown and/or described in relation to the multi-mote content log of mote 6 A of FIGS. 7 , 8 , . . . , and/or 13 ).
- the operation of obtaining at least a part of a first-administered content log from a first set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing/control log from a reporting entity at a mote of the first set of motes.
- the operation of obtaining at least a part of a first-administered content log from a first set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from a reporting entity at a mote of the first set of motes.
- federated log creation agent 914 receiving at least a part of a mote-addressed routing/spatial log from one or more associated reporting entities at the motes of first-administered set 1000 of motes (e.g., such as shown and/or described in relation to the mote-addressed content logs of motes 3 A and/or 5 A of 7 , 8 , . . . , and/or 13 ).
- the operation of obtaining at least a part of a second-administered content log from a second set of motes includes but is not limited to the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes.
- federated log creation agent 914 receiving at least a part of the multi-mote content log associated with a mote of second-administered set 1002 of motes (e.g., such as shown and/or described in relation to FIGS. 10 , 11 , 12 and/or 13 ).
- the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing log/control log from at least one aggregation of one or more second-administered logs.
- federated log creation agent 914 receiving at least a part of aggregation of second-administered log(s) 912 as transmitted by second-administered reporting entity 904 for second-administered set 1002 of motes (e.g., as shown and/or described in relation to FIGS. 10 , 11 , 12 , and/or 13 ).
- the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from at least one aggregation of one or more second-administered logs.
- federated log creation agent 914 receiving at least a part of aggregation of second-administered log(s) 912 transmitted by second-administered reporting entity 904 for second-administered set 1002 of motes (e.g., as shown and described in relation to FIGS. 10 , 11 , 12 , and/or 13 ).
- the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing/control log from a multi-mote reporting entity at a mote of the second set of motes.
- federated log creation agent 914 receiving at least a part of one or more multi-mote content logs of second-administered set 1002 of motes from one or more multi-mote content logs' associated multi-mote reporting entities (e.g., such as shown and described in relation to the multi-mote content logs and/or reporting entities of second-administered set 1002 of motes of FIGS. 10 , 11 , 12 and/or 13 ).
- the operation of receiving at least a part of one or more multi-mote content logs of the second set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from a multi-mote reporting entity at a mote of the second set of motes.
- federated log creation agent 914 receiving at least a part of a mote-addressed routing/spatial log from a multi-mote reporting entity at a mote of the second-administered set 1002 of motes from an associated multi-mote reporting entity (e.g., such as shown and described in relation to the multi-mote content logs and/or reporting entities of second-administered set 1002 of motes of FIGS. 10 , 11 , 12 , and/or 13 ).
- the operation of obtaining at least a part of a second-administered content log from a second set of motes includes but is not limited to the operation of receiving at least a part of at least one of a mote-addressed sensing/control log from a reporting entity at a mote of the second set of motes.
- federated log creation agent 914 receiving at least a part of a mote-addressed sensing/control log from one or more associated reporting entities at the motes of second-administered set 1002 of motes (e.g., such as shown and described in relation the mote-addressed content logs and associated reporting entities of second-administered set 1002 of motes of FIGS. 10 , 11 , 12 and/or 13 ).
- the operation of obtaining at least a part of a second-administered content log from a second set of motes includes but is not limited to the operation of receiving at least a part of a mote-addressed routing/spatial log from a reporting entity at a mote of the second set of motes.
- federated log creation agent 914 receiving at least a part of a mote-addressed routing/spatial log from one or more associated reporting entities at the motes of second-administered set 1002 of motes (e.g., such as shown and described in relation the mote-addressed content logs of second-administered set 1002 of motes of FIGS. 10 , 11 , 12 , and/or 13 ).
- the operation of creating a federated log from at least a part of the first-administered content log and at least a part of the second-administered content log includes the operation of federated log creation agent 914 generating federated log 916 in response to one or more logs (e.g., multi-mote and/or mote-addressed logs) obtained from both first-administered set 1000 of motes and the second-administered set 1002 of motes.
- logs e.g., multi-mote and/or mote-addressed logs
- federated log creation agent 914 creates federated log 916 to include at least a part of a content log from two differently-administered mote networks, such as first-administered set 1000 of motes and second-administered set 1002 of motes (see., e.g., federated log 916 of FIG. 13 ).
- federated log creation agent 914 creates federated log 916 to include one or more entries denoting one or more respective administrative domains of one or more content log entries (e.g., see federated log 916 of FIG. 13 ).
- federated log creation agent 914 creates federated log 916 to include access information to one or more content logs for an administered content log (e.g., in some implementations, this is actually in lieu of a content log). In other implementations, federated log creation agent 914 creates federated log 916 to include information pertaining to a currency of at least one entry of an administered content log. In other implementations, federated log creation agent 914 creates federated log 916 to include information pertaining to an expiration of at least one entry of an administered content log.
- federated log creation agent 914 creates federated log 916 to include metadata pertaining to an administrative domain, wherein the metadata includes at least one of an ownership indicator, an access right indicator, a log refresh indicator, or a predefined policy indicator.
- federated log creation agent 914 creates federated log 916 to include an administrative domain-specific query string generated for or supplied by an administrative domain to produce an updated content log for that domain.
- the operation of creating a federated log from at least a part of the first-administered content log and at least a part of the second-administered content log includes but is not limited to the operations of creating the federated log from at least a part of one or more multi-mote content logs of the first set of motes; creating the federated log from at least a part of at least one of a mote-addressed sensing/control log or a mote-addressed routing log/spatial log of the first set of motes; creating the federated log from at least a part of one or more multi-mote content logs of the second set of motes; and/or creating the federated log from at least a part of at least one of a mote-addressed sensing/control log or a mote-addressed routing log/spatial log of the second set of motes.
- federated log creation agent 914 creating at least a part of federated log 916 in response to portions of multi-mote content logs (e.g., multi-mote logs and/or aggregations of logs) received from reporting entities associated with first-administered set 1000 of motes and/or second-administered set 1002 of motes (e.g., such as shown and described in relation to FIGS. 10 , 11 , 12 , and/or 13 ).
- multi-mote content logs e.g., multi-mote logs and/or aggregations of logs
- Some specific exemplary processes include the operations of creating one or more first-administered content logs for a first set of motes; obtaining at least a part of the one or more first-administered content logs of the first set of motes; creating one or more second-administered content logs for a second set of motes; obtaining at least a part of the second-administered content logs of the second set of motes; and creating a federated log from at least a part of the one or more first-administered content logs and at least a part of the one or more second-administered content logs.
- the operations of creating one or more first-administered content logs for a first set of motes and creating one or more second-administered content logs for a second set of motes function substantially analogously as the processes described in creating mote-addressed content logs, mote-addressed logs, and aggregations of logs as set forth elsewhere herein (e.g., such as shown and/or described under text/drawings of Roman Numeral headings I (“MOTE-ASSOCIATED LOG CREATION”), III (“AGGREGATING MOTE-ASSOCIATED LOG DATA”), and V (“FEDERATING MOTE-ASSOCIATED LOG DATA”), above, as well as in the as-filed claims).
- the operations of obtaining at least a part of the one or more first-administered content logs of the first set of motes; obtaining at least a part of the second-administered content logs of the second set of motes; and creating a federated log from at least a part of the one or more first-administered content logs and at least a part of the one or more second-administered content logs function substantially analogously as to like processes described elsewhere herein (e.g., as shown and described under text/drawings of Roman Numeral heading V (“FEDERATING MOTE-ASSOCIATED LOG DATA”), above, as well as in the as-filed claims).
- the specific exemplary processes of the operations of obtaining at least a part of the one or more first-administered content logs of the first set of motes; obtaining at least a part of the second-administered content logs of the second set of motes; and creating a federated log from at least a part of the one or more first-administered content logs and at least a part of the one or more second-administered content logs are not explicitly redescribed here for sake of clarity, in that such specific exemplary processes will be apparent to one of skill in the art in light of the disclosure herein (e.g., as shown and described under text/drawings of Roman Numeral heading V, above, as well as in the as-filed claims).
- FIG. 14 depicted is a perspective cut-away view of a hallway that may form an environment of processes and/or devices described herein.
- Wall 1400 and floor 1402 are illustrated having motes (depicted as circles and/or ovals).
- the motes may be as described elsewhere herein (e.g., mote 200 , 300 , 500 , and/or 600 ).
- the motes are applied to wall 1400 and/or floor 1402 with an adhesive.
- the motes are formed into 1400 and/or floor 1402 during fabrication.
- a covering for the wall e.g., wallpaper and/or paint
- FIGS. 15 , 16 , and 17 shown are three time-sequenced views of a person transiting wall 1400 and floor 1402 of the hallway of FIG. 14 .
- FIG. 18 depicted is a perspective view of the hallway of FIG. 14 , modified in accord with aspects of the subject matter described herein. Illustrated is that the motes of wall 1400 may be treated as a first set 400 of motes that function and/or are structured in fashions analogous to first set 400 of motes shown/described elsewhere herein (e.g., in relation to FIGS. 4-9 ) and/or as shown/described here. Accordingly, antenna 1802 is shown proximate to wall 1400 and feeding gateway 704 onto WAN 714 .
- Multi-mote log creation agent 716 is depicted as executing on the more powerful computational systems of gateway 704 (e.g., a mini and/or mainframe computer system) to create aggregation 710 of content logs.
- Gateway 704 , multi-mote creation agent 716 , and aggregation 710 of content logs function and/or are structured analogously as described elsewhere herein, and are not expressly re-described here for sake of clarity.
- first set 400 of the physical motes of wall 1400 may be treated as mapped into a conceptual x-y coordinate system.
- the mapping into the conceptual x-y coordinate system may be used to illustrate how a multi-mote content log or aggregation of content logs can be used to advantage.
- the mapping will typically be into a three-space coordinate system (e.g., x-y-z), but that a two-space (e.g., x-y) example is described herein for sake of clarity.
- rectilinear coordinate systems are described herein, those having skill in the art will appreciate that other coordinate systems (e.g., spherical, cylindrical, circular, etc.) may be substituted consistent with the teachers herein.
- FIG. 20 shown is a partially schematic diagram that pictographically illustrates the coordinating of the conceptual mapping of the motes of wall 1400 with the logs of first set 400 of the motes of wall 1400 .
- the mapping of the physical motes as shown in FIG. 19 can be abstracted into mote content logs.
- the mote content logs can be used to “stand in” for or “represent” the first set 400 of motes, and can be managed and/or searched using high speed computer systems.
- FIGS. 21 , 22 , and 23 shown are time-stamped versions of aggregation 710 associated with the state of first set 400 of motes.
- aggregation 710 will generally be in the form of nested data structures and that the pictographic representations of how the person would “appear” in FIGS. 21 , 22 , and 23 are used herein for sake of clarity.
- motes can include any number of devices whose information can be captured in aggregates of content logs (e.g., aggregation 710 of content logs). Accordingly, aggregation 710 allows flexible and powerful searching techniques, a few of which will now be described.
- Method step 2400 shows the start of the process.
- Method step 2402 depicts accepting input defining a mote-appropriate network search.
- Method step 2404 searching at least one mote-addressed content log in response to said input.
- Method step 2406 shows the end of the process.
- method step 2402 includes method step 2500 .
- Method step 2500 shows accepting a visual-definition input.
- electrical circuitry accepts the visual-definition input.
- electrical circuitry e.g., electrical circuitry configured to provide a graphical user interface (GUI)
- GUI graphical user interface
- electrical circuitry e.g., electrical circuitry configured to provide a graphical user interface (GUI) accepts a request to search for a particular shape (e.g., a line drawing of a prone person, such as might appear if a person were to fall onto the motes of floor 1402 of FIG. 14 ).
- GUI graphical user interface
- the visual-definition input may be more abstract, such as, for example, a request may be in the form of spatial frequency content, spectral components, or other aspects of a searched for object, event or set of objects.
- method step 2402 includes method step 2502 .
- Method step 2502 shows accepting at least one of an infrared-definition input or a temperature-definition input.
- electrical circuitry accepts the at least one of an infrared-definition input or a temperature-definition input.
- electrical circuitry e.g., electrical circuitry configured to provide a graphical user interface (GUI) accepts a command to search for a particular infra-red signature or temperature (e.g., an infrared signature or temperature in closet of a building indicate of a potential spontaneous combustion).
- GUI graphical user interface
- electrical circuitry e.g., a touch screen of a computer system showing motes superimposed over particular plants or plant groupings
- accepts a request to monitor various plants or groups of plants for either or both a particular infrared signature or temperature profile e.g., a defined range of temperatures for optimal growing, such as might be controlled in a greenhouse environment.
- method step 2402 includes method step 2504 .
- Method step 2504 shows accepting a pressure-definition input.
- electrical circuitry accepts the pressure-definition input.
- electrical circuitry e.g., electrical circuitry configured to provide a graphical user interface (GUI) accepts a command to sound an alert if a specified pressure at any one or more motes is exceeded (e.g., a pressure sensed by one or more motes interior to a cast indicates a potential for ischemic necrosis or neural impairment).
- GUI graphical user interface
- electrical circuitry e.g., an input panel exterior to a piping system
- method step 2402 includes method step 2506 .
- Method step 2506 shows accepting a sonic-definition input.
- electrical circuitry accepts the sonic-definition input.
- electrical circuitry e.g., electrical circuitry configured to convert microphone input to a digital audio file and/or configured to accept digital audio directly
- electrical circuitry accepts a request that a system determine whether a particular voice has been heard in a room during some defined interval of time (e.g., have you heard “this voice” during the last 24 hours where “this voice” could either be a sample captured in real time or a stored sample of voice).
- electrical circuitry e.g., electrical circuitry configured to accept digital audio directly
- accepts a request that the system perform an action when a certain sound pattern over time is detected e.g., if the sonic-definition input where a time series of audio that indicated that a hard disk failure was imminent, request would be that the system order a new hard disk and perform a disk swap at some time before the predicted imminent failure).
- method step 2404 includes method step 2600 .
- Method step 2600 shows searching a time series of at least two content logs.
- electrical circuitry successively searches a time series of content logs for various defined types of information.
- electrical circuitry e.g., electrical circuitry forming a processor configured by program to perform various tasks
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 2402 .
- method step 2404 includes method step 2602 .
- Method step 2602 shows searching at least one multi-mote content log having the at least one mote-addressed content log.
- electrical circuitry searches the at least one multi-mote content log having the at least one mote-addressed content log.
- electrical circuitry searches one or more multi-mote content logs, over time, in response to a defined search (e.g., electrical circuitry searching one or more multi-mote content logs for motes distributed proximate to a patient's heart for sounds indicative of arrhythmia, in response to a search requesting that the logs be so searched).
- a defined search e.g., electrical circuitry searching one or more multi-mote content logs for motes distributed proximate to a patient's heart for sounds indicative of arrhythmia, in response to a search requesting that the logs be so searched.
- electrical circuitry searches one or more multi-mote content logs, over time, in response to a defined search (e.g., electrical circuitry searching one or more multi-mote content logs for motes in a defined area of aviation equipment, such as a jet engine, for sounds indicative of motor failure, in response to a search requesting that the logs be so searched).
- a defined search e.g., electrical circuitry searching one or more multi-mote content logs for motes in a defined area of aviation equipment, such as a jet engine, for sounds indicative of motor failure, in response to a search requesting that the logs be so searched.
- method step 2602 includes method step 2700 .
- Method step 2700 shows searching a time series of at least two multi-mote logs, the time series including the at least one multi-mote content log having the at least one mote-addressed content log.
- electrical circuitry successively searches a time series of content logs for various defined types of information.
- electrical circuitry e.g., electrical circuitry forming a processor configured by program to perform various tasks
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 2402 .
- Method step 2604 shows searching at least one aggregation of content logs, the aggregation having the at least one mote-addressed content log.
- electrical circuitry searches the at least one aggregation of content logs, the aggregation having the at least one mote-addressed content log.
- electrical circuitry e.g., electrical circuitry forming a processor configured by program to perform various tasks
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 2402 .
- method step 2604 includes method step 2800 .
- Method step 2800 illustrates searching a time series of at least two aggregations of content logs, the time series including the at least one aggregation of content logs.
- electrical circuitry searches the time series of the at least one aggregation of content logs.
- electrical circuitry e.g., electrical circuitry forming a processor configured by program to perform various tasks
- t_ 1 FIG. 21
- t_ 2 FIG. 22
- t_ 3 FIG. 23
- method step 2604 includes method step 2804 .
- Method step 2804 illustrates searching at least one multi-mote content log of the at least one aggregation of content logs.
- electrical circuitry is used to effect the searching at least one multi-mote content log of the at least one aggregation of content logs.
- the searching described in relation to various processes herein is performed on mote-addressed content logs, multi-mote content logs, and/or aggregations of content logs loaded to computer systems external to a mote-appropriate network.
- gateway 704 which can include, for example, one or more of a notebook computer system, minicomputer system, server computer system, and/or a mainframe computer system.
- the searching described in relation to various processes herein e.g., such as those shown/described in relation to FIGS.
- FIG. 29 illustrated is the perspective cut-away view of the hallway of FIG. 14 modified in accord with aspects of the subject matter described herein. Illustrated is that the motes of wall 1400 may be partitioned into first-administered set 1000 , of motes and second-administered set 1002 of motes analogous to the first-administered set 1000 of motes and second-administered set 1002 of motes shown/described elsewhere herein (e.g., in relation to FIGS. 10-13 ). Antenna 2900 is shown proximate to first-administered set 1000 of motes and shown feeding gateway 704 onto WAN 714 .
- Multi-mote log creation agent 716 is depicted as executing on the more powerful computational system(s) of gateway 704 (e.g., a mini and/or a mainframe computer system) to create aggregation 910 of first-administered content logs.
- First-administered reporting entity 902 is illustrated as executing on gateway 704 .
- Gateway 704 , multi-mote log creation agent 716 , aggregation 910 of first-administered content logs, and first-administered reporting entity 902 function and/or are structured in fashions analogous to those described here and/or elsewhere herein.
- Antenna 2902 is shown proximate to second-administered set 1002 of motes and feeding gateway 706 onto WAN 714 .
- Multi-mote log creation agent 718 is depicted as executing on the more powerful computational system(s) of gateway 706 (e.g., a mini and/or a mainframe computer system) to create aggregation 912 of second-administered content logs.
- Second-administered reporting entity 904 is illustrated as executing on gateway 706 .
- Gateway 706 multi-mote log creation agent 718 , aggregation 912 of second-administered content logs, and second-administered reporting entity 904 function and/or are structured in fashions analogous to those described here and/or elsewhere herein.
- frequency re-use techniques are utilized across first-administered set 1000 of motes and second-administered set 1002 of motes. For instance, first-administered set 1000 of motes operating on or around a first carrier frequency and second-administered set 1002 of motes operating on or around a second carrier frequency. Accordingly, in some implementations antenna 2900 is tuned to a carrier frequency of first-administered set 1000 of motes and antenna 2902 is tuned to a carrier frequency of second-administered set 1002 of motes.
- frequency re-use techniques are not used across first-administered set 1000 of motes and second-administered set 1002 of motes (e.g., the differently administered networks use different addressing spaces and/or proximities to provide for the separate network administrations).
- federated log creation agent 914 and federated content log 916 resident within mainframe computer system 990 .
- Federated log creation agent 914 , federated content log 916 , and mainframe computer system 990 function and/or are structured in fashions analogous to those described here and/or elsewhere herein.
- first-administered set 1000 and second-administered set 1002 of the physical motes of wall 1400 may be treated as mapped into a conceptual x-y coordinate system.
- the mapping into the conceptual x-y coordinate system may be used to illustrate how a multi-mote content log or aggregation of content logs (e.g., such as those forming at least a part of federated content log 916 ) can be used to advantage.
- the mapping will typically be into a three-space coordinate system (e.g., x-y-z), but that a two-space (e.g., x-y) example is described herein for sake of clarity.
- rectilinear coordinate systems are described herein, those having skill in the art will appreciate that other coordinate systems (e.g., spherical, cylindrical, circular, etc.) may be substituted consistent with the teachings herein.
- FIG. 31 shown is a partially schematic diagram that pictographically illustrates the coordinating of the conceptual mapping of the motes of wall 1400 with logs of first-administered set 1000 and second-administered set 1002 of the physical motes of wall 1400 .
- This abstraction is illustrated in FIG. 31 by the dashed lines indicating the motes.
- the mapping of the physical motes shown in FIG. 30 can be abstracted into aggregation 910 of first-administered content logs and aggregation 912 of second-administered content logs.
- the mote content logs can be used to “stand in” for or “represent” first-administered set 1000 and/or second-administered set 1002 of the physical motes of wall 1400 , and can be independently and/or jointly managed and/or searched using high speed computer systems.
- FIG. 32 shown are time-stamped versions of aggregation 910 of first-administered content logs associated with the state of first-administered set 1000 of motes.
- aggregation 910 of first-administered content logs will generally be in the form of nested data structures and that the pictographic representations of how the person would “appear” in FIG. 32 are used herein for sake of clarity.
- FIG. 33 depicted are time-stamped versions of aggregation 912 of second-administered content logs associated with the state of second-administered set 1002 of motes.
- aggregation 912 of second-administered content logs will generally be in the form of nested data structures and that the pictographic representations of how the person would “appear” in FIG. 33 are used herein for sake of clarity.
- a separate administration scheme paired with the federation schemes as described herein allows use of mote networks to track large and/or dense subject matter domains with less resource utilization (e.g., less power consumption such as that associated with either or both less transmission, and/or less reception).
- FIGS. 34 , 35 , and 36 illustrated are different versions of federated content log 916 .
- federated content log 916 will generally be in the form of nested data structures and that the pictographic representations of how the person would “appear” in FIGS. 34 , 35 , and 36 are used herein for sake of clarity.
- motes can include any number of devices whose information can be captured in content logs (e.g., federated content log 916 ). Accordingly, federated content log 916 allows flexible and powerful searching techniques, a few of which will now be described.
- Method step 3700 shows the start of the process.
- Method step 3702 depicts accepting input defining a mote-appropriate network search.
- Method step 3704 depicts searching at least one federated log in response to said accepted input.
- Method step 3706 shows the end of the process.
- method step 3702 includes method step 3800 .
- Method step 3800 shows accepting a visual-definition input.
- electrical circuitry accepts the visual-definition input.
- electrical circuitry e.g., electrical circuitry configured to provide a graphical user interface (GUI)
- GUI graphical user interface
- electrical circuitry e.g., electrical circuitry configured to provide a graphical user interface (GUI) accepts a request to search for a particular shape (e.g., a line drawing of a prone person, such as might appear if a person were to fall onto the motes of floor 1402 of FIG. 14 ).
- GUI graphical user interface
- the visual-definition input may be more abstract, such as, for example, a request may be in the form of spatial frequency content, spectral components, or other aspects of a searched for object, event or set of objects.
- method step 3702 includes method step 3802 .
- Method step 3802 shows accepting at least one of an infrared-definition input or a temperature-definition input.
- electrical circuitry accepts the at least one of an infrared-definition input or a temperature-definition input.
- electrical circuitry e.g., electrical circuitry configured to provide a graphical user interface (GUI) accepts a command to search for a particular infra-red signature or temperature (e.g., an infrared signature or temperature in a closet of a building indicative of a potential spontaneous combustion).
- electrical circuitry e.g., a touch screen of a computer system showing motes superimposed over particular plants or plant groupings
- accepts a request to monitor various plants or groups of plants for either or both a particular infrared signature or temperature profile e.g., a defined range of temperatures for optimal growing, such as might be controlled in a greenhouse environment.
- method step 3702 includes method step 3804 .
- Method step 3804 shows accepting a pressure-definition input.
- electrical circuitry accepts the pressure-definition input.
- electrical circuitry e.g., electrical circuitry configured to provide a graphical user interface (GUI) accepts a command to sound an alert if a specified pressure at any one or more motes is exceeded (e.g., a pressure sensed by one or more motes interior to a cast indicates a potential for ischemic necrosis or neural impairment).
- GUI graphical user interface
- electrical circuitry e.g., an input panel exterior to a piping system
- method step 3702 includes method step 3806 .
- Method step 3806 shows accepting a sonic-definition input.
- electrical circuitry accepts the sonic-definition input.
- electrical circuitry e.g., electrical circuitry configured to convert microphone input to a digital audio file and/or configured to accept digital audio directly
- electrical circuitry accepts a request that a system determine whether a particular voice has been heard in a room during some defined interval of time (e.g., have you heard “this voice” during the last 24 hours where “this voice” could either be a sample captured in real time or a stored sample of voice).
- electrical circuitry e.g., electrical circuitry configured to accept digital audio directly
- accepts a request that the system perform an action when a certain sound pattern over time is detected e.g., if the sonic-definition input where a time series of audio that indicated that a hard disk failure was imminent, request would be that the system order a new hard disk and perform a disk swap at some time before the predicted imminent failure).
- method step 3704 includes method step 3906 .
- Method step 3906 shows searching a federated log having at least one first-administered content log and at least one second-administered content log.
- electrical circuitry successively searches the at least one first-administered content log and at least one second-administered content log for various defined types of information.
- electrical circuitry e.g., electrical circuitry forming a processor configured by a program to perform various tasks
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 3702 .
- method step 3906 includes method step 4000 .
- Method step 4000 illustrates searching at least one of a first-administered mote-addressed content log, a first-administered multi-mote content log, or a first-administered aggregation of content logs and searching at least one of a second-administered mote-addressed content log, a second-administered multi-mote content log, or a second-administered aggregation of content logs.
- electrical circuitry searches the at least one of a first-administered mote-addressed content log, a first-administered multi-mote content log, or a first-administered aggregation of content logs and at least one of a second-administered mote-addressed content log, a second-administered multi-mote content log, or a second-administered aggregation of content logs for various defined types of information.
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 3702 .
- method step 3704 includes method step 3900 .
- Method step 3900 shows searching a time series of at least two federated logs.
- electrical circuitry successively searches a time series of federated logs for various defined types of information.
- electrical circuitry e.g., electrical circuitry forming a processor configured by program to perform various tasks
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 3702 .
- Method step 3902 shows searching at least one multi-mote content log of the at least one federated log.
- electrical circuitry searches at least one multi-mote content log of the at least one federated log.
- electrical circuitry searches one or more multi-mote content logs, over time, in response to a defined search (e.g., electrical circuitry searching one or more multi-mote content logs for motes distributed proximate to a patient's heart for sounds indicative of arrhythmia, in response to a search requesting that the logs be so searched).
- electrical circuitry searches one or more multi-mote content logs, over time, in response to a defined search (e.g., electrical circuitry searching one or more multi-mote content logs for motes in a defined area of aviation equipment, such as a jet engine, for sounds indicative of motor failure in response to a search requesting that the logs be so searched).
- a defined search e.g., electrical circuitry searching one or more multi-mote content logs for motes in a defined area of aviation equipment, such as a jet engine, for sounds indicative of motor failure in response to a search requesting that the logs be so searched.
- method step 3902 includes method step 4100 .
- Method step 4100 shows searching a time series of at least two multi-mote logs, the time series including the at least one multi-mote content log of the at least one federated log.
- electrical circuitry successively searches a time series of content logs for various defined types of information.
- electrical circuitry e.g., electrical circuitry forming a processor configured by program to perform various tasks
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 3702 .
- method step 3704 includes method step 3904 .
- Method step 3904 shows searching at least one aggregation of content logs, wherein the at least one aggregation of content logs forms a part of the at least one federated log.
- electrical circuitry searches the at least one aggregation of content logs, wherein the at least one aggregation of content logs forms a part of the at least one federated log.
- electrical circuitry e.g., electrical circuitry forming a processor configured by program to perform various tasks
- method step 3904 includes method step 4200 .
- Method step 4200 illustrates searching a time series of at least two aggregations of content logs, the time series including the at least one aggregation of content logs, wherein the at least one aggregation of content logs forms a part of the at least one federated log.
- electrical circuitry searches the at least two aggregations of content logs, the time series including the at least one aggregation of content logs, wherein the at least one aggregation of content logs forms a part of the at least one federated log.
- electrical circuitry e.g., electrical circuitry forming a processor configured by program to perform various tasks
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 3702 .
- method step 3904 includes method step 4202 .
- Method step 4202 illustrates searching at least one mote-addressed content log of the at least one aggregation of content logs, wherein the at least one aggregation of content logs forms a part of the at least one federated log.
- electrical circuitry is used to effect the searching at least one mote-addressed content log of the at least one aggregation of content logs, wherein the at least one aggregation of content logs forms a part of the at least one federated log.
- Those skilled in the art will appreciate that many other searches may be performed, dependent upon the accepted input defining the mote appropriate search of method step 3702 .
- method step 3904 includes method step 4204 .
- Method step 4204 illustrates searching at least one multi-mote content log of the at least one aggregation of content logs, wherein the at least one aggregation of content logs forms a part of the at least one federated log.
- electrical circuitry is used to effect the searching at least one multi-mote content log of the at least one aggregation of content logs.
- the searching described in relation to various processes herein is performed on mote-addressed content logs, multi-mote content logs, and/or aggregations of content logs loaded to computer systems external to a mote-appropriate network.
- gateway 704 which can include, for example, one or more of a notebook computer system, minicomputer system, server computer system, and/or a mainframe computer system.
- the searching described in relation to various processes herein e.g., such as those shown/described in relation to FIGS.
- an implementer may opt for a hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a solely software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.
- any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary.
- Those skilled in the art will recognize that optical aspects of implementations will require optically-oriented hardware, software, and or firmware.
- a signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CD ROMs, digital tape, and computer memory; and transmission type media such as digital and analog communication links using TDM or IP based communication links (e.g., packet links).
- electrical circuitry includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of random access memory), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment).
- a computer program e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein
- electrical circuitry forming a memory device
- a typical mote processing system generally includes one or more of a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, user interfaces, drivers, sensors, actuators, applications programs, one or more interaction devices, such as USB ports, control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities).
- a typical mote processing system may be implemented utilizing any suitable available components, such as those typically found in mote-appropriate computing/communication systems, combined with standard engineering practices. Specific examples of such components include commercially described components such as Intel Corporation's mote components and supporting hardware, software, and firmware.
- any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components.
- any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
- 1. U.S. patent application Ser. No. 10/844,613 entitled MOTE-ASSOCIATED LOG CREATION, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed May 12, 2004.
- 2. U.S. patent application Ser. No. 10/844,564 entitled TRANSMISSION OF MOTE-ASSOCIATED LOG DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed May 12, 2004.
- 3. U.S. patent application Ser. No. 10/844,612 entitled AGGREGATING MOTE-ASSOCIATED LOG DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed May 12, 2004.
- 4. U.S. patent application Ser. No. 10/844,614 entitled TRANSMISSION OF AGGREGATED MOTE-ASSOCIATED LOG DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed May 12, 2004.
- 5. U.S. patent application Ser. No. 10/843,987 entitled FEDERATING MOTE-ASSOCIATED LOG DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed May 12, 2004.
- 6. U.S. patent application Ser. No. 10/816,375 entitled MOTE-ASSOCIATED INDEX CREATION, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed Mar. 31, 2004.
- 7. U.S. patent application Ser. No. 10/816,082 entitled TRANSMISSION OF MOTE-ASSOCIATED INDEX DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed Mar. 31, 2004.
- 8. U.S. patent application Ser. No. 10/816,358 entitled AGGREGATING MOTE-ASSOCIATED INDEX DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed Mar. 31, 2004.
- 9. U.S. patent application Ser. No. 10/816,102 entitled TRANSMISSION OF AGGREGATED MOTE-ASSOCIATED INDEX DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed Mar. 31, 2004.
- 10. U.S. patent application Ser. No. 10/816,364 entitled FEDERATING MOTE-ASSOCIATED INDEX DATA, naming Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed Mar. 31, 2004.
- 11. U.S. patent application Ser. No. 10/813,967 entitled MOTE NETWORKS HAVING DIRECTIONAL ANTENNAS, naming Clarence T. Tegreene as inventor, filed Mar. 31, 2004.
- 12. U.S. patent application Ser. No. 10/814,454 entitled MOTE NETWORKS USING DIRECTIONAL ANTENNA TECHNIQUES, naming Clarence T. Tegreene as inventor, filed Mar. 31, 2004.
- 13. U.S. patent application Ser. No. 10/850,914 entitled USING MOTE-ASSOCIATED LOGS, Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed May 20, 2004.
- 14. U.S. patent application Ser. No. 10/877,099 entitled FREQUENCY REUSE TECHNIQUES IN MOTE-APPROPRIATE NETWORKS, Edward K. Y. Jung and Clarence T. Tegreene as inventors, filed Jun. 25, 2004.
Claims (48)
Priority Applications (18)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/877,109 US7389295B2 (en) | 2004-06-25 | 2004-06-25 | Using federated mote-associated logs |
US10/903,652 US7536388B2 (en) | 2004-03-31 | 2004-07-30 | Data storage for distributed sensor networks |
EP05733117A EP1733574A2 (en) | 2004-03-31 | 2005-03-29 | Using federated mote-associated indexes |
PCT/US2005/010954 WO2005096746A2 (en) | 2004-03-31 | 2005-03-29 | Data storage for distributed sensor networks |
PCT/US2005/010843 WO2005099035A2 (en) | 2004-03-31 | 2005-03-29 | Discovery of occurrence-data |
PCT/US2005/010842 WO2005099287A2 (en) | 2004-03-31 | 2005-03-29 | Using federated mote-associated indexes |
PCT/US2005/010955 WO2005099036A2 (en) | 2004-03-31 | 2005-03-29 | Aggregation and retrieval of network sensor data |
PCT/US2005/010953 WO2005099288A2 (en) | 2004-03-31 | 2005-03-29 | Using mote-associated indexes |
EP05734921A EP1735914A2 (en) | 2004-03-31 | 2005-03-30 | Using federated mote-associated logs |
PCT/US2005/011202 WO2005099102A2 (en) | 2004-03-31 | 2005-03-30 | Using federated mote-associated logs |
PCT/US2005/011225 WO2005099144A2 (en) | 2004-03-31 | 2005-03-30 | Mote appropriate network power reduction techniques |
PCT/US2005/011203 WO2005099037A2 (en) | 2004-03-31 | 2005-03-30 | Frequency reuse techniques in mote-appropriate networks |
US11/999,094 US8352420B2 (en) | 2004-06-25 | 2007-12-04 | Using federated mote-associated logs |
US12/286,736 US8271449B2 (en) | 2004-03-31 | 2008-09-30 | Aggregation and retrieval of mote network data |
US12/454,171 US8275824B2 (en) | 2004-03-31 | 2009-05-12 | Occurrence data detection and storage for mote networks |
US12/454,634 US7941188B2 (en) | 2004-03-31 | 2009-05-19 | Occurrence data detection and storage for generalized sensor networks |
US12/584,058 US8284689B2 (en) | 2004-03-31 | 2009-08-27 | Frequency reuse techniques in mote-appropriate networks |
US16/726,504 US11246017B2 (en) | 2004-03-31 | 2019-12-24 | Mote networks using directional antenna techniques |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/877,109 US7389295B2 (en) | 2004-06-25 | 2004-06-25 | Using federated mote-associated logs |
Related Parent Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/877,099 Continuation-In-Part US7599696B2 (en) | 2004-03-31 | 2004-06-25 | Frequency reuse techniques in mote-appropriate networks |
US10/877,099 Continuation US7599696B2 (en) | 2004-03-31 | 2004-06-25 | Frequency reuse techniques in mote-appropriate networks |
US10/882,119 Continuation-In-Part US20060062252A1 (en) | 2004-03-31 | 2004-06-30 | Mote appropriate network power reduction techniques |
US11/999,094 Continuation-In-Part US8352420B2 (en) | 2004-03-31 | 2007-12-04 | Using federated mote-associated logs |
Related Child Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/850,914 Continuation-In-Part US20060004888A1 (en) | 2004-03-31 | 2004-05-21 | Using mote-associated logs |
US10/850,914 Continuation US20060004888A1 (en) | 2004-03-31 | 2004-05-21 | Using mote-associated logs |
US10/882,119 Continuation-In-Part US20060062252A1 (en) | 2004-03-31 | 2004-06-30 | Mote appropriate network power reduction techniques |
US11/999,094 Continuation US8352420B2 (en) | 2004-03-31 | 2007-12-04 | Using federated mote-associated logs |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050289122A1 US20050289122A1 (en) | 2005-12-29 |
US7389295B2 true US7389295B2 (en) | 2008-06-17 |
Family
ID=35507303
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/877,109 Active 2025-05-18 US7389295B2 (en) | 2004-03-31 | 2004-06-25 | Using federated mote-associated logs |
US11/999,094 Active 2027-01-15 US8352420B2 (en) | 2004-03-31 | 2007-12-04 | Using federated mote-associated logs |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/999,094 Active 2027-01-15 US8352420B2 (en) | 2004-03-31 | 2007-12-04 | Using federated mote-associated logs |
Country Status (1)
Country | Link |
---|---|
US (2) | US7389295B2 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090216713A1 (en) * | 2004-06-25 | 2009-08-27 | Jung Edward K Y | Using federated mote-associated logs |
US8085792B1 (en) | 2007-06-29 | 2011-12-27 | Google Inc. | Traffic-oblivious load balancing protocol for sensor networks |
US8392401B1 (en) * | 2007-06-29 | 2013-03-05 | Google Inc. | Query partitioning to decompose hotspots in sensor networks |
US9756549B2 (en) | 2014-03-14 | 2017-09-05 | goTenna Inc. | System and method for digital communication between computing devices |
US10416661B2 (en) | 2017-11-30 | 2019-09-17 | Abb Schweiz Ag | Apparatuses, systems and methods of secure cloud-based monitoring of industrial plants |
US10944669B1 (en) | 2018-02-09 | 2021-03-09 | GoTenna, Inc. | System and method for efficient network-wide broadcast in a multi-hop wireless network using packet echos |
US11082344B2 (en) | 2019-03-08 | 2021-08-03 | GoTenna, Inc. | Method for utilization-based traffic throttling in a wireless mesh network |
US11811642B2 (en) | 2018-07-27 | 2023-11-07 | GoTenna, Inc. | Vine™: zero-control routing using data packet inspection for wireless mesh networks |
US11879273B2 (en) | 2016-02-16 | 2024-01-23 | Go Lock Technology, Inc. | Portable lock with integrity sensors |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8572100B2 (en) * | 2004-01-19 | 2013-10-29 | Nigel Hamilton | Method and system for recording search trails across one or more search engines in a communications network |
US9053124B1 (en) | 2014-09-30 | 2015-06-09 | Code 42 Software, Inc. | System for a distributed file system element collection |
US10362113B2 (en) * | 2015-07-02 | 2019-07-23 | Prasenjit Bhadra | Cognitive intelligence platform for distributed M2M/ IoT systems |
US10321313B2 (en) | 2016-09-09 | 2019-06-11 | Dell Products L.P. | Enabling remote access to a service controller having a factory-installed unique default password |
Citations (59)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5432519A (en) | 1993-04-22 | 1995-07-11 | National Space Development Agency Of Japan | Method of performing beam compression process on antenna pattern of radar |
US5581694A (en) | 1994-10-17 | 1996-12-03 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Method of testing and predicting failures of electronic mechanical systems |
US5615367A (en) | 1993-05-25 | 1997-03-25 | Borland International, Inc. | System and methods including automatic linking of tables for improved relational database modeling with interface |
US5697066A (en) | 1996-03-07 | 1997-12-09 | The Trustees Of Columbia University | Media access protocol for packet access within a radio cell |
US6088665A (en) | 1997-11-03 | 2000-07-11 | Fisher Controls International, Inc. | Schematic generator for use in a process control network having distributed control functions |
US6124806A (en) | 1997-09-12 | 2000-09-26 | Williams Wireless, Inc. | Wide area remote telemetry |
US6131119A (en) | 1997-04-01 | 2000-10-10 | Sony Corporation | Automatic configuration system for mapping node addresses within a bus structure to their physical location |
US6208247B1 (en) | 1998-08-18 | 2001-03-27 | Rockwell Science Center, Llc | Wireless integrated sensor network using multiple relayed communications |
US6229486B1 (en) | 1998-09-10 | 2001-05-08 | David James Krile | Subscriber based smart antenna |
US6296205B1 (en) | 1999-03-11 | 2001-10-02 | Aeroastro, Inc. | RF inspection satellite |
US20010027495A1 (en) | 2000-03-29 | 2001-10-04 | Valentino Campagnolo | Multiprocessor control system for cycles, for example for competition bicycles |
US6344797B1 (en) | 1999-07-21 | 2002-02-05 | Diaa M. Hosny | Digital electronic locator |
US20020027504A1 (en) | 1999-03-18 | 2002-03-07 | James Davis | System and method for controlling communication between a host computer and communication devices associated with remote devices in an automated monitoring system |
US20020036595A1 (en) | 2000-09-22 | 2002-03-28 | Tantivy Communications, Inc. | Adaptive antenna for use in wireless communication systems |
US6421354B1 (en) | 1999-08-18 | 2002-07-16 | Phoenix Datacomm, Inc. | System and method for retrieval of data from remote sensors using multiple communication channels |
US20020095501A1 (en) | 2001-01-12 | 2002-07-18 | Chiloyan John H. | Method and system to access software pertinent to an electronic peripheral device based on an address stored in a peripheral device |
US20020095568A1 (en) | 1999-12-20 | 2002-07-18 | Norris Jeffrey S. | Securely and autonomously synchronizing data in a distributed computing environment |
US20020123864A1 (en) | 2001-03-01 | 2002-09-05 | Evren Eryurek | Remote analysis of process control plant data |
US20020161751A1 (en) | 2001-01-17 | 2002-10-31 | Mulgund Sandeep S. | System for and method of relational database modeling of ad hoc distributed sensor networks |
US6504829B1 (en) | 1999-06-28 | 2003-01-07 | Rockwell Collins, Inc. | Method and apparatus for managing communication resources using channelized neighborhoods |
US6505205B1 (en) | 1999-05-29 | 2003-01-07 | Oracle Corporation | Relational database system for storing nodes of a hierarchical index of multi-dimensional data in a first module and metadata regarding the index in a second module |
US20030026268A1 (en) | 2000-11-28 | 2003-02-06 | Siemens Technology-To-Business Center, Llc | Characteristic routing |
US20030033394A1 (en) | 2001-03-21 | 2003-02-13 | Stine John A. | Access and routing protocol for ad hoc network using synchronous collision resolution and node state dissemination |
US20030135495A1 (en) | 2001-06-21 | 2003-07-17 | Isc, Inc. | Database indexing method and apparatus |
US20030151513A1 (en) | 2002-01-10 | 2003-08-14 | Falk Herrmann | Self-organizing hierarchical wireless network for surveillance and control |
US6618745B2 (en) | 1999-09-10 | 2003-09-09 | Fisher Rosemount Systems, Inc. | Linking device in a process control system that allows the formation of a control loop having function blocks in a controller and in field devices |
US20030172221A1 (en) | 2002-03-01 | 2003-09-11 | Mcneil Donald H. | Ultra-modular processor in lattice topology |
US6640145B2 (en) | 1999-02-01 | 2003-10-28 | Steven Hoffberg | Media recording device with packet data interface |
US6640087B2 (en) | 2001-12-12 | 2003-10-28 | Motorola, Inc. | Method and apparatus for increasing service efficacy in an ad-hoc mesh network |
US20030222818A1 (en) | 1998-09-21 | 2003-12-04 | Tantivity Communications, Inc. | Method and apparatus for adapting antenna array using received predetermined signal |
US20030228857A1 (en) | 2002-06-06 | 2003-12-11 | Hitachi, Ltd. | Optimum scan for fixed-wireless smart antennas |
US20040005889A1 (en) | 2002-06-28 | 2004-01-08 | Naoki Nishimura | Wireless communication apparatus and method |
US20040008140A1 (en) | 2002-04-15 | 2004-01-15 | Sengupta Louise C. | Frequency agile, directive beam patch antennas |
US20040010492A1 (en) | 2002-05-28 | 2004-01-15 | Xerox Corporation | Systems and methods for constrained anisotropic diffusion routing within an ad hoc network |
US6697649B1 (en) | 1997-10-01 | 2004-02-24 | At&T Laboratories Cambridge Limited | Peer-to-peer communication in a radio network |
US6704742B1 (en) | 2001-07-03 | 2004-03-09 | Johnson Controls Technology Company | Database management method and apparatus |
US20040090326A1 (en) | 2002-11-12 | 2004-05-13 | Chin Kwan Wu | Wireless sensor apparatus and method |
US20040122849A1 (en) | 2002-12-24 | 2004-06-24 | International Business Machines Corporation | Assignment of documents to a user domain |
US20040137915A1 (en) | 2002-11-27 | 2004-07-15 | Diener Neil R. | Server and multiple sensor system for monitoring activity in a shared radio frequency band |
US6778844B2 (en) | 2001-01-26 | 2004-08-17 | Dell Products L.P. | System for reducing multipath fade of RF signals in a wireless data application |
US6792321B2 (en) | 2000-03-02 | 2004-09-14 | Electro Standards Laboratories | Remote web-based control |
US20040218602A1 (en) | 2003-04-21 | 2004-11-04 | Hrastar Scott E. | Systems and methods for dynamic sensor discovery and selection |
US20040230638A1 (en) | 2003-05-01 | 2004-11-18 | Krishna Balachandran | Adaptive sleeping and awakening protocol for an energy-efficient adhoc network |
US6826162B2 (en) | 2001-09-28 | 2004-11-30 | Hewlett-Packard Development Company, L.P. | Locating and mapping wireless network devices via wireless gateways |
US20040249563A1 (en) | 2001-10-12 | 2004-12-09 | Yoshiyuki Otsuki | Information processor, sensor network system, information processing program, computer-readable storage medium on which information processing program is recorded, and information processing method for sensor network system |
US20050021724A1 (en) | 2003-07-07 | 2005-01-27 | Industrial Technology Research Institute And Hsiang-Tsung Kung | Methods and systems for operating a logical sensor network |
US20050062653A1 (en) | 2002-12-31 | 2005-03-24 | The Regents Of The University Of California | MEMS fabrication on a laminated substrate |
US6888453B2 (en) | 2001-06-22 | 2005-05-03 | Pentagon Technologies Group, Inc. | Environmental monitoring system |
US20050143133A1 (en) | 2003-12-31 | 2005-06-30 | Raj Bridgelall | System and a node used in the system for wireless communication and sensory monitoring |
US20050141706A1 (en) | 2003-12-31 | 2005-06-30 | Regli William C. | System and method for secure ad hoc mobile communications and applications |
US6943747B2 (en) | 2002-09-02 | 2005-09-13 | Samsung Electronics Co., Ltd. | Small and omni-directional biconical antenna for wireless communications |
US6950778B2 (en) | 2001-06-21 | 2005-09-27 | Tri-Tronics Company, Inc. | Programmable photoelectric sensor and a system for adjusting the performance characteristics of the sensor |
US20050275532A1 (en) | 2004-05-28 | 2005-12-15 | International Business Machines Corporation | Wireless sensor network |
US7016812B2 (en) | 2003-07-09 | 2006-03-21 | Hitachi, Ltd. | Apparatus and control method for intelligent sensor device |
US20060136627A1 (en) | 2004-01-09 | 2006-06-22 | American Megatrends, Inc. | Methods, systems, and computer readable media that provide programming for a sensor monitoring system using a softprocessor |
US7103511B2 (en) | 1998-10-14 | 2006-09-05 | Statsignal Ipc, Llc | Wireless communication networks for providing remote monitoring of devices |
US20060212570A1 (en) | 2005-03-16 | 2006-09-21 | Hitachi, Ltd. | Security system |
US20060224434A1 (en) | 2005-03-29 | 2006-10-05 | Zarpac, Inc. | Human data acquisition and analysis for industrial processes |
US7167859B2 (en) | 2000-04-27 | 2007-01-23 | Hyperion Solutions Corporation | Database security |
Family Cites Families (66)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4308911A (en) * | 1979-11-13 | 1982-01-05 | Mandl William J | Residential monitoring and control system |
US4761641A (en) * | 1983-01-21 | 1988-08-02 | Vidcom Rentservice B.V. | Information display system |
US5159631A (en) * | 1990-04-26 | 1992-10-27 | Macrovision Corporation | Audio scrambling system using in-band carrier |
US5321396A (en) * | 1991-02-07 | 1994-06-14 | Xerox Corporation | Indexing of audio/video data |
US5394882A (en) * | 1993-07-21 | 1995-03-07 | Respironics, Inc. | Physiological monitoring system |
GB9315448D0 (en) * | 1993-07-26 | 1993-09-08 | Rank Xerox Ltd | Recording and retrieval of information relevant to the activities of a user |
US5796951A (en) * | 1995-12-22 | 1998-08-18 | Intel Corporation | System for displaying information relating to a computer network including association devices with tasks performable on those devices |
US6094600A (en) * | 1996-02-06 | 2000-07-25 | Fisher-Rosemount Systems, Inc. | System and method for managing a transaction database of records of changes to field device configurations |
US6798341B1 (en) * | 1998-05-18 | 2004-09-28 | Leviton Manufacturing Co., Inc. | Network based multiple sensor and control device with temperature sensing and control |
US6187483B1 (en) * | 1999-05-28 | 2001-02-13 | Advanced Micro Devices, Inc. | Mask quality measurements by fourier space analysis |
US7064671B2 (en) * | 2000-06-23 | 2006-06-20 | Fisher Controls International Llc | Low power regulator system and method |
US6735630B1 (en) * | 1999-10-06 | 2004-05-11 | Sensoria Corporation | Method for collecting data using compact internetworked wireless integrated network sensors (WINS) |
US6954859B1 (en) | 1999-10-08 | 2005-10-11 | Axcess, Inc. | Networked digital security system and methods |
CN1382289A (en) * | 1999-10-28 | 2002-11-27 | 鲍尔斯马特公司 | Time constrained sensor data retrieval system and method |
US6999957B1 (en) * | 2000-01-11 | 2006-02-14 | The Relegence Corporation | System and method for real-time searching |
US6721726B1 (en) | 2000-03-08 | 2004-04-13 | Accenture Llp | Knowledge management tool |
US7034864B2 (en) * | 2000-05-19 | 2006-04-25 | Canon Kabushiki Kaisha | Image display apparatus, image display system, and image display method |
US6700526B2 (en) * | 2000-09-08 | 2004-03-02 | Witten Technologies Inc. | Method and apparatus for identifying buried objects using ground penetrating radar |
US6924727B2 (en) * | 2000-09-27 | 2005-08-02 | Ntt Docomo, Inc. | Method for remote control of home-located electronic devices and a management facility |
US6879984B2 (en) * | 2000-10-05 | 2005-04-12 | Clareos, Inc. | Analytical database system that models data to speed up and simplify data analysis |
US6691070B1 (en) * | 2000-11-03 | 2004-02-10 | Mack Information Systems | System and method for monitoring a controlled environment |
US6708239B1 (en) * | 2000-12-08 | 2004-03-16 | The Boeing Company | Network device interface for digitally interfacing data channels to a controller via a network |
US20020165933A1 (en) * | 2001-04-24 | 2002-11-07 | Yu Philip Shi-Lung | System to acquire location information |
US7203693B2 (en) * | 2001-06-12 | 2007-04-10 | Lucent Technologies Inc. | Instantly indexed databases for multimedia content analysis and retrieval |
US6668194B2 (en) * | 2001-07-16 | 2003-12-23 | Medtronic, Inc. | Method and apparatus for monitoring conduction times in a bi-chamber pacing system |
US7277414B2 (en) | 2001-08-03 | 2007-10-02 | Honeywell International Inc. | Energy aware network management |
WO2003014642A1 (en) * | 2001-08-10 | 2003-02-20 | Daniel Kallestad | Grain aeration system and techniques |
US20030058111A1 (en) | 2001-09-27 | 2003-03-27 | Koninklijke Philips Electronics N.V. | Computer vision based elderly care monitoring system |
US7436887B2 (en) | 2002-02-06 | 2008-10-14 | Playtex Products, Inc. | Method and apparatus for video frame sequence-based object tracking |
US6856247B1 (en) * | 2002-05-10 | 2005-02-15 | A La Cart, Inc. | Food information monitoring system |
US20030236866A1 (en) | 2002-06-24 | 2003-12-25 | Intel Corporation | Self-surveying wireless network |
US8074201B2 (en) | 2002-07-10 | 2011-12-06 | National Instruments Corporation | Deployment and execution of a program on an embedded device |
US7486795B2 (en) * | 2002-09-20 | 2009-02-03 | University Of Maryland | Method and apparatus for key management in distributed sensor networks |
US7079023B2 (en) * | 2002-10-04 | 2006-07-18 | Sap Aktiengesellschaft | Active object identification and data collection |
CN1241401C (en) | 2002-10-08 | 2006-02-08 | 佳能株式会社 | Radio photographic device and its control method |
US7472135B2 (en) | 2002-10-18 | 2008-12-30 | Nokia Corporation | Method and system for recalling details regarding past events |
US20080129495A1 (en) | 2002-10-28 | 2008-06-05 | Hitt Dale K | Wireless sensor system for environmental monitoring and control |
US6870503B2 (en) * | 2002-11-19 | 2005-03-22 | Farrokh Mohamadi | Beam-forming antenna system |
US20040139110A1 (en) | 2002-12-31 | 2004-07-15 | Lamarca Anthony G. | Sensor network control and calibration system |
US20040144849A1 (en) * | 2003-01-28 | 2004-07-29 | Osman Ahmed | Building control system using integrated MEMS devices |
US20040158627A1 (en) * | 2003-02-11 | 2004-08-12 | Thornton Barry W. | Computer condition detection system |
US7146356B2 (en) * | 2003-03-21 | 2006-12-05 | International Business Machines Corporation | Real-time aggregation of unstructured data into structured data for SQL processing by a relational database engine |
US7019637B1 (en) * | 2003-03-28 | 2006-03-28 | Sandia National Laboratories | Systems and methods for detecting and processing |
US20040262410A1 (en) | 2003-04-11 | 2004-12-30 | Hull Gerry G. | Graphical thermostat and sensor |
US7137019B2 (en) * | 2003-04-30 | 2006-11-14 | International Business Machines Corporation | Adaptive throttling system for data processing systems |
US7792273B2 (en) * | 2003-09-15 | 2010-09-07 | Accenture Global Services Gmbh | Remote media call center |
US20050085248A1 (en) * | 2003-10-15 | 2005-04-21 | Ballay Joseph M. | Home system including a portable fob mating with system components |
JP3840223B2 (en) | 2003-11-14 | 2006-11-01 | キヤノン株式会社 | Information collection system |
US7665126B2 (en) * | 2003-12-17 | 2010-02-16 | Microsoft Corporation | Mesh networks with exclusion capability |
CA2569588C (en) * | 2004-02-13 | 2013-06-11 | Trig Medical Ltd. | Performing tasks with sensors |
US7599696B2 (en) * | 2004-06-25 | 2009-10-06 | Searete, Llc | Frequency reuse techniques in mote-appropriate networks |
US8284689B2 (en) * | 2004-03-31 | 2012-10-09 | The Invention Science Fund I, Llc | Frequency reuse techniques in mote-appropriate networks |
US7389295B2 (en) * | 2004-06-25 | 2008-06-17 | Searete Llc | Using federated mote-associated logs |
US20050256667A1 (en) * | 2004-05-12 | 2005-11-17 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Federating mote-associated log data |
US20070214133A1 (en) | 2004-06-23 | 2007-09-13 | Edo Liberty | Methods for filtering data and filling in missing data using nonlinear inference |
US20060018516A1 (en) | 2004-07-22 | 2006-01-26 | Masoud Osama T | Monitoring activity using video information |
US7386352B2 (en) * | 2004-10-06 | 2008-06-10 | Sandia Corporation | Modular sensor network node |
US8731708B2 (en) | 2005-03-10 | 2014-05-20 | Amazon Technologies, Inc. | Method and apparatus for multi-destination item selection using motes |
US7830805B2 (en) | 2005-08-12 | 2010-11-09 | The Invention Science Fund I, Llc | Sensor emulation using mote networks |
US7705743B2 (en) * | 2006-03-01 | 2010-04-27 | L-3 Communications Corporation | Self-assembling wireless network, vehicle communications system, railroad wheel and bearing monitoring system and methods therefor |
JP2007300572A (en) | 2006-05-08 | 2007-11-15 | Hitachi Ltd | Sensor network system, and sensor network position specifying program |
US20080003948A1 (en) * | 2006-06-29 | 2008-01-03 | Patrick Mitran | Calibration systems and techniques for distributed beamforming |
US7589636B2 (en) * | 2006-10-27 | 2009-09-15 | The Boeing Company | Methods and systems for automated safety device inspection using radio frequency identification |
CN101285426B (en) | 2007-04-09 | 2010-10-06 | 山东申普汽车控制技术有限公司 | Method for combined pulse spectrum controlling engine idle speed |
US9848058B2 (en) | 2007-08-31 | 2017-12-19 | Cardiac Pacemakers, Inc. | Medical data transport over wireless life critical network employing dynamic communication link mapping |
US20090195401A1 (en) | 2008-01-31 | 2009-08-06 | Andrew Maroney | Apparatus and method for surveillance system using sensor arrays |
-
2004
- 2004-06-25 US US10/877,109 patent/US7389295B2/en active Active
-
2007
- 2007-12-04 US US11/999,094 patent/US8352420B2/en active Active
Patent Citations (60)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5432519A (en) | 1993-04-22 | 1995-07-11 | National Space Development Agency Of Japan | Method of performing beam compression process on antenna pattern of radar |
US5615367A (en) | 1993-05-25 | 1997-03-25 | Borland International, Inc. | System and methods including automatic linking of tables for improved relational database modeling with interface |
US5581694A (en) | 1994-10-17 | 1996-12-03 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Method of testing and predicting failures of electronic mechanical systems |
US5697066A (en) | 1996-03-07 | 1997-12-09 | The Trustees Of Columbia University | Media access protocol for packet access within a radio cell |
US6131119A (en) | 1997-04-01 | 2000-10-10 | Sony Corporation | Automatic configuration system for mapping node addresses within a bus structure to their physical location |
US6124806A (en) | 1997-09-12 | 2000-09-26 | Williams Wireless, Inc. | Wide area remote telemetry |
US6697649B1 (en) | 1997-10-01 | 2004-02-24 | At&T Laboratories Cambridge Limited | Peer-to-peer communication in a radio network |
US6088665A (en) | 1997-11-03 | 2000-07-11 | Fisher Controls International, Inc. | Schematic generator for use in a process control network having distributed control functions |
US6208247B1 (en) | 1998-08-18 | 2001-03-27 | Rockwell Science Center, Llc | Wireless integrated sensor network using multiple relayed communications |
US6229486B1 (en) | 1998-09-10 | 2001-05-08 | David James Krile | Subscriber based smart antenna |
US20030222818A1 (en) | 1998-09-21 | 2003-12-04 | Tantivity Communications, Inc. | Method and apparatus for adapting antenna array using received predetermined signal |
US7103511B2 (en) | 1998-10-14 | 2006-09-05 | Statsignal Ipc, Llc | Wireless communication networks for providing remote monitoring of devices |
US6640145B2 (en) | 1999-02-01 | 2003-10-28 | Steven Hoffberg | Media recording device with packet data interface |
US6296205B1 (en) | 1999-03-11 | 2001-10-02 | Aeroastro, Inc. | RF inspection satellite |
US20020027504A1 (en) | 1999-03-18 | 2002-03-07 | James Davis | System and method for controlling communication between a host computer and communication devices associated with remote devices in an automated monitoring system |
US6505205B1 (en) | 1999-05-29 | 2003-01-07 | Oracle Corporation | Relational database system for storing nodes of a hierarchical index of multi-dimensional data in a first module and metadata regarding the index in a second module |
US6504829B1 (en) | 1999-06-28 | 2003-01-07 | Rockwell Collins, Inc. | Method and apparatus for managing communication resources using channelized neighborhoods |
US6344797B1 (en) | 1999-07-21 | 2002-02-05 | Diaa M. Hosny | Digital electronic locator |
US6421354B1 (en) | 1999-08-18 | 2002-07-16 | Phoenix Datacomm, Inc. | System and method for retrieval of data from remote sensors using multiple communication channels |
US6618745B2 (en) | 1999-09-10 | 2003-09-09 | Fisher Rosemount Systems, Inc. | Linking device in a process control system that allows the formation of a control loop having function blocks in a controller and in field devices |
US20020095568A1 (en) | 1999-12-20 | 2002-07-18 | Norris Jeffrey S. | Securely and autonomously synchronizing data in a distributed computing environment |
US6792321B2 (en) | 2000-03-02 | 2004-09-14 | Electro Standards Laboratories | Remote web-based control |
US20010027495A1 (en) | 2000-03-29 | 2001-10-04 | Valentino Campagnolo | Multiprocessor control system for cycles, for example for competition bicycles |
US7167859B2 (en) | 2000-04-27 | 2007-01-23 | Hyperion Solutions Corporation | Database security |
US20020036595A1 (en) | 2000-09-22 | 2002-03-28 | Tantivy Communications, Inc. | Adaptive antenna for use in wireless communication systems |
US20030026268A1 (en) | 2000-11-28 | 2003-02-06 | Siemens Technology-To-Business Center, Llc | Characteristic routing |
US7165109B2 (en) | 2001-01-12 | 2007-01-16 | Microsoft Corporation | Method and system to access software pertinent to an electronic peripheral device based on an address stored in a peripheral device |
US20020095501A1 (en) | 2001-01-12 | 2002-07-18 | Chiloyan John H. | Method and system to access software pertinent to an electronic peripheral device based on an address stored in a peripheral device |
US20020161751A1 (en) | 2001-01-17 | 2002-10-31 | Mulgund Sandeep S. | System for and method of relational database modeling of ad hoc distributed sensor networks |
US6778844B2 (en) | 2001-01-26 | 2004-08-17 | Dell Products L.P. | System for reducing multipath fade of RF signals in a wireless data application |
US20020123864A1 (en) | 2001-03-01 | 2002-09-05 | Evren Eryurek | Remote analysis of process control plant data |
US20030033394A1 (en) | 2001-03-21 | 2003-02-13 | Stine John A. | Access and routing protocol for ad hoc network using synchronous collision resolution and node state dissemination |
US6950778B2 (en) | 2001-06-21 | 2005-09-27 | Tri-Tronics Company, Inc. | Programmable photoelectric sensor and a system for adjusting the performance characteristics of the sensor |
US20030135495A1 (en) | 2001-06-21 | 2003-07-17 | Isc, Inc. | Database indexing method and apparatus |
US6888453B2 (en) | 2001-06-22 | 2005-05-03 | Pentagon Technologies Group, Inc. | Environmental monitoring system |
US6704742B1 (en) | 2001-07-03 | 2004-03-09 | Johnson Controls Technology Company | Database management method and apparatus |
US6826162B2 (en) | 2001-09-28 | 2004-11-30 | Hewlett-Packard Development Company, L.P. | Locating and mapping wireless network devices via wireless gateways |
US20040249563A1 (en) | 2001-10-12 | 2004-12-09 | Yoshiyuki Otsuki | Information processor, sensor network system, information processing program, computer-readable storage medium on which information processing program is recorded, and information processing method for sensor network system |
US6640087B2 (en) | 2001-12-12 | 2003-10-28 | Motorola, Inc. | Method and apparatus for increasing service efficacy in an ad-hoc mesh network |
US20030151513A1 (en) | 2002-01-10 | 2003-08-14 | Falk Herrmann | Self-organizing hierarchical wireless network for surveillance and control |
US20030172221A1 (en) | 2002-03-01 | 2003-09-11 | Mcneil Donald H. | Ultra-modular processor in lattice topology |
US20040008140A1 (en) | 2002-04-15 | 2004-01-15 | Sengupta Louise C. | Frequency agile, directive beam patch antennas |
US20040010492A1 (en) | 2002-05-28 | 2004-01-15 | Xerox Corporation | Systems and methods for constrained anisotropic diffusion routing within an ad hoc network |
US20030228857A1 (en) | 2002-06-06 | 2003-12-11 | Hitachi, Ltd. | Optimum scan for fixed-wireless smart antennas |
US20040005889A1 (en) | 2002-06-28 | 2004-01-08 | Naoki Nishimura | Wireless communication apparatus and method |
US6943747B2 (en) | 2002-09-02 | 2005-09-13 | Samsung Electronics Co., Ltd. | Small and omni-directional biconical antenna for wireless communications |
US20040090326A1 (en) | 2002-11-12 | 2004-05-13 | Chin Kwan Wu | Wireless sensor apparatus and method |
US20040137915A1 (en) | 2002-11-27 | 2004-07-15 | Diener Neil R. | Server and multiple sensor system for monitoring activity in a shared radio frequency band |
US20040122849A1 (en) | 2002-12-24 | 2004-06-24 | International Business Machines Corporation | Assignment of documents to a user domain |
US20050062653A1 (en) | 2002-12-31 | 2005-03-24 | The Regents Of The University Of California | MEMS fabrication on a laminated substrate |
US20040218602A1 (en) | 2003-04-21 | 2004-11-04 | Hrastar Scott E. | Systems and methods for dynamic sensor discovery and selection |
US20040230638A1 (en) | 2003-05-01 | 2004-11-18 | Krishna Balachandran | Adaptive sleeping and awakening protocol for an energy-efficient adhoc network |
US20050021724A1 (en) | 2003-07-07 | 2005-01-27 | Industrial Technology Research Institute And Hsiang-Tsung Kung | Methods and systems for operating a logical sensor network |
US7016812B2 (en) | 2003-07-09 | 2006-03-21 | Hitachi, Ltd. | Apparatus and control method for intelligent sensor device |
US20050141706A1 (en) | 2003-12-31 | 2005-06-30 | Regli William C. | System and method for secure ad hoc mobile communications and applications |
US20050143133A1 (en) | 2003-12-31 | 2005-06-30 | Raj Bridgelall | System and a node used in the system for wireless communication and sensory monitoring |
US20060136627A1 (en) | 2004-01-09 | 2006-06-22 | American Megatrends, Inc. | Methods, systems, and computer readable media that provide programming for a sensor monitoring system using a softprocessor |
US20050275532A1 (en) | 2004-05-28 | 2005-12-15 | International Business Machines Corporation | Wireless sensor network |
US20060212570A1 (en) | 2005-03-16 | 2006-09-21 | Hitachi, Ltd. | Security system |
US20060224434A1 (en) | 2005-03-29 | 2006-10-05 | Zarpac, Inc. | Human data acquisition and analysis for industrial processes |
Non-Patent Citations (87)
Title |
---|
"Data Repository", University of California Berkeley, located at http://localization.millennium.berkeley.edu/data<SUB>-</SUB>repository.html, pp. 1 of 1, bearing a date of 2001, printed on Apr. 7, 2004. |
"Localization Distributed Embedded Systems" UCLA Computer Science 213: Localization Systems Powerpoint Presentation, pp. 1-61, bearing a course name of CS 213/Estrin/Winter 2003, bearing a speaker name of: Lewis Girod, bearing a date of Feb. 4, 2003, printed on Mar. 15, 2004. |
"Localization Standards", University of California Berkeley, located at http://localization.millenium.berkeley.edu/localization<SUB>-</SUB>standards.html, pp. 1 of 1, bearing a date of 2001, printed on Apr. 7, 2004. |
"Localization.Millennium.Berkeley.Edu", University of California Berkeley, located at http://localization.millennium.berkley.edu/introduction.html, pp. 1 of 1, bearing a date of 2001, printed on Apr. 7, 2004. |
"The Ad-Hoc Localization System (AHLoS)" Networks and Embedded System Lab, University of California, Los Angeles; located at http://nesl.ee.ucla.edu/projects/ahlos/Default.htm, pp. 1-4, printed on Feb. 23, 2004. |
"Tiny DB A Declarative Database for Sensor Networks" pp. 1-2, located at http://telegraph.cs.berkely.edu/tinydb/ printed on Apr. 9, 2004. |
Andreas Krause et al., "Near-optimal sensor placements: maximizing information while minimizing communication cost", 2006, ACM Pres, NY NY, pp. 2-10. * |
Buonadonna, Phillip; Hill, Jason; Culler, David; "Active Message Communication for Tiny Networked Sensors," pp. 1-11, printed on Mar. 8, 2004. |
Center for the Built Environment, "XYZ On A Chip: Integrated Wireless Sensor Networks for the Control of the Indoor Environment in Buildings" pp. 1-2, located at http://www.cbe.berkeley.edu/research/briefs-wirelessxyz.htm, bearing a date of 2002, printed on Jan. 27, 2004. |
Citris, "Brainy Buildings Conserve Energy" p. 1-3 located at http://www.citris.berkeley.edu/applications/energy/smartbuildings.html, printed on Jan. 27, 2004. |
Citris, "The Real World as One Giant Database" pp. 1-3 located at http://www.citris.berkeley.edu/newsletter/2003<SUB>-</SUB>Newsletters/december<SUB>-</SUB>2003/feature.htm, bearing a date of 2003, printed on Apr. 9, 2004. |
Culler, David E.; Mulder, Hans; "Smart Sensors To Network The World"; Scientific American; printed on Jun. 26, 2007; pp. 1-10; http://www.intel.com/research/exploratory/smartnetworks.htm. |
Culler, David; Estrin, Deborah; Srivastava, Mani; "Overview Of Sensor Networks"; Computer; Aug. 2004; pp. 41-49; vol. 37, No. 8; IEEE Computer Society. |
David Culler et al, "Building Sensor Networks with TinyOS", 2003, http:web.cs.berkeley.edu, pp. 1-41. * |
Fall, Kevin; "A Delay-Tolerant Network Architecture For Challenged Internets"; Intel Research Berkeley; Feb. 26, 2003; pp. 1-14; ACM Press. |
Gay, David; Levis, Phil; Von Behren; Welsh, Matt; Brewer, Eric; and Culler, David, "The nesCLanguage: A Holistic Approach to Network Embedded Systems," pp. 1-11; Intel Research Berkeley, The Intel Corporation, Nov. 2002. |
Gelsinger, Pat; Intel.com, "Expanding Moore's Law with Convergance" pp. 1-4 located at http://www.intel.com/labs/features/em101031.htm, printed on Apr. 9, 2004. |
Govindan, Ramesh; Kohler, Eddie; Estrin, Deborah; Bian, Fang; Chintalapudi, Krishna; Gnawali, Om; Gummadi, Ramakrishna; Rangwala, Sumit, Stathopoulos, Thanos; "Tenet: An Architecture For Tiered Embedded Networks"; pp. 1-8. |
Hill, Jason; Szewczyk, Robert; Woo, Alec; Hollar, Seth; Culler, David; Pister, Kristofer, "System Architecture Directions for Networked Sensors," ASPLOS 2000, Cambridge, Nov. 2000, pp. 1-12. |
INTEL.COM, "Exploratory Research Deep Networking" pp. 1-10 located at http://www.inte.com/research/exploratory/heterogenerous.htm, printed on Mar. 25, 2004. |
INTEL.COM, "New Computing Frontiers-The Wireless Vineyard" pp. 1-4 located at http://www.intel.com/labs/features/rs01031.htm, printed on Apr. 7, 2004. |
ISIS NEST: Institute For Software Integrated Systems; "Applications: Shooter Localizations", pp. 1-5 located at http://www.isis.vanderbilt.edu/projects/nest/applications.html, printed on Apr. 14, 2004. |
ISIS NEST: Institute For Software Integrated Systems; "Documents: NEST Documents", pp. 1-2, located at http://www.isis.vanderbilt.edu/projects.nest/documents.html, printed on Apr. 14, 2004. |
ISIS NEST: Institute For Software Integrated Systems; "Download: NEST Download", pp. 1-2, located at http://www.isis.vanderbilt.edu/projects.nest/download.html, printed on Apr. 14, 2004. |
ISIS NEST: Institute For Software Integrated Systems; "Middleware: Next Middleware Services", pp. 1 of 1, located at http:www.isis.vanderbilt.edu/projects.nest/middleware.html, printed on Apr. 14, 2004. |
ISIS NEST: Institute For Software Integrated Systems; "NEST Home: Network Embedded Systems Technology", pp. 1-2, located at http://www.isis.vanderbilt.edu/projects.nest/index.html, printed on Apr. 14, 2004. |
ISIS NEST: Institute For Software Integrated Systems; "People: The NEST Group", pp. 1 of 1, located at http://www.vanderbilt.edu/projects.nest/people.html, printed on Apr. 14, 2004. |
ISIS NEST: Institute For Software Integrated Systems; "Tools: NEST Tools", pp. 1 of 1, located at http://www.isis.vanderbilt.edu/projects.nest/tools.html, printed on Apr. 14, 2004. |
Jie Lu, et al., User modeling for full-text federated search in peer-to-peer networks, 2006, ACM Press NY NY, pp. 332-339. * |
Johnson, R. Colin, "Companies test prototype wireless-sensor nets" EE Times, pp. 1-3, printable version of article located at http://www.eet.com/article/showArticle.jhtml?articleID=9900910, bearing the date of Jan. 29, 2003, printed on Jan. 27, 2004. |
Kafil M. Razeeb et al, "A hybrid network of autonomous sensor nodes", 2004, ACM Press, NY, NY, pp. 69-70. * |
Kahn, Kevin C.; Culler, David E.; "Ad Hoc Sensor Networks A New Frontier for Computing Applications", Apr. 2002, printed on Apr. 9, 2004, pp. 1-4. |
Kling, Ralph, "Intel(R) Research Mote" pp. 1-13, Powerpoint Presentation, located at http://webs.cs.berkeley.edu/retreat-1-03/slides/imote-nest-q103-03-dist.pdf , Intel Corporation Research, Santa Clara, CA, printed on Apr. 13, 2004. |
Lama Nachman et al, "The Intel Mote platform: a Bluetooth-based sensor network for industrial monitoring", 2005, ACM NY, NY, Article No. 1, pp. 1-6. * |
Levis, Philip, Patel, Neil; "Maté: Building Application-Specific Sensor Network Language Runtimes"; bearing a date of Nov. 11, 2003, printed on Apr. 12, 2004, pp. 1-3. |
Levis, Philip; "Viral Code Propagation in Wireless Sensor Networks," EECS Department, University of California at Berkeley, printed on Mar. 8, 2004, pp. 1-7. |
Levis, Philip; Culler, David; "Maté: A Tiny Virtual Machine for Sensor Networks", pp. 1-11, printed on Apr. 12, 2004. |
Levis, Philip; Madden, Sam; Gay, David; Polastre, Joseph; Szewczyk, Robert; Woo, Alec; Brewer, Eric; Culler, David; "The Emergence of Networking Abstractions and Techniques in TinyOS" pp. 1-14, printed on Apr. 13, 2004. |
Levis, Philip; Patel, Neil; Culler, David; Shenker, Scott; "Trickle: A Self-Regulating Algorithm for Code Propagation and Maitenance in Wireless Sensor Networks", printed on Apr. 13, 2004, pp. 1-14. |
Li, Xin; Kim, Young Jin; Govindan, Ramesh; Hong, Wei; Multi-Dimensional Range Queries in Sensor Networks; ACM; bearing a date of Nov. 7, 2003; pp. 63-75; located at: http://www.cens.ucla.edu/sensys03/proceedings/p63-li.pdf. |
Liscano, Ramiro, "Service Discovery in Sensor Networks, An Overview" Powerpoint Presentation; pp. 1-51; School of Information Technology and Engineering, University of Ottawa, Ottawa, Canada, bearing a date of 2003, printed on Mar. 8, 2004. |
Lu, Jie; Callan, Jamie; "Content-Based Retrieval In Hybrid Peer-To-Peer Networks"; CIKM'03; bearing dates of Nov. 3-8, 2003; ACM. |
Lu, Jie; Callan, Jamie; "Content-Based Retrieval In Hybrid Peer-To-Peer Networks"; Information Retrieval Session 4: General Retrieval Issues; 2003; pp. 199-206; ACM Press. |
Madden et al.; "TAG: a Tiny Aggregation Service for Ad-Hoc Sensor Networks"; bearing a date of 2002; pp. 1-14; ; located at: http://www.cs.berkeley.edu/~franklin/Papers/madden<SUB>-</SUB>tag.pdf. |
Madden, Samuel, "Acquisitional Query Processing in TinyDB" Powerpoint Presentation, pp. 1-51; NEST Winter Retreat 2003, printed on Mar. 8, 2004. |
Madden, Samuel, "Challenges in Sensor Network Query Processing" Powerpoint Presenation at the Jan. 15, 2002 NEST Retreat, printed on Mar. 8, 2004, pp. 1-56. |
Madden, Samuel; Franklin, Michael J.; Hellerstein, Joseph; M., and Hong, Wei, "The Design of an Acquistional Query Processor for Sensor Networks," pp. 1-14, SIGMOD, Jun. 2003. |
Madden, Samuel; Szewczyk, R.; Franklin, Michael; and Culler, David "Supporting Aggregate Queries Over Ad-Hoc Wireless Sensor Networks," pp. 1-10, printed on Mar. 8, 2004. |
Madden, Samuel; Szewczyk, R.; Franklin, Michael; Culler, David "Supporting Aggregate Queries Over Ad-Hoc Wireless Sensor Networks" Powerpoint Presentation, pp. 1-47, 4<SUB>th </SUB>IEEE Workshop on Mobile Computer, dated Jun. 21, 2002. |
Maróti, Miklós; Völgysi, Péter; Simon, Gyula; Karsai, Gábor; Lédeczi, Akos; "Distributed Middleware Services Composition and Synthesis Technology"; pp. 1-8, IEEE, bearing a date of 2002, printed on Apr. 14, 2004. |
Mehdi Sharifzadeh et al., "Supporting spatial aggregation in sensor network databases" 2004, ACM NY, NY, pp. 166-175. * |
Michael Kaminsky et al., "Decentralized User Authentication in a Global File System," Oct. 2003, ACM, NY, NY, vol. 37, Issue 5, pp. 60-73. * |
P.K. Dutta, "System software techniques for low-power operation in wireless sensor networks" 2005, IEEE Computer Society, Washington, DC, pp. 925-93. * |
Patnode, David; Dunne, Joseph; "Senior Design Project"; Wisenet, Spring, bearing a date of 2003; pp. 1-26; located at http://cegt201.bradley.edu/projects/proj2003/wisenet/downloads/Wisenet<SUB>-</SUB>FINAL<SUB>-</SUB>REPORT.pdf. |
Patnode, David; Dunne, Joseph; "TinyOS Based Wireless Network of Sensors"; IEEE; bearing a date of Nov. 6, 2003; pp. 1-6. |
PCT International Search Report; International App No. PCT US05/10053; Aug. 10, 2007. |
PCT International Search Report; International App No. PCT/US05/09640; Jul. 9, 2007. |
PCT International Search Report; International App. No. PCT/US 05/09641; 5 pages; Sep. 13, 2007. |
PCT International Search Report; International App. No. PCT/US 05/09703; pp. 1-4; Sep. 28, 2007. |
PCT International Search Report; International App. No. PCT/US 05/10059; pp. 1-5; Oct. 26, 2007. |
PCT International Search Report; International App. No. PCT/US 05/10249; pp. 1-4; Oct. 24, 2007. |
PCT International Search Report; International App. No. PCT/US 05/10250; pp. 1-5; Oct. 18, 2007. |
PCT International Search Report; International App. No. PCT/US 05/10251; pp. 1-5; Oct. 25, 2007. |
PCT International Search Report; International App. No. PCT/US 05/10253; pp. 1-4; Oct. 23, 2007. |
PCT International Search Report; International App. No. PCT/US 05/10254; pp. 1-5; Oct. 17, 2007. |
PCT International Search Report; International App. No. PCT/US 05/10842; pp. 1-3; Nov. 7, 2007. |
PCT International Search Report; International App. No. PCT/US 05/11207; pp. 1-4; Nov. 13, 2007. |
PCT International Search Report; International App. No. PCT/US05/09479; Jul. 17, 2007. |
PCT International Search Report; International App. No. PCT/US05/10843; Mar. 29, 2005. |
PCT International Search Report; International App. No. PCT/US05/11202; Sep. 27, 2006. |
PCT International Search Report; International App. No. PCTUS05/10054; Dec. 1, 2006. |
PCT International Search Report; International App. No.: PCT/US05/11203; Feb. 9, 2007. |
Pescovitz, David, "Robugs: Smart Dust Has Legs" pp. 1-2, located at http://www.coe.berkeley.edu/labnotes/0903/pister<SUB>-</SUB>print.html, bearing a date of Sep. 2003, printed on Apr. 9, 2004. |
Raghunathan, Vijay; Schurgers, Curt; Park, Sung; Srivastava, Mani B.; "Energy Aware Wireless Sensor Networks" pp. 1-17; Department of Electrical Engineering, University of California, Los Angeles; printed on Mar. 15, 2004. |
Robert Adler et al. , "Intel mole 2: an advanced platform for demanding sensor network applications", 2005, ACM Press, NY, NY, pp. 298-298. * |
Ryer, Alex; Light Measurement Handbook, http://www.intl-light.com/handbook; pp. 1-64, copyright 1997, printed on Mar. 8, 2004. |
Savvides, Andreas; "Hardware", pp. 1-3, located at http://nesl.ee.ucle.edu/projects/ahlos/hardware.htm, Networks and Embedded Systems Lab, University of California, Los Angeles; bearing a date of Jan. 8, 2003, printed on Feb. 23, 2004. |
Savvides, Andreas; "Localization Forum", pp. 1 of 1, located at http://nesl.ee.ucla.edu/projects/ahlos/localization<SUB>-</SUB>forum.htm, Networks and Embedded Systems Lab, University of California, Los Angeles; bearing a date of Dec. 24, 2003, printed on Feb. 23, 2004. |
SEARCHMOBILECOMPUTING.COM, "Ad-Hoc Network" pp. 1-3 located at http://searchmobilecomputing.techtarget.com/sDefinition/0,,sid40<SUB>-</SUB>gci213462,00.html, bearing a date of Apr. 11, 2003, printed on Mar. 8, 2004. |
Searchnetworking.com Definitions, "Jini" pp. 1-3 located at http://searchnetworking.techtarget.com/sDefinition/0,,sid7<SUB>-</SUB>gci212422,00.html, bearing a date of Apr. 10, 2003, printed on Mar. 8, 2004. |
Spyropoulos, Akis; Raghavendra, C.S., "Energy Efficient Communications in Ad Hoc Networks Using Directional Antennas," Dept. of Electrical Engineering-Systems, University of Southern California, bearing a date of 2002, printed on Feb. 23, 2004, pp. 1-9. |
Strathopoulos, Thanos; Girod, Lewis; Heidemann, John; Estrin, Deborah; "More Herding For Tiered Wireless Sensor Networks"; Center For Embedded Networked Sensing; pp. 1-14; UCLA, Department Of Computer Science / USC, Information Sciences Institute. |
Tiny Sec: Link Layer Security for Tiny Devices, Calamari: A localization system for sensor networks: pp. 1-6, located at http://www.cs.berkeley.edu/~kamin/calamari/ printed on Apr. 12, 2004. |
Viswanath, Kumar, "Adaptive, Integrated Multicast Routing for Group Communications in Ad-Hoc Networks" Powerpoint Presentation, pp. 1-12; Computer Engineering Department, University of California, Santa Cruz, printed on Mar. 8, 2004. |
Woo, Alec; Culler, David E.; "A Transmission Control Scheme for Media Access in Sensor Networks"; bearing a date of Jul. 2001; pp. 1-15; located at: http://www.cs.berkeley.edu/~awoo/awoo<SUB>-</SUB>mobicom.pdf. |
Woo, Alec; Tong, Terence; and Culler, David, "Taming the Underlying Challenges of Reliable Multihop Routing in Sensor Networks," pp. 1-14, SenSys '03, Nov. 5-7, 2003, Los Angeles, California, USA. |
Zhao, Feng; Guibas, Leonidas J.; Wireless Sensor Networks: An Information Processing Approach. San Francisco: Morgan Kaufmann Publishers-Elsevier Inc., bearing a copyright date of 2004. |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090216713A1 (en) * | 2004-06-25 | 2009-08-27 | Jung Edward K Y | Using federated mote-associated logs |
US8352420B2 (en) * | 2004-06-25 | 2013-01-08 | The Invention Science Fund I, Llc | Using federated mote-associated logs |
US8085792B1 (en) | 2007-06-29 | 2011-12-27 | Google Inc. | Traffic-oblivious load balancing protocol for sensor networks |
US8392401B1 (en) * | 2007-06-29 | 2013-03-05 | Google Inc. | Query partitioning to decompose hotspots in sensor networks |
US8625575B1 (en) | 2007-06-29 | 2014-01-07 | Google Inc. | Traffic-oblivious load balancing protocol for sensor networks |
US10015720B2 (en) | 2014-03-14 | 2018-07-03 | GoTenna, Inc. | System and method for digital communication between computing devices |
US9756549B2 (en) | 2014-03-14 | 2017-09-05 | goTenna Inc. | System and method for digital communication between computing devices |
US10602424B2 (en) | 2014-03-14 | 2020-03-24 | goTenna Inc. | System and method for digital communication between computing devices |
US11879273B2 (en) | 2016-02-16 | 2024-01-23 | Go Lock Technology, Inc. | Portable lock with integrity sensors |
US10416661B2 (en) | 2017-11-30 | 2019-09-17 | Abb Schweiz Ag | Apparatuses, systems and methods of secure cloud-based monitoring of industrial plants |
US10944669B1 (en) | 2018-02-09 | 2021-03-09 | GoTenna, Inc. | System and method for efficient network-wide broadcast in a multi-hop wireless network using packet echos |
US11750505B1 (en) | 2018-02-09 | 2023-09-05 | goTenna Inc. | System and method for efficient network-wide broadcast in a multi-hop wireless network using packet echos |
US11811642B2 (en) | 2018-07-27 | 2023-11-07 | GoTenna, Inc. | Vine™: zero-control routing using data packet inspection for wireless mesh networks |
US11082344B2 (en) | 2019-03-08 | 2021-08-03 | GoTenna, Inc. | Method for utilization-based traffic throttling in a wireless mesh network |
US11558299B2 (en) | 2019-03-08 | 2023-01-17 | GoTenna, Inc. | Method for utilization-based traffic throttling in a wireless mesh network |
Also Published As
Publication number | Publication date |
---|---|
US20090216713A1 (en) | 2009-08-27 |
US8352420B2 (en) | 2013-01-08 |
US20050289122A1 (en) | 2005-12-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8352420B2 (en) | Using federated mote-associated logs | |
US11356346B2 (en) | Mote-associated log creation | |
US20190364400A1 (en) | Using mote-associated indexes | |
US7599696B2 (en) | Frequency reuse techniques in mote-appropriate networks | |
US8284689B2 (en) | Frequency reuse techniques in mote-appropriate networks | |
US20060064402A1 (en) | Using federated mote-associated indexes | |
US8346846B2 (en) | Transmission of aggregated mote-associated log data | |
US20060062252A1 (en) | Mote appropriate network power reduction techniques | |
US20060004888A1 (en) | Using mote-associated logs | |
US8335814B2 (en) | Transmission of aggregated mote-associated index data | |
WO2005099038A2 (en) | Using mote-associated logs | |
US11246017B2 (en) | Mote networks using directional antenna techniques | |
WO2005099037A2 (en) | Frequency reuse techniques in mote-appropriate networks | |
US11106749B2 (en) | Federating mote-associated index data | |
WO2005099144A2 (en) | Mote appropriate network power reduction techniques | |
US20050256667A1 (en) | Federating mote-associated log data | |
US20050265388A1 (en) | Aggregating mote-associated log data | |
US20050255841A1 (en) | Transmission of mote-associated log data | |
US20060079285A1 (en) | Transmission of mote-associated index data | |
WO2005099034A2 (en) | Transmission of aggregated mote-associated log data |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SEARETE LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JUNG, EDWARD K. Y.;TEGREENE, CLARENCE T.;REEL/FRAME:015553/0332;SIGNING DATES FROM 20040629 TO 20040701 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: INVENTION SCIENCE FUND I, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SEARETE LLC;REEL/FRAME:023484/0625 Effective date: 20091106 |
|
AS | Assignment |
Owner name: INVENTION SCIENCE FUND I, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SEARETE LLC;REEL/FRAME:023487/0793 Effective date: 20091106 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: FORTRESS CREDIT CO LLC, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:TRIPLAY, INC.;REEL/FRAME:035120/0862 Effective date: 20150302 |
|
AS | Assignment |
Owner name: TRIPLAY, INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:INVENTION SCIENCE FUND I, LLC;SEARETE LLC;REEL/FRAME:035643/0702 Effective date: 20150224 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: TRIPLAY, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:FORTRESS CREDIT CO LLC;REEL/FRAME:052156/0955 Effective date: 20200311 |
|
FEPP | Fee payment procedure |
Free format text: 11.5 YR SURCHARGE- LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1556); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |
|
AS | Assignment |
Owner name: JTT INVESTMENT PARTNERS, LLC, GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TRIPLAY, INC.;REEL/FRAME:053411/0805 Effective date: 20200302 |
|
AS | Assignment |
Owner name: ALARM.COM INCORPORATED, VIRGINIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JTT INVESTMENT PARTNERS, LLC;REEL/FRAME:062279/0900 Effective date: 20221230 |