Art Vandenberg August 14, 2001 draft-vandenberg-vidmid-scenarios-summary-00.txt VidMid Comments to: vidmid@internet2.edu Abstract: VidMid Working Group - Summary of Scenarios. The following collects information from VidMid activities so far in regards scenario development. These notes are drawn from meeting minutes, email discussions to the VidMid list, and various submitted scenarios. Information is presented generally in chronological order as received by Working Group discussions. Purpose of scenarios stated (April 17, 2001 minutes): " 'get [scenarios] clearly stated and call everything else out of scope.' From there... proceed to specifying requirements, architectures, flows, protocols, and standards." Data Collaboration, Streaming, VoD, VoIP scenarios suggested (May 1, 2001 minutes): "A short discussion affirmed the place of video data collaboration, streaming video, video on demand, and voice over IP in VidMid's work." Directory Services for Multimedia Telephony - Tyler Johnson, December 4, 2000 http://middleware.internet2.edu/video/docs/johnson-dirs-for-multimedia-tel-00.pdf Directory Scenarios for Videoconferencing - Art Vandenberg, May 25, 2001 http://middleware.internet2.edu/video/draftdocs/draft-vandenberg-vidmid-dir-scenarios- 00.html Directory Scenarios for Video on Demand - Mairead Martin, May 29, 2001 http://middleware.internet2.edu/video/draftdocs/draft-martin-vidmid-vod-scenarios-00.html Scenarios for broad range of services, initial focus narrow (May 29, 2001 minutes): "...produce scenarios for a broad range of services, but focus... initial problem-solving efforts on authentication, security, and accounting & billing for videoconferencing..." Data Collaboration, Streaming, VoD, VoIP scenarios, Agenda Item #5 - June 11, 2001: "5. Scenarios streaming and video-on-demand videoconferencing VoIP scenario Video data collaboration" SURFnet scenarios URL (Email to VidMid from Egon Verharen sent June 11, 2001 1:45pm, SUBJECT= More scenarios?) http://www.surfnet.nl/innovatie/surfworks/showcase/scenario.html Scenario details: access controls, directory schema for archiving/access, integration of real-time video with streaming - June 25, 2001 Draft minutes: (see VidMid URL) "The three primary categories that may be considered for these scenarios are metadata, access controls, and codecs, though the last one is beyond the scope of this group... "Three scenarios have been proposed to date. The first would describe the use of proper middleware to implement appropriate access controls to video information. This would entail both fine- and course-grained definitions, allowing permissions to be issued across the spectrum from broad groups such as 'all members of Internet2' to individuals. The second proposed scenario would describe the sorts of directory schema necessary to provide adequate archiving and access to information. The system would have to allow both humans and computers through traditional directory means to quickly determine the movies they are interested in retrieving. A third scenario would integrate real-time video with streaming video and a real-time capture of this information. An example given during the call was that of a security camera needing to both display real-time information and be able to quickly archive and recall specific events, often in time-critical applications. "...During the next phone call, the group will finalize a set of four scenarios to characterize the most urgent issues." More definition of VoD & Videoconferencing scenarios, with samples (Email to VidMid from Ken Klingenstein sent July 8, 2001 8:34pm, SUBJECT= Agenda for VidMid Call 09.7.01 "5. Scenarios to drive requirements: a. Discussion of two samples see below b. VoD instances i. VoD access control from Mairead sample ii. Directory information for collections eg UW iii. Hybrid?? c. Videoconferencing instances i. Point to point ?? ii. MCU ?? iii. Hybrid - remote access to security cameras in real time, with archiving needed. Markus Buckhorn "Sample scenario VoD , drawn from Mairead's original: "The owner of a video asset should be able to assign user rights and permissions to categories of people, and to individuals for specific types of access. For example, the content owner wanting to provide access to the VidMid working group video archives would like to set permissions only need not necessarily know the directory specifics for each working group member. Differential user access (view, download, copy, modify, etc.) should be supported. "Differential access within the video asset will also be supported in the same way. The object-level functionalities of MPEG-4, for example, will require authentication at the granular object level: an instructor may wish to give selected viewers permission to change the visual properties or modify an object within a video. "The emergence of modification capabilities, including object-level modification, will necessitate a baseline and journaling function that captures user and usage information. This information should be available for billing and accounting algorithms. The owner of the asset would like to be able to utilize the [sic] "A directory entry can contain or link to an index of video assets created or owned by the user. The index will include details on formatting, required players/clients, location of assets, IPR information, etc. Some of these assets may be archived videoconferencing sessions. A user will be able to easily and transparently add assets, assign user and usage rights, and standardized metadata to their content. This entry should not replace metadatabases, however. "Sample Scenario, videoconferencing, drawn from Art's material "User can look up person information for video contact. Search interface is simple, 'intuitive' and provides contact details. Directory details include attributes specific to supporting videoconference connection (cf. IP address, type of equipment, local time zone info, bandwidth...?). "User can register and maintain their directory entry. User's initial default data may be displayed based on expected common data or through 'auto- discovery' by directory tool. User can link their directory profile to a source (directory or other data source) that will automatically synchronize and propagate changes. "User's video conferencing software provides an LDAP interface to the directory information user has set up. The result of a lookup can be used to initiate a conference connection ('click to connect') and the software can use the configuration details in the directory to negotiate the connection. User's results are returned quickly and any connections are initiated with minimum delay. Results should conform to the expectation for looking up someone's number, dialing the number, and hearing the ring. "User should be able to rely on the 'authority' of the directory. This may require that initial entry into the directory is screened or verified to ensure that services will be delivered correctly. For instance, the name, address, phone info may be confirmed via call back; the configuration info may be confirmed by test conference; etc. Authority of the directory includes accuracy of information, timeliness of entry updates, and audit trail of changes." Security cameras scenario (Email to VidMid from Markus Buckhorn, sent July 8, 2001 9:38pm, SUBJECT= VidMid Scenario - security cameras) "Remote access to Security Video "There are two aspects to this scenario - one is live access to a remote camera, for the purposes of viewing real-time events. The other is access to an archive of the same content. I think the latter will have significant and/or better coverage in other VoD scenarios, but mention some specific needs here. "Within the live-access situation there are several components. Initially a user (security personnel) needs to be authenticated and authorised to access a (set of) camera(s) and any associated alert systems. Once alerted, or on- demand/browsing, the user then needs to access a particular camera (implying a choice of video source), jump between cameras (tracking situation) and also drive the cameras that support pan-tilt-zoom (PTZ) operations. "Extensions to this scenario include - the need to support multiple users accessing the same camera (e.g. several police tracking a suspect, but who controls the camera's PTZ?), - the need to encrypt/sign the actual stream (avoid middleman problems, where the stream is either tapped or tampered with). - levels of access required, depending on the user and the infrastructure (new users, part-time private security vs full-time police, police vs NSA :-), as well as high-res/low-res cameras, white light/infrared, with/without PTZ, etc.) - real-time parallel archiving of the video, including indexing (tagging with time/location metadata), as well as control/access information (who drove the camera that way, who was watching this particular scene?), and potentially encryption of the archive. "One aspect of accessing the archive that may be different to other VoD scenarios is the requirement to do so extremely quickly. It needs to support the 'Hey, what just happened?' question common in security situations to initiate tracking and/or reaction by security personnel. If it takes several hours/days to archive and index the content it becomes useful for evidence but not for reaction. Similarly if it takes 10-30 seconds for a recorded stream to start playing it is also too slow. This may require a two-tier archiving system, where the first tier is effectively a smart/continuous cache of live content, and the second tier is your more traditional content archive. Content needs to move (in a trusted but rapid fashion) between the live/tier-1/tier-2 systems." Scenario from general end user perspective (A. Vandenberg notes from July 9, 2001 VidMid call) "Scenario - should be more generalized, end user perspective. Scenario leads to requirements, then requirements drive implementation." URL to three streaming scenarios (Email to VidMid from Jim Whitlock, sent July 9, 2001 11:24am, SUBJECT= Streaming Scenarios) http://ub-iptv-mgr-1.cit.buffalo.edu/wny-hpnvi/webs/blurbs/stream-conf- scenarios.htm "Draft streaming video application scenarios arising in a VidMid WG teleconference call on 6/25/01 are presented... "Streams and VOD as Successively Reduced-Cost Participatory Modes for Real-time Interactive Events "Streaming Video as a Security Monitoring Tool "Streaming Video as an Improved Remote Site Content-Origination Source Feed for Centralized Support of Real-Time IP-video Supported Events "Basic, extended, advanced" scenario model via SURFNet (Email to VidMid from Egon Verharen, sent July 17, 2001 10:46am, SUBJECT= Re: action items from July 9 VidMid call) "Basic "Sandra enters the library and finds an available PC at one of the work places. She starts up her email and notices a new mail from mr. Curver pointing at the material discussed today during the political propaganda class. At the course's website she clicks on the playlist generated by mr. Curver which shows 3 clips of the party leader using body language to stress his points. This week's assignment is to show other examples of him using this, extra credit can be won by showing example footage of him using the words 'please', 'I promise' and 'burning water'. Next week's assignment is to compare the acts of the party leaders of the three biggest parties. In order to find the appropriate clips Sandra opens the search page of the local archive and types in the terms 'speech', the party leader's name(which she ORs with the party's name) and as time period the last three months. "She is presented with a list of available clips that match the search criteria. The list shows not only a key frame of the clip, but also the associated metadata in which her search terms are highlighted and other basic info, such as the format the clip is in, the duration and the clip's source (TV channel, tape,). She opens the first clip and watches the first 10 seconds. This is just a general introduction before the party leader starts his speech. She moves the slider of the video player to the 2 minute mark and watches the next ten seconds. She sees the party leader stressing a point by hitting the stand and almost knocking over the microphone. Using the slider again she scrolls back a minute and finds the first frame of this scene. She marks the time code, and then browses the video for the end of the scene and again marks the time code of the last frame. The second video is of too low a quality to actually see what the party leader is doing. Sandra continues! to check the assets in the list. When she has found the three clips that best illustrate the point in her point of view she writes an email to mr. Curver with the clips' names and time codes of the scenes she selected. "Extended "After Sandra examines the list of available assets she opens a new playlist which she stores in her personal directory. The player allows her to set IN and OUT marks and drag the clip to her playlist. Continuing this she finds three clips showing the point. Not being sure whether she selected the best clips available she mails her friend Cathy the code of the playlist that she publishes as 'protected'. After Cathy plays the clips in the playlist and sends her the OK, Cathy publishes the playlist as 'public' and sends the URL to the class' discussion list. "In class the next week Cathy is asked by mr. Curver to explain why she chose these scenes. Using the presenter's PC she logs in and finds her playlist. She opens the playlist and selects the high quality playback option. The scenes are shown using the class' ceiling mounted beamer at MPEG-2 quality and she freezing the clip using the player functionality she can point at the specific posture the party leader takes. "Advanced "Sandra uses the advanced search options to search for the words 'please', 'I promise' and 'burning water' in the audio tracks, and the party leaders names and the party names in the description field and as source 'TV' in the other metadata field. Furthermore she fires of the query not only to the archive but also to the public playlists of her classmates. "She is presented with a list of assets in the archive and the playlist of John that used the same search terms as she did. Opening John's playlist she notices that he only selected very old clips. She starts the original clip that is associated with John's first choice. She notices however that a minute after the scene John selected a better scene is available. She opens the metadata editor and types in this comment in the text field associated with her selection. To be sure to not forget to tell John she also enters this comment as added metadata to her playlist. "On her way back home together with her friend and classmate Peter she discusses the assignment. Peter really wants to know what assets Sandra has chosen to present to class. Sandra uses her mobile phone and PDA to bring up her playlist with titles emphasized. Peter asks if he can get this list and study it at home and see if he can improve upon it. "Generic: "The end-user, working with a PC-like device that has video playback capability and an internet connection, accesses the VoD archive catalogue by using either a browser or a dedicated VoD client. [login: authentication]. Based on the user's credentials [authorization] the list of available directories and/or assets is shown [content distribution]. Playback of a video is started by selecting an asset [capability negotiation device, QoS negotiation, content play out]. The user is able to search for assets using the metadata search engine [authentication]. Results can be previewed at low quality. The clips metadata can be collected and stored for later use [metadata, authorization]. The user can set permissions on the collected metadata [authorization] "Note: for an alternative, please see the scenario document mailed around earlier today." [following is the URL - 65 pages]: http://www.telin.nl/dscgi/ds.py/Get/File-16051/Scenarios_for_Video_Over_IP.pdf/ Multipoint (MCU) videoconferencing scenario (Email to VidMid from Art Vandenberg sent July 30, 2001 1:28pm, SUBJECT= Multipoint Scenario) "VidMid Scenario for Multipoint Video Conferencing "Abstract: This scenario briefly states some issues related to providing multipoint video conferencing. The scenario will serve as a point of departure for defining specific action items for implementation of robust video middleware. "A multipoint video conference scenario is envisaged in which an interface allows video conferences to be set up by individuals, or administrators on their behalf, selecting the appropriate criteria for their connection. Each point in the multipoint represents an end-user or group of users (as in a meeting room). An important initial consideration is what end-user experience is being requested, as there are various styles of multipoint conferencing: group meeting (full-duplex 'everyone talks', a chair controls who speaks, etc.), classroom style, collaboration, etc. "Support for these various video conference styles requires coordination of local technical capabilities of the end points: hardware configuration (cameras, video displays, workstations, microphones, and speakers), video conferencing software (supporting audio, video, collaboration mechanisms), and network characteristics (speed, availability, requirements for gateways). It is desirable that such technical details be automatically discovered and negotiated, perhaps with a 'best fit' recommended. "Specification would include scheduling the meeting time to accommodate participants' existing calendar commitments or time zone preferences. Set up might include coordination or reservation of bandwidth, in case of limiting factors imposed by the video conferencing or other simultaneous activities. Presumably, security issues, such as who can participate, whether the meeting is public or private, are also addressed. Aspects of the multipoint set up might be saved for reuse (such as the list of participants, their configurations, their time zone preferences, etc.) It may be that the configuration aspects of individual end points are maintained in a manner that permits them to be mixed and matched dynamically for other multipoint (or endpoint-to-endpoint) sessions."