DOCSLIB.ORG

Arubaos 8: Understanding Aruba Airgroup Principles

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Arubaos 8: Understanding Aruba Airgroup Principles ArubaOS 8: Understanding Aruba AirGroup Principles Herman Robers, EMEA Security CSE October 2019 #ArubaAirheads Agenda • AirGroup Basics • Centralized vs Distributed • Best Practices • How to configure and verify #ArubaAirheads 2 From the End User perspective #ArubaAirheads 3 From the End User perspective Display Print Listen Control #ArubaAirheads 4 (1) Discovery & Communication [mDNS Query] – Step 1: Discovery. mDNS (5353) or SSDP (1900) is used to discover services offered #ArubaAirheads 5 (2) Discovery & Communication [mDNS unicast response] #ArubaAirheads 6 (1) Discovery & Communication [mDNS Query] – Step 1: Discovery. mDNS (5353) or SSDP (1900) is used to discover services offered #ArubaAirheads 7 (2) Discovery & Communication [mDNS unicast response] #ArubaAirheads 8 (1) Discovery & Communication [SSDP Query] – Step 1: Discovery. mDNS (5353) or SSDP (1900) is used to discover services offered #ArubaAirheads 9 (2) Discovery & Communication [SSDP Response] #ArubaAirheads 10 (3) Discovery & Communication [client -> server unicast] Direct communication client to printer/speaker/tv #ArubaAirheads 11 Designed for home use – used in Enterprise –Designed for consumer/home use: Assumes single L2 domain and open communication. –Challenges when used in the Enterprise: - The (multicast) discovery does not cross L2 boundaries / subnets - If it would work across subnets, scale and usability is an issue: - Large lists are unusable to find your local resource - Lot of airtime used for the multicast discovery in larger subnets - Who is allowed to use services? - Communication across the subnet possible? #ArubaAirheads 12 (3) Discovery & Communication [client -> server unicast] Direct communication client to printer AirGroup will just take care of the Discovery. Make sure the unicast traffic is possible! - Inter-user traffic (SSID) - Inter-VLAN traffic (Firewall, guests-VLAN?) - Role based access firewall rules #ArubaAirheads 13 AirGroup Overview • Enterprise class Zero-Configuration-Networking for Bonjour & DLNA services, and SSDP • Mobility Master (Centralized mode) / Mobility Controller (Distributed mode) / Instant AP terminates mDNS/SSDP multicast messages • Unicast responses to queries • Context-awareness of services across network • Supported in tunnel and decrypt-tunnel forwarding modes • Supports both wired and wireless devices • ClearPass Policy Manager for device (self) registration & sharing policies #ArubaAirheads 14 AirGroup Support – Aruba Instant (6.x/8.x) – Mobility Master-Managed Device (8.x) Centralized mode (AirGroup runs on MM) Distributed mode (AirGroup runs on MD) – Master Controller Mode (6.x/8.x) – Stand-alone Controller (6.x/8.x) #ArubaAirheads 15 FYI: Bonjour, mDNS, DLNA, SSDP, UPnP Apple Bonjour (marketing name) is used by most Apple Devices for service discovery and uses mDNS (udp 5353 multicast). DLNA (Digital Living Network Alliance, marketing name) uses SSDP (Simple Service Discovery Protocol, udp 1900 multicast) for discovery. SSDP was incorporated into the UPnP protocol stack. For this presentation: Bonjour = mDNS and DLNA = SSDP #ArubaAirheads 16 Exception: Bluetooth Discovery and AirGroup for AppleTV Where AirGroup was equivalent to AppleTV Airplay, it isn’t anymore: – Bluetooth Discovery: Apple device to discover an Apple TV that is within the Bluetooth range. –AirGroup supports only mDNS-based device discovery and does not support Bluetooth based device discovery mechanism. –Bluetooth cannot be disabled – Ad-hoc WiFi network: Apple TV Generation 3+ when connected wirelessly will form an ad-hoc network between the client and the Apple TV, which will bypass the existing WiFi network. –Ad-hoc can be disabled under the management profile for organized-owed Apple TV’s (AirPlay Security) #ArubaAirheads 17 What does AirGroup do? Periodic query for services Block mDNS/SSDP Build server table Build user table Proxy services (filtered, unicast) 1) Block multicast mDNS/SSDP between clients on the network 2) Based on the blocked packets, build a table of clients 3) AP/MD Actively query available services, build table of services 4) Proxy services to clients (even across subnets, across wired/wireless) 5) Filter service discovery based on Role/VLAN/ClearPass #ArubaAirheads 18 AirGroup in more detail #ArubaAirheads 19 (1) Discovery & Communication [mDNS Query] 192.168.31.10 = Mobility Master #ArubaAirheads 20 Centralized vs Distributed – Centralized Distributed • MM contains all AirGroup info • Operates the same as in 6.x • MM sends RADIUS requests to ClearPass • Roaming can be an issue between MDs when configured • Same scaling numbers as 6.x • Uses Openflow to get mDNS/Bonjour/SSDP/DNLA messages from the MD to the MM • All config must be placed in /md • Wired devices and duplication #ArubaAirheads 21 Best Practices – Centralized Distributed • Only enable services that are going to be used • Useful when there are many small sites • 2 or less controllers • Disable openflow on roles that do not use mDNS • Bandwidth / latency constraints. • Block mDNS in the roles that do not need • One MM for world in US and sites in Asia airgroup with low bandwidth/high latency • Limit servers to locations • No not use limiters such as AP Group. • Check messaging rates • Auto associate ap-name doesn’t apply for wired devices • If you want to apply policies to wired devices, use MAC address based policy with ClearPass or CLI • Auto associate for wireless is recommended for optimum performance #ArubaAirheads 22 AOS 8 – AirGroup working reference: Wired device using Dynamic AOS 8 version Wired device Without Dynamic Segmentation Segmentation 8.2.1.x Yes No (Note 1) 8.3.0.x Yes No (Note 1) 8.4.0.x Yes Yes Note 1: Due to an issue with an OpenFlow bug, the AirGroup device is not being picked up through the tunnel (Bug # 176930) #ArubaAirheads 23 Scalability AOS 8 - Centralized – AirGroup can scale to support up to 100,000 devices in which up to 17,000 servers can exist. – In centralized mode, on Mobility Master, the mDNS packet limit is 1750 pps. In mixed mode, the mDNS packet limit of 1750 pps applies only for centralized mode. #ArubaAirheads 24 Scalability limits are based on: Memory Utilization • Memory utilization is affected by; • AirGroup servers and Users, • Total number of AirGroup servers and users cannot exceed the limit defined by the top end stand- alone controller CPU Utilization • CPU utilization is measured by the rate at which a stand-alone controller receives mDNS packets per second. • The rate of mDNS packets per second depends on the number of AirGroup servers, users, and number of applications installed on these devices. • When the number of mDNS packets per second exceeds the limit, AirGroup drops the additional packets (Centralized – dropped at MM, in Distributed at limit of MC’s (Mobility Controllers)) #ArubaAirheads 25 Scalability Limit in Stand-alone or Distributed Controller AOS 8 AOS 8.x AOS 8.x Stand-alone Controller Model Servers Users 7240 10000 20000 7220 7000 15000 7210 5000 10000 7205 2000 6000 7030 1000 3000 7024 600 1400 7010 500 1500 7005 300 700 Note: This data is taken from the 8.2.1.0 and 8.3.0.0 User Guides #ArubaAirheads 26 mDNS Packet Limits in Stand-alone Controller or Distributed Mode Stand-alone Controller Model or Distributed Mode mDNS packets per second (pps) Mobility Master – in centralized Mode (10k) 1750 7280 150 (Note 1) 7240 150 7220 90 7210 90 7205 60 7030 75 7024 75 7010 45 7005 45 Note 1: In the 8.3.0.x User Guide there is an error showing 7280 supporting 1750 PPS. Note 2: This data is taken from the 8.2.1.0 and 8.3.0.0 User Guides Note 3: Command to determine the number of mDNS packets received per second by a managed device: show airgroup internal-state statistics #ArubaAirheads 27 Centralized mode: Open Flow Packet Forwarding – After Open Flow connection has been established between the Mobility Master and the managed node, the MM sends OF Flows to the MD. – When AirGroup is enabled(mDNS and DLNA) then 2 flows are pushed to the MD. – When AirGroup IPv6 is enabled, then 2 more flows are pushed to the MD IPv4/IPv6 – When AirGroup Vlan Aggregation is enabled then 1 more flow is pushed to the MD mDNS Open flow-table details on controller, pushed from MM: (EmeaEvent01) #show openflow flow-table | include 5353,1900,60001 * * * 0x86dd ::/0 ::/0 17 * 5353 (Output:controller) * * * 0x800 * * 17 * 1900 (Output:controller) * * * 0x86dd ::/0 ::/0 17 * 1900 (Output:controller) * * * 0x800 * * 17 * 5353 (Output:controller) * * * 0x800 192.168.4.5 222.173.190.239 17 60001 60001 (Output:controller) Flow for mDNS packet: port 5353 IPv4/IPv6 DLNA VLAN AGGREGATION 192.168.4.5 = MD ‘o’ represents open flow #ArubaAirheads 28 Fun fact: Open Flow Packet Forwarding 222.173.190.239 in hex: de.ad.be.ef (0xdeadbeef) 186.173.202.254 in hex: ba.ad.ca.fe (0xbaadcafe) http://www.catb.org/jargon/html/D/DEADBEEF.html: DEADBEEF: /dedbeef/, n.The hexadecimal word-fill pattern for freshly allocated memory under a number of IBM environments, including the RS/6000. Some modern debugging tools deliberately fill freed memory with this value as a way of converting heisenbugs into Bohr bugs. As in “Your program is DEADBEEF” (meaning gone, aborted, flushed from memory); if you start from an odd half-word boundary, of course, you have BEEFDEAD. See also the anecdote under fool and dead beef attack. #ArubaAirheads 29 VLAN Aggregation – AP VLAN aggregation allows the discovery of wired mDNS or SSDP devices which do not have L2 connectivity with the Mobility Master or a stand-alone controller or which do not trunk on the Mobility Master or a stand-alone controller. – An AP, which is in the same VLAN as the wired mDNS or SSDP device which does not trunk on Mobility Master or a stand-alone controller receives and forwards the mDNS or SSDP packets from the wired mDNS or SSDP devices to the Mobility Master or a stand-alone controller. – The AP forms a separate split tunnel (0x8000) and aggregates all mDNS or SSDP traffic. Up to 4094 VLANs are supported.
Load more

Recommended publications
  • Arubaos-Switch Multicast and Routing Guide for YC.16.04
    ArubaOS-Switch Multicast and Routing Guide for YC.16.04 Part Number: 5200-3134 Published: July 2017 Edition: 1 © Copyright 2017 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. Java® and Oracle® are registered
    [Show full text]
  • Developing a Solution for Multimedia Home Networking
    Peng Liu Developing a Solution for Multimedia Home Networking School of Electrical Engineering Thesis submitted for examination for the degree of Master of Science in Technology. Espoo 20.5.2015 Thesis supervisor: Prof. Raimo A. Kantola Thesis advisor: PhD Mikko Välimäki aalto university abstract of the school of electrical engineering master’s thesis Author: Peng Liu Title: Developing a Solution for Multimedia Home Networking Date: 20.5.2015 Language: English Number of pages: 9+66 Department of Communications and Networking Professorship: Networking Technology Code: S-38 Supervisor: Prof. Raimo A. Kantola Advisor: PhD Mikko Välimäki In recent years, the rapid development of electronics and computer science has enabled home networking devices to become more affordable and more powerful. Several widely used multimedia-streaming solutions have become available in the market. However, as a result of their different technical designs, these standards naturally experience serious compatibility issues. Thus, end users can have several multimedia devices, with each one using a distinctive, unique protocol, making it challenging or even impossible sometimes to share media between those devices. These compatibility issues have motivated the need to determine the technological features common to the existing multimedia-streaming standards and to develop a more easy-to-use multimedia home networking solution. This thesis compares the modern solutions for multimedia home networking (MHN), including AirPlay, Miracast, Chromecast, and especially the Digital Liv- ing Network Alliance (DLNA) standard due to its wide adoption. By conducting research on the features and capabilities of these existing solutions, a suitable mo- bile solution for MHN, which takes advantage of AirPlay, Discovery and Launch (DIAL), and DLNA, is proposed for the Android platform.
    [Show full text]
  • D2.1 System Architecture
    Directorate General for Communications Networks, Content and Technology Innovation Action ICT-687655 D2.1 System Architecture Due date of deliverable: 31 March 2016 Actual submission date: 10 May 2016 Resubmitted with minor changes: 14 July 2017 Start date of project: 1 December 2015 Duration: 36 months Lead contractor for this deliverable: Cisco Version: 14 July 2017 Confidentiality status: Public © 2-IMMERSE Consortium 2017 Page 1 of (135) Grant Agreement number: 687655 — 2-IMMERSE — H2020-ICT-2015 D2.1 System Architecture Abstract This document describes the system architecture being developed by the 2-IMMERSE project. This architecture is designed to enable the four multi-screen service prototypes that will be delivered through the project. The System Architecture is layered as a set of platform services, a client application architecture and production architecture. The system architecture is a work in progress; it will evolve both as we refine it and specify it in more detail, and as we deliver each of the multi-screen service prototypes through the project. Target audience This is a public deliverable and could be read by anyone with an interest in the system architecture being developed by the 2-IMMERSE project. As this is inherently technical in nature, we assume the audience is technically literate with a good grasp of television and Internet technologies in particular. We have included a Technology Overview section that summarises a range of technologies that are potentially applicable within the project. This document will be read by the Project Consortium as it defines the system architecture that will be adopted and evolved throughout the project.
    [Show full text]
  • Using the DIAL Protocol for Zero Configuration Connectivity in Cross
    Institutionen f¨ordatavetenskap Department of Computer and Information Science Final thesis Using the DIAL Protocol for Zero Configuration Connectivity in Cross-Platform Messaging by Emil Bergwik LIU-IDA/LITH-EX-A{14/030{SE 2014-06-18 Linköpings universitet Linköpings universitet SE-581 83 Linköping, Sweden 581 83 Linköping Link¨opingsuniversitet Institutionen f¨ordatavetenskap Final thesis Using the DIAL Protocol for Zero Configuration Connectivity in Cross-Platform Messaging by Emil Bergwik LIU-IDA/LITH-EX-A{14/030{SE 2014-06-18 Supervisor: Anders Fr¨oberg, Link¨opingUniversity Shu Liu, Harbin Institute of Technology Peter Steiner, Accedo Broadband AB Examiner: Erik Berglund, Link¨opingUniversity Abstract Today's living room context offers more and more possibilities when it comes to when and how to interact with the television and media content offer- ings. Buzzwords such as "TV Everywhere" is something that both hard- ware manufacturers, content providers and television networks are pursuing to great lengths. At the core of such marketing schemes is the availability of platform-independent content consumption. In a Utopian setting, the end-user should never have to worry if he or she is currently using a smart TV, tablet, phone or computer to view a video or photos, play music or play games. Taking the concept even further, the devices should also be able to connect and communicate with each other seamlessly. Having for example a television set (first screen) controlled by a mobile phone (second screen) is commonly referred to as companion device interaction and is what this thesis has investigated. More specifically, a way of discovering and launch- ing a first screen application from a second screen application using the zero configuration discovery protocol named DIAL has been implemented into a cross-platform messaging solution.
    [Show full text]
  • Apple Bonjour Protocol Specification
    Apple Bonjour Protocol Specification Swishier and amitotic Juan papers her silverback flounce peevishly or neoterizing wickedly, is Worden athletic? Micheal carbonylates stochastically while legitimist Wells hocusing cheap or reallotting scienter. Dehydrated Alastair bastinados ravingly or boondoggles homeopathically when Neel is leering. Linux releases of use your music library must correctly advertised service configured for bonjour protocol that allows a broadcast Apple working condition make Bonjour compatible with enterprise. AirPlay 2 Specifications macsysadmin Reddit. Derived from the protocol specification and vast the interoperability of different implementations of their same. Zeroconf Linux. Seems to avoid wasting network protocols, specification is discovering recommended. Apple's Multicast DNS mDNS is these open specification while Microsoft's Link-local Multicast Name Resolution LLMNR is little used and the. Data and Step 3 AirPrint uses the IPP protocol specifically IPP to manage print jobs. Hack 7 Advertise Bonjour Services in Linux Software Hacks. IP allocation has been standardized first is used by Apple Microsoft and. Discovery protocol which those answers, apple computers and thirdparty local and os. PDF Rule-Based Verification of Network Protocol. Apple Macintosh Mac and Mac OS are registered trademarks of Apple Inc. Changing network instead of western europe in this document authors also discovery aggregation server has bonjour protocol specification, only be considered. Authentication via MAC addresses must be deactivated All WiFi-based devices with HomeKit support may the Bonjour protocol Multicast to. Php is bonjour protocol specifically require any. Ietf zeroconf services can restore the apple bonjour protocol specification uses. Sets of a plan to node provides multicast, these statements based in.
    [Show full text]
  • Vorlage Für 2-Seiter DIN A4 (Produktblatt )
    FRAUNHOFER INSTITUTE FOR OPEN COMMUNICATION SYSTEMS FOKUS FAMIUM MULTISCREEN What is FAMIUM? FAMIUM is an end-to-end prototype implementation for early technology evaluation and Contact interoperability testing developed by Fraunhofer FOKUS’ Competence Center Future Louay Bassbouss Applications and Media (FAME). FAMIUM facilitates multiscreen content presentation and Competence Center FAME synchronization, adaptive media streaming and content protection. Phone +49 30 3463-7275 FAMIUM includes a Chromium build with extended features of upcoming Web and [email protected] streaming standards to allow early prototyping, experimentation and testing. These for example include W3C Presentation API, DIAL, Network service discovery, UPnP / DLNA, Fraunhofer FOKUS W3C TunerControl API, W3C Media Source Extensions (MSE) and Encrypted Media Kaiserin-Augusta-Allee 31 Extensions (EME). Furthermore, FAMIUM supports Dynamic Adaptive Streaming over HTTP 10589 Berlin (DASH) and Digital Rights Management (DRM). Germany FAMIUM Multiscreen www.fokus.fraunhofer.de/go/famium TV sets and companion devices (e.g., smartphones, tablets, etc.) have outgrown their original purpose and are now playing together an important role in multiscreen context. Also TVs and companion devices are used quite often at the same time, especially in home environments while already multi screen applications are entering the market. The main drivers of this trend are connected TV sets. You would like to show your application even bigger on other screens? For example show photos to your friends on the TV rather than just on a smartphone? Or extend your application to show more content on different screens? FAMIUM Multiscreen provides technologies to connect multiple screens together so that applications can make use of and interact directly with all accessible screens.
    [Show full text]
  • A Closer Look Into Privacy and Security of Chromecast Multimedia Cloud Communications
    A Closer Look into Privacy and Security of Chromecast Multimedia Cloud Communications Ali Tekeoglu, Ali S¸aman Tosun Department of Computer Science University of Texas at San Antonio San Antonio, TX, 78249 Email: {[email protected], [email protected]} Abstract—Chromecast is a small, system-on-chip device, that are comparable to Apple TV. Netgear NeoMediacast HDMI plugs into the HDMI port of a larger screen and turns it into a Dongle [11] is another HDMI stick, which is about to be re- smart screen. It is designed for multimedia streaming in a home- leased to the market. It runs Android OS and is decorated with network environment. By setting up Chromecast, you can stream videos onto a larger screen and control it from a mobile device the latest specification WiFi hardware, Miracast functionality such as a smart-phone, tablet or a laptop. The idea is to cast the and integrated DRM support. Chromecast is a cost effective multimedia to a larger second screen and use the smaller one as a way of streaming multimedia, either from Internet or locally remote control. Since its based on Google Cast SDK which is open stored, onto a larger screen. Its an HDMI stick that connects to to developers, a growing number of multimedia content providers HDMI port and communicates over Wi-Fi. Among the severe such as YouTube, Netflix, Hulu and HBO are offering appli- cations to support Chromecast streaming for mobile operating competition in the market, Chromecast [9] has emerged as the systems. This device uses Discovery and Launch (DIAL) protocol, most successful with respect to functionality/cost metric.
    [Show full text]
  • Support De Présentation
    3 Juillet 2019 La découverte de service à l’aide du DNS Antoine BERNARD Sommaire I. Qu’est ce que DNS-SD ? II. Fonctionnement III. Évolutions et perspectives Antoine BERNARD Diplômé Télécom SudParis, spécialisation Réseaux et Services Emergents Doctorant en CIFRE à l’AFNIC depuis décembre 2018 La découverte de service d’après Wikipédia Service discovery is the automatic detection of devices and services offered by these devices on a computer network. A service discovery protocol (SDP) is a network protocol that helps accomplish service discovery. Service discovery aims to reduce the configuration efforts from users. La découverte de service d’après Wikipédia Détection d’appareils et des services à l’aide d’un réseau Basé sur un protocole de découverte (SDP) Ayant pour objectif de réduire l’effort de configuration utilisateur. Qu’est ce que DNS- SD ? Mise en réseau sans configuration (Zero Configuration Networking) « Installer du matériel qui marche sans se poser de questions » « Pas d’IP à configurer Pas de messages d’erreur Pas de frustration » « Construire des appareils et des applications qui se configurent tous seuls » Zero Configuration Networking: The Definitive Guide Daniel Steinberg and Stuart Cheshire, 2005 Historiquement développé par Apple Standard ouvert Protocole RendezVous, puis Bonjour d’Apple Windows Linux Mac OS X Implémentation existantes pour divers langages (C, C++, Java, Python, Ruby, Go...) Bonjour © 2019 Apple Inc (Première Release : Août 2002) Basé sur le standard mDNS Issu de GT Zero Sémantique DNS sans Configuration
    [Show full text]
  • Assessing the Impact of Second Screen
    Assessing the impact of second screen MC/168 This document has been prepared for Ofcom Report by Technologia in association with DTG and i2 media research Authors Dr Jeremy Klein, Technologia Dr Jonathan Freeman, i2 media research David Harding, DTG Ali Teffahi, DTG 4 March 2014 This document has been prepared for Ofcom Version 1 Assessing the impact of second screen Contents Executive summary .....................................................................................................................................................................7 1 Introduction .......................................................................................................................................................................17 2 Definitions and scope .........................................................................................................................................................18 2.1 Terminology .......................................................................................................................................................................... 18 2.2 Existing definitions of ‘second screen’ .................................................................................................................................. 18 2.3 The ‘second screen phenomenon’ ........................................................................................................................................ 20 2.4 Key dimensions ....................................................................................................................................................................
    [Show full text]
  • A Survey on Chromecast Digital Device
    © 2018 JETIR October 2018, Volume 5, Issue 10 www.jetir.org (ISSN-2349-5162) A SURVEY ON CHROMECAST DIGITAL DEVICE 1 Mrs.A.Pavithra, 2Mr.H.Vignesh Ramamoorthy, 3Ms M.Reka Eswari, 4Ms. C.G.Nandhini, 1Assistant Professor, 2Assistant Professor, 3Student, 4Student Department of UG Computer Science, Sree Saraswathi Thyagaraja College, Pollachi, India ABSTRACT Chromecast is a smart digital invention, developed by google. It is used to convert TV into smart TV. It is supported by several apps launched by google this makes the device to convert TV into smart TV. It is low overhead when compared to smart TV. This device helps the lower middle peoples to experience the smart TV. Its appearance is similar to pen drive. Since because of its overhead every level of peoples can buy easily. The invention of this device makes us to use and experience smart TV very easily and it is very comfort to connect the device into the TV. It is very stress-free to set up. Everyone have a dream to see smart TV but it is not possible for everyone to see it, but this device is the greatest invention which makes everyone’s dream come true. This is not only used in TV it is also supported by many electronic devices like mobiles, laptops etc. Let us see more and detailed about the smart digital invention chromecast. Keywords: Chromecast, Smart TV, Smartphone, Wi-Fi, HDTV 1. INTRODUCTION Chromecast is the smartest device which workings with devices you previously own, together with Android smartphones and tablets, iPhones and iPads, Windows and Mac laptops, and Chromebook Pixel.
    [Show full text]
  • Institutionen För Datavetenskap Integrating the Google Cast Technology in a Second-Screen Solution
    Institutionen f¨ordatavetenskap Department of Computer and Information Science Final thesis Integrating the Google Cast Technology in a Second-screen Solution by Niklas Lavrell LIU-IDA/LITH-EX-A{14/031{SE 2014-06-23 Linköpings universitet Linköpings universitet SE-581 83 Linköping, Sweden 581 83 Linköping Link¨opingsuniversitet Institutionen f¨ordatavetenskap Final thesis Integrating the Google Cast Technology in a Second-screen Solution by Niklas Lavrell LIU-IDA/LITH-EX-A{14/031{SE 2014-06-23 Supervisor: Anders Fr¨oberg (Link¨opingsUniversity), Deng Shengchun (Harbin Institute of Technology), Peter Steiner (Accedo Broadband AB) Examiner: Erik Berglund (Link¨opingsUniversity) Abstract The newly released Google Chromecast has generated an increasing amount of interest for so called second-screen experiences in the market. Although the technology behind such experiences has existed for a couple of years, end users are now truly starting to grasp the concept and benefits of multi- screen. The company, at which the thesis was performed at, provides a cloud-based messaging solution for Internet connected devices, which en- ables multi-screen use cases. To increase the amount of supported platforms in the solution, new technologies frequently needs to be integrated. In this thesis I have performed an exploratory research & development project with the aim to integrate the Google Cast technology in this multi-screen solu- tion. The fundamental difference in how the two ecosystems were designed resulted in a companion device framework that acted as a wrapper over the technologies. The framework was implemented on the Android platform to- gether with a set of demo applications. The proposed solution should be seen as a starting point for integrating different multi-screen technologies within a single companion device framework.
    [Show full text]
  • Application Discovery Anwendungsentdeckung Découverte D’Application
    (19) *EP002680500B1* (11) EP 2 680 500 B1 (12) EUROPEAN PATENT SPECIFICATION (45) Date of publication and mention (51) Int Cl.: of the grant of the patent: H04L 12/28 (2006.01) H04L 29/08 (2006.01) 23.10.2019 Bulletin 2019/43 (21) Application number: 13174379.1 (22) Date of filing: 28.06.2013 (54) Application discovery Anwendungsentdeckung Découverte d’application (84) Designated Contracting States: • "X display manager (program type)", , 16 June AL AT BE BG CH CY CZ DE DK EE ES FI FR GB 2012 (2012-06-16), XP055076688, Retrieved from GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO the Internet: PL PT RO RS SE SI SK SM TR URL:http://en.wikipedia.org/w/index.php?ti tle=X_display_manager_%28program_type%29 (30) Priority: 28.06.2012 US 201261665827 P &o ldid=497826983 [retrieved on 2013-08-27] 25.07.2012 US 201261675756 P • UPNP FORUM: "UPnP Device Architecture 1.1", 14.03.2013 US 201313827720 UPNP FORUM , 15 October 2008 (2008-10-15), pages I-VI,1, XP002562314, Retrieved from the (43) Date of publication of application: Internet: 01.01.2014 Bulletin 2014/01 URL:http://www.upnp.org/specs/arch/UPnP-ar ch-DeviceArchitecture-v1.1.pdf [retrieved on (73) Proprietor: Netflix, Inc. 2010-01-08] Los Gatos, California 95032 (US) • "DIAL - DIscovery And Launch protocol specification - Version 1.6.4", , 19 December 2012 (72) Inventors: (2012-12-19), pages 1-16, XP055076322, • White, Jean-Marie Retrieved from the Internet: Los Gatos, CA 95032 (US) URL:http://www.dial-multiscreen.org/dial-p • Danciu, Daniel rotocol-specification/DIAL-2ndScreenProtoc Los Gatos,
    [Show full text]