SIST ETS 300 393-2:1999

• Abstract:

  To update the PDO Air interface standard after validation of the SDL model.

• Status: Published
• Publication Date: 30-Jun-1999
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: RES - Radio equipment and systems
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jul-1999
• Due Date: 01-Jul-1999
• Completion Date: 01-Jul-1999
• Mandate: BC-T-344
• Mandate: T-172
• Ref Project: ETSI ETS 300 393-2 ed.2 (1999-08) - Terrestrial Trunked Radio (TETRA); Packet Data Optimized (PDO); Part 2: Air Interface (AI)

SIST ETS 300 393-2:1999 is the Slovenian adoption of ETS 300 393-2 Edition 2 from ETSI. It specifies the Terrestrial Trunked Radio (TETRA) Packet Data Optimized (PDO) air interface, covering the radio, protocol, and layer 2 behavior needed for packet data transfer between a Base Station (BS) and a Mobile Station (MS). Engineers, operators, quality teams, and test labs use it to design, implement, and verify TETRA PDO equipment and networks.

What does SIST ETS 300 393-2:1999 specify?

SIST ETS 300 393-2:1999 specifies the TETRA PDO radio air interface and the procedures that support packet data operation on that interface. The document is organized from radio behavior through network services, mobility management, and layer 2 procedures, so a reader can follow the path from over-the-air signaling to service primitives and protocol data units.

Clause group	What it covers
1-3	Scope, normative references, definitions, symbols, abbreviations
4-10	Radio aspects, modulation, RF transmission and reception, synchronization, coding, multiplexing, and link control
11-14	Connection-oriented and connectionless network services and protocols
15-18	Mobility Management (MM), the PDO MM protocol, MLE service, and the PDO MLE protocol
19-22	Layer 2 service descriptions, PDUs and elements, Logical Link Control (LLC), and Medium Access Control (MAC)

Annex	What it covers
Annex A	X.25 1980 sub-network dependent convergence protocol
Annex B	Classification
Annex C	Sub-network convergence protocol for use with X.25 permanent virtual circuits
Annex D	Protocol implementation conformance statement proforma
Annex E	Additional considerations of CONS primitives
Annex F	Use of X.25/PLP NPAI
Annex G	Transit delay calculations
Annex H	Example of priority negotiation
Annex I	Differences between CCITT Recommendation X.223 and ISO/IEC 8878

What are the key requirements of SIST ETS 300 393-2:1999?

SIST ETS 300 393-2:1999 sets out the air-interface behavior in enough detail to make BS and MS implementations interoperable. The main requirements are spread across the radio, coding, mobility, packet service, and layer 2 clauses.

Radio interface, modulation, and RF performance

• Clauses 4 and 5 define the radio structure: logical channels, reference configuration, error control schemes, multiple access, slot structure, coding, interleaving, scrambling, and modulation. In practice, this tells implementers how a transmitted signal is built before it reaches the air interface.
• Clause 6 specifies transmitter and receiver characteristics, including frequency bands, channel arrangement, reference test planes, output power, unwanted emissions, frequency tolerance, output power time mask, intermodulation attenuation, blocking, spurious response rejection, and receiver performance. This is the main clause used when checking whether BS and MS radio hardware behaves correctly in testing.
• Clause 6 also includes modulation accuracy and receiver sensitivity/performance under defined propagation conditions. That matters because equipment has to work not only in ideal laboratory conditions but also under fading and interference cases.
• Clause 7 defines synchronization requirements using timebase counters, transmitted-signal timing, and separate BS and MS synchronization rules. This keeps bursts aligned so the network can maintain carrier and frame timing.
• Clause 8 defines the channel coding methods, including 16-state Rate-Compatible Punctured Convolutional (RCPC) codes, a block code, block interleaving, and scrambling, plus the MBCH and NBCH error-control schemes. In practice, these rules determine how protection is added before data is placed on the air interface.
• Clause 9 maps layer 2 blocks into sub-bursts and bursts, with defined bit allocation and timing for uplink, downlink, synchronization, and linearization cases. That mapping is what designers use to place training, correction, and user bits in the correct burst positions.

Link control, mobility, and service behavior

• Clause 10 defines radio subsystem link control, including RF power control, path-loss formulae, monitoring measurements, scanning, initial cell selection, cell re-selection, and serving-cell quality measurements. This is the logic that lets a mobile decide when to stay on a cell, search for another one, or hand over service behavior.
• Clause 10 also uses received signal strength, BER, MER, and the RDC counter as part of its quality and re-selection logic. In practice, these measurements are what a tester or engineer monitors to confirm that a terminal makes the right cell decision.
• Clauses 11 to 14 define the packet-service layer above the radio interface: Connection Oriented Network Service (CONS), Connection Oriented Network Protocol (CONP), Specific-ConnectionLess Network Service (S-CLNS), and Specific-ConnectionLess Network Protocol (S-CLNP). These clauses explain how packet connections, delivery options, priority, multicast selection, timestamps, and checksum handling are carried over TETRA PDO.
• Clauses 15 and 16 cover Mobility Management (MM), including authentication, detach, registration, energy-saving mode, group identity download, and the associated MM PDUs and timers. These rules matter when a terminal joins the network, updates its location, or is instructed to save energy.
• Clauses 17 and 18 define the Mobile Link Entity (MLE) service and the PDO MLE protocol, including cell scanning, neighbour-cell monitoring, cell ranking, initial selection, re-selection, address handling, message routing, and broadcast system information. This is the control layer that keeps a mobile attached to the best available cell and routes control information correctly.
• Clauses 19 to 22 define layer 2 service access points, block structures, PDUs, Logical Link Control (LLC), and Medium Access Control (MAC) procedures. These clauses are the basis for implementing and testing data transfer, random access, acknowledgements, broadcast handling, and multi-carrier operation.

What terms does SIST ETS 300 393-2:1999 define?

• Terrestrial Trunked Radio (TETRA) - The trunked radio system family covered by the standard, aimed at organized mobile radio networks.
• Packet Data Optimized (PDO) - The TETRA profile described here, focused on packet data transport over the air interface.
• Air Interface (AI) - The radio interface between the network and the mobile terminal, including burst structure, coding, and timing.
• Base Station (BS) - The fixed network-side radio equipment that transmits to and receives from mobiles.
• Mobile Station (MS) - The terminal-side radio equipment that moves between cells and performs access, measurement, and data transfer functions.
• Mobile Link Entity (MLE) - The sublayer that handles attachment, routing, broadcast system information, and local control between mobility and layer 2.
• Logical Link Control (LLC) - The layer 2 function that provides AI-frames, RR-frames, and UI-frames with sequencing and acknowledgement behavior.
• Master Block CHannel (MBCH) - One of the two error-control block-channel schemes defined for PDO, used alongside the Normal Block CHannel (NBCH).

Who uses SIST ETS 300 393-2:1999?

SIST ETS 300 393-2:1999 is used by TETRA equipment manufacturers, protocol developers, network integrators, operators, and independent test laboratories. It is the reference for anyone who needs to design BS or MS behavior, implement packet services, tune cell selection and power control, or create conformance and interoperability tests.

Quality and procurement teams also use it when they need a technical basis for acceptance checks. The document gives them a common reference for radio performance, service behavior, and protocol structure, so they can check whether a product matches the expected PDO air-interface behavior.

What changed in SIST ETS 300 393-2:1999 from the previous edition?

SIST ETS 300 393-2:1999 is the Second Edition and updates the PDO Air interface standard after validation of the SDL model. The Slovenian standard is identical to ETS 300 393-2 Edition 2.

Which standards are used with SIST ETS 300 393-2:1999?

• ISO/IEC 8348 - Used as the base for the Connection Oriented Network Service (CONS) description in clause 11.
• ISO/IEC 8878 - Used with the CONS delta clauses and the X.25/PLP-based service procedures in clause 11.
• ISO/IEC 8208 - Used as the basis for the Connection Oriented Network Protocol (CONP) delta in clause 12.
• ETS 300 393-1 - Referenced for the TETRA Subscriber Identity (TSI) used in packet address fields in clause 14.5.3.
• CCITT Recommendation X.223 - Compared with ISO/IEC 8878 in the clause 11 annex material.

What does the SIST ETS 300 393-2:1999 document contain?

The document contains detailed parameter tables for RF behavior, coding, burst layouts, protocol fields, timers, and service primitives. It also includes procedures, state descriptions, and PDU formats for network service, mobility management, MLE, LLC, and MAC behavior.

Several parts are presented as figures, tables, or structured procedures rather than narrative text. Examples include path-loss formulae, cell re-selection criteria, checksum algorithms, burst bit allocation, and PDU header layouts.

The later clauses include worked examples and state-transition material, including the example sections in G.1-G.4 and the transition material in H.1-H.2. Clause 11 also adds conformance-oriented material through the Protocol Implementation Conformance Statement proforma in Annex D.

For a reader, this means the standard is useful not only for design but also for test planning, interoperability checks, and conformance documentation.

SLOVENSKI STANDARD
01-julij-1999
Prizemni snopovni radio (TETRA) - Optimiran sistem za prenos paketiranih
podatkov (PDO) - 2. del: Radijski vmesnik (AI)
Terrestrial Trunked Radio (TETRA); Packet Data Optimized (PDO); Part 2: Air Interface
(AI)
Ta slovenski standard je istoveten z: ETS 300 393-2 Edition 2
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
EUROPEAN pr ETS 300 393-2
TELECOMMUNICATION June 1998
STANDARD Second Edition
Source: TETRA Reference: RE/TETRA-04004-2
ICS: 33.020
Key words: TETRA, PDO
Terrestrial Trunked Radio (TETRA);
Packet Data Optimized (PDO);
Part 2: Air Interface (AI)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: [e-mail] - http://www.etsi.fr - http://www.etsi.org
Tel.: [phone] - Fax: [phone]
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 1998. All rights reserved.

Page 2
Draft prETS 300 393-2: June 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.

Page 3
Draft prETS 300 393-2: June 1998
Contents
Foreword .19
1 Scope .21
2 Normative references.21
3 Definitions, symbols and abbreviations.22
3.1 Definitions .22
3.2 Symbols .23
3.3 Abbreviations .23
4 Radio aspects.24
4.1 Introduction .24
4.2 Set of logical channels.24
4.3 Reference configuration.24
4.4 Error control schemes.25
4.5 Multiple access and time slot structure.25
4.5.1 Sub-bursts.25
4.5.1.1 Downlink sub-bursts .25
4.5.1.2 Uplink sub-bursts.25
4.5.2 Bursts .26
4.5.2.1 Downlink bursts .26
4.5.2.2 Uplink bursts.26
4.6 Coding, interleaving and scrambling.27
4.7 Modulation .27
4.8 Transmission and reception.27
4.9 Other radio-related functions .27
4.10 Performance .28
5 Modulation.28
5.1 Introduction .28
5.2 Modulation type.28
5.3 Modulation rate .28
5.4 Modulation symbol definition.28
5.5 Modulated signal definition .29
5.6 Modulation filter definition .30
5.7 Modulation block diagram.30
6 Radio transmission and reception.30
6.1 Introduction .30
6.2 Frequency bands and channel arrangement .30
6.3 Reference test planes.31
6.4 Transmitter characteristics .31
6.4.1 Output power.31
6.4.1.1 BS.32
6.4.1.2 MS .32
6.4.2 Unwanted conducted emissions.32
6.4.2.1 Definitions.32
6.4.2.2 Unwanted emissions close to the carrier.33
6.4.2.2.1 Measurement over the useful part of
the burst.33
6.4.2.2.2 Measurement during the switching
transients .33
6.4.2.3 Unwanted emissions far from the carrier.34
6.4.2.4 Unwanted emissions during the CLCH and BLCH .34
6.4.2.5 Unwanted emissions in the non-transmit state.34
6.4.3 Unwanted radiated emissions .34

Page 4
Draft prETS 300 393-2: June 1998
6.4.4 Radio frequency tolerance. 34
6.4.5 RF Output power time mask. 34
6.4.5.1 BS . 36
6.4.5.2 MS. 36
6.4.6 Intermodulation attenuation . 36
6.4.6.1 Definition . 36
6.4.6.2 BS . 36
6.4.6.3 MS. 36
6.4.7 Intra-BS intermodulation requirements. 37
6.5 Receiver characteristics . 37
6.5.1 Blocking characteristics . 37
6.5.1.1 Definition . 37
6.5.1.2 Specification. 37
6.5.2 Spurious response rejection . 38
6.5.2.1 Definition . 38
6.5.2.2 Specification. 38
6.5.3 Intermodulation response rejection . 38
6.5.3.1 Definition . 38
6.5.3.2 Specification. 38
6.5.4 Unwanted conducted emissions. 39
6.5.4.1 Definition . 39
6.5.4.2 Specification. 39
6.5.5 Unwanted radiated emissions. 39
6.6 Transmitter/receiver performance. 39
6.6.1 Modulation accuracy. 39
6.6.1.1 Ideal case. 39
6.6.1.2 Vector error magnitude requirement at symbol time. 40
6.6.2 Receiver performance . 40
6.6.2.1 Nominal error rates . 41
6.6.2.2 Dynamic reference sensitivity performance. 41
6.6.2.2.1 BS receiver performance . 41
6.6.2.2.2 MS receiver performance. 42
6.6.2.3 Reference interference performance. 42
6.6.2.3.1 BS receiver performance . 42
6.6.2.3.2 MS receiver performance. 42
6.6.2.4 Static reference sensitivity performance. 42
6.6.2.4.1 BS receiver performance . 43
6.6.2.4.2 MS receiver performance. 43
6.6.2.5 MS receiver performance for synchronization burst
acquisition . 43
6.6.3 Propagation conditions . 43
6.6.3.1 Propagation conditions - introduction. 43
6.6.3.2 Tap-gain process types. 44
6.6.3.3 Propagation models . 44
7 Radio sub-system synchronization . 44
7.1 General description of synchronization system. 45
7.2 Timebase counters.45
7.2.1 Downlink . 45
7.2.1.1 Timing counters . 45
7.2.1.2 Values of counters . 45
7.2.2 Uplink. 46
7.2.2.1 Timing counters . 46
7.2.2.2 Values of counters . 46
7.3 Timing of transmitted signals . 46
7.4 BS requirements for synchronization . 46
7.5 MS requirements for synchronization. 47
8 Channel coding. 47
8.1 Introduction. 47
8.2 General. 47
8.2.1 Interfaces in the error control structure. 47
8.2.2 Notation . 49

Page 5
Draft prETS 300 393-2: June 1998
8.2.3 Definition of error control codes .49
8.2.3.1 16-state Rate-Compatible Punctured Convolutional
(RCPC) codes .49
8.2.3.1.1 Encoding by the 16-state mother code
of rate 1/4.49
8.2.3.1.2 Puncturing of the mother code.50
8.2.3.1.3 Puncturing scheme of the RCPC code
of rate 2/3.50
8.2.3.2 (K +16, K ) block code .50
1 1
8.2.4 Definition of interleaving schemes.51
8.2.4.1 Block interleaving.51
8.2.5 Definition of scrambling.51
8.2.5.1 Scrambling method.51
8.2.5.2 Scrambling sequence .51
8.3 Error control schemes.52
8.3.1 Master Block CHannel (MBCH).52
8.3.2 Normal Block CHannel (NBCH) .52
9 Channel multiplexing.53
9.1 Logical channels for passing layer 2 blocks to the channel coding .53
9.2 The physical resource.54
9.2.1 General.54
9.2.2 Radio frequency channels.54
9.3 Physical channel .54
9.3.1 Sub-burst.54
9.3.2 Bursts .55
9.3.2.1 General.55
9.3.2.2 Modulation symbols numbering.55
9.3.2.3 Modulation bit numbering .55
9.3.2.4 Burst timing.55
9.3.3 Type of burst and burst timing.55
9.3.3.1 General.55
9.3.3.2 Modulation bits allocation .56
9.3.3.2.1 Uplink start sub-burst.56
9.3.3.2.2 Uplink even sub-burst .56
9.3.3.2.3 Uplink odd sub-burst.56
9.3.3.2.4 Uplink end sub-burst.56
9.3.3.2.5 Downlink normal sub-burst .57
9.3.3.2.6 Downlink synchronization sub-burst .57
9.3.3.2.7 Linearization up-link burst.57
9.3.3.3 Sub-burst fields.57
9.3.3.3.1 Frequency correction field.57
9.3.3.3.2 Normal training sequence.57
9.3.3.3.3 Extended training sequence .58
9.3.3.3.4 Synchronization training sequence .58
9.3.3.3.5 Tail bits.58
9.3.3.3.6 Phase adjustment bits .58
9.4 Mapping of multiplexed blocks into sub-bursts.58
9.4.1 Mapping of multiplexed blocks into sub-bursts on the downlink .59
9.4.2 Mapping of multiplexed blocks into sub-bursts on the uplink.59
9.4.3 Timing of transmission .59
10 Radio subsystem link control.61
10.1 Scope.61
10.2 General .61
10.3 RF power control.62
10.3.1 Overall process .62
10.3.2 MS power control implementation.62
10.3.3 MS power control range .62
10.4 Definition of path loss formulae .63
10.4.1 Path loss parameter C1.63
10.4.2 Path loss parameter C2.63
10.4.3 Path loss parameter C3.64

Page 6
Draft prETS 300 393-2: June 1998
10.4.4 Path loss parameter C4. 64
10.5 Monitoring measurements. 65
10.5.1 Signal strength measurement. 65
10.6 Scanning measurement . 65
10.6.1 Foreground scanning. 66
10.6.2 Background scanning (optional) . 66
10.6.2.1 Signal strength measurements . 66
10.6.2.2 Cell selection parameters measurement . 66
10.6.3 Interrupting scanning . 67
10.6.3.1 Signal strength measurements . 67
10.6.3.2 Cell selection parameters measurement . 67
10.7 Selection formulae . 67
10.7.1 Initial cell selection. 67
10.7.2 Cell re-selection . 68
10.7.2.1 Criterion for relinquishable link. 68
10.7.2.2 Criterion for improvable link . 68
10.8 Measuring quality of serving cell . 69
10.8.1 Downlink measurements . 69
10.8.1.1 Cell (re-)selection parameters decoding. 69
10.8.1.2 Signal strength . 69
10.8.1.3 Radio downlink counter. 69
10.9 Radio link measurements of signal quality. 70
10.9.1 Received signal strength . 70
10.9.2 RDC counter. 70
10.9.3 BER . 70
10.9.4 MER. 70
10.10 Control parameters . 71
10.10.1 Parameters . 71
11 Connection Oriented Network Service description (CONS) (ISO/IEC 8348 and ISO/IEC 8878
delta). 73
11.1 Introduction. 73
11.2 Organization of the present document . 73
11.3 Service description. 73
11.4 ISO/IEC 8878 delta . 74
11.4.1 Scope and field of application. 74
11.4.2 References . 74
11.4.3 Definitions . 74
11.4.4 Abbreviations . 74
11.4.5 Overview. 74
11.4.5.1 Elements of the X.25/PLP 1984 used to support the OSI
CONS. 74
11.4.5.2 General operation of the X 25 PLP 1984 for supporting
the OSI CONS. 78
11.4.6 Network connection establishment phase . 78
11.4.6.1 Primitive/parameter and packet field relationships . 78
11.4.6.2 Procedures. 78
11.4.6.2.1 Primitive and packet mapping. 78
11.4.6.2.2 NSAP addresses. 78
11.4.6.2.3 Receipt confirmation selection . 78
11.4.6.2.4 Expedited data selection . 78
11.4.6.2.5 QoS parameter set. 79
11.4.6.2.6 NS user data . 79
11.4.7 Network connection release phase. 79
11.4.7.1 Primitive/Parameter and packet/field relationships. 79
11.4.7.2 Procedures. 79
11.4.8 Data transfer phase: data transfer service . 79
11.4.8.1 Primitive/Parameter and packet/field relationship. 79
11.4.8.2 Procedures. 79
11.4.9 Data transfer phase: receipt confirmation service . 80
11.4.10 Data transfer phase: expedited data transfer service. 80
11.4.11 Data transfer phase: reset service. 80
11.4.12 Response to protocol violation. 80

Page 7
Draft prETS 300 393-2: June 1998
11.4.13 Conformance.80
11.5 Annex A: X.25 1980 sub-network dependant convergence protocol (normative) .80
11.6 Annex B: Classification (normative).80
11.7 Annex C: Sub-network convergence protocol for use with X.25 permanent virtual
circuits (normative) .80
11.8 Annex D: Protocol implementation conformance statement proforma (normative).80
11.9 Annex E: Additional considerations of CONS primitives (informative).80
11.10 Annex F: Use of X.25/PLP NPAI (informative) .80
11.11 Annex G: Transit delay calculations (informative) .80
11.12 Annex H: Example of priority negotiation (informative).80
11.13 Annex I: Differences between CCITT Recommendation X.223 and ISO/IEC 8878 [9]
(informative).81
12 CONP protocol (ISO/IEC 8208 delta).81
12.1 Introduction .81
12.2 Organization of this clause.81
12.3 Overview of the protocol .81
12.3.1 Position of the protocol in the network layer.81
12.3.2 Services provided by the protocol .81
12.3.3 Underlying services assumed by the protocol.81
12.3.4 Services assumed from the local environment .82
12.4 ISO/IEC 8208 delta.82
12.4.1 Scope .82
12.4.2 Normative references.82
12.4.3 General considerations .83
12.4.4 Procedures for reset and restart .83
12.4.5 Procedures for virtual call set-up and clearing .84
12.4.6 Procedures for data and interrupt transfer .85
12.4.7 Procedures for flow control.85
12.4.8 Procedures for reset.85
12.4.9 Effects of clear, reset, restart procedures on the transfer of packets .85
12.4.10 Effects of layer 1 and 2 on the packet layer .86
12.4.11 Error handling.86
12.4.12 Packet format .86
12.4.13 Procedures for optional user facilities .86
12.4.14 Procedures for optional CCITT specified DTE facilities .86
12.4.15 Format for facility field in call set-up clearing packets.86
12.4.16 Format for registration field in registration packets .86
12.4.17 Diagnostic codes.86
12.4.18 Timers and re-transmission counts.86
12.4.19 State diagrams .86
12.4.20 State tables .86
12.4.21 Annex A: Private networks .86
12.4.22 Annex B: Differences between the first and the second editions of
ISO/IEC 8208 .86
12.4.23 Amendment 1: Alternative logical channel identifier assignment .87
12.5 Protocol functions .87
12.6 Provision of the underlying protocol.88
12.6.1 Mapping of the primitives .88
12.6.2 Mapping of QoS .88
13 Specific-ConnectionLess Network Service description (S-CLNS) .89
13.1 Introduction .89
13.1.1 Specific connectionless service.89
13.1.2 ISO principles of connectionless-mode transmission .90
13.1.3 General principles .90
13.1.4 Sub-addresses .90
13.2 S-CLNS service description.91
13.2.1 SAP .91
13.2.2 Services available at the TN-SCLNS SAP .91
13.2.3 Full and slim services.91
13.2.3.1 Data transfer service .91
13.2.3.2 Facilities provided by the service.92

Page 8
Draft prETS 300 393-2: June 1998
13.3 Primitive definitions . 92
13.3.1 Primitives types. 92
13.3.2 Data transfer primitives. 92
13.3.3 Sequence of data transfer primitives . 93
13.3.4 Contents of primitives . 93
13.3.4.1 Parameter definitions . 94
13.3.4.2 TN-UNITDATA primitives. 94
13.3.4.3 TN-DELIVERY primitives . 95
13.3.5 State description . 95
14 Protocol for providing the Specific Connectionless network service (S-CLNP). 96
14.1 Introduction. 96
14.2 Overview of the protocol.96
14.2.1 Position of the protocol in the NWK layer . 96
14.2.2 Slim subset of the protocol . 97
14.2.3 Addresses. 97
14.2.4 Services provided by the protocol. 97
14.2.4.1 Data transfer service. 97
14.2.4.2 Facilities . 98
14.2.5 Underlying services assumed by the protocol . 98
14.2.6 One instance of protocol. 98
14.2.7 Timers. 98
14.3 Overview of the PDU structures. 99
14.4 PDU descriptions. 99
14.4.1 General format. 99
14.4.2 and PDU headers with short address. 101
14.4.3 and PDU headers with long address. 101
14.4.4 PDU header . 102
14.4.5 PDU header with short address. 102
14.4.6 PDU header with long address . 103
14.4.7 PDU header . 103
14.5 Formats of fields. 104
14.5.1 General principles. 104
14.5.2 Fixed part fields . 104
14.5.2.1 Version (4 bits). 104
14.5.2.2 Type (4 bits) . 104
14.5.2.3 Flags (4 bits) . 105
14.5.2.4 Packet length (12 bits) . 105
14.5.3 Address part fields. 105
14.5.4 Facility part fields . 105
14.5.4.1 Sub-address. 105
14.5.4.2 Priority. 105
14.5.4.3 Delivery/Storage request. 106
14.5.4.4 Report request . 106
14.5.4.5 Disposition. 107
14.5.4.6 Multicast area selection. 107
14.5.4.7 Time stamp . 108
14.5.4.8 Packet route. 108
14.5.5 Header checksum. 108
14.5.6 User data part. 108
14.6 Primitive definitions and format. 108
14.7 Protocol functions. 108
14.7.1 Data PDU composition . 109
14.7.1.1 PDU composition. 110
14.7.1.2 PDU composition. 110
14.7.1.3 PDU composition. 110
14.7.1.4 Composition of facility fields. 111
14.7.2 Delivery PDU composition . 111
14.7.2.1 PDU composition . 111
14.7.2.2 PDU composition . 111
14.7.2.3 PDU composition . 112
14.7.2.4 Composition of facility fields. 112
14.7.3 Data PDU decomposition . 112

Page 9
Draft prETS 300 393-2: June 1998
14.7.4 Delivery PDU decomposition.112
14.7.5 Route PDU .113
14.7.6 Forward PDU.113
14.7.7 Discard PDU.113
14.7.8 PDU header error detection .114
14.7.9 Facility functions.114
14.7.9.1 Sub-addressing.114
14.7.9.2 Priority.114
14.7.9.3 D/S (delivery/storage) request.115
14.7.9.3.1 Delivery facility .115
14.7.9.3.2 Storage facility .115
14.7.9.4 Report request.115
14.7.9.5 Multicast area selection .115
14.7.9.6 Time stamping.115
14.7.9.7 Disposition report.116
14.8 Provision of the underlying service .116
14.8.1 General.116
14.8.2 Operation over MLE .116
14.9 Conformance .116
14.10 Algorithms for PDU header error detection function.116
14.10.1 Symbols used in algorithms .117
14.10.2 Arithmetic conventions .117
14.10.3 Algorithm for generating checksum parameters .117
14.10.4 Algorithms for checking checksum parameters .118
14.10.5 Algorithm to adjust the checksum parameter when an octet is altered.118
15 Mobility Management (MM): service description.119
15.1 Introduction .119
15.2 Services offered.119
15.3 Primitive description.119
15.3.1 Service state model for the MS .120
15.3.2 Service primitives for the MS.120
15.3.2.1 Primitives for authentication of the network.120
15.3.2.2 Primitives for de-registration (detach).120
15.3.2.3 Primitives for indication of the state of a mobile .121
15.3.2.4 Primitives for registration .121
15.3.2.5 Primitives for energy saving mode .121
15.3.3 Primitive summary.121
15.3.4 Parameters definition .122
15.3.5 State description for the MS.122
15.3.5.1 Not updated .122
15.3.5.2 Wait updating.122
15.3.5.3 Updated .
...