1、 ITU-T RECflNUF.32 95 D rib25L ObOBOBb 35b m INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES F.32 (1 0/95) TELEGRAM DESTINATION INDICATORS ITU-T Recommendation F.32 (Previously “CCITT Recommendation”) 1T
2、U-T RECMN*F.32 95 = 4862591 Ob014087 292 E FOREWORD The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (U). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommen- dations on them with a
3、 view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recom
4、mendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). ITU-T Recommendation F.32 was prepared by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 3rd of October 1995. NOTE In
5、 this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O ITU 1996 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or me
6、chanical, including photocopying and microfilm, without permission in writing from the ITU. ITU-T RECMN+F=32 95 W 4862593 Ob08088 129 W CONTENTS Page 1 Background and scope . 1 2 References and terminology . 1 3 Code structure 1 4 Allocation of telegram network codes 2 5 Particular combinations for
7、office codes 4 6 Allocation of office codes 4 7 Registration and publication . 4 Recommendation F.32 (10195) 1 ITU-T RECMN*F.32 75 4862593 0608087 Ob5 SUMMARY The operation of the ?Telegram Retransmission System?, described in Recommendation F.3 depends on the use of a standard format in telegrams.
8、The format contains routing and other operational information in a heading part. This includes a four-letter ?destination indicator?, which is one of the key elements used for routing a telegram at switching centres in the origin country, and in any transit country(ies). They are also used for routi
9、ng in the destination country. This Recommendation lays down the general principles applying to the selection of destination indicators, the allocation of the indicators? four letters, the application of analogous two- and four-letter codes for certain other purposes in operating the telegram servic
10、e, procedures for changing or adding to code allocations and the timely promulgation of the information on codes to Recognized Operating Agencies (ROAS). 11 Recommendation F.32 (10/95) - - ITU-T RECMNUF.32 95 4862591 Ob08090 887 Recommendation F.32 TELEGRAM DESTINATION INDICATORS (Geneva, 1995) 1 Ba
11、ckground and scope 1.1 The operation of the “Telegram Retransmission System”, described in Recommendation F.3 1, depends on the use of a standard format in telegrams. The format contains routing and other operational information in a heading part. This includes a four-letter “destination indicator”,
12、 which is one of the key elements used for routing a telegram at switching centres in the origin country, and in any transit country(ies). They are also used for routing in the destination country. Depending on the arrangements in individual centres, other elements used for automatic or manual routi
13、ng include the origin indicator, the outgoing or incoming channel indicator and the office of destination. These elements are also used to provide the basis for the billing and accounting processes. For this and other operational reasons, the “F.3 1” format or its component parts are used when handl
14、ing telegrams other than via the Telegram Retransmission System. Destination indicators have wide applicability. 1.2 This Recommendation lays down the general principles applying to the selection of destination indicators, the allocation of the indicators four letters, the application of analogous t
15、wo-and four-letter codes for certain other purposes in operating the telegram service, procedures for changing or adding to code allocations and the timely promulgation of the information on codes to Recognized Operating Agencies (ROAS). 2 References and terminology 2.1 service and their relation wi
16、th other codes used in the international public telegram and telex services are: The Recommendations relevant to the allocation of codes, the use of destination indicators in the telegram - ITU-T Recommendation C.2 (1993). Collection and publication of oficial service information. - CCITT Recommenda
17、tion F.3 1 (1988), Telegram retransmission system. - CCITT Recommendation F.68 (1988), Establishment of the automatic intercontinental telex network. - CCITT Recommendation F.69 (1988), Plan for telex destination codes. 2.2 service. The service itself and the main operational arrangements are define
18、d in Recommendation F.1. Various technical and operational arrangements may be used to support the international public telegram 2.3 the two-letter parts of destination indicators are “Telegram Network Code” and “Office Code” (see clause 3). In accordance with the provisions in Recommendation F.31,
19、the terms used in this Recommendation to identify 3 Code structure 3.1 Each destination indicator consists of four-letters taken from the Latin alphabet. 3.2 (see Recommendation F.69). The two letters characterize either: The first two letters (the “telegram network code”) fulfil a function analogou
20、s to a telex destination code a) a particular destination country or geographical area; or b) a particular network in a destination country or geographical area, for cases where the origin office wishes to route a telegram to a particular network; or Recommendation F.32 (10/95) 1 c) where the office
21、 of origin has no special preference for the destination network, an “unrouted” combination, which allows a gateway or transit centre to select the actual network to be used, e.g. on a quota basis. 3.3 network identification code, this code should be the same as its telegram network code described i
22、n 3.2 above. In accordance with Recommendation F.68, where a ROA has been, or is to be, allocated a two-letter telex 3.4 The third and fourth letters (the “office code”) characterize, principally for routing purposes, either: a) the destination office shown in the address part of the telegram; or b)
23、 a centre that serves a number of destination offices in a region or district; or c) an “all others” indicator to cover those destinations not covered by a) and b) above; or d) certain applications related to the operation of the telegram service (see clause 4 below); or e) a single code covering al
24、l destinations except for the applications in d) above. 3.5 differs in at least two letters from any other indicator. As far as possible the whole of the four-letter destination indicators should be selected such that any indicator 3.6 The same four-letter code structure is used for destination and
25、origin indicators (see Recommendation F.31). 4 Allocation of telegram network codes 4.1 Any administration of an ROA wishing to bring a new network into service (or to change the designation of an existing network, country or geographical area) should apply to the Director of the TSB for the assignm
26、ent of a two- letter network code (see 3.2 above). In its request it may indicate the available code preferred, but see 3.3 above. 4.2 In all cases such requests (and any request for a change in the telegram network code of an existing network) shall be referred to the Chairman of ITU-T Study Group
27、1 for guidance on technical and operational issues, taking account of possible future requirements. 4.3 It is the responsibility of the TSB: - to carry out the necessary discussions with the applicant Administration and/or its ROA; and - to ensure that the Chairman of Study Group 1 is satisfied that
28、 any technical and operational requirements have been covered before allocation of a new telegram network code. 4.4 Discontinued telegram network codes shall not be reallocated for a period of at least two years. 4.5 Figure 1 illustrates the procedure specific to telegram network codes. 4.6 code for
29、 each ROAS network see 3.2 c) above. Where there are competing ROAS, an “unrouted” telegram network code must be allocated in addition to a 4.7 country. The destination indicator XQXQ is reserved for use in emergency broadcast messages (see clause 10E.31). The letter X should not be allocated as the
30、 first letter of a telegram network code for any specific destination 4.8 organizations in the preamble line of telegrams pursuant to Recommendation F. 1, A218. The procedure in 4.1 to 4.5 above shall also be applied for two-letter indicators used to designate international 2 Recommendation F.32 (10
31、/95) ITU-T RECflN*F.32 95 M 48b259L Ob08092 b5T r StudyGrcup 1 Chairmana) reverts to TSB with guidance on resolution of any identifled Operational or technical issues TSB/Applicant discussions H Request received in TSB for allocatidchange of code) I- Details passed by TSB to Study Group 1 Chaimana)
32、I Study Group 1 Chaimana) seeks guidance from Study Group 1 expert group) on propasalb) t I I I Normally 15 working Study Group 1 Chairmana) replies accordingly to the TSB IA YB No I TSB informs applicant and To1 04920-95dO I Relevant Study Group 1 expert group to inform the next meeting of Study Gr
33、oup 1 (Working Party) on work announces code allocation in Operational Bulletin I TSB to publish updated list of allocated and spare codes periodically in Operational Bulletin a) Or Chairmans delegated representative. b, To be done in consultation with expert group nominated by Study Group 1 for suc
34、h tasks. FIGURE 1E.32 Scheme for the allocation and publication of telegram network codes Recommendation F.32 (10195) 3 - ITU-T RECflNtF.32 95 48b259L Ob08093 596 m 5 Particular combinations for office codes 5.1 The second letter of any “all others” office code should be X. 5.2 Where a single office
35、 code is used to cover all destinations in a given network, it should be XX. 5.3 The combinations SV, MV, XQ and YQ are reserved for the segregation of particular types of messages (service advices, service notes) at gateway centres or major offices. (See 2.2.3F.31 and 3.5F.31 on the use of such com
36、binations in origin and destination indicators for return service advices.) 5.4 reaction in a connected telegram retransmission centre. (See clause 10F.3 1 .) The combination ZZ is strictly reserved for automatic service notes, which are designed to trigger an automatic 5.5 between connected switchi
37、ng centres). The combinations RQ, BQ, XQ, if used at all, should only be associated with service notes (i.e. messages 6 Allocation of offce codes 6.1 The office codes (i.e. the third and fourth letters in a destination indicator) allocated for each network code should be kept to a minimum number in
38、each network. (This does not exclude the use of additional unregistered office codes for national purposes.) Keeping the number of office codes to a minimum eases the task of operators in distant countries who have to select the appropriate code in their outgoing telegrams. A very short list is part
39、icularly helpful for offices handling a small number of outgoing international telegrams. Where the destination network is capable of carrying out the national routing without an office code (e.g. by analysing the address part of the telegram as well as the pilot line), a single office code (XX) is
40、preferred. 6.2 Administrations should coordinate the requirements of their individual ROAS, where applicable, for any changes to the office codes within a given country or geographical area. Any proposed changes should respect the guidelines in clause 5 above. 6.3 TSB of the proposed changes. The Ad
41、ministration, or a ROA if so authorized by the Administration, should then advise the Director of the 6.4 proposed changes to these shall be handled in the same manner as for office codes within destination indicators. Where ROAS use special office codes within their origin indicators in accordance
42、with 2.2.3F.31, any 6.5 operational issues when proposed changes to office codes: The Director of the TSB should consult the Chairman of Study Group 1 for guidance on any technical and - do not conform with the requirements in this Recommendation; andor - propose a major re-arrangement of a networks
43、 office codes; or - may impinge on possible future requirements andor known or anticipated developments in other networks. 7 Registration and publication 7.1 Ail additions and changes to destination codes that are accepted in accordance with clauses 4 and 6 above shall be entered into a register mai
44、ntained by the TSB. All special origin indicators (6.4 above) used internationally shall also be included. 7.2 The fact that changes are being made in a given network or networks shall also be published in the next available Operation Bulletin, together with dates of entry into effect. The Operation
45、al Bulletin shall also give the details of any new or changed telegram network codes. However, the Administration or ROA(s) initiating the changes shall circulate details of the approved changes to office codes to ali ROAS needing this operational information. 4 Recommendation F.32 (10/95) ITU-T REC
46、MN*F-32 95 4862573 Ob0804 422 7.3 In accordance with Recommendation F.69 (1994), a list of telex network identification codes is published periodically in the Operational Bulletin. For convenience, the two-letter telegram network codes corresponding to one- letter telex network identification codes
47、should be appended to this list. 7.4 The date of entry into effect of changes (additions and deletions) in destination indicators should normally be the first day of the third month following publication. However a shorter delay, but normally not less than a month, may be acceptable in the case of c
48、hanges in office codes. 7.5 The TSB shall publish a list of the current four-letter destination indicators in the Operational Bulletin at approximately three-yearly intervals, or as the number of changes may justify it. The current list on the TSBs database should also be readily accessible to Administrations and ROAS. Recommendation F.32 (10/95) 5 ITU-T RECMN*F-32 75 4862591 Ob08095 3b7 = Printed in Switzerland Geneva, 1996
