Model Interfaces
Packet Formats
The following table lists the packet formats used in the TPAL model suite.
Table 230: TPAL Packet Formats
| name | description |
|---|---|
| tpal_aal5_signal | Used for signaling. It contains the fields type, rem_port, rem_addr and protocol. This packet format is only used by the tpal_aal5_if_v2 process model. |
| frms_tpal_setup_frame | Used to send setup information, including OPEN_REQ, OPEN_CONF, CLOSE_REQ, and CLOSE_CONF to another tpal session. Setup information includes request type, Local Port, Remote Port, Local TPAL Address and Remote TPAL Address. This packet format is only used by the tpal_intf_fr_v2 process model. |
ICI Formats
The following table lists the interface control information (ICI) formats used in the TPAL model suite. The application is responsible for destroying these ICIs at the end of a session.
Table 231: TPAL ICI Formats
| name | description |
|---|---|
| tpal_req | When application sends a request to the tpal module by scheduling a remote interrupt with a command code or by sending a packet, this ICI must accompany the packet or remote interrupt. It identifies the transport protocol and session, so that the request can be forwarded correctly. The tpal_req ICI also contains addressing information and command options. |
| tpal_serv_reg | When a server application adds itself to the global server registry by issuing a remote interrupt, this ICI accompanies the interrupt. It identifies the transport protocol, the name of the service (for debugging purposes only) and the local port index used by the service. |
| tpal_ind | All indications sent to the application are accompanied by this ICI format. It contains information about the Session ID, Application ID, optional information about the indication, and the Remote Port and Address. During the session, the receiving application should neither destroy this ICI nor modify its contents. |
TPAL Requests and Indications
An application issues a request to tpal to initiate a session, to send data through an established session, or to end the session. The following table lists the requests that are available to applications.
Table 232: TPAL Requests
| request | description |
|---|---|
| OPEN_REQ | Request that a session be initiated using a specified transport protocol. If a connection-oriented protocol is specified, a connection is opened. If a connectionless protocol is specified, no connection can be opened, but the remote address information is retained for future requests. The OPEN_REQ may be active (the application, usually a client process, connects to a waiting application at a specified remote host) or passive (the application, usually a server process, reserves local system resources to prepare for incoming requests). |
| DATA_REQ | Send data. This request should be issued only after the session is established. |
| CLOSE_REQ | Request that the session be terminated gracefully, waiting for all data to reach its destination. Some transport protocols do not support graceful termination; in this case, CLOSE_REQ is equivalent to ABORT_REQ. |
| ABORT_REQ | Request that the session be terminated immediately. Data in transit may be lost. |
The following table lists indications that are sent from TPAL to the application.
Table 233: TPAL Indications
| indication | description |
|---|---|
| OPEN_IND | A remote application is attempting to establish a session. The session is not yet fully established. This indication is especially useful for server processes that need to have a session free to wait for incoming requests: when the OPEN_IND is received, the server must start another session. |
| OPEN_CONFIRM | A session has been established and can now be used to send data. |
| DATA_IND | Data has arrived from the remote application. |
| CLOSE_IND | The remote application has terminated the session gracefully, waiting for all data to reach its destination. |
| ABORT_IND | The remote application has terminated the session immediately. Data in transit might be lost. |