1 / 10

Enhancing Diameter Protocol with Group Signaling for Efficient Session Management

This document outlines the proposed enhancements to the Diameter protocol to reduce signaling overhead in scenarios requiring simultaneous management of multiple sessions. The goal is to facilitate group signaling with minimal impact on existing Diameter applications. It addresses group assignment management, session manipulation, and introduces new commands for group actions. The draft also seeks to define best practices that other standards development organizations (SDOs) can adopt to tackle similar problems, ensuring backward compatibility and improving operational efficiency.

harlow
Download Presentation

Enhancing Diameter Protocol with Group Signaling for Efficient Session Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Diameter Group Signaling Thursday, March 28, 2012 draft-jones-diameter-group-signaling-01 Mark Jones IETF 83 Paris, France

  2. Motivations • Reduce signaling in those use cases that require many Diameter sessions to be modified or terminated at the same time. • Add group signaling to existing Diameter applications with minimal impact and ambiguity. • Describe the problem space in an application neutral fashion (best practices?) to aid other SDOs in tackling this problem.

  3. Two Problem Aspects • Managing group assignments. • How to add or remove sessions from groups. • Guidelines for modifying group assignments. • Permission model (or not) • Manipulating groups of sessions • Defines new group command equivalents for RAR/RAA, ASR/ASA and STR/STA. • Defines the session state machine for these new commands.

  4. Managing Group Assignments • In the current version of the draft: • Either Diameter peer may assign a session to a group. • Mid-session modification of group assignments are allowed. • A Diameter peer may remove the group(s) assigned to the active session by its peer. • However, Diameter applications may impose a stricter model or forbid some functions.

  5. Manipulating Groups of Sessions • Current version of the draft proposes defining new group command equivalents for the group actions. • Only RFC3588 equivalents defined so far. • No intent to define NASREQ/DCCA equivs. • Alternative approaches have been proposed: • Use existing commands • Bulk command container • New group command flag

  6. New Group Commands • New Diameter application is mandatory. • New group commands do not have the same ABNF as non-group commands. • Session-Id is not present. • Other AVPs may be absent/present depending on application-specific restrictions. • CER/CEA takes care of backwards compatibility. • Peers can negotiate down to non-group mode.

  7. Existing Commands • New Diameter application is mandatory. • Group commands have same ABNF as non-group commands but a different Diameter application id. • Session-Id is a required AVP so it is either: • re-purposed to contain a group identifier, OR • ignored, new ‘optional’ AVP contains group identifier.

  8. Bulk Command Container • New Diameter application is mandatory. • Single new command is defined, serving as container for all group commands. • Actual group command code added as AVP • Bulk command container contains a group identifier and * [ AVP ]. • Presence of further AVPs depends on which group action is being performed.

  9. New Group Command Flag • New Diameter application is mandatory. • New Group flag is introduced in the command flags field. • Group commands have same ABNF as non-group commands but a different Diameter application id. • (Ed: It is unclear to me what the advantages are over simply reusing existing commands ABNF.)

  10. Next Steps • Complete guidelines for managing group assignments. • Pick ONE method for Manipulating Groups for Sessions. • All methods could work. • Don’t want a long drawn out beauty contest. • Question for DIME WG: • Adopt this draft as a basis for addressing the new group signaling charter item?

More Related