General


This is a technical documentation that describes the IPscreener Local installation and ineraction with the AutoMatch search engine. The specification is intended for those who are experienced in programming software applications. This documentation is subject to continuous change, however normally backward compatibility is maintained.

API updates / change log

This document will be updated with the latest information regarding the installation onfrastructure and functionality. Notifications of changes will be sent to registered users via email.

Service Management and Support


The support is managed by the IPscreener team and contact is encouraged for any inquiries, as well for technical matters as for user specific questions. For any questions, please contact our support team by sending an email to support@ipscreener.com.

Terms of Use


The terms of use for the local installation are regulated by agreements and the general terms for web services. We apply a strict fair usage principle and in endeavoring to make the IPscreener install is stable for everyone to use, we place restrictions on the number of requests you can make to the service. If you exceed the limits set out we may throttle, suspend or terminate your access to external patant data downloading. The set limit may be adjusted by us when updating the IPscreener core. For more information please refer to the general terms, which sent upon request from support@ipscreener.com

Disclaimer


Introduction to IPscreener


IPscreener is a decision support tool based on semantic technology used for automatic prior art retrieval. When feeding a raw text to the IPscreener service, the AutoMatch search engine converts this text to a fingerprint representation. This representation is used to fetch the most similar documents reflecting the context of the query text. This is done from a specially tailored global reference database of patent documents. Thus, relevant prior art is identified and presented to a user in a client platform without any manual interaction needed. Therefore, each review of an idea along the innovation process is given a support for faster decisions, better priority of resources and at a higher quality.


The IPscreener installation is implemented as a standalone-module that is easily integrated with any existing commercial or internal patent administration system. The API service is built using REST principles which ensures predictable URLs that supports easy connectivity and communication. For a descriptive overview of the data flow see Fig. 1. The IPscreener REST API follows standard HTTP rules, enabling a wide range of HTTP clients to be able to interact with the service.

Hardware installation environment

The hardware backend need to provide at leats 4 CPU cores with a minimum of 64 GB of dedicated RAM. We recommend to use Solid State Disks (SSD) for the installation environment, granting a minimum of 1TB of dedicated storage. This is ineeed for best performance of database indexes. Eventual local indexeds of separate internal mateiral sucha as inevntikon disclosures etc may need addioalt disk sapce, to be communicated after specifc analysis.


Software environment

In order to perform a smooth and maximum stability of the software OS platform we recommned CentOS or Ubuntu od at least version (??). Furthernore, the isntallation requires Docker of at least verion ??)

If installation required mail support, please provide with your mail server.



Firewall

Access to route traffic from hub.docker.com both port 80 and 443.

Access to route traffic from IPscreener data center domains *.api.uppdragshuset.se both port 80 and 443.

Server output uses port 80 or if needed local encryption port 443 with your SSL keys.




Operational installation

Recommend to have a planning meeting first. 

Upload feature database index as pre-installation step a few days ahead.

Installation itself with validation takes around 1 working day, depends on features.