1、Standard ECMA-232 December 1995Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chPrivate Integrated ServicesNetwork (PISN) -Profile Standard for theConnection of Radio PagingEquipment (RPE) to a PISN
2、.Standard ECMA-232 December 1995Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW - Ecma-232.doc - 25.08.98 09:28Private Integrated ServicesNetwork (PISN) -Profile Standard for theConnection of Ra
3、dio PagingEquipment (RPE) to a PISN.Brief HistoryThis Standard is one of a series of ECMA standards defining services and signalling protocols applicable to Private IntegratedServices Networks (PISNs). The series uses the ISDN concepts as developed by the ITU-T (formerly CCITT) and is alsowithin the
4、 framework of standards for open system interconnection as defined by ISO.This Standard specifies the functional profile for interconnecting Radio Paging Equipment (RPE) with PISNs to permitinteroperability between equipment from different vendors.The Standard is based upon the practical experience
5、of ECMA member companies and the results of their active andcontinuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and various international and national standardizationbodies. It represents a pragmatic and widely based consensus.This ECMA Standard is envisaged for contribution to ETSI fo
6、r adoption as an ETS.This ECMA Standard has been adopted by the ECMA General Assembly of December 1995.List of corrected errata for ECMA-23221 August 1998SummaryFollowing is a summary of the errors detected and corrected in Standard ECMA-232, Private Integrated ServicesNetwork - Profile Standard for
7、 the Connection of Radio Paging Equipment (RPE) to a PISN.Clause 2G01 Spell out “implementation conformance statement” before using the acronym.Corrected:A system conforms to this Standard if it correctly performs all the mandatory capabilities defined in the requirementlist (RL) and the profile spe
8、cific implementation conformance statement (ICS). Note that more capabilities may bemandatory than in the base standards (annex A and B).Original:A system conforms to this Standard if it correctly performs all the mandatory capabilities defined in the requirementlist (RL) and the profile specific IC
9、S. Note that more capabilities may be mandatory than in the base standards (annexA and B).Clause 6, penultimate paragraphG01 therefore is misspelledCorrected:In the case of the S reference point the meet-me destination numbers are implementation dependant and the definitionof them is therefore outsi
10、de the scope of this Standard.Original:In the case of the S reference point the meet-me destination numbers are implementation dependant and the definitionof them is therefor outside the scope of this Standard.Clause 7.2.3, Note 1G01 replace “S-bus” by “interface at the S reference point”Corrected:I
11、f in addition to the RPE other compatible terminals (e.g. telephones) are connected to the same interface at the Sreference point, care should be taken that all the equipment can evaluate called party number information to preventincorrect answers.Original:If in addition to the RPE other compatible
12、terminals (e.g. telephones) are connected to the same S-bus, care should betaken that all the equipment can evaluate called party number information to prevent incorrect answers.Clause 7.2.5.1G01 replace “64 kbit data” by “unrestricted digital information”, and improve wordingCorrected:Information t
13、ransfer capability shall be speech or 3.1 kHz audio. In addition unrestricted digital information may beused.Original:Information transfer capability may only be speech, 3.1 kHz audio or unrestricted 64 kbit data.Clause B.3.4G01 wrong reference, replace “B.3.1” by “B.3.2”Corrected:This section is on
14、ly applicable if the answer to RPEA1 in clause B.3.2 was Yes.Original:This section is only applicable if the answer to RPEA1 in clause B.3.1 was Yes.Clause B.3.5G01 wrong reference, replace “B.3.1” by “B.3.2”Corrected:This section is only applicable if the answer to RPEA2 or RPEA3 in clause B.3.2 wa
15、s Yes.Original:This section is only applicable if the answer to RPEA2 or RPEA3 in clause B.3.1 was Yes.Clause B.4.4G01 wrong reference, replace “B.4.1” by “B.4.2”Corrected:This section is only applicable if the answer to RPEE1 in clause B.4.2 was Yes.Original:This section is only applicable if the a
16、nswer to RPEE1 in clause B.4.1 was Yes.Clause B.4.5G01 wrong reference, replace “B.4.1” by “B.4.2”Corrected:This section is only applicable if the answer to RPEE2 or RPEE3 in clause B.4.2 was Yes.Original:This section is only applicable if the answer to RPEE2 or RPEE3 in clause B.4.1 was Yes.- i -Ta
17、ble of contentsPage1 Scope 12 Conformance 13 References 14 Definitions 24.1 External definitions 24.2 Meet-me answer 24.3 Meet-me (answer) destination 24.4 Meet-me service 34.5 Paging (call) 34.6 Pager 34.7 Pager number 34.8 Speech paging 35 List of acronyms 36 Addressing 47 Profile for the S refere
18、nce point 47.1 Paging services 47.1.1 Paging call with or without a speech connection to the pager 47.1.2 Diversion to paging 47.1.3 Paging with meet-me answer 57.2 Basic access interface (S0) 57.2.1 Layer 1 requirements 57.2.2 Layer 2 requirements 57.2.3 Layer 3 requirements for basic call procedur
19、es 57.2.4 Supplementary services requirements 67.2.5 Layer 3 coding requirements 68 Profile for the Q reference point 78.1 Paging services 78.1.1 Paging call with or without a speech connection to the pager 78.1.2 Diversion to paging 78.1.3 Paging with meet-me answer 78.2 Applicable scenarios 88.2.1
20、 Layer 1 requirements 88.2.2 Layer 2 requirements 88.2.3 Channel numbering 8- ii -8.3 Layer 3 requirements for basic call procedures 88.3.1 Messages 88.3.2 Information element coding 98.4 Supplementary services and ANF requirements 98.4.1 Generic Procedures 98.4.2 Name supplementary services (CNIP,
21、CONP) 98.4.3 Call Diversion (CFU, CFNR, CFB) 98.4.4 Call Transfer (CT) 98.4.5 Unsuccessful call supplementary services (CCBS, CO, CI, DNDO) 98.4.6 Call waiting (CW) 98.4.7 Do Not Disturb (DND) 98.4.8 Call Interception (CINT) 9Annex A - Profile Requirements List (RL) 11Annex B - Profile specific ICS
22、proforma 15Annex C - RPE/PINX services 25Annex D - Information flow diagrams, examples 271ScopeThis Profile Standard specifies the combination of base standards, together with the selection of appropriate optionsand parameter values, necessary to interface a Radio Paging Equipment, RPE, to a PINX.Th
23、e standard provides for two methods of connection of an RPE to a PINX. With the first method, the RPE isconnected in a similar manner to a TE connected at the S reference point using an ISDN basic access interface at layer1. With the second method the RPE is connected in a similar manner to another
24、PINX connected at the C referencepoint using an ISDN basic access interface or a primary rate interface at layer 1. In this case static mapping isemployed between the C reference point and the Q reference point. The C, Q and S reference points are defined inISO/IEC 11579-1.This Standard states requi
25、rements upon implementations to achieve interoperability between equipment on each side ofthe RPE/PINX interface.NOTEImplementation of one or more profiles from this Standard does not preclude a manufacturer from offering othermeans of interconnection.2 ConformanceA system conforms to this Standard
26、if it correctly performs all the mandatory capabilities defined in the requirementlist (RL) and the profile specific implementation conformance statement (ICS). Note that more capabilities may bemandatory than in the base standards (annex A and B).3 ReferencesECMA-221 Private Telecommunication Netwo
27、rk (PTN) - Inter-Exchange Signalling Protocol - CallInterception Additional Network Feature (QSIG-CINT) (1995)ISO/IEC 9646-7 Information technology - Open Systems Interconnection - Conformance testingmethodology and framework - Part 7: Implementation conformance statements -Requirements and guidance
28、 on ICS and ICS proformas (1995)ISO/IEC 11571 Information technology - Telecommunications and information exchange betweensystems - Numbering and sub-addressing in private integrated services network (1994)ISO/IEC 11572 Information technology - Telecommunications and information exchange betweensyst
29、ems - Private Integrated Services Network - Circuit-mode bearer services - Inter-exchange signalling procedures and protocol (1994)ISO/IEC 11579-1 Information technology - Telecommunications and information exchange betweensystems - Private Integrated Services Network - Part 1: Reference configurati
30、on forPISN Exchanges (PINX) (1994)ISO/IEC 11582 Information technology - Telecommunications and information exchange betweensystems - Private Integrated Services Network - Generic functional protocol for thesupport of supplementary services - Inter-exchange signalling procedures and protocol(1995)IS
31、O/IEC 13868 Information technology - Telecommunications and information exchange betweensystems - Private Integrated Services Network - Inter-exchange signalling protocol -Name identification supplementary services (1995)ISO/IEC 13869 Information technology - Telecommunications and information excha
32、nge betweensystems - Private Integrated Services Network - Inter-exchange signalling protocol - Calltransfer supplementary service (1995)ISO/IEC 13873 Information technology - Telecommunications and information exchange betweensystems - Private Integrated Services Network - Inter-exchange signalling
33、 protocol - Calldiversion supplementary services (1995)- 2 -ISO/IEC 13874 Information technology - Telecommunications and information exchange betweensystems - Private Integrated Services Network - Inter-exchange signalling protocol -Path replacement additional network feature (1995)ETS 300 011 Inte
34、grated Services Digital Network (ISDN); Primary rate user-network interface; Layer1 specification and test principles (1992)ETS 300 012 Integrated Services Digital Network (ISDN); Basic user-network interface; Layer 1specification and test principles (1992)ETS 300 192 Private Telecommunication Netwo
35、rk (PTN); Signalling protocol at the S-referencepoint; Circuit mode basic services (1992)ETS 300 362 Private Telecommunication Network (PTN); Inter-exchange signalling protocol; Calloffer supplementary service (1994)ETS 300 364 Private Telecommunication Network (PTN); Inter-exchange signalling proto
36、col; Do notdisturb and do not disturb override supplementary services (1994)ETS 300 366 Private Telecommunication Network (PTN); Inter-exchange signalling protocol; Callcompletion supplementary services (1994)ETS 300 402-1 Integrated Services Digital Network (ISDN); Digital Subscriber Signalling Sys
37、tem No.one (DSS1) protocol; Data link layer; Part 1: General aspects (1995)ETS 300 402-2 Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No.one (DSS1) protocol; Data link layer; Part 2: General protocol specification (1995)prETS 300 402-4 Integrated Services Digital
38、Network (ISDN); Digital Subscriber Signalling System No.one (DSS1) protocol; Data link layer; Part 4: Protocol Implementation ConformanceStatement (PICS) proforma specification for the general protocolETS 300 426 Private Telecommunication Network (PTN); Inter-exchange signalling protocol; Callintrus
39、ion supplementary service (1995)ITU-T Rec. Q.850 Usage of cause and location in the Digital Subscriber Signalling System No.1 and theSignalling System No.7 ISDN User Part (1993)ESPA rec. 4.4.8 Proposal for standard supplementary services for interworking of Private ISDN andRadio Paging (1992)4 Defin
40、itionsFor the purpose of this standard the following definitions apply.4.1 External definitionsThis Standard uses the following terms defined in other documents: Additional Network Feature (ANF) (ISO/IEC 11582) Call, Basic call (ISO/IEC 11582) Private Integrated Services Network Exchange (PINX) (ISO
41、/IEC 11579) Transferring PINX (ISO/IEC 13869) Transit PINX (ISO/IEC 11572) Terminating PINX (ISO/IEC 11572)4.2 Meet-me answerA procedure for the paged user, after he has been paged, to answer a call (i.e. to get a speech connection with thecalling user) by calling a specific destination in the PISN.
42、4.3 Meet-me (answer) destinationA PISN-number which is called in a meet-me answer.- 3 -4.4 Meet-me serviceA service in a PISN to allow a called user to be connected to a calling user by making a meet-me answer.4.5 Paging (call)A basic call where the destination is a pager rather than a terminal.4.6
43、PagerA pocket receiver in a paging system.4.7 Pager numberPISN-number which identifies a pager.4.8 Speech pagingA paging where a speech connection is established to the pager.5 List of acronymsANF Additional Network FeatureCD Call DeflectionCFB Call Forwarding on BusyCFNR Call Forwarding on No Reply
44、CFU Call Forwarding UnconditionalCI Call IntrusionCINT Call InterceptionCLIP Calling Line Identification PresentationCLIR Calling Line Identification RestrictionCNIP Calling Name Identification PresentationCO Call OfferCOLP Connected Line Identification PresentationCONP Connected Name Identification
45、 PresentationCT Call TransferCW Call WaitingDND Do Not DisturbDNDO DND OverrideICS Implementation Conformance StatementPICS Protocol ICSPINX Private Integrated Services Network ExchangePISN Private Integrated Services NetworkRL Requirements ListRPE Radio Paging EquipmentTE Terminal Equipment- 4 -6 A
46、ddressingAddressable entities are:G01 Pagers;G01 Meet-me answer destinations;G01 optionally the RPE fixed part.Pager numbers shall be part of the native numbering plan as defined in ISO/IEC 11571 and shall uniquely identify thepagers. All pager numbers shall be allocated to the RPE. For the S refere
47、nce point this means that all pager numberswill have to be assigned to the access where the RPE is connected. This results in an MSN arrangement. For the Qreference point this means that all paging calls are routed to the RPE in the same way as to another PINX.NOTEThis means that in general the same
48、 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 numberingplan and shall be allocated to the RPE. There could either be a fixed relationship between the pager number and themeet-me answer
49、number, or a dynamic allocation of the meet-me answer number on a per call basis. The relationshipbetween 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 definitionof 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 nativenumbering plan.7 Profile for the S reference pointAn RPE acts as a TE when connected to an interface at the
