Future of Broadcasting and The Future Internet: 1st IEEE BTS GOLD Workshop 6 / 7 March 2012

School of Engineering and Design
Future of Broadcasting and The Future Internet

1st IEEE BTS GOLD Workshop th / 7th March 2012 6
Professor John Cosmas

Wireless Networks and Communications Research Centre
john.cosmas@brunel.ac.uk
www.brunel.ac.uk/about/acad/sed
Introduction
Motivations Factors constraining broadcasters using Internet Current limitations of Internet Approaches to Future Internet Architecture Research Key Differences between Current and Future Internet Current Future Internet Research Themes Software Defined Networking Information Centric Networking Declarative Networking Research Forums FIA, NEM, FIRE, ONF Conclusions
Motivations
In the long term, it makes more sense to deliver television services and other consumer applications to the home using optical fibre networks rather than using electromagnetic radio networks which are more suited to delivering mobile services. Radio spectrum will be used for Wireless LAN operating in licensed spectrum in areas to access those households of subscribers which are located in remote areas and to which it is too expensive to route optical cable. Radio spectrum is more usefully used for mobile Internet services.
Factors constraining broadcasters using Internet

Broadcast network operators have established that four things must occur before this transition can be commercially attractive:
Sufficient number of households must be connected to broadband optical Internet (the so-called tipping point); Quality of TV services must be at least as good as that provided by the current terrestrial TV networks; There must be an efficient system to incorporate new subscribers and efficiently include these new subscribers to the multicast; TV Services must be delivered as Over The Top (OTT) streaming video content to obviate the need for an Internet service provider as part of the delivery process.
Current limitations of Internet

The principal paradigm of the current Internet architecture is end-to-end communication between hosts. Its limitations include:
Increased Capacity; Ability to choose price/performance; Reliability, Resilience and Availability; Trust; User Connectivity; Networking Flexibility; Quality of Service.
Approaches to Future Internet Architecture Research

Clean Slate approach
the system is redesigned from scratch to offer improved abstractions and/or performance, while providing similar functionality based on new core principles allows us to explore radically new designs, to see if they are viable alternatives to the solution we have now.
Evolutionary approach
the system is evolved from one state to another with incremental improvements. adopts the best ideas from clean slate approach but with clear and incremental path from Current Internet towards the deployment of the Future Internet will interest industry.
Key Differences between Current and Future Internet

Whereas the first generation Internet facilitated the sharing of information (e.g. media streaming, web, email, search engines, interactive applications etc.), the second generation Internet will facilitate the sharing of control in order to manage the provisioning of services through
universal usability (user focus: real-time adaption of form-factors, formats, security, quality, mobility protocols; personalization of user interface, services, interest profiles, interactivity and user inclusion), ubiquitous computing (hardware focus: interoperation of disparate devices), distributed control (software focus: distributed and controlled processing for across networks) which will used to provide solutions for security, mobility, reliability, resilience, availability, problem analysis, networking, protocol flexibility, connectivity, scalability and quality of service.
Current Future Internet Research Themes

Information Centric Networking (ICN) focuses on finding and transmitting information to end users instead of connecting end hosts that exchange information. Software Defined Networking (SDN) refers to a network architecture in which the network control plane is decoupled from the physical topology. Declarative Networking is a programming methodology that enables developers to concisely specify network protocols and services. This can either be realised using a Declarative Language, which is directly compiled to a dataflow framework that executes the specifications or using Distributed Programming combined with Service Description Schemas).
Information Centric Networking

Information Objects with Caching
In Named Data Network (NDN) Project a packet "address" consists of named content, not location (clean slate) A request for an information object (IO), called an interest packet, is routed towards the location in the network where that IO has been published. The routers use Forwarding Information Base (FIB), which is populated by a name-based routing protocol. Interest packet reaches a node that has the requested data and a Data packet is sent back. It traces in reverse the path created by the Interest packet back to the consumer. For any subsequent packet address, the caches of nodes traversed on the way towards the source are checked for copies of the requested IO. As soon as an instance of IO is found (a cached copy or the source IO), it is returned to the requester along the path the request came from. All the nodes along that path cache a copy of the IO in case they receive more requests for it.

Information Objects with Registration of Locators
Current Internet architecture is designed to provide access to specific nodes in the network whereas todays usage is dominated by information dissemination where the information requester does not care about the source location. A namespace is used to name information independent of the storage location. The use of information objects with registration of locators has been proposed principally by NetInf which is part of the 4WARD Project (clean slate). In NetInf IOs are also published into the network and registered with a name resolution service (NRS). The NRS is also used to register network locators that can be used to retrieve data objects that represent the published IOs. When a receiver wants to retrieve an IO the request for the IO is resolved by the NRS into a set of locators. These locators are then used to retrieve a copy of the data object from the best available source(s). It uses multi-level distributed hash tables for performing the name resolution and also the data transfer.
Information Objects with IP Backward Compatibility

In the CONVERGENCE project (evolutionary), its CONET ICN is backward compatible with current IP Internet with co-existing Information Object based addressing and Location Based addressing. A Border Node checks if the content required by the content request packet is available in its cache, if not it performs forward-by-name. If the CONET Sub-System is an IP network, the result of the forward-by-name operation is the IP address of the upstream Border Node, therefore the content request can be sent using this destination IP address. An Internal Node in the path between the two border nodes intercepts the content request, it checks if the requested content is available in its cache, if not it forwards the packet using the IP destination address. A plain IP Router in the path between the two Border Nodes will simply forward the packet looking at the IP destination address. Border nodes act as caches for the Information Centric Network and can handle Information Object Interest packets as well as Location addressed packets. The IO Interest packets are converted into normal Location Based addressed packets for transmission in a conventional router network.

Packet Control
In the 4WARD and SAIL projects (clean slate), the virtualisation system architecture encompasses three basic roles:
a) the infrastructure provider (having the capability to virtualise the physical infrastructure by partitioning them into slices), b) the virtual network provider (making the provisioning of complete end-to-end VNets by putting together slices from the underlying infrastructure), c) the virtual network operator who is operating and managing a VNET.
Such an architecture allows Generic Paths to be established which abstracts away from the implementation of the communication path through the network but allows a generic us of such a construct at application to network interface for the easy creation of application communication.

Publish and Subscribe
PURSUIT project (clean slate), which is the successor to the PSIRP, project defines:
Rendezvous (RV) is used to declare QoS metadata for all communications. Topology Management (TM) - collects the information about the current network states and this is used to determine a suitable delivery graph (route) for the transfer of the respective information and thus for optimization of forwarding paths. Forwarding Function receives link-layer frames via the Communication Elements and depending on the forwarding information in each frame, it forwards them to other network interfaces and/or to the local RV function.
PURSUIT projects publishing and subscribing mechanisms operate at the application

and service layers and lacks the mechanisms to make it backward compatible with current Internet protocols, hence making difficult their implementation to integrate with current Internet.

Publish and Subscribe
In the DONA project (clean slate) each domain or administrative entity will have one logical Resolution Handler (RH). Nodes that are authorized to serve data, register to the resolution infrastructure. IOs are also published into the network by the sources. Once a given content is registered, requests can be routed to it. Resolution handlers have a hierarchical structure and requests are routed by name in a hierarchical fashion. Each RH maintains a registration table that maps a IO name to both a next-hop RH and the distance to the copy (in terms of the number of RH hops, or some other metric). The resolution infrastructure routes requests by name and tries to find a copy or the content closest to the client. In data-oriented operation, IOs are routed back along the same path of the request.
Information Centric Networking Cloud Computing

Nebula project (clean slate) supports a cloud-oriented model of computing Data plane model is deny by default: all parties, including the end user, internet service provider, cloud computing operator, and the application provider, must consent to the path and its behaviour for the path to be used. All of the entities along the path must approve of the entire path; if a path is not approved, packets will not flow. NDP specifies the routing mechanism for the data plane, and NVENT specifies the policy framework for the control plane Service interface (NVENT) allows an application or access provider to request a service and specify the level of availability required. NVENT is responsible for determining packet paths, gathering the approval of all intermediate domains (the PoCs); and learning which packets should be in the path. NDP router wraps the data into NDP packets for the assured path that was obtained from NVENT

Metadata from Services
The ENVISION project (clean slate) resource management system monitors network metrics and applies solutions for optimising the network based on service/application metadata. It allows the exchange of network and application specific information and the activation and invocation of network services, as well as content adaptation services. The links are monitored for changing conditions and content and network services invoked:
Content Adaptation Services: Cross Layer Optimisation, SVC, FEC Multicast Delivery: Setting up and managing multicast Caching: Positioning and querying of content in caching nodes
Software Defined Networking (SDN) OpenFlow
In the current Internet a router or switch, the fast packet forwarding (data path) and the high level routing decisions (control path) occur on the same device. An OpenFlow Switch (clean slate) separates these two functions. The data path portion still resides on the switch, while high-level routing decisions are moved to a separate controller, typically a standard server. The OpenFlow Switch and Controller communicate via the OpenFlow protocol, which defines messages, such as packetreceived, send-packet out, modify-forwarding-table, and get-stats. OpenFlow Switch receives a packet it has never seen before, for which it has no matching flow entries, it sends this packet to the controller. The controller then makes a decision on how to handle this packet. It can drop the packet, or it can add a flow entry directing the switch on how to forward similar packets in the future. OpenFlow allows to define policies to find automatically paths that accomplish certain characteristics, like having higher band width, suffering less latency, reducing the number of hops and reducing the required energy that needs traffic to reach its destination.
john.cosmas@brunel.ac.uk www.brunel.ac.uk/about/acad/sed
Software Defined Networking (SDN) OFELIA
The underlying principle of OpenFlow is to treat traffic as flows and to have the control functionality taken out of the networking equipments to a centrally managed or a distributed OpenFlow controller, while retaining only data plane on the equipment. OFELIA project (clean slate) integrates the packet switch OpenFlow controller integrated with a GMPLS control plane within an overlay model.
GMPLS is based on Generalized Labels. The Generalized Label is a label that can represent either (a) a single fiber in a bundle, (b) a single waveband within fiber, (c) a single wavelength within a waveband (or fiber), or (d) a set of time-slots within a wavelength (or fiber). The Generalized Label can also carry a label that represents a generic MPLS label, a Frame Relay label, or an ATM label.
Declarative Networking
Programming
Network programming (distributed programming APIs), which involves computers working together over a network.
There exists several enabling technologies:
Web Services e.g. HTTP REST (Representational State Transfer), is a method of communication between two electronic devices over a network with software designed to support interoperable machine-to-machine (M2M) interaction. Rather than use complex mechanisms such as CORBA, RPC, SOAP to connect between machines, simple HTTP is used. REST applications use HTTP requests to post data (create/update), read data and delete data. RMI, which provides for remote communication between programs written in the Java programming language; Remote Procedure Call (RPC) for inter-process communication that allows a program to cause a subroutine or procedure to execute in another address space (commonly on another computer on a shared network) without the programmer explicitly coding the details for this remote interaction. Common Object Request Broker Architecture (CORBA) is a standard defined by the Object Management Group (OMG) that enables software components written in multiple computer languages and running on multiple computers to work together (i.e., it supports multiple platforms). SOAP, originally defined as Simple Object Access Protocol, is a protocol for exchanging structured information in the implementation of Web Services in computer networks. It relies on XML for its message format, and usually relies on other Application Layer protocols, most notably Hypertext Transfer Protocol (HTTP) and Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission.
Languages
Declarative programming: is a programming paradigm that expresses the logic of a computation without describing its control flow thus describing what the program should accomplish, rather than how it should accomplish it. P2 (from University of California, Berkeley) is an API for the construction, maintenance, and sharing of declarations in overlay networks. Applications submit to P2 a concise logical description of an overlay network, and P2 executes this to maintain routing data structures, perform resource discovery, and optionally provide forwarding for the overlay. P2 is intended to greatly simplify the process of selecting, implementing, deploying and evolving an overlay network design. Bloom (successor to P2) is a programming language for the cloud and other distributed computing systems. BUD is the first prototype implementation of Bloom. A High level declarative query language consists of a recursive query language (Datalog) complemented with communication and state update.
P2 Architecture
Datalog is a query and rule language for deductive databases that syntactically is a subset (simplified version) of Prolog. OverLog is an implementation of Datalog for overlay networks.
john.cosmas@brunel.ac.uk www.brunel.ac.uk/about/acad/sed
Schemas
ENVISION project considered Dublin Core, MPEG-7, MPEG-21 and TV-Anytime. ENVISION has proposed a metadata model based on some elements from MPEG21 and MPEG 7 standards that satisfy the ENVISION needs, namely: End User, Terminal Capabilities, Content, Network, Service, Session, Peer. This is similar but not the same as DVB-CBMS and OMA-BCAST schemas. The ENVISION metadata storage depends on the nature of the metadata. Several metadata element types, such as the user description metadata, will be stored in local databases or file for privacy and security issues. Some metadata such as the content metadata will be conveyed with the data, others such as the network metadata, should be distributed over the network since it is often requested. Therefore user metadata will be fragmented and distributed stored across the network.
Schemas
PURSUIT declares QoS metadata defined within their project for all communications using rendezvous function. PURSUIT develops service dissemination strategies associated with (parts of) the information structure that is replicated across nearly ubiquitously available storage devices. When a client is interested in a particular piece of information, their request is redirected to one of the existing replicas rather than requiring retrieval from the original publisher.
Future Internet Assembly (FIA)

This is a future Internet portal, which serves as the central forum/hub for European activities and discussions on the future of the Internet and which regularly organises workshops and conferences with a particular emphasis on the future Internet architecture research. This is a very suitable forum for finding latest future Internet architecture research for network equipment manufacturers and operators.
Networked and Electronic Media (NEM)

This is a future Internet portal, which serves as a forum/hub that promotes an innovative European approach to the convergence of media and telecommunication networks towards a Future Media Internet to enhance the lives of European citizens through a richer media experience. This is a very suitable forum to find out about latest research in future Internet architecture and its synergies with the 3D Cloud Gaming and TV content creators, providers and network operators.
Future Internet Research and Experimentation (FIRE)

This is part of the EU ICT work programme that makes available to Internet community experimental facilities for experimentally driven research on the Future Internet This is a good facility to conduct experimental research on the existing future Internet experimental facilities.
Open Networking Foundation (ONF)

This was founded in 2011 by Deutsche Telekom, Facebook, Google, Microsoft, Verizon, and Yahoo. It is a non-profit organization whose goal is to rethink networking and quickly and collaboratively bring to market standards and solutions. ONF will accelerate the delivery and use of SDN standards and foster a vibrant market of products, services, applications, customers, and users.
Conclusions
The premise of this research is that ultimately the delivery of TV to home users will be delivered by the fixed broadband optical Internet. The current Internet has limitations that is stopping this occurring There is much research being done on the Future Internet that has been introduced in this presentation that may change this and is broadly classified into: Information Centric Networking; Software Defined Networking; Declarative Networking. Most of this research has adopted a clean slate approach with the one evolutionary approach proposing an inelegant solution. It is important that the broadcasting industry participates in this research to influence its direction towards solutions that are favourable to the broadcasting industry.

Future of Broadcasting and The Future Internet: 1st IEEE BTS GOLD Workshop 6 / 7 March 2012

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Future of Broadcasting and The Future Internet: 1st IEEE BTS GOLD Workshop 6 / 7 March 2012

Enviado por

Direitos autorais:

Formatos disponíveis

School of Engineering and Design