Next Generation Networks Next Generation Networks QoS Control - - PowerPoint PPT Presentation

▶
next generation networks next generation networks qos
SMART_READER_LITE
LIVE PREVIEW

Next Generation Networks Next Generation Networks QoS Control - - PowerPoint PPT Presentation

Nov 02, 2023 461 likes •666 views

I nternational Telecom m unication Union ITU-T Next Generation Networks Next Generation Networks QoS Control Architectures and QoS Control Architectures and Protocols Protocols Keith Mainwaring Technical Leader, Cisco S ystems I TU-T W

slide-1
SLIDE 1

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6

I nternational Telecom m unication Union

ITU-T

Next Generation Networks Next Generation Networks QoS Control Architectures and QoS Control Architectures and Protocols Protocols Keith Mainwaring

Technical Leader, Cisco S ystems

slide-2
SLIDE 2

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2

ITU-T

Outline of NGN QoS Control ( ETSI term inology)

UE NASS NASS P-CSCF AF (e.g. P-CSCF) SPDF BGF A-RACF e2 e2 e2 e4 Authentication Authorisation Configuration Service Request (e.g. SIP INVITE) 1 2 3 Resource Request 4 Policy Push Resource Request 5

slide-3
SLIDE 3

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 3

ITU-T

ETSI TI SPAN NASS Arctitecture

a4 Service control subsystems and applications TE CNG a3 a1 a2 e1 e2 e4 e3 Resource and Admission Control Subsystem CLF NACF CPECF AMF PDBF UAAF ARF e1 e2 e5 CNGCF UE

slide-4
SLIDE 4

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 4

ITU-T

NASS Functions

  • CNGCF (Customer Network Gateway Configuration Function) - used during initialization

and update of the UE to provide the UE with configuration information (e.g. configuration

  • f a firewall internally in the UE and QoS marking of IP packets) additional to the network

configuration data provided by the NACF.

  • ARF (Access Relay Function) - relay between the CNG and the NAS

S that inserts local configuration information.

  • AMF (Access Management Function) - translates the network access requests sent by the

UE and forwards requests for allocation of an IP address and possibly additional network configuration parameters to/ from the NACF and forwards requests to the User Access Authorisation Function (UAAF) to authenticate the user, authorize or deny the network access, and ret rieve user-specific access configuration parameters. If PPP is used the AMF terminates the PPP connection and acts as a RADIUS client if the UAAF is implemented in a RADIUS server.

  • NACF (Network Access Configuration Function) - responsible for the IP address allocation.

Typically implemented as a DHCP or RADIUS server.

  • UAAF (User Access Authorisation Function) - performs user authentication and

authorisation checking, based on user profiles. Communication between UAAFs in different administrative domains is provided by the e5 interface allowing a UAAF-proxy to request the UAAF-server for user authentication and authorization and allowing the UAAF-proxy to forward accounting data for the particular user session to the UAAF-server.

  • PDBF (Profile Database Function) - contains user authentication data (e.g. user identity,

list of supported authentication methods, and authentication keys). It may be co-located with UAAF (the interface between them is not to be standardized).

  • CLF (Connectivity S

ession Location and Repository Function) - registers the association between the IP address allocated to the UE and related network location information. The CLF has interfaces to the AF (e.g. P-CS CF) and to the RACS .

slide-5
SLIDE 5

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 5

ITU-T

e2 interface

  • Enables Application Functions (AF), such as an IMS

P-CS CF or a Presence Network Agent (PNA) to retrieve IP-connectivity related session data from the NAS S CLF

  • The AF can request the following information for a specific

subscriber (identified by a globally unique IP address or a subscriber identifier):

  • S

ubscriber-id;

  • Location information;
  • RACS

contact point;

  • Access network type (ATM, Ethernet or Unknown); and
  • Terminal Type.
  • The e2 interface may also be used between a CLF in a visited

network and a CLF in a home network in the case in which the P- CS CF resides in the home network.

slide-6
SLIDE 6

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 6

ITU-T

ETSI TI SPAN Resource & Adm ission Control

Di Transport Layer R q Di A-R ACF Ia e4 R e Gq’

Ra

NASS AF SPDF Core Border Node BGF Ip E dge RCEF L2T Point

Access Node

RACS

UE

Ds

Di Transport Layer R q Di A-R ACF Ia e4 R e Gq’

Ra

NASS AF SPDF Core Border Node BGF Ip E dge RCEF L2T Point

Access Node

RACS

UE

Ds

slide-7
SLIDE 7

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 7

ITU-T

RACS Functions

  • Policy control, resource reservation and admission control in

the access and aggregation sections of fixed access networks.

  • Network Address Translation (NAT) at any place, or places, in

the access, aggregation or core networks.

  • Request and reservation of transport resources.
  • RACS supports a “Push” model in which service requests are

“pushed” to RACS from the Application Function using the Gq’

interface and then, if these requests are compliant with the policies established by the operator and the appropriate transport resources are available, RACS “pushes” requests to the transport layer to control the appropriate transport resources.

  • The AF, SPDF and A-RACF may all be in different administrative
  • domains. The AF is either configured with the address of the

S PDF or obtains this information via the e2 interface to the NASS The contact points for the A-RACFs and the BGFs are locally configured in the SPDF.

slide-8
SLIDE 8

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 8

ITU-T

Service Policy Decision Function ( SPDF)

  • checks if the request information received from the

AF is consistent with the policy rules defined in the SPDF;

  • authorizes the requested resources for the AF

session based on the request information received from the AF ;

  • locates the BGF and/ or A-RACF in accordance with

the transport capabilities required;

  • requests resources from the A-RACF;
  • requests one or more services from the BGF; and
  • hides the details of the RACS

and of the transport layer from the AF.

slide-9
SLIDE 9

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 9

ITU-T

ETSI TI SPAN Protocols

  • e2, e4, Gq’ and Rq
  • Based on Diameter (RFC 3588)
  • Diameter messages are transported using S

CTP (RFC 2960) and use is made

  • f the S

CTP checksum method specified in RFC 3309.

  • IPS

ec may be used for secure transport of Diameter messages.

  • Accounting functionality is not used and Diameter sessions are implicitly

terminated (i.e. the server does not maintain state information).

  • Ia
  • Based on H.248.1 version 3.
slide-10
SLIDE 10

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 0

ITU-T

Gq’ interface

  • ETS

I AVPs

  • Binding-Information
  • Binding-Input-List
  • Binding-Output-List
  • V6-Transport-Address
  • V4-Transport-Address
  • Port-Number
  • Reservation-Class
  • Latching-Indication
  • Reservation-Priority
slide-11
SLIDE 11

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 1

ITU-T

Rq interface – Resource reservation request

  • Application Function ID
  • S

ubscriber ID

  • Globally-unique IP Adress
  • Assigned IP address

(IPv4/ IPv)

  • Address realm
  • Requestor name
  • S

ervice class

  • S

ervice priority

  • Charging correlation

information

  • Media description
  • Media type
  • Media ID
  • Media priority
  • Traffic flow parameters

—Direction —Flow ID —IP address —Ports —Protocol —Bandwidth —Reservation class —Transport service class

  • Commit ID
slide-12
SLIDE 12

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 2

ITU-T

e4 interface

  • Enables the exchange of IP-connectivity related session data between the

NASS CLF and the Access -RACF in the RACS

  • The following information can be transferred from the CLF to the A-RACF:
  • Initial Gate Setting
  • List of allowed destinations
  • Up-Link S

ubscribed Bandwidth

  • Down-Link S

ubscribed Bandwidth

  • QoS Profile Information
  • Transport service class
  • Media-Type
  • Up-Link S

ubscribed Bandwidth

  • Down-Link S

ubscribed Bandwidth

  • Maximum Priority
  • Requestor Name
  • The Access Profile is “pushed” from the CLF to the A-RACF when an IP address

has been allocated to a subscriber or in the case of a modification occurring on a profile that has already been pushed to the RACS and “pulled” by the A- RACF from the CLF after a restart or upon reception of a resource reservation request associated with an IP-Address for which no record is stored.

  • The CLF can also report the loss of IP connectivity enabling the RACS to

remove the access profile from its internal data base. This occurs when the allocated IP address is released (e.g. DHCP leased timer expiry) or due to the release of the underlying layer 2 resources.

slide-13
SLIDE 13

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 3

ITU-T

Border gatew ay control

RCEF C-BGF I-BGF Open / close gates Open / close gates Open / close gates Packet marking Packet marking Packet marking Resource allocation (per flow) Resource allocation (per flow) NAT NAT Hosted NAT traversal Policing of down/uplink traffic Policing of down/uplink traffic Policing of down/uplink traffic Usage metering Usage metering

slide-14
SLIDE 14

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 4

ITU-T

I a protocol

  • opening and closing gates (i.e. packets filtering

depending on "IP address / port");

  • allocation and translation of IP addresses and port

numbers (NAPT);

  • interworking between IPv4 and IPv6 networks (NAPT-

PT);

  • hosted NAT traversal;
  • packet marking for outgoing traffic;
  • resource allocation and bandwidth reservation;
  • policing of incoming traffic; and
  • usage metering.
slide-15
SLIDE 15

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 5

ITU-T

I a H.2 4 8 Packages

  • Generic
  • Base root
  • Network
  • Diffserv
  • Gate management
  • Traffic management
  • IP NAPT traversal
  • MPLS

(optional)

  • VLAN (optional)
  • MGC Information (optional)
  • Inactivity (optional)
  • S

egmentation (optional)

slide-16
SLIDE 16

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 6

ITU-T

RCEF intended to condition traffic on basis of:

  • pure L2 QoS mechanisms, e.g., VP/ VC based

for ATM networks, DLCI based for FR networks, or VLAN tag for Ethernet

  • intermediate L2/ L3 QoS mechanisms, e.g.,

MPLS

  • pure L3 QoS mechanisms, e.g., DiffS

erv

  • L3 over L2 QoS mechanisms, e.g., DiffS

erv

  • ver ATM or FR
  • L3 over intermediate L2/ L3, e.g., DiffS

erv and MPLS seamless integration.

slide-17
SLIDE 17

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 7

ITU-T

I TU-T Resource & Adm ission Control Architecture

Transport Functions

Other NGNs RACF Service Control Functions Network Attachment Control Functions TRC-FE Rs Rw Ru Rn Rc Rp Rt Service Stratum Transport Stratum Rd Ri PE-FE PD-FE TE-FE Interconnection Functions Functional Entities PD-FE: Policy Decision PE-FE: Policy Enforcement TRC-FE: Transport Resource Control TE-FE: Transport Enforcement :

slide-18
SLIDE 18

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 8

ITU-T

I TU-T Resource Control Protocol Drafts

  • Q.rcp.1 – Protocol at the interface between S

ervice Control Network Element and Resource and Admission Control Network Element.

  • Q.rcp.2 – Protocol at the interface between Resource

and Admission Control Network Elements.

  • Q.rcp.3 – Protocol at the interface between Resource

and Admission Control Network Element and Edge Node Network Element.

  • Q.rcp.4 – Protocol at the interface between Resource

and Admission Control Network Element and Transport Network Element.

  • Q.rcp.5 – Protocol at the interface between Policy

Decision Network Element and Transport Resource Control Network Element in access network.

Rs Rp Rw/Rn Rc ? Diameter COPS COPS COPS

slide-19
SLIDE 19

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 9

ITU-T

Looking ahead

  • Completion of work on current architecture
  • Harmonisation of the work of various S

DOs e.g. ITU-T & ETS I TIS PAN

  • S

upport of enterprise network connection

  • S

upport of non-S IP applications e.g. web- browsing, IPTV

  • NAT/ Firewall traversal (ICE, S

TUN, TURN)

  • Path-coupled QoS

control mechanism