Abstract

Revision of ETS 300 133 in consideration of change requests received by RES 4.

Status
Published
Publication Date
30-Sep-1998
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Oct-1998
Due Date
01-Oct-1998
Completion Date
01-Oct-1998

Buy Documents

Standard

SIST ETS 300 133-3:1998

English language (277 pages)
Preview
Preview
e-Library read for
×1 day

SIST ETS 300 133-3:1998 is the Slovenian version of ETS 300 133-3 Edition 2 from ETSI. It specifies the network aspects of the Enhanced Radio MEssage System (ERMES), including system architecture, numbering and addressing, call processing, access methods, and the internal interfaces used to move paging traffic through the network. It is written for people who design, integrate, operate, or assess ERMES network equipment and access services.

What does SIST ETS 300 133-3:1998 specify?

SIST ETS 300 133-3:1998 describes the network side of ERMES. The standard covers how the Telecommunication Network (TN) is organized, how subscribers and network blocks are identified, how calls are processed, and how access, interworking, and paging-area control are handled in practice.

The document is organized into clauses for scope, references, definitions, architecture, numbering, call processing, access methods, the I5, I4, I3 and I2 interfaces, the Paging Network Controller (PNC), and the Paging Area Controller (PAC). It also contains annexes with SDL diagrams, access-method examples, ROSE operations, ASN.1 definitions, and typical I6 dialogues.

AnnexWhat it covers
BSDL diagrams for call processing, including paging calls, roaming, and call diversion
CAn informative list of access methods and their combinations of network, type, mode, and terminal
DNormative SDL diagrams for interactive access mode
ENormative PNC I4 ROSE operations and their parameters
FNormative ASN.1 specification for the I4 interface protocol
GInformative typical I6 dialogues for call input

What are the key requirements of SIST ETS 300 133-3:1998?

The standard defines the network roles and message paths that make ERMES work across operators, access networks, and paging areas. In practice, this is the part a network planner or implementer uses to decide how calls enter the system, how they are routed, and how network elements must behave toward each other.

System architecture and roles

Clause 4 divides the ERMES network into the TN part and the operation and maintenance network part. Each TN is associated with a PNC, and each PAC manages one Paging Area (PA); one PNC shall control up to 64 PACs. That matters because it fixes the network scale and the control structure that implementers must support.

Clause 4 also shows the functional split between the PNC, PAC and BS, and states that the I1 interface is defined in ETS 300 133-4. For a reader, that means this part defines the network control functions, while the air-interface detail sits in the companion part.

Numbering, addressing, and identification

Clause 5 explains how Mobile Subscribers (MS) and Fixed Subscribers (FS) are addressed and identified. It distinguishes one-stage and two-stage selection: one-stage selection sends the AdC directly with the call, while two-stage selection first uses a Service Number (SN) and then sends the AdC and message or subscriber-feature dialogue. This matters because the operator must choose the right access path for each service.

Clause 5 also requires each PNC to have an unambiguous PNC number built from zone code, country code, and operator code. PA numbers are two digits, PAC numbers are two digits, and BS numbers have three digits maximum. The clause also lists Supplementary Service identification codes for page input and subscriber features, so systems can recognize services such as repetition, prioritization, multi-address calling, deferred delivery, roaming, and password-related functions.

Call processing and quality of service

Clause 6 describes how page input is processed, including the roles called PNC-I, PNC-H and PNC-T. It covers supplementary services such as choice of destination, repetition, prioritization, urgent message indication, deferred delivery, reverse charging, standard texts, and multi-address calls, as well as subscriber features such as diversion, message storing, temporary barring, encryption, roaming, group call, and legitimisation of all calls. In practice, this clause tells implementers which service logic the network has to support at each stage.

Clause 6 also defines transaction time limits when more than one PNC is involved. The standard says the applicable I4 transaction delays shall meet the stated limits for greater than 90% of calls processed, with page request allowed a longer limit than the other I4 operations. That matters because it ties inter-PNC messaging directly to user experience and paging reliability.

Access methods and user dialogues

Clause 7 groups access methods by access network, access type, access mode, and access terminal. The standard separates telephonic from non-telephonic access and gives generic protocols for interactive and non-interactive operation, including one-stage and two-stage selection. Annex C lists example combinations such as PSTN, TELEX, PSPDN, CSPDN, ISDN, and bureau access.

Clause 7 also states that some supplementary services require legitimisation, while mobile and fixed subscribers use authentication for access to certain features. For a buyer or engineer, this is important because the terminal type and access network determine whether the service can be offered in a standard or specialized way.

I5 interface and Universal Computer Protocol (UCP)

Clause 8 defines the I5 interface between the access TN and the PNC and describes version 02.01 of the Universal Computer Protocol (UCP). It supports access over PSTN, PSPDN, CSPDN, ISDN, and Telex Network. The protocol includes message header, data field, checksum, version negotiation, and a defined set of operations such as call input, multiple address call input, address list management, standard text handling, roaming control, message retrieval, call barring, call diversion, deferred delivery, and feature reset.

For operators and gateway designers, this clause is the practical link between external access systems and ERMES service control. It also defines error codes for invalid AdC, authentication failure, message too long, invalid character set, and similar conditions.

I4, I3 and I2 interfaces

Clause 9 defines the I4 interface used for communication between PNCs. It uses a minimum profile called the basic kernel, requires ACSE association control, uses ROSE operations, and relies on password-based authorization when PNCs bind to each other. Annex E gives the operation definitions and Annex F gives the ASN.1 format.

Clause 10 defines the I3 interface from PNC-T to PAC as a functional interface for paging data transfer and operation and maintenance messages. Clause 11 defines the I2 interface between PAC and BS, with X.21bis physical interface elements, ISO/IEC 7776 link procedures, PAC-master/BS-slave control, and application transactions for page requests, BS time reference, status, control, poll and report functions. These clauses matter because they show how paging traffic is carried from controller to radio equipment.

PNC and PAC behavior

Clause 12 sets out the PNC databases, interface management, call acceptance principles, universal time reference, character-set translation, encryption handling, transparent data calls, and call queuing. Clause 13 describes the PAC architecture, its input and output sections, control section, and the way it batches, queues and prioritizes paging messages before sending them to BSs. For implementation and testing, these clauses are the practical rules for controller behavior under load and during maintenance.

What terms does SIST ETS 300 133-3:1998 define?

  • Address Code (AdC) - The code that identifies the Radio Identity Code (RIC) and the alert signal indicator for a paging target.
  • Paging Network Controller (PNC) - The functional entity that controls network-related features and manages the I3, I4 and I5 interfaces.
  • Paging Area Controller (PAC) - The functional block that manages one Paging Area and the Base Stations that provide its radio coverage.
  • access method - The combination of access terminal, access network, access mode, and access type used to reach a service.
  • access mode - The communication procedure between the calling party and the PNC, either interactive or non-interactive.
  • access type - The selection method, either one-stage or two-stage.
  • Authentication Code (AC) - A code used by a mobile or fixed subscriber so the PNC can verify identity.
  • Supplementary Service (SS) - A service attached to page input or subscriber features, such as prioritization, roaming, deferred delivery, or reverse charging.

Who uses SIST ETS 300 133-3:1998?

SIST ETS 300 133-3:1998 is used by ERMES network operators, system integrators, and equipment vendors who need to build or connect paging systems. It is also relevant to engineers working on PNCs, PACs, BSs, access networks, O&M systems, and gateways that support paging, roaming, subscriber features, and message handling.

Quality and test teams use it to check call-processing behavior, interface conformance, error handling, and timing behavior across the ERMES network. Buyers use it to compare equipment and ask whether a supplier supports the required interfaces, access methods, and controller functions.

What changed in SIST ETS 300 133-3:1998 from the previous edition?

SIST ETS 300 133-3:1998 is a revision of ETS 300 133 prepared in consideration of change requests received by RES 4. It is identified as the second edition.

Which standards are used with SIST ETS 300 133-3:1998?

  • ETS 300 133-2 - Provides the ERMES service aspects, including QoS limits and the character set used in the network.
  • ETS 300 133-4 - Provides the ERMES air interface specification and the I1 interface referenced by this part.
  • ETS 300 133-7 - Provides the operation and maintenance aspects used alongside the network description here.
  • ITU-T Recommendation E.163 - Provides PSTN international dialling numbers.
  • CEPT Recommendation T/SF 31 - Provides service and facility aspects of ISDN.
  • ITU-T Recommendation F.69 - Provides the plan for telex destination codes.
  • ITU-T Recommendation F.410 - Provides the public message transfer service framework.
  • ITU-T Recommendation F.420 - Provides the public interpersonal messaging service framework.

What does the SIST ETS 300 133-3:1998 document contain?

The document contains structured technical descriptions, protocol rules, and interface definitions rather than a simple service summary. It includes service-number and supplementary-service code tables, network architecture figures, access-method dialogues, and detailed call-processing flows for paging, roaming, and call diversion.

It also includes operational content that supports implementation and testing: UCP message formats, I4 ROSE operations, ASN.1 definitions, error codes, and database descriptions for subscriber records, groups, configuration, status, and geographical areas. Annexes B, D, and G provide SDL and dialogue examples, while annexes E and F give the formal data and operation definitions used for PNC interworking.

Buy Documents

Standard

SIST ETS 300 133-3:1998

English language (277 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified

Sponsored listings

Frequently Asked Questions

SIST ETS 300 133-3:1998 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "ElectroMagnetic Compatibility and Radio Spectrum Matters (ERM); Enhanced Radio MEssage System (ERMES); Part 3: Network aspects". This standard covers: Revision of ETS 300 133 in consideration of change requests received by RES 4.

Revision of ETS 300 133 in consideration of change requests received by RES 4.

SIST ETS 300 133-3:1998 is classified under the following ICS (International Classification for Standards) categories: 33.070.20 - Paging systems. The ICS classification helps identify the subject area and facilitates finding related standards.

SIST ETS 300 133-3:1998 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


SLOVENSKI STANDARD
01-oktober-1998
(OHNWURPDJQHWQD]GUXåOMLYRVW (0& LQ]DGHYHSRYH]DQH]UDGLMVNLPVSHNWURP
(50 ,]EROMãDQLVLVWHP]DUDGLMVNRVSRURþDQMH (50(6 GHO2PUHåQLYLGLNL
ElectroMagnetic Compatibility and Radio Spectrum Matters (ERM); Enhanced Radio
MEssage System (ERMES); Part 3: Network aspects
Ta slovenski standard je istoveten z: ETS 300 133-3 Edition 2
ICS:
33.070.20 Sistem za osebni klic Paging systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 133-3
TELECOMMUNICATION November 1997
STANDARD Second Edition
Source: ERM Reference: RE/ERM-RP04-007-3
ICS: 33.020
Key words: ERMES, paging, radio, network
Electromagnetic compatibility
and Radio spectrum Matters (ERM);
Enhanced Radio MEssage System (ERMES);
Part 3: Network aspects
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
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1997. All rights reserved.

Page 2
ETS 300 133-3: November 1997
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 Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 133-3: November 1997
Contents
Foreword .15
Intellectual Property Rights.15
1 Scope .17
2 Normative references.17
3 Definitions and abbreviations .18
3.1 Definitions .18
3.2 Abbreviations .21
4 System architecture.23
4.1 General .23
4.2 Telecommunication Network (TN) part.23
4.2.1 Functional description of PNC.24
4.2.2 Functional description of PAC.24
4.2.3 Functional description of BS.24
4.3 General description of network interfaces .24
4.3.1 I6 interface.24
4.3.2 I5 interface.24
4.3.3 I4 interface.25
4.3.4 I3 interface.25
4.3.5 I2 interface.25
4.3.6 I1 interface.25
4.4 Operation & maintenance network part .25
4.5 General description of O&M interfaces.25
5 Numbering, addressing and identification .29
5.1 General .29
5.2 Addressing and numbering.30
5.2.1 Mobile subscriber .30
5.2.1.1 Individual.30
5.2.1.1.1 One-stage selection.30
5.2.1.1.2 Two-stage selection.30
5.2.1.2 Group.31
5.2.2 Fixed subscribers .31
5.3 Identification of network functional blocks .31
5.4 Service access.32
5.4.1 Service numbers .32
5.4.2 Supplementary service identification codes .32
6 Call processing.33
6.1 Call processing for page input .33
6.1.1 General principles .33
6.1.1.1 PNC-I processing .35
6.1.1.2 PNC-H processing.36
6.1.1.3 PNC-T processing .37
6.1.2 Supplementary services .37
6.1.2.1 General principle.37
6.1.2.2 Choice of destination .37
6.1.2.3 Repetition.37
6.1.2.4 Prioritization .37
6.1.2.5 Multi-address .38
6.1.2.6 Urgent message indication .38
6.1.2.7 Deferred delivery .38
6.1.2.8 Standard texts.38

Page 4
ETS 300 133-3: November 1997
6.1.2.9 Reverse charging. 38
6.1.3 Subscriber features. 38
6.1.3.1 General principle. 38
6.1.3.2 Diversion . 38
6.1.3.3 Repetition. 39
6.1.3.4 Message storing. 39
6.1.3.5 Prioritization . 39
6.1.3.6 Reverse charging. 39
6.1.3.7 Temporary barring . 39
6.1.3.8 Deferred delivery. 40
6.1.3.9 Encryption . 40
6.1.3.10 Roaming. 40
6.1.3.11 Group call. 40
6.1.3.12 Automatic retransmission of the last message number. 41
6.1.3.13 Legitimisation of all calls . 41
6.2 Call processing for access to subscriber features . 41
6.2.1 General principles. 41
6.2.2 Available to all calling parties. 42
6.2.2.1 Subscriber directory . 42
6.2.3 Available to fixed subscribers . 42
6.2.3.1 Address list management . 42
6.2.3.2 Editing of standard text . 42
6.2.3.3 Advice of accumulated call charges. 42
6.2.3.4 Password management . 42
6.2.3.5 Legitimisation code management . 43
6.2.4 Available to mobile subscribers . 43
6.2.4.1 Roaming. 43
6.2.4.1.1 General principles . 43
6.2.4.1.2 PNC-I processing . 43
6.2.4.1.3 PNC-H processing . 45
6.2.4.2 Temporary barring . 46
6.2.4.3 Deferred delivery. 47
6.2.4.4 Call diversion. 48
6.2.4.5 Message retrieval. 49
6.2.4.6 Password management . 49
6.2.4.7 Legitimisation code management . 50
6.2.4.8 All features reset . 50
6.3 Call processing transaction time limits. 50
7 Access methods . 52
7.1 General. 52
7.1.1 Generic protocol for non-interactive access mode . 53
7.1.2 Generic protocol for interactive access mode - two-stage selection . 53
7.1.2.1 Functional description of the protocol . 54
7.1.2.1.1 Common elements (for both service
numbers). 54
7.1.2.1.2 Protocol via Service Number 1 (SN1) . 54
7.1.2.1.3 Protocol via Service Number 2 (SN2) . 55
7.1.2.2 System responses and acknowledgement . 55
7.1.2.2.1 General system messages. 56
7.1.2.2.2 Input prompts . 56
7.1.2.2.3 Input acknowledgements . 57
7.1.2.2.4 Help and guidance messages. 57
7.1.2.3 Input editing and typing error correction. 57
7.1.2.3.1 The Escape command . 57
7.1.2.3.2 Other editing commands - terminals
other than DTMF telephones . 58
7.1.2.4 Guidance to the calling party. 58
7.1.2.4.1 Help command. 58
7.1.2.4.2 Incomplete or interrupted input . 58
7.1.2.4.3 No input - time-out. 58
7.1.2.4.4 Invalid input . 58
7.1.3 Generic protocol for interactive access mode - one-stage selection. 58

Page 5
ETS 300 133-3: November 1997
7.1.3.1 Functional description of the protocol.58
7.1.3.1.1 Common elements .59
7.1.3.1.2 The protocol.59
7.1.3.2 System responses and acknowledgements .59
7.1.3.2.1 General system message.59
7.1.3.2.2 Input prompts.60
7.1.3.2.3 Input acknowledgements.60
7.1.3.2.4 Help and guidance messages .61
7.1.3.3 Input editing and typing error correction .61
7.1.3.3.1 The Escape command.61
7.1.3.3.2 Other editing commands - terminals
other than DTMF telephones .61
7.1.3.4 Guidance to the calling party .61
7.1.3.4.1 Help command.61
7.1.3.4.2 Incomplete or interrupted input .62
7.1.3.4.3 No input - time-out .62
7.1.3.4.4 Invalid input.62
7.1.4 Character conversion .62
7.1.5 Use of special characters.63
7.2 Access methods applicable to each service.63
7.2.1 Basic services .63
7.2.2 Supplementary Services (SSs) .64
7.2.2.1 Page input related SSs.64
7.2.2.2 Subscriber features .64
7.2.2.2.1 Subscriber directory.64
7.2.2.2.2 Fixed subscribers.64
7.2.2.2.3 Mobile subscribers.65
7.3 Telephonic access methods .65
7.3.1 General.65
7.3.1.1 Input editing and typing error correction .65
7.3.1.2 Invoking the characters in the numeric service .66
7.3.1.3 Invoking the characters in the alphanumeric service.66
7.3.1.4 Guidance to the calling party .67
7.3.2 One-stage selection method .68
7.3.2.1 Tone-only message input .68
7.3.2.1.1 Functional description of the protocol .68
7.3.2.2 Numeric message input.68
7.3.2.2.1 Functional description of the protocol .68
7.3.2.2.2 System responses and
acknowledgements.68
7.3.2.3 Alphanumeric service .68
7.3.2.3.1 Functional description of the protocol .68
7.3.2.3.2 System responses and
acknowledgements.69
7.3.2.4 Message input with Supplementary Services (SSs).69
7.3.2.4.1 Functional description of the protocol .69
7.3.2.4.2 System responses and
acknowledgements.69
7.3.2.4.3 Supplementary Service (SS)
sequences .69
7.3.3 Two-stage selection method .70
7.3.3.1 Tone-only message input .70
7.3.3.1.1 Functional description of the protocol .70
7.3.3.1.2 System responses and
acknowledgements.71
7.3.3.2 Numeric message input.71
7.3.3.2.1 Functional description of the protocol .71
7.3.3.2.2 System responses and
acknowledgements.71
7.3.3.3 Alphanumeric message input .72
7.3.3.3.1 Functional description of the protocol .72
7.3.3.3.2 System responses and
acknowledgements.72

Page 6
ETS 300 133-3: November 1997
7.3.3.4 Call input with supplementary services. 72
7.3.3.4.1 Functional description of the protocol . 72
7.3.3.4.2 System responses and
acknowledgements . 73
7.3.3.4.3 Supplementary service sequences . 73
7.3.3.5 Subscriber features for fixed subscribers . 74
7.3.3.5.1 Functional description of the protocol . 74
7.3.3.6 Subscriber features for mobile subscribers . 74
7.3.3.6.1 Functional description of the protocol . 74
7.3.3.6.2 System responses and
acknowledgements . 75
7.3.3.6.3 Subscriber feature control sequences. 75
7.4 Alphanumeric terminal access methods . 76
7.5 Telex access . 77
7.5.1 One-stage selection. 77
7.5.1.1 General . 77
7.5.1.2 Interactive mode . 77
7.5.1.2.1 Functional description of the protocol . 77
7.5.1.3 Non-interactive mode. 77
7.5.1.3.1 Functional description of the protocol . 77
7.5.2 Two-stage selection - interactive . 77
7.5.2.1 General . 77
7.5.2.1.1 System responses and
acknowledgements . 77
7.5.2.1.2 Input editing and typing error
correction . 77
7.5.2.1.3 Guidance to the calling party. 77
7.5.2.2 The protocol via SN1. 78
7.5.2.2.1 Interactive mode. 78
7.5.2.2.2 Fast interactive mode. 78
7.5.2.2.3 Call input related supplementary
services . 78
7.5.2.3 The protocol via SN2. 79
7.5.2.3.1 Roaming interactive mode . 79
7.5.2.3.2 Roaming fast interactive mode. 79
7.5.3 Two-stage selection - non-interactive. 80
7.5.3.1 General . 80
7.5.3.2 The protocol via SN1. 80
7.5.3.2.1 Call input . 80
7.5.3.2.2 Call input related supplementary
services . 80
7.5.3.3 The protocol via SN2. 80
7.6 Message handling system access . 80
7.6.1 General . 80
7.6.2 ERMES access unit. 81
7.6.3 Structure of IP-message. 81
7.6.4 One-stage selection. 81
7.6.4.1 Operational procedures . 81
7.6.4.2 Call input . 82
7.6.5 Two-stage selection. 82
7.6.5.1 Operational procedures . 82
7.6.5.2 Call input . 82
7.6.5.3 Call input with supplementary services. 83
7.6.5.4 Access to subscriber features. 83
7.7 Bureau access . 83
7.8 Videotex access method. 83
7.8.1 General . 83
7.8.2 Message page input . 83
7.9 ISDN Access . 84
7.9.1 General . 84
7.9.2 One-stage selection. 84
7.9.2.1 One-stage selection for tone-only service via ISDN. 84
7.9.2.2 One-stage selection for numeric service via ISDN (UUS3) 85

Page 7
ETS 300 133-3: November 1997
7.9.2.3 One-stage selection for alphanumeric service via ISDN
(UUS3).89
7.9.2.4 One-stage selection for numeric service via ISDN (UUS1).89
7.9.2.5 One-stage selection for alphanumeric service via ISDN
(UUS1).91
7.9.3 Two-stage selection access type .91
7.9.3.1 Two-stage selection for tone-only service via ISDN
(UUS3).91
7.9.3.2 Two-stage selection for numeric service via ISDN (UUS3).94
7.9.3.3 Two-stage selection for alphanumeric service via ISDN
(UUS3).99
7.9.3.4 Two-stage selection for numeric service via ISDN (UUS1).99
7.9.3.5 Two-stage selection for alphanumeric service via ISDN
(UUS1).101
8 I5 interface.101
8.1 General .101
8.2 Universal computer protocol .101
8.2.1 Introduction.101
8.2.2 Operation and result.101
8.2.3 Data transaction sequence.102
8.2.4 Description of message format .102
8.2.4.1 General.102
8.2.4.2 Header.103
8.2.4.3 Data field.103
8.2.4.4 Checksum.104
8.2.4.5 UCP version number negotiation:.104
8.2.4.5.1 PNC-I supporting version 01.01 only .104
8.2.4.5.2 PNC-I supporting only lower versions
than the version proposed by calling
party .104
8.2.4.5.3 PNC-I supporting the same version
number.105
8.2.4.5.4 PNC-I only supporting higher versions
than the proposed one.105
8.2.5 Operations provided by the Universal Computer Interface .105
8.2.5.1 Enquiry operation.106
8.2.5.1.1 Enquiry operation (positive result) .106
8.2.5.1.2 Enquiry operation (negative result) .106
8.2.5.2 Call input operation.106
8.2.5.2.1 Call input operation (positive result).107
8.2.5.2.2 Call input operation (negative result) .107
8.2.5.3 Multiple address call input operation .107
8.2.5.3.1 Multiple address call input operation
(positive result).108
8.2.5.3.2 Multiple address call input operation
(negative result) .109
8.2.5.4 Call input with supplementary services operation.109
8.2.5.4.1 Call input with supplementary service
operation (positive result).110
8.2.5.4.2 Call input with supplementary
information (negative result) .110
8.2.5.5 Address list information operation .110
8.2.5.5.1 Address list information operation
(positive result).111
8.2.5.5.2 Address list information operation
(negative result) .111
8.2.5.6 Change address list operation.111
8.2.5.6.1 Change address list operation
(positive result).111
8.2.5.6.2 Change address list operation
(negative result) .111
8.2.5.7 Advice of accumulated charges operation.111

Page 8
ETS 300 133-3: November 1997
8.2.5.7.1 Advice of accumulated charges
operation (positive result). 112
8.2.5.7.2 Advice of accumulated charges
operation (negative result). 112
8.2.5.8 Password management operation . 112
8.2.5.8.1 Password management operation
(positive result). 112
8.2.5.8.2 Password management operation
(negative result). 112
8.2.5.9 Legitimisation code management operation . 112
8.2.5.9.1 Legitimisation code management
operation (positive result). 113
8.2.5.9.2 Legitimisation code management
operation (negative result). 113
8.2.5.10 Standard text information operation. 113
8.2.5.10.1 Standard text information operation
(positive result). 113
8.2.5.10.2 Standard text information operation
(negative result). 114
8.2.5.11 Change standard text operation. 114
8.2.5.11.1 Change standard text operation
(positive result). 114
8.2.5.11.2 Change standard text operation
(negative result). 114
8.2.5.12 Request roaming information operation. 114
8.2.5.12.1 Request roaming information
operation (positive result). 114
8.2.5.12.2 Request roaming information
operation (negative result). 115
8.2.5.13 Change roaming operation . 115
8.2.5.13.1 Change roaming operation (positive
result) . 115
8.2.5.13.2 Change roaming operation (negative
result) . 115
8.2.5.14 Roaming reset operation. 116
8.2.5.14.1 Roaming reset operation (positive
result) . 116
8.2.5.14.2 Roaming reset operation (negative
result) . 116
8.2.5.15 Message retrieval operation. 116
8.2.5.15.1 Message retrieval operation (positive
result) . 117
8.2.5.15.2 Message retrieval operation (negative
result) . 117
8.2.5.16 Request call barring operation . 118
8.2.5.16.1 Request call barring operation
(positive result). 118
8.2.5.16.2 Request call barring operation
(negative result). 118
8.2.5.17 Cancel call barring operation . 118
8.2.5.17.1 Cancel call barring operation (positive
result) . 118
8.2.5.17.2 Cancel call barring operation (negative
result) . 118
8.2.5.18 Request call diversion operation. 118
8.2.5.18.1 Request call diversion operation
(positive result). 119
8.2.5.18.2 Request call diversion operation
(negative result). 119
8.2.5.19 Cancel call diversion operation . 119
8.2.5.19.1 Cancel call diversion operation
(positive result). 119

Page 9
ETS 300 133-3: November 1997
8.2.5.19.2 Cancel call diversion operation
(negative result) .119
8.2.5.20 Request deferred delivery.119
8.2.5.20.1 Request deferred delivery (positive
result).119
8.2.5.20.2 Request deferred delivery (negative
result).119
8.2.5.21 Cancel deferred delivery.119
8.2.5.21.1 Cancel deferred delivery (positive
result).120
8.2.5.21.2 Cancel deferred delivery (negative
result).120
8.2.5.22 All features reset operation.120
8.2.5.22.1 All features reset operation (positive
result).120
8.2.5.22.2 All features reset operation (negative
result).120
8.2.5.23 Call input operation with additional character set .120
8.2.5.23.1 Call input operation with specific
character set (positive result).120
8.2.5.23.2 Call input operation with specific
character set (negative result) .121
8.2.5.24 UCP Version status request (OT = 23).121
8.2.5.24.1 UCP Version status request (positive
result).121
8.2.5.24.2 UCP Version status request (negative
result).121
8.2.5.25 Mobile subscriber feature status request.121
8.2.5.25.1 Mobile subscriber feature status
request (positive result) .122
8.2.5.25.2 Mobile subscriber feature status
request (negative result) .123
8.2.6 Error codes.123
8.2.7 Error codes applicable to each operation.124
9 Network interworking (I4 interface) .124
9.1 General .124
9.2 Protocol stack for the I4 interface .125
9.2.1 Physical, link and network layers.125
9.2.2 Transport layer .125
9.2.3 Session layer.125
9.2.4 Presentation layer.125
9.2.4.1 Presentation contexts .125
9.2.5 Application layer .125
9.2.5.1 ACSE.126
9.2.5.2 ROSE.126
9.2.5.3 Other application entities .126
9.3 PNC operations.126
9.3.1 Introduction.126
9.3.2 Description of operations.126
9.3.2.1 General.126
9.3.2.2 Pager information .126
9.3.2.3 Page request .126
9.3.2.4 Transmit.127
9.3.2.5 Choice of destination .127
9.3.2.6 Roaming validation .127
9.3.2.7 Roaming reset .127
9.3.2.8 Roaming information .127
9.3.2.9 Change roaming .127
9.3.2.10 Confirm change of roaming .127
9.3.2.11 Call diversion start .127
9.3.2.12 Call diversion stop .127
9.3.3 Use of operations .127

Page 10
ETS 300 133-3: November 1997
9.4 Use of ACSE . 129
9.5 Use of ROSE. 130
9.6 PNC addressing . 132
9.6.1 PNC network address. 132
9.6.2 PNC layer 4, 5, 6 and application addresses. 132
9.7 Interoperability of version 1 and version 2 systems . 132
9.7.1 Protocol negotiation between adjacent PNC's. 132
10 I3 interface. 133
10.1 General description . 133
10.2 Functional description . 133
10.2.1 List of functional messages . 133
10.2.1.1 Paging data transfer, individual call . 133
10.2.1.2 Paging data transfer, group call . 133
10.2.1.3 Operation and maintenance messages . 134
11 PAC to BS Interface (I2 interface) . 134
11.1 General aspects and principles. 134
11.2 Layer 1 . 134
11.3 Layer 2 . 134
11.4 Layer 3 . 135
11.5 Layer 4 (fragmentation). 135
11.5.1 General . 135
11.5.2 Fragmentation header . 135
11.5.3 Description. 135
11.6 Layer 7 (application). 136
11.6.1 General . 136
11.6.2 Data processing. 136
11.6.3 Application header . 136
11.6.4 Transaction data. 138
11.6.4.1 General . 138
11.6.4.2 Page request transaction . 138
11.6.4.2.1 Page request operation. 138
11.6.4.2.2 Page request result . 140
11.6.4.3 BS time reference transaction. 141
11.6.4.3.1 BS time reference operation . 141
11.6.4.3.2 BS time reference result. 141
11.6.4.4 Status request transaction . 142
11.6.4.4.1 Status request operation . 142
11.6.4.4.2 Status request result . 142
11.6.4.5 Control command transaction. 143
11.6.4.5.1 Control command operation. 144
11.6.4.5.2 Control command result. 146
11.6.4.6 Poll request transaction. 147
11.6.4.6.1 Poll request operation . 147
11.6.4.6.2 Poll request result. 147
11.6.4.7 Report request transaction. 148
11.6.4.7.1 Report request operation . 148
11.6.4.7.2 Report request result. 150
12 Paging network controller specification . 152
12.1 PNC functional description. 152
12.2 Database specifications . 152
12.2.1 Mobile Subscriber (MS) AdC-records database . 153
12.2.2 Mobile Subscriber (MS) RIC-message database . 154
12.2.3 Fixed subscriber records database . 154
12.2.4 Group database for group calls . 155
12.2.5 Closed User Group (CUG) database. 155
12.2.6 System addressing database . 155
12.2.6.1 PNC/PNC addressing . 156
12.2.6.2 PNC/OMC addressing . 156
12.2.6.3 PNC/PAC addressing. 156
12.2.7 System configuration database . 156

Page 11
ETS 300 133-3: November 1997
12.2.8 System status database.156
12.2.9 Geographical area database.157
12.3 Management of the I5 interface.157
12.3.1 Configuration .157
12.3.2 Processing of fault situations.157
12.3.3 Processing of O&M data .157
12.4 Management of the I4 interface.157
12.4.1 Control of I4 passwords.157
12.5 Management of the I3 interface.158
12.6 Call acceptance principles and calculation .158
12.6.1 General principles .158
12.6.2 Definition of terms .159
12.6.3 State detection and parameter calculation.161
12.6.4 Availability and delay evaluation.162
12.6.4.1 Availability evaluation involving only paging areas .162
12.6.4.2 Availability evaluation involving only geographical areas.162
12.6.4.3 Availability evaluation involving paging and geographical
areas.
...