SIST ETS 300 133-3:1998/A1:1999
(Amendment)Paging Systems (PS); Enhanced Radio MEssage System (ERMES); Part 3: Network aspects
- Abstract
RE/RES-04003-3
- Status
- Published
- Publication Date
- 30-Jun-1999
- 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
SIST ETS 300 133-3:1998/A1:1999 is the Slovenian version of ETS 300 133-3/A1 Edition 1 from ETSI for Paging Systems (PS) and Enhanced Radio Message System (ERMES). It amends the network-aspects part of the standard, with changes focused on character-set handling, call acceptance, paging operations, and the protocol data used by paging network functions.
What does SIST ETS 300 133-3:1998/A1:1999 specify?
SIST ETS 300 133-3:1998/A1:1999 specifies amendments to the network aspects of ETS 300 133-3. In practice, it updates how paging networks process messages, choose character sets, accept calls, and represent protocol data.
The amendment touches Clause 2, Clauses 7, 8, 9, 11 and 13, and Annexes B, E and F. That matters because implementers need to align software, database fields, and call-processing logic with the revised network behavior.
| Annex | What it covers |
|---|---|
| B | SDL diagrams for call processing, including page input and roaming |
| E | Parameter tables for paging and message operations |
| F | ASN.1 definitions, error codes and I4 ROSE operations |
What are the key requirements of SIST ETS 300 133-3:1998/A1:1999?
The amendment mainly tightens character conversion, call acceptance, and the data carried in paging operations. It also adds or updates protocol elements so that the network can signal character set choice, legitimization, and specific error conditions.
Character conversion in 8.1.4 applies only to numeric and alphanumeric services, and only to the message part. Each PNC needs a conversion table for each supported access method, defined by the operator according to national requirements. For operators, this means character handling must be planned and implemented consistently across the network.
PNC-I, PNC-H and PNC-T character-set handling depends on whether the operators have an agreement. If they do, PNC-I can work with the selected character set and check that the receiver supports it; if they do not, PNC-I forwards the message transparently and PNC-H performs the conversion. This matters because the message must reach the receiver in a character set it can display.
Unsupported characters are rejected. If the calling party enters a character that is not mapped by the operator to the ERMES character set, that character is refused and the caller is notified. This is important for user input validation and for avoiding corrupted paging messages.
Low network status blocks call acceptance in Clauses 7.1.2.2, 7.1.2.7 and 7.1.3.8. If information about low network status has been received, calls cannot be accepted. In practice, the network must use its status information as a gating condition before accepting paging traffic.
Option 22 and subclause 9.2.5.23 add call input with a specific character set. The operation is used when no SSs are requested and the calling party uses a specific character set. The message data includes address codes, authentication, message type, and the character-set code; the positive response includes a positive acknowledgement and may include a system message. This gives network software a defined way to carry the user’s chosen alphabet end-to-end.
Message retrieval in 9.2.5.15 supports stored messages. A mobile subscriber can request retransmission or retrieval of stored messages, using message numbers or intervals, and choose retrieval or retransmit on the radio channel. That matters for message-store functions and for handling negative results consistently.
Annex E and Annex F add character-set-aware data fields and errors. The parameter tables now carry character-set information where needed, including receiver character-set lists and chosen character set values. The ASN.1 definitions also add error values such as low-network-status and diversion-already-activated, so systems can signal failures precisely.
What terms does SIST ETS 300 133-3:1998/A1:1999 define?
SIST ETS 300 133-3:1998/A1:1999 uses a set of paging-network terms and data elements that recur throughout the amendment.
- PNC-I - the paging network center on the incoming side of a call or page input, which can perform initial message handling and character conversion.
- PNC-H - the home network center, which can verify subscriber capability and may perform character conversion before forwarding a message.
- PNC-T - the terminating network center that transmits the message toward the receiver.
- MS - the mobile subscriber, which in this amendment is the party that can request message retrieval or initiate call input.
- AdC - the address code used for the mobile subscription or recipient address.
- GAdC - the group address code used when address lists are registered as a group.
- CS - the character-set code carried with a message when the ERMES character set is not used.
- low network status - a network-status condition that, once received, prevents call acceptance.
Who uses SIST ETS 300 133-3:1998/A1:1999?
SIST ETS 300 133-3:1998/A1:1999 is used by paging network operators, equipment suppliers, protocol developers and test labs working on ERMES systems. It is also relevant to quality and compliance teams checking that paging services handle character sets, call acceptance and stored-message operations in the prescribed way.
It is particularly useful for people configuring PNCs, receiver databases and messaging interfaces. The amendment also affects teams that define operator-specific conversion tables and legitimacy data for paging subscribers.
What changed in SIST ETS 300 133-3:1998/A1:1999 from the previous edition?
SIST ETS 300 133-3:1998/A1:1999 modifies ETS 300 133-3 (1992). The amendment adds ISO 646 as a reference, rewrites character conversion rules, blocks call acceptance after low network status, adds a service identification code for legitimization management, introduces call input with a specific character set, and updates the call-processing diagrams and ASN.1 structures.
It also expands the parameter sets in Annex E and Annex F to carry character-set information, receiver character-set lists, legitimization data and new error causes. For implementers, the practical result is a broader and more explicit protocol model for charset-aware paging.
Which standards are used with SIST ETS 300 133-3:1999/A1:1999?
The amendment names three external references or companion parts that support its technical content:
- ISO 646 (1991) - provides the 7-bit coded character set used for numeric message characters.
- ETS 300 133-2 - Annex B of that part provides the ERMES character table used for alphanumeric messages.
- ETS 300 133-4 - subclause 6.5.3 provides the procedure used to end transparent data messages.
What does the SIST ETS 300 133-3:1998/A1:1999 document contain?
SIST ETS 300 133-3:1998/A1:1999 contains revised call-processing diagrams, updated parameter tables and ASN.1 definitions, plus clause changes that redefine how paging networks handle character sets and related errors. The document shows SDL diagrams in Annex B for page input and roaming scenarios, which are used to design and validate network behavior.
Annex E gives the parameter sets for paging operations, including fields for character-set codes, receiver capabilities and legitimization-related data. Annex F gives the formal protocol structures, including the error enumeration and the SEQUENCE definitions used in I4 operations.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST ETS 300 133-3:1998/A1:1999 is a amendment published by the Slovenian Institute for Standardization (SIST). Its full title is "Paging Systems (PS); Enhanced Radio MEssage System (ERMES); Part 3: Network aspects". This standard covers: RE/RES-04003-3
RE/RES-04003-3
SIST ETS 300 133-3:1998/A1:1999 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/A1:1999 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-julij-1999
6LVWHPLRVHEQHJDNOLFD 36 (YURSVNLVLVWHP]DUDGLMVNRVSRURþDQMH (50(6
GHO 2PUHå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 - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 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 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
...