The present disclosure relates to systems and techniques for data integration, analysis, and visualization. More specifically, the present disclosure relates to dynamic linked panels associated with queries performed on data sources and visualization of results of the queries.
Organizations and/or companies are producing increasingly large amounts of data. Such data may be queried and presented in a user interface.
The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be discussed briefly.
In one embodiment, a computer system configured to display data from one or more data sources comprises: one or more hardware computer processors configured to execute code in order to cause the system to: generate a user interface configured to display a plurality of panels including a first panel and a second panel, each of the plurality of panels having respective display settings and queries including code for querying one more data sources; execute a first query associated with the first panel; display the first panel in the user interface based on first display settings of the first panel, the first panel displaying at least a portion of the result of the first query, the result of the first query being associated with a variable; execute a second query associated with the second panel, wherein the second query refers to the variable associated with the first query of the first panel; display the second panel in the user interface based on second display settings of the second panel, the second panel displaying at least a portion of the result of the second query; and in response to user input changing the displayed result in the first panel: re-execute the second query associated with the second panel; and update the display of the second panel in the user interface based on results of the re-executed second query of the second panel.
According to certain aspects, the code can be further configured to: receive a third query from the first panel for writing data to the one or more data sources; process one or more parameters in the third query by invoking a function; and perform the third query with the processed one or more parameters to write data to the one or more data sources. The processing of the one or more parameters in the third query may be performed at least in part by: replacing the one or more parameters with respective placeholders; and storing respective values corresponding to the one or more parameters in an array. The processing of the one or more parameters in the third query may be performed at least in part by changing respective values corresponding to the one or more parameters to string format. Each of the plurality of panels can be referenced as a template that is rendered by a template engine, and the function can be registered with the template engine. The code may be further configured to: prior to running the query of the first panel, invoke one or more functions to determine whether a table, a row, or a column referenced in the query exists in the one or more data sources.
In another embodiment, a method of displaying data from one or more data sources comprises: using one or more hardware computer processors: generating a user interface configured to display a plurality of panels including a first panel and a second panel, each of the plurality of panels having respective display settings and queries including code for querying one more data sources; executing a first query associated with the first panel; displaying the first panel in the user interface based on first display settings of the first panel, the first panel displaying at least a portion of the result of the first query, the result of the first query being associated with a variable; executing a second query associated with the second panel, wherein the second query refers to the variable associated with the first query of the first panel; displaying the second panel in the user interface based on second display settings of the second panel, the second panel displaying at least a portion of the result of the second query; and in response to user input changing the displayed result in the first panel: re-executing the second query associated with the second panel; and updating the display of the second panel in the user interface based on results of the re-executed second query of the second panel.
According to certain aspects, the method may further comprise: receiving a third query from the first panel for writing data to the one or more data sources; processing one or more parameters in the third query by invoking a function; and performing the third query with the processed one or more parameters to write data to the one or more data sources. Said processing the one or more parameters in the third query can comprise: replacing the one or more parameters with respective placeholders; and storing respective values corresponding to the one or more parameters in an array. Said processing the one or more parameters in the third query can comprise changing respective values corresponding to the one or more parameters to string format. Each of the plurality of panels may be referenced as a template that is rendered by a template engine, and the function may be registered with the template engine. The method may further comprise: prior to running the query of the first panel, invoking one or more functions to determine whether a table, a row, or a column referenced in the query exists in the one or more data sources.
In some embodiments, a non-transitory compute readable medium comprises instructions for displaying data from one or more data sources that cause a computer processor to: generate a user interface configured to display a plurality of panels including a first panel and a second panel, each of the plurality of panels having respective display settings and queries including code for querying one more data sources; execute a first query associated with the first panel; display the first panel in the user interface based on first display settings of the first panel, the first panel displaying at least a portion of the result of the first query, the result of the first query being associated with a variable; execute a second query associated with the second panel, wherein the second query refers to the variable associated with the first query of the first panel; display the second panel in the user interface based on second display settings of the second panel, the second panel displaying at least a portion of the result of the second query; and in response to user input changing the displayed result in the first panel: re-execute the second query associated with the second panel; and update the display of the second panel in the user interface based on results of the re-executed second query of the second panel.
According to certain aspects, the instructions can be further configured to cause the computer processor to: receive a third query from the first panel for writing data to the one or more data sources; process one or more parameters in the third query by invoking a function; and perform the third query with the processed one or more parameters to write data to the one or more data sources. The processing of the one or more parameters in the third query may be performed at least in part by: replacing the one or more parameters with respective placeholders; and storing respective values corresponding to the one or more parameters in an array. The processing of the one or more parameters in the third query may be performed at least in part by changing respective values corresponding to the one or more parameters to string format. Each of the plurality of panels can be referenced as a template that is rendered by a template engine, and the function can be registered with the template engine. The instructions may be further configured to cause the computer processor to: prior to running the query of the first panel, invoke one or more functions to determine whether a table, a row, or a column referenced in the query exists in the one or more data sources.
Disclosed herein are various systems and methods for providing a plurality of dynamic panels in a user interface (UI). The dynamic panels (or “panels”) can display different pieces of data from one or more data sources. For example, a query can be run on one or more data sources, and different parts of the result from the query can be output using different dynamic panels. For instance, each dynamic panel can be associated with a variable to output. Different types of dynamic panels can be provided, such as charts (e.g., line chart, bar chart, etc.), controls (e.g., dropdown, multiselect box, search box, etc.), maps, tables, text boxes, etc. The panels can be data source agnostic. For example, the panels can be associated with data from different types of data sources, such as relational databases (e.g., SQL Server), Elasticsearch, etc. In some embodiments, individual panels may each be referred to as “widgets.” In some embodiments, the user interface including multiple panels may be referred to as a “dashboard.”
A dynamic panel can be linked to one or more other dynamic panels. As mentioned above, the output of a panel can be used in another panel. When the data of a panel depends or relies on the data of another panel, if the data in the source panel changes, the data in the panel that relies on the source panel may also change or be refreshed. For example, in
The query and the settings relating to the display of particular panels can be managed separately. For example, a user interface can provide a section for entering the query and another section for entering display related settings. Separate management of the query and the display settings can allow the panels to be easily updated within the user interface and allow reuse of queries. The page that contains the panels may be referred to as a “document.”
In this manner, multiple panels can be used to display different aspects of the result from a query. One query can be run to obtain the needed information, and the result can be parsed and displayed using multiple panels. Display of information can be simplified by using multiple panels. Also, the query can be reused across panels since each panel can extract a portion of the result to display. In certain embodiments, each panel may have its own query and display the result of the query. The panels can also be linked together so that the data from one panel can be used to display the data in another panel.
Exemplary User Interface of Dashboard Creation System
Using the main page 210, the user can create, edit, delete, and manage one or more panels. In one embodiment, the main page 210 includes a top section 211 that displays the name of the document selected, if any; links to the query page 220 (
Moving to
In some embodiments, the user interface 200, including the various pages illustrated in
In one embodiment, the user interface 200 can have two viewing modes: a WYSIWYG (What You See Is What You Get) editor mode and a corresponding read-only consumer mode. In editor mode, built-in panels like bar charts, scatter plots, time series plots, tables, dropdown menus, text boxes, etc. can be added and arranged on the canvas or page. The user can author and edit data queries via a rich editor UI, which can support quickly previewing results for quick debugging. Queries may natively support templating (e.g., via Handlebars) to link to panels, URL parameters, or data from other queries. Panels can also be templatized to link to data from the queries and coordinate with other panels. Additionally, the editor can customize styling for a particular page or document, or deployment. The read-only consumer mode may allow finished web pages to be shared to a set of users that can interact with a page but not edit its layout or setup.
Querying and Displaying Data in Data Sources Using Dynamic Panels
At data flow action 1, the user creates a panel. As explained above, a panel can have a query associated with it and display settings associated with it.
At data flow action 2, the user defines a query associated with the panel. As mentioned above, the panels can be data source agnostic and can be associated with data from different types of data sources, such as relational databases SQL, Elasticsearch, etc. The system 300 can connect to and query data from any data source that supports a text-based query language. The system 300 can support different types of query languages and/or tools, depending on the embodiment. In certain embodiments, Handlebars can be used for the queries. In some embodiments, JSON (JavaScript Object Notation) can be used for the queries. In other embodiments, the system 300 can include one adapter for SQL databases and another adapter for REST backends (e.g., Elasticsearch), which may be provided as default adapters. The system 300 can additionally allow the user to transform and selectively extract data out of query results. For example, the user can extract data from JSON query responses using JSONPath.
At data flow action 3, the user defines display settings associated with the panel. The user can define the display settings in the document CSS for the panel. The user can create additional panels and define the query and display settings for each panel. One or more panels may be added to a container. A container may function as a holder for panels. A container can act as a collection of panels that move as a unit. The user can define the layout of the panels within the container, and also define behavior for the container, which can apply to all the panels in the container as a group. The user may add tabs for a container. For example, a container may include multiple tabs, and the user can switch between tabs to view different content. Each tab can act as a separate content space and hold different panels.
At data flow action 4, the system 300 generates the user interface page for the document that contains the panel. When the system 300 receives a request from the user system 320 for a particular document, the system 300 can obtain the requested document, for example, from the template storage 350 and run the query associated with the panels in the documents. The template engine 350 may combine the document, the panels, and the query results in order to generate finished user interface pages. As explained above, one query can be used to obtain data, and different parts of the query can be associated with different panels. For instance, a query q returns columns c1, c2, c3, and c4, and the system 300 creates a text panel whose text is {{q.c1}}, a dropdown panel whose values is {{q.c2}}, and a chart panel whose x values and y values are {{q.c3}} and {{q.c4}}, respectively. Or each panel may have a query associated with it and the result of the query can be associated with the particular panel. The finished user interface pages can be then sent to the user system 320 to be displayed in a user interface.
At data flow action 5, the user system 320 receives user input/selection in the user interface. The user may change the displayed result in the user interface of the user system 320. For example, the user may select a particular value in a dropdown control. Or the user may select a particular panel or an item within a panel. The user input or selection is sent to the system 300.
At data flow action 6, the system 300 updates the display of the panel. For instance, the query may be rerun or the query result may be filtered based on the selected value in a dropdown control. Or actions may be associated with a panel or an item within a panel, and such actions may be performed. For example, selection of a panel or an item within a panel can display options or attributes related to the panel or the item. In one example, the selection of a table row in one panel is linked to another panel that contains more detailed information about the selected row. A table shows a list of games as in
The system 300 can be highly extensible, and panels can be easily created, edited, and/or removed. In one embodiment, a new panel can be added by creating a web module (e.g., an AngularJS module). A simple web module may be easily created by a suitable module generator (e.g., via Yeoman generator). Similarly, data adapters for new types of data sources can be easily added (e.g., via a java jar).
Linking of Dynamic Panels
The query may refer to panels, variables of panels, and/or global variables as templates, and a template system or language can process the queries and replace any templates with corresponding values. For example, a template can be indicated by double curly brackets “{{” and “}}” in a template system or language, such as Handlebars and Mustache. In the example above, p1.selectedValue and p2.selectedValue may be enclosed in double curly brackets to indicate that they are templates. Therefore, the query for the example above can be written as: SELECT column FROM table WHERE team={{p1.selectedValue}} AND season={{p2.selectedValue}}. The template engine 350 can process and replace the templates with their corresponding values at the time of generating the finished user interface pages. In certain embodiments, the system 300 builds a graph of all the references from the templates and associates the references such that if any of the references change, the corresponding templates are regenerated or refreshed. Templates may also refer to objects other than panels, depending on the embodiment. Using double curly brackets to indicate templates is described above as an example, and any other syntax elements can be used to indicate templates.
In some embodiments, the user can define variables associated with the panels that can be referenced in a query. For example, the user can define variable A for panel 310 and variable B for panel 320, and the query for panel 330 can reference variable A and variable B in the query. For example, variable A and variable B can be associated with the selected value of panel 310 and panel 320, respectively. As explained above, in some embodiments, panels can have global variables associated with them.
Writing to Data Sources Using Dynamic Panels
In some cases, it may be useful to allow users to write to or update the data sources through the panels. For example, the user may want to change the data in a panel and reflect the changes to the data source. The user could also save some selected rows from a table in one document for later use in other documents, or save notes from different users to a table for later reference. In certain cases, the user may also want to rename a portfolio in a database.
The system 400 can allow the users to update the data sources 410 through queries. For example, SQL queries or JSON queries can be used. SQL queries and JSON queries can refer to the panels as templates, and a template system or language like Handlebars or Mustache can process the queries and replace any templates with corresponding values. However, in certain cases, directly replacing the templates with the corresponding values can lead to unintended consequences. For instance, the user may specify an always true condition as the value to be replaced with a template in the WHERE clause of a SQL query, which can result in changing all data. In one example, the user creates a query as follows: UPDATE table SET text=“newText” WHERE id={{p1.text}}. If the value of p1.text is “1=1,” replacing the template {{p1.text}} with “1=1 would update every row in the table. Accordingly, the system 400 make the queries secure by using a custom function as explained below.
At data flow action 1, the system 400 creates a custom function to verify parameters in a query. For example, an administrator of the system 400 can create the custom function.
In some embodiments, the system 400 uses SQL queries and processes the SQL queries using Handlebars. The custom function can be a Handlebars helper. For example, the custom function can be named “param” and registered with Handlebars. Handlebars can invoke the custom function when processing the SQL queries. The user can use the custom function when using templates in SQL queries.
In one embodiment, the custom function prevents use of text values in templates and only allows parameter values in templates. For example, a variable of a panel used in a template should be a parameter value. Supposing that the variable of the panel referred to in a template is p1.property, the custom function checks whether p1.property is an array. If p1.property is not an array, the custom function replaces “{{param p1.property}}” with a “?” and saves the value of p1.property for reference, for example, in a reference array. If p1.property is an array with a length of n, the custom function replaces “{{param p1.property}}” with a string containing n question marks separated by commas and saves the value of each of element in the array for reference, for example, in a reference array. In this way, the custom function can help create parameterized queries, which contain placeholders such as “?” that can be inserted in query parameters. The SQL engine would escape and not evaluate these parameters, and therefore, parameterized queries can prevent SQL injection. For instance, the expression “1=1” would be escaped and would not be evaluated as a boolean expression; rather it is evaluated as a string.
For example, if p1.property is equal to 1, the custom function processes the SQL query UPDATE table SET text=“newText” WHERE id={{param p1.property}} to UPDATE table SET text=“newText” WHERE id=?, and stores 1 in the reference array. In another example, if p1.property is equal to an array [1, 2], the custom function processes the SQL query UPDATE table SET text=“newText” WHERE id={{param p1.property}} to UPDATE table SET text=“newText” WHERE id=(?, ?), and stores 1 and 2 in the reference array. The processed query and parameters can be prepared as a JDBC statement and run against one or more data sources 410. Types of parameters can be preserved (e.g., whether the parameter is a number or a string) by using additional Handlebars helpers.
In other embodiments, the system 400 uses JSON queries and processes the JSON queries using Handlebars and/or Mustache. A JSON query can include three parts: path, method, and body. The path and the body can use templates; since the method generally has a few options, templates may not be used with the method. In order to have different rules for the use of templates, the path, method, and body can be separated into different components of the query. For example, the path and method can be considered as metadata, and the body can be considered as the template.
The custom function can be used on the body of a JSON query. The custom function can be a Handlebars helper. For example, the custom function can be named “{{esc}}” and registered with Handlebars. Handlebars can invoke the custom function when processing JSON queries. The user can use the custom function when using templates in JSON queries. The custom function may verify that all values for templates are valid JSON values (e.g., string, number, object, array, boolean, null, etc.). The custom function can convert the value of templates to string format (e.g., using JSON stringify function). For example, {value: {{esc ptvalue}}} where p1.value is “a” (chars [a]) is evaluated to be {value: “a”}.
The system 400 can also create an additional custom function for string interpolation or for cases where the user wants to use another Handlebars helper (e.g., the join helper). The additional custom function can be a block helper; for example, it can be referred to as {{#esc}}{{/esc}} block helper. In one embodiment, the block helper can evaluate the templates within the block helper, take the result as one string, and convert the one string to string format. In other embodiments, Handlebars evaluates what is inside the block helper, and the helpers within the block helper can convert the result to string format. In certain embodiments, the block helper or helpers convert the result to string format (e.g., by calling JSON stringify function) for security. In one embodiment, JSON stringify function can be called on block helpers for security. Various embodiments described in this disclosure may be implemented separately or in combination as appropriate.
The system 400 may also define rules and features to be implemented in association with the custom function(s). In one example, for the path, the system 400 can require that values for templates are uniform resource identifier (URI) unreserved characters and are not periods. This can prevent the template value from going outside of the intended space in the path (e.g., intended directory). In some embodiments, the system 400 may not allow quotes around templates to avoid a string object from being closed accidentally. The system 400 may also require that all other non-block helpers are nested inside the {{esc}} helper or used inside the {{#esc}}{{/esc}} block helper.
At data flow action 2, the user writes a query in a panel using the custom function in order to write data to a data source 410. The system 400 can require users to use the custom functions when writing queries to write to a data source 410. For instance, the system 400 can return errors for queries that do not use the custom functions or do not use the custom functions properly.
At data flow action 3, the user runs the query. The user can associate the query with a query button panel. The user may run the query by clicking on the query button. The user system 420 can send the user query to the system 400.
At data flow action 4, the system 400 invokes the custom function to verify and process the parameters in the query. Upon receiving the user query from the user system 420, the system 400 can invoke the custom function on the query and format the query appropriately. If the processed query does not conform to the rules associated with the custom function, the system 400 can return an error.
At data flow action 5, the system 400 runs the query with the processed parameters to write to the data source 410. If the processed query is properly written and/or conforms to the rules associated with the custom function, the system 400 runs the query against the data source 410.
In certain embodiments, the system 400 also implements custom functions to verify parameters of queries for reading data. For example, the system 400 can create custom functions (e.g., Handlebars helpers) for verifying table names, column names, alias table names, alias column names, etc. In one embodiment, the system 400 creates Handlebars helpers “table,” “column,” and “alias” to make sure the table, column, or alias actually exists in the data sources 410. The system 400 can verify a table name or column name by checking that the table name or column name is within the schema of the database. The user can register the alias table name or column name, and the system 400 may verify an alias name by checking that it is registered.
At block 501, the system 300 generates a user interface configured to display a plurality of panels, each panel associated with display settings and a query. At block 502, the system 300 performs the query associated with a first panel. The first panel can be panel 310 in
At block 503, the system 300 displays the first panel in the user interface based on the display settings of the first panel. The query of panel 310 can be run to obtain the list of teams to display in panel 310. The list of teams can be displayed according the document CSS of panel 310. One team from the list of teams may be displayed in panel 310 as the default value. For example, panel 310 shows the first team in the list.
Similarly, the system 300 can perform the query associated with panel 320 and display panel 320 in the user interface based on the display settings of panel 320. One season from the list of seasons may be displayed in panel 320 as the default value. For example, panel 320 shows the most current season in the list.
At block 504, the system 300 performs the query associated with a second panel. The second panel can be panel 330 in
At block 505, the system 300 displays the second panel in the user interface based on the display settings of the second panel. The query of panel 330 can be run to obtain the list of games to display in panel 330. As explained above, the query of panel 330 obtains the list of games to display for the team selected in panel 310 and the season selected in panel 320. The list of games can be displayed according the document CSS of panel 330.
At block 506, the system 300 receives user input changing the displayed result in the first panel. For example, the user selects Team 1 from the list of teams in panel 310, and panel 310 is updated to show Team 1 as selected. The user selection is sent to the system 300.
At block 507, the system 300 updates the display of the first panel. If there are any changes to be made to panel 310, the system 300 can refresh panel 310, e.g., by rerunning the query and/or regenerating panel 310 through the template engine 350. In the example of
At block 508, the system 300 updates the display of the second panel. Since the query of panel 330 links to panel 310, panel 330 is also updated to display games for Team 1 for the season selected in panel 320. For example, the query for panel 330 can be rerun. In this manner, linked panels can be updated dynamically.
At block 601, the system 400 creates a custom function to verify parameters in a query. The custom functions may be Handlebars helpers explained above, such as param helper, {{esc}} helper, {{#esc}}{{/esc}} block helper, etc.
At block 602, the system 400 receives a query using the custom function from a panel in the user interface. The user writes a query that uses the custom function.
At block 603, the system 400 invokes the custom function to verify and process parameters in the query. In one embodiment, the custom function replaces the parameters with respective placeholders and stores respective values corresponding to the parameters in an array. In another embodiment, the custom function changes respective values corresponding to the parameters to string format.
At block 604, the system 400 runs the query with the processed parameters to write to or read from the data source(s) 410.
In certain embodiments, the user login information may be saved as global variables so that they can be accessible within the document. The user login information can include the group, email address, name, etc. of the user. The user login information may be used in queries, for example, to check permissions, etc.
Dashboard Creation Application
The system for providing a plurality of dynamic panels in a user interface as explained above may also be referred to as a “Dashboard Creation Application.” The Dashboard Creation Application (DCA) can be an extensible WYSIWYG (What You See Is What You Get) web application for quickly and easily creating interactive, data-driven web pages. For example, the Dashboard Creation Application can easily create interactive dashboards which support lightweight filtering and drill-down operations on top of arbitrary data storage systems or data sources.
In one embodiment, the Dashboard Creation Application enables analysts to author dashboards of visualizations for easy consumption by end users. It will provide a number of panels like charts, tables, and images, in a pluggable architecture so analysts can add custom panels for particular deployments. For example, a standard plug-in structure can be used across systems and products. Panels will be interactive and coordinated, and support filtering/aggregations to create drill-down style analysis. The dashboard author will have fine control over the layout and styling of the panels contained in each Dashboard Creation Application dashboard. The Dashboard Creation Application will be deployable on top of any collection of other products for presentation and dashboarding use cases because it is agnostic to the underlying data store.
In various embodiments, the Dashboard Creation Application may perform one or more of the functions noted below:
In some embodiments, the Dashboard Creation Application integrates closely with other products so that more use cases can be covered by combining the tools appropriately. The numbers and types of users reached can be increased by improving the usability and expressiveness of the UI available to end users for building dashboards. In various embodiments, the Dashboard Creation Application may implement one or more of the functions noted below:
According to one embodiment, the techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include circuitry or digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or program logic to implement the techniques.
Computing device(s) are generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatible operating systems. In other embodiments, the computing device may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (“GUI”), among other things.
For example,
Computer system 800 includes a bus 802 or other communication mechanism for communicating information, and a hardware processor, or multiple processors, 804 coupled with bus 802 for processing information. Hardware processor(s) 804 may be, for example, one or more general purpose microprocessors.
Computer system 800 also includes a main memory 806, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 802 for storing information and instructions to be executed by processor 804. Main memory 806 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 804. Such instructions, when stored in storage media accessible to processor 804, render computer system 800 into a special-purpose machine that is customized to perform the operations specified in the instructions.
Computer system 800 further includes a read only memory (ROM) 808 or other static storage device coupled to bus 802 for storing static information and instructions for processor 804. A storage device 810, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 802 for storing information and instructions.
Computer system 800 may be coupled via bus 802 to a display 812, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user. An input device 814, including alphanumeric and other keys, is coupled to bus 802 for communicating information and command selections to processor 804. Another type of user input device is cursor control 816, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 804 and for controlling cursor movement on display 812. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. In some embodiments, the same direction information and command selections as cursor control may be implemented via receiving touches on a touch screen without a cursor.
Computing system 800 may include a user interface module to implement a GUI that may be stored in a mass storage device as executable software codes that are executed by the computing device(s). This and other modules may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution). Such software code may be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage
Computer system 800 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 800 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 800 in response to processor(s) 804 executing one or more sequences of one or more instructions contained in main memory 806. Such instructions may be read into main memory 806 from another storage medium, such as storage device 810. Execution of the sequences of instructions contained in main memory 806 causes processor(s) 804 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
The term “non-transitory media,” and similar terms, as used herein refers to any media that store data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 810. Volatile media includes dynamic memory, such as main memory 806. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.
Non-transitory media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between nontransitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 802. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 804 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 800 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 802. Bus 802 carries the data to main memory 806, from which processor 804 retrieves and executes the instructions. The instructions received by main memory 806 may optionally be stored on storage device 810 either before or after execution by processor 804.
Computer system 800 also includes a communication interface 818 coupled to bus 802. Communication interface 818 provides a two-way data communication coupling to a network link 820 that is connected to a local network 822. For example, communication interface 818 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 818 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicate with a WAN). Wireless links may also be implemented. In any such implementation, communication interface 818 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
Network link 820 typically provides data communication through one or more networks to other data devices. For example, network link 820 may provide a connection through local network 822 to a host computer 824 or to data equipment operated by an Internet Service Provider (ISP) 826. ISP 826 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 825. Local network 822 and Internet 825 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 820 and through communication interface 818, which carry the digital data to and from computer system 800, are example forms of transmission media.
Computer system 800 can send messages and receive data, including program code, through the network(s), network link 820 and communication interface 818. In the Internet example, a server 830 might transmit a requested code for an application program through Internet 825, ISP 826, local network 822 and communication interface 818.
The received code may be executed by processor 804 as it is received, and/or stored in storage device 810, or other non-volatile storage for later execution.
Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms may be implemented partially or wholly in application-specific circuitry.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
This application claims the benefit of U.S. Provisional Application No. 62/045,488, filed Sep. 3, 2014, and U.S. Provisional Application No. 62/135,448, filed Mar. 19, 2015, each of which is incorporated herein by reference in its entirety. Any and all applications, if any, for which a foreign or domestic priority claim is identified in the Application Data Sheet of the present application are hereby incorporated by reference under 37 CFR 1.57.
Number | Name | Date | Kind |
---|---|---|---|
5109399 | Thompson | Apr 1992 | A |
5241625 | Epard et al. | Aug 1993 | A |
5329108 | Lamoure | Jul 1994 | A |
5632009 | Rao et al. | May 1997 | A |
5670987 | Doi et al. | Sep 1997 | A |
5724575 | Hoover et al. | Mar 1998 | A |
5781704 | Rossmo | Jul 1998 | A |
5798769 | Chiu et al. | Aug 1998 | A |
5845300 | Comer | Dec 1998 | A |
5872973 | Mitchell et al. | Feb 1999 | A |
5897636 | Kaeser | Apr 1999 | A |
5999911 | Berg et al. | Dec 1999 | A |
6057757 | Arrowsmith et al. | May 2000 | A |
6065026 | Cornelia et al. | May 2000 | A |
6073129 | Levine et al. | Jun 2000 | A |
6091956 | Hollenberg | Jul 2000 | A |
6161098 | Wallman | Dec 2000 | A |
6219053 | Tachibana et al. | Apr 2001 | B1 |
6232971 | Haynes | May 2001 | B1 |
6237138 | Hameluck et al. | May 2001 | B1 |
6243706 | Moreau et al. | Jun 2001 | B1 |
6243717 | Gordon et al. | Jun 2001 | B1 |
6247019 | Davies | Jun 2001 | B1 |
6279018 | Kudrolli et al. | Aug 2001 | B1 |
6304873 | Klein et al. | Oct 2001 | B1 |
6341310 | Leshem et al. | Jan 2002 | B1 |
6366933 | Ball et al. | Apr 2002 | B1 |
6369835 | Lin | Apr 2002 | B1 |
6370538 | Lamping et al. | Apr 2002 | B1 |
6418438 | Campbell | Jul 2002 | B1 |
6430305 | Decker | Aug 2002 | B1 |
6456997 | Shukla | Sep 2002 | B1 |
6510504 | Satyanarayana | Jan 2003 | B2 |
6523019 | Borthwick | Feb 2003 | B1 |
6549944 | Weinberg et al. | Apr 2003 | B1 |
6560620 | Ching | May 2003 | B1 |
6574635 | Stauber et al. | Jun 2003 | B2 |
6581068 | Bensoussan et al. | Jun 2003 | B1 |
6594672 | Lampson et al. | Jul 2003 | B1 |
6631496 | Li et al. | Oct 2003 | B1 |
6642945 | Sharpe | Nov 2003 | B1 |
6665683 | Meltzer | Dec 2003 | B1 |
6674434 | Chojnacki et al. | Jan 2004 | B1 |
6714936 | Nevin, III | Mar 2004 | B1 |
6745382 | Zothner | Jun 2004 | B1 |
6775675 | Nwabueze et al. | Aug 2004 | B1 |
6820135 | Dingman | Nov 2004 | B1 |
6828920 | Owen et al. | Dec 2004 | B2 |
6839745 | Dingari et al. | Jan 2005 | B1 |
6850317 | Mullins et al. | Feb 2005 | B2 |
6877137 | Rivette et al. | Apr 2005 | B1 |
6944821 | Bates et al. | Sep 2005 | B1 |
6967589 | Peters | Nov 2005 | B1 |
6976210 | Silva et al. | Dec 2005 | B1 |
6980984 | Huffman et al. | Dec 2005 | B1 |
6985950 | Hanson et al. | Jan 2006 | B1 |
7036085 | Barros | Apr 2006 | B2 |
7043702 | Chi et al. | May 2006 | B2 |
7055110 | Kupka et al. | May 2006 | B2 |
7058648 | Lightfoot et al. | Jun 2006 | B1 |
7086028 | Davis et al. | Aug 2006 | B1 |
7111231 | Huck et al. | Sep 2006 | B1 |
7139800 | Bellotti et al. | Nov 2006 | B2 |
7158878 | Rasmussen et al. | Jan 2007 | B2 |
7162475 | Ackerman | Jan 2007 | B2 |
7168039 | Bertram | Jan 2007 | B2 |
7171427 | Witkowski | Jan 2007 | B2 |
7174377 | Bernard et al. | Feb 2007 | B2 |
7194680 | Roy | Mar 2007 | B1 |
7213030 | Jenkins | May 2007 | B1 |
7269786 | Malloy et al. | Sep 2007 | B1 |
7278105 | Kitts | Oct 2007 | B1 |
7290698 | Poslinski et al. | Nov 2007 | B2 |
7333998 | Heckerman et al. | Feb 2008 | B2 |
7370047 | Gorman | May 2008 | B2 |
7379811 | Rasmussen et al. | May 2008 | B2 |
7379903 | Caballero et al. | May 2008 | B2 |
7392254 | Jenkins | Jun 2008 | B1 |
7426654 | Adams et al. | Sep 2008 | B2 |
7441182 | Beilinson et al. | Oct 2008 | B2 |
7441219 | Perry et al. | Oct 2008 | B2 |
7454466 | Bellotti et al. | Nov 2008 | B2 |
7461158 | Rider et al. | Dec 2008 | B2 |
7467375 | Tondreau et al. | Dec 2008 | B2 |
7487139 | Fraleigh et al. | Feb 2009 | B2 |
7502786 | Liu et al. | Mar 2009 | B2 |
7525422 | Bishop et al. | Apr 2009 | B2 |
7529727 | Arning et al. | May 2009 | B2 |
7529734 | Dirisala | May 2009 | B2 |
7558677 | Jones | Jul 2009 | B2 |
7574409 | Patinkin | Aug 2009 | B2 |
7574428 | Leiserowitz et al. | Aug 2009 | B2 |
7579965 | Bucholz | Aug 2009 | B2 |
7596285 | Brown et al. | Sep 2009 | B2 |
7614006 | Molander | Nov 2009 | B2 |
7617232 | Gabbert et al. | Nov 2009 | B2 |
7620628 | Kapur et al. | Nov 2009 | B2 |
7627812 | Chamberlain et al. | Dec 2009 | B2 |
7634717 | Chamberlain et al. | Dec 2009 | B2 |
7703021 | Flam | Apr 2010 | B1 |
7706817 | Bamrah et al. | Apr 2010 | B2 |
7712049 | Williams et al. | May 2010 | B2 |
7716077 | Mikurak | May 2010 | B1 |
7725530 | Sah et al. | May 2010 | B2 |
7725547 | Albertson et al. | May 2010 | B2 |
7725728 | Ama et al. | May 2010 | B2 |
7730082 | Sah et al. | Jun 2010 | B2 |
7730109 | Rohrs et al. | Jun 2010 | B2 |
7765489 | Shah et al. | Jul 2010 | B1 |
7770100 | Chamberlain et al. | Aug 2010 | B2 |
7805457 | Viola et al. | Sep 2010 | B1 |
7809703 | Balabhadrapatruni et al. | Oct 2010 | B2 |
7818658 | Chen | Oct 2010 | B2 |
7870493 | Pall et al. | Jan 2011 | B2 |
7877421 | Berger et al. | Jan 2011 | B2 |
7880921 | Dattilo et al. | Feb 2011 | B2 |
7894984 | Rasmussen et al. | Feb 2011 | B2 |
7899611 | Downs et al. | Mar 2011 | B2 |
7917376 | Bellin et al. | Mar 2011 | B2 |
7920963 | Jouline et al. | Apr 2011 | B2 |
7933862 | Chamberlain et al. | Apr 2011 | B2 |
7941336 | Robin-Jan | May 2011 | B1 |
7958147 | Turner et al. | Jun 2011 | B1 |
7962281 | Rasmussen et al. | Jun 2011 | B2 |
7962495 | Jain et al. | Jun 2011 | B2 |
7962848 | Bertram | Jun 2011 | B2 |
7966199 | Frasher | Jun 2011 | B1 |
7970240 | Chao et al. | Jun 2011 | B1 |
7971150 | Raskutti et al. | Jun 2011 | B2 |
7984374 | Caro et al. | Jul 2011 | B2 |
8001465 | Kudrolli et al. | Aug 2011 | B2 |
8001482 | Bhattiprolu et al. | Aug 2011 | B2 |
8010507 | Poston et al. | Aug 2011 | B2 |
8010545 | Stefik et al. | Aug 2011 | B2 |
8015487 | Roy et al. | Sep 2011 | B2 |
8024778 | Cash et al. | Sep 2011 | B2 |
8036632 | Cona et al. | Oct 2011 | B1 |
8041714 | Aymeloglu et al. | Oct 2011 | B2 |
8073857 | Sreekanth | Dec 2011 | B2 |
8103543 | Zwicky | Jan 2012 | B1 |
8112425 | Baum et al. | Feb 2012 | B2 |
8126848 | Wagner | Feb 2012 | B2 |
8134457 | Velipasalar et al. | Mar 2012 | B2 |
8145703 | Frishert et al. | Mar 2012 | B2 |
8185819 | Sah et al. | May 2012 | B2 |
8191005 | Baier et al. | May 2012 | B2 |
8214361 | Sandler et al. | Jul 2012 | B1 |
8214764 | Gemmell et al. | Jul 2012 | B2 |
8225201 | Michael | Jul 2012 | B2 |
8229947 | Fujinaga | Jul 2012 | B2 |
8230333 | Decherd et al. | Jul 2012 | B2 |
8271461 | Pike et al. | Sep 2012 | B2 |
8280880 | Aymeloglu et al. | Oct 2012 | B1 |
8290838 | Thakur et al. | Oct 2012 | B1 |
8290926 | Ozzie et al. | Oct 2012 | B2 |
8290942 | Jones et al. | Oct 2012 | B2 |
8301464 | Cave et al. | Oct 2012 | B1 |
8301904 | Gryaznov | Oct 2012 | B1 |
8302855 | Ma et al. | Nov 2012 | B2 |
8312367 | Foster | Nov 2012 | B2 |
8312546 | Alme | Nov 2012 | B2 |
8352881 | Champion et al. | Jan 2013 | B2 |
8368695 | Howell et al. | Feb 2013 | B2 |
8397171 | Klassen et al. | Mar 2013 | B2 |
8412707 | Mianji | Apr 2013 | B1 |
8447722 | Ahuja et al. | May 2013 | B1 |
8452790 | Mianji | May 2013 | B1 |
8463036 | Ramesh et al. | Jun 2013 | B1 |
8489331 | Kopf et al. | Jul 2013 | B2 |
8489641 | Seefeld et al. | Jul 2013 | B1 |
8494984 | Ito et al. | Jul 2013 | B2 |
8504542 | Chang et al. | Aug 2013 | B2 |
8510743 | Hackborn et al. | Aug 2013 | B2 |
8514082 | Cova et al. | Aug 2013 | B2 |
8515207 | Chau | Aug 2013 | B2 |
8527949 | Pleis et al. | Sep 2013 | B1 |
8554579 | Tribble et al. | Oct 2013 | B2 |
8554653 | Falkenborg et al. | Oct 2013 | B2 |
8554709 | Goodson et al. | Oct 2013 | B2 |
8560413 | Quarterman et al. | Oct 2013 | B1 |
8577911 | Stepinski et al. | Nov 2013 | B1 |
8589273 | Creeden et al. | Nov 2013 | B2 |
8595234 | Siripurapu et al. | Nov 2013 | B2 |
8620641 | Farnsworth et al. | Dec 2013 | B2 |
8639757 | Zang et al. | Jan 2014 | B1 |
8646080 | Williamson et al. | Feb 2014 | B2 |
8676857 | Adams et al. | Mar 2014 | B1 |
8682696 | Shanmugam | Mar 2014 | B1 |
8688573 | Rukonic et al. | Apr 2014 | B1 |
8689108 | Duffield et al. | Apr 2014 | B1 |
8713467 | Goldenberg et al. | Apr 2014 | B1 |
8726379 | Stiansen et al. | May 2014 | B1 |
8732574 | Burr et al. | May 2014 | B2 |
8739278 | Varghese | May 2014 | B2 |
8742934 | Sarpy et al. | Jun 2014 | B1 |
8744890 | Bernier | Jun 2014 | B1 |
8745516 | Mason et al. | Jun 2014 | B2 |
8781169 | Jackson et al. | Jul 2014 | B2 |
8787939 | Papakipos et al. | Jul 2014 | B2 |
8788407 | Singh et al. | Jul 2014 | B1 |
8799313 | Satlow | Aug 2014 | B2 |
8799799 | Cervelli et al. | Aug 2014 | B1 |
8807948 | Luo et al. | Aug 2014 | B2 |
8812960 | Sun et al. | Aug 2014 | B1 |
8830322 | Nerayoff et al. | Sep 2014 | B2 |
8832594 | Thompson et al. | Sep 2014 | B1 |
8868537 | Colgrove et al. | Oct 2014 | B1 |
8917274 | Ma et al. | Dec 2014 | B2 |
8924872 | Bogomolov et al. | Dec 2014 | B1 |
8930331 | McGrew et al. | Jan 2015 | B2 |
8930874 | Duff et al. | Jan 2015 | B2 |
8937619 | Sharma et al. | Jan 2015 | B2 |
8938686 | Erenrich et al. | Jan 2015 | B1 |
8984390 | Aymeloglu et al. | Mar 2015 | B2 |
9009171 | Grossman et al. | Apr 2015 | B1 |
9009827 | Albertson et al. | Apr 2015 | B1 |
9021260 | Falk et al. | Apr 2015 | B1 |
9021384 | Beard et al. | Apr 2015 | B1 |
9043696 | Meiklejohn et al. | May 2015 | B1 |
9043894 | Dennison et al. | May 2015 | B1 |
9058315 | Burr et al. | Jun 2015 | B2 |
9116975 | Shankar et al. | Aug 2015 | B2 |
9165100 | Begur et al. | Oct 2015 | B2 |
20010051949 | Carey et al. | Dec 2001 | A1 |
20020032677 | Morgenthaler et al. | Mar 2002 | A1 |
20020033848 | Sciammarella et al. | Mar 2002 | A1 |
20020065708 | Senay et al. | May 2002 | A1 |
20020091694 | Hrle et al. | Jul 2002 | A1 |
20020091707 | Keller | Jul 2002 | A1 |
20020095360 | Joao | Jul 2002 | A1 |
20020095658 | Shulman | Jul 2002 | A1 |
20020103705 | Brady | Aug 2002 | A1 |
20020116120 | Ruiz et al. | Aug 2002 | A1 |
20020174201 | Ramer et al. | Nov 2002 | A1 |
20020194119 | Wright et al. | Dec 2002 | A1 |
20020196229 | Chen et al. | Dec 2002 | A1 |
20030028560 | Kudrolli et al. | Feb 2003 | A1 |
20030036927 | Bowen | Feb 2003 | A1 |
20030039948 | Donahue | Feb 2003 | A1 |
20030093755 | O'Carroll | May 2003 | A1 |
20030105759 | Bess et al. | Jun 2003 | A1 |
20030115481 | Baird et al. | Jun 2003 | A1 |
20030120675 | Stauber et al. | Jun 2003 | A1 |
20030126102 | Borthwick | Jul 2003 | A1 |
20030140106 | Raguseo | Jul 2003 | A1 |
20030144868 | MacIntyre et al. | Jul 2003 | A1 |
20030163352 | Surpin et al. | Aug 2003 | A1 |
20030212718 | Tester | Nov 2003 | A1 |
20030225755 | Iwayama et al. | Dec 2003 | A1 |
20030229848 | Arend et al. | Dec 2003 | A1 |
20040032432 | Baynger | Feb 2004 | A1 |
20040034570 | Davis | Feb 2004 | A1 |
20040044648 | Anfindsen et al. | Mar 2004 | A1 |
20040064256 | Barinek et al. | Apr 2004 | A1 |
20040085318 | Hassler et al. | May 2004 | A1 |
20040095349 | Bito et al. | May 2004 | A1 |
20040111410 | Burgoon et al. | Jun 2004 | A1 |
20040117345 | Bamford et al. | Jun 2004 | A1 |
20040117387 | Civetta et al. | Jun 2004 | A1 |
20040126840 | Cheng et al. | Jul 2004 | A1 |
20040143602 | Ruiz et al. | Jul 2004 | A1 |
20040143796 | Lerner et al. | Jul 2004 | A1 |
20040148301 | McKay et al. | Jul 2004 | A1 |
20040163039 | Gorman | Aug 2004 | A1 |
20040193600 | Kaasten et al. | Sep 2004 | A1 |
20040205492 | Newsome | Oct 2004 | A1 |
20040221223 | Yu et al. | Nov 2004 | A1 |
20040236688 | Bozeman | Nov 2004 | A1 |
20040236711 | Nixon et al. | Nov 2004 | A1 |
20040260702 | Cragun et al. | Dec 2004 | A1 |
20040267746 | Marcjan et al. | Dec 2004 | A1 |
20050010472 | Quatse et al. | Jan 2005 | A1 |
20050027705 | Sadri et al. | Feb 2005 | A1 |
20050028094 | Allyn | Feb 2005 | A1 |
20050039116 | Slack-Smith | Feb 2005 | A1 |
20050039119 | Parks et al. | Feb 2005 | A1 |
20050065811 | Chu et al. | Mar 2005 | A1 |
20050080769 | Gemmell | Apr 2005 | A1 |
20050086207 | Heuer et al. | Apr 2005 | A1 |
20050091186 | Elish | Apr 2005 | A1 |
20050097441 | Herbach et al. | May 2005 | A1 |
20050108231 | Findleton et al. | May 2005 | A1 |
20050114763 | Nonomura et al. | May 2005 | A1 |
20050125715 | Franco et al. | Jun 2005 | A1 |
20050162523 | Darrell et al. | Jul 2005 | A1 |
20050166144 | Gross | Jul 2005 | A1 |
20050180330 | Shapiro | Aug 2005 | A1 |
20050182793 | Keenan et al. | Aug 2005 | A1 |
20050183005 | Denoue et al. | Aug 2005 | A1 |
20050210409 | Jou | Sep 2005 | A1 |
20050246327 | Yeung et al. | Nov 2005 | A1 |
20050251786 | Citron et al. | Nov 2005 | A1 |
20050289524 | McGinnes | Dec 2005 | A1 |
20060026120 | Carolan et al. | Feb 2006 | A1 |
20060026170 | Kreitler et al. | Feb 2006 | A1 |
20060026561 | Bauman et al. | Feb 2006 | A1 |
20060031779 | Theurer et al. | Feb 2006 | A1 |
20060053097 | King et al. | Mar 2006 | A1 |
20060053170 | Hill et al. | Mar 2006 | A1 |
20060059139 | Robinson | Mar 2006 | A1 |
20060059423 | Lehmann et al. | Mar 2006 | A1 |
20060074881 | Vembu et al. | Apr 2006 | A1 |
20060080139 | Mainzer | Apr 2006 | A1 |
20060080316 | Gilmore et al. | Apr 2006 | A1 |
20060080619 | Carlson et al. | Apr 2006 | A1 |
20060093222 | Saffer et al. | May 2006 | A1 |
20060095521 | Patinkin | May 2006 | A1 |
20060116991 | Calderwood | Jun 2006 | A1 |
20060129746 | Porter | Jun 2006 | A1 |
20060136513 | Ngo et al. | Jun 2006 | A1 |
20060139375 | Rasmussen et al. | Jun 2006 | A1 |
20060142949 | Helt | Jun 2006 | A1 |
20060143034 | Rothermel | Jun 2006 | A1 |
20060143075 | Carr et al. | Jun 2006 | A1 |
20060149596 | Surpin et al. | Jul 2006 | A1 |
20060155654 | Plessis et al. | Jul 2006 | A1 |
20060161558 | Tamma et al. | Jul 2006 | A1 |
20060178915 | Chao | Aug 2006 | A1 |
20060203337 | White | Sep 2006 | A1 |
20060218206 | Bourbonnais et al. | Sep 2006 | A1 |
20060218491 | Grossman et al. | Sep 2006 | A1 |
20060218637 | Thomas et al. | Sep 2006 | A1 |
20060241974 | Chao et al. | Oct 2006 | A1 |
20060242040 | Rader | Oct 2006 | A1 |
20060242630 | Koike et al. | Oct 2006 | A1 |
20060253502 | Raman et al. | Nov 2006 | A1 |
20060265397 | Bryan et al. | Nov 2006 | A1 |
20060265417 | Amato et al. | Nov 2006 | A1 |
20060271277 | Hu et al. | Nov 2006 | A1 |
20060277460 | Forstall et al. | Dec 2006 | A1 |
20060279630 | Aggarwal et al. | Dec 2006 | A1 |
20070000999 | Kubo et al. | Jan 2007 | A1 |
20070011150 | Frank | Jan 2007 | A1 |
20070016363 | Huang et al. | Jan 2007 | A1 |
20070038646 | Thota | Feb 2007 | A1 |
20070038962 | Fuchs et al. | Feb 2007 | A1 |
20070043686 | Teng et al. | Feb 2007 | A1 |
20070050429 | Goldring et al. | Mar 2007 | A1 |
20070057966 | Ohno et al. | Mar 2007 | A1 |
20070061487 | Moore et al. | Mar 2007 | A1 |
20070061752 | Cory | Mar 2007 | A1 |
20070078832 | Ott et al. | Apr 2007 | A1 |
20070083541 | Fraleigh et al. | Apr 2007 | A1 |
20070094389 | Nussey et al. | Apr 2007 | A1 |
20070113164 | Hansen et al. | May 2007 | A1 |
20070136095 | Weinstein | Jun 2007 | A1 |
20070143253 | Kostamaa et al. | Jun 2007 | A1 |
20070150369 | Zivin | Jun 2007 | A1 |
20070168871 | Jenkins | Jul 2007 | A1 |
20070174760 | Chamberlain et al. | Jul 2007 | A1 |
20070185850 | Walters | Aug 2007 | A1 |
20070192265 | Chopin et al. | Aug 2007 | A1 |
20070198571 | Ferguson et al. | Aug 2007 | A1 |
20070208497 | Downs et al. | Sep 2007 | A1 |
20070208498 | Barker et al. | Sep 2007 | A1 |
20070208736 | Tanigawa et al. | Sep 2007 | A1 |
20070233709 | Abnous | Oct 2007 | A1 |
20070233756 | D'Souza et al. | Oct 2007 | A1 |
20070240062 | Christena et al. | Oct 2007 | A1 |
20070245339 | Bauman et al. | Oct 2007 | A1 |
20070266336 | Nojima et al. | Nov 2007 | A1 |
20070271317 | Carmel | Nov 2007 | A1 |
20070284433 | Domenica et al. | Dec 2007 | A1 |
20070294643 | Kyle | Dec 2007 | A1 |
20070299697 | Friedlander et al. | Dec 2007 | A1 |
20080015970 | Brookfield et al. | Jan 2008 | A1 |
20080016155 | Khalatian | Jan 2008 | A1 |
20080040684 | Crump | Feb 2008 | A1 |
20080051989 | Welsh | Feb 2008 | A1 |
20080052142 | Bailey et al. | Feb 2008 | A1 |
20080077597 | Butler | Mar 2008 | A1 |
20080077642 | Carbone et al. | Mar 2008 | A1 |
20080082486 | Lermant et al. | Apr 2008 | A1 |
20080091693 | Murthy | Apr 2008 | A1 |
20080104019 | Nath | May 2008 | A1 |
20080104149 | Vishniac et al. | May 2008 | A1 |
20080109714 | Kumar et al. | May 2008 | A1 |
20080126951 | Sood et al. | May 2008 | A1 |
20080148398 | Mezack et al. | Jun 2008 | A1 |
20080155440 | Trevor et al. | Jun 2008 | A1 |
20080162616 | Gross et al. | Jul 2008 | A1 |
20080172607 | Baer | Jul 2008 | A1 |
20080177782 | Poston et al. | Jul 2008 | A1 |
20080186904 | Koyama et al. | Aug 2008 | A1 |
20080195417 | Surpin et al. | Aug 2008 | A1 |
20080195608 | Clover | Aug 2008 | A1 |
20080195672 | Hamel et al. | Aug 2008 | A1 |
20080222295 | Robinson et al. | Sep 2008 | A1 |
20080249820 | Pathria et al. | Oct 2008 | A1 |
20080255973 | El Wade et al. | Oct 2008 | A1 |
20080263468 | Cappione et al. | Oct 2008 | A1 |
20080267107 | Rosenberg | Oct 2008 | A1 |
20080270316 | Guidotti et al. | Oct 2008 | A1 |
20080276167 | Michael | Nov 2008 | A1 |
20080278311 | Grange et al. | Nov 2008 | A1 |
20080288306 | MacIntyre et al. | Nov 2008 | A1 |
20080301378 | Carrie | Dec 2008 | A1 |
20080301643 | Appleton et al. | Dec 2008 | A1 |
20080313132 | Hao et al. | Dec 2008 | A1 |
20080313243 | Poston et al. | Dec 2008 | A1 |
20090002492 | Velipasalar et al. | Jan 2009 | A1 |
20090027418 | Maru et al. | Jan 2009 | A1 |
20090030915 | Winter et al. | Jan 2009 | A1 |
20090031247 | Walter et al. | Jan 2009 | A1 |
20090031401 | Cudich et al. | Jan 2009 | A1 |
20090043801 | LeClair et al. | Feb 2009 | A1 |
20090055251 | Shah et al. | Feb 2009 | A1 |
20090088964 | Schaaf et al. | Apr 2009 | A1 |
20090089651 | Herberger et al. | Apr 2009 | A1 |
20090106178 | Chu | Apr 2009 | A1 |
20090106308 | Killian et al. | Apr 2009 | A1 |
20090112678 | Luzardo | Apr 2009 | A1 |
20090112745 | Stefanescu | Apr 2009 | A1 |
20090119309 | Gibson et al. | May 2009 | A1 |
20090125359 | Knapic | May 2009 | A1 |
20090125369 | Kloostra et al. | May 2009 | A1 |
20090125459 | Norton et al. | May 2009 | A1 |
20090132921 | Hwangbo et al. | May 2009 | A1 |
20090132953 | Reed et al. | May 2009 | A1 |
20090143052 | Bates et al. | Jun 2009 | A1 |
20090144262 | White et al. | Jun 2009 | A1 |
20090144274 | Fraleigh et al. | Jun 2009 | A1 |
20090150868 | Chakra et al. | Jun 2009 | A1 |
20090164387 | Armstrong et al. | Jun 2009 | A1 |
20090164934 | Bhattiprolu et al. | Jun 2009 | A1 |
20090171939 | Athsani et al. | Jul 2009 | A1 |
20090172511 | Decherd et al. | Jul 2009 | A1 |
20090172821 | Daira et al. | Jul 2009 | A1 |
20090177962 | Gusmorino | Jul 2009 | A1 |
20090179892 | Tsuda et al. | Jul 2009 | A1 |
20090187464 | Bai et al. | Jul 2009 | A1 |
20090187546 | Whyte et al. | Jul 2009 | A1 |
20090199106 | Jonsson et al. | Aug 2009 | A1 |
20090222400 | Kupershmidt et al. | Sep 2009 | A1 |
20090222759 | Drieschner | Sep 2009 | A1 |
20090222760 | Halverson et al. | Sep 2009 | A1 |
20090234720 | George et al. | Sep 2009 | A1 |
20090248757 | Havewala et al. | Oct 2009 | A1 |
20090249178 | Ambrosino et al. | Oct 2009 | A1 |
20090249244 | Robinson et al. | Oct 2009 | A1 |
20090254970 | Agarwal et al. | Oct 2009 | A1 |
20090254971 | Herz | Oct 2009 | A1 |
20090271343 | Vaiciulis et al. | Oct 2009 | A1 |
20090271435 | Yako et al. | Oct 2009 | A1 |
20090281839 | Lynn et al. | Nov 2009 | A1 |
20090282068 | Shockro et al. | Nov 2009 | A1 |
20090287470 | Farnsworth et al. | Nov 2009 | A1 |
20090292626 | Oxford | Nov 2009 | A1 |
20090307049 | Elliott et al. | Dec 2009 | A1 |
20090313223 | Rantanen | Dec 2009 | A1 |
20090313311 | Hoffmann et al. | Dec 2009 | A1 |
20090313463 | Pang et al. | Dec 2009 | A1 |
20090319891 | MacKinlay et al. | Dec 2009 | A1 |
20100011282 | Dollard et al. | Jan 2010 | A1 |
20100036831 | Vemuri et al. | Feb 2010 | A1 |
20100042922 | Bradateanu et al. | Feb 2010 | A1 |
20100057622 | Faith et al. | Mar 2010 | A1 |
20100057716 | Stefik et al. | Mar 2010 | A1 |
20100070523 | Delgo et al. | Mar 2010 | A1 |
20100070842 | Aymeloglu et al. | Mar 2010 | A1 |
20100070844 | Aymeloglu et al. | Mar 2010 | A1 |
20100070845 | Facemire et al. | Mar 2010 | A1 |
20100070897 | Aymeloglu et al. | Mar 2010 | A1 |
20100076939 | Iwaki et al. | Mar 2010 | A1 |
20100082541 | Kottomtharayil | Apr 2010 | A1 |
20100098318 | Anderson | Apr 2010 | A1 |
20100100963 | Mahaffey | Apr 2010 | A1 |
20100103124 | Kruzeniski et al. | Apr 2010 | A1 |
20100114817 | Broeder et al. | May 2010 | A1 |
20100114831 | Gilbert et al. | May 2010 | A1 |
20100114887 | Conway et al. | May 2010 | A1 |
20100122152 | Chamberlain et al. | May 2010 | A1 |
20100131457 | Heimendinger | May 2010 | A1 |
20100138842 | Balko et al. | Jun 2010 | A1 |
20100145909 | Ngo | Jun 2010 | A1 |
20100161565 | Lee et al. | Jun 2010 | A1 |
20100161688 | Kesselman et al. | Jun 2010 | A1 |
20100162176 | Dunton | Jun 2010 | A1 |
20100191563 | Schlaifer et al. | Jul 2010 | A1 |
20100191884 | Holenstein et al. | Jul 2010 | A1 |
20100198684 | Eraker et al. | Aug 2010 | A1 |
20100199225 | Coleman et al. | Aug 2010 | A1 |
20100211550 | Daniello et al. | Aug 2010 | A1 |
20100211618 | Anderson et al. | Aug 2010 | A1 |
20100223260 | Wu | Sep 2010 | A1 |
20100228812 | Uomini | Sep 2010 | A1 |
20100235606 | Oreland et al. | Sep 2010 | A1 |
20100238174 | Haub et al. | Sep 2010 | A1 |
20100250412 | Wagner | Sep 2010 | A1 |
20100262901 | DiSalvo | Oct 2010 | A1 |
20100280851 | Merkin | Nov 2010 | A1 |
20100280857 | Liu et al. | Nov 2010 | A1 |
20100283787 | Hamedi et al. | Nov 2010 | A1 |
20100293174 | Bennett et al. | Nov 2010 | A1 |
20100306713 | Geisner et al. | Dec 2010 | A1 |
20100306722 | LeHoty et al. | Dec 2010 | A1 |
20100313119 | Baldwin et al. | Dec 2010 | A1 |
20100313239 | Chakra et al. | Dec 2010 | A1 |
20100318924 | Frankel et al. | Dec 2010 | A1 |
20100321399 | Ellren et al. | Dec 2010 | A1 |
20100325526 | Ellis et al. | Dec 2010 | A1 |
20100325581 | Finkelstein et al. | Dec 2010 | A1 |
20100330801 | Rouh | Dec 2010 | A1 |
20110029498 | Ferguson et al. | Feb 2011 | A1 |
20110029526 | Knight et al. | Feb 2011 | A1 |
20110047159 | Baid et al. | Feb 2011 | A1 |
20110047540 | Williams | Feb 2011 | A1 |
20110060753 | Shaked et al. | Mar 2011 | A1 |
20110061013 | Bilicki et al. | Mar 2011 | A1 |
20110066933 | Ludwig | Mar 2011 | A1 |
20110074788 | Regan et al. | Mar 2011 | A1 |
20110074811 | Hanson et al. | Mar 2011 | A1 |
20110078055 | Faribault et al. | Mar 2011 | A1 |
20110078173 | Seligmann et al. | Mar 2011 | A1 |
20110093327 | Fordyce, III et al. | Apr 2011 | A1 |
20110099133 | Chang et al. | Apr 2011 | A1 |
20110117878 | Barash et al. | May 2011 | A1 |
20110119100 | Ruhl et al. | May 2011 | A1 |
20110137766 | Rasmussen et al. | Jun 2011 | A1 |
20110153384 | Horne et al. | Jun 2011 | A1 |
20110161096 | Buehler et al. | Jun 2011 | A1 |
20110161409 | Nair et al. | Jun 2011 | A1 |
20110167105 | Ramakrishnan et al. | Jul 2011 | A1 |
20110170799 | Carrino et al. | Jul 2011 | A1 |
20110173032 | Payne et al. | Jul 2011 | A1 |
20110173093 | Psota et al. | Jul 2011 | A1 |
20110173619 | Fish | Jul 2011 | A1 |
20110179048 | Satlow | Jul 2011 | A1 |
20110184813 | Barne et al. | Jul 2011 | A1 |
20110185316 | Reid et al. | Jul 2011 | A1 |
20110208565 | Ross et al. | Aug 2011 | A1 |
20110208724 | Jones et al. | Aug 2011 | A1 |
20110213655 | Henkin | Sep 2011 | A1 |
20110218934 | Elser | Sep 2011 | A1 |
20110219450 | McDougal et al. | Sep 2011 | A1 |
20110225198 | Edwards et al. | Sep 2011 | A1 |
20110225482 | Chan et al. | Sep 2011 | A1 |
20110238495 | Kang | Sep 2011 | A1 |
20110238553 | Raj et al. | Sep 2011 | A1 |
20110251951 | Kolkowitz | Oct 2011 | A1 |
20110258158 | Resende et al. | Oct 2011 | A1 |
20110258242 | Eidson et al. | Oct 2011 | A1 |
20110270705 | Parker | Nov 2011 | A1 |
20110270812 | Ruby | Nov 2011 | A1 |
20110289397 | Eastmond et al. | Nov 2011 | A1 |
20110289407 | Naik et al. | Nov 2011 | A1 |
20110289420 | Morioka et al. | Nov 2011 | A1 |
20110291851 | Whisenant | Dec 2011 | A1 |
20110310005 | Chen et al. | Dec 2011 | A1 |
20110314007 | Dassa et al. | Dec 2011 | A1 |
20120004894 | Butler et al. | Jan 2012 | A1 |
20120013684 | Robertson et al. | Jan 2012 | A1 |
20120019559 | Siler et al. | Jan 2012 | A1 |
20120022945 | Falkenborg et al. | Jan 2012 | A1 |
20120036013 | Neuhaus et al. | Feb 2012 | A1 |
20120036434 | Oberstein | Feb 2012 | A1 |
20120050293 | Carlhian et al. | Mar 2012 | A1 |
20120059853 | Jagota | Mar 2012 | A1 |
20120066296 | Appleton et al. | Mar 2012 | A1 |
20120072825 | Sherkin et al. | Mar 2012 | A1 |
20120079363 | Folting et al. | Mar 2012 | A1 |
20120084117 | Tavares et al. | Apr 2012 | A1 |
20120084118 | Bai et al. | Apr 2012 | A1 |
20120084184 | Raleigh et al. | Apr 2012 | A1 |
20120106801 | Jackson | May 2012 | A1 |
20120117082 | Koperda et al. | May 2012 | A1 |
20120123989 | Yu | May 2012 | A1 |
20120131512 | Takeuchi et al. | May 2012 | A1 |
20120137235 | T S et al. | May 2012 | A1 |
20120144335 | Abeln et al. | Jun 2012 | A1 |
20120150791 | Willson | Jun 2012 | A1 |
20120159307 | Chung et al. | Jun 2012 | A1 |
20120159362 | Brown et al. | Jun 2012 | A1 |
20120159399 | Bastide et al. | Jun 2012 | A1 |
20120170847 | Tsukidate | Jul 2012 | A1 |
20120173985 | Peppel | Jul 2012 | A1 |
20120180002 | Campbell et al. | Jul 2012 | A1 |
20120188252 | Law | Jul 2012 | A1 |
20120196557 | Reich et al. | Aug 2012 | A1 |
20120196558 | Reich et al. | Aug 2012 | A1 |
20120197651 | Robinson et al. | Aug 2012 | A1 |
20120197657 | Prodanovich | Aug 2012 | A1 |
20120197660 | Prodanovich | Aug 2012 | A1 |
20120203708 | Psota et al. | Aug 2012 | A1 |
20120208636 | Feige | Aug 2012 | A1 |
20120215784 | King et al. | Aug 2012 | A1 |
20120221511 | Gibson et al. | Aug 2012 | A1 |
20120221553 | Wittmer et al. | Aug 2012 | A1 |
20120221580 | Barney | Aug 2012 | A1 |
20120226590 | Love et al. | Sep 2012 | A1 |
20120245976 | Kumar et al. | Sep 2012 | A1 |
20120246148 | Dror | Sep 2012 | A1 |
20120254129 | Wheeler et al. | Oct 2012 | A1 |
20120284345 | Costenaro et al. | Nov 2012 | A1 |
20120284670 | Kashik et al. | Nov 2012 | A1 |
20120290879 | Shibuya et al. | Nov 2012 | A1 |
20120296907 | Long et al. | Nov 2012 | A1 |
20120311684 | Paulsen et al. | Dec 2012 | A1 |
20120323888 | Osann, Jr. | Dec 2012 | A1 |
20120330801 | McDougal et al. | Dec 2012 | A1 |
20120330908 | Stowe et al. | Dec 2012 | A1 |
20120330973 | Ghuneim et al. | Dec 2012 | A1 |
20130006426 | Healey et al. | Jan 2013 | A1 |
20130006725 | Simanek et al. | Jan 2013 | A1 |
20130006916 | McBride et al. | Jan 2013 | A1 |
20130016106 | Yip et al. | Jan 2013 | A1 |
20130018796 | Kolhatkar et al. | Jan 2013 | A1 |
20130024268 | Manickavelu | Jan 2013 | A1 |
20130036346 | Cicerone | Feb 2013 | A1 |
20130046635 | Grigg et al. | Feb 2013 | A1 |
20130046842 | Muntz et al. | Feb 2013 | A1 |
20130060786 | Serrano et al. | Mar 2013 | A1 |
20130061169 | Pearcy et al. | Mar 2013 | A1 |
20130073377 | Heath | Mar 2013 | A1 |
20130073454 | Busch | Mar 2013 | A1 |
20130078943 | Biage et al. | Mar 2013 | A1 |
20130086482 | Parsons | Apr 2013 | A1 |
20130097130 | Bingol et al. | Apr 2013 | A1 |
20130097482 | Marantz et al. | Apr 2013 | A1 |
20130110822 | Ikeda et al. | May 2013 | A1 |
20130110877 | Bonham et al. | May 2013 | A1 |
20130111320 | Campbell et al. | May 2013 | A1 |
20130117651 | Waldman et al. | May 2013 | A1 |
20130150004 | Rosen | Jun 2013 | A1 |
20130151148 | Parundekar et al. | Jun 2013 | A1 |
20130151305 | Akinola et al. | Jun 2013 | A1 |
20130151388 | Falkenborg et al. | Jun 2013 | A1 |
20130151453 | Bhanot et al. | Jun 2013 | A1 |
20130157234 | Gulli et al. | Jun 2013 | A1 |
20130166348 | Scotto | Jun 2013 | A1 |
20130166480 | Popescu et al. | Jun 2013 | A1 |
20130166550 | Buchmann et al. | Jun 2013 | A1 |
20130176321 | Mitchell et al. | Jul 2013 | A1 |
20130179420 | Park et al. | Jul 2013 | A1 |
20130224696 | Wolfe et al. | Aug 2013 | A1 |
20130225212 | Khan | Aug 2013 | A1 |
20130226318 | Procyk | Aug 2013 | A1 |
20130226953 | Markovich et al. | Aug 2013 | A1 |
20130232045 | Tai | Sep 2013 | A1 |
20130238616 | Rose et al. | Sep 2013 | A1 |
20130246170 | Gross et al. | Sep 2013 | A1 |
20130251233 | Yang et al. | Sep 2013 | A1 |
20130262527 | Hunter et al. | Oct 2013 | A1 |
20130263019 | Castellanos et al. | Oct 2013 | A1 |
20130267207 | Hao et al. | Oct 2013 | A1 |
20130268520 | Fisher et al. | Oct 2013 | A1 |
20130279757 | Kephart | Oct 2013 | A1 |
20130282696 | John et al. | Oct 2013 | A1 |
20130290011 | Lynn et al. | Oct 2013 | A1 |
20130290825 | Arndt et al. | Oct 2013 | A1 |
20130297619 | Chandrasekaran et al. | Nov 2013 | A1 |
20130304770 | Boero et al. | Nov 2013 | A1 |
20130311375 | Priebatsch | Nov 2013 | A1 |
20130318060 | Chang et al. | Nov 2013 | A1 |
20140019936 | Cohanoff | Jan 2014 | A1 |
20140032506 | Hoey et al. | Jan 2014 | A1 |
20140033010 | Richardt et al. | Jan 2014 | A1 |
20140040371 | Gurevich et al. | Feb 2014 | A1 |
20140047319 | Eberlein | Feb 2014 | A1 |
20140047357 | Alfaro et al. | Feb 2014 | A1 |
20140059038 | McPherson et al. | Feb 2014 | A1 |
20140067611 | Adachi et al. | Mar 2014 | A1 |
20140068487 | Steiger et al. | Mar 2014 | A1 |
20140074855 | Zhao et al. | Mar 2014 | A1 |
20140095273 | Tang et al. | Apr 2014 | A1 |
20140095509 | Patton | Apr 2014 | A1 |
20140108068 | Williams | Apr 2014 | A1 |
20140108380 | Gotz et al. | Apr 2014 | A1 |
20140108985 | Scott et al. | Apr 2014 | A1 |
20140129261 | Bothwell et al. | May 2014 | A1 |
20140129936 | Richards | May 2014 | A1 |
20140149272 | Hirani et al. | May 2014 | A1 |
20140149436 | Bahrami et al. | May 2014 | A1 |
20140156527 | Grigg et al. | Jun 2014 | A1 |
20140157172 | Peery et al. | Jun 2014 | A1 |
20140164502 | Khodorenko et al. | Jun 2014 | A1 |
20140189536 | Lange et al. | Jul 2014 | A1 |
20140195515 | Baker et al. | Jul 2014 | A1 |
20140195887 | Ellis et al. | Jul 2014 | A1 |
20140208281 | Ming | Jul 2014 | A1 |
20140214579 | Shen et al. | Jul 2014 | A1 |
20140222521 | Chait | Aug 2014 | A1 |
20140222793 | Sadkin et al. | Aug 2014 | A1 |
20140244284 | Smith | Aug 2014 | A1 |
20140244388 | Manouchehri et al. | Aug 2014 | A1 |
20140267294 | Ma | Sep 2014 | A1 |
20140267295 | Sharma | Sep 2014 | A1 |
20140279824 | Tamayo | Sep 2014 | A1 |
20140310266 | Greenfield | Oct 2014 | A1 |
20140316911 | Gross | Oct 2014 | A1 |
20140333651 | Cervelli et al. | Nov 2014 | A1 |
20140337772 | Cervelli et al. | Nov 2014 | A1 |
20140344230 | Krause et al. | Nov 2014 | A1 |
20140344231 | Stowe et al. | Nov 2014 | A1 |
20140358829 | Hurwitz | Dec 2014 | A1 |
20150019394 | Unser et al. | Jan 2015 | A1 |
20150026622 | Roaldson et al. | Jan 2015 | A1 |
20150046870 | Goldenberg et al. | Feb 2015 | A1 |
20150073954 | Braff | Mar 2015 | A1 |
20150089353 | Folkening | Mar 2015 | A1 |
20150089424 | Duffield et al. | Mar 2015 | A1 |
20150100897 | Sun et al. | Apr 2015 | A1 |
20150100907 | Erenrich et al. | Apr 2015 | A1 |
20150106347 | McGrew et al. | Apr 2015 | A1 |
20150106379 | Elliot et al. | Apr 2015 | A1 |
20150112956 | Chang et al. | Apr 2015 | A1 |
20150134666 | Gattiker et al. | May 2015 | A1 |
20150169709 | Kara et al. | Jun 2015 | A1 |
20150169726 | Kara et al. | Jun 2015 | A1 |
20150170077 | Kara et al. | Jun 2015 | A1 |
20150178825 | Huerta | Jun 2015 | A1 |
20150178877 | Bogomolov et al. | Jun 2015 | A1 |
20150186483 | Tappan et al. | Jul 2015 | A1 |
20150186821 | Wang et al. | Jul 2015 | A1 |
20150187036 | Wang et al. | Jul 2015 | A1 |
20150212663 | Papale | Jul 2015 | A1 |
20150227295 | Meiklejohn et al. | Aug 2015 | A1 |
20150254220 | Burr et al. | Sep 2015 | A1 |
20150261817 | Harris et al. | Sep 2015 | A1 |
20150309719 | Ma et al. | Oct 2015 | A1 |
20150317342 | Grossman et al. | Nov 2015 | A1 |
20150324868 | Kaftan et al. | Nov 2015 | A1 |
20160062555 | Ward et al. | Mar 2016 | A1 |
Number | Date | Country |
---|---|---|
2013251186 | Nov 2015 | AU |
2014206155 | Dec 2015 | AU |
102054015 | May 2014 | CN |
102014103482 | Sep 2014 | DE |
102014215621 | Feb 2015 | DE |
0 652 513 | May 1995 | EP |
1672527 | Jun 2006 | EP |
2551799 | Jan 2013 | EP |
2555126 | Feb 2013 | EP |
2560134 | Feb 2013 | EP |
2778977 | Sep 2014 | EP |
2835745 | Feb 2015 | EP |
2835770 | Feb 2015 | EP |
2838039 | Feb 2015 | EP |
2846241 | Mar 2015 | EP |
2851852 | Mar 2015 | EP |
2858014 | Apr 2015 | EP |
2858018 | Apr 2015 | EP |
2863326 | Apr 2015 | EP |
2863346 | Apr 2015 | EP |
2869211 | May 2015 | EP |
2881868 | Jun 2015 | EP |
2884439 | Jun 2015 | EP |
2884440 | Jun 2015 | EP |
2891992 | Jul 2015 | EP |
2911078 | Aug 2015 | EP |
2911100 | Aug 2015 | EP |
2940603 | Nov 2015 | EP |
2940609 | Nov 2015 | EP |
2993595 | Mar 2016 | EP |
2516155 | Jan 2015 | GB |
2518745 | Apr 2015 | GB |
2012778 | Nov 2014 | NL |
2013306 | Feb 2015 | NL |
624557 | Dec 2014 | NZ |
WO 0009529 | Feb 2000 | WO |
WO 0125906 | Apr 2001 | WO |
WO 0188750 | Nov 2001 | WO |
WO 02065353 | Aug 2002 | WO |
WO 2005104736 | Nov 2005 | WO |
WO 2007133206 | Nov 2007 | WO |
WO 2008064207 | May 2008 | WO |
WO 2009061501 | May 2009 | WO |
WO 2010000014 | Jan 2010 | WO |
WO 2010030913 | Mar 2010 | WO |
WO 2010030914 | Mar 2010 | WO |
WO 2012025915 | Mar 2012 | WO |
WO 2012119008 | Sep 2012 | WO |
WO 2013010157 | Jan 2013 | WO |
WO 2013102892 | Jul 2013 | WO |
Entry |
---|
“A First Look: Predicting Market Demand for Food Retail using a Huff Analysis,” TRF Policy Solutions, Jul. 2012, pp. 30. |
“A Quick Guide to UniProtKB Swiss-Prot & TrEMBL,” Sep. 2011, pp. 2. |
“A Word About Banks and the Laundering of Drug Money,” Aug. 18, 2012, http://www.golemxiv.co.uk/2012/08/a-word-about-banks-and-the-laundering-of-drug-money/. |
Acklen, Laura, “Absolute Beginner's Guide to Microsoft Word 2003,” Dec. 24, 2003, pp. 15-18, 34-41, 308-316. |
Amnet, “5 Great Tools for Visualizing Your Twitter Followers,” posted Aug. 4, 2010, http://www.amnetblog.com/component/content/article/115-5-grate-tools-for-visualizing-your-twitter-followers.html. |
Ananiev et al., “The New Modality API,” http://web.archive.org/web/20061211011958/http://java.sun.com/developer/technicalArticles/J2SE/Desktop/javase6/modality/ Jan. 21, 2006, pp. 8. |
Antoshenkov, Gennady, “Dictionary-Based Order-Preserving String Compression,” The VLDB Journal, 1997, vol. 6, pp. 26-39. |
“Apache HBase,” <http://hbase.apache.org/> printed Sep. 14, 2011 in 1 page. |
“BackTult—JD Edwards One World Version Control System,” printed Jul. 23, 2007 in 1 page. |
Baker et al., “Megastore: Providing Scalable, Highly Available Storage for Interactive Services,” 5th Biennial Conference on Innovative Data Systems Research (CIDR '11), Jan. 9-12, 2011, Asilomar, California, pp. 12. |
Bernstein et al., “Hyder—A Transactional Record Manager for Shared Flash,” 5th Biennial Conference on Innovative Data Systems Research (CIDR '11), Jan. 9-12, 2011, Asilomar, California, pp. 12. |
Bluttman et al., “Excel Formulas and Functions for Dummies,” 2005, Wiley Publishing, Inc., pp. 280, 284-286. |
Boyce, Jim, “Microsoft Outlook 2010 Inside Out,” Aug. 1, 2010, retrieved from the internet https://capdtron.files.wordpress.com/2013/01/outlook-2010-inside—out.pdf. |
Bugzilla@Mozilla, “Bug 18726—[feature] Long-click means of invoking contextual menus not supported,” http://bugzilla.mozilla.org/show—bug.cgi?id=18726 printed Jun. 13, 2013 in 11 pages. |
Canese et al., “Chapter 2: PubMed: The Bibliographic Database,” The NCBI Handbook, Oct. 2002, pp. 1-10. |
Celik, Tantek, “CSS Basic User Interface Module Level 3 (CSS3 UI),” Section 8 Resizing and Overflow, Jan. 17, 2012, retrieved from internet http://www.w3.org/TR/2012/WD-css3-ui-20120117/#resizing-amp-overflow retrieved on May 18, 2015. |
Chang et al., “Bigtable: A Distributed Storage System for Structured Data”, Google, Inc., OSDI'06: Seventh Symposium on Operating System Design and Implementation, Seattle, WA, Nov. 2006, pp. 14. |
Chen et al., “Bringing Order to the Web: Automatically Categorizing Search Results,” CHI 2000, Proceedings of the SIGCHI conference on Human Factors in Computing Systems, Apr. 1-6, 2000, The Hague, The Netherlands, pp. 145-152. |
Chung, Chin-Wan, “Dataplex: An Access to Heterogeneous Distributed Databases,” Communications of the ACM, Association for Computing Machinery, Inc., vol. 33, No. 1, Jan. 1, 1990, pp. 70-80. |
Conner, Nancy, “Google Apps: The Missing Manual,” May 1, 2008, pp. 15. |
Definition “Identify” downloaded Jan. 22, 2015, 1 page. |
Definition “Overlay” downloaded Jan. 22, 2015, 1 page. |
Delcher et al., “Identifying Bacterial Genes and Endosymbiont DNA with Glimmer,” BioInformatics, vol. 23, No. 6, 2007, pp. 673-679. |
Dramowicz, Ela, “Retail Trade Area Analysis Using the Huff Model,” Directions Magazine, Jul. 2, 2005 in 10 pages, http://www.directionsmag.com/articles/retail-trade-area-analysis-using-the-huff-model/123411. |
Dreyer et al., “An Object-Oriented Data Model for a Time Series Management System,” Proceedings of the 7th International Working Conference on Scientific and Statistical Database Management, Charlottesville, Virginia USA, Sep. 28-30, 1994, pp. 12. |
Elmasri et al., “Fundamentals of Database Systems,” 2004, Fourth Edition, pp. 455-491. |
GIS-NET 3 Public—Department of Regional Planning. Planning & Zoning Information for Unincorporated LA County. Retrieved Oct. 2, 2013 from http://gis.planning.lacounty.gov/GIS-NET3—Public/Viewer.html. |
Goswami, Gautam, “Quite Writly Said!,” One Brick at a Time, Aug. 21, 2005, pp. 7. |
Griffith, Daniel A., “A Generalized Huff Model,” Geographical Analysis, Apr. 1982, vol. 14, No. 2, pp. 135-144. |
Hansen et al. “Analyzing Social Media Networks with NodeXL: Insights from a Connected World”, Chapter 4, pp. 53-67 and Chapter 10, pp. 143-164, published Sep. 2010. |
Hardesty, “Privacy Challenges: Analysis: It's Surprisingly Easy to Identify Individuals from Credit-Card Metadata,” MIT News on Campus and Around the World, MIT News Office, Jan. 29, 2015, 3 pages. |
Hibbert et al., “Prediction of Shopping Behavior Using a Huff Model Within a GIS Framework,” Healthy Eating in Context, Mar. 18, 2011, pp. 16. |
Hogue et al., “Thresher: Automating the Unwrapping of Semantic Content from the World Wide Web,” 14th International Conference on World Wide Web, WWW 2005: Chiba, Japan, May 10-14, 2005, pp. 86-95. |
Huff et al., “Calibrating the Huff Model Using ArcGIS Business Analyst,” ESRI, Sep. 2008, pp. 33. |
Huff, David L., “Parameter Estimation in the Huff Model,” ESRI, ArcUser, Oct.-Dec. 2003, pp. 34-36. |
Kahan et al., “Annotea: an open RDF infrastructure for shared WEB annotations”, Computer Networks 39, pp. 589-608, 2002. |
Keylines.com, “An Introduction to KeyLines and Network Visualization,” Mar. 2014, <http://keylines.com/wp-content/uploads/2014/03/KeyLines-White-Paper.pdf> downloaded May 12, 2014 in 8 pages. |
Keylines.com, “KeyLines Datasheet,” Mar. 2014, <http://keylines.com/wp-content/uploads/2014/03/KeyLines-datasheet.pdf> downloaded May 12, 2014 in 2 pages. |
Keylines.com, “Visualizing Threats: Improved Cyber Security Through Network Visualization,” Apr. 2014, <http://keylines.com/wp-content/uploads/2014/04/Visualizing-Threats1.pdf> downloaded May 12, 2014 in 10 pages. |
Kitts, Paul, “Chapter 14: Genome Assembly and Annotation Process,” The NCBI Handbook, Oct. 2002, pp. 1-21. |
Klemmer et al., “Where Do Web Sites Come From? Capturing and Interacting with Design History,” Association for Computing Machinery, CHI 2002, Apr. 20-25, 2002, Minneapolis, MN, pp. 8. |
Kokossi et al., “D7-Dynamic Ontoloty Management System (Design),” Information Societies Technology Programme, Jan. 10, 2002, pp. 1-27. |
Li et al., “Interactive Multimodal Visual Search on Mobile Device,” IEEE Transactions on Multimedia, vol. 15, No. 3, Apr. 1, 2013, pp. 594-607. |
Liu, Tianshun, “Combining GIS and the Huff Model to Analyze Suitable Locations for a New Asian Supermarket in the Minneapolis and St. Paul, Minnesota USA,” Papers in Resource Analysis, 2012, vol. 14, pp. 8. |
Madden, Tom, “Chapter 16: The BLAST Sequence Analysis Tool,” The NCBI Handbook, Oct. 2002, pp. 1-15. |
Manno et al., “Introducing Collaboration in Single-user Applications through the Centralized Control Architecture,” 2010, pp. 10. |
Manske, “File Saving Dialogs,” <http://www.mozilla.org/editor/ui—specs/FileSaveDialogs.html>, Jan. 20, 1999, pp. 7. |
Map of San Jose, CA. Retrieved Oct. 2, 2013 from http://maps.bing.com. |
Map of San Jose, CA. Retrieved Oct. 2, 2013 from http://maps.google.com. |
Map of San Jose, CA. Retrieved Oct. 2, 2013 from http://maps.yahoo.com. |
Mentzas et al. “An Architecture for Intelligent Assistance in the Forecasting Process,” Proceedings of the Twenty-Eighth Hawaii International Conference on System Sciences, Jan. 3-6, 1995, vol. 3, pp. 167-176. |
Microsoft—Developer Network, “Getting Started with VBA in Word 2010,” Apr. 2010, <http://msdn.microsoft.com/en-us/library/ff604039%28v=office.14%29.aspx> as printed Apr. 4, 2014 in 17 pages. |
Microsoft Office—Visio, “About connecting shapes,” <http://office.microsoft.com/en-us/visio-help/about-connecting-shapes-HP085050369.aspx> printed Aug. 4, 2011 in 6 pages. |
Microsoft Office—Visio, “Add and glue connectors with the Connector tool,” <http://office.microsoft.com/en-us/visio-help/add-and-glue-connectors-with-the-connector-tool-HA010048532.aspx?CTT=1> printed Aug. 4, 2011 in 1 page. |
Miklau et al., “Securing History: Privacy and Accountability in Database Systems,” 3rd Biennial Conference on Innovative Data Systems Research (CIDR), Jan. 7-10, 2007, Asilomar, California, pp. 387-396. |
Mizrachi, Ilene, “Chapter 1: GenBank: The Nuckeotide Sequence Database,” The NCBI Handbook, Oct. 2002, pp. 1-14. |
Niepert et al., “A Dynamic Ontology for a Dynamic Reference Work”, Joint Conference on Digital Libraries, Jun. 17-22, 2007, Vancouver, British Columbia, Canada, pp. 1-10. |
Nierman, “Evaluating Structural Similarity in XML Documents,” 2002, 6 pages. |
Olanoff, Drew, “Deep Dive with the New Google Maps for Desktop with Google Earth Integration, It's More than Just a Utility,” May 15, 2013, pp. 1-6, retrieved from the internet: http://web.archive.org/web/20130515230641/http://techcrunch.com/2013/05/15/deep-dive-with-the-new-google-maps-for-desktop-with-google-earth-integration-its-more-than-just-a-utility/. |
Palmas et al., “An Edge-Bunding Layout for Interactive Parallel Coordinates” 2014 IEEE Pacific Visualization Symposium, pp. 57-64. |
Peng et al., “Large-scale Incremental Processing Using Distributed Transactions and Notifications” Proceedings of the 9th USENIX Symposium on Operating Systems Design and Implementation, USENIX, 2010, pp. 14. |
“Potential Money Laundering Warning Signs,” snapshot taken 2003, https://web.archive.org/web/20030816090055/http:/finsolinc.com/ANTI-MONEY%20LAUNDERING%20TRAINING%20GUIDES.pdf. |
“Refresh CSS Ellipsis When Resizing Container—Stack Overflow,” Jul. 31, 2013, retrieved from internet http://stackoverflow.com/questions/17964681/refresh-css-ellipsis-when-resizing-container, retrieved on May 18, 2015. |
Rouse, Margaret, “OLAP Cube,” <http://searchdatamanagement.techtarget.com/definition/OLAP-cube>, Apr. 28, 2012, pp. 16. |
Sigrist, et al., “PROSITE, a Protein Domain Database for Functional Characterization and Annotation,” Nucleic Acids Research, 2010, vol. 38, pp. D161-D166. |
Sirotkin et al., “Chapter 13: The Processing of Biological Sequence Data at NCBI,” The NCBI Handbook, Oct. 2002, pp. 1-11. |
“The Apache Cassandra Project,” <http://cassandra.apache.org/> printed Sep. 14, 2011 in 3 pages. |
“The FASTA Program Package,” fasta-36.3.4, Mar. 25, 2011, pp. 29. |
Thomson et al., “The Case for Determinism in Database Systems,” The 36th International Conference on Very Large Data Bases, Sep. 13-17, 2010, Singapore, Proceedings of the VLDB Endowment, vol. 3, No. 1, pp. 11. |
Thompson, Mick, “Getting Started with GEO,” Getting Started with GEO, Jul. 26, 2011. |
Umagandhi et al., “Search Query Recommendations Using Hybrid User Profile with Query Logs,” International Journal of Computer Applications, vol. 80, No. 10, Oct. 1, 2013, pp. 7-18. |
Wikipedia, “Federated Database System,” Sep. 7, 2013, retrieved from the internet on Jan. 27, 2015 http://en.wikipedia.org/w/index.php?title=Federated—database—system&oldid=571954221. |
Wollrath et al., “A Distributed Object Model for the Java System,” Conference on Object-Oriented Technologies and Systems, Jun. 17-21, 1996, pp. 219-231. |
Yang et al., “HTML Page Analysis Based on Visual Cues,” 2001, pp. 859-864. |
Notice of Allowance for U.S. Appl. No. 13/826,228 dated Mar. 27, 2015. |
Notice of Allowance for U.S. Appl. No. 14/102,394 dated Aug. 25, 2014. |
Notice of Allowance for U.S. Appl. No. 14/108,187 dated Aug. 29, 2014. |
Notice of Allowance for U.S. Appl. No. 14/135,289 dated Oct. 14, 2014. |
Notice of Allowance for U.S. Appl. No. 14/192,767 dated Dec. 16, 2014. |
Notice of Allowance for U.S. Appl. No. 14/225,084 dated May 4, 2015. |
Notice of Allowance for U.S. Appl. No. 14/268,964 dated Dec. 3, 2014. |
Notice of Allowance for U.S. Appl. No. 14/294,098 dated Dec. 29, 2014. |
Notice of Allowance for U.S. Appl. No. 14/451,221 dated Aug. 4, 2015. |
Notice of Allowance for U.S. Appl. No. 14/473,552 dated Jul. 24, 2015. |
Notice of Allowance for U.S. Appl. No. 14/473,860 dated Jan. 5, 2015. |
Notice of Allowance for U.S. Appl. No. 14/486,991 dated May 1, 2015. |
Notice of Allowance for U.S. Appl. No. 14/504,103 dated May 18, 2015. |
Notice of Allowance for U.S. Appl. No. 14/616,080 dated Apr. 2, 2015. |
Official Communication for Australian Patent Application No. 2014201511 dated Feb. 27, 2015. |
Official Communication for Australian Patent Application No. 2014202442 dated Mar. 19, 2015. |
Official Communication for Australian Patent Application No. 2014210604 dated Jun. 5, 2015. |
Official Communication for Australian Patent Application No. 2014210614 dated Jun. 5, 2015. |
Official Communication for Australian Patent Application No. 2014213553 dated May 7, 2015. |
Official Communication for Australian Patent Application No. 2014250678 dated Jun. 17, 2015. |
Official Communication for European Patent Application No. 14158861.6 dated Jun. 16, 2014. |
Official Communication for European Patent Application No. 14159464.8 dated Jul. 31, 2014. |
Official Communication for European Patent Application No. 14180142.3 dated Feb. 6, 2015. |
Official Communication for European Patent Application No. 14180281.9 dated Jan. 26, 2015. |
Official Communication for European Patent Application No. 14180321.3 dated Apr. 17, 2015. |
Official Communication for European Patent Application No. 14180432.8 dated Jun. 23, 2015. |
Official Communication for European Patent Application No. 14186225.0 dated Feb. 13, 2015. |
Official Communication for European Patent Application No. 14187739.9 dated Jul. 6, 2015. |
Official Communication for European Patent Application No. 14187996.5 dated Feb. 12, 2015. |
Official Communication for European Patent Application No. 14189344.6 dated Feb. 20, 2015. |
Official Communication for European Patent Application No. 14189347.9 dated Mar. 4, 2015. |
Official Communication for European Patent Application No. 14189802.3 dated May 11, 2015. |
Official Communication for European Patent Application No. 14191540.5 dated May 27, 2015. |
Official Communication for European Patent Application No. 14197879.1 dated Apr. 28, 2015. |
Official Communication for European Patent Application No. 14197895.7 dated Apr. 28, 2015. |
Official Communication for European Patent Application No. 14199182.8 dated Mar. 13, 2015. |
Official Communication for Great Britain Patent Application No. 1404457.2 dated Aug. 14, 2014. |
Official Communication for Great Britain Patent Application No. 1404574.4 dated Dec. 18, 2014. |
Official Communication for Great Britain Patent Application No. 1408025.3 dated Nov. 6, 2014. |
Official Communication for Great Britain Patent Application No. 1411984.6 dated Dec. 22, 2014. |
Official Communication for Great Britain Patent Application No. 1413935.6 dated Jan. 27, 2015. |
Official Communication for Netherlands Patent Application No. 2013306 dated Apr. 24, 2015. |
Official Communication for New Zealand Patent Application No. 622513 dated Apr. 3, 2014. |
Official Communication for New Zealand Patent Application No. 622517 dated Apr. 3, 2014. |
Official Communication for New Zealand Patent Application No. 624557 dated May 14, 2014. |
Official Communication for New Zealand Patent Application No. 627962 dated Aug. 5, 2014. |
Official Communication for New Zealand Patent Application No. 628161 dated Aug. 25, 2014. |
Official Communication for New Zealand Patent Application No. 628263 dated Aug. 12, 2014. |
Official Communication for New Zealand Patent Application No. 628495 dated Aug. 19, 2014. |
Official Communication for New Zealand Patent Application No. 628585 dated Aug. 26, 2014. |
Official Communication for New Zealand Patent Application No. 628840 dated Aug. 28, 2014. |
Official Communication for U.S. Appl. No. 12/556,318 dated Jul. 2, 2015. |
Official Communication for U.S. Appl. No. 13/247,987 dated Apr. 2, 2015. |
Official Communication for U.S. Appl. No. 13/831,791 dated Mar. 4, 2015. |
Official Communication for U.S. Appl. No. 13/831,791 dated Aug. 6, 2015. |
Official Communication for U.S. Appl. No. 13/835,688 dated Jun. 17, 2015. |
Official Communication for U.S. Appl. No. 13/839,026 dated Aug. 4, 2015. |
Official Communication for U.S. Appl. No. 14/148,568 dated Oct. 22, 2014. |
Official Communication for U.S. Appl. No. 14/148,568 dated Mar. 26, 2015. |
Official Communication for U.S. Appl. No. 14/196,814 dated May 5, 2015. |
Official Communication for U.S. Appl. No. 14/225,006 dated Sep. 10, 2014. |
Official Communication for U.S. Appl. No. 14/225,006 dated Sep. 2, 2015. |
Official Communication for U.S. Appl. No. 14/225,006 dated Feb. 27, 2015. |
Official Communication for U.S. Appl. No. 14/225,084 dated Sep. 2, 2014. |
Official Communication for U.S. Appl. No. 14/225,084 dated Feb. 20, 2015. |
Official Communication for U.S. Appl. No. 14/225,160 dated Feb. 11, 2015. |
Official Communication for U.S. Appl. No. 14/225,160 dated Aug. 12, 2015. |
Official Communication for U.S. Appl. No. 14/225,160 dated May 20, 2015. |
Official Communication for U.S. Appl. No. 14/225,160 dated Oct. 22, 2014. |
Official Communication for U.S. Appl. No. 14/225,160 dated Jul. 29, 2014. |
Official Communication for U.S. Appl. No. 14/268,964 dated Sep. 3, 2014. |
Official Communication for U.S. Appl. No. 14/278,963 dated Jan. 30, 2015. |
Official Communication for U.S. Appl. No. 14/289,596 dated Jul. 18, 2014. |
Official Communication for U.S. Appl. No. 14/289,596 dated Jan. 26, 2015. |
Official Communication for U.S. Appl. No. 14/289,596 dated Apr. 30, 2015. |
Official Communication for U.S. Appl. No. 14/289,599 dated Jul. 22, 2014. |
Official Communication for U.S. Appl. No. 14/289,599 dated May 29, 2015. |
Official Communication for U.S. Appl. No. 14/294,098 dated Aug. 15, 2014. |
Official Communication for U.S. Appl. No. 14/294,098 dated Nov. 6, 2014. |
Official Communication for U.S. Appl. No. 14/306,138 dated Feb. 18, 2015. |
Official Communication for U.S. Appl. No. 14/306,138 dated Sep. 23, 2014. |
Official Communication for U.S. Appl. No. 14/306,138 dated May 26, 2015. |
Official Communication for U.S. Appl. No. 14/306,147 dated Feb. 19, 2015. |
Official Communication for U.S. Appl. No. 14/306,147 dated Aug. 7, 2015. |
Official Communication for U.S. Appl. No. 14/306,147 dated Sep. 9, 2014. |
Official Communication for U.S. Appl. No. 14/306,154 dated Mar. 11, 2015. |
Official Communication for U.S. Appl. No. 14/306,154 dated May 15, 2015. |
Official Communication for U.S. Appl. No. 14/306,154 dated Jul. 6, 2015. |
Official Communication for U.S. Appl. No. 14/306,154 dated Sep. 9, 2014. |
Official Communication for U.S. Appl. No. 14/319,765 dated Jun. 16, 2015. |
Official Communication for U.S. Appl. No. 14/319,765 dated Nov. 25, 2014. |
Official Communication for U.S. Appl. No. 14/319,765 dated Feb. 4, 2015. |
Official Communication for U.S. Appl. No. 14/323,935 dated Jun. 22, 2015. |
Official Communication for U.S. Appl. No. 14/323,935 dated Nov. 28, 2014. |
Official Communication for U.S. Appl. No. 14/323,935 dated Mar. 31, 2015. |
Official Communication for U.S. Appl. No. 14/326,738 dated Dec. 2, 2014. |
Official Communication for U.S. Appl. No. 14/326,738 dated Jul. 31, 2015. |
Official Communication for U.S. Appl. No. 14/326,738 dated Mar. 31, 2015. |
Official Communication for U.S. Appl. No. 14/451,221 dated Apr. 6, 2015. |
Official Communication for U.S. Appl. No. 14/473,552 dated Feb. 24, 2015. |
Official Communication for U.S. Appl. No. 14/486,991 dated Mar. 10, 2015. |
Official Communication for U.S. Appl. No. 14/504,103 dated Mar. 31, 2015. |
Official Communication for U.S. Appl. No. 14/504,103 dated Feb. 5, 2015. |
Official Communication for U.S. Appl. No. 14/579,752 dated Aug. 19, 2015. |
Official Communication for U.S. Appl. No. 14/579,752 dated May 26, 2015. |
Official Communication for U.S. Appl. No. 14/580,218 dated Jun. 26, 2015. |
Official Communication for U.S. Appl. No. 14/631,633 dated Sep. 10, 2015. |
Official Communication for U.S. Appl. No. 14/639,606 dated May 18, 2015. |
Official Communication for U.S. Appl. No. 14/639,606 dated Jul. 24, 2015. |
Official Communication for U.S. Appl. No. 14/734,772 dated Jul. 24, 2015. |
About 80 Minutes, “Palantir in a Number of Parts—Part 6—Graph,” Mar. 21, 2013, pp. 1-6. |
Alur et al., “Chapter 2: IBM InfoSphere DataStage Stages,” IBM InfoSphere DataStage Data Flow and Job Design, Jul. 1, 2008, pp. 35-137. |
Gesher, Ari, “Palantir Screenshots in the Wild: Swing Sightings,” The Palantir Blog, Sep. 11, 2007, pp. 1-12. |
Huang et al., “Systematic and Integrative Analysis of Large Gene Lists Using DAVID Bioinformatics Resources,” Nature Protocols, 4.1, 2008, 44-57. |
“Money Laundering Risks and E-Gaming: A European Overview and Assessment,” 2009, http://www.cf.ac.uk/socsi/resources/Levi—Final—Money—Laundering—Risks—egaming.pdf. |
Nolan et al., “MCARTA: A Malicious Code Automated Run-Time Analysis Framework,” Homeland Security, 2012 IEEE Conference on Technologies for, Nov. 13, 2012, pp. 13-17. |
Palantir Technologies, “Palantir Labs—Timeline,” Oct. 1, 2010, retrieved from the internet https://www.youtube.com/watch?v=JCgDW5bru9M. |
Perdisci et al., “Behavioral Clustering of HTTP-Based Malware and Signature Generation Using Malicious Network Traces,” USENIX, Mar. 18, 2010, pp. 1-14. |
Shi et al., “A Scalable Implementation of Malware Detection Based on Network Connection Behaviors,” 2013 International Conference on Cyber-Enabled Distributed Computing and Knowledge Discovery, IEEE, Oct. 10, 2013, pp. 59-66. |
Symantec Corporation, “E-Security Begins with Sound Security Policies,” Announcement Symantec, Jun. 14, 2001. |
“Using Whois Based Geolocation and Google Maps API for Support Cybercrime Investigations,” http://wseas.us/e-library/conferences/2013/Dubrovnik/TELECIRC/TELECIRC-32.pdf. |
Wright et al., “Palantir Technologies VAST 2010 Challenge Text Records—Investigations into Arms Dealing,” Oct. 29, 2010, pp. 1-10. |
Notice of Acceptance for Australian Patent Application No. 2014250678 dated Oct. 7, 2015. |
Notice of Allowance for U.S. Appl. No. 12/556,318 dated Nov. 2, 2015. |
Notice of Allowance for U.S. Appl. No. 14/148,568 dated Aug. 26, 2015. |
Notice of Allowance for U.S. Appl. No. 14/326,738 dated Nov. 18, 2015. |
Notice of Allowance for U.S. Appl. No. 14/676,621 dated Feb. 10, 2016. |
Official Communication for European Patent Application No. 14197938.5 dated Apr. 28, 2015. |
Official Communication for European Patent Application No. 15155845.9 dated Oct. 6, 2015. |
Official Communication for European Patent Application No. 15155846.7 dated Jul. 8, 2015. |
Official Communication for European Patent Application No. 15165244.3 dated Aug. 27, 2015. |
Official Communication for European Patent Application No. 15175106.2 dated Nov. 5, 2015. |
Official Communication for European Patent Application No. 15175151.8 dated Nov. 25, 2015. |
Official Communication for European Patent Application No. 15188106.7 dated Feb. 3, 2016. |
Official Communication for European Patent Application No. 15190307.7 dated Feb. 19, 2016. |
Official Communication for Netherlands Patent Application No. 2012437 dated Sep. 18, 2015. |
Official Communication for U.S. Appl. No. 12/556,321 dated Feb. 25, 2016. |
Official Communication for U.S. Appl. No. 13/247,987 dated Sep. 22, 2015. |
Official Communication for U.S. Appl. No. 14/134,558 dated Oct. 7, 2015. |
Official Communication for U.S. Appl. No. 14/225,084 dated Sep. 11, 2015. |
Official Communication for U.S. Appl. No. 14/289,599 dated Sep. 4, 2015. |
Official Communication for U.S. Appl. No. 14/306,138 dated Sep. 14, 2015. |
Official Communication for U.S. Appl. No. 14/306,138 dated Dec. 3, 2015. |
Official Communication for U.S. Appl. No. 14/306,154 dated Nov. 16, 2015. |
Official Communication for U.S. Appl. No. 14/319,765 dated Sep. 10, 2015. |
Official Communication for U.S. Appl. No. 14/490,612 dated Aug. 18, 2015. |
Official Communication for U.S. Appl. No. 14/639,606 dated Oct. 16, 2015. |
Official Communication for U.S. Appl. No. 14/715,834 dated Feb. 19, 2016. |
Official Communication for U.S. Appl. No. 14/726,353 dated Sep. 10, 2015. |
Official Communication for U.S. Appl. No. 14/741,256 dated Feb. 9, 2016. |
Official Communication for U.S. Appl. No. 14/813,749 dated Sep. 28, 2015. |
Official Communication for U.S. Appl. No. 14/841,338 dated Feb. 18, 2016. |
Official Communication for U.S. Appl. No. 14/871,465 dated Apr. 11, 2016. |
Official Communication for U.S. Appl. No. 14/871,465 dated Feb. 9, 2016. |
Official Communication for U.S. Appl. No. 14/883,498 dated Mar. 17, 2016. |
Official Communication for U.S. Appl. No. 14/883,498 dated Dec. 24, 2015. |
Official Communication for U.S. Appl. No. 14/961,481 dated Mar. 2, 2016. |
Restriction Requirement for U.S. Appl. No. 13/839,026 dated Apr. 2, 2015. |
Abbey, Kristen, “Review of Google Docs,” May 1, 2007, pp. 2. |
Adams et al., “Worklets: A Service-Oriented Implementation of Dynamic Flexibility in Workflows,” R. Meersman, Z. Tari et al. (Eds.): OTM 2006, LNCS, 4275, pp. 291-308, 2006. |
Chaudhuri et al., “An Overview of Business Intelligence Technology,” Communications of the ACM, Aug. 2011, vol. 54, No. 8. |
Devanbu et al., “Authentic Third-party Data Publication,” 2000, pp. 19, http://www.cs.ucdavis.edu/˜devanbu/authdbpub.pdf. |
Galliford, Miles, “SnagIt Versus Free Screen Capture Software: Critical Tools for Website Owners,” http://www.subhub.com/articles/free-screen-capture-software, Mar. 27, 2008, pp. 11. |
“GrabUp—What a Timesaver!” http://atlchris.com/191/grabup/, Aug. 11, 2008, pp. 3. |
Gu et al., “Record Linkage: Current Practice and Future Directions,” Jan. 15, 2004, pp. 32. |
Hua et al., “A Multi-attribute Data Structure with Parallel Bloom Filters for Network Services” HiPC 2006, LNCS 4297, pp. 277-288, 2006. |
JetScreenshot.com, “Share Screenshots via Internet in Seconds,” http://web.archive.org/web/20130807164204/http://www.jetscreenshot.com/, Aug. 7, 2013, pp. 1. |
Kwout, http://web.archive.org/web/20080905132448/http://www.kwout.com/ Sep. 5, 2008, pp. 2. |
Microsoft, “Registering an Application to a URI Scheme,” http://msdn.microsoft.com/en-us/library/aa767914.aspx, printed Apr. 4, 2009 in 4 pages. |
Microsoft, “Using the Clipboard,” http://msdn.microsoft.com/en-us/library/ms649016.aspx, printed Jun. 8, 2009 in 20 pages. |
Microsoft Windows, “Microsoft Windows Version 2002 Print Out 2,” 2002, pp. 1-6. |
Nitro, “Trick: How to Capture a Screenshot as PDF, Annotate, Then Share It,” http://blog.nitropdf.com/2008/03/04/trick-how-to-capture-a-screenshot-as-pdf-annotate-it-then-share/, Mar. 4, 2008, pp. 2. |
Online Tech Tips, “Clip2Net—Share files, folders and screenshots easily,” http://www.online-tech-tips.com/free-software-downloads/share-files-folders-screenshots/, Apr. 2, 2008, pp. 5. |
O'Reilly.com, http://oreilly.com/digitalmedia/2006/01/01/mac-os-x-screenshot-secrets.html published Jan. 1, 2006 in 10 pages. |
Quest, “Toad for ORACLE 11.6—Guide to Using Toad,” Sep. 24, 2012, pp. 1-162. |
Schroder, Stan, “15 Ways to Create Website Screenshots,” http://mashable.com/2007/08/24/web-screenshots/, Aug. 24, 2007, pp. 2. |
SnagIt, “SnagIt Online Help Guide,” http://download.techsmith.com/snagit/docs/onlinehelp/enu/snagit—help.pdf, TechSmith Corp., Version 8.1, printed Feb. 7, 2007, pp. 284. |
SnagIt, “SnagIt 8.1.0 Print Out,” Software release date Jun. 15, 2006, pp. 6. |
SnagIt, “SnagIt 8.1.0 Print Out 2,” Software release date Jun. 15, 2006, pp. 1-3. |
Wang et al., “Research on a Clustering Data De-Duplication Mechanism Based on Bloom Filter,” IEEE 2010, 5 pages. |
Warren, Christina, “TUAW Faceoff: Screenshot apps on the firing line,” http://www.tuaw.com/2008/05/05/tuaw-faceoff-screenshot-apps-on-the-firing-line/, May 5, 2008, pp. 11. |
Notice of Acceptance for Australian Patent Application No. 2013251186 dated Nov. 6, 2015. |
Notice of Allowance for U.S. Appl. No. 14/265,637 dated Feb. 13, 2015. |
Notice of Allowance for U.S. Appl. No. 14/278,963 dated Sep. 2, 2015. |
Notice of Allowance for U.S. Appl. No. 14/552,336 dated Nov. 3, 2015. |
Official Communication for Australian Patent Application No. 2013251186 dated Mar. 12, 2015. |
Official Communication for Canadian Patent Application No. 2831660 dated Jun. 9, 2015. |
Official Communication for European Patent Application No. 12181585.6 dated Sep. 4, 2015. |
Official Communication for European Patent Application No. 15183721.8 dated Nov. 23, 2015. |
Official Communication for Great Britain Patent Application No. 1404486.1 dated Aug. 27, 2014. |
Official Communication for Great Britain Patent Application No. 1404489.5 dated Aug. 27, 2014. |
Official Communication for Great Britain Patent Application No. 1404499.4 dated Aug. 20, 2014. |
Official Communication for Netherlands Patent Application No. 2011729 dated Aug. 13, 2015. |
Official Communication for Netherlands Patent Application No. 2012436 dated Nov. 6, 2015. |
Official Communication for Netherlands Patent Application No. 2012438 dated Sep. 21, 2015. |
Official Communication for New Zealand Patent Application No. 622473 dated Jun. 19, 2014. |
Official Communication for New Zealand Patent Application No. 622473 dated Mar. 27, 2014. |
Official Communication for U.S. Appl. No. 12/556,321 dated Jul. 7, 2015. |
Official Communication for U.S. Appl. No. 13/196,788 dated Oct. 23, 2015. |
Official Communication for U.S. Appl. No. 13/196,788 dated Nov. 25, 2015. |
Official Communication for U.S. Appl. No. 13/669,274 dated Aug. 26, 2015. |
Official Communication for U.S. Appl. No. 13/669,274 dated May 6, 2015. |
Official Communication for U.S. Appl. No. 13/827,491 dated Jun. 22, 2015. |
Official Communication for U.S. Appl. No. 13/827,491 dated Oct. 9, 2015. |
Official Communication for U.S. Appl. No. 14/222,364 dated Dec. 9, 2015. |
Official Communication for U.S. Appl. No. 14/552,336 dated Jul. 20, 2015. |
Official Communication for U.S. Appl. No. 14/571,098 dated Nov. 10, 2015. |
Official Communication for U.S. Appl. No. 14/571,098 dated Mar. 11, 2015. |
Official Communication for U.S. Appl. No. 14/571,098 dated Aug. 24, 2015. |
Official Communication for U.S. Appl. No. 14/571,098 dated Aug. 5, 2015. |
Official Communication for U.S. Appl. No. 14/578,389 dated Oct. 21, 2015. |
Official Communication for U.S. Appl. No. 14/734,772 dated Oct. 30, 2015. |
Official Communication for U.S. Appl. No. 14/746,671 dated Nov. 12, 2015. |
Official Communication for U.S. Appl. No. 14/746,671 dated Sep. 28, 2015. |
Official Communication for U.S. Appl. No. 14/800,447 dated Dec. 10, 2015. |
Official Communication for U.S. Appl. No. 14/842,734 dated Nov. 19, 2015. |
Number | Date | Country | |
---|---|---|---|
20160062555 A1 | Mar 2016 | US |
Number | Date | Country | |
---|---|---|---|
62045488 | Sep 2014 | US | |
62135448 | Mar 2015 | US |