Impinj, Inc.

Microsoft Technology Licensing, LLC

Motorola Solutions, Inc.

Balaji Shyamkumar

Scott A Cooper

Kurt Eugene Sundstrom

Sandesh Doddameti

Jayasuryan Iyer

Christopher J Diorio

Fabrice Canel

Dean M Wierman

Curtis Porter

Charles (Xi) Zhang

Robert E Bonham

Puneet Sahni

Harsh Verma

Charles Zhang

A device, system and process for controlling document access using hierarchical paths is provided. A query, received from a requesting device, comprises: a search string for searching a document database; and an identifier associated with a user. A security permissions database is accessed using the identifier to receive permissible hierarchical document access paths indicating document access permissions associated with the identifier. A modified query includes the permissible hierarchical document access paths. The modified query used to access an index of the document database, the index comprising: a searchable content portion, and corresponding hierarchical document access paths, of a document. Document identifiers are received that identify only the documents having: respective searchable content portions that include the search string of the modified query; and at least one respective corresponding hierarchical document access path encompassed by the permissible hierarchical document access paths. The document identifiers are provided to the requesting device.

Device, system and method for controlling document access using hierarchical paths

An RFID-based item tracking system may use statistical methods to determine whether a tag or tagged item that does not respond when inventoried is present in a particular zone or reader antenna field-of-view. In one embodiment, the item tracking system may determine an observability of an item based on one or more initial trials. Upon not detecting the item in one or more subsequent trials, the item tracking system may estimate whether the item is still present based on the observability.

RFID-based item presence detection

A politeness manager estimates traffic to the sites based on historical log data generated and sent by plug-ins or toolbars on client web browsers. The historical log data details dates and times the web browsers visit different web sites that is used to understand what timeframes specific web sites are busy and what timeframes the web sites are not busy. Crawl rates for different timeframes for a web site are determined based on the historical log data, and web crawlers are scheduled to crawl the web site according to the crawl rates to minimize the chances that web crawler requests are responsible for the site crashing.

Optimizing web crawling with user history

Search engines may utilize web crawlers to discover desirable content that may be provided to users as search results. Unfortunately, document providers, such as websites, may return junk web pages and/or maintenance web pages as document results, which may be undesirable for a search engine to provide as search results. Accordingly, document providers may be grouped into provider clusters. Profiles may be assigned to provider clusters, where a profile may comprise parameters representing 'expected' parameters historically returned from normal document fetch operations to document providers within the provider cluster. Parameters of a profile for a provider cluster comprising a document provider may be compared with current document fetch parameters of a current document fetch operation. If the parameters of the profile and the current document fetch parameters do not match, then an alert may be generated.

Discrepancy detection for web crawling

Growing community of inventors

Sammamish, WA, United States of America

Balaji Shyamkumar