Project status:

  • Paper initiation draft
  • Paper complete
Topics from the right

Authors/Editors

Top Level Messaging for the project/project stream

  • What is it?
  • What Does it do
  • What is the impact on stakeholders
    • stakeholders End-users: (Enterprise, multi-locations, Service Providers
    • what does enable: ability of providers to market more value-added services
    •  scale thousand, millions of users: $millions, $billions, $100s billions?
  • why now?
  • Why BBF?
    • Connects to all of the BBF initiatives, especially BAS, TR-317, Ultrafast, CloudCO
    • Not addressed elsewhere
    • required part of BBF vision for holistic broadband
    • Complements work of other SDOs, OS groups

next steps:

  • powerpoint that captures the above (needs graphics)?
  • Short paper or article
  • press release(Provider endorses identified) (timing??)
  • engage Layer 123 for the Hague event
  • Write web page


Introduction

This short paper is relates to (what is it) ...  The resulting work will enable.... The potential impact of the work is

etc.
etc.
Summary, Call to actionLinks, etc.

Status/Approval

VersionVersion editorProject StatusChanges in this versionWiki page version

original is .01

1.0 is first approved version


e.g. original , member notification, draft approved, update, straw ballot, final ballot, published work, etc


required for approved and ballot versions

For papers requiring ToC use this

Considerations (as a starting point)

The following considerations dictate the style of the deliverable being created. The term "white paper" implies a set of text and diagrams the may be published in various forms papers, articles, briefings, web pages, etc.

Is there a top level of positioning  & messaging for the project?

  • If not complete the section on the left

Deliverable examples document/paper/page types:

  • New Project briefing - coincides with approval of BBF project
  • Positioning paper
  • Educational Paper- helps reader understand technical work
  • Best practices paper. - provides implementation guidance
  • Use Case or application note
  • Presentation

Structure, Length

  • There probably is no right structure with a couple of exceptions
  • Introduction must be clear and motivate the reader:
    • what is the paper about. and why are we writing it?
    • If it's about technical work then, what is it why is it, what does it do, what's the impact, how many does it impact and what is the business value of the work to stakeholders?
  • Body of the document
    • Dependent on the paper
    • Informative papers should be specific and with use case examples that are realizable
    • Genral information about the problems that need addressing without a proposed solution are generally of little value and may just irritated the reader who knows about the problems and is reading to find a solution.
  • Length
    • Dependent on the paper type but the shorter the better. If the paper has good detailed technical information or multiple use case then longer papers may be justified
    • Briefings are likely a single web page / 3-500 words
  • summary
    • return to the importance how the work could make a difference for the reader and their organization
    • return to reason why we wrote it and there must be a recommended call to action and expected outcome

Unless this is something

Language, Respect

  • This is declared to be an acronym-free zone.
  • there was one diagram shown recently that had 14 unexplained acronyms
  • Only if a term is used more than once may the construct Xxxxxx Yyy Zzz(XYZ) be used. Use of unexplained acroynms, is arrogant, and the fastest way  to stop the understanding of a piece
  • Avoid pontification with supposedly insightful wisdom, People want facts and actions

Purpose of paper

  • What is it?
  • who does it help?
  • Why is it impactful?

Technical Papers

  • Use cases for the work etc
  • Project description
  • Timeline
  • Getting people to participate at the BBF

Positioning papers

  • Why the BBF is doing the work?

Network diagram or graphic

Audience

Publication type

  • Web Page
  • Article
  • Posted white paper
  • Social media

Format

  • Toc?
  • Length
  • 1 page, 3-4 pages. 6-8 pages
  • The whole traditional BBF format does not work for short papers

Delivery and promotion

  • Consider infographs, blogs, articles, web pages,mixed media, video  delivery perhaps called videopapers), not just PDFs

Table of Contents

FiguresLink
Open Broadband Continuous Integration

Remote Surgery

A common robotic surgical system generally consists of one or more robotic arms (controlled by the surgeon), a surgeon console, and a sensory system giving feedback to the user [1]. Usually, the robotic surgical system consists of a surgeon's console that is typically in the same room as the patient, and a patient-side cart with interactive robotic arms controlled from the console. The surgeon uses the console's master controls to maneuver the patient-side cart's robotic arms. The instruments' jointed-wrist design exceeds the natural range of motion of the human hand; motion scaling and tremor reduction further interpret and refine the surgeon's hand movements. The robotic surgical system always requires a human operator, and incorporates multiple redundant safety features designed to minimize opportunities for human error when compared with traditional approaches. Figure 1 indicates one robotic surgery scenario using robotic surgical system.

Figure 1 Example of robotic surgical system
In the robotic surgery prototype, the surgeon before the console is seated at a 20-foot distance from the patient cart and surgical robot as the shown in the Figure 2.

Figure 2 One Example of Robotic Surgery Prototype
Remote surgery (also known as telesurgery) is the ability for a doctor to perform surgery on a patient even though they are not physically in the same location. It further includes the high-speed communication networks, connecting the surgical robot in one location to the surgeon console at another location manipulating the robot through an operation. 
Remote telesurgery allows the specialized surgeons to be available to the patients worldwide, without the need for patients to travel beyond their local hospital. This is illustrated in the following Figure 3. Think of an injured soldier needing immediate, specialized surgery on a battlefield. Then consider a reality where a surgeon wouldn't need to enter said war zone to operate on a soldier, but could perform the surgery from thousands of miles away. Or, imagine a doctor in an urban city, performing an urgent procedure on a patient in an inaccessible rural area.

Figure 3 Remote Telesurgery
The concept of telesurgery is certainly not a brand new one. In fact, it's been around for more than a decade. Back in the early 2000's, the first complete trans-atlantic robotic surgery happened in 2001 [2], Dr. Jacques Marescaux in New York removed a 68-year-old woman's gall-bladder as she lay across the ocean in Strasbourg, France, more than 7,000 kilometers away shown in Figure 4.


Figure 4 Dr. Jacques Marescaux was operating remotely
The Communication networks between the New York and Strasbourg were done through asynchronous transfer mode (ATM) technology (France Telecom/Equant's, Paris, France). ATM network nodes are interconnected through a high-speed terrestrial fiber-optic network that transports data through virtual connections dedicated per customer, providing a low transport delay, high reliability and low packet loss ratio [3]. However, the expense of dedicated ATM network is highly costly, there was no practical way to transmit large amounts of data quickly or reliably enough to make the concept a reality, it will be preferable to use conventional network infrastructures for the future expansion of telesurgery.

Impacts on the Network

With the development of 5G research, a recent 5G White Paper deliverable from Next Generation Mobile Network (NGMN) releases several 5G characteristics [4]. Remote surgery is part of what is characterized as "Ultra-reliable Communications". In order to ensure a telesurgery procedure to be highly safe, we would require a particularly unique demand on the network, at least including very reliable connection (99.999% availability), sufficient bandwidth to ensure adequate video resolution as required by the remote surgeon controlling the robot, as little as possible latency allowing the feel of instantaneous reaction to the actions of the surgeons and of course as little as possible latency variation (i.e., jitter) allowing system or human correction of the latency.
The Nicholson Center at Florida Hospital has successfully tested the latency time created by the Internet for a simulated robotic surgery in Ft. Worth, Texas, more than 1,200 miles away from the surgeon in Orlando hospital campuses [<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="8dc6c2ad-06a3-4f10-a62e-6b823da96df0"><ac:parameter ac:name="">_Hlt492042456</ac:parameter></ac:structured-macro>5]. The experiment aims to determine the end-to-end latency threshold--that is, the amount of delay a surgeon can experience between the moments they perform an action to the moment video of the action being carried out at the surgery site reaches their eyes. The problem has less to do with the speed of light at which electrons travel via fiber optics and more to do with Internet provider processing times. To find the E2E latency threshold, the team used simulators to introduce a video delay while having surgeons perform basic surgical tasks.
Findings show that at 200 milliseconds, surgeons could not detect a lag time. From 300 to 500 milliseconds, some surgeons could detect lag time, but they were able to compensate for it by pausing their movement. But at 600 milliseconds, most surgeons became insecure about their ability to perform a procedure.

Figure 5 the effects of lag times on remote telesurgery
From above scientific study, that E2E latency beyond 200 milliseconds affects the performance of surgeons and beyond 250 milliseconds it is very difficult for surgeons to operate at all. The system immanent latency of a modern operating robot is already around 180 milliseconds (Da Vinci System) [6]. That means the transmission latency for remote telesurgery is around 20~30 milliseconds.
Based on above latency requirements analysis, and the current performance of broadband networks, it is clear that some changes need to be made to the current broadband network in order to successfully incorporate telesurgery service in the near future.

Reference


[1] Da Vinci Surgical System: https://en.wikipedia.org/wiki/Da<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="ea653c98-cb13-42dd-9b94-0207a146b473"><ac:parameter ac:name="">_Hlt491935496</ac:parameter></ac:structured-macro><ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="094929d6-0ceb-4110-b57d-c3c5adf4d873"><ac:parameter ac:name="">_Hlt491935497</ac:parameter></ac:structured-macro>_Vinci_Surgical_System;
[2] First Complete Trans-Atlantic Robotic Surgery: https://www.scientificamerican.com/article/first-complete-trans-atla/;
[3] Transcontinental Robot-Assisted Remote Telesurgery: Feasibility and Potential Applications: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1422462/
[4] 5G White Paper: https://www.ngmn.org/5g-white-paper.html
[5] Hospital tests lag time for robotic surgery 1,200 miles away from doctor: https://www.computerworld.com/article/2927471/healthcare-it/robot-performs-test-surgery-1200-miles-away-from-doctor.html
[6] 5G and e-Health: https://5g-ppp.eu/wp-content/uploads/2016/02/5G-PPP-White-Paper-on-eHealth-Vertical-Sector.pdf
End New Text