OSI/AS Configuration and Management Manual

OSI/AS Subsystem Description
OSI/AS Configuration and Management Manual—424119-001
7-12
NSP Process: TLAM
NSP Process: TLAM
In an OSI/AS subsystem, TLAM is not considered to be a network service provider;
this function is included in the TSP process. Nevertheless, TLAM is a distinct process
that can be analyzed separately.
Downward Information Flow
TLAM accepts primitives from the TSP process connectionless-oriented OSI IP in
file-system calls to the TLAM port. All TSP subdevices that use TLAM as the NSP
process share the same port and use the class 4 transport protocol.
Upon receiving a request or response primitive, TLAM adds an LLC1 header, as
prescribed by the IEEE 802.2 standard, and forwards the PDUs to the LAN controller.
Upward Information Flow
TLAM strips the headers from incoming PDUs and forwards them to the TSP process as
file-system completions. Received errors are noted and returned in the error completion.
State Machine
The state machine follows the IEEE 802.2 and IEEE 802.3 protocols.
NSP Process: PAM
In an OSI/AS subsystem, PAM is not considered to be a network service provider; this
function is included in the TSP process. Nevertheless, PAM is a distinct process that can
be analyzed separately.
Downward Information Flow
PAM accepts primitives from the TSP process’ connectionless-oriented OSI IP in file-
system calls to the PAM port. All TSP subdevices that use PAM as the NSP process
share the same port and use the class 4 transport protocol.
Upon receiving a request or response primitive, PAM adds an LLC1 header, as
prescribed by the IEEE 802.2 standard, and forwards the PDUs to the LAN controller.
Upward Information Flow
PAM strips the headers from incoming PDUs and forwards them to the TSP process as
file-system completions. Received errors are noted and returned in the error completion.