Skip Navigation

Flow for Session Locking when Sending a Single Command to the Host Communications Service

The following flow demonstrates how the host communications service handles TA session locking when a Red App sends a single command in a single session.

  1. The Red App sends a command to the host communications service. This is the most important activity for the Red App because the host communications service handles the locking and unlocking of the TA session for the Red App.

  2. The host communications service checks to see if a lock is already set on the TA session. The result is negative, therefore, the host communications service locks the TA session internally.

  3. The host communications service locks the TA session.

  4. The host communications service sends a command to the host.

  5. The host communications service receives the response from the host.

  6. The host communications service unlocks the session during service processing.

  7. The host communications service returns the response to the Red App.