Deadlock-free verification and performance enhancement of RosettaNet PIPs with time Petri nets

[[abstract]]This paper deals with the deadlock-free verification problem of RosettaNet, a promising and widespread e-business protocol in the information technology and electronic industries. RosettaNet PIPs (partner interface processes) specifications are first modelled with time Petri nets (TPNs) which allow an explicit modelling of concurrency and parallelism. Correctness of the TPN models is verified to ensure the capability of deadlock-freeness, auto-repairing implementation of RosettaNet applications. We adopt the idea of checking the possible existence of an uncontrolled siphon as our deadlock detection mechanism. We demonstrate that RosettaNet PIPs are deadlock-free in both deterministic and stochastic operational environments. A patch subnet technique is developed to improve the efficiency of RosettaNet PIPs. We also prove that the execution of some steps defined in RosettaNet PIPs will never take place. We therefore suggest to removing these unnecessary steps from RosettaNet PIPs and from a lean model.[[note]]SC

Deadlock-free verification and performance enhancement of RosettaNet PIPs with time Petri nets

[[abstract]]This paper deals with the deadlock-free verification problem of RosettaNet, a promising and widespread e-business protocol in the information technology and electronic industries. RosettaNet PIPs (partner interface processes) specifications are first modelled with time Petri nets (TPNs) which allow an explicit modelling of concurrency and parallelism. Correctness of the TPN models is verified to ensure the capability of deadlock-freeness, auto-repairing implementation of RosettaNet applications. We adopt the idea of checking the possible existence of an uncontrolled siphon as our deadlock detection mechanism. We demonstrate that RosettaNet PIPs are deadlock-free in both deterministic and stochastic operational environments. A patch subnet technique is developed to improve the efficiency of RosettaNet PIPs. We also prove that the execution of some steps defined in RosettaNet PIPs will never take place. We therefore suggest to removing these unnecessary steps from RosettaNet PIPs and from a lean model.[[note]]SC