Patent mapping

Information

  • Patent Grant
  • 11301810
  • Patent Number
    11,301,810
  • Date Filed
    Monday, December 30, 2019
    4 years ago
  • Date Issued
    Tuesday, April 12, 2022
    2 years ago
  • CPC
  • Field of Search
    • US
    • 707 741000
    • CPC
    • G06Q10/10
    • G06F16/3331
  • International Classifications
    • G06F16/00
    • G06Q10/10
    • G06F16/33
    • Disclaimer
      This patent is subject to a terminal disclaimer.
Abstract
System and method permit patent mapping. A method may comprise maintaining a database of patent portfolios and a database of patents with each patent stored in the database of patents associated with one or more patent portfolios stored in the database of patent portfolios. A search query may be received associated with a first patent portfolio and the first portfolio may be searched as a function of the search query. Search results may be generate which include one or more patent claims associated with the search query. The one or more patent claims may be mapped to a patent concept.
Description
BACKGROUND

Tools for identifying patents for a particular purpose such as a prior art search, validity analysis, or a freedom to operate investigation, operate by performing Boolean queries using various search operators. These operators allow for searching by date, terms, document number, and patent classification, among others. These tools further allow for searching individual document portions such as a document title, abstract, or claim set.


Other searching tools accept freeform text. Such tools accept a freeform text block and extract information from the text block deemed most likely to return acceptable results. However, such tools are still limited to only performing Boolean queries and displaying a list of results.


These search tools often provide large numbers of results, most of which are irrelevant. These tools fail to present results in a manner allowing for quick relevancy determinations. The presentation also fails to provide enough detail suggesting how to adjust a search for obtaining only relevant results. Further, the search tools provide the documents of the result set in a manner very similar to the traditional paper format of the documents.





BRIEF DESCRIPTION OF THE DRAWINGS

Some example embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:



FIG. 1 is a diagram of a system, according to an example embodiment.



FIG. 2 is a block diagram of a server device, according to an example embodiment.



FIGS. 3-8 are data model diagrams, according to example embodiments.



FIGS. 9-15 are user interfaces, according to example embodiments.



FIGS. 16-22 are example generated charts, according to example embodiments.



FIG. 23 is a computer system, according to an example embodiment.





DETAILED DESCRIPTION

The following detailed description of the present subject matter refers to the accompanying drawings which show, by way of illustration, specific aspects and embodiments in which the present subject matter may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the present subject matter. Other embodiments may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the present subject matter. References to “an”, “one”, or “various” embodiments in this disclosure are not necessarily to the same embodiment, and such references contemplate more than one embodiment. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope is defined, only by the appended claims, along with the full scope of legal equivalents to which such claims are entitled.


The subject matter herein provides systems, software, methods, and data structures for patent mapping, ranking and rating of patents, searching, and generating visual representations of the patents and patent portfolios to quickly analyze the patents for many reasons including, but not limited to, claim coverage and value. In an example embodiment, a patent portfolio may comprise one or more patents that may or may not be commonly owned or related. The collection of patent portfolios and patents may be stored in one or more databases. A patent may belong to more than one portfolio at the same time. In an example embodiment, the underlying patents and patent claims included in each patent portfolio may be categorized by patent concepts (sometimes referred herein as concepts) such as scope concepts (SC) and technology categories (TC).


In an example embodiment, technology categories are categories that claims relate to, but are not necessarily limited to. For example, a claim to a pulse generator may be put in the technology category “pacemaker”, but not be limited, to a pacemaker per se—perhaps the claim merely says that the pulse generator generates a pulse of certain type that is useful for pacing, but pacing does not appear in the claim. Hence, the claim relates to the technology category “pacemaker,” but it is not limited to being a pacemaker.


In an example embodiment, scope concepts are concepts that a claim is limited to. This is contrast to technology categories, where the claim may be mapped to a TC but it not necessarily limited to it. A scope concept may defined in a way to give the concept a context that a user can understand without necessarily having to look at the corresponding claim language. For example, if the scope concept is “method or apparatus for cardiac rhythm management”, and it is mapped to claim A, then claim A by definition is limited to this application, such that if a target device does not perform cardiac rhythm management, then it would not infringe claim A.


In an example embodiment, there are two types of scope concepts: 1) high level scope concepts that are like technical categories in the sense they are broad and general and apply to many claims in a portfolio; and 2) scope concepts that are specific to a limited number of claims—for example all claims in a patent may be limited to a very specific distinguishing feature, and this feature could be the basis for a scope concept.


In some example embodiments, high level scope concepts may be defined prior to mapping, and then assigned as applicable. For example, several scope concepts like: atrial pacing, ventricular pacing, defibrillation method or device, etc, may be defined. Then a mapping team may go through all claims in a portfolio and map these scope concepts to claims that are limited to these concepts. After the mapping is complete, an analysis may be done showing how many claims in the portfolio are limited to each of these scope concepts, and the claims may be presented for each SC. This may be useful is disqualify claims that are not of interest to a particular target (e.g., if an analysis is being done to find a claim that covers an alleged infringer). In some example embodiments, specific scope concepts are mapped patent by patent or by patent family. These may enable a person to create one or two scope concepts that can be mapped across all claims in given patent, a family of patents, or across a portion of a patent portfolio. In order to effectively formulate a scope concept that may be globally useful across a patent portfolio, it may be useful to be able to examine multiple patent claims at the same time even if they are not all in the same patent or patent family.



FIG. 1 illustrates an example system to implement the methods described herein. Shown is a user 102 and a user device 104. The user device 104 may be, for example, a personal computer, mobile phone, or personal digital assistant. The user device 104 may be a computer system as described in FIG. 17. Users of the system may include specialized personnel trained to map patent claims as well as personnel trained to analyze the resulting claim map. The user device 102 may communicate with a server device 106 over a network 108 (e.g., the Internet) using a variety of communication means including, but not limited to, wired and wireless communication. The server device 106 may be a computer system as described in FIG. 17. In an example embodiment, the user 102 requests patent claims 110 from the server device 106 and transmits concept mappings 112 back to the server device 106 through the user device 104 via the network 108. In various embodiments, one or more software applications are executed on the user device which facilitate the interactions and data transmissions between user 102, user device 104, and server device 106. Other information needed to complete the methods described herein may be transmitted between the user device 102 and server device 106 according to example embodiments.



FIG. 2 illustrates an example server device 200. In an example embodiment, the server device includes one or more modules, databases, and engines. The various modules, databases, and engines may interact with each other and may take on the functionality of other modules, databases, and engines. Databases, according to an example embodiment, generally refer to sets of data stored in tables and may be implemented using a variety of database solutions including Oracle and MySQL. Engines, according to an example embodiment, generally refer to the generation of a product/image that is presented to a user (e.g., a webpage). Modules, according to an example embodiment, generally refer to functionality or features of the system that a user may invoke. For example, the mapping module may provide the necessary logic to create a mapping between a concept and a patent claim. According to an example embodiment, server device 200 includes an account database 202, a mining module 204, visualization engine 206, a web server engine 208, a ranking module 210, a patent database 212, a valuation module 214, a tracking module 216, a concept database 218, a patent claim database 220, a patent set database 222, a flapping module 224, and an ontology database 226.


In various embodiments, the modules, engines, and databases are implemented in a combination of software and hardware. For example, a mapping module can be stored as set of instructions stored on a machine-readable medium. The instructions can be executed on a processor and cause a machine to perform operations related to mapping. Additionally, the visual presentation of data in not limited to engines and may be done by modules as well. Similarly, engines may contain underlying logic dictating on how each engine functions and interacts with the user, software, and hardware of the system. In various embodiments, the modules, engines, and databases are combined.


In an example embodiment, the account database 202 includes data pertaining to the different users of the system. In some embodiments, different levels of user are defined. For example, an administrator level allows the creation of an ontology (e.g., a collection of patent concepts and keywords) and mapping of patent claims while an analysis level user may only mine the map for patent claims. The web server engine 208 may present webpages to the user via the user device. The webpages may include forms and user interfaces for the user to interact with such that the user may manipulate the underlying data stored on the server device on one or more databases.


In an example embodiment, databases 212, 218, 220, 222, and 226 store the underlying data that the server device interacts with and modifies according to user input. The patent database 212 may include information related to all the patents stored in the system such as title, filing data, assignee, etc. The concept database 218 may store all the concepts that have been defined either by the user or automatically by the system. The patent claim database 220 may include information related to patent claims including which patent they belong to as well as concepts that have been mapped to the patent claims. The patent set database 222 may store information on sets of patents that have been defined by the user. In an example embodiment, a patent set may be defined by exclusion mining (e.g., the set of patents that have NOT been mapped to a certain concept). The ontology database 226 may store information on a user defined set of concepts.


The mapping module 224, in an example embodiment, enables a user to map a concept to a patent claim. For example, the user may create and define a patent concept which is then stored in the concept database. The user may then send an indication, through the user device, that a patent claim in the patent claim database 220 should be mapped to the new concept. The indication may take the form of a type of user input such as clicking on an interface using an input device. The server device may then store this mapping in the patent claim database. For example, a relationship between the patent claim and concept may be stored in one or more of the databases.


The mining module 204, in an example embodiment, allows a user to search through the data stored in the databases to find patent claims of interest. For example, a user may wish to find all the patent claims related to a gear used in a bicycle. Rather than having the user define what the gear is, the user may indicate to the mining module what the gear is not, by indicating what concepts do not apply (exclusion mining). The mining module may search the entire universe of claims in the patent claim database, or a portion of the patent claim database, and retrieve the remaining patent claims (those claims that not have the concept) and present them to the user.


The visualization engine, in an example embodiment, generates reports and visual depictions of the data contained in a set of claims. For example, the visualization engine may generate a spreadsheet with the concepts in the concept database as rows and the patent claims as the columns. Color coding may be used to signify where a patent claim has been mapped to a concept. In some example embodiments, a user of the system may add additional data that influences the spreadsheet created. Some example embodiments include the generation of competitor landscape, freedom to operate, product coverage, validity, valuation, white space analysis, and white space claim generation spreadsheets. In various embodiments, other forms of coding are used such as shading and patterning.


The tracking module 216, according to an example embodiment, maintains information related to a specific patent, group of patents, or concept. For example, the tracking module may store information related to a patent's prosecution and litigation history such as office actions or claim amendments. Alerts (e.g., electronic mail) may be sent to a user indicating a change in a patent or patent application.


The ranking module 210 and valuation module 214, according to example embodiments, enable the user to provide additional information related to patents, patent claims, and concepts that may be used to determine a course of action such as abandoning a patent or pursing research in a specific field. For example, a user may indicate a specific concept as being key to her business. Further, a lawyer or other trained patent professional may provide a ranking for each patent included in her portfolio related to scope, design around protection, and detectability effort. The system may take this knowledge and through the visualization engine generate a chart that shows the highest ranked patents that also include her important concept.


Data Models


In an example embodiment, data models are defined to store the information related to the patents being analyzed. FIGS. 3-8 illustrate example data models that may be utilized. These may be defined in any suitable programming language such as C, C++, Java, Ruby, etc, that allows the manipulation of data models. In some embodiments, data models are referred to as classes and both terms will be used in the following descriptions. Further, an object may refer to a specific instance of a class or data model. As one skilled in the art will recognize, there may be more than one way to define the models and the relationships between the models. The illustrated models are to be taken only as one way of implementing the systems and methods described in this application, FIGS. 3-8, in some example embodiments, provide the lower level details of the information stored in databases 212, 218, 220, 222 and 226.



FIG. 3, according to an example embodiment, illustrates data models related generally to mappable data. Shown are models and relationships for a Patent 302, Mappable Data 304, Patent Specification 306, Global Patent Ranking 308, Mapping 310, claim 312, Concept 314, Concept Type 316, Patent Inclusion 318, Patent Relation 320, Ontology Relationships 322, Ontology 324, Mapping Status 326, and Ontology Concept 328. Each model may contain one or more elements that are defined either by the system or a user. Further, as illustrated, some models are related to each in other in a one to many relationship. For example, an Ontology object 324 may be related to many Ontology Concept objects 328.


In an example embodiment, Patent model 302 includes types of information related to a patent including, but not limited to, whether or not it is an application, the number of claims, when it was filed, what organization it may belong to, the serial number, and its status. As can be seen, each piece of information may have an associated class such as a Boolean or string. In some cases, the type is actually another class (e.g, global ranking has a class of Global Ranking). Further shown are the elements of a data model that relate to another data model. For example, example Mapping Status 326, Patent Relation 320, Patent Inclusion 318, and claim 312 models all include an element of patent with a class of Patent. This relationship allows the system to examine a Claim class and determine the Patent in which the Claim is included.


In some embodiments, the Mapping 310 data model defines persistent objects that define the relationships between the a concept (e.g., technology categories and scope concept), a claim, and an ontology. As shown, there are many elements that a Mapping 320 class may include, such as, but not limited to, citations, notes, ontology, concept type and claim. Further, in an example embodiment, many Mapping objects may be related to one Ontology object and one Claim object. Thus, if one were to examine a Mapping object, there would be a relationship defining the ontology to which the object belongs to as well as the claim to which it has been assigned. In addition, there may be an integer signifying the type of concept to which the Mapping object belongs. As data model Concept Type 316 suggests each type of concept may be enumerated as well as be defined by an integer value. For example, the concept of scope concept may be given the value of ‘1.’ Also, the “object” element illustrated has an associated class of Concept 314. Accordingly, the Mapping object may be linked to an example concept that has been defined as “two wheeled transportation.” The mapping operation element may define the relationship between the cited claim and the concept. For example, a concept may be directly mapped to a claim. Other possibilities are discussed further with reference to FIG. 10. Accordingly, a Mapping object may contain the following information with regards to some of the displayed elements.


claim: Claim A


conceptType: 1


object: Two wheeled transportation


ontology: Bikes


mapping operation: Directly Mapped


In an example embodiment, a Mapping object is created each time the system receives an indication a concept is to be mapped to a claim. In an embodiment, an indication may be stored that a concept is not mapped to a claim.


In an example embodiment, a Concept 314 object is created for every user defined concept as well as any concept the system may define automatically. Each Concept 314 may contain, but is not limited to elements of, conceptType, description, hidden, intelliMapAllowed, keywordLabel, name, organization, and underReview. As discussed above, a Concept 314 object may contain an enumeration of the ConceptType 316 object. For example, the conceptType element may have an example value of “scope concept.” The description element may describe when a concept should be applied to a claim or other helpful information relating to the concept. The intelliMapAllowed Boolean may indicate whether the system may automatically apply the concept to other claims included in the system. For example, a concept type might be “keyword.” These keywords may be verbatim phrases or individual words in the claim. Thus, a user may be able to safely have the system search other claims and find the same keyword and automatically create Mapping 310 objects for the keyword and found claims. The intelliMapAllowed may indicate whether the system should search automatically for these keywords.


In an example embodiment, the OntologyConcept 328 class only contains two elements, ontology and concept. An Ontology Concept 328 may be created to signify the relationship between a Concept 314 object and an Ontology 324 object. As shown, an Ontology 324 object may include many OntologyConcept objects. Also, as shown, a Concept 314 object may belong to many OntologyConcept 328 objects.


Also shown in FIG. 3, is the PatentInclusion 318 object. A PatentInclusion Object may include elements of inclusionType, patent, patentSet, ranking, reviewed, and ruleType. A PatentInclusion 318 object may be used to signify the relationship between a patent and a patentSet. This relationship is more fully explained with reference to FIG. 4.



FIG. 4, according to an example embodiment, illustrates data models related, generally, to mining mapped data. Shown are models and relationships for PatentOpinion 402, IncludedClaim 404, ScheduledIntelliMap 406, PatentSet 408, ConceptExclusion 410, PortfolioDomain 412, PatentSearch 414, PatentInclusion 416, LocalPatentRanking 418, TextInclusion 420, ConceptInclusion 422, and Concept 424 classes. In some embodiments, classes with the same name as in FIG. 3 are defined similarly. For example, Concept class 424 may contain the same elements as Concept class 314. However, as illustrated, additional functions are included that may operate on the class. For example, function “createCopy( )” is illustrated in Concept class 424.


In an example embodiment, the PatentSet 408 class operates as the central class for milling. As illustrated, many of the other classes shown relate to the PatentSet 408 class. A PatentSet object may have many Pateranclusion 416, ConceptExclusion 410, and IncludedClaim 404 objects. Also, in an example embodiment, a PatentSet object may have many ConceptinInclusion 422 objects related to it by virtue of the PatentSearch 414 class. Through user interfaces presented to a user and user input, a Patent Set may be defined. This may be done by a user adding claims manually or by a more sophisticated method involving a user defining which concepts to exclude or include. The various data models support an almost endless amount of customization for users of the system in the creation of patent sets.


In an example embodiment, the created patent sets may be saved for future use, as well as themselves becoming the basis for creating a new patent set. This may enable a user to efficiently search through any number of patents. The system may operate in such a manner that when a request is made to retrieve patents included in a patent set, the system responds by applying the relationships defined by the objects for that patent set. For example, the ConceptExclusion objects. This execution method may allow newly mapped patents to be included or excluded from the patent set with no additional input from a user. Thus, if a user wishes to find the intersection between a patent set related to vehicles and a patent set related to audio, the most current mapped patents available will be presented. As will be discussed in greater detail with respect to portfolio mapping, the ability to create patent sets and combine them may greatly speed up the process of finding common concepts across patents.



FIG. 5, according to an example embodiment, illustrates data models related, generally, to annuity data. Shown are models and relationships for Patent 502, ClaimMappedUser 504, AnnuityInformation 506, PatentRanking 508, ScoringCriteria 510, and Scorer objects 512. In an example embodiment to further enable a person to quickly analyze a large group of patent claims, patents may be given a rating. In an example embodiment, only the broadest independent claim in each patent is given a ranking, as the broadest claim will often have the most value. The patent claims may be ranked according to multiple criteria, including, but not limited to scope, detectability, and the ability to design around the patent. In an example embodiment, the ranking information may be stored in a PatentRanking object and retrieved through the Scorer interface. Each criteria may be given a weighting depending on the client's needs. For example, a client may decide that scope is twice as important as the other two criteria. Therefore, the formula to rank the patents may be:

0.5(scope)+0.25(detectability)+0.25(design around)=rating.

Once all of the patents have been ranked, the results may be presented to the user in a web browser, in the form of a chart or using any other suitable display mechanism.


An AnnuityInformation object may include information related to annuities for an issued patent. Depending on the rating and annuity information of a patent, a user may automatically let patents go abandoned, a user may be alerted, or an annuity may automatically be paid. Other example embodiments will be obvious to one skilled in the art.



FIG. 6, according to an example embodiment, illustrates data models related generally to patent tracking. FIG. 7, according to an example embodiment, illustrates data models related generally to products and features. FIG. 8, according to an example embodiment, illustrates data models related generally to technology hierarchies.


Portfolio Mapping



FIG. 9 illustrates an example user interface that may be utilized to facilitate the methods described to map patent claims, according to an example embodiment. Displayed is the title 902 of a patent portfolio, controls are also illustrated that allow a user to edit to the portfolio, list the patents in the portfolio, “quick rank,” and generate a panoramic claim map. Also shown is the “Default Ontology” 904 being used. In an example embodiment, “Quick Rank” allows a user to map all the patent claims in a patent to concepts at the same time. An ontology, in an example embodiment, includes the different concepts available to a user to map to one or more of the patent claims. Further, there is an example search criteria box 906 which allows a user to specify a search query. Included are options to narrow the search by type of claim 908 including searching independent claims, dependent claims, or both. The search expression box 910 may allow a user to specify a regular expression to use as a search query. There is also an option to have keywords highlighted 912 in the search results. In an example embodiment, this may include the searched for keywords or keywords that have previously been mapped to the claims. Also shown are options to narrow the search results by technology categories 914 and scope concepts 916.



FIG. 10 illustrates a method to map concepts to patent claims according to an example embodiment. A user interface such as the one illustrated in FIG. 9 may be used to facilitate this example method. Further, in an example embodiment, the method may be implemented using the data models and server device described above (e.g., server device 106 with reference to FIG. 1). At block 1002, a database of patent portfolios and a database of patents are maintained, each patent stored in the database of patents associated with one or more patent portfolios stored in the database of patent portfolios. A database management system may be used (DBMS) for storing and retrieving data from a data store which includes the database of patents and database of patent portfolios. In some embodiments, the DBMS is a relational database management system (RDBMS). In some other embodiments, the data store includes storing data in a Resource Description Framework Schema (RDFS). In some embodiments, communication with the data store includes using a language such as Structured Query Language (SQL) or eXtensible Markup Language (XML).


In an example embodiment, a database of ontologies may also be maintained, the ontologies including one or more patent concepts. As discussed above, an ontology may include all the metadata (patent concepts) that one may wish to map to a patent claim. For instance, the one or more patent concepts may include a technology category. The one or more patent claims may also include a scope concept, the scope concept defining a scope to which a patent claim is limited. Keywords may also be used as patent concepts. These may be any term or short phrase that appears in the claim, exactly as it appears in the claim. As these terms are taken from the claims, they may be thought of as limitations in the sense that if the term cannot be read on an accused device, the claim probably does not cover the accused device. Example user interfaces showing scope concepts in an ontology can be seen with reference to FIG. 11.


In an example embodiment, at block 1004, a search query associated with a first patent portfolio is retrieved. A user of the system may wish to search a previously created portfolio of patents. A patent portfolio may include patents that a user wishes to analyze. For example, a portfolio might include all of the patents for a company ABC Corp (ABC). A portfolio may be stored and defined as a patent set in the patent set database (e.g., patent set database 222 in FIG. 2) ABC might have received information on a potential infringing product. In order to find the patent claims relevant to the product, ABC may wish to map its entire patent portfolio and use the resulting mapped portfolio to quickly find the best claims to assert in an infringement lawsuit. However, it may also be useful to map the patents of the alleged infringer. These patents may also be added to the portfolio as it is likely ABC's patents and the alleged infringer's patents will have overlapping subject matter.


The search query may help to narrow down the patent. In an example embodiment, the search query many include a regular expression. For example, if the search query is “*” all the patent claims in the patent portfolio will be displayed. Boolean expressions such as “car && dog” may also be used. In some example embodiments, an option is included to only search independent claims, dependent claims, or to search both. In some example embodiments, the portfolio may further be narrowed by using patent concepts that have been included in the current ontology.



FIG. 12 shows an example user interface with example options available to search by technology category. An example option is presented allowing a user to search technology categories disjunctively or conjunctively. In an example embodiment, each technology category in the ontology is shown to the user with three example options “Direct mapped claims,” “Direct Mapped or ‘Does Not Map,’” and “Direct Mapped or ‘Unresolved.’” These terms will be discussed in greater detail with respect to block 1010.



FIG. 13 shows an example user interface with example options available to search by scope concept. In an example embodiment, each scope concept in the ontology is shown to the user with four example options “Direct mapped claims,” “Do not include Direct Mapped or ‘Does Not Map,’” “Direct Mapped or ‘Does Not Map,’” and “Direct Mapped and ‘Unresolved.’” These terms will be discussed in greater detail with respect to block 1010.


Referring back to FIG. 10, in an example embodiment at block 1006, the first portfolio is searched as a function of the search query. At block 1008, in an example embodiment, search results 918 are generated, the search results including one or more patent claims associated with the search query. Using the search query provided, a query may be formatted as an SQL query or other suitable format to query the underlying databases. Generating the search results may include retrieving patent claims which include terms from the search query and synonyms of the terms as well as plural versions of terms in the search query. The results of the query may then be presented to the user in an example user interface as shown in FIG. 9. Only one patent claim is illustrated, however, more patent claims may have resulted from the search and may be shown simultaneous as to have the ability to manipulate multiple patent claims. Column headings may include four radio buttons 920 signifying the options available for mapping, the matter number, the claim number, the claim text, and other technology categories or scope concepts currently mapped to the claim. Because the generated search results are searching an entire portfolio of patents it may be possible that not all of the claims of a given patent will match to the search query. A trio of numbers 922 may also be displayed for each claim in relationship to the technology category heading and the scope concept heading. These represent the nature of the relationship between the claim and the technology category or scope concept. For example, as illustrated, claim 1 has two technology categories directly mapped: “space vehicle” and “Electric Device or Method.” It also has one scope concept directly mapped.


Referring back to FIG. 10, at block 1010, in an example embodiment, a plurality of patent claims are mapped to a patent concept. In an example embodiment, in addition to the database of patents and patent portfolios, a database of patent claims may be maintained. The database of patent claims may be administered and interacted with using a DBMS as described above. As described more fully with reference to FIG. 3, each patent claim may have one or more patent concepts that have been mapped to the claim. As discussed above with reference to narrowing down search results, the relationship between a patent concept and a patent claim may take on many forms. For example, the relationship may be one where the patent concept is directly mapped to a patent claim. This may indicate that a user who looked at the claim made the decision that the patent claim was in a particular technology category, for example. Another relationship may indicate that a patent concept is not mapped to a patent claim. If a user is sure that a particular claim is not in a technology category, for example, it may be beneficial for that information to be saved so that the mapping process is not unnecessarily duplicative.


With reference back to FIG. 9, a user may select one or more patent claims to map based on the radio buttons displayed. In an example embodiment, there are four radio buttons indicating options for the claim: “Direct Mapped,” “Does Not Map,” “Unresolved,” and “No Operation.” The first two options are described in detail above. The “Unresolved” radio button may indicate that a user is not sure whether the concept should be mapped to the patent claim. This may be helpful in cases where the user does not have the legal or technical expertise to make a decision one way or another. A more senior user may then review the unresolved patent claims en masse at a later time. The last radio button may indicate that a user does not wish to have any relationship defined between the patent claim and a patent concept. In an example embodiment the “No Operation” radio button is selected by default for all the patent claims returned from the search query.


Upon a user indicating a preferred mapping for each patent claim, a user may further indicate a preference of which category of patent concept to map. In an example embodiment, there are two categories: technology categories and scope concepts (e.g., elements 924 & 926 in FIG. 9). In an example embodiment, a user clicks on the button corresponding to their preference and this preference is sent to the service device which detects the category of concept the user clicked. In response, a user interface is presented to the user corresponding to his or her preference. For example, FIG. 14, may be presented.



FIG. 14 illustrates an example search box 1402 and an example search results 1404 section. Across the top is an option to add a new patent concept 1406 (see FIG. 15 for a more detailed look at an example method to add a patent concept). Other options may include returning to the main mapping screen (e.g. FIG. 9) or canceling the mapping. In an example embodiment, the search box allows a user to search across an entire ontology for potential patent concepts. Similar to searching for patent claims, a user may enter a regular expression such as ‘*’ to retrieve all the concepts included in the present ontology. For example, the results of the search 1404 displayed in FIG. 14 only returns “multiple blades.” A checkbox is presented allowing a user to select the concept 1408. If there is more than one concept displayed a user may select more than one of the concepts by selecting the respective checkboxes next to the patent concepts. A checkbox at the top of the results may be selected if a user wishes to select all 1410 of the concepts returned from the ontology search.


Further example options may be presented to the right of each concept. An option to “modify and map” 1412 may be selected if the user wishes to modify the concept. This may be useful if a user wishes to broaden the concept so that it may be mapped to more patent claims. For example, a narrow technology category may have been defined as “power computer speakers.” Rather than a user defining a new technology category of “passive computer speakers,” the user might decide it makes more logical sense to only have one technology category titled “computer speakers.” In an example embodiment, the user can safely select “modify and map” and change the technology category to “computer speakers.” This may safely be done because all “powered computer speakers” are also “computer speakers.” In an example embodiment, every patent claim, regardless of which portfolio(s) it may be included in, will be updated to reflect the modified concept. Thus, it may not be advisable to narrow a concept without being certain every patent claim in the system adheres to the modified concept. In an example embodiment, a warning may be displayed to the user explaining the effects of modifying a concept.


In an example embodiment, an indication of a relationship between the patent concept and the plurality of claims in the database of patents may be stored (e.g., updating one or more databases). This may be accomplished, for example, by the user selecting the map button as displayed in FIG. 14. As discussed above, a user may have selected multiple patent claims resulting from searching and may have further indicated a preference for one or more patents claims to have concepts directly mapped as well as indicated a preference to have one or more patent claims have patent concepts not mapped. Thus, in an example embodiment, the indication of the relationship may include an indication that the plurality of patent claims are not mapped to the patent concept. In an example embodiment, the indication of the relationship includes an indication that the plurality of patent claims are mapped to the patent concept.


It some example embodiments mapping a plurality of patent claims to a patent concept includes defining the patent concept. Defining the patent concept may be initiated by a user clicking on the example “add_new” button 1406 as displayed in FIG. 14. An example user interface that may be presented to the user in response to this selection is illustrated in FIG. 15. Two example options may be presented, “Save” and “Cancel.” Also shows are two input text boxes, “Concept Name” and “Description.” The concept name may be the actual concept and may be, for example, either a technology category or a scope concept. A user may indicate which category of patent concept the new concept belongs using a pull down menu. The user may further wish to add the concept to an existing ontology by selecting one or more ontologies as presented in FIG. 15.


Report and Chart Generation


As described, the system may allow the generation of visual representation of the data included in the databases to further maximize the value of concepts to patent claims. In some example embodiments the charts may be interactive. In some example embodiments, a method to generate the charts includes formulating a query to send to one or more databases, the query requesting whether or not a set of patent claims have been mapped to a set of patent concepts. An additional query may be sent to the databases to determine additional metadata about the patent claims including, but not limited to, the filing data and owner of each patent. Ranking data may be received for each patent concept retrieved from the databases. In an example embodiment, the system generates a relationship between a ranking, a patent concept, and a patent claim and displays the relationship to the user in the form of a chart. The ranking data may be stored in the database or may be received from a user. In some embodiments, ranking data may include integer values of disparate range (e.g., 1-10 or 1-100) alphabetical letters (e.g., a grading scale of A-F), or any other means to characterize a claim or concept.


In an example embodiment, a competitor landscape chart may be generated. An example simple competitor landscape chart is shown in FIG. 16. Shown is the title, patent number, filing data, total claims, each independent claim, and owner of each patent in a patent set. The patent set may reflect the patents owned by the competitors of a company requesting the map. The scope concepts that have been mapped to the patent claims in the patent set may be displayed as rows in the chart. If a scope concept has been mapped to a patent claim than the intersecting cell between the patent claim and concept may be filled in, checked, change color, patterned, shaded or otherwise have an indication of the mapping. Additional columns may indicate the competitor that first introduced, a concept as well as the date it was introduced. This may be determined by examining each patent that has a concept mapped to at least one of the claims and examining the dates of each of the matching patents. In addition, the scope concepts may be sorted by frequency. Each competitor may be assigned a color or other designation such that a user may quickly determine which company owns each patent as well as who introduced what concepts first.


In an example embodiment, a product coverage chart may be generated. An example product coverage chart is shown in FIG. 17. As with FIG. 16, relevant patent information for patents included in the patent set is displayed. Also, displayed is a column titled “Has Feature?” This column may have values ranging from one to three signifying the degree to which the product includes the concept. For example, a value of three may mean the product definitely includes the concept and a value of one means the product definitely does not relate to the concept. Based on these values, the chart may dynamically update and determine values for the claim coverage and product coverage rows. For example, SC 1 and SC 5 both have a rating of ‘3’ and are present in all of the claims of patent “Title 1.” Thus, “Title 1” has a claim coverage of ‘3’ and a product coverage value of “potentially applies.” It is only “potentially applies” because it cannot be known for certain whether the patent applies but only that that SC 1 and SC 5 are present in the claims. However, because scope concepts always describe limitations, if a claim has two scope concepts mapped, as shown with respect to the claims in patent “Title 2,” the lowest ratings score will control the claim coverage. As shown, SC 6 is described as not being present in the product and the “Title 2” claims have been mapped to SC 6. Therefore, regardless of the fact the SC 3 has also been mapped and the product has this feature, the “Title 2” claims cannot apply to the product as they are at least limited to SC 6.


This chart may also allow interactivity with a user. This interactivity may include the user changing the “Has feature” values and the chart automatically updating the claim coverage and product coverage rows. For example, if the SC 1 rating was changed to ‘1,’ the claim coverage value of the patent “Title 1” may change to “1” signifying the patent does not apply to the product. In some embodiments, any changes that result from input from the user are highlighted on the chart. This may allow a user to quickly see the effects of potential changes to product coverage.



FIG. 18 illustrates an example freedom to operate chart. In an example embodiment, a freedom to operate chart allows a user to quickly see which patents may be necessary to obtain licenses from or purchase to produce a product, sell a service, etc. FIG. 18 is similar to FIG. 17 except for in place of a “Has feature?” column there is a “Need Feature?” column. The values in this column may represent whether or not, and to what extent, a user believes a feature is necessary in his or her product. A ‘3’ may indicate that the scope concept is necessary, a ‘2’ may indicate the scope concept is wanted, but not needed, and a ‘1’ may indicate the scope concept is not needed. In an example embodiment, the “claim status” row shown in FIG. 18 reflects whether a patent in the patent set needs to be licensed or purchased in order for the user to operate freely. As with the product coverage chart, the lowest value in the “need feature” column controls. Thus, patent “Title 1” is not needed even though SC 1 is mapped to all the claims and the user has indicated the feature is necessary. Similarly to above, a user may interact with the ratings to see in real-time the impact of removing or adding features in terms of the number of patents needing to be licensed or purchased.



FIG. 19 illustrates an example claim/patent valuation chart. In an example embodiment, a claim/patent valuation chart allows a user to see which patents/claims may be necessary to license, etc., to maximize the value of a currently owned patent or patent claim. FIG. 19 is similar to FIG. 17 except the values in the ratings column reflect whether or not a scope concept is necessary to maximize a patent's value. The values in this column may represent whether or not, and to what extent, a user believes a feature is necessary in maximize a patent's value. A ‘3’ may indicate that the scope concept is necessary, a ‘2’ may indicate the scope concept is wanted, but not needed, and a ‘1’ may indicate the scope concept is not needed. In an example embodiment, the “claim value” row shown in FIG. 19 reflects whether a patent in the patent set needs to be licensed or purchased in order to maximize the user's patent. As with the product coverage chart, the lowest value in the rating column controls. Thus, patent “Title 1” is not important, even though SC 1 is mapped to all the claims and the user has indicated a high value for SC 1. Similarly to the above charts, a user may interact with the chart by changing the ratings to see in real-time the effects on patents in the patent set.



FIG. 20 illustrates an example validity chart. In an example embodiment, a validity chart allows a user to see the overlap between a patent and a patent set. FIG. 20 is similar to FIG. 17 except the values in the ratings column reflect whether or not a feature is shown in the patent in question (the patent to which the patent set is being compared). The values in this column may represent whether or not, and to what extent, a user believes a feature is present in the patent in question. A ‘3’ may indicate that the scope concept is shown, a ‘2’ may indicate the scope concept is possibly shown, and a ‘1’ may indicate the scope concept is not shown. In an example embodiment, the claim status row shown in FIG. 20 reflects the extent to which the patent in question and the patents in the patent set overlap. Unlike the product coverage chart, if two scope concepts are mapped to a patent, but contain different ratings, the feature rating becomes “some overlap”. Thus, even though SC 5 has been rated as not shown and mapped to patent “Title 1,” SC 1 is also mapped to the patent but is shown and therefore there is some overlap between the patent in question and patent “Title 1.” A finding of “complete overlap” may indicate to a user that a patent or claim is completed anticipated. As above, the user may interact with the chart by changing the ratings to see in real-time the effects on patents in the patent set.



FIG. 21 illustrates an example white space analysis chart. In an example embodiment, a white space analysis chart allows a user to see the frequency in which scope concepts appear in a patent set. In some embodiments there are scope concepts that are in no patent claims. The chart may be color coded to allow a user to quickly ascertain the least frequently used scope concepts. FIG. 22 illustrates an example white space claim generation chart. In an example embodiment the generated chart illustrates suggested combinations of unclaimed combinations of existing scope concepts as well as suggested combinations of new scope concepts with existing scope concepts.


Computer System



FIG. 23 shows a diagrammatic representation of a machine in the example form of a computer system 2300 within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a server-client network environment or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a Personal Computer (PC), a tablet PC, a Set-Top Box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. Example embodiments can also be practiced in distributed system environments where local and remote computer systems which are linked (e.g., either by hardwired, wireless, or a combination of hardwired and wireless connections) through a network both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory-storage devices (see below).


The example computer system 2300 includes a processor 2302 (e.g., a Central Processing Unit (CPU), a Graphics Processing Unit (GPU) or both), a main memory 2304 and a static memory 2306, which communicate with each other via a bus 2308. The computer system 2300 may further include a video display unit 2310 (e.g., a Liquid Crystal Display (LCD) or a Cathode Ray Tube (CRT)). The computer system 2300 may also includes an alphanumeric input device 2312 (e.g., a keyboard), a User Interface (UI) cursor controller (e.g., a mouse), a disc drive unit 2316, a signal generation device 2318 (e.g., a speaker) and a network interface device (e.g., a transmitter) 2320.


The disc drive unit 2316 includes a machine-readable medium 2328 on which is stored one or more sets of instructions 2317 and data structures (e.g., software) embodying or utilized by any one or more of the methodologies or functions illustrated herein. The software may also reside, completely or at least partially, within the main memory 2304 and/or within the processor 2302 during execution thereof by the computer system 2300, the main memory 2304 and the processor 2302 also constituting machine-readable media.


The instructions 2317 may further be transmitted or received over a network (e.g., the INTERNET) 2326 via the network interface device 2320 utilizing any one of a number of well-known transfer protocols (e.g., HTTP, Session Initiation Protocol (SIP)).


The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any of the one or more of the methodologies illustrated herein. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic medium.


The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims
  • 1. A system comprising: at least one processor; andmemory including instructions that, when executed by the at least one processor, cause the at least one processor to perform operations to:maintain a database of patent portfolios and a database of patents;generate a patent mapping graphical user interface including a search expression entry user interface element for receiving a search query that is automatically associated with a selected patent portfolio;generate, for display in the patent mapping graphical user interface, a set of search results returned by searching a plurality of patent claims in the selected patent portfolio that include one or more patent claims including elements of the search query;upon receipt of an indication of a selection of a patent mapping user interface element, display a patent concept graphical user interface that includes a patent concept entry user interface element for receipt of a patent concept and a selectable submission user interface element for submission of the patent concept;upon receipt of an indication of a selection of the selectable submission user interface element, generate a mapping object for each of the one or more patent claims of the set of search results, wherein the mapping object describes the relationship between the patent concept and a respective patent claim of the one or more patent claims;map the one or more patent claims of the set of search results to the patent concept using the respective mapping object for each of the one or more patent claims; anddisplay the mapped one or more patent claims in the patent mapping graphical user interface.
  • 2. The system of claim 1, further comprising instructions to: maintain a database of ontologies, wherein the ontologies include one or more patent concepts, wherein the patent concept entry user interface includes a list of selectable user interface elements associated with the one or more patent concepts, and wherein the patent concept is received upon receipt of an indication of a selection of a member of the list of selectable user interface elements.
  • 3. The system of claim 2, wherein the one or more patent concepts includes a technology category.
  • 4. The system of claim 2, wherein the one or more patent concepts includes a scope concepts, the scope concept defining a scope to which a patent claim is limited.
  • 5. The system of claim 1, wherein the instructions to map the one or more patent claims to the patent concept further comprises instructions to: maintain a database of patent claims, the database of patent claims including the one or more patent claims; andstore an indication of a relationship between the patent concept and the one or more patent claims in the database of patent claims.
  • 6. The system of claim 5, wherein the indication of the relationship includes an indication that the one or more claims are not mapped to the patent concept.
  • 7. The system of claim 5, wherein the indication of the relationship includes an indication that the one or more patent claims are mapped to the patent concept.
  • 8. At least one non-transitory machine-readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations to: maintain a database of patent portfolios and a database of patents;generate a patent mapping graphical user interface including a search expression entry user interface element for receiving a search query that is automatically associated with a selected patent portfolio;generate, for display in the patent mapping graphical user interface, a set of search results returned by searching a plurality of patent claims in the selected patent portfolio that include one or more patent claims including elements of the search query;upon receipt of an indication of a selection of a patent mapping user interface element, display a patent concept graphical user interface that includes a patent concept entry user interface element for receipt of a patent concept and a selectable submission user interface element for submission of the patent concept;upon receipt of an indication of a selection of the selectable submission user interface element, generate a mapping object for each of the one or more patent claims of the set of search results, wherein the mapping object describes the relationship between the patent concept and a respective patent claim of the one or more patent claims;map the one or more patent claims of the set of search results to the patent concept using the respective mapping object for each of the one or more patent claims; anddisplay the mapped one or more patent claims in the patent mapping graphical user interface.
  • 9. The at least one non-transitory machine readable medium of claim 8, further comprising instructions to: maintain a database of ontologies, wherein the ontologies include one or more patent concepts, wherein the patent concept entry user interface includes a list of selectable user interface elements associated with the one or more patent concepts, and wherein the patent concept is received upon receipt of an indication of a selection of a member of the list of selectable user interface elements.
  • 10. The at least one non-transitory machine readable medium of claim 9, wherein the one or more patent concepts includes a technology category.
  • 11. The at least one non-transitory machine readable medium of claim 9, wherein the one or more patent concepts includes a scope concepts, the scope concept defining a scope to which a patent claim is limited.
  • 12. The at least one non-transitory machine readable medium of claim 8, wherein the instructions to map the one or more patent claims to the patent concept further comprises instructions to: maintain a database of patent claims, the database of patent claims including the one or more patent claims; andstore an indication of a relationship between the patent concept and the one or more patent claims in the database of patent claims.
  • 13. The at least one non-transitory machine readable medium of claim 12, wherein the indication of the relationship includes an indication that the one or more claims are not mapped to the patent concept.
  • 14. The at least one non-transitory machine readable medium of claim 12, wherein the indication of the relationship includes an indication that the one or more patent claims are mapped to the patent concept.
  • 15. A method performed by processing circuitry of a computing device, the method comprising: maintaining a database of patent portfolios and a database of patents;generating a patent mapping graphical user interface including a search expression entry user interface element for receiving a search query that is automatically associated with a selected patent portfolio;generating, for display in the patent mapping graphical user interface, a set of search results returned by searching a plurality of patent claims in the selected patent portfolio that include one or more patent claims including elements of the search query;upon receipt of an indication of a selection of a patent mapping user interface element, displaying a patent concept graphical user interface that includes a patent concept entry user interface element for receipt of a patent concept and a selectable submission user interface element for submission of the patent concept;upon receipt of an indication of a selection of the selectable submission user interface element, generating a mapping object for each of the one or more patent claims of the set of search results, wherein the mapping object describes the relationship between the patent concept and a respective patent claim of the one or more patent claims;mapping the one or more patent claims of the set of search results to the patent concept using the respective mapping object for each of the one or more patent claims; anddisplaying the mapped one or more patent claims in the patent mapping graphical user interface.
  • 16. The method of claim 15, further comprising: maintaining a database of ontologies, the ontologies including one or more patent concepts, wherein the patent concept entry user interface includes a list of selectable user interface elements associated with the one or more patent concepts, and wherein the patent concept is received upon receipt of an indication of a selection of a member of the list of selectable user interface elements.
  • 17. The method of claim 16, wherein the one or more patent concepts includes a technology category.
  • 18. The method of claim 16, wherein the one or more patent concepts includes a scope concepts, the scope concept defining a scope to which a patent claim is limited.
  • 19. The method of claim 15, wherein mapping the one or more patent claims to the patent concept further comprises: maintaining a database of patent claims, the database of patent claims including the one or more patent claims; andstoring an indication of a relationship between the patent concept and the one or more patent claims in the database of patent claims.
  • 20. The method of claim 19, wherein the indication of the relationship includes an indication that the one or more patent claims are mapped to the patent concept.
RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. 119(e) of U.S. Provisional Patent Application Ser. No. 61/107,930 filed Oct. 23, 2008, which is incorporated herein by reference in its entirety and made a part hereof. This application is related to U.S. patent application Ser. No. 11/494,278, entitled “Patent Mapping,” by Steven W. Lundberg, Janal M. Kalis, and Pradeep Sinha, filed Jul. 27, 2006, which is incorporated herein by reference; and is further related to U.S. patent application Ser. No. 11/888,632, entitled “Patent Tracking,” by Steven W. Lundberg and Janal M. Kalis, filed Aug. 1, 2007 which is incorporated herein by reference; and is further related to U.S. patent application Ser. No. 10/710,656, entitled “Patent Mapping,” by Steven W. Lundberg, Jana M. Kalis, and Pradeep Sinha, filed Jul. 27, 2004 which is incorporated herein by reference and corresponding PCT application PCT/US2005/026768 filed Jul. 27, 2005.

US Referenced Citations (622)
Number Name Date Kind
4807154 Scully et al. Feb 1989 A
4868733 Fujisawa et al. Sep 1989 A
5297039 Kanaegami et al. Mar 1994 A
5329447 Leedom, Jr. Jul 1994 A
5404506 Fujisawa et al. Apr 1995 A
5410646 Tondevold et al. Apr 1995 A
5530852 Meske et al. Jun 1996 A
5548506 Srinivasan Aug 1996 A
5548753 Linstead et al. Aug 1996 A
5553226 Kiuchi et al. Sep 1996 A
5555408 Fujisawa et al. Sep 1996 A
5557515 Abbruzzese et al. Sep 1996 A
5592664 Starkey Jan 1997 A
5623679 Rivette et al. Apr 1997 A
5623681 Rivette et al. Apr 1997 A
5644740 Kiuchi Jul 1997 A
5659729 Nielsen Aug 1997 A
5664063 Johnson et al. Sep 1997 A
5664714 Navarro et al. Sep 1997 A
5694523 Wical Dec 1997 A
5696916 Yamazaki et al. Dec 1997 A
5699528 Hogan Dec 1997 A
5721910 Unger et al. Feb 1998 A
5745745 Tada et al. Apr 1998 A
5754840 Rivette May 1998 A
5758328 Giovannoli May 1998 A
5768580 Wical Jun 1998 A
5774833 Newman Jun 1998 A
5787411 Groff et al. Jul 1998 A
5794236 Mehrle Aug 1998 A
5799325 Rivette et al. Aug 1998 A
5809318 Rivette et al. Sep 1998 A
5850520 Greibenow et al. Dec 1998 A
5870745 McCune Feb 1999 A
5895468 Whitmyer, Jr. Apr 1999 A
5903881 Schrader et al. May 1999 A
5907837 Ferrel et al. May 1999 A
5926811 Miller et al. Jul 1999 A
5940821 Wical Aug 1999 A
5953726 Carter et al. Sep 1999 A
5970463 Cave et al. Oct 1999 A
5991751 Rivette et al. Nov 1999 A
5991756 Wu Nov 1999 A
5991780 Rivette et al. Nov 1999 A
5999907 Donner et al. Dec 1999 A
6006221 Liddy et al. Dec 1999 A
6014663 Rivette et al. Jan 2000 A
6038561 Snyder et al. Mar 2000 A
6049801 Whitmyer, Jr. Apr 2000 A
6055538 Kessenich et al. Apr 2000 A
6076088 Paik et al. Jun 2000 A
6094652 Faisal Jul 2000 A
6182062 Fujisawa et al. Jan 2001 B1
6182078 Whitmyer, Jr. Jan 2001 B1
6216128 Di-Criescenzo et al. Apr 2001 B1
6226792 Goiffon et al. May 2001 B1
6263335 Paik et al. Jul 2001 B1
6327593 Goiffon Dec 2001 B1
6339767 Rivette et al. Jan 2002 B1
6363361 Lundberg Mar 2002 B1
6363378 Conklin et al. Mar 2002 B1
6401118 Thomas Jun 2002 B1
6405190 Conklin Jun 2002 B1
6415283 Conklin Jul 2002 B1
6415319 Ambroziak Jul 2002 B1
6434580 Takano et al. Aug 2002 B1
6453312 Goiffon et al. Sep 2002 B1
6460043 Tabbara et al. Oct 2002 B1
6490581 Neshatfar et al. Dec 2002 B1
6499026 Rivette et al. Dec 2002 B1
6502081 Wiltshire, Jr. et al. Dec 2002 B1
6513027 Powers et al. Jan 2003 B1
6526440 Bharat Feb 2003 B1
6542884 Soderberg et al. Apr 2003 B1
6556992 Barney et al. Apr 2003 B1
6560620 Ching May 2003 B1
6574632 Fox et al. Jun 2003 B2
6629097 Keith Sep 2003 B1
6654731 Mahesh Nov 2003 B1
6662178 Lee Dec 2003 B2
6665656 Carter Dec 2003 B1
6665670 Winer et al. Dec 2003 B2
6675159 Lin et al. Jan 2004 B1
6678692 Hyatt Jan 2004 B1
6694315 Grow Feb 2004 B1
6694331 Lee Feb 2004 B2
6701309 Beeferman et al. Mar 2004 B1
6751621 Calistri-Yeh et al. Jun 2004 B1
6766315 Bratsos et al. Jul 2004 B1
6789092 Oppedahl et al. Sep 2004 B1
6823331 Abu-Hakima Nov 2004 B1
6839665 Meyers Jan 2005 B1
6847960 Li et al. Jan 2005 B1
6847966 Sommer et al. Jan 2005 B1
6847979 Allemang et al. Jan 2005 B2
6879990 Boyer et al. Apr 2005 B1
6885999 Corless Apr 2005 B1
6889223 Hattori et al. May 2005 B2
6941553 Eisler et al. Sep 2005 B2
6970842 Ashby Nov 2005 B1
6970881 Mohan et al. Nov 2005 B1
6976016 Chang Dec 2005 B2
6980984 Huffman et al. Dec 2005 B1
6981007 Whitmyer, Jr. Dec 2005 B1
7003516 Dehlinger et al. Feb 2006 B2
7016852 Lee Mar 2006 B1
7016895 Dehlinger et al. Mar 2006 B2
7024408 Dehlinger et al. Apr 2006 B2
7035463 Monobe et al. Apr 2006 B1
7051022 Faisal May 2006 B1
7054854 Hattori et al. May 2006 B1
7054856 Won et al. May 2006 B2
7080067 Nonomura et al. Jul 2006 B2
7085771 Chung et al. Aug 2006 B2
7158983 Willse et al. Jan 2007 B2
7185172 Mick, Jr. et al. Feb 2007 B1
7221016 Inoue May 2007 B2
7231384 Wu et al. Jun 2007 B2
7231386 Nonomura et al. Jun 2007 B2
7281008 Lawrence et al. Oct 2007 B1
7293018 Hattori et al. Nov 2007 B2
7296015 Poltorak Nov 2007 B2
7305625 Zilka et al. Dec 2007 B1
7369701 Lundberg May 2008 B2
7383294 Tamer et al. Jun 2008 B1
7386460 Frank et al. Jun 2008 B1
7395261 Atzel Jul 2008 B1
7433884 Breitzman Oct 2008 B2
7444589 Zellner et al. Oct 2008 B2
7483829 Murakami et al. Jan 2009 B2
7493253 Ceusters et al. Feb 2009 B1
7523126 Rivette et al. Apr 2009 B2
7536446 Blumberg May 2009 B2
7610185 Ershov Oct 2009 B1
7653631 Lundberg Jan 2010 B1
7676375 Neifeld et al. Mar 2010 B1
7680733 Lundberg Mar 2010 B1
7698330 Kim Apr 2010 B2
7702640 Vermeulen et al. Apr 2010 B1
7716226 Barney May 2010 B2
7716581 Tran May 2010 B2
7734545 Fogliano et al. Jun 2010 B1
7739240 Saito et al. Jun 2010 B2
7765227 Khoshnevisan et al. Jul 2010 B1
7769685 Malackowskl et al. Aug 2010 B2
7783619 Mcbeath et al. Aug 2010 B2
7788251 Carlson et al. Aug 2010 B2
7801889 Kim et al. Sep 2010 B2
7801909 Poltorak Sep 2010 B2
7823061 Chan Oct 2010 B2
7836048 Schneider Nov 2010 B2
7881937 Hasan et al. Feb 2011 B2
7962511 Barney Jun 2011 B2
7966328 Germeraad et al. Jun 2011 B2
7983928 Lee Jul 2011 B2
7996753 Chan et al. Aug 2011 B1
8000528 Ming et al. Aug 2011 B2
8005760 Lee Aug 2011 B1
8041739 Glasgow Oct 2011 B2
8064736 Chan et al. Nov 2011 B2
8078545 Zilka et al. Dec 2011 B1
8095581 Stobbs et al. Jan 2012 B2
8131701 Barney Mar 2012 B2
8160306 Neustel et al. Apr 2012 B1
8161025 Lundberg et al. Apr 2012 B2
8176440 Stading May 2012 B2
8196030 Wang et al. Jun 2012 B1
8204816 Brodsky et al. Jun 2012 B2
8254692 Ramachandrula et al. Aug 2012 B2
8275708 Dennes et al. Sep 2012 B1
8380548 Ng et al. Feb 2013 B2
8386456 Paiz Feb 2013 B1
8442814 Ceusters et al. May 2013 B2
8447758 Adler et al. May 2013 B1
8538794 Marko et al. Sep 2013 B2
8543511 Wang Sep 2013 B2
8589413 Mohan et al. Nov 2013 B1
8600900 Lundberg Dec 2013 B2
8713078 Kunjithapatham et al. Apr 2014 B2
8812292 Ceusters et al. Aug 2014 B2
8892547 Lundberg Nov 2014 B2
8972385 Lundberg Mar 2015 B2
9003474 Smith Apr 2015 B1
9098568 Li et al. Aug 2015 B2
9110971 Liao et al. Aug 2015 B2
9146985 Carter Sep 2015 B2
9201956 Lundberg et al. Dec 2015 B2
9201966 Lundberg Dec 2015 B2
9286351 Lundberg Mar 2016 B2
9396274 Lundberg Jul 2016 B2
9541977 Lee Jan 2017 B1
9652546 Lundberg May 2017 B2
9659071 Lundberg et al. May 2017 B2
9679019 Lundberg Jun 2017 B2
9858319 Lundberg et al. Jan 2018 B2
9904726 Lundberg Feb 2018 B2
9965460 Wasiuk et al. May 2018 B1
10013726 Jung et al. Jul 2018 B1
10268731 Lundberg Apr 2019 B2
10546273 Lundberg Jan 2020 B2
10614082 Lundberg et al. Apr 2020 B2
10628429 Lundberg Apr 2020 B2
10860657 Lundberg Dec 2020 B2
10885078 Lundberg Jan 2021 B2
11048709 Lundberg Jun 2021 B2
20010007977 Geary Jul 2001 A1
20010042064 Davis et al. Nov 2001 A1
20010049688 Fratkina et al. Dec 2001 A1
20020004775 Kossovsky et al. Jan 2002 A1
20020007373 Blair et al. Jan 2002 A1
20020022974 Lindh Feb 2002 A1
20020023053 Szoc et al. Feb 2002 A1
20020029208 Josephson Mar 2002 A1
20020035499 Germeraad et al. Mar 2002 A1
20020035571 Coult Mar 2002 A1
20020042784 Kerven et al. Apr 2002 A1
20020052971 Okudera et al. May 2002 A1
20020059076 Grainger et al. May 2002 A1
20020065675 Grainger et al. May 2002 A1
20020065677 Grainger et al. May 2002 A1
20020072920 Grainger Jun 2002 A1
20020077835 Hagelin Jun 2002 A1
20020078090 Hwang et al. Jun 2002 A1
20020082778 Barnett Jun 2002 A1
20020091541 Lundberg Jul 2002 A1
20020091542 Grainger Jul 2002 A1
20020091702 Mullins Jul 2002 A1
20020103654 Poltorak Aug 2002 A1
20020107896 Ronai Aug 2002 A1
20020111824 Grainger Aug 2002 A1
20020111941 Roux et al. Aug 2002 A1
20020111953 Snyder Aug 2002 A1
20020116363 Grainger Aug 2002 A1
20020129015 Caudill et al. Sep 2002 A1
20020138384 Malackowski Sep 2002 A1
20020138465 Lee et al. Sep 2002 A1
20020138474 Lee Sep 2002 A1
20020138475 Lee Sep 2002 A1
20020143496 Mactas et al. Oct 2002 A1
20020143742 Nonomura et al. Oct 2002 A1
20020147711 Hattori et al. Oct 2002 A1
20020147738 Reader et al. Oct 2002 A1
20020161733 Grainger Oct 2002 A1
20020163541 Williams et al. Nov 2002 A1
20020174131 Winer et al. Nov 2002 A1
20020175934 Hand et al. Nov 2002 A1
20020175941 Hand et al. Nov 2002 A1
20020177907 Hand et al. Nov 2002 A1
20020184234 Lundberg Dec 2002 A1
20030004843 Frain Jan 2003 A1
20030004936 Grune et al. Jan 2003 A1
20030026459 Won et al. Feb 2003 A1
20030033295 Adler et al. Feb 2003 A1
20030033333 Nishino et al. Feb 2003 A1
20030046269 Yamazaki Mar 2003 A1
20030046307 Rivette Mar 2003 A1
20030050915 Allemang et al. Mar 2003 A1
20030066025 Garner et al. Apr 2003 A1
20030074354 Lee et al. Apr 2003 A1
20030084066 Waterman et al. May 2003 A1
20030115191 Copperman et al. Jun 2003 A1
20030154085 Kelley Aug 2003 A1
20030167181 Lundberg et al. Sep 2003 A1
20030187832 Reader Oct 2003 A1
20030187874 Peschel et al. Oct 2003 A1
20030191654 Panchal et al. Oct 2003 A1
20030191780 Heger et al. Oct 2003 A1
20030195764 Baker et al. Oct 2003 A1
20030212572 Poltorak Nov 2003 A1
20030212706 Shih Nov 2003 A1
20030217335 Chung et al. Nov 2003 A1
20030220891 Fish Nov 2003 A1
20030225749 Cox et al. Dec 2003 A1
20030229470 Pejic Dec 2003 A1
20040002892 Gluck et al. Jan 2004 A1
20040006457 Dehlinger et al. Jan 2004 A1
20040006459 Dehlinger et al. Jan 2004 A1
20040006547 Dehlinger et al. Jan 2004 A1
20040006558 Dehlinger et al. Jan 2004 A1
20040006594 Boyer et al. Jan 2004 A1
20040010393 Barney Jan 2004 A1
20040015481 Zinda Jan 2004 A1
20040024733 Won et al. Feb 2004 A1
20040024739 Copperman et al. Feb 2004 A1
20040044688 Brudz et al. Mar 2004 A1
20040049498 Dehlinger et al. Mar 2004 A1
20040054672 Tsuchitani et al. Mar 2004 A1
20040059736 Willse et al. Mar 2004 A1
20040059994 Fogel et al. Mar 2004 A1
20040064438 Kostoff Apr 2004 A1
20040073443 Gabrick et al. Apr 2004 A1
20040078192 Poltorak Apr 2004 A1
20040078365 Poltorak Apr 2004 A1
20040083206 Wu et al. Apr 2004 A1
20040088306 Murthy et al. May 2004 A1
20040088332 Lee et al. May 2004 A1
20040103112 Colson et al. May 2004 A1
20040122656 Abir Jun 2004 A1
20040122841 Goodman et al. Jun 2004 A1
20040133433 Lee et al. Jul 2004 A1
20040133534 Mahesh Jul 2004 A1
20040133555 Toong et al. Jul 2004 A1
20040133566 Ishiguro et al. Jul 2004 A1
20040167875 Sneiders Aug 2004 A1
20040177068 Beretich et al. Sep 2004 A1
20040181417 Piller et al. Sep 2004 A1
20040181427 Stobbs et al. Sep 2004 A1
20040186705 Morgan et al. Sep 2004 A1
20040186738 Reisman Sep 2004 A1
20040199400 Lundberg Oct 2004 A1
20040223648 Hoene et al. Nov 2004 A1
20040236646 Wu et al. Nov 2004 A1
20040260569 Bell et al. Dec 2004 A1
20040268399 Asakawa Dec 2004 A1
20050004806 Lin et al. Jan 2005 A1
20050005239 Richards et al. Jan 2005 A1
20050010555 Gallivan Jan 2005 A1
20050010863 Zernik Jan 2005 A1
20050021522 Herman et al. Jan 2005 A1
20050060170 Kummamura et al. Mar 2005 A1
20050060303 Wu et al. Mar 2005 A1
20050060306 Hattori et al. Mar 2005 A1
20050080656 Crow et al. Apr 2005 A1
20050080723 Burchetta et al. Apr 2005 A1
20050080775 Colledge et al. Apr 2005 A1
20050080776 Colledge et al. Apr 2005 A1
20050097628 Lussier et al. May 2005 A1
20050108652 Beretich, Jr. et al. May 2005 A1
20050114763 Nonomura et al. May 2005 A1
20050119995 Lee Jun 2005 A1
20050120011 Dehlinger et al. Jun 2005 A1
20050125459 Sutinen et al. Jun 2005 A1
20050131882 Beretich et al. Jun 2005 A1
20050144177 Hodes Jun 2005 A1
20050154673 Fellenstein et al. Jul 2005 A1
20050165600 Kasravi et al. Jul 2005 A1
20050165744 Taylor et al. Jul 2005 A1
20050182755 Tran Aug 2005 A1
20050198026 Dehlinger et al. Sep 2005 A1
20050203768 Florance et al. Sep 2005 A1
20050210008 Tran et al. Sep 2005 A1
20050210009 Tran Sep 2005 A1
20050210042 Goedken Sep 2005 A1
20050216898 Powell, Jr. et al. Sep 2005 A1
20050228684 Pogodin et al. Oct 2005 A1
20050234738 Hodes Oct 2005 A1
20050234881 Burago et al. Oct 2005 A1
20050240595 Chandrasekaran Oct 2005 A1
20050246194 Lundberg Nov 2005 A1
20050251383 Murray Nov 2005 A1
20050256734 Ciikeman Nov 2005 A1
20050261927 Bilak et al. Nov 2005 A1
20050289524 McGinnes Dec 2005 A1
20060015485 Hofmann Jan 2006 A1
20060026174 Lundberg et al. Feb 2006 A1
20060026203 Tan et al. Feb 2006 A1
20060036451 Lundberg et al. Feb 2006 A1
20060036452 Williams Feb 2006 A1
20060036453 Williams Feb 2006 A1
20060036529 Williams Feb 2006 A1
20060036632 Williams Feb 2006 A1
20060036635 Williams Feb 2006 A1
20060053154 Yano Mar 2006 A1
20060074836 Gardner et al. Apr 2006 A1
20060074867 Breitzman Apr 2006 A1
20060074991 Lussier et al. Apr 2006 A1
20060085249 Diaz et al. Apr 2006 A1
20060085478 Landau et al. Apr 2006 A1
20060106793 Liang May 2006 A1
20060106847 Eckardt, III et al. May 2006 A1
20060112084 Mcbeath et al. May 2006 A1
20060143162 Bernacki et al. Jun 2006 A1
20060149720 Dehlinger Jul 2006 A1
20060150074 Zellner Jul 2006 A1
20060161562 McFarland et al. Jul 2006 A1
20060173903 Zimmerman et al. Aug 2006 A1
20060173920 Adler et al. Aug 2006 A1
20060190449 Lundberg et al. Aug 2006 A1
20060190807 Tran Aug 2006 A1
20060212302 Lundberg et al. Sep 2006 A1
20060212402 Lundberg et al. Sep 2006 A1
20060212471 Lundberg et al. Sep 2006 A1
20060212480 Lundberg et al. Sep 2006 A1
20060218188 Duncan et al. Sep 2006 A1
20060218491 Grossman et al. Sep 2006 A1
20060224412 Frank et al. Oct 2006 A1
20060224999 Albrecht et al. Oct 2006 A1
20060225000 Albrecht et al. Oct 2006 A1
20060229983 Lundberg Oct 2006 A1
20060235811 Fairweather Oct 2006 A1
20060258397 Kaplan et al. Nov 2006 A1
20060287971 Armstrong Dec 2006 A1
20070005575 Dai et al. Jan 2007 A1
20070010994 Mueller Jan 2007 A1
20070011154 Musgrove et al. Jan 2007 A1
20070011175 Langseth et al. Jan 2007 A1
20070050343 Siddaramappa et al. Mar 2007 A1
20070057967 Armstrong Mar 2007 A1
20070061384 Harrington et al. Mar 2007 A1
20070067297 Kublickis Mar 2007 A1
20070073625 Shelton Mar 2007 A1
20070073748 Barney Mar 2007 A1
20070130112 Lin Jun 2007 A1
20070136116 Germeraad et al. Jun 2007 A1
20070136271 Masuyama et al. Jun 2007 A1
20070136373 Piasecki Jun 2007 A1
20070150298 Barney Jun 2007 A1
20070168345 Gibbs et al. Jul 2007 A1
20070174041 Yeske Jul 2007 A1
20070192272 Elfayoumy et al. Aug 2007 A1
20070198578 Lundberg et al. Aug 2007 A1
20070208669 Rivette et al. Sep 2007 A1
20070208719 Tran Sep 2007 A1
20070219853 Van Luchene et al. Sep 2007 A1
20070219988 Mueller et al. Sep 2007 A1
20070220041 Van Luchene et al. Sep 2007 A1
20070220042 Mueller et al. Sep 2007 A1
20070239705 Hunt et al. Oct 2007 A1
20070245380 Dommer et al. Oct 2007 A1
20070250468 Pieper Oct 2007 A1
20070250488 Lee Oct 2007 A1
20070288256 Speier Dec 2007 A1
20070288856 Butlin et al. Dec 2007 A1
20070294610 Ching Dec 2007 A1
20080005103 Ratcliffe et al. Jan 2008 A1
20080005144 Katz et al. Jan 2008 A1
20080016069 Holt Jan 2008 A1
20080030800 Matsukawa et al. Feb 2008 A1
20080077570 Tang et al. Mar 2008 A1
20080077577 Byrne et al. Mar 2008 A1
20080097931 Grotto Apr 2008 A1
20080104032 Sarkar May 2008 A1
20080109454 Willse et al. May 2008 A1
20080140644 Franks et al. Jun 2008 A1
20080154767 D'agostino Jun 2008 A1
20080154848 Haslam et al. Jun 2008 A1
20080162444 Lee et al. Jul 2008 A1
20080183518 Jiang et al. Jul 2008 A1
20080195568 Chen et al. Aug 2008 A1
20080195595 Masuyama et al. Aug 2008 A1
20080195601 Ntoulas et al. Aug 2008 A1
20080216013 Lundberg et al. Sep 2008 A1
20080243799 Rozich Oct 2008 A1
20080244429 Stading Oct 2008 A1
20080281748 Newman Nov 2008 A1
20080281821 Chen et al. Nov 2008 A1
20080301138 Hasan et al. Dec 2008 A1
20080306952 Lynn et al. Dec 2008 A1
20080312981 Marlett et al. Dec 2008 A1
20090006328 Lindberg et al. Jan 2009 A1
20090006379 Shen et al. Jan 2009 A1
20090007200 Amento et al. Jan 2009 A1
20090012827 Avrunin Jan 2009 A1
20090012937 Lee et al. Jan 2009 A1
20090030713 Venkatachalam Jan 2009 A1
20090043797 Dorie et al. Feb 2009 A1
20090048925 Song et al. Feb 2009 A1
20090055721 Kahn Feb 2009 A1
20090063468 Berg Mar 2009 A1
20090070301 McLean et al. Mar 2009 A1
20090083049 Sciarrino et al. Mar 2009 A1
20090150326 Sheets Jun 2009 A1
20090157717 Palahnuk et al. Jun 2009 A1
20090164431 Zivkovic et al. Jun 2009 A1
20090177656 Carter Jul 2009 A1
20090216994 Hsieh et al. Aug 2009 A1
20090228578 Demers et al. Sep 2009 A1
20090228777 Henry et al. Sep 2009 A1
20090248468 Cronin et al. Oct 2009 A1
20090257396 Eliezer et al. Oct 2009 A1
20090259459 Ceusters et al. Oct 2009 A1
20090259506 Barney Oct 2009 A1
20090265274 Hahn-carlson et al. Oct 2009 A1
20090282054 Casey Nov 2009 A1
20100005094 Poltorak Jan 2010 A1
20100023386 Avisar et al. Jan 2010 A1
20100030680 Malackowski et al. Feb 2010 A1
20100057533 Martinez Ruiz et al. Mar 2010 A1
20100077007 White et al. Mar 2010 A1
20100082395 De Andrade Apr 2010 A1
20100106752 Eckardt, III et al. Apr 2010 A1
20100114587 Masuyama et al. May 2010 A1
20100131513 Lundberg May 2010 A1
20100174698 Odland et al. Jul 2010 A1
20100179948 Xie et al. Jul 2010 A1
20100180223 Speier Jul 2010 A1
20100185689 Hu et al. Jul 2010 A1
20100191622 Reiss et al. Jul 2010 A1
20100191702 Hofmann Jul 2010 A1
20100235337 Shanahan et al. Sep 2010 A1
20100250479 Carter Sep 2010 A1
20100287478 Avasarala et al. Nov 2010 A1
20100306825 Spivack Dec 2010 A1
20100324991 Colledge et al. Dec 2010 A1
20100332511 Stockton et al. Dec 2010 A1
20110029476 Kasravi et al. Feb 2011 A1
20110047166 Stading et al. Feb 2011 A1
20110055192 Tang et al. Mar 2011 A1
20110072014 Lundberg et al. Mar 2011 A1
20110072024 Barney Mar 2011 A1
20110093449 Belenzon et al. Apr 2011 A1
20110099084 Horn et al. Apr 2011 A1
20110099186 Zohar et al. Apr 2011 A1
20110112824 Sayers et al. May 2011 A1
20110113385 Sayers et al. May 2011 A1
20110119134 Zivkovic et al. May 2011 A1
20110153509 Lundberg et al. Jun 2011 A1
20110153852 Thomas Jun 2011 A1
20110179032 Ceusters et al. Jul 2011 A1
20110191310 Liao et al. Aug 2011 A1
20110191314 Howes et al. Aug 2011 A1
20110197121 Kletter Aug 2011 A1
20110202334 Abir Aug 2011 A1
20110225159 Murray Sep 2011 A1
20110231449 Ashley et al. Sep 2011 A1
20110246379 Maddox et al. Oct 2011 A1
20110246473 Stec Oct 2011 A1
20110246486 Peng et al. Oct 2011 A1
20110258177 Wu et al. Oct 2011 A1
20110289096 Barney Nov 2011 A1
20110302172 Chandrasekar et al. Dec 2011 A1
20110307499 Elias et al. Dec 2011 A1
20110320367 Kan et al. Dec 2011 A1
20110320582 Lewis Dec 2011 A1
20120016859 Sears Jan 2012 A1
20120078913 Muni et al. Mar 2012 A1
20120078979 Ghimire Mar 2012 A1
20120095984 Wren-hilton et al. Apr 2012 A1
20120095993 Shau Apr 2012 A1
20120096027 Coult Apr 2012 A1
20120102427 Fenster et al. Apr 2012 A1
20120109642 Stobbs et al. May 2012 A1
20120116989 Lai et al. May 2012 A1
20120117082 Koperda et al. May 2012 A1
20120130773 Abu-ghazalah et al. May 2012 A1
20120130993 Lundberg May 2012 A1
20120174017 Tidwell et al. Jul 2012 A1
20120215768 Zellweger Aug 2012 A1
20120221580 Barney Aug 2012 A1
20120239591 Powell, Jr. et al. Sep 2012 A1
20120240026 Iyer et al. Sep 2012 A1
20120254155 Heim et al. Oct 2012 A1
20120259787 Speier Oct 2012 A1
20120278244 Lee et al. Nov 2012 A1
20120284199 Lundberg Nov 2012 A1
20120290487 Lee et al. Nov 2012 A1
20120317041 Shaffer et al. Dec 2012 A1
20130007578 Shreck et al. Jan 2013 A1
20130013645 Dias et al. Jan 2013 A1
20130054581 Tawfick et al. Feb 2013 A1
20130084009 Lundberg Apr 2013 A1
20130085911 Lundberg Apr 2013 A1
20130085912 Lundberg Apr 2013 A1
20130085929 Lundberg Apr 2013 A1
20130085933 Lundberg Apr 2013 A1
20130085934 Lundberg Apr 2013 A1
20130085946 Lundberg Apr 2013 A1
20130085947 Lundberg Apr 2013 A1
20130085948 Lundberg Apr 2013 A1
20130085949 Lundberg Apr 2013 A1
20130085950 Marais Apr 2013 A1
20130085964 Marais Apr 2013 A1
20130086032 Lundberg Apr 2013 A1
20130086033 Lundberg Apr 2013 A1
20130086042 Lundberg Apr 2013 A1
20130086043 Lundberg Apr 2013 A1
20130086044 Lundberg Apr 2013 A1
20130086045 Lundberg Apr 2013 A1
20130086046 Lundberg Apr 2013 A1
20130086047 Lundberg et al. Apr 2013 A1
20130086048 Lundberg et al. Apr 2013 A1
20130086049 Lundberg et al. Apr 2013 A1
20130086050 Lundberg Apr 2013 A1
20130086070 Lundberg Apr 2013 A1
20130086080 Lundberg Apr 2013 A1
20130086084 Lundberg Apr 2013 A1
20130086093 Lundberg Apr 2013 A1
20130086094 Lundberg Apr 2013 A1
20130086106 Lundberg Apr 2013 A1
20130086117 Lundberg Apr 2013 A1
20130086120 Lundberg et al. Apr 2013 A1
20130086257 Lundberg Apr 2013 A1
20130086469 Lundberg Apr 2013 A1
20130132302 Lundberg et al. May 2013 A1
20130144895 Cameron Jun 2013 A1
20130282409 Lundberg Oct 2013 A1
20130282571 Lundberg Oct 2013 A1
20130282599 Kang et al. Oct 2013 A1
20130282735 Pedersen et al. Oct 2013 A1
20130346116 Lundberg Dec 2013 A1
20130346265 Lundberg Dec 2013 A1
20130346323 Lundberg Dec 2013 A1
20130346505 Lundberg Dec 2013 A1
20140032513 Gaither Jan 2014 A1
20140089210 Lundberg Mar 2014 A1
20140324808 Sandhu et al. Oct 2014 A1
20140379388 Lundberg Dec 2014 A1
20140379686 Vadlamani et al. Dec 2014 A1
20150066842 Lundberg Mar 2015 A1
20150134549 Lundberg et al. May 2015 A1
20150149368 Lundberg May 2015 A1
20150169777 Lundberg Jun 2015 A1
20150347604 Lundberg Dec 2015 A1
20150347605 Lundberg et al. Dec 2015 A1
20150348217 Lundberg Dec 2015 A1
20150371349 Lundberg et al. Dec 2015 A1
20160078109 Lundberg et al. Mar 2016 A1
20160154863 Lundberg Jun 2016 A1
20160358274 George Dec 2016 A1
20160378766 Lundberg Dec 2016 A1
20170046398 Beretich, Jr. et al. Feb 2017 A1
20170075929 Lundberg Mar 2017 A1
20170213291 Plow et al. Jul 2017 A1
20170316036 Lundberg Nov 2017 A1
20170351682 Lundberg Dec 2017 A1
20180137194 Lundberg May 2018 A1
20180157665 Lundberg et al. Jun 2018 A1
20180204180 Lundberg et al. Jul 2018 A1
20200050609 Lundberg Feb 2020 A1
20200210440 Lundberg et al. Jul 2020 A1
20210149969 Lundberg May 2021 A1
20210173858 Lundberg Jun 2021 A1
Foreign Referenced Citations (18)
Number Date Country
2006272510 Feb 2012 AU
2012200701 May 2014 AU
2013270517 Apr 2016 AU
0638870 Feb 1995 EP
2156112 Oct 1985 GB
2260007 Mar 1993 GB
WO-9816890 Apr 1998 WO
WO-0054185 Sep 2000 WO
WO-0243306 May 2002 WO
WO-02080039 Oct 2002 WO
WO-2006015110 Feb 2006 WO
WO-2006015110 Feb 2006 WO
WO-2006128183 Nov 2006 WO
WO-2006128183 Nov 2006 WO
WO-2007014341 Feb 2007 WO
WO-2007014341 Feb 2007 WO
WO-2007014341 Feb 2007 WO
WO-2011123517 Oct 2011 WO
Non-Patent Literature Citations (753)
Entry
“U.S. Appl. No. 10/710,656, Non Final Office Action dated Jan. 17, 2007”, 16 pgs.
“U.S. Appl. No. 10/710,656, Response filed Nov. 13, 2006 to Restriction Requirement dated Oct. 13, 2006”, 6 pgs.
“U.S. Appl. No. 10/710,656, Restriction Requirement dated Oct. 13, 2006”, 9 pgs.
“U.S. Appl. No. 10/915,265, Advisory Action dated Jul. 31, 2008”, 3 pgs.
“U.S. Appl. No. 10/915,265, Final Office Action dated Jul. 10, 2007”, 26 pgs.
“U.S. Appl. No. 10/915,265, Final Office Action dated Jul. 14, 2008”, 23 pgs.
“U.S. Appl. No. 10/915,265, Non Final Office Action dated Jan. 22, 2007”, 15 pgs.
“U.S. Appl. No. 10/915,265, Non-Final Office Action dated Apr. 13, 2009”, 27 pgs.
“U.S. Appl. No. 10/915,265, Non-Final Office Action dated Jun. 2, 2010”, 29 pgs.
“U.S. Appl. No. 10/915,265, Non-Final Office Action dated Nov. 5, 2008”, 27 pgs.
“U.S. Appl. No. 10/915,265, Non-Final Office Action dated Dec. 28, 2007”, 25 pgs.
“U.S. Appl. No. 10/915,265, Response filed Feb. 5, 2009 to Non-Final Office Action dated Nov. 5, 2008”, 11 pgs.
“U.S. Appl. No. 10/915,265, Response filed Apr. 28, 2008 to Non-Final Office Action dated Dec. 28, 2007”, 14 pgs.
“U.S. Appl. No. 10/915,265, Response filed May 18, 2007 to Noon Final Office Action dated Jan. 22, 2007”, 9 pgs.
“U.S. Appl. No. 10/915,265, Response filed Jul. 18, 2008 to Final Office Action dated Jul. 14, 2008”, 17 pgs.
“U.S. Appl. No. 10/915,265, Response filed Sep. 1, 2010 to Non Final Office Action dated Jun. 2, 2010”, 12 pgs.
“U.S. Appl. No. 10/915,265, Response filed Oct. 10, 2007 to Final Office Action filed Jul. 10, 2007”, 15 pgs.
“U.S. Appl. No. 10/915,265, Response filed Nov. 13, 2006 to Restriction Requirement dated Oct. 11, 2006”, 5 pgs.
“U.S. Appl. No. 10/915,265, Restriction Requirement dated Oct. 13, 2006”, 10 pgs.
“U.S. Appl. No. 11/494,278, Final Office Action dated Mar. 23, 2009”, 21 pgs.
“U.S. Appl. No. 11/494,278, Final Office Action dated Apr. 1, 2010”, 20 pgs.
“U.S. Appl. No. 11/494,278, Non Final Office Action dated Oct. 8, 2009”, 21 pgs.
“U.S. Appl. No. 11/494,278, Non-Final Office Action dated Mar. 5, 2008”, 14 pgs.
“U.S. Appl. No. 11/494,278, Notice of Allowance dated May 3, 2011”, 12 pgs.
“U.S. Appl. No. 11/494,278, Notice of Allowance dated Dec. 15, 2011”, 14 pgs.
“U.S. Appl. No. 11/494,278, Notice of Non-Compliant Amendment dated Jun. 7, 2010”, 2 pgs.
“U.S. Appl. No. 11/494,278, Preliminary Amendment filed Oct. 30, 2007”, 6 pgs.
“U.S. Appl. No. 11/494,278, Response filed Feb. 10, 2010 to Non Final Office Action dated Oct. 8, 2009”, 8 pgs.
“U.S. Appl. No. 11/494,278, Response filed Jun. 2, 2010 to Final Office Action dated Apr. 1, 2010”, 7 pgs.
“U.S. Appl. No. 11/494,278, Response filed Jun. 5, 2008 to Non-Final Office Action dated Mar. 5, 2008”, 12 pgs.
“U.S. Appl. No. 11/494,278, Response filed Jun. 9, 2010 to Notice of Non-Compliant Amendment dated Jun. 7, 2010”, 7 pgs.
“U.S. Appl. No. 11/494,278, Response filed Jun. 23, 2009 to Final Office Action dated Mar. 23, 2009”, 8 pgs.
“U.S. Appl. No. 11/888,632, Amendment filed Jun. 12, 2012”, 8 pgs.
“U.S. Appl. No. 11/888,632, Appeal Brief filed Jun. 4, 2015”, 16 pgs.
“U.S. Appl. No. 11/888,632, Appeal Decision mailed Jan. 19, 2017”, 8 pgs.
“U.S. Appl. No. 11/888,632, Decision on Pre-Appeal Brief mailed Mar. 9, 2012”, 2 pgs.
“U.S. Appl. No. 11/888,632, Final Office Action dated Sep. 8, 2014”, 12 pgs.
“U.S. Appl. No. 11/888,632, Final Office Action dated Oct. 19, 2011”, 9 pgs.
“U.S. Appl. No. 11/888,632, Non Final Office Action dated Jan. 19, 2011”, 12 pgs.
“U.S. Appl. No. 11/888,632, Non Final Office Action dated Jan. 24, 2014”, 12 pgs.
“U.S. Appl. No. 11/888,632, Pre-Appeal Brief Request filed Feb. 21, 2012”, 4 pgs.
“U.S. Appl. No. 11/888,632, Response filed Jun. 24, 2014 to Non Final Office Action dated Jan. 24, 2014”, 9 pgs.
“U.S. Appl. No. 11/888,632, Response filed Jul. 19, 2011 to Non Final Office Action dated Jan. 19, 2011”, 8 pgs.
“U.S. Appl. No. 11/888,632, Response filed Dec. 7, 2010, to Restriction Requirement dated Jul. 7, 2010”, 7 pgs.
“U.S. Appl. No. 11/888,632, Restriction Requirement dated Jul. 7, 2010”, 5 pgs.
“U.S. Appl. No. 11/915,718, Advisory Action dated Feb. 15, 2012”, 3 pgs.
“U.S. Appl. No. 11/915,718, Final Office Action dated Dec. 30, 2011”, 13 pgs.
“U.S. Appl. No. 11/915,718, Non Final Office Action dated May 26, 2011”, 9 pgs.
“U.S. Appl. No. 11/915,718, Non Final Office Action dated Jul. 7, 2014”, 17 pgs.
“U.S. Appl. No. 11/915,718, Notice of Non-Compliant Amendment dated Oct. 6, 2011”, 2 pgs.
“U.S. Appl. No. 11/915,718, Preliminary Amendment filed Nov. 27, 2007”, 2 pgs.
“U.S. Appl. No. 11/915,718, Response filed Feb. 8, 2012 to Final Office Action dated Dec. 30, 2011”, 13 pgs.
“U.S. Appl. No. 11/915,718, Response filed Sep. 26, 2011 to Non-Final Office Action dated May 26, 2011”, 9 pgs.
“U.S. Appl. No. 11/915,718, Response filed Oct. 11, 2011 to Notice of Non-Compliant Amendment dated Oct. 6, 2011”, 4 pgs.
“U.S. Appl. No. 12/605,030, Appeal Decision mailed Sep. 1, 2017”, 14 pgs.
“U.S. Appl. No. 12/605,030, Final Office Action dated May 21, 2012”, 10 pgs.
“U.S. Appl. No. 12/605,030, Final Office Action dated Jul. 16, 2014”, 16 pgs.
“U.S. Appl. No. 12/605,030, Non Final Office Action dated Oct. 7, 2011”, 12 pgs.
“U.S. Appl. No. 12/605,030, Non Final Office Action dated Nov. 7, 2013”, 16 pgs.
“U.S. Appl. No. 12/605,030, Response filed Feb. 7, 2012 to Non Final Office Action dated Oct. 7, 2011”, 9 pgs.
“U.S. Appl. No. 12/605,030, Response Filed May 7, 2014 to Non Final Office Action dated Nov. 7, 2013”, 8 pgs.
“U.S. Appl. No. 12/605,030, Response filed Oct. 22, 2012 to Final Office Action dated May 21, 2012”, 8 pgs.
“U.S. Appl. No. 12/658,113, Non Final Office Action dated Feb. 28, 2011”, 26 pgs.
“U.S. Appl. No. 12/958,113, Examiner Interview Summary dated Aug. 24, 2015”, 2 pgs.
“U.S. Appl. No. 12/958,113, Final Office Action dated Aug. 8, 2011”, 26 pgs.
“U.S. Appl. No. 12/958,113, Final Office Action dated Nov. 3, 2014”, 25 pgs.
“U.S. Appl. No. 12/958,113, Non Final Office Action dated Feb. 4, 2016”, 25 pgs.
“U.S. Appl. No. 12/958,113, Non Final Office Action dated Apr. 30, 2014”, 21 pgs.
“U.S. Appl. No. 12/958,113, Non Final Office Action dated Aug. 20, 2015”, 25 pgs.
“U.S. Appl. No. 12/958,113, Notice of Allowance dated Mar. 1, 2017”, 14 pgs.
“U.S. Appl. No. 12/958,113, Response filed Feb. 3, 2015 to Final Office Action dated Nov. 3, 2014”, 11 pgs.
“U.S. Appl. No. 12/958,113, Response filed Feb. 8, 2012 to Final Office Action dated Aug. 8, 2011”, 12 pgs.
“U.S. Appl. No. 12/958,113, Response filed May 3, 2016 to Non Final Office Action dated Feb. 4, 2016”, 11 pgs.
“U.S. Appl. No. 12/958,113, Response filed May 20, 2011 to Non Final Office Action dated Feb. 28, 2011”, 13 pgs.
“U.S. Appl. No. 12/958,113, Response filed Jul. 16, 2014 to Non Final Office Action dated Apr. 30, 2014”, 12 pgs.
“U.S. Appl. No. 12/958,113, Response filed Nov. 6, 2015 to Non Final Office Action dated Aug. 20, 2015”, 12 pgs.
“U.S. Appl. No. 13/253,936, Final Office Action dated Jun. 24, 2013”, 13 pgs.
“U.S. Appl. No. 13/253,936, Non Final Office Action dated Nov. 28, 2012”, 11 pgs.
“U.S. Appl. No. 13/253,936, Response filed Mar. 27, 2013 to Non Final Office Action dated Nov. 28, 2012”, 11 pgs.
“U.S. Appl. No. 13/253,936, Response filed May 10, 2019 to Final Office Action dated Jul. 11, 2018”, 13 pgs.
“U.S. Appl. No. 13/253,936, Response filed Dec. 23, 2013 to Final Office Action dated Jun. 24, 2013”, 5 pgs.
“U.S. Appl. No. 13/253,941, Final Office Action dated Jun. 6, 2013”, 16 pgs.
“U.S. Appl. No. 13/253,941, Non Final Office Action dated May 7, 2014”, 18 pgs.
“U.S. Appl. No. 13/253,941, Non Final Office Action dated Nov. 15, 2012”, 14 pgs.
“U.S. Appl. No. 13/253,941, Response filed Apr. 15, 2013 to Non Final Office Action dated Nov. 15, 2012”, 13 pgs.
“U.S. Appl. No. 13/253,941, Response filed Nov. 6, 2013 to Final Office Action dated Jun. 6, 2013”, 11 pgs.
“U.S. Appl. No. 13/309,200, Appeal Brief Filed Jun. 8, 2015”, 17 pgs.
“U.S. Appl. No. 13/309,200, Appeal Decision mailed Aug. 28, 2017”, 12 pgs.
“U.S. Appl. No. 13/309,200, Corrected Notice of Allowability dated Jan. 9, 2019”, 2 pgs.
“U.S. Appl. No. 13/309,200, Final Office Action dated Jan. 8, 2015”, 14 pgs.
“U.S. Appl. No. 13/309,200, Final Office Action dated Jan. 14, 2014”, 15 pgs.
“U.S. Appl. No. 13/309,200, Final Office Action dated Jun. 18, 2018”, 18 pgs.
“U.S. Appl. No. 13/309,200, Non Final Office Action dated Jul. 2, 2013”, 14 pgs.
“U.S. Appl. No. 13/309,200, Non Final Office Action dated Sep. 10, 2012”, 12 pgs.
“U.S. Appl. No. 13/309,200, Non Final Office Action dated Sep. 24, 2014”, 14 pgs.
“U.S. Appl. No. 13/309,200, Non Final Office Action dated Dec. 4, 2017”, 17 pgs.
“U.S. Appl. No. 13/309,200, Notice of Allowance dated Dec. 6, 2018”, 9 pgs.
“U.S. Appl. No. 13/309,200, Preliminary Amendment filed Dec. 8, 2011”, 8 pgs.
“U.S. Appl. No. 13/309,200, Response filed Jan. 2, 2014 to Non Final Office Action dated Jul. 2, 2013”, 12 pgs.
“U.S. Appl. No. 13/309,200, Response filed Mar. 11, 2013 to Non Final Office Action dated Sep. 10, 2012”, 13 pgs.
“U.S. Appl. No. 13/309,200, Response filed Apr. 4, 2018 to Non Final Office Action dated Dec. 4, 2017”, 11 pgs.
“U.S. Appl. No. 13/309,200, Response filed Jul. 10, 2014 to Final Office Action dated Jan. 14, 2014”, 13 pgs.
“U.S. Appl. No. 13/309,200, Response filed Jan. 17, 2018 to Final Office Action dated Jun. 18, 2018”, 38 pgs.
“U.S. Appl. No. 13/309,200, Response filed Oct. 30, 2017 to Final Office Action dated Jan. 8, 2017”, 12 pgs.
“U.S. Appl. No. 13/309,200, Response filed Dec. 23, 2014 to Non Final Office Action dated Sep. 24, 2014”, 9 pgs.
“U.S. Appl. No. 13/310,279, Appeal Brief filed Nov. 3, 2014”, 19 pgs.
“U.S. Appl. No. 13/310,279, Appeal Decision mailed Aug. 30, 2017”, 9 pgs.
“U.S. Appl. No. 13/310,279, Examiner Interview Summary dated Nov. 19, 2013”, 3 pgs.
“U.S. Appl. No. 13/310,279, Final Office Action dated Sep. 10, 2018”, 24 pgs.
“U.S. Appl. No. 13/310,279, Final Office Action dated Dec. 3, 2013”, 14 pgs.
“U.S. Appl. No. 13/310,279, Non Final Office Action dated Feb. 2, 2018”, 21 pgs.
“U.S. Appl. No. 13/310,279, Non Final Office Action dated Jun. 17, 2013”, 12 pgs.
“U.S. Appl. No. 13/310,279, Pre-Appeal Brief Request filed Apr. 3, 2014”, 5 pgs.
“U.S. Appl. No. 13/310,279, Reply Brief dated Jan. 4, 2016 to Appeal Brief filed Nov. 3, 2014”, 3 pgs.
“U.S. Appl. No. 13/310,279, Response filed May 2, 2018 to Non Final Office Action dated Feb. 2, 2018”, 10 pgs.
“U.S. Appl. No. 13/310,279, Response filed Sep. 13, 2013 to Non Final Office Action dated Jun. 17, 2013”, 15 pgs.
“U.S. Appl. No. 13/310,279, Response filed Oct. 30, 2017 to Non Final Office Action dated Dec. 3, 2017”, 8 pgs.
“U.S. Appl. No. 13/310,322, Appeal Brief filed Jan. 15, 2015”, 17 pgs.
“U.S. Appl. No. 13/310,322, Appeal Decision mailed Sep. 20, 2017”, 18 pgs.
“U.S. Appl. No. 13/310,322, Decision on Pre-Appeal Brief Request dated Sep. 15, 2015”, 2 pgs.
“U.S. Appl. No. 13/310,322, Final Office Action dated Feb. 13, 2014”, 15 pgs.
“U.S. Appl. No. 13/310,322, Final Office Action dated Mar. 31, 2015”, 16 pgs.
“U.S. Appl. No. 13/310,322, Non Final Office Action dated Jul. 2, 2013”, 16 pgs.
“U.S. Appl. No. 13/310,322, Non Final Office Action dated Oct. 3, 2014”, 16 pgs.
“U.S. Appl. No. 13/310,322, Pre-Appeal Brief Request filed Jul. 31, 2015”, 5 pgs.
“U.S. Appl. No. 13/310,322, Reply Brief filed Aug. 15, 2016”, 4 pgs.
“U.S. Appl. No. 13/310,322, Response filed Jan. 5, 2015 to Non Final Office Action dated Oct. 3, 2014”, 12 pgs.
“U.S. Appl. No. 13/310,322, Response filed Nov. 1, 2013 to Non Final Office Action dated Jul. 2, 2013”, 12 pgs.
“U.S. Appl. No. 13/310,332, Response filed Jul. 14, 2014 to Final Office Action dated Feb. 13, 2014”, 12 pgs.
“U.S. Appl. No. 13/310,368, Advisory Action dated Jun. 9, 2015”, 3 pgs.
“U.S. Appl. No. 13/310,368, Advisory Action dated Jul. 8, 2015”, 2 pgs.
“U.S. Appl. No. 13/310,368, Advisory Action dated Aug. 21, 2015”, 2 pgs.
“U.S. Appl. No. 13/310,368, Appeal Brief filed Aug. 2, 2018”, 17 pgs.
“U.S. Appl. No. 13/310,368, Appeal Brief filed Aug. 17, 2015”, 27 pgs.
“U.S. Appl. No. 13/310,368, Appeal Decision mailed Aug. 30, 2017”, 11 pgs.
“U.S. Appl. No. 13/310,368, Final Office Action dated Jan. 7, 2014”, 17 pgs.
“U.S. Appl. No. 13/310,368, Final Office Action dated Mar. 18, 2015”, 15 pgs.
“U.S. Appl. No. 13/310,368, Final Office Action dated Jul. 18, 2019”, 12 pgs.
“U.S. Appl. No. 13/310,368, Non Final Office Action dated Jun. 17, 2013”, 17 pgs.
“U.S. Appl. No. 13/310,368, Non Final Office Action dated Sep. 12, 2014”, 19 pgs.
“U.S. Appl. No. 13/310,368, Non Final Office Action dated Nov. 29, 2018”, 16 pgs.
“U.S. Appl. No. 13/310,368, Non Final Office Action dated Dec. 1, 2017”, 17 pgs.
“U.S. Appl. No. 13/310,368, Notice of Allowance dated Dec. 5, 2019”, 11 pgs.
“U.S. Appl. No. 13/310,368, Response filed May 18, 2015 to Final Office Action dated Mar. 18, 2015”, 11 pgs.
“U.S. Appl. No. 13/310,368, Response filed Jul. 7, 2014 to Final Office Action dated Jan. 7, 2014”, 12 pgs.
“U.S. Appl. No. 13/310,368, Response filed Sep. 17, 2013 to Non Final Office Action dated Jun. 17, 2013”, 15 pgs.
“U.S. Appl. No. 13/310,368, Response filed Oct. 18, 2019 to Final Office Action dated Jul. 18, 2019”, 10 pgs.
“U.S. Appl. No. 13/310,368, Response filed Oct. 30, 2017 to Final Office Action dated Mar. 18, 2015”, 8 pgs.
“U.S. Appl. No. 13/310,368, Response filed Dec. 12, 2014 to Non Final Office Action dated Sep. 12, 2014”, 9 pgs.
“U.S. Appl. No. 13/310,368, Response filed Apr. 29, 2019 to Non Final Office Action dated Nov. 29, 2018”, 12 pgs.
“U.S. Appl. No. 13/310,417, Appeal Brief filed Sep. 11, 2015”, 19 pgs.
“U.S. Appl. No. 13/310,417, Final Office Action dated Jan. 9, 2014”, 17 pgs.
“U.S. Appl. No. 13/310,417, Final Office Action dated Mar. 11, 2015”, 17 pgs.
“U.S. Appl. No. 13/310,417, Non Final Office Action dated Feb. 11, 2016”, 12 pgs.
“U.S. Appl. No. 13/310,417, Non Final Office Action dated Jun. 17, 2013”, 13 pgs.
“U.S. Appl. No. 13/310,417, Non Final Office Action dated Sep. 8, 2014”, 17 pgs.
“U.S. Appl. No. 13/310,417, Response filed May 27, 2014 to Final Office Action dated Jan. 9, 2014”, 14 pgs.
“U.S. Appl. No. 13/310,417, Response filed Sep. 17, 2013 to Non Final Office Action dated Jun. 17, 2013”, 14 pgs.
“U.S. Appl. No. 13/310,452, Advisory Action dated Jul. 17, 2014”, 3 pgs.
“U.S. Appl. No. 13/310,452, Appeal Brief filed Oct. 17, 2016”, 25 pgs.
“U.S. Appl. No. 13/310,452, Appeal Decision mailed Sep. 29, 2017”, 20 pgs.
“U.S. Appl. No. 13/310,452, Decision on Pre-Appeal Brief mailed Apr. 17, 2015”, 2 pgs.
“U.S. Appl. No. 13/310,452, Final Office Action dated May 1, 2014”, 18 pgs.
“U.S. Appl. No. 13/310,452, Final Office Action dated Dec. 15, 2015”, 21 pgs.
“U.S. Appl. No. 13/310,452, Non Final Office Action dated May 4, 2015”, 17 pgs.
“U.S. Appl. No. 13/310,452, Non Final Office Action dated Jul. 10, 2013”, 14 pgs.
“U.S. Appl. No. 13/310,452, Non Final Office Action dated Oct. 6, 2014”, 18 pgs.
“U.S. Appl. No. 13/310,452, Pre-Appeal Brief Request filed Mar. 5, 2015”, 5 pgs.
“U.S. Appl. No. 13/310,452, Response filed Jan. 10, 2014 to Non Final Office Action dated Jul. 10, 2013”, 11 pgs.
“U.S. Appl. No. 13/310,452, Response filed Jul. 1, 2014 to Final Office Action dated May 1, 2014”, 11 pgs.
“U.S. Appl. No. 13/310,452, Response filed Sep. 3, 2015 to Non Final Office Action dated May 4, 2015”, 14 pgs.
“U.S. Appl. No. 13/365,062, Non Final Office Action dated Mar. 19, 2015”, 14 pgs.
“U.S. Appl. No. 13/365,062, Non Final Office Action dated Apr. 30, 2014”, 13 pgs.
“U.S. Appl. No. 13/365,062, Non Final Office Action dated Aug. 19, 2013”, 14 pgs.
“U.S. Appl. No. 13/365,062, Non Final Office Action dated Oct. 9, 2014”, 13 pgs.
“U.S. Appl. No. 13/365,062, Non Final Office Action dated Nov. 30, 2012”, 19 pgs.
“U.S. Appl. No. 13/365,062, Non-Final Office Action dated Jul. 3, 2012”, 20 pgs.
“U.S. Appl. No. 13/365,062, Notice of Allowance dated Jul. 24, 2015”, 11 pgs.
“U.S. Appl. No. 13/365,062, Response filed Feb. 9, 2015 to Non Final Office Action dated Oct. 9, 2014”, 6 pgs.
“U.S. Appl. No. 13/365,062, Response filed May 29, 2013 to Non Final Office Action dated Nov. 30, 2012”, 8 pgs.
“U.S. Appl. No. 13/365,062, Response filed Jun. 19, 2015 to Non Final Office Action dated Mar. 19, 2015”, 9 pgs.
“U.S. Appl. No. 13/365,062, Response filed Sep. 2, 2014 to Non Final Office Action dated Jul. 30, 2014”, 8 pgs.
“U.S. Appl. No. 13/365,062, Response filed Oct. 3, 2012 to Non Final Office Action dated Jul. 3, 2012”, 8 pgs.
“U.S. Appl. No. 13/365,062, Response filed Dec. 19, 2013 to Non Final Office Action dated Aug. 19, 2013”, 10 pgs.
“U.S. Appl. No. 13/464,598, Appeal Brief filed Jan. 28, 2016”, 19 pgs.
“U.S. Appl. No. 13/464,598, Appeal Decision mailed Jul. 31, 2017”, 18 pgs.
“U.S. Appl. No. 13/464,598, Examiner Interview Summary dated May 1, 2014”, 3 pgs.
“U.S. Appl. No. 13/464,598, Final Office Action dated Jul. 28, 2015”, 38 pgs.
“U.S. Appl. No. 13/464,598, Non Final Office Action dated Mar. 16, 2015”, 51 pgs.
“U.S. Appl. No. 13/464,598, Non Final Office Action dated Dec. 4, 2013”, 26 pgs.
“U.S. Appl. No. 13/464,598, Notice of Allowance dated Oct. 12, 2017”, 5 pgs.
“U.S. Appl. No. 13/464,598, Response filed Apr. 5, 2014 to Non Final Office Action dated Dec. 4, 2013”, 44 pgs.
“U.S. Appl. No. 13/464,598, Response filed Jul. 16, 2015 to Non Final Office Action dated Mar. 16, 2015”, 24 pgs.
“U.S. Appl. No. 13/464,598, Response filed Oct. 2, 2017 to Final Office Action dated Jul. 28, 2017”, 17 pgs.
“U.S. Appl. No. 13/573,803, Appeal Brief filed Dec. 29, 2015”, 20 pgs.
“U.S. Appl. No. 13/573,803, Appeal Decision mailed Jul. 28, 2017”, 24 pgs.
“U.S. Appl. No. 13/573,803, Final Office Action dated Apr. 7, 2015”, 16 pgs.
“U.S. Appl. No. 13/573,803, Non Final Office Action dated Sep. 15, 2014”, 15 pgs.
“U.S. Appl. No. 13/573,803, Non Final Office Action dated Dec. 5, 2013”, 16 pgs.
“U.S. Appl. No. 13/573,803, Reply Brief filed Jul. 13, 2016”, 6 pgs.
“U.S. Appl. No. 13/573,803, Response filed Jun. 5, 2014 to Non Final Office Action dated Dec. 5, 2013”, 12 pgs.
“U.S. Appl. No. 13/573,803, Response filed Dec. 15, 2014 to Non Final Office Action dated Sep. 15, 2014”, 12 pgs.
“U.S. Appl. No. 13/573,804, Final Office Action dated Mar. 23, 2015”, 16 pgs.
“U.S. Appl. No. 13/573,804, Non Final Office Action dated Oct. 20, 2014”, 15 pgs.
“U.S. Appl. No. 13/573,804, Response filed Jan. 20, 2015 to Non Final Office Action dated Oct. 20, 2014”, 15 pgs.
“U.S. Appl. No. 13/573,804, Response filed Aug. 29, 2014 to Restriction Requirement dated Jun. 30, 2014”, 8 pgs.
“U.S. Appl. No. 13/573,804, Restriction Requirement dated Jun. 30, 2014”, 5 pgs.
“U.S. Appl. No. 14/010,376, Appeal Brief filed Apr. 19, 2016”, 19 pgs.
“Application Serial No. 14/010,376, Appeal Decision mailed Sep. 8, 2017”, 17 pgs.
“U.S. Appl. No. 14/010,376, Final Office Action dated Aug. 19, 2015”, 13 pgs.
“U.S. Appl. No. 14/010,376, Non Final Office Action dated Mar. 24, 2015”, 10 pgs.
“U.S. Appl. No. 14/010,376, Reply Brief filed Nov. 22, 2016”, 5 pgs.
“U.S. Appl. No. 14/010,376, Response filed Jun. 24, 2015 to Non Final Office Action dated Mar. 24, 2015”, 10 pgs.
“U.S. Appl. No. 14/010,380, Appeal Decision mailed Sep. 27, 2017”, 18 pgs.
“U.S. Appl. No. 14/010,380, Examiners Answer dated Nov. 9, 2016”, 8 pgs.
“U.S. Appl. No. 14/010,380, Final Office Action dated Oct. 6, 2015”, 11 pgs.
“U.S. Appl. No. 14/010,380, Non Final Office Action dated Apr. 15, 2015”, 11 pgs.
“U.S. Appl. No. 14/010,380, Reply Brief filed Jan. 9, 2017”, 6 pgs.
“U.S. Appl. No. 14/010,380, Response filed Aug. 17, 2015 to Non Final Office Action dated Apr. 15, 2015”, 11 pgs.
“U.S. Appl. No. 14/010,391, Appeal Brief filed Aug. 15, 2016”, 23 pgs.
“U.S. Appl. No. 14/010,391, Appeal Decision mailed Oct. 25, 2017”, 19 pgs.
“U.S. Appl. No. 14/010,391, Examiners Answer dated Nov. 9, 2016”, 10 pgs.
“U.S. Appl. No. 14/010,391, Final Office Action dated Sep. 15, 2015”, 11 pgs.
“U.S. Appl. No. 14/010,391, Non Final Office Action dated Mar. 23, 2015”, 11 pgs.
“U.S. Appl. No. 14/010,391, Reply Brief filed Jan. 9, 2017”, 6 pgs.
“U.S. Appl. No. 14/010,391, Response filed Jul. 22, 2015 to Non Final Office Action dated Mar. 23, 2015”, 10 pgs.
“U.S. Appl. No. 14/010,400, Appeal Brief filed Aug. 8, 2016”, 17 pgs.
“U.S. Appl. No. 14/010,400, Examiners Answer dated Nov. 9, 2016”, 9 pgs.
“U.S. Appl. No. 14/010,400, Final Office Action dated Sep. 10, 2015”, 9 pgs.
“U.S. Appl. No. 14/010,400, Non Final Office Action dated Apr. 22, 2015”, 11 pgs.
“U.S. Appl. No. 14/010,400, Response filed Jul. 22, 2015 to Non Final Office Action dated Apr. 22, 2015”, 10 pgs.
“U.S. Appl. No. 14/010,903, Examiners Answer dated Nov. 9, 2016”, 9 pgs.
“U.S. Appl. No. 14/483,903, Appeal Brief filed Oct. 11, 2016”, 21 pgs.
“U.S. Appl. No. 14/483,903, Appeal Decision mailed Sep. 25, 2017”, 18 pgs.
“U.S. Appl. No. 14/483,903, Final Office Action dated Feb. 10, 2016”, 11 pgs.
“U.S. Appl. No. 14/483,903, Non Final Office Action dated Sep. 1, 2015”, 10 pgs.
“U.S. Appl. No. 14/483,903, Reply Brief filed Jan. 9, 2017”, 6 pgs.
“U.S. Appl. No. 14/483,903, Response filed Jan. 4, 2016 to Non Final Office Action dated Sep. 1, 2015”, 11 pgs.
“U.S. Appl. No. 14/536,320, Non Final Office Action dated Mar. 25, 2015”, 9 pgs.
“U.S. Appl. No. 14/750,559, Preliminary Amendment filed Jun. 26, 2015 t”, 9 pgs.
“U.S. Appl. No. 14/826,018, Non Final Office Action dated Jan. 11, 2017”, 19 pgs.
“U.S. Appl. No. 14/826,018, Notice of Allowance dated Aug. 28, 2017”, 13 pgs.
“U.S. Appl. No. 14/826,018, Preliminary Amendment filed Aug. 28, 2015”, 8 pgs.
“U.S. Appl. No. 14/826,018, Response Filed May 11, 2017 to Non Final Office Action dated Jan. 11, 2017”, 14 pgs.
“U.S. Appl. No. 14/949,549, Notice of Allowance dated Jan. 18, 2017”, 11 pgs.
“U.S. Appl. No. 14/949,549, Response filed Jul. 20, 2016 to Non Final Office Action dated Apr. 20, 2016”, 8 pgs.
“U.S. Appl. No. 14/949,549, Response filed Aug. 26, 2016 to Non Final Office Action dated Apr. 20, 2016”, 8 pgs.
“U.S. Appl. No. 14/949,549, Response filed Dec. 27, 2016 to Final Office Action dated Oct. 27, 2016”, 7 pgs.
“U.S. Appl. No. 15/722,868, Non Final Office Action dated Oct. 4, 2019”, 19 pgs.
“U.S. Appl. No. 15/722,868, Preliminary Amendment filed Jan. 19, 2018”, 8 pgs.
“U.S. Appl. No. 15/801,056, Corrected Notice of Allowability dated Nov. 7, 2019”, 2 pgs.
“U.S. Appl. No. 15/801,056, Corrected Notice of Allowability dated Dec. 17, 2019”, 2 pgs.
“U.S. Appl. No. 15/801,056, Final Office Action dated Jan. 25, 2019”, 12 pgs.
“U.S. Appl. No. 15/801,056, Non Final Office Action dated Jul. 11, 2018”, 13 pgs.
“U.S. Appl. No. 15/801,056, Notice of Allowance dated Sep. 13, 2019”, 11 pgs.
“U.S. Appl. No. 15/801,056, Preliminary Amendment filed Apr. 30, 2018”, 9 pgs.
“U.S. Appl. No. 15/801,056, Response filed Jul. 25, 2019 to Final Office Action dated Jan. 25, 2019”, 10 pgs.
“U.S. Appl. No. 15/849,362, Final Office Action dated May 2, 2019”, 8 pgs.
“U.S. Appl. No. 15/849,362, Non Final Office Action dated Oct. 5, 2018”, 9 pgs.
“U.S. Appl. No. 15/849,362, Notice of Allowance dated Jul. 18, 2019”, 10 pgs.
“U.S. Appl. No. 15/849,362, Notice of Allowance dated Nov. 20, 2019”, 11 pgs.
“U.S. Appl. No. 15/849,362, Preliminary Amendment filed Feb. 22, 2018”, 7 pgs.
“U.S. Appl. No. 15/849,362, Response filed Jan. 7, 2019 to Non Final Office Action dated Oct. 5, 2018”, 14 pgs.
“U.S. Appl. No. 15/849,362, Response filed Jul. 2, 2019 to Final Office Action dated May 2, 2019”, 10 pgs.
“U.S. Appl. No. 13/310,417, Response filed Dec. 8, 2014 to Non Final Office Action dated Sep. 8, 2014”, 11 pgs.
“U.S. Appl. No. 14/949,549, Final Office Action dated Oct. 27, 2016”, 14 pgs.
“U.S. Appl. No. 14/949,549, Non Final Office Action dated Apr. 20, 2016”, 14 pgs.
“Australian Application Serial No. 2006272510, Office Action dated Oct. 22, 2010”, 3 pgs.
“Australian Application Serial No. 2006272510, Response filed Oct. 6, 2011 to Office Action dated Oct. 22, 2011”, 15 pgs.
“Australian Application Serial No. 2012200701, Office Action dated Aug. 21, 2013”, 2 pgs.
“Australian Application Serial No. 2012200701, Response filed Dec. 12, 2013 to Office Action dated Aug. 21, 2013”, 33 pgs.
“Australian Application Serial No. 2013270518, Response filed May 25, 2016 to Subsequent Examiners Report dated Feb. 1, 2016”, 13 pgs.
“Australian Application Serial No. 2013270518, Subsequent Examiners Report dated Feb. 1, 2016”, 2 pgs.
“Australian Application Serial No. 2013270518, Subsequent Examiners Report dated Jun. 7, 2016”, 2 pgs.
“Casefinder Manual, Ch. 1: Overview; Ch. 8: Hyperlinking”, [Online], Retrieved from the Internet: <URL: http://web.archive.org/web/20040419155315/http://www.casefinder.com/downloads/manual-5.00.pdf>, (Archived Apr. 19, 2004), 13 pgs.
“East Text Search Training”, (Jan. 2000), 155 pgs.
“European Application Serial No. 05775617.3, Extended European Search Report dated Mar. 24, 2009”, 8 pgs.
“European Application Serial No. 06800464.7, Amendment filed Mar. 21, 2011”, 7 pgs.
“European Application Serial No. 06800464.7, Examination Notification Art. 94(3) dated May 2, 2014”, 8 pgs.
“European Application Serial No. 06800464.7, Extended European Search Report dated Aug. 24, 2010”, 8 pgs.
“European Application Serial No. 06800464.7, Response filed Sep. 11, 2014 to Office Action dated May 2, 2014”, 16 pgs.
“European Application Serial No. 06800464.7, Summons to Attend Oral Proceedings mailed Oct. 10, 2017”, 10 pgs.
“International Application Serial No. PCT/US2005/026768, Demand mailed Mar. 7, 2007”, 9 pgs.
“International Application Serial No. PCT/US2005/026768, International Preliminary Report on Patentability dated Mar. 29, 2007”, 8 pgs.
“International Application Serial No. PCT/US2005/026768, International Search Report dated Mar. 7, 2007”, 5 pgs.
“International Application Serial No. PCT/US2005/026768, Written Opinion dated Mar. 7, 2007”, 5 pgs.
“International Application Serial No. PCT/US2006/020950, International Preliminary Report on Patentability dated Dec. 13, 2007”, 6 pgs.
“International Application Serial No. PCT/US2006/020950, International Search Report dated Feb. 5, 2007”, 2 pgs.
“International Application Serial No. PCT/US2006/020950, Written Opinion dated Feb. 5, 2007”, 4 pgs.
“International Application Serial No. PCT/US2006/029456, International Preliminary Report on Patentability dated Feb. 7, 2008”, 9 pgs.
“International Application Serial No. PCT/US2006/029456, International Search Report dated Oct. 1, 2007”, 5 pgs.
“International Application Serial No. PCT/US2006/029456, Written Opinion dated Oct. 1, 2007”, 7 pgs.
“International Search Report and Written Opinion in PCT/US05/26768, dated Mar. 7, 2007”, 15 pgs.
“Notice from the European Patent Office dated Oct. 1, 2007 concerning business methods”, Official Journal of the European Patent Office, 30(11), (Nov. 1, 2007), 592-593.
“PatentPleeze Overview”, [Online], Retrieved from the Internet: <URL: http://web.archive.org/web/20060824063540/web.ncf.ca/ex133/patnow.pdf>, (Archived Aug. 24, 2006), 33 pgs.
“Using Citation Link”, Delphion, [Online], Retrieved from the Internet: <URL: http://web.archive.org/web/20041204224023/www.delphion.com/help/citelink_help>, (Archived Dec. 4, 2004), 10 pgs.
“What is PAIR?”, USPTO, [Online], Retrieved from the Internet: <URL: http://web.archive.org/web/20040606224528/pair.uspto.gov/cgi-bin/final/help.pl>, (Archived Jun. 6, 2004), 9 pgs.
Broekstra, Joen, et al., “Sesame: A Generic Architecture for Storing and Querying RDF and RDF Schema”, Int'l Semantic Web Conference (ISWC). Lecture Notes in Computer Science, vol. 2342. Springer, Berlin, Heidelberg, (2002), 16 pgs.
Chang, Muchiu, “Sun Tzu and sustainable competitive advantage”, IEEE Int'l Engineering Management Conference, vol. 1, (Oct. 18-21, 2004), 153-157.
Davis, Lee, “The Strategic Use of Patents in International Business”, The 28th Annual EIBA Conference, Athens, Greece, (Dec. 2002), 27 pgs.
East, T. W, “Patent Claims—How to Keep Track of Them”, IEEE Aerospace and Electronic Systems Magazine, 10(8), (Aug. 1995), 32-33.
Fall, C.J., et al., “Literature Survey: Issue to be considered in the automatic classifications of patents”, World Intellectual Property Organization, (Oct. 2002), 64 pgs.
Gruber, T R, et al., “A Translation Approach to Portable Ontology Specifications”, KSL Report KSL-92-71, Knowledge Systems Laboratory, Stanford University, (1993), 24 pgs.
Hoover, A. E, “Electronic Filing Top 10 Wish List”, IP Today, (Jul. 2006), 2 pgs.
Hutzell, Paula, “Image File Wrapper (IFW) Processing”, USPTO PPT Presentation, (May 8, 2003), 25 pgs.
Indukuri, Kishore Varma, et al., “Similarity Analysis of Patent Claims Using Natural Language Processing Techniques”, International Conference on Computational Intelligence and Multimedia Applications, (2007), 169-175.
Langan-Fox, Janice, “Team Mental Models: Techniques, Methods, and Analytic Approaches”, The Journal of the Human Factors and Ergonomics Society, vol. 42, No. 2, (2000), 30 pgs.
Larkey, L. S, “A Patent Search and Classification System”, Proc. of the 4th ACM Conference of Digital Libraries, (1999), 179-187.
Larkey, Leah S, et al., “Collection Selection and Results Merging with Topically Organized U.S. Patents and TREC Data”, Proc. of the 9th Int'l Conference on Information and Knowledge Management, (2000), 8 pgs.
Luo, Si, et al., “A Semisupervised Learning Method to Merge Search Engine results”, ACM Transactions on Information Systems, vol. 21, No. 4, (Oct. 2002), 35 pgs.
Madrid, Juan M, et al., “Incorporating Conceptual Matching in Search”, Proc. of the 11th Conference on Information and Knowledge Management, [Online] Retrieved from the Internet: <crazybody.com>, (2002), 17 pgs.
Mahesh, K., “Ontology Development for Machine Translation: Ideology and Methodology”, Technical Report MCCS-96-292, Computing Research Laboratory, New Mexico State University, (1996), 87 pgs.
Mase, H., et al., “Proposal of Two-Stage Patent Retrieval Method Considering the Claim Structure”, ACM Transactions on Asian Language Information Processing (TALIP), 4(2), (Jun. 2005), 190-206.
Quinn, B., “Internet Access to Patent Application Files Now Available”, Press Release, [Online]. Retrieved from the Internet: <URL: http://web.archive.org/web/20040813210925/http://www.uspto.gov/web/offices/com/speeches/04-13.htm>, (Aug. 2, 2004), 1 pg.
Sheremetyeva, S., et al., “Generating Patent Claims from Interactive Input”, Proc. of the 8th International Workshop on Natural Language Generation (INLG), (Jun. 1996), 61-70.
Sheremetyeva, S., et al., “Knowledge Elicitation for Authoring Patent Claims”, IEEE Computer, 29(7), (Jul. 1996), 57-63.
Sheremetyeva, S., “Natural Language Analysis of Patent Claims”, Proc. of the ACL-2003 Workshop on Patent Corpus Processing, (2003), 66-73.
Sheremetyeva, S., et al., “On Creating Metadata with Authoring Tools”, Proc. of the ECAI Workshop on Semantic Authoring, Annotation and Knowledge Markup (SAAKM), (Jul. 2002), 22-26.
Sheremetyeva, Svetlana, “Natural Language Analysis of Patent Claims”, Department of Computational Linguistics Copenhagen Business School, Bernhard Bangs Alle 17 B, DK—Denmark., (2000).
Von-Wun, Soo, et al., “A Cooperative Multi-Agent Platform for Invention based on Ontology and Patent Document Analysis”, The 9th International Conference on Computer Supported Cooperative Work in Design Proceedings, (2005), 411-416.
Woods, W. A, “Conceptual Indexing: A Better Way to Organize Knowledge”, Sun Microsystems, Inc., (1997), 99 pgs.
U.S. Appl. No. 12/605,030, filed Oct. 23, 2009, Patent Mapping.
U.S. Appl. No. 15/801,056 U.S. Pat. No. 10,546,273, filed Nov. 1, 2017, Patent Mapping.
U.S. Appl. No. 13/253,936, filed Oct. 5, 2011, Patent Mapping.
U.S. Appl. No. 13/253,941, filed Oct. 5, 2011, Prior Art Management.
U.S. Appl. No. 13/464,598 U.S. Pat. No. 9,904,726, filed May 4, 2012, Apparatus and Method for Automated and Assisted Patent Claim Mapping and Expense Planning.
U.S. Appl. No. 15/722,868, filed Oct. 2, 2017, Apparatus and Method for Automated and Assisted Patent Claim Mapping and Expense Planning.
U.S. Appl. No. 13/309,200 U.S. Pat. No. 10,268,731, filed Dec. 1, 2011, Patent Mapping.
U.S. Appl. No. 16/352,364, filed Mar. 13, 2019, Patent Mapping.
U.S. Appl. No. 13/310,279, filed Dec. 2, 2011, Patent Mapping.
U.S. Appl. No. 13/310,322, filed Dec. 2, 2011, Patent Mapping.
U.S. Appl. No. 13/310,368 U.S. Pat. No. 10,628,429, filed Dec. 2, 2011, Patent Mapping.
U.S. Appl. No. 16/814,911, filed Mar. 10, 2020, Patent Mapping.
U.S. Appl. No. 13/310,417, filed Dec. 2, 2011, Patent Mapping.
U.S. Appl. No. 13/310,452, filed Dec. 2, 2011, Patent Mapping.
U.S. Appl. No. 14/826,018 U.S. Pat. No. 9,858,319, filed Aug. 13, 2015, Patent Mapping.
U.S. Appl. No. 15/849,362 U.S. Pat. No. 10,614,082, filed Dec. 20, 2017, Patent Mapping.
“U.S. Appl. No. 13/109,080, Response filed Mar. 28, 2013 to Final Office Action dated Nov. 5, 2012”, 10 pgs.
“U.S. Appl. No. 13/253,801, Final Office Action dated Jul. 18, 2013”, 39 pgs.
“U.S. Appl. No. 13/253,801, Final Office Action dated Oct. 1, 2012”, 41 pgs.
“U.S. Appl. No. 13/253,801, Non Final Office Action dated Apr. 10, 2013”, 37 pgs.
“U.S. Appl. No. 13/253,801, Non Final Office Action dated Aug. 2, 2012”, 42 pgs.
“U.S. Appl. No. 13/253,801, Notice of Allowance dated May 16, 2014”, 10 pgs.
“U.S. Appl. No. 13/253,801, Notice of Allowance dated Jul. 16, 2014”, 9 pgs.
“U.S. Appl. No. 13/253,801, Preliminary Amendment filed Oct. 5, 2011”, 4 pgs.
“U.S. Appl. No. 13/253,801, Response filed Mar. 20, 2013 to Final Office Action dated Oct. 1, 2012”, 16 pgs.
“U.S. Appl. No. 13/253,801, Response filed Jul. 5, 2013 to Non Final Office Action dated Apr. 10, 2013”, 18 pgs.
“U.S. Appl. No. 13/253,801, Response filed Sep. 7, 2012 to Non Final Office Action dated Aug. 2, 2012”, 17 pgs.
“U.S. Appl. No. 13/253,801, Response filed Nov. 18, 2013 to Final Office Action dated Jul. 18, 2013”, 16 pgs.
“U.S. Appl. No. 13/253,811, Appeal Decision mailed Nov. 1, 2017”, 21 pgs.
“U.S. Appl. No. 13/253,811, Final Office Action dated Apr. 11, 2016”, 14 pgs.
“U.S. Appl. No. 13/253,811, Final Office Action dated Jul. 2, 2013”, 12 pgs.
“U.S. Appl. No. 13/253,811, Final Office Action dated Dec. 9, 2014”, 13 pgs.
“U.S. Appl. No. 13/253,811, Non Final Office Action dated May 1, 2014”, 13 pgs.
“U.S. Appl. No. 13/253,811, Non Final Office Action dated Jun. 18, 2015”, 12 pgs.
“U.S. Appl. No. 13/253,811, Non Final Office Action dated Oct. 18, 2012”, 12 pgs.
“U.S. Appl. No. 13/253,811, Preliminary Amendment filed Oct. 5, 2011”, 4 pgs.
“U.S. Appl. No. 13/253,811, Response filed Jan. 2, 2014 to Final Office Action dated Jul. 2, 2013”, 13 pgs.
“U.S. Appl. No. 13/253,811, Response filed Mar. 18, 2013 to Non Final Office Action dated Oct. 18, 2012”, 13 pgs.
“U.S. Appl. No. 13/253,811, Response filed Apr. 9, 2015 to Final Office Action dated Dec. 9, 2014”, 11 pgs.
“U.S. Appl. No. 13/253,811, Response filed Oct. 1, 2014 to Non Final Office Action dated May 1, 2014”, 10 pgs.
“U.S. Appl. No. 13/253,811, Response filed Oct. 19, 2015 to Non Final Office Action dated Jun. 18, 2015”, 9 pgs.
“U.S. Appl. No. 13/253,825, Examiner Interview Summary dated Aug. 13, 2013”, 3 pgs.
“U.S. Appl. No. 13/253,825, Final Office Action dated Aug. 14, 2013”, 35 pgs.
“U.S. Appl. No. 13/253,825, Final Office Action dated Nov. 21, 2012”, 33 pgs.
“U.S. Appl. No. 13/253,825, Non Final Office Action dated Feb. 11, 2014”, 45 pgs.
“U.S. Appl. No. 13/253,825, Non Final Office Action dated Apr. 25, 2013”, 32 pgs.
“U.S. Appl. No. 13/253,825, Non Final Office Action dated Aug. 3, 2012”, 32 pgs.
“U.S. Appl. No. 13/253,825, Notice of Allowance dated Oct. 23, 2014”, 16 pgs.
“U.S. Appl. No. 13/253,825, Preliminary Amendment filed Oct. 5, 2011”, 4 pgs.
“U.S. Appl. No. 13/253,825, Response filed Mar. 20, 2013 to Final Office Action dated Nov. 21, 2012”, 17 pgs.
“U.S. Appl. No. 13/253,825, Response filed Jun. 11, 2014 to Non Final Office Action dated Feb. 11, 2014”, 16 pgs.
“U.S. Appl. No. 13/253,825, Response filed Jul. 18, 2013 to Non Final Office Action dated Apr. 25, 2013”, 16 pgs.
“U.S. Appl. No. 13/253,825, Response filed Oct. 3, 2013 to Final Office Action dated Aug. 14, 2013”, 15 pgs.
“U.S. Appl. No. 13/253,846, Advisory Action dated Sep. 10, 2013”, 3 pgs.
“U.S. Appl. No. 13/253,846, Decision on Pre-Appeal Brief Request mailed Dec. 26, 2013”, 2 pgs.
“U.S. Appl. No. 13/253,846, Final Office Action dated Apr. 12, 2016”, 22 pgs.
“U.S. Appl. No. 13/253,846, Final Office Action dated Jun. 19, 2013”, 21 pgs.
“U.S. Appl. No. 13/253,846, Final Office Action dated Oct. 23, 2014”, 19 pgs.
“U.S. Appl. No. 13/253,846, Non Final Office Action dated Mar. 7, 2014”, 20 pgs.
“U.S. Appl. No. 13/253,846, Non Final Office Action dated Jun. 25, 2015”, 19 pgs.
“U.S. Appl. No. 13/253,846, Non Final Office Action dated Oct. 29, 2012”, 12 pgs.
“U.S. Appl. No. 13/253,846, Pre-Appeal Brief Request filed Oct. 21, 2013”, 4 pgs.
“U.S. Appl. No. 13/253,846, Response filed Jan. 23, 2015 to Final Office Action dated Oct. 23, 2014”, 15 pgs.
“U.S. Appl. No. 13/253,846, Response filed Mar. 26, 2013 to Non Final Office Action dated Oct. 29, 2012”, 17 pgs.
“U.S. Appl. No. 13/253,846, Response filed Aug. 16, 2013 to Final Office Action dated Jun. 19, 2013”, 16 pgs.
“U.S. Appl. No. 13/253,846, Response filed Oct. 26, 2015 to Non Final Office Action dated Jun. 25, 2015”, 14 pgs.
“U.S. Appl. No. 13/253,931, Advisory Action dated Sep. 11, 2013”, 3 pgs.
“U.S. Appl. No. 13/253,931, Examiner Interview Summary dated Sep. 12, 2013”, 2 pgs.
“U.S. Appl. No. 13/253,931, Final Office Action dated Jun. 20, 2013”, 11 pgs.
“U.S. Appl. No. 13/253,931, Final Office Action dated Dec. 3, 2014”, 11 pgs.
“U.S. Appl. No. 13/253,931, Non Final Office Action dated Apr. 18, 2014”, 11 pgs.
“U.S. Appl. No. 13/253,931, Non Final Office Action dated Nov. 28, 2012”, 13 pgs.
“U.S. Appl. No. 13/253,931, Response filed Mar. 26, 2013 to Non Final Office Action dated Nov. 28, 2012”, 13 pgs.
“U.S. Appl. No. 13/253,931, Response filed Aug. 16, 2013 to Final Office Action dated Jun. 20, 2013”, 14 pgs.
“U.S. Appl. No. 13/253,931, Response filed Sep. 18, 2014 to Non Final Office Action dated Apr. 18, 2014”, 9 pgs.
“U.S. Appl. No. 13/253,931, Response filed Sep. 20, 2013 to Final Office Action dated Jun. 20, 2013”, 13 pgs.
“U.S. Appl. No. 13/253,936, Appeal Brief filed Jan. 8, 2016”, 10 pgs.
“U.S. Appl. No. 13/253,936, Appeal Brief filed Jun. 8, 2015”, 13 pgs.
“U.S. Appl. No. 13/253,936, Appeal Decision mailed Aug. 3, 2017”, 10 pgs.
“U.S. Appl. No. 13/253,936, Corrected Notice of Allowability dated Sep. 21, 2020”, 2 pgs.
“U.S. Appl. No. 13/253,936, Corrected Notice of Allowability dated Sep. 25, 2020”, 2 pgs.
“U.S. Appl. No. 13/253,936, Corrected Notice of Allowability dated Oct. 2, 2020”, 2 pgs.
“U.S. Appl. No. 13/253,936, Examiner's Answer to Appeal Brief mailed Jun. 23, 2016”, 6 pgs.
“U.S. Appl. No. 13/253,936, Final Office Action dated Feb. 4, 2015”, 14 pgs.
“U.S. Appl. No. 13/253,936, Final Office Action dated Apr. 9, 2020”, 14 pgs.
“U.S. Appl. No. 13/253,936, Final Office Action dated Jul. 11, 2018”, 18 pgs.
“U.S. Appl. No. 13/253,936, Non Final Office Action dated Feb. 7, 2018”, 16 pgs.
“U.S. Appl. No. 13/253,936, Non Final Office Action dated Jun. 18, 2014”, 14 pgs.
“U.S. Appl. No. 13/253,936, Non Final Office Action dated Aug. 9, 2019”, 15 pgs.
“U.S. Appl. No. 13/253,936, Non Final Office Action dated Oct. 8, 2015”, 15 pgs.
“U.S. Appl. No. 13/253,936, Notice of Allowance dated Aug. 5, 2020 ”, 13pgs.
“U.S. Appl. No. 13/253,936, Reply Brief filed Aug. 23, 2016”, 4 pgs.
“U.S. Appl. No. 13/253,936, Response filed Feb. 10, 2020 to Non Final Office Action dated Aug. 9, 2019”, 10 pgs.
“U.S. Appl. No. 13/253,936, Response Filed Jun. 7, 2018 to Non Final Office Action dated Feb. 7, 2018”, 13 pgs.
“U.S. Appl. No. 13/253,936, Response filed Jul. 9, 2020 to Final Office Action dated Apr. 9, 2020”, 12 pgs.
“U.S. Appl. No. 13/253,936, Response filed Oct. 3, 2017 to Appeal Decision mailed Aug. 3, 2017”, 8 pgs.
“U.S. Appl. No. 13/253,936, Response filed Dec. 16, 2014 to Non Final Office Action dated Jun. 18, 2014”, 9 pgs.
“U.S. Appl. No. 13/253,941, Final Office Action dated Dec. 26, 2014”, 18 pgs.
“U.S. Appl. No. 13/253,941, Response filed Nov. 7, 2014 to Non Final Office Action dated May 7, 2014”, 10 pgs.
“U.S. Appl. No. 13/253,846, Response filed Aug. 6, 2014 to Non Final Office Action dated Mar. 7, 2014”, 14 pgs.
“U.S. Appl. No. 13/255,825, Response filed Oct. 30, 2012 to Non Final Office Action dated Aug. 3, 2012”, 18 pgs.
“U.S. Appl. No. 13/275,707, Appeal Brief filed May 26, 2015”, 37 pgs.
“U.S. Appl. No. 13/275,707, Examiner Interview Summary dated Apr. 8, 2015”, 3 pgs.
“U.S. Appl. No. 13/275,707, Examiner Interview Summary dated Jul. 29, 2013”, 3 pgs.
“U.S. Appl. No. 13/275,707, Examiner Interview Summary dated Nov. 28, 2014”, 2 pgs.
“U.S. Appl. No. 13/275,707, Final Office Action dated Jul. 30, 2013”, 90 pgs.
“U.S. Appl. No. 13/275,707, Final Office Action dated Nov. 28, 2014”, 57 pgs.
“U.S. Appl. No. 13/275,707, Non Final Office Action dated Apr. 30, 2014”, 94 pgs.
“U.S. Appl. No. 13/275,707, Non Final Office Action dated Dec. 12, 2012”, 39 pgs.
“U.S. Appl. No. 13/275,707, Notice of Allowance dated Jul. 27, 2015”, 19 pgs.
“U.S. Appl. No. 13/275,707, Response filed Jan. 30, 2014 to Final Office Action dated Jul. 30, 2013”, 14 pgs.
“U.S. Appl. No. 13/275,707, Response filed Apr. 9, 2013 to Non Final Office Action dated Dec. 12, 2012”, 14 pgs.
“U.S. Appl. No. 13/275,707, Response filed Aug. 28, 2014 to Non Final Office Action dated Apr. 30, 2014”, 11 pgs.
“U.S. Appl. No. 13/309,039, Advisory Action dated Apr. 16, 2013”, 3 pgs.
“U.S. Appl. No. 13/309,039, Appeal Brief filed Jul. 5, 2013”, 18 pgs.
“U.S. Appl. No. 13/309,039, Appeal Brief filed Sep. 3, 2014”, 20 pgs.
“U.S. Appl. No. 13/309,039, Appeal Decision mailed Sep. 23, 2016”, 10 pgs.
“U.S. Appl. No. 13/309,039, Decision on Pre-Appeal Brief Request mailed Jun. 7, 2013”, 2 pgs.
“U.S. Appl. No. 13/309,039, Examiner Interview Summary dated Oct. 23, 2012”, 3 pgs.
“U.S. Appl. No. 13/309,039, Examiner's Answer to Appeal Brief mailed Nov. 14, 2014”, 11 pgs.
“U.S. Appl. No. 13/309,039, Final Office Action dated Jan. 2, 2013”, 11 pgs.
“U.S. Appl. No. 13/309,039, Non Final Office Action dated Sep. 11, 2012”, 9 pgs.
“U.S. Appl. No. 13/309,039, Non Final Office Action dated Sep. 11, 2013”, 13 pgs.
“U.S. Appl. No. 13/309,039, Pre-Appeal Brief Request filed May 6, 2013”, 5 pgs.
“U.S. Appl. No. 13/309,039, Response filed Jan. 14, 2015 to Examiner's Answer to Appeal Brief mailed Nov. 14, 2014”, 8 pgs.
“U.S. Appl. No. 13/309,039, Response filed Apr. 1, 2013 to Final Office Action dated Jan. 2, 2013”, 13 pgs.
“U.S. Appl. No. 13/309,039, Response filed Oct. 22, 2012 to Non Final Office Action dated Sep. 11, 2012”, 13 pgs.
“U.S. Appl. No. 13/309,060, Advisory Action dated Apr. 18, 2014”, 3 pgs.
“U.S. Appl. No. 13/309,060, Appeal Brief filed Apr. 21, 2015”, 16 pgs.
“U.S. Appl. No. 13/309,060, Appeal Decision mailed Aug. 25, 2017”, 9 pgs.
“U.S. Appl. No. 13/309,060, Final Office Action dated Oct. 11, 2013”, 13 pgs.
“U.S. Appl. No. 13/309,060, Final Office Action dated Nov. 28, 2014”, 13 pgs.
“U.S. Appl. No. 13/309,060, Final Office Action dated Dec. 7, 2012”, 10 pgs.
“U.S. Appl. No. 13/309,060, Non Final Office Action dated May 30, 2013”, 11 pgs.
“U.S. Appl. No. 13/309,060, Non Final Office Action dated Jun. 17, 2014”, 12 pgs.
“U.S. Appl. No. 13/309,060, Non Final Office Action dated Aug. 1, 2012”, 8 pgs.
“U.S. Appl. No. 13/309,060, Notice of Allowance dated Nov. 27, 2017”, 7 pgs.
“U.S. Appl. No. 13/309,060, Response filed Mar. 4, 2014 to Final Office Action dated Dec. 24, 2013”, 11 pgs.
“U.S. Appl. No. 13/309,060, Response filed Apr. 8, 2013 to Final Office Action dated Dec. 7, 2012”, 10 pgs.
“U.S. Appl. No. 13/309,060, Response filed Aug. 15, 2013 to Non Final Office Action dated May 30, 2013”, 10 pgs.
“U.S. Appl. No. 13/309,060, Response filed Sep. 20, 2012 to Non Final Office Action dated Aug. 1, 2012”, 8 pgs.
“U.S. Appl. No. 13/309,060, Response filed Nov. 17, 2014 to Non Final Office Action dated Jun. 17, 2014”, 6 pgs.
“U.S. Appl. No. 13/309,080, Appeal Brief filed May 20, 2014”, 12 pgs.
“U.S. Appl. No. 13/309,080, Appeal Decision mailed May 27, 2016”, 8 pgs.
“U.S. Appl. No. 13/309,080, Examiner Interview Summary dated Sep. 5, 2012”, 3 pgs.
“U.S. Appl. No. 13/309,080, Examiner Interview Summary dated Dec. 17, 2012”, 3 pgs.
“U.S. Appl. No. 13/309,080, Final Office Action dated Oct. 11, 2013”, 11 pgs.
“U.S. Appl. No. 13/309,080, Final Office Action dated Nov. 5, 2012”, 8 pgs.
“U.S. Appl. No. 13/309,080, Non Final Office Action dated Jun. 10, 2013”, 12 pgs.
“U.S. Appl. No. 13/309,080, Non Final Office Action dated Jul. 30, 2012”, 8 pgs.
“U.S. Appl. No. 13/309,080, Notice of Non-Compliant Appeal Brief mailed Jun. 3, 2014”, 2 pgs.
“U.S. Appl. No. 13/309,080, Notice of Panel Decision from Pre-Appeal Brief Review mailed May 1, 2014”, 2 pgs.
“U.S. Appl. No. 13/309,080, Pre-Appeal Brief Request for Review filed Mar. 4, 2014”, 5 pgs.
“U.S. Appl. No. 13/309,080, Response filed Aug. 15, 2013 to Non Final Office Action dated Jun. 10, 2013”, 14 pgs.
“U.S. Appl. No. 13/309,080, Response filed Aug. 29, 2012 to Non Final Office Action dated Jul. 30, 2012”, 11 pgs.
“U.S. Appl. No. 13/309,080, Response filed Sep. 30, 2014 to Examiner's Answer to Appeal Brief mailed Aug. 1, 2014”, 5 pgs.
“U.S. Appl. No. 13/309,080, Examiner's Answer to Appeal Brief mailed Aug. 1, 2014”, 7 pgs.
“U.S. Appl. No. 13/309,102, Appeal Brief filed Jun. 5, 2014”, 19 pgs.
“U.S. Appl. No. 13/309,102, Appeal Decision mailed Jun. 1, 2016”, 13 pgs.
“U.S. Appl. No. 13/309,102, Decision on Pre-Appeal Brief Request mailed May 1, 2014”, 2 pgs.
“U.S. Appl. No. 13/309,102, Examiner's Answer to Appeal Brief mailed Jul. 31, 2014”, 6 pgs.
“U.S. Appl. No. 13/309,102, Final Office Action dated Nov. 27, 2013”, 12 pgs.
“U.S. Appl. No. 13/309,102, Final Office Action dated Dec. 10, 2012”, 10 pgs.
“U.S. Appl. No. 13/309,102, Non Final Office Action dated May 30, 2013”, 13 pgs.
“U.S. Appl. No. 13/309,102, Non Final Office Action dated Aug. 6, 2012”, 7 pgs.
“U.S. Appl. No. 13/309,102, Pre-Appeal Brief Request filed Mar. 26, 2014”, 5 pgs.
“U.S. Appl. No. 13/309,102, Response filed Apr. 9, 2013 to Final Office Action dated Dec. 10, 2012”, 13 pgs.
“U.S. Appl. No. 13/309,102, Response filed Sep. 5, 2013 to Non Final Office Action dated May 30, 2013”, 13 pgs.
“U.S. Appl. No. 13/309,102, Response filed Sep. 25, 2012 to Non Final Office Action dated Aug. 6, 2012”, 10 pgs.
“U.S. Appl. No. 13/309,102, Response filed Sep. 30, 2014 to Examiner's Answer to Appeal Brief mailed Jul. 31, 2014”, 4 pgs.
“U.S. Appl. No. 13/309,127, Appeal Brief filed Apr. 30, 2014”, 19 pgs.
“U.S. Appl. No. 13/309,127, Appeal Decision mailed Jul. 26, 2017”, 16 pgs.
“U.S. Appl. No. 13/309,127, Final Office Action dated Oct. 10, 2012”, 18 pgs.
“U.S. Appl. No. 13/309,127, Final Office Action dated Oct. 22, 2013”, 19 pgs.
“U.S. Appl. No. 13/309,127, Non Final Office Action dated Apr. 25, 2013”, 19 pgs.
“U.S. Appl. No. 13/309,127, Non Final Office Action dated Jun. 25, 2012”, 15 pgs.
“U.S. Appl. No. 13/309,127, Pre-Appeal Brief Request filed Feb. 28, 2014”, 5 pgs.
“U.S. Appl. No. 13/309,127, Response filed Mar. 25, 2013 to Final Office Action dated Oct. 10, 2012”, 13 pgs.
“U.S. Appl. No. 13/309,127, Response filed Jul. 24, 2013 to Non Final Office Action dated Apr. 25, 2013”, 11 pgs.
“U.S. Appl. No. 13/309,127, Response filed Aug. 1, 2012 to Non Final Office Action dated Jun. 25, 2012”, 15 pgs.
“U.S. Appl. No. 13/309,127, Response filed Sep. 30, 2014 to Examiner's Answer to Appeal Brief mailed Jul. 31, 2014”, 6 pgs.
“U.S. Appl. No. 13/309,127, Examiner's Answer to Appeal Brief mailed Jul. 31, 2014”, 9 pgs.
“U.S. Appl. No. 13/309,146, Advisory Action dated Feb. 12, 2015”, 3 pgs.
“U.S. Appl. No. 13/309,146, Appeal Brief filed Jan. 12, 2015”, 10 pgs.
“U.S. Appl. No. 13/309,146, Appeal Decision mailed Jun. 1, 2016”, 10 pgs.
“U.S. Appl. No. 13/309,146, Final Office Action dated Jun. 27, 2014”, 14 pgs.
“U.S. Appl. No. 13/309,146, Non Final Office Action dated Dec. 19, 2013”, 10 pgs.
“U.S. Appl. No. 13/309,146, Response filed Apr. 24, 2014 to Non Final Office Action dated Dec. 19, 2013”, 10 pgs.
“U.S. Appl. No. 13/309,166, Advisory Action dated Dec. 1, 2017”, 3 pgs.
“U.S. Appl. No. 13/309,166, Appeal Brief filed Sep. 1, 2016”, 17 pgs.
“U.S. Appl. No. 13/309,166, Examiner Interview Summary dated May 20, 2015”, 3 pgs.
“U.S. Appl. No. 13/309,166, Examiner Interview Summary dated Nov. 13, 2017”, 5 pgs.
“U.S. Appl. No. 13/309,166, Final Office Action dated Aug. 10, 2017”, 15 pgs.
“U.S. Appl. No. 13/309,166, Final Office Action dated Sep. 1, 2015”, 11 pgs.
“U.S. Appl. No. 13/309,166, Final Office Action dated Nov. 13, 2013”, 9 pgs.
“U.S. Appl. No. 13/309,166, Non Final Office Action dated Feb. 13, 2015”, 10 pgs.
“U.S. Appl. No. 13/309,166, Non Final Office Action dated Feb. 22, 2013”, 9 pgs.
“U.S. Appl. No. 13/309,166, Non Final Office Action dated May 23, 2013”, 9 pgs.
“U.S. Appl. No. 13/309,166, Non Final Office Action dated Dec. 29, 2016”, 15 pgs.
“U.S. Appl. No. 13/309,166, Response filed Jan. 10, 2018 to Final Office Action dated Aug. 10, 2017”, 9 pgs.
“U.S. Appl. No. 13/309,166, Response filed Apr. 11, 2014 to Final Office Action dated Nov. 13, 2013”, 13 pgs.
“U.S. Appl. No. 13/309,166, Response filed May 1, 2017 to Non Final Office Action dated Dec. 29, 2016”, 14 pgs.
“U.S. Appl. No. 13/309,166, Response filed May 13, 2015 to Non Final Office Action dated Feb. 13, 2015”, 8 pgs.
“U.S. Appl. No. 13/309,166, Response filed May 14, 2013 to Non Final Office Action dated Feb. 22, 2013”, 10 pgs.
“U.S. Appl. No. 13/309,166, Response filed Aug. 15, 2013 to Non Final Office Action dated May 23, 2013”, 11 pgs.
“U.S. Appl. No. 13/309,166, Response filed Nov. 6, 2017 to Final Office Action dated Aug. 10, 2017”, 11 pgs.
“U.S. Appl. No. 13/310,279, Appeal Brief filed Sep. 11, 2019”, 19 pgs.
“U.S. Appl. No. 13/310,279, Final Office Action dated Jun. 24, 2021”, 25 pgs.
“U.S. Appl. No. 13/310,279, Final Office Action dated Jul. 23, 2020”, 23 pgs.
“U.S. Appl. No. 13/310,279, Non Final Office Action dated Jan. 31, 2020”, 25 pgs.
“U.S. Appl. No. 13/310,279, Non Final Office Action dated Dec. 24, 2020”, 24 pgs.
“U.S. Appl. No. 13/310,279, Response filed Mar. 24, 2021 to Non Final Office Action dated Dec. 24, 2020”, 11 pgs.
“U.S. Appl. No. 13/310,279, Response filed Jun 1, 2020 to Non Final Office Action dated Jan. 31, 2020”, 11 pgs.
“U.S. Appl. No. 13/310,279, Response filed Nov. 23, 2020 to Final Office Action dated Jul. 23, 2020”, 11 pgs.
“U.S. Appl. No. 13/312,507, Final Office Action dated Nov. 21, 2014”, 12 pgs.
“U.S. Appl. No. 13/312,507, Non Final Office Action dated Mar. 26, 2015”, 13 pgs.
“U.S. Appl. No. 13/312,507, Non Final Office Action dated May 27, 2014”, 13 pgs.
“U.S. Appl. No. 13/312,507, Notice of Allowance dated Oct. 30, 2015”, 19 pgs.
“U.S. Appl. No. 13/312,507, PTO Response to Rule 312 Communication dated Feb. 16, 2016”, 2 pgs.
“U.S. Appl. No. 13/312,507, Response filed Feb. 19, 2015 to Final Office Action dated Nov. 21, 2014”, 10 pgs.
“U.S. Appl. No. 13/312,507, Response filed Jul. 27, 2015 to Non Final Office Action dated Mar. 26, 2015”, 11 pgs.
“U.S. Appl. No. 13/312,507, Response filed Oct. 27, 2014 to Non Final Office Action dated May 27, 2014”, 10 pgs.
“U.S. Appl. No. 13/351,533, Final Office Action dated Jan. 23, 2013”, 33 pgs.
“U.S. Appl. No. 13/351,533, Final Office Action dated Mar. 20, 2015”, 28 pgs.
“U.S. Appl. No. 13/351,533, Non Final Office Action dated Feb. 4, 2014”, 26 pgs.
“U.S. Appl. No. 13/351,533, Non Final Office Action dated May 25, 2012”, 20 pgs.
“U.S. Appl. No. 13/351,533, Non Final Office Action dated Sep. 6, 2012”, 26 pgs.
“U.S. Appl. No. 13/351,533, Non Final Office Action dated Oct. 14, 2014”, 25 pgs.
“U.S. Appl. No. 13/351,533, Response filed Jan. 14, 2015 to Non Final Office Action dated Oct. 14, 2014”, 18 pgs.
“U.S. Appl. No. 13/351,533, Response filed Apr. 10, 2013 to Final Office Action dated Jan. 23, 2013”, 12 pgs.
“U.S. Appl. No. 13/351,533, Response Filed Jun. 3, 2014 to Non Final Office Action dated Feb. 4, 2014”, 14 pgs.
“U.S. Appl. No. 13/351,533, Response filed Jun. 8, 2012 to Non Final Office Action dated May 25, 2012”, 12 pgs.
“U.S. Appl. No. 13/351,533, Response filed Nov. 20, 2012 to Non Final Office Action dated Sep. 6, 2012”, 14 pgs.
“U.S. Appl. No. 13/408,877, Appeal Brief filed Nov. 10, 2015”, 14 [gs/.
“U.S. Appl. No. 13/408,877, Appeal Decision mailed Sep. 6, 2017”, 23 pgs.
“U.S. Appl. No. 13/408,877, Final Office Action dated May 8, 2015”, 24 pgs.
“U.S. Appl. No. 13/408,877, Final Office Action dated Sep. 3, 2013”, 27 pgs.
“U.S. Appl. No. 13/408,877, Non Final Office Action dated Feb. 28, 2013”, 22 pgs.
“U.S. Appl. No. 13/408,877, Non Final Office Action dated Oct. 8, 2014”, 26 pgs.
“U.S. Appl. No. 13/408,877, Response filed Jan. 8, 2015 to Non Final Office Action dated Oct. 8, 2014”, 15 pgs.
“U.S. Appl. No. 13/408,877, Response filed May 16, 2013 to Non Final Office Action dated Feb. 28, 2013”, 17 pgs.
“U.S. Appl. No. 13/408,877, Response filed Dec. 3, 2013 to Final Office Action dated Sep. 3, 2013”, 18 pgs.
“U.S. Appl. No. 13/408,917, Appeal Brief filed Jan. 19, 2016”, 18 pgs.
“U.S. Appl. No. 13/408,917, Appeal Decision mailed Sep. 12, 2017”, 19 pgs.
“U.S. Appl. No. 13/408,917, Decision on Pre-Appeal Brief Request mailed Sep. 17, 2015”, 2 pgs.
“U.S. Appl. No. 13/408,917, Examiner Interview Summary dated Aug. 28, 2013”, 3 pgs.
“U.S. Appl. No. 13/408,917, Final Office Action dated May 11, 2015”, 23 pgs.
“U.S. Appl. No. 13/408,917, Final Office Action dated Aug. 28, 2013”, 24 pgs.
“U.S. Appl. No. 13/408,917, Non Final Office Action dated Mar. 5, 2013”, 18 pgs.
“U.S. Appl. No. 13/408,917, Non Final Office Action dated Oct. 9, 2014”, 24 pgs.
“U.S. Appl. No. 13/408,917, Pre-Appeal Brief Request filed Aug. 12, 2015”, 5 pgs.
“U.S. Appl. No. 13/408,917, Reply Brief filed Oct. 3, 2016”, 4 pgs.
“U.S. Appl. No. 13/408,917, Response filed Jan. 9, 2015 to Non Final Office Action dated Oct. 9, 2014”, 13 pgs.
“U.S. Appl. No. 13/408,917, Response filed Jun. 3, 2013 to Non Final Office Action dated Mar. 5, 2013”, 16 pgs.
“U.S. Appl. No. 13/408,917, Response filed Nov. 27, 2013 to Final Office Action dated Aug. 28, 2013”, 17 pgs.
“U.S. Appl. No. 13/409,189 Examiner's Answer mailed Jan. 4, 2017”, 12 pgs.
“U.S. Appl. No. 13/409,189, Appeal Brief filed Oct. 25, 2016”, 30 pgs.
“U.S. Appl. No. 13/409,189, Appeal Decision mailed Dec. 18, 2017”, 14 pgs.
“U.S. Appl. No. 13/409,189, Examiner Interview Summary dated Aug. 30, 2013”, 3 pgs.
“U.S. Appl. No. 13/409,189, Final Office Action dated May 8, 2015”, 23 pgs.
“U.S. Appl. No. 13/409,189, Final Office Action dated Aug. 28, 2013”, 22 pgs.
“U.S. Appl. No. 13/409,189, Non Final Office Action dated Feb. 28, 2013”, 20 pgs.
“U.S. Appl. No. 13/409,189, Non Final Office Action dated Oct. 9, 2014”, 23 pgs.
“U.S. Appl. No. 13/409,189, Non Final Office Action dated Dec. 23, 2015”, 12 pgs.
“U.S. Appl. No. 13/409,189, Response filed Jan. 9, 2015 to Non Final Office Action dated Oct. 9, 2014”, 13 pgs.
“U.S. Appl. No. 13/409,189, Response filed May 28, 2013 to Non Final Office Action dated Feb. 28, 2013”, 16 pgs.
“U.S. Appl. No. 13/409,189, Response filed Sep. 8, 2005 to Final Office Action dated May 8, 2015”, 16 pgs.
“U.S. Appl. No. 13/409,189, Response filed Nov. 27, 2013 to Final Office Action dated Aug. 28, 2013”, 15 pgs.
“U.S. Appl. No. 13/422,750, Final Office Action dated Jun. 15, 2016”, 37 pgs.
“U.S. Appl. No. 13/422,750, Final Office Action dated Aug. 7, 2013”, 29 pgs.
“U.S. Appl. No. 13/422,750, Non Final Office Action dated Apr. 1, 2014”, 32 pgs.
“U.S. Appl. No. 13/422,750, Non Final Office Action dated Apr. 12, 2013”, 19 pgs.
“U.S. Appl. No. 13/422,750, Non Final Office Action dated Oct. 31, 2014”, 32 pgs.
“U.S. Appl. No. 13/422,750, Response filed Jan. 30, 2014 to Final Office Action dated Aug. 7, 2013”, 13 pgs.
“U.S. Appl. No. 13/422,750, Response filed Feb. 2, 2015 to Non Final Office Action dated Oct. 31, 2014”, 11 pgs.
“U.S. Appl. No. 13/422,750, Response filed Jul. 12, 2013 to Non Final Office Action dated Apr. 12, 2013”, 14 pgs.
“U.S. Appl. No. 13/422,750, Response filed Sep. 2, 2014 to Non Final Office Action dated Apr. 1, 2014”, 10 pgs.
“U.S. Appl. No. 13/424,682, Non Final Office Action dated Apr. 11, 2013”, 6 pgs.
“U.S. Appl. No. 13/424,682, Notice of Allowance dated Jul. 30, 2013”, 13 pgs.
“U.S. Appl. No. 13/424,682, Response filed Jul. 5, 2013 to Non Final Office Action dated Apr. 11, 2013”, 10 pgs.
“U.S. Appl. No. 13/424,705, Advisory Action dated Nov. 29, 2013”, 3 pgs.
“U.S. Appl. No. 13/424,705, Final Office Action dated Sep. 11, 2015”, 28 pgs.
“U.S. Appl. No. 13/424,705, Final Office Action dated Sep. 19, 2013”, 11 pgs.
“U.S. Appl. No. 13/424,705, Non Final Office Action dated Apr. 12, 2013”, 14 pgs.
“U.S. Appl. No. 13/424,705, Non Final Office Action dated Jun. 16, 2014”, 21 pgs.
“U.S. Appl. No. 13/424,705, Non Final Office Action dated Jul. 23, 2014”, 21 pgs.
“U.S. Appl. No. 13/424,705, Response filed Jul. 12, 2013 to Non Final Office Action dated Apr. 12, 2013”, 11 pgs.
“U.S. Appl. No. 13/424,705, Response filed Nov. 19, 2013 to Final Office Action dated Sep. 19, 2013”, 11 pgs.
“U.S. Appl. No. 13/424,705, Response filed Nov. 24, 2014 to Non Final Office Action dated Jul. 23, 2014”, 14 pgs.
“U.S. Appl. No. 13/452,400, Examiner Interview Summary dated Sep. 11, 2013”, 3 pgs.
“U.S. Appl. No. 13/452,400, Final Office Action dated Jul. 5, 2013”, 25 pgs.
“U.S. Appl. No. 13/452,400, Final Office Action dated Jul. 30, 2015”, 32 pgs.
“U.S. Appl. No. 13/452,400, Non Final Office Action dated Jan. 15, 2015”, 24 pgs.
“U.S. Appl. No. 13/452,400, Non Final Office Action dated Oct. 5, 2012”, 23 pgs.
“U.S. Appl. No. 13/452,400, Preliminary Amendment filed May 16, 2012”, 3 pgs.
“U.S. Appl. No. 13/452,400, Response filed Jan. 7, 2013 to Non Final Office Action dated Oct. 5, 2012”, 12 pgs.
“U.S. Appl. No. 13/452,400, Response filed Apr. 15, 2015 to Non Final Office Action dated Jan. 15, 2015”, 31 pgs.
“U.S. Appl. No. 13/452,400, Response filed Sep. 26, 2013 to Final Office Action”, 12 pgs.
“U.S. Appl. No. 13/553,572 Response filed Jun. 3, 2013 to Non-Final Office Action dated Mar. 7, 2013”, 17 pgs.
“U.S. Appl. No. 13/553,572, Final Office Action dated Jul. 2, 2013”, 12 pgs.
“U.S. Appl. No. 13/553,572, Non Final Office Action dated Mar. 7, 2013”, 14 pgs.
“U.S. Appl. No. 13/553,572, Non Final Office Action dated Nov. 4, 2014”, 13 pgs.
“U.S. Appl. No. 13/553,572, Preliminary Amendment filed Sep. 17, 2012”, 7 pgs.
“U.S. Appl. No. 13/553,572, Response filed Jan. 2, 2014 to Final Office Action dated Jul. 2, 2013”, 15 pgs.
“U.S. Appl. No. 13/553,596, Advisory Action dated Apr. 29, 2015”, 3 pgs.
“U.S. Appl. No. 13/553,596, Final Office Action dated Feb. 4, 2015”, 16 pgs.
“U.S. Appl. No. 13/553,596, Non Final Office Action dated Jul. 28, 2014”, 14 pgs.
“U.S. Appl. No. 13/553,596, Non Final Office Action dated Aug. 31, 2015”, 17 pgs.
“U.S. Appl. No. 13/553,596, Response filed Apr. 6, 2015 to Final Office Action dated Feb. 4, 2015”, 10 pgs.
“U.S. Appl. No. 13/553,596, Response filed Nov. 26, 2014 to Non Final Office Action dated Jul. 28, 2014”, 8 pgs.
“U.S. Appl. No. 13/594,002, Final Office Action dated Mar. 19, 2015”, 36 pgs.
“U.S. Appl. No. 13/594,002, Final Office Action dated Jul. 31, 2013”, 24 pgs.
“U.S. Appl. No. 13/594,002, Final Office Action dated Sep. 6, 2016”, 55 pgs.
“U.S. Appl. No. 13/594,002, Non Final Office Action dated Feb. 27, 2013”, 21 pgs.
“U.S. Appl. No. 13/594,002, Non Final Office Action dated Nov. 30, 2015”, 41 pgs.
“U.S. Appl. No. 13/594,002, Non Final Office Action dated Dec. 4, 2014”, 29 pgs.
“U.S. Appl. No. 13/594,002, Response filed Mar. 3, 2015 to Non Final Office Action dated Dec. 4, 2014”, 23 pgs.
“U.S. Appl. No. 13/594,002, Response filed May 14, 2013 to Non Final Office Action dated Feb. 27, 2013”, 11 pgs.
“U.S. Appl. No. 13/594,002, Response filed May 31, 2016 to Non Final Office Action dated Nov. 30, 2015”, 12 pgs.
“U.S. Appl. No. 13/594,002, Response filed Aug. 19, 2015 to Final Office Action dated Mar. 19, 2015”, 14 pgs.
“U.S. Appl. No. 13/594,002, Response filed Oct. 28, 2013 to Final Office Action dated Jul. 31, 2013”, 11 pgs.
“U.S. Appl. No. 13/679,830, Examiner Interview Summary dated Sep. 28, 2017”, 3 pgs.
“U.S. Appl. No. 13/679,830, Final Office Action dated Jan. 31, 2014”, 27 pgs.
“U.S. Appl. No. 13/679,830, Final Office Action dated Apr. 23, 2015”, 36 pgs.
“U.S. Appl. No. 13/679,830, Final Office Action dated Sep. 9, 2016”, 59 pgs.
“U.S. Appl. No. 13/679,830, Final Office Action dated Nov. 15, 2017”, 98 pgs.
“U.S. Appl. No. 13/679,830, Non Final Office Action dated Jan. 4, 2016”, 61 pgs.
“U.S. Appl. No. 13/679,830, Non Final Office Action dated Jun. 14, 2013”, 21 pgs.
“U.S. Appl. No. 13/679,830, Non Final Office Action dated Jun. 15, 2017”, 82 pgs.
“U.S. Appl. No. 13/679,830, Non Final Office Action dated Nov. 6, 2014”, 36 pgs.
“U.S. Appl. No. 13/679,830, Response filed Feb. 6, 2015 to Non Final Office Action dated Nov. 6, 2014”, 12 pgs.
“U.S. Appl. No. 13/679,830, Response filed Feb. 9, 2017 to Final Office Action dated Sep. 9, 2016”, 19 pgs.
“U.S. Appl. No. 13/679,830, Response filed Jun. 12, 2014 to Final Office Action dated Jan. 31, 2014”, 16 pgs.
“U.S. Appl. No. 13/679,830, Response filed Jul. 5, 2016 to Non Final Office Action dated Jan. 4, 2016”, 11 pgs.
“U.S. Appl. No. 13/679,830, Response filed Sep. 23, 2015 to Final Office Action dated Apr. 23, 2015”, 14 pgs.
“U.S. Appl. No. 13/679,830, Response Filed Oct. 16, 2017 to Non Final Office Action dated Jun. 15, 2017”, 13 pgs.
“U.S. Appl. No. 13/679,830, Response filed Nov. 14, 2013 to Non Final Office Action dated Jun. 14, 2013”, 14 pgs.
“U.S. Appl. No. 14/010,400, Appeal Decision mailed Nov. 3, 2017”, 16 pgs.
“U.S. Appl. No. 14/094,542, Final Office Action dated Feb. 9, 2015”, 6 pgs.
“U.S. Appl. No. 14/094,542, Final Office Action dated Sep. 2, 2015”, 6 pgs.
“U.S. Appl. No. 14/094,542, Non Final Office Action dated Feb. 12, 2014”, 7 pgs.
“U.S. Appl. No. 14/094,542, Non Final Office Action dated May 19, 2015”, 5 pgs.
“U.S. Appl. No. 14/094,542, Non Final Office Action dated Aug. 15, 2014”, 7 pgs.
“U.S. Appl. No. 14/094,542, Response filed Jan. 15, 2015 to Non Final Office Action dated Aug. 15, 2014”, 10 pgs.
“U.S. Appl. No. 14/094,542, Response filed May 11, 2015 to Final Office Action dated Feb. 9, 2015”, 12 pgs.
“U.S. Appl. No. 14/094,542, Response filed Jul. 14, 2014 to Non Final Office Action dated Feb. 12, 2014”, 12 pgs.
“U.S. Appl. No. 14/094,542, Response filed Aug. 19, 2015 to Non Final Office Action dated May 19, 2015”, 12 pgs.
“U.S. Appl. No. 14/540,346, Non Final Office Action dated Aug. 24, 2015”, 16 pgs.
“U.S. Appl. No. 14/540,346, Notice of Allowance dated Mar. 18, 2016”, 7 pgs.
“U.S. Appl. No. 14/540,346, Preliminary Amendment filed Dec. 11, 2014”, 8 pgs.
“U.S. Appl. No. 14/540,346, Response filed Dec. 23, 2015 to Non Final Office Action dated Aug. 24, 2015”, 7 pgs.
“U.S. Appl. No. 14/608,520, Appeal Brief filed May 12, 2017”, 25 pgs.
“U.S. Appl. No. 14/608,520, Appeal Decision mailed Nov. 27, 2017”, 14 pgs.
“U.S. Appl. No. 14/608,520, Final Office Action dated Oct. 12, 2016”, 44 pgs.
“U.S. Appl. No. 14/608,520, Non Final Office Action dated Mar. 18, 2016”, 39 pgs.
“U.S. Appl. No. 14/608,520, Non Final Office Action dated Oct. 15, 2015”, 19 pgs.
“U.S. Appl. No. 14/608,520, Preliminary Amendment filed Feb. 26, 2015”, 10 pgs.
“U.S. Appl. No. 14/608,520, Response filed Jan. 15, 2016 to Non Final Office Action dated Oct. 15, 2015”, 9 pgs.
“U.S. Appl. No. 14/608,520, Response filed Sep. 19, 2016 to Non Final Office Action dated Mar. 18, 2016”, 12 pgs.
“U.S. Appl. No. 14/628,941, Appeal Brief filed May 12, 2017”.
“U.S. Appl. No. 14/628,941, Appeal Decision mailed Dec. 6, 2017”, 14 pgs.
“U.S. Appl. No. 14/628,941, Final Office Action dated Oct. 13, 2016”, 43 pgs.
“U.S. Appl. No. 14/628,941, Non Final Office Action dated Mar. 18, 2016”, 38 pgs.
“U.S. Appl. No. 14/628,941, Non Final Office Action dated Sep. 24, 2015”, 21 pgs.
“U.S. Appl. No. 14/628,941, Preliminary Amendment filed Feb. 26, 2015”, 9 pgs.
“U.S. Appl. No. 14/628,941, Response filed Sep. 19, 2016 to Non Final Office Action dated Mar. 18, 2016”, 12 pgs.
“U.S. Appl. No. 14/628,941, Response filed Dec. 23, 2015 to Non Final Office Action dated Sep. 24, 2015”, 9 pgs.
“U.S. Appl. No. 14/750,559, Final Office Action dated Nov. 29, 2018”, 22 pgs.
“U.S. Appl. No. 14/750,559, Non Final Office Action dated Feb. 27, 2018”, 15 pgs.
“U.S. Appl. No. 14/750,559, Non Final Office Action dated Jun. 13, 2019”, 11 pgs.
“U.S. Appl. No. 14/750,559, Response filed Jul. 27, 2018 to Non Final Office Action dated Feb. 27, 2018”, 12 pgs.
“U.S. Appl. No. 14/750,559, Response filed Mar. 29, 2019 to Final Office Action dated Nov. 29, 2018”, 13 pgs.
“U.S. Appl. No. 14/750,559, Response filed Sep. 13, 2019 to Non-Final Office Action dated Jun. 13, 2019”, 12 pgs.
“U.S. Appl. No. 14/826,006, Advisory Action dated May 10, 2017”, 3 pgs.
“U.S. Appl. No. 14/826,006, Final Office Action dated Jan. 17, 2017”, 13 pgs.
“U.S. Appl. No. 14/826,006, Final Office Action dated Jan. 19, 2018”, 17 pgs.
“U.S. Appl. No. 14/826,006, Non Final Office Action dated Jun. 2, 2016”, 11 pgs.
“U.S. Appl. No. 14/826,006, Non Final Office Action dated Aug. 18, 2017”, 16 pgs.
“U.S. Appl. No. 14/826,006, Preliminary Amendment filed Aug. 28, 2015”, 6 pgs.
“U.S. Appl. No. 14/826,006, Response filed Apr. 18, 2017 to Final Office Action dated Jan. 17, 2017”, 13 pgs.
“U.S. Appl. No. 14/826,006, Response filed Nov. 1, 2016 to Non Final Office Action dated Jun. 2, 2016”, 7 pgs.
“U.S. Appl. No. 14/826,006, Response filed Nov. 17, 2017 to Non Final Office Action dated Aug. 18, 2017”, 11 pgs.
“U.S. Appl. No. 14/826,025, Final Office Action dated May 15, 2017”, 13 pgs.
“U.S. Appl. No. 14/826,025, Non Final Office Action dated Aug. 25, 2016”, 14 pgs.
“U.S. Appl. No. 14/826,025, Preliminary Amendment filed Aug. 28, 2015”, 6 pgs.
“U.S. Appl. No. 14/826,025, Response filed Jan. 25, 2017 to Non Final Office Action dated Aug. 25, 2016”, 13 pgs.
“U.S. Appl. No. 14/952,699, Non Final Office Action dated Jun. 8, 2016”, 9 pgs.
“U.S. Appl. No. 14/952,699, Notice of Allowability dated Oct. 7, 2016”, 5 pgs.
“U.S. Appl. No. 14/952,699, Notice of Allowance dated Jan. 9, 2017”, 9 pgs.
“U.S. Appl. No. 14/952,699, Notice of Allowance dated Sep. 19, 2016”, 8 pgs.
“U.S. Appl. No. 14/952,699, Preliminary Amendment filed May 27, 2016”, 8 pgs.
“U.S. Appl. No. 14/952,699, Response filed Sep. 8, 2016 to Non Final Office Action dated Jun. 8, 2016”, 8 pgs.
“U.S. Appl. No. 15/057,047, Non Final Office Action dated Sep. 29, 2016”, 19 pgs.
“U.S. Appl. No. 15/057,047, Notice of Allowance dated Feb. 10, 2017”, 11 pgs.
“U.S. Appl. No. 15/057,047, Preliminary Amendment filed Sep. 15, 2016”, 5 pgs.
“U.S. Appl. No. 15/057,047, Response Filed Dec. 29, 2016 to Non Final Office Action dated Sep. 29, 2016”, 11 pgs.
“U.S. Appl. No. 15/211,917, Non Final Office Action dated Nov. 15, 2017”, 13 pgs.
“U.S. Appl. No. 15/211,917, Preliminary Amendment filed Dec. 2, 2016”, 8 pgs.
“U.S. Appl. No. 15/595,629, Preliminary Amendment filed Jul. 24, 2017”, 8 pgs.
“U.S. Appl. No. 15/619,150, Preliminary Amendment filed Aug. 28, 2017”, 8 pgs.
“U.S. Appl. No. 15/722,868, Advisory Action dated Apr. 8, 2020”, 3 pgs.
“U.S. Appl. No. 15/722,868, Examiner Interview Summary dated Aug. 27, 2020”, 3 pgs.
“U.S. Appl. No. 15/722,868, Final Office Action dated Jan. 28, 2020”, 23 pgs.
“U.S. Appl. No. 15/722,868, Non Final Office Action dated May 18, 2020”, 26 pgs.
“U.S. Appl. No. 15/722,868, Notice of Allowance dated Sep. 3, 2020”, 22 pgs.
“U.S. Appl. No. 15/722,868, Response filed Jan. 6, 2020 to Non Final Office Action dated Oct. 4, 2019”, 12 pgs.
“U.S. Appl. No. 15/722,868, Response filed Mar. 30, 2020 to Final Office Action dated Jan. 28, 2020”, 11 pgs.
“U.S. Appl. No. 15/722,868, Response filed Aug. 18, 2020 to Non Final Office Action dated May 18, 2020”, 12 pgs.
“U.S. Appl. No. 16/352,364, Corrected Notice of Allowability dated Feb. 26, 2021”, 7 pgs.
“U.S. Appl. No. 16/352,364, Non Final Office Action dated Aug. 27, 2020”, 10 pgs.
“U.S. Appl. No. 16/352,364, Notice of Allowance dated Feb. 8, 2021”, 10 pgs.
“U.S. Appl. No. 16/352,364, Preliminary Amendment filed Dec. 27, 2019”, 8 pgs.
“U.S. Appl. No. 16/352,364, Response filed Jan. 27, 2021 to Non Final Office Action dated Aug. 27, 2020”, 9 pgs.
“U.S. Appl. No. 16/814,911, Non Final Office Action dated Oct. 15, 2021”, 14 pgs.
“U.S. Appl. No. 17/103,870, Preliminary Amendment filed Feb. 9, 2021”, 8 pgs.
“U.S. Appl. No. 17/125,979, Preliminary Amendment filed Apr. 7, 2021”, 9 pgs.
“U.S. Appl. No. 13/408,877, Reply Brief mailed Aug. 8, 2016”, 5 pgs.
“ClaimMaster Software User Guide”, ClaimMaster Software LLP, (2009), 36 pgs.
“Definition of Timeline”, [Online] Retrieved from the Internet: <URL: https://www.yourdictionary.com/>, (Mar. 17, 2015), 1 pg.
“Google Definition: System”, [Online] Retrieved from the Internet: <URL: http://www.google.com>, (Retrieved Aug. 13, 2012), 3 pgs.
“Module”, Dictionary.com, [Online] Retrieved from Internet: <URL: http://dictionary.reference.com/browse/module>, (Retrieved Aug. 13, 2012), 5 pgs.
“Patent Rank: A Network-Dominant Logic for Innovation”, Submitted to Marketing Science, manuscript MKSC—Oct. 10—0356, (Oct. 2010), 36 pgs.
“PatentOptimizer”, LexisNexis, (2009), 2 pgs.
Brinn, Michael W, et al., “Investigation of forward citation count as a patent analysis method”, Proceedings of the 2003 Systems and Information Engineering Design Symposium, (2003), 6 pgs.
Fenton, Gillian M., et al., “Freedom to Operate: The Law Firms Approach and Role”, In: Intellectual Property Management in Health and Agricultural Innovation: A Handbook of Best Practices, [online]. [retrieved on Mar. 17, 2015]. Retrieved from the Internet: <URL: www.iphandbook.org/handbook/ch14/p04/index_print.html>, (2007), 11 pgs.
Gipp, Bela, et al., “Comparative Evaluation of Text- and Citation based Plagiarism Detection Approaches using GuttenPlag”, [Online] Retrieved from the Internet: <URL: http://gipp.com/wp-content/papercite-data/pdf/gipp11b.pdf>, (2011), 4 pgs.
Hall, et al., “Market Value and Patent Citations”, The RAND Journal of Economics, vol. 36, No. 1, (2005), 16-38.
Jagalla, Christopher, “Searching USPTO Assignments on the Web”, (Nov. 20, 2010), 4 pgs.
Mary, Ellen Mogee, et al., “Patent co-citation analysis of Eli Lilly & Co. patents”, Expert Opinion on Therapeutic Patents, (Feb. 25, 2005).
Paul, Stockwell, et al., “Use of an automatic content analysis tool: Atechnique for seeing both local and global scope”, Int. J. Human-Computer Studies 67, (2009), 424-436.
“U.S. Appl. No. 13/310,279, Response filed Oct. 25, 2021 to Final Office Action dated Jun. 24, 2021”, 11 pgs.
U.S. Appl. No. 16/814,911, Notice of Allowance dated Feb. 11, 2022, 10 pgs.
Related Publications (1)
Number Date Country
20200279222 A1 Sep 2020 US
Provisional Applications (1)
Number Date Country
61107930 Oct 2008 US
Continuations (2)
Number Date Country
Parent 15801056 Nov 2017 US
Child 16730678 US
Parent 12605030 Oct 2009 US
Child 15801056 US