Taesang Choi

1
Y.Mpm RACF Relationship

• 2008. 7. 23
• Taesang Choi
• choits_at_etri.re.kr
• TTA

2
Main Issues

• Current PE-FE provides metering capability for
  bandwidth collection only. However, the
  measurement-based resource control may need more
  than bandwidth information. For example, one-way
  delay (or other performance) information from TE
  to PE-FE or PE-FE to destination TE can be
  important to make a policy decision for the
  on-going service media flows. There are two ways
  to solve this issue 1. extending PE-FE
  capability to meet such additional requirements
  or 2. getting such information from other
  management entities such as MPM. By considering
  the realistic implementation limitations, we
  consider the latter as better choice.
• Next issue is then how such information can be
  exchanged between appropriate functional
  entities. There are several options for this
• Extending Rc to allow symmetric communication so
  that performance measurement information for
  target media flow (s) can be requested by TRC-FE
  to MPM. For such extension, the currently
  defined Rc protocols such as SNMP and COPS may
  not meet the new requirements and MPMs Mu
  reference point is used to interact with Rc
  reference point in this case.
• Introduce a new reference point to meet the new
  requirements. We can call it Rm. (m for
  management) Rm can be utilized for RACF to
  interact with various NGN management functional
  entities. One example is MPM. There are two
  cases on how to use Rm
• Use Rm to receive information on which
  performance measurement should be made from RACF
  and use Rc to provide measurement results to
  RACF. This method requires some extension of Rc
  in terms of its information elements.
• Use Rm to both receive and reply to RACF
  requests.
• Last issue is, then, where Rm is attached to
  RACF. There are two options PD-FE or TRC-FE.
• PD-FE In this case, PD-FE needs to decide which
  reference point it uses for resource usage
  information collection, either Rm or Rc. More
  sophisticated measurement based admission control
  is required, Rm can be used. Otherwise Rc can be
  used.
• TRC-FE In this case, Rm is also similarly used
  as in Rm of PD-FE but its usage is limited in the
  scope of TRC-FE. If Rm needs to be used to
  communicate with other NGN management functional
  entities which are beyond transport resource
  control, it may not be possible.
• Conclusion Based on the examination and analysis
  of the above issues in terms of simplicity,
  efficiency, and extensibility, we conclude that
  the best interaction method between RACF and MPM
  is a new reference point Rm attached at PD-FE

3
Proposal
4
Reference Point Rm Functional Requirements

• The Rm reference point is required to carry the
  following information
• Measurement and analysis reports for MPM
  applications within the same NGN provider domain
• Acknowledgement for the reports transfer receipt
• The description information of media flows
  specified by the service control function.

5
Reference Point Rm Information Exchange
Requirements

• Request-response transactions The reference
  point must allow the PD-FE to request a
  transaction to be performed by a transport
  element and get a response (that can be
  correlated with the request) in return.
• Notifications The reference point must allow the
  notification of asynchronous events (from a MPM
  to the PD-FE).
• Reliable delivery The reference point should
  provide reliable delivery of messages.
• One-to-many/many-to-one Two modes shall be
  supported 1) One-to-many mode, a PD-FE shall be
  able to communicate with multiple MPMs 2)
  Many-to-one mode, multiple PD-FEs shall be able
  to make requests to a given MPM.
• Security All messages between PD-FE and MPM
  should be authenticated such that requests to the
  MPM from unauthenticated sources will not be
  performed and such that notifications sent from
  the MPM to PD-FE can be ensured to come from an
  authenticated source.

6
Reference Point Rm Information Components
7
Thanks You