emolero commited on
Commit
0786807
·
verified ·
1 Parent(s): 1ed025d

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/Rel-18/21_series/21101/raw.md +182 -0
  2. marked/Rel-18/21_series/21111/raw.md +559 -0
  3. marked/Rel-18/21_series/21201/raw.md +182 -0
  4. marked/Rel-18/21_series/21202/raw.md +268 -0
  5. marked/Rel-18/21_series/21205/raw.md +144 -0
  6. marked/Rel-18/21_series/21900/raw.md +0 -0
  7. marked/Rel-18/23_series/23014/5fb340ad68b0c71df0b56698b137e35b_img.jpg +3 -0
  8. marked/Rel-18/23_series/23014/64662465bba247703fdec49c8f3309f9_img.jpg +3 -0
  9. marked/Rel-18/23_series/23014/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg +3 -0
  10. marked/Rel-18/23_series/23014/c9d8a18a6137ad054b841d7a614afb48_img.jpg +3 -0
  11. marked/Rel-18/23_series/23014/d0abac95583b52a3b35f74a215567334_img.jpg +3 -0
  12. marked/Rel-18/23_series/23014/e6df2733626a85205c1db682e6259c46_img.jpg +3 -0
  13. marked/Rel-18/23_series/23032/07f537f57749b75157f742525e6a8dbc_img.jpg +3 -0
  14. marked/Rel-18/23_series/23032/0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg +3 -0
  15. marked/Rel-18/23_series/23032/0ee9d674085524d589646a6c3fb21ec3_img.jpg +3 -0
  16. marked/Rel-18/23_series/23032/10953d657a5f47fdc829a800419dd370_img.jpg +3 -0
  17. marked/Rel-18/23_series/23032/18442e4e239480f0c3c95b547aa8fde2_img.jpg +3 -0
  18. marked/Rel-18/23_series/23032/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg +3 -0
  19. marked/Rel-18/23_series/23032/34fccc54a5930cbdf0f07e02c3745e35_img.jpg +3 -0
  20. marked/Rel-18/23_series/23032/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg +3 -0
  21. marked/Rel-18/23_series/23032/474a819357587e34949a3e110ff19b30_img.jpg +3 -0
  22. marked/Rel-18/23_series/23032/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg +3 -0
  23. marked/Rel-18/23_series/23032/53298644c66fa3fca81d6eec654afec5_img.jpg +3 -0
  24. marked/Rel-18/23_series/23032/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg +3 -0
  25. marked/Rel-18/23_series/23032/64662465bba247703fdec49c8f3309f9_img.jpg +3 -0
  26. marked/Rel-18/23_series/23032/6786ba12e3eceb3cf496108a02a37f09_img.jpg +3 -0
  27. marked/Rel-18/23_series/23032/73dff6b45b2b9ffd384bab3235f869af_img.jpg +3 -0
  28. marked/Rel-18/23_series/23032/7d2d1d3870cd224c4430d19334557716_img.jpg +3 -0
  29. marked/Rel-18/23_series/23032/b77cd8b2f763af8d453537177ac5942f_img.jpg +3 -0
  30. marked/Rel-18/23_series/23032/d8b92bdf09d07cb6c7b6961db9f6c4bb_img.jpg +3 -0
  31. marked/Rel-18/23_series/23032/d9a8b92ba7fc661ebe736ba3e4088eb5_img.jpg +3 -0
  32. marked/Rel-18/23_series/23032/e15f9dc3ef94138759781dc3c620b48d_img.jpg +3 -0
  33. marked/Rel-18/23_series/23035/5fb340ad68b0c71df0b56698b137e35b_img.jpg +3 -0
  34. marked/Rel-18/23_series/23035/64662465bba247703fdec49c8f3309f9_img.jpg +3 -0
  35. marked/Rel-18/23_series/23057/13fde41de77bf026013a0b81684d1fc9_img.jpg +3 -0
  36. marked/Rel-18/23_series/23057/17f0cf80b9c38adb460d4ca836960da7_img.jpg +3 -0
  37. marked/Rel-18/23_series/23057/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg +3 -0
  38. marked/Rel-18/23_series/23057/392a79ccd95e682ccd08f35ab2e64144_img.jpg +3 -0
  39. marked/Rel-18/23_series/23057/42d3842485845d9f6e511e6526061a55_img.jpg +3 -0
  40. marked/Rel-18/23_series/23057/44c649b1c110b4cd617810ae17342927_img.jpg +3 -0
  41. marked/Rel-18/23_series/23057/64662465bba247703fdec49c8f3309f9_img.jpg +3 -0
  42. marked/Rel-18/23_series/23057/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg +3 -0
  43. marked/Rel-18/23_series/23057/822e033872d5ab16e861571f47b81ba7_img.jpg +3 -0
  44. marked/Rel-18/23_series/23057/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg +3 -0
  45. marked/Rel-18/23_series/23057/9e8ebf03cae78f4f81b697548c2d7250_img.jpg +3 -0
  46. marked/Rel-18/23_series/23057/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg +3 -0
  47. marked/Rel-18/23_series/23057/a0e8fe7862a6d7341faf5dac275277cc_img.jpg +3 -0
  48. marked/Rel-18/23_series/23057/b63f41ca262d8ce9ef8affb62607f32b_img.jpg +3 -0
  49. marked/Rel-18/23_series/23057/cf018d13814389b0bd7f94a2f9bb812a_img.jpg +3 -0
  50. marked/Rel-18/23_series/23057/ddee3e67e0dfc22e25188fa635a19558_img.jpg +3 -0
marked/Rel-18/21_series/21101/raw.md ADDED
@@ -0,0 +1,182 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ # 3GPP TS 21.101 V18.1.0 (2025-03) ---
4
+
5
+ *Technical Specification*
6
+
7
+ ## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specifications and Technical Reports for a UTRAN-based 3GPP system (Release 18)**
8
+
9
+ ![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
10
+
11
+ ---
12
+
13
+ The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. The '3' is black, the 'G' is black, the 'P' is black, and the 'P' is black. There is a small red signal icon below the 'G'.
14
+
15
+ 3GPP logo
16
+
17
+ The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
18
+
19
+ The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
20
+ This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
21
+ Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organisational Partners' Publications Offices.
22
+
23
+ ---
24
+
25
+ ## --- **Keywords**
26
+
27
+ UMTS, architecture
28
+
29
+ ## **3GPP**
30
+
31
+ ## --- **Postal address**
32
+
33
+ ### --- **3GPP support office address**
34
+
35
+ 650 Route des Lucioles - Sophia Antipolis
36
+ Valbonne - FRANCE
37
+ Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
38
+
39
+ ## --- **Internet**
40
+
41
+ <http://www.3gpp.org>
42
+
43
+ ## --- **Copyright Notification**
44
+
45
+ No part may be reproduced except as authorized by written permission.
46
+ The copyright and the foregoing restriction extend to reproduction in all media.
47
+
48
+ © 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
49
+ All rights reserved.
50
+
51
+ UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
52
+ 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
53
+ LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
54
+ GSM® and the GSM logo are registered and owned by the GSM Association
55
+
56
+ ## --- Contents
57
+
58
+ - Foreword ..... 4
59
+ - 1 Scope..... 5
60
+ - 2 References..... 5
61
+ - 3 Abbreviations..... 5
62
+ - 4 General..... 5
63
+ - 5 Specifications and Reports..... 5
64
+ - Annex A (informative): Change history..... 6**
65
+
66
+ ## --- Foreword
67
+
68
+ This Technical Specification (TS) has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
69
+
70
+ The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
71
+
72
+ Version x.y.z
73
+
74
+ where:
75
+
76
+ - x the first digit:
77
+ - 1 presented to TSG for information;
78
+ - 2 presented to TSG for approval;
79
+ - 3 or greater indicates TSG approved document under change control.
80
+ - y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
81
+ - z the third digit is incremented when editorial only changes have been incorporated in the document.
82
+
83
+ ## --- 1 Scope
84
+
85
+ The present document identifies the 3GPP system specifications for Release 18. The specifications and reports of this Release have a major version number 18 (i.e. 18.x.y). The listed Specifications are required to build a system based on UTRAN radio technology.
86
+
87
+ ## --- 2 References
88
+
89
+ The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
90
+
91
+ - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
92
+ - For a specific reference, subsequent revisions do not apply.
93
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
94
+
95
+ [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
96
+
97
+ [2] 3GPP TR 21.900: "Technical Specification Group working methods".
98
+
99
+ ## --- 3 Abbreviations
100
+
101
+ For the purposes of the present document, the terms and definitions given in 3GPP TS 21.905 [1] apply.
102
+
103
+ ## --- 4 General
104
+
105
+ The numbering scheme for specifications is described in 3GPP TR 21.900 [2].
106
+
107
+ ## --- 5 Specifications and Reports
108
+
109
+ The list of Technical Specifications and Technical Reports can be found at <https://portal.3gpp.org/Specifications.aspx?q=1&tbid=All&releases=193&draft=False&underCC=True&withACC=False&withBCC=False&tech=2&numberNYA=False>
110
+
111
+ NOTE 1: The padlock icon on the right of each row indicates whether or not the documents are intended for adoption by the partner Standards Development Organizations as their own publications. Those with a padlock icon are internal working documents of the 3GPP TSGs.
112
+
113
+ NOTE 2: Some of the algorithm specifications in the 35.-series are available only under licence.
114
+
115
+ NOTE 3: "Type" indicates Technical Specification (TS) or Technical Report (TR).
116
+
117
+ ## Annex A (informative): Change history
118
+
119
+ | Change history | | | | | |
120
+ |----------------|------------------------------|--------|-----------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
121
+ | TSG SA# | Version | CR | Tdoc SA | New Version | Subject/Comment |
122
+ | SP-12 | 3GPP TS 21.103 version 0.0.0 | - | SP-010275 | 3GPP TS 21.103 version 0.1.0 | First draft |
123
+ | | 0.1.0 | | SP-010382 | 1.0.0 | table of specs revised |
124
+ | SP-13 | 1.0.0 | | SP-010418 | 1.1.0 | table of specs revised |
125
+ | SP-15 | 1.1.0 | | SP-020095 | 1.2.0 | table of specs revised; columns to show freeze status added |
126
+ | SP-15 | 1.2.0 | | SP-020202 | 2.0.0 | table of specs revised |
127
+ | SP-16 | 2.0.0 | | SP-020271 | 2.1.0 | table of specs revised |
128
+ | | 2.1.0 | | SP-020398 | 2.2.0 | table of specs revised |
129
+ | | 2.2.0 | | SP-020410 | | table of specs revised; unknown freeze target dates blanked |
130
+ | | | | | 5.0.0 | approved |
131
+ | SP-17 | 5.0.0 | 001 r1 | SP-020628 | 5.1.0 | updates lists of specs, editorial corrections to titles of specs |
132
+ | SP-18 | 5.1.0 | 002 r1 | SP-020831 | 5.2.0 | Correction to list of specs, editorial corrections to titles of specs |
133
+ | SP-19 | 5.2.0 | 003 r1 | SP-030077 | 5.3.0 | Correction to list of specs, editorial corrections to titles of specs |
134
+ | SP-20 | 3GPP TS 21.103 version 5.3.0 | 004 | SP-030229 | 3GPP TS 21.101 version 5.4.0 | Correction to list of specs |
135
+ | | | | SP-030235 | | Renumber from 21.103 to 21.101 |
136
+ | SP-22 | 5.4.0 | 017 | SP-030574 | 5.5.0 | Correction to list of specs, editorial corrections to spec titles |
137
+ | SP-23 | 5.5.0 | 020 r2 | SP-040221 | 5.6.0 | Corrections to list of specifications |
138
+ | SP-24 | 5.6.0 | 021 r1 | SP-040358 | 5.7.0 | Corrections to list of specifications |
139
+ | SP-26 | 5.7.0 | 025 r1 | SP-040880 | 6.0.0 | Corrections to list of specifications |
140
+ | SP-27 | 6.0.0 | 029 | SP-050126 | 6.1.0 | Corrections to list of specifications |
141
+ | SP-28 | 6.1.0 | 031 r1 | SP-050356 | 6.2.0 | Corrections to list of specifications |
142
+ | SP-29 | 6.2.0 | 032 | SP-050470 | | Change instances of Release 5 to Release 6 |
143
+ | | | 033 | SP-050462 | 6.3.0 | Corrections to list of specifications |
144
+ | SP-30 | 6.3.0 | 034 r1 | SP-050845 | 6.4.0 | Corrections to list of specifications |
145
+ | post SP-31 | 6.4.0 | | | 6.4.1 | Correction to title of reference to 21.900. Correction to spec list table entries for 23.125 and 32.251 to show that the <i>are</i> intended for SDO publication. |
146
+ | post SP-31 | 6.4.1 | | | 6.4.2 | Corrects cover date. |
147
+ | SP-34 | 6.4.2 | 038 | SP-060901 | 6.5.0 | Correction to list of Specs and minor editorials |
148
+ | SP-35 | 6.5.0 | 038 | SP-070188 | 6.6.0 | Corrections to list of specifications |
149
+ | SP-36 | 6.6.0 | 041 | SP-070344 | 6.7.0 | Corrections to list of specifications |
150
+ | SP-37 | 6.7.0 | 042 | SP-070519 | 7.0.0 | Upgrade to Rel-7 |
151
+ | SP-38 | 7.0.0 | 047 | SP-070770 | | Corrections to list of specifications |
152
+ | | | 052 | | 7.1.0 | Update of informative text |
153
+ | SP-40 | 7.1.0 | 053 | SP-080435 | 7.2.0 | Corrections to list of specifications |
154
+ | SP-42 | 7.2.0 | 054 r1 | SP-080722 | 7.3.0 | Corrections to list of specifications |
155
+ | SP-43 | 7.3.0 | 057 r1 | SP-090033 | 8.0.0 | List of Rel-8 specifications |
156
+ | SP-44 | 8.0.0 | 058 r1 | SP-090382 | 8.1.0 | Corrections to list of specifications |
157
+ | SP-46 | 8.1.0 | 064 r1 | SP-090695 | 8.2.0 | Corrections to list of specifications |
158
+ | SP-47 | 8.2.0 | 065 | SP-100012 | 9.0.0 | Update list of specs |
159
+
160
+ | | | | | | |
161
+ |-------|--------|-----------|-----------|--------|-----------------------------------------|
162
+ | SP-51 | 9.0.0 | | | 10.0.0 | Automatic upgrade on freezing Release |
163
+ | SP-52 | 10.0.0 | 068 | SP-110298 | 10.1.0 | Corrections to list of specifications |
164
+ | SP-55 | 10.1.0 | 071<br>r1 | SP-120114 | 10.2.0 | Changes to list of Specs: UTRAN systems |
165
+ | SP-59 | 10.2.0 | 072 | SP-130155 | 10.3.0 | Update list of specs |
166
+ | SP-59 | 10.3.0 | 073 | SP-130155 | 11.0.0 | Update list of specs |
167
+ | SP-64 | 11.0.0 | 075 | SP-140200 | 11.1.0 | Update to list of specs |
168
+
169
+ | Change history | | | | | | | |
170
+ |----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------|---------------|
171
+ | Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
172
+ | 2016-03 | SA#71 | SP-160124 | 0077 | | F | Update to list of specs | 12.0.0 |
173
+ | 2016-05 | | | | | | Empty table in clause 5 removed | 12.0.1 |
174
+ | 2016-12 | SA#74 | SP-160973 | 0078 | 1 | F | Update to list of specs | 13.0.0 |
175
+ | 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 |
176
+ | 2017-06 | SA#76 | SP-170459 | 0079 | | F | Replace list of specs with pointer to web page showing up to date list | 14.1.0 |
177
+ | 2018-06 | SA#80 | | | | | Upgrade unchanged on Rel-15 freeze | 15.0.0 |
178
+ | 2020-07 | SA#88-e | | | | | Upgrade on Rel-16 freeze | 16.0.0 |
179
+ | 2022-03 | SA#95-e | | | | | Upgrade on Rel-17 freeze | 17.0.0 |
180
+ | 2023-03 | SA#99 | SP-230321 | 0083 | | A | Correction of specs list URL | 17.1.0 |
181
+ | 2024-03 | SA#103 | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
182
+ | 2025-03 | SA#107 | SP-250225 | 0091 | 1 | A | Correction of Release | 18.1.0 |
marked/Rel-18/21_series/21111/raw.md ADDED
@@ -0,0 +1,559 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ # 3GPP TS 21.111 V18.0.0 (2024-03)
4
+
5
+ *Technical Specification*
6
+
7
+ ## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; USIM and IC card requirements (Release 18)**
8
+
9
+ ![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
10
+
11
+ The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
12
+
13
+ 5G Advanced logo
14
+
15
+ ![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
16
+
17
+ The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
18
+
19
+ 3GPP logo
20
+
21
+ The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
22
+
23
+ ## **3GPP**
24
+
25
+ ---
26
+
27
+ Postal address
28
+
29
+ ---
30
+
31
+ 3GPP support office address
32
+
33
+ ---
34
+
35
+ 650 Route des Lucioles - Sophia Antipolis
36
+ Valbonne - FRANCE
37
+ Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
38
+
39
+ ---
40
+
41
+ Internet
42
+
43
+ ---
44
+
45
+ <http://www.3gpp.org>
46
+
47
+ ## --- **Copyright Notification** ---
48
+
49
+ No part may be reproduced except as authorized by written permission.
50
+ The copyright and the foregoing restriction extend to reproduction in all media.
51
+
52
+ © 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
53
+ All rights reserved.
54
+
55
+ UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
56
+ 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
57
+ LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
58
+ GSM® and the GSM logo are registered and owned by the GSM Association
59
+
60
+ # --- Contents
61
+
62
+ | | |
63
+ |--------------------------------------------------------------|----|
64
+ | Foreword ..... | 5 |
65
+ | 1 Scope..... | 6 |
66
+ | 2 References..... | 6 |
67
+ | 2.1 Normative references ..... | 6 |
68
+ | 2.2 Void..... | 7 |
69
+ | 3 Definitions, symbols and abbreviations ..... | 7 |
70
+ | 3.1 Definitions..... | 7 |
71
+ | 3.2 Void..... | 7 |
72
+ | 3.3 Abbreviations ..... | 7 |
73
+ | 4 General requirements ..... | 7 |
74
+ | 5 Security requirements ..... | 7 |
75
+ | 5.1 File access conditions..... | 8 |
76
+ | 5.2 User authentication..... | 8 |
77
+ | 5.3 User data stored in ME..... | 8 |
78
+ | 5.4 Authentication ..... | 9 |
79
+ | 5.5 Data integrity of signalling elements ..... | 9 |
80
+ | 5.6 User identity confidentiality..... | 9 |
81
+ | 5.7 Length of security parameters ..... | 9 |
82
+ | 6 Logical issues..... | 9 |
83
+ | 6.1 Application selection..... | 9 |
84
+ | 6.2 Simultaneous access..... | 9 |
85
+ | 7 Service Requirements ..... | 10 |
86
+ | 7.1 Void..... | 10 |
87
+ | 7.2 Data transfer ..... | 10 |
88
+ | 7.3 Application execution environment ..... | 10 |
89
+ | 7.4 Profile exchange..... | 10 |
90
+ | 7.5 Version identification..... | 10 |
91
+ | 8 Physical Characteristics ..... | 10 |
92
+ | 8.1 Void..... | 10 |
93
+ | 8.2 Void..... | 10 |
94
+ | 9 Electrical characteristics and transmission protocols..... | 10 |
95
+ | 9.1 Void..... | 11 |
96
+ | 10 Contents of the Elementary Files ..... | 11 |
97
+ | 10.1 USIM information storage requirements..... | 11 |
98
+ | 10.2 Phone Book ..... | 12 |
99
+ | 10.2.1 Support of two name fields per entry ..... | 12 |
100
+ | 10.2.2 Support of multiple phone numbers per entry ..... | 12 |
101
+ | 10.2.3 Support of email address ..... | 12 |
102
+ | 10.2.4 Support of user definable groupings..... | 12 |
103
+ | 10.2.5 Support of hidden entries..... | 12 |
104
+ | 10.2.6 Number of entries ..... | 12 |
105
+ | 10.2.7 Void ..... | 12 |
106
+ | 10.3 Storage of call details ..... | 12 |
107
+ | 10.4 Void..... | 13 |
108
+ | 11 3G/GSM interworking ..... | 13 |
109
+ | 11.1 Void..... | 13 |
110
+ | 11.2 3G subscribers in a GSM network ..... | 13 |
111
+
112
+ 12 Contact Manager................................................................................................................................................ 13
113
+
114
+ **Annex A (informative): Change history.................................................................................................................. 16**
115
+
116
+ # Foreword
117
+
118
+ This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
119
+
120
+ The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
121
+
122
+ Version x.y.z
123
+
124
+ where:
125
+
126
+ - x the first digit:
127
+ - 1 presented to TSG for information;
128
+ - 2 presented to TSG for approval;
129
+ - 3 or greater indicates TSG approved document under change control.
130
+ - y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
131
+ - z the third digit is incremented when editorial only changes have been incorporated in the document.
132
+
133
+ In the present document, modal verbs have the following meanings:
134
+
135
+ - shall** indicates a mandatory requirement to do something
136
+ - shall not** indicates an interdiction (prohibition) to do something
137
+
138
+ The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
139
+
140
+ The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
141
+
142
+ - should** indicates a recommendation to do something
143
+ - should not** indicates a recommendation not to do something
144
+ - may** indicates permission to do something
145
+ - need not** indicates permission not to do something
146
+
147
+ The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
148
+
149
+ - can** indicates that something is possible
150
+ - cannot** indicates that something is impossible
151
+
152
+ The constructions "can" and "cannot" are not substitutes for "may" and "need not".
153
+
154
+ - will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
155
+ - will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
156
+ - might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
157
+
158
+ **might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
159
+
160
+ In addition:
161
+
162
+ **is** (or any other verb in the indicative mood) indicates a statement of fact
163
+
164
+ **is not** (or any other negative verb in the indicative mood) indicates a statement of fact
165
+
166
+ The constructions "is" and "is not" do not indicate requirements.
167
+
168
+ # --- 1 Scope
169
+
170
+ This document defines the requirements of the USIM (Universal Subscriber Identity Module) and the IC card for 3G (UICC). These are derived from the service and security requirements defined in TS 22.100 [1] and TS 22.101 [2]. The USIM is a 3G application on an IC card. It inter-operates with a 3G terminal and provides access to 3G services. This document is intended to serve as a basis for the detailed specification of the USIM and the UICC, and the interface to the 3G terminal.
171
+
172
+ # --- 2 References
173
+
174
+ ## 2.1 Normative references
175
+
176
+ The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
177
+
178
+ - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
179
+ - For a specific reference, subsequent revisions do not apply.
180
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
181
+
182
+ - [1] 3GPP TS 22.100 v3.x.x: "UMTS phase 1" (Release 99).
183
+ - [2] 3GPP TS 22.101: "Service principles".
184
+ - [3] 3GPP TS 31.101: "UICC-Terminal Interface; Physical and Logical Characteristics".
185
+ - [4] Void.
186
+ - [5] ETSI TS 101 220: "ETSI Numbering System for AIDs".
187
+ - [6] 3GPP TS 31.111: "USIM Application Toolkit (USAT)".
188
+ - [7] 3GPP TS 33.102: "3G Security: Security Architecture".
189
+ - [8] 3GPP TS 51.011, Rel-4: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface".
190
+ - [9] Void.
191
+ - [10] Void.
192
+ - [11] ISO/IEC 7816-3: "Information technology - Identification cards - Integrated circuit(s) cards with contacts - Part 3: Electronic signals and transmission protocols".
193
+ - [12] ISO/IEC 7816-4: "Identification cards - Integrated circuit cards, Part 4: Organization, security and commands for interchange".
194
+
195
+ - [13] Void.
196
+ - [14] 3GPP TS 36.306: "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities"
197
+
198
+ ## 2.2 Void
199
+
200
+ # --- 3 Definitions, symbols and abbreviations
201
+
202
+ ## 3.1 Definitions
203
+
204
+ For the purposes of the present document, the following definitions apply:
205
+
206
+ ## 3.2 Void
207
+
208
+ ## 3.3 Abbreviations
209
+
210
+ For the purposes of the present document, the following abbreviations apply:
211
+
212
+ | | |
213
+ |------|------------------------------------------|
214
+ | ADN | Abbreviated Dialling Number |
215
+ | ATR | Answer To Reset |
216
+ | DF | Dedicated File |
217
+ | EF | Elementary File |
218
+ | ICC | Integrated Circuit Card |
219
+ | IK | Integrity Key |
220
+ | IMSI | International Mobile Subscriber Identity |
221
+ | ME | Mobile Equipment |
222
+ | MF | Master File |
223
+ | PIN | Personal Identification Number |
224
+ | PPS | Protocol and Parameter Selection |
225
+ | SIM | Subscriber Identity Module |
226
+ | USIM | Universal Subscriber Identity Module |
227
+
228
+ # --- 4 General requirements
229
+
230
+ The UICC shall be either a removable hardware module or a non-removable separate hardware module embedded in the ME. The USIM on a UICC shall contain an identity which unambiguously identifies a subscriber.
231
+
232
+ For access to 3G services, a UICC containing a valid USIM shall be present at all times, other than for emergency calls.
233
+
234
+ The specifications shall support the security requirements as defined in 3GPP TS 33.102 [7].
235
+
236
+ The USIM shall provide storage for subscription and subscriber related information.
237
+
238
+ The UICC/USIM may also contain applications which use the features defined in the USIM Application Toolkit specification 3GPP TS 31.111 [6].
239
+
240
+ # --- 5 Security requirements
241
+
242
+ The USIM shall be used to provide security features. If the UICC is removed from the 3G terminal, the service shall be terminated immediately. The functions of the USIM include authenticating itself to the network and vice versa, authenticating the user and providing additional security functions as defined in 3GPP TS 33.102 [7].
243
+
244
+ The USIM shall be unambiguously identified.
245
+
246
+ Means shall be provided to prevent fraudulent use of stolen UICCs.
247
+
248
+ It shall not be possible to access data intended for USIM internal use, e.g. authentication keys.
249
+
250
+ Further details of the following requirements are given in 3GPP TS 33.102 [7].
251
+
252
+ ## 5.1 File access conditions
253
+
254
+ Actions, such as READ, UPDATE on UICC data shall be controlled by access conditions. These shall be satisfied prior to the action being performed.
255
+
256
+ Since a UICC may contain multiple (3G and non-3G) applications, a flexible method of controlling file access shall be provided.
257
+
258
+ ## 5.2 User authentication
259
+
260
+ The USIM shall support means to authenticate the user, to provide, for example, protection against the use of stolen cards. For the USIM, authentication shall be performed by the verification of a numeric PIN of four (4) to eight (8) decimal digits.
261
+
262
+ A function to disable user authentication may exist which may be inhibited by the application provider, in which case the user shall always use the PIN. Otherwise, the user may decide whether or not to make use of the user authentication function. If disabled, the user authentication function remains disabled until the user specifically re-enables it.
263
+
264
+ Following correct PIN presentation, the ME may perform functions and actions on USIM data, which are protected by the relevant access condition.
265
+
266
+ If an incorrect PIN is entered, an indication shall be given to the user. After three (3) consecutive incorrect entries the relevant PIN is blocked, i.e. functions and actions on data protected by the access condition shall no longer be possible, even if between attempts the UICC has been removed, the USIM has been deselected or the ME has been switched off. Once a PIN is blocked, further PIN verifications shall be denied.
267
+
268
+ The USIM shall support a mechanism for unblocking a blocked PIN. Unblocking of a PIN is performed by using the relevant PIN Unblocking Key.
269
+
270
+ PINs, but not Unblock PINs, shall be changeable by the user following correct entry of either the current PIN or Unblock PIN.
271
+
272
+ The Unblock PIN shall consist of eight (8) decimal digits and shall not be changeable by the user. If an incorrect Unblock PIN is presented, an indication shall be given to the user. After ten (10) consecutive incorrect entries, the Unblock PIN shall be blocked, even if between attempts the UICC has been removed, the USIM has been deselected or the ME has been switched off. Unblocking of a blocked PIN shall not be possible.
273
+
274
+ It shall not be possible to read PINs or Unblock PINs.
275
+
276
+ ## 5.3 User data stored in ME
277
+
278
+ Subject to the exception below, all user related information transferred into the ME during network operations shall be deleted from the ME after removal of the UICC, deselection of the USIM, deactivation of the ME, or following an electrical reset of the UICC. This includes any data that was transferred to the ME by USIM Application Toolkit commands.
279
+
280
+ User related security codes such as PIN and Unblock PIN may only be stored by the ME during the procedures involving such a code and shall be discarded by the ME immediately after completion of the procedure.
281
+
282
+ Optionally, an ME may retain some less security-sensitive data at UICC removal, USIM deselection or ME switch-off. Such data are e.g. SMS, ADN/SSC, FDN/SSC, LND. These data, when stored in the ME, shall only be readable/retrievable if the same USIM is reactivated (as determined by the IMSI). If the IMSI is retained in the ME for this purpose, it shall be stored securely and shall not be able to be read out.
283
+
284
+ ## 5.4 Authentication
285
+
286
+ A means shall be specified to mutually authenticate the USIM and the network by showing knowledge of a secret key K which is shared between and available only to the USIM and in the user's Home Environment. The method is composed of a challenge/response and key establishment protocol combined with a sequence number-based one-pass protocol for network authentication.
287
+
288
+ ## 5.5 Data integrity of signalling elements
289
+
290
+ Some signalling information elements are considered sensitive and must be integrity protected. An integrity function shall be applied on certain signalling information elements transmitted between the ME and the network.
291
+
292
+ The 3GPP Integrity Algorithm (UIA) is used with an Integrity Key (IK) to compute a message authentication code for a given message. The setting of IK is triggered by the authentication procedure. IK shall be stored on the USIM.
293
+
294
+ ## 5.6 User identity confidentiality
295
+
296
+ A mechanism shall be specified to provide user identity confidentiality by means of a temporary identity.
297
+
298
+ ## 5.7 Length of security parameters
299
+
300
+ In order to allow for enhancements of the security level in 3G, the following requirements shall be covered:
301
+
302
+ - all security-related parameters for 3G shall be accompanied by a length indicator;
303
+ - the USIM shall support variable-length security parameters.
304
+
305
+ If the USIM supports the GSM security mechanisms in addition to 3G security, fixed length security parameters according to 3GPP TS 51.011 [8] shall be supported in addition.
306
+
307
+ # --- 6 Logical issues
308
+
309
+ ## 6.1 Application selection
310
+
311
+ In a multiapplication environment, a flexible application selection method is required. The application identifier defined in ETSI TS 101 220 [5] should be used for application selection. Direct application selection, including selection by partial DF name and the EF<sub>DIR</sub> concept of ISO/IEC 7816-4 [12] shall be followed. In particular, a mechanism for the ME and the UICC shall be specified in order to allow the user, when the ME is in idle mode, to select and activate one application amongst those which are available and supported by the ME (this will permit the user to choose, for instance, between 2 different USIM applications). At switch on, the last active USIM shall be automatically selected. The last active USIM shall be stored on the UICC. By default if there is no last active USIM defined in the UICC, the user shall be able to select the active USIM amongst those available on the UICC.
312
+
313
+ ## 6.2 Simultaneous access
314
+
315
+ A mechanism shall be specified for simultaneous access to several files or applications.
316
+
317
+ # --- 7 Service Requirements
318
+
319
+ ## 7.1 Void
320
+
321
+ ## 7.2 Data transfer
322
+
323
+ A mechanism allowing highly secure transfer of applications and/or associated data to/from the UICC/USIM shall be specified in line with the requirements in 3GPP TS 22.101 [2]. This requires a secure transfer mechanism.
324
+
325
+ ## 7.3 Application execution environment
326
+
327
+ An application execution environment may exist on the UICC/USIM which includes functionality defined in 3GPP TS 31.111 [6].
328
+
329
+ ## 7.4 Profile exchange
330
+
331
+ A mechanism for the ME, the USIM and the network to exchange service capabilities shall be specified. The following exchange of service capabilities may occur:
332
+
333
+ - ME services capabilities may be provided to the USIM/UICC;
334
+ - USIM/UICC services capabilities may be provided to the ME (and thus potentially to the network);
335
+ - network services capabilities may be provided to the USIM/UICC via the ME.
336
+
337
+ ## 7.5 Version identification
338
+
339
+ A means for identification of the version of the USIM shall be provided.
340
+
341
+ # --- 8 Physical Characteristics
342
+
343
+ The physical characteristics shall be in accordance with the specifications in 3GPP TS 31.101 [3].
344
+
345
+ ## 8.1 Void
346
+
347
+ ## 8.2 Void
348
+
349
+ # --- 9 Electrical characteristics and transmission protocols
350
+
351
+ Electronic signals and transmission protocols shall be in accordance with the specifications in 3GPP TS 31.101 [3].
352
+
353
+ The electrical specifications shall at least cover the 1.8V and 3V voltage ranges as specified in 3GPP TS 31.101 [3]. Lower voltages may be added in the future. 3G terminals and beyond shall not support 5V on the ME-UICC interface. Both ME and UICC shall support operational class indication as defined in ISO/IEC 7816-3 [11].
354
+
355
+ UICC shall support at least two consecutive voltage classes unless it has a non removable form factor. ME shall support at least two consecutive voltage classes, unless it contains a non-removable UICC or unless it supports any of the following, or a combination of: NB-IoT, GERAN EC-GSM-IoT, Category M1 of E-UTRAN enhanced-MTC and Category 1bis as specified in 3GPP TS 36.306 [14].
356
+
357
+ An ME supporting NG-RAN and containing a removable UICC shall support at least the 1.8V voltage class, and may support a second, consecutive voltage class.
358
+
359
+ Both UICC and ME shall support PPS as defined in ISO/IEC 7816-3 [11] with at least the values defined in 3GPP TS 31.101 [3].
360
+
361
+ The ME shall have the capabilities of initiating a warm reset as defined in ISO/IEC 7816-3 [11]. The UICC shall support warm reset as defined in ISO/IEC 7816-3 [11].
362
+
363
+ NOTE2: The warm reset is used during a session when there is a need to restart the USIM due to internal modifications of data caused by user actions or network data downloading.
364
+
365
+ The UICC may indicate in the ATR to the warm reset that the specific mode is entered automatically, using the parameters that were used prior to the warm reset. In case of a cold reset, the UICC shall enter the negotiable mode.
366
+
367
+ In addition to the T=0 protocol which is mandatory for the UICC and the ME, the T=1 protocol shall be mandatory for the ME. It is optional for the UICC.
368
+
369
+ The speed enhancement as specified in 3GPP TS 31.101 [3] shall be supported by both the ME and the UICC.
370
+
371
+ ## 9.1 Void
372
+
373
+ # --- 10 Contents of the Elementary Files
374
+
375
+ ## 10.1 USIM information storage requirements
376
+
377
+ The USIM shall contain information elements for 3G network operations. The USIM may contain information elements related to the subscriber, 3G services and home environment or service provider related information.
378
+
379
+ The UICC shall provide storage capability for the following:
380
+
381
+ - UICC related information:
382
+ - IC card identification: a number uniquely identifying the UICC and the card issuer;
383
+ - Preferred language(s);
384
+ - Directory of applications.
385
+ - USIM related information:
386
+ - Administrative information: indicates mode of operation of the USIM, e.g. normal, type approval;
387
+ - USIM service table: indicates which optional services are provided by the USIM;
388
+ - IMSI;
389
+ - Language indication;
390
+ - Location information;
391
+ - Cipher key (Kc) and cipher key sequence number;
392
+ - Access control class(es);
393
+ - Forbidden PLMNs;
394
+ - Ciphering Key for GPRS;
395
+ - GPRS location information;
396
+ - Cell Broadcast related information;
397
+ - Emergency call codes;
398
+ - Phone numbers (ADN, FDN, SDN);
399
+ - Short messages and related parameters;
400
+ - Capability and Configuration parameters;
401
+ - Higher Priority PLMN search period;
402
+ - list of carrier frequencies to be used for cell selection.
403
+ - Information accessible to the USIM and other applications:
404
+ - ADN.
405
+
406
+ In addition, the USIM shall manage and provide storage for the following information in accordance with the security requirements of clause 5:
407
+
408
+ - PIN;
409
+ - PIN enabled/disabled indicator;
410
+ - PIN error counter;
411
+ - Unblock PIN;
412
+ - Unblock PIN error counter;
413
+ - Data integrity keys;
414
+ - Subscriber authentication keys.
415
+
416
+ ## 10.2 Phone Book
417
+
418
+ A Phone Book entry consists of a record in an ADN file and, optionally, additional records which are placed in different EFs. In the latter case, a mechanism shall be defined to link all records in the same Phone Book entry. These features shall be supported by the ME while their support by the UICC is optional.
419
+
420
+ ### 10.2.1 Support of two name fields per entry
421
+
422
+ The support of two name fields per entry shall be specified to allow, for example, for two different representations of the same name (for example, in Japanese characters and in Latin characters).
423
+
424
+ ### 10.2.2 Support of multiple phone numbers per entry
425
+
426
+ The support of multiple phone numbers per entry shall be specified, for example, office, home, fax, mobile or pager. In addition to that, information for identifying those attributes are needed.
427
+
428
+ ### 10.2.3 Support of email address
429
+
430
+ The support of email addresses linked to Phone Book entries shall be specified. In addition to that, information for identifying these addresses is needed.
431
+
432
+ ### 10.2.4 Support of user definable groupings
433
+
434
+ The specification shall support the grouping of Phone Book entries into groups defined by the user, for example, business and private.
435
+
436
+ ### 10.2.5 Support of hidden entries
437
+
438
+ The specification shall support means of marking Phone Book entries as "hidden".
439
+
440
+ ### 10.2.6 Number of entries
441
+
442
+ The specification shall support storage of at least 500 entries.
443
+
444
+ ### 10.2.7 Void
445
+
446
+ ## 10.3 Storage of call details
447
+
448
+ The specification shall support provision of storage for call detail information. The call detail information consists of the following attributes:
449
+
450
+ - mobile terminated calls:
451
+ - calling party number, date and time, calling party's name and status of call (i.e. answered or missed), duration;
452
+ - mobile originated calls:
453
+
454
+ called party number, date and time, called party's name and duration;
455
+
456
+ - accumulated duration of preceding calls, separately for mobile originated and mobile terminated calls.
457
+
458
+ Call detail attributes are optional. A value to mark them as "undefined" shall be available.
459
+
460
+ NOTE 1: The calling/called party's name may be available from the Phone Book.
461
+
462
+ ## 10.4 Void
463
+
464
+ # --- 11 3G/GSM interworking
465
+
466
+ ## 11.1 Void
467
+
468
+ ## 11.2 3G subscribers in a GSM network
469
+
470
+ 3GPP TS 22.101 [2] requires that UMTS shall provide some mechanisms which permit UMTS subscribers to roam easily onto pre-UMTS systems and access the services.
471
+
472
+ Thus, the specification shall allow the UICC to be used with a dual mode (GSM/ 3G) ME and a GSM ME for the provision of GSM service.
473
+
474
+ # --- 12 Contact Manager
475
+
476
+ ## 12.1 General
477
+
478
+ The Contact Manager provides an interface for the management of contact information including rich content without any structural limitations.
479
+
480
+ There shall be a mechanism for the ME to detect that the UICC containing the Contact Manager has changed. This mechanism may be used by the ME to ask the user whether synchronization of data between the ME and the UICC Contact Manager should occur.
481
+
482
+ This clause defines the functional requirements of the Contact Manager. An ME and a 3GPP application supporting the Contact Manager shall comply with all these requirements.
483
+
484
+ ## 12.2 Security requirements
485
+
486
+ The Contact Manager may contain personal information. It shall be possible to restrict the access to this information to authorized users or entities (e.g. by binding the access to the verification of the USIM PIN).
487
+
488
+ ### 12.4.3 Interworking with the 3G Phone Book
489
+
490
+ In case both the ME and the 3GPP application support both the 3G Phone Book (i.e. as defined in clause 10.2 of the present document) and the Contact Manager the Contact Manager shall be used. There shall be a mechanism for the 3GPP application to indicate the support of the Contact Manager.
491
+
492
+ ### 12.4.4 Content description
493
+
494
+ #### 12.4.4.1 Number of contacts
495
+
496
+ The Contact Manager specification shall not unreasonably restrict the number of contacts.
497
+
498
+ #### 12.4.4.2 Contact structure
499
+
500
+ The Contact Manager shall consist of contacts, which are made up of various fields (e.g. phone number, name, photo). A filtering mechanism according to OMA DS Field Filtering shall be supported.
501
+
502
+ It shall be possible to have several instances of a field in a contact when appropriate (e.g. a contact may have two fax numbers).
503
+
504
+ An extensible coding scheme shall be defined which allows to describe a contact including all its fields. An existing scheme (e.g. "vcard") shall be used, if appropriate.
505
+
506
+ A minimum set of field types recognised by the 3GPP application and the ME shall be defined (e.g. name, phone number, URL, Email address, address, sound, pictures, notes).
507
+
508
+ It shall be possible to store and associate multimedia information (stored on the 3GPP application) with a contact (e.g. photo, logo, video, ring tone, voice tag).
509
+
510
+ It shall be possible to associate an icon or a label to each contact field type (e.g. associate an icon representing a phone to the number field. "Home address" could be configured as the label of the "mailing address" field type).
511
+
512
+ It shall be possible to configure the structure and the display order of the contact fields (e.g. first name then Instant Messaging address then number, etc) depending on ME capabilities.
513
+
514
+ #### 12.4.4.3 Group management
515
+
516
+ It shall be possible to define new groups (e.g. My Tennis Club).
517
+
518
+ It shall be possible to pre-define groups (e.g. Friend, Work, Family and VIP).
519
+
520
+ It shall be possible to store and associate multimedia information (stored on the 3GPP application) with a group (e.g. photo, logo, video, ring tone, icon).
521
+
522
+ It shall be possible to bind contacts to one or several groups.
523
+
524
+ #### 12.4.4.4 User Action Management
525
+
526
+ It shall be possible to configure a list of possible actions that could be proposed to the user when the contact is selected (e.g. Launch Browser, Send SMS, Send MMS, Instant messaging, Make a voice over IP call, Make a video call, Make a conference call, Game player, Send Email).
527
+
528
+ ### 12.4.5 Interface capabilities description
529
+
530
+ An external and an internal interface to the Contact Manager shall be defined.
531
+
532
+ The external interface between the Contact Manager and a UICC external entity, i.e. the ME, shall rely on a transport protocol layer that is independent of the physical interface (i.e. the ISO interface and the new high-speed interface). This is to allow the definition of one solution that can use either the existing ISO interface or the new high-speed interface. The external interface definition shall also ease interfacing the PC applications with the Contact Manager.
533
+
534
+ Both the ME and the UICC shall be capable of initiating contact information synchronization based on a configurable policy. The internal interface allows other UICC resident applications to access the Contact Manager e.g. through a dedicated API. This enables the creation of additional services utilizing the Contact Manager data and properties. There shall be a mechanism for the user to allow or prevent remote access to the Contact Manager.
535
+
536
+ The external and internal interface shall provide means to:
537
+
538
+ - identify Contact Manager capabilities
539
+ - perform the following operations on a contact or a group: create, retrieve, modify, delete, search
540
+
541
+ In addition the internal interface shall provide mechanisms to:
542
+
543
+ - register/deregister an UICC resident application to the Contact Manager.
544
+
545
+ - allow a resident UICC application to access Contact Manager data and properties based on user permission.
546
+ - allow the Contact Manager to notify events to registered UICC application and to pass event related information when applicable. Events notifying the applications shall include:
547
+ - contact information is modified locally
548
+ - contact information is modified remotely
549
+ - change of contact manager configuration
550
+
551
+ ### 12.4.6 Efficient browsing and searching
552
+
553
+ The Contact Manager interfaces should allow efficient searching and browsing of the contacts (i.e. the user experience browsing the Contact Manager should be acceptable).
554
+
555
+ ### 12.4.7 Associated services
556
+
557
+ #### 12.4.7.1 Memory management
558
+
559
+ It shall be possible to determine the number of stored contacts and the amount of the available and used Contact Manager memory.
marked/Rel-18/21_series/21201/raw.md ADDED
@@ -0,0 +1,182 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ # 3GPP TS 21.201 V18.1.0 (2025-03) ---
4
+
5
+ *Technical Specification*
6
+
7
+ ## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specifications and Technical Reports for an Evolved Packet System (EPS) based 3GPP system (Release 18)**
8
+
9
+ ![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
10
+
11
+ ---
12
+
13
+ The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
14
+
15
+ 5G Advanced logo
16
+
17
+ ![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
18
+
19
+ The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
20
+
21
+ 3GPP logo
22
+
23
+ The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
24
+
25
+ The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
26
+ This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
27
+ Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
28
+
29
+ ---
30
+
31
+ ## --- **Keywords**
32
+
33
+ LTE, Packet Mode, Architecture
34
+
35
+ ### **3GPP**
36
+
37
+ ### --- **Postal address**
38
+
39
+ ### --- **3GPP support office address**
40
+
41
+ 650 Route des Lucioles - Sophia Antipolis
42
+ Valbonne - FRANCE
43
+ Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
44
+
45
+ ## --- **Internet**
46
+
47
+ <http://www.3gpp.org>
48
+
49
+ ## --- **Copyright Notification**
50
+
51
+ No part may be reproduced except as authorized by written permission.
52
+ The copyright and the foregoing restriction extend to reproduction in all media.
53
+
54
+ © 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
55
+ All rights reserved.
56
+
57
+ UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
58
+ 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
59
+ LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
60
+ GSM® and the GSM logo are registered and owned by the GSM Association
61
+
62
+ ## --- Contents
63
+
64
+ | | |
65
+ |---------------------------------------------------|----------|
66
+ | Foreword ..... | 4 |
67
+ | 1 Scope..... | 5 |
68
+ | 2 References..... | 5 |
69
+ | 3 Definitions, symbols and abbreviations ..... | 5 |
70
+ | 3.1 Definitions..... | 5 |
71
+ | 3.2 Symbols..... | 5 |
72
+ | 3.3 Abbreviations ..... | 5 |
73
+ | 4 General..... | 5 |
74
+ | 5 Specifications and Reports..... | 6 |
75
+ | <b>Annex A (informative): Change history.....</b> | <b>7</b> |
76
+
77
+ # --- Foreword
78
+
79
+ This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
80
+
81
+ The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
82
+
83
+ Version x.y.z
84
+
85
+ where:
86
+
87
+ - x the first digit:
88
+ - 1 presented to TSG for information;
89
+ - 2 presented to TSG for approval;
90
+ - 3 or greater indicates TSG approved document under change control.
91
+ - y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
92
+ - z the third digit is incremented when editorial only changes have been incorporated in the document.
93
+
94
+ # --- 1 Scope
95
+
96
+ The present document identifies the 3GPP system specifications for Release 18. The specifications and reports of this Release have a major version number 18 (i.e. 18.x.y). The listed Specifications are required to build a system based on the Evolved Packet System.
97
+
98
+ The high-level architecture of such a system is defined in 3GPP TS 23.002 [2] (figure 1b).
99
+
100
+ # --- 2 References
101
+
102
+ The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
103
+
104
+ - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
105
+ - For a specific reference, subsequent revisions do not apply.
106
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
107
+
108
+ [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
109
+
110
+ [2] 3GPP TS 23.002: "Network architecture".
111
+
112
+ [3] 3GPP TS 21.900: "Technical Specification Group working methods".
113
+
114
+ # --- 3 Definitions, symbols and abbreviations
115
+
116
+ ## 3.1 Definitions
117
+
118
+ For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply.
119
+
120
+ ## 3.2 Symbols
121
+
122
+ (Void)
123
+
124
+ ## 3.3 Abbreviations
125
+
126
+ For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply.
127
+
128
+ # --- 4 General
129
+
130
+ The numbering scheme for specifications is described in 3GPP TR 21.900 [3].
131
+
132
+ # --- 5 Specifications and Reports
133
+
134
+ The list of Technical Specifications and Technical Reports can be found at
135
+
136
+ <https://portal.3gpp.org/Specifications.aspx?q=1&tbid=All&releases=193&draft=False&underCC=True&withACC=False&withBCC=False&tech=3&numberNYA=False>
137
+
138
+ NOTE 1: The padlock icon on the right of each row indicates whether or not the documents are intended for adoption by the partner Standards Development Organizations as their own publications. Those with a padlock icon are internal working documents of the 3GPP TSGs.
139
+
140
+ NOTE 2: Some of the algorithm specifications in the 35.-series are available only under licence.
141
+
142
+ NOTE 3: "Type" indicates Technical Specification (TS) or Technical Report (TR).
143
+
144
+ ## Annex A (informative): Change history
145
+
146
+ | Change history | | | | | | | |
147
+ |----------------|----------------|------------------------|----|-----|----------------------------------------------------------------------------------------------------------------------|--------|--------|
148
+ | Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New |
149
+ | 2008-03 | | | | | First draft based on SA1 request to SP-38, refined at SP-39. Spec list based on Specification Manager's whim. | | 0.0.0 |
150
+ | 2008-05 | | | | | Rapporteur's revision | 0.0.0 | 0.1.0 |
151
+ | 2008-12 | SP-42 | SP-080723 | | | Rapporteur's revision prior to upgrading of specs to Rel-8 following Release freeze. | 0.1.0 | 0.2.0 |
152
+ | 2009-01 | | | | | Further rapporteur revision in the light of feedback | 0.2.0 | 0.3.0 |
153
+ | 2009-03 | CP-43<br>RP-43 | CP-080927<br>RP-081048 | | | Submission for review | 0.3.0 | 1.0.0 |
154
+ | 2009-03 | SP-43 | SP-090034 | | | Clean up of §3. To SA for information. | 1.0.0 | 1.0.1 |
155
+ | 2009-03 | SP-43 | SP-090224 | | | Major revision following clarification of scope, restricting the TS to a list of normative elements specific to EPS. | 1.0.1 | 2.0.0 |
156
+ | 2009-03 | SP-43 | | | | Approved | 2.0.0 | 8.0.0 |
157
+ | 2009-06 | SP-45 | SP-090495 | 1 | 2 | Update list of Specs | 8.0.0 | |
158
+ | | | | 2 | 2 | Clarification of scope | | 8.1.0 |
159
+ | 2009-12 | SP-46 | SP-090695 | 3 | 1 | Correction to list of specifications | 8.1.0 | 8.2.0 |
160
+ | 2010-03 | SP-47 | SP-100012 | 4 | - | Update list of specs | 8.2.0 | 8.3.0 |
161
+ | 2010-03 | SP-47 | SP-100012 | 5 | - | Update list of specs | 8.3.0 | 9.0.0 |
162
+ | 2011-03 | SP-51 | | | | Automatic upgrade on Release freeze | 9.0.0 | 10.0.0 |
163
+ | 2011-06 | SP-52 | SP-110298 | 8 | - | Correction to list of specifications | 10.0.0 | 10.1.0 |
164
+ | 2012-03 | SP-55 | SP-120114 | 11 | 1 | Changes to list of Specs: LTE systems | 10.1.0 | 10.2.0 |
165
+ | 2013-03 | SP-59 | SP-130155 | 12 | | Update to list of specs | 10.2.0 | 10.3.0 |
166
+ | 2013-03 | SP-59 | SP-130155 | 13 | | Update to list of specs | 10.3.0 | 11.0.0 |
167
+ | 2014-06 | SP-64 | SP-140200 | 15 | | Update to list of specs | 11.0.0 | 11.1.0 |
168
+
169
+ | Change history | | | | | | | |
170
+ |----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------|---------------|
171
+ | Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
172
+ | 2016-03 | SA#71 | SP-160126 | 0017 | | F | Update to list of Specs | 12.0.0 |
173
+ | 2013-12 | SA#74 | SP-150974 | 0018 | 1 | F | Update to list of Specs | 13.0.0 |
174
+ | 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 |
175
+ | 2017-06 | SA#76 | SP-170460 | 0019 | | F | Replace list of specs with pointer to web page showing up to date list | 14.1.0 |
176
+ | 2018-06 | SA#80 | | | | | Upgrade unchanged on freeze of Rel-15 | 15.0.0 |
177
+ | 2020-07 | SA#88-e | | | | | Upgrade on freeze of Rel-16 | 16.0.0 |
178
+ | 2022-03 | SA#95-e | | | | | Upgrade on freeze of Rel-17 | 17.0.0 |
179
+ | 2023-03 | SA#99 | SP-230325 | 0023 | | A | Correction of specs list URL | 17.1.0 |
180
+ | 2023-03 | SA#99 | | | | | Correction of release | 17.1.1 |
181
+ | 2024-03 | SA#103 | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
182
+ | 2025-03 | SA#107 | SP-250226 | 0024 | 1 | F | Correction of Release | 18.1.0 |
marked/Rel-18/21_series/21202/raw.md ADDED
@@ -0,0 +1,268 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ # 3GPP TS 21.202 V18.1.0 (2025-12)
4
+
5
+ Technical Specification
6
+
7
+ ## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specifications and Technical Reports relating to the Common IP Multimedia Subsystem (IMS) (Release 18)**
8
+
9
+ ![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
10
+
11
+ The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
12
+
13
+ 5G Advanced logo
14
+
15
+ ![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
16
+
17
+ The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it.
18
+
19
+ 3GPP logo
20
+
21
+ A GLOBAL INITIATIVE
22
+
23
+ The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
24
+
25
+ ## **3GPP**
26
+
27
+ ---
28
+
29
+ Postal address
30
+
31
+ ---
32
+
33
+ 3GPP support office address
34
+
35
+ ---
36
+
37
+ 650 Route des Lucioles - Sophia Antipolis
38
+ Valbonne - FRANCE
39
+ Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
40
+
41
+ ---
42
+
43
+ Internet
44
+
45
+ ---
46
+
47
+ <http://www.3gpp.org>
48
+
49
+ ## --- **Copyright Notification** ---
50
+
51
+ No part may be reproduced except as authorized by written permission.
52
+ The copyright and the foregoing restriction extend to reproduction in all media.
53
+
54
+ © 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
55
+ All rights reserved.
56
+
57
+ UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
58
+ 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
59
+ LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
60
+ GSM® and the GSM logo are registered and owned by the GSM Association
61
+
62
+ # --- Contents
63
+
64
+ - Foreword ..... 4
65
+ - 1 Scope..... 5
66
+ - 2 References..... 5
67
+ - 3 Definitions, symbols and abbreviations..... 5
68
+ - 3.1 Definitions..... 5
69
+ - 3.2 Symbols..... 5
70
+ - 3.3 Abbreviations ..... 5
71
+ - 4 General..... 5
72
+ - 5 Specifications and Reports..... 6
73
+ - Annex A (informative): void..... 11**
74
+ - Annex B (informative): void..... 11**
75
+ - Annex C (informative): Change history..... 12**
76
+
77
+ # --- Foreword
78
+
79
+ This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
80
+
81
+ The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
82
+
83
+ Version x.y.z
84
+
85
+ where:
86
+
87
+ - x the first digit:
88
+ - 1 presented to TSG for information;
89
+ - 2 presented to TSG for approval;
90
+ - 3 or greater indicates TSG approved document under change control.
91
+ - y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
92
+ - z the third digit is incremented when editorial only changes have been incorporated in the document.
93
+
94
+ # --- 1 Scope
95
+
96
+ The present document identifies the 3GPP Technical Specifications and Technical Reports specifically relating to the Common IP Multimedia Subsystem (IMS) maintained by 3GPP. Standards organizations adopting the Common IP Multimedia Subsystem (IMS) might not need to use all listed specifications.
97
+
98
+ ## --- 2 References
99
+
100
+ The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
101
+
102
+ - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
103
+ - For a specific reference, subsequent revisions do not apply.
104
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
105
+
106
+ [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
107
+
108
+ [2] 3GPP TR 21.900: "Technical specification group working methods".
109
+
110
+ ## --- 3 Definitions, symbols and abbreviations
111
+
112
+ ### 3.1 Definitions
113
+
114
+ For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply.
115
+
116
+ ### 3.2 Symbols
117
+
118
+ (None)
119
+
120
+ ### 3.3 Abbreviations
121
+
122
+ For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
123
+
124
+ | | |
125
+ |--------|----------------------------------------------------------------------------------------|
126
+ | NGN | Next Generation Network |
127
+ | R1 | Release 1 |
128
+ | R2 | Release 2 |
129
+ | TISPAN | Telecommunications and Internet converged Services and Protocols for Advanced Networks |
130
+
131
+ ## --- 4 General
132
+
133
+ The numbering scheme for specifications is described in 3GPP TR 21.900 [2].
134
+
135
+ ## --- 5 Specifications and Reports
136
+
137
+ NOTE 1: The "for publication?" column of the table below indicates whether or not the documents are intended for adoption by the partner Standards Development Organizations as their own publications. Those marked "no" are internal working documents of the 3GPP TSGs.
138
+
139
+ NOTE 2: Some of the algorithm specifications in the 35.-series are available only under licence.
140
+
141
+ NOTE 3: "Type" indicates Technical Specification (TS) or Technical Report (TR).
142
+
143
+ NOTE 4: For definition of "freezing" of specifications (last two columns), see 3GPP TR 21.900 [2].
144
+
145
+ The table below contains all Common IMS specs pertaining to Release 18.
146
+
147
+ | Type | Number | Title | Group | For publication? |
148
+ |------|--------|--------------------------------------------------------------------------------------------------------------------------------------|-------|------------------|
149
+ | TS | 21.111 | USIM and IC card requirements | C6 | Yes |
150
+ | TR | 21.905 | Vocabulary for 3GPP Specifications | SP | Yes |
151
+ | TS | 22.030 | Man-Machine Interface (MMI) of the User Equipment (UE) | S1 | Yes |
152
+ | TS | 22.041 | Operator Determined Barring (ODB) | S1 | Yes |
153
+ | TS | 22.071 | Location Services (LCS); Service description; Stage 1 | S1 | Yes |
154
+ | TS | 22.101 | Service aspects; Service principles | S1 | Yes |
155
+ | TS | 22.105 | Services and service capabilities | S1 | Yes |
156
+ | TS | 22.115 | Service aspects; Charging and billing | S1 | Yes |
157
+ | TS | 22.140 | Multimedia Messaging Service (MMS); Stage 1 | S1 | Yes |
158
+ | TS | 22.141 | Presence service; Stage 1 | S1 | Yes |
159
+ | TS | 22.153 | Multimedia priority service | S1 | Yes |
160
+ | TS | 22.173 | IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 | S1 | Yes |
161
+ | TS | 22.174 | Push Service; Service aspects; Stage 1 | S1 | Yes |
162
+ | TS | 22.182 | Customized Alerting Tones (CAT) requirements; Stage 1 | S1 | Yes |
163
+ | TS | 22.183 | Customized Ringing Signal (CRS) requirements; Stage 1 | S1 | Yes |
164
+ | TS | 22.228 | Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1 | S1 | Yes |
165
+ | TS | 22.250 | IP Multimedia Subsystem (IMS) Group Management; Stage 1 | S1 | Yes |
166
+ | TS | 22.279 | Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1 | S1 | Yes |
167
+ | TS | 22.340 | IP Multimedia Subsystem (IMS) messaging; Stage 1 | S1 | Yes |
168
+ | TR | 22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | S1 | Yes |
169
+ | TS | 23.141 | Presence service; Architecture and functional description | S2 | Yes |
170
+ | TS | 23.167 | IP Multimedia Subsystem (IMS) emergency sessions | S2 | Yes |
171
+ | TS | 23.204 | Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 | S2 | Yes |
172
+ | TS | 23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | C1 | Yes |
173
+ | TS | 23.228 | IP Multimedia Subsystem (IMS); Stage 2 | S2 | Yes |
174
+ | TS | 23.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions | C4 | Yes |
175
+ | TS | 23.334 | IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions | C4 | Yes |
176
+ | TS | 24.141 | Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | C1 | Yes |
177
+ | TS | 24.147 | Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | C1 | Yes |
178
+ | TS | 24.173 | IMS Multimedia telephony communication service and supplementary services; Stage 3 | C1 | Yes |
179
+ | TS | 24.174 | Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage 3 | C1 | Yes |
180
+ | TS | 24.175 | Management Object (MO) for multi-device and multi-identity in the IP Multimedia Subsystem (IMS) | C1 | Yes |
181
+ | TS | 24.182 | IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification | C1 | Yes |
182
+ | TS | 24.229 | IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 | C1 | Yes |
183
+ | TS | 24.238 | Session Initiation Protocol (SIP) based user configuration; Stage 3 | C1 | Yes |
184
+ | TS | 24.239 | Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
185
+ | TS | 24.247 | Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | C1 | Yes |
186
+
187
+ | Type | Number | Title | Group | For publication? |
188
+ |------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------|
189
+ | TS | 24.315 | IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB); Stage 3: protocol specification | C1 | Yes |
190
+ | TS | 24.341 | Support of SMS over IP networks; Stage 3 | C1 | Yes |
191
+ | TS | 24.604 | Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
192
+ | TS | 24.605 | Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
193
+ | TS | 24.606 | Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
194
+ | TS | 24.607 | Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
195
+ | TS | 24.608 | Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
196
+ | TS | 24.610 | Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
197
+ | TS | 24.611 | Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
198
+ | TS | 24.615 | Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification | C1 | Yes |
199
+ | TS | 24.616 | Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
200
+ | TS | 24.628 | Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
201
+ | TS | 24.629 | Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
202
+ | TS | 24.642 | Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | C1 | Yes |
203
+ | TS | 24.647 | Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem | C1 | Yes |
204
+ | TS | 24.654 | Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification | C1 | Yes |
205
+ | TR | 24.930 | Signalling flows for the session setup in the IP Multimedia core network Subsystem (IMS) based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 | C1 | Yes |
206
+ | TR | 26.954 | Test plan for speech quality and delay through a headset electrical interface | S4 | Yes |
207
+ | TS | 29.162 | Interworking between the IM CN subsystem and IP networks | C3 | Yes |
208
+ | TS | 29.163 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks | C3 | Yes |
209
+ | TS | 29.165 | Inter-IMS Network to Network Interface (NNI) | C3 | Yes |
210
+ | TS | 29.212 | Policy and Charging Control (PCC); Reference points | C3 | Yes |
211
+ | TS | 29.213 | Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping | C3 | Yes |
212
+ | TS | 29.214 | Policy and charging control over Rx reference point | C3 | Yes |
213
+ | TS | 29.215 | Policy and Charging Control (PCC) over S9 reference point; Stage 3 | C3 | Yes |
214
+ | TS | 29.228 | IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents | C4 | Yes |
215
+ | TS | 29.229 | Cx and Dx interfaces based on the Diameter protocol; Protocol details | C4 | Yes |
216
+ | TS | 29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 | C4 | Yes |
217
+ | TS | 29.238 | Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3 | C4 | Yes |
218
+ | TS | 29.292 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS) | C3 | Yes |
219
+ | TS | 29.311 | Service Level Interworking (SLI) for messaging services | C3 | Yes |
220
+ | TS | 29.328 | IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents | C4 | Yes |
221
+
222
+ | Type | Number | Title | Group | For publication? |
223
+ |------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------------|
224
+ | TS | 29.329 | Sh interface based on the Diameter protocol; Protocol details | C4 | Yes |
225
+ | TS | 29.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface; Stage 3 | C4 | Yes |
226
+ | TS | 29.334 | IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3 | C4 | Yes |
227
+ | TS | 29.541 | 5G System; Network Exposure (NE) function services for Non-IP Data Delivery (NIDD) and Short Message Services (SMS); Stage 3 | C4 | Yes |
228
+ | TS | 29.658 | SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification | C3 | Yes |
229
+ | TS | 31.101 | UICC-terminal interface; Physical and logical characteristics | C6 | Yes |
230
+ | TS | 31.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application | C6 | Yes |
231
+ | TS | 31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | C6 | Yes |
232
+ | TS | 31.116 | Remote APDU Structure for (U)SIM Toolkit applications | C6 | Yes |
233
+ | TS | 31.133 | IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™ | C6 | Yes |
234
+ | TS | 32.240 | Telecommunication management; Charging management; Charging architecture and principles | S5 | Yes |
235
+ | TS | 32.260 | Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging | S5 | Yes |
236
+ | TS | 32.275 | Telecommunication management; Charging management; MultiMedia Telephony (MMTel) charging | S5 | Yes |
237
+ | TS | 32.276 | Telecommunication management; Charging management; Voice Call Service (VCS) charging | S5 | Yes |
238
+ | TS | 32.281 | Telecommunication management; Charging management; Announcement service | S5 | Yes |
239
+ | TS | 32.290 | Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) | S5 | Yes |
240
+ | TS | 32.291 | Telecommunication management; Charging management; 5G system, charging service; Stage 3 | S5 | Yes |
241
+ | TS | 32.295 | Telecommunication management; Charging management; Charging Data Record (CDR) transfer | S5 | Yes |
242
+ | TS | 32.297 | Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer | S5 | Yes |
243
+ | TS | 32.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | S5 | Yes |
244
+ | TS | 32.299 | Telecommunication management; Charging management; Diameter charging applications | S5 | Yes |
245
+ | TS | 33.141 | Presence service; Security | S3 | Yes |
246
+ | TS | 33.203 | 3G security; Access security for IP-based services | S3 | Yes |
247
+ | TS | 33.210 | Network Domain Security (NDS); IP network layer security | S3 | Yes |
248
+ | TS | 33.226 | Security assurance for IP Multimedia Subsystem (IMS) | S3 | Yes |
249
+ | TS | 33.328 | IP Multimedia Subsystem (IMS) media plane security | S3 | Yes |
250
+ | TS | 34.229-1 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 1: Protocol conformance specification | R5 | Yes |
251
+ | TS | 34.229-2 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) specification | R5 | Yes |
252
+ | TS | 34.229-3 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS) | R5 | Yes |
253
+ | TS | 34.229-5 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 5: Protocol conformance specification using 5G System (5GS) | R5 | Yes |
254
+ | TS | 36.579- | Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS) | R5 | Yes |
255
+
256
+ | Type | Number | Title | Group | For publication? |
257
+ |------|----------|-------------------------------------------------------------------|-------|------------------|
258
+ | | 5 | | | |
259
+ | TS | 37.579-5 | Mission Critical (MC) services; Part 5: Abstract test suite (ATS) | R5 | Yes |
260
+
261
+ ---
262
+
263
+ Annex A (informative):
264
+ void
265
+
266
+ Annex B (informative):
267
+ void
268
+
marked/Rel-18/21_series/21205/raw.md ADDED
@@ -0,0 +1,144 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+
3
+ # 3GPP TS 21.205 V18.1.0 (2025-03) ---
4
+
5
+ *Technical Specification*
6
+
7
+ ## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Technical Specifications and Technical Reports for a 5G based 3GPP system (Release 18)**
8
+
9
+ ![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg)
10
+
11
+ ---
12
+
13
+ The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
14
+
15
+ 5G ADVANCED logo
16
+
17
+ ![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
18
+
19
+ The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
20
+
21
+ 3GPP logo
22
+
23
+ The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP.
24
+
25
+ The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
26
+
27
+ ---
28
+
29
+ ## --- **Keywords**
30
+
31
+ 5G, Architecture
32
+
33
+ ## **3GPP**
34
+
35
+ ## --- **Postal address**
36
+
37
+ ## --- **3GPP support office address**
38
+
39
+ 650 Route des Lucioles - Sophia Antipolis
40
+ Valbonne - FRANCE
41
+ Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
42
+
43
+ ## --- **Internet**
44
+
45
+ <http://www.3gpp.org>
46
+
47
+ ## --- **Copyright Notification**
48
+
49
+ No part may be reproduced except as authorized by written permission.
50
+ The copyright and the foregoing restriction extend to reproduction in all media.
51
+
52
+ © 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
53
+ All rights reserved.
54
+
55
+ UMTSTM is a Trade Mark of ETSI registered for the benefit of its members
56
+ 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
57
+ LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
58
+ GSM® and the GSM logo are registered and owned by the GSM Association
59
+
60
+ ## --- Contents
61
+
62
+ - Foreword ..... 4
63
+ - 1 Scope..... 5
64
+ - 2 References..... 5
65
+ - 3 Definitions, symbols and abbreviations ..... 5
66
+ - 3.1 Definitions..... 5
67
+ - 3.2 Symbols..... 5
68
+ - 3.3 Abbreviations ..... 5
69
+ - 4 General..... 5
70
+ - 5 Specifications and Reports..... 6
71
+ - Annex A (informative): Change history..... 7**
72
+
73
+ ## --- Foreword
74
+
75
+ This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
76
+
77
+ The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
78
+
79
+ Version x.y.z
80
+
81
+ where:
82
+
83
+ - x the first digit:
84
+ - 1 presented to TSG for information;
85
+ - 2 presented to TSG for approval;
86
+ - 3 or greater indicates TSG approved document under change control.
87
+ - y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
88
+ - z the third digit is incremented when editorial only changes have been incorporated in the document.
89
+
90
+ ## --- 1 Scope
91
+
92
+ The present document identifies the 3GPP Technical Specifications required to build a 5G system. It also lists relevant Technical Reports.
93
+
94
+ ## --- 2 References
95
+
96
+ The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
97
+
98
+ - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
99
+ - For a specific reference, subsequent revisions do not apply.
100
+ - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
101
+
102
+ [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
103
+
104
+ [2] 3GPP TR 21.900: "Technical Specification Group working methods".
105
+
106
+ ## --- 3 Definitions, symbols and abbreviations
107
+
108
+ ### 3.1 Definitions
109
+
110
+ For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply.
111
+
112
+ ### 3.2 Symbols
113
+
114
+ (Void)
115
+
116
+ ### 3.3 Abbreviations
117
+
118
+ For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply.
119
+
120
+ ## --- 4 General
121
+
122
+ The numbering scheme for specifications is described in 3GPP TR 21.900 [2].
123
+
124
+ ## --- 5 Specifications and Reports
125
+
126
+ The list of Technical Specifications and Technical Reports can be found at <https://portal.3gpp.org/Specifications.aspx?q=1&tbid=All&releases=193&draft=False&underCC=True&withACC=False&withBCC=False&tech=3,4&numberNYA=False>
127
+
128
+ NOTE 1: The padlock icon on the right of each row indicates whether or not the documents are intended for adoption by the partner Standards Development Organizations as their own publications. Those with a padlock icon are internal working documents of the 3GPP TSGs.
129
+
130
+ NOTE 2: Some of the algorithm specifications in the 35.-series are available only under licence.
131
+
132
+ ## Annex A (informative): Change history
133
+
134
+ | Change history | | | | | | | |
135
+ |----------------|---------|-----------|------|-----|-----|--------------------------------------------------|---------------|
136
+ | Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version |
137
+ | 2018-03 | SA#79 | SP-180039 | | | | First draft, presented to TSG SA for information | 1.0.0 |
138
+ | 2018-09 | SA#81 | SP-180849 | | | | For approval | 2.0.0 |
139
+ | 2018-09 | SA#81 | | | | | Approved, under change control | 15.0.0 |
140
+ | 2020-07 | SA#88-e | | | | | Upgrade on freeze of Release 16 | 16.0.0 |
141
+ | 2022-03 | SA#95-e | | | | | Upgrade on freeze of Release 17 | 17.0.0 |
142
+ | 2023-03 | SA#99 | SP-230328 | 0003 | | A | Correction of specs list URL | 17.1.0 |
143
+ | 2024-03 | SA#103 | - | - | - | - | Update to Rel-18 version (MCC) | <b>18.0.0</b> |
144
+ | 2025-03 | SA#107 | SP-250227 | 0004 | 1 | F | Correction of Release | 18.1.0 |
marked/Rel-18/21_series/21900/raw.md ADDED
The diff for this file is too large to render. See raw diff
 
marked/Rel-18/23_series/23014/5fb340ad68b0c71df0b56698b137e35b_img.jpg ADDED

Git LFS Details

  • SHA256: 102a0ea618bdd116de489c17735c4e5978504f6625a8f70fc45242411e7902a3
  • Pointer size: 129 Bytes
  • Size of remote file: 9.53 kB
marked/Rel-18/23_series/23014/64662465bba247703fdec49c8f3309f9_img.jpg ADDED

Git LFS Details

  • SHA256: c8c7cc8413a242e2f968cccb966c52409059e44dcc1f7ab5d2fb76cb6b30b489
  • Pointer size: 129 Bytes
  • Size of remote file: 5.7 kB
marked/Rel-18/23_series/23014/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg ADDED

Git LFS Details

  • SHA256: 69981c3e8f82291ba460c7dad242fcbb6b04295f37bdfee95546cf0aaf369b46
  • Pointer size: 131 Bytes
  • Size of remote file: 107 kB
marked/Rel-18/23_series/23014/c9d8a18a6137ad054b841d7a614afb48_img.jpg ADDED

Git LFS Details

  • SHA256: d3337e7c7add9fe6761a682b8e5200b1dbca82a8e42e64ea158e246510d20f68
  • Pointer size: 130 Bytes
  • Size of remote file: 56 kB
marked/Rel-18/23_series/23014/d0abac95583b52a3b35f74a215567334_img.jpg ADDED

Git LFS Details

  • SHA256: 032321e6541fadb49b9200b6f8e68a3c5104a39acf835ac0e4bfb1c46f687079
  • Pointer size: 130 Bytes
  • Size of remote file: 54.8 kB
marked/Rel-18/23_series/23014/e6df2733626a85205c1db682e6259c46_img.jpg ADDED

Git LFS Details

  • SHA256: 56ce2450c2044f2f1e23e83927a4d3e7bebfe6a1526f5e8b78a2cf272c15fe10
  • Pointer size: 131 Bytes
  • Size of remote file: 144 kB
marked/Rel-18/23_series/23032/07f537f57749b75157f742525e6a8dbc_img.jpg ADDED

Git LFS Details

  • SHA256: 3f427cd882f289af91453f429e1e5451a6f13849cc8e18b7670f8b370df86a8f
  • Pointer size: 129 Bytes
  • Size of remote file: 7.3 kB
marked/Rel-18/23_series/23032/0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg ADDED

Git LFS Details

  • SHA256: 938b2d449ebe765b4a4d135058df0ea04cf80587366886790808db90e6ed0fa0
  • Pointer size: 130 Bytes
  • Size of remote file: 17.2 kB
marked/Rel-18/23_series/23032/0ee9d674085524d589646a6c3fb21ec3_img.jpg ADDED

Git LFS Details

  • SHA256: 30eeaada668b7b4ccac0d56b0cfcb27e43002baf7efa1fbb69117979a39f9d17
  • Pointer size: 130 Bytes
  • Size of remote file: 21.9 kB
marked/Rel-18/23_series/23032/10953d657a5f47fdc829a800419dd370_img.jpg ADDED

Git LFS Details

  • SHA256: 7664646e8d2177cbbb8c6d4be2753623fb797e3b513075aacc36160df5e21d75
  • Pointer size: 130 Bytes
  • Size of remote file: 21.6 kB
marked/Rel-18/23_series/23032/18442e4e239480f0c3c95b547aa8fde2_img.jpg ADDED

Git LFS Details

  • SHA256: 372cf3d762cee9e013aa2d6c4da0167e21924a958fcc5800ddfedffa80d2bcf4
  • Pointer size: 130 Bytes
  • Size of remote file: 15.8 kB
marked/Rel-18/23_series/23032/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg ADDED

Git LFS Details

  • SHA256: 3303c6b52f9b4593c382cb32ee9968cf3e6f522658e2c85354b9874e9d34a96b
  • Pointer size: 130 Bytes
  • Size of remote file: 17.5 kB
marked/Rel-18/23_series/23032/34fccc54a5930cbdf0f07e02c3745e35_img.jpg ADDED

Git LFS Details

  • SHA256: d1cb6ace27aa507ec217d997a65ead2e87ef61935eadb7f966fa7314786f468e
  • Pointer size: 130 Bytes
  • Size of remote file: 17.1 kB
marked/Rel-18/23_series/23032/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg ADDED

Git LFS Details

  • SHA256: e151a8e5142820cbc9d9efcb5fa611a9c28350e178e0120b6b743a21608c6852
  • Pointer size: 130 Bytes
  • Size of remote file: 27.5 kB
marked/Rel-18/23_series/23032/474a819357587e34949a3e110ff19b30_img.jpg ADDED

Git LFS Details

  • SHA256: fab36e541c892af89c7db83de068c003f34cc730790537f29a85dd5bdf5ab495
  • Pointer size: 131 Bytes
  • Size of remote file: 106 kB
marked/Rel-18/23_series/23032/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg ADDED

Git LFS Details

  • SHA256: 336351255f55d02220db9b68b7aaad507eb522205a9989d6d365025e2acc1200
  • Pointer size: 130 Bytes
  • Size of remote file: 44.3 kB
marked/Rel-18/23_series/23032/53298644c66fa3fca81d6eec654afec5_img.jpg ADDED

Git LFS Details

  • SHA256: 97b43ba4ec681a36dd98a48cd043313725737b2192a5f50d7e3c05a4b2e06852
  • Pointer size: 130 Bytes
  • Size of remote file: 21.6 kB
marked/Rel-18/23_series/23032/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg ADDED

Git LFS Details

  • SHA256: a9031614ada06e02a60fd231058763b5076d05190ebd3e7665a247f935f80834
  • Pointer size: 130 Bytes
  • Size of remote file: 17 kB
marked/Rel-18/23_series/23032/64662465bba247703fdec49c8f3309f9_img.jpg ADDED

Git LFS Details

  • SHA256: b8af86a1d11a9116305e4c63e470ce1a961ea0a959b39f7282f7dd03e0719f64
  • Pointer size: 129 Bytes
  • Size of remote file: 8.63 kB
marked/Rel-18/23_series/23032/6786ba12e3eceb3cf496108a02a37f09_img.jpg ADDED

Git LFS Details

  • SHA256: ba019a1ffdc9263625a3457b26de1ba3aee986efa8681542a58cc41a0f9a4ba6
  • Pointer size: 130 Bytes
  • Size of remote file: 47.6 kB
marked/Rel-18/23_series/23032/73dff6b45b2b9ffd384bab3235f869af_img.jpg ADDED

Git LFS Details

  • SHA256: 068a879a7a07fad3e8531fd9e72ddf68137ac8c62659d5bc5ea4d917274a57c0
  • Pointer size: 130 Bytes
  • Size of remote file: 36.1 kB
marked/Rel-18/23_series/23032/7d2d1d3870cd224c4430d19334557716_img.jpg ADDED

Git LFS Details

  • SHA256: 70ab7997110cf3c5d17906fd9ed4cfa1363d467724726268c0211d7b865e8f62
  • Pointer size: 131 Bytes
  • Size of remote file: 104 kB
marked/Rel-18/23_series/23032/b77cd8b2f763af8d453537177ac5942f_img.jpg ADDED

Git LFS Details

  • SHA256: c25bdd833d2bc9d4d32349a6df803bdd013c67e3be28f6279bb47108255bd1a2
  • Pointer size: 130 Bytes
  • Size of remote file: 18.8 kB
marked/Rel-18/23_series/23032/d8b92bdf09d07cb6c7b6961db9f6c4bb_img.jpg ADDED

Git LFS Details

  • SHA256: 172c3e5e1b6973266621008b4d7661e53f33ced5741645b559ef59f70fbebc16
  • Pointer size: 130 Bytes
  • Size of remote file: 27.9 kB
marked/Rel-18/23_series/23032/d9a8b92ba7fc661ebe736ba3e4088eb5_img.jpg ADDED

Git LFS Details

  • SHA256: d547b22be6702372bc1b1eae3feb2db7a69204f52ee9a05a6082321cf1789fcf
  • Pointer size: 130 Bytes
  • Size of remote file: 15.4 kB
marked/Rel-18/23_series/23032/e15f9dc3ef94138759781dc3c620b48d_img.jpg ADDED

Git LFS Details

  • SHA256: a5b10cc31dc3ac9bf9731fe755707026a85c70dd70e517af31ef44edc1d1e2fa
  • Pointer size: 130 Bytes
  • Size of remote file: 12 kB
marked/Rel-18/23_series/23035/5fb340ad68b0c71df0b56698b137e35b_img.jpg ADDED

Git LFS Details

  • SHA256: 8b42d116d8c2d814c86377d52a84e0f5d4ef04fd6b66457e5edf7e3dd2ea4cb7
  • Pointer size: 129 Bytes
  • Size of remote file: 9.37 kB
marked/Rel-18/23_series/23035/64662465bba247703fdec49c8f3309f9_img.jpg ADDED

Git LFS Details

  • SHA256: 9faff289c269ff2b0f41d2267933e4cc43c36969d345e79d9a3b32ee4d7b5dbd
  • Pointer size: 129 Bytes
  • Size of remote file: 5.42 kB
marked/Rel-18/23_series/23057/13fde41de77bf026013a0b81684d1fc9_img.jpg ADDED

Git LFS Details

  • SHA256: 7fde80314d0caa8df66b4cdebed4a6824f941010214ffb6ce4a3c16741ac9f92
  • Pointer size: 130 Bytes
  • Size of remote file: 61.7 kB
marked/Rel-18/23_series/23057/17f0cf80b9c38adb460d4ca836960da7_img.jpg ADDED

Git LFS Details

  • SHA256: 83b687636bfe8dbfdd796562bbeee3ee7c41bbc9232c70893f13d31de19fd210
  • Pointer size: 130 Bytes
  • Size of remote file: 57.6 kB
marked/Rel-18/23_series/23057/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg ADDED

Git LFS Details

  • SHA256: 58a533de35371018eb6c99cb081de9e6a3dadec59202b3d2c67fcf6590b343f6
  • Pointer size: 130 Bytes
  • Size of remote file: 28.2 kB
marked/Rel-18/23_series/23057/392a79ccd95e682ccd08f35ab2e64144_img.jpg ADDED

Git LFS Details

  • SHA256: f8b2da84ddeaedce337975787ec5a59098500e9639db0488bc76bcb7cf12ca82
  • Pointer size: 130 Bytes
  • Size of remote file: 53.8 kB
marked/Rel-18/23_series/23057/42d3842485845d9f6e511e6526061a55_img.jpg ADDED

Git LFS Details

  • SHA256: 393c7ffdfb5a443ebe3778144e573ec18dfa6d58fd26537e2d33e99fbecefd4c
  • Pointer size: 130 Bytes
  • Size of remote file: 29.4 kB
marked/Rel-18/23_series/23057/44c649b1c110b4cd617810ae17342927_img.jpg ADDED

Git LFS Details

  • SHA256: 11ac9de8fbe9e29718d6f5b5ebc477ef5a457f340fdab4c53345517485d3b4f0
  • Pointer size: 130 Bytes
  • Size of remote file: 50.7 kB
marked/Rel-18/23_series/23057/64662465bba247703fdec49c8f3309f9_img.jpg ADDED

Git LFS Details

  • SHA256: 62b254a3e8f8b851eae1619e301780f412a5cc516e8474bfa79002d88e3c7157
  • Pointer size: 129 Bytes
  • Size of remote file: 7.65 kB
marked/Rel-18/23_series/23057/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg ADDED

Git LFS Details

  • SHA256: cc1b7bd84b1e1feb95088491a36449b1c1298c1348c2a7a69baf020db906454f
  • Pointer size: 131 Bytes
  • Size of remote file: 109 kB
marked/Rel-18/23_series/23057/822e033872d5ab16e861571f47b81ba7_img.jpg ADDED

Git LFS Details

  • SHA256: 38627cb4e369b4d1cb3a4c24d28ebefe53f2b3a651043735e4d1236ef3989c39
  • Pointer size: 130 Bytes
  • Size of remote file: 34 kB
marked/Rel-18/23_series/23057/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg ADDED

Git LFS Details

  • SHA256: 791f504b47d340713d62f1273c76f239c2cacbb4b9a09ff76e7cf83145481f8c
  • Pointer size: 131 Bytes
  • Size of remote file: 146 kB
marked/Rel-18/23_series/23057/9e8ebf03cae78f4f81b697548c2d7250_img.jpg ADDED

Git LFS Details

  • SHA256: 800d8d7309338bd6a55679e442653bc315b8061c4370a37ed6fd766dcf29cbb8
  • Pointer size: 131 Bytes
  • Size of remote file: 153 kB
marked/Rel-18/23_series/23057/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg ADDED

Git LFS Details

  • SHA256: 3edc5c8340adfebdb6fb523cc50fb07a82f63c2ac223cd4547871d28ecd4acd7
  • Pointer size: 131 Bytes
  • Size of remote file: 104 kB
marked/Rel-18/23_series/23057/a0e8fe7862a6d7341faf5dac275277cc_img.jpg ADDED

Git LFS Details

  • SHA256: eb16433800e01bbb904487e7c49e8ada250b9b72afe481f485acedd59cef3513
  • Pointer size: 130 Bytes
  • Size of remote file: 73.5 kB
marked/Rel-18/23_series/23057/b63f41ca262d8ce9ef8affb62607f32b_img.jpg ADDED

Git LFS Details

  • SHA256: 8f337c95784d83f13e2e4a9d4d07df1a68ca6588ebe6d1c63d22fbc5884b3fbd
  • Pointer size: 130 Bytes
  • Size of remote file: 44.6 kB
marked/Rel-18/23_series/23057/cf018d13814389b0bd7f94a2f9bb812a_img.jpg ADDED

Git LFS Details

  • SHA256: 321414e92dddf565dc4c3112931f6bc521926e1d06813090937822e8e0f0fb9f
  • Pointer size: 130 Bytes
  • Size of remote file: 36.1 kB
marked/Rel-18/23_series/23057/ddee3e67e0dfc22e25188fa635a19558_img.jpg ADDED

Git LFS Details

  • SHA256: 452bfa677b47b4ea05870924e61733adff7c2ba057bb38c2adc4391a10a98b4a
  • Pointer size: 131 Bytes
  • Size of remote file: 140 kB