emolero commited on
Commit
5ca0c07
·
verified ·
1 Parent(s): 910403d

Add files using upload-large-folder tool

Browse files
This view is limited to 50 files because it contains too many changes.   See raw diff
Files changed (50) hide show
  1. marked/F/T-REC-F.100-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  2. marked/F/T-REC-F.104-199110-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  3. marked/F/T-REC-F.104-199110-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg +3 -0
  4. marked/F/T-REC-F.104-199110-I_PDF-E/raw.md +101 -0
  5. marked/F/T-REC-F.105-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  6. marked/F/T-REC-F.105-198811-I_PDF-E/raw.md +109 -0
  7. marked/F/T-REC-F.106-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  8. marked/F/T-REC-F.107-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  9. marked/F/T-REC-F.108-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  10. marked/F/T-REC-F.108-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg +3 -0
  11. marked/F/T-REC-F.111-199103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  12. marked/F/T-REC-F.111-199103-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg +3 -0
  13. marked/F/T-REC-F.112-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  14. marked/F/T-REC-F.116-200003-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  15. marked/F/T-REC-F.14-199208-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  16. marked/F/T-REC-F.14-199208-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg +3 -0
  17. marked/F/T-REC-F.14-199208-I_PDF-E/raw.md +126 -0
  18. marked/F/T-REC-F.140-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  19. marked/F/T-REC-F.140-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg +3 -0
  20. marked/F/T-REC-F.140-199303-I_PDF-E/raw.md +200 -0
  21. marked/F/T-REC-F.15-199208-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg +3 -0
  22. marked/F/T-REC-F.15-199208-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  23. marked/F/T-REC-F.15-199208-I_PDF-E/raw.md +146 -0
  24. marked/F/T-REC-F.16-199502-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg +3 -0
  25. marked/F/T-REC-F.16-199502-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg +3 -0
  26. marked/F/T-REC-F.16-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  27. marked/F/T-REC-F.16-199502-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg +3 -0
  28. marked/F/T-REC-F.16-199502-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg +3 -0
  29. marked/F/T-REC-F.16-199502-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg +3 -0
  30. marked/F/T-REC-F.16-199502-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg +3 -0
  31. marked/F/T-REC-F.16-199502-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg +3 -0
  32. marked/F/T-REC-F.16-199502-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg +3 -0
  33. marked/F/T-REC-F.16-199502-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg +3 -0
  34. marked/F/T-REC-F.16-199502-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg +3 -0
  35. marked/F/T-REC-F.16-199502-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg +3 -0
  36. marked/F/T-REC-F.16-199502-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg +3 -0
  37. marked/F/T-REC-F.17-199208-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  38. marked/F/T-REC-F.17-199208-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg +3 -0
  39. marked/F/T-REC-F.171-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  40. marked/F/T-REC-F.18-199803-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg +3 -0
  41. marked/F/T-REC-F.18-199803-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  42. marked/F/T-REC-F.18-199803-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg +3 -0
  43. marked/F/T-REC-F.18-199803-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg +3 -0
  44. marked/F/T-REC-F.18-199803-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg +3 -0
  45. marked/F/T-REC-F.18-199803-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg +3 -0
  46. marked/F/T-REC-F.182bis-199610-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  47. marked/F/T-REC-F.185-199806-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  48. marked/F/T-REC-F.185-199806-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg +3 -0
  49. marked/F/T-REC-F.185-199806-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg +3 -0
  50. marked/F/T-REC-F.185-199806-I_PDF-E/raw.md +306 -0
marked/F/T-REC-F.100-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
  • Pointer size: 129 Bytes
  • Size of remote file: 7.39 kB
marked/F/T-REC-F.104-199110-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: f09f10840d9270effd61b9bf244f3ce48bb34a123133778505623acaa4163a8d
  • Pointer size: 129 Bytes
  • Size of remote file: 7.49 kB
marked/F/T-REC-F.104-199110-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg ADDED

Git LFS Details

  • SHA256: 495c6c5b5acabcf027f4b5444cdec07c1959db3d409caa558de1bfc54abb8dc6
  • Pointer size: 129 Bytes
  • Size of remote file: 5.75 kB
marked/F/T-REC-F.104-199110-I_PDF-E/raw.md ADDED
@@ -0,0 +1,101 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ ![ITU logo: A globe with the letters ITU and a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
4
+
5
+ ITU logo: A globe with the letters ITU and a lightning bolt.
6
+
7
+ INTERNATIONAL TELECOMMUNICATION UNION
8
+
9
+ **CCITT**
10
+
11
+ **F.104**
12
+
13
+ THE INTERNATIONAL
14
+ TELEGRAPH AND TELEPHONE
15
+ CONSULTATIVE COMMITTEE
16
+
17
+ **TELEGRAPH AND MOBILE SERVICES
18
+ OPERATIONS AND QUALITY OF SERVICE**
19
+
20
+ ---
21
+
22
+ **INTERNATIONAL LEASED CIRCUIT
23
+ SERVICES – CUSTOMER
24
+ CIRCUIT DESIGNATIONS**
25
+
26
+ **Recommendation F.104**
27
+
28
+ ---
29
+
30
+ ![CCITT logo: A globe with the letters CCITT.](6ed175c791b5e156d9c98a8dbcc3318c_img.jpg)
31
+
32
+ CCITT logo: A globe with the letters CCITT.
33
+
34
+ Geneva, 1991
35
+
36
+ # FOREWORD
37
+
38
+ 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.
39
+
40
+ 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).
41
+
42
+ Recommendation F.104 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 11th of October 1991.
43
+
44
+ ## --- CCITT NOTE
45
+
46
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
47
+
48
+ ## Recommendation F.104
49
+
50
+ # INTERNATIONAL LEASED CIRCUIT SERVICES – CUSTOMER CIRCUIT DESIGNATIONS
51
+
52
+ ## 1 Introduction
53
+
54
+ 1.1 CCITT Recommendation M.140 (Designations of international circuits, groups, group and line links, digital blocks, digital paths, data transmission systems and related information) specifies a scheme for the designation of international routes <sup>1)</sup>.
55
+
56
+ 1.2 The designation scheme is based on a layered approach with:
57
+
58
+ layer 1 – a unique identification providing limited information;
59
+
60
+ layer 2 – additional information that must be known at both termination of the route; and
61
+
62
+ layer 3 – (optional) – bilateral information not the subject of international standardization.
63
+
64
+ ## 2 General
65
+
66
+ 2.1 Layer 1 of the Recommendation M.140 designation scheme provides unique circuit information that is common at both ends of the route and is suitable to be made available to the customer as the *customer international circuit designations*.
67
+
68
+ ## 3 Customer international circuit designations
69
+
70
+ 3.1 Section 3 of Recommendation M.140 specifies the format of the designation for fixed circuits as given in the following subsections. An example of the format of a unique circuit designation is shown in Figure 1/F.104.
71
+
72
+ 3.2 The customer circuit designation should be in accordance with layer 1 designation of § 3.2 of Recommendation M.140.
73
+
74
+ 3.2.1 Towns A and B, with a possible (optional) transmission station suffix, should identify the terminal points of the circuit. They appear in alphabetical order.
75
+
76
+ 3.2.2 The identification of the terminal point is up to the Administration concerned. In cases where the town name exceeds the maximum length of 12 characters, the Administration should supply a suitable abbreviation which must be unique. The use of the last three characters to indicate the country is suggested.
77
+
78
+ 3.2.3 The transmission station suffix is an optional field which may be used further to identify the terminal point, e.g. when there is more than one RPOA operating in the town. The need for a suffix and its form should be decided by the RPOA concerned.
79
+
80
+ 3.2.4 The function code should identify the type of circuit. Function codes should be in accordance with Recommendation M.140.
81
+
82
+ 3.2.5 The serial number should be a separate numbering series for each traffic relation and function code. In the case of more than one RPOA, serial numbering will be on a transmission station to transmission station and functional code basis.
83
+
84
+ ---
85
+
86
+ <sup>1)</sup> The word “route” in this context has a very general meaning.
87
+
88
+ 3.3 Layer 2 of Recommendation M.140 is meant for Administration use.
89
+
90
+ 3.4 In special cases in which CCITT Recommendations do not apply, the circuit designation should be bilaterally agreed between the two terminal Administrations.
91
+
92
+ *Example:* BERN/1RS-NEW YORK/1RC TP1
93
+
94
+ | Format of designation | Town A | Delim-<br>iter (/) | Trans-<br>mission<br>station<br>suffix<br>optional | Delimi-<br>ter (-) | Town B | Delimi-<br>ter (/) | Trans-<br>mission<br>station<br>suffix<br>optional | Delim-<br>iter<br>(Space) | Function<br>code | Serial<br>No. |
95
+ |-----------------------|--------|--------------------|----------------------------------------------------|--------------------|-------------|--------------------|----------------------------------------------------|---------------------------|------------------|---------------|
96
+ | e.g. | BERN | / | 1RS | - | NEW<br>YORK | / | 1RC | Sp | TP | 1 |
97
+ | No. of Characters | 1-12 | 1 | 1-3 | 1 | 1-12 | 1 | 1-3 | 1 | 1-4 | 1-4 |
98
+
99
+ FIGURE 1/F.104
100
+
101
+ **Format of unique circuit designation**
marked/F/T-REC-F.105-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 39fecafb2f82be549519274cbcc76e5c508ef064a283e3aabfe904469e087b93
  • Pointer size: 129 Bytes
  • Size of remote file: 7.5 kB
marked/F/T-REC-F.105-198811-I_PDF-E/raw.md ADDED
@@ -0,0 +1,109 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ ![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
4
+
5
+ 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.
6
+
7
+ ITU logo
8
+
9
+ INTERNATIONAL TELECOMMUNICATION UNION
10
+
11
+ **ITU-T**
12
+
13
+ TELECOMMUNICATION
14
+ STANDARDIZATION SECTOR
15
+ OF ITU
16
+
17
+ **F.105**
18
+
19
+ # **OPERATIONS AND QUALITY OF SERVICE TELEGRAPH SERVICES** ---
20
+
21
+ ## **OPERATIONAL PROVISIONS FOR PHOTOTELEGRAMS**
22
+
23
+ **ITU-T Recommendation F.105**
24
+
25
+ (Extract from the *Blue Book*)
26
+
27
+ ---
28
+
29
+ ### NOTES
30
+
31
+ 1 ITU-T Recommendation F.105 (new numbering of Rec. F.80) 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).
32
+
33
+ 2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
34
+
35
+ ## OPERATIONAL PROVISIONS FOR PHOTOTELEGRAMS<sup>1)</sup>
36
+
37
+ ### 1 Field of application
38
+
39
+ 1.1 These rules apply to phototelegrams in both continental and intercontinental relations (exchanged between public stations or between public stations and private stations). The provisions concerning the exchange of phototelegraph calls between private stations or from private to public stations are embodied in Recommendation F.80 *bis* and D.81.
40
+
41
+ 1.2 The rules governing the method of communication between phototelegraph stations are embodied in Recommendation F.82.
42
+
43
+ ### 2 General
44
+
45
+ 2.1 Private stations may be authorized by the Administrations concerned to exchange phototelegrams with public stations.
46
+
47
+ 2.2 In both continental and intercontinental relations, private stations communicate directly with public stations providing that the characteristics of their equipment conform with CCITT Recommendations.
48
+
49
+ 2.3 Administrations shall agree upon the working hours of their phototelegraph offices. The hours during which private offices are open shall be fixed by the private organization concerned.
50
+
51
+ ### 3 Conditions of acceptance
52
+
53
+ 3.1 In order to ensure satisfactory transmission of a phototelegram it is recommended that senders should be advised to avoid the use of the colours blue, lilac, green or yellow, or gilt print, or prints on yellow, red or grey paper, which lack the qualities necessary for good transmission, and to avoid handing in phototelegrams with very weak contrast or inadequate definition.
54
+
55
+ 3.2 If, after the sender has been informed that the general quality of the original phototelegram is not suitable for satisfactory transmission, he insists on handing it in, the phototelegram shall only be accepted at the risk of the sender. In this case the service instruction **RISQUES EXPEDITEUR** shall be included in the preamble.
56
+
57
+ 3.3 Phototelegrams must be rectangular in shape. Each Administration shall decide what is the maximum format capable of being sent in a single transmission by all the machines used by that Administration. However, in relations where equipment is used permitting the single transmission of greater areas, Administrations may authorize larger sizes.
58
+
59
+ 3.4 Phototelegrams of larger dimensions than those admitted in the relation concerned must be divided into parts by the sender. The order of transmission of the parts must be indicated.
60
+
61
+ 3.5 In phototelegraph transmission a strip of the edges of the phototelegram may be lost on two opposite sides of the document to be transmitted. For this reason care should be taken when dividing a phototelegram to see that there is no loss at the separation line. If there is any doubt, the sender may be advised to authorize the division of the phototelegram by the phototelegraph station.
62
+
63
+ 3.6 It may happen that the format of phototelegrams is enlarged or diminished during a phototelegraph transmission, owing to the different characteristics of the sending and receiving equipment. If this is so, however, the phototelegram will be reproduced with the same proportions as the original.
64
+
65
+ ### 4 Arrangement of the parts of a phototelegram
66
+
67
+ 4.1 Every phototelegram must bear an address. A signature shall be optional. The address and the signature shall form part of the phototelegram to be transmitted.
68
+
69
+ 4.2 Every phototelegram shall include a preamble. The relevant instructions shall be the same as those for the preamble line of a telegram. But the number of words shall be replaced by a statement of the charging step.
70
+
71
+ ---
72
+
73
+ 1) See also Recommendation D.80.
74
+
75
+ ### 5 Handing in a phototelegram
76
+
77
+ - 5.1 A phototelegram may be handed in:
78
+ - at the counter of an authorized telegraph office;
79
+ - directly at a public station (handing in by messenger).
80
+ - 5.2 A phototelegram from a private station which is received by a public station for delivery to the addressee or for retransmission shall be considered as having been handed in at the public station (handing in by phototelegraphy).
81
+ - 5.3 Depending on the method used, the time of handing in shall be:
82
+ - the time of acceptance at the counter of a telegraph office;
83
+ - the time of acceptance by the public station (in the case of direct handing in);
84
+ - the time of arrival at the public station (service from a private station to a public station).
85
+
86
+ ### 6 Transmission of a phototelegram
87
+
88
+ - 6.1 Phototelegrams of the same rank shall be transmitted by the outgoing station in the order in which they are handed in, and by the intermediate stations in the order of reception.
89
+ - 6.2 A phototelegram to a private station shall, after closure of its office or if its equipment is out of order, be routed to another station of the incoming country only by agreement with the sender.
90
+ - 6.3 A transmission that is unsuccessful because of adverse transmission conditions should be repeated as soon as circumstances permit.
91
+ - 6.4 But if the sender could be informed of unsatisfactory transmission conditions and if he insists upon an attempt at transmission being made, the phototelegram shall be accepted only at the risk of the sender. In this case the service instruction **RISQUES EXPEDITEUR** shall be included in the preamble. If the copy received at the receiving phototelegraph station is not satisfactory after a maximum of three attempted transmissions, no further re-runs should, in principle, be attempted. The sender should be notified of the circumstances.
92
+
93
+ ### 7 Delivery of a phototelegram
94
+
95
+ - 7.1 Phototelegrams received by a public station shall be delivered unless they are to be retransmitted. A phototelegram may be delivered to an addressee in the locality where the public receiving station is located:
96
+ - by messenger;
97
+ - through personal collection by the addressee.
98
+ - 7.2 A phototelegram transmitted from a public station to a private station shall be considered as delivered to the addressee (delivery by phototelegraphy).
99
+ - 7.3 Phototelegrams addressed to localities that are not connected to the phototelegraph network shall be delivered by post. They shall be considered as postal correspondence from the time they are handed over to the postal service.
100
+ - 7.4 For special reasons, a phototelegram may be kept on hand at a public station – at the sender's request – until a private station re-calls it (collection by phototelegraphy). A public station having phototelegrams on hand intended for a private station shall not act on a request for transmission made by the private station until it has satisfied itself of the identity of the latter.
101
+ - 7.5 Depending on the method applied, the time of delivery of a phototelegram shall be:
102
+ - the time of delivery to the addressee;
103
+ - the time when the addressee, having been informed of the received phototelegram, expresses the intention of sending a private messenger;
104
+ - the time when the transmission is terminated, in service from a public station to a private station;
105
+ - the time of handing over to the postal service in the case of delivery of post.
106
+
107
+ ### 8 Charging
108
+
109
+ - 8.1 The rates for phototelegrams in continental and in intercontinental relations exchanged between public stations or from a public station to a private station are governed in Recommendation D.83.
marked/F/T-REC-F.106-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 0e63988e160a5a663f5a0496675594529a7c13c153518b0cee3b6016e695b52c
  • Pointer size: 129 Bytes
  • Size of remote file: 7.46 kB
marked/F/T-REC-F.107-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: b69fbf51a775dd9a6d6f1a54889692b863303e635a263d2ff12b4e9196beb36b
  • Pointer size: 129 Bytes
  • Size of remote file: 7.45 kB
marked/F/T-REC-F.108-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
  • Pointer size: 129 Bytes
  • Size of remote file: 7.39 kB
marked/F/T-REC-F.108-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg ADDED

Git LFS Details

  • SHA256: b2cf941838e325d1e3962d8034b1e113f7e4e6610ea06ad195f41807ea186f09
  • Pointer size: 130 Bytes
  • Size of remote file: 85.5 kB
marked/F/T-REC-F.111-199103-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: b1fe7e9cde82cdc0a16fac850a13112ee3dd1f43c121fc02ce73fcee110e7ab6
  • Pointer size: 129 Bytes
  • Size of remote file: 7.38 kB
marked/F/T-REC-F.111-199103-I_PDF-E/6ed175c791b5e156d9c98a8dbcc3318c_img.jpg ADDED

Git LFS Details

  • SHA256: 7fec63cd1723746ba55d6f3aa1c77168cfaebc18527e0ee3a5f5adf69a0e011e
  • Pointer size: 129 Bytes
  • Size of remote file: 5.82 kB
marked/F/T-REC-F.112-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
  • Pointer size: 129 Bytes
  • Size of remote file: 7.39 kB
marked/F/T-REC-F.116-200003-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: c7a97195c2fd68ad39d82d19b808d1738dce3aa52e94325870a031b5a2ea7c01
  • Pointer size: 129 Bytes
  • Size of remote file: 8.28 kB
marked/F/T-REC-F.14-199208-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: e68f3a8996c9beea065b8f957418db62724b0d6a120b43ff3f66c469a40e8991
  • Pointer size: 129 Bytes
  • Size of remote file: 7.41 kB
marked/F/T-REC-F.14-199208-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg ADDED

Git LFS Details

  • SHA256: f1c4d6c9fe549df7fc35a757ee52742499850e6b4772eeea8a38b0dacbe2655d
  • Pointer size: 129 Bytes
  • Size of remote file: 5.81 kB
marked/F/T-REC-F.14-199208-I_PDF-E/raw.md ADDED
@@ -0,0 +1,126 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ ![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
4
+
5
+ ITU logo: A globe with a lightning bolt and the letters ITU.
6
+
7
+ INTERNATIONAL TELECOMMUNICATION UNION
8
+
9
+ **CCITT**
10
+
11
+ THE INTERNATIONAL
12
+ TELEGRAPH AND TELEPHONE
13
+ CONSULTATIVE COMMITTEE
14
+
15
+ **F.14**
16
+
17
+ (08/92)
18
+
19
+ **TELEGRAPH AND MOBILE SERVICES
20
+ OPERATIONS AND QUALITY OF SERVICE**
21
+
22
+ ---
23
+
24
+ **GENERAL PROVISIONS FOR
25
+ ONE-STOP-SHOPPING ARRANGEMENTS**
26
+
27
+ **Recommendation F.14**
28
+
29
+ ---
30
+
31
+ ![CCITT logo: A globe with the letters CCITT.](84a1d09fb489061482111515543b60dc_img.jpg)
32
+
33
+ CCITT logo: A globe with the letters CCITT.
34
+
35
+ Geneva, 1992
36
+
37
+ # FOREWORD
38
+
39
+ 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.
40
+
41
+ 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).
42
+
43
+ Recommendation F.14 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992.
44
+
45
+ ---
46
+
47
+ ## CCITT NOTE
48
+
49
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
50
+
51
+ # **GENERAL PROVISIONS FOR ONE-STOP-SHOPPING ARRANGEMENTS**
52
+
53
+ (1992)
54
+
55
+ ## **1 Introduction**
56
+
57
+ ### **1.1 Scope**
58
+
59
+ This Recommendation sets out the general procedures for the implementation of one-stop-shopping (OSS) arrangements associated with the customer provision of international telecommunication services.
60
+
61
+ 1.2 OSS may be defined as an optional arrangement for both customer and Administration whereby a single Administration (the coordinating Administration) provides and/or coordinates with other Administrations (the participating Administrations) the provision of one or more telecommunication services. It is designed to simplify for the customer the ordering, implementation and billing procedures currently undertaken by each Administration for the establishment and ongoing provision of international services.
62
+
63
+ ### **1.3 Options**
64
+
65
+ The OSS arrangements may include one or more of the following customer options:
66
+
67
+ - a) single end ordering;
68
+ - b) single end billing<sup>1)</sup>;
69
+ - c) single contact point fault reporting;
70
+ - d) maintenance coordination.
71
+
72
+ Where the customer so wishes, the OSS arrangement may also encompass those other components of a customer network that do not originate or terminate within the operating area of the coordinating Administration.
73
+
74
+ The OSS arrangement requires close coordination and designation of contact points among the Administrations concerned at all levels, commercial, administrative and technical.
75
+
76
+ ## **2 Organizational aspects**
77
+
78
+ 2.1 Administrations should designate contact points for participating Administrations, making due allowance for any difference in time zones, for the following activities:
79
+
80
+ - a) enquiry/pre-sales activities;
81
+ - b) ordering/confirmation between Administrations;
82
+ - c) billing and inter-Administration accounting;
83
+ - d) maintenance coordination and customer support.
84
+
85
+ ### **2.2 Information exchange**
86
+
87
+ Through the coordinating Administration, customers may obtain end-to-end information about services, tariffs, delivery times, etc., from any participating Administration. If the information is not immediately available, the coordinating Administration may request the necessary details from the contact points of the other Administration(s) involved. Administrations should endeavour to provide the requested information promptly.
88
+
89
+ ---
90
+
91
+ <sup>1)</sup> Billing and accounting aspects are covered in the relevant D-Series Recommendations.
92
+
93
+ ### 2.3 *Selection*
94
+
95
+ The customer will select the Administration it wishes to act as the single point of contact among the Administrations involved in providing the service. Agreement to the customer's selection or any subsequent changes in that selection shall not be unreasonably withheld by other Administration(s).
96
+
97
+ ### 2.4 *Quotation*
98
+
99
+ A quotation should be prepared by the coordinating Administration for the customer, as agreed by contact points of the participating Administrations. Participating Administrations shall agree on the content of their respective parts of a quotation before submission to the customer.
100
+
101
+ ### 2.5 *Ordering*
102
+
103
+ The coordinating Administration shall assume responsibility for handling the ordering arrangements for the customer. The coordinating Administration should arrange for the customer to sign and complete the forms required by the participating Administration concerned.
104
+
105
+ ### 2.6 *Order progress*
106
+
107
+ The coordinating Administration should be responsible for providing the customer with information on the progress of service provision. Should any problems or delays occur within a participating Administration's field of responsibility, the coordinating Administration should be notified immediately, and *vice versa*.
108
+
109
+ ## 3 **Operational aspects**
110
+
111
+ 3.1 The coordinating Administration should normally be responsible to the customer for the overall coordination of the service installation, testing, advising the customer of service availability, and the coordination of on-going maintenance.
112
+
113
+ 3.2 The coordinating and participating Administration(s) should designate the centres which will interface with each other for installation, testing and ongoing maintenance, in accordance with the relevant M-Series Recommendations. The centre of the coordinating Administration should normally function as the coordinating centre, unless otherwise agreed by the Administrations concerned. When the service does not pass through the territory of the coordinating Administration, a coordinating centre should be chosen from one of the participating Administrations in consultation with the coordinating Administration.
114
+
115
+ 3.3 The coordinating centre should contact the participating centre(s) and agree on a programme of tests to be conducted in accordance with the relevant CCITT Recommendations. The coordinating and participating Administration(s) should agree on the following dates, as appropriate for the service concerned:
116
+
117
+ - *ready for service date*: which is the date when the service should be complete and made available to the customer.
118
+ - *national test date*: which is the date by which the domestic parts of the service will be installed and tested in the respective countries.
119
+ - *line-up test date*: which is the date that the service will be tested between the respective international centres.
120
+ - *end-to-end test date*: which is the date that the service will be tested overall.
121
+
122
+ 3.4 When the service is handed over to the customer and accepted, the coordinating Administration should advise all participating Administrations that the service is now in use.
123
+
124
+ 3.5 When the customer has selected single contact point fault reporting, faults should be reported to the coordinating centre which then coordinates fault investigation and clearance. The coordinating centre should keep the customer informed as to fault clearance status.
125
+
126
+ 3.6 Testing maintenance functions should be performed in accordance with the relevant M-Series Recommendations.
marked/F/T-REC-F.140-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 5603f29a95a0e06c23a7d999918e378ff6b453c50915bd3f942fba08cc4ba16b
  • Pointer size: 129 Bytes
  • Size of remote file: 8.29 kB
marked/F/T-REC-F.140-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg ADDED

Git LFS Details

  • SHA256: 63ce0aa4e4211f23bade5718e25166dc0c5f57f042fa7aa8b73ec3872700fd6d
  • Pointer size: 131 Bytes
  • Size of remote file: 107 kB
marked/F/T-REC-F.140-199303-I_PDF-E/raw.md ADDED
@@ -0,0 +1,200 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ ![ITU logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
4
+
5
+ The logo of the International Telecommunication Union (ITU) features a globe with a lightning bolt striking across it, and the letters 'ITU' superimposed on the globe.
6
+
7
+ ITU logo
8
+
9
+ INTERNATIONAL TELECOMMUNICATION UNION
10
+
11
+ **ITU-T**
12
+
13
+ TELECOMMUNICATION
14
+ STANDARDIZATION SECTOR
15
+ OF ITU
16
+
17
+ **F.140**
18
+
19
+ (03/93)
20
+
21
+ **OPERATIONS AND QUALITY OF SERVICE
22
+ MOBILE SERVICE**
23
+
24
+ ---
25
+
26
+ **POINT-TO-MULTIPOINT TELECOMMUNICATION
27
+ SERVICE VIA SATELLITE**
28
+
29
+ **ITU-T Recommendation F.140**
30
+
31
+ (Previously "CCITT Recommendation")
32
+
33
+ ---
34
+
35
+ # FOREWORD
36
+
37
+ The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. 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.
38
+
39
+ The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
40
+
41
+ ITU-T Recommendation F.140 was revised by the ITU-T Study Group I (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993).
42
+
43
+ ---
44
+
45
+ # NOTES
46
+
47
+ 1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its place, the ITU Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector.
48
+
49
+ In order not to delay publication of this Recommendation, no change has been made in the text to references containing the acronyms "CCITT, CCIR or IFRB" or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure.
50
+
51
+ 2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
52
+
53
+ # CONTENTS
54
+
55
+ *Page*
56
+
57
+ | | | |
58
+ |-----|--------------------------------------|---|
59
+ | 1 | Scope..... | 1 |
60
+ | 1.1 | Definition of service ..... | 1 |
61
+ | 2 | Service description..... | 1 |
62
+ | 2.1 | Functional elements of service ..... | 1 |
63
+ | 2.2 | Service provision ..... | 2 |
64
+ | 2.3 | Types of service..... | 2 |
65
+ | 2.4 | Areas of service coverage ..... | 2 |
66
+ | 2.5 | Service configurations ..... | 2 |
67
+ | 3 | Quality of Service ..... | 2 |
68
+ | 3.1 | Service availability ..... | 3 |
69
+ | 4 | Access ..... | 4 |
70
+ | 4.1 | Transmit..... | 4 |
71
+ | 4.2 | Receive ..... | 4 |
72
+ | 5 | Classes of space segment ..... | 4 |
73
+
74
+
75
+
76
+ # **POINT-TO-MULTIPOINT TELECOMMUNICATION SERVICE VIA SATELLITE**
77
+
78
+ *(Melbourne, 1988; revised Helsinki, 1993)*
79
+
80
+ The CCITT,
81
+
82
+ *considering*
83
+
84
+ - (a) the need for a point-to-multipoint telecommunication service;
85
+ - (b) the loss of the HF multi-destinational Press broadcast service for this purpose;
86
+ - (c) the availability of satellites for point-to-multipoint telecommunications services on a regional and world-wide basis;
87
+ - (d) the availability of a multiplicity of earth station sizes;
88
+ - (e) the need for a clarification in terms of the functional elements of this service;
89
+ - (f) the need for the flexibility of their implementation in order to adapt to the needs of all Administrations,
90
+
91
+ *recommends*
92
+
93
+ the following operational guidelines and Quality of Service requirements for an international point-to-multipoint telecommunication service via satellite.
94
+
95
+ ## **1 Scope<sup>1)</sup>**
96
+
97
+ This Recommendation provides operational guidelines and Quality of Service requirements for an international one-way point-to-multipoint telecommunication service via satellite. See Recommendation D.185 for the general tariff and accounting principles for the international point-to-multipoint telecommunication service via satellite.
98
+
99
+ ## **1.1 Definition of service**
100
+
101
+ The **international point-to-multipoint telecommunication service via satellite** is defined as a service provided to a customer by Administrations for the transmission for example, of text, photographs or data via a satellite for the reception at a multiplicity of destinations by receive-only earth stations.
102
+
103
+ # **2 Service description**
104
+
105
+ ## **2.1 Functional elements of service**
106
+
107
+ A point-to-multipoint telecommunication service via satellite includes the seven following elements (see Figure 1);
108
+
109
+ - 1) the provider(s) of information;
110
+ - 2) the link between the provider(s) and the control management centre;
111
+
112
+ ---
113
+
114
+ <sup>1)</sup> Multipoint-to-point and two-way multiple access services are not addressed in this Recommendation, and are subject to further study.
115
+
116
+ - 3) the control management centre which uses various transmission means in order to collect, address, and multiplex the information from the provider(s);
117
+ - 4) the link between the command and management centre and the up link transmit earth stations;
118
+ - 5) transmit earth station(s);
119
+ - 6) the transponder of a satellite(s);
120
+ - 7) one or several receive earth stations;
121
+ - 8) the link(s) from the receive earth station(s) to the user(s) equipment.
122
+
123
+ ## **2.2 Service provision**
124
+
125
+ The service may be provided on either a full time 24-hour basis, a scheduled part-time basis (e.g., five hours per day), or occasional use basis (e.g., a special event), subject to such terms as may be agreed between Administrations.
126
+
127
+ ## **2.3 Types of service**
128
+
129
+ The service may be provided:
130
+
131
+ - a) in the form of one or more analogue channels, the bandwidth of which may lie anywhere within the maximum available bandwidth of one transponder; or
132
+ - b) in the form of one or more digital channels operating at any speed within the maximum available digital capacity of one transponder.
133
+
134
+ ## **2.4 Areas of service coverage**
135
+
136
+ The service may be provided on a regional or global basis depending on customer requirements and satellite capability.
137
+
138
+ ## **2.5 Service configurations**
139
+
140
+ As illustrated in Figure 1, there are eight functional elements in the provision of a point-to-multipoint telecommunication service via satellite. Owing to the need for flexibility, the systems may be adapted to a diversity of needs and the regulations of each Administration involved.
141
+
142
+ The conditions of use of the transmit (5) and receive (7) earth stations and the links (2) and (4) conveying the information flow remain a national matter to be determined by the competent authority in each country.
143
+
144
+ The conditions of use of the space segment (6) are defined by the organizations (INTELSAT, EUTELSAT, etc.) in charge of their provision and by whatever agreements on coordination made by the competent international organizations.
145
+
146
+ The control management centre (3) for the service may be located and/or operated with the transmit earth station, the provider of the information or independently of these two entities.
147
+
148
+ # **3 Quality of Service**
149
+
150
+ The efficiency of operation and therefore the Quality of Service provided to the users 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 their operation. Quality of Service parameters and values are for further study based on operational experience.
151
+
152
+ ![Diagram of a satellite communication system architecture showing providers, transmissions, a control management centre, and receive earth stations.](fc46871d72c65d3381d9201646d23439_img.jpg)
153
+
154
+ The diagram illustrates a satellite communication system architecture, divided into three main functional areas by vertical dashed lines:
155
+
156
+ - Providers:** On the left, this section contains:
157
+ - (1) Host A and Host C, represented by rectangular blocks.
158
+ - Sub-network B, represented by a dashed oval.
159
+ - (2) Lines connecting Host A, Sub-network B, and Host C to the central processing unit.
160
+ - Transmissions:** The central area features:
161
+ - (3) A large rectangular block labeled "Protocol conversion Multiplexing Addressing Network control".
162
+ - (4) A line connecting Host C to the central block.
163
+ - (5) A "Transmit earth station(s)" icon, represented by a square with a circle inside.
164
+ - (6) A "Satellite" icon, represented by a circle with a cross inside.
165
+ - Dashed arrows showing the signal flow from the transmit earth station (5) to the satellite (6).
166
+ - Receive earth stations:** On the right, this section shows:
167
+ - (7) Three dashed ovals, each containing a receive earth station icon (square with a circle).
168
+ - (8) Each oval is connected to "User equipment", represented by a trapezoidal shape.
169
+ - Dashed arrows showing the signal flow from the satellite (6) to each of the three receive earth stations (7).
170
+
171
+ At the bottom of the diagram, the text "T0103140-93/d01" is present in the bottom right corner.
172
+
173
+ Diagram of a satellite communication system architecture showing providers, transmissions, a control management centre, and receive earth stations.
174
+
175
+ FIGURE 1/F.140
176
+
177
+ ## 3.1 Service availability
178
+
179
+ Service availability is the ratio of aggregate time during which satisfactory or tolerable service is or could be provided, to the total observation period (Recommendation X.140, definition).
180
+
181
+ As this availability of service depends on the class of space segment, the earth station configurations, the propagation and interference effects and the bit error ratio required, it is not possible to specify a service availability requirement for all point-to-multipoint telecommunication services via satellite. The service availability for each customer will have to be calculated on an individual case basis considering all the points mentioned above.
182
+
183
+ # 4 Access
184
+
185
+ ## 4.1 Transmit
186
+
187
+ The point of interconnection to the service may be located at the providers' location or on the Administrations' premises. When the point of interconnection to the service is located on the Administrations' premises, the providers' access may be via a leased circuit or a public switched network.
188
+
189
+ ## 4.2 Receive
190
+
191
+ The receive earth station(s) may be located on the users premises or at Administrations' premises. Where the receive earth stations are located at the Administration's premises, access to the user should be via direct connection. The user of a public switched network is for further study.
192
+
193
+ # 5 Classes of space segment
194
+
195
+ Services offered may take account of classes of space segment available from the space segment provider(s). The following classes of space segment may be utilized to provide service:
196
+
197
+ - 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 service:
198
+ - 1) protected – A service for which restoration is guaranteed; and
199
+ - 2) unprotected – A service for which restoration is not guaranteed and which may only be restored subject to availability of an alternate facility;
200
+ - b) *pre-emptible* – A service which may be interrupted to provide a service of higher priority.
marked/F/T-REC-F.15-199208-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg ADDED

Git LFS Details

  • SHA256: 585dd722ecc04d3d3166b4fb43f2782193f3f2ccf18e0831ebf487cf1138cba1
  • Pointer size: 129 Bytes
  • Size of remote file: 5.82 kB
marked/F/T-REC-F.15-199208-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 53b38f9728e381fb51b0c45f96e9b10639de778e8b4033416d00ef085b8f75b2
  • Pointer size: 129 Bytes
  • Size of remote file: 7.46 kB
marked/F/T-REC-F.15-199208-I_PDF-E/raw.md ADDED
@@ -0,0 +1,146 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ ![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
4
+
5
+ ITU logo: A globe with a lightning bolt and the letters ITU.
6
+
7
+ INTERNATIONAL TELECOMMUNICATION UNION
8
+
9
+ **CCITT**
10
+
11
+ THE INTERNATIONAL
12
+ TELEGRAPH AND TELEPHONE
13
+ CONSULTATIVE COMMITTEE
14
+
15
+ **F.15**
16
+
17
+ (08/92)
18
+
19
+ **TELEGRAPH AND MOBILE SERVICES**
20
+
21
+ **OPERATIONS AND QUALITY OF SERVICE**
22
+
23
+ ---
24
+
25
+ **EVALUATING THE SUCCESS
26
+ OF NEW SERVICES**
27
+
28
+ **Recommendation F.15**
29
+
30
+ ---
31
+
32
+ ![CCITT logo: A globe with the letters CCITT.](1d7527f4316cfe2d342b08d1653d1592_img.jpg)
33
+
34
+ CCITT logo: A globe with the letters CCITT.
35
+
36
+ Geneva, 1992
37
+
38
+ # FOREWORD
39
+
40
+ The CCITT (the International Telegraph and Telephone Consultative Committee) is the 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.
41
+
42
+ 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).
43
+
44
+ Recommendation F.15 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992.
45
+
46
+
47
+
48
+ ---
49
+
50
+ # CCITT NOTE
51
+
52
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
53
+
54
+ # **EVALUATING THE SUCCESS OF NEW SERVICES**
55
+
56
+ (1992)
57
+
58
+ ## **1 Introduction**
59
+
60
+ This Recommendation provides guidance on the factors which should be taken into account in assessing the probability of success of new services which Administrations may be considering for introduction. Such a determination will permit Administrations to be more responsive to customers' growing and changing needs, and will also permit Administrations to plan the necessary network facilities and capacities which the new service may require.
61
+
62
+ *Note* – Guidance on forecasting new services for traffic engineering purposes may be found in Recommendation E.508.
63
+
64
+ ## **2 Market research**
65
+
66
+ Market research is a valuable tool which should be used for new services or for services for which there is no historical demand data. This research may employ questionnaires, market analysis, focus groups and interviews. Its purpose is to determine customers' intentions to purchase or use a new service, customers' attitudes towards new or existing services, price sensitivity and cross-service elasticities. Market research helps to identify customers' needs for innovative services and the likely success of new service offerings. Market research will help to avoid the pitfall of offering new services which are developed largely on the basis of the capabilities of the new technologies, without a clear understanding of customers' needs.
67
+
68
+ ## **3 Factors affecting the successful offering of new services**
69
+
70
+ The following are some important factors which should be analysed and taken into account when assessing the chances for the success of a new service offering.
71
+
72
+ ### **3.1 Customer-oriented factors**
73
+
74
+ #### **3.1.1 Customers' needs**
75
+
76
+ - Strength of customers' needs (business/residence);
77
+ - degree to which the service solves customers' needs;
78
+ - availability of other solutions.
79
+
80
+ #### **3.1.2 Human factors aspects of the service**
81
+
82
+ - Ease of learning (learnability);
83
+ - ease of use (usability);
84
+ - extent of match with users' requirements (functionality);
85
+ - capability to satisfy needs of different categories of users (flexibility);
86
+ - benefits provided to users (usefulness);
87
+ - availability of corresponding services to others (ubiquity).
88
+
89
+ #### **3.1.3 Customers' price sensitivity**
90
+
91
+ - Expected limit/range of charges for the service (or package of services);
92
+ - price of alternative services;
93
+ - price/benefit relationship.
94
+
95
+ #### **3.1.4 Customers' quality expectations**
96
+
97
+ - Availability;
98
+ - connection speed, accuracy and clarity;
99
+
100
+ - reliability;
101
+ - ease of problem referral;
102
+ - speed of repair;
103
+ - privacy and security;
104
+ - training and customer support.
105
+
106
+ #### 3.1.5 *Charging and billing aspects*
107
+
108
+ - Charging mode/method;
109
+ - charging accuracy;
110
+ - completeness and clarity of bills;
111
+ - frequency of bill presentation;
112
+ - resolution of billing disputes.
113
+
114
+ #### 3.1.6 *Provisioning aspects*
115
+
116
+ - Ease of placing orders;
117
+ - speed of installation;
118
+ - accommodation of special requests;
119
+ - reliability in meeting service dates.
120
+
121
+ ### 3.2 *Administration-oriented factors*
122
+
123
+ #### 3.2.1 *Expected market size*
124
+
125
+ - Expected number of customers – initially, long-term;
126
+ - amount of service usage by typical customer;
127
+ - availability of alternative services – now, later;
128
+ - reaction of competitors;
129
+ - service life-cycle.
130
+
131
+ #### 3.2.2 *Service provisioning*
132
+
133
+ - Internal procedures and interfaces;
134
+ - external procedures and interfaces.
135
+
136
+ #### 3.2.3 *Technical requirements*
137
+
138
+ - Development requirements and timeframes;
139
+ - impact on network and other services;
140
+ - maintenance and operational considerations.
141
+
142
+ #### 3.2.4 *Regulatory consequences*
143
+
144
+ - Possible conflicts with present or future regulations;
145
+ - privacy requirements;
146
+ - security requirements.
marked/F/T-REC-F.16-199502-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg ADDED

Git LFS Details

  • SHA256: 61b45b08f661cfa65ec7d7d9d3044bb39b4637efe798cb5996e8b7a06d9320c4
  • Pointer size: 130 Bytes
  • Size of remote file: 64.4 kB
marked/F/T-REC-F.16-199502-I_PDF-E/1956f44611abd5c3c41049836aa78ad8_img.jpg ADDED

Git LFS Details

  • SHA256: c399680630d327d832fe74256181c01abb06e7bb7788dfef4cce571a9fc53a68
  • Pointer size: 130 Bytes
  • Size of remote file: 66.9 kB
marked/F/T-REC-F.16-199502-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 918856d707d44d2b6816333bd3ab17245b7ca6e7d7dcbf81a5f92a45078c43f8
  • Pointer size: 129 Bytes
  • Size of remote file: 8.2 kB
marked/F/T-REC-F.16-199502-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg ADDED

Git LFS Details

  • SHA256: 5d82d284dd728376d9af9c18c43002556fd9fc4dc7048243bd08769a90de3e55
  • Pointer size: 130 Bytes
  • Size of remote file: 64.7 kB
marked/F/T-REC-F.16-199502-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg ADDED

Git LFS Details

  • SHA256: fa9eab66d422398fad4c63c33d2fd22803288580f267770c5356011883a9bd57
  • Pointer size: 130 Bytes
  • Size of remote file: 29.3 kB
marked/F/T-REC-F.16-199502-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg ADDED

Git LFS Details

  • SHA256: 079b3d69ca6d51a583ee5ddbc5f4be462df885f1b18899d7082f544099b2cc9b
  • Pointer size: 131 Bytes
  • Size of remote file: 125 kB
marked/F/T-REC-F.16-199502-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg ADDED

Git LFS Details

  • SHA256: d14fc06711df7da588404d5b2d74f7640db7e6f6af5ee0d3ebc2dae6b2fd5e0e
  • Pointer size: 131 Bytes
  • Size of remote file: 124 kB
marked/F/T-REC-F.16-199502-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg ADDED

Git LFS Details

  • SHA256: 516c4667a7d03d3ca794b707ced776182fc415381adc5ed99286101a1ddde627
  • Pointer size: 131 Bytes
  • Size of remote file: 133 kB
marked/F/T-REC-F.16-199502-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg ADDED

Git LFS Details

  • SHA256: 3f1dd3039cd40660503a0cbe0fc653e89ef4a79bcea224c6f9b09d8bfac5fd1e
  • Pointer size: 130 Bytes
  • Size of remote file: 65.3 kB
marked/F/T-REC-F.16-199502-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg ADDED

Git LFS Details

  • SHA256: bc2976ed737022a7ddad50577947a4b7034abc32163ce35e5b0b0f6dfac5b7a5
  • Pointer size: 130 Bytes
  • Size of remote file: 41.4 kB
marked/F/T-REC-F.16-199502-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg ADDED

Git LFS Details

  • SHA256: 040593ae97c3d6a5aea37bb7d25531f72e85e29c596a847f0236e5970a85ce9d
  • Pointer size: 130 Bytes
  • Size of remote file: 87.3 kB
marked/F/T-REC-F.16-199502-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg ADDED

Git LFS Details

  • SHA256: 752305be572cc8c80d5fc3b51c594c2adb0c88d09149c5586fc238414466f8ff
  • Pointer size: 131 Bytes
  • Size of remote file: 140 kB
marked/F/T-REC-F.16-199502-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg ADDED

Git LFS Details

  • SHA256: f8e8f51cdcc05d5dbbc5402f6dd193dc54a7c38f3929e6314366f200dad16881
  • Pointer size: 130 Bytes
  • Size of remote file: 67.8 kB
marked/F/T-REC-F.17-199208-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 53b38f9728e381fb51b0c45f96e9b10639de778e8b4033416d00ef085b8f75b2
  • Pointer size: 129 Bytes
  • Size of remote file: 7.46 kB
marked/F/T-REC-F.17-199208-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg ADDED

Git LFS Details

  • SHA256: 8ad771190b3f2dc31027dd113f455c05fa2b1c3c918ddc72edc6e79481a5f1e2
  • Pointer size: 129 Bytes
  • Size of remote file: 5.79 kB
marked/F/T-REC-F.171-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 454a9958ffe168868cb7d38a0eb24418dafe31a7a4245c992089b2316ac37d3e
  • Pointer size: 129 Bytes
  • Size of remote file: 7.39 kB
marked/F/T-REC-F.18-199803-I_PDF-E/042733dc5e8e7f5f30b60adba3266cde_img.jpg ADDED

Git LFS Details

  • SHA256: dfb08ea0460b17b312638c236bfc425ead9bf8736d7824324d5facec5af0cc11
  • Pointer size: 130 Bytes
  • Size of remote file: 87.4 kB
marked/F/T-REC-F.18-199803-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 45c6dff9053d8a7e288da732dba26e17495b18ed53976902395111cbbc38e6cb
  • Pointer size: 129 Bytes
  • Size of remote file: 8.29 kB
marked/F/T-REC-F.18-199803-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg ADDED

Git LFS Details

  • SHA256: 94a87671774611a21844244cbe3ab0e750b0c55a5b56c5452b255959e31cb760
  • Pointer size: 131 Bytes
  • Size of remote file: 100 kB
marked/F/T-REC-F.18-199803-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg ADDED

Git LFS Details

  • SHA256: 212095117febff7f9829aa69e14ff251d7b8f7d4d849f6140499217f116e6568
  • Pointer size: 130 Bytes
  • Size of remote file: 99.5 kB
marked/F/T-REC-F.18-199803-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg ADDED

Git LFS Details

  • SHA256: b932e2f38829b587e760446e7fd8fa54ddbff38c4819ea047f0739000cf09efb
  • Pointer size: 130 Bytes
  • Size of remote file: 67.8 kB
marked/F/T-REC-F.18-199803-I_PDF-E/e9314c83043183351ed74908e9bf2f90_img.jpg ADDED

Git LFS Details

  • SHA256: a60fc850634f0ed597837cf4d045c375eeeddecfe269e6720a1bca935cb63154
  • Pointer size: 130 Bytes
  • Size of remote file: 86.1 kB
marked/F/T-REC-F.182bis-199610-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 97adcbdebb3326a1af9817c0266d6c1cef088a8f97dc377b1e5fd01e721d14f7
  • Pointer size: 129 Bytes
  • Size of remote file: 8.27 kB
marked/F/T-REC-F.185-199806-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 45c6dff9053d8a7e288da732dba26e17495b18ed53976902395111cbbc38e6cb
  • Pointer size: 129 Bytes
  • Size of remote file: 8.29 kB
marked/F/T-REC-F.185-199806-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg ADDED

Git LFS Details

  • SHA256: 1173e52051faba516700c2595006751abf40b608ce4ad7398eaf0b1b86c546f5
  • Pointer size: 130 Bytes
  • Size of remote file: 44.7 kB
marked/F/T-REC-F.185-199806-I_PDF-E/7a0db9703b68b3d06cdaeefc084c0006_img.jpg ADDED

Git LFS Details

  • SHA256: e93a74be1fd8f54bddbb203404dc01a2235a0d815cdc5183130a705dcd7f1db9
  • Pointer size: 130 Bytes
  • Size of remote file: 35.3 kB
marked/F/T-REC-F.185-199806-I_PDF-E/raw.md ADDED
@@ -0,0 +1,306 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ ![ITU logo: A globe with a lightning bolt and the letters ITU.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
4
+
5
+ ITU logo: A globe with a lightning bolt and the letters ITU.
6
+
7
+ INTERNATIONAL TELECOMMUNICATION UNION
8
+
9
+ **ITU-T**
10
+
11
+ TELECOMMUNICATION
12
+ STANDARDIZATION SECTOR
13
+ OF ITU
14
+
15
+ **F.185**
16
+
17
+ (06/98)
18
+
19
+ SERIES F: NON-TELEPHONE TELECOMMUNICATION
20
+ SERVICES
21
+
22
+ Telematic services – Public facsimile service
23
+
24
+ ---
25
+
26
+ **Internet facsimile: Guidelines for the support of
27
+ the communication of facsimile documents**
28
+
29
+ ITU-T Recommendation F.185
30
+
31
+ (Previously CCITT Recommendation)
32
+
33
+ ---
34
+
35
+ # ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
36
+
37
+ | | |
38
+ |-----------------------------------------------------------------|--------------------|
39
+ | <b>TELEGRAPH SERVICE</b> | |
40
+ | Operating methods for the international public telegram service | F.1–F.19 |
41
+ | The gentex network | F.20–F.29 |
42
+ | Message switching | F.30–F.39 |
43
+ | The international telemessage service | F.40–F.58 |
44
+ | The international telex service | F.59–F.89 |
45
+ | Statistics and publications on international telegraph services | F.90–F.99 |
46
+ | Scheduled and leased communication services | F.100–F.104 |
47
+ | Phototelegraph service | F.105–F.109 |
48
+ | <b>MOBILE SERVICE</b> | |
49
+ | Mobile services and multdestination satellite services | F.110–F.159 |
50
+ | <b>TELEMATIC SERVICES</b> | |
51
+ | <b>Public facsimile service</b> | <b>F.160–F.199</b> |
52
+ | Teletex service | F.200–F.299 |
53
+ | Videotex service | F.300–F.349 |
54
+ | General provisions for telematic services | F.350–F.399 |
55
+ | <b>MESSAGE HANDLING SERVICES</b> | F.400–F.499 |
56
+ | <b>DIRECTORY SERVICES</b> | F.500–F.549 |
57
+ | <b>DOCUMENT COMMUNICATION</b> | |
58
+ | Document communication | F.550–F.579 |
59
+ | Programming communication interfaces | F.580–F.599 |
60
+ | <b>DATA TRANSMISSION SERVICES</b> | F.600–F.699 |
61
+ | <b>AUDIOVISUAL SERVICES</b> | F.700–F.799 |
62
+ | <b>ISDN SERVICES</b> | F.800–F.849 |
63
+ | <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b> | F.850–F.899 |
64
+ | <b>HUMAN FACTORS</b> | F.900–F.999 |
65
+
66
+ *For further details, please refer to ITU-T List of Recommendations.*
67
+
68
+ # **ITU-T RECOMMENDATION F.185**
69
+
70
+ # **INTERNET FACSIMILE: GUIDELINES FOR THE SUPPORT OF THE COMMUNICATION OF FACSIMILE DOCUMENTS**
71
+
72
+ ## **Summary**
73
+
74
+ This Recommendation describes the guidelines for the support of the communication of facsimile documents (both Group 3 and Group 4) via the Internet in real-time or store-and-forward mode.
75
+
76
+ NOTE – Support for Group 4 is for further study.
77
+
78
+ ### **Source**
79
+
80
+ ITU-T Recommendation F.185 was prepared by ITU-T Study Group 8 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 18th of June 1998.
81
+
82
+ ## FOREWORD
83
+
84
+ 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.
85
+
86
+ 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.
87
+
88
+ The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
89
+
90
+ 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.
91
+
92
+ ### NOTE
93
+
94
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
95
+
96
+ ## INTELLECTUAL PROPERTY RIGHTS
97
+
98
+ 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.
99
+
100
+ 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.
101
+
102
+ © ITU 1998
103
+
104
+ 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.
105
+
106
+ ## CONTENTS
107
+
108
+ *Page*
109
+
110
+ | | | |
111
+ |-------|-------------------------------------------------------------------|---|
112
+ | 1 | Scope..... | 1 |
113
+ | 2 | References..... | 1 |
114
+ | 3 | Definitions and abbreviations..... | 1 |
115
+ | 3.1 | Definitions ..... | 1 |
116
+ | 3.1.1 | Real-time session oriented Internet facsimile ("real-time") ..... | 1 |
117
+ | 3.1.2 | Store-and-forward facsimile..... | 1 |
118
+ | 3.1.3 | Standard facsimile terminal..... | 2 |
119
+ | 3.1.4 | Gateway ..... | 2 |
120
+ | 3.1.5 | Email client..... | 2 |
121
+ | 3.1.6 | Internet Aware Facsimile terminal (IAF)..... | 2 |
122
+ | 3.2 | Abbreviations ..... | 2 |
123
+ | 4 | Models for Internet access ..... | 2 |
124
+ | 5 | General provisions ..... | 3 |
125
+ | 5.1 | General ..... | 3 |
126
+ | 5.2 | Basic requirements ..... | 4 |
127
+ | 5.3 | Standardized options ..... | 4 |
128
+ | 6 | Network requirements..... | 4 |
129
+ | 7 | Procedures for the transmission of documents ..... | 4 |
130
+ | 8 | Coding scheme..... | 4 |
131
+
132
+
133
+
134
+ # **INTERNET FACSIMILE: GUIDELINES FOR THE SUPPORT OF THE COMMUNICATION OF FACSIMILE DOCUMENTS**
135
+
136
+ *(Geneva, 1998)*
137
+
138
+ ## **1 Scope**
139
+
140
+ This Recommendation describes the guidelines for the support of the communication of facsimile documents (both Group 3 and Group 4) via the Internet in real-time or store-and-forward mode.
141
+
142
+ NOTE – Support for Group 4 is for further study.
143
+
144
+ ## **2 References**
145
+
146
+ 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.
147
+
148
+ - ITU-T Recommendation T.4 (1996), *Standardization of Group 3 facsimile terminals for document transmission*.
149
+ - ITU-T Recommendation T.563 (1996), *Terminal characteristics for Group 4 facsimile apparatus*.
150
+ - ITU-T Recommendation T.37 (1998), *Procedures for the transfer of facsimile data via store-and-forward on the Internet*.
151
+ - ITU-T Recommendation T.38 (1998), *Procedures for real-time Group 3 facsimile communication over IP networks*.
152
+
153
+ ## **3 Definitions and abbreviations**
154
+
155
+ ### **3.1 Definitions**
156
+
157
+ This Recommendation defines the following terms:
158
+
159
+ #### **3.1.1 Real-time session oriented Internet facsimile ("real-time")**
160
+
161
+ Real-time session oriented Internet facsimile involves the transmission/reception of a facsimile in a single session such that confirmation of receipt is provided to the transmitting terminal prior to disconnection. Real-time session oriented communication over the Internet between two facsimile terminals conforming to the relevant ITU-T Recommendations is accomplished when:
162
+
163
+ - 1) the contents and sequence of standard messages exchanged between the sending and receiving terminals are preserved, as far as practicable;
164
+ - 2) the call duration using the Internet is comparable to that of a facsimile session using the GSTN/ISDN between the two terminals.
165
+
166
+ This definition is valid both for terminals connected directly to the Internet and for terminals using another network for access to the Internet.
167
+
168
+ #### **3.1.2 Store-and-forward facsimile**
169
+
170
+ **3.1.2.1** This involves the transmission/reception of a facsimile other than in real-time. Such transmission/reception takes place via the store-and-forward mode on the Internet using Internet Email.
171
+
172
+ **3.1.2.2** "Simple" mode store-and-forward facsimile communication over the Internet is accomplished when only the coded image is transmitted.
173
+
174
+ **3.1.2.3** "Full" mode store-and-forward facsimile communication over the Internet between two facsimile terminals conforming to the relevant ITU-T Recommendations is accomplished when:
175
+
176
+ - 1) the capabilities of the terminals are exchanged;
177
+ - 2) an acknowledgement of receipt is exchanged between gateways and may be transferred from the receiving terminal to the sending terminal;
178
+ - 3) the contents of standard messages used by the transmitting terminal are preserved.
179
+
180
+ This definition is valid both for terminals connected directly to the Internet (Internet Aware Facsimile) and for terminals using another network for access to the Internet.
181
+
182
+ #### **3.1.3 Standard facsimile terminal**
183
+
184
+ A standard facsimile terminal is a system currently capable of sending and receiving facsimile documents in accordance with the relevant ITU-T Recommendations. Such a terminal has no capabilities to enable it to send or receive store-and-forward facsimile. A standard facsimile terminal may be connected to a gateway to provide the functionality of an Internet Aware Facsimile.
185
+
186
+ #### **3.1.4 Gateway**
187
+
188
+ A gateway provides access to the Internet for standard facsimile terminals. A gateway service is capable of accepting facsimile documents from, and capable of sending facsimile documents to, standard facsimile terminals.
189
+
190
+ The responsibilities of such gateways are for further study.
191
+
192
+ #### **3.1.5 Email client**
193
+
194
+ An Email client is a UA capable of sending and receiving Internet Email and capable of store-and-forward facsimile. Such a client may be an Email package conforming to the relevant Internet standards and the connection to the Internet may be via a local network or via a dial-up call over the GSTN or ISDN.
195
+
196
+ #### **3.1.6 Internet Aware Facsimile terminal (IAF)**
197
+
198
+ For store-and-forward facsimile, an Internet Aware Facsimile terminal combines the capabilities of a standard facsimile terminal and an Email client. For real-time facsimile, an Internet Aware Facsimile terminal has the capabilities of a standard facsimile terminal as well as having an IP address or domain name together with its GSTN address. In either mode, it is capable of sending and receiving facsimile documents via the appropriate network.
199
+
200
+ ### **3.2 Abbreviations**
201
+
202
+ This Recommendation uses the following abbreviations:
203
+
204
+ | | |
205
+ |---------|---------------------------------------------|
206
+ | Email | Electronic Mail |
207
+ | Group 3 | Terminal conforming to Recommendation T.4 |
208
+ | Group 4 | Terminal conforming to Recommendation T.563 |
209
+ | GSTN | General Switched Telephone Network |
210
+ | IAF | Internet Aware Facsimile terminal |
211
+ | ISDN | Integrated Services Digital Network |
212
+ | UA | User Agent |
213
+
214
+ ## **4 Models for Internet access**
215
+
216
+ The diagrams below show different methods of Internet access for PC Email clients, Internet Aware Facsimile terminals and standard facsimile terminals connected via a gateway. Such connections may be used for store-and-forward facsimile or real-time facsimile.
217
+
218
+ Figure 1 shows the methods for store-and-forward Internet facsimile and Figure 2 shows the methods for real-time Internet facsimile.
219
+
220
+ As an option, in case of communication difficulties with the real-time method, it is permitted to fall back to the store-and-forward mode.
221
+
222
+ ![Diagram of store-and-forward operation (T.37)](562f471e8153729557e6a4ee6343c32c_img.jpg)
223
+
224
+ This diagram illustrates the store-and-forward operation for Internet facsimile. At the center is a diamond labeled 'The Internet'. To the left, three boxes are connected to it: 'Standard fax terminal' via a 'Gateway', 'Email client', and 'Internet Aware Fax terminal (IAF)'. To the right, the same three boxes are connected to 'The Internet' in the same manner. Arrows indicate bidirectional communication between each terminal and its respective connection point (Gateway or directly to the Internet diamond). A small code 'T0828030-98/d01' is located at the bottom right of the diagram.
225
+
226
+ Diagram of store-and-forward operation (T.37)
227
+
228
+ Figure 1/F.185 – Store-and-forward operation (T.37)
229
+
230
+ ![Diagram of real-time operation (T.38)](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
231
+
232
+ This diagram illustrates the real-time operation for Internet facsimile. At the center is a diamond labeled 'The Internet'. To the left, two boxes are connected to it: 'Standard fax terminal' via a 'Gateway' and 'Internet Aware Fax terminal (IAF)' directly. To the right, the same two boxes are connected to 'The Internet' in the same manner. Arrows indicate bidirectional communication between each terminal and its respective connection point (Gateway or directly to the Internet diamond). A small code 'T0828040-98/d02' is located at the bottom right of the diagram.
233
+
234
+ Diagram of real-time operation (T.38)
235
+
236
+ Figure 2/F.185 – Real-time operation (T.38)
237
+
238
+ ## 5 General provisions
239
+
240
+ ### 5.1 General
241
+
242
+ The essential characteristic of the guidelines for the support of the communication of facsimile documents over the Internet is that it provides a basic level of compatibility between all terminals supporting the capabilities.
243
+
244
+ The communication of facsimile documents via the GSTN or ISDN has a greater level of message privacy than via the Internet. The use of security enhancements on the Internet increases the level of message privacy.
245
+
246
+ ### **5.2 Basic requirements**
247
+
248
+ - 1) The basic level of compatibility is provided between any two terminals both nationally and internationally so that they may communicate image coded information to each other. This is to be achieved by requiring that terminals comply with the relevant ITU-T Recommendations as modified for transmission across the Internet.
249
+ - 2) It should be possible to extend the support of the communication of facsimile documents on the Internet to any number of countries.
250
+ - 3) It should enable the transport of the recipient terminal addressing information across the Internet.
251
+ - 4) To permit private use options, there shall be no technical limitation on the bit sequence of the user's information that may be transmitted.
252
+ - 5) A received Internet facsimile document can be printed or displayed as decided by the recipient and taking into account the terminal characteristics.
253
+ - 6) In the simple mode, terminal-to-terminal receipt acknowledgement need not be provided. In the full mode, terminal-to-terminal receipt acknowledgement shall be provided.
254
+ - 7) The receipt acknowledgement shall contain information to indicate successful receipt or an indication of any error. An example might be the rejection of a request to relay a store-and-forward facsimile document to a standard facsimile terminal.
255
+ - 8) It is intended that the support of communication of facsimile documents on the Internet should require no changes to the Recommendations for existing services or networks.
256
+ - 9) The intention is that the terminal's memory requirement is one page.
257
+ - 10) The intention is that the support of communication of facsimile documents on the Internet should not create additional difficulties for users, e.g. handling the reception of large volumes of unsolicited bulk advertising.
258
+
259
+ ### **5.3 Standardized options**
260
+
261
+ It is recognized that some users may need to use their facsimile terminals to communicate nationally and 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 for which a clear international need can be foreseen.
262
+
263
+ In real-time, the sending terminal shall ensure the transmission of documents using only those options that have been indicated as being available at the receiving terminal. In the store-and-forward mode, the sending terminal shall ensure the transmission of documents using only those options that have been indicated as being available at the receiving terminal where these are known.
264
+
265
+ ## **6 Network requirements**
266
+
267
+ - 1) The support for the communication of facsimile documents over the Internet may be provided over all public networks using the appropriate ITU-T Recommendations for the network concerned.
268
+ - 2) Terminals on any public network which support the communication of facsimile documents over the Internet shall be able to communicate automatically with any other facsimile terminals.
269
+
270
+ ## **7 Procedures for the transmission of documents**
271
+
272
+ The technical procedures for support for the communication of facsimile documents over the Internet are given in Recommendations T.37 for store-and-forward and T.38 for real-time Group 3 documents.
273
+
274
+ ## **8 Coding scheme**
275
+
276
+ All image coding schemes defined in the ITU-T T-series Recommendations for use with standard facsimile terminals should be supported.
277
+
278
+ # ITU-T RECOMMENDATIONS SERIES
279
+
280
+ | | |
281
+ |-----------------|--------------------------------------------------------------------------------------------------------------------------------|
282
+ | Series A | Organization of the work of the ITU-T |
283
+ | Series B | Means of expression: definitions, symbols, classification |
284
+ | Series C | General telecommunication statistics |
285
+ | Series D | General tariff principles |
286
+ | Series E | Overall network operation, telephone service, service operation and human factors |
287
+ | <b>Series F</b> | <b>Non-telephone telecommunication services</b> |
288
+ | Series G | Transmission systems and media, digital systems and networks |
289
+ | Series H | Audiovisual and multimedia systems |
290
+ | Series I | Integrated services digital network |
291
+ | Series J | Transmission of television, sound programme and other multimedia signals |
292
+ | Series K | Protection against interference |
293
+ | Series L | Construction, installation and protection of cables and other elements of outside plant |
294
+ | Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
295
+ | Series N | Maintenance: international sound programme and television transmission circuits |
296
+ | Series O | Specifications of measuring equipment |
297
+ | Series P | Telephone transmission quality, telephone installations, local line networks |
298
+ | Series Q | Switching and signalling |
299
+ | Series R | Telegraph transmission |
300
+ | Series S | Telegraph services terminal equipment |
301
+ | Series T | Terminals for telematic services |
302
+ | Series U | Telegraph switching |
303
+ | Series V | Data communication over the telephone network |
304
+ | Series X | Data networks and open system communications |
305
+ | Series Y | Global information infrastructure |
306
+ | Series Z | Programming languages |