Boomer-III User Manual & Integrator’s Guide______________________Appendix B – SDK NCL-API and Port Server
BM310012WT04
97
Copyright Wavenet Technology © October 2003
LAYER NAME
CONTENT
FUNCTION
7. APPLICATION
Application specific data.
Applications are to initialise a RX MSMQ (Microsoft
Message Queuing system) queue and open a session
with the VDD by passing the RX queue handler.
6. PRESENTATION
LAYER
Unused
5. SESSION
LAYER
Unused
4. TRANSPORT
LAYER
Unused
3. NETWORK
LAYER
Router
MSMQ is run as a device driver on the Pocket PC
and is run from power up (i.e. Non-suspend mode).
The VDD will post events (RCV messages etc) to all
application RX queues enabled for that event.
Responses to application requests will be posted to
the calling application RX queue.
The VDD process TX requests via a FIFO queue to
the NCL Interpreter. The Host base routing or Peer-
to-Peer routing SDU formatting is contained in the
NCL interpreter.
2. DATA LINK LAYER
NCL Interpreter &
Extender port – Serial
Driver.
Application NCL API function requests are processed
via a FIFO queue. RPM responses or received data is
tagged and encoded for the router as required Also
the UART DLL that handles the extender port UART
to modem communications resides in the link layer
modules..
1. PHYSICAL / BIT TRANSFER
LAYER
Extender Port to RPM.
9600, 8, 1, N on serial port and a wakeup line.
Wavenet’s current NCL API protocol stack is implemented with the
hierarchical structure. All DLLs including MSMQ files are included in
the install cabinet files for the VDD.
Message Router
The PC or PPC loads MSMQ as a device driver. Applications using the
modem must open a session with VDD by calling ‘VDDOpen()’ which
will create a private Receive MSMQ queue for the instance of the
application (client). The name of this private queue will be sent to the
serial port server (VDD) along with an open session request. The port
server will in turn create a private MSMQ queue to receive data from
the client. All Modem Events and response messages to be
communicated between the VDD and the application will be via the
receive queues. Transmit function requests from the applications
(clients) are queued by the VDD and are processed as a FIFO buffer by
the NCL interpreter. On Wakeup the VDD will be activated, if any
applications receive queues are open the RX event will be posted to
those queues. If no receive queues are active, the VDD will buffer the
RX events and start up the registered on_wakeup applications. After
the applications have successfully opened a VDD session the VDD will
pass the RX events to those applications.
NCL Interpreter
The NCL Interpreter strips NCL API function calls from application
messages, queue the calls and execute the calls on a FIFO basis.
Received messages will be queued and matched against an appropriate
