Page History

...

The figure below shows the overall system design with communication channels for queries and data fetching.  If The green arrow shows the data flow for sending text query requests and for retrieving associated results. For more information on the specific query procedures and format, please consult the IPscreener API access guidelines. If IPscreener is installed locally external Internet access is only used to verify status and/or to fetch patent data, related PDF and images responding to the API outcome. If 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.   ThusThus, 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 standard installation and it's functionality.

...

The security settings of a local IPscreener 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 documents and registers. Furthermore, the installation environment needs access to route traffic from the IPscreener data center domains *.api.uppdragshusetipscreener.secom, 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.

...