1 / 11

Diameter General Purpose Session draft-liebsch-dime-diameter-gps-01.txt

Diameter General Purpose Session draft-liebsch-dime-diameter-gps-01.txt. M. Liebsch, G. Punz IETF80, Prague Diameter Maintenance and Extensions (DIME) WG 01 st April 2011. History. Initial version presented at IETF78 in Maastricht Updated version presented at IETF79 in Beijing

quasar
Download Presentation

Diameter General Purpose Session draft-liebsch-dime-diameter-gps-01.txt

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 General Purpose Sessiondraft-liebsch-dime-diameter-gps-01.txt M. Liebsch, G. Punz IETF80, PragueDiameter Maintenance and Extensions (DIME) WG 01st April 2011

  2. History • Initial version presented at IETF78 in Maastricht • Updated version presented at IETF79 in Beijing • First revision addresses comments and adds more details as well as clarifications • GP Session concept • Context Grouping • Analysis • Approaches

  3. Idea behind the GP Session (2/2) AVPs apply to single user Single-user context(RFC3588) Diameter Hdr Session-ID AVPs Maintain standard format,but adopt new interpretation AVPs apply to group of users Multi-user context/ Bulk signaling Diameter Hdr GP Session-ID Users AVPs - Group-ID - List of individual Session-IDs - Grouped AVP

  4. Coding options for bulk signaling(in the order of efficiency) • Group-ID identifies multiple users, list of attributes/values applies to all users of the group • List of Session-IDs identifies a group of users, list of attributes/values applies to all users of the group • List of Session-IDs identifies multiple users, each Session-ID has an individual list of AVPs associated Diameter Hdr GP Session-ID AVP 1 AVP 2 AVP N Group-ID Diameter Hdr GP Session-ID AVP 1 AVP 2 AVP N Session-ID 1 Session-ID K Diameter Hdr GP Session-ID Session-ID 1 AVP 1.1 AVP 1.2 AVP 1.N Session-ID K AVP K.1 AVP K.2 AVP K.N

  5. Valuable & Positive Feedback • More use cases and enlarged scope • GP Session has value, but represents a new application • Platform for specification: DIME or alternative group • Good idea, but overloading only 3GPP habit • New messages as alternative • GP Session has clear rules, but other SDOs (TISPAN) just ignore the Session ID • Enlarge the scope of the idea to address also signaling without Session ID • Focus on grouping for bulk signaling

  6. What‘s Next? • Proposal to split the current draft • Target 2 separate documents • Approach meets all comments • (1) Diameter GPS • Focus on the use of a shared Session ID • Extension to Diameter base or New Application • May come with other functions • Query, State Restoration, ... • (2) Coding Options for bulk signaling • Enables use with other Diameter signaling • No limitation to Session ID based messages

  7. What‘s Next? • Interest in working on this? • Thanks for all comments !

  8. Appendix

  9. Idea behind the GP Session (1/2) • Eshablish a dedicated session (and Session-ID) to signal multi-user context (bulk signaling)  GP Session • Clarification: GP Session-ID does not identify a group of users! • GP Session-ID.. • .. allows the re-use of available commands (e.g. STR), which mandate a single Session-ID AVP, to signal attribues/values applying to multiple users • RFC3588: Single Session-ID AVP at fixed location (after Diameter header) identifies the user where subsequent attribute/values apply to • .. indicates that attributes/values apply to a group of users or all users! • .. avoids specification of new command codes and formats for bulk signaling

  10. Again: Use cases • Bulk signaling, e.g. • Bulk Session Termination using STR • Bulk policy enforcement • Recovery from total/partial Diameter node failure Server states restoration Group policy enforcement server server Req(multiple users [failed_server_id]) Req(multiple users, context1, context2, ...contextN) Resp (multiple users,context1, context2,... contextN) client client PCEF data traffic Policy Enforcement

  11. Stepwise realization of the extended session concept Deployment-specificguidelines forbulk signaling Specify GP Sessionextension Bulk-signaling operation andextensions specified in Applications Deployment by usingRFC4006+ and RFC4005+ Deployment-specific guidelines and specification (e.g. By 3GPP) NASREQRFC4005 BulkExt. BulkExt. NASREQRFC4005+ Credit ControlRFC4006 Credit ControlRFC4006+ GPS GPS Diameter Base RFC3588 Diameter Base RFC3588

More Related