Information technology - Wireless beacon-enabled energy efficient mesh network (WiBEEM) for wireless home network services - Part 3: NWK layer

ISO/IEC 29145-3:2014(E) specifies the network layer (NWK) of the WiBEEM (Wireless Beacon-enabled Energy Efficient Mesh network) protocol for wireless home network services that supports a low power-consuming wireless mesh network as well as device mobility and QoS.

General Information

Status
Published
Publication Date
05-Mar-2014
Current Stage
PPUB - Publication issued
Start Date
15-Jan-2014
Completion Date
06-Mar-2014
Ref Project
Standard
ISO/IEC 29145-3:2014 - Information technology - Wireless beacon-enabled energy efficient mesh network (WiBEEM) for wireless home network services - Part 3: NWK layer
English language
29 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


ISO/IEC 29145-3
Edition 1.0 2014-03
INTERNATIONAL
STANDARD
Information technology – Wireless beacon-enabled energy efficient mesh
network (WiBEEM) for wireless home network services –
Part 3: NWK layer
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é Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
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 corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing more than 30 000 terms and
Technical Specifications, Technical Reports and other definitions in English and French, with equivalent terms in 14
documents. Available for PC, Mac OS, Android Tablets and additional languages. Also known as the International
iPad. Electrotechnical Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a More than 55 000 electrotechnical terminology entries in
variety of criteria (reference number, text, technical English and French extracted from the Terms and Definitions
committee,…). It also gives information on projects, replaced clause of IEC publications issued since 2002. Some entries
and withdrawn publications. have been collected from earlier publications of IEC TC 37,

77, 86 and CISPR.
IEC Just Published - webstore.iec.ch/justpublished

Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
ISO/IEC 29145-3
Edition 1.0 2014-03
INTERNATIONAL
STANDARD
Information technology – Wireless beacon-enabled energy efficient mesh

network (WiBEEM) for wireless home network services –

Part 3: NWK layer
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
P
ICS 35.200 ISBN 978-2-8322-1450-3

– 2 – ISO/IEC 29145-3 © ISO/IEC 2014
CONTENTS
FOREWORD . 4
INTRODUCTION . 5
1 Scope . 6
2 Normative references . 6
3 Terms, definitions and abbreviations . 6
3.1 Terms and definitions . 6
3.2 Abbreviations . 7
3.3 Conventions . 8
4 Conformance . 8
5 Overview of the WiBEEM technology . 8
6 NWK layer specifications . 8
6.1 General . 8
6.2 NWK layer service specifications . 8
6.2.1 Overview . 8
6.2.2 NWK data service . 9
6.2.3 NWK management service . 12
6.2.4 Network formation . 14
6.2.5 Allowing devices to join . 16
6.2.6 Begin as a router . 18
6.2.7 Joining a network . 19
6.2.8 Joining a device directly to a network . 22
6.2.9 Leaving a network . 24
6.2.10 Resetting a device . 26
6.2.11 Receiver synchronisation . 27
6.2.12 Information base maintenance . 30
Bibliography . 34

Figure 1 – NWK layer structure . 9
Figure 2 – Message sequence chart for resetting the network layer . 27
Figure 3 – Message sequence chart for synchronising in a non-beaconing network . 30

Table 1 – NLDE-DATA.request parameters . 10
Table 2 – NLDE-DATA.confirm parameters . 11
Table 3 – NLDE-DATA.indication parameters . 12
Table 4 – Summary of primitives used by NWK layer . 12
Table 5 – NLME-NETWORK-DISCOVERY.request parameters . 13
Table 6 – NLME-WiBEEM-DISCOVERY.confirm paramters . 14
Table 7 – Network descriptor information fields . 14
Table 8 – NLME-WRC-OPERATING.request parameters . 15
Table 9 – NLME-NETWORK-FORMATION.confirm parameters . 16
Table 10 – NLME-ALLOW-JOINING.request . 17
Table 11 – NLME-ALLOW-JOINING.confirm parameters . 17

ISO/IEC 29145-3 © ISO/IEC 2014 – 3 –
Table 12 – NLME-SET-SUPERFRAME.request parameters . 18
Table 13 – NLME-SET-SUPERFRAME.confirm parameters . 19
Table 14 – NLME-JOIN.request parameters . 20
Table 15 – NLME-JOIN.indication parameters . 21
Table 16 – NLME-JOIN.confirm parameters . 22
Table 17 – NLME-DETERMINED-JOIN.request parameters . 22
Table 18 – Capability information parameter format . 23
Table 19 – NLME-DETERMINED-JOIN.confirm parameters . 23
Table 20 – NLME-LEAVE.request parameters . 24
Table 21 – NLME-LEAVE.indication parameters . 25
Table 22 – NLME-LEAVE.confirm parameters . 25
Table 23 – NLME-RESET.confirm parameters . 27
Table 24 – NLME-SYNC.request parameters . 28
Table 25 – NLME-SYNC.confirm parameters . 29
Table 26 – NLME-READ-NIB.request parameters . 30
Table 27 – NLME-READ-NIB.confirm parameters . 31
Table 28 – NLME-WRITE-NIB.request parameters . 32
Table 29 – NLME-WRITE-NIB.confirm parameters . 33

– 4 – ISO/IEC 29145-3 © ISO/IEC 2014
INFORMATION TECHNOLOGY –
WIRELESS BEACON-ENABLED ENERGY EFFICIENT MESH
NETWORK (WIBEEM) FOR WIRELESS HOME NETWORK SERVICES –

Part 3: NWK layer
FOREWORD
1) ISO (International Organization for Standardization) and IEC (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. Their preparation is entrusted to technical committees; any ISO and
IEC member body interested in the subject dealt with may participate in this preparatory work. International
governmental and non-governmental organizations liaising with ISO and IEC also participate in this preparation.
2) In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.
3) 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 member bodies.
4) IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted
by IEC 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.
5) In order to promote international uniformity, IEC 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 publication and the corresponding national or regional publication
should be clearly indicated in the latter.
6) ISO and IEC provide no marking procedure to indicate their approval and cannot be rendered responsible for
any equipment declared to be in conformity with an ISO/IEC publication.
7) All users should ensure that they have the latest edition of this publication.
8) 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 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.
9) 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.
10) Attention is drawn to the possibility that some of the elements of this International Standard 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 29145-3 was prepared by subcommittee 25: Interconnection
of information technology equipment, of ISO/IEC joint technical committee 1: Information
technology.
The list of all currently available parts of the ISO/IEC 29145 series, under the general title
Information technology – Wireless beacon-enabled energy efficient mesh network (WiBEEM)
for wireless home network services, can be found on the IEC web site.
This International Standard has been approved by vote of the member bodies, and the voting
results may be obtained from the address given on the second title page.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

ISO/IEC 29145-3 © ISO/IEC 2014 – 5 –
INTRODUCTION
This International Standard specifies the WiBEEM (Wireless Beacon-enabled Energy Efficient
Mesh network) protocol, which provides low-power-consuming mesh network functions by
enabling the “beacon mode operation”. WiBEEM is based on the IEEE 802.15.4 standard with
additional upper layer protocols and a specific usage of the MAC layer protocol. Through the
novel use of beacons, WiBEEM technology achieves longer battery life, larger network
support, quicker response, enhanced mobility and dynamic reconfiguration of the network
topology compared with other protocols such as ZigBee.
In the beacon mode, beacon information propagates over the entire mesh network nodes
during the BOP (Beacon-Only Period) of the superframe structure without any beacon
conflicts by utilising a smart beacon scheduling technique in the BOP. It also provides
location information about moving devices without spending extra time running a positioning
and locating algorithm by using RSSI (Received Signal Strength Indication). These features
allow the WiBEEM protocol to be widely used for wireless home network services in the
ubiquitous network era.
One of the key features of the WiBEEM protocol is that it has a special time interval called
BOP (Beacon-Only Period) in the superframe structure that allows more than two beacons to
be transmitted. This unique time period is located at the beginning of the Superframe.
Because the BOP does not use the CSMA/CA mechanism, the network will not work properly
in the beacon mode unless an appropriate algorithm is applied. This algorithm needs to
manage and control multiple beacons in a single superframe. The solution is the Beacon
Scheduling method applied in the BOP to avoid collisions among beacons, providing
synchronisation among all the nodes of the entire mesh network.
For the network layer, the NAA (Next Address Available) mechanism, which is a short address
allocation algorithm, has been adopted to provide an efficient way of utilising the complete 16-
bit address space. The NAA algorithm does not limit the maximum number of children nodes
that a node of a mesh network can have. Since the number of children nodes is unlimited, the
NAA mechanism allows the WiBEEM protocol to be used not only for home network services,
but also for community services. WiBEEM can be used where high network expandability
through efficient use of short address spaces, device mobility and end-to-end QoS are
required.
This part of ISO/IEC 29145 specifies the network layer (NWK) of the WiBEEM protocol for
wireless home network services that support a low-power-consuming wireless mesh network
as well as device mobility and QoS.

– 6 – ISO/IEC 29145-3 © ISO/IEC 2014
INFORMATION TECHNOLOGY –
WIRELESS BEACON-ENABLED ENERGY EFFICIENT MESH
NETWORK (WIBEEM) FOR WIRELESS HOME NETWORK SERVICES –

Part 3: NWK layer
1 Scope
This part of ISO/IEC 29145 specifies the network layer (NWK) of the WiBEEM (Wireless
Beacon-enabled Energy Efficient Mesh network) protocol for wireless home network services
that support a low-power-consuming wireless mesh network as well as device mobility and
quality of service.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
ISO/IEC 29145-1:2014, Information technology – Wireless beacon-enabled energy efficient
mesh network (WiBEEM) for wireless home network services – Part 1: PHY layer
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
association
service used to establish the membership of a device in a wireless mesh network
3.1.2
co-ordinator
wireless device configured to provide synchronisation services through the transmission of
beacons
Note 1 to entry: If a co-ordinator is the principal controller of a wireless mesh network, it is called the WMC
(WiBEEM mesh co-ordinator).
3.1.3
device
entity containing an implementation of the WiBEEM applications, NWK, MAC and physical
interface to the wireless medium
3.1.4
frame
data format of aggregated bits from a medium access control (MAC) layer entity transmitted in
a specified sequence
ISO/IEC 29145-3 © ISO/IEC 2014 – 7 –
3.1.5
packet
format of aggregated bits transmitted in a specified sequence across the physical medium
3.1.6
personal operating space
space of typically about 10 m around a person or an object, no matter whether this person or
object is stationary or in motion
3.1.7
protocol data unit
unit of data exchanged between two peer entities
3.1.8
WiBEEM end device
WiBEEM device acting as the leaf device of a mesh network
3.1.9
WiBEEM mesh co-ordinator
WiBEEM device acting as the principal controller of a mesh network
Note 1 to entry: A WiBEEM mesh network has exactly one WiBEEM mesh co-ordinator.
3.1.10
WiBEEM routable co-ordinator
WiBEEM device acting as the router of a mesh network
3.1.11
wireless medium
medium used to implement the transfer of protocol data units (PDUs) between peer physical
layer (PHY) entities of a low-rate wireless mesh network
3.2 Abbreviations
The following acronyms and abbreviations are used in this standard and commonly used in
other industry publications.
AES Advanced Encryption Standard
ARQ Automatic Request-Response
BO Beacon Order
BOP Beacon Only Period
BTTSL Beacon Transmit Time Slot Length
CAP Contention Access Period
ID Identifier
MIB Management Information Base
NAA Next Address Available
PDU Protocol Data Unit
PQP Prioritised QoS Period
QoS Quality of Service
RAP Reservation-Based Access Period
WED WiBEEM End Device
WiBEEM Wireless Beacon-enabled Energy Efficient Mesh network
WMC WiBEEM Mesh Co-ordinator
– 8 – ISO/IEC 29145-3 © ISO/IEC 2014
WRC WiBEEM Routable Co-ordinator
3.3 Conventions
All the italicised words used in this standard represent relevant constants defined and stored
in the MIB (management information base) of each layer.
4 Conformance
A WiBEEM device that claims conformance to this part of ISO/IEC 29145 shall implement all
the primitives that are specified in 6.2. Each WiBEEM device shall be able to act as a WMC, a
WRC and a WED. When operating in the role of a WMC it shall act as specified in 5.3.2 of
ISO/IEC 29145-1:2014, when operating in the role of a WRC, it shall act as specified in 5.3.3
of ISO/IEC 29145-1:2014, and when operating in the role of a WED, it shall act as specified in
5.3.3 of ISO/IEC 29145-1.
5 Overview of the WiBEEM technology
Clause 5 of ISO/IEC 29145-1:2014 presents an overview of the WiBEEM technology and the
functionalities of the WiBEEM devices.
6 NWK layer specifications
6.1 General
This clause specifies the NWK layer of this standard. The NWK layer handles network
management, message broker and routing. This clause specifies the services that shall be
provided by the WiBEEM NWK layer.
Constants and attributes that are specified and maintained by the MAC layer are written in the
text of this clause in italics. Constants have a general prefix of “a”. Attributes have a general
prefix of “mac”.
6.2 NWK layer service specifications
6.2.1 Overview
The NWK layer services provide an interface between the NWK layer and the APP layer. The
NWK layer provides two services, accessed through two SAPs:
– MAC data service, accessed through the NWK layer data SAP (NLDE-SAP); and
– NWK management service, accessed through the NLME-SAP.
Figure 1 depicts the elements and interfaces of NWK layer.

ISO/IEC 29145-3 © ISO/IEC 2014 – 9 –
NLME-WiBEEM-DISCOVERY.request
NLME-WiBEEM-DISCOVERY.confirm
NLME-WRC-OPERATING.request
NLME-WRC-OPERATING.confirm
NLME-ALLOW-JOINING.request
NLME-ALLOW-JOINING.confirm
NLME-SET-SUPERFRAME.request NLME-SET-SUPERFRAME.confirm
NLDE-DATA.confirm
NLME-JOIN.request
NLME-JOIN.confirm
NLDE-DATA.indication
NLME-DETERMINED-JOIN.request
NLME-JOIN.indication
NLME-LEAVE.request
NLME-DETERMINED-JOIN.confirm
NLME-RESET.request
NLME-LEAVE.confirm
NLME-SYNC.request
NLME-LEAVE.indication
NLME-READ-NIB.request
NLME-RESET.confirm
NLME-WRITE-NIB.request NLME-SYNC.confirm
NLME-SYNC.indication
NLDE-DATA.request
NLME-READ-NIB.confirm
NLME-WRITE-NIB.confirm
Next Higher Layer Entity
nwkBCSN
nwkPassiveAckTimeout
NLDE-SAP NLME-SAP
nwkMaxBroadcastRetries
nwkMaxChildren
nwkMaxDepth
nwkMaxRouters
nwkNeighborTable
nwkNetworkBroadcastDeliveryTime
NLDE NLME
nwkReportConstantCost
nwkRouteDiscoveryRetriesPermitted
NIB
nwkRouteTable
nwkSecureAllFrames
nwkSecurityLevel
MLDE-SAP MLME-SAP
nwkSymLink
nwkCapabilityformation
MAC Layer Entity
wakeupSuperframePeriod
Figure 1 – NWK layer structure
6.2.2 NWK data service
6.2.2.1 Overview
The NWK layer data entity SAP (NLDE-SAP) supports the transport of application protocol
data units (APDUs) between peer application entities.
6.2.2.2 NLDE-DATA.request
6.2.2.2.1 Function
This primitive requests the transfer of a data PDU (NSDU) from the local Application layer
entity to a single or multiple peer application layer entities.
6.2.2.2.2 Semantics of the service primitive
The semantics of this primitive is as follows:
DE-DATA.request (
DstAddr,
NsduLength,
Nsdu,
NsduHandle,
BroadcastRadius,
DiscoverRoute,
SecurityEnable
)
– 10 – ISO/IEC 29145-3 © ISO/IEC 2014
Table 1 specifies the parameters for the NLDE-DATA.request primitive.
Table 1 – NLDE-DATA.request parameters
Name Type Valid range Description
The network address of the entity or entities to
DstAddr Device address Specified by the DstAddr
which the NSDU is being transferred.
The number of octets comprising the NSDU
NsduLength integer
≤nwkcMaxPayloadSize
to be transferred.
The set of octets comprising the NSDU to be
Nsdu Set Of Octets –
transferred.
The handle associated with the NSDU to be
NsduHandle integer 0x00 to 0xff
transmitted by the NWK layer entity.
The distance, in hops, that a broadcast frame
BroadcastRadius integer 0x00 to 0xff
will be allowed to travel through the network.
The DiscoverRoute parameter may be used to
enable route discovery operations for the transit
of this frame.
DiscoverRoute Boolean TRUE or FALSE
TRUE = enable route discovery
FALSE = disable route discovery
The SecurityEnable parameter may be used
Security enable Boolean TRUE or FALSE to enable NWK layer security processing for
the current frame.
6.2.2.2.3 When generated
This primitive is generated by a local APS sublayer entity whenever a data PDU (NSDU) is to
be transferred to a peer APS sublayer entity.
6.2.2.2.4 Effect on receipt
On receipt of this primitive on a device that is not currently associated, the NWK layer will
issue an NLDE-DATA.confirm primitive with a status of INVALID_REQUEST.
On receipt of this primitive, the NLDE first constructs an NPDU in order to transmit the
supplied NSDU.
If, during processing, the NLDE issues the NLDE-DATA.confirm primitive prior to transmission
of the NSDU, all further processing is aborted.
6.2.2.3 NLDE-DATA.confirm
6.2.2.3.1 Function
This primitive reports the results of a request to transfer a data PDU (NSDU) from a local APS
sublayer entity to a single peer APS sublayer entity.
6.2.2.3.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLDE-DATA.confirm  (
NsduHandle,
Status
)
Table 2 specifies the parameters for the NLDE-DATA.confirm primitive.

ISO/IEC 29145-3 © ISO/IEC 2014 – 11 –
Table 2 – NLDE-DATA.confirm parameters
Name Type Valid range Description
The handle associated with the
nsduHandle Integer 0x00 to 0xff
NSDU being confirmed.
SUCCESS, TRANSACTION_OVERFLOW,
TRANSACTION_EXPIRED,
CHANNEL_ACCESS_FAILURE,
INVALID_GTS, NO_ACK, The status of the corresponding
Status Enumeration
UNAVAILABLE_KEY, request.
FRAME_TOO_LONG,
FAILED_SECURITY_CHECK,
or INVALID_PARAMETER
6.2.2.3.3 When generated
This primitive is generated by the local NLDE in response to the reception of an NLDE-
DATA.request primitive.
6.2.2.3.4 Effect on receipt
On receipt of this primitive the APS sublayer of the initiating device is notified of the result of
its request to transmit. If the transmission attempt was successful, the status parameter will
be set to SUCCESS. Otherwise, the status parameter will indicate the error.
6.2.2.4 NLDE-DATA.indication
6.2.2.4.1 Function
This primitive indicates the transfer of a data PDU (NSDU) from the NWK layer to the local
APS sublayer entity.
6.2.2.4.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLDE-DATA.indication  (
SrcAddress,
NsduLength,
Nsdu,
LinkQuality
)
Table 3 specifies the parameters for the NLDE-DATA.indication primitive.

– 12 – ISO/IEC 29145-3 © ISO/IEC 2014
Table 3 – NLDE-DATA.indication parameters
Name Type Valid range Description
SrcAddre 16-bit Device Any valid device address The individual device address from which the NSDU
originated.
address Except the broadcast
Address
NsduLength integer The number of octets comprising the NSDU being
≤nwkcMaxPayloadSize
indicated.
Nsdu Set of Object – The set of octets comprising the NSDU being indicated.
LinkQuality Integer 0x00 to 0xff The link quality indication delivered by the MAC on receipt
of this frame as a parameter of the MAC-DATA.indication
primitive.
6.2.2.4.3 When generated
This primitive is generated by the NLDE and issued to the APS sublayer on receipt of an
appropriately addressed data frame from the local MAC sublayer entity.
6.2.2.4.4 Effect on receipt
On receipt of this primitive the APS sublayer is notified of the arrival of data at the device.
6.2.3 NWK management service
6.2.3.1 Overview
The NWK layer management entity SAP (NLME-SAP) allows the transport of management
commands between the next higher layer and the NLME. Table 4 summarises the primitives
supported by the NLME through the NLME-SAP interface. See the following subclauses for
more details on the individual primitives.
Table 4 – Summary of primitives used by NWK layer
Name Request Indication Response Confirm
NLME-WiBEEM-DISCOVERY O   O
NLME-WRC-OPERATING O   O
NLME-ALLOW-JOINING O   O
NLME-WRITE-NIB-SUPERFRAME O   O
NLME-JOIN O O  O
NLME-DETERMINED-JOIN O   O
NLME-LEAVE O O  O
NLME-RESET O   O
NLME-SYNC O O  O
NLME-READ-NIB O   O
NLME-WRITE-NIB O   O
6.2.3.2 Network discovery
The NWK layer management entity SAP (NLME-SAP) supports the discovery of operating
networks. The primitives employed in network discovery are the NLME-NETWORK-
DISCOVERY primitives.
ISO/IEC 29145-3 © ISO/IEC 2014 – 13 –
6.2.3.3 NLME-WiBEEM-DISCOVERY.request
6.2.3.3.1 Function
This primitive allows the next higher layer to request that the NWK layer discover networks
currently operating within the POS.
6.2.3.3.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLME-WiBEEM-DISCOVERY.request (
ScanChannels,
ScanDuration
)
Table 5 specifies the parameters for the NLME- WiBEEM-DISCOVERY.request primitive.
Table 5 – NLME-NETWORK-DISCOVERY.request parameters
Name Type Valid range Description
The five most significant bits (b ,b ) are reserved. The 27 least
ScanChannels Bitmap 32 bit field
27 31
significant bits (b , b , . b ) indicate which channels are to be
0 1 26
scanned (1 = scan, 0 = do not scan) for each of the 27 valid channels.
ScanDuration Integer 0x00 to 0x0e A value used to calculate the length of time to spend scanning each
channel.
The time spent scanning each channel is (aBaseSuperframeDuration *
(2n + 1)) symbols, where n is the value of the ScanDuration parameter.
For more information on MAC subayer scanning.

6.2.3.3.3 When generated
This primitive is generated by the next higher layer of a device and issued to its NLME to
request the discovery of networks operating within the device’s personal operating space
(POS).
6.2.3.3.4 Effect on receipt
On receipt of this primitive, the NWK will attempt to discover networks operating within the
device’s POS by scanning over the channels specified in the ScanChannels argument for the
period specified in the ScanDuration parameter.
6.2.3.4 NLME-WiBEEM-DISCOVERY.confirm
6.2.3.4.1 Function
This primitive reports the results of a network discovery operation.
6.2.3.4.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLME-WiBEEM-DISCOVERY.confirm (
NetworkCount,
NetworkDescriptor,
Status
)
Table 6 below describes the arguments of the NLME-WiBEEM-DISCOVERY.confirm primitive.

– 14 – ISO/IEC 29145-3 © ISO/IEC 2014
Table 6 – NLME-WiBEEM-DISCOVERY.confirm paramters
Name Type Valid range Description
NetworkCount Integer 0x00 to 0xff Gives the number of networks discovered by the
search.
NetworkDescription List of network The list contains the A list of descriptors, one for each of the
descriptors number of elements given networks discovered. Table 10 gives a detailed
by the NetworkCount account of the content of each item.
parameter.
Status Enumeration SUCCESS, NO_BEACON, Result of scan request
or INVALID_PARAMETER
Table 7 gives a detailed account of the content of a network descriptor from the
NetworkDescriptor parameter.
Table 7 – Network descriptor information fields
Name Type Valid range Description
MeshID Integer 0x0000 to 0xffff The 16-bit Mesh identifier of the discovered
network.
LogicalChannel Integer Selected from the available The current logical channel occupied by the
logical channels supported network.
by the PHY
StackProfile Integer 0x00 to 0x0f A WiBEEM stack profile identifier indicating the
stack profile in use in the discovered network.
WiBEEMVersion Integer 0x00 to 0x0f The version of the WiBEEM protocol in use in
the discovered network.
BeaconOrder Integer 0 to 15 This specifies how often the MAC sublayer beacon is
to be transmitted by a given device on the network.
For a discussion of MAC sublayer beacon order.
SuperframeOrder Integer 0-BO or 15 For beacon-oriented networks, i.e. beacon order <15,
this specifies the length of the active period of the
superframe. For a discussion of MAC sublayer
superframe order.
PermitJoining Boolean TRUE or FALSE A value of TRUE indicates that at least one WRC on
the network currently permits joining, i.e. its NWK has
been issued an NLMEPERMIT-JOINING primitive
and the time limit, if given, has not yet expired.
SecurityLevel Integer 0x00 to 0x07 The security level in use on the discovered network.

6.2.3.4.3 When generated
This primitive is generated by the NLME and issued to its next higher layer on completion of
the discovery task initiated by an NLME-WiBEEM-DISCOVERY.request primitive.
6.2.3.4.4 Effect on receipt
On receipt of this primitive, the next higher layer is notified of the results of a network search.
6.2.4 Network formation
6.2.4.1 Overview
This set of primitives defines how the next higher layer of a device can initialise itself as the
WMC of a new network.
ISO/IEC 29145-3 © ISO/IEC 2014 – 15 –
6.2.4.2 NLME – WRC – OPERATING.request
6.2.4.2.1 Function
This primitive allows the next higher layer to request that the device start a new network with
itself as the WMC.
6.2.4.2.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLME-WRC-OPERATING.request   (
ScanChannels,
ScanDuration,
BeaconOrder,
SuperframeOrder,
MeshID,
BatteryLifeExtension,
BTTSL,
MaxBeaconTxNumber,
Profile ID
)
Table 8 specifies the parameters for the NLME-WRC-OPERATING.request primitive.
Table 8 – NLME-WRC-OPERATING.request parameters
Name Type Valid range Description
ScanChannels Bitmap 32-bit field The five most significant bits (b . ,b ) are reserved. The
,
27 31
27 least significant bits (b , b , . b ) indicate which
0 1 26
channels are to be scanned in preparation for starting a
network (1 = scan, 0 = do not scan) for each of the 27 valid
channels.
ScanDuration Integer 0 to 14 A value used to calculate the length of time to spend
scanning each channel. The time spent scanning each
channel is (aBaseSuperframeDuration* (2n + 1)) symbols,
where n is the value of the ScanDuration parameter.
BeaconOrder Integer 0 to 15 The beacon order of the network that the higher layers wish
to form.
SuperframeOrder Integer 0 to BO or 15 The superframe order of the network that the higher layers
wish to form.
MeshID Integer 0x0000 to 0xffff The 16-bit mesh identifier of the discovered network.
BatteryLifeExtension Boolean TRUE or FALSE If this value is TRUE, the NLME will request that the WMC is
started supporting battery life extension mode. If this value
is FALSE, the NLME will request that the WMC is started
without supporting battery life extension mode.
BTTSL BYTE 0x00 to 0xff The length of the beacon transmission time slot. This value
can be calculated by adding the size of the beacon and the
BeaconTxMargin.
MaxBeaconTxNumber BYTE 0x00 to 0xff The maximum number of beacons transmitted.
Profile ID BYTE 0x00 to 0xff The number that specifies its corresponding application. A
different application program is running based on this value.

6.2.4.2.3 When generated
This primitive is generated by the next higher layer of a WMC-capable device and issued to its
NLME to request the initialisation of itself as the WMC of a new network.

– 16 – ISO/IEC 29145-3 © ISO/IEC 2014
6.2.4.2.4 Effect on receipt
On receipt of this primitive by a device that is not capable of being a WMC of a network, the
NLME issues the NLME-NETWORK-FORMATION.confirm primitive with the status parameter
set to INVALID_REQUEST.
6.2.4.3 NLME-WRC-OPERATING.confirm
6.2.4.3.1 Function
This primitive reports the results of the request to initialise a WMC in a network.
6.2.4.3.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLME-NETWORKFORMATION.confirm (
Status
)
Table 9 specifies the parameters for the NLME-NETWORK-FORMATION.confirm primitive.
Table 9 – NLME-NETWORK-FORMATION.confirm parameters
Name Type Valid range Description
INVALID_REQUEST, STARTUP_FAILURE or any status value The result of the attempt to
Status Status
returned from the MLME-START.confirm primitive. initialise a WMC.

6.2.4.3.3 When generated
This primitive is generated by the NLME and issued to its next higher layer in response to an
NLME NETWORK-FORMATION.request primitive. This primitive returns a status value of
INVALID_REQUEST, STARTUP_FAILURE or any status value returned from the MLME
START.confirm primitive.
6.2.4.3.4 Effect on receipt
On receipt of this primitive, the next higher layer is notified of the results of its request to
initialise the device as a WMC. If the NLME has been successful, the status parameter will be
set to SUCCESS. Otherwise, the status parameter indicates the error.
6.2.5 Allowing devices to join
6.2.5.1 Overview
This primitive defines how the next higher layer of a WMC or WRC can request that devices
be permitted to join its network.
6.2.5.2 NLME-ALLOW-JOINING.request
6.2.5.2.1 Function
This primitive allows the next higher layer of a WMC or WRC to set its MAC sublayer
association permit flag for a fixed period during which it may accept devices onto its network.
6.2.5.2.2 Semantics of the service primitive
The semantics of this primitive is as follows:

ISO/IEC 29145-3 © ISO/IEC 2014 – 17 –
NLME-ALLOW-JOINING.request (
PermitDuration
)
Table 10 specifies the parameters for the NLME-ALLOW-JOINING.request primitive.
Table 10 – NLME-ALLOW-JOINING.request
Valid
Name Type Description
range
PermitDuration Integer 0x00 to The length of time in seconds during which the WMC or WRC will allow
0xff associations. The values 0x00 and 0xff indicate that permission is disabled
or enabled, respectively, without a specified time limit.

6.2.5.2.3 When generated
This primitive is generated by the next higher layer of a WMC or WRC and issued to its NLME
whenever it is desired to allow devices to join its network.
6.2.5.2.4 Effect on receipt
It is only permissible that the next higher layer of a WMC or WRC issue this primitive. On
receipt of this primitive by the NWK layer of a WED, the NLME-PERMIT-JOINING.confirm
primitive returns a status of INVALID_REQUEST.
6.2.5.3 NLME-ALLOW-JOINING.confirm
6.2.5.3.1 Function
This primitive allows the next higher layer of a WMC or WRC to be notified of the results of its
request to permit the acceptance of devices onto the network.
6.2.5.3.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLME-ALLOW-JOINING.confirm (
Status
)
Table 11 specifies the parameters for the NLME-ALLOW-JOINING.confirm primitive.
Table 11 – NLME-ALLOW-JOINING.confirm parameters
Name Type Valid range Description
Any status returned from the MLME-SET.confirm The status of the corresponding
Status Status
primitive request.
6.2.5.3.3 When generated
This primitive is generated by the initiating NLME of a WMC or WRC and issued to its next
higher layer in response to an NLME-PERMIT-JOINING.request. The status parameter either
indicates the status received from the MAC sublayer or an error code of INVALID_REQUEST.

– 18 – ISO/IEC 29145-3 © ISO/IEC 2014
6.2.5.3.4 Effect on receipt
On receipt of this primitive, the next higher layer of the initiating device is notified of the
results of its request to permit devices to join the network.
6.2.6 Begin as a router
6.2.6.1 Overview
This set of primitives allows a WRC that is newly joined to a network to setup its superframe
configuration. It may also be used by a WMC or WRC to reconfigure its superframe.
6.2.6.2 NLME-SET-SUPERFRAME.request
6.2.6.2.1 Function
This primitive allows the next higher layer of a WRC to initialise or change its superframe
configuration. It also allows the next higher layer of a WMC to change its superframe
configuration.
6.2.6.2.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLME-SET-SUPERFRAME.request (
BeaconOrder,
SuperframeOrder,
BatteryLifeExtension
)
Table 12 specifies the parameters for NLME-SET-SUPERFRAME.request.
Table 12 – NLME-SET-SUPERFRAME.request parameters
Name Type Valid range Description
BeaconOrder Integer 0 to 15 The beacon order of the network that the higher layers wish to
form.
SuperframeOrder Integer 0 to BO or 15 The superframe order of the network that the higher layers wish
to form.
BatteryLifeExtension Boolean TRUE or FALSE If this value is TRUE, the NLME will request that the WMC is
started supporting battery life extension mode. If this value is
FALSE, the NLME will request that the WMC is started without
supporting battery life extension mode.

6.2.6.2.3 When generated
This primitive is generated by the next higher layer of a new device and issued to its NLME to
request the initialisation of itself as a WRC. It may also be issued to the NLME of a device
that is already operating as a WMC or WRC to adjust the configuration of its superframe.
6.2.6.2.4 Effect on receipt
On receipt of this primitive by a device that is not already joined to a network as a WRC, the
NLME issues the NLME-START-ROUTER.confirm primitive with the Status parameter set to
INVALID_REQUEST.
To initialise a new superframe configuration or to reconfigure an already existing one, the
NLME issues the MLME-START.request primitive to the MAC sublayer. The
CoordRealignment parameter in the MLME-START.request primitive is set to FALSE if the

ISO/IEC 29145-3 © ISO/IEC 2014 – 19 –
primitive is issued to initialise a new superframe. The CoordRealignment parameter is set to
TRUE if the primitive is issued to change any of the PAN configuration attributes.
6.2.6.3 NLME-SET-SUPERFRAME.confirm
6.2.6.3.1 Function
This primitive reports the results of the request to initialise or change the superframe
configuration of a WRC. If the device is a WMC, then the primitive reports the results of the
request to change the superframe configuration.
6.2.6.3.2 Semantics of the service primitive
The semantics of this primitive is as follows:
NLME-SET-SUPERFRAME.confirm  (
Status
)
Table 13 specifies the parameters for NLME-SET-SUPERFRAME.confirm.
Table 13 – NLME-SET-SUPERFRAME.confirm parameters
Name Type Valid range Description
INVALID_REQUEST or any status value returned from the MLME- The result of the attempt to
Status Status
START.confirm primitive. initialise a WMC.

6.2.6.3.3 When generated
This primitive is generated by the NLME and issued to its next higher layer in response to an
NLME-SET-SUPERFRAME.request primitive. This primitive returns a status value of
INVALID_REQUEST or any status value returned from the MLME-START.confirm primitive.
6.2.6.3.4 Effect on receipt
On receipt of this primitive, the next higher layer is notified of the results of its request to
initialise or change the superframe configuration of a WRC or to change the superframe
configuration of a WMC. If the NLME has been successful, the status parameter will be set to
SUCCESS. Otherwise, the status parameter indicates the error.
6.2.7 Joining a network
6.2.7.1 Overview
This set of primitives defines how the next higher layer of a device can
• request to join a network through assoc
...

Questions, Comments and Discussion

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

Loading comments...