Discard. 0.67 ≤ IAA < 0.8 Tentative 0.8 ≤ IAA ≤ 1 Good Table 1: Xxxxxxxxxxxx (1980). IAA value IAA interpretation IAA < 0 Poor 0 ≤ IAA ≤ 0.2 Slight
Discard. From then onwards, the FMU offers two options: it either goes into a state where the FMU’s state is queried and the simulation is finished (process EndSim), or has its state reset to a previous state to rollback the simulation and try to perform it with the current time point and a new step-size. EndSim = → get cint ?cint (UpdateCT (snd (cint ) + 1, cint ); Finalise) DoStepDiscard = let DoStepDiscard0 = (EnquiryFMU ; EndSim) → { } → 2 setState.i?ctr?str get ct ? ct { } → → ctr <= ct & upd ct ! ctr upd st !st r SKIP 2 ctr > ct & DoStepDiscard0 within doStepOutcome.i!discard → DoStepDiscard0 The next process tells the environment that the FMU is still carrying out the co-simulation step by broadcasting the event doStepOutcome.i.pending . From then onwards, the FMU may inform the environment that the step is finished with event stepFinished , followed by the conclusion of the step (FinishStep above) or the step may be cancelled by the environment through channel stepCancel , after which the simulation concludes (EndSim above). DoStepPending(ctr) = let DoStepPending0 = → → stepFinished.i get st ?st FinishStep(ctr, st ) → within
Discard. From then onwards, the FMU offers two options: it either goes into a state where the FMU’s state is queried and the simulation is finished (process EndSim), or has its state reset to a previous state to rollback the simulation and try to perform it with the current time point and a new step-size. EndSim = → get cint ?cint (UpdateCT (snd (cint ) + 1, cint ); Finalise) DoStepDiscard = let DoStepDiscard0 = (EnquiryFMU ; EndSim) . → { } → Σ
Discard. Figure 2 QoS controls for 3-tier SLA with class upgrades The BA classifier represents a Behavior Aggregate classifier which classifies packets based on the TOS or DSCP field in the packet, and redirects traffic to one of 3 meters labeled “Gold 2MBps”, “Silver 3MBps” and “Bronze 1MBps” which meter the customers’ Gold, Silver and Bronze traffic to what was negotiated (as specified in Table 4 in this case), respectively. These meters work as follows: - Gold meter colors conformant (conformant to some certain leaky bucket parameters for example) Gold traffic White, and non-conformant Gold traffic Black (in this case, the excess Gold or Black traffic is dropped). - Silver meter colors conformant Silver traffic Green, and non-conformant Silver traffic Yellow. - Bronze meter colors conformant Bronze meter Brown, and non-conformant Bronze traffic Red. The output of the first stage of meters is re-inserted into a second level of color-aware policers. This second stage of policers labeled “W(G,Y) 2MBps”, “G(Y,B,R) 3MBps”, and “B(R) 1 MBps” work as follows: - The “W(G,Y) 2MBps” policer, counts White packets without policing them (i.e. forwards White packets unconditionally to the Gold queue) and allows Green or Yellow packets into the Gold queue based on both available rate (based on bytes inserted into queue within a period T) and the Gold Queue Size. If there is some Gold bandwidth available, Green (originally Silver) packets are inserted into the Gold queue based on a threshold set for a certain size of the Gold queue. If the queue size is above a certain Green threshold, the Green packet is forwarded to the “G(Y,B,R) 3MBps” Policer otherwise, the Green packet is promoted to Gold and inserted into the Gold queue. Yellow packets observe the same behavior except that the Policer checks a Yellow threshold (where Yellow threshold > Green threshold) to remark and insert a Yellow packet into the Gold queue. - The “G(Y,B,R) 3MBps” Policer works in a similar manner to the “W(G,Y) 2MBps” Policer in which the Green packets are forwarded unconditionally to the Silver queue and Yellow, Brown, and Red packets are forwarded based on available bandwidth and Yellow, Brown and Red queue thresholds, respectively (where Red threshold> Brown threshold>Yellow threshold).
