DOCSLIB.ORG

Alljoyn Device Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Alljoyn Device Management Any questions please contact [email protected] • The “medium” to enable AllJoyn applications to communicate via published APIs • Communication is via messages that map directly to APIs in high-level programming languages • Based on discovery of applications/services Can run over Wi-Fi, Wi-Fi Direct, Ethernet, PLC and Bluetooth Consumer (client) Producer (server) If required, authentication occurs on demand between the two apps when a method is invoked or to receive a signal. PIN code, PSK, or ECDSA (Elliptical Curve Digital Signature Algorithm). Once authenticated, all messages between these two devices are encrypted using AES-128 CMM. Servicing, reduced code size Optimized performance, full integration Reduced code size, integrated with Windows SDK AllJoyn Studio accelerates development for Windows UWP Samples AllJoyn Standard Client API (C) MSAJAPI.dll An Visual Studio extension developed by Microsoft Windows Runtime Class Description <Foo>Watcher Searches for producers that advertise the target service Reports the success or failure of joining a session, and exposes a <Foo>JoinSessionResult <Foo>Consumer instance for the session if the join was successful. <Foo>Producer Advertises a service and exposes handlers for AllJoyn events. Exposes methods and handlers to send and receive signals. Used <Foo>Signals by both producers and consumers. <Foo>Consumer Interacts with a service after it has been discovered. Arguments passed to methods in <Foo><Method>CalledEventArgs EventAdapters.<Foo>ServiceEventAdapter. Used by method implementations in IService to report the success <Foo><Method>Result or failure of the call, as well as any return values. <Foo><Signal>ReceivedEventArgs Arguments passed to a signal in Signals. <node> <interface name="com.example.Door"> <annotation name="org.alljoyn.Bus.Secure" value="true" /> <annotation name="org.alljoyn.Bus.DocString.En" value="Example interface for a doorway" /> <property name="Locked" type="b" access="read"> <annotation name="org.freedesktop.DBus.Property.EmitsChangedSignal" Interfaces as described via value="true" /> </property> signals, properties and <method name="SetLockState"> methods. <arg name="lockDoor" type="b" direction="in" /> <annotation name="org.freedesktop.DBus.Method.NoReply" value="true" /> </method> <signal name="ThresholdCrossed" /> </interface> </node> low-overhead, inter-process communication with a type format for data representation. Extends D-Bus Specification XML with XML tags for holding textual descriptions while also applying AllJoyn principles to the specification. "com.contoso.Sensor” vs “com.contoso.Sensor.Humidity” The "Foo" interface created by Contoso Ltd., which owns the contoso.com domain <interface name="com.contoso.Foo"> <node> <interface name="com.example.Door"> <annotation name="org.alljoyn.Bus.Secure" value="true" /> <annotation name="org.alljoyn.Bus.DocString.En" value="Example interface for a doorway" /> Properties <property name="Locked" type="b" access="read"> Signals <annotation Methods name="org.freedesktop.DBus.Property.EmitsChangedSignal" value="true" /> </property> <method name="SetLockState"> <arg name="lockDoor" type="b" direction="in" /> Describe additional functionality <annotation name="org.freedesktop.DBus.Method.NoReply" value="true" /> or constraints </method> <signal name="ThresholdCrossed" /> </interface> </node> Producer Consumer (direction="out") Consumer Producer (direction="in") Default: "null" authentication Strong authentication: pre-shared key (PSK) / certificate key exchange (ECDSA). <node> <interface name="com.example.Door"> <annotation name="org.alljoyn.Bus.Secure" value="true" /> <annotation name="org.alljoyn.Bus.DocString.En" value="Example interface for a doorway"/> ... </interface> </node> • Allow access to a producer's state • Access values: “read” and “readwrite” • Annotation - “org.freedesktop.DBus.Property.EmitsChangedSignal” Value Action when property change occurs true Emit a signal denoting the changed property and the new value Invalidates Emit a signal denoting the changed property but NOT the new value false Emit no signal The property will never change value and never emit a changed signal. const This will be introduced in the AllJoyn 16.04 release; until then, use "true". • Modify the state of a producer • May have input and output arguments • No return message: "org.freedesktop.DBus.Method.NoReply". • Inform consumers of an event that they could not determine by querying the producer • “out” arguments only. • Should never be state-based. Provide feedback as error, warning, and informational messages ajxmlcop.exe doorExample.xml GitHub 1. Install the AllJoyn Studio 2. Launch Visual Studio 2015, click File > New > Project. 3. In the New Project dialog box, click Installed > Templates > Visual C# > Windows > Universal to create a new AllJoyn App project Add and Remove Interfaces Automatically add the generated files as a WinRT Component To modify the interfaces after the solution is created… Go to AllJoyn > Add/Remove Interfaces... to launch the Interface manager Add a “Using” clause to access the WinRT components Using Windows.Devices.AllJoyn; Using com.example.Door; Implement the Producer 1. Create a class for the producer’s service. Use Quick Action to fill in the necessary components. 2. Create a new AllJoynBusAttachment 3. (Optional) Populate the About data for the producer through AllJoynBusAttachment.AboutData 4. Initialize the producer with the AllJoynBusAttachment 5. Instantiate the newly created Service for the producer 6. Start the producer [email protected] Subscribe https://channel9.msdn.com/Blogs/Internet-of-Things-Blog/Creating-AllJoyn-Producers-and-Authoring- AllJoyn-Introspection-XML?ocid=EntriesInArea https://channel9.msdn.com/Blogs/Internet-of-Things-Blog/Using-the-AllJoyn--Studio-Extension https://wiki.allseenalliance.org/irb/interface_design_guidelines_1.1 Join WinHEC LINE Community We want to hear from you! @winhec Please Complete the Evaluation Form and return it to our reception. Your input is highly important to us! Thank you!! .
Load more

Recommended publications
  • Woo Project Overview
    WoO Approach General Overview WF-IoT 2014 Mihaela Brut, Patrick Gatellier Thales Services, France Ilyoung Chong, Hankuk University of Foreign Studies, Korea 6th Of March 2014 2 / 01: Scientific and Business Context Scientific and Business Context 3 / Context – IoT and WoT gather more and more devices IoT boom: u Since 2007: more devices than people are connected to Internet (Cisco IoT IBSG, 2011) u In 2020: 50 billions devices will be connected to Internet (Ericson, 2010) u In 2020: the global M2M business (large industry, solution providers, connectivity providers) will reach 260 milliards Euros (Machina Research, 2012); u By 2020: IoT will add $1,9 trillion to the global economy (Gartner, 2013) => huge business application development (WoT & Future Internet boom) People connected to Internet resulted in Web 1.0, 2.0, 3.0 … applications What can we imagine about the future of the connected devices? 4 / Context – status of IoT and WoT business Huge deployment of smart devices and sensors, resulting in huge amount of data collected, not exploited in real-time, nor outside a closed system: u Smart metering => filtered data is selected for billing purposes, and various statistic analysis are accomplished £ If a third party (e.g. insurance company) is interested in specific data, no legal framework and no technical support u Smart homes: each equipment is able to switch in secure mode, and to send information or alarm messages, eventually to receive remote control commands £ France: government investment in “sensing” the elder people homes
    [Show full text]
  • Hypermedia Apis for Sensor Data: a Pragmatic Approach to the Web of Things
    Hypermedia APIs for Sensor Data: A pragmatic approach to the Web of Things The MIT Faculty has made this article openly available. Please share how this access benefits you. Your story matters. Citation Russell, Spencer, and Joseph Paradiso. “Hypermedia APIs for Sensor Data: A Pragmatic Approach to the Web of Things.” Proceedings of the 11th International Conference on Mobile and Ubiquitous Systems: Computing, Networking and Services (2014). As Published http://dx.doi.org/10.4108/icst.mobiquitous.2014.258072 Publisher European Union Digital Library/ICST Version Author's final manuscript Citable link http://hdl.handle.net/1721.1/103763 Terms of Use Creative Commons Attribution-Noncommercial-Share Alike Detailed Terms http://creativecommons.org/licenses/by-nc-sa/4.0/ Hypermedia APIs for Sensor Data A pragmatic approach to the Web of Things Spencer Russell Joseph A. Paradiso [email protected] [email protected] Responsive Environments Group MIT Media Lab Massachusetts Institute of Technology Cambridge, MA, USA ABSTRACT dards and protocols such as AllJoyn1 and MQTT2, other As our world becomes more instrumented, sensors are ap- projects [20] seek to use existing application-level Web stan- pearing in our homes, cars, and on our bodies [12]. These dards such as HTTP to provide an interface that is more sensors are connected to a diverse set of systems and pro- familiar to developers, and also that can take advantage of tocols driven by cost, power, bandwidth, and more. De- tooling and infrastructure already in place for the World spite this heterogeneous infrastructure, we need to be able Wide Web. These efforts are often dubbed the Web of to build applications that use that data, and the most value Things, which reflects the relationships to existing Web stan- comes from integrating these disparate sources together.
    [Show full text]
  • Smart Homes and the New White Futurism
    Journal of Futures Studies 2021,Vol. 25(4) 45–56 DOI: 10.6531/JFS.202106_25(4).0004 Article Smart Homes and the New White Futurism Adam Richard Rottinghaus1,* 1Assistant Professor of Media, Journalism & Film, Miami University, Williams Hall, 208, 350 Oak Ave., Oxford, OH, 45056, USA Abstract This article explores the consumer technology industry’s discourse about emerging Internet of Things smart home devices and sketches an outline of a “new white futurism.” New white futurism displaces prior consumer fantasies of labor-free living in smart homes and frames emerging smart home devices as tools for data-driven management of work/life balance in contemporary heteronormative, white, middle-class culture. The research draws on existing scholarly literature, archival documents, contemporary marketing discourses, and participant observation at CES in 2014 and 2018. The article concludes that it is crucial to reimagine cultural relationships to emerging technologies through Afro, Indigenous, and queer futuristic thought. Keywords Smart Homes, Emerging Technologies, Internet of Things, Futurism, Labor, Corporate Power This article explores the consumer technology industry’s discourse about emerging smart home devices and begins sketching the outlines of a “new white futurism.” New white futurism is a discourse from companies that promotes emerging smart home technologies as tools for data-driven management of work/life balance in contemporary heteronormative, white, middle-class culture. Since 2008 the consumer technology industry has increasingly focused on the Internet of Things (IoT) and connected smart homes as the dominant retail application. IoT smart home devices have precipitated a shift away from promoting imaginative technological futures that bring about changes in labor or culture in everyday life toward one of logistics and management that reproduce the status quo.
    [Show full text]
  • Better Life with Smart Media & Things
    Better Life with Smart media & things Innopia Technologies Inc. Why Smart Media Gateway for IoT Service? 1 Interactive media consumption with IoT devices 2 More effective information on TV interface 3 Always connected gateway at living room AllSeen Alliance Ecosystem LG AT&T Panasonic Microsoft Vodafone Technicolor Qualcomm Century Link Philips ADT Sony LGU+ Canon Haier Solution Service Operators CE Manufacturer Why Innopia for AllJoyn Solution? Specialty of Embedded Design House SW for Linux & Android experiences with platform various SoC Guaranteed Inter- Make media as one of operability with strong IoT smart home service expertise in HW & SW Innopia Advantages Innopia AllJoyn enabled product roadmap 1. AllJoyn 3. AllJoyn notification, 5. AllJoyn support Wi-Fi notification enabled control panel enabled Smart radar tracer for Smart TV wireless TV the multiple movement enablement stick streaming projector and presence monitoring MP CS CS Dev. Plan. 2. Smart home package 4. Multi-protocol including Wi-Fi power support smart media plug, Wi-Fi LED bulb and GW based on own GW stick based on AllJoyn bridge system AllJoyn framework for for AllJoyn control panel home automation, energy management with media entertainment Now Launching Launching Launching Launching available Q3, 2015 Q3, 2015 Q4, 2015 Q2, 2016 Smart Home Starter Package Wi-Fi Smart LED MagicCast Wi-Fi Smart Light Bulb - AllJoyn Gateway Power Plug Smart Media Service Use Cases 1 Interactive game with LED bulb 2 Home theater experience from media mode Smart Media Service Use Cases
    [Show full text]
  • Standardized Service Layering for Iot in Onem2m
    Standardized Service Layering for IoT in oneM2M ETSI M2M Workshop, Sophia‐Antipolis, Dec. 2015 Nicolas Damour, [email protected] Senior Manager for Business & Innovation at Sierra Wireless Chairman of the Architecture Working Group at oneM2M © 2015 oneM2M 1 Connected Pancakes –1/3 “Thing” “Thing” Communication Communication Unit Unit Data Processing Data Processing & Communication & Communication Application Application Network © 2015 oneM2M Connected Pancakes –2/3 “Thing” “Thing” Communication Communication Unit Unit Data Processing Data Processing Part Part Data Communication Data Communication Part Part Network © 2015 oneM2M Connected Pancakes –3/3 “Thing” “Thing” Communication Communication Unit Unit Data Processing Data Processing Part Part Common Services Common Services Part Part Data Communication Data Communication Part Part Network © 2015 oneM2M oneM2M Pancakes “Thing” “Thing” Communication Communication Unit Unit Data Processing Data Processing Part Part Common Services Common Services oneM2M Part Part Data Communication Data Communication Part Part Network © 2015 oneM2M oneM2M Architecture Node (Host) Logical equivalent of a physical (or possibly virtualized) device Common Services Entity (Service Layer) Provides the set of "service functions" common to the M2M environments Application Entity (Application) Provides application logic for the end‐to‐end M2M solutions Reference Point (Interface) One or more interfaces ‐ Mca, Mcn, Mcc and Mcc’ (between 2 service providers) Network Services Entity (Modem) Provides connectivity
    [Show full text]
  • Avoid the Silos and Help Build the True Internet of Things
    Avoid the Silos and Help Build the True Internet of Things April 2016 Aaron Vernon, CTO at Higgns [email protected] I N T R O D U C T I O N ● Aaron Vernon, CTO at Higgns ● Previously I was VP Software Engineering at LIFX and CTO at Two Bulls ● Chair of the AllSeen Alliance Common Frameworks Working Group ● I am going to cover the following: ○ The complexities of the current IoT landscape ○ How this affects companies and users ○ The Internet of Silos example ○ How we can work together better Transports W i F i ● Uses the 802.11 standard ● Standard on all mobile devices and routers ● Has become ubiquitous for users ● Great range ● Great bandwidth ● High power consumption ● High cost ● Onboarding experience can be complicated ● Examples: Nest Cam, LIFX, Canary, Honeywell Lyric B L U E T O O T H S M A R T ● Standard on most mobile devices ● Becoming increasingly ubiquitous ● Low bandwidth ● Medium range ● Low power consumption ● Low cost ● Smart Mesh is being worked on ● Examples: Flic, Ilumi, Elgato Eve Z I G B E E ● Uses the 802.15.4 standard ● Low bandwidth ● Low range ● Low power consumption ● Very low cost ● Forms a mesh network ● Typically requires a hub for the radio ● Known to have interop and interference problems ● Examples: Phillips Hue, large amount of sensors and actuators Z W A V E ● Proprietary - chips developed by a single manufacturer ● Uses different frequencies in different countries ● Low bandwidth ● Medium range ● Low power consumption ● Very low cost ● Forms a mesh network ● Better interoperability and less interference
    [Show full text]
  • D3.1. State of the Art FUSE-IT
    D3.1. State of the Art FUSE-IT Editors: Son Han, Shohreh Ahvar, Noël Crespi, Reza Farahbakhsh, Bahram Alinia (IMT-TSP) Contributors: CCS, CEA-LIST, Evoleo, ICAM, iMINDS, IMT-TSP, ISEP/GCAD, SOGETI, Thales Services, ULR Reviewer: Hélia POUYLLAU (Thales RT) Draft history V.0.1.0 15 Dec 2014 Initial Version (Reviewed by Thales RT) V.1.0.0 30 Jan 2015 Release 1 - Revisions needed: - 3.1.4. Physical Detection and Anti-intrusion Sensors [Thales Services - Introduction] - 3.3.3. Network Operation Centers (NOC) [CCS - Solutions & Products] - 3.4.3. Security Operation Centers (SOC) [CCS – Figure 3.4.4, Situation awareness, limitation of SIEM and/or ad-hoc orchestrator] - 4.1.3. Internet of Things Alliances [SOGETI, technical details] V.1.0.1 30 May 2015 - Revisions needed as in V.1.0.0 - Added Smart Grid and Smart Grid Standards (ISEP/GECAD) - Updated 4.1.3 Internet of Things Alliances (SOGETI) V. Final 22 June 2015 - Updated 3.1.1 Smart Energy sensors, 3.2.2 Building Automation & SCADA (ICAM) - Updated 4.1.3 Internet of Things Alliances (SOGETI) V.Update 8 August 2015 - Added 4.4 Security Standards (IMT) - Updated 4.2.1 Building Automation Standards (IMT) - Added 3.4.1 Smart meters and cyber security (Thales Services) - Added 3.1.3 Heterogeneous traffic data , 3.1.4 Opportunistic spectrum access sensors and 3.4.3 Attacks and threats in IoT (ULR) <FUSE-IT> D3.1. State of the Art Table of Contents 1 Introduction ....................................................................................................................................... 6 1.1 Overview .................................................................................................................................. 6 1.2 FUSE-IT Components ............................................................................................................. 7 2 Related Projects ..............................................................................................................................
    [Show full text]
  • Guia De Configuração E Do Utilizador Copyright
    TG789vac v2 Guia de configuração e do utilizador Copyright Copyright ©1999-2016 Technicolor. Todos os direitos reservados. A distribuição e a cópia deste documento, bem como o uso e a divulgação do seu conteúdo, não são permitidos sem autorização por escrito da Technicolor. O conteúdo deste documento é fornecido apenas para uso informativo e pode estar sujeito a alterações sem aviso prévio e não deve ser interpretado como um compromisso da Technicolor. A Technicolor não é responsável por nenhum erro ou incorre- ção que possa aparecer neste documento. Technicolor 1-5 rue Jeanne d’Arc 92130 Issy-les-Moulineaux France http://www.technicolor.com Marcas comerciais As seguintes marcas comerciais podem ser usadas neste documento: • AllSeen™, AllSeen Alliance™, o logótipo AllSeen Alliance, AllJoyn™, o logótipo AllJoyn e o logótipo Designed for AllSeen são marcas registadas da AllSeen Alliance, Inc. • AutoWAN sensing™ é uma marca registada da Technicolor. • Qeo™ é uma marca registada da Qeo LLC, subsidiária da Technicolor. • Adobe®, o logótipo da Adobe, Acrobat® e Adobe Reader® são marcas comerciais ou marcas comerciais registadas da Adobe Systems, Incorporated, registadas nos Estados Unidos e/ou noutros países. • Apple® e Mac OS® são marcas comerciais registadas da Apple Computer, Incorporated, registadas nos Estados Unidos e noutros países. • A marca e os logótipos Bluetooth® são propriedade da Bluetooth SIG, Inc. • CableLabs® e DOCSIS® são marcas comerciais registadas da CableLabs, Inc. • DECT™ é uma marca comercial da ETSI. • DLNA® é uma marca comercial registada, o logótipo DLNA é uma marca de serviço, e DLNA Certified™ é uma marca registada da Digital Living Network Alliance.
    [Show full text]
  • Horizontal Platforms Offer Fast Track to Vertical Applications – Applicability of Onem2m to Smart City and Smart Living
    HORIZONTAL PLATFORMS OFFER FAST TRACK TO VERTICAL APPLICATIONS – APPLICABILITY OF ONEM2M TO SMART CITY AND SMART LIVING Presenter: Omar Elloumi, oneM2M TP Chair, Alcatel‐Lucent (acknowledgment: the author thanks oneM2M members who provided input to this presentation) oneM2M www.oneM2M.org © 2015 oneM2M Outline • Introduction • Technology trends • Smart cities • Smart living • take‐away © 2015 oneM2M 2 IoT, the next internet evolution And so what? © 2015 oneM2M 3 It’s all about quality of life Needs/enables Smart Smart Smart Home security/ buildings infrastructure mobility automation Smart Smart governance/ healthcare education Smart Smart Smart technology energy Health, fitness energy and lifestyle Smart grid‐micro grid What makes cities smart What makes living smart (adapted from Frost & Sullivan report) (adapted from Ovum report) There are more of this © 2015 oneM2M 4 The IoT empowers a long tail of applications Source: Alcatel‐Lucent © 2015 oneM2M 5 TECHNOLOGY TRENDS © 2015 oneM2M Trend1: horizontalization NICHE VERTICALS BROAD ADOPTION Low volumes, high ARPC, high TCO High volume, low ARPC, low TCO • Devices and Applications are designed as “stove‐pipes” • Devices and Applications are designed to collaborate • Devices dedicated for single application use across “clouds” • Solutions are closed and not scalable: duplication of • Devices are used for multiple application purposes dedicated infrastructure • Devices and Applications offering continuously evolve • High development & delivery cost • Easy app development and device integra‐tion through APIs and standard interfaces Horizontal platform with common functions and interfaces Source: Alcatel‐Lucent © 2015 oneM2M 7 Trend 2: softwarization Source: ITU‐T Focus Group IMT2020 © 2015 oneM2M 8 Trend 3: connectivity, plenty to chose from Range (extended) Native Low Power Wide‐area Access LTE enhancements 3GPP Cellular and/or CIoT (GSM/LTE) Device cost (low) Device cost (high) Bitrate (low) Bitrate (high) WPAN WLAN (e.g.
    [Show full text]
  • Pervasive Device and Service Discovery Protocol in Interoperability Xbee-IP Network
    TELKOMNIKA, Vol.15, No.4, December 2017, pp. 1875~1882 ISSN: 1693-6930, accredited A by DIKTI, Decree No: 58/DIKTI/Kep/2013 DOI: 10.12928/TELKOMNIKA.v15i4.5725 1875 Pervasive Device and Service Discovery Protocol in Interoperability XBee-IP Network Sabriansyah Rizqika Akbar*, Helmi Nizar, Wijaya Kurniawan, Mochammad Hannats Hanafi Ichsan, Issa Arwani Faculty of Computer Science, University of Brawijaya, Jl. Veteran Malang, East Java, Phone: +62 341 551611/ Fax +62 341 565420 *Corresponding author, e-mail: [email protected], [email protected], [email protected], [email protected], [email protected] Abstract The Internet of Things (IoT) communication protocol built over IP and non-IP environment. Therefore, a gateway device will be needed to bridge the IP and non-IP network transparently since an IoT user is more likely to concern on the service provided by the IoT device, rather than the complexity of the network or device configuration. Since today ubiquitous computing needs to hide the architectural level from it users, the data & information centric approach was proposed. However, the data & information centric protocol is having several issues and one of them is device and service discovery protocol over IP & non-IP network. This paper proposed a pervasive device and service discovery protocol that able to work in interoperability of the IP and non-IP network. The system environment consists of a smart device with XBee Communication as the non-IP network that will send the device and service description data to the IP network using WebSocket. The gateway will able to recognize the smart device and sent the data to the web-based user application.
    [Show full text]
  • Comparison of Iot Frameworks for the Smart Home
    Alexander Nimmermark Larsson Erik & Comparison frameworks of IoT for the smart Master’s Thesis Comparison of IoT frameworks for the smart home Alexander Larsson Erik Nimmermark home Series of Master’s theses Department of Electrical and Information Technology LU/LTH-EIT 2016-520 http://www.eit.lth.se Department of Electrical and Information Technology, Faculty of Engineering, LTH, Lund University, 2016. Comparison of IoT frameworks for the smart home Alexander Larsson [email protected] Erik Nimmermark [email protected] Anima AB Västra Varvsgatan 19, Malmö Advisor: Maria Kihl, EIT June 15, 2016 Printed in Sweden E-huset, Lund, 2016 Abstract The smart home landscape is rapidly evolving right now. There is yet to be an industry-wide common standard and several organizations are introducing their own proposed solutions. This has led to fragmentation and the field can appear confusing to interested parties trying to enter the market. There is a need to evaluate the different technologies to discern their distinguishing characteristics. This thesis report provides a comparison between HomeKit and IoTivity based on our proposed evaluation model. The model identifies a set of relevant charac- teristics which are evaluated through operationalization of criteria into composite measurables. Our comparison shows that at this time there is no definite answer to what framework to choose. Developers will have to compromise and make a decision based on the type of product they want to make. The proposed model can readily be used as a tool to evaluate any Internet of Things framework and provide guidance when choosing what technology to use.
    [Show full text]
  • Setup and User Guide Copyright
    TG789vac v2 Setup and User Guide Copyright Copyright ©1999-2016 Technicolor. All rights reserved. Distribution and copying of this document, use and communication of its contents are not permitted without written authorization from Technicolor. The content of this document is furnished for informational use only, may be subject to change without notice, and should not be construed as a commitment by Technicolor. Technicolor assumes no responsibility or liability for any errors or inaccuracies that may appear in this document. Technicolor 1-5 rue Jeanne d’Arc 92130 Issy-les-Moulineaux France http://www.technicolor.com Trademarks The following trademarks may be used in this document: • AllSeen™, AllSeen Alliance™, the AllSeen Alliance logo, AllJoyn™, the AllJoyn logo and the Designed for AllSeen logo are trademarks of the AllSeen Alliance, Inc. • AutoWAN sensing™ is a trademark of Technicolor. • Qeo™ is a trademark of Qeo LLC, a subsidiary of Technicolor. • Adobe®, the Adobe logo, Acrobat® and Adobe Reader® are trademarks or registered trademarks of Adobe Systems, Incorporated, registered in the United States and/or other countries. • Apple® and Mac OS® are registered trademarks of Apple Computer, Incorporated, registered in the United States and other countries. • Bluetooth® word mark and logos are owned by the Bluetooth SIG, Inc. • CableLabs® and DOCSIS® are registered trademarks of CableLabs, Inc. • DECT™ is a trademark of ETSI. • DLNA® is a registered trademark, DLNA disc logo is a service mark, and DLNA Certified™ is a trademark of the Digital Living Network Alliance. Digital Living Network Alliance is a service mark of the Digital Living Network Alliance. • Ethernet™ is a trademark of the Xerox Corporation.
    [Show full text]