...
The figure below shows the overall system design with communication channels for queries and data fetching. If IPscreener is installed locally external internet Internet access is only used to verify status and/or to fetch patent data, related PDF and images responding to the API outcome. If the IPscreener shall screen additional prior art data from e.g. the IPM system or from the company archives (such as e.g. invention disclosures or specific non-patent related literature) a specific access loop has to be engaged. Thus, to populate the search engine and classifier engine either the client or the IPM platform push the requested data to the IPscreener platform or alternatively IPscreener is granted access to the local company/IPM APIs to fetch data for the processing procedures. No data from the IPM system is stored in raw format in our search engine or classifier, the only data stored is index-structure data. There are two general options at hand where either the IPM platform is installed locally at the client premises or hosted externally at the IPM premises, both fully compliable with the IPscreener standard installation and it's functionality.
IPM system internally
...
The hardware backend need to provide at leats least 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 needed for best performance of semantic AI search engine, data fetching and accessing of database indexes. Eventually local indexes of separate internal material, such as invention disclosures etc, may need additional disk storage, which is to be communicated after specific analysis. For smooth access to external patent data the IPscreener installation needs a recommended access to Internet of 1 GB/s.
...
In order to perform a smooth and maximum stability of the software OS platform we recommend Ubuntu version 18 or higher (alternatively CentOS version 7 or higher). Furthermore, the installation requires Docker version 17 or higher. We recommend to define defining and provide providing associated mail server information for enabling alert, support and surveillance procedures.
...
The security settings of a local IPscreener installtion installtaion needs access to route traffic from hub.docker.com both port 80 and 443. This traffic is needed to access and download associated third party material related to patent dopcuments documents and registers. Furthermore, the installation environment needs access to route traffic from IPscreener data center domains *.api.uppdragshuset.se, also via both port 80 and 443. The IPscreener web server uses for communication port 80 or, if local encryption is needed, also of port 443 with your specified SSL keys provided.
...
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 patent 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.
...