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
  • ODT export
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • ODT export
  • 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 [2024/12/24 06:47] – [Authentication and Authorization] elena.krasnobryzhen:dpi:epdg:integration_cases [2026/03/12 08:10] (current) – elena.krasnobryzh
    Line 1: Line 1:
     {{indexmenu_n>4}} {{indexmenu_n>4}}
    -======Integration Cases of SSG EPDG with Operator's IS====== +======Integration Cases of SSG ePDG with Operator's IS====== 
    -To implement SSG EPDG it is required to set up interaction with the following systems of the telecom operator via Diameter protocol:+To implement SSG ePDG it is required to set up interaction with the following systems of the telecom operator via Diameter protocol:
       * AAA server - for authentication and authorization;   * AAA server - for authentication and authorization;
       * HSS (only if AAA server is absent);   * HSS (only if AAA server is absent);
    Line 9: Line 9:
      
     =====Authentication and Authorization===== =====Authentication and Authorization=====
    -The authorization module (MA, Authorization management) of the SSG EPDG is responsible for authorization of the operator's subscriber. The settings and configuration of this module allow to support different integration scenarios depending on the interfaces that the operator is willing to provide.+The authorization module (MA, Authorization management) of the SSG ePDG is responsible for authorization of the operator's subscriber. The settings and configuration of this module allow to support different integration scenarios depending on the interfaces that the operator is willing to provide.
     ====Case 1. Authorization on AAA (Diameter protocol, SWm interface)==== ====Case 1. Authorization on AAA (Diameter protocol, SWm interface)====
     **Conditions:**\\ **Conditions:**\\
    Line 29: Line 29:
      
     ====Option. AAA-proxy Mode (SWa (SWm) interface for External IS)==== ====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.+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===== =====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.+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)==== ====Case 1. Work via Standard Interface (S2b interface)====
     **Conditions:**\\ **Conditions:**\\
    -Operator's PGW supports EPDG's native interface - S2b.+Operator's PGW supports ePDG's native interface - S2b.
      
     **Process:**\\ **Process:**\\