Internet of Things (IoT) - Underwater acoustic sensor network (UWASN) - Network management system - Part 2: Underwater management information base (u-MIB)

ISO/IEC 30142-2:2022 (E) provides the underwater management information base (u-MIB) of the underwater network management system (U-NMS). It specifies the following:
– general requirements for constructing u-MIB in U-NMS;
– designing the managed objects of the manager and agent u-MIB;
– integrating the managed objects of the manager and agent u-MIB

General Information

Status
Published
Publication Date
16-Aug-2022
Current Stage
PPUB - Publication issued
Completion Date
17-Aug-2022
Ref Project

Buy Standard

Standard
ISO/IEC 30142-2:2022 - Internet of Things (IoT) - Underwater acoustic sensor network (UWASN) - Network management system - Part 2: Underwater management information base (u-MIB)
English language
31 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

ISO/IEC 30142-2
Edition 1.0 2022-08
INTERNATIONAL
STANDARD
colour
inside
Internet of Things (IoT) – Underwater acoustic sensor network (UWASN) –
Network management system –
Part 2: Underwater management information base (u-MIB)
ISO/IEC 30142-2:2022-08(en)
---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2022 ISO/IEC, Geneva, Switzerland

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 Secretariat 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 IEC Products & Services Portal - products.iec.ch

The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the

variety of criteria (reference number, text, technical publications previews. With a subscription you will always have

committee, …). It also gives information on projects, replaced access to up to date content tailored to your needs.

and withdrawn publications.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 300 terminological entries in English
details all new publications released. Available online and once
and French, with equivalent terms in 19 additional languages.
a month by email.
Also known as the International Electrotechnical Vocabulary
(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc
If you wish to give us your feedback on this publication or need
further assistance, please contact the Customer Service
Centre: sales@iec.ch.
---------------------- Page: 2 ----------------------
ISO/IEC 30142-2
Edition 1.0 2022-08
INTERNATIONAL
STANDARD
colour
inside
Internet of Things (IoT) – Underwater acoustic sensor network (UWASN) –
Network management system –
Part 2: Underwater management information base (u-MIB)
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 35.110 ISBN 978-2-8322-4503-3

Warning! Make sure that you obtained this publication from an authorized distributor.

---------------------- Page: 3 ----------------------
– 2 – ISO/IEC 30142-2:2022 © ISO/IEC 2022
CONTENTS

FOREWORD ........................................................................................................................... 4

INTRODUCTION ..................................................................................................................... 6

1 Scope .............................................................................................................................. 7

2 Normative references ...................................................................................................... 7

3 Terms and definitions ...................................................................................................... 7

4 Abbreviated terms ........................................................................................................... 8

5 u-MIB overview and basic concepts ................................................................................. 8

5.1 u-MIB definition ....................................................................................................... 8

5.2 Necessity of u-MIB in U-NMS .................................................................................. 9

5.3 U-NMS system architecture for using u-MIB ............................................................ 9

5.4 Structure of u-MIB ................................................................................................. 10

5.4.1 General ......................................................................................................... 10

5.4.2 u-MIB objects ................................................................................................ 10

5.4.3 u-MIB OIDs .................................................................................................... 10

5.4.4 u-MIB OID hierarchy ...................................................................................... 10

5.5 General format of managed objects in u-MIB ........................................................ 11

6 General requirements for constructing u-MIB in U-NMS ................................................. 12

7 Designing the managed objects of manager and agent u-MIB ........................................ 14

7.1 Object identifiers of u-MIB ..................................................................................... 14

7.2 Classification of u-MIB tables ................................................................................ 15

7.3 Classification of MOs in the manager and agent u-MIB ......................................... 15

7.4 MOs of u-MIB Trap ............................................................................................... 22

8 Integrating MOs of the manager and agent u-MIB .......................................................... 23

Annex A (informative) u-MIB Module .................................................................................... 25

A.1 Example of creating u-MIB objects ........................................................................ 25

A.2 Example of accessing MOs between manager and agent ...................................... 28

Bibliography .......................................................................................................................... 31

Figure 1 – Elements of u-MIB in U-NMS .................................................................................. 8

Figure 2 – U-NMS system architecture for using u-MIB ......................................................... 10

Figure 3 – u-MIB hierarchy structure ..................................................................................... 11

Figure 4 – General format of u-MIB ....................................................................................... 12

Figure 5 – MOs of the manager and agent u-MIB .................................................................. 16

Figure 6 – Structure of event_trap ......................................................................................... 22

Figure 7 – Integration of MOs between manager and agent u-MIB ........................................ 23

Figure 8 – MOs' requests via the network management protocol ........................................... 24

Figure A.1 – Device battery information requests via u-MIB in U-NMS .................................. 29

Figure A.2 – Example of MO value access from u_MIB ......................................................... 30

Table 1 – u-MIB object groups .............................................................................................. 11

Table 2 – Attributes used for representing MOs in u-MIB ...................................................... 12

Table 3 – Underwater network requirements of u-MIB in U-NMS ........................................... 12

Table 4 – Mandatory underwater device requirements of u-MIB in U-NMS ............................ 13

---------------------- Page: 4 ----------------------
ISO/IEC 30142-2:2022 © ISO/IEC 2022 – 3 –

Table 5 – Mandatory data type requirements of u-MIB in U-NMS .......................................... 14

Table 6 – OIDs of u-MIB ....................................................................................................... 14

Table 7 – Defining u-MIB tables ............................................................................................ 15

Table 8 – MOs of u_networks ............................................................................................... 17

Table 9 – MOs of u_devices .................................................................................................. 19

Table 10 – MOs of u_trap object in u-MIB ............................................................................. 22

---------------------- Page: 5 ----------------------
– 4 – ISO/IEC 30142-2:2022 © ISO/IEC 2022
INTERNET OF THINGS (IoT) –
UNDERWATER ACOUSTIC SENSOR NETWORK (UWASN) –
NETWORK MANAGEMENT SYSTEM –
Part 2: Underwater management information base (u-MIB)
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.

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 and ISO National bodies.

3) IEC and ISO documents have the form of recommendations for international use and are accepted by IEC and

ISO National bodies in that sense. While all reasonable efforts are made to ensure that the technical content of

IEC and ISO documents is accurate, IEC and 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 and ISO National bodies undertake to apply IEC and

ISO documents transparently to the maximum extent possible in their national and regional publications. Any

divergence between any IEC and ISO document and the corresponding national or regional publication shall be

clearly indicated in the latter.

5) IEC and ISO do not provide any attestation of conformity. Independent certification bodies provide conformity

assessment services and, in some areas, access to IEC and ISO marks of conformity. IEC and ISO 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 document.

7) No liability shall attach to IEC and ISO or their directors, employees, servants or agents including individual

experts and members of its technical committees and IEC and ISO National 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, use of, or reliance upon, this ISO/IEC document or any

other IEC and ISO documents.

8) Attention is drawn to the Normative references cited in this document. Use of the referenced publications is

indispensable for the correct application of this document.

9) Attention is drawn to the possibility that some of the elements of this ISO/IEC document may be the subject of

patent rights. IEC and ISO shall not be held responsible for identifying any or all such patent rights.

10) The managed objects need to highlight specifically throughout this document. Therefore, the managed objects in

this document are highlighted with italic font style.

ISO/IEC 30142-2 has been prepared by subcommittee 41: Internet of Things and Digital Twin,

of ISO/IEC joint technical committee 1: Information technology. It is an International Standard.

The text of this International Standard is based on the following documents:
Draft Report on voting
JTC1-SC41/288/FDIS JTC1-SC41/296/RVD

Full information on the voting for its approval can be found in the report on voting indicated in

the above table.
The language used for the development of this International Standard is English.

This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in

accordance with ISO/IEC Directives, Part 1, available at www.iec.ch/members_experts/refdocs

and www.iso.org/directives.
---------------------- Page: 6 ----------------------
ISO/IEC 30142-2:2022 © ISO/IEC 2022 – 5 –

In order to highlight specifically the managed objects in this document, the managed objects

are written in italics throughout this document.

A list of all parts in the ISO/IEC 30142 series, published under the general title Internet of

Things (IoT) – Underwater acoustic sensor network (UWASN) – Network management system,

can be found on the IEC website.

IMPORTANT – The "colour inside" logo on the cover page of this document 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.
---------------------- Page: 7 ----------------------
– 6 – ISO/IEC 30142-2:2022 © ISO/IEC 2022
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.

To build and apply the UWASN technology, most suitable methods for managing the network

have been developed based on the ISO/IEC 30140 series. This document describes the network

management outline and requirements appropriate to the UWASN under the constraints of an

underwater physical environment.

The ISO/IEC 30142 series provides information such as requirements of an underwater network

management system (U-NMS), functions supporting U-NMS, and components required for

U-NMS in UWASN.

This document provides the underwater management information base (u-MIB) for the U-NMS.

u-MIB is a hierarchical database specifically designed for managing the networks or devices in

the underwater network management system of UWASN.

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.
---------------------- Page: 8 ----------------------
ISO/IEC 30142-2:2022 © ISO/IEC 2022 – 7 –
INTERNET OF THINGS (IoT) –
UNDERWATER ACOUSTIC SENSOR NETWORK (UWASN) –
NETWORK MANAGEMENT SYSTEM –
Part 2: Underwater management information base (u-MIB)
1 Scope
This document provides the underwater management information base (u-MIB) of the
underwater network management system (U-NMS). It specifies the following:
– general requirements for constructing u-MIB in U-NMS;
– designing the managed objects of the manager and agent u-MIB;
– integrating the managed objects of the manager and agent u-MIB.
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 terminology databases for use in standardization at the following

addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1
managed object

abstract representation of an underwater object or resource in u-MIB that is managed using an

underwater network management system
3.2
managed objects

collection of underwater objects or resources that are defined in the underwater management

information base (u-MIB)

Note 1 to entry: The managed objects (MOs) are the component used for exchanging the information between

manager and agent in U-NMS.
3.3
management protocol
protocol used for carrying information between the manager and agent in U-NMS
3.4
TABLE

data type that holds a collection of information related to underwater networks and underwater

devices
EXAMPLE The notification record.
---------------------- Page: 9 ----------------------
– 8 – ISO/IEC 30142-2:2022 © ISO/IEC 2022
3.5
OBJID
data type that holds the unique identity of each managed object
4 Abbreviated terms
MO managed object
MOs managed objects
MIB management information base
OID object identifier
u-MIB underwater management information base
U-NMS underwater network management system
UUV unmanned underwater vehicle
UWA-CH underwater acoustic cluster head
UWA-GW underwater acoustic gateway
UWA-SNode underwater acoustic sensor node
5 u-MIB overview and basic concepts
5.1 u-MIB definition

Underwater management information base (u-MIB) is a database specifically designed for

managing the elements or entities in the underwater network management system (U-NMS).

Figure 1 shows the elements of U-NMS where u-MIB is included. The u-MIB is included in the

elements such as a manager and an agent.

– In U-NMS, the manager is the program installed in the devices to control the whole functions

of underwater networks.

– The agent is the program that is bundled inside the underwater devices such as UWA-GW,

UWA-CH, UUV, UWA-SNode, etc.

– Management protocol defines the format of a packet exchange between a manager and an

agent in U-NMS.

– u-MIB creates the collection of managed objects (MOs) that uses the structured format for

defining the name and objects which are adapted to U-NMS.
Figure 1 – Elements of u-MIB in U-NMS
---------------------- Page: 10 ----------------------
ISO/IEC 30142-2:2022 © ISO/IEC 2022 – 9 –
5.2 Necessity of u-MIB in U-NMS

The environmental condition of underwater networks is considerably different from that of

terrestrial area networks. Hence, the underwater network management system is necessary to

handle the networks and devices in the underwater environment. In this case, it is difficult to

adapt the legacy management information base (MIB) to the underwater environment because

of the following factors.

a) The resource availability of underwater devices is extremely different from terrestrial

devices.

b) MIB in terrestrial area networks holds a huge number of MOs. Hence, it is heavyweight and

therefore it is difficult to adapt it to underwater devices .

Therefore, it is necessary to establish a unique underwater MIB based on the condition of the

underwater environment by reducing the MOs. The reduced MOs can be termed "u-MIB", which

has the key functions of U-NMS and is utilized to monitor the status of devices and networks in

the underwater environment.
The specific roles of u-MIB in U-NMS are given below.

– Used as the database: u-MIB is used by the manager and agent for storing and retrieving

information in U-NMS.

– Avoiding complexity: u-MIB is the lightweight version with limited MOs. Therefore, it is

suitable for the U-NMS components such as manager and agent. This can avoid the
complexity in U-NMS.

– Easy adaptation/management: Due to the dynamic changes in the underwater environment,

the MOs need to be created based on the problems in U-NMS such as memory problems,

battery problems, connection problems, etc. Therefore, the U-NMS components can be

adapted or managed easily in the underwater environment.
5.3 U-NMS system architecture for using u-MIB

Figure 2 shows the U-NMS system architecture for using u-MIB, which indicates the formation

of u-MIB in U-NMS components such as the manager, and agent. The u-MIB is installed

separately into the manager and agent components of U-NMS. The installed MOs are extremely

different for both manager and agent u-MIB. The methods such as Get Request, Get Response,

Set Request and Set Response are used by the manager to MOs from the agent. Trap is the

notification message sent by the agent if some critical events occur in underwater devices such

as the increase in temperature, reduced battery charge, out of memory space, etc. The

exchange of messages between the manager and agents is performed using the network

management protocol.
---------------------- Page: 11 ----------------------
– 10 – ISO/IEC 30142-2:2022 © ISO/IEC 2022
Figure 2 – U-NMS system architecture for using u-MIB
5.4 Structure of u-MIB
5.4.1 General

In general, the u-MIB is designed using the collection of MOs constructed in a hierarchical

structure, as shown in Figure 3.
5.4.2 u-MIB objects

It is the collection of MOs in U-NMS. u-MIB objects comprise management information of each

device in U-NMS built in a structured format.
5.4.3 u-MIB OIDs

The object identifiers (OIDs) in u-MIB allow the U-NMS to access information inside the U-NMS

devices.
5.4.4 u-MIB OID hierarchy

The OIDs of u-MIB are described in a hierarchical format (u-MIBObjects u_networks and u-

MIBObjects u_devices).
– u-MIBObjects;
– u_networks;
– u_devices.
u-MIB in U-NMS can be categorized into two sections.

a) u_networks: It is also known as underwater network information. In this case, OIDs are

utilized to manage the network link between U-NMS devices.

MOs of network management are built under the name u_networks in u-MIBObjects. For

example, checking the connectivity between the devices.
---------------------- Page: 12 ----------------------
ISO/IEC 30142-2:2022 © ISO/IEC 2022 – 11 –

b) u_devices: It is also known as underwater device information. In this case, OIDs are utilized

to manage the specific devices in U-NMS, such as the proxy agent, master agent, and

subagent.
MOs of device management are built under the name u_devices in u-MIBObjects. For

example, underwater devices battery management is the u-MIBObjects under u-devices.

Figure 3 – u-MIB hierarchy structure

Table 1 shows the two-essential u-MIB object groups of U-NMS such as u_networks and

u_devices.
Table 1 – u-MIB object groups
u-MIB Objects Type Object Object Identifier Name
Identifier
u_networks GROUP 1.1 u-MIBObjects(1).u_networks(1)
u_devices GROUP 1.2 u-MIBObjects(1).u_devices(2)
5.5 General format of managed objects in u-MIB

Figure 4 shows the general structure of u-MIB objects in U-NMS. u-MIB includes a collection of

MOs that include the network management information of underwater devices. Each MO is

designed using the name, data type, right to access, status indicator, and object description

customized to underwater communication. Interface description language is used for defining

MOs in u-MIB. The structured format is used for defining the name and objects in u-MIB.

---------------------- Page: 13 ----------------------
– 12 – ISO/IEC 30142-2:2022 © ISO/IEC 2022
Figure 4 – General format of u-MIB
Table 2 shows the attributes for defining MOs in U-NMS.
Table 2 – Attributes used for representing MOs in u-MIB
Keywords Description

OBJECT-NAME It describes the name of the objects such as MIB version, device name, etc.

DATA-TYPE It describes the data types corresponding to the OBJECT-NAME, such as INTEGER,

STRING, etc.

RIGHT-TO-ACCESS It indicates permission to retrieve objects such as read-write, read-only, etc.

STATUS-INDICATOR It describes whether the object is mandatory or optional.
OBJECT-DESCRIPTION It defines the textual description of objects.
6 General requirements for constructing u-MIB in U-NMS

The general requirements of u-MIB design are based on two parts: (1) underwater network

requirements for designing u-MIB, and (2) underwater devices requirements for designing u-

MIB. The underwater network specification requirements are established based on the factors

considering the networks in the underwater environment. Table 3 shows the requirements of

underwater networks for designing u-MIB.
Table 3 – Underwater network requirements of u-MIB in U-NMS
Name Description

Networks connectivity information Network type, link quality, signal strength, number of devices connected,

network active time with devices, network suspended time with devices,
etc. shall be used in u-MIB to identify the network connectivity status in
underwater networks.

Networks packets information The packets information of underwater networks such as packets received,

packets transferred, Get Request, Set Request, etc. shall be used to send
or receive the packets in underwater networks.

Networks notification Trap messages shall be used in underwater networks when some critical

events occur in networks such as link failure and authentication failure.
---------------------- Page: 14 ----------------------
ISO/IEC 30142-2:2022 © ISO/IEC 2022 – 13 –

The underwater device specification requirements are separated into two parts: (1) object

information, and (2) object status. The object information represents the general information

about the underwater object such as device name, device manufacturer name, device ID, etc.

The object status represents the device status such as battery damaged, out of memory, etc.

Table 4 shows the mandatory requirements of underwater devices for designing u-MIB.

Table 4 – Mandatory underwater device requirements of u-MIB in U-NMS
Name Description
Device information The information such as u_devices_ID, u_devices_firmware,
u_devices_manufacturer_name, u_devices_type, etc. shall be used to identify the
general information of devices in underwater networks.
Device status information shall be used to indicate the status of underwater
Device status
devices such as u_devices_active_time, u_devices_location,
u_devices_suspendedtime, etc.
Information such as u_devices_battery_available, u_devices_battery_total, and
Battery information
u_devices_battery_used shall be used to indicate the resource availability of
battery in underwater devices.

Battery status The battery status information shall be used to report the current status of the

battery in underwater devices such as u_devices_battery_damaged,
u_devices_battery_low, u_devices_battery_normal, etc.

Memory information The information such as u_devices_memory_available, u_devices_memory_total,

and u_devices_memory_used shall be used to indicate the resource availability of
memory in underwater devices.

Memory status The memory status information shall be used to report the current status of

memory in underwater devices such as u_devices_memory_damaged,
u_devices_memory_low, etc.
Location information The information such as u_devices_address, u_devices_depth,

u_devices_received_time, etc. shall be used to identify the position of underwater

devices.

Connectivity information The information such as u_devices_network_type, u_devices_signal_link_quality,

u_devices_signal_strength, etc. shall be used to find the connectivity between the

devices in underwater networks.

Message information The information such as u_devices_max_size, u_devices_rcvd_bits, etc. shall be

used to report total data collected in underwater networks such as the total
number of messages received, the total number of messages sent, etc.

Notification information The information such as u_devices_event_code, u_devices_event_description,

u_devices_event_name, u_devices_event_send_time, etc. shall be used to

describe the critical event information in detail such as event name, event code,

event ID, event time, etc.

The notification status information shall be used to report the critical situation of

Notification status
underwater devices such as u_devices_battery_trap, u_devices_link_failure_trap,
u_devices_low_signal_trap, etc.

Temperature status The temperature status information shall be used to report the current

temperature status of underwater devices such as u_devices_curr_temp_level,
and u_devices_notify_temp_limit.
Table 5 shows the mandatory data types required for designing u-MIB in U-NMS.
---------------------- Page: 15 ----------------------
– 14 – ISO/IEC 30142-2:2022 © ISO/IEC 2022
Table 5 – Mandatory data type requirements of u-MIB in U-NMS
Types Description
INTEGER It indicates the MO value of u-MIB that holds a whole number.
It indicates the MO value of u-MIB which uses the combination of a whole number
FLOAT
and a decimal number.

STRING It indicates the MO value of u-MIB with a sequence of characters, which also

includes special characters and numbers.
OBJID It indicates MO's position in u-MIB
TABLE It indicates types of data inside columns and variables in u-MIB.

TIME It indicates the DATETIME value inside the u-MIB as two integers. One represents

the date and the other represents the time.

BOOLEAN It indicates the MO value of u-MIB that holds either one of two values. For example,

true or false.
LOCATION It indicates the MO value of type LOCATION (value1, value2, valu
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.