ISO/IEC/IEEE 8802-15-6:2017 情報技術—システム間の電気通信と情報交換—ローカルおよびメトロポリタンエリアネットワーク—特定の要件—パート15-6：ワイヤレスボディエリアネットワーク | ページ 5

3.1.1

abbreviated address

A one-octet identifier (ID) selected as an address for a node, hub, or body area network (BAN) in frame exchanges.

3.1.2

active state

An internal power management state that is ready for frame reception and transmission.

3.1.3

active superframe

A superframe in which frame transmission typically occurs within the body area network (BAN) of the hub announcing such a superframe.

3.1.4

allocation

One or more time intervals that a node or a hub obtains using an access method for initiating one or more frame transactions. An allocation comprises one or more allocation intervals. Reference to allocation of a node means that the node is the sender or recipient in the allocation.

3.1.5

allocation interval

A continuous time interval in an allocation, comprising one or more consecutive allocation slots. Reference to allocation interval of a node means that the node is the sender or recipient in the allocation interval.

3.1.6

allocation slot

A time unit used to designate the lengths of medium access related time intervals, such as beacon period (superframe) and allocation interval.

3.1.7

beacon

A frame transmitted by a hub to facilitate network management, such as the coordination of medium access and power management of the nodes in the body area network (BAN) of the hub, and to facilitate clock synchronization therein.

3.1.8

beacon period

A repetitive time interval to which medium access is referenced and in which a beacon is transmitted when appropriate, comprising the same number of time units (allocation slots) of equal duration.

3.1.9

bilink

A communications link for transfer of management and data traffic from a hub to a node or/and vice versa.

3.1.10

bilink allocation

An allocation with allocation interval(s) in which a hub or a node initiates one or more frame transactions to transmit management and data traffic to a node or a hub, respectively, and the recipient returns acknowledgment if required, with the provision that the node initiates frame transaction(s) only after receiving a poll from the hub.

3.1.11

connected node

A node that has a connection with a hub.

3.1.12

connection

A relationship between a node and a hub in a body area network (BAN), substantiated by a connected node identification assigned to the node by the hub and by a wakeup arrangement between them, and optionally by one or more scheduled allocations or unscheduled bilink allocations between them.

3.1.13

contended allocation

A non-reoccurring time interval, within a random access phase (RAP) or a contention access phase (CAP), that a node obtains using random access for initiating a frame transaction. A contended allocation is an uplink allocation, suitable for servicing “unpredictable” uplink traffic (for example, due to data rate variations and/or channel impairments).

3.1.14

contention access

An access method, based on carrier sense multiple access with collision avoidance (CSMA/CA) or slotted Aloha access but not both, whereby a node obtains a time interval in a contention access phase (CAP) for initiating one or more frame transactions. As an access method, contention access is synonymous with random access.

3.1.15

contention access phase (CAP)

A time span set aside by a hub and announced via a preceding non-beacon frame for contention access to the medium by the nodes in the body area network (BAN) of the hub.

3.1.16

downlink

A communications link for transfer of management and data traffic from a hub to a node.

3.1.17

downlink allocation

An allocation with allocation interval(s) in which a hub initiates one or more frame transactions to transmit management and data traffic to a node and the node returns acknowledgment if required.

3.1.18

entity authentication

Corroboration of the identity of the node or the hub in a security association procedure.

3.1.19

exclusive access phase (EAP)

A time span set aside by a hub in a beacon period (superframe) for transfer of the traffic of the highest user priority (UP) (for emergency or medical implant event report).

3.1.20

frame

An uninterrupted sequence of octets delivered by the medium access control (MAC) sublayer to the physical (PHY) layer, or vice versa, within a node or a hub.

3.1.21

hub

An entity that possesses a node’s functionality and coordinates the medium access and power management of the nodes in its body area network (BAN).

3.1.22

hub identifier (HID)

An abbreviated address of a hub.

3.1.23

improvised access

An access method, based on impromptu polling or posting by a hub, whereby a hub grants to a node or itself a polled or posted allocation, typically outside scheduled downlink and uplink allocations, for initiating one or more frame transactions by the node or hub, respectively.

3.1.24

inactive state

An internal power management state that is not ready for frame reception and transmission.

3.1.25

inactive superframe

A superframe in which no frame transmission occurs within the body area network (BAN) of the hub announcing such a superframe.

3.1.26

information element (IE)

An optional part, with variable but self-identifiable length, of some frames.

3.1.27

managed access phase (MAP)

A time span set aside by a hub for improvised access, scheduled access, and unscheduled access to the medium by the hub and the nodes in the body area network (BAN) of the hub.

3.1.28

master key (MK)

A secret bit string activated or established between a node and a hub in a security association procedure and used to create a pairwise temporal key (PTK) shared between them.

3.1.29

message authentication

Corroboration of the origin of a message in a message transfer.

3.1.30

multi-periodic (m-periodic) allocation

A scheduled allocation or an unscheduled bilink allocation that has allocation intervals reoccurring in every mth beacon period (superframe) with m being an integer larger than one. An m-periodic scheduled allocation is an uplink allocation, a downlink allocation, or a bilink allocation, suitable for servicing low duty cycle periodic or quasi-periodic traffic on a committed schedule. An m-periodic unscheduled allocation is a bilink allocation, suitable for servicing low duty cycle periodic or quasi-periodic traffic on a best-effort basis.

3.1.31

node

An entity that contains a medium access control (MAC) sublayer, a physical (PHY) layer, and that optionally provides security services.

3.1.32

node identifier (NID)

An abbreviated address of a single node or of a logical group of nodes.

3.1.33

nonce

A number that is unique per instantiation of a cryptography protocol as part of a measure to thwart cryptanalytic and other cryptographic attacks.

3.1.34

non-secure frame

A term that is interchangeable with unsecured frame.

3.1.35

one-periodic (1-periodic) allocation

A scheduled allocation that has allocation intervals reoccurring in every beacon period (superframe), or an unscheduled bilink allocation that has allocation intervals reoccurring in every beacon period (superframe) or in round-robin together with the allocation intervals of other 1-periodic unscheduled bilink allocations. A 1-periodic scheduled allocation is an uplink allocation, a downlink allocation, or a bilink allocation, suitable for servicing high duty cycle periodic or quasi-periodic traffic on a committed schedule. A 1-periodic unscheduled bilink allocation is a bilink allocation, suitable for servicing high duty cycle periodic or quasi-periodic traffic on a best-effort basis.

3.1.36

pairwise temporal key (PTK)

A secret bit string shared between a node and a hub and used to secure frames transferred between them.

3.1.37

pairwise temporal key (PTK) creation

A procedure used to create a PTK between a node and a hub based on a master key (MK) shared between them, and to confirm possession of a shared MK between the node and the hub.

3.1.38

poll

A control type frame or its variant sent by a hub to grant an immediate polled allocation to the addressed node or to inform the node of a future poll or post.

3.1.39

polled allocation

A non-reoccurring time interval that a hub grants to a node using polling access for initiating one or more frame transactions by the node. A polled allocation is an uplink allocation interval, suitable for servicing “ordinary,” “unexpected,” or “extra” uplink traffic (for example, due to data rate variations and/or channel impairments). A polled allocation is also called a polled allocation interval.

3.1.40

polling access

An access method, based on impromptu or scheduled polling by a hub, whereby a hub grants to a node a polled allocation for initiating one or more frame transactions by the node.

3.1.41

post

A management or data type frame sent by a hub to a node within its body area network (BAN). A post starts a posted allocation.

3.1.42

posted allocation

A non-reoccurring time interval that a hub grants to itself using posting access for initiating a frame transaction. A posted allocation is a downlink allocation interval, suitable for servicing “unexpected” or “extra” downlink traffic (for example, due to network management needs, data rate variations, and/or channel impairments).

3.1.43

posting access

An access method, based on impromptu or scheduled posting by a hub, whereby a hub grants to itself a posted allocation, typically outside scheduled uplink allocations, for initiating one or more frame transactions by the hub.

3.1.44

random access

An access method, based on carrier sense multiple access with collision avoidance (CSMA/CA) or slotted Aloha access but not both, whereby a node obtains a time interval in a random access phase (RAP) for initiating one or more frame transactions.

3.1.45

random access phase (RAP)

A time span set aside by a hub and announced via a beacon frame for random access to the medium by the nodes in the body area network (BAN) of the hub.

3.1.46

relayed node

A node that communicates with a hub through another node.

3.1.47

relaying node

A node through which another node communicates with a hub.

3.1.48

scheduled access

An access method, based on advance reservation and committed scheduling, whereby a node and a hub obtain scheduled reoccurring time intervals for initiating frame transactions.

3.1.49

scheduled allocation

One or more scheduled reoccurring time intervals that a node and a hub obtains using scheduled access for initiating frame transactions. A scheduled allocation is an uplink allocation, a downlink allocation, or a bilink allocation, suitable for servicing high or low duty cycle periodic or quasi-periodic traffic on a committed schedule.

3.1.50

scheduled-polling access

A combination of scheduled access and polling access, whereby a node and a hub obtain scheduled reoccurring time intervals, wherein the hub grants to the node and/or itself non-reoccurring time intervals for initiating frame transactions on uplink and/or downlink.

3.1.51

secure frame

A term that is interchangeable with secured frame.

3.1.52

secured communication

Exchange of secured frames.

3.1.53

secured frame

A frame that is secured with authenticity, integrity, confidentiality if required, and replay protection.

3.1.54

security association

A procedure used to identify a node and a hub to each other and establish a new master key (MK) shared between them or activate an existing MK pre-shared between them.

3.1.55

star network

A logical network partition comprising a hub and zero or more nodes whose medium access and power management are coordinated by the hub.

3.1.56

superframe

A term that is interchangeable with beacon period used especially when no beacons are transmitted.

3.1.57

type-I polled allocation

A polled allocation the length of which is specified in terms of the duration of time granted for transmission.

3.1.58

type-I polling access

Polling access that provides type-I polled allocations.

3.1.59

type-II polled allocation

A polled allocation the length of which is specified in terms of the number of frames granted for transmission.

3.1.60

type-II polling access

Polling access that provides type-II polled allocations.

3.1.61

unconnected node

A node that does not have a connection with a hub in a body area network (BAN).

3.1.62

unscheduled access

A combination of best-effort scheduled access and polling access, whereby a node and a hub obtain unscheduled reoccurring time intervals, wherein the hub grants to the node and/or itself non-reoccurring time intervals for initiating frame transactions in an uplink and/or downlink.

3.1.63

unscheduled bilink allocation

One or more unscheduled reoccurring time intervals that a node and a hub obtains using unscheduled access for initiating frame transactions. An unscheduled bilink allocation is a bilink allocation, suitable for servicing high or low duty cycle periodic or quasi-periodic traffic in an uplink and/or downlink on a best-effort basis.

3.1.64

unsecured communication

Exchange of unsecured frames.

3.1.65

unsecured frame

A frame that is not secured with authenticity, integrity, confidentiality, or replay protection.

3.1.66

uplink allocation

An allocation with allocation interval(s) in which a node initiates one or more frame transactions to transmit management and data traffic to a hub and the hub returns acknowledgment if required.

3.1.67

uplink

A communications link for transfer of management and data traffic from a node to a hub.

3.2.1

association

A term synonymous to security association in absence of the qualifier “security.”

3.2.2

appropriate

Subject to the rules specified in Clause 5, Clause 6, and Clause 7.

3.2.3

frame transaction

All management or data type frames of the same frame subtype, and an acknowledgment frame if required, that are separated in time by an appropriate interframe space and transmitted between a node and a hub. Examples of a frame transaction: (a) a management type frame and an immediate acknowledgment frame; (b) all data type frames of the same frame subtype after a block acknowledgment frame, and the block acknowledgment frame that follows; (c) a management or data type frame, which is followed by another management or data type frame of a different frame subtype; (d) a management or data type frame, which is separated by more than an appropriate interframe space by another management or data type frame of the same frame subtype.

3.2.4

implant

An entity that is placed inside a human body for medical purposes.

3.2.5

low power low duty cycle (LP/LDC)

Power, duty cycle, and transmission (transmissions/per hour) limits defined by standards and regulations for implants transmitting within the band 403.5 MHz to 403.8 MHz without coordination with a hub.

3.2.6

medical implant event

A term referenced in regulatory documents governing the use of the Medical Device Radiocommunication Service (MedRadio), which includes the Medical Implant Communications Service (MICS) from 402 MHz to 405 MHz.