...
...
| Figure A: Notification of document availability | Figure B: OSF checking document availability |
|---|
| The following diagram describes the exchange flows for registration and retrieval of documents hosted in WIPO DAS by notification to OSF | The following diagram describes the exchange flows for registration and retrieval of documents hosted in WIPO DAS |
|
|
...
and the OSF checking on regular basis statuses of retrievals requests | | draw.io Diagram |
|---|
| border | true |
|---|
| |
|---|
| diagramName | Documents-hosted-by-WIPO-DAS |
|---|
| simpleViewer | true |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| diagramDisplayName | Figure A |
|---|
| lbox | true |
|---|
| diagramWidth | 659 |
|---|
| revision | 1 |
|---|
|
|
|
|
Figure A: Notification of document availability
| draw.io Diagram |
|---|
| border | true |
|---|
| |
|---|
| diagramName | DAS Retrievals by checking document availability |
|---|
| simpleViewer | false |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| lbox | true |
|---|
| diagramWidth | 659 |
|---|
| revision | 1 |
|---|
|
|
|
| Column |
|---|
| a.- New DAS exchange API | Page Tree |
|---|
| root | a.- New DAS exchange API |
|---|
| page | a.- Initial private_key_jwt registration process |
|---|
|
|
|
...
Exchange flow to register document
| Section |
|---|
| Column |
|---|
|
| Step | API Request | Notes |
|---|
| (1a) - OFF requests a |
|
|
...
| pre-signed URL from WIPO DAS to upload a file identified by a file |
|
|
...
...
| Not required if OFF keeps the actual document file content in its own digital library | | (1b) - OFF uploads the document file content using a |
|
|
...
| pre-signed URL given in step (step 1a) | File upload via PUT | | (1c) - OFF requests document registration to WIPO DAS by referring to the uploaded file content by the corresponding file |
|
|
...
...
| Column |
|---|
|  Image Added
|
|
| Note |
|---|
| Steps (1a) and (1b) are not required if the OFF keeps the actual document file content in its own digital library
|
...
Exchange flow to correct filing date or parent application details in which the foreign priority document is held
...
| Section |
|---|
| Column |
|---|
|
| Step | API Request | Notes |
|---|
| (1c) - OFF requests document registration to WIPO DAS by specifying the new document attributes |
|
|
...
...
...
Exchange flow to replace document content for correction purpose
| Section |
|---|
| Column |
|---|
|
| Step | API Request | Notes |
|---|
| (1a) - OFF requests a |
|
|
...
| pre-signed URL from WIPO DAS to upload a file identified by a file id |
|
|
...
...
|
| (1b) - OFF uploads the corrected document file content using a |
|
|
...
pre-signed URL given in step (1a) |
|
| | (1c) - OFF requests document registration to WIPO DAS by referring to the uploaded file content by the corresponding file |
|
|
...
...
...
Exchange flow to retrieve document hosted in WIPO DAS
...
| Section |
|---|
| Column |
|---|
|
| Step | API Request | Notes |
|---|
| (2a) - OSF sends a document retrieval request to WIPO DAS and receives a request acknowledgement |
|
|
...
...
|
| | (2b) - WIPO DAS prepares the requested document for download and notifies the OSF of the document availability (i.e. Figure A) by referring to the request acknowledgement id returned in step (2a) |
|
|
...
| POST /das/v1/requests/notifications |
|
|
...
...
| Alternatively , OSF may use the check status (i.e. Figure B) to download the document content when it is reported as available by WIPO DAS (i.e. GET /das/v1/requests/retrievals |
|
|
...
| ) | (2c) - OSF retrieves file location URL from WIPO DAS to download the document file |
|
|
...
...
...
| Downloads can be repeated while the requested document is not deleted from WIPO DAS | (2d) - OSF downloads file from WIPO DAS |
|
| | (2e) - Optionally OSF deletes the download files from the DAS transit |
|
|
...
...
|
| Note |
|---|
| If OSF does not delete the downloaded file, WIPO DAS will delete it after a pre-defined period (e.g. 1 week) |
|
|
The following diagram describes the exchange flows for registration and retrieval of documents hosted in WIPO DAS and the OSF checking on regular basis statuses of retrievals requests
...
Figure B: OSF checking document availability
Documents registered and kept in the OFF digital library
The following diagram describes the exchange flows for registration and retrieval of documents hosted in OFF
...
Exchange flow to retrieve document from the OFF digital library
- OSF sends a document retrieval request to WIPO DAS and receives a request acknowledgement id issued by WIPO DAS (i.e. POST /das/v1/requests/retrievals)
- WIPO DAS forwards the retrieval request to the OFF (i.e. POST /das/v1/requests/retrievals)
- OFF prepares the requested document for download and notify WIPO DAS of the document availability by referring to the request acknowledgement id returned by WIPO DAS (i.e. POST /das/v1/requests/notifications)
- WIPO DAS retrieves the file location URL based on (i.e. GET /das/v1/requests/files/url-downloads)
- WIPO DAS download the document file content from OFF
- WIPO DAS prepares the requested document for download by OSF and notifies the OSF of the document availability by referring to the request acknowledgement id returned in step 1 (i.e. POST /das/v1/requests/notifications)
- OSF retrieves the file location URL for document download by referring to the request acknowledgement id returned in step 1 (i.e. GET /das/v1/requests/files/url-downloads)
- OSF uses the given file location URL obtained in step 7 to download the document file content
- Optionally OSF deletes the download files from the DAS transit zone (i.e. DELETE /das/v1/requests/files)
Note: if OSF does not delete the downloaded file, WIPO DAS will delete it after a pre-defined period (e.g. 1 week)
Documents can be registered by OFF using WIPO DAS as transit zone to exchange big-sized documents
The following diagram describes the exchange flows for registration and retrieval of documents hosted in OFF but big-sized documents can be transmitted through the DAS transit zone
...
...
Exchange flow to retrieve document transmitted by OFF to WIPO DAS transit zone
- OSF sends a document retrieval request to WIPO DAS and receives a request acknowledgement id issued by WIPO DAS (i.e. POST /das/v1/requests/retrievals)
- WIPO DAS forwards the retrieval request to the OFF and receives a request acknowledgement id issued by OFF (i.e. POST /das/v1/requests/retrievals)
- OFF requests a presigned url from WIPO DAS to upload a file and receives the file id from WIPO DAS (i.e. POST /das/v1/requests/url-uploads)
- OFF uploads the requested document file content into DAS transit zone using a presigned url given in step 3
- OFF notifies WIPO DAS of the document availability by referring to the request acknowledgement id returned in step 2 (i.e. POST /das/v1/requests/notifications)
- WIPO DAS prepares the requested document for download by OSF and notifies the OSF of the document availability by referring to the request acknowledgement id returned in step 1 (i.e. POST /das/v1/requests/notifications)
- OSF retrieves the file location URL to download the document file content by referring to the request acknowledgement id returned in step 1 (i.e. GET /das/v1/requests/files/url-downloads)
- OSF downloads the file using the URL obtained in step 8
- Optionally OSF deletes the download file from the DAS transit zone (i.e. DELETE /das/v1/requests/files)
| Note |
|---|
| If OSF does not delete the downloaded file, WIPO DAS will delete it after a pre-defined period (e.g. 1 week)
|
