Transcript PPT - Ken Rehor

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
1
Agenda
• Changes in draft-ram-siprec-metadata from
the previous version
• Discuss Open items in Metadata Model
• Next Steps
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.
Metadata Model
Recording Session(RS)
1
1..*
0..*
Communication Session(CS) Group
1
1
1..*
0..*
Communication Session(CS)
0.. *
2..*
0.. *
Participant
1.. * 0..*
sends
1
1.. *
0..*
receives
0.. *
Application
Data
Media
Stream
1
1
4
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).
Metadata Model: Communication Session Group
Recording Session (RS)
• Conclusions after
discussions in SIPREC
mailer after last
interim
1..*
0..*
Communication Session
Group (CS Group)
CS Group unique ID
1
0..*
Application
Data
–
–
1
1..*
Communication Session
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
6
Metadata Model: Communication Session
Communication Session
Group (CS Group)
• CS to Media Stream
Association allows
1
1..*
Communication Session
(CS)
-Call Termination
Reason
-Force deletion
0..*
2..*
Participant
1.. *
0..*
Media
Stream
–
1
0..*
Application
Data
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
7
Metadata Model: Participant
Communication Session
• Attributes ( lists only
modified attributes)
0..*
2..*
Participant
•AoR list
•Name
• Participant Type
1
0..*
Application
Data
– 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
0.. *
– Participant role. Is it
needed ?
– What other attributes ?
1.. *
receives
sends
0..*
0..*
Media Stream
8
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
Metadata Model: Media Stream
Participant
0.. *
• New Associations
1.. *
receives
– CS to Media Streams
sends
0..*
• What other
attributes are needed
?
Open items:
0..*
Media Stream
CS
1..* 0..*
•Start Time
•End Time
•Codec param
•Media Stream
Reference
1
0..*
Application – How to model media
Data
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
10
needed ?
Metadata Model: Application Data
Application Data
1
0..*
•Type Identifier
•Data Encoding?
•Opaque 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
11
Next steps
• Request for review of draft-ram-siprecmetadata-03 in the mailer
• Adopt metadata model draft as WG item ?
• Add more Use cases to the Metadata Model
draft (object instances)