1 / 12

SIPREC Recording Metadata Model for SRS (draft-ram-siprec-metadata-03)

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

arthur-england
Télécharger la présentation

SIPREC Recording Metadata Model for SRS (draft-ram-siprec-metadata-03)

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-ram-siprec-metadata-03) Jan 25-26, 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-ram-siprec-metadata from the previous version • Discuss Open items in Metadata Model • Next Steps

  3. Changes from Previous version • Updated the Metadata model to have Media Stream block directly linked to CS apart from linked to Participant • Modified the sections of Metadata elements to reflect the discussions /comments closed during Dec 16th 2010 Interim.

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

  5. Metadata Model (contd..) • The updated model has Media Stream block directly associated with CS along with Participant block. • This is done because the “receives” association between Participant and Media stream allows a stream to be received by Zero participants. To represent such streams we need to have explicit linkage between CS and Media Streams. Example of a case where a stream is not received by any Participant - A stream generated ( say by a MOH source) but sent only to the SRC and SRS, not to any participant. (In conferencing where all participants are on hold and the SRC is collocated with the focus).

  6. Metadata Model: Communication Session Group Recording Session (RS) • Conclusions after discussions in SIPREC mailer after last interim • The scope of uniqueness of the ID is with in a single SRC(multiple SRC cases are outside scope) and SRS ( may be multiple SRSs) • The mechanism for ensuring unique is discussed in metadata format slides • App Data may have information like Grouping details e.t.c 1..* 0..* 1 0..* Communication Session Group (CS Group) CS Group unique ID Application Data 1 1..* Communication Session

  7. Metadata Model: Communication Session Communication Session Group (CS Group) • CS to Media Stream Association allows • A CS to have zero or more Streams • A stream can be associated with 1 or more CS. e.g. Multicast MoH stream which might be associated with many CSs. Also if we were to consider a B2BUA to have a separate CS on each "side" then they might share a stream.(Though more likely this would be treated as a single CS.) • App Data may have information like Direction, Initiator e.t.c 1 1..* 1 0..* Communication Session (CS) • Call Termination Reason • Force deletion Application Data 0..* 2..* 1.. * 0..* Participant Media Stream

  8. Metadata Model: Participant 0..* 2..* Communication Session • Attributes ( lists only modified attributes) • AoR list. We would probably need a AoR list instead of allowing one AoR [e.g. P-Asserted-ID which can have both SIP and TEL URIs] • Open Item • Participant role. Is it needed ? • What other attributes ? 1 0..* Participant • AoR list • Name • Participant Type Application Data 0.. * 1.. * receives sends 0..* 0..* Media Stream

  9. Metadata : Participant • App Data may have attributes like • End point information: ip/port, device id (MAC address), Agent ID, OSlogin • Device type: external, station, IVR, routing point, QUEUE, Gateway, MCU, Operator, etc

  10. Metadata Model: Media Stream Participant • New Associations • CS to Media Streams • What other attributes are needed ? Open items: • How to model media streams that are not recorded (two types): 1) SRC offered certain media types but SRS accepts only subset of them streams 2) Should details of streams that SRC doesn’t have capability to record sent to SRS ? • what App Data is needed ? 1 0..* 0..* 1..* Media Stream • Start Time • End Time • Codec param • Media Stream Reference Application Data CS 0.. * 1.. * receives sends 0..* 0..*

  11. Metadata Model: Application Data • Allowing any number of application data objects attached to any of the others. • Can we eliminate for any of the blocks ? • We need a type identifier. • What namespace? • What assignment rules? • Do we need a data encoding type separate from type id? • How do we represent / transmit the opaque data? • Text/binary 1 0..* Application Data • Type Identifier • Data Encoding? • Opaque Data

  12. Next steps • Request for review of draft-ram-siprec-metadata-03 in the mailer • Adopt metadata model draft as WG item ? • Add more Use cases to the Metadata Model draft (object instances)

More Related