idnits 2.17.1 draft-xiao-clue-telemedical-use-case-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 6, 2012) is 4283 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2119' is defined on line 159, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CLUE WG L. Xiao 3 Internet-Draft R. Even 4 Intended status: Informational Huawei Technologies Co., Ltd. 5 Expires: January 7, 2013 July 6, 2012 7 Use Case for Telemedical with Multi-streams 8 draft-xiao-clue-telemedical-use-case-00.txt 10 Abstract 12 This memo presenst a telemedicine use case where multiple 13 presentation streams are used for conveying different information in 14 parallel to the main video from the surgery room 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on January 7, 2013. 33 Copyright Notice 35 Copyright (c) 2012 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Requirement for telemedical use case . . . . . . . . . . . . . 4 52 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 54 5. Informative References . . . . . . . . . . . . . . . . . . . . 5 55 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 57 1. Introduction 59 This use case describes a scenario where multiple presentation 60 streams are used. In this use case, the local site is a surgery room 61 connected to one or more different types of remote sites. In the 62 local site three main cameras capture the whole room. Multiple 63 presentation inputs are possible: a surgery camera which is used to 64 provide to zoomed view of the operation, an endoscopic monitor, an 65 X-ray CT image output device, a B-ultrasonic apparatus, a cardiogram 66 generator, an MRI image instrument, etc. These devices are used to 67 provide multiple local video presentation streams to help the surgeon 68 monitor the status of the patient and assist the process of the 69 surgery. 71 Three main screens and one (or more) presentation screen(s) are 72 provided. The main screens can be used to display the remote 73 experts. The presentation screen(s) can be used to display multiple 74 presentation streams from local and remote sites simultaneously. 75 Three main cameras capture different parts of the surgery room. The 76 surgeon can decide the number, the size and the placement of the 77 presentations displayed on the local presentation screen(s). He can 78 also indicate which local presentation captures are provided for the 79 remote sites. The local site can send multiple presentation captures 80 to remote sites and it can receive multiple presentations related to 81 the patient or the procedure from them. 83 One type of remote site is a single or dual screen and one camera 84 system with a consulting expert of a particular field present. In 85 the general case the remote sites can be part of a Telepresence 86 conference with multiple experts to start a consultation. The 87 presentation screens are also provided at the remote sites allowing 88 the experts to see the details of the operation and related data. 89 Like the main site, the experts can decide the number, the size and 90 the placement of the presentations displayed on the presentation 91 screens. The presentation screens can display presentation streams 92 from the surgery room or other remote sites and also presentation 93 streams generated locally by the remote site. Thus the experts can 94 also start sending presentation streams, which can carry medical 95 records, pathology data, or their reference and analysis, etc. 97 Another type of remote site is a typical immersive Telepresence room 98 with three camera/screen pairs allowing more experts to join the 99 consultation. These sites can also be used for education. The 100 teacher and the students are in different remote sites. Students can 101 observe and learn the details of the whole procedure, while the 102 teacher can explain and answer questions during the operation. 104 Generally, the education sites can only send streams among 105 themselves. For example, they can share slides and videos, but 106 neither their main captures nor their presentation captures are sent 107 to other sites (i.e. the surgery room and the experts). 109 All remote education sites can display the surgery room. Or they can 110 display it on the center screen, and the rest of the screens can show 111 the teacher and the student who is asking a question. 113 All remote sites shall display the zoomed surgery view on their 114 presentation screen. Other dynamic and static data can be optional 115 and up to user's decision. 117 For all the above sites, more presentation screens can be used to 118 enhance visibility: one screen for zoomed surgery stream and the 119 others for medical image streams, such as MRI images, cardiogram, 120 B-ultrasonic images and pathology data. 122 2. Requirement for telemedical use case 124 1. The solution must enable an endpoint to send and receive multiple 125 presentation captures. 127 2. The solution must support a means to identify presentation 128 captures, including the number, purpose, etc. 130 3. The solution must support multiple presentation sources from 131 different endpoints at the same time. 133 4. The solution must support means of enabling interoperability 134 between Telepresence endpoints that send and receive different 135 numbers of presentation streams. 137 5. The solution must support means of enabling interoperability 138 between Telepresence endpoints where presentation screens are of 139 different resolutions. 141 6. The solution must enable an endpoint to mix multiple presentation 142 captures locally. 144 Note: the last two requirements are included in the CLUE requirement 145 draft: 147 3. IANA Considerations 149 This document contains no IANA considerations. 151 4. Security Considerations 153 While there are likely to be security considerations for any solution 154 for telepresence interoperability, this document has no security 155 considerations. 157 5. Informative References 159 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 160 Requirement Levels", BCP 14, RFC 2119, March 1997. 162 Authors' Addresses 164 Lennard Xiao 165 Huawei Technologies Co., Ltd. 166 Shenzhen, 167 PRC 169 Email: lennard.xiao@huawei.com 171 Roni Even 172 Huawei Technologies Co., Ltd. 173 Tel Aviv, 174 Israel 176 Email: even.roni@huawei.com