![Page 1: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/1.jpg)
1
SIPRECRecording Metadata Model for SRS
(draft-ram-siprec-metadata-03)
Jan 25-26, 2011 Virtual Interim meetingRam Mohan R
On behalf of the team
Team: Paul Kyzivat, Ram Mohan R, R Parthasarathi
![Page 2: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/2.jpg)
Agenda
• Changes in draft-ram-siprec-metadata from the previous version
• Discuss Open items in Metadata Model• Next Steps
![Page 3: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/3.jpg)
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.
![Page 4: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/4.jpg)
sends
receives
1
1
1
0..*
Metadata Model
4
Recording Session(RS)
Communication Session(CS) Group
Media Stream
ApplicationData
Communication Session(CS) 1
Participant
0.. *2..*
11..*
1
1..*0..*
0.. * 0.. *
1.. * 0..*
1.. *0..*
![Page 5: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/5.jpg)
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).
![Page 6: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/6.jpg)
Metadata Model: Communication Session Group
6
Communication Session
Communication Session Group (CS Group)
CS Group unique ID
Application Data
1 0..*
• 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
Recording Session (RS)1..*0..*
11..*
![Page 7: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/7.jpg)
0..*2..*
Metadata Model: Communication Session
7
Participant
Communication Session (CS)
-Call Termination Reason
-Force deletionApplication Data
1 0..*
• 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
Communication Session Group (CS Group)
11..*
1.. *0..*
Media Stream
![Page 8: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/8.jpg)
Metadata Model: Participant
8
Participant
•AoR list•Name• Participant Type
Application Data
1 0..*
• 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 ?
Communication Session0..*2..*
Media Stream
sendsreceives0.. *
0..*
1.. *
0..*
![Page 9: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/9.jpg)
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
![Page 10: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/10.jpg)
Metadata Model: Media Stream
10
Media Stream
•Start Time•End Time•Codec param •Media Stream Reference
Application Data
1 0..*
• 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 ?
Participant
sendsreceives0.. *
0..*
1.. *
0..*
CS 1..* 0..*
![Page 11: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/11.jpg)
Metadata Model: Application Data
11
Application Data
•Type Identifier•Data Encoding?•Opaque Data
1 0..*
• 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
![Page 12: 1 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:](https://reader036.vdocuments.net/reader036/viewer/2022081512/56649f455503460f94c67988/html5/thumbnails/12.jpg)
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)