Presently, there are 4 possible use cases in the current existing technical arrangements of TDA/pdx. The below use cases are examples of how to replace the TDA-based exchange using the new DAS Rest API.
Use Case 1 - Document Registration by OFF to WIPO DAS
| Existing flow operated with TDA/pdx | New flow using DAS Rest API | |
|---|---|---|
| IP5 (OFF) --- dasRegRequest ---> WIPO DAS. As a result, OFF receives an ackId | POST https://{wipo-hostname}/am/oauth2/access_token | IP5 (OFF) uses the OFF private key to generate the JWT client assertion (see more details) to request a valid access-token to WIPO DAS |
| POST https://{wipo-hostname}/requests/registrations | IP5 (OFF) sends a document registration request without document content (similarly to the TDA/pdx), receives an ackId and the request status | |
| WIPO DAS ---- dasRegResponse --> IP5 (OFF). As a result, OFF receives the ackId and related registration status | ||
Use Case 2 - Document De-registration by OFF to WIPO DAS
There is a special arrangement to allow the OFF to deregister a document by sending a dasRegRequest request with the registered document details but with the das-access-code as 'unregister'.
| Existing flow operated with TDA/pdx | New flow using DAS Rest API | |
|---|---|---|
| IP5 (OFF) --- dasRegRequest ---> WIPO DAS. As a result, OFF receives an ackId | POST https://{wipo-hostname}/am/oauth2/access_token | IP5 (OFF) uses the OFF private key to generate the JWT client assertion (see more details) to request a valid access-token to WIPO DAS |
| DELETE https://{wipo-hostname}/requests/registrations | IP5 (OFF) sends a document deregistration request to WIPO DAS | |
| WIPO DAS ---- dasRegResponse --> IP5 (OFF). As a result, OFF receives the ackId and related registration status | ||
Use Case 3 - Document Retrieval to WIPO DAS by OSF
| Existing flow operated with TDA/pdx | New flow using DAS Rest API with notifications of document availability | |
|---|---|---|
| IP5 (OSF) --- pdRequest ---> WIPO DAS. As a result, OSF receives an ackId | POST https://{wipo-hostname}/am/oauth2/access_token | IP5 (OSF) uses the OSF private key to generate the JWT client assertion (see more details) to request a valid access-token to WIPO DAS |
| POST https://{wipo-hostname}/requests/retrievals | IP5 (OSF) sends a document retrieval request, receives an ackId and the request status | |
| WIPO DAS ---- pdResponse --> IP5 (OSF). As a result, OSF receives the ackId and the requested document | POST https://{osf-hostname}/oauth2/access_token | WIPO DAS uses the WIPO private key to generate the JWT client assertion to request a valid access-token to OSF |
| POST https://{off-hostname}/requests/notifications | WIPO DAS notifies OSF of the availability of documents | |
| POST https://{wipo-hostname}/am/oauth2/access_token | IP5 (OSF) uses the OSF private key to generate the JWT client assertion to request a valid access-token to WIPO DAS | |
| GET https://{wipo-hostname}/requests/retrievals | IP5 (OSF) downloads the requested documents one by one | |
Note: There is no document size limitation
Use Case 4 - Document Retrieval to OFF by WIPO DAS
| Existing flow operated with TDA/pdx | New flow using DAS Rest API with notifications of document availability | |
|---|---|---|
| WIPO DAS --- pdRequest ---> IP5 (OFF). As a result, WIPO DAS receives an ackId | POST https://{off-hostname}/oauth2/access_token | WIPO DAS uses the WIPO private key to generate the JWT client assertion (see more details) to request a valid access-token to OFF |
| POST https://{off-hostname}/requests/retrievals | WIPO DAS sends a document retrieval request, receives an ackId and the request status | |
| IP5 (OFF) ---- pdResponse --> WIPO DAS. As a result, WIPO DAS receives the ackId and the requested document | POST https://{wipo-hostname}/am/oauth2/access_token | OFF uses the OFF private key to generate the JWT client assertion to request a valid access-token to WIPO DAS |
| POST https://{wipo-hostname}/requests/notifications | OFF notifies WIPO DAS of the availability of documents | |
| POST https://{off-hostname}/oauth2/access_token | WIPO DAS uses the WIPO private key to generate the JWT client assertion to request a valid access-token to OFF | |
| GET https://{off-hostname}/requests/retrievals | WIPO DAS downloads the requested documents one by one | |
Note: There is no document size limitation