Add files using upload-large-folder tool

marked/F/T-REC-F.10-198811-I_PDF-E/raw.md

@@ -0,0 +1,63 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**F.10**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# **OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES** ---
+
+## **CHARACTER ERROR RATE OBJECTIVE FOR TELEGRAPH COMMUNICATION USING 5 - UNIT START-STOP EQUIPMENT**
+
+**ITU-T Recommendation F.10**
+
+(Extract from the *Blue Book*)
+
+---
+
+## NOTES
+
+1 ITU-T Recommendation F.10 was published in Fascicle II.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## Recommendation F.10
+
+## CHARACTER ERROR RATE OBJECTIVE FOR TELEGRAPH COMMUNICATION USING 5-UNIT START-STOP EQUIPMENT
+
+The CCITT,
+
+*considering*
+
+- (a) that it would be useful to have a common standard for assessing the quality of telegraph communications,
+- (b) that the character error rate [1] of a telegraph communication would be suitable for this purpose;
+- (c) that a defined error rate objective should be established;
+- (d) that all forms of current wideband transmission techniques have intrinsic characteristics that make some errors economically unavoidable;
+- (e) that occasional bursts of errors occur (errors that are concentrated into a relatively short time interval, i.e. seconds),
+
+*unanimously declares*
+
+- (1) that the quality of service must be the same for telegraph communication in the public telegram service, the telex service and the leased circuit service;
+- (2) that the objective, irrespective of transmission media and intervening equipment, should be an error rate not greater than 3 in 100 000 alphabetic telegraph signals transmitted;
+- (3) that the error rate objective should have not less than a 95% probability;
+- (4) that, in the determination of error rate, measurements should be made for relatively long time periods, i.e. for at least several hours (see Note 1);
+- (5) that the effects of operator error rates (e.g. in the public telegram service) and of local ends and their terminations (e.g. teleprinters) should be excluded when determining the error rate.
+
+*Note 1* – The minimum time interval should include the busy hour and be of at least 12 hours duration.
+
+*Note 2* – The absolute value for the error rate objective requires further study.
+
+## Reference
+
+- [1] CCITT Definition: *Character error rate*, Vol. I, Fascicle I.3 (Terms and Definitions).

marked/F/T-REC-F.100-198811-I_PDF-E/raw.md

@@ -0,0 +1,83 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' in a bold, sans-serif font.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**F.100**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**OPERATIONS AND QUALITY OF SERVICE  
+TELEGRAPH SERVICES**
+
+---
+
+**SCHEDULED RADIOCOMMUNICATION  
+SERVICES**
+
+**ITU-T Recommendation F.100**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation F.100 was published in Fascicle II.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# **SCHEDULED RADIOCOMMUNICATION SERVICES**
+
+The CCITT,
+
+*unanimously declares*
+
+that the following rules should be adopted for the scheduled radiocommunication service.
+
+## **1 General**
+
+1.1 These rules are to be observed in the scheduled radiocommunication service in which radiocommunications are transmitted to one or more destinations.
+
+1.2 Only those senders and addressees who satisfy the provisions and conditions agreed between the Administrations concerned shall be allowed to participate in this service.
+
+## **2 Conditions of acceptance**
+
+2.1 Transmissions over the scheduled radiocommunication service must consist only of information and news relating to politics, commerce, etc., and must contain no communication of a private nature and no messages on behalf of third parties. They may include, however, brief indications as to how they should be passed on and to whom, provided that the time required to transmit them does not exceed 5 per cent of the total time taken to transmit the information or news, or, where appropriate, 5 per cent of the number of words of which the information or news consists.
+
+2.2 The sender shall communicate to the Administration of the country of emission the addresses of any intended recipient or recipients.
+
+2.3 The radiocommunications may be expressed either in plain language or in secret language, as decided by the Administrations of the countries of emission and of reception. In the absence of special arrangements between the Administrations concerned, the only languages authorized for plain language shall be French, one of the languages designated by the country of origin or one of the languages of one of the countries of reception. The Administrations of the countries of emission and of reception shall reserve to themselves the right to require the deposit of the codes used.
+
+2.4 The radio transmissions shall bear, as the address, an arbitrary word placed immediately before the text.
+
+## **3 Conditions of transmission**
+
+3.1 The Administration of the country of emission shall communicate to the other Administrations the address of any person residing in their territory for whom the radiocommunications are intended. It shall notify, in addition, in respect of each addressee, the date fixed for the first reception, the name of the emitting station and the address of the sender. The Administrations shall notify one another of any changes which occur in the number and the addresses of the senders and recipients.
+
+3.2 Where the services are operated by recognized private operating agencies, Administrations may authorize such agencies to communicate the notifications required under the preceding paragraph.
+
+3.3 Each Administration shall take, as far as is practicable, suitable measures to ensure that only the stations authorized for this special service of communication make use of the radiocommunications in question and then only of those intended for them. The provisions of the Convention relating to the secrecy of telecommunications shall apply to these radiocommunications.
+
+3.4 These radiocommunications shall be transmitted at fixed times.
+
+## **4 Conditions of reception**
+
+4.1 The Administration of the country of reception shall decide whether reception shall be permitted in its country. It may authorize the direct reception of such communications by the addressees designated by the sender or may itself make reception equipment available to the addressees to this end. It shall notify the Administration of the country of emission of the conditions under which reception takes place.
+
+## **5 Charging**
+
+5.1 The charge to be collected from the sender shall be fixed by the Administration of the country of emission.
+
+5.2 Apart from any charges levied for the establishment and working of private receiving stations or for the lease of receiver equipment, the addressees of these radiocommunications may be subjected by the Administration of their country to the payment of a receiver charge, the amount and method of assessment of which shall be decided on by that Administration.
+
+5.3 The charges for these radiocommunications shall not enter into the international accounts.

marked/F/T-REC-F.106-198811-I_PDF-E/raw.md

@@ -0,0 +1,69 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.106**
+
+# **OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES** ---
+
+## **OPERATIONAL PROVISIONS FOR PRIVATE PHOTOTELEGRAPH CALLS**
+
+**ITU-T Recommendation F.106**
+
+(Extract from the *Blue Book*)
+
+---
+
+### NOTES
+
+1 ITU-T Recommendation F.106 (new numbering of Rec. F.80 *bis*) was published in Fascicle II.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+### **OPERATIONAL PROVISIONS FOR PRIVATE PHOTOTELEGRAPH CALLS<sup>1)</sup>**
+
+#### **1 Field of application**
+
+1.1 These provisions apply to calls between private stations or between (outgoing) private stations and (incoming) public stations.
+
+1.2 The rules governing phototelegrams exchanged between private stations and public stations are embodied in Recommendations F.80 and D.80.
+
+#### **2 General**
+
+2.1 Private phototelegraph stations may be authorized by the Administration concerned to communicate with one another and to exchange phototelegrams with public stations.
+
+2.2 Administrations undertake to set up connections for such transmissions or to make suitable leased circuits available to private stations at their request.
+
+#### **3 Conditions of acceptance**
+
+3.1 Private stations may communicate with all (public and private) phototelegraph stations connected to the international phototelegraph network.
+
+3.2 Calls between private stations set up on the international phototelegraph network are allowed without any time limit. However, when telephone traffic is subjected to restrictions, the exchange of phototelegraph calls between private stations may be delayed or limited by agreement between the terminal centres concerned.
+
+3.3 Connections with a public station may be made available to a private station only during the business hours of the public phototelegraph office. However, the public station may not close until it has accepted all the phototelegrams that the private station has announced it wishes to hand in.
+
+3.4 The conditions under which booked phototelegraph calls are made available are specified in Recommendation F.82.
+
+#### **4 Charging**
+
+4.1 Charges for phototelegraph calls in continental and in intercontinental relations exchanged between private stations or from a private station to a public station are governed by Recommendation D.83.
+
+#### **5 Special services**
+
+5.1 The special urgent service shall be allowed in relations where it exists for telephone traffic.
+
+---
+
+<sup>1)</sup> See also Recommendation D.81.

marked/F/T-REC-F.107-198811-I_PDF-E/raw.md

@@ -0,0 +1,157 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.107**
+
+# **OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES** ---
+
+## **RULES FOR PHOTOTELEGRAPH CALLS ESTABLISHED OVER CIRCUITS NORMALLY USED FOR TELEPHONE TRAFFIC**
+
+**ITU-T Recommendation F.107**
+
+(Extract from the *Blue Book*)
+
+---
+
+## NOTES
+
+1 ITU-T Recommendation F.107 (new numbering of Rec. F.82) was published in Fascicle II.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## **RULES FOR PHOTOTELEGRAPH CALLS ESTABLISHED OVER CIRCUITS NORMALLY USED FOR TELEPHONE TRAFFIC**
+
+The CCITT,
+
+*considering*
+
+(a) that, in international phototelegraph communications, the occupation time of international telephone circuits often greatly exceeds the duration of the actual phototelegraph call;
+
+(b) that this drawback results *in part* from the inadequacy of existing rules on the setting up, supervision and clearing of phototelegraph calls over circuits normally used for telephone traffic, even if these circuits have been designated in advance as capable of carrying phototelegraph calls;
+
+(c) that phototelegraph communications between public stations on the one hand and public and private stations on the other, require close collaboration between the telegraph and telephone services of the various Administrations;
+
+(d) that, on the other hand, phototelegraph communications between private stations do not concern the telegraph services, although it is desirable for all phototelegraph calls between public stations, between public and private stations, and between private stations to be established in the same way,
+
+*unanimously declares*
+
+that the following rules should be applied to the provision of international phototelegraph connections.
+
+### **1 Field of application**
+
+1.1 The rules below define the operating procedure to be followed in the international phototelegraph service when phototelegraph calls are set up on circuits normally used for telephone traffic. They do not apply to phototelegraph transmissions on circuits in permanent use for that purpose or on leased circuits.
+
+1.2 These rules define the procedure applicable to the setting up, supervision and clearing of international phototelegraph calls:
+
+- between public stations;
+- between a public and a private station;
+- between private stations.
+
+### **2 General provisions**
+
+2.1 In relations where telephone circuits are used for both the phototelegraph service and the telephone service, the Administrations concerned shall assign by mutual agreement a certain number of circuits for phototelegraph transmissions, taking into account the usual requirements of both phototelegraphy and the telephone service.
+
+2.2 These circuits shall be specially marked at terminal exchanges and repeater stations with a view to the protection of the phototelegraph transmissions.
+
+2.3 The telephone circuits used for international phototelegraph transmissions shall, as far as practicable, be four-wire circuits. For phototelegraph transmission, they shall normally be disconnected from the switching equipment used for telephone calls. Interconnection of circuits for setting up phototelegraph calls should be four-wire-four-wire, as far as possible, both on the international and the national side.
+
+2.4 Administrations shall designate in each international phototelegraph terminal centre an authority responsible for the international phototelegraph calls. This authority is in a position to carry out, or cause to be carried out, all the operations necessary for the establishment of international phototelegraph calls. This authority shall henceforth be called the *international phototelegraph position (IPP)*.
+
+2.5 Administrations are recommended to centralize, as far as possible, in one place all the technical, operational and charging procedures necessary in an international centre when telephone circuits are used for phototelegraph calls.
+
+2.6 A booking for a phototelegraph call emanating from a public or private phototelegraph station is routed to (or arrives directly at) the IPP of the origin country responsible for setting up the international phototelegraph call that has been booked. This IPP then becomes the control IPP for establishing the call.
+
+### **3 Setting up, supervision and clearing of international phototelegraph calls**
+
+3.1 If the telephone service on the international circuit needed for setting up a phototelegraph call is operated with advance preparation, requests for phototelegraph calls rank in the order in which they are accepted among requests for telephone calls of the same category.
+
+3.2 In this case the control IPP advises the telephone office responsible for these circuits that a phototelegraph transmission is to take place. The control IPP agrees with the telephone service on the probable time at which the phototelegraph transmission will be taking place.
+
+3.3 The IPPs shall proceed as follows when setting up an international call.
+
+3.3.1 The control IPP transmits the following information as quickly as possible to the destination IPP:
+
+- designation of the transmitting station;
+- designation of the destination station;
+- probable time at which the phototelegraph call will take place;
+- where necessary, indication of the subscriber responsible for the charges; and, in addition:
+  - a) for calls requested by public stations:
+    - category of phototelegram to be transmitted;
+    - date and time of handing-in of the phototelegram.
+  - b) for calls requested by private stations:
+    - category of call requested;
+    - date and time of the request.
+
+3.3.2 The destination IPP shall take the necessary steps to advise immediately the destination phototelegraph station by telephone that a phototelegraph transmission is about to take place.
+
+3.3.3 If the called phototelegraph station is in a position to receive the phototelegraph call at the time fixed, the destination IPP informs the control IPP. At the said time, the two IPPs take the necessary steps, in agreement with the telephone service, to establish the call. Care must be taken to avoid interrupting telephone calls in progress.
+
+3.3.4 If the called phototelegraph station is not in a position to receive the call at the time fixed, the destination IPP fixes the time when the transmission is to take place, taking into account the information received from the receiving phototelegraph station. It then communicates the time fixed to the control IPP, which informs the calling station.
+
+3.3.5 The control IPP then takes the necessary measures, in agreement with the telephone service, to establish the phototelegraph call between the stations concerned at the agreed time.
+
+3.4 If the telephone service involved is demand service, the outgoing IPP shall take an available circuit for the phototelegraph call, after ensuring that telephone calls in progress are not interrupted; it shall use this circuit to call the incoming IPP.
+
+3.4.1 To establish a phototelegraph call, it shall transmit the data mentioned under § 3.3.1 above to the incoming IPP, except for the probable time of the phototelegraph call.
+
+3.4.2 The incoming IPP shall take the necessary steps to advise immediately the called phototelegraph station by telephone that a phototelegraph transmission is about to take place.
+
+3.4.3 If the called phototelegraph station is in a position to receive the phototelegraph call immediately, the two IPPs shall straight away establish the necessary connection.
+
+3.4.4 If the called phototelegraph station is not in a position to receive the call immediately, the destination IPP fixes the time when the transmission is to take place, taking into account the information received from the receiving phototelegraph station. It then communicates the time fixed to the control IPP, which informs the calling station. The two immediately clear the international telephone circuit.
+
+3.4.5 At the time agreed upon, the outgoing IPP shall take the necessary steps to establish the phototelegraph call.
+
+3.5 The control IPP shall note the time when the phototelegraph call starts. The beginning of the call is the moment when the connection with the called station is offered to the caller. When the international circuit is extended towards a national PP at the caller's end, the latter shall determine the beginning of the call and indicate it to the IPP in its country when the call is cleared (see § 3.7 below).
+
+- 3.6 The control IPP supervises the transmission in progress:
+- a) on the transmitting (go) path by means of a device enabling it to check, without risk of interference, that transmission is taking place;
+  - b) on the return path by means of a device enabling it to listen to service conversation from the phototelegraph receiving station.
+
+Intervention in the circuits should be avoided after the call has been established, unless such intervention has been requested by one of the IPPs or one of the phototelegraph stations connected.
+
+3.7 After consulting the receiving phototelegraph station, the calling phototelegraph station announces the end of the call either direct to its IPP, or, in the case of extension of an international circuit, to the national PP on which it depends.
+
+3.7.1 The latter must inform its IPP as quickly as possible, giving the time at which it received notice of the end of the call. The control IPP notes the end-of-transmission time and immediately communicates the notice announcing the end to the incoming IPP and, if necessary, to the transit IPP.
+
+3.7.2 The outgoing and incoming IPPs and any transit IPPs then take the necessary measures to restore the international circuit to the telephone service without delay.
+
+3.7.3 It is recommended that the called station should likewise announce the end of transmission so that the called station may be cleared more quickly.
+
+3.8 Unless the Administrations concerned decide to the contrary, the terminal IPPs do not come to an agreement on the chargeable duration, since this is determined by the control IPP.
+
+### **4 Special procedures for phototelegraph stations**
+
+4.1 For each phototelegram to be transmitted, the outgoing public station shall prepare a narrow tape comprising the preamble and address (and, if necessary, the signature and special service indications), unless these indications have been written on the phototelegram by the sender. This tape is transmitted with the phototelegram.
+
+4.2 As soon as the call is established, the interconnected phototelegraph stations proceed to adjust the equipment and to transmit, in accordance with the instructions of the receiving station, adopting the following order of operations:
+
+- a) if necessary, agreement on the index of cooperation and speed of transmission, then synchronization adjustment by means of the synchronization frequency;
+- b) adjustment of the white level;
+- c) adjustment of the black level;
+- d) phasing;
+- e) start;
+- f) transmission.
+
+4.3 If the phototelegram is passed to a public station by a private station, the public station shall ask the private station, if necessary, for information regarding establishment of the preamble and conditions of delivery to the addressee.
+
+### **5 Faulty transmissions**
+
+5.1 In the case of fault conditions, the control IPP shall immediately make arrangements to clear the fault or make another circuit available.
+
+5.2 When, after completion of the call, it is seen that the transmission was faulty, the receiving phototelegraph station shall inform its IPP. If it so desires, the receiving phototelegraph station can make a new booking with its IPP for a phototelegraph call, in the manner defined in § 2.6, with the sending station.
+
+5.3 If the phototelegraph station that receives the faulty picture and books a new call is a private station, its attention should be drawn to the fact that both calls will be chargeable if the faults in the picture are not due to the telephone or telegraph services.

marked/F/T-REC-F.108-198811-I_PDF-E/raw.md

@@ -0,0 +1,139 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**F.108**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# **OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES** ---
+
+## **OPERATING RULES FOR INTERNATIONAL PHOTOTELEGRAPH CALLS TO MULTIPLE DESTINATIONS**
+
+**ITU-T Recommendation F.108**
+
+(Extract from the *Blue Book*)
+
+---
+
+### NOTES
+
+- 1 ITU-T Recommendation F.108 (new numbering of Rec. F.85) was published in Fascicle II.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+- 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## **OPERATING RULES FOR INTERNATIONAL PHOTOTELEGRAPH CALLS TO MULTIPLE DESTINATIONS<sup>1)</sup>**
+
+The CCITT,
+
+*considering*
+
+(a) that it seems advisable to provide for rules to which the Administrations may refer in the case where they decide to allow calls enabling several phototelegraph stations in different countries to receive a transmission simultaneously;
+
+(b) that for multiple calls of this kind *international dissemination* (i.e., a distribution of the transmission to different countries) is necessary and possibly *national dissemination* in the incoming countries (i.e., to the various receiving stations belonging to the same national network);
+
+(c) that the participants in a multiple call may be both public stations and private stations (primarily press agencies);
+
+(d) that press agencies are anxious to transmit pictures to their customers (newspaper offices) directly – without retransmission;
+
+(e) that in the case of transmission by series, the agencies also wish to add or disconnect certain customers between two successive transmissions;
+
+(f) that operation over the international part of the collective connection should not be help up by modifications in an incoming country;
+
+*considering further*
+
+(g) that dissemination equipment can be set up either in the offices of Administrations or on the premises of private enterprises;
+
+(h) that press agencies operate private phototelegraph networks for their own requirements;
+
+(i) that private enterprises should be allowed under certain conditions to use their own equipment and networks to effect an additional dissemination service to their customers;
+
+*and recognizing*
+
+(j) that satisfactory transmission of phototelegrams to multiple destinations can be obtained only if all the countries concerned employ a uniform mode of operation;
+
+*unanimously declares the view*
+
+that multiple calls may be allowed in the international service to enable several phototelegraph stations in different countries to receive a transmission from a transmitting station simultaneously.
+
+The rules below define the procedure to be followed for multiple destination calls. The conditions for ordinary connections that are part of the collective link are governed by Recommendations F.82 and D.83.
+
+---
+
+<sup>1)</sup> See also Recommendation D.85.
+
+#### 1 Conditions of acceptance
+
+- 1.1 A multiple call may be requested for *primary dissemination* to various destination countries (international dissemination) and for *secondary dissemination* in the incoming countries (national dissemination). Simultaneously a national dissemination in the origin country can be combined with the international dissemination.
+- 1.2 Private stations of a receiving country participating in a multiple call (generally press agencies) are allowed to effect simultaneously with reception *further dissemination* to other private stations (generally newspaper offices).
+- 1.3 *Further dissemination* may be made either over a private network or over circuits of the public network made available by the Administration. In the latter case the further dissemination is allowed only within the country where the main receiving station is situated.
+- 1.4 The primary dissemination (including, where necessary, dissemination in the origin country) and the secondary dissemination must be effected by the Administration concerned.
+- 1.5 Any further dissemination over a private network shall in any case by the agency to which the network belongs. When circuits on the public network are used for dissemination to subordinate stations, the Administration concerned shall decide who should effect this further dissemination. For technical and operational reasons (see § 3.4 below), it is preferable that every further dissemination should be carried out by the agency using its own distribution equipment, provided that the equipment has been inspected and approved by the Administration.
+- 1.6 In any case, the installation at the main station shall be such that the operator using it can so control operations as to ensure that the subordinate stations cannot enter into communication with the transmitting station.
+
+#### 2 Setting up and constitution of a multiple call connection
+
+- 2.1 To obtain a multiple call, the transmitting station shall contact the international phototelegraph position (IPP) of its country and indicate, separately for each country, which phototelegraph stations are to receive the simultaneous transmission. Requests should be made as soon as possible, and in any case not later than two hours before the transmission is to take place, to enable the Administrations concerned to make arrangements to set up the call.
+- 2.2 The IPP of the origin country (see Figure 1/F.85, country A) shall inform the IPPs of the destination countries (countries B, C and D) giving the names of the called participants and the time at which the transmission is to take place (see § 5.2 below). So as not to surcharge the outgoing IPP, the incoming IPPs shall, at the same time, be asked to set up an international connection from their own end at the scheduled time.
+- 2.3 The incoming IPPs shall arrange, where necessary, to make facilities available for national dissemination to participants in the multiple call (see § 5.3 below). If only one participant is designated in an incoming country (C), the international circuit shall be switched directly to the receiving station in question.
+- 2.4 An intermediate connection with the international dissemination shall be requested in a transit country for destination countries to which it is not possible to connect directly for the dissemination from the origin country.
+- 2.5 The outgoing IPP is the control IPP for the multiple call (i.e., as far as the main receiving stations). If an intermediate connection with the international dissemination service has been set up, the transit IPP acts as the sub-control IPP for the part of the multiple call farther down the circuit.
+- 2.6 The control IPP notes the time when the multiple call begins and ends and the time and duration of any interruption or irregularity that may occur during transmission (for the purpose of calculating a refund). The start of the call is the moment at which the multiple connection has been placed at the disposal of the caller. The end of the call is the moment at which it is released by the transmitting station.
+- 2.7 On clearing the multiple call, the control IPP must notify the incoming IPPs concerned of the time at which the call began and ended (to ensure conformity with the national dissemination charges).
+
+![Diagram of phototelegraph transmissions to multiple destinations across four countries (A, B, C, D). It shows various stations including Transmitter, PTT, Public, Ag 1, Ag 2, Ag 3, Ag 4, Control station, and Sub-control station. A legend at the bottom defines symbols for primary, secondary, and further dissemination, as well as station types and network types.](f9a14fbfecbd7d059226cc93677d721b_img.jpg)
+
+The diagram illustrates a network of phototelegraph transmissions across four countries: Country A (Country of origin), Country B, Country C, and Country D. In Country A, a Transmitter connects to a PTT, which then connects to a Public network. From the Public network, the signal is disseminated to Ag 1 (press agency) and Ag 2. Ag 1 connects to a Control station, which in turn connects to a Sub-control station. Ag 2 connects to Ag 3 in Country C. Ag 3 connects to Ag 4 in Country D. Ag 4 connects to a Two-wire network, which then connects to a private network. The diagram uses various symbols to represent different types of connections and stations. A legend at the bottom defines these symbols:
+
+- Primary dissemination (solid square)
+- Secondary dissemination (open square)
+- Further dissemination (square with 'pp')
+- Chief receiving station (solid square)
+- Subordinate station (open square)
+- Public control station (square with 'P')
+- Press agency (Ag)
+- Private network (two parallel lines)
+
+Diagram of phototelegraph transmissions to multiple destinations across four countries (A, B, C, D). It shows various stations including Transmitter, PTT, Public, Ag 1, Ag 2, Ag 3, Ag 4, Control station, and Sub-control station. A legend at the bottom defines symbols for primary, secondary, and further dissemination, as well as station types and network types.
+
+FIGURE 1/F.108  
+Phototelegraph transmissions to multiple destinations
+
+#### 3 Extension of a multiple call
+
+3.1 When a private dissemination is added to the multiple call, the Administration shall merely make the required circuits available to the user. The individual calls shall then be set up successively to the calling station and shall be charged from the moment they are made available.
+
+3.2 The routing to public network circuits of a phototelegraph transmission received on a leased circuit (see Ag 1 of country D) is not allowed.
+
+3.3 Each press agency is the control station for the connections with its customers. In secondary private dissemination (see Ag 1 in country D) the second connecting station becomes the sub-control station for the part farther down the circuit.
+
+3.4 Should an Administration ensure itself (see § 1.5 above) the further dissemination on the public network (country D), two separate distribution panels (I and II, country D) will be necessary to connect the incoming circuit separately to the main station (Ag 4) and to its group of customers. To prevent subordinate stations from coming in on the international part of the collective call, the interconnection between I and II must be made by a one-way channel. The private enterprise (Ag 4) must direct the operations for which it is responsible in the two sections of the further dissemination facilities. Since the Administration is responsible for making its dissemination facilities available at the right time, and in view of the operational difficulties, in particular resulting from any change required in this part of the further dissemination, this mode of operation is not recommended.
+
+#### **4 Speech circuit**
+
+4.1 The speech circuit is a leased telephone circuit that provides a direct connection between the site of the transmitting equipment and the control IPP. This type of connection expedites the procedures preparatory to the call and enables rapid action to be taken to overcome any difficulties experienced during transmission. It also allows timely notice to be given of the end of the multiple call and, further, it is a suitable means for determining exactly the chargeable duration of the call.
+
+4.2 The speech circuit may, however, be replaced by a telephone connection set up from the transmitting station over the general telephone network.
+
+#### **5 General provisions**
+
+5.1 The setting up of a multiple call may involve unforeseen delays in practice, particularly when intermediate connection centres are used in the international dissemination sector. For these reasons, it is impossible for Administrations to give any guarantee that a multiple call will be made available at a specific time.
+
+5.2 It is for the control IPP to estimate the time required to make the requested call available. It must inform all IPPs (incoming and transit, if need be) of the time at which transmission is to take place.
+
+5.3 The incoming IPPs must do their utmost to respect the scheduled time for setting up the international connection to the control (or sub-control) IPP. To avoid any delay in commencing the simultaneous transmission because of arrangements to be made in an incoming country, the national extension (dissemination or simple prolongation) should in all cases be ready before the international circuit is made available.
+
+5.4 If a called station is unable to accept the call at the scheduled time, the incoming IPP shall so inform the control IPP. It will be for the station requesting the multiple call to decide whether transmission should be held up until the station is ready to receive, or whether the station should be brought in later or whether it should be excluded from the call. In any case, the call charge begins from the time the caller is informed of the position.
+
+5.5 When it is not possible to set up an international or national connection required for the multiple call within six minutes after the appointed time, the control IPP shall draw the caller's attention to the difficulties that have arisen. Whatever course the caller decides to take, the part of the call that has taken place will be charged for.
+
+5.6 When a request is made to extend to other relations a call (single or multiple) that has already begun, it must be regarded as a new call request. This call will be made available to the caller as soon as it is set up, and will be charged for separately from that time. The caller must indicate the time at which it should be combined with the original call.

marked/F/T-REC-F.11-199110-I_PDF-E/raw.md

@@ -0,0 +1,73 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**CCITT**
+
+**F.11**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+**TELEGRAPH AND MOBILE SERVICES  
+OPERATIONS AND QUALITY OF SERVICE**
+
+---
+
+**CONTINUED AVAILABILITY  
+OF TRADITIONAL SERVICES**
+
+**Recommendation F.11**
+
+---
+
+![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+Geneva, 1991
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.11 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 11th of October 1991.
+
+# --- CCITT NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
+
+## **Recommendation F.11**
+
+## **CONTINUED AVAILABILITY OF TRADITIONAL SERVICES**
+
+## **1 Background**
+
+1.1 At the World Administrative Telegraph and Telephone Conference (Melbourne, 1988) considerable attention was given to ensuring a wide availability of telecommunication services with effective interconnection and interoperability. This implied a continuing availability of basic or traditional services in many international relations, despite the evolution of new or more sophisticated services. Article 4 of the International Telecommunication Regulation (Melbourne, 1988) expects Administrations to provide “a wide range of international telecommunication services” including “at least a form of telecommunication which is reasonably accessible to the public, including those who may not be subscribers to a specific telecommunication service”.
+
+1.2 Resolution No. 6 of the same World Administrative Telegraph and Telephone Conference (Melbourne, 1988) called for provisions to be made “to allow, through available communication infrastructures, continued availability of traditional services so as to enable effective communications on a world-wide basis”. In particular this concerned services in “certain rural areas and developing countries” that “may need to rely on existing widely available services for a relatively long period of time”.
+
+## **2 Scope**
+
+2.1 Pursuant to the International Telecommunication Regulations (Melbourne, 1988), this Recommendation lays down general principles on the continued availability of traditional services to facilitate global interconnection and interoperability of telecommunication facilities, pending the establishment of new services and to ensure the efficiency, usefulness and availability to the public of international telecommunication services.
+
+2.2 It addresses the coordination needed between Administrations to achieve that continued availability. Members should take any necessary steps to ensure that coordination.
+
+2.3 Within the framework of this Recommendation, “traditional” services include the international public telegram, telex and telephone services.
+
+## **3 Services principles**
+
+3.1 Pursuant to Article 4 (4.3) of the International Telecommunication Regulations, and subject to national coordination arrangements, Administrations should provide and maintain at least a minimum quality of service corresponding to the relevant CCITT Recommendations for the various telecommunication services that they offer to the public.
+
+3.2 Administrations may take action to develop, to improve or to rationalize this range of services, including an integration of elements of various services (interworking or accessing arrangements) or the introduction of new services. Provisions to ensure adequate interconnection and interoperability may be incorporated into existing Recommendations or covered by new Recommendations. In particular the aspects of quality of service (as perceived by the user) and tariff principles need to be covered in the appropriate Recommendations.
+
+3.3 When the Administration (or Administrations) in one country suspends an international service definitively, either in all or certain relations, it shall make arrangements to ensure to the greatest extent practicable that the service may effectively continue to operate in some acceptable form for other Administrations, pending the establishment of the relevant new or replacement services in their countries. In this context, the continuing service is the end result perceived by the user. The actual telecommunication infrastructure used to furnish that end service may vary. For example in some instances and for agreed classes of traffic the telemessage and/or bureaufax services could be considered to provide an adequate replacement for an international public telegram service.
+
+3.4 In principle, such replacement services or interworking arrangements should not unduly burden Administrations that may reasonably be considered to rely on the continued availability of the relevant traditional service. Consequently, the necessary changes in the technical facilities and in the operational procedures (including accounting) should be arranged to have minimum impact on Administrations needing to retain the traditional service.

marked/F/T-REC-F.111-199103-I_PDF-E/raw.md

@@ -0,0 +1,89 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**CCITT**
+
+**F.111**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+**TELEGRAPH AND MOBILE SERVICE  
+OPERATIONS AND QUALITY OF SERVICE**
+
+---
+
+**PRINCIPLES OF SERVICE FOR  
+MOBILE SYSTEMS**
+
+**Recommendation F.111**
+
+---
+
+![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+Geneva, 1991
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.111 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 11 of March 1991.
+
+## --- CCITT NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
+
+# **PRINCIPLES OF SERVICE FOR MOBILE SYSTEMS**
+
+## **1 Scope**
+
+1.1 This Recommendation defines the principles applicable to international public correspondence service provided by mobile systems connected to the international telecommunication (fixed) networks. This Recommendation applies to aeronautical, land and maritime mobile-satellite and terrestrial systems.
+
+## **2 Introduction**
+
+2.1 There is an increased availability of mobile telecommunication systems on an international, regional and national basis. International mobile satellite systems offer telephone, data and telex services to aeronautical, land and maritime mobile users. Regional and national cellular systems, both analogue and digital, are in operation or at an advanced planning stage. Users of these mobile systems expect to be connected to the international telecommunications networks and be able to obtain international services available to fixed network customers. In order to ensure that both fixed and mobile user needs are met, principles of service for both satellite and terrestrial mobile systems when interworking with the international telecommunication networks are presented in this Recommendation.
+
+## **3 Services**
+
+3.1 The services offered by mobile systems (e.g. voice, data, telex) when interworking with the international telecommunication networks should, as far as practicable, be similar to those offered on fixed networks.
+
+## **4 Operation**
+
+4.1 When interworking between the mobile system and the fixed network the operational procedures for mobile system users should, wherever possible, be the same as for fixed networks. The same tones, announcements, service codes and signals, etc., used in the fixed network should be recognized and where appropriate returned by the mobile system.
+
+4.2 Any numbering plan for a national mobile system normally is part of the relevant national numbering plan of the country in which it is resident.
+
+4.3 For international mobile systems the numbering plan should either be derived from the national numbering plan of the participating countries or follow the international numbering plan applicable for the services to be provided.
+
+4.4 There should be mechanisms in place to cater for the needs of any call recording, billing and international accounting functions that might be required.
+
+## **5 Service between mobile systems**
+
+5.1 There should be no restrictions to establishing international calls between mobile terminals in different mobile systems via the relevant fixed network(s). For example, a user of a land mobile cellular terminal should be able to make an international telephone call to a mobile satellite terminal using the established international routing methods and procedures.
+
+## **6 Quality of service**
+
+6.1 The quality of service (e.g. bit error rate for data) of a mobile system should be such that the service experienced by the mobile user should be, where practical, similar to that of a user of a fixed network service.
+
+## **7 Service limitations**
+
+7.1 It is recognized that because of various reasons that mobile systems may not provide all the same services to their users as provided to users of the fixed telecommunication networks. Any limitation on service imposed by the mobile system on its users should, as far as practicable, not adversely affect the quality of service provided to fixed network users when the systems are interconnected.
+
+## **8 Special mobile services**
+
+8.1 It is recognized that mobile systems often provide services other than the conveyance of public correspondence. Mobile services may involve special services, e.g. priority and/or preemption treatment for safety of life messages, navigation, etc.
+
+8.2 Facilities for such special services are not necessarily available within the fixed networks. Where necessary Administrations should make any arrangements for the provision of these services (e.g. dedicated circuits), which is then a national matter outside the scope of CCITT Recommendations.
+
+8.3 CCITT Recommendations cover the effects of such special services on calls to/from the fixed networks.

marked/F/T-REC-F.112-198811-I_PDF-E/raw.md

@@ -0,0 +1,57 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**F.112**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**OPERATIONS AND QUALITY OF SERVICE**
+
+**MOBILE SERVICE**
+
+---
+
+**QUALITY OBJECTIVES FOR 50-BAUD  
+START - STOP TELEGRAPH TRANSMISSION  
+IN THE MARITIME MOBILE-SATELLITE  
+SERVICE**
+
+**ITU-T Recommendation F.112**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation F.112 was published in Fascicle II.4 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## **Recommendation F.112**
+
+# **QUALITY OBJECTIVES FOR 50-BAUD START-STOP TELEGRAPH TRANSMISSION IN THE MARITIME MOBILE-SATELLITE SERVICE**
+
+The CCITT,
+
+*considering*
+
+- (a) that proper interworking of this telegraph transmission with the international telegraph services must be ensured;
+- (b) CCITT Recommendation F.10 concerning character error rate for telegraph communications,
+
+*unanimously recommends*
+
+that, for the coast-earth station-to-mobile terminal and mobile terminal-to-coast-earth station links, sufficient margin should be included to overcome adverse propagation conditions. The objective should be that propagation conditions should not contribute any character errors for at least 95% of all calls with mobile terminals within the satellite service area. With the exception of blockage effects, propagation conditions should not contribute more than 8 errors in 100 000 characters with a 99% confidence level for mobile terminals at the edge of the service area.
+
+*Note* - This Recommendation corresponds to CCIR Recommendation 552.

marked/F/T-REC-F.113-199208-I_PDF-E/raw.md

@@ -0,0 +1,170 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**CCITT**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+**F.113**
+
+(08/92)
+
+**TELEGRAPH AND MOBILE SERVICES  
+OPERATIONS AND QUALITY OF SERVICE**
+
+---
+
+**SERVICE PROVISIONS FOR  
+AERONAUTICAL PASSENGER  
+COMMUNICATIONS SUPPORTED  
+BY MOBILE-SATELLITE SYSTEMS**
+
+**Recommendation F.113**
+
+---
+
+![CCITT logo: A globe with the letters CCITT.](84a1d09fb489061482111515543b60dc_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+Geneva, 1992
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.113 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992.
+
+## --- CCITT NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency.
+
+# **SERVICE PROVISIONS FOR AERONAUTICAL PASSENGER COMMUNICATIONS SUPPORTED BY MOBILE-SATELLITE SYSTEMS**
+
+(1992)
+
+## **1 Introduction**
+
+### **1.1 Scope**
+
+1.1.1 This Recommendation makes provision for the operational and Quality of Service requirements for both air-to-ground and ground-to-air aeronautical passenger communications mobile-satellite services. This Recommendation follows the principles laid down in Recommendation F.111.
+
+1.1.2 Operation in the AMS(R)S<sup>1)</sup> band must meet the standards established by the International Civil Aviation Organization (ICAO). This includes the technical specifications, preemptive and priority functions, as defined in ICAO Annex 10, Aeronautical Telecommunications.
+
+1.1.3 This Recommendation only covers aeronautical passenger communications. Other service and operational provisions are not covered by this Recommendation.
+
+1.1.4 Aeronautical passengers communications (APC), a form of communications, unrelated to safety and regularity of flight or the aircraft operating agency, which is at the disposal of the passenger and crew of an aircraft in flight status (see Note) on a controlled basis subject to flight safety requirements. Aeronautical passenger communications is one form of public correspondence.
+
+*Note* – An aircraft may be considered to be in flight status, while on the ground waiting for departure, while taxiing for take-off, while flying, while taxiing following landing, and while waiting for passengers to leave the aircraft.
+
+## **2 System description**
+
+2.1 An aeronautical mobile-satellite system provides two-way voice and data communication with aircraft operating within the field-of-view of a satellite.
+
+An aeronautical mobile-satellite system comprises of three basic elements:
+
+- *Aircraft earth stations (AES)* – Transmitting and receiving stations located on the aircraft capable of communicating with the satellite and interfacing with terminals within the aircraft.
+- *Aeronautical ground earth stations (GES)* – Fixed terrestrial transmitting and receiving stations communicating with the satellite and interfacing with terrestrial public and private telecommunication networks. For the purpose of this Recommendation the acronym GES will be used to denote an aeronautical ground earth station to avoid confusion over identical acronyms, although it is recognized that *Radio Regulation 77* defines this as an aeronautical earth station (see Note).
+
+*Note* – Fixed terrestrial transmitting and receiving stations jointly providing a combination of maritime, land and aeronautical mobile services are commonly referred to as land earth stations (LES) in the INMARSAT system.
+
+- *Satellite* – Providing communication between AESs and GESs.
+
+---
+
+<sup>1)</sup> AMS(R)S Aeronautical mobile-satellite (route) service.
+
+2.2 The system may support:
+
+- i) aeronautical passenger communications (APC);
+- ii) aeronautical administrative communications (AAC);
+- iii) aeronautical operational control (AOC) communications; and
+- iv) air traffic services (ATS) communications.
+
+2.3 Terrestrial networks that may be interconnected with aeronautical mobile satellite systems are:
+
+- public telephone, telex, packet switched and circuit switched data networks;
+- dedicated private networks for aeronautical telecommunication services.
+
+## 3 Service description
+
+3.1 Aeronautical passenger communications support the following services:
+
+- telephone;
+- telex;
+- packet switched data transmission;
+- circuit switched data transmission;
+- facsimile.
+
+Administrations may provide one or more of these services.
+
+## 4 Air-to-ground calls
+
+4.1 *General*
+
+4.1.1 Fully automatic service operation should be employed, where practicable, for all services.
+
+4.1.2 The AES and the GES provide preemptive and priority functions for the control of air-to-ground calls, in accordance with the International Civil Aviation Organization (ICAO) standards and recommended practices and the ITU Radio Regulations.
+
+4.1.3 Provision shall be made for the collection of information relevant to billing and international accounting functions.
+
+4.1.4 When a credit card system is employed, the relevant details of the credit card must also be recorded for validity check purposes.
+
+4.1.5 Procedures for call establishment should be in accordance with CCITT Recommendations, e.g. Recommendations E.216, F.126 and X.350 are applicable in respect to the INMARSAT-aeronautical system.
+
+4.2 *Telephone service*
+
+4.2.1 The service requirements and interworking procedures with the telephone service as defined in Recommendation E.105, are for further study.
+
+4.3 *Telex service*
+
+4.3.1 The service requirements and interworking procedures with the telex service as defined in Recommendation F.60, are for further study.
+
+### 4.4 *Data transmission services*
+
+#### 4.4.1 *Packet switched data transmission services*
+
+The service attributes, facilities, numbering and selection procedures are for further study.
+
+#### 4.4.2 *Circuit switched data transmission services*
+
+The service attributes, facilities, numbering and selection procedures are for further study.
+
+## **5 Ground-to-air calls**
+
+### 5.1 *General*
+
+5.1.1 The unique aircraft number identification is standardized by ICAO. A unique AES mobile number based upon this aircraft identification number should be used regardless of the types of service provided, on the radio link between the ground and aircraft.
+
+5.1.2 The AES and GES provide preemptive and priority functions for the control of ground-to-air calls, in accordance with ICAO standards and recommended practices and the ITU Radio Regulations.
+
+5.1.3 Numbering plans and call selection procedures should be in accordance with CCITT Recommendations, e.g. Recommendations E.215, F.125 and X.121, applicable to the INMARSAT-aeronautical system.
+
+5.1.4 Non-automatic operation for ground-to-air communication is for further study.
+
+### 5.2 *Telephone service*
+
+5.2.1 The service requirements are for further study.
+
+### 5.3 *Telex service*
+
+5.3.1 The service requirements are for further study.
+
+### 5.4 *Data transmission services*
+
+#### 5.4.1 *Packet switched data transmission services*
+
+5.4.1.1 The service requirements are for further study.
+
+#### 5.4.2 *Circuit switched data transmission services*
+
+5.4.2.1 The service requirements are for further study.

marked/F/T-REC-F.115-199502-I_PDF-E/raw.md

@@ -0,0 +1,388 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**F.115**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+(02/95)
+
+**OPERATIONS AND QUALITY OF SERVICE  
+MOBILE SERVICE**
+
+---
+
+**SERVICE OBJECTIVES AND PRINCIPLES  
+FOR FUTURE PUBLIC LAND MOBILE  
+TELECOMMUNICATION SYSTEMS**
+
+**ITU-T Recommendation F.115**
+
+(Previously "CCITT Recommendation")
+
+---
+
+# FOREWORD
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations 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.115 was prepared by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 21st February 1995.
+
+# --- NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+|                                                                | <i>Page</i> |
+|----------------------------------------------------------------|-------------|
+| 1 Introduction .....                                           | 1           |
+| 2 Scope .....                                                  | 1           |
+| 3 References .....                                             | 1           |
+| 3.1 CCITT and ITU-T Recommendations .....                      | 1           |
+| 3.2 ITU-R Recommendations .....                                | 2           |
+| 4 Definitions .....                                            | 2           |
+| 5 Service principles .....                                     | 3           |
+| 6 Overall service objectives .....                             | 4           |
+| 7 Service requirements .....                                   | 4           |
+| 7.1 General service requirements .....                         | 4           |
+| 7.2 General access requirements .....                          | 4           |
+| 7.3 Numbering considerations .....                             | 5           |
+| 8 Services supported .....                                     | 5           |
+| 8.1 Introduction .....                                         | 5           |
+| 8.2 Common FPLMTS services .....                               | 5           |
+| 8.3 FPLMTS specific services .....                             | 5           |
+| 9 Quality of Service .....                                     | 5           |
+| 9.1 General .....                                              | 6           |
+| 9.2 Speech quality .....                                       | 6           |
+| 9.3 Traffic engineering aspects .....                          | 7           |
+| Appendix I – Recommendations relevant to common services ..... | 7           |
+
+# **SUMMARY**
+
+The introduction of third generation digital mobile systems known as FPLMTS, which are scheduled to start service around the year 2000 subject to market considerations, will result in mobile communication becoming available to mass markets for the purpose of global communication. This Recommendation defines the service objectives and principles for FPLMTS which will enable the development of FPLMTS into the future. These objectives and principles are produced to aid the intercommunication of services provided over both FPLMTS and the fixed telecommunication network and to provide guidance for further development of FPLMTS.
+
+# **SERVICE OBJECTIVES AND PRINCIPLES FOR FUTURE PUBLIC LAND MOBILE TELECOMMUNICATION SYSTEMS**
+
+*(Geneva, 1994)*
+
+# **1 Introduction**
+
+**1.1** Future Public Land Mobile Telecommunication Systems (FPLMTS) will provide access, by means of one or more radio links, to a range of telecommunication services which are specific to mobile users and to telecommunication services supported by the fixed telecommunication network. FPLMTS are third generation mobile systems which may be terrestrial or satellite based and are scheduled to start service around the year 2000 subject to market considerations. They may be utilized as stand alone mobile systems or as part of the fixed network. The frequency bands 1885-2025 and 2110-2200 MHz have been identified by Radio Regulation WARC-92 (Footnote 746A) for use on a worldwide basis for implementation of FPLMTS. The high level description of FPLMTS and the framework of services are covered in ITU-R Recommendations M.687-1 and M.816 respectively.
+
+**1.2** Key features of FPLMTS are expected to be:
+
+- applicability to land mobile, aeronautical mobile, and maritime mobile environments;
+- incorporation of a variety of systems;
+- high degree of commonality of design;
+- compatibility of services within FPLMTS and with the fixed network;
+- quality of service comparable to that of the fixed network;
+- security of communications comparable to that of the fixed network;
+- worldwide intercommunication and interoperability;
+- use of a lightweight, pocket-sized terminal.
+
+**1.3** FPLMTS services may be divided into those which are specific to FPLMTS and those which are common to the fixed network.
+
+# **2 Scope**
+
+The purpose of this Recommendation is to identify and define the service objectives and principles for the Future Public Land Mobile Telecommunication Systems (FPLMTS) and to provide guidance for the further development of FPLMTS. This Recommendation is part of a family of Recommendations dealing with FPLMTS which are defined in clause 3.
+
+# **3 References**
+
+FPLMTS are defined by a set of related (FPLMTS and non-FPLMTS specific) Recommendations. Recommendations of general interest are listed in this clause while Recommendations of a more specific nature are referenced with the applicable text.
+
+## **3.1 CCITT and ITU-T Recommendations**
+
+- CCITT Recommendation E.164 (1991), *Numbering plan for the ISDN era*.
+- ITU-T Recommendation E.750 (1993), *Introduction to E.750-Series of Recommendations on traffic engineering aspects of mobile networks*.
+- ITU-T Recommendation E.751 (1993), *Reference connections for traffic engineering of land mobile networks*.
+
+- ITU-T Recommendation E.770 (1993), *Land mobile and fixed network interconnection traffic grade of service concept*.
+- ITU-T Recommendation E.771 (1993), *Network grade of service parameters and target values for circuit-switched land mobile services*.
+- CCITT Recommendation F.111 (1991), *Principles of service for mobile systems*.
+- ITU-T Recommendation F.850 (1993), *Principles of Universal Personal Telecommunication (UPT)*.
+- ITU-T Recommendation F.851 (1995), *Universal Personal Telecommunication (UPT) – Service description (service set one)*.
+- ITU-T Recommendation G.114 (1993), *One-way transmission time*.
+- ITU-T Recommendation G.174 (1994), *Transmission performance objectives for terrestrial digital wireless systems using portable terminals to access the PSTN*.
+- ITU-T Recommendation I.114 (1993), *Vocabulary of terms for Universal Personal Telecommunication*.
+
+## 3.2 ITU-R Recommendations
+
+Recommendation ITU-R M.687-1 (Future Public Land Mobile Telecommunication Systems) is the core document for the definition of FPLMTS.
+
+- ITU-R Recommendation M.687-1, *Future Public Land Mobile Telecommunication Systems (FPLMTS)*.
+- ITU-R Recommendation M.816, *Framework for services supported on Future Public Land Mobile Telecommunication Systems (FPLMTS)*.
+- ITU-R Recommendation M.817, *FPLMTS network architectures*.
+- ITU-R Recommendation M.818, *Satellite operation within FPLMTS*.
+- ITU-R Recommendation M.819-1, *FPLMTS for developing countries*.
+- ITU-R Recommendation M.[Doc. 8/154(+ Corr.1)], *Security principles for FPLMTS*.
+- ITU-R Recommendation M.[Doc. 8/155], *Speech and voiceband data performance requirements for FPLMTS*.
+- Recommendation FPLMTS.TMLG, *Vocabulary of terms for FPLMTS*.
+- Recommendation FPLMTS.RSEL, *Procedures for selection of radio transmission technologies for FPLMTS*.
+- Recommendation FPLMTS.NMGM, *Framework of FPLMTS network management*.
+- ITU-R Recommendation M.1034, *Requirements for the radio interface(s) for FPLMTS*.
+- ITU-R Recommendation M.1035, *Framework for the radio interface(s) and radio subsystem functionality for FPLMTS*.
+- ITU-R Recommendation M.1036, *Spectrum considerations for implementation of Future Public Land Mobile Telecommunication Systems (FPLMTS) in the bands 1885-2025 MHz and 2110-2200 MHz*.
+
+NOTE – ITU-R Recommendation numbers will be checked and updated prior to the printing of this Recommendation.
+
+# 4 Definitions
+
+For the purposes of this Recommendation, the following specifications apply:
+
+**4.1 Future Public Land Mobile Telecommunication Systems (FPLMTS):** FPLMTS are third generation mobile systems, which are scheduled to start service around the year 2000 subject to market considerations. They may be utilized as stand alone mobile systems or as part of the fixed network. They are systems which will provide telecommunication services to mobile or stationary users by means of one or more radio links. The frequency bands 1885-2025 and 2110-2200 MHz have been identified by Radio Regulation WARC-92 (Footnote 746A) for use on a
+
+worldwide basis for implementation of FPLMTS. This mobility will be unrestricted in terms of location within the radio coverage area. FPLMTS will extend the telecommunication services of the fixed network to these users over wide geographic areas, subject to constraints imposed by spectrum allocation and radio propagation. In addition, FPLMTS will support a range of services particular to mobile radio systems (see Recommendation ITU-R M.687-1). Provision of services may be limited by the capabilities of the involved terminals and network.
+
+**4.2 terminal mobility:** The ability of the terminal to access telecommunication services from different locations and while in motion, and the capability of the network to identify and locate that terminal (see Recommendation I.114).
+
+**4.3 FPLMTS user mobility:** FPLMTS user mobility is a feature which enables a FPLMTS user to transfer his/her identity between FPLMTS mobile terminals.
+
+**4.4 Universal Personal Telecommunication (UPT):** UPT enables access to telecommunication services while allowing personal mobility. It enables each UPT user to participate in a user-defined set of subscribed services and to initiate and receive calls on the basis of a personal, network-transparent, UPT number across multiple networks at any terminal, fixed or mobile, irrespective of geographic location, limited only by terminal and network capabilities and restrictions imposed by the network operator (see Recommendation F.850).
+
+**4.5 privacy:** The right of individuals to control or influence what information related to them may be collected or stored and by whom and to whom that information may be disclosed.
+
+**4.6 mobile terminal:** For the purposes of this Recommendation this term includes both the radiocommunication equipment and specific telecommunication service equipment, e.g. telephone (handset) and fax machine.
+
+# **5 Service principles**
+
+**5.1** FPLMTS are intended to provide users with services which will be available globally. The provision of these services may involve cooperation between a number of operating entities (e.g. service providers, mobile network operators and fixed network operators).
+
+**5.2** At any geographical location there may be more than one network operator or service provider.
+
+**5.3** As an aid to users, it is desirable that any service offered should have a similarity of access interaction and operational procedures on a global basis.
+
+**5.4** FPLMTS will integrate a terrestrial component and a satellite-based component (see Recommendations ITU-R M.687-1 and M.818). Satellite based services may however have some properties different from those provided terrestrially.
+
+**5.5** To satisfy the need for call detail recording between different countries and service providers, there may be a requirement for FPLMTS to be able to include, in call records, the geographical location of the calling and called parties. In order to maintain the privacy of the FPLMTS user as the called party, the geographic location of the FPLMTS user should not appear on any bill or statement submitted to any party other than the FPLMTS subscriber or appropriate service provider. See 7.1.5.
+
+**5.6** Interworking of FPLMTS with the fixed network should be in accordance with Recommendation F.111, Principles of service for mobile systems.
+
+**5.7** Terminal mobility which enables a user to be in motion during all aspects of a call give rise to specific service requirements whether the service being used is a FPLMTS specific service or one of the services of the fixed networks. It will require authentication and validation procedures to verify the right of the user to access the service. The recording of call details may capture an indication of user location, network access point and called party location, in addition to other billing, charging and accounting information. See 5.5 concerning FPLMTS user privacy.
+
+# **6 Overall service objectives**
+
+- 6.1** To provide FPLMTS users with continuous availability of their subscribed telecommunication services regardless of their roaming situation, geographic location, or network access, on a global basis but subject to the terms and conditions under which the visited network offers service to roaming users.
+- 6.2** To provide to FPLMTS users, where feasible, services which are identical, or similar, to those offered by the fixed telecommunication networks. (Refer to 7.1/F.111.)
+- 6.3** To facilitate introduction of new customised services, in particular for multimedia applications, which allow the use of modular reusable service components in accordance with ITU-T Recommendations.
+- 6.4** To provide telecommunications of high quality that is comparable to that of the fixed network.
+- 6.5** To accommodate a variety of mobile terminals ranging from those which are small enough to be carried to those which are mounted in vehicles or otherwise used in conjunction with a mobile network.
+- 6.6** To provide commonality of service presentation and operation (the means by which the service and the user interact) among FPLMTS.
+- 6.7** To provide for forward compatibility with developing telecommunication services.
+- 6.8** To support a range of telecommunication services in various configurations such as point-to-point, multipoint and point-to-multipoint.
+- 6.9** To provide for backward compatibility with services provided by existing mobile systems to the extent practicable.
+
+# **7 Service requirements**
+
+## **7.1 General service requirements**
+
+- 7.1.1** Provide for service availability such that the users of one service provider may request service in real time from another service provider without the need for prior arrangements or agreements on both an international and national basis, where national regulations and implementations permit.
+- 7.1.2** Provide for the secure and timely communication of billing, charging and accounting information.
+- 7.1.3** Provide for the secure authentication and validation of mobile terminals and users.
+- 7.1.4** Provide for appropriate levels of security for telecommunication services to ensure that the user perceives the security of the communication as being comparable to that of the fixed network.
+- 7.1.5** Provide for optional location privacy at the request of the user.
+- 7.1.6** Provide for the secure and accurate creation of appropriate data records to facilitate charging, billing, accounting and network management functions in accordance with the relevant D- and M-Series Recommendations.
+- 7.1.7** Provide a capability for UPT support (i.e. personal mobility aspects, see Recommendation F.851).
+- 7.1.8** Provide for FPLMTS terminal mobility and FPLMTS user mobility both within and among FPLMTS.
+
+## **7.2 General access requirements**
+
+- 7.2.1** Features and facilities of FPLMTS should, to the extent feasible, enable mobile users of one service provider to access and utilize the system of a service provider in another country, on an automatic basis when visiting that country. Such international, automatic roaming would be subject to national regulation, international agreement and any limitations imposed by service providers.
+
+**7.2.2** In a similar manner to international operation, access to FPLMTS should be available in the maritime and aeronautical environments to the extent permitted by national and international regulatory authorities, the characteristics of the system used and any limitations imposed by service providers.
+
+**7.2.3** Access to FPLMTS satellite services should be available to the extent permitted by national and international regulatory authorities, the characteristics of the system used and any limitations imposed by service providers.
+
+**7.2.4** The FPLMTS support of access to UPT will have the objective of maintaining UPT's common presentation functionality to users.
+
+## **7.3 Numbering considerations**
+
+**7.3.1** A FPLMTS user requires a number formatted in accordance with Recommendation E.164 by which he/she can be addressed by callers.
+
+**7.3.2** FPLMTS users may participate in closed user groups utilizing non-E.164 numbers as closed user group identities.
+
+# **8 Services supported**
+
+## **8.1 Introduction**
+
+The services to be supported by FPLMTS reflect the needs of users to communicate in a mobile environment.
+
+Each FPLMTS provider will determine what services will be offered to its users. However, it is recommended that the following be offered:
+
+- i) voice communication with other users of fixed or mobile terminals (telephone service) connected to private or public networks; and
+- ii) data communications with other fixed or mobile terminals.
+
+It should be noted that this does not prevent other services being offered.
+
+Figure 1 illustrates the service relationships.
+
+## **8.2 Common FPLMTS services**
+
+The services which are applicable to the common area shown in Figure 1 are those of the fixed network. The definitions, service and operational provisions relating to these services may be found in the relevant E-, F- and I-Series Recommendations as listed in Appendix I. This list is not intended to be exclusive.
+
+## **8.3 FPLMTS specific services**
+
+The following services are applicable to the FPLMTS specific area as shown in the diagram above. This list is not intended to be exclusive.
+
+- Location services.
+- Paging service.
+- Short message services.
+- Traffic and navigation services.
+
+# **9 Quality of Service**
+
+The Quality of Service offered by the FPLMTS should be comparable to that of the PSTN/ISDN and public data networks as far as practicable. [See ITU-R M.(Doc. 8/155), Recommendation FPLMTS.PRQ and Recommendation G.174.]
+
+NOTE – ITU-R Recommendation numbers will be checked and updated prior to the printing of this Recommendation.
+
+![Conceptual model of network infrastructures and their services relationship diagram](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+The diagram illustrates the conceptual model of network infrastructures and their services relationship. At the top, three boxes represent service types: 'Fixed network specific services', 'Common services', and 'FPLMTS specific services'. A horizontal dashed line separates these from the infrastructure layer below. To the right of this line, the text 'ITU service Recommendations' is above 'ITU technical Recommendations'. Below the dashed line, two large overlapping ovals represent 'Fixed network infrastructure' and 'FPLMTS infrastructure'. Lines connect the service boxes to these infrastructure ovals. Below the infrastructure ovals, various devices are shown: 'Fixed links (Physical or radio)' (represented by a telephone icon), a 'PBX' (Private Branch Exchange) connected to multiple telephones and a computer, and 'Mobile Radio links' (represented by a zigzag line) connecting to a telephone and a computer. The text 'T0103790-94/d01' is located in the bottom right corner of the diagram area.
+
+Conceptual model of network infrastructures and their services relationship diagram
+
+FIGURE 1/F.115  
+**Conceptual model of network infrastructures  
+ and their services relationship**
+
+## 9.1 General
+
+Consideration will need to be given to maintaining Quality of Service during handover between cells and to any implications in relation to cell size, frequency requirements, protocols, etc.
+
+To maintain the Quality of Service for data services, additional error control facilities for the radiocommunication path may be required (e.g. for facsimile machines).
+
+## 9.2 Speech quality
+
+The quality of speech services in FPLMTS should be comparable to that of the PSTN/ISDN. Speech services are sensitive to delay and this needs to be taken into consideration (see Recommendation G.114).
+
+The quality of speech supported within FPLMTS should be nominally that recommended in the P-Series Recommendations. However, it is acknowledged that in some applications where low bit rate coding is employed, some minimal degradation of speech quality may occur.
+
+## 9.3 Traffic engineering aspects
+
+As per the E.700-Series Recommendations on traffic engineering of mobile networks.
+
+# Appendix I
+
+## Recommendations relevant to common services
+
+(This appendix does not form an integral part of this Recommendation)
+
+As noted in 8.2, this list is not intended to be exclusive.
+
+- F.110 *Operational provisions for the maritime mobile service.*
+- F.111 *Principles of service for mobile systems.*
+- F.113 *Service provision for aeronautical passenger communications supported by mobile satellite systems.*
+- F.122 *Operational procedures for the maritime satellite data transmission service.*
+- F.160 *General operational provisions for the international public facsimile services.*
+- F.180 *General operational provisions for the international public facsimile service between subscribers stations.*
+- F.182 *Operational provisions for the international public facsimile service between subscriber stations with groups 2 and 3 facsimile machines.*
+- F.184 *Operational provisions for the international public facsimile service between subscriber stations with group 4 facsimile machines.*
+- F.200 *Teletex service.*
+- F.300 *Videotex service.*
+- F.310 *Broadband Videotex services.*
+- F.600 *Service and operational principles for public data transmission services.*
+- F.701 *Teleconference service.*
+- F.710 *General principles for audiographic conference services.*
+- F.711 *Audiographic conference teleservice for ISDN.*
+- F.720 *Videotelephony services general.*
+- F.721 *Videotelephony service for ISDN.*
+- F.722 *Broadband videotelephony services.*
+- F.730 *Videoconference service general.*
+- F.732 *Broadband videoconference services.*
+- F.740 *Audiovisual interactive services.*
+- F.761 *Service-oriented requirements for telewriting applications.*
+- F.811 *Broadband connection-oriented bearer services.*
+- F.812 *Broadband connectionless data bearer service.*
+- F.813 *Virtual path service for reserved and permanent communications.*
+- F.821 *Broadband TV distribution services.*
+- F.822 *Broadband HDTV distribution services.*
+- F.850 *Principles of UPT.*
+- F.851 *Universal Personal Telecommunications (UPT) service description (service set one).*
+
+- F.400 *Message handling system and service overview.*
+- F.401 *Message handling services: Naming and addressing for public message handling services.*
+- F.410 *Message handling services: The public message transfer service.*
+- F.415 *Message handling services: Intercommunication with public physical delivery services.*
+- F.420 *Message handling services: The public interpersonal messaging service.*
+- F.435 *Message handling: EDI messaging service.*
+- F.440 *Message handling services: The voice messaging service.*
+- F.450 *Asynchronous group communication.*
+- F.500 *International public directory services.*
+- F.16 *Global Virtual Network Service.*
+- I.241.8 *Teleaction stage one service description.*
+- E.105 *International telephone service.*
+- E.116 *International telecommunications charge card service.*
+- E.140 *Operator-assisted telephone service.*
+- E.152 *International freephone service.*
+- E.330 *User control of ISDN-supported services.*
+
+### **ISDN supplementary services**
+
+- I.230 *Definition of bearer service categories.*
+- I.231 *Circuit-mode bearer service categories.*
+- I.232 *Packet mode bearer service categories.*
+- I.240 *Teleservices supported by ISDN.*
+- I.241.7 *Telephony 7 kHz teleservice.*
+- I.250 *Definition of supplementary services.*
+- I.251 *NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES.*
+- I.251.1 *Direct-Dialling-In.*
+- I.251.2 *Multiple Subscriber Number.*
+- I.251.3 *Calling Line Identification Presentation.*
+- I.251.4 *Calling Line Identification Restriction.*
+- I.251.5 *Connected Line Identification Presentation.*
+- I.251.6 *Connected Line Identification Restriction.*
+- I.251.7 *Malicious Call Identification.*
+- I.251.8 *Sub-addressing.*
+- I.252 *CALL OFFERING SUPPLEMENTARY SERVICES.*
+- I.252.1 *Call Transfer (normal).*
+- I.252.2 *Call Forwarding Busy.*
+- I.252.3 *Call Forwarding No Reply.*
+- I.252.4 *Call Forwarding Unconditional.*
+- I.252.5 *Call Deflection.*
+- I.252.6 *Line Hunting.*
+- I.252.7 *Call Transfer (explicit).*
+- I.252.8 *Call Transfer (single step).*
+- I.253 *CALL COMPLETION SUPPLEMENTARY SERVICES.*
+- I.253.1 *Call Waiting.*
+- I.253.2 *Call Hold.*
+
+- I.253.3 *Completion of calls to busy subscribers.*
+- I.253.4 *Completion of calls to no reply.*
+- I.254 *MULTIPARTY SUPPLEMENTARY SERVICES.*
+- I.254.1 *Conference Calling.*
+- I.254.2 *Three-Party Service.*
+- I.254.3 *Preset Conference Calling Service.*
+- I.254.4 *Conference Call, Booked add-on.*
+- I.254.5 *Conference Call, Meet me.*
+- I.255 *COMMUNITY OF INTEREST SUPPLEMENTARY SERVICES.*
+- I.255.1 *Closed User Group.*
+- I.255.2 *Support of Private Numbering Plans.*
+- I.255.3 *Multi-level precedence and pre-emption service.*
+- I.255.4 *Priority service.*
+- I.255.5 *Outgoing call barring.*
+- I.256 *CHARGING SUPPLEMENTARY SERVICES.*
+- I.256.1 *Credit Card Calling.*
+- I.256.2 a) *Advice of Charge: Charging information at call set-up time.*
+- I.256.2 b) *Advice of Charge: Charging information during the call.*
+- I.256.2 c) *Advice of Charge: Charging information at the end of the call.*
+- I.256.3 *Reverse charging.*
+- I.256.4 *ISDN freephone service.*
+- I.257 *ADDITIONAL INFORMATION TRANSFER.*
+- I.257.1 *User-to-user signalling.*
+
+NOTE – This list will be checked and updated, if required, prior to the printing of this Recommendation.

marked/F/T-REC-F.116-200003-I_PDF-E/raw.md

@@ -0,0 +1,504 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.116**
+
+(03/00)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Mobile service – Mobile services and multdestination  
+satellite services
+
+---
+
+**Service features and operational provisions in  
+IMT-2000**
+
+ITU-T Recommendation F.116
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| <b>Mobile services and multdestination satellite services</b>   | <b>F.110–F.159</b> |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | F.700–F.799        |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>HUMAN FACTORS</b>                                            | F.900–F.999        |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## **SERVICE FEATURES AND OPERATIONAL PROVISIONS IN IMT-2000**
+
+## **Summary**
+
+IMT-2000 systems are third generation mobile systems, which may be terrestrial, or satellite-based and may be characterized as networks in terms of service provision. This Recommendation describes service features and operational provisions that apply to IMT-2000 systems. It defines a set of service features and capabilities to standardize service presentation and to facilitate global mobility for users across network boundaries. Some of these services features and capabilities are essential whilst others are optional.
+
+## **Source**
+
+ITU-T Recommendation F.116 was prepared by ITU-T Study Group 2 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 13 March 2000.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2000
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+###### Page
+
+|        |                                                 |   |
+|--------|-------------------------------------------------|---|
+| 1      | Introduction.....                               | 1 |
+| 2      | Scope.....                                      | 1 |
+| 3      | References.....                                 | 1 |
+| 4      | Terminology.....                                | 1 |
+| 5      | Mobility concept.....                           | 2 |
+| 5.1    | Terminal mobility .....                         | 2 |
+| 5.2    | Standard terminal equipment portability .....   | 2 |
+| 5.3    | IMT-2000 user mobility.....                     | 2 |
+| 6      | Support of flexible service provision.....      | 2 |
+| 7      | Universal bearer capability handling .....      | 3 |
+| 7.1    | Data service types .....                        | 3 |
+| 7.2    | Quality of service categories.....              | 4 |
+| 7.3    | Example combinations.....                       | 4 |
+| 8      | Support of multimedia services in IMT-2000..... | 4 |
+| 9      | IMT-2000 service capabilities .....             | 5 |
+| 9.1    | Privacy and fraud prevention .....              | 5 |
+| 9.2    | Emergency call support service .....            | 5 |
+| 9.3    | Man-Machine Interface (MMI) functions.....      | 6 |
+| 9.4    | User registration.....                          | 6 |
+| 9.5    | Multiple profiles/subscriptions .....           | 6 |
+| 9.6    | IMT-2000 service profile management.....        | 6 |
+| 9.6.1  | IMT-2000 profile interrogation .....            | 6 |
+| 9.6.2  | IMT-2000 profile modification.....              | 6 |
+| 9.6.3  | IMT-2000 profile portability .....              | 7 |
+| 9.7    | Roaming capability .....                        | 7 |
+| 9.8    | Addressing capabilities .....                   | 7 |
+| 9.9    | Over-the-Air services.....                      | 7 |
+| 9.9.1  | Over-the-Air service provisioning.....          | 7 |
+| 9.9.2  | Over-the-Air profile administration.....        | 7 |
+| 9.10   | Priority access .....                           | 7 |
+| 9.11   | Services based on location.....                 | 7 |
+| 9.11.1 | Position determination.....                     | 7 |
+| 9.11.2 | Emergency calls.....                            | 7 |
+| 9.11.3 | Location registration.....                      | 8 |
+
+|                                                     | <b>Page</b> |
+|-----------------------------------------------------|-------------|
+| 9.12 Identification services .....                  | 8           |
+| 9.13 Teleservice support capability .....           | 8           |
+| 9.14 Supplementary service support capability ..... | 8           |
+| 9.15 Voice Recognition support capability.....      | 9           |
+| 9.16 Preferred language .....                       | 9           |
+
+# **Introduction**
+
+IMT-2000 are third generation mobile systems, which may be terrestrial or satellite-based. These systems may be characterized as networks in terms of service provision. They may be utilized as stand-alone mobile systems or as part of the fixed network.
+
+
+
+## **SERVICE FEATURES AND OPERATIONAL PROVISIONS IN IMT-2000**
+
+*(Geneva, 2000)*
+
+# **1 Introduction**
+
+IMT-2000 are third generation mobile systems, which may be terrestrial or satellite-based. These systems may be characterized as networks in terms of service provision. They may be utilized as stand-alone mobile systems or as part of the fixed network.
+
+# **2 Scope**
+
+This Recommendation describes service features and operational provisions that apply to IMT-2000 systems. It defines a set of service features and capabilities, some of which are essential and some optional. The intent is to standardize service presentation and to facilitate global mobility for users across network boundaries.
+
+# **3 References**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- ITU-T Recommendation F.111 (1991), *Principles of service for mobile systems*.
+- ITU-T Recommendation F.115 (1995), *Service objectives and principles for future public land mobile telecommunication systems*.
+- ITU-T Recommendation F.700 (2000), *Framework Recommendation for audiovisual/multimedia services*.
+- ITU-T Recommendation Q.1701 (1999), *Framework for IMT-2000 networks*.
+- Recommendation ITU-R M.816-1 (1997), *Framework for services supported on International Mobile Telecommunications 2000 (IMT-2000)*.
+- Recommendation ITU-R M.1078 (1993), *Security principles for International Mobile Telecommunications 2000 (IMT-2000)*.
+- Recommendation ITU-R M.1223 (1997), *Evaluation of security mechanisms for IMT-2000*.
+
+# **4 Terminology**
+
+This Recommendation defines the following terms:
+
+**4.1 mobile terminal:** For the purpose of this Recommendation, this term includes both the radiocommunication equipment, specific service equipment (e.g. telephone (handset), fax machine) and user identity module (UIM). Several types of terminal equipment (e.g. ISDN TE) may be connected to a mobile terminal.
+
+**4.2 User Identity Module (UIM):** A standard device or functionality providing secure procedures in support of user or terminal registration, authentication, and privacy for wireless access to IMT-2000. It may also contain application data to be used to facilitate telecommunication services and other services (e.g. UPT, banking).
+
+**4.3 virtual home environment:** Virtual home environment (VHE) is a capability whereby a user is offered the same service experience in a visited network as in his home network.
+
+The degree to which the VHE matches the actual home environment may, for example, be subject to the degree of cooperation between the visited and home network, their relative technical capabilities and the compatibility of the user terminal.
+
+# **5 Mobility concept**
+
+### **5.1 Terminal mobility**
+
+The ability of the terminal to access telecommunication services from different locations while in motion and the capability of the network to identify and locate that terminal.
+
+NOTE – The term "motion" includes the stationary state. This mobility aspect does not preclude the concept of fixed terminals participating in IMT-2000.
+
+## **5.2 Standard terminal equipment portability**
+
+The ability to connect terminal equipment to IMT-2000 mobile terminals.
+
+### **5.3 IMT-2000 user mobility**
+
+IMT-2000 user mobility is a feature which enables an IMT-2000 user to transfer his/her identity between IMT-2000 mobile terminals.
+
+The IMT-2000 user mobility affords the IMT-2000 user, with the application of a user identity module (e.g. "smart card"), to make an IMT-2000 mobile terminal his/her own mobile terminal. In this manner, the IMT-2000 user can access telecommunication services specified in their service profile with any IMT-2000 mobile terminal.
+
+# **6 Support of flexible service provision**
+
+In IMT-2000, services should be offered in a flexible way so that the preferences of each user can be fulfilled but without unduly constraining interoperability of, and roaming between, networks. For example, the user might be offered a choice of language in which to receive network prompts and announcements. The concept of Virtual Home Environment (VHE) has been proposed as a means of facilitating such an approach.
+
+When VHE is applied, depending on appropriate business arrangements and agreements, the following options exist:
+
+- the service profile of a user and the MMI (Man Machine Interface) which he is accustomed to are recorded, so that they can be transferred electronically from the home network to the visited network;
+- the service profile of a user and/or the MMI which he is accustomed to are partially stored in the UIM and the remaining information stored in the appropriate databases in the home network;
+- the service profile of a user and the MMI which he is accustomed to are stored completely in the UIM.
+
+For users who roam from their home network, each visited network can provide the same service-related functions in the same way as the home network, provided sufficient information has been supplied by the home network.
+
+# 7 Universal bearer capability handling
+
+IMT-2000 systems should support services based on digital transmission in an efficient, economical and user-friendly way. The service requester should have maximum freedom in communicating the characteristics of the requested service to the network. These characteristics might include a combination of service types and their quality of service. The network should try to fulfill the requirement or propose a reasonable alternative to the requester.
+
+The universal bearer services should allow for the emulation of, and interworking with, existing second generation services, e.g. 3.1 kHz audio UDI, Multicast, Group Broadcast, Voice Broadcast, Groupcall.
+
+The following service types may be provided using ITU defined protocols or using IETF (Internet Engineering Task Force) defined protocols (IP). In the specific case of IP, both static and dynamic IP-based addressing capabilities may be used to provide associated mobility support for services.
+
+Multiple concurrent session controls may also be provided as a service provider option to avoid routing ambiguities.
+
+### 7.1 Data service types
+
+The data service types supported by IMT-2000 are classified as follows:
+
+#### *Communication configurations*
+
+- PTP: Point-to-point service.
+- PTM-B: Point-to-multipoint broadcast service.
+- PTM-M: Point-to-multipoint multicast service.
+- MTM: Multipoint-to-multipoint (e.g. needed for multimedia services with different sources of content).
+
+#### *Area selection*
+
+- geographical area selection;
+- address domain selection;
+- multicast group selection;
+- static and dynamic addressing in IP.
+
+#### *Communication modes for network services*
+
+- CLNS: Connectionless network service;
+- CONS: Connection oriented network service;
+- via ITU protocols or via IETF protocols.
+
+#### *Timing relationship*
+
+- timing relationship between source and destination required;
+- timing relationship between source and destination not required.
+
+#### *Bit rate*
+
+- constant bit rate;
+- variable bit rate;
+- asymmetry.
+
+## **7.2 Quality of service categories**
+
+The quality of service that a user can request is described by categories such as:
+
+- Best effort
+
+or:
+
+- QoS guaranteed with parameters such as:
+  - bit rate;
+  - throughput;
+  - delay characteristics;
+  - Maximum Bit Error Rate.
+
+### **7.3 Example combinations**
+
+Depending on the attributes, Timing Relationship, Bit rate and Communication mode, different bearer classes can be distinguished, which can occur within different communication configurations and area selections. They are further qualified by the set of QoS parameters.
+
+# **8 Support of multimedia services in IMT-2000**
+
+Multimedia services combine two or more media into a single integrated service. From the user's point of view, a multimedia telecommunication service is the combination of IMT-2000 telecommunication capabilities required to support a particular multimedia application. From the IMT-2000 provider's point of view, a multimedia telecommunication service is a combination or set of combinations of two or more media components (e.g. audio, video, graphics, etc.).
+
+Examples of IMT-2000 multimedia services which could be supported by one or several multimedia communication tasks are:
+
+- mobility services (specifically related to the mobility of the user, like location service);
+- conference services (providing bidirectional and synchronized real-time transfer of voice and possibly moving pictures);
+- conversation services (allowing bidirectional dialogue communication with real-time end-to-end information transfer);
+- distribution services (providing continuous flow of information from a central source);
+- retrieval services (allowing to retrieve information from one source at a time);
+- collection services (allowing to retrieve information from several sources in parallel);
+- message services (offering user-to-user communications with store-and-forward capabilities).
+
+# **9 IMT-2000 service capabilities**
+
+### **9.1 Privacy and fraud prevention**
+
+Security mechanisms for the protection of the IMT-2000 user, service provider and network operator should provide for the following features in order to guarantee a maximum of privacy and fraud prevention, that are at least as good as in second generation wireless systems.
+
+The special security issues that arise from user/terminal mobility and inter-PLMN roaming shall be considered:
+
+- confidentiality of user messages;
+- privacy of user/subscriber related data;
+- privacy of billing data;
+- authentication of user to UIM, UIM to the network, network to UIM, service provider to network operator, visited network to home network, etc.;
+- event reporting and event limitation.
+
+The features above should be fulfilled in a way that is transparent to the user or is at least user-friendly. The impact on the quality of service in normal operation should be kept to a minimum.
+
+Service-related security features shall operate when roaming.
+
+The home network is informed if the visited network cannot provide the security functions deemed essential by the home network operator, who shall then be enabled to take the appropriate action and assure the integrity of the service.
+
+Some security features could be an integral part of the services and should be defined by the service provider.
+
+For further details on security features and security mechanisms for IMT-2000, refer to Recommendations ITU-R M.1078 and M.1223.
+
+### **9.2 Emergency call support service**
+
+Any IMT-2000 mobile terminal should be allowed to make a call attempt to an emergency call centre.
+
+The emergency call centre should be able to infer that the call was initiated by a mobile terminal (e.g. based on trunk group). The current location of the mobile terminal, if available, is to be supplied to the emergency call centre. Upon answering the call, the emergency call centre shall be able to communicate with the caller over a normal voice connection. After establishment of the call with the emergency call centre, the caller may allow a party or parties previously put on "hold" to join the conversation. Release occurs when either the caller or the emergency call centre disconnects. The emergency call centre should be supplied with sufficient information to enable it to re-establish the call to the caller after the emergency call is released.
+
+The emergency call concept is applicable to voice and Telecommunications Device for the Deaf/Text Telephony (TDD/TTY).
+
+National and/or service provider options include:
+
+- a) the concept of access for emergency call attempts to be given preferential or priority access to the scarce radio resources compared with normal call attempts;
+- b) the facility to permit call attempts to an emergency call centre to be subjected to a reduced level of authentication and validation. For example, a call may be made without a UIM in the terminal.
+
+### **9.3 Man-Machine Interface (MMI) functions**
+
+MMI plays a role of the user's terminal access, network access, call setup, and service control. It should be possible for the user to customize certain aspects of the MMI. The presentation of a familiar MMI to the user should form a central part of the Virtual Home Environment (VHE). The service provider may be able to offer tailored MMI solutions using VHE. The MMI should meet the requirements to support the VHE to allow seamless service provision even across different types of networks and access terminals. This Recommendation is not intended to provide detailed MMI specifications, although it is desirable for the user to be offered a friendly MMI, integrating functions provided by the terminal manufacturer with those requested by the VHE.
+
+### **9.4 User registration**
+
+User registration is a feature by which a user associates himself and his service profile with the terminal for the purpose of accessing telecommunication services (e.g. receiving incoming and originate outgoing calls) and by which a network becomes aware of the existence and location of a terminal and its associated user(s).
+
+In order for an IMT-2000 user to be registered on an IMT-2000 terminal, a UIM associated with the user has to be physically present in the terminal.
+
+User authentication should be executed at each user registration. A user may explicitly deregister.
+
+IMT-2000 networks should provide a capability to support UPT and therefore UPT user registration.
+
+### **9.5 Multiple profiles/subscriptions**
+
+It shall be possible for a user to obtain certain services from one service provider and some other services from another service provider using a single UIM. Where multiple subscriptions on a single UIM are in use the following principles shall apply:
+
+- if there are several service providers subscriptions on a single UIM, then different numbers are to be used for each service provider, i.e. shared numbering shall not be used;
+- for outgoing calls, the user shall be able to select which service provider to use on a per call basis or on a subscription basis;
+- it shall be possible to have multiple subscriptions active simultaneously;
+- there is a requirement for a terminal supported by one network operator to be able to have users from different service providers associated with that terminal. Such a capability infers that the service provider of each associated user will have an agreement with the service provider supporting that terminal.
+
+### **9.6 IMT-2000 service profile management**
+
+#### **9.6.1 IMT-2000 profile interrogation**
+
+This feature enables a user to interrogate the current status of their service profile (e.g. for location information, availability of services, charging information, etc.).
+
+Some data included in the profile is restricted from view of the user. User authentication/validation security procedures should be executed at each profile interrogation.
+
+#### **9.6.2 IMT-2000 profile modification**
+
+This feature enables a user to modify their current service profile (e.g. for availability of services, changing of password, etc.).
+
+Some data included in the profile is restricted from the view of the user. User authentication/validation security procedures should be executed at each profile interrogation.
+
+#### **9.6.3 IMT-2000 profile portability**
+
+The concept of VHE in IMT-2000 requires that the service profile of a user is used when roaming outside the home network. Technical or business constraints or other reasons may limit its full application.
+
+### **9.7 Roaming capability**
+
+IMT-2000 networks may provide VHE support to facilitate roaming outside the home network in an environment of flexible service provision.
+
+### **9.8 Addressing capabilities**
+
+IMT-2000 should be able to support the traditional addressing mechanisms that exist in existing networks, e.g. E.164 telephone number, X.121 address on packet data networks or X.400 or IP address or name for electronic mail. IMT-2000 should also support a more integrated approach, where multimedia calls can be set up without having to use all these mechanisms together.
+
+Therefore, there is a general service requirement that the signalling capability of IMT-2000 systems should support the use of numeric, alpha and alphanumeric naming schemes.
+
+### **9.9 Over-the-Air services**
+
+#### **9.9.1 Over-the-Air service provisioning**
+
+This is a feature which allows a subscriber to IMT-2000 to negotiate an initial subscription with a service provider and subsequently amend that subscription using automatic procedures over the air. (The term "automatic procedures" is intended to convey the fact that no human intervention is required on the part of the service provider.)
+
+#### **9.9.2 Over-the-Air profile administration**
+
+This is a feature, which enables a service provider to automatically update the user profile data as required. For example, updating the system selection preference list for use when the user is roaming.
+
+### **9.10 Priority access**
+
+As a service provider option and subject to national requirements it should be possible to create different classes of service to enable users to be offered Priority Access and Assignment. This feature functions when no radio channels are available. Users are placed in a queuing system until radio channels are available and then assigned channels on a first come first served basis subject to their class of service priority. Whilst in the queue awaiting channel assignment, a user is considered to be in the busy condition.
+
+### **9.11 Services based on location**
+
+#### **9.11.1 Position determination**
+
+Location allows an IMT-2000 user's position to be determined. Position determination may be initiated by the user, the network, or an external party (e.g. an Emergency Centre). Position determination may be subject to various restrictions based on capability, security, service profiles, etc.
+
+#### **9.11.2 Emergency calls**
+
+For the specific case of emergency calls, this capability is needed to identify the location of an IMT-2000 terminal from which an emergency call is being placed to within the limits specified by the appropriate national authority.
+
+NOTE – In the United States of America, for example, this is to within a radius of 125 metres in 67 per cent of all cases or better.
+
+The implementation of location services by satellite-based systems is not covered by this Recommendation.
+
+#### **9.11.3 Location registration**
+
+Services based on location registration will offer subscribers the opportunity to tailor their set of active services according to their current serving location. For example, there may be a specific set of active services for the residential location and a separate set of active services for the business location.
+
+### **9.12 Identification services**
+
+For reasons of public safety and service, it should be possible to make available within the network and in some cases to an end user, IMT-2000 user parameters such as user identity, network address and location information.
+
+For example, for emergency calls, the emergency call-handling centre may need all of these IMT-2000 user parameters to be able to:
+
+- identify a calling party;
+- re-establish a terminated call to a calling party;
+- pass calling party location information, to an emergency service.
+
+These IMT-2000 user parameters should be generated at the calling/originating end of the network, and be available for delivery as required.
+
+Public safety and service needs may also require the same information for the called IMT-2000 party, i.e. the called IMT-2000 user identity, the IMT-2000 network address of the call termination, and the location information for the call recipient. These IMT-2000 user parameters should be generated at the called/terminating end of the network and be available for delivery as required.
+
+### **9.13 Teleservice support capability**
+
+New teleservices as well as those that are supported in existing telecommunication systems should be supported by IMT-2000 (e.g. messaging, speech, facsimile, paging).
+
+### **9.14 Supplementary service support capability**
+
+New and existing supplementary services should be supported by IMT-2000. Examples of such supplementary services are as follows:
+
+- a) Identification Supplementary Services (e.g. Abbreviated Dialling, Calling Line Identification Presentation/Restriction, Connected Line Identification Presentation/Restriction, Malicious Call Identification, Universal Access Number, Multiple Subscriber Number, Calling Name Identification Presentation/Restriction, Calling Number Identification Presentation/Restriction).
+- b) Call Offering Supplementary Services (e.g. Call Distribution, Call Deflection, Call Forwarding Unconditional/Busy/No Reply/Not Reachable/default, Call Transfer, Destination Call Routing, Follow-Me Diversion, Mobile Access Hunting, Universal Access Number, Flexible Alerting).
+- c) Call Completion Supplementary Services (e.g. Call Hold, Call Waiting, Completion of Calls to Busy Subscriber).
+- d) Multiparty Supplementary Services (e.g. Conference Calling, 3-way calling).
+
+- e) Community of Interest Supplementary Services (e.g. Closed User Group, Virtual Private Network).
+- f) Charging Supplementary Services (Charge Card Calling, Advice of Charge, Credit Card Calling).
+- g) Additional Information Transfer Supplementary Services (User-to-user signalling, Message Waiting Notification).
+- h) Call Restriction Supplementary Services (e.g. Selective barring or screening of Incoming/outgoing Calls, Password and PIN restrictions).
+
+### **9.15 Voice Recognition support capability**
+
+Voice Recognition will enable a user to control features and supplementary services using spoken commands: (e.g. call origination, activation and de-activation of features, registration operations, user identification, validation and authentication, creation of short text messages and access to the short message service).
+
+### **9.16 Preferred language**
+
+This feature enables the subscriber to specify the language for network services. Network services, which could be offered in the subscriber's preferred language, include:
+
+- recorded announcements;
+- directory assistance;
+- operator services;
+- emergency services;
+- "Help" lines;
+- Message Waiting Notification;
+- CLIP number not available;
+- CLIP number restricted.
+
+
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of the ITU-T                                                                                          |
+| Series B        | Means of expression: definitions, symbols, classification                                                                      |
+| Series C        | General telecommunication statistics                                                                                           |
+| Series D        | General tariff principles                                                                                                      |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                              |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                |
+| Series G        | Transmission systems and media, digital systems and networks                                                                   |
+| Series H        | Audiovisual and multimedia systems                                                                                             |
+| Series I        | Integrated services digital network                                                                                            |
+| Series J        | Transmission of television, sound programme and other multimedia signals                                                       |
+| Series K        | Protection against interference                                                                                                |
+| Series L        | Construction, installation and protection of cables and other elements of outside plant                                        |
+| Series M        | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                |
+| Series O        | Specifications of measuring equipment                                                                                          |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                   |
+| Series Q        | Switching and signalling                                                                                                       |
+| Series R        | Telegraph transmission                                                                                                         |
+| Series S        | Telegraph services terminal equipment                                                                                          |
+| Series T        | Terminals for telematic services                                                                                               |
+| Series U        | Telegraph switching                                                                                                            |
+| Series V        | Data communication over the telephone network                                                                                  |
+| Series X        | Data networks and open system communications                                                                                   |
+| Series Y        | Global information infrastructure                                                                                              |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                           |
+
+\*18042\*

marked/F/T-REC-F.127-199610-I_PDF-E/raw.md

@@ -0,0 +1,285 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.127**
+
+(10/96)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Mobile service – Mobile services and multdestination  
+satellite services
+
+---
+
+**Operational procedures for interworking  
+between the international telex service and the  
+service offered by the INMARSAT-C system**
+
+ITU-T Recommendation F.127
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1–F.109          |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| MOBILE SERVICE                                                  | F.110–F.159        |
+| <b>Mobile services and multdestination satellite services</b>   | <b>F.110–F.159</b> |
+| TELEMATIC SERVICES                                              | F.160–F.399        |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499        |
+| DIRECTORY SERVICES                                              | F.500–F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550–F.599        |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699        |
+| AUDIOVISUAL SERVICES                                            | F.700–F.799        |
+| ISDN SERVICES                                                   | F.800–F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899        |
+| HUMAN FACTORS                                                   | F.900–F.999        |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## FOREWORD
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations 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.127 was revised by ITU-T Study Group 1 (1993-1996) and was approved by the WTSC (Geneva, 9-18 October 1996).
+
+---
+
+## NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+© ITU 1997
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+|                                                                                | <i>Page</i> |
+|--------------------------------------------------------------------------------|-------------|
+| 1 Definitions.....                                                             | 1           |
+| 2 Scope.....                                                                   | 1           |
+| 3 Introduction.....                                                            | 2           |
+| 4 Principles of operation .....                                                | 2           |
+| 5 Operational procedures .....                                                 | 2           |
+| 5.1 International telex service to INMARSAT-C system.....                      | 2           |
+| 5.2 Calls from an MES to subscribers of the international telex service .....  | 4           |
+| 5.3 MES-to-MES calls utilizing the international telex service.....            | 4           |
+| Annex A – Alphabetical list of abbreviations used in this Recommendation ..... | 4           |
+
+# OPERATIONAL PROCEDURES FOR INTERWORKING BETWEEN THE INTERNATIONAL TELEX SERVICE AND THE SERVICE OFFERED BY THE INMARSAT-C SYSTEM
+
+*(revised 1992 and 1996)*
+
+The ITU-T,
+
+*considering*
+
+- a) that INMARSAT has introduced various mobile services based on the INMARSAT-A, INMARSAT-B and INMARSAT-C systems;
+- b) that Recommendation F.120 specifies ship station identification for the maritime mobile-satellite service;
+- c) that Recommendation F.125 specifies the numbering plan for the maritime mobile-satellite service of INMARSAT;
+- d) that the provision of interworking with the international telex service is a standard requirement within the INMARSAT-C system,
+
+*unanimously recommends*
+
+that operational procedures of interworking between the international telex service and the service provided by the INMARSAT-C system be in accordance with this Recommendation.
+
+## 1 Definitions
+
+This Recommendation defines the following terms:
+
+**1.1 ship earth station** is defined in Article 1, section 4.16 of the *Radio Regulations*, ITU Geneva, 1982. For the purpose of this Recommendation, the terms “ship earth station” and “mobile earth station” are interchangeable.
+
+**1.2 coast earth station** is defined in Article 1, section 4.14 of the *Radio Regulations*, ITU Geneva, 1982. For the purpose of this Recommendation, the terms “coast earth station” and “land earth station” are interchangeable.
+
+**1.3 The mobile satellite store-and-forward unit** is the functional interface between the mobile satellite message transmission system and the international telex service.
+
+## 2 Scope
+
+**2.1** The purpose of this Recommendation is:
+
+- a) to standardize procedures for the subscribers of the international telex service calling Mobile Earth Stations (MESs) in the INMARSAT-C system;
+- b) to standardize procedures for an MES calling subscribers of the international telex service;
+- c) to standardize procedures for MES-to-MES calls that transit the international telex network.
+
+## 3 Introduction
+
+3.1 The characteristics of the mobile satellite circuit provided by the INMARSAT-C system are such that only store-and-forward operation is supported when interworking with the international telex service.
+
+3.2 A general description of the INMARSAT-C system and the services it may support is given in Supplement No. 3 to the F-Series Recommendations (*Blue Book*, Fascicle II.4, Melbourne, 1988).
+
+3.3 In the interests of ensuring that the optimum use is made of the international telex service, Administrations may wish to advise their customers of any differences in messaging procedures between the service offered by the INMARSAT-C system and normal telex procedures as offered by other INMARSAT standard systems.
+
+3.4 The provisions of this Recommendation should be applied to future implementation and, as far as practicable, to existing implementations of Mobile Satellite Store-and-Forward Unit (MSSFU).
+
+## 4 Principles of operation
+
+4.1 Communication between subscribers of the international telex service and an MES is on a store-and-forward basis. Thus, conversational mode interworking between terminals is not provided.
+
+4.2 Interworking between the international telex service and the INMARSAT-C system may employ either one-stage or two-stage selection procedures for the delivery of telex messages to an MES. Administrations may provide either or both modes of operation.
+
+These services may be extended across international boundaries on a bilateral basis. Where no such bilateral agreement exists, the Administration operating the MSSFU may clear the call and return the service signal (**NA**).
+
+4.3 In mobile to fixed direction, subscribers to the mobile-satellite service provided by the INMARSAT-C system may send single messages to the subscribers of the international telex service and to the appropriate applications. The messages are forwarded by the MSSFU via the international telex service.
+
+4.4 For calls from MES-to-MES, the procedures for handling calls between different satellite regions is not the subject for international standardization. Such calls which utilize the international telex service should follow normal telex procedures.
+
+## 5 Operational procedures
+
+### 5.1 International telex service to INMARSAT-C system
+
+#### 5.1.1 One-stage selection by the telex customer
+
+5.1.1.1 A customer of the international telex service may place a call to a mobile earth station using normal telex procedures.
+
+5.1.1.2 The originating telex subscriber, when calling an INMARSAT-C MES, should input the following selection information, plus any necessary prefix and end-of-selection signal:
+
+58S4X<sub>1</sub>.....X<sub>8</sub>
+
+where 58S is the telex destination code in accordance with Recommendation F.69 (S = 1, 2, 3 or 4), 4 is the T-digit in accordance with Recommendation F.125, and X<sub>1</sub>.....X<sub>8</sub> are part of the MES identity in accordance with Recommendation F.125.
+
+5.1.1.3 On receipt of this address, the MSSFU should check that the addressed MES is logged into the satellite region and should, if the result is positive, return the call connect signal in accordance with the relevant U-Series Recommendations. If the check fails, the call attempt should be cleared by the MSSFU with the appropriate service signal in accordance with Recommendation F.131.
+
+5.1.1.4 The MSSFU should return the MES answerback, formatted in accordance with Recommendation F.74.
+
+5.1.1.5 The MSSFU should transmit a **WRU** signal following the MES answerback in order to capture the answerback of the originating telex subscriber.
+
+**5.1.1.5 bis** Where the call to the MSSFU is being handled by a telex SFU operating in accordance with Recommendations F.72 and U.81 on behalf of a customer of the international telex service, the telex SFU identification should be forwarded to the MSSFU immediately following receipt of the called MES answerback. This should comprise the code expression **CI**, the characters **SFU** and the TNIC of the parent network of the telex SFU. This will then allow the procedures which subsequently follow to be under the full control of the telex SFU with no prompt signals returned by the MSSFU.
+
+Where the call to the MSSFU is originated by a subscriber of the international telex service operating in interactive or manual mode, the procedures of 5.1.1.6 to 5.1.1.8 should be applied.
+
+**5.1.1.6** The calling telex address shall be determined from the received telex answerback in accordance with the rules described in Recommendation U.74.
+
+Where the calling telex address cannot be determined, the MSSFU should wait 3 seconds from the end of the received answerback to enable the originating telex customer to voluntarily input his telex address, in accordance with Recommendation U.208. At the end of this period, the MSSFU shall return the prompt signal **ADD**. If the calling telex address is not received within 15 seconds of the **ADD** prompt, another **ADD** prompt signal shall be returned. If another 15 seconds elapse without the receipt of the calling telex address, the connection shall be cleared by the MSSFU.
+
+Optionally, the call may be accepted by the MSSFU, and the **GA** prompt returned, where, in the event of non-delivery of an accepted message, alternative arrangements are in place to provide a non-delivery notification message to the originating telex subscriber, for example, spill out to an assistance position.
+
+It should be noted that some MSSFU do not support the **ADD** procedure. In this case, the MSSFU should return the code expression **REJ** and clear the call.
+
+**5.1.1.7** Input of the message may now be commenced by the originating telex customer.
+
+**5.1.1.8** The preferred method of clearing to be applied by the originating telex customer is by the use of the End-of-Transmission (EOT) signal, four times combination 26 in figures case (++++) which need not be passed to the intended recipient. This method enables the provision of a message reference number by the MSSFU which could be useful to the message originator should a Non-Delivery Notification (NDN) be subsequently received. However, it should be recognized that the originating telex customer could clear the connection in one of the following ways:
+
+- a) The customer may close his message with the End-of-Message (EOM) signal **NNNN** which is followed by a period of idle condition of 30 seconds. This should be interpreted by the MSSFU as being equivalent to an EOT signal and return the input transaction accepted for delivery (ITD) sequence as specified in Recommendation U.208.
+- b) The customer may close his message with the end-of-message signal **NNNN** followed immediately by a clear, having optionally exchanged answerbacks, in which case the MSSFU should proceed as in c).
+- c) The call may be cleared without EOT or EOM, in which case all text received should be forwarded to the MES in the normal way, optionally including a statement which would advise the recipient that the message originator did not clear the connection using the EOT procedure and that consequently the message may be incomplete.
+- d) To facilitate clearing by Telex Automatic Emitting Device (TAED) which may interpret a clear initiated by the MSSFU as an abnormal condition, the **ITD** sequence should be followed by a period of idle condition to enable clearing by TAEDs in accordance with Recommendation S.20.
+
+**5.1.1.9** Following clearing of the connection across the international telex network, delivery of the message to the address MES should commence at the earliest opportunity.
+
+**5.1.1.10** The message should not be held in the MSSFU for more than 24 hours.
+
+**5.1.1.11** In the event of non-delivery of the message to the MES, it is the responsibility of the MSSFU to return an NDN directly to the originating telex customer in accordance with Recommendation U.208.
+
+**5.1.1.12** If message delivery has not commenced at the expiry of the 24-hour period, an NDN should be provided to the originating telex customer. However, any delivery procedure which has already been commenced by the MSSFU that would exceed the 24-hour period, should be completed.
+
+#### **5.1.2 Two-stage selection**
+
+**5.1.2.1** Subscribers of the international telex service should use normal telex call establishment procedures to access the MSSFU, which is allocated a national number for this purpose, the general service principles and access procedures and protocols being in accordance with Recommendations F.72 and U.80 for two-stage access to a store-and-forward unit.
+
+**5.1.2.2** The MSSFU should accept both single and multi-addressed calls, the address line containing an optional attention information field in accordance with Recommendation F.72 to indicate the expected answerback of the recipient, attention information, class of delivery indicator, and a request for positive delivery notification. The list of addresses, either single or multiple, should be closed by the End-of-Address (EOA) signal **BT**.
+
+As a minimum, the address line should contain the selection information in accordance with 5.1.1.2.
+
+**5.1.2.3** If the calling address cannot be determined from the calling subscriber's answerback for the purpose of delivering a non-delivery advice, the call should be cleared.
+
+The call may be accepted where, in the event of non-delivery of a message, alternative arrangements for delivery are provided. The alternative arrangements, for example, may be the provision of an operator position.
+
+**5.1.2.4** The action to be taken when abnormal conditions are encountered during message input shall be in accordance with Recommendations F.72 and U.80.
+
+### **5.2 Calls from an MES to subscribers of the international telex service**
+
+**5.2.1** Subscribers to the Mobile Satellite service provided by the INMARSAT-C system may send messages to subscribers of the international telex service.
+
+**5.2.2** The messages should be forwarded by the MSSFU to the addressed telex subscriber via the international telex service. The answerback sent to the called telex subscriber should be that of the MES.
+
+**5.2.3** Upon delivery of the message to the destination telex subscriber, the MSSFU, if requested by the originating MES, should provide a Positive Delivery Notification (PDN) to the MES. In the event of non-delivery of the message to the destination telex subscriber, it is an INMARSAT requirement of the MSSFU to provide a Non-Delivery Notification (NDN) to the MES. The manner in which these notifications are provided to the MES is not the subject for international standardization.
+
+### **5.3 MES-to-MES calls utilizing the international telex service**
+
+**5.3.1** Subscribers to the Mobile Satellite service provided by the INMARSAT-C system may send messages to another MES.
+
+**5.3.2** Where the call is to an MES in another satellite region and the call is carried by the international telex service, the procedures to be followed should be in accordance with 5.2.
+
+The procedures to be adopted where the destination MSSFU does not support a one-stage selection method on calls from the international telex service are for further study.
+
+**5.3.3** The procedures for calls between MESs in the same satellite region or in satellite regions served by the same Land Earth Station (LES), are not the subject for international standardization.
+
+## **Annex A**
+
+### **Alphabetical list of abbreviations used in this Recommendation**
+
+EOA End-of-Address
+
+EOM End-of-Message
+
+EOT End-of-Transmission
+
+ITD Input Transaction accepted for Delivery  
+LES Land Earth Station  
+MES Mobile Earth Station  
+MSSFU Mobile Satellite Store-and-Forward Unit  
+NDN Non-Delivery Notification  
+PDN Positive Delivery Notification  
+TAED Telex Automatic Emitting Device
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Telephone network and ISDN
+- Series F Non-telephone telecommunication services**
+- Series G Transmission systems and media
+- Series H Transmission of non-telephone signals
+- Series I Integrated services digital network
+- Series J Transmission of sound-programme and television signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound-programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality
+- Series Q Switching and signalling
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminal equipments and protocols for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages

marked/F/T-REC-F.141-199406-I_PDF-E/raw.md

@@ -0,0 +1,154 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**F.141**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+(06/94)
+
+**OPERATIONS AND QUALITY OF SERVICE  
+MOBILE SERVICE**
+
+---
+
+**INTERNATIONAL TWO-WAY MULTIPOINT  
+TELECOMMUNICATION SERVICE  
+VIA SATELLITE**
+
+**ITU-T Recommendation F.141**
+
+(Previously "CCITT Recommendation")
+
+---
+
+# FOREWORD
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations 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.141 was prepared by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 1st of June 1994.
+
+---
+
+# NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+|                                                    | <i>Page</i> |
+|----------------------------------------------------|-------------|
+| 1 Scope .....                                      | 1           |
+| 1.1 Definition of service .....                    | 1           |
+| 2 Service description .....                        | 1           |
+| 2.1 Functional elements of service provision ..... | 1           |
+| 2.2 Service provision .....                        | 1           |
+| 2.3 Types of service .....                         | 1           |
+| 2.4 Area of service .....                          | 1           |
+| 2.5 Service configuration .....                    | 2           |
+| 3 Quality of Service .....                         | 3           |
+| 4 Service availability .....                       | 3           |
+| 5 Class of space segment capacity .....            | 3           |
+
+# **SUMMARY**
+
+This Recommendation provides service and operational guidelines for the provision of international two-way multipoint telecommunication service via satellite.
+
+International two-way multipoint telecommunication service via satellite is defined as a service provided to customers by Recognized Operating Agencies (ROAs) for the two-way transmission of information via satellite, between a central facility and a multiplicity of points where transmit/receive earth stations are located.
+
+# INTERNATIONAL TWO-WAY MULTIPOINT TELECOMMUNICATION SERVICE VIA SATELLITE
+
+*(Geneva, 1994)*
+
+# 1 Scope
+
+This Recommendation provides operational guidelines and a service description including quality of service requirements for international two-way multipoint telecommunication service via satellite.
+
+## 1.1 Definition of service
+
+**international two-way multipoint telecommunication service via satellite** is defined as a service provided to customers by Recognized Operating Agencies (ROAs) for the two-way transmission of information via satellite, between a central facility and a multiplicity of points where transmit/receive earth stations are located.
+
+# 2 Service description
+
+## 2.1 Functional elements of service provision
+
+An international two-way multipoint telecommunication service via satellite generally includes the following nine elements (see Figure 1):
+
+- 1) the customer central facility equipment;
+- 2) the links between the customer central facility equipment and the service provider command and control management centre;
+- 3) the service provider command and control management centre;
+- 4) the link between the master earth station and the service provider command and control management centre;
+- 5) the master earth station (hub);
+- 6) the space segment capacity;
+- 7) the remote earth station antennas;
+- 8) the link between transmit/receive remote earth station antenna and user terminal equipment;
+- 9) the user terminal equipment.
+
+## 2.2 Service provision
+
+The service may be provided on either a full-time (24-hour) basis, a scheduled part-time basis or an occasional basis. Where the hub and one or more of the remote earth stations are in different countries, the provision of service is governed by the appropriate national and international regulations and subject to agreement between the ROAs. The ROA in each country should be made aware of their scope of the service coverage and the traffic routing capabilities.
+
+## 2.3 Types of service
+
+The service may be digital or analogue, provided in the form of inbound (remote to hub) and outbound (hub to remote) channels at rates depending on the application and within the capacity available. The data rates, bandwidths, and frequencies of the outbound channels and those of the inbound channels may be different.
+
+## 2.4 Area of service
+
+The service may be provided on a national and/or international basis in accordance with relevant national regulatory requirements.
+
+## 2.5 Service configuration
+
+2.5.1 As illustrated in Figure 1, there are generally nine functional elements in the provision of an international two-way multipoint telecommunication service via satellite.
+
+![Diagram of international two-way multipoint telecommunication service via satellite showing functional elements 1 through 9.](f6d72d7c790e7f585532140f3971639a_img.jpg)
+
+The diagram illustrates the functional elements of an international two-way multipoint telecommunication service via satellite. It is divided into three main sections: Customer Central Facility (1), Service Provider Command and Control Management Centre (3), and Remote E.S. (7, 8, 9) for three different customers (A, B, and C). The central part of the diagram shows the 'Space segment' containing a satellite (6) and a 'Master E.S.' (5). The 'Service Provider Command and Control Management Centre' contains a 'Protocol Conversion Multiplexing Addressing Network Control Master ES TE' (4). The 'Customer Central Facility' (1) contains three 'Customer' units (2). Arrows indicate the flow of communication: from the Customer Central Facility to the Service Provider Command and Control Management Centre, from the Service Provider Command and Control Management Centre to the Master E.S., from the Master E.S. to the Space segment, and from the Space segment to each of the Remote E.S. units. Each Remote E.S. unit contains three 'User TE' units (8) connected to a 'Remote E.S.' (7). The diagram is labeled 'T0103400-94/d01' in the bottom right corner.
+
+Diagram of international two-way multipoint telecommunication service via satellite showing functional elements 1 through 9.
+
+FIGURE 1/F.141  
+International two-way multipoint telecommunication service via satellite
+
+2.5.2 Owing to the need for flexibility, the service may be adapted to meet a variety of requirements taking into account the regulations governing the operation of the space segment providers and ROAs involved.
+
+2.5.3 Subject to national regulatory arrangements, interconnection may be offered with the public switched network, a customer's private network and/or by other arrangements designed to meet specific customer requirements.
+
+2.5.4 The two-way operation is in a star configuration enabling communications between several remote locations and the hub, and communications among remote locations through the hub. The two-way operation can be achieved under proven multiple access procedures, such as those defined in G-, M-, and N-Series Recommendations.
+
+2.5.5 The master hub, consisting of a master earth station and a service provider command and control management centre, may be dedicated to a single customer or may be shared by a number of customers; it may be located either on a customer's site or may be remotely connected.
+
+2.5.6 The conditions for use of the master earth station (5), the remote transmit/receive earth stations (7), the service provider command and control management centre (3) and the links (2, 4) are a national matter.
+
+2.5.7 The conditions for the use of the space segment capacity (6) are defined by the satellite system space segment providers.
+
+2.5.8 The remote transmit/receive earth stations (7) would normally be located at the user premises near the user equipment; but the user equipment may also be remotely connected by a link (8) to the transmit/receive earth stations.
+
+# 3 Quality of Service
+
+The efficiency of operation and therefore the quality of service provided to the customers are linked to the relationship of all parties which contribute to the provision of the service, i.e. the technical equipment and the entities in charge of the operation.
+
+# 4 Service availability
+
+The service availability, as defined in CCITT Recommendation X.140, is the ratio of aggregate time, during which satisfactory or tolerable service is or could be provided, to the total observation period. Service availability depends on the class of space segment capacity, the earth station configuration and interference effects, and the bit error rate required. It is not possible to specify a service availability requirement for all two-way multipoint telecommunication services implementations via satellite. The availability for each implementation will have to be calculated on an individual basis considering all the points mentioned above.
+
+# 5 Class of space segment capacity
+
+Services offered may take account of classes of space segment capacity available from the space segment provider. The following classes of space segment capacity may be utilized to provide services:
+
+- a) *Non-pre-emptible* – A service which may not be interrupted or terminated for the provision of a service to another customer. There are two types of non-pre-emptible services:
+  - 1) *protected* – A service for which restoration is guaranteed; and
+  - 2) *unprotected* – A service for which restoration is not guaranteed and which may only be restored subject to availability of an alternate facility.
+- b) *Pre-emptible* – A service which may be interrupted to provide a service of higher priority.

marked/F/T-REC-F.150-199110-I_PDF-E/raw.md

@@ -0,0 +1,198 @@
+
+
+![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**CCITT**
+
+**F.150**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+**TELEGRAPH AND MOBILE SERVICES  
+OPERATIONS AND QUALITY OF SERVICE**
+
+---
+
+**SERVICE AND OPERATIONAL  
+PROVISIONS FOR THE  
+INTEX SERVICE**
+
+**Recommendation F.150**
+
+---
+
+![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+Geneva, 1991
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.150 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 11th of October 1991.
+
+## --- CCITT NOTES
+
+- 1) In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
+- 2) A list of abbreviations used in this Recommendation can be found in Annex A.
+
+## **Recommendation F.150**
+
+# **SERVICE AND OPERATIONAL PROVISIONS FOR THE INTEX<sup>1)</sup> SERVICE**
+
+## **1 Introduction**
+
+1.1 With the continuing development of the infrastructures of the networks which currently support, amongst others, the international telex service, it is feasible that some of these networks could support other services operating at speeds in excess of 50 bauds and using character sets other than those of International Telegraph Alphabet No. 2 (ITA2). There may be benefits to both customer and Administrations if a new text service could be introduced that would utilize the same network infrastructure as the international telex service.
+
+## **2 Scope**
+
+2.1 This Recommendation sets out the service and operational principles for the introduction of a new text service, initially operating asynchronously at 300 bit/s and using International Alphabet No. 5 (IA5).
+
+## **3 Service outline**
+
+3.1 This service will be real-time circuit switched and provide asynchronous operation with a basic transmission rate of 300 bit/s. The use of other transmission rates at a future date is for further study.
+
+3.2 The service will be half-duplex in its normal mode (see § 4.5) but will allow for full duplex operation in the transparent mode (see § 4.8).
+
+3.3 The Intex service will use the destination codes detailed in Recommendation F.69.
+
+3.4 It is recommended that the national numbering scheme for the Intex service be similar to and compatible with that used for the international telex service.
+
+## **4 Service description**
+
+4.1 Call set up procedures should be in accordance with the relevant Recommendations.
+
+4.2 To allow maximum flexibility of use of the service and to ensure the compatibility of terminals interworking at the higher speed, four separate operating modes may be provided. These are normal mode, telex interworking mode, extended mode and transparent mode. As a minimum, normal and telex interworking mode should be provided, with the choice of operating in three modes, other than telex interworking, being a customer option on a call-by-call basis, or within a call.
+
+4.3 At the beginning of any incoming or outgoing call an Intex terminal shall always default to the normal mode.
+
+4.4 Character sets, structure and procedures for generating mode changes should generally be in accordance with the relevant CCITT Recommendation.
+
+---
+
+1) The use of the name Intex is conditional on its being freely available in Member countries and hence the name of the service offered may vary from country to country.
+
+### 4.5 *Normal mode*
+
+Normal mode is the mode of the basic Intex call for the exchange of text. There is no need for any prearrangement or pre-knowledge with regard to the capabilities of the called terminal over and above that of normal mode functions. The character set in this mode shall be derived from the International Alphabet No. 5 in accordance with Recommendation S.34.
+
+### 4.6 *Telex interworking mode*
+
+Telex interworking mode is intended for interworking with the international telex service (see § 7). This mode may be invoked at the start of a call where it is known that the called party is a terminal participating in the international telex service or it will be entered into automatically where the call is found to terminate on such a terminal and the service identifier **TLX** will be indicated at the Intex terminal.
+
+When the call is established in manual mode, the Intex operator should be informed if a previously-prepared message contains non-ITA2 characters. The procedures to be applied for automatic call set-up in the case where the Intex operator is not aware of the characteristics of the called party terminal are for further study.
+
+### 4.7 *Extended mode*
+
+Extended mode allows for the exchange of messages using the full character set of International Alphabet No. 5 in accordance with Recommendation T.50. This mode shall only be used when it has been established that it is supported by both terminals.
+
+### 4.8 *Transparent mode*
+
+In the transparent mode the character set to be used is defined by the customers involved in the call, subject only to the restriction on character structure within the network used. This mode shall only be used when it has been established that it is supported by both terminals.
+
+## 5 Answerback composition
+
+5.1 The Intex service shall employ the principle of the exchange of answerbacks, resident in the terminals and under the control of the service provider. The composition of the answerbacks for the Intex service must facilitate interworking, especially with the international telex service where many terminals employ answerback checking mechanisms based on format and length as well as content.
+
+5.2 Intex answerbacks shall include:
+
+- a) the customer's national number;
+- b) the terminal identity letter or letters (if required);
+- c) an abbreviated name designating the customer;
+- d) the identification code, equivalent to the telex network identification code (TNIC) as specified in Recommendation F.69, preceded by a space character.
+
+5.3 The Intex answerback shall comprise a sequence of 20 IA5 characters, formatted in accordance with Recommendation S.35, as follows:
+
+- a) for terminals without identification letters:
+  - character US (unit separator);
+  - carriage return;
+
+- line feed;
+  - numeric characters representing the national number of the customer;
+  - character RS (record separator);
+  - space;
+  - alpha characters indicating the name of the customer;
+  - space;
+  - one or two characters representing the network identification code;
+  - character RS;
+- b) for terminals with identification letters:
+- character US;
+  - carriage return;
+  - line feed;
+  - numeric characters representing the national number of the customer;
+  - character RS;
+  - one or two alpha characters identifying the terminal;
+  - space;
+  - alpha characters indicating the name of the customer;
+  - space;
+  - one or two characters representing the network identification code;
+  - character RS;
+- c) for terminals without identification letters and whose answerback code does not include letters indicating the name of the customer:
+- character US;
+  - carriage return;
+  - line feed;
+  - numeric characters representing the national number of the customer;
+  - character RS;
+  - space;
+  - one or two characters representing the network identification code;
+  - character RS;
+- d) for terminals with identification letters and whose answerback code does not include letters indicating the name of the customer:
+- character US;
+  - carriage return;
+  - line feed;
+  - numeric characters representing the national number of the customer;
+  - character RS;
+  - one or two alpha characters identifying the terminal;
+  - space;
+
+- one or two characters representing the network identification code;
+- character RS;
+- e) for terminals providing mailbox or similar store and retrieval facilities:
+  - character US;
+  - carriage return;
+  - line feed;
+  - numeric characters representing the national number of the customer;
+  - = (“equals” sign);
+  - character RS;
+  - two alpha characters identifying the mailbox;
+  - space;
+  - one or two characters representing the network identification code;
+  - character RS.
+
+If the signals in the answerback code do not fill all the 20 places available, the unused places shall be filled by the necessary number of characters RS inserted before the network identification code.
+
+5.4 The alpha fields of Intex answerbacks shall comprise either upper- or lower case latin letters, but not mixed.
+
+5.5 Intex answerbacks, when subjected to the code conversion rules applied by networks, should result in answerback formats compatible with the requirements of the service with which Intex is interworking.
+
+## 6 Operations
+
+6.1 International interconnection of Intex services should be agreed bilaterally.
+
+6.2 International signalling and information transfer procedures should be in accordance with the relevant CCITT Recommendations.
+
+## 7 Interworking with the international telex service
+
+7.1 Interworking with the international telex service should be in accordance with Recommendation F.82.
+
+## ANNEX A (to Recommendation F.150)
+
+### Alphabetical list of abbreviations used in this Recommendation
+
+|      |                                        |
+|------|----------------------------------------|
+| IA5  | International Alphabet No. 5           |
+| ITA2 | International Telegraph Alphabet No. 2 |
+| RS   | Record separator                       |
+| TNIC | Telex network identification code      |
+| US   | Unit separator                         |

marked/F/T-REC-F.16-199502-I_PDF-E/raw.md

@@ -0,0 +1,855 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the center.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.16**
+
+(02/95)
+
+**OPERATIONS AND QUALITY OF SERVICE  
+TELEGRAPH SERVICES**
+
+---
+
+**GLOBAL VIRTUAL NETWORK SERVICE**
+
+**ITU-T Recommendation F.16**
+
+(Previously "CCITT Recommendation")
+
+---
+
+# **FOREWORD**
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations 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.16 was prepared by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 21st of February 1995.
+
+# --- **NOTE**
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+# CONTENTS
+
+Page
+
+|     |                                                                    |    |
+|-----|--------------------------------------------------------------------|----|
+| 1   | Definition .....                                                   | 1  |
+| 1.1 | Scope .....                                                        | 1  |
+| 1.2 | References.....                                                    | 1  |
+| 1.3 | Definitions .....                                                  | 1  |
+| 1.4 | Abbreviations.....                                                 | 4  |
+| 2   | Description .....                                                  | 4  |
+| 2.1 | General description.....                                           | 4  |
+| 2.2 | GVNS access .....                                                  | 4  |
+| 2.3 | GVNS calling.....                                                  | 6  |
+| 2.4 | GVNS features description.....                                     | 6  |
+| 2.5 | GVNS operation, administration, maintenance and provisioning ..... | 7  |
+| 2.6 | Applicability .....                                                | 8  |
+| 3   | Procedures.....                                                    | 8  |
+| 3.1 | Provision/withdrawal .....                                         | 8  |
+| 3.2 | Normal procedures.....                                             | 8  |
+| 3.3 | Exceptional procedures.....                                        | 8  |
+| 3.4 | Alternate procedures .....                                         | 8  |
+| 4   | Network capabilities for charging .....                            | 9  |
+| 5   | Interworking requirements .....                                    | 9  |
+| 5.1 | Interworking with non-ISDN networks .....                          | 9  |
+| 5.2 | Interworking with the private networks (non-ISDN and ISDN) .....   | 9  |
+| 6   | Interactions with supplementary services.....                      | 9  |
+| 6.1 | Number related supplementary services .....                        | 9  |
+| 6.2 | Community of interest supplementary services .....                 | 10 |
+| 6.3 | Charging supplementary services .....                              | 10 |
+| 6.4 | Other supplementary services .....                                 | 10 |
+| 7   | SDL diagrams.....                                                  | 10 |
+
+# **SUMMARY**
+
+The Global Virtual Network Service (GVNS) is a multi-network international service which provides private network functions to users at geographically dispersed international locations while minimizing the need for dedicated network resources. It may be offered to customers over the PSTN and/or ISDN.
+
+# **INTRODUCTION**
+
+This Recommendation focuses on how interworking service providers can provide the seamless Global Virtual Network Service (GVNS). It presents the service description of GVNS that supports global virtual networking. The GVNS is described here from the user's point of view and is characterized by a prose service definition description in accordance with Recommendation I.130.
+
+# GLOBAL VIRTUAL NETWORK SERVICE
+
+(Geneva, 1994)
+
+# 1 Definition
+
+The **Global Virtual Network Service (GVNS)** is a multi-network international service which provides private network functions to users at geographically dispersed international locations while minimizing the need for dedicated network resources. It may be offered to customers over the PSTN and/or ISDN.
+
+The Global Virtual Network Service is a feature-rich communications service. It provides the functions typically associated with the private networks (see 1.3.10), but utilizing the public switched network(s). The GVNS Customer's network configuration is defined per the customer's direction using customer-specific service information resident in multiple networks. The network configurations may be administered by the GVNS Customer directly, the GVNS Participating Service Provider(s) and/or the GVNS Coordinator(s) (see 1.3.11 and 1.3.12).
+
+The GVNS provides the customers with global services as a result of internetworking among the GVNS Participating Service Providers in various countries. GVNS may accommodate this interconnection both via ISDN and non-ISDN facilities.
+
+## 1.1 Scope
+
+This Recommendation contains the service description of GVNS for the PSTN and ISDN. This Recommendation defines the service from a user's perspective. This Recommendation does not specify the requirements where the service is provided to the user by the private networks; however, it addresses the interworking requirements with private networks.
+
+This Recommendation is the Stage 1 service description for the ISDN and is applicable to the ISDN Stages 2 and 3 Recommendations for GVNS. The terms Stages 1, 2 and 3 are defined in CCITT Recommendation I.130.
+
+## 1.2 References
+
+The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- CCITT Recommendation I.130 (1988), *Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN*.
+- ITU-T Recommendation I.112 (1993), *Vocabulary of terms for ISDNs*.
+- ITU-T Recommendation I.210 (1993), *Principles of telecommunication services supported by an ISDN and the means to describe them*.
+- ITU-T Recommendation Z.100 (1993), *CCITT specification and description language (SDL)*.
+
+## 1.3 Definitions
+
+**1.3.1 GVNS customer:** A **GVNS Customer (e.g. a person or an organization)** is the entity that purchases the service (e.g. the telecommunication manager of a corporation). The GVNS Customer functions as an interface between the GVNS Service Provider(s) and the GVNS Users. The GVNS Customer can define aspects of the service; for example, the on-net locations, numbering plan, and/or the calling privileges of the GVNS Users.
+
+**1.3.2 GVNS user:** A **GVNS User** is the end-user of the service. Typically, GVNS Users are not allowed to change their calling privileges.
+
+**1.3.3 on-net locations:** These are stations, user-network interfaces and authorized remote access locations that are logically defined by the GVNS Customer to be part of its virtual network during service provisioning or remote access (see 2.2.2.3).
+
+GVNS Customers may define a physical entity (station or user network interface) as multiple on-net locations during service provisioning. As a result, one physical entity may be registered to one or more GVNS User Groups.
+
+The relationship between the logical virtual networks and the physical networks is depicted in Figure 1.
+
+**1.3.4 off-net locations:** These are stations and user-network interfaces that are not defined by the GVNS Customer to be part of the GVNS. In some cases, a customer may define off-net locations as part of its customer-defined numbering plan. Such locations are termed as virtual on-net locations.
+
+**1.3.5 virtual on-net locations:** These are off-net locations included in the customer-defined numbering plan. The numbers that are defined in the numbering plan to reach to these off-net locations may be subject to GVNS-specific treatments (e.g. Call Screening).
+
+**1.3.6 GVNS calls:** GVNS Calls are calls from an on-net location. It may terminate to an on-net, off-net, or virtual on-net location. GVNS Calls include the following two types of calls:
+
+### – *On-net Calls:*
+
+An On-net Call is a call from an on-net location to another on-net location of the same GVNS User Group.
+
+### – *Off-net Calls:*
+
+An Off-net Call is a call from an on-net location to an off-net location. These calls can be specified with a customer-defined number (to a virtual on-net location) or as a public number.
+
+**1.3.7 GVNS user group and subgroup:** A GVNS user group is made up of a group of on-net locations defined by the GVNS Customer (including authorized remote access locations, see 2.2.2.3).
+
+A GVNS Customer may optionally define GVNS subgroups when they are offered by the GVNS Participating Service Provider. A GVNS subgroup is made up of a subset of the locations defined by the GVNS Customer as on-net locations (including authorized remote access locations). An on-net location belongs to one and only one GVNS subgroup. Subgroup identification is required to support subnetworking (see 2.4.8). The relationship between the user group and subgroups is depicted in Figure 1.
+
+**1.3.8 GVNS user group and subgroup identifier:** A GVNS user group is assigned a unique GVNS user group identifier to identify a group among supporting networks. The subgroup identifier uniquely identifies a group of users within a customer's GVNS user group, and has meaning only within that user group.
+
+**1.3.9 numbering plan:** A GVNS Customer has a numbering plan which associates addresses with locations in the GVNS (on-net addresses). These numbers may be public numbers or customer-defined (private). The GVNS Customers may also define private numbers to identify off-net addresses. When a GVNS Customer uses customer-defined numbers, the capabilities may include, but are not limited to those of the Support of Private Numbering Plans supplementary service. These capabilities are defined by each GVNS Participating Service Provider.
+
+**1.3.10 private network functions:** Private network functions include those provided by dedicated private networks and dedicated business groups. The private network functionality can be customer based (e.g. PBX), network based (e.g. business group) or a combination of both.
+
+**1.3.11 GVNS participating service provider:** The GVNS Participating Service Provider is a ROA that provides customer access and egress to and from the GVNS. The GVNS Participating Service Provider optionally offers the features defined in 2.4 on a national and/or international basis. The interworking of such services between ROAs in multiple countries creates the GVNS offering.
+
+![Diagram showing four virtual networks: User group W, User group X, User group Y, and User group Z. User group W contains Subgroup W1 (A1.A5.B1, B2.C2.C3, C4) and Subgroup W2 (A2.B4.B5, B6.C1). User group X contains Subgroup X1 (C5.C6.C7.A8) and Subgroup X2 (A4.B3.B7, A3.A6.A7). User group Y contains A8.B8.C8.C9. User group Z contains A9.B9.B10.](fc46871d72c65d3381d9201646d23439_img.jpg)
+
+Virtual (logical) networks
+
+Diagram showing four virtual networks: User group W, User group X, User group Y, and User group Z. User group W contains Subgroup W1 (A1.A5.B1, B2.C2.C3, C4) and Subgroup W2 (A2.B4.B5, B6.C1). User group X contains Subgroup X1 (C5.C6.C7.A8) and Subgroup X2 (A4.B3.B7, A3.A6.A7). User group Y contains A8.B8.C8.C9. User group Z contains A9.B9.B10.
+
+![Diagram showing three physical networks: Network A, Network B, and Network C. Network A has connections A1, A2, A3, A4, A5, A6, A7, A8, A9. Network B has connections B1, B2, B3, B4, B5, B6, B7, B8, B9, B10. Network C has connections C1, C2, C3, C4, C5, C6, C7, C8, C9. Connection A8 is shared between Network A and Network C.](1956f44611abd5c3c41049836aa78ad8_img.jpg)
+
+Physical networks (GVNS Participating Networks)
+
+Diagram showing three physical networks: Network A, Network B, and Network C. Network A has connections A1, A2, A3, A4, A5, A6, A7, A8, A9. Network B has connections B1, B2, B3, B4, B5, B6, B7, B8, B9, B10. Network C has connections C1, C2, C3, C4, C5, C6, C7, C8, C9. Connection A8 is shared between Network A and Network C.
+
+T0102660-92/d01
+
+User Group W  
+Subgroup W1  
+Subgroup W2  
+  
+User Group X  
+Subgroup X1  
+Subgroup X2
+
+User Group Y  
+No Subgroups  
+  
+User Group Z  
+No Subgroups
+
+GVNS participating service provider for W = A, B, C  
+ GVNS participating service provider for X = A, B, C  
+ GVNS participating service provider for Y = C, A, B  
+ GVNS participating service provider for Z = B, A  
+ A1 ... B9 = physical connections to Network A  
+ B1 ... B10 = physical connections to Network B  
+ C1 ... C9 = physical connections to Network C  
+ A8 = one physical connection belonging to two user groups (X and Y)
+
+FIGURE 1/F.16  
+**GVNS user groups and subgroups**
+
+**1.3.12 GVNS coordinator:** One or more GVNS Coordinators may be elected by the GVNS Customer to provide and arrange with other ROAs (GVNS Participating Service Providers) the provision of GVNS.
+
+The GVNS Coordinator(s) will arrange customers ordering, provisioning, and billing procedures currently undertaken by each GVNS Participating Service Provider for the establishment and ongoing provision of GVNS.
+
+## 1.4 Abbreviations
+
+|       |                                                         |
+|-------|---------------------------------------------------------|
+| CLI   | Calling Line Identification                             |
+| GVNS  | Global Virtual Network Service                          |
+| ISDN  | Integrated Services Digital Network                     |
+| PBX   | Private Branch Exchange                                 |
+| PIN   | Personal Identification Number                          |
+| OAM&P | Operation, Administration, Maintenance and Provisioning |
+| PSTN  | Public Switched Telephone Network                       |
+| ROA   | Recognized Operating Agency                             |
+| SDL   | Specification and Description Language                  |
+
+# 2 Description
+
+## 2.1 General description
+
+The GVNS allows service providers to offer subscribing customers a service with the features and functionality similar to that of a private network while minimizing the need for dedicated network resources. However, dedicated network resources may be used to access GVNS or in conjunction with GVNS.
+
+A GVNS Customer may optionally elect one or more GVNS Coordinators to provide one or more of the following functions:
+
+- a) Single End Service Ordering;
+- b) Single End Fault Reporting;
+- c) Maintenance Coordination;
+- d) Configuration Management;
+- e) Network Management Reporting Tools.
+
+A GVNS Customer is assigned a unique identifier which identifies the global GVNS User Group (see 1.3.7). GVNS User Group identification provides a means by which various networks can recognize the GVNS Customer.
+
+A GVNS Customer may choose to group users into one or more subgroups (see 1.3.7) in order to allow subgroup dependent service interactions and operations.
+
+GVNS users can be located in one or more networks, and may interwork with private network resources.
+
+A variety of routing privileges may be assigned to GVNS calls. GVNS users can make calls to other users within their GVNS and to non-GVNS users. GVNS calls can also be made from non-GVNS locations. At the customer's request, appropriate verification of the calling party may be required.
+
+## 2.2 GVNS access
+
+Dependent upon GVNS Participating Service Provider capabilities, the customer can choose from various user access procedures and physical access arrangements.
+
+### **2.2.1 User access procedures**
+
+Based upon the GVNS Participating Service Provider capabilities, the customer can choose either direct or indirect access to the GVNS.
+
+#### **2.2.1.1 Direct access**
+
+This type of access allows the user to reach the GVNS without providing any code(s). This is only possible from on-net locations if the network recognizes the GVNS location by performing Calling Line Identification (CLI) screening or using another automatic mechanism (e.g. physical network connection).
+
+An example of User Access Procedures:
+
+- a) the GVNS user lifts the handset and waits for network response;
+- b) the network sends an acknowledgement (e.g. dial tone);
+- c) depending upon customer requirements, the user may be required to provide an authorization code and the network sends an acknowledgement to the user;
+- d) the user is now connected to the GVNS and can use the service features available.
+
+If the GVNS location from which the user accesses its GVNS is a PBX extension, the procedure could change in a way that is PBX dependent (e.g. dialling a prefix).
+
+#### **2.2.1.2 Indirect access**
+
+This type of access allows the GVNS user to reach its GVNS by providing a service access code and/or authorization code. This type of access is available both from on-net and off-net locations.
+
+##### **2.2.1.2.1 Indirect access from on-net locations**
+
+When indirect access is used from an on-net location, the user is only required to provide a service access code. The network recognizes the GVNS location by CLI screening or using another automatic mechanism (e.g. physical network connection).
+
+An example of User Access Procedures:
+
+- a) the GVNS user lifts the handset and waits for a network response;
+- b) the network sends a network acknowledgement;
+- c) the user provides a service access code;
+- d) the network sends another network acknowledgement;
+- e) depending upon customer requirement, the user may be required to provide an authorization code and the network sends an acknowledgement to the user;
+- f) the user is now connected to the GVNS and can use the service features available.
+
+##### **2.2.1.2.2 Indirect access from off-net locations**
+
+When indirect access is used from an off-net location (see Remote Access 2.2.2.3), the network cannot identify the user via CLI or another automated mechanism. Therefore, the user is required to provide both a Remote Access Number and an authorization code. The user privileges and network authentication are based upon the authorization code.
+
+An example of User Access Procedures:
+
+- a) the GVNS user lifts the handset and waits for a network response;
+- b) the network sends a network acknowledgement;
+- c) the Remote Access Number (e.g. a public number) is provided by the user;
+- d) an indication is provided to guide the caller to provide an authorization code;
+- e) the authorization code is provided.
+
+Depending upon the GVNS Participating Network Provider's implementation, the authorization code may be a single set of digits or split (e.g. separate network prompts for authorization code and PIN);
+
+- f) the network informs the user by means of tone(s), announcement(s), and/or other mechanisms that indicate access to the GVNS has been successful.
+
+### **2.2.2 Physical access arrangements**
+
+Dependent upon GVNS Participating Service Provider capability, the customer can choose from various Dedicated, Switched and Remote Access arrangements to receive the features and functions of the GVNS.
+
+#### **2.2.2.1 Dedicated access**
+
+Dedicated access is a physical connection from the user to a network that supports the relevant GVNS for only one GVNS Customer. If the GVNS for only one GVNS Customer uses the same dedicated access for more than one service, the user may need to dial a special code (e.g. prefix or access code) to identify GVNS calls.
+
+#### **2.2.2.2 Switched access**
+
+Switched access is a switched connection from the user to a GVNS via one or more networks on which:
+
+- a) the particular GVNS is not supported; and
+- b) the circuits to the GVNS Participating Service Provider carry the GVNS traffic of various GVNS User Groups and possibly non-GVNS traffic.
+
+The user may need to dial a special code (e.g. prefix or access code) to identify the desired GVNS Participating Service Provider. The availability of Calling Line Identification (network provided or network verified) is necessary to provide authorized access to the GVNS.
+
+#### **2.2.2.3 Remote access**
+
+Remote access can be used to make GVNS calls from locations not identified as part of the GVNS at service provisioning. The caller makes a call to a Remote Access Number (e.g. public number or service code) and, optionally, provides an authorization code. Either the Remote Access Number or the authorization code provides authorized access to the GVNS. Once a non-GVNS location receives authorized access from a GVNS participating service provider, it becomes an on-net location (authorized remote access location, see 1.3.3).
+
+## **2.3 GVNS calling**
+
+All calls made from an on-net location may terminate on an on-net, off-net, or virtual on-net location. If terminating on an on-net location, it could be done via dedicated or a switched access. The user may provide a customer-defined or a public number to reach on-net, off-net or virtual on-net locations.
+
+## **2.4 GVNS features description**
+
+A GVNS Participating Service Provider may support one or more of the following optional features. The GVNS Participating Service Providers will interwork their systems and procedures to provide GVNS features for customers in multiple countries.
+
+### **2.4.1 Call screening**
+
+The GVNS Customer can define call screening to determine what type of calls are allowed from on-net or remote access locations. This may include, but is not limited to, restrictions such as, allow private number dialled calls only, or allow all private number and public number calls in a particular country only.
+
+Call screening is also a mechanism which may be used by the GVNS Customer to restrict GVNS users access and/or calling privileges.
+
+### **2.4.2 Customer-defined numbering**
+
+GVNS allows the customer to define a private numbering plan for some or all of their dialling needs. The number of digits sent and received between the customer's equipment and the GVNS service point will be at the customer's discretion, within a given range, specified by each GVNS Participating Service Provider. The GVNS Customers should have the capability to define an on-net location with a customer-defined private number or a public number.
+
+### **2.4.3 Private network interface**
+
+The GVNS Customers should be able to interconnect with their private network(s) using GVNS. The GVNS must be able to communicate to and from the customer's private network(s) (see 5.2).
+
+### **2.4.4 Standard announcements**
+
+General and network announcements are to be provided when appropriate for GVNS calls. A verbal announcement may be played when a certain predefined condition occurs (e.g. "All circuits are busy" at the general level; "You are not authorized to dial this number" at the network level).
+
+### **2.4.5 Customized announcements**
+
+A GVNS Customer can select a particular announcement to the caller given the dialled digits or any of several intercept conditions (e.g. "Welcome to XYZ company's private network"). The customer sets up the routing to the announcements. The customized announcements capability may have the flexibility to support multiple messages in different languages and countries.
+
+### **2.4.6 Authorization code**
+
+Authorization codes may be used by the GVNS Customer to identify whether the GVNS User has the authorization to place the call. Authorization codes may also be used to assign varying levels of functionality. As a GVNS Service Provider option, the calling party could place additional calls without requiring re-entry of the authorization code.
+
+### **2.4.7 Accounting code**
+
+The accounting code may be used by the user to identify an individual or group with which a GVNS call should be associated.
+
+### **2.4.8 Subnetworking (subgrouping)**
+
+A customer of the GVNS service may choose to group its users into subnetworks with their own access and routing restrictions. Optionally, each subnetwork may have its own numbering plan. The subnetworking provides the flexibility to the GVNS Customer by allowing its users to associate subnetworks with functional organizations, e.g. manufacturing, marketing, or with geographical locations.
+
+### **2.4.9 Direct termination overflow**
+
+If the dedicated access for the GVNS call termination is busy, the incoming call can overflow to another dedicated access, switched access, or to an announcement.
+
+## **2.5 GVNS operation, administration, maintenance and provisioning**
+
+The GVNS coordinator(s), if elected (see 1.3.12) will coordinate the Operation, Maintenance, Administration and Provisioning (OAM&P) aspects of the GVNS with the service providers involved in providing the service in multiple countries. The supporting networks should be able to identify the GVNS coordinator(s), i.e. the country and the network in order to provide some of the OAM&P functionalities, e.g. billing. Some examples of such OAM&P activities are listed below<sup>1)</sup>.
+
+### **2.5.1 Provisioning**
+
+This function provides means of order processing, provisioning and installing the GVNS service for the customer.
+
+### **2.5.2 Configuration management**
+
+The customer should be able to configure its GVNS according to its needs from domestic and international locations<sup>2)</sup>. The configuration management involves GVNS dialling plan changes, activation/deactivation of authorization codes, routing changes, etc.
+
+---
+
+1) The concept of Telecommunication Management Network (TMN) is in the M-Series Recommendations. The TMN embodies these OAM&P aspects. TMN would facilitate the customer being able to access one system for configuration management.
+
+2) The GVNS coordinator can also provide the configuration management capability on the customer's behalf.
+
+### **2.5.3 Performance monitoring**
+
+In order to properly monitor the performance of its GVNS, the customer should be able to obtain various traffic statistics, e.g. trunk group usage, originating/terminating traffic from/to a particular location. The GVNS coordinator or the customer may create reports based on these statistics. These reports could provide input for decisions to reconfigure and/or add additional resources to the GVNS.
+
+## **2.6 Applicability**
+
+This service is applicable to the PSTN and circuit mode bearer services in the ISDN.
+
+# **3 Procedures**
+
+Specific procedures for the provision and withdrawal of access methods (see 2.2) and features (see 2.4) could vary by GVNS Participating Service Providers and, therefore, are not defined below.
+
+## **3.1 Provision/withdrawal**
+
+The GVNS is provided to the customer by subscription. Provision and coordination of GVNS may be required in multiple networks depending on the location of the GVNS Users.
+
+## **3.2 Normal procedures**
+
+### **3.2.1 Activation/deactivation/registration**
+
+Activation, deactivation, and registration of GVNS may be performed by the GVNS Participating Service Providers and/or Coordinator(s) by arrangements with the customer. If the customer elects a GVNS Coordinator, the Coordinator may arrange activation, deactivation, and registration among the GVNS Participating Service Providers. The GVNS Participating Service Providers and/or Coordinator(s) and the customer can change the information relating to GVNS, e.g. on-net and off-net locations by following appropriate procedures.
+
+### **3.2.2 Invocation and operation**
+
+Depending upon the access arrangement (see 2.2.2), a GVNS User may be required to dial an access code, Remote Access Number, or Authorization Code which identifies the call as being a GVNS call. Optionally, the user only dials a customer-defined or public number. The network then, handles the call according to the customer-specific record stored in the network, (e.g. routes to the proper destination), and creates a record for billing, international accounting, and various reporting purposes. Call screening may be performed before the call is routed to ensure calling security and authorization.
+
+## **3.3 Exceptional procedures**
+
+If the call cannot be routed to the proper destination due to, e.g. unavailability of network resources, unauthorized access, an appropriate indication shall be returned to the calling user.
+
+### **3.3.1 Activation/deactivation/registration**
+
+None identified.
+
+### **3.3.2 Invocation and operation**
+
+None identified.
+
+## **3.4 Alternate procedures**
+
+None identified.
+
+# **4 Network capabilities for charging**
+
+The GVNS Participating Service Provider may choose to offer a call charge for GVNS which is different from other network charges as part of the GVNS service. The exact nature of the call charges is the subject of the D-Series Recommendations. In any case, the GVNS Participating Service Provider should record the relevant details in order to be able to charge the customer accurately for the service.
+
+# **5 Interworking requirements**
+
+## **5.1 Interworking with non-ISDN networks**
+
+If during interworking it is not possible to sustain the association of the call with the specific GVNS information, the call may still be allowed to proceed if the network has enough information to bill the call properly and the customer has chosen this treatment.
+
+## **5.2 Interworking with the private networks (non-ISDN and ISDN)**
+
+The GVNS Customers should be able to interconnect with their private network(s) using GVNS. The GVNS must be able to communicate to and from the customer's private network(s).
+
+The GVNS service provides the same features and functions to users directly connected to the public networks as to users connected via private networks. Locations connected to GVNS via private network(s) are not required to send or to receive additional information for GVNS calls over and beyond those required to initiate or to complete basic calls via PSTN or ISDN.
+
+Certain features and functions provided within the private networks may not be implemented on GVNS.
+
+# **6 Interactions with supplementary services**
+
+Interaction with the ISDN supplementary services defined in the I.250-Series Recommendations is described in this clause. The GVNS interactions for some of these supplementary services are defined below. Interactions with the remaining supplementary services are for further study.
+
+A description of the interaction with PSTN supplementary services is not possible as there are no descriptions that have been standardized on an international basis.
+
+A list of possible supplementary telephone services is contained in Supplement No. 1 of the CCITT *Blue Book*, Fascicle II.2.
+
+## **6.1 Number related supplementary services**
+
+### **6.1.1 Calling Line Identification Presentation**
+
+No customer-defined number will be provided to an off-net location.
+
+If a GVNS call is made to an off-net location (including to a virtual on-net location), the calling line identity is the public number. If no public number is available, the calling line identity will not be provided to the called user. If the call is forwarded to an on-net location, the customer-defined number is provided unless the customer specifies a public number.
+
+If a GVNS call is made to an on-net location, the calling line identity is the customer-defined number; however, if a public number is provided by the caller, the calling line identity is the public number. If the call is forwarded to another on-net location, the same calling line identity treatment is provided.
+
+### **6.1.2 Calling Line Identification Restriction**
+
+No impact.
+
+### **6.1.3 Connected Line Identification Presentation**
+
+No customer-defined number will be provided to an off-net location.
+
+If a GVNS call is made to a public number, the connected line identity is the public number. If the call is forwarded to another public number, that public number will be the connected line identity. If the call is forwarded to an on-net or virtual on-net location, the connected line identity is the customer-defined number of that location; however, if a public number is provided by the connecting user, the connected line identity is the public number.
+
+If a GVNS call is made to an on-net location or virtual on-net location, the connected line identity is the customer-defined number of that location; however, if a public number is provided by the connecting user, the connected line identity is the public number. If the call is forwarded to another on-net location, the connected line identity is the customer-defined number of that location; if the call is forwarded to a public number, the connected line identity is the public number of that location.
+
+### **6.1.4 Connected Line Identification Restriction**
+
+No impact.
+
+### **6.1.5 Sub-addressing**
+
+No impact. Subaddressing can be employed as an addition to the GVNS defined number.
+
+## **6.2 Community of interest supplementary services**
+
+### **6.2.1 Support of Private Numbering Plans**
+
+It is possible for the GVNS Customer to assign private numbers for all of their calling needs. Additional aspects are for further study.
+
+## **6.3 Charging supplementary services**
+
+### **6.3.1 Telecommunications Charge Card Service**
+
+It may be possible to make GVNS calls using a charge card. Additional aspects are for further study.
+
+## **6.4 Other supplementary services**
+
+### **6.4.1 User-to-User Signalling**
+
+No impact.
+
+# **7 SDL diagrams**
+
+Figures 2 and 3 specify the dynamic description of GVNS Stage 1 using graphic means.
+
+Process GVNS User
+
+![SDL diagram for user's view of GVNS. The process starts with a note about the calling party being a GVNS user who sends a service request. It then enters a state, sends a GVNS Request to Network (linked to section 3.2.2), and waits for a response. The response can be a Dialled Number Request, Authorization Code Request, Account Code Request, or Interim Calling User Call Set-up Success. The first three lead to corresponding network responses and then back to a waiting state. The fourth leads to the GVNS Active state.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> State1
+    State1 --> GVNS_Request_to_Network : GVNS Request to Network [ See 3.2.2 ]
+    GVNS_Request_to_Network --> Waiting1 : Waiting for GVNS Response
+    Waiting1 --> Dialled_Number_Request_From_Network : Dialled Number Request From Network
+    Waiting1 --> Authorization_Code_Request_from_Network : Authorization Code Request from Network
+    Waiting1 --> Account_Code_Request_from_Network : Account Code Request from Network
+    Waiting1 --> Interim_Calling_User_Call_Set-up_Success : Interim Calling User Call Set-up Success
+    Dialled_Number_Request_From_Network --> Dialled_Number_to_Network : Dialled Number to Network
+    Authorization_Code_Request_from_Network --> Authorization_Code_to_Network : Authorization Code to Network
+    Account_Code_Request_from_Network --> Account_Code_to_Network : Account Code to Network
+    Dialled_Number_to_Network --> Waiting2 : Waiting for GVNS Response
+    Authorization_Code_to_Network --> Waiting2
+    Account_Code_to_Network --> Waiting2
+    Interim_Calling_User_Call_Set-up_Success --> GVNS_Active : GVNS Active
+    note left of State1 : /* Calling party is a GVNS User
+    The user knows the type of access being used and sends the appropriate GVNS service request.
+    */
+    note right of GVNS_Request_to_Network : T0104310-95/d02
+  
+```
+
+SDL diagram for user's view of GVNS. The process starts with a note about the calling party being a GVNS user who sends a service request. It then enters a state, sends a GVNS Request to Network (linked to section 3.2.2), and waits for a response. The response can be a Dialled Number Request, Authorization Code Request, Account Code Request, or Interim Calling User Call Set-up Success. The first three lead to corresponding network responses and then back to a waiting state. The fourth leads to the GVNS Active state.
+
+FIGURE 2/F.16 (sheet 1 of 2)  
+**SDL diagram for user's view of GVNS**
+
+Process GVNS User
+
+![SDL diagram for user's view of GVNS. The diagram shows two state transition paths. The top path starts with 'Waiting for GVNS Response' (state), followed by 'Interim Calling User Call Set-up Failure' (event). It then reaches a decision 'Follow-on Status' (X). If 'Prompt not received' (Z), it goes to 'Follow-on Request to Network' (output), then 'Waiting for Follow-on Response' (state), leading to 'Follow-on Offer' (output) or 'Follow-on Limit Exceeded' (output). 'Follow-on Offer' leads to state Y. If 'Follow-on not available', the path ends. If 'Prompt received' (Y), it reaches 'User Action?' (decision). 'Reject' leads to 'Disconnect Request to Network' (output) and ends. 'Continue' leads to 'Dialled Number to Network' (output), then 'Waiting for GVNS Response' (state). The bottom path starts with 'GVNS Active' (state), leading to three parallel outputs: 'Calling User Disconnect' (output) leading to 'Disconnect Request to Network' (output) and ending; 'Calling User Follow-on' (output) leading to state Z; and 'Calling User Disconnect' (output) leading to state X.](5cab96b2d23174c25919840ecd50aa48_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> S1: Waiting for GVNS Response
+    S1 --> E1: Interim Calling User Call Set-up Failure
+    E1 --> D1: Follow-on Status
+    D1 --> O1: Follow-on Request to Network: Prompt not received (Z)
+    O1 --> S2: Waiting for Follow-on Response
+    S2 --> O2: Follow-on Offer
+    S2 --> O3: Follow-on Limit Exceeded
+    O2 --> S3: Y
+    O3 --> [*]
+    D1 --> D2: Prompt received: Follow-on not available
+    D2 --> [*]
+    D1 --> D3: User Action?: Prompt received (Y)
+    D3 --> O4: Dialled Number to Network: Continue
+    O4 --> S4: Waiting for GVNS Response
+    D3 --> O5: Disconnect Request to Network: Reject
+    O5 --> [*]
+
+    S5: GVNS Active --> O6: Calling User Disconnect
+    S5 --> O7: Calling User Follow-on
+    S5 --> O8: Calling User Disconnect
+    O6 --> O9: Disconnect Request to Network
+    O9 --> [*]
+    O7 --> S6: Z
+    O8 --> S7: X
+  
+```
+
+SDL diagram for user's view of GVNS. The diagram shows two state transition paths. The top path starts with 'Waiting for GVNS Response' (state), followed by 'Interim Calling User Call Set-up Failure' (event). It then reaches a decision 'Follow-on Status' (X). If 'Prompt not received' (Z), it goes to 'Follow-on Request to Network' (output), then 'Waiting for Follow-on Response' (state), leading to 'Follow-on Offer' (output) or 'Follow-on Limit Exceeded' (output). 'Follow-on Offer' leads to state Y. If 'Follow-on not available', the path ends. If 'Prompt received' (Y), it reaches 'User Action?' (decision). 'Reject' leads to 'Disconnect Request to Network' (output) and ends. 'Continue' leads to 'Dialled Number to Network' (output), then 'Waiting for GVNS Response' (state). The bottom path starts with 'GVNS Active' (state), leading to three parallel outputs: 'Calling User Disconnect' (output) leading to 'Disconnect Request to Network' (output) and ending; 'Calling User Follow-on' (output) leading to state Z; and 'Calling User Disconnect' (output) leading to state X.
+
+T0104320-95/d03
+
+FIGURE 2/F.16 (sheet 2 of 2)  
+**SDL diagram for user's view of GVNS**
+
+# PROCESS GVNS\_Service\_Provider
+
+![SDL diagram for GVNS service provider's view of GVNS. The diagram shows a state transition from 'Idle' to 'Calling User GVNS Access Request'. From there, it branches based on 'Access arrangement' ('Dedicated', 'Switched', 'Remote'). The 'Dedicated' and 'Switched' paths lead to 'Response To Calling User' and then 'Wait for Dialled Number'. The 'Remote' path leads to a decision 'Collect dialled number first?'. If 'Yes', it goes to 'Collect Dialled Number' and then 'Success?'. If 'No', it goes to 'Collect Authorization Code' and then 'Success?'. Both 'Success?' decisions lead to 'Terminate Call' if 'No', or to a connector 'G' if 'Yes'. A note on the left indicates that for remote access, the user has dialed an appropriate code. Another note indicates that the B party number may have been included in the access request. Four boxes at the top right list actions: Terminate Call, Collect Dialled Number, Collect Authorization Code, and Collect Account Code.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Idle
+    Idle --> CallingUserGVNSAccessRequest: Calling User GVNS Access Request
+    CallingUserGVNSAccessRequest --> AccessArrangement: Access arrangement?
+    AccessArrangement --> Dedicated: 'Dedicated'
+    AccessArrangement --> Switched: 'Switched'
+    AccessArrangement --> Remote: 'Remote'
+    Dedicated --> ResponseToCallingUser: Response To Calling User
+    Switched --> ResponseToCallingUser
+    Remote --> CollectDialledNumberFirst: 'Collect dialled number first?'
+    CollectDialledNumberFirst --> Yes1: 'Yes'
+    CollectDialledNumberFirst --> No1: 'No'
+    Yes1 --> CollectDialledNumber: Collect Dialled Number
+    CollectDialledNumber --> Success1: 'Success?'
+    Success1 --> Yes2: 'Yes'
+    Success1 --> No2: 'No'
+    No2 --> CollectAuthorizationCode: Collect Authorization Code
+    CollectAuthorizationCode --> Success2: 'Success?'
+    Success2 --> Yes3: 'Yes'
+    Success2 --> No3: 'No'
+    No3 --> TerminateCall: Terminate Call
+    Yes2 --> G: G
+    Yes3 --> G
+    TerminateCall --> [*]
+    Note left of CallingUserGVNSAccessRequest: /* High level description of network actions provided by GVNS service provide */
+    Note right of AccessArrangement: For remote access, user has dialled appropriate code. For direct or switched access, user may have dialled access code to identify GVNS service or GVNS service provider. Call has been routed to correct service provider.
+    Note left of ResponseToCallingUser: If required. B party number may have been included in access request
+    Note right of TerminateCall: Terminate Call /* Q.71 actions */
+    Note right of CollectDialledNumber: Collect Dialled Number
+    Note right of CollectAuthorizationCode: Collect Authorization Code
+    Note right of CollectAccountCode: Collect Account Code
+    
+```
+
+SDL diagram for GVNS service provider's view of GVNS. The diagram shows a state transition from 'Idle' to 'Calling User GVNS Access Request'. From there, it branches based on 'Access arrangement' ('Dedicated', 'Switched', 'Remote'). The 'Dedicated' and 'Switched' paths lead to 'Response To Calling User' and then 'Wait for Dialled Number'. The 'Remote' path leads to a decision 'Collect dialled number first?'. If 'Yes', it goes to 'Collect Dialled Number' and then 'Success?'. If 'No', it goes to 'Collect Authorization Code' and then 'Success?'. Both 'Success?' decisions lead to 'Terminate Call' if 'No', or to a connector 'G' if 'Yes'. A note on the left indicates that for remote access, the user has dialed an appropriate code. Another note indicates that the B party number may have been included in the access request. Four boxes at the top right list actions: Terminate Call, Collect Dialled Number, Collect Authorization Code, and Collect Account Code.
+
+T0103490-94/d04
+
+FIGURE 3/F.16 (sheet 1 of 7)  
+ SDL diagram for GVNS service provider's view of GVNS
+
+![SDL diagram for GVNS service provider's view of GVNS. The process starts with 'Wait for Dialled Number', leading to 'Calling Party Disconnect' and 'Dialled Number /* from Calling user */'. 'Calling Party Disconnect' leads to 'Terminate Call' and then an exit. 'Dialled Number' leads to 'Identify GVNS User Group', which then leads to a decision 'More Information?'. 'More Information?' has 'Yes' and 'No' paths. 'Yes' leads to 'Account code first?'. 'No' leads to connector D. 'Account code first?' has 'Yes' and 'No' paths. 'Yes' leads to connector B and 'Collect Account code'. 'No' leads to connector A and 'Collect Authorization Code'. Both 'Collect Account code' and 'Collect Authorization Code' lead to 'Success?' decisions. 'Success?' has 'Yes' and 'No' paths. 'Yes' leads to 'Authorization code also and not yet collected?' or 'Account code also and not yet collected?'. 'No' leads to 'Terminate Call'. 'Authorization code also and not yet collected?' has 'Yes' and 'No' paths. 'Yes' leads to connector A. 'No' leads to an exit. 'Account code also and not yet collected?' has 'Yes' and 'No' paths. 'Yes' leads to connector B. 'No' leads to an exit. Both exits lead to a decision 'Dialled number collected?'. 'Dialled number collected?' has 'Yes' and 'No' paths. 'Yes' leads to connector D. 'No' leads to connector C. Connector G also leads to the 'Dialled number collected?' decision.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+PROCESS GVNS\_Service\_Provider
+
+```
+
+stateDiagram-v2
+    [*] --> Wait
+    state "Wait for Dialled Number" as Wait
+    Wait --> CPD
+    state "Calling Party Disconnect" as CPD
+    CPD --> TC1
+    state "Terminate Call" as TC1
+    TC1 --> [*]
+    Wait --> DN
+    state "Dialled Number /* from Calling user */" as DN
+    DN --> IGUG
+    state "Identify GVNS User Group" as IGUG
+    IGUG --> MI
+    state "More Information?" as MI
+    MI --> D1((D)) : No
+    MI --> ACF
+    state "Account code first?" as ACF
+    ACF --> B1((B)) : Yes
+    ACF --> A1((A)) : No
+    ACF --> CAC
+    state "Collect Account code" as CAC
+    ACF --> CACode
+    state "Collect Authorization Code" as CACode
+    CAC --> S1
+    state "Success?" as S1
+    S1 --> [*] : No
+    S1 --> ACNYC
+    state "Authorization code also and not yet collected?" as ACNYC
+    ACNYC --> A2((A)) : Yes
+    ACNYC --> [*] : No
+    CACode --> S2
+    state "Success?" as S2
+    S2 --> [*] : No
+    S2 --> ACCNYC
+    state "Account code also and not yet collected?" as ACCNYC
+    ACCNYC --> B2((B)) : Yes
+    ACCNYC --> [*] : No
+    [*] --> DNC
+    state "Dialled number collected?" as DNC
+    DNC --> C((C)) : No
+    DNC --> D2((D)) : Yes
+    G((G)) --> DNC
+  
+```
+
+SDL diagram for GVNS service provider's view of GVNS. The process starts with 'Wait for Dialled Number', leading to 'Calling Party Disconnect' and 'Dialled Number /\* from Calling user \*/'. 'Calling Party Disconnect' leads to 'Terminate Call' and then an exit. 'Dialled Number' leads to 'Identify GVNS User Group', which then leads to a decision 'More Information?'. 'More Information?' has 'Yes' and 'No' paths. 'Yes' leads to 'Account code first?'. 'No' leads to connector D. 'Account code first?' has 'Yes' and 'No' paths. 'Yes' leads to connector B and 'Collect Account code'. 'No' leads to connector A and 'Collect Authorization Code'. Both 'Collect Account code' and 'Collect Authorization Code' lead to 'Success?' decisions. 'Success?' has 'Yes' and 'No' paths. 'Yes' leads to 'Authorization code also and not yet collected?' or 'Account code also and not yet collected?'. 'No' leads to 'Terminate Call'. 'Authorization code also and not yet collected?' has 'Yes' and 'No' paths. 'Yes' leads to connector A. 'No' leads to an exit. 'Account code also and not yet collected?' has 'Yes' and 'No' paths. 'Yes' leads to connector B. 'No' leads to an exit. Both exits lead to a decision 'Dialled number collected?'. 'Dialled number collected?' has 'Yes' and 'No' paths. 'Yes' leads to connector D. 'No' leads to connector C. Connector G also leads to the 'Dialled number collected?' decision.
+
+T0103500-94/d05
+
+FIGURE 3/F.16 (sheet 2 of 7)  
+ SDL diagram for GVNS service provider's view of GVNS
+
+PROCESS GVNS\_Service\_Provider
+
+![SDL diagram for GVNS service provider's view of GVNS. The process starts at connector 'C', proceeds to 'Collect Dialled Number', then checks 'Success?'. If 'No', it goes to connector 'D'. If 'Yes', it checks 'GVNS User Group Identified?'. If 'No', it goes to 'Identify GVNS User Group' then checks 'Success?'. If 'Yes', it goes to 'Call Screening' then checks 'Passed?'. If 'No', it goes to connector 'D'. If 'Yes', it checks 'Remote Access?'. If 'Yes', it checks 'Account Code Needed?'. If 'Yes', it goes to 'Collect Account Code' then checks 'Success?'. If 'No', it goes to 'Terminate Call'. If 'Yes', it goes to connector 'H'. If 'No', it goes to connector 'D'. If 'No' to 'Remote Access?', it goes to connector 'H'. From 'H', it goes to 'Set up GVNS call' then checks 'Success?'. If 'No', it goes to connector 'E'. If 'Yes', it goes to 'GVNS Active'. From 'E', it checks 'Follow on available?'. If 'No', it goes to connector 'F'. If 'Yes', it goes to 'Follow on Offer to the Calling User' then 'Wait for user action'. From 'F', it goes to 'Play Announcement To the Calling User' then 'Terminate Call'.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> C
+    C --> CollectDialledNumber[Collect Dialled Number]
+    CollectDialledNumber --> Success1{Success?}
+    Success1 -- No --> D
+    Success1 -- Yes --> GVNSUserGroupIdentified{GVNS User Group Identified?}
+    GVNSUserGroupIdentified -- No --> IdentifyGVNSUserGroup[Identify GVNS User Group]
+    IdentifyGVNSUserGroup --> Success2{Success?}
+    Success2 -- No --> D
+    Success2 -- Yes --> CallScreening[Call Screening]
+    CallScreening --> Passed{Passed?}
+    Passed -- No --> D
+    Passed -- Yes --> RemoteAccess{Remote Access?}
+    RemoteAccess -- Yes --> AccountCodeNeeded{Account Code Needed?}
+    AccountCodeNeeded -- Yes --> CollectAccountCode[Collect Account Code]
+    CollectAccountCode --> Success3{Success?}
+    Success3 -- No --> TerminateCall1[Terminate Call]
+    Success3 -- Yes --> H
+    AccountCodeNeeded -- No --> H
+    RemoteAccess -- No --> H
+    H --> SetupGVNSCall[Set up GVNS call]
+    SetupGVNSCall --> Success4{Success?}
+    Success4 -- No --> E
+    Success4 -- Yes --> GVNSActive([GVNS Active])
+    E --> FollowOnAvailable{Follow on available?}
+    FollowOnAvailable -- No --> F
+    FollowOnAvailable -- Yes --> FollowOnOffer[Follow on Offer to the Calling User]
+    FollowOnOffer --> WaitForUserAction([Wait for user action])
+    F --> PlayAnnouncement[Play Announcement To the Calling User]
+    PlayAnnouncement --> TerminateCall2[Terminate Call]
+    
+```
+
+Reasons can include:  
+ - not subscribed;  
+ - not provided by N/W;  
+ - allowed number of calls exceeded.
+
+SDL diagram for GVNS service provider's view of GVNS. The process starts at connector 'C', proceeds to 'Collect Dialled Number', then checks 'Success?'. If 'No', it goes to connector 'D'. If 'Yes', it checks 'GVNS User Group Identified?'. If 'No', it goes to 'Identify GVNS User Group' then checks 'Success?'. If 'Yes', it goes to 'Call Screening' then checks 'Passed?'. If 'No', it goes to connector 'D'. If 'Yes', it checks 'Remote Access?'. If 'Yes', it checks 'Account Code Needed?'. If 'Yes', it goes to 'Collect Account Code' then checks 'Success?'. If 'No', it goes to 'Terminate Call'. If 'Yes', it goes to connector 'H'. If 'No', it goes to connector 'D'. If 'No' to 'Remote Access?', it goes to connector 'H'. From 'H', it goes to 'Set up GVNS call' then checks 'Success?'. If 'No', it goes to connector 'E'. If 'Yes', it goes to 'GVNS Active'. From 'E', it checks 'Follow on available?'. If 'No', it goes to connector 'F'. If 'Yes', it goes to 'Follow on Offer to the Calling User' then 'Wait for user action'. From 'F', it goes to 'Play Announcement To the Calling User' then 'Terminate Call'.
+
+T0103510-94/d06
+
+FIGURE 3/F.16 (sheet 3 of 7)  
+ SDL diagram for GVNS service provider's view of GVNS
+
+Process GVNS\_Service\_Provider
+
+![State transition diagram for GVNS Active state](83852ec55d4802521a727926336bedab_img.jpg)
+
+This state transition diagram starts with an initial state labeled "GVNS Active" in a double oval. Three arrows lead to different input/output blocks: "Calling User Disconnect", "Calling User Follow on Request", and "Called User Disconnect". The "Calling User Disconnect" block leads to a "Terminate Call" process block (double rectangle), which then leads to an exit symbol (a circle with an X). The "Calling User Follow on Request" block leads to a decision diamond labeled "Follow on available?". From this diamond, a "Yes" path leads to a circle labeled "C", and a "No" path leads to a circle labeled "F". The "Called User Disconnect" block leads to a circle labeled "E".
+
+State transition diagram for GVNS Active state
+
+![State transition diagram for Wait for user action state](5445597cceefaca1ac89e710fe339325_img.jpg)
+
+This state transition diagram starts with an initial state labeled "Wait for user action" in a double oval. Two arrows lead to different input/output blocks: "Calling User Disconnect" and "Calling User Follow on Request". The "Calling User Disconnect" block leads to a "Terminate Call" process block (double rectangle), which then leads to an exit symbol (a circle with an X). The "Calling User Follow on Request" block leads to a circle labeled "C". Below the diagram is the text "T0103810-94/d07".
+
+State transition diagram for Wait for user action state
+
+FIGURE 3/F.16 (sheet 4 of 7)  
+SDL diagram for GVNS service provider's view of GVNS
+
+## PROCEDURE Collect Authorization Code
+
+![SDL diagram for GVNS service provider's view of GVNS. The process starts with an initial state, followed by 'Request Authorization Code from Calling User', then 'GVNS Waiting for Calling User Response'. From there, three paths emerge: 'Timer expiry' leading to 'Retry allowed?' (Yes loops back, No leads to 'Play Announcement To User'), 'Authorization Code /* from Calling user */' leading to 'Code valid?' (Yes leads to end, No loops back), and 'Calling User Disconnect' leading to end. Reference T0103530-94/d08.](812e188283162af0b54fb3e30ffee51b_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Request
+    state "Request Authorization Code from Calling User" as Request
+    Request --> Waiting
+    state "GVNS Waiting for Calling User Response" as Waiting
+    Waiting --> TimerExpiry
+    Waiting --> AuthCode
+    Waiting --> Disconnect
+    state "Timer expiry" as TimerExpiry
+    TimerExpiry --> RetryAllowed{Retry allowed?}
+    RetryAllowed -- Yes --> Request
+    RetryAllowed -- No --> PlayAnnouncement
+    state "Play Announcement To User" as PlayAnnouncement
+    PlayAnnouncement --> [*]
+    state "Authorization Code /* from Calling user */" as AuthCode
+    AuthCode --> CodeValid{Code valid?}
+    CodeValid -- Yes --> [*]
+    CodeValid -- No --> Request
+    state "Calling User Disconnect" as Disconnect
+    Disconnect --> [*]
+    note right of Disconnect: T0103530-94/d08
+  
+```
+
+SDL diagram for GVNS service provider's view of GVNS. The process starts with an initial state, followed by 'Request Authorization Code from Calling User', then 'GVNS Waiting for Calling User Response'. From there, three paths emerge: 'Timer expiry' leading to 'Retry allowed?' (Yes loops back, No leads to 'Play Announcement To User'), 'Authorization Code /\* from Calling user \*/' leading to 'Code valid?' (Yes leads to end, No loops back), and 'Calling User Disconnect' leading to end. Reference T0103530-94/d08.
+
+FIGURE 3/F.16 (sheet 5 of 7)  
+SDL diagram for GVNS service provider's view of GVNS
+
+## PROCEDURE Collect Account Code
+
+![SDL diagram for GVNS service provider's view of GVNS. The process starts with an initial state, followed by 'Request Account Code from Calling User', then 'GVNS Waiting for Calling User Response'. It then branches into three events: 'Timer expiry', 'Account Code /* from Calling User */', and 'Calling User Disconnect'. 'Timer expiry' leads to a decision 'Retry allowed?'. If 'Yes', it loops back to the request. If 'No', it leads to 'Code valid?'. If 'Code valid?' is 'Yes', it ends. If 'Code valid?' is 'No', it leads to 'Play Announcement To User' and then ends. 'Calling User Disconnect' also ends the process. A label T0103540-94/d09 is present.](08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Request
+    state "Request Account Code from Calling User" as Request
+    Request --> Waiting
+    state "GVNS Waiting for Calling User Response" as Waiting
+    Waiting --> TimerExpiry
+    Waiting --> AccountCode
+    Waiting --> Disconnect
+    state "Timer expiry" as TimerExpiry
+    state "Account Code /* from Calling User */" as AccountCode
+    state "Calling User Disconnect" as Disconnect
+    TimerExpiry --> RetryAllowed
+    state "Retry allowed?" as RetryAllowed
+    RetryAllowed -- Yes --> Request
+    RetryAllowed -- No --> CodeValid
+    state "Code valid?" as CodeValid
+    CodeValid -- Yes --> [*]
+    CodeValid -- No --> PlayAnnouncement
+    state "Play Announcement To User" as PlayAnnouncement
+    PlayAnnouncement --> [*]
+    Disconnect --> [*]
+    note right of Disconnect: T0103540-94/d09
+  
+```
+
+SDL diagram for GVNS service provider's view of GVNS. The process starts with an initial state, followed by 'Request Account Code from Calling User', then 'GVNS Waiting for Calling User Response'. It then branches into three events: 'Timer expiry', 'Account Code /\* from Calling User \*/', and 'Calling User Disconnect'. 'Timer expiry' leads to a decision 'Retry allowed?'. If 'Yes', it loops back to the request. If 'No', it leads to 'Code valid?'. If 'Code valid?' is 'Yes', it ends. If 'Code valid?' is 'No', it leads to 'Play Announcement To User' and then ends. 'Calling User Disconnect' also ends the process. A label T0103540-94/d09 is present.
+
+FIGURE 3/F.16 (sheet 6 of 7)  
+**SDL diagram-for GVNS service provider's view of GVNS**
+
+## PROCEDURE Collect Dialled Number
+
+![SDL diagram for GVNS service provider's view of GVNS. The flowchart starts with an initial state, followed by 'Request Dialled Number from Calling User', then 'GVNS Waiting for User Response'. It then branches into three events: 'Timer expiry', 'Dialled Number /* from user Calling /*', and 'Calling user Disconnect'. 'Timer expiry' leads to a decision 'Retry allowed?'. If 'Yes', it loops back to the request. If 'No', it leads to 'Number valid?'. If 'Number valid?' is 'Yes', it ends. If 'Number valid?' is 'No', it leads to 'Play Announcement to the Calling User', which then ends. 'Calling user Disconnect' ends the process. A reference code T0103550-94/d10 is present.](365b54f616aff249b4e6c0edafdcb9b3_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> RequestDialledNumber
+    RequestDialledNumber: Request Dialled Number from Calling User
+    state RequestDialledNumber
+    RequestDialledNumber --> Waiting
+    state Waiting {
+        direction LR
+        GVNS_Waiting: GVNS Waiting for User Response
+    }
+    Waiting --> TimerExpiry: Timer expiry
+    Waiting --> DialledNumber: Dialled Number /* from user Calling /*
+    Waiting --> Disconnect: Calling user Disconnect
+    
+    TimerExpiry --> RetryAllowed
+    state RetryAllowed <<choice>>
+    note right of RetryAllowed: 'Retry allowed?'
+    RetryAllowed --> RequestDialledNumber: 'Yes'
+    RetryAllowed --> NumberValid: 'No'
+    
+    DialledNumber --> NumberValid
+    state NumberValid <<choice>>
+    note right of NumberValid: 'Number valid?'
+    NumberValid --> [*]: 'Yes'
+    NumberValid --> PlayAnnouncement: 'No'
+    
+    PlayAnnouncement: Play Announcement to the Calling User
+    PlayAnnouncement --> [*]
+    
+    Disconnect --> [*]
+    
+    note bottom of Disconnect: T0103550-94/d10
+
+```
+
+SDL diagram for GVNS service provider's view of GVNS. The flowchart starts with an initial state, followed by 'Request Dialled Number from Calling User', then 'GVNS Waiting for User Response'. It then branches into three events: 'Timer expiry', 'Dialled Number /\* from user Calling /\*', and 'Calling user Disconnect'. 'Timer expiry' leads to a decision 'Retry allowed?'. If 'Yes', it loops back to the request. If 'No', it leads to 'Number valid?'. If 'Number valid?' is 'Yes', it ends. If 'Number valid?' is 'No', it leads to 'Play Announcement to the Calling User', which then ends. 'Calling user Disconnect' ends the process. A reference code T0103550-94/d10 is present.
+
+FIGURE 3/F.16 (sheet 7 of 7)  
+**SDL diagram for GVNS service provider's view of GVNS**

marked/F/T-REC-F.162-199607-I_PDF-E/raw.md

@@ -0,0 +1,375 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.162**
+
+(07/96)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Telematic services – Public facsimile service
+
+---
+
+**Service and operational requirements of  
+store-and-forward facsimile service**
+
+ITU-T Recommendation F.162
+
+(Previously "CCITT Recommendation")
+
+---
+
+# FOREWORD
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations 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.162 was revised by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 19th of July 1996.
+
+---
+
+# NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+© ITU 1996
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+# CONTENTS
+
+*Page*
+
+|     |                                                      |   |
+|-----|------------------------------------------------------|---|
+| 1   | Introduction .....                                   | 1 |
+| 2   | Scope .....                                          | 1 |
+| 3   | Definitions .....                                    | 1 |
+| 4   | Service description .....                            | 2 |
+| 5   | Service facilities .....                             | 2 |
+| 5.1 | Access management .....                              | 2 |
+| 5.2 | Message addressing .....                             | 3 |
+| 5.3 | Address list codes .....                             | 3 |
+| 5.4 | Message identification .....                         | 3 |
+| 5.5 | Classes of message delivery .....                    | 3 |
+| 5.6 | Message deferral .....                               | 3 |
+| 5.7 | Cover page .....                                     | 3 |
+| 5.8 | Customer report .....                                | 4 |
+| 5.9 | Facsimile format conversion .....                    | 5 |
+| 6   | Access procedures .....                              | 6 |
+| 7   | Delivery procedures .....                            | 6 |
+| 7.1 | Automatic call retry .....                           | 6 |
+| 7.2 | Call records .....                                   | 6 |
+| 7.3 | Recovery from interrupted message delivery .....     | 6 |
+| 8   | Quality of service .....                             | 6 |
+| 8.2 | Quality of service targets .....                     | 6 |
+| 8.3 | Storage capacity .....                               | 7 |
+| 8.4 | Public network circuits .....                        | 7 |
+|     | Annex A – Example of COMFAX service cover page ..... | 8 |
+|     | Annex B – Example of access procedures .....         | 9 |
+
+
+
+# SERVICE AND OPERATIONAL REQUIREMENTS OF STORE-AND-FORWARD FACSIMILE SERVICE
+
+*(revised in 1992 and in 1996)*
+
+# 1 Introduction
+
+1.1 The development and growth of store-and-forward equipment and the potential for the international interconnection of such equipment requires a common set of facilities and operational procedures to meet the needs of users. The COMFAX service may be accessed by a variety of terminals which can employ a variety of networks for access purposes. Access to a COMFAX service will be predominantly from facsimile terminals connected to its associated national public networks. However, there are advantages in defining features and procedures for the service to promote and assist the provision of such services in many countries.
+
+# 2 Scope
+
+2.1 This Recommendation defines the general principles and basic operational requirements of the COMFAX service provided by Administrations using computer-controlled facsimile store-and-forward units (Fax SFU). Although customer access will be, predominantly, from within the same country in which the Fax SFU is situated, this Recommendation sets out the minimum service requirements that should be provided to allow extension of the service, by the interconnection with one or more other Fax SFUs, across national boundaries, for message delivery purposes.
+
+2.2 Technical requirements of the service are covered in the relevant T- and X-Series Recommendations.
+
+2.3 Tariff and accounting aspects are covered in the D-Series Recommendations. Fax SFUs must record and store sufficient information for charging and settlement of accounts.
+
+2.4 The operational aspects of the interconnection of Fax SFUs are covered in Recommendation F.163.
+
+2.5 The interworking between COMFAX and other services using the Message Handling System (MHS) is a requirement; details are for further study. The interworking between the COMFAX service and other UIT-T defined services is for further study.
+
+# 3 Definitions
+
+This Recommendation uses the terms listed below.
+
+NOTE – Use of the terms “delivery”, “submission”, “transfer”, does not imply any specific protocol implementation regarding the X.400-Series Recommendations.
+
+3.1 **Fax SFU:** A Fax SFU refers to the boundary within which the facsimile store-and-forward service is provided by one or more facsimile store-and-forward units under the control of one Administration. A Fax SFU must provide the functions of message submission, message delivery and, in the case of interconnection, message transfer.
+
+3.2 **message delivery:** Message delivery is defined as the transfer of message data and responsibility for the message from a Fax SFU to a recipient address.
+
+3.3 **recipient address:** A recipient address is defined as the ultimate destination of a message. A recipient address may designate a facsimile terminal or a storage device empowered to receive messages for a FAX recipient.
+
+3.4 **message submission:** Message submission is defined as the transfer of message data and responsibility for the message from the originator to the COMFAX service (e.g. typically indicated by the successful completion of the T.30 protocol).
+
+3.5 **message transfer:** Message transfer is defined as the transfer of message data and responsibility for the message from one Fax SFU (or transfer system) to another Fax SFU (or transfer system).
+
+**3.6 transfer system:** A transfer system is defined as a system which accomplishes message transfer as defined above. A transfer system may or may not provide end user facsimile services.
+
+# 4 Service description
+
+**4.1** Customers may submit messages to the COMFAX service for delivery to one or more recipients. The service provides a range of facilities which may be used by the customer for message management purposes. Facilities such as cover page and deferred delivery allow the customer to specify how messages are handled in their transmission from source to destination. Other facilities, such as customer reports, may provide the customer with more complete messages statistics than are generally available in the real-time group 3 facsimile service.
+
+The service shall accept messages submitted in group 3 facsimile format. Acceptance of messages in other formats is optional.
+
+**4.2** Customers access the COMFAX service via public networks. Messages are also delivered to destination terminals via public networks.
+
+**4.3** Where the service is provided by means of the interconnection by two or more Administrations interworking between Fax SFUs is as defined in Recommendation F.163. Interworking using group 3 facsimile image format is mandatory. Interworking using other formats is optional.
+
+# 5 Service facilities
+
+The provision of service facilities to the facsimile customer is a local matter and may vary between Administrations. However, Administrations extending their service across international boundaries by interconnection with one or more Fax SFUs should regard the basic service facilities as mandatory or optional in accordance with Table 1.
+
+## 5.1 Access management
+
+Access management is the identification and validation of the originating customer. This may be achieved by passwords where pre-registration is involved. In cases where pre-registration is not employed, the identification of the originating customer may be achieved through the transfer of automatic number identification data from the access network to the Fax SFU. Where passwords are used, it should be possible for the customer to change the password periodically. The exact procedures for security of access should be a local matter.
+
+TABLE 1/F.162  
+**Classification of COMFAX service facilities**
+
+| Service facility            | Classification | Reference |
+|-----------------------------|----------------|-----------|
+| Access management           | M              | 5.1       |
+| Single address message      | M              | 5.2.1     |
+| Multiple address message    | O              | 5.2.2     |
+| Address list codes          | O              | 5.3       |
+| Message identification      | M              | 5.4       |
+| Class of message delivery   | O              | 5.5       |
+| Message deferral            | O              | 5.6       |
+| Cover page                  | O              | 5.7       |
+| Message failure report      | M              | 5.8.1     |
+| Message delivery report     | O              | 5.8.2     |
+| Facsimile format conversion | O              | 5.9       |
+| M Mandatory                 |                |           |
+| O Optional                  |                |           |
+
+## **5.2 Message addressing**
+
+The method of specifying the recipient address is a local matter.
+
+#### **5.2.1 Single address message**
+
+A single address message is a message with one recipient address.
+
+#### **5.2.2 Multiple address message**
+
+A multiple address message is a message with more than one recipient address. Fax SFUs should be able to accommodate messages addressed to 512 recipient addresses.
+
+## **5.3 Address list codes**
+
+An address list code is a code which is used to reference a pre-registered list of recipient addresses. A customer may use an address list code at the time of message submission.
+
+## **5.4 Message identification**
+
+The message reference is an identification which can be used to unambiguously identify a message relative to the message originator. When interconnection between Fax SFUs is required, the message reference must be linked to the message identifier (see 6.3/F.163).
+
+## **5.5 Classes of message delivery**
+
+There may be three classes of message delivery:
+
+- a) urgent;
+- b) nominal;
+- c) non-urgent.
+
+The process by which the class of message delivery is selected should be a local matter. Quality of Service objectives for the above classes of delivery are shown in clause 8.
+
+### **5.6 Message deferral**
+
+The process by which the message deferral is selected is a local matter. There may be two types of message deferrals:
+
+- a) to a time specified by the originator;
+- b) to a time determined by the service provider.
+
+#### **NOTES**
+
+- 1 In a) the customer may choose any of the classes of delivery supported to take effect at the specified time.
+- 2 Deferral b) is only provided when a customer has selected the non-urgent class of delivery.
+
+### **5.7 Cover page**
+
+A cover page is a service provided facsimile page which is automatically added to the front of a customer provided message. The size of the cover page is the same as the first page of the message. All of the data presented on the cover page should be displayable within this size. The cover page may contain information concerning the originator, recipient, and the message. A customer may select the cover page facility on a per message basis.
+
+#### **5.7.1 Multiple address cover page**
+
+Cover page generation for multiple address messages is supported. A cover page request applies to all recipients of the multiple address message. The service should have the capability to provide a different cover page per recipient of a multiple address message.
+
+#### **5.7.2 Cover page selection**
+
+A customer of the COMFAX service should have three options in selecting a cover page:
+
+- a) no cover page;
+- b) COMFAX service cover page;
+- c) customer defined cover page.
+
+#### **5.7.3 COMFAX service cover page**
+
+In this case, the COMFAX service is responsible for providing a cover page. The contents of the cover page and selection are described in the following subclause.
+
+##### **5.7.3.1 Cover page contents**
+
+The contents of the cover page are found in Table 2.
+
+##### **5.7.3.2 Selection and display of contents in the COMFAX service cover page**
+
+All of the information fields listed in Table 2 which are provided in a message shall be displayed on the cover page. Fields which are required by the protocol will, therefore, always be displayed. Fields which are optional will be displayed if the field is present. Control and suppression of the display of fields is for further study.
+
+A suggested layout can be found in Annex A.
+
+#### **5.7.4 Customer defined cover page**
+
+The method of providing customer defined cover pages is a local matter.
+
+### **5.8 Customer report**
+
+Message status information provided in level 1 and level 2 notifications described in Recommendation F.163 may be used to provide originators with customer reports, as described in the following subclauses. The presentation of the content of reports and the handling of multiple address reports is a local matter. The method of delivery of the reports is a local matter, e.g. forced – facsimile or queried – delivery.
+
+#### **5.8.1 Message failure report**
+
+The service should report to the originator the failure to deliver a message to the destination address.
+
+The report to the customer may provide at least the following information:
+
+- message reference;
+- recipient address;
+- last attempt time.
+
+NOTE – Provision of time zone indication is a local matter.
+
+#### **5.8.2 Message delivery report**
+
+The service may report to the originator the successful delivery of a message to the recipient address.
+
+The report to the customer may provide at least the following information:
+
+- message reference;
+- recipient address;
+- time of delivery to recipient address;
+- number of pages delivered.
+
+NOTE – Provision of time zone indication is a local matter.
+
+TABLE 2/F.162
+
+#### **COMFAX service cover page contents**
+
+| Field                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Length                                                                                                       | PM/PA                                                  |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|
+| Image field                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Maximum 8 cm                                                                                                 | PM (Note 1)                                            |
+| Recipient information<br>NAME: choice of<br>Personal name<br>Common name<br>Free form name<br>ORGANIZATION<br>ORGANIZATIONAL UNIT(S)<br>PHYSICAL ADDRESS LINES<br>FAX NETWORK ADDRESS<br>TELEPHONE NUMBER                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | <br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3) | <br>PA<br>PA<br>PA<br>PA<br>PA<br>PA<br>PA<br>PA<br>PA |
+| Message information<br>Pages<br>Priority<br>Submission date and time<br>Message reference<br>Subject                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | <br>3 bytes<br>1 byte<br>(Note 5)<br>(Note 4)<br>(Note 3)                                                    | <br>PM<br>PM<br>PM<br>PM/PA (Note 2)<br>PM             |
+| Originator information<br>NAME: choice of<br>Personal name<br>Common name<br>Free form name<br>ORGANIZATION<br>ORGANIZATIONAL UNIT(S)<br>PHYSICAL ADDRESS LINES<br>FAX NETWORK ADDRESS<br>TELEPHONE NUMBER                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | <br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3)<br>(Note 3) | <br>PM<br>PM<br>PM<br>PM<br>PM<br>PM<br>PM<br>PM<br>PM |
+| Additional recipients                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | (Note 6)                                                                                                     | PM/PA                                                  |
+| PA Per address<br>PM Per message<br>NOTES<br>1 The image field is either customer provided or service provided with a maximum length of 8 cm and fall within the guaranteed reproducible area of the group 3 facsimile page, in accordance with Appendix I/T.4.<br>2 The message reference shall be unique for each message, an additional three-digit part may be optionally used to signify each recipient.<br>3 Same value as in Recommendation F.401 or X.402.<br>4 The message reference is described in 5.4.<br>5 The date and time of submission of the message is to be displayed in the local time; a time zone indication should be provided. Translation of submission time to time zones other than the Fax SFU time zone is a local matter.<br>6 Display of additional recipients is an item for further study. A method of requesting additional recipient fields is to be defined. If necessary, additional cover pages may be used to provide additional recipient information. |                                                                                                              |                                                        |
+
+## **5.9 Facsimile format conversion**
+
+The facsimile format conversion service facility enables the content (image) of a facsimile message to be converted from one format to another. Conversion may be performed on the paper size, the resolution of the message and so on.
+
+If a Fax SFU supports optional values of several features of Group 3, it shall either support conversion of the image of a message to deliver it or shall not deliver a message whenever it detects that unsupported conversion is required.
+
+NOTE – It is preferred to support conversion to increase success rate of delivery in cases that loss of information due to conversion is not significant.
+
+If a Fax SFU supports facsimile terminals other than Group 3, then it shall support conversion between that group and Group 3.
+
+Conversion shall be an automatic facility and shall not require additional procedures for users. When conversion is supported in a Fax SFU, it shall be performed in a way that the image of the original message is best preserved. That is, conversion is performed only on the unsupported features trying to use values closer to the basic ones.
+
+Conversion that may result in loss of information may optionally be prohibited by the originator. The details of specifying conversion prohibition at origination are a local matter.
+
+The details of conversion rules and possible combinations of conversions are defined in the relevant T-Series Recommendations.
+
+# **6 Access procedures**
+
+Access procedures are a local matter but should make provision for security of access, destination address selection, delivery instructions and message submission. An example of access procedures is given in Annex B.
+
+# **7 Delivery procedures**
+
+## **7.1 Automatic call retry**
+
+Procedures for automatic call retry on terminal busy, ringing no reply or incomplete calls, subject to national regulatory requirements should be provided. Where the service is extended across national boundaries for the delivery of messages, then the target delivery times specified in clause 8 should be taken into account when setting the call retry periods.
+
+## **7.2 Call records**
+
+A call record confirmation successful or unsuccessful delivery to the recipient address should be maintained, which will include the relevant information provided by notifications. The storage of call records is a local matter.
+
+## **7.3 Recovery from interrupted message delivery**
+
+If a message is interrupted during the delivery from the destination Fax SFU to the destination terminal, subsequent attempts to deliver the message should commence with the first page not successfully delivered. Delivery should be attempted as soon as possible to avoid significant time periods occurring between receipt of the parts of the message. The recipient must be given sufficient information to correlate the parts of the message.
+
+# **8 Quality of service**
+
+**8.1** The introduction of a Fax SFU should not increase, on a per address basis, the probability of message loss or corruption.
+
+In the event of system failure, all accepted messages should be traceable. If messages have to be cancelled, because of system failure, the originating customers should be informed.
+
+## **8.2 Quality of service targets**
+
+**8.2.1** When the service is extended across international boundaries for delivery purposes, it is recommended that the Fax SFU design be such that quality of service targets shown in Figure 1 and Table 3 are maintained.
+
+![Diagram illustrating quality of service times. It shows a timeline with three vertical lines: 'End of submission', 'Start of first delivery attempt', and 'Forced negative L2N'. A horizontal double-headed arrow labeled T_A spans from 'End of submission' to 'Start of first delivery attempt'. A horizontal double-headed arrow labeled T_B spans from 'End of submission' to 'Forced negative L2N'. Below the diagram is the text 'T0102450-92/d01'.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+Diagram illustrating quality of service times. It shows a timeline with three vertical lines: 'End of submission', 'Start of first delivery attempt', and 'Forced negative L2N'. A horizontal double-headed arrow labeled T\_A spans from 'End of submission' to 'Start of first delivery attempt'. A horizontal double-headed arrow labeled T\_B spans from 'End of submission' to 'Forced negative L2N'. Below the diagram is the text 'T0102450-92/d01'.
+
+$T_A$  Time from the end of submission of the message or the time specified for deferred delivery to the start of the first call attempt
+
+$T_B$  Time from the end of submission of the message or the time specified for deferred delivery to the forced generation of a negative 2nd level notification and termination of message delivery attempt (unless transmission has already commenced)
+
+FIGURE 1/F.162  
+**Illustration of quality of service times**
+
+TABLE 3/F.162  
+**Quality of service targets**
+
+| Class of message delivery | $T_A$      | $T_B$    |
+|---------------------------|------------|----------|
+| Urgent                    | 0.25 hours | 1 hour   |
+| Normal                    | 1 hour     | 4 hours  |
+| Non-urgent                | 8 hours    | 12 hours |
+
+**8.2.2** The Fax SFU should be capable of meeting the quality of service targets at least 95% of traffic received during any one hour period.
+
+**8.2.3** While delivery is being attempted the Fax SFU may send interim reports to the customer showing that delivery of the message is still outstanding.
+
+## 8.3 Storage capacity
+
+Storage capacity will vary from one Fax SFU to another according to the volume of traffic. However, sufficient storage capacity should be provided to cater for an average message size of two pages, and up to maximum message size of 128 pages. With associated notifications and possible cover page requirements, this could represent a total data content of 6 megabytes.
+
+## 8.4 Public network circuits
+
+**8.4.1** The provision of network circuits for the reception and delivery of traffic by the Fax SFU will vary between Administrations. However, sufficient outgoing public network circuits should be provided to meet the quality of service targets of 8.2.
+
+**8.4.2** Administrations should make observations to evaluate the performance of the Fax SFU to ensure, in particular, that public network provisions are such that quality of service targets of 8.2 are being achieved.
+
+
+
+# Annex B
+
+## Example of access procedures
+
+(This annex is not an integral part of this Recommendation)
+
+- B.1** Access to the COMFAX system will normally be via the Public Switched Telephone Network (PSTN).
+- B.2** After normal voice call establishment procedures, the COMFAX system should answer with a tone or voice prompt requesting the user to input their respective user identity (ID) code by means of either the facsimile terminal Mediation Function (MF) keypad or an associated system compatible device.
+- B.3** The COMFAX system should then request the input of a Personal Identity Number (PIN) to ensure security of use. The request for the PIN may be prompted by either a tone or voice message.
+- B.4** When the ID and PIN codes have been successfully validated, the COMFAX system should request the input of the required destination address or addresses. These may be input in the form of the full national and international telephone number, including national access code requirements or code representing a pre-stored address list. The request for address input should be prompted by a tone or voice message. The destination address information should be entered by using either the facsimile terminal MF keypad, or an associated system compatible device.
+- B.5** Delivery instructions, i.e. deferred delivery, may be entered by selection of the appropriate code. The request for delivery instructions may be prompted by a tone or voice message. The required code should be entered by using either the facsimile terminal MF keypad or an associated system compatible device.
+- B.6** When destination address input and delivery instructions are completed, the COMFAX system should request the submission of the facsimile message. The request for message input may be prompted by a tone or voice message.
+- B.7** At the end of message input the PSTN call should be cleared using normal group 3 facsimile procedures.
+- B.8** The choice of tone or voice message prompts is a local matter. Where voice prompts are used, they should be in the language of the originator. The support of more than one language on a COMFAX system is a local matter.

marked/F/T-REC-F.163-199607-I_PDF-E/raw.md

@@ -0,0 +1,463 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.163**
+
+(07/96)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Telematic services – Public facsimile service
+
+---
+
+**Operational requirements of the interconnection  
+of facsimile store-and-forward units**
+
+ITU-T Recommendation F.163
+
+(Previously "CCITT Recommendation")
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1-F.109          |
+| Operating methods for the international public telegram service | F.1-F.19           |
+| The gentex network                                              | F.20-F.29          |
+| Message switching                                               | F.30-F.39          |
+| The international telemessage service                           | F.40-F.58          |
+| The international telex service                                 | F.59-F.89          |
+| Statistics and publications on international telegraph services | F.90-F.99          |
+| Scheduled and leased communication services                     | F.100-F.104        |
+| Phototelegraph service                                          | F.105-F.109        |
+| MOBILE SERVICE                                                  | F.110-F.159        |
+| Mobile services and multdestination satellite services          | F.110-F.159        |
+| <b>TELEMATIC SERVICES</b>                                       | <b>F.160-F.399</b> |
+| Public facsimile service                                        | F.160-F.199        |
+| Teletex service                                                 | F.200-F.299        |
+| Videotex service                                                | F.300-F.349        |
+| General provisions for telematic services                       | F.350-F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400-F.499        |
+| DIRECTORY SERVICES                                              | F.500-F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550-F.599        |
+| Document communication                                          | F.550-F.579        |
+| Programming communication interfaces                            | F.580-F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600-F.699        |
+| AUDIOVISUAL SERVICES                                            | F.700-F.799        |
+| ISDN SERVICES                                                   | F.800-F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850-F.899        |
+| HUMAN FACTORS                                                   | F.900-F.999        |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## FOREWORD
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations 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.163 was revised by ITU-T Study Group 1 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 19th of July 1996.
+
+---
+
+### NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+© ITU 1996
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+|                                                             | <i>Page</i> |
+|-------------------------------------------------------------|-------------|
+| 1 Introduction.....                                         | 1           |
+| 2 Scope.....                                                | 1           |
+| 3 Definitions.....                                          | 1           |
+| 4 Overview.....                                             | 2           |
+| 5 Interconnection requirements .....                        | 2           |
+| 5.1 General .....                                           | 2           |
+| 5.2 Information transfer unit.....                          | 2           |
+| 5.3 Transit arrangements .....                              | 4           |
+| 6 Service interworking principles.....                      | 4           |
+| 6.1 Message addressing .....                                | 5           |
+| 6.2 Address list codes .....                                | 5           |
+| 6.3 Message identification .....                            | 5           |
+| 6.4 Class of message delivery.....                          | 5           |
+| 6.5 Message deferral.....                                   | 5           |
+| 6.6 Cover page.....                                         | 5           |
+| 6.7 Advice of successful/unsuccessful message transfer..... | 5           |
+| 6.8 Advice of successful/unsuccessful message delivery..... | 6           |
+| 6.9 Facsimile format conversion.....                        | 7           |
+| 7 Quality of service .....                                  | 7           |
+| 7.6 Observations on the quality of service.....             | 7           |
+| 7.7 Duration of service .....                               | 7           |
+
+# OPERATIONAL REQUIREMENTS OF THE INTERCONNECTION OF FACSIMILE STORE-AND-FORWARD UNITS
+
+*(revised in 1996)*
+
+## 1 Introduction
+
+A growing number of Administrations are offering store-and-forward facsimile (COMFAX) services to their customers. For the efficient and economical extension of these services across international boundaries, there is a need for the interconnection of the facilities used to provide these services.
+
+## 2 Scope
+
+2.1 This Recommendation describes the general principles and operational aspects of the COMFAX service when operated and interconnected between Administrations.
+
+2.2 This Recommendation should be implemented in conjunction with Recommendation F.162 which describes the COMFAX service, and the relevant technical requirements of the T- and X-Series Recommendations. This Recommendation may also be used in connection with the provision of the bureaufax service as described in Recommendations F.170 and F.171.
+
+## 3 Definitions
+
+This Recommendation uses the terms listed below.
+
+NOTE – Use of the terms “delivery”, “submission”, “transfer”, does not imply any specific protocol implementation regarding the X.400-Series of Recommendations.
+
+3.1 **Fax SFU:** A Fax SFU refers to the boundary within which the facsimile store-and-forward service is provided by one or more facsimile store-and-forward units under the control of one Administration. A Fax SFU must provide the functions of message submission, message delivery and, in the case of interconnection, message transfer.
+
+3.2 **message delivery:** Message delivery is defined as the transfer of message data and responsibility for the message from a Fax SFU to a recipient address.
+
+3.3 **recipient address:** A recipient address is defined as the ultimate destination of a message. A recipient address may designate a facsimile terminal or a storage device empowered to receive messages for a FAX recipient.
+
+3.4 **message submission:** Message submission is defined as the transfer of message data and responsibility for the message from the originator to the COMFAX service (e.g. typically indicated by the successful completion of the T.30 protocol).
+
+3.5 **message transfer:** Message transfer is defined as the transfer of message data and responsibility for the message from one Fax SFU (or transfer system) to another Fax SFU (or transfer system).
+
+3.6 **transfer system:** A transfer system is defined as a system which accomplishes message transfer as defined above. A transfer system may or may not provide end user facsimile services.
+
+3.7 **transit facility:** A transit facility is either a Fax SFU or a transfer system.
+
+## 4 Overview
+
+4.1 The interconnection of Fax SFUs is provided on the basis of bilateral agreement between the Administrations concerned.
+
+4.2 The following two types of interconnection as illustrated in Figure 1 have been identified.
+
+4.2.1 Interconnected store and forward is where Fax SFUs operated by two Administrations are directly connected.
+
+4.2.2 Transit store and forward is where the Fax SFU transfers the facsimile message between Fax SFUs via other Fax SFUs or transfer systems.
+
+4.3 Interconnection between COMFAX and other services using the Message Handling System (MHS) will be provided by the transfer system. Details are for further study.
+
+![Diagram illustrating COMFAX interworking scenarios. It shows two main paths between an SFU in country A and an SFU in country B. Path (4.2.1) is a direct connection. Path (4.2.2) goes from the SFU in country A through an SFU transit system to the SFU in country B. A reference code T0105980-96/d01 is shown near the transit system.](1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg)
+
+```
+graph LR; A["SFU country A"] -- "(4.2.1)" --> B["SFU country B"]; A -- "(4.2.2)" --> T["SFU transit"]; T -- "T0105980-96/d01" --> B;
+```
+
+Diagram illustrating COMFAX interworking scenarios. It shows two main paths between an SFU in country A and an SFU in country B. Path (4.2.1) is a direct connection. Path (4.2.2) goes from the SFU in country A through an SFU transit system to the SFU in country B. A reference code T0105980-96/d01 is shown near the transit system.
+
+FIGURE 1/F.163  
+**COMFAX interworking scenarios**
+
+## 5 Interconnection requirements
+
+### 5.1 General
+
+5.1.1 In the interconnection of Fax SFUs, the responsibility to deliver single and multi-address messages is transferred from the originating Fax SFU to one or more destination Fax SFUs.
+
+5.1.2 In the interconnection of Fax SFUs, it is mandatory to provide two levels of notification to support the COMFAX service as defined in Recommendation F.162.
+
+### 5.2 Information transfer unit
+
+5.2.1 The basic unit of the inter-SFU communication is the Information Transfer Unit (ITU). This unit is classified as either a user ITU or a service ITU allowing easy identification of the function(s) for which cooperation is required.
+
+5.2.1.1 There is only one type of user ITU, which is the user message. This user message consists of the customer's facsimile message and some additional information (e.g. address).
+
+5.2.1.2 There are two types of service ITUs:
+
+- a) Level 1 notification (LIN) – Indicates the successful and/or unsuccessful transfer of responsibility for the user message to the destination SFU. An LIN conveys the information associated with the successful or unsuccessful transfer of responsibility on a per recipient basis. Table 1 lists the contents of the LIN.
+
+TABLE 1/F.163
+
+#### **Contents of level 1 notification (LIN)**
+
+|                                     |
+|-------------------------------------|
+| <b>Common field</b>                 |
+| original message identifier         |
+| recipient address                   |
+| original encoded information types  |
+| converted encoded information types |
+| <b>Successful transfer field</b>    |
+| last transfer time                  |
+| <b>Unsuccessful transfer field</b>  |
+| reason code                         |
+| diagnostic code                     |
+
+- b) Level 2 notification (L2N) – Indicates the successful or unsuccessful delivery of the responsibility for and delivery of the user message to the recipient address. Responsibility is transferred to a user by transmission of the message to either a facsimile terminal or a storage device empowered to receive messages for a facsimile recipient. Table 2 lists the contents of the L2N.
+
+TABLE 2/F.163
+
+#### **Contents of level 2 notification (L2N)**
+
+|                                       |
+|---------------------------------------|
+| <b>Common field</b>                   |
+| original message identifier           |
+| recipient address                     |
+| last encoded information types        |
+| SFU reference                         |
+| <b>Successful delivery field</b>      |
+| time of delivery to recipient address |
+| receiving terminal identifier         |
+| number of pages                       |
+| duration of delivery                  |
+| <b>Unsuccessful delivery field</b>    |
+| reason code                           |
+| diagnostic code                       |
+| last attempt time                     |
+| number of attempts                    |
+| delivered                             |
+
+**5.2.2** Information transfer units should be transferred between Fax SFUs using Protocol Data Units (PDUs) in accordance with the X.400-Series Recommendations.
+
+**5.2.3** The encoded message part within the user information transfer unit should be indicated as group 3 facsimile for interconnection. The use of other facsimile formats and encoded information types is subject to bilateral agreement.
+
+**5.2.4** Fax SFUs shall transfer recipient addresses using the originator/recipient (O/R) address form defined in Recommendation F.401.
+
+### **5.3 Transit arrangements**
+
+**5.3.1** The use of transit facilities for message transfer is subject to agreement of the service providers involved.
+
+**5.3.2** A facsimile message may pass through a transit facility consisting of a Fax SFU or some other transfer system. Where messages are routed via transit facilities, the transit facility is required to support the first level notification.
+
+**5.3.3** Where a message contains a multiple recipient address, it shall be possible for the transfer facility to accept responsibility for some recipient addresses and to onward transfer to one or more Fax SFUs or transfer systems the responsibility for other recipient addresses.
+
+## **6 Service interworking principles**
+
+The classification of the interworking requirements is shown in Table 3.
+
+TABLE 3/F.163
+
+### **Interworking requirements of service facilities**
+
+| Service Facility Requirement                           | ORIG                                                                                                                                            | TRANS | DEST | Reference |
+|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------|------|-----------|
+| Single address message                                 | M                                                                                                                                               | M1    | M    | 6.1.1     |
+| Multiple address message                               | C                                                                                                                                               | M1    | M    | 6.1.2     |
+| Address list codes                                     | C                                                                                                                                               | N/A   | N/A  | 6.2       |
+| Message identification                                 | M                                                                                                                                               | M     | M    | 6.3       |
+| Class of message delivery                              | C                                                                                                                                               | M1    | M    | 6.4       |
+| Message deferral                                       | C                                                                                                                                               | N/A   | N/A  | 6.5       |
+| Cover page                                             | C                                                                                                                                               | N/A   | M    | 6.6       |
+| Advice of successful message transfer (positive L1N)   | C                                                                                                                                               | M     | M    | 6.7       |
+| Advice of unsuccessful message transfer (negative L1N) | M                                                                                                                                               | M     | M    | 6.7       |
+| Advice of successful message delivery (positive L2N)   | M                                                                                                                                               | M1    | M    | 6.8       |
+| Advice of unsuccessful message delivery (negative L2N) | M                                                                                                                                               | M1    | M    | 6.8       |
+| Facsimile format conversion                            | C                                                                                                                                               | N/A   | C    | 6.9       |
+| M                                                      | Mandatory                                                                                                                                       |       |      |           |
+| M1                                                     | Mandatory. In the case that the transit facility does not take responsibility for any message delivery, the service facility shall be conveyed. |       |      |           |
+| C                                                      | Conditional                                                                                                                                     |       |      |           |
+| N/A                                                    | Not applicable                                                                                                                                  |       |      |           |
+| ORIG                                                   | Originating Fax SFU                                                                                                                             |       |      |           |
+| TRANS                                                  | Transit facility                                                                                                                                |       |      |           |
+| DEST                                                   | Destination Fax SFU                                                                                                                             |       |      |           |
+
+### **6.1 Message addressing**
+
+#### **6.1.1 Single address message**
+
+In the interconnection of Fax SFUs a single address message should be supported as defined in Recommendation F.162.
+
+#### **6.1.2 Multiple address message**
+
+In the interconnection of Fax SFUs a multiple address message should be supported as defined in Recommendation F.162.
+
+### **6.2 Address list codes**
+
+Expansion of address lists should be performed at the originating Fax SFU. Expansion of address lists at other Fax SFUs is for further study.
+
+### **6.3 Message identification**
+
+On successful submission of a message, the originating Fax SFU shall assign a globally unique identification to the message. The message identifier is used to identify the message in notifications between Fax SFUs.
+
+### **6.4 Class of message delivery**
+
+In the interconnection of Fax SFUs, the three classes of message delivery, urgent, normal and non-urgent, as defined in Recommendation F.162, should be supported.
+
+### **6.5 Message deferral**
+
+The storage of messages to the customer specified time for message delivery, as described in Recommendation F.162, should be carried out by the originating Fax SFU.
+
+### **6.6 Cover page**
+
+Cover page is described in Recommendation F.162. The customer choice of cover page shall be transferred from the originating Fax SFU to the destination Fax SFU.
+
+#### **6.6.1 Support of no cover page request**
+
+When no cover page is requested, no cover page shall be provided.
+
+#### **6.6.2 Support of the COMFAX service cover page**
+
+The destination Fax SFU generates the COMFAX service cover page. The layout of the page is a local matter. Table 4 specifies which Fax SFU provides the COMFAX service cover page contents.
+
+#### **6.6.3 Support of customer defined cover page**
+
+Use of a page description method of providing customer defined cover pages is for further study.
+
+### **6.7 Advice of successful/unsuccessful message transfer**
+
+**6.7.1** A LIN includes information indicating the successful and/or unsuccessful acceptance of responsibility for the message on a per recipient basis.
+
+**6.7.2** A LIN which only contains information regarding unsuccessful transfer shall be generated by either the destination Fax SFU or the transit facility as soon as it is determined that responsibility for the message on a per recipient basis cannot be accepted or transferred.
+
+6.7.3 A LIN for successful transfer shall only be returned when requested. The request shall be processed on a per recipient address basis.
+
+6.7.4 An unsuccessful message transfer is indicated by the generation of a negative LIN. (There is no requirement for the generation of a negative L2N in this case.) It shall be mandatory to return a LIN for unsuccessful transfer on a per recipient basis.
+
+TABLE 4/F.163
+
+#### **Provision of COMFAX Service cover page contents**
+
+| Field                                                                                                                                                                                                                                                                                                                                    | Provided by                                  |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|
+| Image field                                                                                                                                                                                                                                                                                                                              | O/D (Note 1)                                 |
+| Recipient information<br>NAME: choice of<br>Personal name<br>Common name<br>Free form name<br>ORGANIZATION<br>ORGANIZATIONAL UNIT(S)<br>PHYSICAL ADDRESS LINES<br>FAX NETWORK ADDRESS<br>TELEPHONE NUMBER                                                                                                                                | <br><br>O<br>O<br>O<br>O<br>O<br>O<br>O<br>O |
+| Message information<br>Pages<br>Priority<br>Submission date and time<br>Message Reference<br>Subject                                                                                                                                                                                                                                     | <br>D<br>O<br>O<br>O<br>O                    |
+| Originator information<br>NAME: choice of<br>Personal name<br>Common name<br>Free form name<br>ORGANIZATION<br>ORGANIZATIONAL UNIT(S)<br>PHYSICAL ADDRESS LINES<br>FAX NETWORK ADDRESS<br>TELEPHONE NUMBER                                                                                                                               | <br><br>O<br>O<br>O<br>O<br>O<br>O<br>O<br>O |
+| Additional recipients                                                                                                                                                                                                                                                                                                                    | (Note 2)                                     |
+| O    Provided by originating Fax SFU<br>D    Provided by destination Fax SFU<br>NOTES<br>1    Provision of service providers' images are by bilateral agreement. If joint service providers' images are required no extension to the image field size is allowed.<br>2    Display of additional recipients is an item for further study. |                                              |
+
+### **6.8 Advice of successful/unsuccessful message delivery**
+
+6.8.1 A positive L2N indicates successful message delivery and shall be returned to the originating Fax SFU on a per recipient basis. A L2N for successful message delivery shall only be returned when requested. The request shall be processed on a per recipient basis.
+
+6.8.2 A negative L2N indicates unsuccessful message delivery and shall be returned to the originating Fax SFU on a per recipient basis. It is mandatory to return a L2N for unsuccessful delivery.
+
+### **6.9 Facsimile format conversion**
+
+The facsimile format conversion service facility enables the content (image) of a facsimile message to be converted from one format to another. Conversion may be performed on the paper size, the resolution of the message and so on.
+
+When a message is transferred to another Fax SFU, the message shall be in a basic format of group 3 using facsimile format conversion unless there is a bilateral agreement. If such a bilateral agreement exists, the destination Fax SFU shall either support conversion of the image of a message to deliver it or shall not deliver a message whenever it detects that unsupported conversion is required.
+
+Conversion shall be an automatic facility and shall not require additional procedures for users. When conversion is supported in a Fax SFU, it shall be performed in a way that the image of the original message is best preserved. That is, conversion is performed only on the unsupported features trying to use values closer to the basic ones.
+
+Conversion that may result in loss of information may optionally be prohibited by the originator. The details of transferring information on conversion prohibition are for further study.
+
+The details of conversion rules and possible combinations of conversions are defined in relevant T-Series Recommendations.
+
+## **7 Quality of service**
+
+**7.1** The quality of the image, as received from the originating facsimile, terminal should not be adversely affected by any Fax SFU, transit facility, or any transmission facility between Fax SFUs through which the image may pass.
+
+**7.2** The following quality of services objectives are defined for messages passed across the international boundary for delivery by a destination Fax SFU. The overall service delivery objectives are specified in Table 3/F.162. In order that the destination Fax SFU is able to meet the objectives as stated in Table 3/F.162, the originating Fax SFU should transfer the message according to the objectives illustrated in Figure 2 and described in Table 5.
+
+The objectives for times  $T_A$  and  $T_B$  are defined in Recommendation F.162.
+
+The objectives for times  $T_1$ ,  $T_2$ , and  $T_3$  should be met for at least 95% of messages during any 1 hour period.
+
+The number of attempts to deliver a message to the destination terminal and the interval between attempts are a local matter.
+
+**7.3** The quality of service targets specified in Table 5 should not be affected by any transit or transmission facilities.
+
+**7.4** If a message is interrupted during the delivery from the destination Fax SFU to the destination terminal, subsequent attempts to deliver the message should commence with the first page not successfully delivered. The recipient shall be given sufficient information to correlate the parts of the message. In addition, the number of pages delivered in each partial transmission are required to be returned to the originating Fax SFU.
+
+**7.5** System design and dimensioning should be such that the quality of service objectives are met for at least 95% of messages received during any 1 hour period.
+
+### **7.6 Observations on the quality of service**
+
+Administrations shall make observations to evaluate the quality of the COMFAX service across national boundaries.
+
+### **7.7 Duration of service**
+
+The national and international COMFAX facilities shall be open continuously.
+
+![Sequence diagram of a fax transmission across an international boundary. The diagram shows the flow from an originating FAX terminal through a Fax SFU, across an international boundary to another Fax SFU, and finally to a destination FAX terminal. Key events include message submission, transfer, Level 1 and Level 2 notifications, and multiple delivery attempts. Timing intervals T1, T2, TA, TB, T3, and T4 are indicated on the left side.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+The diagram illustrates the sequence of operations for a fax transmission across an international boundary. The components involved are an Originating FAX terminal, a Fax SFU, an international boundary, another Fax SFU, and a Destination FAX terminal. The sequence of messages is as follows:
+
+- Message submission:** From the Originating FAX terminal to the first Fax SFU.
+- Message transfer:** From the first Fax SFU to the second Fax SFU across the international boundary.
+- Level 1 notification:** From the second Fax SFU back to the first Fax SFU.
+- Message delivery (1st attempt):** From the second Fax SFU to the Destination FAX terminal.
+- Message delivery (last attempt of retry algorithm):** From the second Fax SFU to the Destination FAX terminal.
+- Level 2 notification:** From the second Fax SFU back to the first Fax SFU.
+- Customer report:** From the first Fax SFU back to the Originating FAX terminal.
+
+Timing intervals are defined on the left side of the diagram:
+
+- $T_1$ : Time interval between message submission and message transfer.
+- $T_2$ : Time interval between message transfer and Level 1 notification.
+- $T_A$ : Time interval between message submission and Level 1 notification.
+- $T_B$ : Time interval between message submission and the start of the first delivery attempt.
+- $T_3$ : Time interval between the start of the first delivery attempt and the start of the last delivery attempt.
+- $T_4$ : Time interval between the start of the last delivery attempt and the start of the Level 2 notification.
+
+T0105990-96/d02
+
+Sequence diagram of a fax transmission across an international boundary. The diagram shows the flow from an originating FAX terminal through a Fax SFU, across an international boundary to another Fax SFU, and finally to a destination FAX terminal. Key events include message submission, transfer, Level 1 and Level 2 notifications, and multiple delivery attempts. Timing intervals T1, T2, TA, TB, T3, and T4 are indicated on the left side.
+
+#### NOTES
+
+- 1 The objectives for times  $T_A$  and  $T_B$  are defined in Recommendation F.162.
+- 2 The objectives for times  $T_1$ ,  $T_2$ , and  $T_3$  should be met for at least 95% of messages during any 1 hour period.
+- 3 The number of attempts to deliver a message to the destination terminal and the interval between attempts are a national matter.
+
+FIGURE 2/F.163
+
+TABLE 5/F.163
+
+#### **Quality of service targets**
+
+| Time           | Description                                                                                                                                                                                                                                           | Grade of delivery | Target (hours) |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------|
+| T <sub>A</sub> | Time from the end of submission of the message, or the time specified for the deferred delivery, to the start of the first call attempt                                                                                                               | Urgent            | 0.25           |
+|                |                                                                                                                                                                                                                                                       | Normal            | 1.0            |
+|                |                                                                                                                                                                                                                                                       | Non-Urgent        | 8.0            |
+| T <sub>B</sub> | Time from the end of submission of the message, or the time specified for deferred delivery, to the forced generation of a negative second level notification and termination of message delivery attempt (unless transmission has already commenced) | Urgent            | 1.0            |
+|                |                                                                                                                                                                                                                                                       | Normal            | 4.0            |
+|                |                                                                                                                                                                                                                                                       | Non-Urgent        | 212.0          |
+| T <sub>1</sub> | Time from the end of the submission of the message, or the time specified for deferred delivery, to the end of the transfer of the message from the originating Fax SFU to the destination Fax SFU                                                    | Urgent            | 0.15           |
+|                |                                                                                                                                                                                                                                                       | Normal            | 0.6            |
+|                |                                                                                                                                                                                                                                                       | Non-Urgent        | 4.8            |
+| T <sub>2</sub> | Time from the end of the transfer of the message from the originating Fax SFU to the destination Fax SFU, to the end of the transfer of the first notification from the destination Fax SFU to the originating Fax SFU                                | All               | 0.15           |
+| T <sub>3</sub> | Time from the end of message delivery, or the forced generation of a negative second level notification, to the end of the transfer of a second level notification from the destination fax SFU to the originating Fax SFU                            | All               | 0.15           |
+| T <sub>4</sub> | Time from the end of transfer of a second level notification from the destination Fax SFU to the originating Fax SFU, to the generation of a customer report                                                                                          | All               | Local matter   |
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Telephone network and ISDN
+- Series F Non-telephone telecommunication services**
+- Series G Transmission systems and media
+- Series H Transmission of non-telephone signals
+- Series I Integrated services digital network
+- Series J Transmission of sound-programme and television signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound-programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality
+- Series Q Switching and signalling
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminal equipments and protocols for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages

marked/F/T-REC-F.17-199208-I_PDF-E/raw.md

@@ -0,0 +1,89 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**CCITT**
+
+THE INTERNATIONAL  
+TELEGRAPH AND TELEPHONE  
+CONSULTATIVE COMMITTEE
+
+**F.17**
+
+(08/92)
+
+**TELEGRAPH AND MOBILE SERVICES  
+OPERATIONS AND QUALITY OF SERVICE**
+
+---
+
+**OPERATIONAL ASPECTS OF SERVICE  
+TELECOMMUNICATIONS**
+
+**Recommendation F.17**
+
+---
+
+![CCITT logo: A globe with the letters CCITT.](84a1d09fb489061482111515543b60dc_img.jpg)
+
+CCITT logo: A globe with the letters CCITT.
+
+Geneva, 1992
+
+# FOREWORD
+
+The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
+
+Recommendation F.17 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992.
+
+## --- CCITT NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized private operating agency.
+
+# **OPERATIONAL ASPECTS OF SERVICE TELECOMMUNICATIONS**
+
+(1992)
+
+## **1 Scope**
+
+- 1.1 This Recommendation lays down the general operational principles concerning service telecommunications.
+- 1.2 Additional operational provisions relating to service telecommunications in the different telecommunication services (telegram, telephone, telex, etc.) may be found in the Recommendations (and Instructions) specific to those services (F.1, E.105, F.60, etc.).
+- 1.3 The principles for charging and accounting for service telecommunications are given in Recommendation D.192.
+
+## **2 Definition and basic principles**
+
+- 2.1 Article 2 of the International Telecommunication Regulations (Melbourne, 1988) defines **service telecommunications** as:
+
+A telecommunication that relates to public international telecommunications and that is exchanged among the following:
+
+- Administrations;
+  - recognized private operating agencies; and
+  - the Chairman of the Administrative Council, the Secretary-General, the Deputy Secretary-General, the Directors of the International Consultative Committees, the members of the International Frequency Registration Board, other representatives or authorized officials of the International Telecommunication Union, including those working on official matters outside the seat of the Union.
+- 2.2 Appendix 3 of the same Regulations states that service telecommunications may be provided free of charge<sup>1)</sup>.
+  - 2.3 Service telecommunications should be established outside the busiest hours as far as possible, and should be kept to a minimum in number and length consistent with efficient operation.
+
+## **3 Content of service telecommunications**
+
+- 3.1 Service telecommunications as identified in § 2.1 must relate to the business of providing international telecommunication services, i.e. the doing of all things needful to provide, to administer and to maintain services, such as the establishment and maintenance of circuits, network management, accounting, handling of customer complaints, etc.
+- 3.2 Service telecommunications may only be requested or established by persons authorized to do so by their respective Administration.
+
+## **4 Corresponding arrangements between Administrations**
+
+- 4.1 An Administration that routes service telecommunications over facilities owned or operated by another Administration in a given relation, should allow its facilities to be used in a similar manner to carry service telecommunications originated by the latter Administration.
+- 4.2 This principle may be applied not only to a given telecommunication service in a relation but also between services in that relation.
+
+---
+
+<sup>1)</sup> Service telecommunications are normally, but not automatically, provided free of charge.
+
+## 5 Communications with and via the ITU
+
+5.1 Where appropriate, service telecommunications may be used for official communications between Administrations and the ITU, e.g. for the purposes described in Article 8 of the International Telecommunication Regulations and in Resolution No. 7 of the World Administrative Telegraph and Telephone Conference (Melbourne, 1988).
+
+*Note* — Privilege telecommunications (see Recommendation D.193) are not service telecommunications, although the treatment of this optional class of traffic may be similar.

marked/F/T-REC-F.170-199803-I_PDF-E/raw.md

@@ -0,0 +1,465 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.170**
+
+(03/98)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Telematic services – Public facsimile service
+
+---
+
+**Operational provisions for the international  
+public facsimile service between public bureaux  
+(Bureaufax)**
+
+ITU-T Recommendation F.170
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+## **TELEGRAPH SERVICE**
+
+|                                                                 |             |
+|-----------------------------------------------------------------|-------------|
+| Operating methods for the international public telegram service | F.1–F.19    |
+| The gentex network                                              | F.20–F.29   |
+| Message switching                                               | F.30–F.39   |
+| The international telemessage service                           | F.40–F.58   |
+| The international telex service                                 | F.59–F.89   |
+| Statistics and publications on international telegraph services | F.90–F.99   |
+| Scheduled and leased communication services                     | F.100–F.104 |
+| Phototelegraph service                                          | F.105–F.109 |
+
+## **MOBILE SERVICE**
+
+|                                                        |             |
+|--------------------------------------------------------|-------------|
+| Mobile services and multdestination satellite services | F.110–F.159 |
+|--------------------------------------------------------|-------------|
+
+## **TELEMATIC SERVICES**
+
+|                                           |                    |
+|-------------------------------------------|--------------------|
+| <b>Public facsimile service</b>           | <b>F.160–F.199</b> |
+| Teletex service                           | F.200–F.299        |
+| Videotex service                          | F.300–F.349        |
+| General provisions for telematic services | F.350–F.399        |
+
+## **MESSAGE HANDLING SERVICES**
+
+F.400–F.499
+
+## **DIRECTORY SERVICES**
+
+F.500–F.549
+
+## **DOCUMENT COMMUNICATION**
+
+|                                      |             |
+|--------------------------------------|-------------|
+| Document communication               | F.550–F.579 |
+| Programming communication interfaces | F.580–F.599 |
+
+## **DATA TRANSMISSION SERVICES**
+
+F.600–F.699
+
+## **AUDIOVISUAL SERVICES**
+
+F.700–F.799
+
+## **ISDN SERVICES**
+
+F.800–F.849
+
+## **UNIVERSAL PERSONAL TELECOMMUNICATION**
+
+F.850–F.899
+
+## **HUMAN FACTORS**
+
+F.900–F.999
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## **ITU-T RECOMMENDATION F.170**
+
+# **OPERATIONAL PROVISIONS FOR THE INTERNATIONAL PUBLIC FACSIMILE SERVICE BETWEEN PUBLIC BUREAUX (BUREAUFAX)**
+
+## **Summary**
+
+In accordance with the general conditions of Recommendation F.160, this Recommendation describes an international public facsimile service between public bureaux, provided that terminals are compatibles or compatibility is ensured by the network from the standpoint of the characteristics specified in the relevant Recommendations and in accordance with bilateral or multilateral agreements. This service, known internationally as Bureaufax, may be provided by telecommunication Recognized Operating Agencies (ROA) or by postal Administrations.
+
+###### **Source**
+
+ITU-T Recommendation F.170 was revised by ITU-T Study Group 2 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 9th of March 1998.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1998
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+|                                                                                                                                                            | <i>Page</i> |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| 1 General provisions .....                                                                                                                                 | 1           |
+| 2 Conditions for acceptance .....                                                                                                                          | 1           |
+| 3 Composition of a facsimile transmission.....                                                                                                             | 2           |
+| 3.2 Transmittal sheet.....                                                                                                                                 | 2           |
+| 3.3 Sender's document.....                                                                                                                                 | 2           |
+| 4 Acceptance .....                                                                                                                                         | 2           |
+| 5 Transmission .....                                                                                                                                       | 4           |
+| 6 Delivery.....                                                                                                                                            | 4           |
+| 7 Service facsimile correspondence .....                                                                                                                   | 5           |
+| 8 Archives .....                                                                                                                                           | 5           |
+| 9 Charging, refunds and accounting.....                                                                                                                    | 5           |
+| 10 Cancellation at the request of the sender .....                                                                                                         | 6           |
+| 11 Bureaufax table .....                                                                                                                                   | 6           |
+| 12 Bureaufax service via the public switched telephone network, via a public data network, via ISDN or via facilities dedicated to Bureaufax service ..... | 6           |
+| Annex A – Definitions of delivery modes .....                                                                                                              | 7           |
+| A.1 Letter-post item (mode A) .....                                                                                                                        | 7           |
+| A.2 Delivery by special messenger (mode B).....                                                                                                            | 7           |
+| A.3 EMS (Express Mail Service) (mode C) .....                                                                                                              | 7           |
+| A.4 Counter collection (mode D) .....                                                                                                                      | 7           |
+| A.5 Counter collection with advice (modes E, G) .....                                                                                                      | 7           |
+| A.6 Telefax (mode F) .....                                                                                                                                 | 7           |
+| Bibliography.....                                                                                                                                          | 7           |
+
+
+
+## OPERATIONAL PROVISIONS FOR THE INTERNATIONAL PUBLIC FACSIMILE SERVICE BETWEEN PUBLIC BUREAUX (BUREAUFAX)
+
+*(revised in 1998)*
+
+## 1 General provisions
+
+1.1 In accordance with the general conditions of Recommendation F.160, this Recommendation describes an international public facsimile service between public bureaux, provided that terminals are compatible or compatibility is ensured by the network from the standpoint of the characteristics specified in the relevant Recommendations and in accordance with bilateral or multilateral agreements. This service, known internationally as Bureaufax, may be provided by telecommunication Recognized Operating Agencies (ROA) or by Postal Administrations. For the purposes of this Recommendation only, both are comprised in the term "service providers".
+
+NOTE 1 – The operation of the international public facsimile service between public bureaux and subscriber stations and vice versa is covered by Recommendation F.190.
+
+NOTE 2 – Where agreed between the relevant service providers, telegrams and teletext messages may also be transmitted directly via facsimile from the origin country to a public facsimile bureau of the destination country and delivered by the Bureaufax service in the destination country.
+
+1.2 Facsimile terminals should have automatic operation of the called station. The operational procedures applicable in relations between the different types of stations are set out in the relevant Recommendations in the T-Series.
+
+## 2 Conditions for acceptance
+
+2.1 Documents for facsimile transmission shall normally be accepted up to a maximum size of ISO format A4 (210 × 297 mm). Documents with larger sizes can be accepted only if the transmission can be done within the ISO format A4. Exceptionally, documents of a different size may be accepted by bilateral agreement between those service providers concerned, for example the North American "legal" size (216 × 356 mm).
+
+2.2 For faithful transmission, contents of documents must leave minimum blank margins of 8 mm on all four sides. With regard to the reproduction in formats other than A4 which have been bilaterally agreed, the margins to be left on all four sides of the documents shall be 15 mm.
+
+2.3 Where the area to be transmitted exceeds the area reproducible by facsimile, a document should be divided by the sender or his authorized representative.
+
+2.4 Care must be taken to ensure that there is no loss of the reproducible part transmitted.
+
+2.5 To ensure the satisfactory facsimile transmission of a document, senders should be advised not to submit documents with insufficiently sharp contrast or inadequate definition.
+
+2.6 If the sender or his authorized representative presents a document containing colours of half-tones, he should be informed that, with existing equipment, faithful reproduction at the distant end will not be possible as printing will be in black and white only.
+
+2.7 If, after having been informed that the quality of the document to be transmitted is unsuitable for satisfactory facsimile transmission (this includes all photographs and documents in colour), the sender of the document or his authorized representative still insists on its transmission, it shall be accepted by the public bureau only at the sender's own risk. In this event the service instruction **RISQUES EXPÉDITEUR** (abbreviated **RE**) must be inserted in box 6 on the transmittal sheet (see Figure 1). When the service instruction **RE** is not applicable to the whole document, the relevant pages must be designated in box 6 of the transmittal sheet, for example: **RE 3 + 5 + 12**.
+
+2.8 Administrations shall reserve the right to refuse the transmission of documents in the circumstances described in Articles 34 and 35 of the ITU Constitution [1] and in Article 26 of the Universal Postal Union Convention [2].
+
+## 3 Composition of a facsimile transmission
+
+### 3.1 Every facsimile transmission shall include:
+
+- a transmittal sheet as the first page, in accordance with 3.2; and
+- a sender's document in accordance with 3.3.
+
+### 3.2 Transmittal sheet
+
+#### 3.2.1 The transmittal sheet must permit the identification of the following information:
+
+- 1) originating office and optional, originating number of the document;
+- 2) international transmitting bureau (sending office);
+- 3) document sending number;
+- 4) number of pages (including the transmittal sheet);
+- 5) date and, if necessary, time of acceptance;
+- 6) service instruction **RE (RISQUES EXPÉDITEUR)** in accordance with 2.7, if applicable;
+- 7) delivery mode, in coded form, and other service instructions, if any and the call number for delivery modes **E**, **F** and **G**;
+- 8) the addressee's address containing all the particulars necessary to ensure the routing and delivery of the facsimile document without enquiries or requests for information. As a general rule, it should indicate:
+  - i) the designation of the addressee;
+  - ii) his full postal address (including, if it exists, the postal code) and, if available, his telephone, and telex number;
+- 9) sender's address (including, if it exists, the postal code) and, if available, his telephone and/or telex number.
+
+NOTE – Items 1) and 9) may be omitted from the transmittal sheet if this information can be traced from other information provided elsewhere on the form.
+
+#### 3.2.2 The various parts of the transmittal sheet shall be contained within ISO format A5 (210 × 148 mm). They may also be located in the upper half of a sheet of ISO format A4 so that the sender can use the lower half to write a document.
+
+NOTE – If a North American format is used for the transmittal sheet, the width of the sheet will be 216 mm (instead of 210 mm).
+
+#### 3.2.3 The various parts of the transmittal sheet shall be designated at least in French or in English or in Spanish. Other languages may be added by service providers.
+
+#### 3.2.4 Figure 1 shows the measurements, locations and designations of the various parts of the transmittal sheet.
+
+### 3.3 Sender's document
+
+#### 3.3.1 The document for facsimile transmission can contain written or printed matter, drawings, or any other graphic, subject to the limitations referred to under conditions for acceptance in clause 2 above. A signature is optional.
+
+## 4 Acceptance
+
+### 4.1 A document for facsimile transmission may be handed in at the counter of a public bureau. Other means of acceptance and the modes of returning the original to the sender after transmission may be designated by the service provider responsible for the public bureau.
+
+### 4.2 The sender may use transmittal sheets that consist of the A4 version in accordance with 3.2.2, if available, for writing out a document in the lower half of the sheet.
+
+### 4.3 The sender of a facsimile document shall be required to establish his identity if called upon to do so by the accepting public facsimile bureau.
+
+![Diagram of a transmittal sheet with measurements, locations, and designations of various parts. The sheet is 148 mm high and 210 mm wide. It contains several numbered boxes: 1. Originating office, Document originating No., Telephone No.; 2. Sending office; 3. Document sending number; 4. Pages; 5. Date (and time) with 'Acceptance-sending' and 'Receiving' options; 6. *) with 'RE' option; 7. Delivery mode and service instructions; 8. Addressee (including postal code); 9. Sender (including postal code). Dimensions are marked: 45 mm for boxes 2-5, 15 mm for box 7, 42 mm for box 8, 15 mm for the bottom section, 80 mm for the left part of box 9, 10 mm for the middle part of box 9, 90 mm for the right part of box 9, and 8.2 mm for the bottom right corner of box 8.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg)
+
+Diagram of a transmittal sheet with measurements, locations, and designations of various parts. The sheet is 148 mm high and 210 mm wide. It contains several numbered boxes: 1. Originating office, Document originating No., Telephone No.; 2. Sending office; 3. Document sending number; 4. Pages; 5. Date (and time) with 'Acceptance-sending' and 'Receiving' options; 6. \*) with 'RE' option; 7. Delivery mode and service instructions; 8. Addressee (including postal code); 9. Sender (including postal code). Dimensions are marked: 45 mm for boxes 2-5, 15 mm for box 7, 42 mm for box 8, 15 mm for the bottom section, 80 mm for the left part of box 9, 10 mm for the middle part of box 9, 90 mm for the right part of box 9, and 8.2 mm for the bottom right corner of box 8.
+
+a) North American standard: 216 mm.
+
+\*) Insert "RE" in box 6 in case the message is accepted at the sender's own risk.
+
+NOTE 1 – The information in boxes 1 and 9 need not necessarily be transmitted and may be inserted elsewhere on the sheet. When the information in box 9 (sender) is given on the front of the sheet, it must appear in the left-hand part.
+
+NOTE 2 – In box 5, the time and words "acceptance-sending" and "receiving" are optional.
+
+NOTE 3 – Concerning box 7, the following delivery modes may be supplied on the basis of agreements between the service providers concerned (for definitions, see Annex A):
+
+|   |                                                                       |                                                                            |                                                                            |
+|---|-----------------------------------------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------|
+| A | Letter-post item                                                      | <i>Courrier ordinaire</i>                                                  | <i>Correo ordinario</i>                                                    |
+| B | Delivery by special messenger (express item)                          | <i>Porteur spécial</i>                                                     | <i>Urgente (entrega efectuada por un mensajero especial)</i>               |
+| C | EMS item (Express Mail Service)                                       | <i>EMS (service de courrier exprès)</i>                                    | <i>EMS (servicio de correo urgente)</i>                                    |
+| D | Counter collection                                                    | <i>Retrait au guichet</i>                                                  | <i>Recogida en ventanilla</i>                                              |
+| E | Counter collection with telephone advice to the indicated call number | <i>Retrait au guichet avec avis téléphonique au numéro indiqué</i>         | <i>Recogida en ventanilla con aviso telefónico al número indicado</i>      |
+| F | Telefax (with call number and ITU-T Group when known)                 | <i>Téléfax (avec numéro d'appel et, s'il est connu, groupe de l'UIT-T)</i> | <i>Telefax (con número de llamada y grupo del UIT-T cuando se conozca)</i> |
+| G | Counter collection with telex advice to the indicated call number     | <i>Retrait au guichet avec avis télex au numéro indiqué</i>                | <i>Recogida en ventanilla con aviso télex al número indicado</i>           |
+| T | Telegram                                                              | <i>Télégramme</i>                                                          | <i>Telegrame</i>                                                           |
+
+Other modes of delivery may be agreed between service providers.
+
+**Figure 1/F.170 – Measurements, locations and designations of the various parts of the transmittal sheet in accordance with 3.2**
+
+## 5 Transmission
+
+5.1 In principle, documents shall be transmitted by a public bureau in the order in which they are accepted, except where a priority system is established.
+
+NOTE – In the case of facsimile transmission of telegrams and telemessages, the priorities for transmission of these services have to be considered.
+
+5.2 At the request of the international transmitting public bureau, on a case-by-case basis and immediately after the transmission, the international receiving public bureau will acknowledge the satisfactory receipt of a facsimile document.
+
+5.3 A transmission prevented by adverse conditions shall be repeated as soon as conditions allow.
+
+In case of unsatisfactory receipt, the international receiving public bureau should indicate service instruction **RPT PAGE** ... in box 7 of the transmittal sheet.
+
+After a maximum of three attempts, the international transmitting public bureau should, if practicable, use another transmission means among those listed in 3.4/F.18. If this is not practicable, the sender will be informed of the situation by the transmitting public bureau in his country.
+
+5.4 If transmission cannot be effected by the international transmitting public bureau within four hours of acceptance by the public facsimile bureau, the sender should be informed as soon as possible by the transmitting bureau in his country.
+
+5.5 On no account will the international receiving public bureau request repeat transmissions in an attempt to improve the quality of facsimile reproduction of pages designated as unsuitable by the service instruction **RE**.
+
+5.6 Any two service providers may agree to apply special operational procedures in their mutual relation when there is a large volume of messages being sent to a given office, or in other special cases.
+
+## 6 Delivery
+
+6.1 The service providers determine the mode of delivery they use for the facsimile documents they receive, according to Figure 1, Note 3. The modes of delivery used by each service provider should figure in the Bureaufax table (see clause 11).
+
+NOTE – If a telegram<sup>1</sup> or a telemessage<sup>2</sup> is transmitted to a public facsimile bureau for delivery, the delivery modes of the Bureaufax service laid down in 6.4 will apply:
+
+- urgent telegrams are delivered according to the delivery mode B or C;
+- ordinary telegrams are delivered according to the delivery mode A;
+- letter telegrams and telemessages are delivered according to the delivery mode A.
+
+6.2 The facsimile documents received by an international receiving public bureau are, as far as possible, delivered to the addressee according to the mode of delivery indicated in box 7 of the facsimile transmittal sheet.
+
+6.3 The receiving public bureau shall, if required, record the date and time of receipt and the mode of delivery of each facsimile document.
+
+6.4 Facsimile documents should be delivered to the addressee within the following times from the moment when the international receiving public bureau is able to process the documents received (the hours when the receiving public bureau is closed are not taken into account for delivery times):
+
+Mode of delivery A:                      delivery next working day after receipt;
+
+Mode of delivery B:                      places of delivery having a Bureaufax bureau: four hours;
+
+places of destination without a Bureaufax bureau: as provided by the service provider responsible for the Bureaufax special delivery service;
+
+<sup>1</sup> For details, see Recommendation F.1 for telegrams.
+
+<sup>2</sup> For details, see Recommendations F.40 and F.41 for telemessages.
+
+Mode of delivery C:                places of delivery having a Bureaufax bureau and places of destination without a Bureaufax bureau: documents received before 1200 noon on working days, delivery the same day; documents received after 1200 noon on working days, delivery the next working day;
+
+Mode of delivery D:              collection from the counter of the receiving public bureau: one hour after receipt;
+
+Method of delivery E, F, G:    the addressee is called within one hour by the receiving public bureau. If this cannot reach the addressee within three hours, the destination service provider may apply another method of delivery, to deliver the facsimile document to the addressee as soon as possible.
+
+NOTE – If the destination service provider cannot comply with the established times, other times may be agreed between service providers in relation to the ordinary postal service times.
+
+**6.5**        The addressee of a facsimile document must establish his identity if required to do so by the receiving public bureau.
+
+**6.6**        The addressee of a facsimile document with the service instruction **RE** in accordance with 2.7 above shall be obliged to accept the quality of facsimile reproduction offered.
+
+**6.7**        When a facsimile document cannot be delivered to the addressee, the destination service provider must advise the international transmitting public bureau of the origin service provider, giving the reason for non-delivery. Box 7 of the Bureaufax transmittal sheet can be used to this effect. The service providers can agree to transmit this information through other telecommunication services like telex, etc. The origin service provider should notify the sender giving the reason why a document was not delivered.
+
+NOTE – If an origin country transmits a telegram or a telemessage to the destination country by facsimile this subclause will also apply.
+
+## **7        Service facsimile correspondence**
+
+**7.1**        By agreement between service providers (see Recommendation F.17), service facsimile correspondence may be exchanged between the service providers concerned for the purposes mentioned below:
+
+- to exchange communications between the service providers concerned for the efficient operation of the Bureaufax service as necessary, including communications concerning enquiries or claims from customers in connection with the Bureaufax service;
+- to exchange communications between the service providers concerned in connection with other telecommunication services provided mutually by these service providers, in particular urgent communications that cannot be effected by other telecommunication means, e.g. by international telex or telegram services, because they contain diagrammatic material or other material where it is important for the original to be exactly reproduced.
+
+NOTE – The indication **SERVICE** should be clearly shown on the transmittal sheet.
+
+**7.2**        The service providers should reply to the requests for information and claims by correspondence within 15 days of receipt of the request.
+
+## **8        Archives**
+
+**8.1**        The maintenance of archives shall be at the discretion of the individual service providers concerned which will decide on the most suitable arrangements to answer any subsequent queries, in particular on the international accounts.
+
+## **9        Charging, refunds and accounting**
+
+**9.1**        Charging principles, refund of charges and international accounting for the transmission of documents in the international public facsimile service between public bureaux are governed by Recommendations, agreements and/or Conventions such as are given in Recommendation D.70.
+
+## **10 Cancellation at the request of the sender**
+
+**10.1** Where permitted by the service provider concerned, the sender of a facsimile document, or his authorized representative, may, upon establishing his identity or authority, cancel his document provided its international transmission has not begun.
+
+**10.2** In the case of multipage facsimile documents, pages of which the international transmission has not yet begun may be cancelled. If pages have already been transmitted, the international transmitting public bureau must amend accordingly the number of pages cited on the transmittal sheet and request the receiving public bureau to do likewise.
+
+This amendment goes at the end of the transmission, through a new transmittal sheet, giving the correct number of pages effectively transmitted. This second transmittal sheet shall contain the necessary information to identify the sheet initially transmitted.
+
+**10.3** At the sender's request, pages already received by the receiving public bureau may be either delivered to the addressee or destroyed according to the instructions of the sender.
+
+## **11 Bureaufax table**
+
+**11.1** This table contains the information required for routing traffic as well as useful information concerning operational aspects of the service offered by the service provider concerned.
+
+**11.2** With the authorization and/or coordination of the relevant Administration, each service provider participating in the Bureaufax service should supply information required for the Bureaufax table to the ITU, either directly or through the International Bureau of the UPU. All subsequent amendments should be communicated by the Administration concerned in the same manner as they arise.
+
+**11.3** The ITU publishes this information periodically in the Bureaufax table, with subsequent amendments appearing in the Operational Bulletin.
+
+NOTE – The number of gateway bureaux must be kept to a reasonable limit. For guidance, see Bureaufax table.
+
+## **12 Bureaufax service via the public switched telephone network, via a public data network, via ISDN or via facilities dedicated to Bureaufax service**
+
+**12.1** The special provisions applicable in the case of international public facsimile service via the public switched telephone network are normally those indicated in Recommendation F.182.
+
+**12.2** Special provisions applicable in the case of international public facsimile service via a public data network are being studied.
+
+**12.3** Special provisions applicable in the case of international public facsimile service via the integrated services digital network are for further study.
+
+**12.4** Special provisions applicable in the case of international public facsimile service via dedicated circuits are for further study.
+
+**12.5** Special provisions applicable in the case of international public facsimile service using a store-and-forward switching facilities are those indicated in Recommendation F.171.
+
+**12.6** Special provisions applicable in the case of international public facsimile using MH services are for further study.
+
+## Annex A
+
+### Definitions of delivery modes (see Figure 1)
+
+#### **A.1 Letter-post item (mode A)<sup>3</sup>**
+
+This delivery mode enables the receiving service provider to transport and deliver the Bureaufax message through the letter-mail service in the country of destination. This mode is utilized for the transport and delivery of a physical message in case no other mode is requested (default action). In countries of destination where letter-post items are classified according to speed, Bureaufax messages are sent as priority items (1st class, "A" mail, etc.).
+
+#### **A.2 Delivery by special messenger (mode B)<sup>4</sup>**
+
+This delivery mode allows an originating user to instruct the receiving service provider to transport the Bureaufax message through the ordinary letter-mail circulation system and to deliver it by special messenger delivery.
+
+#### **A.3 EMS (Express Mail Service) (mode C)<sup>5</sup>**
+
+This delivery mode allows an originating user to instruct the receiving service provider to transport and deliver the Bureaufax message through the quickest postal service by physical means available in the destination country [Express Mail Service (EMS) or the equivalent domestic service]. Whilst delivery mode B only provides for fast delivery at the place of destination, delivery mode C means both fast transport from the receiving public bureau to the place of destination as well as fast delivery.
+
+#### **A.4 Counter collection (mode D)**
+
+This delivery mode allows an originating user to instruct the receiving service provider to keep the Bureaufax message ready for counter collection at the Bureaufax office specified by the originator, or at the Bureaufax office which offers counter collection service closest to the given recipient's address.
+
+#### **A.5 Counter collection with advice (modes E, G)**
+
+This delivery mode allows an originating user to instruct the receiving service provider to keep the Bureaufax message ready for counter collection at the Bureaufax office specified by the originator, or at the Bureaufax office which offers counter collection service closest to the given recipient's address, and to inform the recipient via telephone, or telex, using the number provided by the originator.
+
+#### **A.6 Telefax (mode F)**
+
+This delivery mode allows an originating user to instruct the accepting service provider to transmit the message to the telefax terminal of a private subscriber.
+
+These definitions are in alignment with the respective definitions of physical delivery elements of service as given in Annex B/F.400.
+
+## **Bibliography**
+
+- [1] International Telecommunication Constitution, Geneva, 1992.
+- [2] Universal Postal Union Convention, Seoul, 1994.
+
+---
+
+<sup>3</sup> The corresponding service on international postal level is described in Article 9 of the Universal Postal Convention (Seoul 1994) (Article 19 of the 1989 Washington Convention).
+
+<sup>4</sup> The corresponding express delivery service on international postal level is described in Article 19 of the Universal Postal Convention (Seoul 1994) (Article 35 of the 1989 Washington Convention).
+
+<sup>5</sup> The corresponding service on international postal level is described in Article 57 of the Universal Postal Convention (Seoul 1994) (Article 92 of the 1989 Washington Convention).
+
+
+
+# ITU-T RECOMMENDATIONS SERIES
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of the ITU-T                                                                                          |
+| Series B        | Means of expression: definitions, symbols, classification                                                                      |
+| Series C        | General telecommunication statistics                                                                                           |
+| Series D        | General tariff principles                                                                                                      |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                              |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                |
+| Series G        | Transmission systems and media, digital systems and networks                                                                   |
+| Series H        | Audiovisual and multimedia systems                                                                                             |
+| Series I        | Integrated services digital network                                                                                            |
+| Series J        | Transmission of television, sound programme and other multimedia signals                                                       |
+| Series K        | Protection against interference                                                                                                |
+| Series L        | Construction, installation and protection of cables and other elements of outside plant                                        |
+| Series M        | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                |
+| Series O        | Specifications of measuring equipment                                                                                          |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                   |
+| Series Q        | Switching and signalling                                                                                                       |
+| Series R        | Telegraph transmission                                                                                                         |
+| Series S        | Telegraph services terminal equipment                                                                                          |
+| Series T        | Terminals for telematic services                                                                                               |
+| Series U        | Telegraph switching                                                                                                            |
+| Series V        | Data communication over the telephone network                                                                                  |
+| Series X        | Data networks and open system communications                                                                                   |
+| Series Y        | Global information infrastructure                                                                                              |
+| Series Z        | Programming languages                                                                                                          |

marked/F/T-REC-F.171-198811-I_PDF-E/raw.md

@@ -0,0 +1,137 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features the letters 'ITU' in a bold, sans-serif font, superimposed on a stylized globe with intersecting lines.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**F.171**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**OPERATIONS AND QUALITY OF SERVICE  
+TELEMATIC SERVICE**
+
+---
+
+**OPERATIONAL PROVISIONS RELATING TO  
+THE USE OF STORE - AND - FORWARD  
+SWITCHING NODES WITHIN THE  
+BUREAUFAX SERVICE**
+
+**ITU-T Recommendation F.171**
+
+(Extract from the *Blue Book*)
+
+---
+
+# NOTES
+
+1 ITU-T Recommendation F.171 was published in Fascicle II.5 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below).
+
+2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+## **OPERATIONAL PROVISIONS RELATING TO THE USE OF STORE-AND-FORWARD SWITCHING NODES WITHIN THE BUREAUFAX SERVICE**
+
+### **1 General provisions**
+
+1.1 In accordance with Recommendations F.160 and F.170, Administrations may operate an international public facsimile service between public bureaux. Additionally, in accordance with Recommendation F.190. Administrations may operate a service between public bureaux and private subscribers' stations.
+
+1.2 In the bureaufax service, it is not uncommon for the transmitted document to be scanned and transmitted several times as it progresses from the office of origin to the office of destination. With each rescan and retransmission, the quality of the document, as finally delivered to the addressee is progressively degraded. By the replacement of manual retransmission practices with switching nodes, employing store-and-forward techniques, document quality may be preserved. Quality may even be improved over current transmission practices through the use of error handling techniques between nodes and the use of data networks, rather than the telephone network, as the transmission medium,
+
+1.3 This Recommendation states the operational provisions peculiar to the bureaufax service when store-and-forward facsimile switching nodes are employed within the international transmission of documents.
+
+### **2 Conditions of acceptance**
+
+2.1 Documents for transmission within the bureaufax service and between subscriber stations and public bureaux shall conform to § 2 of Recommendation F.170.
+
+### **3 Composition of a facsimile transmission**
+
+3.1 Every facsimile transmission shall include a transmittal sheet and the customer's document as defined in § 3 of Recommendation F.170
+
+### **4 Acceptance**
+
+#### *4.1 Acceptance at a public bureau*
+
+The acceptance of documents at the counter of a public bureau will conform to § 4 of Recommendation F.170.
+
+#### *4.2 Acceptance from subscribers' stations*
+
+4.2.1 A document for delivery through the bureaufax service may be accepted directly from the subscriber's station into store and forward node in the country of origination.
+
+4.2.2 The customer will access the store and forward node in conformance with the provisions of Recommendation F.162. At the discretion of the administration in the country of origin, the customer must be a registered user of the service.
+
+4.2.3 The Administration in the country of origin will provide users of the service with the information necessary to route the document through the store and forward node, and any interconnected store and forward node, to the appropriate public bureau in the country of destination. The addressing of such facsimile messages should use abbreviated dialling codes rather than explicit telephone numbers for the facsimile terminals in the destination bureau.
+
+4.2.4 The correct addressing of the facsimile message will be the responsibility of the originating subscriber.
+
+4.2.5 As for transmissions originating from a public bureau, messages entered into the bureaufax service by a subscriber must contain a transmittal sheet, in accordance with F.170, § 3.2, as the first page. The Administration in the country of origin will ensure that transmittal forms are available to its subscribers.
+
+4.2.6 Acceptance of the facsimile document by the node will constitute acceptance into the bureaufax service.
+
+4.2.7 Facsimile documents to be entered into the bureaufax service may, optionally, be accepted from text terminals in cases where the node can provide the necessary conversion to the appropriate facsimile format. In such cases, the transmittal sheet may be generated either by the originating terminal or by the node.
+
+### 5 Transmission
+
+5.1 International bureaufax transmissions may involve store and forward switching nodes, typically at gateway locations, in three different ways:
+
+- nodes in both the country of origin and country of destination,
+- node located in the country of origin,
+- node located in the country of destination.
+
+In any case, each node will be programmed with abbreviated codes for delivering documents to inland public bureaux. These abbreviated codes will be made available to other administrations for the efficient routing of traffic.
+
+#### 5.1.1 *Nodes in both countries*
+
+5.1.1.1 Facsimile documents will be entered into the node both by public bureaux and by private subscribers.
+
+5.1.1.2 Documents will be transmitted between nodes in accordance with Recommendation F.162, § 4.6. Wherever possible, the routing between nodes will employ networks designed specifically for the transmission of data to preserve a maximum quality of delivered document. This is important since the end-to-end transmission may still involve multiple scans and retransmissions.
+
+5.1.1.3 If the quality of the document received at the public bureau in the country of destination is not satisfactory, the receiving bureau will contact the assistance operator at the node in the country of destination, who, following confirmation that the document held in store in the node is acceptable, will initiate a retransmission.
+
+5.1.1.4 If the quality of the document held in store by the node in the country of destination is not satisfactory, the operator will contact the assistance operator at the node in the country of origin who, following confirmation that the document held in store there is acceptable, will initiate a retransmission.
+
+5.1.1.5 If the quality of the document held in store by the node in the country of origin is not satisfactory, the operator will request retransmission from the originating public bureau or subscriber.
+
+#### 5.1.2 *Node in the country of origin*
+
+5.1.2.1 The international transmission from the node in the country of origin to the public bureau in the country of destination will comply with Recommendation F.170, § 5, with the following exceptions:
+
+5.1.2.2 If a document received at the international receiving public station is not satisfactory, the international receiving public station will contact the assistance operator at the node in the originating country to request retransmission. The assistance operator will act in accordance with § 5.1.1.5 above.
+
+#### 5.1.3 *Node in the destination country*
+
+5.1.3.1 Except by bilateral agreement, the node in the destination country will accept facsimile transmissions from the country of origin in a manner emulating a facsimile terminal, i.e. the originating country's operator need not be knowledgeable of any special procedures to deposit the document into the node. In this case, transmission is in conformance with § 5 of Recommendation F.170 except that the node acts as the international receiving public facsimile station.
+
+5.1.3.2 Documents received by the node in the above manner will be routed to the destination public bureau through manual intervention.
+
+### 6 Delivery
+
+6.1 Delivery of facsimile messages by the destination public facsimile bureau will generally comply with § 6 of Recommendation F.170.
+
+6.2 Delivery of bureaufax messages to subscribers' stations will generally comply with § 2 of Recommendation F. 190.
+
+6.2.1 In cases where a store and forward node exists in the country of destination, the message will be transmitted to the subscribers' stations directly from the node, without recourse to an additional stage of printing and rescanning the document.
+
+6.2.2 By bilateral agreement, the facsimile transmitting station in the country of origin may provide the node with sufficient information to effect automatic switching and retransmission of the message directly to subscribers' stations. Otherwise, transmission to subscribers' stations will be effected by manual intervention of the node operator.
+
+6.2.3 By bilateral agreement in cases where a node exists only in the country of origin, facsimile messages may be transmitted directly from the node to subscribers' stations in the country of destination.
+
+### **7 Other provisions**
+
+Provisions relating to:
+
+- Service facsimile correspondence
+- Archives
+- Charging, refunds and accounting
+- Cancellation at the request of the sender
+- List of public bureaux
+
+will conform to the appropriate section of Recommendation F.170.

marked/F/T-REC-F.18-199803-I_PDF-E/raw.md

@@ -0,0 +1,376 @@
+
+
+![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: A globe with a lightning bolt and the letters ITU.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.18**
+
+(03/98)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Telegraph service – Operating methods for the  
+international public telegram service
+
+---
+
+**Guidelines on harmonization of international  
+public bureau services**
+
+ITU-T Recommendation F.18
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                        |                 |
+|------------------------------------------------------------------------|-----------------|
+| TELEGRAPH SERVICE                                                      |                 |
+| <b>Operating methods for the international public telegram service</b> | <b>F.1–F.19</b> |
+| The gentex network                                                     | F.20–F.29       |
+| Message switching                                                      | F.30–F.39       |
+| The international telemessage service                                  | F.40–F.58       |
+| The international telex service                                        | F.59–F.89       |
+| Statistics and publications on international telegraph services        | F.90–F.99       |
+| Scheduled and leased communication services                            | F.100–F.104     |
+| Phototelegraph service                                                 | F.105–F.109     |
+| MOBILE SERVICE                                                         |                 |
+| Mobile services and multdestination satellite services                 | F.110–F.159     |
+| TELEMATIC SERVICES                                                     |                 |
+| Public facsimile service                                               | F.160–F.199     |
+| Teletex service                                                        | F.200–F.299     |
+| Videotex service                                                       | F.300–F.349     |
+| General provisions for telematic services                              | F.350–F.399     |
+| MESSAGE HANDLING SERVICES                                              | F.400–F.499     |
+| DIRECTORY SERVICES                                                     | F.500–F.549     |
+| DOCUMENT COMMUNICATION                                                 |                 |
+| Document communication                                                 | F.550–F.579     |
+| Programming communication interfaces                                   | F.580–F.599     |
+| DATA TRANSMISSION SERVICES                                             | F.600–F.699     |
+| AUDIOVISUAL SERVICES                                                   | F.700–F.799     |
+| ISDN SERVICES                                                          | F.800–F.849     |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                                   | F.850–F.899     |
+| HUMAN FACTORS                                                          | F.900–F.999     |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+# **ITU-T RECOMMENDATION F.18**
+
+# **GUIDELINES ON HARMONIZATION OF INTERNATIONAL PUBLIC BUREAU SERVICES**
+
+## **Summary**
+
+This Recommendation contains the general concept for the harmonized application of international public bureau services. It is intended to guide Administrations/ROAs in implementing Recommendation F.11 (Continued availability of traditional services).
+
+###### **Source**
+
+ITU-T Recommendation F.18 was revised by ITU-T Study Group 2 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 9th of March 1998.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+### INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1998
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+|                                                                                             | <i>Page</i> |
+|---------------------------------------------------------------------------------------------|-------------|
+| 1 Introduction.....                                                                         | 1           |
+| 2 Terminology.....                                                                          | 1           |
+| 3 Scope.....                                                                                | 1           |
+| 4 Basic requirements.....                                                                   | 2           |
+| 5 Mode of operation.....                                                                    | 2           |
+| Annex A – Harmonization of international public bureau services – Detailed guidelines ..... | 2           |
+| A.1 Introduction .....                                                                      | 2           |
+| A.2 Possible solutions for a harmonization of bureau services .....                         | 3           |
+| A.3 Routing and retransmission of messages (Selection modes).....                           | 5           |
+
+
+
+## **GUIDELINES ON HARMONIZATION OF INTERNATIONAL PUBLIC BUREAU SERVICES**
+
+*(revised in 1998)*
+
+## **1 Introduction**
+
+*considering*
+
+- a) the reasonable needs of customers for a service of last resort;
+- b) ITU-T Study Group 1's work on harmonization of the telegram, telemessage and bureaufax services;
+- c) Resolution No. 6 (World Administrative Telegraph and Telephone Conference, WATTC, Melbourne 1988) and Recommendation F.11 on continued availability of traditional services in accordance with which the classical telegram service is no longer obligatory for international relations where a reasonable alternative such as bureaufax or telemessage exists;
+- d) the moral obligation on ITU Members to provide at least a form of international service of last resort;
+- e) the possibilities of newly introduced transport mechanisms or services which could play an important role for efficient operation of traditional services;
+- f) that there is no basis in the Regulations of the ITU to require any particular form of transmission for bureau services;
+- g) that a harmonization and utilization of positive elements of the individual bureau services could improve flexibility, simplify operation, and increase cost-effectiveness;
+- h) that bureaufax, in view of its much greater flexibility, simple operation and cost-effectiveness, might be encouraged in other countries to allow a transfer from telegram transmitted in accordance with the 1998 version of Recommendation F.1 to facsimile applications over a wide area;
+- i) that other technical solutions may be developed,
+
+this Recommendation provides broad guidelines on the minimum requirements for a harmonized operation of existing bureau services.
+
+## **2 Terminology**
+
+For the purpose of this Recommendation, a **bureau service** is a message service for those who are permanently or temporarily not subscribers to other services or who wish to use this service for any other reason whereby it will be perceived as simply transporting a message regardless of the mechanism used.
+
+## **3 Scope**
+
+**3.1** This Recommendation contains the general concept for the harmonized application of international public bureau services. It is intended to guide Administrations/ROAs in implementing Recommendation F.11.
+
+**3.2** The international public bureau services should provide the capability of operation in conjunction with each other to the extent practicable.
+
+**3.3** The tariff principles for the international public bureau services are laid down in the relevant D-Series Recommendations.
+
+**3.4** The provisions set out below shall apply to the operation of public bureau services via telecommunication networks:
+
+- a) between public facsimile bureaux (bureaufax: see Recommendations F.170 and F.171);
+- b) between public facsimile bureaux and subscribers' facsimile stations, and vice versa (see Recommendation F.190);
+- c) between telegram offices (see Recommendations F.1 and F.31);
+- d) between telemessage offices (see Recommendation F.40);
+- e) between telegram and bureaufax offices (see Recommendations F.1, F.31 and F.170);
+- f) between telegram offices and subscriber facsimile stations (see Recommendation F.1);
+- g) between telegram offices and telex subscribers (see Recommendation F.1);
+- h) between telegram and telemessage offices and vice versa (see Recommendation F.41).
+
+### **3.5 Classes of service**
+
+Classes of service in each category mentioned in 3.4 are handled in the relevant F-Series Recommendations.
+
+## **4 Basic requirements**
+
+**4.1** The basic requirements for international public bureau services are:
+
+- a) reasonable access to the national service in the country of origin for lodging messages (e.g. over a counter, by telephone and perhaps by other telecommunication links to a public office, which may need to include format conversion);
+- b) international transmission (e.g. by facsimile, telegram retransmission, gentex, telex, MHS, ...);
+- c) format conversion, store-and-forward at a gateway if required;
+- d) national transmission and/or format conversion as necessary;
+- e) delivery by mail, or electronically as an option where practicable.
+
+**4.2** The more likely and preferred harmonized applications will be identified in the appropriate service Recommendations as necessary, including the operational procedures, and service parameters.
+
+**4.3** Any effects on charging and accounting will be covered in the D-Series Recommendations with the objective of operational simplicity.
+
+## **5 Mode of operation**
+
+**5.1** The mode of operation should be in accordance with the mechanism used for transporting the message [see 4.1, b)].
+
+**5.2** Specific details will be found in the individual service Recommendations.
+
+**5.3** The quality of service aspects are also handled in the relevant F-Series Recommendations.
+
+## **Annex A**
+
+### **Harmonization of international public bureau services – Detailed guidelines**
+
+### **A.1 Introduction**
+
+This annex represents a more detailed approach for possible solutions for a harmonization of bureau services, taking into account the different situations in the various countries. Different steps or phases seem to be necessary and/or possible to introduce improvements in the area of bureau services.
+
+A number of problems/solutions depend on national organization/structure of bureau services.
+
+The following subclauses propose arrangements where facsimile transmission is used to carry telegrams nationally and/or internationally.
+
+Specific operational provisions applying to facsimile transmissions can be found in Recommendations F.1, Part E, and F.170.
+
+If specific provisions do not exist in Recommendation F.1, a number of problems could be solved by bilateral agreements.
+
+### **A.2 Possible solutions for a harmonization of bureau services**
+
+#### **A.2.1 Possible first approach (Domestic telegram and bureaufax services; see Figure A.1)**
+
+The harmonization of both services could start nationally simply by common use of telegram and bureaufax facilities. No technical changes are necessary.
+
+The way these services are named, charged and marketed is a national matter.
+
+National innovation should not be restrained. Which organization (postal authority, telecommunication ROA, etc.) operates any bureau service is also a national matter.
+
+At this stage, at the international interface, a clear distinction should be made between telegrams and bureaufax.
+
+Internationally the character-coded telegram service could be replaced by a fax-based bureau service.
+
+Where suitable replacements exist, the international telegram will gradually disappear. Abolition in low-volume relations should be encouraged.
+
+This stage could be characterised by:
+
+- The existing technical facilities will be used further, only necessary improvements will be implemented.
+- The transmission via facsimile will be preferred.
+- Reasonable access to the national service for the input of messages will be provided.
+- Domestic messages handed in over the counter will be transmitted via facsimile to the appropriate public bureau. Messages can contain written matter or printed matter, drawings or any other graphics.
+- Telegrams and bureaufax for abroad will be transmitted, by the accepting public bureau, to the appropriate national gateway for further transmission (character-coded or image-coded).
+- Where agreed, the office of origin may route telegrams directly to a telefax subscriber in another country.
+
+#### **A.2.2 Possible next step (International telegram and bureaufax service; see Figure A.2)**
+
+All aspects under A.2.1 should be considered.
+
+The domestic Telegram Retransmission System will be improved (character-coded/image-coded interface to a fax store-and-forward system).
+
+Direct transmission and delivery to fax machines nationwide and abroad will be possible.
+
+By bilateral agreement it becomes possible to transmit (F.1) telegrams from the origin country to a public bureau abroad by fax.
+
+The character set (ITA2) used for telegrams remains unchanged.
+
+Direct international transmission via point-to-point (p.t.p.) and gentex will no longer be the sole means of international transmission.
+
+Some countries may need to continue an F.1-type service nationally for longer. In this case a gateway to the international bureaufax service would facilitate these international transmissions.
+
+![Figure A.1/F.18: Possible solutions for a harmonization of bureaux services. This flowchart illustrates various transmission paths from a 'CUSTOMER (Sender)' to an 'Addressee'. The sender can choose between VTX, FAX, COUNTER, TLF, and TLX. VTX and FAX lead to a 'Bureaufax Office (Gateway)', which connects to 'Foreign countries' via 'Facsimile' and to an 'Appropriate Public Bureau (destination)' via 'FAX'. The COUNTER path leads to a 'Public Bureau (origin)', which connects to the 'National Telegraph Office' via 'FAX' and to the 'Appropriate Public Bureau (destination)' via 'FAX'. The TLF and TLX paths lead to the 'National Telegraph Office' and 'TRS Telegram Retransmission System', which both connect to 'Foreign countries' via 'Point-to-Point', 'Gentex', and 'Facsimile transmission'. The 'Appropriate Public Bureau (destination)' connects to the 'Addressee' via 'FAX', 'TLF', and 'Messenger Counter collection Mail P.O. Box'. The 'National Telegraph Office' and 'TRS' also connect to the 'Addressee' via 'TLF' and 'TLX'. A label 'T0206800-97/d01' is present in the bottom right.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+Figure A.1/F.18: Possible solutions for a harmonization of bureaux services. This flowchart illustrates various transmission paths from a 'CUSTOMER (Sender)' to an 'Addressee'. The sender can choose between VTX, FAX, COUNTER, TLF, and TLX. VTX and FAX lead to a 'Bureaufax Office (Gateway)', which connects to 'Foreign countries' via 'Facsimile' and to an 'Appropriate Public Bureau (destination)' via 'FAX'. The COUNTER path leads to a 'Public Bureau (origin)', which connects to the 'National Telegraph Office' via 'FAX' and to the 'Appropriate Public Bureau (destination)' via 'FAX'. The TLF and TLX paths lead to the 'National Telegraph Office' and 'TRS Telegram Retransmission System', which both connect to 'Foreign countries' via 'Point-to-Point', 'Gentex', and 'Facsimile transmission'. The 'Appropriate Public Bureau (destination)' connects to the 'Addressee' via 'FAX', 'TLF', and 'Messenger Counter collection Mail P.O. Box'. The 'National Telegraph Office' and 'TRS' also connect to the 'Addressee' via 'TLF' and 'TLX'. A label 'T0206800-97/d01' is present in the bottom right.
+
+**Figure A.1/F.18 – Possible solutions for a harmonization of bureaux services**
+
+The number of fax machines in public bureaux will be increased, gentex transmission to teleprinters (domestic) will be substituted by facsimile transmission.
+
+**Advantages:** Cost reduction (fax machines and transmission over the public telephone network is cheaper than the costs of teleprinters and the use of the national gentex network).
+
+The handling of messages takes less time (no word count necessary, easy transmission by facsimile etc.).
+
+In the absence of new international accounting provisions, accounting could be solved by bilateral agreements.
+
+#### **A.2.3 Possible second approach (International telegram and bureaufax services; see Figure A.3)**
+
+All aspects under A.2.1 and A.2.2 should be considered.
+
+Implementation of a domestic fax store-and-forward-system with automatic routing capabilities and centralised accounting and statistics.
+
+In addition, where bilaterally agreed, the form accepted from the originator can be transmitted by facsimile internationally. Where agreed, characters outside ITA2 may be used.
+
+The treatment of such messages, including international accounting, can be agreed bilaterally.
+
+#### **A.2.4 Possible final solution; see Figure A.4**
+
+The aim is to replace the classical telegram transmission technique completely by another transport mechanism.
+
+### A.3 Routing and retransmission of messages (Selection modes)
+
+It should be noted that the choice of international transmission mode is not necessarily the same in each direction. For example, in any international relation it may be agreed that facsimile be used in one direction and printing telegraph in the other.
+
+![Figure A.2/F.18: Possible next step (International telegram and bureaufax service). This flowchart shows message routing from various sources (Counter/Fax, Customer/Fax A, Customer/Fax B, Counter/TF, Customer/TF, Counter/TF/Fax, Customer/TF/Fax) through a Manual operation centre or Intercept to a Telegram retransmission centre. From there, messages are routed through a National gateway (F.31/fax store and forward) or an International gateway (F.31/fax store and forward). The National gateway leads to a National delivery point (outputting Messenger and TF) or a Fax subscriber. The International gateway leads to an International delivery point (outputting Messenger and TF) or a Fax subscriber. All international paths are labeled 'charactercoded and/or picle coded'. A code T0206810-97/d02 is present at the bottom right.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+Figure A.2/F.18: Possible next step (International telegram and bureaufax service). This flowchart shows message routing from various sources (Counter/Fax, Customer/Fax A, Customer/Fax B, Counter/TF, Customer/TF, Counter/TF/Fax, Customer/TF/Fax) through a Manual operation centre or Intercept to a Telegram retransmission centre. From there, messages are routed through a National gateway (F.31/fax store and forward) or an International gateway (F.31/fax store and forward). The National gateway leads to a National delivery point (outputting Messenger and TF) or a Fax subscriber. The International gateway leads to an International delivery point (outputting Messenger and TF) or a Fax subscriber. All international paths are labeled 'charactercoded and/or picle coded'. A code T0206810-97/d02 is present at the bottom right.
+
+Figure A.2/F.18 – Possible next step (International telegram and bureaufax service)
+
+![Figure A.3/F.18: Possible second approach (International telegram and bureaufax services). This flowchart shows message routing from sources (Counter/Fax (National Tel), Customer/Fax A (National Tel), Customer/Fax B (National Tel), Counter/TF (National Tel), Customer/TF (National Tel), Counter/TF/Fax (International Tel), Customer/TF/Fax (International Tel)). National sources go to a Manual operation centre or Intercept A (National traffic), then to a Fax store and forward unit. International sources go to a Manual operation centre or Intercept B (International traffic), then to a Telegram retransmission centre. The Fax store and forward unit connects to a National gateway (leading to National delivery point: Messenger, TF, or Fax subscriber) and an International gateway (leading to International delivery point: Messenger, TF, or Fax subscriber). The Telegram retransmission centre connects to an International gateway (leading to Point-to-Point or Gentex). A code T0206820-97/d03 is present at the bottom right.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+Figure A.3/F.18: Possible second approach (International telegram and bureaufax services). This flowchart shows message routing from sources (Counter/Fax (National Tel), Customer/Fax A (National Tel), Customer/Fax B (National Tel), Counter/TF (National Tel), Customer/TF (National Tel), Counter/TF/Fax (International Tel), Customer/TF/Fax (International Tel)). National sources go to a Manual operation centre or Intercept A (National traffic), then to a Fax store and forward unit. International sources go to a Manual operation centre or Intercept B (International traffic), then to a Telegram retransmission centre. The Fax store and forward unit connects to a National gateway (leading to National delivery point: Messenger, TF, or Fax subscriber) and an International gateway (leading to International delivery point: Messenger, TF, or Fax subscriber). The Telegram retransmission centre connects to an International gateway (leading to Point-to-Point or Gentex). A code T0206820-97/d03 is present at the bottom right.
+
+Figure A.3/F.18 – Possible second approach (International telegram and bureaufax services)
+
+![Figure A.4/F.18 – Possible final solution. A flow diagram showing various input types entering a central unit and branching out to national and international delivery points.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+```
+
+graph LR
+    subgraph Inputs
+    C1[Counter/Fax] --> FSFU
+    C2[Customer/Fax A] --> FSFU
+    C3[Customer/Fax B] --> FSFU
+    C4[Counter/TF] --> FSFU
+    C5[Customer/TF] --> FSFU
+    C6[Counter/TF/Fax] --> FSFU
+    C7[Customer/TF/Fax] --> FSFU
+    end
+
+    subgraph Central_Units
+    FSFU[Fax store and forward unit]
+    MOC[Manual operation centre Intercept]
+    FSFU --- MOC
+    end
+
+    FSFU --> NGW[National gateway]
+    FSFU --> IGW[International gateway]
+
+    NGW --> NDP[National delivery point]
+    NGW --> FS1[Fax subscriber]
+    NDP --> M1[Messenger]
+    NDP --> TF1[TF]
+
+    IGW --> IDP[International delivery point]
+    IGW --> FS2[Fax subscriber]
+    IDP --> M2[Messenger]
+    IDP --> TF2[TF]
+
+```
+
+T0206830-97/d04
+
+Figure A.4/F.18 – Possible final solution. A flow diagram showing various input types entering a central unit and branching out to national and international delivery points.
+
+**Figure A.4/F.18 – Possible final solution**
+
+![](042733dc5e8e7f5f30b60adba3266cde_img.jpg)
+
+Operational Modes of Bureau-Services
+
+| Single operational mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | More than one single operational mode                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <div style="border: 1px solid black; padding: 5px; margin-bottom: 10px;">Acceptance counter<br/>(in any form), TF, TLX, etc.</div> <div style="border: 1px solid black; padding: 5px; margin-bottom: 10px;">National system</div> <div style="border: 1px solid black; padding: 5px; margin-bottom: 10px;">National gateway country A<br/>to foreign countries</div> <div style="display: flex; justify-content: space-between;"> <span>Image</span> <span>Character</span> </div> <div style="text-align: center;">Coded transmission</div> <p>a)</p> | <div style="border: 1px solid black; padding: 5px; margin-bottom: 10px;">Acceptance counter<br/>(in any form), TF, TLX, etc.</div> <div style="border: 1px solid black; padding: 5px; margin-bottom: 10px;">National system</div> <div style="border: 1px solid black; padding: 5px; margin-bottom: 10px;">National gateway country A<br/>to foreign countries</div> <div style="border: 1px solid black; padding: 5px; margin-bottom: 10px;"> International gateway in country B <div style="display: flex; justify-content: space-between;"> <span>Image</span> <span>Character</span> </div> <div style="text-align: center;">coded transmission</div> </div> <p>b)</p> <div style="border: 1px solid black; padding: 5px;"> <div style="display: flex; justify-content: space-between;"> <span>Image</span> <span>Character</span> </div> <div style="text-align: center;">coded transmission</div> International gateway in country C </div> |
+
+T0206840-97/d05
+
+- a) Conversion is in all parts a national matter.
+- b) International conversion between gateways B and C.
+
+**Figure A.5/F.18 – Routing and retransmission of messages (selection modes)**
+
+# ITU-T RECOMMENDATIONS SERIES
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of the ITU-T                                                                                          |
+| Series B        | Means of expression: definitions, symbols, classification                                                                      |
+| Series C        | General telecommunication statistics                                                                                           |
+| Series D        | General tariff principles                                                                                                      |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                              |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                |
+| Series G        | Transmission systems and media, digital systems and networks                                                                   |
+| Series H        | Audiovisual and multimedia systems                                                                                             |
+| Series I        | Integrated services digital network                                                                                            |
+| Series J        | Transmission of television, sound programme and other multimedia signals                                                       |
+| Series K        | Protection against interference                                                                                                |
+| Series L        | Construction, installation and protection of cables and other elements of outside plant                                        |
+| Series M        | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                |
+| Series O        | Specifications of measuring equipment                                                                                          |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                   |
+| Series Q        | Switching and signalling                                                                                                       |
+| Series R        | Telegraph transmission                                                                                                         |
+| Series S        | Telegraph services terminal equipment                                                                                          |
+| Series T        | Terminals for telematic services                                                                                               |
+| Series U        | Telegraph switching                                                                                                            |
+| Series V        | Data communication over the telephone network                                                                                  |
+| Series X        | Data networks and open system communications                                                                                   |
+| Series Y        | Global information infrastructure                                                                                              |
+| Series Z        | Programming languages                                                                                                          |

marked/F/T-REC-F.182bis-199610-I_PDF-E/raw.md

@@ -0,0 +1,294 @@
+
+
+![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt superimposed on it, and the letters 'ITU' written across the globe.
+
+ITU logo
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.182 *bis***
+
+(10/96)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Telematic services – Public facsimile service
+
+---
+
+**Guidelines for the support of the  
+communication of documents using Group 3  
+facsimile between user terminals via public  
+networks**
+
+ITU-T Recommendation F.182 *bis*
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               | F.1–F.109          |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| MOBILE SERVICE                                                  | F.110–F.159        |
+| Mobile services and multdestination satellite services          | F.110–F.159        |
+| TELEMATIC SERVICES                                              | F.160–F.399        |
+| <b>Public facsimile service</b>                                 | <b>F.160–F.199</b> |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499        |
+| DIRECTORY SERVICES                                              | F.500–F.549        |
+| DOCUMENT COMMUNICATION                                          | F.550–F.599        |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699        |
+| AUDIOVISUAL SERVICES                                            | F.700–F.799        |
+| ISDN SERVICES                                                   | F.800–F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899        |
+| HUMAN FACTORS                                                   | F.900–F.999        |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## FOREWORD
+
+The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a 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 Recommendations 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.182 *bis*, was prepared by ITU-T Study Group 1 (1993-1996) and was approved by the WTSC (Geneva, 9-18 October 1996).
+
+---
+
+## NOTE
+
+In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+© ITU 1997
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+|                                                     | <i>Page</i> |
+|-----------------------------------------------------|-------------|
+| 1 Scope.....                                        | 1           |
+| 2 References.....                                   | 1           |
+| 3 Abbreviations.....                                | 1           |
+| 4 General provisions .....                          | 2           |
+| 4.1 General.....                                    | 2           |
+| 4.2 Basic requirements.....                         | 2           |
+| 4.3 Standardized options.....                       | 2           |
+| 5 Network requirements.....                         | 3           |
+| 6 Procedures for the transmission of documents..... | 3           |
+| 7 Coding scheme.....                                | 3           |
+| 8 Operation.....                                    | 3           |
+| 9 Terminal identification.....                      | 3           |
+| 10 User terminals .....                             | 4           |
+| 11 Directories .....                                | 4           |
+
+# **SUMMARY**
+
+This Recommendation defines the guidelines for the support of the communication of documents using Group 3 facsimile between user terminals via public networks and is intended to apply in those cases where an ROA or service provider does not wish to offer a Telefax 3 service as defined in Recommendation F.182. This Recommendation is based upon existing Recommendation F.182 but has been developed to reflect the changing telecommunications environment with regard to the provision of regulated "end-to-end" services.
+
+
+
+# **GUIDELINES FOR THE SUPPORT OF THE COMMUNICATION OF DOCUMENTS USING GROUP 3 FACSIMILE BETWEEN USER TERMINALS VIA PUBLIC NETWORKS**
+
+*(Geneva, 1996)*
+
+## **1 Scope**
+
+**1.1** This Recommendation defines the guidelines which may be considered by ROAs or service providers in supporting the communication of documents using Group 3 facsimile.
+
+**1.2** The communication of documents using Group 3 facsimile enables users to exchange documents either manually or automatically via telecommunication networks across international boundaries.
+
+**1.3** The basic element of the correspondence between people is the page, as the smallest unit of text treated as an entity. No restrictions shall exist as far as the user procedures for generation of the text or the positioning of text within the reproducible area on a page are concerned.
+
+**1.4** Questions of an essentially technical nature concerning the communication of documents using Group 3 facsimile are dealt with in the T-Series Recommendations.
+
+**1.5** Provision for communication of documents using Group 3 facsimile may vary from one ROA to another. In some networks, the communication may be provided on an unassured basis and have no guarantee of the quality of transmission, transmission speed, etc. For example, in some cases the call is treated in the same way as a telephone call.
+
+NOTE – If an ROA does not wish to follow the guidelines defined in this Recommendation, then consideration could be given to the use of Recommendation F.182.
+
+## **2 References**
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- ITU-T Recommendation F.182 (1996), *Operational provisions for the international public facsimile service between subscribers with Group 3 facsimile terminals (Telefax 3)*.
+- ITU-T Recommendation F.180 (1996), *General operational provisions for the international public facsimile service between subscribers' terminals (Telefax)*.
+- ITU-T Recommendation T.4 (1996), *Standardization of Group 3 facsimile terminals for document transmission*.
+- ITU-T Recommendation T.30 (1996), *Procedures for document facsimile transmission in the general switched telephone network*.
+- ITU-T Recommendation T.505 (1994), *Document application profile PM-26 for the interchange of enhanced structure, mixed content documents in processable and formatted forms*.
+
+## **3 Abbreviations**
+
+This Recommendation uses the following abbreviations:
+
+ITU-T International Telecommunication Union – Telecommunication Standardization Sector
+
+ROA Recognized Operating Agency
+
+## 4 General provisions
+
+### 4.1 General
+
+The essential characteristic of the communication of documents using Group 3 facsimile is that it provides a basic level of compatibility between all terminals supporting the Group 3 capabilities.
+
+### 4.2 Basic requirements
+
+- a) The basic level of compatibility is provided between any two terminals internationally so that they may communicate image coded information to each other. This is achieved by terminals complying with Recommendations T.4 and T.30;
+- b) it is for each ROA or service provider to decide on the network(s) on which the communication of documents using Group 3 facsimile will be carried. There is no restriction on the type of network to be used;
+- c) it should be possible to extend the communication of documents using Group 3 facsimile to any number of countries;
+- d) to permit private use options, for example encryption, there is no technical limitation on the bit sequence of the user's information that may be transmitted;
+- e) a received Group 3 document can be printed or displayed as decided by the recipient and the terminal characteristics. If the document is printed, the receiving user will be furnished with a document that is identical with that produced by the sending user as far as its contents, layout and format are concerned;
+- f) it is intended that support for the communication of documents using Group 3 facsimile requires no changes to the Recommendations for existing services or networks.
+
+### 4.3 Standardized options
+
+**4.3.1** It is recognized that some users may need to use their Group 3 facsimile terminals to communicate internationally using features that are not included in the basic requirements. A number of ITU-T standardized options have therefore been defined. However, the provision of any option may lead to some degree of incompatibility and the number of standardized options has been restricted to those features which are listed below and for which a clear international need can be foreseen.
+
+The sending terminal ensures the transmission of documents using only those options that have been indicated as being available at the receiving terminal.
+
+**4.3.2** The standardized options provide means for:
+
+- a) higher data signalling rates (Recommendation T.4);
+- b) subscriber identification (Recommendation T.30);
+- c) Error Correction Mode (ECM) (Recommendation T.4);
+- d) higher resolutions (Recommendation T.4);
+- e) optional coding schemes (Recommendation T.4);
+- f) optional page sizes (Recommendation T.4);
+- g) polling (Recommendation T.30);
+- h) Selective Polling (SEP) (Recommendation T.30);
+- i) Password for polling (PWD) (Recommendation T.30);
+- j) Sender Identification (SID) (Recommendation T.30);
+- k) Sub-addressing (SUB) (Recommendation T.30);
+- l) coded character mode (Recommendation T.4);
+- m) Binary File Transfer mode (BFT) (Recommendation T.4);
+- n) Basic Transfer Mode (BTM) (Recommendation T.4);
+- o) Document Transfer Mode (DTM) (Recommendation T.4);
+- p) Electronic Document Interchange (EDI) (Recommendation T.4);
+
+- q) simple mixed mode (Recommendation T.4);
+- r) processable mode 26 (Recommendation T.505);
+- s) digital network operation (Recommendation T.30).
+
+NOTE – As the communication of documents using Group 3 facsimile evolves and further market and user requirements are identified, there is a continuing need for further study and consequently changes may be required to the above list.
+
+**4.4** Communication between terminals takes place at the level of compatibility at, or nearest to, the parameters initially selected by the originating user. The determination of this level is carried out automatically via the premessage procedures. This takes into account aspects of the quality of transmission media available in the participating networks and the options available on the receiving terminal.
+
+## **5 Network requirements**
+
+**5.1** It is the responsibility of each ROA or service provider to decide on which network(s) the communication of documents using Group 3 facsimile is to be provided.
+
+**5.2** The communication of documents using Group 3 facsimile may be supported over all public networks using the appropriate ITU-T technical Recommendations.
+
+If the Integrated Services Digital Network is used, the communication of documents using Group 3 facsimile will be supported as appropriate.
+
+**5.3** Terminals on any public network which support the communication of documents using Group 3 facsimile are able to communicate automatically with terminals supporting the communication of documents using Group 3 Facsimile on any other public network.
+
+## **6 Procedures for the transmission of documents**
+
+The technical procedures for transmitting documents using the communication of documents using Group 3 facsimile are given in Recommendation T.30.
+
+## **7 Coding scheme**
+
+**7.1** The basic coding scheme for the communication of documents using Group 3 facsimile is given in Recommendation T.4.
+
+**7.2** The optional image coding schemes are given in Recommendation T.4.
+
+**7.3** The optional character coding repertoire is given in Recommendation T.4.
+
+## **8 Operation**
+
+**8.1** Support for the communication of documents using Group 3 facsimile in each country and the interconnection between countries or networks should use fully automatic switching so that it is possible for any user to reach any other user using fully automatic selection.
+
+**8.2** It is recommended to allow the through connection of a call between terminals connected to a private automatic branch exchange (or similar systems) and those connected to public exchanges used to provide support for the communication of documents using Group 3 facsimile.
+
+## **9 Terminal identification**
+
+**9.1** On the PSTN, an answering tone of 2100 Hz identifies connection to a non-voice terminal. Additionally, an automatic identification may be provided, see 9.3. ROAs and service providers may wish to consider recommending to users that the terminal identity is entered in the format described in 9.3.
+
+**9.2** If the pages are printed, it is desirable for the identification of the transmitting terminal to appear at the receiving terminal, in the form of an identification line printed at the top of each page received, in an area 10 mm deep extending across the whole width of the page. This area may be either inside or outside the nominal A4 page, in accordance with the option selected by the user.
+
+**9.3** The terminal identification consists of up to 20 characters (including only digits and spaces). For the PSTN and the ISDN, the identification is the international telephone number and the format is as follows: plus sign, country code, space, area code, space, user's number. The coding arrangements are defined in Recommendation T.30.
+
+The form of the terminal identification on other networks is for further study.
+
+**9.4** At the transmitting terminal, the identification of the receiving terminal may be displayed or printed.
+
+## **10 User terminals**
+
+**10.1** A range of data signalling rates has been defined as follows:
+
+### **10.1.1 Public switched telephone network**
+
+Terminals on the public switched network are able to operate at the basic data signalling rate of 4800 bit/s with fall-back to 2400 bit/s. In addition, higher data signalling rates may be provided. Details are given in Recommendation T.30.
+
+### **10.1.2 Integrated Services Digital Network (ISDN)**
+
+If the Integrated Services Digital Network is used, the communication of documents using Group 3 facsimile will be provided as appropriate.
+
+### **10.1.3 Public data networks**
+
+For further study.
+
+**10.2** The facilities required in terminals participating in the international communication of documents using Group 3 facsimile are listed in the following subclauses:
+
+**10.2.1** Group 3 facsimile terminals have the ability to send, receive and display documents encoded with the image coding scheme defined in Recommendation T.4. In addition, they may have the ability to utilize the optional coding schemes defined in Recommendation T.4.
+
+**10.2.2** No constraints shall be placed upon the type of presentation technology employed.
+
+## **11 Directories**
+
+As a means of stimulating the use of the network(s), some ROAs or service providers may wish to consider publishing or encouraging other organizations to publish a directory of users.
+
+The format of the directory is outside the scope of this Recommendation.
+
+# ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services**
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communication
+- Series Z Programming languages