Archive

Archive for the ‘Software’ Category

Google Patents website versions

May 22, 2017 Comments off

In a previous post about expedited single-patent analysis I discuss how much I enjoy the layout format of the version of Google Patents available at the URL syntax of https://www.google.com/patents/patent_identifier. I continue to use this site for reviewing patents in my daily work.

There is also a newer version of Google Patents available at the URL syntax of https://patents.google.com/patent/patent_identifier. This newer version of Google Patents has a variety of improvements over the previous version, such as detailed search capability, patent expiration information, and claim text search term highlighting. The image viewer is also different, though not necessarily better, depending upon the circumstances (as detailed below).

That said, for several reasons I find myself continuing to prefer the previous version of Google Patents, which as of this writing is still available. These reasons include issues with the newer version, which were communicated to the Google Patents development team in 2016, albeit to no reply as of this writing:

  1. Unnecessary Search Column: It would be helpful to be able to collapse the left-most column containing the search fields. Often, when one is reviewing a particular patent, there’s no desire to perform more searches. I admit that I sometimes work from a Chromebook with an 11-inch display, so having that left column go away would provide more precious real estate for the specification content, or possibly allow for images to be shown on the right side.
  2. Small Images Viewer: For the drawings/images/figures, they are presented in a very small area when using a smaller display device, especially when centered with the rest of the content. I often cannot sufficiently see them and therefore must open them in a new window. While it’s often helpful to be able to see the images while still viewing the rest of the content, it would be beneficial to be able to open the set of drawings in a superimposed pop-up like is done for the legacy Google Patents — in this way a new window/tab is not needed, and one can scroll through all the figures quickly, all while being able to sufficiently see them.
  3. Less-Accessible Metadata: It would be better to include the “Also Published As” information in the top metadata box instead of linking to a full list at the bottom of the page. The preexisting Google Patents solution has a collapsed list of related patents, and this would be the preferable solution for ease and speed of use. Or even a hover or pop-up box with the information would be helpful. Searchers and analysts very often need to see what family members there are, particularly US family members, and so having to go all the way to the bottom of the page to see this very important metadata is counter-intuitive and slow.
  4. Much Slower Page Load Time: Beyond viewing the information, the speed of loading of a single newer Google Patents page is now painfully slow, especially as compared to the loading of the earlier version. And the newer pages will not completely load until after a browser tab/window is put into focus, as opposed to the legacy version which loads without being in focus. The newer pages have a title of “Result” on the browser tab until viewed.

One issue that arose in 2016 was that on the legacy Google Patents, newer patents’ images were not being shown because the associated image links were broken. Perhaps this is intentional so as to encourage users to the newer Google Patents, or perhaps it’s because the legacy version is no longer being actively supported (or both). In any case, because I prefer the legacy version, I created a Chrome browser extension called “Google Patents Images” which on the fly modifies the image links for legacy Google Patents to use the image links for the newer Google Patents. The extension should work automatically for any legacy Google Patents page after the initial installation of the extension (as long as JavaScript is enabled).

The first issued US patent with broken figure images is 8,856,962 — all patents before that patent work OK. The first broken US pre-grant publication is 2014/0304877, while the first broken US design patent is D715016.

Replacing the images allows for viewing the images, but the controls to go to the previous/next images are still broken — these are controlled in the page’s JavaScript, which cannot be manipulated by a Chrome extension.

Google Patents Images Chrome extension

Google Patents Images Chrome extension

Categories: Analysis, Resources, Software Tags: ,

More Patent Analysis Tools

November 7, 2014 Comments off

The patent claims tree Chrome browser extension I created in 2012 provides a patent claims tree for a given patent document, and it has become fairly popular, with several hundred users as of this writing. The tool is available at the Chrome Web Store, and is described in more detail here and here.

I have created additional Chrome browser extensions that I have found helpful and that you can use during patent analysis. One provides USPTO patent assignments for any selected text, such as a selected company name. This solution allows you to quickly look up any US patent assignments for a given company name in the USPTO patent assignment database.

UPDATED (May 22, 2017): The other links from a selected patent or patent application identifier on any webpage to the corresponding Google Patents page.

The “Patent Assignments” tool is available at the Chrome Web Store, as is the “Open Google Patents” tool.

Screenshots for each extension are provided below. I hope that you find these applications helpful in your patent analysis.

Patent Assignments - screenshot

Patent Assignments Chrome browser extension

 

Open Google Patents Chrome extension

Open Google Patents Chrome extension

 

Categories: Analysis, Resources, Software Tags: ,

Patent Claims Tree tool updates

May 2, 2014 Comments off

The patent claims tree Chrome browser extension I created in 2012  provides a patent claims tree for a given patent document, and it has become fairly popular, with several hundred users as of this writing. The tool is available at the Chrome Web Store, and is described in more detail here.

I have recently made a couple of improvements to the tool for EP and WO (PCT/WIPO) patent document handling. For one, claim tree creation is now supported for both EP and WO patent documents on Google Patents. Additionally, rudimentary support for German and French for EP patent documents in Google Patents has been added. While the claim type is not handled for German and French, claim tree creation is now provided. Additionally, it should be noted that Google Patents provides kind code B (i.e., issued patent) claims text for EP patents (while Espacenet does not as of this writing — the kind code B issued claims are only available in a PDF file). See this other PatentAnalyst blog post regarding consideration of kind codes for EP patent documents.

The screenshot below shows a claims tree for an issued EP patent viewed in Google Patents. Noteworthy is that not all formats of multiple dependent claims are fully handled in the Patent Claims Tree tool. These types of claims are more common in EP patent documents than in US patent documents.

Google Patents EP claim tree

 

Categories: Analysis, Resources, Software Tags: ,

Capturing and analyzing encrypted HTTPS communications

September 11, 2013 Comments off

More and more web applications typically encrypt communications with a user browser using Transport Layer Security (TLS), making determination of how the web application works more difficult. However, as part of patent analysis it can be quite helpful to peek into client-server communications to better ascertain how functionality works.

Packet capture tools such as Wireshark capture all Ethernet communications at a network adapter, and so cannot see inside encrypted packets like TLS packets used for securely transferring data via Hypertext Transfer Protocol Secure (HTTPS). TLS encrypts packets using symmetric cryptography between communication counterparts, so that unless you’re the NSA it should be challenging to be a “man-in-the-middle” and read the communications in the clear. For this reason, what is needed is insight at a counterpart endpoint, and in the client case for a web application this is the web browser. The web browser itself obviously must be able to encrypt and decrypt communications with a web application server, so it is here that one can capture and analyze HTTPS packets in plaintext format.

There are a variety of browser-specific add-ons that are available to capture and present sent and received HTTPS communications in plaintext format. One example that I have found helpful is HttpFox, an extension for Mozilla-based browsers such as the Firefox browser. HttpWatch is another solution that works for Firefox and on iOS devices (iPhone, iPad) as its own browser.

HttpFox Firefox browser add-on

HttpFox Firefox browser add-on

Below is a screen shot of HttpFox in action — it has captured several HTTPS communications with a website, including a highlighted GET method to obtain some JavaScript:

HttpFox HTTPS Capture

HttpFox HTTPS Capture

It should be noted that while browser extensions such as HttpFox are helpful for capturing and analyzing secure encrypted communications with browsers, these are not helpful for decrypting communications to/from other client applications because these other applications are TLS counterpart endpoints that are using cryptography without providing insight into the communications.

 

Categories: Analysis, Software Tags: , ,

How to Review all Independent Claims in 15 Minutes or Less

July 14, 2013 Comments off

I am very often asked to review and comment on patents in 15 minutes or even less. In those cases I normally am not requested to provide too much detail due to lack of time, but of course clients still want relevant feedback about each patent. Clients will typically indicate what aspects they want detailed, but in any case there really is one overarching question — that is, “How likely is use of this patent?” To arrive at an answer (such as an estimated probability), an analyst must first ascertain what the key elements and limitations are, and should do so not only for claim 1 or the shortest independent claim, but for all independent claims. From that assessment, the analyst can then focus on one independent claim for providing comments, though sometimes it’s best to indicate differences in claim scope that could impact assessments.

When I tell other analysts that one really should review all independent claims, even in a 15-minute review, often the response is that I’m crazy. And perhaps I am, and in fact it wasn’t that long ago that I said that 15 minutes wasn’t long enough to analyze all independent claims in a patent. But it bothered me because of all the times that I saw that the most relevant claim was not actually claim 1 (supposedly the “representative” claim) or even the shortest claim. So what could be improved to allow for a fuller review in just 15 minutes, or even less? Disclaimer: this technique will not work for outliers like this exceptional patent application, which has 7,215 claims: http://www.google.com/patents/US20030100451!

The answer for me, which I wish to share with you, is the use of software tools — for now my favorite combination is Google Patents (in a particular format) and my free Patent Claims Tree Google Chrome extension. Google Patents has been around for years, but for a while I found that many patents were missing, and I preferred the presentation and layout of FreePatentsOnline.  But over time Google Patents improved, and eventually they modified their layout such that I can hardly envision a better format for efficient review of a patent. This format may continue to evolve over time, and perhaps it will even get better, but it certainly is already great — as of this writing, Google Patents has multiple layouts, but the one I particularly like is the format provided for webpages with the following syntax: http://www.google.com/patents/US<patent_number>. Take a look, for example, at: http://www.google.com/patents/US7654321. The title, abstract, and relevant metadata are all presented at the very top of the page in a compact and easily-readable view.

Top-level

Just below that is a set of all images, which can be quickly expanded and perused, and sideways images can be easily rotated. All images can be visually scanned in less time that it takes to open the patent’s PDF file!

Image example

Then perhaps most elegantly, the patent background and the claims are provided in side-by-side columns. The claims are indeed the most important components of a patent because they define a patent’s scope of rights to exclusion, but claims are often worded in manner that can be difficult to comprehend at first glance. Therefore, a quick review of the background section sets the stage for inventive embodiments and helps to scope the claims for a reader. And now this is where the Patent Claims Tree tool for the Chrome browser comes in — with sufficient resolution/zoom, your Chrome browser can simultaneously present the background, claims, and a claims tree with relevant claims metrics, all side-by-side (basically a three-column display):

Three-column display

I find this presentation to be incredibly helpful and fast. The speed at which patent claims can be reviewed using this presentation is key since time is so limited.

With an appropriate input device such as a mouse with a scroll wheel, it is possible to scroll through the claims in Google Patents while the claims tree remains open. Additionally, note all the helpful information presented at a glance in the claims tree: the number of independent claims, which claims are the independent claims, the shortest independent claim, the relative word counts of the independent claims, the type of claim for each independent claim, the relative amount of dependent claims for each independent claim, and which claims use means-plus-function language. Sure, it’s possible to figure all of that out manually, but just that alone would probably take more than 15 minutes by itself.

Those metrics help in determining which independent claim should receive the bulk of your attention. In the example above (I like to use 7,654,321 because it’s a nice number :)), one can quickly determine that in this case there are six independent claims covering a variety of types of coverage, though the “downhole tool” of claim 21 is by far the shortest claim (by about 60 words), so review should probably start there. After reading that claim, if the claim seems to have sufficient coverage, then probably only cursory reviews of the other independent claims are necessary. There are other possible considerations that can be made at a glance as well — e.g., perhaps the client has indicated that it has a threshold for claim word count, so some claims can be discounted rapidly. Or, maybe only claims with a certain type of coverage are desired, and so the claim type can be used to focus on specific claims. In any case, using the three-column presentation, it is normally quite feasible with most patents to have time to read and understand all independent claims, and therefore pick out the best. If you want to find, for example, all method/process claims, this information is there in the tree. Should supplemental background information be needed, it’s right there. Should a figure or two be helpful for understanding scope, it’s simple and speedy to pop them up without a PDF. Should the priority date need consideration, it’s right there above the images.

This approach works quite well for me, and I bet that it will for you too. I am now quite confident in performing 15-minute patent reviews for most technology areas with which I am familiar. There are exceptions of course, but the techniques and software described above have greatly expedited my reviews, making 15 minutes much more comfortable than they used to feel.

If you have additional efficiency tips, please share them in the comments.

Claims tree

Wireless packet capture and analysis

July 3, 2013 Comments off

Fairly often when performing patent analysis, particularly when creating claim charts mapping one or more patented claims against a target product or service, I find it helpful to capture and analyze packets sent from a wireless device. Internet Protocol (IP) packet capture when using a personal computer, such as a Windows or Mac computer, is relatively straightforward using a packet capture tool. I have been using Wireshark (formerly Ethereal) for years as my preferred packet capture tool, although there are certainly other available options from which to choose, both paid and free.

Packet capture for packets sent to and from other wireless devices such as smartphones and tablets is not so straightforward, therefore I provide below details of a solution that I leverage so that you can take advantage of this approach as well during your patent analysis. The high-level summary of this solution is to set up a Windows OS computer to use Wireshark to capture packets on a virtual Wi-Fi adapter — see this Microsoft explanation of the solution, termed VirtualWiFi, which I can confirm works for me with Windows 7. Credit goes to Eric Geier for documenting how to set up virtual W-Fi adapters here.

Steps:

1. In a command prompt (“cmd”), enter the following to set up your hosted network connection: netsh wlan set hostednetwork mode=allow ssid=YourVirtualNetworkName key=YourNetworkPassword  — You can set up your SSID (YourVirtualNetworkName) and password (YourNetworkPassword) as you wish, though of course you’ll need to know these when you try to connect from your wireless device that you’re testing.

Packet capture - step 1

2. Before enabling the virtual hosted network, configure the physical network adapter to share its Internet access using the Internet Connection Sharing (ICS) feature of Windows. To enable ICS, open the Network Connections window, then right-click the network adapter that is actually connected to the Internet and select Properties. Then select the Sharing tab, check the “Allow other network users to connect through this computer’s Internet connection” checkbox, choose the hosted network connection (that you enabled in step #1) from the drop-down listbox, and click OK.

Packet capture - step 2a Packet capture - step 2b

3. In the command prompt, enter the following to start your hosted network connection: netsh wlan start hostednetwork

Packet capture - step 3

4. Open Wireshark and select Capture->Interfaces, and select the adapter for your physical network connection and click Start. You can confirm that you have the correct adapter through comparison of MAC addresses, though the easiest solution is probably just to watch the packet count of adapters when using the target wireless device — the adapter with corresponding increases in packet count is the one to use.

Packet capture - step 4

5. Connect to the new hosted Wi-Fi network with the target wireless device and execute the desired application, website, service, etc. on the target device being tested and step through whatever sequence for which you wish to analyze the corresponding packets.

6. Once done with testing and recording, select Capture->Interfaces->Stop in Wireshark to stop packet capture.

7. You will then have a set of packets to analyze, and you’ll need to determine the IP address of the wireless device being tested. There are many different considerations here as far as best approaches to walk through the packet data, such as filtering, stream following, searching, exporting, etc., so I suggest that you reference the documentation that Wireshark provides here.

8. Disable the hosted network through entering the following command in the command prompt: netsh wlan stop hostednetwork

If at any time during the steps above you wish to see the current status of the hosted network, such as the MAC addresses of connected devices, enter the following command in the command prompt: netsh wlan show hostednetwork

Packet capture - show network

Once you have performed steps 1-2 above, on system reset the hosted network will not automatically start up, so you would need to execute this command again: netsh wlan start hostednetwork. In fact, once steps 1-2 have been performed once, from then on you should not have to perform them again for subsequent testing — you can start at step 3.

I hope you enjoy your wireless packet capturing and analysis!

Google search tools for patent searching and analysis

April 1, 2013 1 comment

When performing patent-related searches and/or analyses, I often leverage Google search tools to facilitate my work. A few examples are provided below, and I welcome others’ insight into other helpful search utilities. I should note that I sometimes also use Microsoft’s Bing search application, particularly because I earn Bing Rewards, but Google does have some specific patent-related utilities that Bing and other publicly-available and free search applications lack.

Google Images

When analyzing a patent and searching for either utilization or related art for inventive embodiments that include aspects that can be seen, such as mechanical designs or computer user interfaces, Google’s Images search results often are handy. A picture truly can be worth a thousand words, if not more. For example, I recently filed a patent application for an invention that my wife and I created for a unique drinking vessel. As part of my patentability assessment, I used Google Images to search for existing beer stein designs that might already disclose what we believed likely to be novel. So I searched using Google with the phrase “beer stein” (among many others of course), then I selected the “Images” link in the results — an example screen shot is shown below (from google.com).

Google Images

Google Images

Date Range

Additionally, when performing patent searches, normally there is a date range of interest. For example, for validity or patentability searches, a priority date is used to limit resulting references to those that precede the priority date of relevance. Google provides for date range selection in various different places, such as through selection of a “Search tools” button in a results banner. From there, a searcher may select a date or time range such as “Past hour”, “Past 24 hours”, “Past week”, etc. Normally the choice of interest is “Custom range…” (highlighted in the screen shot below from google.com). So for example, for a priority date of February 3, 2003, the “From” date field may be left blank, and “2/3/2003” may be entered for the “To” date field. This causes Google to only display results for references published before February 3, 2003.

Google Date/Time Range

Google Date/Time Range

Google Custom Date Range
Google Custom Date Range

Site

When searching for potential patent claim utilization, clients often request specific target companies’ products. In those cases, the strongest references are those provided by a target company itself. Therefore, limiting search results to those provided by the target company is often helpful, and this can be done through use of a additional “site:” parameter. For example, to limit search results to those from “ACME Company, Inc.”, whose main domain is “acmeinc.com”, enter normal search terms plus additionally include “site:acmeinc.com”.

Advanced Search

Google also provides several other parameters that a searcher can use to limit results — these can be found in “Advanced Search” (https://www.google.com/advanced_search). The Advanced Search can also be accessed through selection of the gear icon on a normal search results page. Results can be further limited, for example, through specifying explicit search term combinations, words to exclude, languages, etc. Screen shots are sourced from https://google.com and https://www.google.com/advanced_search:

Google Settings

Google Settings

Google Advanced Search

Google Advanced Search

Prior Art Finder

And of course let’s not forget Google’s Prior Art Finder. For a given patent, Google will extract key terms and search for various types of references using those search terms where the references were published before the patent’s priority date. Additionally, a user can modify, remove, and add search terms and/or change the search’s date range. A key advantage of Google searches is that common synonyms for each search term are also used in the searches, and Google will sometimes leverage synonyms that a searcher may not have envisioned when creating a search plan. References can be sourced from scholarly references, other patent documents, books, the Web, people, or the top 10 from these groups. The example Prior Art Finder screen shot below is for US patent 6368227 for a method of swinging on a swing (https://www.google.com/patents/related/US6368227):

Google Prior Art Finder

Google Prior Art Finder

Categories: Analysis, Search, Software Tags: ,