U NIVERSITY OF B RISTOL Centre for Communications Research Copyright © 2002 NPG 25 June, 2016 Home Interoperability Project Update from UoB 25 May 2004

U NIVERSITY OF B RISTOL Centre for Communications Research Copyright © 2004 Networks & Protocols Group 25 June, 2016 Objective  Interoperability The indicates our limited interest at presentation/application layer; of interest to this group seems to be the areal; and this representation does NOT mean that the HG is sought to be a single physical device EHS Device Lonworks Device X10 Device EHS XML Command Lonworks XML Command X10 XML Command Lonworks to Universal EHS to Universal Universal to EHS Universal to Lonworks IWF Home Gateway Universal Command X10 to Universal Universal to X10 IWF Objective Investigate the processes and some possible technologies to realise the proposed interoperability framework Outcome: Proof of concept realisation Example of complete system chain of transformations for the interoperability A very long list of acronyms Lots more to do, especially to complete the messaging entity, but not critical activity Clarifications of responsibility areas (i.e. areas where the group may have significant difficulties to progress)

U NIVERSITY OF B RISTOL Centre for Communications Research Copyright © 2004 Networks & Protocols Group 25 June, 2016 Vendor schemas A vendor schema describes all the commands a (possibly set of) device(s) from that vendor can process XML command instantiated for a vendors heating controller ………. ………… ……. ………. ………… ……. current_temp 45 read current_temp 45 read light 1 on light 1 on XML command instantiated for a vendors light

U NIVERSITY OF B RISTOL Centre for Communications Research Copyright © 2004 Networks & Protocols Group 25 June, 2016 Interworking Function  EHS IWF Example EHS SchemaEHS XML EHS-Uni XSLT EHS XML Universal XML Uni-EHS XSLT EHS XML EHS Schema Universal Schema EHS XML commands are instantiated from a EHS Schema; then transformed to Universal XML command with a XSLT file The reverse happens to get back to EHS XML WG1 responsibility to define Manufacturer responsibility Implemementation /manufacturer defined

U NIVERSITY OF B RISTOL Centre for Communications Research Copyright © 2004 Networks & Protocols Group 25 June, 2016 Interchange process Vendors Schema (description of the device) 2.GUI creation (JAXB used together with the Vendors Schema) (application/implementation dependent – not a concern in interop work) 3.Application forms (sends) raw-message; JDOM/SAX is used to convert it into internal message in XML format (IWF – Part 1) 4.XML internal message converted to XML interop (or master/universal) message using vendor-supplied XSLT (IWF – Part 2) 5.XML interop format message is packed using some internal HG protocol (in this case SOAP for easy implementation) 6.Message is passed onto the comm system 7.The reverse process is/may be repeated on the connection on the peer system (i.e. if this was the CEBus link to the Interoperable HG, the process is reversed on the Konnex link interface).

U NIVERSITY OF B RISTOL Centre for Communications Research Copyright © 2004 Networks & Protocols Group 25 June, 2016 Further work Ensure common understanding of focus of work OBIX aim seems to be to define a “universal” XML-based home automation language (from the notes of last meeting) If the premises are right (i.e. input from manufactures) it is not impossible, and it aligns with the interop work We seek to define interop functions … and we are hindered as there is no representation from the different standards in the our language of choice (XML) We can guess (?!) on the XML representation from the standards, create a matching language, and then define the interop High risk, high volume work TAHI very active Other parallel projects (Ron) Get input from manufacturers/industry on their schemas, or schema related activity OBIX Abstraction Model? TAHI (through Stephen and Dritan) … ? …