1 / 12

SIPREC Recording Metadata Model for SRS (draft- ietf -siprec-metadata-00)

SIPREC Recording Metadata Model for SRS (draft- ietf -siprec-metadata-00). May 09, 2011 Virtual Interim meeting Ram Mohan R On behalf of the team. Team: Paul Kyzivat, Ram Mohan R, R Parthasarathi. Agenda. Changes in draft- ietf -siprec-metadata from the previous version

lazar
Télécharger la présentation

SIPREC Recording Metadata Model for SRS (draft- ietf -siprec-metadata-00)

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. SIPRECRecording Metadata Model for SRS(draft-ietf-siprec-metadata-00) May 09, 2011 Virtual Interim meeting Ram Mohan R On behalf of the team Team: Paul Kyzivat, Ram Mohan R, R Parthasarathi

  2. Agenda • Changes in draft-ietf-siprec-metadata from the previous version • Discuss Open items in Metadata Model • Next Steps

  3. Changes from Previous version • During the discussions in Prague on draft-ram-siprec-metadata-04 (already agreed for adoption by WG) the following agreements were reached. Modified the draft with same: • Add start/stop time attributes for Communication Session. • Don't include session state attribute for Communication Session. • The metadata model should include media streams that are not being delivered to the SRS (e.g., those offered by the SRC but not accepted by the SRS).

  4. Changes to Metadata Model • This is the change to the model that was agreed upon since the publication of ver 00: • Associate CS block directly with RS since CS-Group is optional

  5. Updated Metadata Model 1 Recording Session(RS) 1..* 0..* Communication Session(CS) Group 1..* 0..* 1 0..1 1..* Communication Session(CS) 1 1.. * 2..* 1.. * 0..* receives 0.. * 0.. * Participant Media Stream 0..* 1 1.. * 0..* Extension Data sends 1

  6. Metadata Model (contd..) • With the modified model we will have: • An instance of RS can have Zero or more CS blocks and Zero or more instance of CS-Group • If a CS-Group is present it will have 1 or more CS. • Each CS can be associated with Zero or 1 CS-Group. • Each CS and CS-Group (if present) will be associated with one or more RS • Open Items: • Do we need to have direct associations between any other blocks to RS ?

  7. Metadata Model: Recording Session Open items: • Optional Stop/Start time attribute has to be added? • Recording Type may not have significance if SRS is designed with “many RS to many CS”. Do we need this ? • “Recording Group” object as an aggregation over RS block in model? • Is it required to remove recording request ID from the model as it is implicit for SRS from SIP dialog creation? 1 0..* Recording Session (RS) • Recording Requestor ID • Recording Type (Selective/Persistent) Extension Data 1..* 0..* 1..* 0..* Communication Session Group Communication Session

  8. Metadata Model: Media Stream Participant Open Items: • Does MS has a life outside CS? [ e.g. MMOH cases and transfer by 3PCC with multiple CS and single MS] 1 0..* 0..* 1..* Media Stream • Start Time • End Time • Codec param • Media Stream Reference Extension Data CS 0.. * 1.. * receives sends 0..* 0..*

  9. Metadata Model: Communication Session Group Recording Session (RS) Closed Items: • As CS-Group is optional ; CS will be directly associated to RS. • CS-Group will be associated to both CS and RS Association between CS-Group and CS: • CS-Group can have 1 or more CS. • Each CS can be associated with Zero or 1 CS-Group. Open Items: • Optional Stop/Start time attribute needed? 1..* 0..* 1 0..* Communication Session Group (CS Group) CS Group unique ID Extension Data 0..1 1..* Communication Session

  10. Metadata Model: Communication Session Recording Session Closed items: • CS directly associated to RS • Model participants always as part of a CS[IOW no dangling participants]. • Example cases are a UA which is part of conference is a participant in CS. In this all information about participants learnt behind this UA will also be associated with the same CS Association changes with Participant: • A participant shall be associated with 1 more CS 1..* 0..* 1 0..* Communication Session (CS) • CS Unique ID • Call Terminate Reason • Start Time • End Time 0..1 1..* Extension Data Communication Session Group 1..* 2..* 1.. * 0..* Participant Media Stream

  11. Metadata Model: Participant 1..* 2..* Communication Session Closed Items: Association changes with CS: • A participant shall be associated with 1 more CS Open Items: • Is Optional Stop/Start time attribute needed? 1 0..* Participant • AoR list • Name • Participant Type Extension Data 0.. * 1.. * receives sends 0..* 0..* Media Stream

  12. Next steps • Close all the open items • Publish draft-ietf-siprec-metadata-01 after closing the open items • WGLC of metadata model draft? OR merge format and metamodel drafts?

More Related