ISO/IEC 30143:2020
(Main)Internet of Things (IoT) - Underwater acoustic sensor network (UWASN) - Application profiles
Internet of Things (IoT) - Underwater acoustic sensor network (UWASN) - Application profiles
ISO/IEC 30143:2020 provides the guidelines for designing and developing new applications in the underwater environment such as fish farming, environment monitoring, harbour security, etc. This document also:
• provides the components required for developing the application;
• provides instructions for modelling the application with examples;
• helps the user to understand the communication between the elements in the application for modelling the communication between elements;
• guides the user with the design process of underwater applications.
General Information
Standards Content (Sample)
ISO/IEC 30143
Edition 1.0 2020-06
INTERNATIONAL
STANDARD
colour
inside
Internet of Things (IoT) – Underwater acoustic sensor network (UWASN) –
Application profiles
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about
ISO/IEC copyright or have an enquiry about obtaining additional rights to this publication, please contact the address
below or your local IEC member National Committee for further information.
IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.
IEC publications search - webstore.iec.ch/advsearchform Electropedia - www.electropedia.org
The advanced search enables to find IEC publications by a The world's leading online dictionary on electrotechnology,
variety of criteria (reference number, text, technical containing more than 22 000 terminological entries in English
committee,…). It also gives information on projects, replaced and French, with equivalent terms in 16 additional languages.
and withdrawn publications. Also known as the International Electrotechnical Vocabulary
(IEV) online.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Glossary - std.iec.ch/glossary
details all new publications released. Available online and 67 000 electrotechnical terminology entries in English and
once a month by email. French extracted from the Terms and Definitions clause of
IEC publications issued since 2002. Some entries have been
IEC Customer Service Centre - webstore.iec.ch/csc collected from earlier publications of IEC TC 37, 77, 86 and
If you wish to give us your feedback on this publication or CISPR.
need further assistance, please contact the Customer Service
Centre: sales@iec.ch.
ISO/IEC 30143
Edition 1.0 2020-06
INTERNATIONAL
STANDARD
colour
inside
Internet of Things (IoT) – Underwater acoustic sensor network (UWASN) –
Application profiles
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 35.110 ISBN 978-2-8322-8485-8
– 2 – ISO/IEC 30143:2020 © ISO/IEC 2020
CONTENTS
FOREWORD . 5
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 7
4 Abbreviated terms . 8
5 Overview of UWASN application profiles . 8
5.1 Introduction to application profiles . 8
5.2 Benefits of application profiles . 8
6 Design process of UWASN application profiles . 8
6.1 General . 8
6.2 Criteria for the design process of UWASN application profiles . 9
6.3 Design process steps for UWASN application profiles . 9
7 Requirements for the design process of UWASN application profiles . 9
7.1 General . 9
7.2 User requirements of UWASN application profiles . 10
7.3 General requirements of UWASN application profiles . 10
7.4 Functional requirements of UWASN application profiles . 11
7.5 Constrained requirements of UWASN application profiles . 12
7.5.1 General . 12
7.5.2 Connectivity . 13
7.5.3 UWA-GW . 13
7.5.4 UWA-DTN-GW . 13
7.5.5 Housing case . 13
7.5.6 Fouling cleaner . 13
7.5.7 Node deployment . 13
7.5.8 Battery . 14
8 Modelling techniques for designing UWASN application profiles . 14
8.1 General . 14
8.2 Use case model . 14
8.2.1 General . 14
8.2.2 Elements of use case diagram . 14
8.2.3 Relationships . 15
8.3 Sequence diagram model . 16
8.3.1 General . 16
8.3.2 Elements of sequence diagram . 16
8.4 Class diagram model . 18
8.4.1 General . 18
8.4.2 Elements of class diagram . 18
9 Guidelines for the implementation of UWASN application profiles . 19
9.1 Layered design approach for developing UWASN application profiles . 19
9.2 Specific architecture for implementing UWASN application profiles . 20
9.3 Framework for implementing UWASN application profiles . 21
9.3.1 User interface . 21
9.3.2 System calculation unit . 22
9.3.3 Surface devices . 22
9.3.4 Sensor node . 22
9.4 Functional operations for implementing UWASN application profiles . 23
10 Specialized maintenance for UWASN application profiles . 24
Annex A (informative) Application profile example. 26
A.1 Fish farming . 26
A.1.1 General . 26
A.1.2 Guidelines for designing UWASN fish farming application . 26
A.1.3 Requirements for the design process of UWASN fish farming application . 27
A.1.4 Modelling techniques for designing UWASN fish farming application . 30
A.1.5 Guidelines for the implementation process of UWASN fish farming
application . 32
Bibliography . 38
Figure 1 – Actor representation examples . 14
Figure 2 – Use case representation examples . 15
Figure 3 – System boundary representation example . 15
Figure 4 – Use case model for UWASN application profiles . 16
Figure 5 – Object symbol in a sequence diagram . 16
Figure 6 – Execution box symbol in a sequence diagram . 17
Figure 7 – Lifeline representation in a sequence diagram . 17
Figure 8 – Sequence diagram modelling for UWASN application profiles . 17
Figure 9 – Representation of different sections in class diagram . 18
Figure 10 – Class diagram modelling for UWASN application profiles . 19
Figure 11 – Layer design approach . 20
Figure 12 – UWASN specific architectural model . 21
Figure 13 – Framework of UWASN application profiles . 23
Figure 14 – Operation design approach . 24
Figure A.1 – Use case model for fish farming application . 31
Figure A.2 – Sequence diagram model for fish farming application . 32
Figure A.3 – Layered design approach of fish farming application . 33
Figure A.4 – Specific fish farming architecture . 34
Figure A.5 – Framework for fish farming application . 35
Figure A.6 – Operation design process for fish farming application . 36
Table 1 – Steps for the design process of UWASN application profiles . 9
Table 2 – User requirements of UWASN application profiles . 10
Table 3 – General requirements for UWASN application profiles . 10
Table 4 – Functional requirements for UWASN application profiles . 11
Table 5 – Constrained requirements for UWASN application profiles . 12
Table 6 – Relationship and symbols of use case diagram . 15
Table 7 – Components for implementing UWASN application profiles . 23
Table 8 – Operation process of UWASN application profiles . 24
Table 9 – Key factors for monitoring UWASN application profiles . 25
Table 10 – Components used for the maintenance of UWASN application profiles . 25
– 4 – ISO/IEC 30143:2020 © ISO/IEC 2020
Table A.1 – Steps for designing UWASN fish farming application . 27
Table A.2 – User requirements for the design process of UWASN fish farming
application . 27
Table A.3 – General requirements for the design process of UWASN fish farming
application . 28
Table A.4 – Functional requirements for the design process of UWASN fish farming
application . 29
Table A.5 – Constrained requirements for the design process of UWASN fish farming
application . 30
Table A.6 – Operation design process of UWASN fish farming application . 36
Table A.7 – Key components to monitor in fish farming application . 37
Table A.8 – Components used for the maintenance of UWASN fish farming application . 37
INTERNET OF THINGS (IoT) –
UNDERWATER ACOUSTIC SENSOR NETWORK (UWASN) –
APPLICATION PROFILES
FOREWORD
1) ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical committees established by the
respective organization to deal with particular fields of technical activity. ISO and IEC technical committees
collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in
liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have
established a joint technical committee, ISO/IEC JTC 1.
2) The formal decisions or agreements of IEC and ISO on technical matters express, as nearly as possible, an
international consensus of opinion on the relevant subjects since each technical committee has representation
from all interested IEC National Committees and ISO member bodies.
3) IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted by
IEC National Committees and ISO member bodies in that sense. While all reasonable efforts are made to ensure
that the technical content of IEC, ISO and ISO/IEC publications is accurate, IEC or ISO cannot be held
responsible for the way in which they are used or for any misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees and ISO member bodies undertake to
apply IEC, ISO and ISO/IEC publications transparently to the maximum extent possible in their national and
regional publications. Any divergence between any ISO, IEC or ISO/IEC publication and the corresponding
national or regional publication should be clearly indicated in the latter.
5) ISO and IEC do not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. ISO or IEC are not responsible for
any services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or ISO or its directors, employees, servants or agents including individual experts
and members of their technical committees and IEC National Committees or ISO member bodies for any personal
injury, property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including
legal fees) and expenses arising out of the publication of, use of, or reliance upon, this ISO/IEC publication or any
other IEC, ISO or ISO/IEC publications.
8) Attention is drawn to the normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this ISO/IEC publication may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
International Standard ISO/IEC 30143 was prepared by subcommittee 41: Internet of Things
and related technologies, of ISO/IEC joint technical committee 1: Information technology.
The text of this International Standard is based on the following documents:
FDIS Report on voting
JTC1-SC41/150/FDIS JTC1-SC41/161/RVD
Full information on the voting for the approval of this International Standard can be found in the
report on voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this document using a colour printer.
– 6 – ISO/IEC 30143:2020 © ISO/IEC 2020
INTRODUCTION
Water covers approximately 70 % of the surface of the Earth. Modern technologies introduce
new methods to monitor the body of water such as pollution monitoring and detection.
Underwater data gathering techniques require exploring the water environment, which can be
most effectively performed by underwater acoustic sensor networks (UWASNs). Applications
developed for the UWASNs can record underwater climate, detect and control water pollution,
monitor marine biology, discover natural resources, detect pipeline leakages, monitor and find
underwater intruders, perform strategic surveillance, and so on.
In order to build and apply the UWASN technology, the most suitable methods for managing
the network have been developed based on the already proposed ISO/IEC 30140 series. This
document describes the application profiles outline and requirements appropriate to the
UWASN under the constraints of underwater physical environment.
The ISO/IEC 30140 series provides general requirements, reference architecture (RA) including
the entity models and high-level interface guidelines supporting interoperability among
UWASNs in order to provide the essential UWASN construction information to help and guide
architects, developers and implementers of UWASNs.
This document provides the guidelines for designing and developing the UWASN application. It
also provides other information such as the components required for developing UWASN
application, modelling techniques for UWASN application and UWASN application profiles
example.
Various technical standards derived from the R&D results of the technical areas under the
UWASN and underwater communication fields not covered by the ISO/IEC 30140 series are
continuously proposed and developed.
INTERNET OF THINGS (IoT) –
UNDERWATER ACOUSTIC SENSOR NETWORK (UWASN) –
APPLICATION PROFILES
1 Scope
This document provides the guidelines for designing and developing new applications in the
underwater environment such as fish farming, environment monitoring, harbour security, etc.
This document also:
• provides the components required for developing the application;
• provides instructions for modelling the application with examples;
• helps the user to understand the communication between the elements in the application
for modelling the communication between elements;
• guides the user with the design process of underwater applications.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1
application profile
set of documents which provides the effective guidance to develop a particular application
3.2
component
representation of an actor in a UWASN application profile
3.3
element
object used to connect the devices and networks in the underwater
environment
EXAMPLE actors, use cases, relationships
3.4
element
essential part used to connect the devices and networks in the
underwater environment
EXAMPLE class, execution place, lifeline
– 8 – ISO/IEC 30143:2020 © ISO/IEC 2020
3.5
element
class, object or method used for the communication between the
devices and networks in the underwater environment
4 Abbreviated terms
RF radio frequency
UUV unmanned underwater vehicle
UWASN underwater acoustic sensor network
UWA-GW underwater acoustic gateway
UWA-SNode underwater acoustic sensor node
UWA-CH underwater acoustic cluster head
UWA-CH-id underwater acoustic cluster head identity
UWA-SNode-id underwater acoustic sensor node identity
UWA-DTN-GW underwater DTN gateway
UWA-FN underwater acoustic fundamental network
5 Overview of UWASN application profiles
5.1 Introduction to application profiles
In UWASN, the application profiles comprise of a group of components, approaches and
guidelines for a specific application.
5.2 Benefits of application profiles
An application profile is a layout or outline for users. Application profiles can help users as
suggested below:
– utilizing them to depict how applications are deployed, arranged and managed in submerged
conditions;
– providing required components for building up new UWASN applications effectively;
– providing the basic information for planning;
– reducing the learning curve;
– standardizing the development work; and
– providing the general requirements and functional requirements for developing the
application.
6 Design process of UWASN application profiles
6.1 General
The primary goal of the design process is to give guidance for developing underwater
applications (See Annex A). The design process of UWASN application profiles provides the
following information:
– purpose of UWASN application;
– overview of UWASN application;
– user requirements for the design process of UWASN application;
– general requirements for the design process of UWASN application;
– functional requirements for the design process UWASN application;
– constrained requirements for the design process of UWASN application;
– consideration for the design process of UWASN application.
6.2 Criteria for the design process of UWASN application profiles
The criteria considered for the design process of the UWASN application profiles include but
are not limited to the following:
– limitation in bandwidth;
– localization;
– limited battery power;
– deployment of devices;
– reliability;
– scalability;
– quality of service;
– distance of transmission;
– propagation delay;
– device configuration;
– device maintenance;
– self-management.
6.3 Design process steps for UWASN application profiles
Table 1 shows the steps for the design process of UWASN application profiles.
Table 1 – Steps for the design process of UWASN application profiles
Design process steps Description
Step 1: User requirements The user requirements for a particular UWASN application are collected.
analysis
Step 2: General requirements The general requirements for particular UWASN application are collected.
analysis
Step 3: Functional requirements The functional requirements for a particular UWASN application are
analysis collected.
Step 4: Constrained The constrained requirements for a particular UWASN application are
requirements analysis collected.
Step 5: Design process The design process of UWASN application profile needs the modelling
techniques for designing the application such as case modelling, sequence
diagram modelling and class diagram modelling.
Step 6: Implementation The implementation process consists of installation, deployment,
guideline process configuration, performing operation and testing.
Step 7: Specialized The specialized maintenance for underwater applications is considered. For
maintenance example, node reclamation (change battery/recharging), fouling cleaner,
housing case, etc.
7 Requirements for the design process of UWASN application profiles
7.1 General
Clause 7 discusses the various requirements such as user requirements, general requirements,
functional requirements and constrained requirements for the design process of UWASN
application profiles (See Annex A).
– 10 – ISO/IEC 30143:2020 © ISO/IEC 2020
7.2 User requirements of UWASN application profiles
Table 2 shows the user requirements for UWASN application profiles.
Table 2 – User requirements of UWASN application profiles
User requirements Description
Durability Durability refers to the time period for which a product or system can meet its
service and performance requirements.
System performance System performance refers to the effectiveness of a system, which includes
response time, throughput, latency, availability, etc.
Low cost includes the total cost of the system, which includes the cost of
Low cost
procurement, installation, usage and disposal.
Efficiency Efficiency of a system can be identified using various factors such as
response time, number of tasks completed in a stipulated time, etc.
Adaptability Adaptability refers to the extent to which a system adapts to the change in its
working environment.
Reliability Reliability refers to the hardware or software or other application related
items; its performance is consistently monitored by the users. It can be
considered while buying or using the product.
Usability Usability can be defined as the ease of use with respect to the system. This
includes measures such as learnability, efficiency, memorability, etc.
Availability Availability refers to the percentage of time that the system is available and
working according to the requirements.
Maintainability Maintainability refers to the ability to make variations in the system quickly
and cost effectively.
Security refers to the ability of the system (1) to resist unauthorized usage
Security
and (2) to continue providing services to the legitimate users in case of
attacks.
Portability Portability can be defined as the ability of a system to run under different
computing environments such as hardware, software, operating systems, etc.
Reusability Reusability refers to the ability of a system to make reuse of existing
components in new applications.
7.3 General requirements of UWASN application profiles
Table 3 shows the general requirements for UWASN application profiles.
Table 3 – General requirements for UWASN application profiles
General requirements Description
Capability of discovery The UWA-SNode shall use discovery capability mechanism to identify other
nodes connected inside the UWASN system.
Connectivity support to different Integration shall be supported by different networks for avoiding complexity.
network
Routing techniques The best routing algorithm is performed by the device known as router, used
for passing the message from source to destination. This technique can also
reduce the cost in UWASN.
Security A standard security system shall be used to prevent attacks from illegal
users.
Service quality Service quality refers to a network capability to attain maximum bandwidth
and deals with the various performance elements of network, which include
latency, error rate, etc.
Scalability If the number of devices increases, the UWASN system shall use the
scalability support.
Dynamic adaptation Due to the mobility of UUV and UWA-SNode, the UWASN shall use dynamic
adaptation techniques.
General requirements Description
Deployment Easy deployment techniques shall be used for the deployment of UWA-
SNodes in the underwater environment.
Battery life time management In UWASN, the battery life time management shall be used to increase the
battery life time of underwater devices.
Localization Localization techniques shall be used to find the location of UWA-SNodes,
UUVs, etc.
Time synchronization Time synchronization shall be used to synchronize the time of all sensor
nodes used in UWASN.
Network management Network management shall be used to manage the whole applications such
as fish farming, environment monitoring, etc.
Wired/wireless communication Wired or wireless communication shall be established based on the
requirements.
Privacy Any information cannot be provided for all. So, this function shall be used for
maintaining privacy.
Packet loss reducing Various techniques shall be used to minimize the packet loss in UWASN.
7.4 Functional requirements of UWASN application profiles
Table 4 shows the functional requirements for UWASN application profiles.
Table 4 – Functional requirements for UWASN application profiles
Functional requirements Description
Data processing Data processing is used for performing the operations such as classifying,
retrieving, transforming, etc.
Device management Device management is used for the management of components such as
UWA-SNode, UWA-GW, etc.
Data acquisition The data acquisition function is used for measuring the physical
characteristics of water such as temperature, dissolved oxygen, pH value,
etc.
Validation process The validation process is used for application quality management, such as
whether the application meets its requirements or services.
Integration This is used to integrate different components to perform the required
functions.
Data communication Communication module and efficient protocols are required for long-range
and short-range communication.
Data storage The amount and type of data stored in UWA-SNode, UWA-CH, etc.
Identification The UWA-SNode needs a unique identifiable address.
The UWA-SNode, UWA-CH and UUV needs the ability to identify their
Self-localization
location.
In UWASN the functions like key distribution, data integrity and
Data security
authentication are used to increase the security level.
Key distribution The shared key mechanism can be used between the nodes such as UUV,
UWA-SNode, UWA-CH, etc. to increase the reliability of communication.
Integrity The integrity mechanism is used to increase the confidentiality while sending
and receiving data.
Authentication The authentication mechanism is used to ensure whether the messages are
generated from the authenticated user or not.
Network recovery The network recovery functions are used to reconnect the network when the
connection is broken.
Device recovery The devices such as UWA-SNodes, UUVs, etc. consist of all the information
related to environment. If some failures occur in the device, the device
recovery function shall be used.
Battery capacity To identify the maximum amount of power availability in underwater devices
such as UWA-SNodes, UUVs, etc. the battery capacity function is needed.
– 12 – ISO/IEC 30143:2020 © ISO/IEC 2020
The functional requirements are used to indicate the function performed by each component in
the UWASN system.
– The UWA-Application Layer: This layer is used to exchange information in the application
process. The main functionality of this application is to exchange data.
– The UWA-Bundle Layer: This layer is used to carry the group of information between the
layers such as application and network layer. The store and forward concepts are used for
transmitting the packets.
– The UWA-Network Layer: The main functionality of this layer is routing. The operations
performed by this layer are packet generation, underwater device communication, address
management, etc.
– The UWA-Data link Layer: The main functionality of this layer is controlling the
UWA-Physical Layer. This layer has the responsibility to check and correct the errors that
occur in the UWA-Physical Layer or devices.
– The UWA-Physical Layer: This layer is used to establish and maintain the connection
between the physical devices in underwater environments.
7.5 Constrained requirements of UWASN application profiles
7.5.1 General
Table 5 shows the constrained requirements for UWASN application profiles.
Table 5 – Constrained requirements for UWASN application profiles
Physical entities
Underwater
Surface
Constrained
requirements
Deployment
Network scale
Wired/wireless
communication
Service quality
Discovery ability
Localization
Time
synchronization
Network
management
Privacy
Routing
UWA-CH
UWA-GW
UUVs
UWA-SNode
Acoustic communication
Relay node
Battery
Housing case
Fouling cleaner
UWA-DTN-GW
Ad-hoc network
Moving gateway
Communication module
Acoustic modem
Access network
Backbone network
Physical entities
Underwater
Surface
Constrained
requirements
Battery life
management
Routing
management
Device
management
Data
communication
Maintenance
Connectivity
7.5.2 Connectivity
The connectivity of UWASN application should be described. Details of UWASN interoperability
between different physical entities can be found in ISO/IEC 30140-4.
7.5.3 UWA-GW
– Role of moving UWA-GW: The moving UWA-GW shall be used to collect different data from
different UWA-FN and transfer the data to a base station. This can connect different
networks from underwater network to terrestrial network by moving from one place to
another. For example, a ship can act as the moving UWA-GW.
– Role of fixed UWA-GW: The fixed UWA-GW shall be used to connect the terrestrial network
with the underwater network. This can collect the data from a single UWA-FN.
7.5.4 UWA-DTN-GW
The UWA-DTN-GW shall be used to support the interoperability of local networks by considering
long delays and by interpreting between regional systems.
7.5.5 Housing case
Waterproof housing shall be used in applications such as fish farming, environmental monitoring,
harbour security, etc. to protect the devices from corrosion and failure caused by water.
7.5.6 Fouling cleaner
Fouling cleaner shall be used in applications such as fish farming, environmental monitoring,
harbour security, etc. to clean mussels, weeds, and barnacles from the UWA-SNode
periodically.
7.5.7 Node deployment
Node deployment shall be used for the placement of devices such as UUVs, UWA-CH,
UWA-SNode, etc.
UWA-CH
UWA-GW
UUVs
UWA-SNode
Acoustic communication
Relay node
Battery
Housing case
Fouling cleaner
UWA-DTN-GW
Ad-hoc network
Moving gateway
Communication module
Acoustic modem
Access network
Backbone network
– 14 – ISO/IEC 30143:2020 © ISO/IEC 2020
7.5.8 Battery
Batteries are required for the management of power in underwater devices such as UUVs, UWA-
CH, UWA-SNode, etc.
8 Modelling techniques for designing UWASN application profiles
8.1 General
Modelling is an approach used for designing the application. Modelling is the main phase of the
application development, which should be performed before the development of application. In
UWASN, modelling is specialized because of constrained environmental conditions. The
modelling technique applied to develop the UWASN applications is the Unified Modelling
Language (UML). The UML based modelling techniques can be used for modelling the UWASN
applications such as environmental monitoring, fish farming, etc.
8.2 Use case model
8.2.1 General
The main purposes of the use case model are to view interactions between the elements in a
UWASN system and to show the objectives achieved by those interactions.
8.2.2 Elements of use case diagram
– Actors: In UWASN, the actors are the things that interact with the system, such as devices,
users, and other entities within the system. Examples of actors in UWASN are listed below
(see also Figure 1):
• base station;
• network manager;
• UUV;
• UWA-GW.
Figure 1 – Actor representation examples
– Use cases: In UWASN, the use cases are the actions performed by the actors inside the
system. Examples of use cases in UWASN are listed below (see also Figure 2):
• monitoring;
• maintenance;
• sensing information;
• validating information.
Figure 2 – Use case representation examples
– System boundary: This is the boundary line used for the separation of actors and use cases.
The system boundary for UWASN is represented using the symbol in Figure 3.
Figure 3 – System boundary representation example
8.2.3 Relationships
– Generalization: For representing the link between actors.
– Association: For representing the link between actor and use cases.
– Include: For breaking use cases into sub use cases.
– Extend: For showing the detailed execution of base use cases.
Relationship and symbols of use case diagram are shown in Table 6.
Table 6 – Relationship and symbols of use case diagram
Relationship Symbol
Label
Generalization
Label
Association
Include <>
<>
Extend
– 16 – ISO/IEC 30143:2020 © ISO/IEC 2020
Figure 4 – Use case model for UWASN application profiles
Figure 4 shows the actors, use cases, system boundary and relationships of UWASN application
profiles. The components like surface station, UWA-SNode, UWA-GW, network manager and
UUV are represented as actors. The actions performed by each of the actors are represented
as use cases. For example, the actions like sensing information, validating, transferring data to
UWA-CH are performed by UWA-SNodes. The relationships like association, includes and
extends are used for building the connection between actors and use cases, and also between
the use cases.
8.3 Sequence diagram model
8.3.1 General
In UWASN, the sequence diagram model is used by the application developers to model the
communication between the elements. It shows how the interaction works between the elements
in UWASN and also how the objects interact with other objects.
8.3.2 Elements of sequence diagram
1) Class: In sequence diagram, class describes the role of objects inside UWASN. The object
is represented using the symbol given in Figure 5.
Figure 5 – Object symbol in a sequence diagram
2) Execution place (Execution box): In sequence diagram, the execution place shows that the
object is busy with another process. The execution box is represented with the symbol given
in Figure 6.
Figure 6 – Execution box symbol in a sequence diagram
3) Lifelines: In sequence diagram, the lifelines are represented using vertical lines with dashes
(see Figure 7) which are used to indicate the presence of an object in the system.
Figure 7 – Lifeline representation in a sequence diagram
4) Messages: In sequence diagram, the messages are used for the interaction between the
objects. The messages are represented using the arrow symbols shown in Figure 8.
Figure 8 – Sequence diagram modelling for UWASN application profiles
– 18 – ISO/IEC 30143:2020 © ISO/IEC 2020
Figure 8 shows the sequence flow of messages between each object in the UWASN system.
The above sequence diagram consists of objects and message flows between the objects.
In the diagram, control room, surface station, UWA-GW and UUV, etc. are represented as
objects. Request for data, response, error correction, etc. are represented as the "message
flows" between the objects.
8.4 Class diagram model
8.4.1 General
In UWASN, the class diagram is used by the application developer to show the whole structure
of the UWASN system. It describes the attributes and the operations of each class in the system
and the relationship between them. The class diagram visually indicates the needs of the
application.
8.4.2 Elements of class diagram
1) Class name: This is the upper section of class diagram (see Figure 9), which represents the
name of the class.
2) Attributes: This is the middle section of class diagram (see Figure 9). The attributes are
considered as the properties of class.
3) Methods: This is the lower section of class diagram (see Figure 9), which describes the
operation or actions of the class.
Figure 9 – Representation of different sections in class diagram
4) Relationships: The relationships are separated into four categories:
– association;
– generalization;
– realization;
– dependency.
Figure 10 illustrates class diagram modelling for UWASN application profiles.
Figure 10 – Class diagram modelling for UWASN application profiles
9 Guidelines for the implementation of UWASN application profiles
9.1 Layered design approach for developing UWASN application profiles
The layered design technique, illustrated in Figure 11, is a combination of layers from the UWA-
Physical Layer to the UWA-Business Layer. This technique is used to control the connection
between each layer.
– 20 – ISO/IEC 30143:2020 © ISO/IEC 2020
Figure 11 – Layer design approach
9.2 Specific architecture for implementing UWASN application profiles
The UWASN specific architecture helps the user to plan, design, deploy and implement new
applications. For designing the architecture of UWASN application, the user follows the
application structure as shown in Figure 12.
Figure 12 – UWASN specific architectural model
– General description of architecture: A reference architecture with high-level description of
UWASN application is required. Configuration of UWASN
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.