emolero commited on
Commit
f7b0bbb
·
verified ·
1 Parent(s): 1e95ee4

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/G/T-REC-G.1027-202111-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg +3 -0
  2. marked/G/T-REC-G.1027-202111-I_PDF-E/352c5fab6f936356e9570761a02ab71e_img.jpg +3 -0
  3. marked/G/T-REC-G.1027-202111-I_PDF-E/602ada2a012ff3cc38d91de2eec5b450_img.jpg +3 -0
  4. marked/G/T-REC-G.1027-202111-I_PDF-E/6279fafb3a874e174648eb907385c954_img.jpg +3 -0
  5. marked/G/T-REC-G.1027-202111-I_PDF-E/raw.md +420 -0
  6. marked/G/T-REC-G.103-199812-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg +3 -0
  7. marked/G/T-REC-G.103-199812-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg +3 -0
  8. marked/G/T-REC-G.103-199812-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg +3 -0
  9. marked/G/T-REC-G.103-199812-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +3 -0
  10. marked/G/T-REC-G.103-199812-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg +3 -0
  11. marked/G/T-REC-G.103-199812-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg +3 -0
  12. marked/G/T-REC-G.103-199812-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg +3 -0
  13. marked/G/T-REC-G.103-199812-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg +3 -0
  14. marked/G/T-REC-G.103-199812-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg +3 -0
  15. marked/G/T-REC-G.103-199812-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg +3 -0
  16. marked/G/T-REC-G.103-199812-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg +3 -0
  17. marked/G/T-REC-G.1031-201402-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg +3 -0
  18. marked/G/T-REC-G.1031-201402-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg +3 -0
  19. marked/G/T-REC-G.1031-201402-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg +3 -0
  20. marked/G/T-REC-G.1033-201910-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg +3 -0
  21. marked/G/T-REC-G.1033-201910-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg +3 -0
  22. marked/G/T-REC-G.1033-201910-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg +3 -0
  23. marked/G/T-REC-G.1033-201910-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg +3 -0
  24. marked/G/T-REC-G.1033-201910-I_PDF-E/90ddf538ef276510e2b631f7b96654e6_img.jpg +3 -0
  25. marked/G/T-REC-G.1033-201910-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg +3 -0
  26. marked/G/T-REC-G.1033-201910-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg +3 -0
  27. marked/G/T-REC-G.1033-201910-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg +3 -0
  28. marked/G/T-REC-G.1033-201910-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg +3 -0
  29. marked/G/T-REC-G.1035-202111-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg +3 -0
  30. marked/G/T-REC-G.1035-202111-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg +3 -0
  31. marked/G/T-REC-G.1035-202111-I_PDF-E/c036e2540a94b31357ceb0002f0cacab_img.jpg +3 -0
  32. marked/G/T-REC-G.1050-201607-I_PDF-E/012117dcead1d581e96cafc55090be70_img.jpg +3 -0
  33. marked/G/T-REC-G.1050-201607-I_PDF-E/03afcee7dbcfc0af9eae2f7bf5eb6712_img.jpg +3 -0
  34. marked/G/T-REC-G.1050-201607-I_PDF-E/03e25a69b2145b8a280edf2421fbc07f_img.jpg +3 -0
  35. marked/G/T-REC-G.1050-201607-I_PDF-E/044324e651f5e7bb5178c637b769cb76_img.jpg +3 -0
  36. marked/G/T-REC-G.1050-201607-I_PDF-E/0577e933d8cc3e958649f0bc343fa804_img.jpg +3 -0
  37. marked/G/T-REC-G.1050-201607-I_PDF-E/0775f419af4e481eea2fb9706fe0b035_img.jpg +3 -0
  38. marked/G/T-REC-G.1050-201607-I_PDF-E/0829927e13d750d95334585b41a1403d_img.jpg +3 -0
  39. marked/G/T-REC-G.1050-201607-I_PDF-E/0c381fb7c01f2da0c5071fb7d3dc29e4_img.jpg +3 -0
  40. marked/G/T-REC-G.1050-201607-I_PDF-E/0f79a59f3766fc341ff688a23692c1d9_img.jpg +3 -0
  41. marked/G/T-REC-G.1050-201607-I_PDF-E/12a14855992490ef325e7c6e167a3472_img.jpg +3 -0
  42. marked/G/T-REC-G.1050-201607-I_PDF-E/13d55e18f0894a96c6e1c95b8e4c9d76_img.jpg +3 -0
  43. marked/G/T-REC-G.1050-201607-I_PDF-E/14294c70b5a0effb6bdaf09c46bbdc9f_img.jpg +3 -0
  44. marked/G/T-REC-G.1050-201607-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg +3 -0
  45. marked/G/T-REC-G.1050-201607-I_PDF-E/201c2ab6f2d9ee6ceabc06b39990b8be_img.jpg +3 -0
  46. marked/G/T-REC-G.1050-201607-I_PDF-E/201de44da5d99899a8cf58eac2fa7bc9_img.jpg +3 -0
  47. marked/G/T-REC-G.1050-201607-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg +3 -0
  48. marked/G/T-REC-G.1050-201607-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg +3 -0
  49. marked/G/T-REC-G.1050-201607-I_PDF-E/33d66c42e2c44378aaab641502989484_img.jpg +3 -0
  50. marked/G/T-REC-G.1050-201607-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg +3 -0
marked/G/T-REC-G.1027-202111-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg ADDED

Git LFS Details

  • SHA256: 80fc82c7ba6dab206ee4da41a28f0e3ee604a6a2af15886ebdb753dd2b4d89e0
  • Pointer size: 129 Bytes
  • Size of remote file: 5.79 kB
marked/G/T-REC-G.1027-202111-I_PDF-E/352c5fab6f936356e9570761a02ab71e_img.jpg ADDED

Git LFS Details

  • SHA256: 3c4def1d2fd1fda8cac03c0d25276c4720d41b94b02b886fec116c3c5fef2a0a
  • Pointer size: 130 Bytes
  • Size of remote file: 64.3 kB
marked/G/T-REC-G.1027-202111-I_PDF-E/602ada2a012ff3cc38d91de2eec5b450_img.jpg ADDED

Git LFS Details

  • SHA256: 78dbe2ddf3c0615e2d9cdd99f66edc82b1f195e498bf424f0066e9215b1bc537
  • Pointer size: 130 Bytes
  • Size of remote file: 41.7 kB
marked/G/T-REC-G.1027-202111-I_PDF-E/6279fafb3a874e174648eb907385c954_img.jpg ADDED

Git LFS Details

  • SHA256: 00635ace41699ea735b6aac95d4b7e229d8c43cceef429100c1d85fd482d82d1
  • Pointer size: 130 Bytes
  • Size of remote file: 42.6 kB
marked/G/T-REC-G.1027-202111-I_PDF-E/raw.md ADDED
@@ -0,0 +1,420 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ **ITU-T**
4
+
5
+ TELECOMMUNICATION
6
+ STANDARDIZATION SECTOR
7
+ OF ITU
8
+
9
+ **G.1027**
10
+
11
+ (11/2021)
12
+
13
+ SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
14
+ DIGITAL SYSTEMS AND NETWORKS
15
+
16
+ Multimedia Quality of Service and performance – Generic
17
+ and user-related aspects
18
+
19
+ ---
20
+
21
+ **Quality of service metrics for the assessment of
22
+ the impact of fixed geographic structures on
23
+ telephony quality and call stability**
24
+
25
+ Recommendation ITU-T G.1027
26
+
27
+ # ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS**
28
+
29
+ | | |
30
+ |----------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
31
+ | INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 |
32
+ | GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 |
33
+ | INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 |
34
+ | GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 |
35
+ | COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 |
36
+ | TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 |
37
+ | DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 |
38
+ | DIGITAL NETWORKS | G.800–G.899 |
39
+ | DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 |
40
+ | <b>MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS</b> | <b>G.1000–G.1999</b> |
41
+ | TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 |
42
+ | DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 |
43
+ | PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 |
44
+ | ACCESS NETWORKS | G.9000–G.9999 |
45
+
46
+ *For further details, please refer to the list of ITU-T Recommendations.*
47
+
48
+ ## Recommendation ITU-T G.1027
49
+
50
+ ## Quality of service metrics for the assessment of the impact of fixed geographic structures on telephony quality and call stability
51
+
52
+ ## Summary
53
+
54
+ Often poor call stability or degradation in speech quality is associated with natural or artificial, geographic or topological structures such as tunnels, ravines, or noise barriers. Recommendation ITU-T G.1027 is an extension of Recommendation ITU-T G.1034 where it defines a set of metrics that describes call stability and changes of speech quality related to the above structures.
55
+
56
+ ## History
57
+
58
+ | Edition | Recommendation | Approval | Study Group | Unique ID* |
59
+ |---------|----------------|------------|-------------|---------------------------------------------------------------------------|
60
+ | 1.0 | ITU-T G.1027 | 2021-11-29 | 12 | <a href="http://handle.itu.int/11.1002/1000/14822">11.1002/1000/14822</a> |
61
+
62
+ ## Keywords
63
+
64
+ Call stability, mobile network, quality of experience (QoE), quality of service (QoS), spatially resolved information.
65
+
66
+ ---
67
+
68
+ \* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
69
+
70
+ ## FOREWORD
71
+
72
+ The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). 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.
73
+
74
+ 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.
75
+
76
+ The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 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
+ Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
85
+
86
+ ## INTELLECTUAL PROPERTY RIGHTS
87
+
88
+ 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.
89
+
90
+ As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
91
+
92
+ © ITU 2022
93
+
94
+ All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
95
+
96
+ ## Table of Contents
97
+
98
+ | | Page |
99
+ |----------------------------------------------------------------------------------------|------|
100
+ | 1 Scope ..... | 1 |
101
+ | 2 References..... | 1 |
102
+ | 3 Definitions ..... | 1 |
103
+ | 3.1 Terms defined elsewhere ..... | 1 |
104
+ | 3.2 Terms defined in this Recommendation..... | 1 |
105
+ | 4 Abbreviations and acronyms ..... | 2 |
106
+ | 5 Conventions ..... | 2 |
107
+ | 6 User perspective of structure-related call stability and other quality metrics ..... | 2 |
108
+ | 7 Computation of structure-related call drop probability (SCDP)..... | 3 |
109
+ | 8 Computation of structure-related speech quality degradation (SSQD) ..... | 4 |
110
+ | 9 Indicator variants ..... | 4 |
111
+ | 10 Spatial and temporal resolution ..... | 4 |
112
+ | Appendix I – Calculation examples for SCDP and SSQD ..... | 6 |
113
+ | Bibliography..... | 9 |
114
+
115
+ # Introduction
116
+
117
+ Recommendation ITU-T G.1027 builds on the concepts and definitions given in Recommendation ITU-T G.1034. While Recommendation ITU-T G.1034 defines metrics for mobile telephony communication during rail travel, based on actual measurement data from telephony tests on trains. Also defining two key metrics i.e., local drop probability (LDP) that describes the local call stability, and call completion probability (CCP) which predicts the expected call stability or telephone calls of selected length. This Recommendation defines a set of respective metrics that describe call stability and speech quality related to fixed geographical structures.
118
+
119
+ Often poor call stability is associated with geographic or topological structures which are a challenge when attempting to achieve good mobile network coverage. Tunnels are a prime example of these types of structures however, there can be other areas along a track where mobile network coverage is poor (e.g., ravines or noise barriers), or where other degradations take place such as larger areas with radio signal interference.
120
+
121
+ Since typically the duration to travel through such structures are rather short, usage of CCP (or the conventional key performance indicator (KPI) "call-drop rate", for this matter) can be deemed unnecessary. To provide some typical real numbers: With a travel speed of 60 km/h, the time per km of the tunnel length is only one minute. Even in a country like Switzerland, only a few tunnels are longer than three km, so the travel time in the tunnel would be three minutes, and respectively shorter when higher speeds are considered. In contrast, it takes about 15 to 30 seconds of poor coverage to seriously degrade speech quality. Even though a shorter time of poor network coverage may suffice, negative impacts of call stability has direct effects on handover/handoff failures or even other hard effects of poor call continuity management.
122
+
123
+ Typically, quality of service (QoS) is not uniform over a given travel time or route. To improve overall QoS, places or structures where call stability or call quality is especially poor need to be identified; this basic task is conveniently supported by the LDP. Since, actual improvements require an optimization effort or investment, respective metrics play a key role in this process by providing guidance on prioritization and result verification.
124
+
125
+ ## Recommendation ITU-T G.1027
126
+
127
+ ## Quality of service metrics for the assessment of the impact of fixed geographic structures on telephony quality and call stability
128
+
129
+ # 1 Scope
130
+
131
+ This work item is an extension of the metrics provided in [ITU-T G.1034] to cover quality-relevant metrics of fixed geographic structures, e.g., tunnels on telephony call stability and speech quality. It builds upon actual measurement data to create spatially resolved information and provides metrics that can be used in the performance assessment and the optimization of networks.
132
+
133
+ This Recommendation does not introduce new modelling for perceptual effects; it provides a way to put existing data into a context related to geographical structures.
134
+
135
+ # 2 References
136
+
137
+ 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. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
138
+
139
+ [ITU-T G.1034] Recommendation ITU-T G.1034 (2020), *Quality of experience metrics for mobile telephony communication during rail travel*.
140
+
141
+ # 3 Definitions
142
+
143
+ ## 3.1 Terms defined elsewhere
144
+
145
+ This Recommendation uses the following terms defined elsewhere:
146
+
147
+ **3.1.1 call completion probability (CCP)** [ITU-T G.1034]: The probability that a telephone call started at a given location can be completed as intended (i.e., without being dropped).
148
+
149
+ **3.1.2 geographical unit (GU)** [ITU-T G.1034]: A segment of a road or railway track, or a square or rectangular shaped area, with given coordinates on a map. Used to aggregate measurement data based on their geographical coordinates.
150
+
151
+ **3.1.3 local drop probability (LDP)** [ITU-T G.1034]: An indicator, computed from drive test data, to indicate the call-drop probability for a given geographical unit (GU).
152
+
153
+ **3.1.4 quality of experience (QoE)** [b-ITU-T P.10]: The degree of delight or annoyance of the user of an application or service.
154
+
155
+ **3.1.5 quality of service (QoS)** [b-ITU-T E.800]: The totality of characteristics of a telecommunications service that bear on its ability to satisfy stated and implied needs of the user of the service.
156
+
157
+ **3.1.6 virtual call** [ITU-T G.1034]: A concept using the local drop probability (LDP) values in a route profile to compute the call completion probability (CCP) for a call of a given duration.
158
+
159
+ ## 3.2 Terms defined in this Recommendation
160
+
161
+ This Recommendation defines the following terms:
162
+
163
+ **3.2.1 structure-related call-drop probability (SCDP):** The probability that a telephone call drops when the device traverses through the given geographical structure.
164
+
165
+ **3.2.2 structure-related speech quality degradation (SSQD):** The (positive or negative) difference of speech quality (expressed in the native units of the speech quality metric) attributed to the given geographical structure.
166
+
167
+ **3.2.3 tunnel-related speech quality degradation (TCDP):** Same as SCDP, when applied specifically to tunnels.
168
+
169
+ **3.2.4 tunnel-related speech quality degradation (TSQD):** same as SSQD, when applied specifically to tunnels.
170
+
171
+ # **4 Abbreviations and acronyms**
172
+
173
+ This Recommendation uses the following abbreviations and acronyms:
174
+
175
+ | | |
176
+ |---------|-------------------------------------------------|
177
+ | KPI | Key Performance Indicator |
178
+ | MOS | Mean Opinion Score |
179
+ | MOS-LQO | Mean Opinion Score, Listening Quality Objective |
180
+ | QoE | Quality of Experience |
181
+ | QoS | Quality of Service |
182
+
183
+ # **5 Conventions**
184
+
185
+ This Recommendation uses the conventions established in [ITU-T G.1034].
186
+
187
+ # **6 User perspective of structure-related call stability and other quality metrics**
188
+
189
+ The following example is given for a typical case of a railway tunnel that has poor mobile network coverage.
190
+
191
+ The use case at hand is a subscriber making a phone call while approaching the tunnel. When entering the tunnel, the call may drop, or the speech quality may decrease. The figure below graphically shows this situation for the example of speech quality.
192
+
193
+ ![Figure 1: A composite figure showing a map of a railway tunnel and a graph of MOS values. The top part is a map with a blue line representing the tunnel path. The bottom part is a line graph with 'Segment index' on the x-axis (0 to 40) and 'MOS value' on the y-axis (3.5 to 4.5). The graph shows individual data points as blue dots and a solid blue line representing the floating average over four segments. The MOS values start around 4.1, dip to a minimum of about 3.8 at segment 15, and then rise back to around 4.2 by segment 40.](352c5fab6f936356e9570761a02ab71e_img.jpg)
194
+
195
+ Figure 1: A composite figure showing a map of a railway tunnel and a graph of MOS values. The top part is a map with a blue line representing the tunnel path. The bottom part is a line graph with 'Segment index' on the x-axis (0 to 40) and 'MOS value' on the y-axis (3.5 to 4.5). The graph shows individual data points as blue dots and a solid blue line representing the floating average over four segments. The MOS values start around 4.1, dip to a minimum of about 3.8 at segment 15, and then rise back to around 4.2 by segment 40.
196
+
197
+ G.1027(21)
198
+
199
+ Constructed image for explanatory purposes; assuming structure-dependent effects with superimposed random variations as in real-world measurements. The solid line has been added for more visual clarity, it represents the floating average over four segments.
200
+
201
+ **Figure 1 – Example: Railway tunnel and the associated speech quality mean opinion score (MOS) values per track segment**
202
+
203
+ NOTE 1 – This diagram is constructed for explanatory purposes. It uses typical speech quality values and patterns seen in real measurement data. It is however not visualizing actual measurement data.
204
+
205
+ In the case of call stability, the question associated with the metric is "how probable is a call drop caused by this tunnel"? For speech quality, the corresponding question would be "What is the degree of speech quality degradation caused by this tunnel"?
206
+
207
+ NOTE 2 – The term "speech quality" is used as a generic term for related metrics. Today, it is assumed that this practically means using the MOS – listening quality objective (MOS-LQO, [b-ITU-T P.863] "POLQA"). In the future, the spectrum may also include listening effort (LE) or other metrics dealing with perceptual quality of speech communication between persons.
208
+
209
+ NOTE 3 – This Recommendation does not introduce a new modelling for perceptual effects; it provides a way to put existing data into a context related to geographical structures.
210
+
211
+ For the following considerations, the abbreviations SCDP (structure-related call-drop probability) and SSQD (structure-related speech quality degradation) are introduced. When specifically tunnels are addressed the narrower terms TCDP and TSQD are used.
212
+
213
+ # 7 Computation of structure-related call drop probability (SCDP)
214
+
215
+ Using LDP as defined in [ITU-T G.1034], the computation of SCDP is straightforward:
216
+
217
+ ### Equation 1: Calculation of SCDP and TCDP
218
+
219
+ $$SCDP = 1 - SCSP = 1 - \prod_{Involved\ segments} (1 - LDP(x)) \quad (1)$$
220
+
221
+ The term SCSP is used as an intermediate definition, expressing the cumulated "call survival probability" which is simply the product of segment-wise LDP values. Therefore, SCSP is similar to
222
+
223
+ ITU-T G.1034's CCP, with the difference that CCP is computed from a "virtual call" with a given duration, whereas SCSP is related to the structure itself, i.e., does not depend on any other parameter.
224
+
225
+ NOTE 1 – If the calculation is done on values specifically for a tunnel, the entity calculated is termed as TCDP.
226
+
227
+ NOTE 2 – The selection of involved segments to be considered may also include adjacent segments, i.e., those which do not belong to the structure itself but are assumed to be part of the effect.
228
+
229
+ NOTE 3 – With a corresponding definition of the call drop which is at the basis of LDP, extensions such as "soft drops" can be seamlessly integrated into the concept. A soft drop would be a situation where the call is technically stable, but speech quality is so poor that the participants of the call agree to end the call and try again later.
230
+
231
+ # 8 Computation of structure-related speech quality degradation (SSQD)
232
+
233
+ By using the same concept, i.e., spatial aggregation of data, degradation of speech quality is addressed. It is assumed that the following will be based on MOS-LQO, b-ITU-T P.863 "POLQA", as the best-suited metric which supports temporal and spatial resolved speech quality assessment with the required granularity.
234
+
235
+ The calculation starts with averaging the MOS values belonging to the structure's segments (or, in the more general definition of [ITU-T G.1034], geo units).
236
+
237
+ In order to express a degradation, this value is then put into relation to a reference value, i.e., the average of the MOS values for the areas adjacent to the structure. Again, the user-perception is straightforward; it expresses the perceived change in speech quality when traversing the structure.
238
+
239
+ NOTE 1 – If the calculation is done on values specifically for a tunnel, the entity calculated is termed TSQD.
240
+
241
+ NOTE 2 – Conceptually, it is also possible to get a positive change of speech quality, e.g., in cases where improvement measures enhanced the quality beyond, that is experienced in the surrounding area.
242
+
243
+ # 9 Indicator variants
244
+
245
+ The definition of SCDP does not depend on the actual dimension of the structure it only looks at the effect on the perceived quality. The underlying assumption is that a subscriber does not care about the dimension of the structure, e.g., the length of a tunnel.
246
+
247
+ This is of course a matter of discussion and there will be cases where the dimension of a structure does matter, e.g., when looking at very long tunnels.
248
+
249
+ Also, especially in the case of tunnels, one may argue that this length can be perceived and be given credit for. For such cases, a secondary metric can be introduced, where the structure's dimension is entirely or partially taken into account.
250
+
251
+ For full normalization, a respective normalized indicator would be defined as $\text{NSCDP} = \text{SCDP} / L$ with $L$ the length of the structure in the direction of travel. The denominator may also be a function of $L$ , e.g., the square root of $L$ , to introduce a more QoE-related way of perception.
252
+
253
+ Likewise, instead of the physical dimension, the time to traverse the structure may be taken into account with a corresponding mathematical expression. For this variant, a larger structure that traverses faster would have the same indicator value i.e., the same severity of effect as a smaller structure that traverses with a lower travel speed.
254
+
255
+ With this spectrum of indicator variants the one which fits best to support a particular periodization strategy for resource usage, can be selected.
256
+
257
+ # 10 Spatial and temporal resolution
258
+
259
+ With reference also to [ITU-T G.1034], the spatial resolution used i.e., the actual length of a track segment or geo unit (GU) is a parameter of the metrics. The GU size, along with the speed of motion
260
+
261
+ provides a transformation between the spatial and the temporal dimension. Practical values for segment sizes are in the range of 100 to 200 m, which equals a time of two to four seconds when travelling at 160 km/h. Achieving a higher spatial or temporal resolution is possible by selecting a smaller segment size; this would however require higher sample numbers to populate each segment adequately and to avoid excessive fluctuations of values per segment. Likewise, spatial resolution can be lowered to larger segment sizes when required.
262
+
263
+ ## Appendix I
264
+
265
+ ### Calculation examples for SCDP and SSQD
266
+
267
+ (This appendix does not form an integral part of this Recommendation.)
268
+
269
+ This appendix shows practical examples for calculating SCDP and SSQD. As a basis, the constructed example shown in Figure 1 in the main text in clause 6 is used. From there, the example calculation of SSQD is demonstrated straightforward. For SCDP, the data base of the example is expanded to contain segment-wise call-drop probabilities (i.e., LDP values).
270
+
271
+ The following diagrams show the data base of values used (constructed values but structurally close to real measurement data). Please note that for explanatory purposes, the display style is different from Figure 1. The x-axis now shows the actual length (using the relative segment index and a segment length of 100 m) with the zero-point set at the position of the left-side tunnel entrance. The basic principle of the construction is however the same.
272
+
273
+ ![Figure I.1: Constructed values for SCDP example. A line graph titled 'LDP' showing LDP (%) on the y-axis (0 to 0.16) versus Relative position (km) on the x-axis (-1.5 to 3). The data points show a sharp peak around 0.5 km, reaching approximately 0.14%.](602ada2a012ff3cc38d91de2eec5b450_img.jpg)
274
+
275
+ The graph displays LDP values across a relative position range. The y-axis is labeled 'LDP (%)' and ranges from 0 to 0.16 in increments of 0.02. The x-axis is labeled 'Relative position (km)' and ranges from -1.5 to 3.0 in increments of 0.5. A blue line connects data points, showing a significant peak between 0 and 1.5 km, with the highest value around 0.14% at approximately 0.5 km. Outside this range, the values drop to near zero.
276
+
277
+ | Relative position (km) | LDP (%) |
278
+ |------------------------|---------|
279
+ | -1.5 | 0.005 |
280
+ | -1.0 | 0.005 |
281
+ | -0.5 | 0.005 |
282
+ | 0.0 | 0.005 |
283
+ | 0.2 | 0.145 |
284
+ | 0.4 | 0.14 |
285
+ | 0.6 | 0.105 |
286
+ | 0.8 | 0.145 |
287
+ | 1.0 | 0.125 |
288
+ | 1.2 | 0.14 |
289
+ | 1.4 | 0.01 |
290
+ | 1.6 | 0.005 |
291
+ | 2.0 | 0.005 |
292
+ | 2.5 | 0.005 |
293
+
294
+ G.1027(21)
295
+
296
+ Figure I.1: Constructed values for SCDP example. A line graph titled 'LDP' showing LDP (%) on the y-axis (0 to 0.16) versus Relative position (km) on the x-axis (-1.5 to 3). The data points show a sharp peak around 0.5 km, reaching approximately 0.14%.
297
+
298
+ Figure I.1 – Constructed values for SCDP example
299
+
300
+ ![Figure I.2: Constructed values for SSQD example. A line graph titled 'MOS value' showing MOS value on the y-axis (3.5 to 4.5) versus Relative position (km) on the x-axis (-1.5 to 3). The data points show a dip around 0.5 km, reaching approximately 3.85.](6279fafb3a874e174648eb907385c954_img.jpg)
301
+
302
+ The graph displays MOS values across a relative position range. The y-axis is labeled 'MOS value' and ranges from 3.5 to 4.5 in increments of 0.1. The x-axis is labeled 'Relative position (km)' and ranges from -1.5 to 3.0 in increments of 0.5. A blue line connects data points, showing a dip around 0.5 km, reaching a minimum of approximately 3.85. The values are generally higher (around 4.2) before 0 km and after 1.5 km.
303
+
304
+ | Relative position (km) | MOS value |
305
+ |------------------------|-----------|
306
+ | -1.5 | 4.25 |
307
+ | -1.0 | 4.2 |
308
+ | -0.5 | 4.15 |
309
+ | 0.0 | 4.2 |
310
+ | 0.2 | 3.85 |
311
+ | 0.4 | 3.85 |
312
+ | 0.6 | 3.9 |
313
+ | 0.8 | 3.9 |
314
+ | 1.0 | 3.95 |
315
+ | 1.2 | 4.0 |
316
+ | 1.4 | 4.15 |
317
+ | 1.6 | 4.2 |
318
+ | 1.8 | 4.2 |
319
+ | 2.0 | 4.2 |
320
+ | 2.2 | 4.2 |
321
+ | 2.4 | 4.2 |
322
+
323
+ G.1027(21)
324
+
325
+ Figure I.2: Constructed values for SSQD example. A line graph titled 'MOS value' showing MOS value on the y-axis (3.5 to 4.5) versus Relative position (km) on the x-axis (-1.5 to 3). The data points show a dip around 0.5 km, reaching approximately 3.85.
326
+
327
+ Figure I.2 – Constructed values for SSQD example
328
+
329
+ For these examples, random noise has been deliberately added to underline that in real-world situations, data is never noise-free. Even if segment-wise data comes from multiple passes of
330
+
331
+ measurements there will still be some fluctuation due to the overall measurement process and dynamic interactions between a mobile device and a network.
332
+
333
+ The table below shows the values used for the computation of the examples. Please note that this table displays only the core part of the data, sufficient to demonstrate calculations, while the figures show a larger range of segments before and after the structure.
334
+
335
+ **Table I.1 – Numerical values of LDP and MOS values used for the examples**
336
+
337
+ | Segment index | In tunnel | Rel. position (km) | LDP | MOS value |
338
+ |---------------|-----------|--------------------|--------|-----------|
339
+ | 6 | 0 | -0.7 | 0.0017 | 4.11 |
340
+ | 7 | 0 | -0.6 | 0.008 | 4.152 |
341
+ | 8 | 0 | -0.5 | 0.0079 | 4.154 |
342
+ | 9 | 0 | -0.4 | 0.0089 | 4.262 |
343
+ | 10 | 0 | -0.3 | 0.0038 | 4.202 |
344
+ | 11 | 0 | -0.2 | 0.0047 | 4.25 |
345
+ | 12 | 0 | -0.1 | 0.0059 | 4.118 |
346
+ | 13 | 1 | 0 | 0.1035 | 3.84 |
347
+ | 14 | 1 | 0.1 | 0.113 | 3.896 |
348
+ | 15 | 1 | 0.2 | 0.143 | 3.832 |
349
+ | 16 | 1 | 0.3 | 0.14 | 3.89 |
350
+ | 17 | 1 | 0.4 | 0.1145 | 3.844 |
351
+ | 18 | 1 | 0.5 | 0.106 | 3.996 |
352
+ | 19 | 1 | 0.6 | 0.1065 | 3.93 |
353
+ | 20 | 1 | 0.7 | 0.12 | 3.878 |
354
+ | 21 | 1 | 0.8 | 0.148 | 3.898 |
355
+ | 22 | 1 | 0.9 | 0.133 | 3.946 |
356
+ | 23 | 1 | 1 | 0.124 | 3.938 |
357
+ | 24 | 1 | 1.1 | 0.139 | 3.962 |
358
+ | 25 | 0 | 1.2 | 0.007 | 4.292 |
359
+ | 26 | 0 | 1.3 | 0.01 | 4.172 |
360
+ | 27 | 0 | 1.4 | 0.0017 | 4.104 |
361
+ | 28 | 0 | 1.5 | 0.0093 | 4.104 |
362
+ | 29 | 0 | 1.6 | 0.0012 | 4.298 |
363
+ | 30 | 0 | 1.7 | 0.0028 | 4.174 |
364
+ | 31 | 0 | 1.8 | 0.0022 | 4.292 |
365
+
366
+ The column "In tunnel" indicates if a data point is assumed to belong to the structure (value 1) or not (value 0).
367
+
368
+ It should also be noticed that the LDP outside the structure is typically not zero. For this example, it is assumed that the outside LDP values are however small against those that are inside (i.e., under the influence of) the structure. In practical situations, using offset or baseline values (acting as an offset to SCDP) will be considered on a pragmatic, case-by-case basis.
369
+
370
+ For SCDP, the calculation is done using Equation 1 given in clause 7 which is reproduced for the convenience of reading here:
371
+
372
+ $$SCDP = 1 - SCSP = 1 - \prod_{\text{Involved segments}} (1 - LDP(x))$$
373
+
374
+ Based on the above definition, the product is calculated over segments 13 to 24. For the example given, SCDP computes to (rounded to 3 after-comma digits) 0.797 which means a near 80% probability that a telephone call would drop during the passage of the structure.
375
+
376
+ As this example describes a tunnel, the more specific indicator name TCDP would be used, so the final result would be $TCDP = 0.979$ .
377
+
378
+ The calculation of SSQD (or, analogously to the above, TSQD), follows the procedure described in clause 8. Averaging the MOS values for segments belonging to the structure (segments 13 to 24) yields (rounded to 2 digits) 3.90.
379
+
380
+ For the reference value outside the structure, values for segments 6 to 12, and segments 25 to 31, are averaged, resulting in a reference value of 4.19. This computes to an SSQD or TSQD value of 0.29, meaning that under the influence of the structure, speech quality will be degraded by 0.29 MOS.
381
+
382
+ For this example, a rather small number of segments have been used so that too much space is not taken up for the table of values. In practical situations, typically a larger number of segments will be used. The actual number of segments will be determined following the targets of using enough elements to provide a sufficiently robust value while on the other hand maintaining a sufficiently localized picture of the QoS situation. For guidance, the segment number could be selected to represent one to two minutes of travel time before and after the structure. For example, at 100 km/h and 1.5 minutes travel time, this would lead to using 25 segments of 100 m length from each end of the structure.
383
+
384
+ # Bibliography
385
+
386
+ - [b-ITU-T E.800] Recommendation ITU-T E.800 (2008), *Definitions of terms related to quality of service*.
387
+ - [b-ITU-T P.10] Recommendation ITU-T P.10/G.100 (2017), *Vocabulary for performance, quality of service and quality of experience*, including Amendment 1 (2019).
388
+ - [b-ITU-T P.863] Recommendation ITU-T P.863 (2018), *Perceptual objective listening quality prediction*.
389
+
390
+
391
+
392
+
393
+
394
+ ## SERIES OF ITU-T RECOMMENDATIONS
395
+
396
+ | | |
397
+ |-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
398
+ | Series A | Organization of the work of ITU-T |
399
+ | Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
400
+ | Series E | Overall network operation, telephone service, service operation and human factors |
401
+ | Series F | Non-telephone telecommunication services |
402
+ | <b>Series G</b> | <b>Transmission systems and media, digital systems and networks</b> |
403
+ | Series H | Audiovisual and multimedia systems |
404
+ | Series I | Integrated services digital network |
405
+ | Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
406
+ | Series K | Protection against interference |
407
+ | Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
408
+ | Series M | Telecommunication management, including TMN and network maintenance |
409
+ | Series N | Maintenance: international sound programme and television transmission circuits |
410
+ | Series O | Specifications of measuring equipment |
411
+ | Series P | Telephone transmission quality, telephone installations, local line networks |
412
+ | Series Q | Switching and signalling, and associated measurements and tests |
413
+ | Series R | Telegraph transmission |
414
+ | Series S | Telegraph services terminal equipment |
415
+ | Series T | Terminals for telematic services |
416
+ | Series U | Telegraph switching |
417
+ | Series V | Data communication over the telephone network |
418
+ | Series X | Data networks, open system communications and security |
419
+ | Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
420
+ | Series Z | Languages and general software aspects for telecommunication systems |
marked/G/T-REC-G.103-199812-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg ADDED

Git LFS Details

  • SHA256: 3fa380ac70b0dbe88f91ebdc6f64e4fee1ebd5c307656e10afc7ae0a722f11b9
  • Pointer size: 130 Bytes
  • Size of remote file: 15.7 kB
marked/G/T-REC-G.103-199812-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg ADDED

Git LFS Details

  • SHA256: c413a37e0c1c167c2f7aae3d086f91cc26c1d01c0298fa2b5f01059ab15d7fa6
  • Pointer size: 130 Bytes
  • Size of remote file: 18.9 kB
marked/G/T-REC-G.103-199812-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg ADDED

Git LFS Details

  • SHA256: 67699f4032cc71166665353306f829d1243b7216436aa4d502fc781c3944f435
  • Pointer size: 130 Bytes
  • Size of remote file: 12.2 kB
marked/G/T-REC-G.103-199812-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg ADDED

Git LFS Details

  • SHA256: d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae
  • Pointer size: 129 Bytes
  • Size of remote file: 8.2 kB
marked/G/T-REC-G.103-199812-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg ADDED

Git LFS Details

  • SHA256: 190f921c2ae8255ebcb1f01602669619325a8b2f36b4619795e05fae5c83227b
  • Pointer size: 131 Bytes
  • Size of remote file: 223 kB
marked/G/T-REC-G.103-199812-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg ADDED

Git LFS Details

  • SHA256: 14d06e35d938a44a86a2b5499d84ca2cb92b4a7052d85b00f7aecb31e6c32c1e
  • Pointer size: 131 Bytes
  • Size of remote file: 133 kB
marked/G/T-REC-G.103-199812-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg ADDED

Git LFS Details

  • SHA256: ab46682d5c183d9061a9e3dfa71dd294479ec637163abf4365fc17b414cf2784
  • Pointer size: 131 Bytes
  • Size of remote file: 129 kB
marked/G/T-REC-G.103-199812-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg ADDED

Git LFS Details

  • SHA256: b03a4e173a6ee8f981332e5225aae14dcd23f393855758a8be0b31f8af1aa101
  • Pointer size: 131 Bytes
  • Size of remote file: 104 kB
marked/G/T-REC-G.103-199812-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg ADDED

Git LFS Details

  • SHA256: f5ca303926f42d66d7b578262c833578d12fc28513035df44718b21eebb4d7e5
  • Pointer size: 130 Bytes
  • Size of remote file: 18.3 kB
marked/G/T-REC-G.103-199812-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg ADDED

Git LFS Details

  • SHA256: a66f79a59098a08d7260444236fb06d56807f08d1331e9006ba29c5b085a9557
  • Pointer size: 131 Bytes
  • Size of remote file: 175 kB
marked/G/T-REC-G.103-199812-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg ADDED

Git LFS Details

  • SHA256: 4bb566b1f01b9407250cedd01e8232c1390114dcbfec71e07423218d9eb6a72c
  • Pointer size: 130 Bytes
  • Size of remote file: 80.9 kB
marked/G/T-REC-G.1031-201402-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg ADDED

Git LFS Details

  • SHA256: aa14933e776f7d0be8b2d60b81cbb6c1ee49deb5080e0281da05296f48189055
  • Pointer size: 129 Bytes
  • Size of remote file: 6.86 kB
marked/G/T-REC-G.1031-201402-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg ADDED

Git LFS Details

  • SHA256: cf28aef19ef7c8af4fd4b0200b4f5c5139fe9cf95b746ac497954de27b66998a
  • Pointer size: 130 Bytes
  • Size of remote file: 19.3 kB
marked/G/T-REC-G.1031-201402-I_PDF-E/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg ADDED

Git LFS Details

  • SHA256: ece5647f406345e7e76b19dbe98e53e5ff047bedc1d475d90bcefb65fc9b50a2
  • Pointer size: 130 Bytes
  • Size of remote file: 23.9 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg ADDED

Git LFS Details

  • SHA256: a78739a1cd1781f7232ef2782342c88689ebb77996024130fcd11d0d00cc7a2c
  • Pointer size: 129 Bytes
  • Size of remote file: 7.05 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg ADDED

Git LFS Details

  • SHA256: 6c3c7f9c72813e575b413437d34306ec09777326cd1dff6fdcb0bdd50cd7356b
  • Pointer size: 130 Bytes
  • Size of remote file: 44.6 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg ADDED

Git LFS Details

  • SHA256: 8471f964b5bc604814b511e5e41e0eaa52af033617cb7018324c74a8da65aa67
  • Pointer size: 130 Bytes
  • Size of remote file: 37 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/844077b3034f0030b404207db0ad76b4_img.jpg ADDED

Git LFS Details

  • SHA256: 3210534beb9ec15146e0148a0f7f666a850f6a7abe5660e5da23b28650027d08
  • Pointer size: 130 Bytes
  • Size of remote file: 39 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/90ddf538ef276510e2b631f7b96654e6_img.jpg ADDED

Git LFS Details

  • SHA256: ca6320855be9d3128adc2e29b34f510afc5bd77b55bd8af1a193757e78ae0786
  • Pointer size: 130 Bytes
  • Size of remote file: 45.5 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/c2fc2621e8206d24427b56bcb2398fc0_img.jpg ADDED

Git LFS Details

  • SHA256: d92480512425ff22b8b14864f9aa7f3fa117aadc10a5da54921bd02d5b85f4ad
  • Pointer size: 130 Bytes
  • Size of remote file: 64.4 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg ADDED

Git LFS Details

  • SHA256: d0b0912effd1232636b1b782282495dda3832bb4a0453791113543653df281c2
  • Pointer size: 130 Bytes
  • Size of remote file: 40.9 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg ADDED

Git LFS Details

  • SHA256: 0a94ce74d9fc874b11d0a856cc84560e5f541e5535c6cffdddf43acddbc3344f
  • Pointer size: 130 Bytes
  • Size of remote file: 31.9 kB
marked/G/T-REC-G.1033-201910-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg ADDED

Git LFS Details

  • SHA256: 2674e2e1aa3aa456294ff482f1c67fef45032634dcc8629e9706a21cd5abf842
  • Pointer size: 130 Bytes
  • Size of remote file: 40.1 kB
marked/G/T-REC-G.1035-202111-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg ADDED

Git LFS Details

  • SHA256: f418e2fcf77b057e807e60d0a0a741dd98ab9ee337764072def10cd9ce79d647
  • Pointer size: 129 Bytes
  • Size of remote file: 5.99 kB
marked/G/T-REC-G.1035-202111-I_PDF-E/54fabc351eda5228d2fa28cd9ba07971_img.jpg ADDED

Git LFS Details

  • SHA256: 676cd402b0cbe66cd5f3efbda17c11c7023f457730e858142ffbe21960cd35af
  • Pointer size: 130 Bytes
  • Size of remote file: 77.3 kB
marked/G/T-REC-G.1035-202111-I_PDF-E/c036e2540a94b31357ceb0002f0cacab_img.jpg ADDED

Git LFS Details

  • SHA256: 9c0aa4105e54ed7879227d9217e21278ebfaecad1a58114e153036d08414c3f3
  • Pointer size: 130 Bytes
  • Size of remote file: 38.9 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/012117dcead1d581e96cafc55090be70_img.jpg ADDED

Git LFS Details

  • SHA256: 5e5a16d8b3fc7280684472ef39462668fabec9b68ab5aaf5f36f5014a214bcec
  • Pointer size: 130 Bytes
  • Size of remote file: 20.4 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/03afcee7dbcfc0af9eae2f7bf5eb6712_img.jpg ADDED

Git LFS Details

  • SHA256: 2c4010c015cd191a7e4e8305e03580016d3f1cafc99f94e4e98acbcdc287696a
  • Pointer size: 130 Bytes
  • Size of remote file: 37.4 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/03e25a69b2145b8a280edf2421fbc07f_img.jpg ADDED

Git LFS Details

  • SHA256: bfa2222c67c0021f8908c66dd718f1afba4e555e83ba23513e9acce6a9f5f445
  • Pointer size: 130 Bytes
  • Size of remote file: 27.4 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/044324e651f5e7bb5178c637b769cb76_img.jpg ADDED

Git LFS Details

  • SHA256: b411f6461923b75549d641fc1630a507cb6d6ed59f8145a7f7055de79018432c
  • Pointer size: 130 Bytes
  • Size of remote file: 29.2 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/0577e933d8cc3e958649f0bc343fa804_img.jpg ADDED

Git LFS Details

  • SHA256: 48dd275a73afdf213cf9d10028710b76827df74657a7ca891fcc20ad3053d058
  • Pointer size: 130 Bytes
  • Size of remote file: 47.4 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/0775f419af4e481eea2fb9706fe0b035_img.jpg ADDED

Git LFS Details

  • SHA256: 9d8c0292ebe4e812750498587418821bd3b5bfd386b34a49614fa9e3a5e9ee37
  • Pointer size: 130 Bytes
  • Size of remote file: 30.1 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/0829927e13d750d95334585b41a1403d_img.jpg ADDED

Git LFS Details

  • SHA256: 884b26e2055a41707b7e02bb22e6298b30010063ab4270a422508b88df30df2d
  • Pointer size: 130 Bytes
  • Size of remote file: 38.7 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/0c381fb7c01f2da0c5071fb7d3dc29e4_img.jpg ADDED

Git LFS Details

  • SHA256: f41b88d735692542091e64b14d532d6412e4142fe2fb3c06b23808ce9c2d3da9
  • Pointer size: 130 Bytes
  • Size of remote file: 12.9 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/0f79a59f3766fc341ff688a23692c1d9_img.jpg ADDED

Git LFS Details

  • SHA256: f0100712b93c4809cd165e69d362950429e77a6832ed1b6680d3f3af0e6e26c4
  • Pointer size: 130 Bytes
  • Size of remote file: 29.4 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/12a14855992490ef325e7c6e167a3472_img.jpg ADDED

Git LFS Details

  • SHA256: badfe3f432775d3f6ed5e2ab79d3c5e8652d0728f25361820180ca00e4ffa6ca
  • Pointer size: 130 Bytes
  • Size of remote file: 40.1 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/13d55e18f0894a96c6e1c95b8e4c9d76_img.jpg ADDED

Git LFS Details

  • SHA256: 97819128fa051c6d2ed5cea2d4cd0e412aee9a509bb7834390b677806b0caabc
  • Pointer size: 130 Bytes
  • Size of remote file: 27 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/14294c70b5a0effb6bdaf09c46bbdc9f_img.jpg ADDED

Git LFS Details

  • SHA256: 6b5b9f269d02f7088cb79521ffea6cd4cd89a18e1db6761b63ff9d39ff886c89
  • Pointer size: 130 Bytes
  • Size of remote file: 20.6 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg ADDED

Git LFS Details

  • SHA256: 35d59812ee21605764a46ee50d9fdaa3dd80c7c7dea4e60b8d0ca636a0684889
  • Pointer size: 129 Bytes
  • Size of remote file: 4.15 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/201c2ab6f2d9ee6ceabc06b39990b8be_img.jpg ADDED

Git LFS Details

  • SHA256: 67ce841d78cb0fb06ebf3654dc3bd608b5661258c183f70d34eeedf8b0000f83
  • Pointer size: 130 Bytes
  • Size of remote file: 25 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/201de44da5d99899a8cf58eac2fa7bc9_img.jpg ADDED

Git LFS Details

  • SHA256: 268c20bc2853300896b1597b3ad113991e88ab598b34107bcdbb81c10cd7bd3d
  • Pointer size: 130 Bytes
  • Size of remote file: 14.9 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg ADDED

Git LFS Details

  • SHA256: 098784c855c68cff37ea77e771f56604963ec7b66a6d028e53491d52af6cb6c9
  • Pointer size: 130 Bytes
  • Size of remote file: 28.8 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg ADDED

Git LFS Details

  • SHA256: 7e685069500410dc04be348e154efd161af41a79751c9432f344b398004c3b7f
  • Pointer size: 130 Bytes
  • Size of remote file: 66.7 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/33d66c42e2c44378aaab641502989484_img.jpg ADDED

Git LFS Details

  • SHA256: 666de201131cfea43d4dd192111fed4306d232945e5bd5b46ac0d3d9b755cedd
  • Pointer size: 130 Bytes
  • Size of remote file: 20.2 kB
marked/G/T-REC-G.1050-201607-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg ADDED

Git LFS Details

  • SHA256: 715633562a109cc125e43e30485f992e34a8393ec611d2431bb3967625f63a06
  • Pointer size: 130 Bytes
  • Size of remote file: 40.9 kB