OSI/MHS P7 Application Programmatic Interface (P7 API) Manual

Introduction to the P7 API
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
1-6
P7 Operations
P7 Operations
The P7 operations that can be performed using a P7 API client application are:
•
Administration
•
MSBIND
•
MSUNBIND
•
Submission
•
MESSAGE SUBMISSION
•
PROBE SUBMISSION
•
CANCEL DEFERRED
•
Retrieval
•
SUMMARIZE
•
LIST
•
FETCH
•
DELETE
•
REGISTER-MS (change-credentials and list- and fetch-attribute-defaults only)
The contents of the P7 operations are as follows:
•
MSBIND and MSUNBIND operations require data to be structured like the user
data in an Application Control Service Element A-Associate Response Application
Protocol Data Unit (ACSE AARE-APDU) as if ACSE were being used.
•
Submission and retrieval operations require data to be structured like a Remote
Operations Invoke Application Protocol Data Unit (ROIV-APDU), which would be
contained in the P-DATA if Presentation Layer Services were being used.
The structure of submission and retrieval operations use ROSE encoding. Invoke
operations (ROIV-APDU) contain an operation code, an invoke ID, and arguments.
Return results (RORJ-APDU or RORS-APDU) and return errors (ROER-APDU)
contain an invoke ID and arguments.
Local User Agents
The operations performed by a P7 client application, or local user agent, are a local
equivalent of the operations performed by a remote user agent for example, both local
UAs and remote UAs can submit LIST, FETCH, and SUBMIT operations. P7 API
client applications connect to the subsystem through the LO group; remote user agents
connect to the subsystem through the Remote Operations Service (RS) group.
Figure 1-4 shows local UAs and remote UAs and how they connect to the OSI/MHS
subsystem.