Differences
This shows you the differences between two versions of the page.
| en:dpi:epdg:basic_processes [2024/09/26 15:29] – created - external edit 127.0.0.1 | en:dpi:epdg:basic_processes [2026/03/12 08:09] (current) – elena.krasnobryzh | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| When operating using the S5/S8 interface, client requests are used similar to the SGW component. | When operating using the S5/S8 interface, client requests are used similar to the SGW component. | ||
| - | When operating using the S2b interface, client requests of the EPDG component are used. | + | When operating using the S2b interface, client requests of the ePDG component are used. |
| - | When interacting with the PGW component, the gateway uses the selected interface to create GTP-U tunnels via the GTP-C protocol for authorized gateway clients between the EPDG and the packet network served by the PGW. Traffic exchange between associated SWn tunnels of gateway clients and GTP-U tunnels is provided via the GTP-U protocol according to specified QoS. | + | When interacting with the PGW component, the gateway uses the selected interface to create GTP-U tunnels via the GTP-C protocol for authorized gateway clients between the ePDG and the packet network served by the PGW. Traffic exchange between associated SWn tunnels of gateway clients and GTP-U tunnels is provided via the GTP-U protocol according to specified QoS. |
| Interaction requests with the PGW component via the GTP-C protocol can be load-balanced across client connections to multiple servers. | Interaction requests with the PGW component via the GTP-C protocol can be load-balanced across client connections to multiple servers. | ||