Integration Cases of SSG EPDG with Operator's IS [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks

    • Differences

    This shows you the differences between two versions of the page.

    Link to this comparison view

    Both sides previous revisionPrevious revision
    en:dpi:epdg:integration_cases:start [2024/05/13 15:52] – elena.krasnobryzhen:dpi:epdg:integration_cases:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
    Line 1: Line 1:
    -{{indexmenu_n>4}} 
    -======Integration Cases of SSG EPDG with Operator's IS====== 
    -To deploy SSG EPDG, integration with the following telecommunications operator systems needs to be configured: 
    -  * AAA server - for authentication and authorization; 
    -  * HSS (only if AAA server is absent); 
    -  * PGW - for receiving signaling and voice traffic. 
    - 
    -Below are several possible integration cases. 
    - 
    -=====Authentication and Authorization===== 
    -//The authorization of the client in EPDG is handled by the Authorization Management Module (AM), which allows implementing several cases on the operator's side.// 
    - 
    -====Case 1. Authorization on AAA (Diameter protocol, SWm interface)==== 
    -**Conditions:**\\ 
    -Operator's AAA operates via the standard SWm interface. 
    - 
    -**Process:**\\ 
    -Authorization Management (AM) module requests authorization from Operator's AAA via SWm, then AAA interacts with HSS via SWx, and during a call, interacts with PGW via S6b. 
    - 
    -{{ :dpi:epdg:aaa_authorization.png?nolink&500 |}} 
    - 
    -====Case 2. Authorization on HSS (Diameter protocol, SWx interface)==== 
    -**Conditions:**\\ 
    -The operator does not have its own AAA server; in this case, the AM obtains authorization directly from the Operator's HSS via SWx. 
    - 
    -**Process:**\\ 
    -During a call, the AM replaces Operator's AAA: Operator's PGW queries it for authorization confirmation via the S6b interface, the AM queries HSS via SWx. 
    - 
    -{{ :dpi:epdg:authorization_without_aaa.png?nolink&450 |}} 
    - 
    -====Option. AAA-proxy Mode (SWa (SWm) interface for External IS)==== 
    -The operator does not have its own AAA server, but there is some IS, for which it is needed, for example, TWAN or another EPDG. In this case, SSG EPDG can accept requests via the SWm interface and perform authorization on HSS and PGW via standard SWx and S6b interfaces. 
    - 
    -=====Tunneling===== 
    -The Tunneling Management Module (TMM) is responsible for organizing tunnels between EPDG Core and Operator's PGW. Several cases can be implemented on the operator's side with its help. 
    - 
    -====Case 1. Work via Standard Interface (S2b interface)==== 
    -**Conditions:**\\ 
    -Operator's PGW supports EPDG's native interface - S2b. 
    - 
    -**Process:**\\ 
    -Signaling traffic from EPDG to PGW flows through the GTP-C tunnel via the native S2b interface. User Plane (voice traffic) flows through the GTP-U tunnel. 
    - 
    -{{ :dpi:epdg:s2b_tunneling.png?nolink&450 |}} 
    - 
    -====Case 2. SGW Emulation (S5/S8 interface)==== 
    -**Conditions:**\\ 
    -Operator's PGW does not support S2b, only supports S5/S8. 
    - 
    -**Process:**\\ 
    -In this case, TMM emulates the operation of SGW and communicates with PGW via the S5/S8 interface. User Plane (voice traffic) flows through the GTP-U tunnel. 
    - 
    -{{ :dpi:epdg:s5s8_tunneling.png?nolink&450 |}}