SIST ETS 300 739 E1:2005

• Abstract:

  This Profile standard specifies the combination of base standards, together with the selection of appropriate options and parameter values, necessary to interface a Radio Paging Equipment, RPE to a PINX. The standard is applicable for connection of Radio Paging Equipment to a PINX.

• Status: Published
• Publication Date: 28-Feb-2005
• ICS: 33.040.35 - Telephone networks
• ICS: 33.050.20 - Paging equipment
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Mar-2005
• Due Date: 01-Mar-2005
• Completion Date: 01-Mar-2005
• Ref Project: ETSI ETS 300 739 ed.1 (1996-12) - Private Integrated Services Network (PISN); Profile Standard for the connection of Radio Paging Equipment (RPE) to a PISN

SIST ETS 300 739 E1:2005 is the Slovenian adoption of ETS 300 739 Edition 1, a profile standard for connecting Radio Paging Equipment (RPE) to a Private Integrated Services Network Exchange (PINX) in a Private Integrated Services Network (PISN). It specifies the combination of base standards, options and parameter values needed for the RPE-PINX interface so equipment from different vendors can interwork.

What does SIST ETS 300 739 E1:2005 specify?

SIST ETS 300 739 E1:2005 specifies how an RPE is connected to a PINX in a PISN, and it does this by selecting the relevant base standards and the required option values for that interface. The standard covers two connection methods: an RPE acting like a terminal at the S reference point, and an RPE acting like another PINX at the Q reference point.

The S reference point part covers the basic access interface only. The Q reference point part covers mapping onto basic access or primary rate access, and it applies to continuous bit stream scenarios.

The document is organized into clauses on scope, conformance, references, definitions, acronyms, addressing, the S reference point profile, and the Q reference point profile. It then adds normative annexes for requirement lists and ICS proformas, plus informative annexes for service examples and information flow diagrams.

Annex	What it covers
Annex A	Profile Requirements List for PINX and RPE implementations
Annex B	Profile specific ICS proforma for PINX and RPE implementations
Annex C	RPE/PINX services overview
Annex D	Information flow diagrams and examples

What are the key requirements of SIST ETS 300 739 E1:2005?

SIST ETS 300 739 E1:2005 requires implementations to follow the profile requirements in annex A and the profile-specific ICS in annex B in addition to the base standards. In practice, that means a supplier must state which profile options are supported and then build the interface so the chosen call and signalling behavior matches the profile.

Connection model and layer requirements

For the S reference point, an RPE acts like a terminal equipment (TE) on an ISDN basic access interface. Layer 1 shall comply with ETS 300 012, layer 2 shall conform to ETS 300 402-2, and the connection should be point-to-multipoint.

For the Q reference point, an RPE acts as a node in the PISN. Layer 1 shall comply with ETS 300 011 for primary rate or ETS 300 012 for basic access, and layer 2 shall conform to ETS 300 402-2 as modified for inter-exchange use.

In practice, this means the installer or designer must choose the correct physical interface and signalling profile for the network arrangement, not just the pager hardware.

Call setup, alerting and release behavior

For paging calls, the RPE receives a SETUP message with the full pager number in the Called party number information element. ALERTING indicates that the paged user has been alerted in a proper way, and CALL PROCEEDING is used when the RPE accepts the call but cannot alert within timer T303.

CONNECT is used only in specific cases such as speech paging, voice message operation, explicit acknowledgement, data calls with B-channel data, or when meet-me handling requires an active call state. DISCONNECT is normally used for a successful paging call with cause 16, "Normal call clearing", after a suitable delay so the calling user can hear the alerting indication.

In practice, these rules control what the call looks like to the PISN and to the calling party, which matters for user experience and for interoperability testing.

Addressing and numbering

Pager numbers shall be part of the native numbering plan and shall uniquely identify the pagers. All pager numbers shall be allocated to the RPE, and for the S reference point this leads to an MSN arrangement.

For the Q reference point, meet-me destinations also belong to the native numbering plan and are allocated to the RPE. The relationship between the pager number and the meet-me answer number is implementation dependent.

In practice, the numbering plan has to be planned carefully so pager calls route correctly and numbers do not clash with normal telephone use.

Paging services and supplementary services

The S reference point profile covers paging calls with or without speech, diversion to paging, and paging with meet-me answer. It also uses CLIP for the calling party number, COLP when a connected number is reported, diversion for calls to and from a pager, and optional Do Not Disturb (DND) support.

The Q reference point profile extends this with supplementary services and ANFs such as CNIP, CONP, CFU, CFNR, CFB, CT, CCBS, CO, CI, DNDO, CW, DND and CINT. Where meet-me service is implemented, call transfer is used to join the paging call with the meet-me answer call.

In practice, these clauses tell a supplier which service interactions the equipment has to handle, especially if the pager can also participate in call diversion or meet-me workflows.

Cause values and coding

The profile specifies which cause values the RPE shall use for conditions such as destination out of order, call rejected because information is missing, subscriber absent, user busy, no circuit/channel available, and resources unavailable. The bearer capability shall be speech, 3.1 kHz audio, or unrestricted digital information where applicable.

High layer compatibility and low layer compatibility may be ignored by the RPE. At the Q reference point, the Cause information element location field may be "User" or "Private network serving the remote user"; at the S reference point, it is set to "User".

In practice, this is what lets a network or tester interpret why a paging attempt failed and whether the failure is local, temporary, or due to missing information.

Conformance and implementation statements

Conformance is based on the mandatory capabilities in the requirements list and the profile-specific ICS. Annex B provides separate ICS proformas for PINX and RPE implementations, so suppliers can declare supported interfaces, supported standards and extra options.

In practice, this is the part that supports procurement, acceptance testing and interoperability checks.

What terms does SIST ETS 300 739 E1:2005 define?

• Private Integrated Services Network (PISN) - A private integrated services network that provides the framework for the paging connection profile.
• Private Integrated Services Network Exchange (PINX) - The exchange node in the PISN that the RPE connects to.
• Radio Paging Equipment (RPE) - The paging equipment connected to the PISN.
• pager - A pocket receiver in a paging system.
• meet-me answer - A procedure that lets a paged user call a specific destination to join the calling user.
• Calling Line Identification Presentation (CLIP) - The supplementary service used to deliver the calling party number to the RPE.
• Call Forwarding Unconditional (CFU) - A diversion service used when calls are forwarded directly to the pager.

Who uses SIST ETS 300 739 E1:2005?

SIST ETS 300 739 E1:2005 is used by suppliers of PISN equipment, suppliers of RPE, network integrators, and test laboratories. It is also relevant to quality managers and buyers who need to check whether a device supports the S reference point, the Q reference point, or both.

In practice, implementers use it to select the required signalling and numbering behavior, test engineers use it to build conformance tests, and purchasers use it to compare declared capability in the ICS proformas.

Which standards are used with SIST ETS 300 739 E1:2005?

• ISO/IEC 9646-7 - Gives the ICS and PICS conformance statement framework used by annexes A and B.
• ISO/IEC 11571 - Defines numbering and sub-addressing in the PISN, used for pager numbers and meet-me destinations.
• ISO/IEC 11572 - Gives inter-exchange signalling procedures for circuit-mode bearer services, used at the Q reference point.
• ISO/IEC 11579-1 - Defines the reference configuration for PINX exchanges.
• ISO/IEC 11582 - Gives the generic functional protocol for supplementary services and ANFs.
• ISO/IEC 13868 - Supports name identification supplementary services such as CNIP and CONP.
• ISO/IEC 13869 - Supports call transfer, used for meet-me service at the Q reference point.
• ISO/IEC 15054 - Supports call interception, referenced for CINT.
• ISO/IEC 13873 - Supports call diversion supplementary services.
• ETS 300 011 and ETS 300 012 - Define primary rate and basic user-network interface layer 1 requirements.
• ETS 300 192 - Provides signalling at the S reference point for circuit-mode basic services.
• ETS 300 362, ETS 300 364, ETS 300 366, ETS 300 426 - Support call offer, do not disturb, call completion and call intrusion related behavior.
• ETS 300 402-1, ETS 300 402-2, ETS 300 402-4 - Cover the DSS1 data link layer, services to layer 3, and the related PICS proforma.
• CCITT Q.850 - Defines cause and location usage for ISDN signalling.
• ESPA 4.4.8 - Gives additional background on interworking services between Private ISDN and radio paging.

What does the SIST ETS 300 739 E1:2005 document contain?

SIST ETS 300 739 E1:2005 contains the message procedures, numbering rules and signalling coding rules for paging calls over the S and Q reference points. It also contains the requirement lists that adjust the base-standard PICS tables for both PINX and RPE implementations.

Annex B contains the profile-specific ICS questionnaires that suppliers complete to declare support for interfaces, standards and options. Annex C summarizes paging service cases such as beep-only paging, display paging, speech paging, explicit acknowledgement and absent-status indication.

Annex D provides information flow diagrams for successful and unsuccessful paging examples, including cases with no speech connection, with speech connection or voice message, and with subscriber absence. These examples help readers and testers understand the expected call sequence in practice.

SLOVENSKI STANDARD
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,616WDQGDUGQLSURILO]DSULNOMXþLWHY
RSUHPHUDGLMVNHJDRVHEQHJDNOLFD53(QD3,61
Private Integrated Services Network (PISN); Profile Standard for the connection of Radio
Paging Equipment (RPE) to a PISN
Ta slovenski standard je istoveten z: ETS 300 739 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
33.050.20 Oprema za osebni klic Paging equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 739
TELECOMMUNICATION December 1996
STANDARD
Source: ETSI TC-ECMA Reference: DE/ECMA-00143
ICS: 35.120
Key words: Paging, PICS, PISN, PTN, PTNX, PINX
Private Integrated Services Network (PISN);
Profile Standard for the
connection of Radio Paging Equipment (RPE)
to a PISN
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: [e-mail]
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 1996. All rights reserved.

Page 2
ETS 300 739: December 1996
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 739: December 1996
Contents
Foreword .7
1 Scope .9
2 Conformance.9
3 References.9
4 Definitions.11
4.1 External definitions.11
4.2 Internal definitions.11
5 List of acronyms .11
6 Addressing .12
7 Profile for the S reference point .12
7.1 Paging services.12
7.1.1 Paging call with or without a speech connection to the pager.12
7.1.2 Diversion to paging.12
7.1.3 Paging with meet-me answer.13
7.2 Basic access interface (S0) .13
7.2.1 Layer 1 requirements .13
7.2.2 Layer 2 requirements .13
7.2.3 Layer 3 requirements for basic call procedures .13
7.2.3.1 SETUP.13
7.2.3.2 CALL PROCEEDING.13
7.2.3.3 ALERTING.14
7.2.3.4 CONNECT.14
7.2.3.5 DISCONNECT.14
7.2.3.6 RELEASE COMPLETE .14
7.2.4 Supplementary services requirements.14
7.2.4.1 Calling Line Identification Presentation (CLIP) .14
7.2.4.2 Connected Line Identification Presentation (COLP).14
7.2.4.3 Diversion.15
7.2.4.4 Do not disturb .15
7.2.5 Layer 3 coding requirements.15
7.2.5.1 Bearer capability .15
7.2.5.2 Called party number .15
7.2.5.3 Calling party number.15
7.2.5.4 Cause .15
7.2.5.5 High layer compatibility.15
7.2.5.6 Low layer compatibility.15
8 Profile for the Q reference point .15
8.1 Paging services.16
8.1.1 Paging call with or without a speech connection to the pager.16
8.1.2 Diversion to paging.16
8.1.3 Paging with meet-me answer.16
8.2 Applicable scenarios.16
8.2.1 Layer 1 requirements .16
8.2.2 Layer 2 requirements .16
8.2.3 Channel numbering.16
8.3 Layer 3 requirements for basic call procedures.16
8.3.1 Messages.17
8.3.1.1 SETUP.17

Page 4
ETS 300 739: December 1996
8.3.1.2 ALERTING . 17
8.3.1.3 CONNECT . 17
8.3.1.4 DISCONNECT . 17
8.3.2 Information element coding . 17
8.4 Supplementary services and ANF requirements. 17
8.4.1 Generic Procedures. 17
8.4.2 Name supplementary services (CNIP, CONP). 17
8.4.3 Call Diversion (CFU, CFNR, CFB). 18
8.4.4 Call Transfer (CT). 18
8.4.5 Unsuccessful call supplementary services (CCBS, CO, CI, DNDO). 18
8.4.6 Call waiting (CW). 18
8.4.7 Do Not Disturb (DND). 18
8.4.8 Call Interception (CINT). 18
Annex A (normative): Profile Requirements List (RL). 19
A.1 General. 19
A.2 Relationship between RL and corresponding PICS proformas . 19
A.3 Requirement List for PINX. 19
A.3.1 Tables for the physical layer. 19
A.3.1.1 S reference point . 19
A.3.1.2 Q reference point. 19
A.3.2 Tables for the link layer: D-channel. 19
A.3.2.1 S reference point . 19
A.3.2.2 Q reference point. 19
A.3.3 Tables for the network layer. 20
A.3.3.1 S reference point . 20
A.3.3.2 Q reference point. 20
A.3.4 Tables for Supplementary Services and ANFs . 20
A.4 Requirement List for RPE. 20
A.4.1 Tables for the physical layer. 20
A.4.1.1 S reference point . 20
A.4.1.2 Q reference point. 20
A.4.2 Tables for the link layer: D-channel. 21
A.4.2.1 S reference point . 21
A.4.2.2 Q reference point. 21
A.4.3 Tables for the network layer. 21
A.4.3.1 S reference point . 21
A.4.3.2 Q reference point. 21
A.4.4 Tables for Supplementary Services and ANFs . 21
Annex B (normative): Profile specific ICS proforma . 22
B.1 Introduction. 22
B.2 Instruction for completing the ICS proforma. 22
B.2.1 General structure of the ICS proforma. 22
B.2.2 Additional Information. 22
B.2.3 Exception Information . 23
B.3 ICS proforma for PINX implementation . 23
B.3.1 Implementation Identification . 23
B.3.2 Supported interfaces for RPE connection. 23
B.3.3 Supported standards for RPE connection. 24
B.3.4 Requirements for the S reference point . 24
B.3.4.1 Layer 3 requirements in addition to ETS 300 192 . 24
B.3.4.2 Additional items . 25
B.3.5 Requirements for the Q reference point. 25
B.3.5.1 Layer 3 requirements in addition to ISO/IEC 11572 . 25
B.3.5.2 Additional questions. 26

Page 5
ETS 300 739: December 1996
B.4 ICS proforma for RPE implementation.26
B.4.1 Implementation Identification .26
B.4.2 Supported interfaces for PINX connection.26
B.4.3 Supported standards for PINX connection .27
B.4.4 Requirements for the S reference point.27
B.4.4.1 Layer 3 requirements in addition to ETS 300 192 .27
B.4.4.2 Additional items .28
B.4.5 Requirements for the Q reference point .28
B.4.5.1 Layer 3 requirements in addition to ISO/IEC 11572.28
B.4.5.2 Additional questions .28
Annex C (informative): RPE/PINX services.29
Annex D (informative): Information flow diagrams, examples.30
D.1 Successful call to pager, no speech connection .30
D.2 Successful call to pager, speech connection or voice message.31
D.3 Unsuccessful call to pager due to absence.32
D.4 Unsuccessful call to pager due to absence. Voice message implemented .32
History.33

Page 6
ETS 300 739: December 1996
Blank page
Page 7
ETS 300 739: December 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the European Computer
Manufacturers Association (ECMA) on behalf of its members and those of the European
Telecommunications Standard Institute (ETSI).
This ETS is one of a series of ECMA standards defining services and signalling protocols applicable to
Private Integrated Services Networks (PISNs). The series uses the ISDN concepts as developed by the
ITU-T (formerly CCITT) and is also within the framework of standards for open system interconnection as
defined by ISO.
This ETS specifies the functional profile for interconnecting Radio Paging Equipment (RPE) with PISNs to
permit interoperability between equipment from different vendors.
This ETS is based upon the practical experience of ECMA member companies and the results of their
active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and various international
and national standardization bodies. It represents a pragmatic and widely based consensus.
Transposition dates
Date of adoption 6 December 1996
Date of latest announcement of this ETS (doa): 31 March 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 September 1997
Date of withdrawal of any conflicting National Standard (dow): 30 September 1997

Page 8
ETS 300 739: December 1996
Blank page
Page 9
ETS 300 739: December 1996
1 Scope
This Profile Standard specifies the combination of base standards, together with the selection of
appropriate options and parameter values, necessary to interface a Radio Paging Equipment (RPE) to a
Private Integrated Services Network Exchange (PINX).
The standard provides for two methods of connection of an RPE to a PINX. With the first method, the
RPE is connected in a similar manner to a TE connected at the S reference point using an ISDN basic
access interface at layer 1. With the second method the RPE is connected in a similar manner to another
PINX connected at the C reference point using an ISDN basic access interface or a primary rate interface
at layer 1. In this case static mapping is employed between the C reference point and the Q reference
point. The C, Q and S reference points are defined in ISO/IEC 11579-1 [4].
This Standard states requirements upon implementations to achieve interoperability between equipment
on each side of the RPE/PINX interface.
NOTE: Implementation of one or more profiles from this Standard does not preclude a
manufacturer from offering other means of interconnection.
2 Conformance
A system conforms to this Standard if it correctly performs all the mandatory capabilities defined in the
requirement list (RL) and the profile specific implementation conformance statement (ICS). Note that more
capabilities may be mandatory than in the base standards (annex A and B).
3 References
[1] ISO/IEC 9646-7 (1995): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation conformance statements - Requirements and guidance on ICS
and ICS proformas".
[2] ISO/IEC 11571 (1994): "Information technology - Telecommunications and
information exchange between systems - Numbering and sub-addressing in
private integrated services network".
[3] ISO/IEC 11572 (1994): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services Network -
Circuit-mode bearer services - Inter-exchange signalling procedures and
protocol".
[4] ISO/IEC 11579-1 (1994): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services Network -
Part 1: Reference configuration for PISN Exchanges (PINX)".
[5] ISO/IEC 11582 (1995): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services Network -
Generic functional protocol for the support of supplementary services -
Inter-exchange signalling procedures and protocol".
[6] ISO/IEC 13868 (1995): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services Network -
Inter-exchange signalling protocol - Name identification supplementary
services".
[7] ISO/IEC 13869 (1995): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services Network -
Inter-exchange signalling protocol - Call transfer supplementary service".

Page 10
ETS 300 739: December 1996
[8] ISO/IEC 15054 (1996): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services Network -
Inter-Exchange Signalling Protocol - Call Interception Additional Network
Feature".
[9] ISO/IEC 13873 (1995): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services Network -
Inter-exchange signalling protocol - Call diversion supplementary services".
[10] ISO/IEC 13874 (1995): "Information technology - Telecommunications and
information exchange between systems - Private Integrated Services Network -
Inter-exchange signalling protocol - Path replacement additional network
feature".
[11] ETS 300 011 (1992): "Integrated Services Digital Network (ISDN); Primary rate
user-network interface; Layer 1 specification and test principles".
[12] ETS 300 012 (1992): "Integrated Services Digital Network (ISDN); Basic user-
network interface; Layer 1 specification and test principles".
[13] ETS 300 192 (1992): "Private Telecommunication Network (PTN); Signalling
protocol at the S-reference point; Circuit mode basic services".
[14] ETS 300 362 (1994): "Private Telecommunication Network (PTN);
Inter-exchange signalling protocol; Call offer supplementary service".
[15] ETS 300 364 (1994): "Private Telecommunication Network (PTN);
Inter-exchange signalling protocol; Do not disturb and do not disturb override
supplementary services".
[16] ETS 300 366 (1994): "Private Telecommunication Network (PTN);
Inter-exchange signalling protocol; Call completion supplementary services".
[17] ETS 300 402-1 (1995): "Integrated Services Digital Network (ISDN); Digital
Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 1:
General aspects".
[18] ETS 300 402-2 (1995): "Integrated Services Digital Network (ISDN); Digital
Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 2:
General protocol specification".
[19] ETS 300 402-4 (1996): "Integrated Services Digital Network (ISDN); Digital
Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 4:
Protocol Implementation Conformance Statement (PICS) proforma specification
for the general protocol".
[20] ETS 300 426 (1995): "Private Telecommunication Network (PTN);
Inter-exchange signalling protocol; Call intrusion supplementary service".
[21] CCITT Q.850 (1993): "Usage of cause and location in the Digital Subscriber
Signalling System No.1 and the Signalling System No.7 ISDN User Part".
[22] ESPA 4.4.8 (1992): "Proposal for standard supplementary services for
interworking of Private ISDN and Radio Paging".

Page 11
ETS 300 739: December 1996
4 Definitions
4.1 External definitions
This standard uses the following terms defined in other documents:
Additional Network Feature (ANF): See ISO/IEC 11582 [5].
call, basic call: See ISO/IEC 11582 [5].
Private Integrated Services Network Exchange (PINX): See ISO/IEC 11579 [4].
transferring PINX: See ISO/IEC 13869 [7].
transit PINX: See ISO/IEC 11572 [3].
terminating PINX: See ISO/IEC 11572 [3].
4.2 Internal definitions
For the purpose of this standard, the following definitions apply:
meet-me answer: A procedure for the paged user, after he has been paged, to answer a call (i.e. to get a
speech connection with the calling user) by calling a specific destination in the PISN.
Meet-Me (ANSWER) destination: A PISN-number which is called in a meet-me answer.
meet-me service: A service in a PISN to allow a called user to be connected to a calling user by making a
meet-me answer.
Paging (CALL): A basic call where the destination is a pager rather than a terminal.
pager: A pocket receiver in a paging system.
pager number: PISN-number which identifies a pager.
speech paging: A paging where a speech connection is established to the pager.
5 List of acronyms
ANF Additional Network Feature
CD Call Deflection
CFB Call Forwarding on Busy
CFNR Call Forwarding on No Reply
CFU Call Forwarding Unconditional
CI Call Intrusion
CINT Call Interception
CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction
CNIP Calling Name Identification Presentation
CO Call Offer
COLP Connected Line Identification Presentation
CONP Connected Name Identification Presentation
CT Call Transfer
CW Call Waiting
DND Do Not Disturb
DNDO DND Override
ICS Implementation Conformance Statement
PICS Protocol ICS
PINX Private Integrated Services Network Exchange
PISN Private Integrated Services Network

Page 12
ETS 300 739: December 1996
RL Requirements List
RPE Radio Paging Equipment
TE Terminal Equipment
6 Addressing
Addressable entities are:
- Pagers;
- Meet-me answer destinations;
- optionally the RPE fixed part.
Pager numbers shall be part of the native numbering plan as defined in ISO/IEC 11571 [2] and shall
uniquely identify the pagers. All pager numbers shall be allocated to the RPE. For the S reference point
this means that all pager numbers will have to be assigned to the access where the RPE is connected.
This results in an MSN arrangement. For the Q reference point this means that all paging calls are routed
to the RPE in the same way as to another PINX.
NOTE: This means that in general the same number cannot be used for a telephone and a
pager.
In the case of the Q reference point all meet-me destinations shall have numbers which are part of the
native numbering plan and shall be allocated to the RPE. There could either be a fixed relationship
between the pager number and the meet-me answer number, or a dynamic allocation of the meet-me
answer number on a per call basis. The relationship between the pager number and meet-me answer
number is an RPE matter and implementation dependant.
In the case of the S reference point the meet-me destination numbers are implementation dependant and
the definition of them is therefore outside the scope of this Standard.
The RPE fixed part may, but need not, be an addressable entity. If it is, its number shall be part of the
native numbering plan.
7 Profile for the S reference point
An RPE acts as a TE when connected to an interface at the S reference point. Only the basic access
interface is covered by this Standard.
7.1 Paging services
The following paging services are covered:
- paging call with or without a speech connection to the pager, with or without explicit
acknowledgement from the pager;
- diversion to paging;
- paging with meet-me answer (implementation dependant).
7.1.1 Paging call with or without a speech connection to the pager
This type of call is a basic call where the called number identifies a pager rather than a terminal. The
paging calls are routed to the RPE by the PISN.
If CLIP is provided the paged user may call the calling user back. This is then a normal basic call and is
outside the scope of this Standard.
NOTE: The pager may send an explicit acknowledgement after receipt of the paging call.
7.1.2 Diversion to paging
Diversion to paging is a normal CFU or CFNR where the diverted-to-number is the number of a pager.
The paging calls are routed to the RPE by the PISN.

Page 13
ETS 300 739: December 1996
If CLIP is provided the paged user may call the calling user back. This is then a normal basic call and is
outside the scope of this Standard.
NOTE: The pager may send an explicit acknowledgement after receipt of the paging call.
7.1.3 Paging with meet-me answer
Support of the meet-me service is implementation dependant and may be implemented either in the PINX
or in the RPE. The meet-me service requires that the call originating from the meet-me answer is joined
with the original call. Procedures how this is achieved are outside the scope of this Standard.
If the PINX has implemented a meet-me service the RPE may be required to reach a certain call state and
remain there while waiting for meet-me answer, or the meet-me answer may be independent of the state
of the paging call. In the first case the meet-me implementation may either require the RPE to wait in the
call received state, or to send a CONNECT and wait in the active state.
If the meet-me service is implemented in the RPE then it has no impact on the PINX. The original call is
joined together locally in the RPE with the meet-me answer call.
NOTE 1: The RPE local meet-me service requires two B-channels per call. It may be improved
e.g. by using a call transfer procedure to re-route the two calls and thereby release the
RPE for new calls. The procedure for this is outside the scope of this Standard.
NOTE 2: The meet-me service may be limited to meet-me answer from the local PINX.
7.2 Basic access interface (S0)
7.2.1 Layer 1 requirements
The layer 1 of the interface shall comply with ETS 300 012 [12].
7.2.2 Layer 2 requirements
The layer 2 protocol shall conform to ETS 300 402-2 [18]. The services provided to layer 3 shall be as
specified in ETS 300 402-1 [17]. The connection should be point-to-multipoint.
7.2.3 Layer 3 requirements for basic call procedures
The procedures of ETS 300 192 [13] for call establishment at the destination interface shall apply with the
qualifications specified below. Only messages with a special meaning to this Standard are mentioned.
NOTE 1: If in addition to the RPE other compatible terminals (e.g. telephones) are connected to
the same interface at the S reference point, care should be taken that all the
equipment can evaluate called party number information to prevent incorrect answers.
NOTE 2: If the RPE has the capability to setup calls this may be done according to subclause
8.1 of ETS 300192 [12] "call establishment at the originating interface". This is outside
the scope of this Standard.
7.2.3.1 SETUP
A call to a pager is established by sending a SETUP message to the RPE. The full pager number shall be
sent in the Called party number information element in the SETUP message.
7.2.3.2 CALL PROCEEDING
CALL PROCEEDING shall be sent from the RPE as response to a SETUP if the RPE accepts the call but
is not able to send an ALERTING within expiry of timer T303.

Page 14
ETS 300 739: December 1996
7.2.3.3 ALERTING
ALERTING shall be sent from the RPE to the PINX as an indication to the calling party that the paged
user will be alerted in a proper way.
NOTE: The exact definition of "alerted in a proper way" is outside the scope of this Standard
and is implementation dependant. Examples of "not alerted in a proper way" may be:
pager in storage rack, no relevant display message (e.g. due to CLIR activated) or
undefined or erroneous pager number (i.e. in the RPE).
7.2.3.4 CONNECT
CONNECT shall be sent from the RPE in the following cases:
- the call is a speech paging and the speech channel is available;
- the call is a speech call and the RPE is equipped with a voice message facility to give information to
the calling user;
- the call is explicitly acknowledged by the pager. In this case it is recommended to provide a special
tone or announcement if possible;
- the call is a data call and the RPE has the poss
...