ats (Spom2 and Rim use the same format) for Spom1, Spom2, Cfm, Rim and Gaom are summarized in Fig. 5.38. CommonFormat ::= $SEQ{par ANY DEFINED BY ohd, END, ohd OHD} ACT::=$BITSTR SIZE (4) rescan ACT ::= '0001'B regIncr ACT '0010'B newAccChan ACT '0110'B accOverLoad ACT '1000'B busyIdleSys ACT : 1001'B accAttempt ACT ::= '1010'B randChallA ACT : 0111'B randChallB ACT '1011'B localControlA ACT ='1110'B localControlB ACT ='1111'B Spom1 ::= $SEQ{parSet ANY DEFINED BY {spom1}, NAWC, {spom1}} Spom2 ::= CommonFormat -value of OHD is spom2 ::= $SEQ{parSet ANY DEFINED BY {cfm}, {cfm}} ::= CommonFormat -value of OHD is rim ::= $SEQ ACT, parSet ANY DEFINED BY act, END, OHD} -value of OHD is gaom OPERATION cfm '001'B -OHD-value PROPERTIES ReportConfirm ({spare1 '010111'B}, CMAC, SDCC1, $SPARE1 SIZE (2), SDDC2, $SPARE1 SIZE (1), WFOM, $SPARE1 SIZE (4)) CMAC ::= reccPowLev $INT (0..7) SDCC1 ::= $BITSTR SIZE (2) SDCC2 ::= $BITSTR SIZE (2) WFOM ::= $BITSTR SIZE (1) readOvhBeforeAccess WFOM ::= '1'B notReadOvhBeforeAccess WFOM ::= '0'B COMMENT This operation is used by the network to inform MSs about - which sending power to use when accessing the network on RECC (CMAC) - which supplementary digital colour codes to use (SDCC1 and SDCC2) - if the MS is expected to have read broadcast information before accessing the network Fig. 5.38 Message specifications for message types in an OvhMessTrain, and the operation spec- ification supported by Cfm messages The operation specification for the operation cfm is also shown in this figure. The ASP for cfm includes considerable overhead of spare bits, which is also the case for most of the other ten operation specifications. It is therefore likely that the complicated message format is a result of the protocol design method that was used, not of an effort to save bits. In conclusion, the analysis made SO far should suffice as an example of how to apply the discrimination and message-handling models. We have provided a formal message specification for the integrator of the terminal process c