commit | 3cded63aa6ea97bd1e0476b4ddd2ef27b6ca8024 | [log] [tgz] |
---|---|---|
author | Harald Welte <laforge@gnumonks.org> | Sat Mar 09 12:59:41 2019 +0100 |
committer | Harald Welte <laforge@gnumonks.org> | Sat Mar 09 13:11:56 2019 +0100 |
tree | 0a05f02254ff552258d53b7681f0019f87fd7e29 | |
parent | 707c85a49b9fbf5ca69c827f181519f331169e96 [diff] |
naming: Distinguish "rspro client" from "remsim client" "remsim-client" is the client program running next to a phone/modem which is attaching to the SIM slot. "RSPRO client" is a protocl-level client of the RSPRO protocol: * the remsim-client connects as RSPRO client to the remsim-server * the remsim-client connects as RSPRO client to the remsim-bankd * the remsim-bankd connects as RSPRO client to the remsim-server Let's clarify this in naming. Change-Id: I10462d4669a0a30c46f3f8d3df67e9c1d4ce8c4b
This software suite is a work in progress.
The client interfaces with GSM phones / modems via dedicated "Card Emulation" devices such as the Osmocom SIMtrace2 or sysmocom sysmoQMOD board + firmware. This hardware implements the ISO7816-3 electrical interface and protocol handling and passes any TPDU headers received from the phone/modem to remsim-client for further processing of the TPDUs associated to the given APDU transfer.
remsim-client connects via a RSPRO control connection to remsim-server at startup and registers itself. It will receive configuration data such as the remsim-bankd IP+Port and the ClientId from remsim-server.
After receiving the configuration, remsim-client will establish a RSPRO data connection to the remsim-bankd IP:Port.
As the USB interface for remote SIM in simtrace2.git uses one interface per slot, we can implement the client in blocking mode, i.e. use blocking I/O on the TCP/RSPRO side. This simplifies the code compared to a more complex async implementation.
The remsim-bankd (SIM Bank Daemon) manages one given SIM bank. The initial implementation supports a PC/SC driver to expose any PC/SC compatible card readers as SIM bank.
remsim-bankd initially connects via a RSPRO control connection to remsim-server at startup, and will in turn receive a set of initial [client,slot]:[bankd,slot] mappings. These mappings determine which slot on the client (corresponding to a modem) is mapped to which slot on the SIM bank. Mappings can be updated by remsim-server at any given point in time.
remsim-bankd implements a RSPRO server, where it listens to connections from remsim-clients.
As PC/SC only offers a blocking API, there is one thread per PC/SC slot. This thread will perform blocking I/O on the socket towards the client, and blocking API calls on PC/SC.
In terms of thread handling, we do:
The worker threads initially don't have any mapping to a specific reader, and that mapping is only established at a later point after the client has identified itself. The advantage is that the entire bankd can live without any non-blocking I/O.
The main thread handles the connection to remsim-server, where it can also use non-blocking I/O. However, re-connection would be required, to avoid stalling all banks/cards in the event of a connection loss to the server.
worker threads have the following states:
Once the client disconnects, or any other error occurs (such as card I/O errors), the worker thread either returns to INIT state (closing client socket and reader), or it terminates. Termination would mean that the main thread would have to do non-blocking join to detect client termination and then re-spawn clients, so the "return to INIT state" approach seems to make more sense.
Open topics: