SIST ES 201 803-2-1 V1.1.1:2005

• Abstract:

  Addressing and channel management.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.40 - Data communication networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI ES 201 803-2-1 V1.1.1 (2002-10) - Dynamic synchronous Transfer Mode (DTM); Part 2: System characteristics; Sub-part 1: Data link aspects

SIST ES 201 803-2-1 V1.1.1:2005 is the Slovenian standard published by SIST and identical to ETSI ES 201 803-2-1 Version 1.1.1. It specifies the data link aspects of Dynamic synchronous Transfer Mode (DTM), with a focus on addressing, channel management, topology discovery, and resource management on DTM bypass chains.

It is written for DTM network and node implementations that need to exchange control information, discover bypass-chain topology, and manage slot usage between physical interfaces.

What does SIST ES 201 803-2-1 V1.1.1:2005 specify?

SIST ES 201 803-2-1 V1.1.1:2005 specifies the system for bypass chain management, control signalling, and bypass chain resource management on the DTM data link layer. In practice, it tells implementers how DTM nodes communicate with neighbouring physical interfaces and how they maintain a consistent view of the network.

The document is organized into:

• Scope, references, definitions and abbreviations
• A data link management system overview
• Slot-0 service
• Bypass chain topology management
• Control channel management
• Resource management
• Annex A with the SDL model
• Annex B with the bibliography

Annex	What it covers
Annex A	SDL model for DLSP
Annex B	Bibliography

What are the key requirements of SIST ES 201 803-2-1 V1.1.1:2005?

SIST ES 201 803-2-1 V1.1.1:2005 defines three linked functions: discovering bypass chains, carrying control signalling, and managing transmission resources. These are the core behaviours that DTM nodes must support to keep the network operating across physical links and bypass chains.

Bypass chain and topology management

Clause 4 explains that a DTM network is built from nodes with one or more physical interfaces and unidirectional physical links. A bypass chain is a series of linked physical interfaces that can carry data end-to-end using bypass switching. This matters because the protocols operate on physical interfaces and bypass chains, not just on nodes as abstract network elements.

Slot-0 is special. Clause 4.1 states that Slot-0 is always used for transmitting data and is never bypass switched. In practice, Slot-0 provides a fixed control path on each frame while other slots may be bypassed unless explicitly allocated.

DLSP discovery and monitoring

Clause 6 defines the DTM Link State Protocol (DLSP) as the mechanism that automatically discovers bypass-chain topology and monitors changes. It runs in two phases: first it establishes neighbour connections, then it distributes topology knowledge so clients can build a full view of the bypass chains they belong to. For implementers, that means topology information is learned progressively and may converge over time after startup or changes.

DLSP also uses a detailed message set, including DLSP_PROBE, DLSP_DETECTED, DLSP_CONFIRM, DLSP_DISTRIBUTE and DLSP_LINK_ERROR. The protocol uses acknowledgements, hop counts and timers to detect changes and keep clients informed. In practice, this is what lets a node notice broken links, new nodes, or changed return paths.

Clause 6.5 describes the SDL processes, including TXprocess, RXprocess, DistributeDownstreamProcess, DistributeUpstreamProcess and BCManager. These processes explain how a node forwards DLSP information and how it reacts to physical-link failures. The practical effect is faster failure notification and controlled topology updates.

Control signalling and DCC

Clause 7 defines the DTM Control Channel function (DCC) for control signalling. DCC can work in a normal two-layer mode with dedicated control channels, or in a special startup mode that uses Slot-0 and the DTM Control Forwarding and Filtering (DCFF) service. This matters because DTM can still carry control traffic before dedicated control channels are established.

The document states that DCC encapsulates messages with DCAP-1 and uses the Channel Multiplexing Identifier (CMI) to deliver incoming control messages to the right client. It also states that DCC does not guarantee delivery. In practice, higher-layer DTM protocols such as DRMP, DRP and DCP must tolerate loss and rely on DCC for addressed communication along bypass chains.

Clause 7.5 also defines how control channels are established and removed. The source node creates and removes the channel, DCFF continues to carry signalling when a dedicated channel is not available, and a FLUSH message is used to move traffic from DCFF onto an established control channel. For operators and implementers, this is the part that keeps control traffic consistent while topology changes.

Resource management and slot ownership

Clause 8 defines the DTM Resource Management Protocol (DRMP). DRMP manages who has the right to use a slot and who owns that right. Ownership can be static or dynamic, and dynamic ownership distributes rights along the bypass chain according to policy.

The document also defines borrowing and lending of tokens, access tokens, and slot scoping. That means a slot can be used over only part of a bypass chain, so the same slot may be reused further along the chain if the topology allows it. This is important for capacity planning because it explains how DTM reuses time slots spatially.

Clause 8 describes the probe mechanism used to check whether a token is free, owned once, or allocated by several nodes. It also defines fault handling for borrowing failures, ownership overlap, loss of access tokens, and multiple allocations. In practice, this is how a node detects conflicting claims on the same slot before traffic is affected.

DRMP procedures and messages

Clause 8.3 gives the Quark machine and the Dynamic Ownership state machine. These state machines describe how a node moves between Free, Busy, Lent, Gone, Borrowed and Probing states, and how it reacts to events such as QRequest, QTransfer, QReturn and Probe replies. For implementers, this is the operational logic behind slot ownership decisions.

Clause 8.4 defines the message formats for DRMP. It includes DRMP_RESOURCE_ANNOUNCE, DRMP_TOKEN_REQUEST, DRMP_TOKEN_TRANSFER, DRMP_TOKEN_RETURN, DRMP_PROBE, DRMP_PROBE_REPLY, DRMP_SYNC, DRMP_GATHER and DRMP_KILL. These formats tell implementations how to encode ownership announcements, borrowing requests, probe exchanges and ownership updates.

What terms does SIST ES 201 803-2-1 V1.1.1:2005 define?

SIST ES 201 803-2-1 V1.1.1:2005 defines the terms that make the DTM data link procedures precise and machine-readable.

• Access token - the right to use a slot for transmission on a physical interface for a limited number of bypass hops.
• Bypass Chain (BC) - a chain of concatenated physical links that can carry data end-to-end using bypass switching.
• Control channel - a channel used for DTM control signalling.
• DTM address - a 64-bit numerical value that uniquely identifies a node in a DTM network.
• Allocation domain - the bypass chain used for ownership and resource allocation, with a topology-dependent rule for whether the last node counts.
• Ownership - responsibility to supervise an access token of a slot.
• Quark - the smallest resource unit, one slot wide and one physical link long, used to model resource management on a bypass chain.
• Return physical interface - the physical interface that receives reply messages from a neighbouring node.

Who uses SIST ES 201 803-2-1 V1.1.1:2005?

SIST ES 201 803-2-1 V1.1.1:2005 is used by engineers and protocol developers working on DTM nodes, interfaces and control planes. It is also relevant to system integrators and test teams that need to verify bypass-chain discovery, control-channel behaviour, and slot ownership handling.

It is particularly useful when a project needs to implement or validate:

• topology discovery on rings, buses, point-to-point links and mixed bypass-chain layouts
• control signalling over Slot-0 or established control channels
• resource ownership, token borrowing and fairness behaviour
• fault detection and recovery when links or interfaces change

Which standards are used with SIST ES 201 803-2-1 V1.1.1:2005?

SIST ES 201 803-2-1 V1.1.1:2005 references ETSI TR 101 287 for common terms and definitions used across SPAN work. That reference supplies the general terminology base used in the document.

The foreword places this sub-part in the DTM family of deliverables:

• ETSI ES 201 803-1 - system description
• ETSI ES 201 803-2-2 - system characteristics, network aspects
• Other DTM parts cover physical protocol, mappings to SDH, PDH, Ethernet, Frame relay, ATM, IP flows, video streams, MPLS, sub-rate DTM, and network management

What does the SIST ES 201 803-2-1 V1.1.1:2005 document contain?

SIST ES 201 803-2-1 V1.1.1:2005 contains process descriptions, SDL models, state machines, message formats, and timing behaviour for DTM data link functions. Clause 6 and Clause 7 define protocol operation with sequence diagrams, message flows, and header formats for DLSP and DCC. Clause 8 provides the Quark machine, the Dynamic Ownership machine, and detailed DRMP message layouts.

The document also includes tables for field contents and constants, plus formulas and rules used for ownership distribution and probe handling. Annex A provides the SDL model for DLSP, which is the part most useful for formal implementation and protocol checking.

SLOVENSKI STANDARD
01-januar-2005
'LQDPLþQLVLQKURQLSUHQRVQLQDþLQ'70±GHO.DUDNWHULVWLNHVLVWHPD±
SRGGHO9LGLNLSRGDWNRYQHSRYH]DYH
Dynamic synchronous Transfer Mode (DTM); Part 2: System characteristics; Sub-part 1:
Data link aspects
Ta slovenski standard je istoveten z: ES 201 803-2-1 Version 1.1.1
ICS:
33.040.40 Podatkovna komunikacijska Data communication
omrežja networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Dynamic synchronous Transfer Mode (DTM);
Part 2: System characteristics;
Sub-part 1: Data link aspects
�
2 ETSI ES 201 803-2-1 V1.1.1 (2002-10)

Reference
DES/SPAN-130005-1
Keywords
addressing, DTM
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2002.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 201 803-2-1 V1.1.1 (2002-10)
Contents
Intellectual Property Rights.7
Foreword.7
Introduction .7
1 Scope.8
2 References.8
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.10
4 Data link management system overview.10
4.1 Physical interfaces and physical links .11
4.2 Bypass chains.11
4.3 Control Services.13
4.4 Topology Management.13
4.5 Resource Management.13
5 Slot-0 Service.13
5.1 Functionality.13
5.1.1 The Slot-0 data transport.13
5.1.2 Control traffic over Slot-0.13
5.2 Characteristics.14
5.3 Addressing.14
5.4 Client Selection.14
5.5 Slot-0 message and header formats .14
6 Bypass chain topology management .14
6.1 Bypass chain topology management overview.14
6.1.1 Void.14
6.1.2 Topology discovery algorithm.14
6.1.3 Bypass chain monitoring.15
6.2 Service interfaces.15
6.2.1 Service provided.15
6.2.2 Service required.16
6.3 Detailed protocol description.16
6.3.1 Establishing connections.16
6.3.1.1 Probing phase.17
6.3.1.2 Return physical interface.17
6.3.1.3 Detection phase.18
6.3.1.4 Confirmation phase.18
6.3.1.5 Distribution phase.19
6.3.1.6 Messages distribution.19
6.3.2 Information Distribution Phase.19
6.3.2.1 Information propagation.21
6.3.2.2 Ending the distribution.21
6.3.2.3 Detecting rings.21
6.3.2.4 Sending out node lists .22
6.3.3 Topology calculation.22
6.3.3.1 Informing DLSP's clients .22
6.3.3.2 Informing the RXprocesses about valid return physical interfaces.22
6.4 Messages.23
6.4.1 Physical interface identifiers field .23
6.4.2 General message format.23
6.4.3 DLSP_PROBE.23
6.4.4 DLSP_PROBE_ACK.24
6.4.5 DLSP_DETECTED.24
ETSI
4 ETSI ES 201 803-2-1 V1.1.1 (2002-10)
6.4.6 DLSP_DETECTED_ACK.24
6.4.7 DLSP_CONFIRM.25
6.4.8 DLSP_CONFIRM_ACK.25
6.4.9 DLSP_DISTRIBUTE.25
6.4.9.1 DLSP_DISTRIBUTE List Entries .26
6.4.10 DLSP_DISTRIBUTE_ACK.26
6.4.11 DLSP_LINK_ERROR.27
6.5 SDL Descriptions.27
6.5.1 Processes.27
6.5.1.1 Relationships between processes in a node.28
6.5.1.2 Relationships between processes in neighbouring nodes.29
6.5.1.3 DistributeDownstreamProcess.29
6.5.1.3.1 Purpose.29
6.5.1.3.2 Operation.29
6.5.1.3.3 Provided services.29
6.5.1.3.4 Timers.30
6.5.1.4 DistributeUpstreamProcess.30
6.5.1.4.1 Purpose.30
6.5.1.4.2 Operation.30
6.5.1.4.3 Provided services.31
6.5.1.4.4 Timers.31
6.5.1.5 Dispatcher.31
6.5.1.6 TXprocess.31
6.5.1.6.1 Purpose.31
6.5.1.6.2 Operation.31
6.5.1.6.3 Provided services.32
6.5.1.6.4 Timers.32
6.5.1.7 RXprocess.33
6.5.1.7.1 Purpose.33
6.5.1.7.2 Operation.33
6.5.1.7.3 Provided services.34
6.5.1.7.4 Timers.34
6.5.1.8 BCManager.34
6.5.1.8.1 Purpose.34
6.5.1.8.2 Operation.34
6.5.1.8.3 Timers.35
6.5.2 Data types.35
6.5.3 Functions.35
6.5.3.1 IsBypassOk.35
6.5.3.2 RecalcTopology.35
6.5.4 Constants.35
6.5.4.1 DLSP_MAX_HOPCOUNT.35
6.5.4.2 DLSP_MAX_CONFIRM_TRIES.36
6.5.4.3 DLSP_MIN_PROBE.36
6.5.4.4 DLSP_TIMEOUT_DISTRIBUTE.36
6.5.4.5 DLSP_TIMEOUT_CONFIRM_IN.36
6.5.4.6 DLSP_TIMEOUT_CONFIRM_OUT'.36
6.5.4.7 DLSP_TIMEOUT_FIRSTCONFIRM_IN.36
6.5.4.8 DLSP_TIMEOUT_DETECTED.36
6.5.4.9 DLSP_PERIOD_PROBE.36
6.5.4.10 DLSP_PERIOD_CONFIRM_OUT.36
6.5.4.11 Timer values.36
7 Control channel management.37
7.1 Overview.37
7.2 Void.38
7.3 DTM Control Forwarding & Filtering Service.38
7.3.1 Functionality.38
7.3.1.1 Handling of messages.38
7.3.2 Characteristics.38
7.3.3 Addressing.39
7.3.4 Client Selection.39
ETSI
5 ETSI ES 201 803-2-1 V1.1.1 (2002-10)
7.4 Messages and Headers.39
7.4.1 The DCFF Tunnel Header .39
7.5 DCC Service.39
7.5.1 Functionality.39
7.5.1.1 Signalling path.40
7.5.1.2 Route path finding.41
7.5.1.3 Establishment and Removal of control channels.42
7.5.1.4 Message filtering.45
7.5.2 Characteristics.45
7.5.2.1 Sending messages in the direction of the bypass chain.45
7.5.2.2 Sending messages in opposite direction of a bypass chain .45
7.5.3 Addressing.45
7.5.3.1 Sending messages along a bypass chain.45
7.5.3.2 Sending messages in opposite direction of a bypass chain .45
7.5.4 Client Selection.45
7.5.5 DCC message and header format.45
7.5.5.1 Payload of DCC clients.46
7.5.5.2 DCC FLUSH message .46
7.5.5.3 DCC Source Address Header.46
7.5.5.4 DCC Route header .46
7.5.5.5 DCC Tear Down .47
7.5.6 DCFF message and header formats .47
7.5.6.1 DCFF Tunnel Header.47
8 Resource management.48
8.1 System overview.48
8.1.1 Functional overview.48
8.1.1.1 Resource ownership.48
8.1.1.2 Borrowing.48
8.1.1.3 Resource announcement.48
8.1.1.4 Probe mechanism.48
8.1.2 Fault management.49
8.1.2.1 Borrowing failed.49
8.1.2.2 Ownership overlapping.49
8.1.2.3 Loss of access tokens .49
8.1.2.4 Tokens allocated by several nodes .49
8.2 Concepts.50
8.2.1 Terminology.50
8.2.1.1 Allocation domain.50
8.2.1.2 Short circuit.50
8.2.1.3 Probe.51
8.2.1.4 Borrowing and lending of token(s) .52
8.2.1.5 Ownership of tokens .52
8.2.1.6 Access to token(s) .52
8.2.1.7 DRMP_GATHER.52
8.2.1.8 DRMP_SYNC.52
8.2.1.9 Start up.52
8.2.1.10 Master physical interface .52
8.2.1.11 Transitional master physical interface.53
8.2.1.12 Probe.53
8.2.1.13 Topology.53
8.2.1.14 Fairness algorithm.53
8.2.1.15 Range change.53
8.2.1.16 Double booking.53
8.2.1.17 Quark.53
8.2.1.18 Got ownership.53
8.2.1.19 Lost ownership.53
8.2.1.20 Alloc.53
8.2.1.21 Dealloc.53
8.2.1.22 Fragmentation.54
8.3 Detailed protocol description.54
8.3.1 The Quark machine.54
ETSI
6 ETSI ES 201 803-2-1 V1.1.1 (2002-10)
8.3.1.1 Simplified diagram.54
8.3.1.2 Events.55
8.3.1.3 States.55
8.3.1.4 Void.55
8.3.1.5 State transition tables .55
8.3.1.5.1 Free.55
8.3.1.5.2 Busy.56
8.3.1.5.3 Lent.56
8.3.1.5.4 Gone.57
8.3.1.5.5 Borrowed.57
8.3.1.5.6 Probing.57
8.3.2 The Dynamic Ownership state machine .58
8.3.2.1 Typical scenarios.58
8.3.2.2 Transition diagrams.60
8.3.2.3 State types.60
8.3.2.4 State variables.60
8.3.2.5 Queries.61
8.3.2.5.1 Probe conditions.61
8.3.2.6 Incoming messages and signals.61
8.3.2.6.1 Bypass Chain Change (BCC) .61
8.3.2.6.2 RangeChange.61
8.3.2.7 Signals and messages.62
8.3.2.7.1 DRMP_SYNC message.62
8.3.2.7.2 DRMP_GATHER.63
8.3.2.8 Outgoing Messages.64
8.3.2.8.1 DRMP_DIST_OWN.64
8.3.2.9 Timeouts.64
8.3.2.9.1 (Re) send DRMP_GATHER .64
8.3.2.10 Distribution and calculation of ownership ranges .64
8.4 Message formats.65
8.4.1 Generic fields.65
8.4.1.1 Physical interface identifiers field.65
8.4.1.2 Slot fragment.66
8.4.1.3 Long slot fragment.66
8.4.1.4 Generic header.66
8.4.2 Statistical information.67
8.4.2.1 DRMP_RESOURCE_ANNOUNCE (Dynamic ownership).67
8.4.2.2 DRMP_RESOURCE_ANNOUNCE (Static ownership) .67
8.4.3 Access token passing .68
8.4.3.1 DRMP_TOKEN_REQUEST.68
8.4.3.2 DRMP_TOKEN_TRANSFER.69
8.4.3.3 DRMP_TOKEN_RETURN.69
8.4.3.4 DRMP_PROBE.70
8.4.3.5 DRMP_PROBE_REPLY.70
8.4.4 Ownership passing.71
8.4.4.1 DRMP_SYNC.72
8.4.4.2 DRMP_GATHER.72
8.4.4.3 DRMP_KILL.73
Annex A (normative): SDL model .74
Annex B (informative): Bibliography.75
History .76

ETSI
7 ETSI ES 201 803-2-1 V1.1.1 (2002-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Services and Protocols for Advanced
Networks (SPAN).
The present document is part 2, sub-part 1 of a multi-part deliverable covering Dynamic synchronous Transfer Mode
(DTM), as identified below:
Part 1: "System description";
Part 2: "System characteristics";
Sub-part 1: "Data link aspects";
Sub-part 2: "Network aspects";
Sub-part 3: "Transport network and channel adaptation aspects";
Part 3: "Physical protocol";
Part 4: "Mapping of DTM frames into SDH containers";
Part 5: "Mapping of PDH over DTM";
Part 6: "Mapping of SDH over DTM";
Part 7: "Ethernet over DTM Mapping";
Part 8: "Mapping of Frame relay over DTM";
Part 9: "Mapping of ATM over DTM";
Part 10: "Routeing and switching of IP flows over DTM";
Part 11: "Mapping of video streams over DTM";
Part 12: "Mapping of MPLS over DTM";
Part 13: "System description of sub-rate DTM";
Part 14: "Network management".
Introduction
The present document describes the architecture and protocols of signalling and maintenance on the data link layer of
the DTM system.
ETSI
8 ETSI ES 201 803-2-1 V1.1.1 (2002-10)
1 Scope
The present document:
• establishes a system for bypass chain management;
• specifies the characteristics of bypass chain management;
• establishes a system for control signalling;
• specifies the characteristics of control signalling;
• establishes a system for bypass chain resource management;
• specifies the characteristics of bypass chain resource management.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
[1] ETSI TR 101 287: "Services and Protocols for Advanced Networks (SPAN); Terms and
Definitions".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
access token: right to use a slot for transmitting data on a physical interface for a certain number of bypass hops
address, DTM address: 64 bit numerical value that uniquely identifies a node in a DTM network
NOTE: See further anycast address and multicast address.
allocation domain: same as a bypass chain where, if the topology is point-to-point or bus, the last node is not counted
as member of the AD
Bypass Chain (BC): series of concatenated physical links, where data can be transported end-to-end using bypass
switching
bypass switching: space switching of slots from a receiver to a transmitter on the same physical interface on a per slot
basis
channel: set of slots allocated from one source Access node to one or more destination Access nodes in a network
NOTE: The source and destination Access nodes can be the same, i.e. the channel is internal to the node.
channel adaptation: channel path termination function that provides an adaptation between the DTM slot based service
and some other traffic service (such as word stream, bit stream or asynchronous packets)
ETSI
9 ETSI ES 201 803-2-1 V1.1.1 (2002-10)
Channel Multiplexing Identifier (CMI): identifier by DCAP-1 used for multiplexing packets of different protocols on
a single channel
control channel: channel used for DTM control signalling
data channel: channel used for transport data between interworking functions
DTM network address, DTM address: See definition of "address, DTM address".
DTM Service Type (DST): identifying the type of interworking function to be associated with the channel
DTM Service Type Instance (DSTI): identifying which interworking function of a specific type to be addressed by the
channel
physical interface address: globally unique identifier of a physical interface that is represented as a 48-bit MAC
address
master physical interface: physical interface in the allocation domain having the lowest physical interface address
multicast address: address used to represent all nodes belonging to a multicast group
network address: an address to be used in the network layer of the ISO OSI model
NOTE 1: A network address may take on different forms depending on which protocol is being used in the network
layer.
NOTE 2: See also DTM network address.
node: network element containing DTM functions
node control channel: dynamically established control channel from one node to one or more other nodes on the same
bypass chain
node identity: identifier that uniquely identifies a node over a global scope
ownership: responsibility to supervise an access token of a slot
physical interface: interface between two equipments
NOTE: Adopted from TR 101 287 [1].
physical link: unidirectional connection between the transmitter of one physical interface and the receiver of another
physical interface
quark: smallest resource unit that is one slot wide and one physical link long
NOTE: Used to model dynamic resource management on a bypass c
...