User's Manual

5 OPERATION
38
HF80 Transponder Reader – HSMS, Release 1.3
The specification of a required TCP Application Program Interface
(API) for use in implementations is outside the scope of HSMS. A
HSMS implementation may use any TCP/IP API - sockets, TLI
(Transport Layer Interface), etc.
#
Current
State
Trigger New State Comment
1
...
Local entity-specific
preparation for
TCP/IP
communication
Not
Connected
Action depends on
connection procedure to be
used: active or passive.
2
Not
connected
A TCP/IP connection
is established for
HSMS
communication.
Connected -
Not Selected
None
3
Connected
Breaking of TCP
connection.
Not
Connected
HSMS only permits
termination of the
connection when the
connection is in the Not
Selected sub state.
4
Not
Selected
Successful completion
of HSMS Select
procedure.
Selected
HSMS communication is
now fully established: data
messages exchange is
permitted.
5
Selected
Successful completion
of HSMS Deselect or
Separate.
Not
Selected
This transition normally
indicates the end of HSMS
communication, and so an
entity would immediately
proceed to break the TCP/IP
connection
6
Not
Selected
T7 Connection
Timeout
Not
Connected
There is a Time limit on
how long an entity is
required to remain in the
Not Selected state before
either entering in the
Selected state or returning to
Not Connected state.