Surveys of marine birnavirus (MABV) were undertaken in cultured olive flounder Paralichthys olivaceus from the south and west coastal areas and Jeju in Korea during the period January 1999 to April 2007. MABV was detected in all seasons from the fry, juveniles and adult fish from the areas examined. Evident cytopathic effects of the virus including rounding and cell lysis were observed in chinook salmon embryo (CHSE-214) and rainbow trout gonad (RTG-2) cells, but not in fathead minnow (FHM) and epithelial papilloma of carp (EPC) cells. Nucleotide sequences of the VP2/NS junction region of the Korean isolates showed 97.8% ~ 100% similarity, and they belonged to the same genogroup. Cross neutralization tests with serotype-specific rabbit antisera against MABV strains exhibited a close antigenic relationships between strains, and were distinct from infectious pancreatic necrosis virus (IPNV) strains. Coinfection of MABV with bacteria (Streptococcus iniae, Vibrio spp.) and viruses (nervous necrosis virus, lymphocystis disease virus, viral hemorrhagic septicemia virus) was observed.

In a marine ubiquitous sensor network (USN) system using expensive sensors in the harsh ocean environment, it is very important to discover failures and devise recovery techniques to deal with such failures. Therefore, in order to perform failure modeling, this study analyzes the USN-based real-time water quality monitoring service of the Gaduri Aqua Farms at Songdo Island of Yeosu, South Korea and devises methods of discovery and recovery of failure by classifying the types of failure into system element failure, communication failure, and data failure. In particular, to solve problems from the perspective of data, this study defines data integrity and data consistency for use in identifying data failure. This study, by identifying the exact type of failure through analysis of the cause of failure, proposes criteria for performing relevant recovery. In addition, the experiments have been made to suggest the duration as to how long the data should be stored in the gateway when such a data failure occurs.

No abstract

No abstract