This specification this document to get an official version of this User Network Interface Specification

Transcription

1 This specification describes the situation of the Proximus network and services. It will be subject to modifications for corrections or when the network or the services will be modified. Please take into account that modifications can appear at any moment. Therefore, the reader is requested to check regularly with the most recent list of available specifications that the document in one's possession is the latest version. Proximus can't be held responsible for any damages due to the use of a version of this specification which is not included in the most recent list of available specifications (list always available with a request to the address mentioned in the underneath paragraph). 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 remarks concerning its accuracy, please send a mail to the following address Proximus.uni.spec@Proximus.be and your remark will be transmitted to the right Proximus department. The User Network Interface pecifications published via Internet are available for your information but have no official value. The only documents with an official value are printed on a specific paper. If you want to get an official version of this User Network Interface pecification, please order it by sending your request by mail to Proximus.uni.spec@Proximus.be

2 hort message communication for PTN/IDN Page A

3 Table of Contents DOCUMENT HITORY... 1 COPE... 2 REFERENCE... 4 GENERAL DECRIPTION ABBREVIATION AND TERMINOLOGY Abbreviations Terminology HORT MEAGE COMMUNICATION BETWEEN A FIXED NETWORK HORT MEAGE TERMINAL EQUIPMENT AND A HORT MEAGE ERVICE CENTRE... 8 APPENDIX A. CLARIFICATION ON TP-TL PARAMETER Page a

4 0. Document history Every update of this document results in a complete new version with new version number and release date. Versi on Date 25 APR EP MAR May EP 2007 Main or important changes since previous version First version Delivery Number adapted (chapter 5, point 5.5.1) Clarification of TP-TL parameters (Appendix A) Change in supported DC values (Appendix A) Change of M-C number to submit an M Page 1

5 1. cope This document gives technical information about the hort Message communication within the Proximus PTN/IDN network. (The document is applicable for the following Proximus digital exchanges and software packages) 12 - P7 and P8 EWD - V14B and V16B The document describes the technical specifications applicable to the user-network interface in order to send and receive hort Messages on the fixed network (PTN/IDN). Page 2

6 Page 3

7 2. References Whenever a date of edition is mentioned, the document with this date should be consulted. If no date is present, the latest version of this document should be consulted. ETI E V1.1.2 ETI E V1.1.1 ( ) ETI T V1.2.1 ( ) ETI ET ETI ET ETI EN V1.2.1 ETI EN V1.2.1 BGC_D_48_9809_30.01_E.pdf BGC_D_48_9807_30_02_E.pdf BGC_D_48_9811_30_09_E.pdf BGC_D_48_0105_30_01_E.pdf ETI T V7.2.0 ETI T V7.4.0 ETI EN V1.3.2 hort Message ervice for PTN/IDN; ervice Description Access and Terminals (AT); hort Message ervice (M) for PTN/IDN; hort Message Communication between a fixed network hort Message Terminal Equipment and a hort Message ervice Centre Access and Terminals (AT); hort Message ervice (M) for PTN/IDN; hort Message Communication between a fixed network hort Message Terminal Equipment and a hort Message ervice Centre (Corrections to E V1.1.1) ubscriber line protocol over the local loop for display (and related) services; Part 1: On-hook data transmission ubscriber line protocol over the local loop for display (and related) services; Part 2: Off-hook data transmission Access and Terminals (AT); Analogue access to the Public witched Telephone Network (PTN); Protocol over the local loop for display and related services; Terminal Equipment requirements; Part 1: On-hook data transmission Access and Terminals (AT); Analogue access to the Public witched Telephone Network (PTN); Protocol over the local loop for display and related services; Terminal Equipment requirements; Part 2: Off-hook data transmission BGC UNI spec: "Euro-IDN (Basic Call)" BGC UNI spec: "Analog ubscriber Line ignalling (Basic Call)" BGC UNI spec : "PTN: ubscriber line protocol for display (and related) services" BGC UNI spec: "IDN - D1 - Network Layer 3 - Calling Name Identification Presentation (CNIP)" Digital cellular telecommunications system (Phase 2+) (GM); Alphabets and language-specific information (GM version Release 1998) Digital cellular telecommunications system (Phase 2+) (GDM) ;Technical realization of the hort Message ervice (M) (GM version Release 1998) Integrated ervices Digital Network (IDN); Digital subscriber ignalling ystem No. one (D1) protocol; ignalling network layer for circuit -mode basic call control; Part 1:Protocol specification [ITU-T Recommendation Q.931 (1993), modified] Page 4

8 3. General description The hort Message ervice (M) is a service that allows text messages to be sent and received. The ETI E V1.1.2 gives an overall service description of the hort Message ervice (M) that can be provided via IDN and PTN accesses. The ETI E V1.1.1 specifies two protocols to provide the M service on the fixed network using a User Based olution (UB). This document specifies how the hort Message ervice will be realised in the Proximus network. The document will also describe the network provider options. Page 5

9 4. Abbreviations and terminology 4.1. Abbreviations PTN C LI CLIP APP CCB CM DLC DLL D1 DTMF FK GM ID N IUP PIN PL RL M M M-C M-TE M-TE-T M-TE- O 7 TL UB Public witched Telephone Network Calling Line Identity Calling Line Identification Presentation Application Completion of Calls to Busy ubscriber Connection Manager Data Link Control Data Link Layer Digital ubscriber ignalling No 1 Dual Tone Multi-Frequency Frequency hift Keying Global ystem for Mobile communication Integrated ervices Digital Network IDN User Part Personal Identification Number Presentation Layer Relay Layer hort Message(s) hort Message ervice hort Message ervice Center hort Message Terminal Equipment hort Message Terminal Equipment Terminated hort Message Terminal Equipment Originated ignalling ystem No. 7 Transfer Layer User Based olution 4.2. Terminology Following abbreviations are used in the tables : = 'upported'. That means that the Proximus network supports the feature in a uniform way for the whole network. U = 'Under study'. That means that : the Proximus network does not generally support the feature, but Proximus studies the implementation for a later phase; some Proximus switches may already support the feature. or the Proximus network does not support the feature in a uniform way for the whole network N = 'Not supported'. That means that the Proximus network does not support the Page 6

10 feature. GID = 'General Information and Definitions' Page 7

11 5. hort Message communication between a fixed network hort Message Terminal Equipment and a hort Message ervice Centre Normative reference: ETI E V1.1.1 The numbering is according to ETI E V1.1.1 ETI E V cope 2. References 3. Definitions and abbreviations 4. Functional description of UB 5. Protocol Overview 5.2 Interworking between M entities and PTN/IDN M ubmission from M-TE and M-C M Delivery from M- C to M-TE Belgaco m status GID GID GID GID GID GID Remarks Proximus's M-C will be connected to the network via a 7 network. The standard Proximus call control procedures according to the related access types will be used to set-up the voice calls between the Proximus M-C and M-TE. Please refer to the following Proximus UNI specs: "EURO-IDN (Basic Call)" and "Analog subscriber line signalling (Basic Call)" Proximus's M-C will support the complete subaddress range "0" -> "9". The default subaddress value, which will be used if no subaddress is specified by the sending user, is "0". The Proximus M-C will not provide the user the possibility to define password- or PINprotected M mailboxes within the M-C. In case of a M-TE with PTN access, the CLI is provided according to the Proximus UNI spec: "PTN: ubscriber line protocol for display (and related) services" In case of a M-TE with IDN access, the CLI is provided according to the Proximus UNI spec: "IDN - D1 - Network Layer 3 - Calling Name Identification Presentation (CNIP)" In a first phase, the Proximus M-C will set the Deliver Mode Identifier on "1". 5.3 Protocol architecture Physical layer Proximus will use the following value for the T10 timer: 2100 ms Page 8

12 5.3.2 Data Link Layer Overview Error handling Timer Page 9

13 5.3.3 Transfer Layer Overview Error handling Timer 5.4 Requirements to the Gateway 5.5 Requirements to the hort Message Terminal Equipment M-C Phone Numbers GID In a first phase the TP_tatus_Report_Indicator will not be used by the Proximus M-C to know when to send or to not send back a status report (delivered or not delivered). The value of the Transfer Layer timer: T_est = 20s The following Proximus M-C numbers will be used: A) "1976"; this number will be used to submit a M B) "01717"; this number will be used for the delivery of a M To submit an M, the M-TE will generate the following called party number: 1976<Calling ubaddress Digit>0 (ee clause 5.5.7) In case of an incoming M-C call (M delivery), the M-TE will see the following calling party number: 01717<Called ubaddress Digit><Deliver Mode Identifier Digit> Ringing uppression M Memory Full M-TE Busy M-TEs with PTN access, should suppress the first ringing cadence if the PTN transmits the caller ID information between the first and second ringing cadence. Based on the Deliver Mode Identifier value "1", which will be used by the Proximus M-C in a first phase, the M-TE will not call back the M- C after sufficient memory. It will be the Proximus M-C, which will call the M-TE again later. The M-TE may support off-hook CLIP but it is not a mandatory option. In case the M-TE supports off-hook CLIP, the M-TE will not generate a return call to the M- C later on (based on the DMI value "1" which will be used by the Proximus M-C in a first phase). Page 10

14 Please refer to the Proximus UNI specs, mentioned in point 5.2.2, for the way the CLI will be provided to the M-TE in the off-hook state. The Proximus M-C will not use CCB to complete the call as soon as possible. Page 11

15 5.5.5 Calling Line Identification Restriction (CLIR) Based on the 7 connection of the Proximus M-C, all the submit M calls will be accepted independent whether the CLIR is activated or not. By default the CLI of the M-TE-O will always be communicated to the M-TE-T Incoming calls Outgoing Calls 5.6 Extensions to the cited GM tandards 6. Protocol 2 U N Proximus will not use an appropriate hash code to know when the originating CLI may be communicated or not. In the initial phase, the DMI value of all incoming M calls will be set on "1". In the initial phase, the collect option will not be available. In a first phase the TP-FC value E0 will not be used by the Proximus M-C to know when it is allowed to transmit the CLI of the M-TE-0 to the M-TE-T. Page 12

16 Appendix A. Clarification on TP-TL parameters 1. M-DELIVER TP-MM TP-RP TP-UDHI TP-RI TP-OA TP-PID TP-DC TP-CT Not used Not used Not used Not used Used Type-of-Address field: Type-of-number = 000 (unknown) Numbering-plan-identification = 0001 (IDN/telephone numering plan) Not used F1 and 00 For the time zone, a fixed value will be set for Belgium (first bit set to 0) 2. M-DELIVER-REPORT TP-FC Behaviour of BGC's MC on following failure causes: A rejection of sms in case of: F 91 9F B0 A re-scheduling of sms in case of: Other failure causes 3. M-UBMIT TP-RD TP-VPF TP-RP TP-UDHI TP-RR TP - D A TP-PID Not interpreted by BGC's MC (no duplicate check is done) Not interpreted by BGC's MC Not interpreted by BGC's MC BGC's MC will reject M messages with TP-UD field containing a header Not interpreted by BGC's MC - BGC is using another notification request mechanism BGC's MC will only correctly interprete the TP-DA using the following Type-of-Address field: Type-of-number = 000 (unknown) Numbering-plan-identification = 0001 (IDN/telephone numering plan) BGC's MC will reject M messages with a Page 13

17 TP -D C TP-VP non-default TP-PID field BGC's MC will only accept correctly M messages with TP-DC field F1 and 00. Other TP-DC values are for further studies. Not interpreted by BGC's MC - BGC's MC is using its own validity mechanism 4. M-UBMIT-REPORT TP-FC The following failure causes are used by BGC's MC: 8F Unspecified PID 9F Unspecified DC B3 Invalid destination number B4 Invalid destination number (invalid number C1 C4 F0 FF format) Originating number barred Destination number barred Problems with BGC's MC Unspecified error 5. M-TATU-REPORT Not used 6. M - COMMAND Rejected - Not interpreted Page 14