emolero commited on
Commit
7724867
·
verified ·
1 Parent(s): 0c58263

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/Q/T-REC-Q.101-198811-I_PDF-E/raw.md +105 -0
  2. marked/Q/T-REC-Q.106-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  3. marked/Q/T-REC-Q.106-198811-I_PDF-E/raw.md +49 -0
  4. marked/Q/T-REC-Q.109-198811-I_PDF-E/raw.md +49 -0
  5. marked/Q/T-REC-Q.113-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  6. marked/Q/T-REC-Q.113-198811-I_PDF-E/raw.md +63 -0
  7. marked/Q/T-REC-Q.114-198811-I_PDF-E/raw.md +104 -0
  8. marked/Q/T-REC-Q.118bis-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  9. marked/Q/T-REC-Q.1200-199709-I_PDF-E/raw.md +364 -0
  10. marked/Q/T-REC-Q.1208-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  11. marked/Q/T-REC-Q.1208-199709-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg +3 -0
  12. marked/Q/T-REC-Q.1208-199709-I_PDF-E/raw.md +196 -0
  13. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/042af54276c75e7b7b48a3af1f0a84e5_img.jpg +3 -0
  14. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg +3 -0
  15. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg +3 -0
  16. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/212c50c4e3d043c989037a01e13c1a98_img.jpg +3 -0
  17. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg +3 -0
  18. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  19. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg +3 -0
  20. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg +3 -0
  21. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg +3 -0
  22. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/575d7d345b3ec04393bb2ec720ebabca_img.jpg +3 -0
  23. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg +3 -0
  24. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg +3 -0
  25. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg +3 -0
  26. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg +3 -0
  27. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg +3 -0
  28. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg +3 -0
  29. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg +3 -0
  30. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg +3 -0
  31. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg +3 -0
  32. marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/raw.md +0 -0
  33. marked/Q/T-REC-Q.1702-200206-I_PDF-E/raw.md +376 -0
  34. marked/Q/T-REC-Q.1721-200006-I_PDF-E/raw.md +0 -0
  35. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/0073ee258067e591778333101c5d2edb_img.jpg +3 -0
  36. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg +3 -0
  37. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg +3 -0
  38. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2b88ad19a498bc8973acfafdd639c1cd_img.jpg +3 -0
  39. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  40. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/3922e505954d53f8864a44dc9ea664c6_img.jpg +3 -0
  41. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/438622ea89762ed550a4ef3c13fa71a6_img.jpg +3 -0
  42. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg +3 -0
  43. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg +3 -0
  44. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg +3 -0
  45. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg +3 -0
  46. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg +3 -0
  47. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg +3 -0
  48. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg +3 -0
  49. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg +3 -0
  50. marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg +3 -0
marked/Q/T-REC-Q.101-198811-I_PDF-E/raw.md ADDED
@@ -0,0 +1,105 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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 latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe.
6
+
7
+ ITU logo
8
+
9
+ INTERNATIONAL TELECOMMUNICATION UNION
10
+
11
+ **ITU-T**
12
+
13
+ **Q.101**
14
+
15
+ TELECOMMUNICATION
16
+ STANDARDIZATION SECTOR
17
+ OF ITU
18
+
19
+ **GENERAL RECOMMENDATIONS ON TELEPHONE
20
+ SWITCHING AND SIGNALLING**
21
+
22
+ **CLAUSES APPLICABLE TO ITU-T STANDARD
23
+ SYSTEMS**
24
+
25
+ ---
26
+
27
+ **FACILITIES PROVIDED IN INTERNATIONAL
28
+ SEMI-AUTOMATIC WORKING**
29
+
30
+ **ITU-T Recommendation Q.101**
31
+
32
+ (Extract from the *Blue Book*)
33
+
34
+ ---
35
+
36
+ # NOTES
37
+
38
+ 1 ITU-T Recommendation Q.101 was published in Fascicle VI.1 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).
39
+
40
+ 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
41
+
42
+ ## **1.1 FACILITIES PROVIDED IN INTERNATIONAL SEMI-AUTOMATIC WORKING**
43
+
44
+ 1.1.1 The operating methods used in the semi-automatic international service are described in the *Instructions for the International Telephone Service*. These operating methods assume the existence of equipment (operator's positions and automatic switching equipment) involving the following categories of operators:
45
+
46
+ - a) *outgoing* operators;
47
+ - b) *incoming* operators;
48
+ - c) *delay* operators;
49
+ - d) *assistance* operators;
50
+ - e) *information* or *special service* operators.
51
+
52
+ 1.1.2 The *outgoing operator* controls the setting up of calls at the outgoing exchange. (From the operating point of view she is, in general, the controlling operator and is sometimes so referred to in the *Instructions*.)
53
+
54
+ She must be able to set up calls to any one of the following points in the called country:
55
+
56
+ - a) subscribers;
57
+ - b) incoming operators at the incoming international exchange;
58
+ - c) delay operators, especially a particular delay operator at the incoming international exchange;
59
+ - d) incoming operators at a local manual exchange in the called country;
60
+ - e) information or special service operators.
61
+
62
+ The outgoing operator should be able to recall incoming and delay operators on calls set up via these operators, by sending a forward-transfer signal as defined in the relevant system specifications.
63
+
64
+ 1.1.3 The *incoming operator*<sup>1)</sup> at the incoming international exchange is obtained by using a special code 11 signal or a special number. The code 11 signal is a particular combination provided by the signal code. This operator performs the functions of an incoming operator in ordinary manual service for those calls which cannot be routed automatically at the incoming international exchange.
65
+
66
+ 1.1.4 The *delay operator* is obtained by using a special code 12 signal, or a special number. The code 12 signal is a particular combination provided by the signal code. The delay operator may be:
67
+
68
+ - any of the operators of this category;
69
+ - or a particular operator, or one of those operating a particular group of positions; her position or her group of positions is then indicated by a number which follows the code 12 signal or is indicated by the special number.
70
+
71
+ With respect to the direction in which a required call is set up, the delay operator may be at the outgoing international exchange and may be called by an operator at the incoming international exchange. From the technical point of view and as far as signalling is concerned, however, the delay operator at the outgoing international exchange called back by an operator at an incoming international exchange must be regarded as being at the incoming end of the international circuit over which she has been called back.
72
+
73
+ 1.1.5 *Notes on incoming and delay operators*
74
+
75
+ a) Incoming and delay operators must be able to speak the *service language* used for the route concerned, and hence may have to belong to a particular language group. A *language (or information) digit*, from 1 to 8, sent on all
76
+
77
+ ---
78
+
79
+ <sup>1)</sup> Called alternatively in French "opératrice translatrice", see *Instructions for the International Telephone Service* (art. 125).
80
+
81
+ semi-automatic calls, is used to obtain operators of a particular language group [see Recommendation Q.104]<sup>2)</sup>.
82
+
83
+ - b) It may be the same operator who acts as an incoming and as a delay operator, and even as an assistance operator. She enters a circuit in any of these capacities in response to the appropriate signal.
84
+ - c) While an incoming or delay operator is being called, the national ringing tone of the incoming country must be sent back over the international circuit.
85
+
86
+ 1.1.6 The *assistance operator* at the incoming international exchange enters a semi-automatic circuit on a call already set up, when requested by the outgoing operator, because of language difficulties or, for instance, when she is required to interpret a national tone. Access to an assistance operator at an international transit exchange is not possible.
87
+
88
+ The assistance operator is called by a forward-transfer signal, sent by the outgoing operator when, for example, she operates a key on the outgoing position. An assistance operator in a required language group is obtained in conjunction with the forward-transfer signal by the language digit (or information) sent previously during the setting up of the call. Hence the incoming relay set must store the language digit (or information).
89
+
90
+ The outgoing operator receives no indication to show that the assistance operator is being called, or to show when she answers or withdraws from the circuit, but if necessary the outgoing operator can send the forward-transfer signal several times on the same call.
91
+
92
+ The assistance operator must be able:
93
+
94
+ - a) to break into the call as a third party (this she would do, for example, when the language spoken in the country of arrival is other than the service language used in that relation, and the operator intervenes as an interpreter);
95
+ - b) to enter a circuit on one side only after having isolated the other. She does this, in particular, when she translates a verbal announcement or interprets an audible tone returned from the incoming end.
96
+
97
+ In no circumstances will the assistance operator be able to block the international circuit.
98
+
99
+ *Note* - It should be noted that the term "assistance operator" has a very definite meaning in CCITT documents. It stands for an operator who breaks in, as required, as a third party in a circuit already set up. Hence this operator must not be confused with any other operator in the incoming country who may help to *set up* the call in conjunction with the international outgoing operator. Assistance operators may not be available on intraregional circuits.
100
+
101
+ 1.1.7 The *information or special service operator* of the country of destination is obtained by using a special number. This operator is responsible for giving details concerning subscriber number and miscellaneous inquiries.
102
+
103
+ ---
104
+
105
+ 2) The language digit may not be used on some intraregional circuits.
marked/Q/T-REC-Q.106-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/Q/T-REC-Q.106-198811-I_PDF-E/raw.md ADDED
@@ -0,0 +1,49 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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 latitude and longitude lines. A lightning bolt symbol is positioned to the right of the globe.
6
+
7
+ ITU logo
8
+
9
+ INTERNATIONAL TELECOMMUNICATION UNION
10
+
11
+ **ITU-T**
12
+
13
+ **Q.106**
14
+
15
+ TELECOMMUNICATION
16
+ STANDARDIZATION SECTOR
17
+ OF ITU
18
+
19
+ **GENERAL RECOMMENDATIONS ON TELEPHONE
20
+ SWITCHING AND SIGNALLING**
21
+
22
+ **CLAUSES APPLICABLE TO ITU-T STANDARD
23
+ SYSTEMS**
24
+
25
+ ---
26
+
27
+ **THE SENDING - FINISHED SIGNAL**
28
+
29
+ **ITU-T Recommendation Q.106**
30
+
31
+ (Extract from the *Blue Book*)
32
+
33
+ ---
34
+
35
+ ## NOTES
36
+
37
+ 1 ITU-T Recommendation Q.106 was published in Fascicle VI.1 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).
38
+
39
+ 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
40
+
41
+ ## **1.6 THE SENDING-FINISHED SIGNAL**
42
+
43
+ In semi-automatic working, when the international outgoing operator has finished keying or dialling, she operates a special button on her keyboard or a key so that, after the number, a local signal which is called a *sending-finished* signal is sent to the outgoing equipment to show that there are no more digits to follow. In automatic working, subscribers cannot show when they have finished dialling the number, and so this signal does not apply.
44
+
45
+ *Note* - In semi-automatic working, local sending of the sending-finished signal will cause an *end-of-pulsing* signal to be sent on the international circuit <sup>1)</sup> or signalling channel. This has the same function and shows the incoming equipment that there are no more digits to be received. In some cases also in automatic working, when the outgoing equipment decides that there are no more digits to follow, an end-of-pulsing signal is sent on the international circuit or signalling channel, for example in the ST condition of System No. 5 (see Recommendation Q.152).
46
+
47
+ ---
48
+
49
+ <sup>1)</sup> In System R2 the sending of end-of-pulsing signal (code 15) may not occur if a *number-received* indication has already been received.
marked/Q/T-REC-Q.109-198811-I_PDF-E/raw.md ADDED
@@ -0,0 +1,49 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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 latitude and longitude lines. A lightning bolt symbol is positioned to the right of the letters.
6
+
7
+ ITU logo
8
+
9
+ INTERNATIONAL TELECOMMUNICATION UNION
10
+
11
+ **ITU-T**
12
+
13
+ **Q.109**
14
+
15
+ TELECOMMUNICATION
16
+ STANDARDIZATION SECTOR
17
+ OF ITU
18
+
19
+ **GENERAL RECOMMENDATIONS ON TELEPHONE
20
+ SWITCHING AND SIGNALLING**
21
+
22
+ **CLAUSES APPLICABLE TO ITU-T STANDARD
23
+ SYSTEMS**
24
+
25
+ ---
26
+
27
+ **TRANSMISSION OF THE ANSWER SIGNAL IN
28
+ INTERNATIONAL EXCHANGES**
29
+
30
+ **ITU-T Recommendation Q.109**
31
+
32
+ (Extract from the *Blue Book*)
33
+
34
+ ---
35
+
36
+ # NOTES
37
+
38
+ 1 ITU-T Recommendation Q.109 was published in Fascicle VI.1 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).
39
+
40
+ 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
41
+
42
+ ## **1.9 TRANSMISSION OF THE ANSWER SIGNAL IN INTERNATIONAL EXCHANGES**
43
+
44
+ For the reasons given in Recommendation Q.27, it is necessary to reduce to a minimum the delays resulting from:
45
+
46
+ - the conversion of the national answer signal into the international answer signal and vice versa; and
47
+ - the transmission of the international answer signal over the international part of the connection,
48
+
49
+ these delays being additional to any delays due to conversions and repetitions of the answer signal within the national systems of the incoming and outgoing countries.
marked/Q/T-REC-Q.113-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/Q/T-REC-Q.113-198811-I_PDF-E/raw.md ADDED
@@ -0,0 +1,63 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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 latitude and longitude lines.
6
+
7
+ ITU logo
8
+
9
+ INTERNATIONAL TELECOMMUNICATION UNION
10
+
11
+ **ITU-T**
12
+
13
+ **Q.113**
14
+
15
+ TELECOMMUNICATION
16
+ STANDARDIZATION SECTOR
17
+ OF ITU
18
+
19
+ **GENERAL RECOMMENDATIONS ON TELEPHONE
20
+ SWITCHING AND SIGNALLING**
21
+
22
+ **CLAUSES APPLICABLE TO ITU-T STANDARD
23
+ SYSTEMS**
24
+
25
+ ---
26
+
27
+ **CONNECTION OF SIGNAL RECEIVERS IN
28
+ THE CIRCUIT**
29
+
30
+ **ITU-T Recommendation Q.113**
31
+
32
+ (Extract from the *Blue Book*)
33
+
34
+ ---
35
+
36
+ # NOTES
37
+
38
+ 1 ITU-T Recommendation Q.113 was published in Fascicle VI.1 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).
39
+
40
+ 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
41
+
42
+ ## **2.2 CONNECTION OF SIGNAL RECEIVERS IN THE CIRCUIT**
43
+
44
+ 2.2.1 The line signal receivers are permanently connected to the 4-wire side of the circuit. The register signal receivers in System No. 5 are connected to the 4-wire side of the circuit when the register is associated with the circuit for the setting up of the call; the same is valid (in the international exchanges) for the register signal receivers in Systems R1 and R2.
45
+
46
+ 2.2.2 An in-band line signal receiver should be protected against disturbing currents (voice currents or possibly noise), coming from the near end of the circuit, by a buffer amplifier or other arrangement. The arrangement used should introduce an appropriate supplementary attenuation in such a manner that, at the point where the line signal receiver is connected, these disturbing currents are of such a level that they cannot:
47
+
48
+ - operate the line signal receiver;
49
+ - interfere with the reception of signals by operating the guard circuit of the line signal receiver.
50
+
51
+ The additional attenuation introduced should in consequence take account of:
52
+
53
+ - a) the relative level $n$ at the point where the signal receiver is connected (this relative level is obtained by assuming a zero relative level at the distant origin of the circuit);
54
+ - b) the minimum permissible signal level at the input to the signal receiver, for example:
55
+ - $-18 + n$ dBm in the case of System No. 4 (see Recommendation Q.123 § 3.2.1),
56
+ - $-16 + n$ dBm in the case of System No. 5 (see Recommendation Q. 144 § 2.4.1);
57
+ - c) the maximum permissible level for disturbing currents (voice currents and switching noise) coming from the near end of the circuit. The maximum level of voice current might be assumed to be, for example, $+10$ dBm0 in the direction *opposite* to that of the signals. The nature of the switching noises depends on the national systems used;
58
+ - d) any attenuation (terminating set and possibly pads) between the point where the signal receiver is connected and the point where the near-end disturbing currents are considered;
59
+ - e) a safety margin to give an appreciable reduction of the level of disturbing currents coming from the near end [as defined in c)] compared to the minimum level of the signal as defined in b).
60
+
61
+ 2.2.3 When a register-signal receiver is connected to the circuit, the exchange side of the circuit is disconnected and hence the receiver is not subject to near-end disturbances.
62
+
63
+ 2.2.4 The Recommendations of Volume III concerning international circuits must still be met after the connection of a signal sender and a signal receiver and of the switching equipment. In consequence, it is necessary to fix the limits of input and output impedance, insertion loss, attenuation distortion, non-linear distortion, balance, and crosstalk of line signal senders and receivers; an example of specification clauses concerning these conditions is given in Recommendation Q.114.
marked/Q/T-REC-Q.114-198811-I_PDF-E/raw.md ADDED
@@ -0,0 +1,104 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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
+ **Q.114**
14
+
15
+ TELECOMMUNICATION
16
+ STANDARDIZATION SECTOR
17
+ OF ITU
18
+
19
+ **GENERAL RECOMMENDATIONS ON TELEPHONE
20
+ SWITCHING AND SIGNALLING**
21
+
22
+ **CLAUSES APPLICABLE TO ITU-T STANDARD
23
+ SYSTEMS**
24
+
25
+ ---
26
+
27
+ **TYPICAL TRANSMISSION REQUIREMENTS
28
+ FOR SIGNAL SENDERS AND RECEIVERS**
29
+
30
+ **ITU-T Recommendation Q.114**
31
+
32
+ (Extract from the *Blue Book*)
33
+
34
+ ---
35
+
36
+ # NOTES
37
+
38
+ 1 ITU-T Recommendation Q.114 was published in Fascicle VI.1 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).
39
+
40
+ 2 In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
41
+
42
+ ## 2.3 TYPICAL TRANSMISSION REQUIREMENTS FOR SIGNAL SENDERS AND RECEIVERS
43
+
44
+ 2.3.1 In-band line signal receivers (including the buffer amplifier or equivalent device), in §§ 2.3.2 to 2.3.7 below, apply only in the case where the signal receiver is a 4-terminal device ("quadrupole") and where the nominal circuit impedance is 600 ohms.
45
+
46
+ ### 2.3.2 *Input and output impedance*
47
+
48
+ The nominal value of the input and output impedances of the signal receiver is 600 ohms.
49
+
50
+ $Z_E$ and $Z_S$ , which are respectively the measured values of the input and output impedance of the signal receiver, should meet the following condition throughout the 300 to 3400 Hz frequency band:
51
+
52
+ $$\left| \frac{Z_E - 600}{Z_E + 600} \right| \leq 0.35 \text{ and } \left| \frac{Z_S - 600}{Z_S + 600} \right| \leq 0.35.$$
53
+
54
+ In making these measurements the free terminals should be looped by a resistance of 600 ohms and the voltage applied must not overload the equipment.
55
+
56
+ ### 2.3.3 *Attenuation*
57
+
58
+ At 800 Hz, the insertion loss of the signal receiver, measured with a generator and a receiver of internal resistance of 600 ohms, must be between the limits:
59
+
60
+ $$A \pm 0.5 \text{ decibel}$$
61
+
62
+ The value $A$ is to be determined from the level diagram of the circuit according to the point of the circuit at which the signal receiver should be connected.
63
+
64
+ The measurement is made with a 1 mW generator having an internal impedance equal to a pure resistance of 600 ohms and having an e.m.f. of $2 \times 0.775$ volt (so-called "standard generator"). The e.m.f. of the generator will be adjusted to take into account the relative level of the point of the circuit at which the signal receiver is connected.
65
+
66
+ If $n$ is the relative level at the signal receiver input, the e.m.f. of the generator will therefore be:
67
+
68
+ $$1.55 \cdot 10^{\frac{n}{20}} \text{ volts, if } n \text{ is expressed in decibels.}$$
69
+
70
+ ### 2.3.4 *Attenuation distortion*
71
+
72
+ The variation in insertion loss of the signal receiver in the 300-3400 Hz frequency band, measured under the conditions of § 2.3.3 above, should not exceed the limits shown in Figure 1/Q.114.
73
+
74
+ As in certain cases Systems No. 5, and R1 may be applied to circuits in transmission systems with a channel spacing of less than 4 kHz, the 300 Hz lower limit shown above may be replaced by 200 Hz for System No. 5.
75
+
76
+ ### 2.3.5 *Nonlinear distortion*
77
+
78
+ The curve representing the variation (as a function of power) of the output level of the signal receiver, with reference to the nominal value of the output level, should be within the limits shown in Figure 2/Q.114 over the relevant frequency range.
79
+
80
+ ### 2.3.6 *Balance*
81
+
82
+ The input and output of the signal receiver should have a high degree of balance to earth, the admittance of each terminal to earth being very low.
83
+
84
+ The same clause should apply to the signal sender.
85
+
86
+ ![Figure 1/Q.114: Attenuation distortion of the signal receiver. A graph showing attenuation in dB versus frequency in Hz. The y-axis ranges from -0.2 to +0.5 dB. The x-axis has markers at 300, 600, 800, 2400, and 3400 Hz. The graph shows a shaded region between +0.2 dB and +0.5 dB from 300 Hz to 2400 Hz, and another shaded region between -0.2 dB and +0.5 dB from 2400 Hz to 3400 Hz. The text 'CCITT - 48 501' is at the bottom right.](09af5b86cf9391543d22db5f2129b3ca_img.jpg)
87
+
88
+ Figure 1/Q.114: Attenuation distortion of the signal receiver. A graph showing attenuation in dB versus frequency in Hz. The y-axis ranges from -0.2 to +0.5 dB. The x-axis has markers at 300, 600, 800, 2400, and 3400 Hz. The graph shows a shaded region between +0.2 dB and +0.5 dB from 300 Hz to 2400 Hz, and another shaded region between -0.2 dB and +0.5 dB from 2400 Hz to 3400 Hz. The text 'CCITT - 48 501' is at the bottom right.
89
+
90
+ FIGURE 1/Q.114
91
+ Attenuation distortion of the signal receiver
92
+
93
+ ![Figure 2/Q.114: Limits for nonlinear distortion due to the insertion of the signal receiver. A graph showing the variation of the output level in dB versus the power level applied to the input in dBm0. The y-axis ranges from -0.2 to +0.2 dB. The x-axis has a marker at 3.5 dBm0. The graph shows a shaded region between -0.2 dB and +0.2 dB up to 3.5 dBm0. The text 'CCITT - 48 511' is at the bottom right. A note indicates: 'Power level applied to the input of the signal receiver and referred to zero relative level'.](a30a7877bf2f45b837a9382e22067ad0_img.jpg)
94
+
95
+ Figure 2/Q.114: Limits for nonlinear distortion due to the insertion of the signal receiver. A graph showing the variation of the output level in dB versus the power level applied to the input in dBm0. The y-axis ranges from -0.2 to +0.2 dB. The x-axis has a marker at 3.5 dBm0. The graph shows a shaded region between -0.2 dB and +0.2 dB up to 3.5 dBm0. The text 'CCITT - 48 511' is at the bottom right. A note indicates: 'Power level applied to the input of the signal receiver and referred to zero relative level'.
96
+
97
+ FIGURE 2/Q.114
98
+ Limits for nonlinear distortion due to the insertion of the signal receiver
99
+
100
+ ### 2.3.7 *Crosstalk between adjacent signal receivers*
101
+
102
+ The crosstalk ratio between two adjacent signal receivers should not be less than 74 dB in the relevant frequency band.
103
+
104
+ 2.3.8 During the register signalling period no speech transmission takes place. It is not essential therefore for the register signalling equipment of systems having separate equipment for that purpose to take account of §§ 2.3.2 to 2.3.7 above but it is desirable to adopt appropriate clauses for efficient signalling performance.
marked/Q/T-REC-Q.118bis-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/Q/T-REC-Q.1200-199709-I_PDF-E/raw.md ADDED
@@ -0,0 +1,364 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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
+ **Q.1200**
18
+
19
+ (09/97)
20
+
21
+ SERIES Q: SWITCHING AND SIGNALLING
22
+
23
+ Intelligent Network
24
+
25
+ # --- **General series Intelligent Network Recommendation structure**
26
+
27
+ ITU-T Recommendation Q.1200
28
+
29
+ (Previously CCITT Recommendation)
30
+
31
+ ---
32
+
33
+ # ITU-T Q-SERIES RECOMMENDATIONS
34
+
35
+ ## **SWITCHING AND SIGNALLING**
36
+
37
+ | | |
38
+ |----------------------------------------------------------|----------------------|
39
+ | SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1-Q.3 |
40
+ | INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4-Q.59 |
41
+ | FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60-Q.99 |
42
+ | CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100-Q.119 |
43
+ | SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120-Q.249 |
44
+ | SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250-Q.309 |
45
+ | SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310-Q.399 |
46
+ | SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400-Q.499 |
47
+ | DIGITAL EXCHANGES | Q.500-Q.599 |
48
+ | INTERWORKING OF SIGNALLING SYSTEMS | Q.600-Q.699 |
49
+ | SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700-Q.849 |
50
+ | DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850-Q.999 |
51
+ | PUBLIC LAND MOBILE NETWORK | Q.1000-Q.1099 |
52
+ | INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100-Q.1199 |
53
+ | <b>INTELLIGENT NETWORK</b> | <b>Q.1200-Q.1999</b> |
54
+ | BROADBAND ISDN | Q.2000-Q.2999 |
55
+
56
+ *For further details, please refer to ITU-T List of Recommendations.*
57
+
58
+ ## **ITU-T RECOMMENDATION Q.1200**
59
+
60
+ # **GENERAL SERIES INTELLIGENT NETWORK RECOMMENDATION STRUCTURE**
61
+
62
+ ## **Summary**
63
+
64
+ This Recommendation explains the structure of the Q.1200-series Intelligent Network (IN) Recommendations and provides the outline of all general (i.e. Q.120x-series) Recommendations.
65
+
66
+ ## **Source**
67
+
68
+ ITU-T Recommendation Q.1200 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997.
69
+
70
+ # FOREWORD
71
+
72
+ 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.
73
+
74
+ 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.
75
+
76
+ The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
77
+
78
+ 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.
79
+
80
+ # NOTE
81
+
82
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
83
+
84
+ # INTELLECTUAL PROPERTY RIGHTS
85
+
86
+ 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.
87
+
88
+ 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.
89
+
90
+ © ITU 1999
91
+
92
+ 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.
93
+
94
+ # CONTENTS
95
+
96
+ *Page*
97
+
98
+ | | | |
99
+ |---|-----------------------------------------------------------|---|
100
+ | 0 | Introduction ..... | 1 |
101
+ | 1 | General structure ..... | 1 |
102
+ | 2 | Q-series Intelligent Network Recommendation overview..... | 1 |
103
+
104
+
105
+
106
+ # **GENERAL SERIES INTELLIGENT NETWORK RECOMMENDATION STRUCTURE**
107
+
108
+ *(revised in 1997)*
109
+
110
+ # **0 Introduction**
111
+
112
+ A block of one hundred numbers has been set aside in the Q series for the development of Intelligent Network (IN) Recommendations. This Recommendation, the first in that series, has been developed to organize the Recommendations in a meaningful way in order to assist users in locating topics of interest. It defines the structure of the Q.1200-series Recommendations and assigns blocks of numbers to the groupings of IN capabilities known as Capability Sets (CSs) and blocks of numbers for general and vocabulary sections. In addition, this Recommendation provides a structural overview of the content of each Recommendation.
113
+
114
+ This Recommendation has been developed with a long range view in mind. By assigning blocks of numbers to each capability set (CS-1, CS-2, CS-n), an organized, parallel structure across capability sets can be maintained; for example, CS-1 has been assigned the Q.121x block of numbers and CS-2 the Q.122x block of numbers.
115
+
116
+ Associated work has been documented in the I-series Recommendations. For the sake of consistency, Recommendations Q.1201, Q.1202 and Q.1203 have been assigned numbers in the I-series Recommendations (I.312, I.328 and I.329, respectively).
117
+
118
+ ## **1 General structure**
119
+
120
+ Table 1 shows the overall Q.1200-series Intelligent Network Recommendation structural distribution through the "ten" digits (1201, 1211, 1221, etc.) and the "one" digits (i.e. 1201, 1211, 1221, etc.).
121
+
122
+ **Table 1/Q.1200 – Recommendation framework structure**
123
+
124
+ | | |
125
+ |-----------------------------------------------------------------------------|-------------------------------------------|
126
+ | 00 – General | |
127
+ | 10 – CS-1 | 1 – Principles introduction |
128
+ | 20 – CS-2 | 2 – Service plane (not included for CS-1) |
129
+ | 30 – CS-3 | 3 – Global functional plane |
130
+ | 40 – CS-4 | 4 – Distributed functional plane |
131
+ | 50 – CS-5 | 5 – Physical plane |
132
+ | 60 – CS-6 | 6 – For future use |
133
+ | 70 – CS-7 | 7 – For future use |
134
+ | 80 – CS-8 | 8 – Interface Recommendation |
135
+ | 90 – Glossary | 9 – Intelligent Network user's guide |
136
+ | NOTE 1 – 1200 is assigned as for the IN Recommendation framework structure. | |
137
+ | NOTE 2 – 1290-series has been set aside for the glossary. | |
138
+
139
+ ## **2 Q-series Intelligent Network Recommendation overview**
140
+
141
+ ### **Q.1200 – General series Intelligent Network Recommendation structure**
142
+
143
+ - 0 Introduction
144
+ - 1 General structure
145
+ - 2 Q-series Intelligent Network Recommendation overview
146
+
147
+ ### **I.312/Q.1201 – Principles of Intelligent Network architecture**
148
+
149
+ - 1 Objectives, overall description
150
+ - 1.1 Motivation, objectives, scope of Intelligent Network
151
+ - 1.1.1 Motivation
152
+ - 1.1.2 Objectives of Intelligent Network
153
+ - 1.1.3 Scope of Intelligent Network
154
+ - 1.2 Definition of Intelligent Network
155
+ - 1.3 Evolution of Intelligent Network Recommendations
156
+ - 1.3.1 General considerations on the standardization process
157
+ - 1.3.2 Recommendation areas
158
+ - 1.3.3 Phased standardization and definition of capability sets
159
+ - 2 IN functional requirements
160
+ - 2.0 Introduction
161
+ - 2.1 Service requirements
162
+ - 2.1.1 Overall requirements
163
+ - 2.1.2 Service creation
164
+ - 2.1.3 Service management
165
+ - 2.1.4 Service processing
166
+ - 2.1.5 Service interworking
167
+ - 2.2 Network requirements
168
+ - 2.2.1 Overall requirements
169
+ - 2.2.2 Service creation
170
+ - 2.2.3 Service management
171
+ - 2.2.4 Network management
172
+ - 2.2.5 Service processing
173
+ - 2.2.6 Network interworking
174
+ - 3 IN architectural concept
175
+ - 3.1 IN Conceptual Model (INCM)
176
+ - 3.1.1 Service plane
177
+ - 3.1.2 Global functional plane
178
+ - 3.1.3 Distributed functional plane
179
+ - 3.1.4 Physical plane
180
+ - 3.1.5 Relationship with the 3-stage method
181
+ - 3.1.6 Service logic
182
+ - 3.1.7 Application Programming Interface (API)
183
+ - 3.1.8 Relationships among different planes
184
+ - 3.1.9 Service interaction
185
+ - 3.1.10 Service and network interworking
186
+ - 3.1.11 Management functionality
187
+ - 4 Intelligent Network (IN) long-term architecture framework
188
+ - 4.1 Introduction
189
+ - 4.2 Intelligent Network Conceptual Model
190
+ - 4.3 Architecture structure
191
+ - 4.3.1 Logical architecture
192
+ - 4.3.2 Physical architecture
193
+ - 4.3.3 Open distributed processing view
194
+ - 4.4 Service considerations
195
+ - 4.4.1 Service/service feature interaction
196
+ - 4.5 Technology basis
197
+ - 4.5.1 Broadband capabilities
198
+ - 4.5.2 Distributed processing
199
+ - 4.5.3 Open Systems Interconnection (OSI)
200
+ - 4.5.4 Object-oriented modelling
201
+ - 4.5.5 Information technology
202
+ - 4.5.6 Cooperative processing
203
+ - 4.5.7 Distributed control
204
+ - 4.5.8 Management of services and networks
205
+ - 4.5.9 Verification/validation
206
+ - 4.5.10 Artificial intelligence
207
+
208
+ ### **I.328/Q.1202 – Intelligent Network Service plane architecture**
209
+
210
+ - 1 General
211
+ - 2 Service plane architecture
212
+ - 2.0 General
213
+ - 2.1 Characterization of services and service capability requirements
214
+ - 2.2 Service plane modelling
215
+ - 2.3 Service and service feature interaction
216
+ - 2.3.1 The service and feature interaction problem
217
+ - 2.3.2 A solution: Which one?
218
+ - 2.3.3 A solution: When?
219
+ - 2.3.4 A solution: How?
220
+
221
+ Annex A – Alphabetical list of abbreviations used in this Recommendation
222
+
223
+ Annex B – A thesaurus of examples
224
+
225
+ - B.1 General
226
+ - B.2 Call Forwarding Unconditional and Terminating Key Code Screening
227
+ - B.2.1 First case
228
+ - B.2.2 Second case
229
+ - B.3 Call Forwarding Unconditional and Automatic Call Back
230
+ - B.3.1 First case
231
+ - B.3.2 Second case
232
+ - B.4 Call Forwarding Unconditional and Terminating Call Screening
233
+
234
+ ### **I.329/Q.1203 – Intelligent Network global functional plane architecture**
235
+
236
+ - 1 General
237
+ - 2 Scope of IN global functional plane architecture
238
+ - 3 References
239
+ - 4 Global functional plane modelling
240
+ - 5 Service independent building blocks
241
+ - 5.1 Definition of an SIB
242
+ - 5.2 Characteristics of an SIB
243
+ - 5.3 Data parameters for SIBs
244
+ - 5.4 Method to describe SIBs
245
+ - 5.5 Flowchart analysis
246
+ - 5.6 Interaction management
247
+ - 5.6.1 Interaction between SIBs
248
+ - 6 Basic call process
249
+ - 6.1 General
250
+ - 6.2 Basic call process functionality
251
+ - 7 Global service logic
252
+ - 7.1 General
253
+
254
+ Annex A – Alphabetical list of abbreviations used in this Recommendation
255
+
256
+ ### **Q.1204 – Intelligent Network distributed functional plane architecture**
257
+
258
+ - 1 General
259
+ - 2 Distributed functional plane model
260
+ - 2.1 Explanation of diagram
261
+ - 2.1.1 Functional entities
262
+ - 2.1.2 Relationships
263
+ - 2.3 Definition of functional entities related to IN service execution
264
+ - 2.4 Definition of IN service creation/management related functional entities
265
+
266
+ - 3 Functional entity call/service logic processing models
267
+ - 3.1 General
268
+ - 3.2 Modelling objectives/criteria
269
+ - 3.2.1 Call modelling objectives/criteria
270
+ - 3.2.2 Modelling of service logic processing objectives/criteria
271
+ - 3.3 General assumptions
272
+ - 3.3.1 Scope of functional entity call/service logic processing models
273
+ - 3.3.2 Relation to IN conceptual model
274
+ - 3.3.3 Use of functional entity call/service logic processing models
275
+ - 3.3.4 Other considerations
276
+ - 3.4 Overview of call/service logic processing related functional entities
277
+ - 3.5 Call/service logic processing functional entity models
278
+ - 4 Relationship between functional entities
279
+ - 4.1 General
280
+ - 4.2 Relationships
281
+ - 4.3 Information flows between functional entities
282
+ - 5 Mapping the global functional plane to the distributed functional plane
283
+ - 5.1 Mapping requirements
284
+ - 5.2 Relationship to IN conceptual model
285
+ - 5.3 An example of mapping some selected SIBs to functional entities
286
+ - Annex A – Example basic call state model (BCSM)
287
+ - Annex B – Object-oriented finite state machine modelling
288
+ - Annex C – Call segment model
289
+
290
+ ### **Q.1205 – Intelligent Network physical plane architecture**
291
+
292
+ - 1 General
293
+ - 2 Requirements and assumptions
294
+ - 2.1 Requirements
295
+ - 2.2 Assumptions
296
+ - 3 Physical entities (PEs)
297
+ - 4 Mapping the distributed functional plane to the physical plane
298
+ - 4.1 Mapping of functional entities to physical entities
299
+ - 4.2 Selection of underlying protocol platforms
300
+ - 5 User interfaces
301
+
302
+ ### **Q.1208 – General aspects of the Intelligent Network application protocol**
303
+
304
+ - 1 Introduction
305
+ - 2 Background
306
+ - 3 Definition methodology
307
+ - 4 Evolutionary requirements
308
+
309
+ ### **Q.1210 – Q.1210-series Intelligent Network Recommendation structure**
310
+
311
+ - 1 General Q.1200-series structure
312
+ - 2 Q.121x-series Intelligent Network Recommendation overview
313
+
314
+ ### **Q.1220 – Q.1220-series Intelligent Network Capability Set 2 Recommendation structure**
315
+
316
+ - 0 Introduction
317
+ - 1 General Q.1200-series structure
318
+ - 2 Q.121x-series Intelligent Network Recommendation overview
319
+
320
+ ### **Q.1230 – Q.1230-series Intelligent Network Capability Set 3**
321
+
322
+ - 1 General Q.1200-series structure
323
+ - 2 Q.123x-series Intelligent Network Recommendation overview
324
+
325
+ ### **Q.1290 – Glossary of terms used in the definition of Intelligent Networks**
326
+
327
+ - 1 General
328
+ - 1.1 Introduction
329
+ - 1.2 Conventions
330
+ - 2 Terms and definitions (listed alphabetically)
331
+
332
+ Annex A – Acronyms
333
+
334
+
335
+
336
+ # ITU-T RECOMMENDATIONS SERIES
337
+
338
+ | | |
339
+ |-----------------|--------------------------------------------------------------------------------------------------------------------------------|
340
+ | Series A | Organization of the work of the ITU-T |
341
+ | Series B | Means of expression: definitions, symbols, classification |
342
+ | Series C | General telecommunication statistics |
343
+ | Series D | General tariff principles |
344
+ | Series E | Overall network operation, telephone service, service operation and human factors |
345
+ | Series F | Non-telephone telecommunication services |
346
+ | Series G | Transmission systems and media, digital systems and networks |
347
+ | Series H | Audiovisual and multimedia systems |
348
+ | Series I | Integrated services digital network |
349
+ | Series J | Transmission of television, sound programme and other multimedia signals |
350
+ | Series K | Protection against interference |
351
+ | Series L | Construction, installation and protection of cables and other elements of outside plant |
352
+ | Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
353
+ | Series N | Maintenance: international sound programme and television transmission circuits |
354
+ | Series O | Specifications of measuring equipment |
355
+ | Series P | Telephone transmission quality, telephone installations, local line networks |
356
+ | <b>Series Q</b> | <b>Switching and signalling</b> |
357
+ | Series R | Telegraph transmission |
358
+ | Series S | Telegraph services terminal equipment |
359
+ | Series T | Terminals for telematic services |
360
+ | Series U | Telegraph switching |
361
+ | Series V | Data communication over the telephone network |
362
+ | Series X | Data networks and open system communications |
363
+ | Series Y | Global information infrastructure |
364
+ | Series Z | Programming languages |
marked/Q/T-REC-Q.1208-199709-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: c315972c25456ec61dce423cf7bdb17e9326e1a8465e66d166c5dfadaf26aa35
  • Pointer size: 129 Bytes
  • Size of remote file: 8.27 kB
marked/Q/T-REC-Q.1208-199709-I_PDF-E/d0abac95583b52a3b35f74a215567334_img.jpg ADDED

Git LFS Details

  • SHA256: 03f9d45627b625858f20174dae594354465ab0cf5f00d1560e2de415f24ba258
  • Pointer size: 130 Bytes
  • Size of remote file: 21.6 kB
marked/Q/T-REC-Q.1208-199709-I_PDF-E/raw.md ADDED
@@ -0,0 +1,196 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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
+ **Q.1208**
18
+
19
+ (09/97)
20
+
21
+ SERIES Q: SWITCHING AND SIGNALLING
22
+
23
+ Intelligent Network
24
+
25
+ # --- **General aspects of the Intelligent Network Application protocol**
26
+
27
+ ITU-T Recommendation Q.1208
28
+
29
+ (Previously CCITT Recommendation)
30
+
31
+ ---
32
+
33
+ ## ITU-T Q-SERIES RECOMMENDATIONS
34
+
35
+ ## **SWITCHING AND SIGNALLING**
36
+
37
+ | | |
38
+ |----------------------------------------------------------|----------------------|
39
+ | SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
40
+ | INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
41
+ | FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
42
+ | CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
43
+ | SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 | Q.120–Q.249 |
44
+ | SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
45
+ | SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
46
+ | SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
47
+ | DIGITAL EXCHANGES | Q.500–Q.599 |
48
+ | INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
49
+ | SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.849 |
50
+ | DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
51
+ | PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
52
+ | INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
53
+ | <b>INTELLIGENT NETWORK</b> | <b>Q.1200–Q.1999</b> |
54
+ | BROADBAND ISDN | Q.2000–Q.2999 |
55
+
56
+ *For further details, please refer to ITU-T List of Recommendations.*
57
+
58
+ ## **ITU-T RECOMMENDATION Q.1208**
59
+
60
+ # **GENERAL ASPECTS OF THE INTELLIGENT NETWORK APPLICATION PROTOCOL**
61
+
62
+ ## **Summary**
63
+
64
+ The objective of this Recommendation is to specify the definition methodology to be applied to the Intelligent Network application protocol Recommendations defined in specific capability sets. This Recommendation is not expected to change greatly in future versions with the possible exception of additional specification mechanisms.
65
+
66
+ Associated standardization work is contained in all of the Q.12xx IN Recommendations and more particularly in the Q.12x8 INAP Recommendations.
67
+
68
+ ### **Source**
69
+
70
+ ITU-T Recommendation Q.1208 was revised by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 12th of September 1997.
71
+
72
+ ## FOREWORD
73
+
74
+ 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.
75
+
76
+ 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.
77
+
78
+ The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
79
+
80
+ 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.
81
+
82
+ ## NOTE
83
+
84
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
85
+
86
+ ## INTELLECTUAL PROPERTY RIGHTS
87
+
88
+ 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.
89
+
90
+ 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.
91
+
92
+ © ITU 1998
93
+
94
+ 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.
95
+
96
+ ## CONTENTS
97
+
98
+ | | <i>Page</i> |
99
+ |----------------------------------------------------------------------|-------------|
100
+ | 1 Introduction ..... | 1 |
101
+ | 2 Background..... | 1 |
102
+ | 3 Definition methodology..... | 1 |
103
+ | 4 Evolutionary requirements ..... | 1 |
104
+ | 4.1 Rules for adding new parameters to INAP..... | 2 |
105
+ | 4.2 Rules/guidelines for development of IN call party handling ..... | 2 |
106
+
107
+
108
+
109
+ # **GENERAL ASPECTS OF THE INTELLIGENT NETWORK APPLICATION PROTOCOL**
110
+
111
+ *(revised in 1997)*
112
+
113
+ ## **1 Introduction**
114
+
115
+ This Recommendation defines the general aspects of the interfaces and protocols. For the detailed protocols and interfaces supported in each capability set, refer to the Q.12x8 Recommendation for that capability set.
116
+
117
+ ## **2 Background**
118
+
119
+ All the work on interface specifications is based on the IN Functional Model (INFM). Each capability set will support a number of the interfaces defined in that model appropriate to the requirements placed upon that capability set.
120
+
121
+ ## **3 Definition methodology**
122
+
123
+ The definition of the protocol can be split into three sections:
124
+
125
+ - the definition of the service which the protocol provides (primitives etc.);
126
+ - the definition of the operations transferred between entities;
127
+ - the definition of the actions taken at each entity as a result of performing the operations.
128
+
129
+ The primitives are defined in a tabular notation and may be omitted. The operation definitions are in Abstract Syntax Notation 1 (ASN.1, see Recommendation X.680). The actions are defined in terms of state transition diagrams. Other definition techniques may be used in future capability sets to supplement or replace these if this seems appropriate.
130
+
131
+ The INAP is a ROSE user protocol (see Recommendation X.219/X.229). The ROSE protocol is contained within the component sublayer of TCAP (see Recommendations Q.771 to Q.775) and DSS 1 (Recommendation Q.932). At present the ROSE APDUs are conveyed in transaction sublayer messages in SS No. 7 and in the Q.931 REGISTER, FACILITY and call control messages in DSS 1. Other supporting protocols may be added at a later date.
132
+
133
+ The INAP (as a ROSE user) and the ROSE protocol have been specified using ASN.1. At present, the only standardized way to encode the resulting PDUs is the basic encoding rules (see Recommendation X.690). The protocols should be defined in such a way that the functional entities defined in the INFM may be mapped into physical entities in any way that operators and manufacturers desire.
134
+
135
+ ## **4 Evolutionary requirements**
136
+
137
+ The use of the application context negotiation mechanism (as defined in the Q.77x-Series Recommendations) allows the two communicating entities to identify exactly what their capabilities (and therefore the capabilities required on the interface) are. Where possible, this should be used to allow evolution through capability sets.
138
+
139
+ Capability sets should always be defined as supersets of previous capability sets to ensure successful interworking with previous capability sets is possible. This may not apply where errors are found in previous capability sets.
140
+
141
+ ### 4.1 Rules for adding new parameters to INAP
142
+
143
+ The objective of the rules is to achieve alignment and to avoid clashes between ITU-T CS-x and implementations based upon the regional standards that emanated from earlier versions of CS-x Recommendations. For network-specific parameters which are included in the Recommendations, context specific tags will be used. Rules for context specific tagging are:
144
+
145
+ - 1) Originally defined Q.12x8 tag values shall be maintained in subsequent capability sets.
146
+ - 2) In case parameters are removed from a defined Q.12x8, the corresponding tag values remain reserved.
147
+ - 3) In case a regional defined parameter is adopted by the ITU-T, the regional defined tag values are also considered.
148
+ - 4) The following structure for tag value allocation shall be used:
149
+
150
+ ![Diagram showing tag value allocation for INAP parameters. It is divided into three sections: 'Q.1218 parameters' (tags 0, 1, 2, ..., x), 'Regional standard adopted parameters' (tags ..., 30), and 'Future Capability Set use' (tags 31, ..., n ...). Arrows indicate the flow and scope of each section.](d0abac95583b52a3b35f74a215567334_img.jpg)
151
+
152
+ | | | | | | | | | | |
153
+ |-------------------|---|---|-----|-----------------------------------------|-----|----|---------------------------|-----------|--|
154
+ | Q.1218 parameters | | | | Regional standard<br>adopted parameters | | | Future Capability Set use | | |
155
+ | → | | | | ← | | | → | | |
156
+ | 0 | 1 | 2 | ... | x | ... | 30 | 31 | ... n ... | |
157
+
158
+ Diagram showing tag value allocation for INAP parameters. It is divided into three sections: 'Q.1218 parameters' (tags 0, 1, 2, ..., x), 'Regional standard adopted parameters' (tags ..., 30), and 'Future Capability Set use' (tags 31, ..., n ...). Arrows indicate the flow and scope of each section.
159
+
160
+ When a new data type is to be added to an existing sequence of data types with an extension marker (...) and the new data type can be ignored when the receiving system is an implementation of an older INAP version, the new data type shall be added at the end of the sequence, after the extension marker. When the new data type cannot be ignored, the new data type shall be positioned before the extension marker, before the last mandatory parameter. The ITU-T shall allocate tag values starting from 0 upwards (as shown above). Regional bodies may then use tag values from 30 downwards for their additions to the Q.12x8 Recommendation. If the ITU-T adopts a parameter for INAP from such a regional standard, the tag value will also be adopted, in order to ensure compatibility. When all tag values from 0 to 30 have been allocated between Q.12x8 and regional standards, tag allocation by the ITU-T will continue from 31 upwards.
161
+
162
+ ### 4.2 Rules/guidelines for development of IN call party handling
163
+
164
+ The information used to synchronize the SSF and SCF with the Connection View State should be as generic as possible, to allow flexibility. Allowing different operators to support differing transitions and priorities for feature interactions, thereby enabling competition. The IFs and IEs should specify the modified use of Legs and Call Segments by LegID and Call Segment ID. This also applies to commands initiated by the SCF, both bidirectional (class 1) and unidirectional (class 2) messages.
165
+
166
+ These requirements also provide a flexible view to evolve to the IN/B-ISDN requirements being developed by the ITU-T, where the addition and removal of parties and bearers should be completely flexible.
167
+
168
+ ## ITU-T RECOMMENDATIONS SERIES
169
+
170
+ | | |
171
+ |-----------------|--------------------------------------------------------------------------------------------------------------------------------|
172
+ | Series A | Organization of the work of the ITU-T |
173
+ | Series B | Means of expression: definitions, symbols, classification |
174
+ | Series C | General telecommunication statistics |
175
+ | Series D | General tariff principles |
176
+ | Series E | Overall network operation, telephone service, service operation and human factors |
177
+ | Series F | Non-telephone telecommunication services |
178
+ | Series G | Transmission systems and media, digital systems and networks |
179
+ | Series H | Audiovisual and multimedia systems |
180
+ | Series I | Integrated services digital network |
181
+ | Series J | Transmission of television, sound programme and other multimedia signals |
182
+ | Series K | Protection against interference |
183
+ | Series L | Construction, installation and protection of cables and other elements of outside plant |
184
+ | Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
185
+ | Series N | Maintenance: international sound programme and television transmission circuits |
186
+ | Series O | Specifications of measuring equipment |
187
+ | Series P | Telephone transmission quality, telephone installations, local line networks |
188
+ | <b>Series Q</b> | <b>Switching and signalling</b> |
189
+ | Series R | Telegraph transmission |
190
+ | Series S | Telegraph services terminal equipment |
191
+ | Series T | Terminals for telematic services |
192
+ | Series U | Telegraph switching |
193
+ | Series V | Data communication over the telephone network |
194
+ | Series X | Data networks and open system communications |
195
+ | Series Y | Global information infrastructure |
196
+ | Series Z | Programming languages |
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/042af54276c75e7b7b48a3af1f0a84e5_img.jpg ADDED

Git LFS Details

  • SHA256: 4115e66089ed2b8eb64ed2a08f3d2b358a51f5ecaa02f3a5bdf48b9bf8331030
  • Pointer size: 129 Bytes
  • Size of remote file: 9.55 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg ADDED

Git LFS Details

  • SHA256: a0b8de0bde776fa456c77cb46fc61863ecc70eb4f52969ac2390c080064b52f5
  • Pointer size: 131 Bytes
  • Size of remote file: 144 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg ADDED

Git LFS Details

  • SHA256: d7680f255e63a44b5b55843947e08228e3e97ed2ecf159c9451f139edaa3ee07
  • Pointer size: 129 Bytes
  • Size of remote file: 9.87 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/212c50c4e3d043c989037a01e13c1a98_img.jpg ADDED

Git LFS Details

  • SHA256: a99f5b2c7f3efb5e307723014026cd5c0418d127fdf93ff3753cf2dba7e6ee9f
  • Pointer size: 131 Bytes
  • Size of remote file: 150 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg ADDED

Git LFS Details

  • SHA256: ed50eb7b97340444a3bbc7ca6dc0235ad3b1554fa6a6707292697e99b9a1b144
  • Pointer size: 130 Bytes
  • Size of remote file: 10.1 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 4e646b535623af01c7c140e1a16eb3827d9384182b9f72383794dfee880e853f
  • Pointer size: 129 Bytes
  • Size of remote file: 8.21 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg ADDED

Git LFS Details

  • SHA256: 2fd6518b07322bb6a6aedb90052ca4297230c2632d986126a939a1ee76738259
  • Pointer size: 131 Bytes
  • Size of remote file: 156 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg ADDED

Git LFS Details

  • SHA256: 633a65ba795b6e76cab2845f75263ea43323f139ad7a8b22f2fb99a04fbe8ea8
  • Pointer size: 131 Bytes
  • Size of remote file: 158 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/40ebe9179df298f1b6d76822f28d90aa_img.jpg ADDED

Git LFS Details

  • SHA256: 511a2d92b566d26680a510de39a97bf222f98128c7641463f8a7d409dbb6239b
  • Pointer size: 130 Bytes
  • Size of remote file: 12.3 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/575d7d345b3ec04393bb2ec720ebabca_img.jpg ADDED

Git LFS Details

  • SHA256: d8c0222e9213502415019f8de96927feeeef10f6963e863654c803334560a329
  • Pointer size: 131 Bytes
  • Size of remote file: 181 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/838c31609fac483fa2c01c7896a2fd6d_img.jpg ADDED

Git LFS Details

  • SHA256: f87e20f1bfc4ced0238cb692d7e219e0d8a2f3f2d59c5d478681a4906240d7df
  • Pointer size: 131 Bytes
  • Size of remote file: 207 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg ADDED

Git LFS Details

  • SHA256: 4b64bfb9ab1f23394a626534a123ccd2eba93dbad18e76e876003a0b08cfc6b0
  • Pointer size: 129 Bytes
  • Size of remote file: 9.51 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg ADDED

Git LFS Details

  • SHA256: 1fa684100eb062630d216e4a49a9da8d7c572fb6236722f73535e856d9b6b96e
  • Pointer size: 130 Bytes
  • Size of remote file: 71.3 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9cd85f266cdb1fb3ad544eb3dd3bd5e4_img.jpg ADDED

Git LFS Details

  • SHA256: e46eb9b1020fabaaeeac6725e8bdd8d800afc672fe5b7f8f34c8bf3d7b3e4d3c
  • Pointer size: 131 Bytes
  • Size of remote file: 173 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg ADDED

Git LFS Details

  • SHA256: 53a3399cc93beae4ff5c873d0d8de3c75efec362fad8ca9aa2654ab5b2b3b9ad
  • Pointer size: 131 Bytes
  • Size of remote file: 216 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg ADDED

Git LFS Details

  • SHA256: 3258a1f81ccb7e389f3b77bca4af9d4aed0cca2b25a945971f14da4799ac4486
  • Pointer size: 131 Bytes
  • Size of remote file: 162 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg ADDED

Git LFS Details

  • SHA256: 0c1c5655515fb197f85c96a57d2b6227dbc2f4d3daad5d4c7edf56e7f4271cfc
  • Pointer size: 131 Bytes
  • Size of remote file: 232 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg ADDED

Git LFS Details

  • SHA256: 5f964f3e15c4bbf6534f862f8a3f4ed2635a25cc0f3906545e0ab2d6ae599578
  • Pointer size: 129 Bytes
  • Size of remote file: 9.8 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/feae5a5b6e128162dbced0860fd97b9b_img.jpg ADDED

Git LFS Details

  • SHA256: cdc434f97f6d49a9f31105466540b8825a14a9b18e2c7d2db08e092e98464437
  • Pointer size: 131 Bytes
  • Size of remote file: 152 kB
marked/Q/T-REC-Q.140-Q.180-198811-I_PDF-E/raw.md ADDED
The diff for this file is too large to render. See raw diff
 
marked/Q/T-REC-Q.1702-200206-I_PDF-E/raw.md ADDED
@@ -0,0 +1,376 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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
+ **Q.1702**
18
+
19
+ (06/2002)
20
+
21
+ SERIES Q: SWITCHING AND SIGNALLING
22
+
23
+ Signalling requirements and protocols for IMT-2000
24
+
25
+ ---
26
+
27
+ **Long-term vision of network aspects for
28
+ systems beyond IMT-2000**
29
+
30
+ ITU-T Recommendation Q.1702
31
+
32
+ ---
33
+
34
+ # ITU-T Q-SERIES RECOMMENDATIONS
35
+
36
+ ## SWITCHING AND SIGNALLING
37
+
38
+ | | |
39
+ |--------------------------------------------------------------------------------|----------------------|
40
+ | SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE | Q.1–Q.3 |
41
+ | INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING | Q.4–Q.59 |
42
+ | FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN | Q.60–Q.99 |
43
+ | CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS | Q.100–Q.119 |
44
+ | SPECIFICATIONS OF SIGNALLING SYSTEM No. 4 | Q.120–Q.139 |
45
+ | SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 | Q.140–Q.199 |
46
+ | SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 | Q.250–Q.309 |
47
+ | SPECIFICATIONS OF SIGNALLING SYSTEM R1 | Q.310–Q.399 |
48
+ | SPECIFICATIONS OF SIGNALLING SYSTEM R2 | Q.400–Q.499 |
49
+ | DIGITAL EXCHANGES | Q.500–Q.599 |
50
+ | INTERWORKING OF SIGNALLING SYSTEMS | Q.600–Q.699 |
51
+ | SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 | Q.700–Q.799 |
52
+ | Q3 INTERFACE | Q.800–Q.849 |
53
+ | DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 | Q.850–Q.999 |
54
+ | PUBLIC LAND MOBILE NETWORK | Q.1000–Q.1099 |
55
+ | INTERWORKING WITH SATELLITE MOBILE SYSTEMS | Q.1100–Q.1199 |
56
+ | INTELLIGENT NETWORK | Q.1200–Q.1699 |
57
+ | <b>SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000</b> | <b>Q.1700–Q.1799</b> |
58
+ | SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) | Q.1900–Q.1999 |
59
+ | BROADBAND ISDN | Q.2000–Q.2999 |
60
+
61
+ *For further details, please refer to the list of ITU-T Recommendations.*
62
+
63
+ # **ITU-T Recommendation Q.1702**
64
+
65
+ # **Long-term vision of network aspects for systems beyond IMT-2000**
66
+
67
+ ## **Summary**
68
+
69
+ This Recommendation addresses the envisaged network environment, network design objectives, and architecture concepts of Systems Beyond IMT-2000. This Recommendation, together with a draft ITU-R Recommendation which covers the radio aspects, form the ITU long-term vision for Systems Beyond IMT-2000.
70
+
71
+ ## **Source**
72
+
73
+ ITU-T Recommendation Q.1702 was prepared by ITU-T SSG (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 June 2002.
74
+
75
+ ## **Keywords**
76
+
77
+ Long-Term Vision, Network Aspects, Systems Beyond IMT-2000
78
+
79
+ ## FOREWORD
80
+
81
+ The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. 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.
82
+
83
+ The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
84
+
85
+ The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
86
+
87
+ 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.
88
+
89
+ ## NOTE
90
+
91
+ In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
92
+
93
+ ## INTELLECTUAL PROPERTY RIGHTS
94
+
95
+ ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. 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.
96
+
97
+ As of the date of approval of this Recommendation, 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.
98
+
99
+ © ITU 2002
100
+
101
+ All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
102
+
103
+ ## CONTENTS
104
+
105
+ ###### Page
106
+
107
+ | | | |
108
+ |-----|-------------------------------------------------------------|---|
109
+ | 1 | Scope ..... | 1 |
110
+ | 2 | References..... | 1 |
111
+ | 3 | Definitions ..... | 1 |
112
+ | 4 | Abbreviations..... | 2 |
113
+ | 5 | Envisaged network environment around the year 2010 ..... | 2 |
114
+ | 5.1 | Market trends..... | 2 |
115
+ | 5.2 | Technology trends ..... | 3 |
116
+ | 6 | Key long-term network design objectives ..... | 3 |
117
+ | 6.1 | Broadband and multiple bearer service capability ..... | 3 |
118
+ | 6.2 | Service expandability and application service support ..... | 4 |
119
+ | 6.3 | Security support..... | 4 |
120
+ | 6.4 | User platform support..... | 4 |
121
+ | 6.5 | High performance and system efficiency ..... | 4 |
122
+ | 6.6 | System flexibility..... | 4 |
123
+ | 6.7 | System scalability..... | 6 |
124
+ | 6.8 | System interoperability..... | 6 |
125
+ | 6.9 | System robustness ..... | 6 |
126
+ | 7 | Long-term network architecture concepts ..... | 6 |
127
+
128
+ # **Introduction**
129
+
130
+ The ITU-T and ITU-R have collaborated to develop a single ITU vision of Systems Beyond IMT-2000 targeted for initial deployment around the year 2010, subject to market considerations. This common ITU Vision is the nucleus and foundation for the development of related Recommendations in both the Telecommunication Standardization Sector and the Radiocommunication Sector. This relationship is responsive to ITU-T Resolution 38 and ITU-R Resolution 50 which require the development of roadmaps on IMT-2000 in an independent, but well-coordinated manner.
131
+
132
+ There is a definite trend towards integration of access networks (e.g., cellular, wireless local area network, personal area wireless network, satellite systems, and Internet.) Based on this trend, it is envisioned that the network environment of Systems Beyond IMT-2000 will consist of packet-based network infrastructure offering a plethora of converged services.
133
+
134
+ # Long-term vision of network aspects for systems beyond IMT-2000
135
+
136
+ # 1 Scope
137
+
138
+ The scope of this Recommendation is to provide a long-term vision (around the year 2010) for the network aspects of Systems Beyond IMT-2000. The further development of existing IMT-2000 systems is not addressed by this Recommendation.
139
+
140
+ # 2 References
141
+
142
+ 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; 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.
143
+
144
+ - [1] ITU-T Recommendation X.233 (1997) *Information technology – Protocol for providing the connectionless-mode network service: Protocol specification.*
145
+ - [2] ITU-T Recommendation I.113 (1997) *Vocabulary of terms for broadband aspects of ISDN.*
146
+ - [3] ITU-T Recommendation H.323 (2000) *Packet-based multimedia communications systems.*
147
+ - [4] ITU-R Recommendation M.687-2 (1997) *International Mobile Telecommunications-2000 (IMT-2000).*
148
+ - [5] ITU-R Recommendation M.1311 (1997) *Framework for modularity and radio commonality within IMT-2000.*
149
+
150
+ # 3 Definitions
151
+
152
+ This Recommendation defines the following terms:
153
+
154
+ **3.1 converged services:** The integration of Internet, multimedia, e-mail, presence, instant messaging, m-commerce, etc., services with voice service.
155
+
156
+ **3.2 mobility:** The ability to provide services irrespective of changes that may occur by user/terminal's activities.
157
+
158
+ **3.3 multicast:** Data transmission to one or more destinations in a selected group in a single service invocation. [1]
159
+
160
+ **3.4 multimedia:** The combination of multiple forms of media such as audio, video, text, graphics, fax, and telephony in the communication of information.
161
+
162
+ **3.5 multimedia service:** A service in which the interchanged information consists of more than one type, such as text, graphics, sound, image and video. [2]
163
+
164
+ **3.6 seamless service:** Seamless Service will prevent users from experiencing any service disruptions while maintaining mobility or portability.
165
+
166
+ **3.7 session continuity:** The ability of the user to maintain continuity of ongoing sessions while changing between terminal devices and across various access and core networks. For example, the user of a mobile terminal may wish to switch from his mobile equipment attached to a wireless network to a laptop connected to a wire-line or Digital Subscriber Line connection. This should be
167
+
168
+ supported without any session discontinuity.
169
+
170
+ **3.8 unicast:** A process of transmitting messages from one source to one destination. [3]
171
+
172
+ **3.9 virtual reality services:** The ability for users to access the sights and sounds of remotely located complex systems in real-time.
173
+
174
+ # 4 Abbreviations
175
+
176
+ This Recommendation uses the following abbreviations:
177
+
178
+ | | |
179
+ |-------|----------------------------------------------------------|
180
+ | API | Application Programming Interface |
181
+ | ASP | Application Service Provider |
182
+ | IMT | International Mobile Telecommunications |
183
+ | IP | Internet Protocol |
184
+ | Mbps | Mega bits per second |
185
+ | OAM&P | Operations, Administration, Maintenance and Provisioning |
186
+ | PAN | Personal Access Network |
187
+ | QoS | Quality of Service |
188
+ | WLAN | Wireless Local Area Network |
189
+
190
+ # 5 Envisaged network environment around the year 2010
191
+
192
+ The following network environment around the year 2010 is envisaged to facilitate the identification of future needs of users, service capabilities, and network capabilities at that time.
193
+
194
+ ## 5.1 Market trends
195
+
196
+ - High-speed data connection is a norm in accessing multimedia services and Internet services, even in the wireless environment, due to additional spectrum, efficient spectrum utilization, and advanced radio technologies. Because of these advancements, "Virtual Reality Services" becomes widely available.
197
+ - The core network is fully Internet Protocol (IP)-based and service provisioning is distributed around the core network. Wireless access is just one of the access methods to the IP-based core network, services, and applications.
198
+ - There exist many complementary wireless networks for voice and data applications in addition to International Mobile Telecommunications-2000 (IMT-2000) terrestrial and satellite-based systems. Some examples are Bluetooth and Wireless Local Area Network (WLAN). A limited integration among these wireless networks and IMT-2000 systems exists.
199
+ - Digital TV with data service capability is ubiquitous.
200
+ - The number of users around the year 2010 could grow to more than 1700 million wireless subscribers with a great number of them having several different terminals for communications. A majority of the user populations is computer proficient and quick to adopt of advanced technologies to enhance quality of life and productivity.
201
+ - There exist Application Service Providers (ASPs) utilizing mobile networks as a means to offer unique services taking advantage of mobile terminal capabilities and location information.
202
+ - Large numbers of users move internationally wanting to use their services anytime anywhere with their personal terminals.
203
+
204
+ - Services are the driver: the role of technology is to enable provision of services (and capacities) that the users are willing to pay for.
205
+
206
+ ## 5.2 Technology trends
207
+
208
+ - Software-defined radio technology has become a main element in the wireless infrastructure and handset implementations. Because of this technology, new and advanced radio technologies are easily introduced and deployed by the Network operators and Service providers to differentiate their services.
209
+ - Mobile terminals may form a closed network, or an *ad hoc* network, which enables direct communications between them. Transmission speed could be independent between an uplink and a downlink. Systems Beyond IMT-2000 are expected to act as platforms to effectively deliver traffic within and between the *ad hoc* networks and to offer additional values to them, such as advanced mobility management techniques.
210
+ - Mobility management will be more than supporting higher speed objects such as vehicles. It will be needed to support applications with very large IP multimedia traffic needs, and with diversified communications including person-to-person, machine-to-machine, machine-to-person and vice versa.
211
+ - The concept of seamless services will be extended beyond handover and roaming services.
212
+ - Diverse end-users' individual needs will require flexibility to deal with their preferences or contexts.
213
+ - The following network security environment around the year 2010 is envisaged:
214
+ - Highly efficient security mechanisms are available in a multimedia environment to process high-speed and high volume information flows.
215
+ - There exist user transparent access authentication and authorization mechanisms to provide protection in different access environments.
216
+ - The security infrastructure is supported across service providers.
217
+ - The capacity of security servers is scaled to provide service for massive network usage.
218
+ - Seamless security is available to maintain the same security strength with unreduced performance in handover procedures.
219
+
220
+ # 6 Key long-term network design objectives
221
+
222
+ The set of network capabilities existing for current IMT-2000 Family Member Systems should be included for Systems Beyond IMT-2000, as needed. The key long-term network design objectives for Systems Beyond IMT-2000 are listed in the following subclauses.
223
+
224
+ ## 6.1 Broadband and multiple bearer service capability
225
+
226
+ - Access is based on advanced radio access technologies that can enable transmission speeds well beyond the current IMT-2000 radio access target speeds of 2 Mega bits per second (Mbps).
227
+ - Access support includes the ability to handle the diverse Quality of Service (QoS) needs of future applications, including considerations for:
228
+ - non-real-time / best effort service,
229
+ - quasi-real-time (such as streaming) service, and
230
+ - real-time service (such as voice and video telephony)
231
+ - Cooperation with broadcast networks (hybrid networks) is included to open up new applications (e.g., navigation, traffic information, interactive multimedia services.)
232
+
233
+ ## 6.2 Service expandability and application service support
234
+
235
+ - Encourages appearances of diversified ASPs by supporting their services and offering additional values to them.
236
+ - Provides multiple service combination capabilities with appropriate mechanisms to handle service interaction and service invocation.
237
+ - Traditional telecommunications service invoking methods are mostly based on service Application Programming Interface (API) and its capabilities. In service provisioning components, the objective is changed to provide flexible service provisioning based on trigger objects, which will enable automatic interaction and invoking of a series of service logic instances that might be fully distributed in different elements.
238
+ - Service interactions will support variable exchange of information element types.
239
+ - Service combinations may be created dynamically, based on a user's profile/situation selections that best fit the user's present usage environment. Users can also build a situation profile in a real-time fashion.
240
+ - The service combination capability should support backward compatibility with existing service platforms.
241
+ - Supports modularized service control and open service architecture.
242
+ - Simplifies service expansion and dynamic creation of multi-facet services at session level.
243
+ - Supports flexibility for adoption of new services.
244
+ - Provides seamless service capabilities across networks.
245
+
246
+ ## 6.3 Security support
247
+
248
+ Provides seamless security protection in Systems Beyond IMT-2000 networks.
249
+
250
+ ## 6.4 User platform support
251
+
252
+ - Mobile users may form a closed *ad hoc* network and communicate directly with each other within that *ad hoc* network. In addition, these users may also wish to communicate normally for conventional communication. Such access requirements must be supported.
253
+ - A group of users may move collectively with respect to a core network (e.g., users in a train, aeroplane, ship, etc.) Such a group may be open or closed. Systems beyond IMT-2000 should accommodate the access requirements of such users. [4]
254
+ - User platforms should provide a natural communication-oriented man-machine interface.
255
+
256
+ ## 6.5 High performance and system efficiency
257
+
258
+ - Efficient handling of very large IP multimedia traffic with various predefined service parameters.
259
+ - Support of a wide range of traffic ratios within the network, including unicast, multicast, broadcast and bursty traffic.
260
+ - Distributing service provisioning according to provider's resource control policy.
261
+
262
+ ## 6.6 System flexibility
263
+
264
+ - Support Moving Networks:
265
+ - A Moving Network is a network that can move in the same manner as a terminal in mobile systems. For example, a Moving Network could be in a train, ship or aeroplane, etc.
266
+ - Accommodate diverse access technologies/schemes.
267
+
268
+ - A key long-term network design objective for Systems Beyond IMT-2000 should be its flexibility to accommodate diverse access technologies/schemes.
269
+ - Future mobile devices are expected to support numerous access technologies (including a variety of wireless and/or wire-line choices.) A key network design goal should be to facilitate a judicious choice of appropriate access technology for a particular usage environment. The choice should be based on:
270
+ - a) availability of access technologies at the mobile user location,
271
+ - b) speed and QoS requirements of the user application,
272
+ - c) cost of using the access technology, etc.
273
+ - Separate control and transport functions.
274
+ - Control functions in the IP-based network platform should be open to support various existing and future evolution signalling systems, and its function will be more focused on signalling processing.
275
+ - Transport functions should fully utilize IP transport capability to direct user traffic flows to their proper destinations.
276
+ - The interface between control and transport functions should be open and standardized.
277
+ - When the control and transport functions are implemented in the same physical equipment, the interface(s) between them still should be opened.
278
+ - Facilitate support of multiple switching control methods, signalling at different layers and their combinations.
279
+ - Switching components in the IP-based network platform may provide multiple switching control methods, and may also provide interoperation among these methods.
280
+ - Switching control methods may be implemented according to their service support requirements, and thus, may be functioning at different internetworking layers.
281
+ - The usage of IP transport for various switching control signalling should be used according to service requirements.
282
+ - Support open interface for roaming and handover among various networks.
283
+ - Automatically manage the access means (including both wired access and wireless access) based on user defined criteria such as cost, speed, QoS, privacy, applications, etc.
284
+ - Have flexible, efficient, and integrated mobility management, i.e., flexibility to support advanced mobility management schemes including:
285
+ - Location Management:
286
+ - Location Registration;
287
+ - Paging.
288
+ - Routing Management:
289
+ - Handover.
290
+ - Session Continuity:
291
+ - Seamless Session Transfer;
292
+ - Diversity Handover across access and core networks;
293
+ - Having a flexible, efficient, and integrated mobility management, i.e., flexibility to support advanced mobility management.
294
+ - Support an efficient and adaptive combination of location registration and IP paging functions.
295
+ - Support dynamic network capacity changes.
296
+
297
+ ## 6.7 System scalability
298
+
299
+ Systems Beyond IMT-2000 are expected to handle very large amounts of multimedia traffic to/from a large number of mobile users. The multimedia applications run by the mobile users will have diverse traffic and performance/QoS requirements. Advanced mobility management techniques are needed to handle the QoS requirements (e.g., satisfying QoS requirements of a mobile application during a sequence of handovers.) The system must also take into consideration all the access technology choices the user may have in a particular network environment. Advanced mobility management schemes are needed to handle multicast and broadcast requirements of geographically dispersed mobile multimedia users.
300
+
301
+ ## 6.8 System interoperability
302
+
303
+ - Support global standards, e.g., standardized interfaces between networks.
304
+ - Effective and user-friendly Operations, Administration, Maintenance and Provisioning (OAM&P) facilities.
305
+ - Interoperability with existing third generation mobile networks. Interoperability in this case means the availability of well-defined gateway points and functions between both networks.
306
+ - Integration/inter-operation with alternative networks, e.g., a Personal Access Network (PAN), a WLAN.
307
+
308
+ ## 6.9 System robustness
309
+
310
+ Provide network security among heterogeneous inter-connected networks. The security objectives shall include the following aspects:
311
+
312
+ - Comprehensive and cross-provider security infrastructure support.
313
+ - Well-defined and conducted routine system risk analysis.
314
+ - Robust system intrusion monitoring and response system to control damage.
315
+ - Low overhead security protocols to accommodate wireless bandwidth limitation.
316
+ - Provide seamless security across heterogeneous access technologies.
317
+
318
+ # 7 Long-term network architecture concepts
319
+
320
+ The network part of Systems Beyond IMT-2000 will be flexible, versatile and new services will be easy-to-deploy. Systems Beyond IMT-2000 are likely to be realized according to the following general principles:
321
+
322
+ - Network architecture based on IP technology;
323
+ - Modular construction using expandable components; and
324
+ - Open interfaces between various systems.
325
+
326
+ An IP-based network concept is likely to be used for future development and standardization efforts.
327
+
328
+ The high-level architecture of Systems Beyond IMT-2000 may be envisaged to include user platform, IP-based network platform, and service provisioning platform. The IP-based network platform includes two types of components: access network components and core network components.
329
+
330
+ The user platform allows a user to gain access to services in conjunction with the access and core networks. User platform can be subdivided into a number of components.
331
+
332
+ Access network components are access technology dependent. They include multiple wireless and wire-line access technologies. Core network components are access technology independent. They
333
+
334
+ include functional components such as control functions and transport functions.
335
+
336
+ It is anticipated that radio access components of Systems Beyond IMT-2000 can dynamically support various radio transmission requirements. In addition to these radio access components, other access components to provide interconnection with other fixed networks are also needed in the IP-based network platform. [5]
337
+
338
+ Core network components will provide control functions and transport functions.
339
+
340
+ It is envisaged that a service provisioning mechanism that can dynamically provide user-defined combined multiple media services at a session level is needed. The service provisioning platform supports such a multiple service combination capability.
341
+
342
+ Service provisioning mechanisms in Systems Beyond IMT-2000 are envisaged to become more flexible in a multi-stage distributed manner. Such a distributed service provisioning platform is expected to help explore the network service potential of Systems Beyond IMT-2000.
343
+
344
+
345
+
346
+
347
+
348
+ ## **SERIES OF ITU-T RECOMMENDATIONS**
349
+
350
+ | | |
351
+ |-----------------|--------------------------------------------------------------------------------------------------------------------------------|
352
+ | Series A | Organization of the work of ITU-T |
353
+ | Series B | Means of expression: definitions, symbols, classification |
354
+ | Series C | General telecommunication statistics |
355
+ | Series D | General tariff principles |
356
+ | Series E | Overall network operation, telephone service, service operation and human factors |
357
+ | Series F | Non-telephone telecommunication services |
358
+ | Series G | Transmission systems and media, digital systems and networks |
359
+ | Series H | Audiovisual and multimedia systems |
360
+ | Series I | Integrated services digital network |
361
+ | Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
362
+ | Series K | Protection against interference |
363
+ | Series L | Construction, installation and protection of cables and other elements of outside plant |
364
+ | Series M | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
365
+ | Series N | Maintenance: international sound programme and television transmission circuits |
366
+ | Series O | Specifications of measuring equipment |
367
+ | Series P | Telephone transmission quality, telephone installations, local line networks |
368
+ | <b>Series Q</b> | <b>Switching and signalling</b> |
369
+ | Series R | Telegraph transmission |
370
+ | Series S | Telegraph services terminal equipment |
371
+ | Series T | Terminals for telematic services |
372
+ | Series U | Telegraph switching |
373
+ | Series V | Data communication over the telephone network |
374
+ | Series X | Data networks and open system communications |
375
+ | Series Y | Global information infrastructure and Internet protocol aspects |
376
+ | Series Z | Languages and general software aspects for telecommunication systems |
marked/Q/T-REC-Q.1721-200006-I_PDF-E/raw.md ADDED
The diff for this file is too large to render. See raw diff
 
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/0073ee258067e591778333101c5d2edb_img.jpg ADDED

Git LFS Details

  • SHA256: fb669f2b7ad73d57990a8077e1fe720b310a7153d9f6d3fffcf9ec73db26e37e
  • Pointer size: 130 Bytes
  • Size of remote file: 38.3 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/18e519d1f91133e080347562f681dfb5_img.jpg ADDED

Git LFS Details

  • SHA256: f2f9d0287d19eeec3486c43af3672b0e5126abba32155c13ac90d5802e1b4f82
  • Pointer size: 130 Bytes
  • Size of remote file: 29.4 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/200e768e8ed91aadff59c651287d1009_img.jpg ADDED

Git LFS Details

  • SHA256: 07826ea36565fb78f9706b36d08aa3f1b8d5358b847b3d73df4901d4caeaa51f
  • Pointer size: 130 Bytes
  • Size of remote file: 23.1 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2b88ad19a498bc8973acfafdd639c1cd_img.jpg ADDED

Git LFS Details

  • SHA256: 4c566632d4db82720667c4ba0dff1ef819f3cd12ee60bd78b15c0c3a0d9b5a00
  • Pointer size: 130 Bytes
  • Size of remote file: 40.5 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: 52a289bbb49d106b16f646b5050f62e5c7cbe1bb201f8c767547c3039abbf359
  • Pointer size: 129 Bytes
  • Size of remote file: 8.25 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/3922e505954d53f8864a44dc9ea664c6_img.jpg ADDED

Git LFS Details

  • SHA256: 939259eb532e2f309c5ff8a133ed5d3658e1f4c7ee6c17391a06f62b7cca79fb
  • Pointer size: 130 Bytes
  • Size of remote file: 43.6 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/438622ea89762ed550a4ef3c13fa71a6_img.jpg ADDED

Git LFS Details

  • SHA256: 6c09f6b6219bc0ac97d291056e1d80ce699d364c506668676c967d4f22e2e6ce
  • Pointer size: 130 Bytes
  • Size of remote file: 42.8 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg ADDED

Git LFS Details

  • SHA256: 1778f188806963b9235c6a435fa9e8e4c803c0d028bbd9eaa2cb1a8a5db54529
  • Pointer size: 130 Bytes
  • Size of remote file: 51.8 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg ADDED

Git LFS Details

  • SHA256: 277b3eeeeabac8a1cc4358ad7c5da0645516936ed9d597951aa809b72945952c
  • Pointer size: 130 Bytes
  • Size of remote file: 17.7 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/5ee80a63ec53c60d7306b5a44984afcf_img.jpg ADDED

Git LFS Details

  • SHA256: 62dd1fdfd7f4e44ff5b7cdf079ac8c31722f0b72f203d754b7c8f114aebef703
  • Pointer size: 130 Bytes
  • Size of remote file: 23.7 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg ADDED

Git LFS Details

  • SHA256: d59a0157ce4a9085e68fdadb191f54e835bb7eacf42c686fa6eb7d04ef7392cf
  • Pointer size: 130 Bytes
  • Size of remote file: 49.3 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg ADDED

Git LFS Details

  • SHA256: bfbc8062742e8fae952daed619b91f5ab37290a35c25cb6f0a028666eff65ad8
  • Pointer size: 131 Bytes
  • Size of remote file: 120 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg ADDED

Git LFS Details

  • SHA256: 49b64e66f97fd1ab5b6e86c2d8b620af091a89de7345fa44a5934af2ac84da87
  • Pointer size: 130 Bytes
  • Size of remote file: 25.3 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/a76fa39f5daf6a026e032495262ed0f6_img.jpg ADDED

Git LFS Details

  • SHA256: 659305c0ef4f07931376c979b36657ca7550dd78d97c64c4f23f8d9a5e9c5332
  • Pointer size: 130 Bytes
  • Size of remote file: 38.5 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg ADDED

Git LFS Details

  • SHA256: aac2675191bb415e1ee679f4dc0622e44b590d6f8c7fd7423c28d689a7789e64
  • Pointer size: 130 Bytes
  • Size of remote file: 47.2 kB
marked/Q/T-REC-Q.1741.2-200212-I_PDF-E/c76da2d73c064464051d1583fd80bb6b_img.jpg ADDED

Git LFS Details

  • SHA256: 23f0d93c6441befadb0404529f25eb602f742ae9c9fbfc40a327aed37df4b6ac
  • Pointer size: 130 Bytes
  • Size of remote file: 56 kB