Diff: rfc9699.original.xml

	rfc9699.original.xml	rfc9699.xml

	<?xml version='1.0' encoding='utf-8'?>	<?xml version='1.0' encoding='UTF-8'?>

	<!DOCTYPE rfc [	<!DOCTYPE rfc [
	<!ENTITY nbsp " ">	<!ENTITY nbsp " ">
	<!ENTITY zwsp "">	<!ENTITY zwsp "">
	<!ENTITY nbhy "‑">	<!ENTITY nbhy "‑">
	<!ENTITY wj "⁠">	<!ENTITY wj "⁠">
	]>	]>

	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" category="info
	" docName="draft-ietf-mops-ar-use-case-18" obsoletes="" updates="" submissionTyp	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" category="info
	e="IETF" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version=	" docName="draft-ietf-mops-ar-use-case-18" number="9699" consensus="true" obsole
	"3">	tes="" updates="" submissionType="IETF" xml:lang="en" tocInclude="true" symRefs=
	<!-- xml2rfc v2v3 conversion 3.11.1 -->	"true" sortRefs="true" version="3">

		<!-- [rfced] How may we update the abbreviated title to better align with the
		document title? The acronym MOPS does not appear elsewhere in the
		document, and the document title uses "Extended Reality" rather than "AR".

		Note: The abbreviated title only appears in the pdf output (in the running
		header at the top of each page).

		Original:
		MOPS AR Use Case

		Perhaps:
		XR Use Case
		-->

		<!-- [rfced] The document title uses "a Use Case" and "Extended Reality
		Application" (singular), while the abstract uses "use cases" and
		"Extended Reality (XR) applications" (plural). Please review and let us
		know if any updates are needed.

		Document title:
		Media Operations Use Case for an Extended Reality Application on Edge
		Computing Infrastructure

		Abstract:
		This document explores the issues involved in the use of Edge
		Computing resources to operationalize media use cases that involve
		Extended Reality (XR) applications.
		...
		In particular, this document
		discusses those applications that run on devices ...
		-->

		<!-- [rfced] Please review the placement of this sentence in the
		abstract. Would it be helpful to move this sentence to be the last
		sentence in the abstract? Or do you prefer the current location?

		Original:
		The intended audience for this document are network operators who are
		interested in providing edge computing resources to operationalize
		the requirements of such applications.
		-->

	<front>	<front>

	<title abbrev="MOPS AR Use Case">Media Operations Use Case for an Extended R	<title abbrev="MOPS AR Use Case">Media Operations Use Case for an Extended
	eality Application on Edge Computing Infrastructure</title>	Reality Application on Edge Computing Infrastructure</title>
	<seriesInfo name="Internet-Draft" value="draft-ietf-mops-ar-use-case-18"/>	<seriesInfo name="RFC" value="9699"/>
	<author fullname="Renan Krishna" initials="R." surname="Krishna">	<author fullname="Renan Krishna" initials="R." surname="Krishna">


	<address>	<address>
	<postal>	<postal>


	<country>United Kingdom</country>	<country>United Kingdom</country>
	</postal>	</postal>
	<email>renan.krishna@gmail.com</email>	<email>renan.krishna@gmail.com</email>

	<uri/>
	</address>	</address>
	</author>	</author>
	<author initials="A." surname="Rahman" fullname="Akbar Rahman">	<author initials="A." surname="Rahman" fullname="Akbar Rahman">
	<organization>Ericsson</organization>	<organization>Ericsson</organization>
	<address>	<address>
	<postal>	<postal>
	<street>349 Terry Fox Drive</street>	<street>349 Terry Fox Drive</street>

	<city>Ottawa Ontario</city>	<city>Ottawa</city>
		<region>Ontario</region>
	<code>K2K 2V6</code>	<code>K2K 2V6</code>
	<country>Canada</country>	<country>Canada</country>

	<region/>
	</postal>	</postal>

	<phone/>
	<email>Akbar.Rahman@ericsson.com</email>	<email>Akbar.Rahman@ericsson.com</email>

	<uri/>
	</address>	</address>
	</author>	</author>

	<date />	<date month="December" year="2024"/>
	<area>Operations and Management</area>	<area>OPS</area>
	<workgroup> MOPS</workgroup>	<workgroup>mops</workgroup>
	<abstract>
	<t>


	This document explores the issues involved in the use of Edge Com	<!-- [rfced] Please insert any keywords (beyond those that appear in
	puting resources to operationalize media use cases	the title) for use on https://www.rfc-editor.org/search. -->
	that involve Extended Reality (XR) applications. In particular, t
	his document discusses those applications that run on devices having different	<keyword>example</keyword>
	form factors (such as different physical sizes and shapes) and ne
	ed Edge computing resources to mitigate the effect of problems such as a need to	<abstract>
	support interactive communication	<t>This document explores the issues involved in the use of Edge
	requiring low latency, limited battery power, and heat dissipatio	Computing resources to operationalize media use cases that involve
	n from those devices. The intended audience for this document are network	Extended Reality (XR) applications. In particular, this document
	operators who are interested in providing edge computing resource	discusses XR applications that run on devices having different form
	s to operationalize the requirements of such applications.	factors (such as different physical sizes and shapes) and need Edge
	This document discusses the expected behavior of XR applications	computing resources to mitigate the effect of problems such as the need
	which can be used to manage the traffic.	to support interactive communication requiring low latency, limited
	In addition, the document discusses the service requirements of X	battery power, and heat dissipation from those devices. Network
	R applications to be able to run on the network.	operators who are interested in providing edge computing resources to
		operationalize the requirements of such applications are the intended
		audience for this document. This document also discusses the expected
		behavior of XR applications, which can be used to manage traffic, and
		the service requirements for XR applications to be able to run on the
		network.

	</t>	</t>
	</abstract>	</abstract>
	</front>	</front>
	<middle>	<middle>
	<section anchor="introduction" numbered="true" toc="default">	<section anchor="introduction" numbered="true" toc="default">
	<name>Introduction</name>	<name>Introduction</name>
	<t>	<t>

	Extended Reality (XR) is a term that includes Augmented Reality (	Extended Reality (XR) is a term that includes Augmented
	AR), Virtual Reality (VR) and Mixed Reality (MR) <xref target="XR" format="defau	Reality (AR), Virtual Reality (VR), and Mixed Reality (MR)
	lt"/>.	<xref target="XR" format="default"/>. AR combines the real
	AR combines the real and virtual, is interactive and is aligned t	and virtual, is interactive, and is aligned to the physical
	o the physical world of the user <xref target="AUGMENTED_2" format="default"/>.	world of the user <xref target="AUGMENTED_2"
	On the other hand,	format="default"/>. On the other hand, VR places the user
	VR places the user inside a virtual environment generated by a co	inside a virtual environment generated by a computer <xref
	mputer <xref target="AUGMENTED" format="default"/>.MR merges the real and virtua	target="AUGMENTED" format="default"/>. MR merges the real and
	l world along a	virtual along a continuum that connects a completely real
	continuum that connects completely real environment at one end to	environment at one end to a completely virtual environment at
	a completely virtual environment at the other end. In this continuum, all	the other end. In this continuum, all combinations of the real
	combinations of the real and virtual are captured <xref target="A	and virtual are captured <xref target="AUGMENTED"
	UGMENTED" format="default"/>.	format="default"/>.
	</t>	</t>

	<t>
	XR applications will bring several requirements for the network and t	<!-- [rfced] Section 1: Will readers understand what "This" refers to in the
	he	second sentence below? The first sentence is included for context.
	mobile devices running these applications. Some XR applications s
	uch as AR require a real-time processing of video streams to	Original:
	recognize specific objects. This is then used to overlay informat	Some XR applications
	ion on the	such as AR require a real-time processing of video streams to
	video being displayed to the user. In addition, XR applications	recognize specific objects. This is then used to overlay information
	such as AR and VR will also require generation of new video	on the video being displayed to the user.
	frames to be played to the user. Both the real-time processing of
	video streams and the generation of overlay information	Perhaps:
	are computationally intensive tasks that generate heat <xref targ	Some XR applications
	et="DEV_HEAT_1" format="default"/>, <xref target="DEV_HEAT_2" format="default"/>	such as AR require a real-time processing of video streams to
	and drain battery power <xref target="BATT_DRAIN" format="default	recognize specific objects. This processing is then used to overlay informat
	"/> on the mobile device running the XR application.	ion
	Consequently, in order to run applications with XR characteristic	on the video being displayed to the user.
	s
	on mobile devices, computationally intensive tasks need to be off	Or:
	loaded to resources provided by Edge Computing.	Some XR applications
		such as AR require a real-time processing of video streams to
		recognize specific objects. The objects are then used to overlay information
		on the video being displayed to the user.
		-->

		<!-- [rfced] Section 1: May we update "XR applications such as AR" and "XR
		applications such as AR and VR" as follows for clarity?

		Original:
		Some XR applications
		such as AR require a real-time processing of video streams to
		recognize specific objects.
		...
		In addition, XR
		applications such as AR and VR will also require generation of new
		video frames to be played to the user.

		Perhaps:
		Some XR applications
		(such as AR applications) require real-time processing of video streams to
		recognize specific objects.
		...
		In addition, other XR
		applications (such as AR and VR applications) will also require generation
		of new video frames to be played to the user.

		Or:
		Some XR applications
		(specifically, AR applications) require real-time processing of video stream
		s to
		recognize specific objects.
		...
		In addition, other XR
		applications (specifically, AR and VR applications) will also require generat
		ion
		of new video frames to be played to the user.
		-->

		<t>
		XR applications have several requirements for the network and the
		mobile devices running these applications. Some XR applications
		such as AR require real-time processing of video streams to
		recognize specific objects. This is then used to overlay
		information on the video being displayed to the user. In
		addition, XR applications such as AR and VR will also require
		generation of new video frames to be played to the user. Both the
		real-time processing of video streams and the generation of
		overlay information are computationally intensive tasks that
		generate heat <xref target="DEV_HEAT_1" format="default"/> <xref
		target="DEV_HEAT_2" format="default"/> and drain battery power
		<xref target="BATT_DRAIN" format="default"/> on the mobile device
		running the XR application. Consequently, in order to run
		applications with XR characteristics on mobile devices,
		computationally intensive tasks need to be offloaded to resources
		provided by Edge Computing.
	</t>	</t>
	<t>	<t>

	Edge Computing is an emerging paradigm where for the purpose of t	Edge Computing is an emerging paradigm where, for the purpose of
	his document, computing resources and storage are made available in close	this document, computing resources and storage are made available in close
	network proximity at the edge of the Internet to mobile devices a	network proximity at the edge of the Internet to mobile devices a
	nd sensors <xref target="EDGE_1" format="default"/>, <xref target="EDGE_2" forma	nd sensors <xref target="EDGE_1" format="default"/> <xref target="EDGE_2" format
	t="default"/>. A computing resource or storage is in	="default"/>. A computing resource or storage is in
	close network proximity to a mobile device or sensor if there is a short and high-capacity network path to it	close network proximity to a mobile device or sensor if there is a short and high-capacity network path to it
	such that the latency and bandwidth requirements of applications running on those mobile devices or sensors can be met.	such that the latency and bandwidth requirements of applications running on those mobile devices or sensors can be met.

	These edge computing devices use cloud technologies that enable t hem to support offloaded XR applications. In particular, cloud implementation te chniques <xref target="EDGE_3" format="default"/> such as the follows can be dep loyed:	These edge computing devices use cloud technologies that enable t hem to support offloaded XR applications. In particular, cloud implementation te chniques <xref target="EDGE_3" format="default"/> such as the following can be d eployed:
	</t>	</t>


	<ul spacing="normal">	<dl spacing="normal">
	<li>Disaggregation (using SDN to break vertically integrated systems int	<dt>Disaggregation:</dt><dd>Using Software-Defined Networking (SDN) to b
	o independent components- these components can have open interfaces which are st	reak vertically integrated systems into independent components. These components
	andard, well documented and not proprietary),	can have open interfaces that are standard, well documented, and non-proprietar
	</li>	y.</dd>
	<li>Virtualization (being able to run multiple independent copies of tho
	se components such as SDN Controller apps, Virtual Network Functions on a	<dt>Virtualization:</dt><dd>Being able to run multiple independent copie
	common hardware platform).</li>	s of those components, such as SDN Controller applications and Virtual Network F
	<li>Commoditization (being able to elastically scale those virtual compo	unctions, on a
	nents across commodity hardware as the workload dictates).</li>	common hardware platform.</dd>
	</ul>	<dt>Commoditization:</dt><dd>Being able to elastically scale those virtu
		al components across commodity hardware as the workload dictates.</dd>
		</dl>

	<t>	<t>

	Such techniques enable XR applications requiring low-latency and high bandwidth to be delivered by proximate edge devices. This is because the d isaggregated components can run on proximate edge devices rather than on remote cloud several hops away and deliver low latency, high bandwidth service to offlo aded applications <xref target="EDGE_2" format="default"/>.	Such techniques enable XR applications that require low latency and high bandwidth to be delivered by proximate edge devices. This is because th e disaggregated components can run on proximate edge devices rather than on a re mote cloud several hops away and deliver low-latency, high-bandwidth service to offloaded applications <xref target="EDGE_2" format="default"/>.
	</t>	</t>


		<!-- [rfced] Section 1: May we combine these sentences as follows to improve
		readability?

		Original:
		Examples of form factors include Head Mounted Displays
		(HMD) such as Optical-see through HMDs and video-see-through HMDs and
		Hand-held displays. Smart phones with video cameras and location
		sensing capabilities using systems such as a global navigation
		satellite system (GNSS) are another example of such devices.

		Perhaps:
		Examples of form factors include the following: 1) head-mounted displays
		(HMDs), such as optical see-through HMDs and video see-through HMDs, 2)
		hand-held displays, and 3) smartphones with video cameras and location-
		sensing capabilities using systems such as a global navigation
		satellite system (GNSS).
		-->

	<t>	<t>

	This document discusses the issues involved when edge computing resourc	This document discusses the issues involved when edge computing
	es are offered by network operators to	resources are offered by network operators to operationalize the
	operationalize the requirements of XR applications running on devices w	requirements of XR applications running on devices with various form
	ith various form factors. A network operator for the purposes of this	factors. For the purpose of this document, a network operator is
	document is any organization or individual that manages or operates the	any organization or individual that manages or operates the computing
	compute resources or storage in close network proximity	resources or storage in close network proximity to a mobile device
	to a mobile device or sensors. Examples of form factors	or sensor. Examples of form factors include head-mounted displays
	include Head Mounted Displays (HMD) such as Optical-see through HMDs an	(HMDs), such as optical see-through HMDs and video see-through HMDs,
	d video-see-through HMDs and Hand-held displays.	and hand-held displays. Smartphones with video cameras and
	Smart phones with video cameras and location sensing capabilities using	location-sensing capabilities using systems such as a global
	systems such as a global navigation satellite system (GNSS) are another example	navigation satellite system (GNSS) are another example of such devices.
	of such devices. These devices have limited	These devices have limited battery capacity and dissipate
	battery capacity and dissipate heat when running. Besides as the user o	heat when running. Also, as the user of these devices moves around
	f these devices moves around as they run the	as they run the XR application, the wireless latency and bandwidth
	XR application, the wireless latency and bandwidth available to the dev	available to the devices fluctuates, and the communication link
	ices fluctuates and the communication link itself	itself might fail. As a result, algorithms such as those based on
	might fail. As a result, algorithms such as those based on adaptive-bit	Adaptive Bitrate (ABR) techniques that base their policy on heuristics
	-rate techniques that base their policy on heuristics	or
	or models of deployment perform sub-optimally in such dynamic environme	models of deployment perform sub-optimally in such dynamic
	nts <xref target="ABR_1" format="default"/>.	environments <xref target="ABR_1" format="default"/>. In addition,
	In addition, network operators can expect that the parameters that char	network operators can expect that the parameters that characterize
	acterize the expected behavior of XR applications	the expected behavior of XR applications are heavy-tailed. Heaviness
	are heavy-tailed. Heaviness of tails is defined as the difference from	of tails is defined as the difference from the normal distribution
	the normal distribution in the proportion of the values that fall a long way fro	in the proportion of the values that fall a long way from the mean
	m the mean <xref target="HEAVY_TAIL_3" format="default"/>. Such workloads requir	<xref target="HEAVY_TAIL_3" format="default"/>. Such workloads
	e appropriate resource management policies to be used on the Edge.	require appropriate resource management policies to be used on the
	The service requirements of XR applications are also challenging when c	Edge. The service requirements of XR applications are also
	ompared to the current video applications.	challenging when compared to current video applications. In
	In particular several Quality of Experience (QoE) factors such as motio	particular, several Quality-of-Experience (QoE) factors such as
	n sickness are unique to XR applications and must be considered when operational	motion sickness are unique to XR applications and must be considered
	izing a network.	when operationalizing a network.


	This document motivates these issues with a use-case that is pres	<!-- [rfced] Section 1: Is "motivates" the correct word choice here? Would
	ented in the following sections.	"addresses", "examines", or something similar be better?

		Original:
		This document motivates these issues
		with a use-case that is presented in the following sections.
		-->

		This document motivates these issues with a use case that is pres
		ented in the following section.
	</t>	</t>
	</section>	</section>

	<section anchor="use_case" numbered="true" toc="default">	<section anchor="use_case" numbered="true" toc="default">
	<name>Use Case</name>	<name>Use Case</name>


		<!-- [rfced] Section 2: We updated "application with XR systems'
		characteristics" as "application with characteristics of an XR
		system". Would it be helpful to further update in one of the ways shown
		below?

		Original:
		A use case is now described that involves an application with XR
		systems' characteristics.

		Current:
		This use case involves an application with characteristics of an
		XR system.

		Perhaps:
		This use case involves an XR application.

		Or:
		This use case involves an XR application running on a mobile device.
		-->

	<t>	<t>

	A use case is now described that involves an application with	This use case involves an application with characteristics of an
	XR systems' characteristics. Consider a group of tourists who ar	XR system. Consider a group of tourists who are taking a
	e being	tour around the historical site of the Tower of London. As
	conducted in a tour around the historical site of the Tower of L	they move around the site and within the historical
	ondon.	buildings, they can watch and listen to historical scenes in
	As they move around the site and within the historical buildings	3D that are generated by the XR application and then overlaid
	, they can	by their XR headsets onto their real-world view. The headset
	watch and listen to historical scenes in 3D that are generated b	continuously updates their view as they move around.
	y the XR application and then
	overlaid by their XR headsets onto their real-world view. The he
	adset then continuously updates their view as they move around.
	</t>	</t>
	<t>	<t>

	The XR application first processes the scene that the walking to urist is watching in real-time and identifies objects	The XR application first processes the scene that the walking to urist is watching in real time and identifies objects
	that will be targeted for overlay of high-resolution videos. It t hen generates high-resolution 3D images	that will be targeted for overlay of high-resolution videos. It t hen generates high-resolution 3D images

	of historical scenes related to the perspective of the tourist i	of historical scenes related to the perspective of the tourist in
	n real-time. These generated video images are then	real time. These generated video images are then
	overlaid on the view of the real-world as seen by the tourist.	overlaid on the view of the real world as seen by the tourist.
	</t>	</t>
	<t>	<t>
	This processing of scenes	This processing of scenes

	and generation of high-resolution images is now discussed in grea ter detail.	and generation of high-resolution images are discussed in greater detail below.

	</t>	</t>
	<section anchor="processsing_of_scenes" numbered="true" toc="default">	<section anchor="processsing_of_scenes" numbered="true" toc="default">
	<name>Processing of Scenes</name>	<name>Processing of Scenes</name>
	<t>	<t>

	The task of processing a scene can be broken down into a pipeline	The task of processing a scene can be broken down into a pipeline
	of three consecutive subtasks namely tracking, followed by an acquisition of a	of three consecutive subtasks: tracking, acquisition of a
	model of the real world, and finally registration <xref target="A	model of the real world, and registration <xref target="AUGMENTED
	UGMENTED" format="default"/>.	" format="default"/>.

	</t>
	<t>
	Tracking: The XR application that runs on the mobile device needs
	to track the six-dimensional pose (translational in the three perpendicular axe
	s and rotational about those three axes)
	of the user's head, eyes and the objects that are in view <xref t
	arget="AUGMENTED" format="default"/>. This requires tracking natural features (f
	or example points or edges of objects) that are then used in the next stage of t
	he pipeline.
	</t>
	<t>
	Acquisition of a model of the real world: The tracked natural fea
	tures are used to develop a model of the real world. One of the ways this is don
	e is to develop an annotated
	point cloud (a set of points in space that are annotated with des
	criptors) based model that is then stored in a database. To ensure that this dat
	abase can be scaled up, techniques such as
	combining a client-side simultaneous tracking and mapping and a s
	erver-side localization
	are used to construct a model of the real world <xref target="SLA
	M_1" format="default"/>, <xref target="SLAM_2" format="default"/>, <xref target=
	"SLAM_3" format="default"/>, <xref target="SLAM_4" format="default"/>. Another m
	odel that can be built is based on polygon mesh and texture mapping technique. T
	he polygon mesh encodes a 3D object's shape which is expressed as a collection o
	f small flat surfaces that are polygons. In texture mapping, color patterns are
	mapped on to an object's surface. A third modelling technique uses a 2D lightfie
	ld that describes the intensity or color of the light rays arriving at a single
	point from arbitrary directions. Such a 2D lightfield is stored as a two-dimensi
	onal table. Assuming distant light sources, the single point is approximately va
	lid for small scenes. For larger scenes, many 3D positions are additionally stor
	ed making the table 5D. A set of all such points (either 2D or 5D lightfield) ca
	n then be used to construct a model of the real world <xref target="AUGMENTED" f
	ormat="default"/>.
	</t>	</t>

	<t>
	Registration: The coordinate systems, brightness, and color
	of virtual and real objects need to be aligned with each other an
	d this process is called registration <xref target="REG" format="default"/>.
	Once the
	natural features are tracked as discussed above, virtual objects
	are geometrically aligned with those features by geometric registration. This is
	followed by
	resolving occlusion that can occur between virtual and the real o
	bjects <xref target="OCCL_1" format="default"/>, <xref target="OCCL_2" format="d
	efault"/>.


	The XR application also applies photometric registration <xref ta	<dl newline="false" spacing="normal">
	rget="PHOTO_REG" format="default"/>
	by aligning the brightness and color between the virtual and	<dt>Tracking:</dt><dd>The XR application that runs on the mobile
	real objects. Additionally, algorithms that calculate global illu	device
	mination of both the virtual and real objects <xref target="GLB_ILLUM_1" format=	needs to track the six-dimensional pose (translational in the
	"default"/>,	three perpendicular axes and rotational about those three
	<xref target="GLB_ILLUM_2" format="default"/> are executed. Vario	axes) of the user's head, eyes, and objects that are in
	us algorithms to deal with artifacts generated by lens distortion <xref target="	view <xref target="AUGMENTED" format="default"/>. This
	LENS_DIST" format="default"/>,	requires tracking natural features (for example, points or
	blur <xref target="BLUR" format="default"/>, noise <xref target="	edges of objects) that are then used in the next stage of the
	NOISE" format="default"/> etc. are also required.	pipeline.</dd>
	</t>
		<dt>Acquisition of a model of the real world:</dt><dd>The
		tracked natural features are used to develop a model of the
		real world. One of the ways this is done is to develop a model ba
		sed on an
		annotated point cloud (a set of points in space that are
		annotated with descriptors) that is then stored in
		a database. To ensure that this database can be scaled up,
		techniques such as combining client-side simultaneous
		tracking and mapping with server-side localization are used
		to construct a model of the real world <xref target="SLAM_1"
		format="default"/> <xref target="SLAM_2" format="default"/>
		<xref target="SLAM_3" format="default"/> <xref target="SLAM_4"
		format="default"/>. Another model that can be built is based
		on a polygon mesh and texture mapping technique. The polygon
		mesh encodes a 3D object's shape, which is expressed as a
		collection of small flat surfaces that are polygons. In
		texture mapping, color patterns are mapped onto an object's
		surface. A third modeling technique uses a 2D lightfield that
		describes the intensity or color of the light rays arriving at
		a single point from arbitrary directions. Such a 2D lightfield
		is stored as a two-dimensional table. Assuming distant light
		sources, the single point is approximately valid for small
		scenes. For larger scenes, many 3D positions are additionally
		stored, making the table 5D. A set of all such points (either a
		2D or 5D lightfield) can then be used to construct a model of
		the real world <xref target="AUGMENTED"
		format="default"/>.</dd>

		<dt>Registration:</dt><dd>The coordinate systems,
		brightness, and color of virtual and real objects need to be
		aligned with each other; this process is called
		"registration" <xref target="REG" format="default"/>. Once the
		natural features are tracked as discussed above, virtual
		objects are geometrically aligned with those features by
		geometric registration. This is followed by resolving
		occlusion that can occur between virtual and real objects
		<xref target="OCCL_1" format="default"/> <xref target="OCCL_2"
		format="default"/>.

		The XR application also applies photometric registration <xref
		target="PHOTO_REG" format="default"/> by aligning
		brightness and color between the virtual and real
		objects. Additionally, algorithms that calculate global
		illumination of both the virtual and real objects <xref
		target="GLB_ILLUM_1" format="default"/> <xref
		target="GLB_ILLUM_2" format="default"/> are executed. Various
		algorithms are also required to deal with artifacts generated by
		lens distortion
		<xref target="LENS_DIST" format="default"/>, blur <xref
		target="BLUR" format="default"/>, noise <xref target="NOISE"
		format="default"/>, etc.</dd>
		</dl>
	</section>	</section>
	<section anchor="generation" numbered="true" toc="default">	<section anchor="generation" numbered="true" toc="default">
	<name>Generation of Images</name>	<name>Generation of Images</name>


		<!-- [rfced] Section 2.2: Will readers know what "the previous step" is?

		Original:
		The XR application must generate a high-quality video that has the
		properties described in the previous step and overlay the video on
		the XR device's display

		Perhaps:
		The XR application must generate a high-quality video that has the
		properties described in the previous section and overlay the video on
		the XR device's display

		Or:
		The XR application must generate a high-quality video that has the
		properties described above and overlay the video on
		the XR device's display
		-->

	<t>	<t>
	The XR application must generate a high-quality video that has th e properties described in the previous step	The XR application must generate a high-quality video that has th e properties described in the previous step

	and overlay the video on the XR device's display- a step called s ituated visualization. A situated visualization is a visualization in which the virtual objects that need to be seen by the XR user are overlaid correctly on th e real world. This entails dealing with registration errors that	and overlay the video on the XR device's display. This step is ca lled "situated visualization". A situated visualization is a visualization in wh ich the virtual objects that need to be seen by the XR user are overlaid correct ly on the real world. This entails dealing with registration errors that
	may arise, ensuring that there is no visual interference <xref ta rget="VIS_INTERFERE" format="default"/>, and finally maintaining	may arise, ensuring that there is no visual interference <xref ta rget="VIS_INTERFERE" format="default"/>, and finally maintaining
	temporal coherence by adapting to the movement of user's eyes and head.	temporal coherence by adapting to the movement of user's eyes and head.
	</t>	</t>
	</section>	</section>
	</section>	</section>
	<section anchor="Req" numbered="true" toc="default">	<section anchor="Req" numbered="true" toc="default">
	<name>Technical Challenges and Solutions</name>	<name>Technical Challenges and Solutions</name>

		<!-- [rfced] Section 3: Should this sentence mention solutions in addition to
		challenges? We note the title of the section is "Technical Challenges and
		Solutions".

		Original:
		This section will
		discuss the challenges such applications can face as a consequence.

		Perhaps:
		This section
		discusses the challenges such applications can face as a consequence and
		offers some solutions.
		-->

	<t>	<t>

	As discussed in section 2, the components of XR applications perform task	As discussed in <xref target="use_case"/>, the components of XR applicati
	s such as real-time generation and processing of	ons perform tasks that are computationally intensive, such as real-time generati
	high-quality video content that are computationally intensive. Th	on and processing of
	is section will discuss the challenges such applications can face as a consequen	high-quality video content. This section discusses the challenges
	ce.</t> <t>As a result of performing computationally intensive tasks on XR devic	such applications can face as a consequence.</t> <t>As a result of performing c
	es such as XR glasses,	omputationally intensive tasks on XR devices such as XR glasses,
	excessive heat is generated by the chip-sets that are involved	excessive heat is generated by the chipsets that are involved
	in the computation <xref target="DEV_HEAT_1" format="default"/>,	in the computation <xref target="DEV_HEAT_1" format="default"/> <
	<xref target="DEV_HEAT_2" format="default"/>. Additionally,	xref target="DEV_HEAT_2" format="default"/>. Additionally,
	the battery on such devices discharges quickly when running	the battery on such devices discharges quickly when running
	such applications <xref target="BATT_DRAIN" format="default"/>.	such applications <xref target="BATT_DRAIN" format="default"/>.

	</t>	</t>
	<t>	<t>

	A solution to the heat dissipation and battery drainage problem is to off load the processing and video generation tasks	A solution to problem of heat dissipation and battery drainage is to offl oad the processing and video generation tasks
	to the remote cloud. However, running such tasks on the cloud is not feas ible as the end-to-end delays	to the remote cloud. However, running such tasks on the cloud is not feas ible as the end-to-end delays
	must be within the order of a few milliseconds. Additionally, suc h applications require high bandwidth	must be within the order of a few milliseconds. Additionally, suc h applications require high bandwidth
	and low jitter to provide a high QoE to the user. In order to ach ieve such hard timing constraints, computationally intensive	and low jitter to provide a high QoE to the user. In order to ach ieve such hard timing constraints, computationally intensive
	tasks can be offloaded to Edge devices.	tasks can be offloaded to Edge devices.

	</t>	</t>
	<t>	<t>

		Another requirement for our use case and similar applications, such as 36
	Another requirement for our use case and similar applications such as 360	0-degree streaming (streaming of video that represents a view in every direction
	-degree streaming (streaming of video that represents a view in every direction	in 3D space), is that the display on
	in 3D space) is that the display on
	the XR device should synchronize the visual input with the way the user i s moving their head. This synchronization	the XR device should synchronize the visual input with the way the user i s moving their head. This synchronization

	is necessary to avoid motion sickness that results from a time-lag betwee	is necessary to avoid motion sickness that results from a time lag betwee
	n when the user moves their head and	n when the user moves their head and
	when the appropriate video scene is rendered. This time lag is often call	when the appropriate video scene is rendered. This time lag is often call
	ed "motion-to-photon" delay.	ed "motion-to-photon delay".
	Studies have shown <xref target="PER_SENSE" format="default"/>, <xref target="XR	Studies have shown that this delay
	" format="default"/>, <xref target="OCCL_3" format="default"/> that this delay	can be at most 20 ms and preferably between 7-15 ms in
	can be at most 20ms and preferably between 7-15ms in	order to avoid motion sickness <xref target="PER_SENSE" format="default"/> <xref
	order to avoid the motion sickness problem. Out of these 20ms, display technique	target="XR" format="default"/> <xref target="OCCL_3" format="default"/>. Out of
	s including the refresh	these 20 ms, display techniques including the refresh
	rate of write displays and pixel switching take 12-13ms <xref target="OCCL_3" fo	rate of write displays and pixel switching take 12-13 ms <xref target="OCCL_3" f
	rmat="default"/>, <xref target="CLOUD" format="default"/>. This leaves 7-8ms for	ormat="default"/> <xref target="CLOUD" format="default"/>. This leaves 7-8 ms fo
	the processing of	r the processing of
	motion sensor inputs, graphic rendering, and round-trip-time (RTT) between the X	motion sensor inputs, graphic rendering, and round-trip time (RTT) between the X
	R device and the Edge.	R device and the Edge.
	The use of predictive techniques to mask latencies has been considered as a miti gating strategy to reduce motion sickness <xref target="PREDICT" format="default "/>.	The use of predictive techniques to mask latencies has been considered as a miti gating strategy to reduce motion sickness <xref target="PREDICT" format="default "/>.
	In addition, Edge Devices that are proximate to the user might be used to offloa d these computationally intensive tasks.	In addition, Edge Devices that are proximate to the user might be used to offloa d these computationally intensive tasks.

	Towards this end, a 3GPP study indicates an Ultra Reliable Low Latency of 0.1ms
	to 1ms for	<!-- [rfced] Section 3: Is "indicates" the best word choice here? Would
		"recommends", "suggests", or something similar be better?

		Original:
		Towards this end, a 3GPP study indicates an Ultra
		Reliable Low Latency of 0.1ms to 1ms for communication between an
		Edge server and User Equipment (UE) [URLLC].
		-->

		Towards this end, a 3GPP study indicates an Ultra-Reliable Low Latency of 0.1 to
		1 ms for
	communication between an Edge server and User Equipment (UE) <xref target="URLL C" format="default"/>.	communication between an Edge server and User Equipment (UE) <xref target="URLL C" format="default"/>.

	</t>	</t>
	<t>	<t>

	Note that the Edge device providing the computation and storage i	Note that the Edge device providing the computation and storage i
	s itself limited in such resources compared to the Cloud. So,	s itself limited in such resources compared to the cloud.
	for example, a sudden surge in demand from a large group of touri	For example, a sudden surge in demand from a large group of touri
	sts can overwhelm that device. This will result in a degraded user	sts can overwhelm the device. This will result in a degraded user
	experience as their XR device experiences delays in receiving th e video frames. In order to deal	experience as their XR device experiences delays in receiving th e video frames. In order to deal

	with this problem, the client XR applications will need to use A daptive Bit Rate (ABR) algorithms that choose bit-rates policies	with this problem, the client XR applications will need to use A BR algorithms that choose bitrate policies
	tailored in a fine-grained manner	tailored in a fine-grained manner

	to the resource demands and playback the videos with appropriate QoE metrics as the user moves around with the group of tourists.	to the resource demands and play back the videos with appropriat e QoE metrics as the user moves around with the group of tourists.
	</t>	</t>


		<!-- [rfced] Section 3: Please review the placement of the sentence starting
		with "Such operational parameters" in the last paragraph of this
		section. Would it be helpful to incorporate this sentence into the first
		sentence of the paragraph?

		Original:
		However, heavy-tailed nature of several operational parameters makes
		prediction-based adaptation by ABR algorithms sub-optimal [ABR_2].
		...
		Such operational parameters include but are not limited
		to buffer occupancy, throughput, client-server latency, and variable
		transmission times.

		Perhaps:
		However, the heavy-tailed nature of several operational parameters
		(e.g., buffer occupancy, throughput, client-server latency, and variable
		transmission times) makes prediction-based adaptation by ABR algorithms sub-o
		ptimal
		[ABR_2].
		-->

		<!-- [rfced] Section 3: Will readers understand what "This" refers to in the
		second sentence below? The first sentence is included for context.

		Original:
		Other subtle issues with these distributions include
		the "expectation paradox" [HEAVY_TAIL_1] where the longer the wait
		for an event, the longer a further need to wait and the issue of
		mismatch between the size and count of events [HEAVY_TAIL_1]. This
		makes designing an algorithm for adaptation error-prone and
		challenging.

		Perhaps:
		Other subtle issues with these
		distributions include the "expectation paradox" [HEAVY_TAIL_1] (the
		longer the wait for an event, the longer a further need to wait) and
		the mismatch between the size and count of events [HEAVY_TAIL_1].
		These issues make designing an algorithm for adaptation error-prone and
		challenging.
		-->

	<t>	<t>

	However, heavy-tailed nature of several operational parameters m	However, the heavy-tailed nature of several operational paramete
	akes prediction-based adaptation by ABR algorithms sub-optimal <xref target="AB	rs makes prediction-based adaptation by ABR algorithms sub-optimal <xref target
	R_2" format="default"/>.	="ABR_2" format="default"/>.
	This is because with such distributions, law of large numbers (ho	This is because with such distributions, the law of large numbers
	w long does it take for sample mean to stabilize) works too slowly <xref target=	(how long it takes for the sample mean to stabilize) works too slowly <xref tar
	"HEAVY_TAIL_2" format="default"/>, the mean of sample does not equal the mean of	get="HEAVY_TAIL_2" format="default"/> and the mean of sample does not equal the
	distribution <xref target="HEAVY_TAIL_2" format="default"/>,	mean of distribution <xref target="HEAVY_TAIL_2" format="default"/>;
	and as a result standard deviation and variance are unsuitable as	as a result, standard deviation and variance are unsuitable as me
	metrics for such operational parameters <xref target="HEAVY_TAIL_1" format="def	trics for such operational parameters <xref target="HEAVY_TAIL_1" format="defaul
	ault"/>. Other subtle issues with	t"/>. Other subtle issues with
	these distributions include the "expectation paradox" <xref targe	these distributions include the "expectation paradox" <xref targe
	t="HEAVY_TAIL_1" format="default"/> where the longer the wait for an event, the	t="HEAVY_TAIL_1" format="default"/> (the longer the wait for an event, the longe
	longer a further need to wait and the	r a further need to wait) and the
	issue of mismatch between the size and count of events <xref targ	mismatch between the size and count of events <xref target="HEAVY
	et="HEAVY_TAIL_1" format="default"/>. This makes designing an algorithm for	_TAIL_1" format="default"/>. This makes designing an algorithm for
	adaptation error-prone and challenging.	adaptation error-prone and challenging.
	Such operational parameters include but are not limited to buffer occupancy, throughput, client-server latency, and variable transmission	Such operational parameters include but are not limited to buffer occupancy, throughput, client-server latency, and variable transmission

	times. In addition, edge devices and communication links may fai l and logical communication relationships between various software components	times. In addition, edge devices and communication links may fai l, and logical communication relationships between various software components
	change frequently as the user moves around with their XR device < xref target="UBICOMP" format="default"/>.	change frequently as the user moves around with their XR device < xref target="UBICOMP" format="default"/>.

	</t>	</t>

	</section>	</section>
	<section anchor="ArTraffic" numbered="true" toc="default">	<section anchor="ArTraffic" numbered="true" toc="default">
	<name>XR Network Traffic</name>	<name>XR Network Traffic</name>

	<section anchor="traffic_workload" numbered="true" toc="default">	<section anchor="traffic_workload" numbered="true" toc="default">
	<name>Traffic Workload</name>	<name>Traffic Workload</name>


		<!-- [rfced] Section 4.1: Would it be helpful to point readers to a specific
		section here?

		Original:
		As discussed earlier, the parameters that capture the characteristics
		of XR application behavior are heavy-tailed.

		Perhaps:
		As discussed in Section 1, the parameters that capture the characteristics
		of XR application behavior are heavy-tailed.
		-->

		<!-- [rfced] Section 4.1: We are having trouble understanding "distribution of
		arrival times between XR application invocation". Perhaps "invocation"
		should be "invocations" (plural), or perhaps a word missing ("between XR
		application invocation and X")? Please review.

		Original:
		Examples of such
		parameters include the distribution of arrival times between XR
		application invocation, the amount of data transferred, and the
		inter-arrival times of packets within a session.

		Perhaps:
		Examples of such
		parameters include the distribution of arrival times between XR
		application invocations, the amount of data transferred, and the
		inter-arrival times of packets within a session.
		-->

	<t>	<t>
	As discussed earlier, the parameters that capture the characteris tics of XR application behavior are heavy-tailed.	As discussed earlier, the parameters that capture the characteris tics of XR application behavior are heavy-tailed.
	Examples of such parameters include the distribution of arrival t imes between XR application invocation, the amount	Examples of such parameters include the distribution of arrival t imes between XR application invocation, the amount
	of data transferred, and the inter-arrival times of packets withi n a session. As a result, any traffic model based on	of data transferred, and the inter-arrival times of packets withi n a session. As a result, any traffic model based on

	such parameters are themselves heavy-tailed. Using	such parameters is also heavy-tailed. Using
	these models to predict performance under alternative resource al locations by the network operator is challenging. For example, both uplink and d ownlink traffic to a user device has parameters such as volume of XR data, burst time, and idle time that are heavy-tailed.	these models to predict performance under alternative resource al locations by the network operator is challenging. For example, both uplink and d ownlink traffic to a user device has parameters such as volume of XR data, burst time, and idle time that are heavy-tailed.
	</t>	</t>
	<t>	<t>

	<xref target="TABLE_1" format="default"/> below shows various streaming	<!-- [rfced] Section 4.1: Please note that RFC 9450 is not a DETNET WG
	video applications and their associated throughput requirements <xref target="M	document; it is a RAW WG document (see
	ETRICS_1" format="default"/>. Since our use case envisages a 6 degrees of freedo	https://datatracker.ietf.org/doc/rfc9450/). In addition, [RFC8939],
	m (6DoF) video or point cloud, it can be seen from the table that it will requir	[RFC9023], and [RFC9450] have been published, so they are no longer
	e 200 to 1000Mbps of bandwidth.	"being developed". How may we updated this sentence?
	As seen from the table, the XR application such as our use case transmit a large
	r amount of data per unit time as compared to traditional video applications. As	Original:
	a result, issues arising out of heavy-tailed parameters such as long-range depe	Providing Edge server support for the techniques being developed at
	ndent traffic <xref target="METRICS_2" format="default"/>, self-similar traffic	the DETNET Working Group at the IETF [RFC8939], [RFC9023], [RFC9450]
	<xref target="METRICS_3" format="default"/>, would be experienced at time scales	could guarantee performance of XR applications.
	of milliseconds and microseconds rather than hours or seconds. Additionally, bu
	rstiness at the time scale of tens of milliseconds due to multi-fractal spectrum	Perhaps:
	of traffic will be experienced <xref target="METRICS_4" format="default"/>.	Providing support for Edge servers in techniques
	Long-range dependent traffic can have long bursts and various traffic parameters	such as those described in [RFC8939], [RFC9023], and [RFC9450]
	from widely separated time can show correlation <xref target="HEAVY_TAIL_1" for	could guarantee performance of XR applications.
	mat="default"/>. Self-similar traffic contains bursts at a wide range of time sc	-->
	ales <xref target="HEAVY_TAIL_1" format="default"/>. Multi-fractal spectrum burs
	ts for traffic summarizes the statistical distribution of local scaling exponent	<!-- [rfced] Section 4.1: Is [RFC2210] is the correct citation here, or should
	s found in a traffic trace <xref target="HEAVY_TAIL_1" format="default"/>.	it be [RFC2112]? We ask because we see only one instance of "quality of
	The operational consequences of XR traffic having characteristics such as long-r	service" in the text of RFC 2210, and the title of RFC 2112 is
	ange dependency, and self-similarity is that the edge servers to which multiple	"Specification of Guaranteed Quality of Service".
	XR devices are connected wirelessly could face long bursts of traffic <xref targ
	et="METRICS_2" format="default"/>, <xref target="METRICS_3" format="default"/>.	Original:
	In addition, multi-fractal spectrum burstiness at the scale of milli-seconds cou	Another option for the network operators could be to deploy equipment that
	ld induce jitter contributing to motion sickness <xref target="METRICS_4" format	supports differentiated services [RFC2475] or per-connection quality-
	="default"/>. This is because bursty traffic combined with variable queueing del	of-service guarantees [RFC2210].
	ays leads to large delay jitter <xref target="METRICS_4" format="default"/>.	-->
	The operators of edge servers will need to run a 'managed edge cloud service' <x
	ref target="METRICS_5" format="default"/> to deal with the above problems. Funct	<xref target="TABLE_1" format="default"/> below shows various streaming
	ionalities that such a managed edge cloud service could operationally provide in	video applications and their associated throughput requirements <xref target="M
	clude dynamic placement of XR servers, mobility support and energy management <x	ETRICS_1" format="default"/>. Since our use case envisages a 6 degrees of freedo
	ref target="METRICS_6" format="default"/>. Providing Edge server support for the	m (6DoF) video or point cloud, the table indicates that it will require 200 to 1
	techniques being developed at the DETNET Working Group at the IETF <xref target	000 Mbps of bandwidth.
	="RFC8939" format="default"/>, <xref target="RFC9023" format="default"/>, <xref	Also, the table shows that XR applications, such as the one in our use case, tra
	target="RFC9450" format="default"/> could guarantee performance of XR applicatio	nsmit a larger amount of data per unit time as compared to traditional video app
	ns. For example, these techniques could be used for the link between the XR devi	lications. As a result, issues arising from heavy-tailed parameters, such as lon
	ce and the edge as well as within the managed edge cloud service. Another option	g-range dependent traffic <xref target="METRICS_2" format="default"/> and self-s
	for the network operators could be to deploy equipment that supports differenti	imilar traffic <xref target="METRICS_3" format="default"/>, would be experienced
	ated services <xref target="RFC2475" format="default"/> or per-connection qualit	at timescales of milliseconds and microseconds rather than hours or seconds. Ad
	y-of-service guarantees <xref target="RFC2210" format="default"/>.	ditionally, burstiness at the timescale of tens of milliseconds due to the multi
		-fractal spectrum of traffic will be experienced <xref target="METRICS_4" format
		="default"/>.
		Long-range dependent traffic can have long bursts, and various traffic parameter
		s from widely separated times can show correlation <xref target="HEAVY_TAIL_1" f
		ormat="default"/>. Self-similar traffic contains bursts at a wide range of times
		cales <xref target="HEAVY_TAIL_1" format="default"/>. Multi-fractal spectrum bur
		sts for traffic summarize the statistical distribution of local scaling exponent
		s found in a traffic trace <xref target="HEAVY_TAIL_1" format="default"/>.
		The operational consequence of XR traffic having characteristics such as long-ra
		nge dependency and self-similarity is that the edge servers to which multiple XR
		devices are connected wirelessly could face long bursts of traffic <xref target
		="METRICS_2" format="default"/> <xref target="METRICS_3" format="default"/>. In
		addition, multi-fractal spectrum burstiness at the scale of milliseconds could i
		nduce jitter contributing to motion sickness <xref target="METRICS_4" format="de
		fault"/>. This is because bursty traffic combined with variable queueing delays
		leads to large delay jitter <xref target="METRICS_4" format="default"/>.
		The operators of edge servers will need to run a "managed edge cloud service" <x
		ref target="METRICS_5" format="default"/> to deal with the above problems. Funct
		ionalities that such a managed edge cloud service could operationally provide in
		clude dynamic placement of XR servers, mobility support, and energy management <
		xref target="METRICS_6" format="default"/>. Providing Edge server support for th
		e techniques being developed at the DETNET Working Group in the IETF <xref targe
		t="RFC8939" format="default"/> <xref target="RFC9023" format="default"/> <xref t
		arget="RFC9450" format="default"/> could guarantee performance of XR application
		s. For example, these techniques could be used for the link between the XR devic
		e and the edge as well as within the managed edge cloud service. Another option
		for network operators would be to deploy equipment that supports differentiated
		services <xref target="RFC2475" format="default"/> or per-connection Quality-of-
		Service (QoS) guarantees <xref target="RFC2210" format="default"/>.

	</t>	</t>

	<table anchor="TABLE_1">	<table anchor="TABLE_1">

	<name>Throughput requirement for streaming video applications</name>	<name>Throughput Requirements for Streaming Video Applications</name>
	<thead>	<thead>
	<tr>	<tr>

	<th> Application</th> <th> Throughput Required</th>	<th>Application</th>
		<th>Throughput Required</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>
	<tr>	<tr>

	<td> <t>Real-world objects annotated with text and images for w	<td><t>Real-world objects annotated with text and images for wo
	orkflow assistance (e.g. repair)</t></td> <td> <t>1 Mbps</t></td>	rkflow assistance (e.g., repair)</t></td>
		<td> <t>1 Mbps</t></td>
	</tr>	</tr>


	<tr>	<tr>

	<td> <t>Video Conferencing</t></td> <td> <t>2 Mbps</t></td>	<td><t>Video conferencing</t></td>
		<td> <t>2 Mbps</t></td>
	</tr>	</tr>
	<tr>	<tr>

	<td> <t>3D Model and Data Visualization</t></td> <td> <t>2 to 2	<td> <t>3D model and data visualization</t></td>
	0 Mbps</t></td>	<td> <t>2 to 20 Mbps</t></td>
	</tr>	</tr>


	<tr>	<tr>

	<td> <t>Two-way 3D Telepresence</t></td> <td> <t>5 to 25 Mbps</	<td> <t>Two-way 3D telepresence</t></td>
	t></td>	<td> <t>5 to 25 Mbps</t></td>
	</tr>	</tr>


	<tr>	<tr>

	<td> <t>Current-Gen 360-degree video (4K)</t></td> <td> <t>10 t	<td> <t>Current-Gen 360-degree video (4K)</t></td>
	o 50 Mbps</t></td>	<td> <t>10 to 50 Mbps</t></td>
	</tr>	</tr>


	<tr>	<tr>

	<td> <t>Next-Gen 360-degree video (8K, 90+ Frames-per-second, H	<td> <t>Next-Gen 360-degree video (8K, 90+ frames per second, h
	igh Dynamic Range, Stereoscopic)</t></td> <td> <t>50 to 200 Mbps</t></td>	igh dynamic range, stereoscopic)</t></td>
		<td> <t>50 to 200 Mbps</t></td>
	</tr>	</tr>


	<tr>	<tr>

	<td> <t>6 Degree of Freedom Video or Point Cloud</t></td> <td>	<td> <t>6DoF video or point cloud</t></td>
	<t>200 to 1000 Mbps</t></td>	<td> <t>200 to 1000 Mbps</t></td>
	</tr>	</tr>


	</tbody>	</tbody>
	</table>	</table>


	<t>	<!-- [rfced] Section 4.1: May we move the following sentence to appear
	Thus, the provisioning of edge servers in terms of the number of servers, the t	before Table 1 rather than after it?
	opology, where to place them, the assignment of link capacity, CPUs and GPUs sho
	uld keep the above factors in mind.


		Original:
		Thus, the provisioning of edge servers in terms of the number of
		servers, the topology, where to place them, the assignment of link
		capacity, CPUs and GPUs should keep the above factors in mind.
		-->
		<t>
		Thus, the provisioning of edge servers (in terms of the number of
		servers, the topology, the placement of servers, the assignment of link
		capacity, CPUs, and Graphics Processing Units (GPUs)) should be performed
		with the above factors in mind.
	</t>	</t>

	</section>	</section>

	<section anchor="traffic_performance" numbered="true" toc="default">	<section anchor="traffic_performance" numbered="true" toc="default">
	<name>Traffic Performance Metrics</name>	<name>Traffic Performance Metrics</name>

	<t>	<t>
	The performance requirements for XR traffic have characteristics that n eed to be considered when operationalizing a network.	The performance requirements for XR traffic have characteristics that n eed to be considered when operationalizing a network.

	These characteristics are now discussed.</t>	These characteristics are discussed in this section.</t>
	<t>The bandwidth requirements of XR applications are substantially higher than t hose of video-based applications.</t>	<t>The bandwidth requirements of XR applications are substantially higher than t hose of video-based applications.</t>


	<t>The latency requirements of XR applications have been studied recently <xref target="XR_TRAFFIC" format="default"/>. The following characteristics we re identified.:	<t>The latency requirements of XR applications have been studied recently <xref target="XR_TRAFFIC" format="default"/>. The following characteristics we re identified:
	</t>	</t>
	<ul spacing="normal">	<ul spacing="normal">
	<li>The uploading of data from an XR device to a remote server for proce ssing dominates the end-to-end latency.	<li>The uploading of data from an XR device to a remote server for proce ssing dominates the end-to-end latency.
	</li>	</li>
	<li> A lack of visual features in the grid environment can cause increas ed latencies as the XR device	<li> A lack of visual features in the grid environment can cause increas ed latencies as the XR device
	uploads additional visual data for processing to the r emote server.</li>	uploads additional visual data for processing to the r emote server.</li>
	<li>XR applications tend to have large bursts that are separated by sign ificant time gaps.</li>	<li>XR applications tend to have large bursts that are separated by sign ificant time gaps.</li>
	</ul>	</ul>


	<t> Additionally, XR applications interact with each other on a time sca	<t> Additionally, XR applications interact with each other on a timescal
	le of a round-trip-time propagation, and this must be considered when operationa	e of an RTT propagation, and this must be considered when operationalizing a net
	lizing a network.</t>	work.</t>

		<!-- [rfced] Section 4.2: What is the relationship between Table 2 and
		[METRICS_6]? We do not see the table in [METRIC_6].

		Original:
		The following Table 2 [METRICS_6] shows a taxonomy of applications
		with their associated required response times and bandwidths.
		-->

	<t>	<t>

	The following <xref target="TABLE_2" format="default"/> <xref target	<xref target="TABLE_2" format="default"/> <xref target="METRICS_6" f
	="METRICS_6" format="default"/> shows a taxonomy of applications with their asso	ormat="default"/> shows a taxonomy of applications with their associated require
	ciated required response times and bandwidths. Response times can	d response times and bandwidths. Response times can
	be defined as the time interval between the end of a request submission and the	be defined as the time interval between the end of a request submission and the
	end of the corresponding response from a system. If the XR device offloads a tas	end of the corresponding response from a system. If the XR device offloads a tas
	k to an edge server, the response time of the server is the round-trip time from	k to an edge server, the response time of the server is the RTT from when a data
	when a data packet is sent from the XR device until a response is received. Not	packet is sent from the XR device until a response is received. Note that the r
	e that the required response time provides an upper bound on the sum of the time	equired response time provides an upper bound for the sum of the time taken by c
	taken by computational tasks such as processing of scenes, generation of images	omputational tasks (such as processing of scenes and generation of images) and t
	and the round-trip time. This response time depends only on the Quality of Serv	he RTT. This response time depends only on the QoS required by an application. T
	ice (QOS) required by an application. The response time is therefore independent	he response time is therefore independent of the underlying technology of the ne
	of the underlying technology of the network and the time taken by the computati	twork and the time taken by the computational tasks.
	onal tasks.

	</t>	</t>

	<t>	<!-- [rfced] Section 4.2: FYI - We updated "section 5.1" to "Section 4.1"
	Our use case requires a response time of 20ms at most and preferably between 7-1	here. Also, because Table 1 appears in Section 4.1, we updated to only
	5ms as discussed earlier. This requirement for response time is similar to the f	mention Section 4.1.
	irst two entries of <xref target="TABLE_2" format="default"/> below. Additionall
	y, the required bandwidth for our use case as discussed in section 5.1, <xref t	Original:
	arget="TABLE_1" format="default"/>, is 200Mbps-1000Mbps.	Additionally, the required bandwidth for our use case as
	Since our use case envisages multiple users running the XR applications on their	discussed in section 5.1, Table 1, is 200Mbps-1000Mbps.
	devices, and connected to an edge server that is closest to them, these latency
	and bandwidth connections will grow linearly with the number of users. The oper
	ators should match the network provisioning to the maximum number of tourists th
	at can be supported by a link to an edge server.


		Current:
		Additionally, the required bandwidth for our use case
		is 200 to 1000 Mbps (see Section 4.1).
		-->
		<t>
		Our use case requires a response time of 20 ms at most and
		preferably between 7-15 ms, as discussed earlier. This requirement
		for response time is similar to the first two entries in <xref
		target="TABLE_2" format="default"/>. Additionally, the required
		bandwidth for our use case is 200 to 1000 Mbps (see <xref
		target="traffic_workload"/>). Since our use case envisages multiple
		users running the XR application on their devices and connecting to
		the edge server that is closest to them, these latency and bandwidth
		connections will grow linearly with the number of users.
		The operators should match the network provisioning to the maximum
		number of tourists that can be supported by a link to an edge
		server.
	</t>	</t>


	<table anchor="TABLE_2">	<table anchor="TABLE_2">
	<name>Traffic Performance Metrics of Selected XR Applications</name>	<name>Traffic Performance Metrics of Selected XR Applications</name>
	<thead>	<thead>
	<tr>	<tr>

	<th> Application</th> <th> Required Response Time</th> <th> Ex	<th> Application</th>
	pected Data Capacity</th> <th> Possible Implementations/ Examples</th>	<th> Required Response Time</th>
		<th> Expected Data Capacity</th>
		<th> Possible Implementations/ Examples</th>
	</tr>	</tr>
	</thead>	</thead>
	<tbody>	<tbody>


	<tr>	<tr>

	<td> <t>Mobile XR based remote assistance with uncompressed 4K	<td><t>Mobile XR-based remote assistance with uncompressed
	(1920x1080 pixels) 120 fps HDR 10-bit real-time video stream</t></td>	4K (1920x1080 pixels) 120 fps HDR 10-bit real-time video
	<td> <t>Less than 10 milliseconds</t></td>	stream</t></td>
	<td> <t>Greater than 7.5 Gbps</t></td>	<td><t>Less than 10 milliseconds</t></td>
	<td> <t>Assisting maintenance technicians, Industry 4.0 remote	<td><t>Greater than 7.5 Gbps</t></td>
	maintenance, remote assistance in robotics industry</t></td>	<td><t>Assisting maintenance technicians, Industry 4.0
		remote maintenance, remote assistance in robotics
		industry</t></td>
	</tr>	</tr>
	<tr>	<tr>

	<td> <t>Indoor and localized outdoor navigation </t></td>	<td><t>Indoor and localized outdoor navigation </t></td>
	<td> <t>Less than 20 milliseconds</t></td>	<td><t>Less than 20 milliseconds</t></td>
	<td> <t>50 to 200 Mbps</t></td>	<td><t>50 to 200 Mbps</t></td>
	<td> <t>Theme Parks, Shopping Malls, Archaeological Sites, Muse	<td><t>Guidance in theme parks, shopping malls, archaeological
	um guidance</t></td>	sites, and
		museums</t></td>
	</tr>	</tr>


	<tr>	<tr>

	<td> <t>Cloud-based Mobile XR applications</t></td>	<td><t>Cloud-based mobile XR applications</t></td>
	<td> <t>Less than 50 milliseconds</t></td>	<td><t>Less than 50 milliseconds</t></td>
	<td> <t>50 to 100 Mbps</t></td>	<td><t>50 to 100 Mbps</t></td>
	<td> <t>Google Live View, XR-enhanced Google Translate </t></td	<td><t>Google Live View, XR-enhanced Google Translate </t></td>
	>
	</tr>	</tr>


	</tbody>	</tbody>

	</table>	</table>

	</section>	</section>

	</section>	</section>

	<section anchor="conclusion" numbered="true" toc="default">	<section anchor="conclusion" numbered="true" toc="default">
	<name>Conclusion</name>	<name>Conclusion</name>
	<t>	<t>

	In order to operationalize a use case such as the one presented in th	In order to operationalize a use case such as the one presented in th
	is document, a network operator could dimension their network to provide a short	is document, a network operator could dimension their network to provide a short
	and high-capacity network path from the edge compute	and high-capacity network path from the edge computing
	resources or storage to the mobile devices running the XR application	resources or storage to the mobile devices running the XR application
	. This is required to ensure a response time of 20ms at most and preferably betw	. This is required to ensure a response time of 20 ms at most and preferably bet
	een 7-15ms. Additionally, a bandwidth of 200	ween 7-15 ms. Additionally, a bandwidth of 200
	to 1000Mbps is required by such applications. To deal with the charac	to 1000 Mbps is required by such applications. To deal with the chara
	teristics of XR traffic as discussed in this document, network operators could d	cteristics of XR traffic as discussed in this document, network operators could
	eploy a managed edge cloud service that operationally	deploy a managed edge cloud service that operationally
	provides dynamic placement of XR servers, mobility support and energy	provides dynamic placement of XR servers, mobility support, and energ
	management. Although the use case is technically feasible, economic viability i	y management. Although the use case is technically feasible, economic viability
	s an important factor that must be considered.	is an important factor that must be considered.

	</t>	</t>
	</section>	</section>

	<section anchor="iana" numbered="true" toc="default">	<section anchor="iana" numbered="true" toc="default">
	<name>IANA Considerations</name>	<name>IANA Considerations</name>
	<t>	<t>
	This document has no IANA actions.	This document has no IANA actions.

	</t>	</t>
	</section>	</section>

	<section anchor="Sec" numbered="true" toc="default">	<section anchor="Sec" numbered="true" toc="default">
	<name>Security Considerations</name>	<name>Security Considerations</name>

	<t>
	The security issues for the presented use case are similar to other s
	treaming applications <xref target="DIST" format="default"/>, <xref target="NIST
	1" format="default"/>, <xref target="CWE" format="default"/>, <xref target="NIST
	2" format="default"/>. This document itself introduces no new security issues.


	</t>	<!-- [rfced] Section 7: We do not see explicit mention of "streaming
		applications" in [DIST], [NIST1], [CWE], and [NIST2]. Please confirm that
		these citations and the phrasing of the text are correct.


	</section>	Original:
		The security issues for the presented use case are similar to other
		streaming applications [DIST], [NIST1], [CWE], [NIST2].


	<section anchor="ack" numbered="true" toc="default">	Perhaps:
	<name>Acknowledgements</name>	The security issues for the presented use case are similar to those
		described in [DIST], [NIST1], [CWE], and [NIST2].

		Or:
		The security issues for the presented use case are similar to those for other
		streaming applications. See [DIST], [NIST1], [CWE], and [NIST2].
		-->
	<t>	<t>

	Many Thanks to Spencer Dawkins, Rohit Abhishek, Jake Holland, Kir an Makhijani, Ali Begen, Cullen Jennings, Stephan Wenger, Eric Vyncke, Wesley Ed dy, Paul Kyzivat, Jim Guichard, Roman Danyliw, Warren Kumari, and Zaheduzzaman S arker for providing very helpful feedback, suggestions and comments.	The security issues for the presented use case are similar to other s treaming applications <xref target="DIST" format="default"/> <xref target="NIST1 " format="default"/> <xref target="CWE" format="default"/> <xref target="NIST2" format="default"/>. This document does not introduce any new security issues.

	</t>	</t>


	</section>	</section>

	</middle>	</middle>
	<back>	<back>
	<references>	<references>
	<name>Informative References</name>	<name>Informative References</name>


	<reference anchor="DEV_HEAT_1" target="">	<!-- [rfced] Section 8 (Informative References)

		a) We added DOIs and URLs to some reference entries. Please review for
		correctness.

		b) FYI - We updated the title of this reference entry as follows. Let us know
		any concerns.

		Original:
		[AUGMENTED]
		Schmalstieg, D. S. and T.H. Hollerer, "Augmented
		Reality", Addison Wesley, 2016.

		Updated:
		[AUGMENTED]
		Schmalstieg, D. and T. Höllerer, "Augmented Reality:
		Principles and Practice", Addison-Wesley Professional,
		2016, <https://www.oreilly.com/library/view/augmented-
		reality-principles/9780133153217/>.

		c) FYI - We updated the date in this reference entry from 2020 to 2022 per
		https://arxiv.org/pdf/2001.10488. Let us know any concerns.

		Original:
		[HEAVY_TAIL_2]
		Taleb, N., "The Statistical Consequences of Fat Tails",
		STEM Academic Press, 2020.

		Updated:
		[HEAVY_TAIL_2]
		Taleb, N., "Statistical Consequences of Fat Tails: Real
		World Preasymptotics, Epistemology, and Applications",
		Revised Edition, STEM Academic Press, 2022,
		<https://arxiv.org/pdf/2001.10488>.

		d) FYI - We updated the date from 1982 to 2007 in this reference entry to
		match the most current version of the book. Let us know any concerns.

		See: https://www.wiley.com/en-us/A+Primer+in+Data+Reduction%3A+An+Introductory+S
		tatistics+Textbook-p-9780471101352

		Original:
		[HEAVY_TAIL_3]
		Ehrenberg, A., "A Primer in Data Reduction.", John Wiley,
		London, 1982.

		Updated:
		[HEAVY_TAIL_3]
		Ehrenberg, A., "A Primer in Data Reduction: An
		Introductory Statistics Textbook", John Wiley and Sons,
		2007, <https://www.wiley.com/en-us/A+Primer+in+Data+Reduct
		ion%3A+An+Introductory+Statistics+Textbook-
		p-9780471101352>.

		e) FYI - We updated the title of this reference entry as follows (i.e., added
		"gDLS:"). Let us know any concerns.

		Original:
		[SLAM_2] Sweeny, C., Fragoso, V., Hollerer, T., and M. Turk, "A
		scalable solution to the generalized pose and scale
		problem", In European Conference on Computer Vision, pp.
		16-31, 2014.

		Perhaps:
		[SLAM_2] Sweeny, C., Fragoso, V., Höllerer, T., and M. Turk, "gDLS:
		A Scalable Solution to the Generalized Pose and Scale
		Problem", Computer Vision - ECCV 2014, pp. 16-31,
		DOI 10.1007/978-3-319-10593-2_2, 2014,
		<https://link.springer.com/
		chapter/10.1007/978-3-319-10593-2_2>.
		-->

		<reference anchor="DEV_HEAT_1" target="https://dl.acm.org/doi/10.1145/2637
		166.2637230">
	<front>	<front>

	<title> Draining our Glass: An Energy and Heat characterization of Goo gle Glass</title>	<title> Draining our glass: an energy and heat characterization of Goo gle Glass</title>
	<author initials="R" surname="LiKamWa" fullname="Robert LiKamWa">	<author initials="R" surname="LiKamWa" fullname="Robert LiKamWa">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="Z" surname="Wang" fullname="Zhen Wang">	<author initials="Z" surname="Wang" fullname="Zhen Wang">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="A" surname="Carroll" fullname="Aaron Carroll">	<author initials="A" surname="Carroll" fullname="Aaron Carroll">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="F" surname="Lin" fullname="Felix Xiaozhu Lin">	<author initials="F" surname="Lin" fullname="Felix Xiaozhu Lin">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="L" surname="Zhong" fullname="Lin Zhong">	<author initials="L" surname="Zhong" fullname="Lin Zhong">
	<organization/>	<organization/>
	</author>	</author>

	<date year="2013"/>	<date year="2014"/>
	</front>	</front>

	<seriesInfo name="In Proceedings of" value="5th Asia-Pacific Workshop on	<refcontent>APSys '14: 5th Asia-Pacific Workshop on Systems, pp. 1-7</re
	Systems pp. 1-7"/>	fcontent>
		<seriesInfo name="DOI" value="10.1145/2637166.2637230"/>
	</reference>	</reference>

	<reference anchor="EDGE_1" target="">
		<reference anchor="EDGE_1" target="https://ieeexplore.ieee.org/document/78
		07196">
	<front>	<front>
	<title> The Emergence of Edge Computing</title>	<title> The Emergence of Edge Computing</title>
	<author initials="M" surname="Satyanarayanan" fullname="Mahadev Satyan arayanan">	<author initials="M" surname="Satyanarayanan" fullname="Mahadev Satyan arayanan">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2017"/>	<date year="2017"/>
	</front>	</front>

	<seriesInfo name="In " value="Computer 50(1) pp. 30-39"/>	<refcontent>Computer, vol. 50, no. 1, pp. 30-39</refcontent>
		<seriesInfo name="DOI" value="10.1109/MC.2017.9"/>
	</reference>	</reference>

	<reference anchor="EDGE_2" target="">
		<reference anchor="EDGE_2" target="https://ieeexplore.ieee.org/document/88
		12200">
	<front>	<front>
	<title> The Seminal Role of Edge-Native Applications</title>	<title> The Seminal Role of Edge-Native Applications</title>
	<author initials="M" surname="Satyanarayanan" fullname="Mahadev Satyan arayanan">	<author initials="M" surname="Satyanarayanan" fullname="Mahadev Satyan arayanan">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="G" surname="Klas" fullname="Guenter Klas">	<author initials="G" surname="Klas" fullname="Guenter Klas">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="M" surname="Silva" fullname="Marco Silva">	<author initials="M" surname="Silva" fullname="Marco Silva">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="S" surname="Mangiante" fullname="Simone Mangiante">	<author initials="S" surname="Mangiante" fullname="Simone Mangiante">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2019"/>	<date year="2019"/>
	</front>	</front>

	<seriesInfo name="In " value="IEEE International Conference on Edge Comp	<refcontent>2019 IEEE International Conference on Edge Computing (EDGE),
	uting (EDGE) pp. 33-40"/>	pp. 33-40</refcontent>
		<seriesInfo name="DOI" value="10.1109/EDGE.2019.00022"/>
	</reference>	</reference>

	<reference anchor="ABR_1" target="">
		<reference anchor="ABR_1" target="https://dl.acm.org/doi/10.1145/3098822.3
		098843">
	<front>	<front>
	<title> Neural Adaptive Video Streaming with Pensieve</title>	<title> Neural Adaptive Video Streaming with Pensieve</title>
	<author initials="H" surname="Mao" fullname="Hongzi Mao">	<author initials="H" surname="Mao" fullname="Hongzi Mao">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="R" surname="Netravali" fullname="Ravi Netravali">	<author initials="R" surname="Netravali" fullname="Ravi Netravali">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="M" surname="Alizadeh" fullname="Mohammad Alizadeh">	<author initials="M" surname="Alizadeh" fullname="Mohammad Alizadeh">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2017"/>	<date year="2017"/>
	</front>	</front>

	<seriesInfo name="In " value="Proceedings of the Conference of the ACM S	<refcontent>SIGCOMM '17: Proceedings of the Conference of the ACM Specia
	pecial Interest Group on Data Communication, pp. 197-210"/>	l Interest Group on Data Communication, pp. 197-210</refcontent>
		<seriesInfo name="DOI" value="10.1145/3098822.3098843"/>
	</reference>	</reference>

	<reference anchor="ABR_2" target="">
		<reference anchor="ABR_2" target="https://www.usenix.org/conference/nsdi20
		/presentation/yan">
	<front>	<front>
	<title> Learning in situ: a randomized experiment in video streaming < /title>	<title> Learning in situ: a randomized experiment in video streaming < /title>
	<author initials="F" surname="Yan" fullname="Francis Y. Yan">	<author initials="F" surname="Yan" fullname="Francis Y. Yan">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="H" surname="Ayers" fullname="Hudson Ayers">	<author initials="H" surname="Ayers" fullname="Hudson Ayers">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="C" surname="Zhu" fullname="Chenzhi Zhu">	<author initials="C" surname="Zhu" fullname="Chenzhi Zhu">
	<organization/>	<organization/>

	skipping to change at line 506 ¶	skipping to change at line 1004 ¶
	</author>	</author>
	<author initials="K" surname="Zhang" fullname="Keyi Zhang">	<author initials="K" surname="Zhang" fullname="Keyi Zhang">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="P" surname="Levis" fullname="Philip Levis">	<author initials="P" surname="Levis" fullname="Philip Levis">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="K" surname="Winstein" fullname="Keith Winstein">	<author initials="K" surname="Winstein" fullname="Keith Winstein">
	<organization/>	<organization/>
	</author>	</author>

	<date year="2020"/>	<date month="February" year="2020"/>
	</front>	</front>

	<seriesInfo name="In " value=" 17th USENIX Symposium on Networked Syste ms Design and Implementation (NSDI 20), pp. 495-511"/>	<refcontent>17th USENIX Symposium on Networked Systems Design and Implem entation (NSDI '20), pp. 495-511</refcontent>
	</reference>	</reference>

	<reference anchor="HEAVY_TAIL_1" target="">
		<reference anchor="HEAVY_TAIL_1" target="https://www.wiley.com/en-us/Inter
		net+Measurement%3A+Infrastructure%2C+Traffic+and+Applications-p-9780470014615">
	<front>	<front>

	<title> Internet measurement: infrastructure, traffic and applications </title>	<title>Internet Measurement: Infrastructure, Traffic and Applications< /title>
	<author initials="M" surname="Crovella" fullname="Mark Crovella">	<author initials="M" surname="Crovella" fullname="Mark Crovella">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="B" surname="Krishnamurthy" fullname="Balachander Kri shnamurthy">	<author initials="B" surname="Krishnamurthy" fullname="Balachander Kri shnamurthy">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2006"/>	<date year="2006"/>
	</front>	</front>

	<seriesInfo name="John " value="Wiley and Sons Inc."/>	<refcontent>John Wiley and Sons</refcontent>
	</reference>	</reference>

	<reference anchor="HEAVY_TAIL_2" target="">
		<reference anchor="HEAVY_TAIL_2" target="https://arxiv.org/pdf/2001.10488"
		>
	<front>	<front>

	<title> The Statistical Consequences of Fat Tails</title>	<title>Statistical Consequences of Fat Tails: Real World Preasymptotic s, Epistemology, and Applications</title>
	<author initials="N" surname="Taleb" fullname="Nassim Nicholas Taleb">	<author initials="N" surname="Taleb" fullname="Nassim Nicholas Taleb">
	<organization/>	<organization/>
	</author>	</author>

	<date year="2020"/>	<date year="2022"/>
	</front>	</front>

	<seriesInfo name="STEM " value="Academic Press"/>	<refcontent>Revised Edition, STEM Academic Press</refcontent>
	</reference>	</reference>

	<reference anchor="UBICOMP" target="">
		<reference anchor="UBICOMP" target="https://www.taylorfrancis.com/chapters
		/edit/10.1201/9781420093612-6/ubiquitous-computing-systems-jakob-bardram-adrian-
		friday">
	<front>	<front>

	<title> Ubiquitous Computing Systems</title>	<title>Ubiquitous Computing Systems</title>
	<author initials="J" surname="Bardram" fullname="Jakob Eyvind Bardram" >	<author initials="J" surname="Bardram" fullname="Jakob Eyvind Bardram" >
	<organization/>	<organization/>
	</author>	</author>
	<author initials="A" surname="Friday" fullname="Adrian Friday">	<author initials="A" surname="Friday" fullname="Adrian Friday">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2009"/>	<date year="2009"/>
	</front>	</front>

	<seriesInfo name="In " value=" Ubiquitous Computing Fundamentals pp. 37- 94. CRC Press"/>	<refcontent>Ubiquitous Computing Fundamentals, 1st Edition, Chapman and Hall/CRC Press, pp. 37-94</refcontent>
	</reference>	</reference>

	<reference anchor="SLAM_1" target="">
		<reference anchor="SLAM_1" target="https://ieeexplore.ieee.org/document/69
		09455">
	<front>	<front>

	<title> A minimal solution to the generalized pose-and-scale problem < /title>	<title>A Minimal Solution to the Generalized Pose-and-Scale Problem</t itle>
	<author initials="J" surname="Ventura" fullname="Jonathan Ventura">	<author initials="J" surname="Ventura" fullname="Jonathan Ventura">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="C" surname="Arth" fullname="Clemens Arth">	<author initials="C" surname="Arth" fullname="Clemens Arth">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="G" surname="Reitmayr" fullname="Gerhard Reitmayr">	<author initials="G" surname="Reitmayr" fullname="Gerhard Reitmayr">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2014"/>	<date year="2014"/>
	</front>	</front>

	<seriesInfo name="In " value="Proceedings of the IEEE Conference on Comp	<refcontent>2014 IEEE Conference on Computer Vision and Pattern Recognit
	uter Vision and Pattern Recognition, pp. 422-429"/>	ion, pp. 422-429</refcontent>
		<seriesInfo name="DOI" value="10.1109/CVPR.2014.61"/>
	</reference>	</reference>

	<reference anchor="SLAM_2" target="">
		<reference anchor="SLAM_2" target="https://link.springer.com/chapter/10.10
		07/978-3-319-10593-2_2">
	<front>	<front>

	<title> A scalable solution to the generalized pose and scale problem </title>	<title>gDLS: A Scalable Solution to the Generalized Pose and Scale Pro blem</title>
	<author initials="C" surname="Sweeny" fullname="Chris Sweeny">	<author initials="C" surname="Sweeny" fullname="Chris Sweeny">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="V" surname="Fragoso" fullname="Victor Fragoso">	<author initials="V" surname="Fragoso" fullname="Victor Fragoso">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="T" surname="Hollerer" fullname="Tobias Hollerer">	<author initials="T" surname="Höllerer" fullname="Tobias Höllerer">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="M" surname="Turk" fullname="Matthew Turk">	<author initials="M" surname="Turk" fullname="Matthew Turk">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2014"/>	<date year="2014"/>
	</front>	</front>

	<seriesInfo name="In " value="European Conference on Computer Vision, pp	<refcontent>Computer Vision - ECCV 2014, pp. 16-31</refcontent>
	. 16-31"/>	<seriesInfo name="DOI" value="10.1007/978-3-319-10593-2_2"/>
	</reference>	</reference>

	<reference anchor="SLAM_3" target="">
		<reference anchor="SLAM_3" target="https://ieeexplore.ieee.org/document/66
		36302">
	<front>	<front>

	<title> Model estimation and selection towards unconstrained real-time tracking and mapping </title>	<title>Model Estimation and Selection towards Unconstrained Real-Time Tracking and Mapping</title>
	<author initials="S" surname="Gauglitz" fullname="Steffen Gauglitz">	<author initials="S" surname="Gauglitz" fullname="Steffen Gauglitz">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="C" surname="Sweeny" fullname="Chris Sweeny">	<author initials="C" surname="Sweeney" fullname="Chris Sweeney">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="J" surname="Ventura" fullname="Jonathan Ventura">	<author initials="J" surname="Ventura" fullname="Jonathan Ventura">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="M" surname="Turk" fullname="Matthew Turk">	<author initials="M" surname="Turk" fullname="Matthew Turk">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="T" surname="Hollerer" fullname="Tobias Hollerer">	<author initials="T" surname="Höllerer" fullname="Tobias Höllerer">
	<organization/>	<organization/>
	</author>	</author>

	<date year="2013"/>	<date year="2014"/>
	</front>	</front>

	<seriesInfo name="In " value="IEEE transactions on visualization and com	<refcontent>IEEE Transactions on Visualization and Computer Graphics, vo
	puter graphics, 20(6), pp. 825-838"/>	l. 20, no. 6, pp. 825-838</refcontent>
		<seriesInfo name="DOI" value="10.1109/TVCG.2013.243"/>
	</reference>	</reference>

	<reference anchor="SLAM_4" target="">
		<reference anchor="SLAM_4" target="https://ieeexplore.ieee.org/document/66
		71783">
	<front>	<front>

	<title> Handling pure camera rotation in keyframe-based SLAM </title>	<title>Handling pure camera rotation in keyframe-based SLAM</title>
	<author initials="C" surname="Pirchheim" fullname="Christian Pirchheim ">	<author initials="C" surname="Pirchheim" fullname="Christian Pirchheim ">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="G" surname="Reitmayr" fullname="Gerhard Reitmayr">	<author initials="G" surname="Reitmayr" fullname="Gerhard Reitmayr">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2013"/>	<date year="2013"/>
	</front>	</front>

	<seriesInfo name="In " value="2013 IEEE international symposium on mixed	<refcontent>2013 IEEE International Symposium on Mixed and Augmented Rea
	and augmented reality (ISMAR), pp. 229-238"/>	lity (ISMAR), pp. 229-238</refcontent>
		<seriesInfo name="DOI" value="10.1109/ISMAR.2013.6671783"/>
	</reference>	</reference>

	<reference anchor="OCCL_1" target="">
		<reference anchor="OCCL_1" target="https://onlinelibrary.wiley.com/doi/10.
		1111/1467-8659.1530011">
	<front>	<front>

	<title> Interactive Occlusion and automatic object placementfor augmen ted reality </title>	<title>Interactive Occlusion and Automatic Object Placement for Augmen ted Reality</title>
	<author initials="D.E" surname="Breen" fullname="David E. Breen">	<author initials="D.E" surname="Breen" fullname="David E. Breen">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="R.T" surname="Whitaker" fullname="Ross T. Whitaker">	<author initials="R.T" surname="Whitaker" fullname="Ross T. Whitaker">
	<organization/>	<organization/>
	</author>	</author>

		<author initials="E" surname="Rose" fullname="Eric Rose">
		<organization/>
		</author>
	<author initials="M" surname="Tuceryan" fullname="Mihran Tuceryan">	<author initials="M" surname="Tuceryan" fullname="Mihran Tuceryan">
	<organization/>	<organization/>
	</author>	</author>

	<date year="1996"/>	<date month="August" year="1996"/>
	</front>	</front>

	<seriesInfo name="In " value="Computer Graphics Forum, vol. 15, no. 3 ,	<refcontent>Computer Graphics Forum, vol. 15, no. 3, pp. 11-22</refconte
	pp. 229-238,Edinburgh, UK: Blackwell Science Ltd"/>	nt>
		<seriesInfo name="DOI" value="10.1111/1467-8659.1530011"/>
	</reference>	</reference>

	<reference anchor="OCCL_2" target="">
		<reference anchor="OCCL_2" target="https://ieeexplore.ieee.org/document/69
		48419">
	<front>	<front>

	<title> Pixel-wise closed-loop registration in video-based augmented r eality </title>	<title>Pixel-wise closed-loop registration in video-based augmented re ality</title>
	<author initials="F" surname="Zheng" fullname="Feng Zheng">	<author initials="F" surname="Zheng" fullname="Feng Zheng">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="G" surname="Welch" fullname="Greg Welch">	<author initials="G" surname="Welch" fullname="Greg Welch">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2014"/>	<date year="2014"/>
	</front>	</front>

	<seriesInfo name="In " value="IEEE International Symposium on Mixed and	<refcontent>2014 IEEE International Symposium on Mixed and Augmented Rea
	Augmented Reality (ISMAR), pp. 135-143"/>	lity (ISMAR), pp. 135-143</refcontent>
		<seriesInfo name="DOI" value="10.1109/ISMAR.2014.6948419"/>
	</reference>	</reference>

	<reference anchor="PHOTO_REG" target="">
		<reference anchor="PHOTO_REG" target="https://ieeexplore.ieee.org/document
		/6165138">
	<front>	<front>

	<title> Online tracking of outdoor lighting variations for augmented r eality with moving cameras </title>	<title>Online Tracking of Outdoor Lighting Variations for Augmented Re ality with Moving Cameras</title>
	<author initials="Y" surname="Liu" fullname="Yanli Liu">	<author initials="Y" surname="Liu" fullname="Yanli Liu">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="X" surname="Granier" fullname="Xavier Granier">	<author initials="X" surname="Granier" fullname="Xavier Granier">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2012"/>	<date year="2012"/>
	</front>	</front>

	<seriesInfo name="In " value="IEEE Transactions on visualization and com	<refcontent>IEEE Transactions on Visualization and Computer Graphics, vo
	puter graphics, 18(4), pp.573-580"/>	l. 18, no. 4, pp. 573-580</refcontent>
		<seriesInfo name="DOI" value="10.1109/TVCG.2012.53"/>
	</reference>	</reference>

	<reference anchor="GLB_ILLUM_1" target="">
		<reference anchor="GLB_ILLUM_1" target="https://ieeexplore.ieee.org/docume
		nt/6671773">
	<front>	<front>

	<title> Differential irradiance caching for fast high-quality light tr ansport between virtual and real worlds.</title>	<title>Differential Irradiance Caching for fast high-quality light tra nsport between virtual and real worlds</title>
	<author initials="P" surname="Kan" fullname="Peter Kan">	<author initials="P" surname="Kan" fullname="Peter Kan">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="H" surname="Kaufmann" fullname="Hannes Kaufmann">	<author initials="H" surname="Kaufmann" fullname="Hannes Kaufmann">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2013"/>	<date year="2013"/>
	</front>	</front>

	<seriesInfo name="In " value="IEEE International Symposium on Mixed and	<refcontent>2013 IEEE International Symposium on Mixed and Augmented Rea
	Augmented Reality (ISMAR),pp. 133-141"/>	lity (ISMAR), pp. 133-141</refcontent>
		<seriesInfo name="DOI" value="10.1109/ISMAR.2013.6671773"/>
	</reference>	</reference>

	<reference anchor="GLB_ILLUM_2" target="">
		<reference anchor="GLB_ILLUM_2" target="https://ieeexplore.ieee.org/docume
		nt/6948407">
	<front>	<front>

	<title> Delta voxel cone tracing.</title>	<title>Delta Voxel Cone Tracing</title>
	<author initials="T" surname="Franke" fullname="Tobias Franke">	<author initials="T" surname="Franke" fullname="Tobias Franke">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2014"/>	<date year="2014"/>
	</front>	</front>

	<seriesInfo name="In " value="IEEE International Symposium on Mixed and	<refcontent>2014 IEEE International Symposium on Mixed and Augmented Rea
	Augmented Reality (ISMAR), pp. 39-44"/>	lity (ISMAR), pp. 39-44</refcontent>
		<seriesInfo name="DOI" value="10.1109/ISMAR.2014.6948407"/>
	</reference>	</reference>

	<reference anchor="LENS_DIST" target="">
		<reference anchor="LENS_DIST" target="https://link.springer.com/chapter/10
		.1007/978-3-7091-6785-4_2">
	<front>	<front>

	<title> Practical calibration procedures for augmented reality.</title >	<title>Practical Calibration Procedures for Augmented Reality</title>
	<author initials="A" surname="Fuhrmann" fullname="Anton Fuhrmann">	<author initials="A" surname="Fuhrmann" fullname="Anton Fuhrmann">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">
	<organization/>	<organization/>
	</author>	</author>

		<author initials="W" surname="Purgathofer" fullname="Werner Purgathofe
		r">
		<organization/>
		</author>
	<date year="2000"/>	<date year="2000"/>
	</front>	</front>

	<seriesInfo name="In " value="Virtual Environments 2000, pp. 3-12. Sprin	<refcontent>Virtual Environments 2000, pp. 3-12</refcontent>
	ger, Vienna"/>	<seriesInfo name="DOI" value="10.1007/978-3-7091-6785-4_2"/>
	</reference>	</reference>

	<reference anchor="BLUR" target="">
		<reference anchor="BLUR" target="https://diglib.eg.org/items/6954bf7e-5852
		-44cf-8155-4ba269dc4cee">
	<front>	<front>

	<title> Physically-Based Depth of Field in Augmented Reality.</title>	<title>Physically-Based Depth of Field in Augmented Reality</title>
	<author initials="P" surname="Kan" fullname="Peter Kan">	<author initials="P" surname="Kan" fullname="Peter Kan">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="H" surname="Kaufmann" fullname="Hannes Kaufmann">	<author initials="H" surname="Kaufmann" fullname="Hannes Kaufmann">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2012"/>	<date year="2012"/>
	</front>	</front>

	<seriesInfo name="In " value="Eurographics (Short Papers), pp. 89-92."/>	<refcontent>Eurographics 2012 - Short Papers, pp. 89-92</refcontent>
		<seriesInfo name="DOI" value="10.2312/conf/EG2012/short/089-092"/>
	</reference>	</reference>

	<reference anchor="NOISE" target="">
		<reference anchor="NOISE" target="https://ieeexplore.ieee.org/document/407
		9277">
	<front>	<front>

	<title> Enhanced visual realism by incorporating camera image effects. </title>	<title>Enhanced visual realism by incorporating camera image effects</ title>
	<author initials="J" surname="Fischer" fullname="Jan Fischer">	<author initials="J" surname="Fischer" fullname="Jan Fischer">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="D" surname="Bartz" fullname="Dirk Bartz">	<author initials="D" surname="Bartz" fullname="Dirk Bartz">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="W" surname="Straßer" fullname="Wolfgang Straßer">	<author initials="W" surname="Strasser" fullname="Wolfgang Strasser">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2006"/>	<date year="2006"/>
	</front>	</front>

	<seriesInfo name="In " value="IEEE/ACM International Symposium on Mixed	<refcontent>2006 IEEE/ACM International Symposium on Mixed and Augmented
	and Augmented Reality, pp. 205-208."/>	Reality, pp. 205-208</refcontent>
		<seriesInfo name="DOI" value="10.1109/ISMAR.2006.297815"/>
	</reference>	</reference>

	<reference anchor="VIS_INTERFERE" target="">
		<reference anchor="VIS_INTERFERE" target="https://ieeexplore.ieee.org/docu
		ment/4538846">
	<front>	<front>

	<title> Interactive focus and context visualization for augmented real ity.</title>	<title>Interactive Focus and Context Visualization for Augmented Reali ty</title>
	<author initials="D" surname="Kalkofen" fullname="Denis Kalkofen">	<author initials="D" surname="Kalkofen" fullname="Denis Kalkofen">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="E" surname="Mendez" fullname="Erick Mendez">	<author initials="E" surname="Mendez" fullname="Erick Mendez">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie g">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2007"/>	<date year="2007"/>
	</front>	</front>

	<seriesInfo name="In " value="6th IEEE and ACM International Symposium o	<refcontent>2007 6th IEEE and ACM International Symposium on Mixed and A
	n Mixed and Augmented Reality, pp. 191-201."/>	ugmented Reality, pp. 191-201</refcontent>
		<seriesInfo name="DOI" value="10.1109/ISMAR.2007.4538846"/>
	</reference>	</reference>

	<reference anchor="DEV_HEAT_2" target="">
		<reference anchor="DEV_HEAT_2" target="https://www.mdpi.com/1424-8220/20/5
		/1446">
	<front>	<front>

	<title> Thermal model and countermeasures for future smart glasses.</t itle>	<title>Thermal Model and Countermeasures for Future Smart Glasses</tit le>
	<author initials="K" surname="Matsuhashi" fullname="Kodai Matsuhashi">	<author initials="K" surname="Matsuhashi" fullname="Kodai Matsuhashi">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="T" surname="Kanamoto" fullname="Toshiki Kanamoto">	<author initials="T" surname="Kanamoto" fullname="Toshiki Kanamoto">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="A" surname="Kurokawa" fullname=" Atsushi Kurokawa">	<author initials="A" surname="Kurokawa" fullname="Atsushi Kurokawa">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2020"/>	<date year="2020"/>
	</front>	</front>

	<seriesInfo name="In " value="Sensors, 20(5), p.1446."/>	<refcontent>Sensors, vol. 20, no. 5, p. 1446</refcontent>
		<seriesInfo name="DOI" value="10.3390/s20051446"/>
	</reference>	</reference>

	<reference anchor="BATT_DRAIN" target="">
		<reference anchor="BATT_DRAIN" target="https://ieeexplore.ieee.org/documen
		t/7993011">
	<front>	<front>

	<title> A survey of wearable devices and challenges.</title>	<title>A Survey of Wearable Devices and Challenges</title>
	<author initials="S" surname="Seneviratne" fullname="Suranga Senevirat ne">	<author initials="S" surname="Seneviratne" fullname="Suranga Senevirat ne">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="Y" surname="Hu" fullname="Yining Hu">	<author initials="Y" surname="Hu" fullname="Yining Hu">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="T" surname="Nguyen" fullname=" Tham Nguyen">	<author initials="T" surname="Nguyen" fullname="Tham Nguyen">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="G" surname="Lan" fullname=" Guohao Lan">	<author initials="G" surname="Lan" fullname="Guohao Lan">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="S" surname="Khalifa" fullname=" Sara Khalifa">	<author initials="S" surname="Khalifa" fullname="Sara Khalifa">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="K" surname="Thilakarathna" fullname=" Kanchana Thila karathna">	<author initials="K" surname="Thilakarathna" fullname="Kanchana Thilak arathna">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="M" surname="Hassan" fullname=" Mahbub Hassan">	<author initials="M" surname="Hassan" fullname="Mahbub Hassan">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="A" surname="Seneviratne" fullname=" Aruna Seneviratn e">	<author initials="A" surname="Seneviratne" fullname="Aruna Seneviratne ">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2017"/>	<date year="2017"/>
	</front>	</front>

	<seriesInfo name="In " value="IEEE Communication Surveys and Tutorials,	<refcontent>IEEE Communication Surveys and Tutorials, vol. 19 no. 4, pp.
	19(4), p.2573-2620."/>	2573-2620</refcontent>
		<seriesInfo name="DOI" value="10.1109/COMST.2017.2731979"/>
	</reference>	</reference>

	<reference anchor="PER_SENSE" target="">
		<reference anchor="PER_SENSE" target="https://dl.acm.org/doi/10.1145/10125
		51.1012559">
	<front>	<front>
	<title> Perceptual sensitivity to head tracking latency in virtual env ironments with varying degrees of scene complexity.</title>	<title> Perceptual sensitivity to head tracking latency in virtual env ironments with varying degrees of scene complexity.</title>

	<author initials="K" surname="Mania" fullname="Katrina Mania">	<author initials="K" surname="Mania" fullname="Katerina Mania">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="B.D." surname="Adelstein" fullname="Bernard D. Adels tein ">	<author initials="B.D." surname="Adelstein" fullname="Bernard D. Adels tein">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="S.R." surname="Ellis" fullname=" Stephen R. Ellis">	<author initials="S.R." surname="Ellis" fullname="Stephen R. Ellis">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="M.I." surname="Hill" fullname=" Michael I. Hill">	<author initials="M.I." surname="Hill" fullname="Michael I. Hill">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2004"/>	<date year="2004"/>
	</front>	</front>

	<seriesInfo name="In " value="Proceedings of the 1st Symposium on Applie	<refcontent>APGV '04: Proceedings of the 1st Symposium on Applied percep
	d perception in graphics and visualization pp. 39-47."/>	tion in graphics and visualization, pp. 39-47</refcontent>
		<seriesInfo name="DOI" value="10.1145/1012551.1012559"/>
	</reference>	</reference>

	<reference anchor="XR" target="">
		<reference anchor="XR" target="https://portal.3gpp.org/desktopmodules/Spec
		ifications/SpecificationDetails.aspx?specificationId=3534">
	<front>	<front>

	<title> 3GPP TR 26.928: Extended Reality (XR) in 5G.</title>	<title>Extended Reality (XR) in 5G</title>
	<author initials="" surname="3GPP" fullname="3GPP">	<author>
	<organization/>	<organization>3GPP</organization>
	</author>	</author>
	<date year="2020"/>	<date year="2020"/>
	</front>	</front>

	<seriesInfo name="" value="https://portal.3gpp.org/desktopmodules/Specif ications/SpecificationDetails.aspx?specificationId=3534"/>	<seriesInfo name="3GPP TR" value="26.928"/>
	</reference>	</reference>

	<reference anchor="CLOUD" target="">
		<reference anchor="CLOUD" target="https://dl.acm.org/doi/10.1145/3442381.3
		449854">
	<front>	<front>

	<title> Surrounded by the Clouds: A Comprehensive Cloud Reachability S	<title>Surrounded by the Clouds: A Comprehensive Cloud Reachability St
	tudy.</title>	udy</title>
	<author initials="L." surname="Corneo" fullname=" Lorenzo Corneo">	<author initials="L." surname="Corneo" fullname="Lorenzo Corneo">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="M." surname="Eder" fullname=" Maximilian Eder">	<author initials="M." surname="Eder" fullname="Maximilian Eder">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="N." surname="Mohan" fullname=" Nitinder Mohan">	<author initials="N." surname="Mohan" fullname="Nitinder Mohan">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="A." surname="Zavodovski" fullname=" Aleksandr Zavodo vski">	<author initials="A." surname="Zavodovski" fullname="Aleksandr Zavodov ski">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="S." surname="Bayhan" fullname=" Suzan Bayhan">	<author initials="S." surname="Bayhan" fullname="Suzan Bayhan">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="W." surname="Wong" fullname=" Walter Wong">	<author initials="W." surname="Wong" fullname="Walter Wong">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="P." surname="Gunningberg" fullname=" Per Gunningberg ">	<author initials="P." surname="Gunningberg" fullname="Per Gunningberg" >
	<organization/>	<organization/>
	</author>	</author>

	<author initials="J." surname="Kangasharju" fullname=" Jussi Kangashar ju">	<author initials="J." surname="Kangasharju" fullname="Jussi Kangasharj u">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="J." surname="Ott" fullname=" Jörg Ott">	<author initials="J." surname="Ott" fullname="Jörg Ott">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2021"/>	<date year="2021"/>
	</front>	</front>

	<seriesInfo name="In" value="Proceedings of the Web Conference 2021, pp.	<refcontent>WWW '21: Proceedings of the Web Conference 2021, pp. 295-304
	295-304"/>	</refcontent>
		<seriesInfo name="DOI" value="10.1145/3442381.3449854"/>
	</reference>	</reference>

	<reference anchor="OCCL_3" target="">
		<reference anchor="OCCL_3" target="https://www.roadtovr.com/oculus-shares-
		5-key-ingredients-for-presence-in-virtual-reality/">
	<front>	<front>

	<title> Oculus Shares 5 Key Ingredients for Presence in Virtual Realit y.</title>	<title>Oculus Shares 5 Key Ingredients for Presence in Virtual Reality </title>
	<author initials="B." surname="Lang" fullname="Ben Lang">	<author initials="B." surname="Lang" fullname="Ben Lang">
	<organization/>	<organization/>
	</author>	</author>

	<date year="2014"/>	<date day="24" month="September" year="2014"/>
	</front>	</front>

	<seriesInfo name="" value="https://www.roadtovr.com/oculus-shares-5-key- ingredients-for-presence-in-virtual-reality/"/>	<refcontent>Road to VR</refcontent>
	</reference>	</reference>

	<reference anchor="PREDICT" target="">
		<reference anchor="PREDICT" target="https://pubmed.ncbi.nlm.nih.gov/226242
		90/">
	<front>	<front>

	<title> The effect of apparent latency on simulator sickness while usi	<title>The effect of apparent latency on simulator sickness while usin
	ng a see-through helmet-mounted display: Reducing apparent latency with predicti	g a see-through helmet-mounted display: reducing apparent latency with predictiv
	ve compensation..</title>	e compensation</title>
	<author initials="T. J." surname="Buker" fullname="Timothy J. Buker">	<author initials="T.J." surname="Buker" fullname="Timothy J. Buker">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="D.A." surname="Vincenzi" fullname="Dennis A. Vincenz i ">	<author initials="D.A." surname="Vincenzi" fullname="Dennis A. Vincenz i ">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="J.E." surname="Deaton" fullname=" John E. Deaton">	<author initials="J.E." surname="Deaton" fullname=" John E. Deaton">
	<organization/>	<organization/>
	</author>	</author>

	<date year="2012"/>	<date month="April" year="2012"/>
	</front>	</front>

	<seriesInfo name="In " value="Human factors 54.2, pp. 235-249."/>	<refcontent>Human Factors, vol. 54, no. 2, pp. 235-249</refcontent>
		<seriesInfo name="DOI" value="10.1177/0018720811428734"/>
	</reference>	</reference>

	<reference anchor="URLLC" target="">
		<reference anchor="URLLC" target="https://portal.3gpp.org/desktopmodules/S
		pecifications/SpecificationDetails.aspx?specificationId=3453">
	<front>	<front>

	<title> 3GPP TR 23.725: Study on enhancement of Ultra-Reliable	<title>Study on enhancement of Ultra-Reliable
	Low-Latency Communication (URLLC) support in the 5G Core	Low-Latency Communication (URLLC) support in the 5G Core

	network (5GC).</title>	network (5GC)</title>
	<author initials="" surname="3GPP" fullname="3GPP">	<author>
	<organization/>	<organization>3GPP</organization>
	</author>	</author>
	<date year="2019"/>	<date year="2019"/>
	</front>	</front>

	<seriesInfo name="" value="https://portal.3gpp.org/desktopmodules/Specif ications/ SpecificationDetails.aspx?specificationId=3453"/>	<seriesInfo name="3GPP TR" value="23.725"/>
	</reference>	</reference>

	<reference anchor="AUGMENTED" target="">
		<reference anchor="AUGMENTED" target="https://www.oreilly.com/library/view
		/augmented-reality-principles/9780133153217/">
	<front>	<front>

	<title> Augmented Reality</title>	<title>Augmented Reality: Principles and Practice</title>
	<author initials="D. S." surname="Schmalstieg" fullname="Dieter Schmal	<author initials="D" surname="Schmalstieg" fullname="Dieter Schmalstie
	stieg">	g">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="T.H." surname="Hollerer" fullname="Dennis A.Hollerer ">	<author initials="T" surname="Höllerer" fullname="Tobias Höllerer">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2016"/>	<date year="2016"/>
	</front>	</front>

	<seriesInfo name="" value="Addison Wesley"/>	<refcontent>Addison-Wesley Professional</refcontent>
	</reference>	</reference>


	<reference anchor="REG" target="">	<reference anchor="REG" target="https://direct.mit.edu/pvar/article-abstra ct/6/4/413/18334/Registration-Error-Analysis-for-Augmented-Reality?redirectedFro m=fulltext">
	<front>	<front>

	<title> Registration error analysis for augmented reality.</title>	<title>Registration Error Analysis for Augmented Reality</title>
	<author initials="R. L." surname="Holloway" fullname="Richard L. Hollo	<author initials="R.L." surname="Holloway" fullname="Richard L. Hollow
	way">	ay">
	<organization/>	<organization/>
	</author>	</author>

	<date year="1997"/>	<date month="August" year="1997"/>
	</front>	</front>

	<seriesInfo name="In " value="Presence:Teleoperators and Virtual Environ	<refcontent>Presence: Teleoperators and Virtual Environments, vol. 6, no
	ments 6.4, pp. 413-432."/>	. 4, pp. 413-432</refcontent>
		<seriesInfo name="DOI" value="10.1162/pres.1997.6.4.413"/>
	</reference>	</reference>


	<reference anchor="XR_TRAFFIC" target="">	<reference anchor="XR_TRAFFIC" target="https://ieeexplore.ieee.org/documen t/9158434">
	<front>	<front>
	<title> Characterization of Multi-User Augmented Reality over Cellular Networks </title>	<title> Characterization of Multi-User Augmented Reality over Cellular Networks </title>
	<author initials="K." surname="Apicharttrisorn" fullname="Kittipat Api charttrisorn">	<author initials="K." surname="Apicharttrisorn" fullname="Kittipat Api charttrisorn">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="B." surname="Balasubramanian" fullname="Bharath Bala subramanian ">	<author initials="B." surname="Balasubramanian" fullname="Bharath Bala subramanian ">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="J." surname="Chen" fullname=" Jiasi Chen">	<author initials="J." surname="Chen" fullname="Jiasi Chen">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="R." surname="Sivaraj" fullname=" Rajarajan Sivaraj">	<author initials="R." surname="Sivaraj" fullname="Rajarajan Sivaraj">
	<organization/>	<organization/>
	</author>	</author>

	<author initials="Y." surname="Tsai" fullname=" Yi-Zhen Tsai">	<author initials="Y." surname="Tsai" fullname="Yi-Zhen Tsai">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="R." surname="Jana" fullname="Rittwik Jana">	<author initials="R." surname="Jana" fullname="Rittwik Jana">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="S." surname="Krishnamurthy" fullname="Srikanth Krish namurthy">	<author initials="S." surname="Krishnamurthy" fullname="Srikanth Krish namurthy">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="T." surname="Tran" fullname="Tuyen Tran">	<author initials="T." surname="Tran" fullname="Tuyen Tran">
	<organization/>	<organization/>
	</author>	</author>
	<author initials="Y." surname="Zhou" fullname="Yu Zhou">	<author initials="Y." surname="Zhou" fullname="Yu Zhou">
	<organization/>	<organization/>
	</author>	</author>
	<date year="2020"/>	<date year="2020"/>
	</front>	</front>

	<seriesInfo name="In " value="17th Annual IEEE International Conference	<refcontent>2020 17th Annual IEEE International Conference on Sensing, C
	on Sensing, Communication, and Networking (SECON), pp. 1-9. IEEE"/>	ommunication, and Networking (SECON), pp. 1-9</refcontent>
		<seriesInfo name="DOI" value="10.1109/SECON48991.2020.9158434"/>
	</reference>	</reference>


	<reference anchor="EDGE_3" target="">	<reference anchor="EDGE_3" target="https://link.springer.com/book/10.1007/ 978-3-031-79733-0">
	<front>	<front>

	<title> 5G mobile networks: A systems approach.</title>	<title>5G Mobile Networks: A Systems Approach</title>
	<author initials="L." surname="Peterson" fullname="Larry Peterson">	<author initials="L." surname="Peterson" fullname="Larry Peterson">
	<organization/>	<organization/>
	</author>	</author>

		<author initials="O." surname="Sunay" fullname="Oguz Sunay">
	<author initials="O." surname="Sunay" fullname="Oguz Sunay">
	<organization/>	<organization/>
	</author>	</author>


	<date year="2020"/>	<date year="2020"/>
	</front>	</front>

	<seriesInfo name="In " value="Synthesis Lectures on Network Systems."/>	<refcontent>Synthesis Lectures on Network Systems</refcontent>
		<seriesInfo name="DOI" value="10.1007/978-3-031-79733-0"/>
	</reference>	</reference>


	<reference anchor="AUGMENTED_2" target="">	<reference anchor="AUGMENTED_2" target="https://direct.mit.edu/pvar/articl e-abstract/6/4/355/18336/A-Survey-of-Augmented-Reality?redirectedFrom=fulltext">
	<front>	<front>

	<title> A Survey of Augmented Reality.</title>	<title>A Survey of Augmented Reality</title>
	<author initials="R. T." surname="Azuma" fullname="Ronald T. Azuma">	<author initials="R.T." surname="Azuma" fullname="Ronald T. Azuma">
	<organization/>	<organization/>
	</author>	</author>

	<date year="1997"/>	<date month="August" year="1997"/>
	</front>	</front>

	<seriesInfo name="" value="Presence:Teleoperators and Virtual Environmen	<refcontent>Presence: Teleoperators and Virtual Environments, vol. 6, no
	ts 6.4, pp. 355-385."/>	. 4, pp. 355-385</refcontent>
		<seriesInfo name="DOI" value="10.1162/pres.1997.6.4.355"/>
	</reference>	</reference>


	<reference anchor="METRICS_1" target="">	<reference anchor="METRICS_1" target="https://gsacom.com/paper/augmented-v irtual-reality-first-wave-5g-killer-apps-qualcomm-abi-research/">
	<front>	<front>

	<title> Augmented and Virtual Reality: The first Wave of Killer Apps.	<title>Augmented and Virtual Reality: The first Wave of Killer Apps: Q
	</title>	ualcomm - ABI Research</title>
	<author initials="" surname="ABI Research" fullname="ABI Research">	<author>
	<organization/>	<organization>ABI Research</organization>
	</author>	</author>

		<date month="April" year="2017"/>
	<date year="2017"/>
	</front>	</front>

	<seriesInfo name="" value="https://gsacom.com/paper/augmented-virtual-re ality-first-wave-5g-killer-apps-qualcomm-abi-research/"/>
	</reference>	</reference>


	<reference anchor="METRICS_2" target="">	<reference anchor="METRICS_2" target="https://ieeexplore.ieee.org/document /392383">
	<front>	<front>

	<title> Wide Area Traffic: The Failure of Poisson Modelling.</title>	<title>Wide area traffic: the failure of Poisson modeling</title>
	<author initials="V." surname="Paxon" fullname="Vern Paxon">	<author initials="V." surname="Paxon" fullname="Vern Paxon">
	<organization/>	<organization/>
	</author>	</author>

		<author initials="S." surname="Floyd" fullname="Sally Floyd">
	<author initials="S." surname="Floyd" fullname="Sally Floyd">
	<organization/>	<organization/>
	</author>	</author>

		<date month="June" year="1995"/>
	<date year="1995"/>
	</front>	</front>

	<seriesInfo name="In" value="IEEE/ACM Transactions on Networking, pp. 2	<refcontent>IEEE/ACM Transactions on Networking, vol. 3, no. 3, pp. 226-
	26-244."/>	244</refcontent>
		<seriesInfo name="DOI" value="10.1109/90.392383"/>
	</reference>	</reference>


	<reference anchor="METRICS_3" target="">	<reference anchor="METRICS_3" target="https://ieeexplore.ieee.org/abstract /document/554723">
	<front>	<front>

	<title> Self-Similarity Through High Variability: Statistical Analysis and Ethernet LAN Traffic at Source Level.</title>	<title>Self-similarity through high variability: statistical analysis and Ethernet LAN traffic at source level</title>
	<author initials="W." surname="Willinger" fullname="Walter Willinger">	<author initials="W." surname="Willinger" fullname="Walter Willinger">
	<organization/>	<organization/>
	</author>	</author>


	<author initials="M.S." surname="Taqqu" fullname="Murad S. Taqqu">	<author initials="M.S." surname="Taqqu" fullname="Murad S. Taqqu">
	<organization/>	<organization/>
	</author>	</author>


	<author initials="R." surname="Sherman" fullname="Robert Sherman">	<author initials="R." surname="Sherman" fullname="Robert Sherman">
	<organization/>	<organization/>
	</author>	</author>


	<author initials="D.V." surname="Wilson" fullname="Daniel V. Wilson">	<author initials="D.V." surname="Wilson" fullname="Daniel V. Wilson">
	<organization/>	<organization/>
	</author>	</author>

		<date month="February" year="1997"/>
	<date year="1997"/>
	</front>	</front>

	<seriesInfo name="In" value="IEEE/ACM Transactions on Networking, pp. 7	<refcontent>IEEE/ACM Transactions on Networking, vol. 5, no. 1, pp. 71-8
	1-86."/>	6</refcontent>
		<seriesInfo name="DOI" value="10.1109/90.554723"/>
	</reference>	</reference>


	<reference anchor="METRICS_4" target="">	<reference anchor="METRICS_4" target="https://www.sciencedirect.com/scienc e/article/pii/S1063520300903427">
	<front>	<front>

	<title> Multiscale Analysis and Data Networks.</title>	<title>Multiscale Analysis and Data Networks</title>
	<author initials="A.C." surname="Gilbert" fullname="A. C. Gilbert">	<author initials="A.C." surname="Gilbert" fullname="A.C. Gilbert">
	<organization/>	<organization/>
	</author>	</author>

		<date month="May" year="2001"/>
	<date year="2001"/>
	</front>	</front>

	<seriesInfo name="In" value="Applied and Computational Harmonic Analysis	<refcontent>Applied and Computational Harmonic Analysis, vol. 10, no. 3,
	, pp. 185-202."/>	pp. 185-202</refcontent>
		<seriesInfo name="DOI" value="10.1006/acha.2000.0342"/>
	</reference>	</reference>


	<reference anchor="METRICS_5" target="">	<reference anchor="METRICS_5" target="https://research.google/pubs/site-re liability-engineering-how-google-runs-production-systems/">
	<front>	<front>

	<title> Site Reliability Engineering: How Google Runs Production Syste	<title>Site Reliability Engineering: How Google Runs Production System
	ms.</title>	s</title>
	<author initials="B." surname="Beyer" fullname="Betsy Beyer">	<author initials="B." surname="Beyer" fullname="Betsy Beyer" role="edi
		tor">
	<organization/>	<organization/>
	</author>	</author>

		<author initials="C." surname="Jones" fullname="Chris Jones" role="edit
	<author initials="C." surname="Jones" fullname="Chris Jones">	or">
	<organization/>	<organization/>
	</author>	</author>

		<author initials="J." surname="Petoff" fullname="Jennifer Petoff" role=
	<author initials="J." surname="Petoff" fullname="Jennifer Petoff">	"editor">
	<organization/>	<organization/>
	</author>	</author>

		<author initials="N.R." surname="Murphy" fullname="Niall Richard Murphy
	<author initials="N.R." surname="Murphy" fullname="Niall Richard Murphy	" role="editor">
	">
	<organization/>	<organization/>
	</author>	</author>


	<date year="2016"/>	<date year="2016"/>
	</front>	</front>

	<seriesInfo name="" value="O'Reilly Media, Inc."/>	<refcontent>O'Reilly Media, Inc.</refcontent>
	</reference>	</reference>


	<reference anchor="METRICS_6" target="">	<reference anchor="METRICS_6" target="https://ieeexplore.ieee.org/document /9363323">
	<front>	<front>

	<title> A survey on mobile augmented reality with 5G mobile edge compu ting: architectures, applications, and technical aspects.</title>	<title>A Survey on Mobile Augmented Reality With 5G Mobile Edge Comput ing: Architectures, Applications, and Technical Aspects</title>
	<author initials="Y." surname="Siriwardhana" fullname="Yushan Siriward hana">	<author initials="Y." surname="Siriwardhana" fullname="Yushan Siriward hana">
	<organization/>	<organization/>
	</author>	</author>


	<author initials="P." surname="Porambage" fullname="Pawani Porambage">	<author initials="P." surname="Porambage" fullname="Pawani Porambage">
	<organization/>	<organization/>
	</author>	</author>


	<author initials="M." surname="Liyanage" fullname="Madhusanka Liyanage" >	<author initials="M." surname="Liyanage" fullname="Madhusanka Liyanage" >
	<organization/>	<organization/>
	</author>	</author>


	<author initials="M." surname="Ylianttila" fullname="Mika Ylianttila">	<author initials="M." surname="Ylianttila" fullname="Mika Ylianttila">
	<organization/>	<organization/>
	</author>	</author>


	<date year="2021"/>	<date year="2021"/>
	</front>	</front>

	<seriesInfo name="In" value="IEEE Communications Surveys and Tutorials,	<refcontent>IEEE Communications Surveys and Tutorials, vol. 23, no. 2, p
	Vol 23, No. 2"/>	p. 1160-1192</refcontent>
		<seriesInfo name="DOI" value="10.1109/COMST.2021.3061981"/>
	</reference>	</reference>


	<reference anchor="HEAVY_TAIL_3" target="">	<reference anchor="HEAVY_TAIL_3" target="https://www.wiley.com/en-us/A+Pri mer+in+Data+Reduction%3A+An+Introductory+Statistics+Textbook-p-9780471101352">
	<front>	<front>

	<title> A Primer in Data Reduction.</title>	<title>A Primer in Data Reduction: An Introductory Statistics Textbook </title>
	<author initials="A." surname="Ehrenberg" fullname="A.S.C Ehrenberg ">	<author initials="A." surname="Ehrenberg" fullname="A.S.C Ehrenberg ">
	<organization/>	<organization/>
	</author>	</author>

		<date year="2007"/>
	<date year="1982"/>
	</front>	</front>

	<seriesInfo name="John" value="Wiley, London"/>	<refcontent>John Wiley and Sons</refcontent>
	</reference>	</reference>


	<reference anchor="RFC9023" target="https://www.rfc-editor.org/info/rfc9023">	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.902
	<front>	3.xml"/>
	<title>Deterministic Networking (DetNet) Data Plane: IP over IEEE 802.1 Time-Sen	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.893
	sitive Networking (TSN)</title>	9.xml"/>
	<author fullname="B. Varga" initials="B." role="editor" surname="Varga"/>	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.945
	<author fullname="J. Farkas" initials="J." surname="Farkas"/>	0.xml"/>
	<author fullname="A. Malis" initials="A." surname="Malis"/>
	<author fullname="S. Bryant" initials="S." surname="Bryant"/>
	<date month="June" year="2021"/>
	<abstract>
	<t>This document specifies the Deterministic Networking IP data plane when opera
	ting over a Time-Sensitive Networking (TSN) sub-network. This document does not
	define new procedures or processes. Whenever this document makes statements or r
	ecommendations, these are taken from normative text in the referenced RFCs.</t>
	</abstract>
	</front>
	<seriesInfo name="RFC" value="9023"/>
	<seriesInfo name="DOI" value="10.17487/RFC9023"/>
	</reference>


	<reference anchor="RFC8939" target="https://www.rfc-editor.org/info/rfc8939">	<reference anchor="DIST" target="https://dl.acm.org/doi/10.5555/2029110">
	<front>	<front>
	<title>Deterministic Networking (DetNet) Data Plane: IP</title>	<title> Distributed Systems: Concepts and Design</title>
	<author fullname="B. Varga" initials="B." role="editor" surname="Varga"/>	<author initials="G" surname="Coulouris" fullname="George Coulouris">
	<author fullname="J. Farkas" initials="J." surname="Farkas"/>	<organization/>
	<author fullname="L. Berger" initials="L." surname="Berger"/>	</author>
	<author fullname="D. Fedyk" initials="D." surname="Fedyk"/>	<author initials="J" surname="Dollimore" fullname="Jean Dollimore">
	<author fullname="S. Bryant" initials="S." surname="Bryant"/>	<organization/>
	<date month="November" year="2020"/>	</author>
	<abstract>	<author initials="T" surname="Kindberg" fullname="Tim Kindberg">
	<t>This document specifies the Deterministic Networking (DetNet) data plane oper	<organization/>
	ation for IP hosts and routers that provide DetNet service to IP-encapsulated da	</author>
	ta. No DetNet-specific encapsulation is defined to support IP flows; instead, th	<author initials="G" surname="Blair" fullname="Gordon Blair">
	e existing IP-layer and higher-layer protocol header information is used to supp	<organization/>
	ort flow identification and DetNet service delivery. This document builds on the	</author>
	DetNet architecture (RFC 8655) and data plane framework (RFC 8938).</t>	<date year="2011"/>
	</abstract>	</front>
	</front>	<refcontent>Addison-Wesley</refcontent>
	<seriesInfo name="RFC" value="8939"/>	</reference>
	<seriesInfo name="DOI" value="10.17487/RFC8939"/>
	</reference>


	<reference anchor="RFC9450" target="https://www.rfc-editor.org/info/rfc9450">	<reference anchor="NIST1" target="https://csrc.nist.gov/pubs/sp/800/146/fi
	<front>	nal">
	<title>Reliable and Available Wireless (RAW) Use Cases</title>	<front>
	<author fullname="CJ. Bernardos" initials="CJ." role="editor" surname="Bernardos	<title>Cloud Computing Synopsis and Recommendations</title>
	"/>	<author>
	<author fullname="G. Papadopoulos" initials="G." surname="Papadopoulos"/>	<organization>NIST</organization>
	<author fullname="P. Thubert" initials="P." surname="Thubert"/>	</author>
	<author fullname="F. Theoleyre" initials="F." surname="Theoleyre"/>	<date month="May" year="2012"/>
	<date month="August" year="2023"/>	</front>
	<abstract>	<seriesInfo name="NIST SP" value="800-146"/>
	<t>The wireless medium presents significant specific challenges to achieve prope	<seriesInfo name="DOI" value="10.6028/NIST.SP.800-146"/>
	rties similar to those of wired deterministic networks. At the same time, a numb	</reference>
	er of use cases cannot be solved with wires and justify the extra effort of goin
	g wireless. This document presents wireless use cases (such as aeronautical comm
	unications, amusement parks, industrial applications, pro audio and video, gamin
	g, Unmanned Aerial Vehicle (UAV) and vehicle-to-vehicle (V2V) control, edge robo
	tics, and emergency vehicles), demanding reliable and available behavior.</t>
	</abstract>
	</front>
	<seriesInfo name="RFC" value="9450"/>
	<seriesInfo name="DOI" value="10.17487/RFC9450"/>
	</reference>


	<reference anchor="DIST" target="">	<reference anchor="CWE" target="https://www.sans.org/top25-software-errors
	<front>	/">
	<title> Distributed Systems: Concepts and Design</title>	<front>
	<author initials="G" surname="Coulouris" fullname="George Coulouris">	<title>CWE/SANS TOP 25 Most Dangerous Software Errors</title>
	<organization/>	<author>
	</author>	<organization>SANS Institute</organization>
	<author initials="J" surname="Dollimore" fullname="Jean Dollimore">	</author>
	<organization/>	</front>
	</author>	</reference>
	<author initials="T" surname="Kindberg" fullname="Tim Kindberg">
	<organization/>
	</author>
	<author initials="G" surname="Blair" fullname="Gordon Blair">
	<organization/>
	</author>
	<date year="2011"/>
	</front>
	<seriesInfo name="" value="Addison Wesley"/>
	</reference>
	<reference anchor="NIST1" target="">
	<front>
	<title> NIST SP 800-146: Cloud Computing Synopsis and Recommendations</title>
	<author initials="" surname="" fullname="NIST">
	<organization/>
	</author>
	<date year="2012"/>
	</front>
	<seriesInfo name="" value="National Institute of Standards and Technology, US De
	partment of Commerce"/>
	</reference>
	<reference anchor="CWE" target="">
	<front>
	<title> CWE/SANS TOP 25 Most Dangerous Software Errorss</title>
	<author initials="" surname="" fullname="SANS Institute">
	<organization/>
	</author>
	<date year="2012"/>
	</front>
	<seriesInfo name="" value="Common Weakness Enumeration, SANS Institute"/>
	</reference>
	<reference anchor="NIST2" target="">
	<front>
	<title> NIST SP 800-123: Guide to General Server Security</title>
	<author initials="" surname="" fullname="NIST">
	<organization/>
	</author>
	<date year="2008"/>
	</front>
	<seriesInfo name="" value="National Institute of Standards and Technology, US De
	partment of Commerce"/>
	</reference>


	<reference anchor="RFC2210" target="https://www.rfc-editor.org/info/rfc22	<reference anchor="NIST2" target="https://csrc.nist.gov/pubs/sp/800/123/fi
	10">	nal">
	<front>	<front>
	<title>The Use of RSVP with IETF Integrated Services</title>	<title>Guide to General Server Security</title>
	<author fullname="J. Wroclawski" initials="J." surname="Wroclawski"/>	<author>
	<date month="September" year="1997"/>	<organization>NIST</organization>
	<abstract>	</author>
	<t>This note describes the use of the RSVP resource reservation protocol with th	<date month="July" year="2008"/>
	e Controlled-Load and Guaranteed QoS control services. [STANDARDS-TRACK]</t>	</front>
	</abstract>	<seriesInfo name="NIST SP" value="800-123"/>
	</front>	<seriesInfo name="DOI" value="10.6028/NIST.SP.800-123"/>
	<seriesInfo name="RFC" value="2210"/>	</reference>
	<seriesInfo name="DOI" value="10.17487/RFC2210"/>
	</reference>


	<reference anchor="RFC2475" target="https://www.rfc-editor.org/info/rfc2475">	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.22
	<front>	10.xml"/>
	<title>An Architecture for Differentiated Services</title>	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.24
	<author fullname="S. Blake" initials="S." surname="Blake"/>	75.xml"/>
	<author fullname="D. Black" initials="D." surname="Black"/>
	<author fullname="M. Carlson" initials="M." surname="Carlson"/>	</references>
	<author fullname="E. Davies" initials="E." surname="Davies"/>
	<author fullname="Z. Wang" initials="Z." surname="Wang"/>	<section anchor="ack" numbered="false" toc="default">
	<author fullname="W. Weiss" initials="W." surname="Weiss"/>	<name>Acknowledgements</name>
	<date month="December" year="1998"/>	<t>Many thanks to <contact fullname="Spencer Dawkins"/>, <contact
	<abstract>	fullname="Rohit Abhishek"/>, <contact fullname="Jake Holland"/>,
	<t>This document defines an architecture for implementing scalable service diffe	<contact fullname="Kiran Makhijani"/>, <contact fullname="Ali
	rentiation in the Internet. This memo provides information for the Internet comm	Begen"/>, <contact fullname="Cullen Jennings"/>, <contact
	unity.</t>	fullname="Stephan Wenger"/>, <contact fullname="Eric Vyncke"/>,
	</abstract>	<contact fullname="Wesley Eddy"/>, <contact fullname="Paul Kyzivat"/>,
	</front>	<contact fullname="Jim Guichard"/>, <contact fullname="Roman
	<seriesInfo name="RFC" value="2475"/>	Danyliw"/>, <contact fullname="Warren Kumari"/>, and <contact
	<seriesInfo name="DOI" value="10.17487/RFC2475"/>	fullname="Zaheduzzaman Sarker"/> for providing helpful feedback,
	</reference>	suggestions, and comments.</t>
		</section>

		<!-- [rfced] We note inconsistencies in the terms listed below. If no
		objections, we will update to the form on the right (i.e., the lowercase
		form). We see a mix of uppercase and lowercase use, but lowercase seems
		more common. In addition, the lowercase form aligns with usage in several
		other RFCs (e.g., RFC 9556).

		Edge Computing vs. Edge computing vs. edge computing

		Edge device vs. Edge Device vs. edge device

		Edge server vs. edge server

		Edge vs. edge
		-->

		<!-- [rfced] FYI - We added expansions for the following abbreviations
		per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each
		expansion in the document carefully to ensure correctness.

		Software-Defined Networking (SDN)
		Graphics Processing Units (GPUs)
		-->

		<!-- [rfced] Please review the "Inclusive Language" portion of the online
		Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
		and let us know if any changes are needed. Updates of this nature typically
		result in more precise language, which is helpful for readers.

		Note that our script did not flag any words in particular, but this should
		still be reviewed as a best practice.

		In addition, please consider whether "tradition" should be updated for clarity.
		While the NIST website
		<https://www.nist.gov/nist-research-library/nist-technical-series-publications-a
		uthor-instructions#table1>
		indicates that this term is potentially biased, it is also ambiguous.
		"Tradition" is a subjective term, as it is not the same for everyone.
		-->


	</references>
	</back>	</back>
	</rfc>	</rfc>

End of changes. 267 change blocks.
	766 lines changed or deleted	1212 lines changed or added
This html diff was produced by rfcdiff 1.48.