ISO/IEC TR 29181-6:2013

TECHNICAL ISO/IEC
REPORT TR
29181-6
First edition
2013-04-15
Information technology — Future
Network — Problem statement and
requirements —
Part 6:
Media transport
Technologies de l'information — Réseaux du futur — Énoncé du
problème et exigences —
Partie 6: Transport des médias

Reference number
©
ISO/IEC 2013
©  ISO/IEC 2013
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any
means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2013 – All rights reserved

Contents Page
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols (and abbreviated terms) . 4
5 Overview . 5
5.1 Networks evolving to support of media . 5
5.2 User demand for media-based services . 6
6 General concept of FN media transport . 7
6.1 Support of connection-oriented and connection-less model . 8
6.2 Classification of basic services and composite service . 8
6.3 Deployment of MANE (Media Aware Network Element) in the network . 9
6.4 Content delivery networking . 10
7 Problem statement . 10
7.1 Protocol overhead and useless information . 10
7.2 Limitation of Layered Coding . 11
7.3 No media-awareness . 11
7.4 No information exchange between protocol stacks (layered network stack) . 11
7.5 Support for new types of media . 11
7.6 Merging of current solutions in supporting media transport . 12
7.7 Contents are left to the end-system . 12
8 Requirements for media transport in Future Network . 12
8.1 General requirements . 12
8.2 Requirements related to functionality of MANE . 14
8.3 Requirements related to media delivery and network . 14
Annex A (informative) Use cases for media transport . 16
A.1 HD Multiparty videoconference . 16
A.1.1 Current Solution . 16
A.1.2 Future Network Solution . 16
A.2 Web browsing . 17
A.2.1 Current Solution . 17
A.2.2 Future Network Solution . 18
A.3 Media Aware Network Element . 18
A.3.1 Content-aware based congestion control . 18
A.3.2 Decision-making . 19
A.3.3 Seamless mobility . 20
Annex B (informative) Related standardization and research activities . 22
B.1 MMT (MPEG Media Transport) . 22
B.2 SMART of Ambient Network . 23
B.3 MEDIEVAL (MultimEDia transport for mobIlE Video AppLications) . 24
B.4 CDNi (Content Delivery Network Interconnection) . 25
B.5 ALICANTE architecture . 26
Bibliography . 29

© ISO/IEC 2013 – All rights reserved iii

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
In exceptional circumstances, when the joint technical committee has collected data of a different kind from
that which is normally published as an International Standard (“state of the art”, for example), it may decide to
publish a Technical Report. A Technical Report is entirely informative in nature and shall be subject to review
every five years in the same manner as an International Standard.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC TR 29181-6 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications and information exchange between systems.
ISO/IEC TR 29181 consists of the following parts, under the general title Information technology — Future
Network — Problem statement and requirements:
 Part 1: Overall aspects
 Part 3: Switching and routing
 Part 4: Mobility
 Part 6: Media transport
 Part 7: Service composition
The following parts are under preparation:
 Part 2: Naming and addressing
 Part 5: Security
iv © ISO/IEC 2013 – All rights reserved

Introduction
ISO/IEC TR 29181-1 describes the definition, general concept, problems and requirements for the Future
Network (FN). The other parts of ISO/IEC TR 29181 provide details of various components of the technology.
This part of ISO/IEC TR 29181 identifies problem of the media transport in the IP-based networks and
examines the requirements for the transport of media data over the Future Network.

© ISO/IEC 2013 – All rights reserved v

TECHNICAL REPORT ISO/IEC TR 29181-6:2013(E)

Information technology — Future Network — Problem
statement and requirements —
Part 6:
Media transport
1 Scope
This part of ISO/IEC TR 29181 describes the problem statement and requirements for the Future Network in
the perspective of Media Transport. This part of ISO/IEC TR 29181 specifies:
a) detailed description of the media transport requirements in the Future Network;
b) identification and definition of services, basic and media services, which will fit the requirements for
communications over heterogeneous environments supporting various user preferences, for any kind of
media content, either time-dependent or time-independent;
c) requirements and functionalities of Media Aware Network Elements, which are intended to be nodes in
the network to provide seamless media experiences to users.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC TR 29181-1, Information technology — Future Network — Problem statement and requirements —
Part 1: Overall aspects
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC TR 29181-1 and the following
apply.
3.1
data
sequence of octets which is conveyed across the network as a single unit
[SOURCE: ISO/IEC TR 29181-3, 3.1]
3.2
media
sequence of bits in a defined format which encodes physical entities such as images, sounds, and text.
3.3
time-independent media
media where the semantic of the content does not depend upon a presentation according to the time domain
© ISO/IEC 2013 – All rights reserved 1

EXAMPLE 1 text
EXAMPLE 2 still image
3.4
time-dependent media
media where there exists a temporal relation amongst the media units
EXAMPLE 1 audio
EXAMPLE 2 video
3.5
content
media media that is carried in the payload of datagrams sent over the network
3.6
static content
time-independent media that is carried in the payload of datagrams sent over the network
3.7
streamed content
time-dependent media that is carried in the payload of datagrams sent over the network but does not have
requirements for latency
EXAMPLE 1 MP3 files
EXAMPLE 2 Video-on-Demand
3.8
live content
time-dependent media that is carried in the payload of datagrams sent over the network and has requirements
for latency.
EXAMPLE 1 telephone conversation
EXAMPLE 2 video conference
3.9
encapsulation
additional octets or other symbols associated with a data unit which serve to delimit it or to identify aspects of
the service it should receive
[SOURCE: ISO/IEC TR 29181-3, 2.15]
3.10
container
encapsulation structure containing a payload, either data units or content, and the header composed by two
parts, what refers to the payload and to the underlying network
NOTE Container has attributes as header fields, which some are related to particular services, and others are
general and specific for a sort of communication.
3.11
context
set of data or information that completely describes a particular communication environment at a particular
point in time
[SOURCE: ISO 16484-5:2007 (Identifier: CDB-00119069-001)]
2 © ISO/IEC 2013 – All rights reserved

3.12
context-awareness
ability of a network to be aware of the context and react accordingly in order to adapt either itself or the data
conveyed over
3.13
modular paradigm
paradigm where complex functions are composed by well-known and deterministic basic functions
NOTE In network realm, protocols are breaking down into its fundamental (also called atomic) functions, such as
sequencing, cyclic redundant coding, addressing, and so on, which combined results into complex functions (or protocols).
3.14
MANE (Media Aware Network Element)
content and context aware network element capable of processing media content passing through to
accommodate a given content or service according to the context
NOTE This element may handle all attributes of containers taking into account the content type and properties,
networking properties and status, and other environmental and conditional properties that may have effect in routing of the
contents and services.
3.15
quality of service (QoS)
set of qualities related to the collective behaviour of one or more objects
[SOURCE: ITU-T Rec. X.902 │ ISO/IEC 10746-2]
NOTE QoS is usually defined regarding to three parameters: bandwidth, delay and error. In conversational
communications, bandwidth consumption is related to the chosen technology (although the lower one is desired), the
delay has to be bounded to assure conversational interactivity among participants, and should be provided a high error
resilience to assure a good data delivery in front of any change on the network.
3.16
quality of experience (QoE)
set of subjective and/or objective qualities related to user perception about consumed media content
NOTE QoE is usually referred to how the user perceives the consumed content. QoE is more related to subjective
quality estimation rather than objective measurements, although they can be related by different mapping schemes.
3.17
connection-oriented
communication between peer protocol entities by means of a connection or association established by an
underlying layer
[SOURCE: ISO/IEC 11582:2002 (Identifier: CDB-00009275-001)]
3.18
connectionless
communication between peer protocol entities by means of an unacknowledged, unidirectional transport
mechanism provided by an underlying layer
[SOURCE: ISO/IEC 11582:2002 (Identifier: CDB-00009276-001)]
3.19
layer coding (LC)
coding technique in which the video stream is split into several hierarchical layers consisting of base layer and
one or more enhancement layers
3.20
multiple description coding (MDC)
coding technique in which a single media stream is fragmented into multiple substreams which can be
delivered over the network in different paths
© ISO/IEC 2013 – All rights reserved 3

4 Symbols (and abbreviated terms)
3D Three Dimensional
AIMD Additive Increase / Multiplicative Decrease
CABCC Content-Aware Based Congestion Control
CLD Cross-layer design
CLO Cross-layer Optimization
FEC Forward Error Correction
HD High Definition
HTTP Hypertext Transfer Protocol
LC Layered Coding
MDC Multimedia Description Coding
MEDIEVAL MultimEDia transport for mobIlE Video AppLications
MMT MPEG Media Transport
MPEG Moving Picture Experts Group
MPEG-TS MPEG-Transport Stream
OSI Open Systems Interconnection
P2P Peer to Peer
RTCP Real-Time Control Protocol
RTP Real-Time Protocol
SMART Smart Multimedia Routing and Transport
SMS Short Messages Services
STREP Small or medium-scale focused research project
SVC Scalable Video Coding
TCP Transmission Control Protocol
TCP/IP Transmission Control Protocol/Internet Protocol
UDP User Datagram Protocoll
UHD Ultra-High definition
VoIP Voice over IP
WWW World Wide Web
4 © ISO/IEC 2013 – All rights reserved

5 Overview
5.1 Networks evolving to support of media
During the last few decades, the various research communities have carried out large research activities in
networking and grid e-Infrastructures, which have concluded with the needs of new types of networks and
distributed computing models of communication. In the mid-80s, the research activity was focused on the
Networking Layer (the lower layers of the stack) in order to improve overall quality of the end-to-end
transmission. In the mid-90s, the telecom boom has arrived and started advertising that networks were ready
for the end user. The trend of collaborative environments appeared, where networks were used only as a
transport tool, and it was necessary to work on distributed solutions. The Supercomputing or more recently the
P2P (peer-to-peer) were, and still are, the research lines for searching these solutions, in the layer called
GRID or distributed computing.
Today, the research is focused on the two emerging layers. The first layer is the Scientific Data Layer, where
all the data to be processed and transported will be collected. Scientific Data Layer deploys data repositories
for the scientific community and future generations of scientist supporting. The data repositories are
implemented in a coordinated way to be used as digital libraries, archives, data storage, access to information
and the necessary pooling of resources [6]. The second layer is a new Multimedia Layer, specifically focused
on the convergence of advanced graphics, media and live videoconferencing, which enables any kind of
multimedia data exchange between users on a computer network. Multimedia Layer can communicate directly
with the Scientific Layer, GRID Layer, or Network Layer. It is dependent on the multimedia application and/or
the type of network which it runs on.

Figure 1 — Layers of research activity
Current multimedia research activities have focused on how to adapt the diverse characteristics of media to
the running network architecture by defining middle layer that provides particular features for this sort of traffic.
RTP/RTCP, RTP for uncompressed video, MPEG-TS, and so on, are well-known examples of these mid
layers designed for this reason, to adapt the media content to the TCP/IP network. New middle layers are in
continuous evolution to adapt themselves basically to users and underlying network requirements. All these
middle layers are designed to adapt the media data to the Internet, over the classical stack of communications
designed in the 70s to transmit computer data from end-to-end user.
The middle layers or protocols are presented in the Figure 2. Starting from the left side is the the OSI model,
the TCP/IP stack, and the protocols adopted for the media transport.
© ISO/IEC 2013 – All rights reserved 5

Figure 2 — Current middle layers or protocols used for media
5.2 User demand for media-based services
Few years ago, after the revolution of the WWW and the spreading of the Internet to the end user, the highest
percentage of the traffic in the backbone was based on raw data or time-independent content. Nowadays, this
trend has changed towards the exchange of time-dependent media content, either streamed or live, between
users themselves or between content providers and users. This change to the traffic types has affected the
current Internet framework, where intelligence is in the edges not in the core of the network, communication
model changed from the server client model to the P2P model, as well as to the types of contents transmitted.
In fact, Internet is already a media network based on P2P media traffic and time-dependent content
applications such as VoD (Video on Demand), videostreaming, and broadcasting. It is in this Internet where a
little part of users generates the major part of the global IP traffic. In this regard, in 2009, media content, from
P2P and video services, represented the 80 % and 90 % of the global Internet traffic, respectively. Due to the
convergence of television, video, graphics, and audio, it is expected that video traffic will continuously
increase as with the increasing demand of media content such as HD, 3D, face-to-face video conferencing,
video gaming, etc.
Content Delivery Network is an example reflecting this demand, because network operators are starting to
set-up customized infrastructures, composed by clusters of VoD servers and high capacity network resources,
to enable a network to feed and deliver streamed and live media content to end users in a faster and more
reliable way. The CDN is an associated hybrid-networking infrastructure that requires an enormous amount of
effort in realization and fine-tuning to enable high quality media stream to be delivered along the network.
6 © ISO/IEC 2013 – All rights reserved

Figure 3 — IP network forecast according to CISCO Visual Networking Index [4]
It must be remembered that current network started as a computer networking revolution, and now the
Internet is evolving as a user driven network, based on various types of audio-visual media content. So, the
change in our traditional paradigm of an information and communication network which relies on computers
and telecommunications is clearly moving towards a new media network which shares all kind of cultural
knowledge, science, technology, arts, and games.
Users are becoming into active players in the media-based networks. An evidence of this is the growth of the
contents generated by the users. Their interest in media contents is growing amazingly, and it is expected to
continuously increase in the near future. That means the people are the new driving forces in the design of the
Future Network and will introduce new requirements and demand for new services, applications, and
functionalities.
So, the Future Network must start based on this reality, where users are continuously consuming various
types of media (music, TV series, etc.), both time-dependent and time-independent, and beginning to offer
self-generated videos to the network. People at home will start creating high quality contents, where the user
can interact with the contents and, even, generate and modify it in a collaborative manner. The problem is that
the current Internet is not ready for this convergence between the real media world and networks and future
demands.
6 General concept of FN media transport
The media transport in the Future Network is based on the premises of simplicity and flexibility (evolvable) and
is focused on high quality multimedia communications.
This document introduces general concept of the Future Network based on the actual mechanisms and
protocols used to manipulate the multimedia data. To face this challenge, service-oriented architectures offer
a flexible approach, which enables to define services and compose multiple services in run-time or design-
time, to fit the requirements for particular media communications over heterogeneous context, for any kind of
media content, either time-dependent or time-independent. Future Network will go further than the application
© ISO/IEC 2013 – All rights reserved 7

layer and go down to the communication protocols themselves, choosing in a dynamic fashion any kind of
basic services (e.g.: acknowledgement, sequence number, flow identification, congestion windows, etc.) and
media services (e.g.: content adaptation, scalability, transcoding, etc.) that are needed in a particular
communication, according to the parties capabilities and the media transport requirements. Thus, this
document describes a general concept of the media transport, as the media service composer element,
forming a common container with just the metadata needed, to compose and dynamically adapt specific
media services for a given communication for every sort of contents.

Figure 4 — Container
6.1 Support of connection-oriented and connection-less model
The model is designed as a service-oriented approach for a flow-oriented context-aware network working
mainly in a connection-oriented mode, although connection-less is allowed for particular sort of services,
where communications are composed in situ (using reusable components) according to the needs and
requirements of the consumed service.
The media transport in the future network should be able to work in connection-oriented and connection-less
fashion in datagram transmission, depending on the working environment. In Internet, most data are conveyed
by using TCP with its strict flow and congestion control. Even media applications using UDP transport protocol
relay either on RTP/RTCP, as transport / control protocols, or with a particular control scheme at application
level. So, Future Network is designed to work with both modes, mainly as a connection-oriented but also as a
connectionless mode accordingly to the communication characteristics. The connectionless mode does not
regard upon the on-line status of the peer on the other side, such as short messages services (SMS and
tweets). Broadcasting services may be set as connection-oriented communications following a multicast
pattern across the network, or connection-less in simplex communications such as traditional radio / TV.
6.2 Classification of basic services and composite service
Services are classified into basic (atomic), and composite services. Basic (atomic) services have individual
functions commonly used in networking protocols, e.g. acknowledgments, sequence numbers, flow control,
etc. These are well-defined and self-contained functions, used to deliver data in a self-adaptable, self-
configurable, and context-aware manner. Concretely, media services are those atomic can operate with
multimedia mechanisms (such as transcoding, VBCC, protection, etc.) that belong to the content realm which
may be executed by the same peer or by different peer to perform task in order to provide a higher level
media service. Composite services are the result of combining basic services. Each composite service or
application implies consuming different basic services or other composite services which may have possible
dependences between them. Service can involve one or more nodes, depending on the complexity of the
service. As a result, a container for each particular communication is generated.
Most error resilience techniques applied on real-time communications are FEC (Forward Error Correction),
which adds redundant information increasing the data rate. The application of interleaving mechanisms
8 © ISO/IEC 2013 – All rights reserved

increases the probability of recovering lost multimedia data in the presence of bursty losses across the
network. These techniques can be applied according the data conveyed as a modular services in an atomic
architecture.
Composite Services
ACK
SN
Basic Services
Adaptation
TS
ACK
SN
… Media Services
Adaptation
SN: Sequence number Scalability
TS: Timestamp
ACK: Acknowledment
Figure 5 — Basic services and composite services
In order to obtain the desired behaviour, functionality and QoS constrains, communications are established
concatenating atomic services into a workflow for consuming a certain composite services. They are allocated
amongst the involved nodes, as required by conditions of temporal context and service requirements. In this
way, all functions are used only when and where they are required, so that there is no functional overlapping
or usage of counterproductive functions. Thus, atomic services can be executed in a per-hop, per-section
(between two non-adjacent nodes), per-AS (between Autonomous Systems) and/or end-to-end basis (section
ranging the entire route). Nodes on the network are intended to be Media Aware Network Elements, which
react either by commands from the control plane or directly over the content or the bit-stream according to
some rules depending on the content itself (i.e., Scalable Video Content or Multiple Description Video Coding).
6.3 Deployment of MANE (Media Aware Network Element) in the network
MANE (Media Aware Network Element) is a content and context aware network element capable of
processing media contents to accommodate a given contents or services according to the context. This
element may handle all attributes of containers taking into account the content type and properties, networking
properties and status, and other environmental and conditional properties that may have effect in routing of
the contents and services. It is an edge elements of any network, included Autonomous System (AS),
operated by a single manager, which perform tasks regarding to the media content such as content adaptation,
scalability decision-making, backward signalling, media mobility, content based congestion control, etc. These
tasks can be performed inside a network, such as in a LAN, or amongst Autonomous Systems inside the core
network.
© ISO/IEC 2013 – All rights reserved 9

Figure 6 — MANEs in the interconnect networks
The capabilities of MANE include caching, adaptation, synchronization, and media aware routing in the
network. MANE also needs to deal with heterogeneous network, user capabilities and preference that may
change in time. The multiple MANEs interacts to provide the most adequate various media delivery
accordingly to the recognized contexts. MANEs may configure media-specific routing information to provide
media delivery. However, the routing information are configured by the FN service composition.
6.4 Content delivery networking
Content delivery networking is an approach that allows user to focus on the required data instead of having to
search for the physical location where data is to be retrieved from. Some of the features of the content
delivery networking include content caching, content searching, content routing, content delivery, and content
retrieval. In media transport aspect, future network should be aware of contents and content receiver to
support optimized content delivery. The FN should be able to provide efficient content routing and content
delivery. For content routing, FN should configure efficient path to deliver contents. A mechanism is needed to
merge and synchronize multiple incoming contents over the network. For content delivery, FN should delivers
contents to the receiver by by unicast or multicast using channels managed by content aware router. Future
network should deal with other issues related to content networking such as performance, resilience, security,
and privacy.
7 Problem statement
This clause lists problems of media transport in the current network.
7.1 Protocol overhead and useless information
Current network architecture design is based on a hierarchical layered model like OSI or TCP/IP stacks. In
these models, networking functions and protocols are grouped in layers, according to a common objective and
scope. Thus, each layer performs different networking tasks, restricting inter-layer communication to
immediately adjacent layers. In theory, each layer is in charge of a group of functions, but in practice functions
overlap at different layers, adding protocol overhead and blurring the layered structure of the protocol stacks.
To send an RTP packet it is needed 20 bytes of the IPv4 header, 8 bytes of UDP, and 20 bytes more of RTP.
So, 48 bytes is needed for headers assuming that there is no additional information (optional fields). For IPv6
(40 bytes) the RTP headers add up to 68 bytes, and a TCP/IPv6 acknowledgement packet is 60 bytes, though
it only carries about 4 bytes of useful information. It must be remembered that TCP/IP network was designed
10 © ISO/IEC 2013 – All rights reserved

to work over any sort of network, and for any sort of application. The main operation of TCP/IP is to transfer
data from end to end, by two different ways, connection oriented (TCP) or connectionless (UDP).
As example of useless fields on the current stack, when MPEG-TS (well self-structured media format with
several information used to “transport” media stream) is sent over the network, a lot of headers and additional
information about the MPEG stream are added. Some fields are already present in the RTP header,
increasing the amount of duplicated information, resulting in a waste of time and resources. This is an
important hint that these protocols need a hard redesign or be replaced. Historically, new features have been
added by means of inserting extra information in higher layers, instead of squeezing the capacities and
features of the existing ones.
7.2 Limitation of Layered Coding
Layered Coding (LC) is based on the idea of splitting a video stream into several hierarchical layers consisting
of a base layer, with minimal features, and enhancement layers. The more layers received the more quality
achieved, as a receiver-driven adaptation system. The main drawbacks of this coding are basically two folded:
(1) real implementations of LC, such as wavelet-based solutions (DWT, e.g.: JPEG2000 and Dirac Pro) and
SVC (Scalable Video Coding), require enormous computational complexity and entail high delay, and (2) its
weakness in terms of reliability in error prone environments.
7.3 No media-awareness
Current common congestion controls are focused on adapting the data rate at bit level according to the
network available resources, instead of on adapting the content (semantic approach). For example, windows-
based congestion control is based on a transmission window, such as TCP that limits the amount of data to be
transmitted usually following the AIMD (Additive Increase / Multiplicative Decrease) algorithm according to the
network status. Other congestion control approaches closer to the multimedia world, such as rate-based,
media-aware rate control and receiver-based mechanism, act over the sending data rate in a smoother way
than the strict data based congestion controls. However, these methods also treat the video flow as a bit
stream adapted to the network conditions.
Future network should be focused on the experience of the user, enabling a control according to the media
content conveyed instead of the network status. As aforementioned, a bit-stream oriented congestion control
is used for time-independent media where a reliable and fast communication is pursued. On the other hand,
for time-dependent media solutions based on content adaptation are basically done over semantic content
parameters, instead of over the bit stream. Both strategies act over the output data rate, increasing or
decreasing the amount of bits issued according to the network congestion, but taking care of different parts of
the bit-stream. As an example, if the content is a video stream (time-dependent media), according to the
variable conditions of the network and taking into account the nature of the data conveyed, the output data
rate adaptation is directly related to the adaptation in real time of the video source parameters, such as either
the resolution, the frame rate or the codec, instead of directly decreasing the data rate.
7.4 No information exchange between protocol stacks (layered network stack)
The Internet does not have any collaboration between different layers. The OSI reference model has designed
layers as separate entities and abstract them by assigning specific roles and requirements to each layers.
Currently, Internet is used in variety of devices including wireless and cellular devices and in variety of
application including real-time multimedia videoconferences, VoIP, and various other types of multimedia
streaming services. These trends has caused the network to face new problems which includes, adaptability
to dynamic changes of the network and traffic conditions, increase in number of connectivity, high effective
capacity utilization, low processing overhead within the network and end-systems. However, these new
requirements are difficult to handle by the IP-based network.
7.5 Support for new types of media
In the near future, the upcoming media types will be 3D contents, UHD (Ultra-High Definition), hologram. New
media types will need the support of high transmission rates, efficiency, and flexibility that is difficult to be
supported by the current network and current media systems. Currently 3D contents as well as 3D devices are
© ISO/IEC 2013 – All rights reserved 11

delivered to the market places which are growing to interactive 3D contents such as 3D gaming. The UHD
enables applications and services such as telemedicine and super high-vision cinema, and super high-vision
theater. UHD contents needs high transmission rate which may cause problem when delivered in the current
unicast-based transport mechanisms. Different approach such as multipath-based transport mechanism is
needed to support such high quality contents [19].
7.6 Merging of current solutions in supporting media transport
Many research in the past for enhancing media transport was dedicated to defining efficient caching
architecture, techniques of media adaptation, and multicast service support, separately. An independent
approach for finding optimal solution for media transport solves only one specific problem [16]. In providing FN
media transport, solutions to the three approaches should be merged and dealt with altogether to find most
efficient solution in supporting media transport. Efficient caching architecture should be applied to MANE,
efficient media adaptation should be applied to MANE and end-devices, and FN should provide efficient
multicast services.
7.7 Contents are left to the end-system
Internet was designed to support host-to-host applications such as telnet and ftp in which the networking
target is the address of the host. However, Internet is used more and more in applications where the target is
the contents rather than the host. This trend has motivated content-oriented networking studies (e.g. DONA,
CCNx). These technologies did not change the functionality of Internet. Instead they have adapted the use of
a special server which is a host that acts as a network element to provide content based networking. However,
the Future Network should be aware of the content and its characteristics to provided efficient content delivery.
8 Requirements for media transport in Future Network
8.1 General requirements
REQ.FN-MT-101 FN media transport framework should support any types of media contents including
current and future types of media ranging from very low to very high data rates and requiring different level of
QoS/QoE, and various types of communications such point-to-point, point-to-multipoint, and multipoint-to-
multipoint.
NOTE Various types of content will appear in the future. Some example would be Ultra HD content, 3D contents, etc.
These types of contents require high data rates in the network and meticulous processing capability in the media devices.
REQ.FN-MT-102 FN media transport framework should support wide range of devices able to consume /
generate media content (i.e.: smartphones and smart TVs) and provide suitable media transport service.
NOTE The media devices include media producing device, media consuming device, media storage device, MANE,
or any media type of devices that is participating in the media transport.
REQ.FN-MT-103 FN media transport framework should support identification of media content, media
devices, and user preferences.
NOTE 1 The consuming device requests for a particular media contents to the media-based networks. The information
of the actual sender(s) or media contents processing procedures is irrelevant to the consuming device. The consuming
device should be able to identify the media contents.
NOTE 2 In certain occasion, the consuming device may needs to identify the servicing media devices to get the
desired service. However, the identification of the media devices does not have to be based on the physical location.
REQ.FN-MT-104 FN media transport framework should support suitable delivery, in terms of delay (tight)
and / or reliability (losses), of data and content (time-independent media objects and time dependent media
objects).
12 © ISO/IEC 2013 – All rights reserved

NOTE 1 The time-independent media object is a type of content that does not depend upon a presentation according
to the time-domain. Such example would be text, image, etc.
NOTE 2 The time-dependent media object is a type of content that has temporal relation amongst the media unit. Such
example would be multimedia video stream, continuous media.
REQ.FN-MT-105 FN media transport framework should be able to exchange information with other
modules by incorporating QoS/QoE related information from different module (i.e., network module,
application module, etc.).
NOTE Inter-module information exchange provides dynamic feedback of the QoS/QoE information across different
modules to provide adaptive setting of service control.
REQ.FN-MT-106 FN media transport framework should support content adaptation through techniques
such as layered coding (LC) and multiple description coding (MDC), among others.
NOTE 1 LC is a coding feature that is used in SVC, in which the video stream is split into several hierarchical layers
consisting of base layer and one or more enhancement layers.
NOTE 2 MDC is a coding technique that fragments a single media stream in multiple substreams which can be
delivered over the network in different paths.
REQ.FN-MT-107 FN media transport framework should be able to generate either in run-time or design-
time an adaptive and tailored container for each communication according to both content and network
requirements.
NOTE Replication of functions along the network stack is a feature of current internet that has to be wiped out in the
FN. Just use what it is really needed in one communication. Nevertheless, as FN is being set-up, just a bunch of well-
predefined containers shall be probably used all the time becomi
...