In the simplest case, the solution does not require any special processing of an inbound fragment. The
fragment is created in the S_InFragArrived state, which is also its final state. The case where special
processing for inbound fragments is required can be handled in the FSM modeling of the input objects, physical
transmission, fragment, batch, and transaction.
The following tables show the events that are raised by EndMapper in addition to E_MpInTxnMapped when
mapping fragments:
Table 1. E_MpInFragBatMapped Events
| TRANSMISSION |
(1) |
| FRAGMENT |
(1) |
| BATCH |
(1) |
| BAT_TYPE |
(0..1) |
| BAT_CLASS |
(0..1) |
| FRAG_SPAN |
(0..1) |
| TXN_PASS_COUNT |
(1) |
| TXN_FAIL_COUNT |
(1) |
Table 2. E_MpInFragMapped Events
| TRANSMISSION |
(1) |
| FRAGMENT |
(1) |
| FRAG_TYPE |
(0..1) |
| FRAG_CLASS |
(0..1) |