SIST ETS 300 133-3:1998/A1:1999

• Abstract:

  RE/RES-04003-3

• Status: Published
• Publication Date: 30-Jun-1999
• ICS: 33.070.20 - Paging systems
• 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
• Ref Project: ETSI ETS 300 133-3/A1 ed.1 (1994-01) - Paging Systems (PS); Enhanced Radio MEssage System (ERMES); Part 3: Network aspects

Overview

SIST ETS 300 133-3:1998/A1:1999 – Paging Systems (PS); Enhanced Radio Message System (ERMES); Part 3: Network Aspects is a Slovenian standard aligning with the European ETS 300 133-3/A1 standard. This amendment outlines updates and clarifications to the network aspects of the European Radio Message System (ERMES), which serves as a standardized paging protocol across Europe. Key areas include the handling of character sets, network status management, message input and retrieval operations, and error codes-all critical for enhancing interoperability and functionality in paging networks.

ERMES supports efficient, reliable wireless messaging and is crucial for service providers and equipment manufacturers engaged in the operation and development of paging networks in compliance with international telecommunication standards.

---

Key Topics

1. Character Set Management

• Addition and specification of character set codes in multiple network operations to support both national and ERMES character sets.
• Ensures accurate conversion and display of numeric and alphanumeric messages, accommodating varying national requirements.
• Introduction of new procedures for message transmission based on character set agreement between network operators.

2. Network Status and Call Acceptance

• Clarified handling of "low network status" whereby calls cannot be accepted if the network is under low resource conditions, ensuring service stability.

3. Message Input and Retrieval

• Enhanced operations for input of calls using specific character sets, including parameters for sender and recipient codes, authentication, message types, and error handling.
• Expanded message retrieval operations, allowing mobile subscribers to request retransmission or retrieval of stored messages, further enriching service reliability.

4. Error Handling and Codes

• Expanded list of error codes for network operations, allowing more precise fault identification, such as “adc-Not-Valid”, “system-Overload”, and “diversion-Already-Activated”.

5. Protocol and Data Structure Updates

• Modifications to core data structures in the protocol description to accommodate new parameters such as character set lists and management codes.
• Updates to SDL diagrams and presentation of operational flows for clarity in network process modeling.

---

Applications

ERMES Network Operators

• Implement standardized approaches to character conversion, ensuring message compatibility across different national networks.
• Utilize improved error handling and status management to maintain high service availability and minimize message loss during low network resource periods.

Service Providers

• Deliver enhanced paging services with better support for national character sets and roaming capabilities.
• Enable users to send and retrieve messages using a variety of formats and character sets, accommodating business and emergency communications.

Paging Device Manufacturers

• Design receivers and transmitters compatible with ERMES protocol updates, ensuring devices can process and display messages correctly in any supported character set.
• Incorporate updated error recognition routines for robust device behavior across varying network states.

Network Integrators

• Apply standardized procedures in system integration projects to facilitate seamless interconnection between diverse paging infrastructures and management systems.

---

Related Standards

• ETS 300 133 Series: Comprehensive specification for ERMES, including radio interface, network protocols, and operational procedures.
• ISO 646: International Standard for 7-bit coded character set for information exchange, referenced for numeric messaging in ERMES.
• ETS 300 133-2: Detailing character encoding tables and requirements for alphanumeric messaging.
• ETS 300 133-4: Messaging procedures, particularly for transparent (raw data) messages.

---

By addressing these key network aspects, SIST ETS 300 133-3:1998/A1:1999 contributes to enhanced interoperability, reliability, and expandability of ERMES-based paging systems across European and international markets. These updates are essential for stakeholders seeking to deliver or utilize advanced wireless paging services in compliance with the latest international telecommunication standards.

SLOVENSKI STANDARD
01-julij-1999
6LVWHPLRVHEQHJDNOLFD36(YURSVNLVLVWHP]DUDGLMVNRVSRURþDQMH(50(6
GHO2PUHåQLYLGLNL
Paging Systems (PS); Enhanced Radio MEssage System (ERMES); Part 3: Network
aspects
Ta slovenski standard je istoveten z: ETS 300 133-3/A1 Edition 1
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.

ETS 300 133-3
MENDMENT A1
A
January 1994
Source: ETSI TC-PS Reference: RE/PS-03002-3
ICS: 33.080
ERMES, paging
Key words:
This amendment A1 modifies
the European Telecommunication Standard ETS 300 133-3 (1992)
Paging Systems (PS);
European Radio Message System (ERMES)
Part 3: Network aspects
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - [e-mail]
X.400: Internet:
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 1994. All rights reserved.
New presentation - see History box

Page 2
ETS 300 133-3:1992/A1:1994
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 Standards Approval Dept." at the address shown on the title page.

Page 3
ETS 300 133-3:1992/A1:1994
Foreword
This Amendment to ETS 300 133-3 (1992) has been produced by the Paging Systems (PS) Technical
Committee of the European Telecommunications Standards Institute (ETSI).
This Amendment contains changes to the following pages of Edition 1 of ETS 300 133-3:
17, 34, 37, 38, 40, 68, 80, 120, 124, 125, 129, 130, 133, 144, 145, 165, 166, 196, 208, 209, 210, 211, 212,
213, 221, 222, 261, 262, 263, 265, 268, 269, 276, 278, 279, 280, 281.
Amendments
Page 17, amendment to Clause 2
Add the following reference after reference [37]:
[38] ISO 646 (1991): "Information technology - ISO 7-bit coded character set for
information exchange".
Page 34, amendment to subclause 7.1.1
Replace the second sentence on page 34, which reads "The PNC-I also converts . to the calling party.",
by the following sentence:
The PNC-I also converts, according to the rules described in subclauses 8.1.4 and 13.8, the national
character set to the ERMES character set and sends back an acknowledgement to the calling party.
Page 37, amendment to subclause 7.1.2.2
Add the following to the end of the paragraph in subclause 7.1.2.2:
Calls cannot be accepted if information about "low network status" has been received.
Page 38, amendment to subclause 7.1.2.7
Delete the last sentence of the first paragraph of subclause 7.1.2.7 which reads "Since the network status
when . without call acceptance criteria.", and replace it with the following sentence:
Calls cannot be accepted if information about "low network status" has been received.
Page 40, amendment to subclause 7.1.3.8
Delete the third paragraph of subclause 7.1.3.8 which reads "The network status when . without call
acceptance criteria.", and replace it with the following sentence:
Calls cannot be accepted if information about "low network status" has been received.

Page 4
ETS 300 133-3:1992/A1:1994
Page 68, amendment to subclause 8.1.4
Replace subclause 8.1.4 by the following:
8.1.4 Character conversion
Character conversion is applicable for numeric and alphanumeric services and applies only to the
message part.
NOTE: The access method may limit access to the complete ERMES character set.
Each PNC shall have a character conversion table for each access method supported by the PNC. The
character conversion tables shall be defined by the operator according to national requirements.
The conversion of the characters of the message shall be done according to the following rules.
If there is an agreement between the PNC-I network operator and the PNC-H network operator
(or if PNC-I = PNC-H): then PNC-I provides access method(s) with the possibility of choosing a different
character set used in the home network's receiver. From the access method, the PNC-I knows the
character set selected by the calling party. For example, this information is known from the dialogue or
from a specific access number.
If the chosen character set is not the ERMES character set, then the PNC-I has to verify that the receiver
of the mobile subscriber supports the corresponding character set (according to the parameters of the
database) in its list. This information is included in the data given in the Pager information result operation.
If it is supported, then the message is sent to the PNC-H with the appropriate conversion, according to the
character set code, and with this character set code included in the Page request operation.
The message is sent to the PNC-T with the character set code included in the Transmit operation. The
message is then transmitted through the I1 interface according to the corresponding procedure (I1 with
possible choice of character set for the receiver).
Receiving the message and the character set code, the receiver can display this message according to
the chosen alphabet.
If there is no agreement between the PNC-I network operator and the PNC-H network operator:
then the PNC-I sends the message without conversion (transparently) to the PNC-H. The Page request
operation will then include the character set code.
The conversion can then be done by the PNC-H which sends the message to the PNC-T.
The PNC-T transmits the message with the character set code given by the PNC-H in the transmit
operation. Receiving the message and the character set code, the receiver can display this message
according to the chosen alphabet.
If a calling party inputs a character which is not mapped by the operator to the ERMES character set then
that character shall be rejected and the calling party shall be notified.

Page 5
ETS 300 133-3:1992/A1:1994
Page 80, amendment to subclause 8.3.3.4.1
Add the following service identification code as the first listed item in subclause 8.3.3.4.1:
-70 Management of the legitimization for all calls by mobile subscribers
Page 120, amendment to subclause 9.2.5
Add the following option after option number 21:
22 Call input operation with specific character set
Page 120, amendment to subclause 9.2.5.1.1
Add the following parameter after parameter "LUM":
LRE Char. '1' or '0' O Leg. code for repetition requested.
Page 124, amendment to subclause 9.2.5.5
Delete the entry for parameter "OAdC" and replace with the following:
OAdC String of num. char. O Address code.
Page 124, amendment to subclause 9.2.5.5.1
Delete the entry for parameter "GAdC" and replace with the following:
GAdC String of num. char. E Group address code with which the
address list are registered.
Page 125, amendment to subclause 9.2.5.6
Delete the entry for parameter "OAdC" and replace with the following:
OAdC String of num. char. O Address code.

Page 6
ETS 300 133-3:1992/A1:1994
Page 129, amendment to subclause 9.2.5.15
Replace subclause 9.2.5.15 by the following text (leaving subclauses 9.2.5.15.1 and 9.2.5.15.2
unchanged):
9.2.5.15 Message retrieval operation
The operation is used by a MS to request retransmission or retrieval on stored messages. The following
operations' negative result are listed in subclause 9.2.7.
Parameter Type Presence Description
AdC String or num char E AdC for the mobile subscription to which
messages are stored.
AC String of char. E Authentication code.
MNo 1 String of num char. E Message number to be retrieved or the first and
last message numbers to be retrieved or
2 String of num char. retrieval of the last stored message, second
last stored message, etc. where 0 = last stored
separated with ','
message, -1 = second last stored message,
etc. or an interval of stored messages (e.g.
-2,0 = interval from the third last stored
message to the last stored message, where 0
is the highest number).
R/T Char. 'R' (52hex) or E Retrieval with positive result or retransmit on
Char. 'T' (54hex) radio channel.
Page 130, amendment to subclause 9.2.5.15.1
Change description of parameter "Msg:s" to read as follows:
Msg:s See below: O List of parameters. Each parameter
consists of 5 items separated with ',' which
are described below:
MN String of numeric char Message number of the retrieved message.
MT One num. char. (1-4) Message type.
SDT 10 num. char. Stored date and time (DDMMYYhhmm)
MP String of char. Message part encoded according to the type of
message.
NB String of numeric char. Number of bits in Transparent Data (TD)
message.
Page 7
ETS 300 133-3:1992/A1:1994
Page 133, addition of new subclauses 9.2.5.23, 9.2.5.23.1 and 9.2.5.23.2
Add the following subclauses after subclause 9.2.5.22.2:
9.2.5.23 Call input operation with specific character set
The operation is used for call input when no SSs are requested by the calling party and when a specific
character set is used. The following list shows the parameters used in the operation data field.
Parameter Type Presence Description
AdC String or num char. E Address code, recipient.
AOdC String or num char. O Address code, originator.
AC String or char. O Authentication code, originator.
MT 1 numeric char. (1-4) E Message type, associated parameters depend
on the value of the message type.
alternative 1: Tone only: no additional parameters used.
alternative 2:
NMsg String of char. O Numeric message.
alternative 3:
AMsg String of char. O Alphanumeric message.
alternative 4:
NB String of num. char. E Number of bits in the TD message.
TMsg String of char. O(1) TD message encoded into IA5 characters.
CS 1 numeric char. E Code of character set used.
9.2.5.23.1 Call input operation with specific character set (positive result)
The following list shows the parameters used in the positive result data field.
Parameter Type Presence Description
ACK Char. 'A' E Positive acknowledgement
SM String of char. O System message
9.2.5.23.2 Call input operation with specific character set (negative result)
Negative result parameters, see subclause 9.2.5.1.2. Error codes which may be returned in the operations
negative result are listed in subclause 9.2.7.

Page 8
ETS 300 133-3:1992/A1:1994
Page 144, amendment to subclause 11.2.1.1
Add the following line after the line "Paging category":
Character set code
Page 145, amendment to subclause 11.2.1.2
Add the following line after the line "Paging category":
Character set code
Page 165, amendment to subclause 13.2.1
Add the following line after line "E RIC":
O MSI
Page 166, amendment to subclause 13.2.1
Add the following 2 lines after the line "E Type of receiver":
O Additional character set
- list of character set codes
Page 196, amendment to figure B.1
Replace figure B.1
...