EPDG implementation plan » History » Version 25
pespin, 02/07/2024 03:18 PM
1 | 2 | laforge | {{>toc}} |
---|---|---|---|
2 | |||
3 | 1 | laforge | h1. EPDG implementation plan |
4 | 2 | laforge | |
5 | h2. The big picture |
||
6 | |||
7 | Ideally, we want to reuse existing code whenever possible, rather than reinvent the wheel. Time will tell, if this works out or if we have to rewrite more of it. |
||
8 | * StrongSwan charon for handling IKEv2 and managing the IPsec SAs in the kernel IPsec |
||
9 | * Erlang DIAMETER application for all the related interfaces |
||
10 | * Erlang gtplib for S2b |
||
11 | |||
12 | This means we will have two major "applications" running: |
||
13 | * charon |
||
14 | * ePDG (likely in Erlang) |
||
15 | |||
16 | Between those two we will need some kind of non-standard, custom interface. For now I've called it "CEAI" for (Charon External AKA Interface) |
||
17 | |||
18 | h2. Control Plane |
||
19 | |||
20 | * *red* color indicates elements / interfaces to be implemented. |
||
21 | |||
22 | {{graphviz_link() |
||
23 | digraph G { |
||
24 | rankdir=LR; |
||
25 | subgraph cluster_swan { |
||
26 | label = "StrongSWAN domain"; |
||
27 | charon; |
||
28 | } |
||
29 | subgraph cluster_erlang { |
||
30 | label = "Erlang domain"; |
||
31 | ePDG [color=red]; |
||
32 | AAA [label="3GPP AAA Server", color=red]; |
||
33 | } |
||
34 | HSS; |
||
35 | PGW; |
||
36 | 14 | pespin | PCRF; |
37 | 2 | laforge | UE; |
38 | |||
39 | charon -> ePDG [label="CEAI", color=red]; |
||
40 | |||
41 | UE -> charon [label="IKEv2"]; |
||
42 | ePDG -> AAA [label="SWm (DIAMETER)", color=red]; |
||
43 | AAA -> HSS [label="SWx (DIAMETER)", color=red]; |
||
44 | 14 | pespin | PGW -> AAA [label="S6b (DIAMETER)", color=red]; |
45 | 2 | laforge | |
46 | ePDG -> PGW [label="S2b (GTPv2C)", color=red]; |
||
47 | 1 | laforge | ePDG -> PCRF [label="Gxb", color=red, style=dashed]; |
48 | PGW -> PCRF [label="Gx (DIAMETER)"]; |
||
49 | 14 | pespin | |
50 | {rank=same; PCRF; HSS} |
||
51 | 2 | laforge | } |
52 | }} |
||
53 | |||
54 | h2. User Plane |
||
55 | |||
56 | * *red* color indicates elements / interfaces to be implemented. |
||
57 | * *blue* color indicates control-plane elements controlling the user plane |
||
58 | |||
59 | {{graphviz_link() |
||
60 | digraph G { |
||
61 | rankdir=LR; |
||
62 | |||
63 | subgraph cluster_swan { |
||
64 | label = "StrongSWAN domain"; |
||
65 | { rank=same; |
||
66 | ipsec [label="Linux kernel\nIPsec"]; |
||
67 | charon [color=blue]; |
||
68 | } |
||
69 | charon -> ipsec [label="netlink", color=blue]; |
||
70 | } |
||
71 | subgraph cluster_erlang { |
||
72 | label = "Erlang domain"; |
||
73 | { rank=same |
||
74 | gtp [label="Linux kernel\nGTP"]; |
||
75 | ePDG [color="blue"]; |
||
76 | } |
||
77 | ePDG -> gtp [label="netlink", color=blue]; |
||
78 | } |
||
79 | PGW; |
||
80 | UE; |
||
81 | |||
82 | UE -> ipsec [label="ESP/UDP"]; |
||
83 | ipsec->gtp [label="kernel IP stack"]; |
||
84 | gtp -> PGW [label="S2b (GTPv1U)", color=red]; |
||
85 | } |
||
86 | }} |
||
87 | |||
88 | 16 | laforge | h3. At system startup |
89 | |||
90 | * set the various routes |
||
91 | * on @epdg@ node |
||
92 | 17 | laforge | ** osmo-epdg creates the @gtp0@ net-device (in GTP_ROLE_SGSN) via netlink |
93 | 16 | laforge | * on @epc@ node |
94 | ** open5gs-upf creates the @tun0@ net-device |
||
95 | |||
96 | h3. When a user authenticates via IPsec |
||
97 | |||
98 | * on @epdg@ node |
||
99 | ** osmo-epdg creates a new GTP tunnel entry within the GTP link |
||
100 | 18 | laforge | *** GTPA_PEER_ADDRESS/ADDR6 = pgw-ip |
101 | *** GTPA_MS_ADDRESS/MS_ADDR6 = ue-ip (inner) |
||
102 | *** GTPA_I_TEI = epdg-teid |
||
103 | *** GTPA_O_TEI = pgw-teid |
||
104 | 16 | laforge | * on @epc@ node |
105 | ** open5gs-upf creates a new GTP tunnel entry within its internal state tables |
||
106 | |||
107 | h3. Uplink traffic (e.g. from UE to P-CSCF) |
||
108 | |||
109 | * one @epdg@ node |
||
110 | ** IPsec-encapsulated traffic from the UE side enters as IPv6-in-ESP-in-UDP-in-IP[v4/v6] on the public/internet-facing side |
||
111 | ** kernel-IPsec (configured by strongswan) will transform (decrypt, ...) the traffic |
||
112 | *** we configure strongswan to mark the ipsec-originated traffic with a certain fwmark |
||
113 | ** traffic with that fwmark is routed (using a statically configured @ip rule@) towards the @gtp0@ net-device (created by osmo-epdg at startup) |
||
114 | ** linux kernel GTP tunnel module |
||
115 | *** looks up the in-kernel table to determine destination TEID and destination IP address based on the MS-side source address |
||
116 | *** encapsulates packet in GTP header and sends it through the in-kernel UDP socket to the PGW |
||
117 | * on the @epc@ node |
||
118 | ** (open5gs-)pgw matches inbound packet based on (dest-ip + TEID) with its internal state table |
||
119 | ** (open5gs-)pgw decapsulates packet from GTP header |
||
120 | ** (open5gs-)pgw exposes inner IPv6 packet on @tun0@ net-device |
||
121 | ** linux kernel routes packet towards P-CSCF (inner IPv6 dest IP address as originally set by UE) |
||
122 | * on the @ims@ node |
||
123 | ** linux kernel routes packet towards local P-CSCF socket |
||
124 | |||
125 | h3. Downlink traffic (e.g. from P-CSCF to UE) |
||
126 | |||
127 | * on @ims@ node |
||
128 | ** IPv6 packet from P-CSCF is sent to UE IPv6 address |
||
129 | ** large network route (for all UE) points towards @epc@ node |
||
130 | * on @epc@ node |
||
131 | ** traffic to UE IPv6 is routed into @tun0@ net-device |
||
132 | ** (open5gs-)pgw looks up destination-ip and TEID |
||
133 | ** (open5gs-)pwg encapsulates packet with GTP-U header and sends it via UDP socket |
||
134 | ** linux kernel routes it towards the ePDG |
||
135 | * on @epdg@ node |
||
136 | ** linux kernel routes GTP packet to locally bound UDP socket and detects the kernel GTP driver is bound to that socket |
||
137 | ** linux kernel GTP driver performs lookup based on dest-ip and TEID |
||
138 | ** linux kernel de-capsulates GTP packet and exposes inner packet on @gtp0@ net-device |
||
139 | ** linux kernel IPsec code applies transformation (crypto) and ESP-in-UDP-encapsulation |
||
140 | * packet is routed towards UE |
||
141 | 5 | lynxis | |
142 | h2. Authentication |
||
143 | |||
144 | !ipsec_auth.png! |
||
145 | |||
146 | 3 | laforge | h2. 3GPP Interfaces and Procedures |
147 | 2 | laforge | |
148 | h3. ePDG |
||
149 | |||
150 | 20 | pespin | h4. IKEv2 to UE |
151 | |||
152 | * TS 33.402 section 8 |
||
153 | * TS 24.302 chapter 7 |
||
154 | 23 | pespin | * RFC 4187 |
155 | 25 | pespin | * RFC 4301 |
156 | 24 | pespin | * RFC 4555 |
157 | 23 | pespin | * RFC 5996 |
158 | 22 | pespin | * RFC 7296 |
159 | 1 | laforge | |
160 | 6 | lynxis | h4. S2b to PGW (GTPv2C) [TS 29.274] |
161 | 2 | laforge | |
162 | h5. Create Session Request / Response |
||
163 | |||
164 | h5. Delete Session Request / Response |
||
165 | |||
166 | h5. Modify Bearer Request / Respone (not needed?) |
||
167 | |||
168 | h5. Modify Bearere Command (not needed?) |
||
169 | |||
170 | h5. Bearer Resource Command (not needed?) |
||
171 | |||
172 | h5. Create Bearer Request / Response |
||
173 | |||
174 | h5. Update Bearer Request / Response (not needed?) |
||
175 | |||
176 | |||
177 | 9 | pespin | h4. SWm to AAA (DIAMETER) [3GPP TS 29.273] |
178 | 2 | laforge | |
179 | h5. Diameter-EAP-Request (DER) / Diameter-EAP-Response (DEA) |
||
180 | |||
181 | h5. Diameter-AA-Request (AAR) / Diameter-AA-Response (AAA) |
||
182 | |||
183 | h5. Session-Termination-Request (STR) / Session-Termination-Answer (STA) |
||
184 | |||
185 | h5. Re-Auth-Requst (RAR) / Re-Auth-Answer (RAA) |
||
186 | |||
187 | h5. Abort-Session-Request (ASR) / Abort-Session-Answer (ASA) |
||
188 | |||
189 | 12 | pespin | h4. SWu to UE (IKEv2, ESP) [3GPP TS 33.402] |
190 | 2 | laforge | |
191 | 11 | pespin | * Related: https://fabricioapps.blogspot.com/2017/10/untrusted-non-3gpp-ip-access-swu-ikev2.html |
192 | 2 | laforge | |
193 | h4. Gxb to PCRF (not needed?) |
||
194 | |||
195 | h3. 3GPP AAA Server |
||
196 | |||
197 | 10 | pespin | h4. SWx to HSS (DIAMETER) [3GPP TS 29.273 sec 8, 3GPP TS 23.402 sec 12] |
198 | 2 | laforge | |
199 | h5. Push-Profile-Request (PPR) / Push-Profile-Answer (PPA) |
||
200 | |||
201 | h5. Registration-Termination-Request (RTR) / Registration-Termination-Answer (RTA) |
||
202 | |||
203 | h5. Multimedia-Auth-Request (MAR) / Multimedia-Auth-Answer (MAA) |
||
204 | |||
205 | 7 | pespin | * 3GPP TS 29.273 8.2.2.1 |
206 | 8 | pespin | * https://www.etsi.org/deliver/etsi_ts/129200_129299/129273/17.06.00_60/ts_129273v170600p.pdf |
207 | 7 | pespin | * https://dstest.info/DiaDict/Dictionary/Multimedia-Auth-Request_SWx.html |
208 | |||
209 | 2 | laforge | h5. Server-Assignment-Request (SAR) / Server-Assignment-Answer (SAA) |
210 | |||
211 | 13 | pespin | h4. S6b to PGW (DIAMETER) [3GPP TS 29.273 sec 9] |
212 | 2 | laforge | |
213 | 13 | pespin | * https://osmocom.org/issues/6229 |
214 | 2 | laforge | |
215 | h4. SWm to ePDG (DIAMETER) |
||
216 | |||
217 | 1 | laforge | see above. |
218 | 3 | laforge | |
219 | 4 | lynxis | h3. custom Interfaces / Procedures |
220 | |||
221 | 19 | lynxis | h4. CEAI / GSUP |
222 | 4 | lynxis | |
223 | 19 | lynxis | All messages must contain the TLV message class using the value IPSEC_EPDG / 5. |
224 | 1 | laforge | |
225 | 19 | lynxis | h5. Send Authentication Information Request |
226 | |||
227 | * Request the Auth Tuples to authenticate a UE. osmo-epdg will use SWx to request the information from the HSS. |
||
228 | * Direction: Send from strongswan to osmo-edpg |
||
229 | |||
230 | h5. Send Authentication Information Result |
||
231 | |||
232 | * Direction: Send from osmo-epdg to strongswan |
||
233 | |||
234 | h5. Send Authentication Information Error |
||
235 | |||
236 | * Direction: Send from osmo-epdg to strongswan |
||
237 | |||
238 | |||
239 | h5. Update Location Request |
||
240 | |||
241 | * Authorization of the UE to use the ePDG and requested APN/PGW. osmo-epdg will use SWx to update the HSS and authorize in the same request the UE + APN/PGW. |
||
242 | * Direction: Send from strongswan to osmo-edpg |
||
243 | |||
244 | h5. Update Location Result |
||
245 | |||
246 | * Direction: Send from osmo-epdg to strongswan |
||
247 | |||
248 | h5. Update Location Error |
||
249 | |||
250 | * Direction: Send from osmo-epdg to strongswan |
||
251 | |||
252 | |||
253 | h5. Tunnel Request |
||
254 | |||
255 | * strongswan ask the osmo-epdg to create the GTP Tunnel towards the PGW. |
||
256 | * Direction: Send from strongswan to osmo-edpg |
||
257 | |||
258 | h5. Tunnel Result |
||
259 | |||
260 | * Direction: Send from osmo-epdg to strongswan |
||
261 | |||
262 | h5. Tunnel Error |
||
263 | |||
264 | * Direction: Send from osmo-epdg to strongswan |
||
265 | 1 | laforge | |
266 | 21 | pespin | h5. Purge MS Request |
267 | 1 | laforge | |
268 | 21 | pespin | * strongswan asks the osmo-epdg to tear down the UE session due to UE disconnection (close ipsec tunnel). |
269 | * Direction: Send from strongswan to osmo-epdg |
||
270 | 1 | laforge | |
271 | 21 | pespin | h5. Purge MS Result |
272 | |||
273 | * Direction: Send from osmo-epdg to strongswan |
||
274 | |||
275 | h5. Purge MS Error |
||
276 | |||
277 | * Direction: Send from osmo-epdg to strongswan |
||
278 | |||
279 | h5. Cancel Location Request |
||
280 | |||
281 | * The HSS/PGW asked to terminate the session since the UE moved somewhere else. |
||
282 | * Direction: Send from osmo-epdg to strongswan |
||
283 | |||
284 | h5. Cancel Location Result |
||
285 | |||
286 | * Direction: Send from strongswan to osmo-epdg |
||
287 | |||
288 | h5. Cancel Location Error |
||
289 | |||
290 | * Direction: Send from strongswan to osmo-epdg |
||
291 | 19 | lynxis | |
292 | |||
293 | h4. Related information links |
||
294 | 15 | pespin | |
295 | * https://www.cisco.com/c/en/us/td/docs/wireless/asr_5000/21-23/PGW-Admin/21-23-pgw-admin/21-16-PGW-Admin_chapter_011001.html |