You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

In this section:


The Access, or User Network Interface (UNI), refers to the service control interface between the user devices and the transport network (core network), and connects subscribers to their immediate service provider. The 

Unable to show "metadata-from": No such page "_space_variables"
 acts as an Access
Unable to show "metadata-from": No such page "_space_variables"
to protect a core/server from a range of individual devices which must communicate through the
Unable to show "metadata-from": No such page "_space_variables"
to achieve connectivity and service to the core network.

As a guardian of the UNI interface, the

Unable to show "metadata-from": No such page "_space_variables"
:

  • Protects the internal resources of the core network (example Application Server) from malicious attacks and genuine but high traffic levels.
  • Acts as B2B UA to bridge/bond the ingress/egress SIP sessions while maintaining distinct networks at the lower layers.
  • Participates in authentication to ensure only approved and well behaved subscribers/UEs achieve service.
  • Provides facilities for protocol repair and adaptation.
  • Protects against DoS (Denial of Service attacks).
  • Polices/enforces bandwidth and resource utilization.
  • Facilitates NAT traversal.
  • Routes UE registration request to an appropriate AS.
  • Provides encryption services.

A Service Provider can use multiple

Unable to show "metadata-from": No such page "_space_variables"
platforms to guard its borders against User Equipment (UE) that commonly resides in untrusted public and private networks. For a UE to access a service provider’s network, it must first meet
Unable to show "metadata-from": No such page "_space_variables"
security criteria before being allowed to pass traffic through the
Unable to show "metadata-from": No such page "_space_variables"
and on to the service provider network. As long as the
Unable to show "metadata-from": No such page "_space_variables"
address is preconfigured on the UE, whenever a request originates from the
Unable to show "metadata-from": No such page "_space_variables"
, traffic passes seamlessly through the configured
Unable to show "metadata-from": No such page "_space_variables"
.

Access - (UNI) Deployment



  • No labels