IoTGateway/AllJoyn - Revision history

Daniel.hung at 06:45, 16 February 2016

2016-02-16T06:45:51Z

Daniel.hung at 03:01, 16 February 2016

2016-02-16T03:01:50Z

Daniel.hung at 05:33, 15 February 2016

2016-02-15T05:33:14Z

Daniel.hung at 05:17, 15 February 2016

2016-02-15T05:17:54Z

Daniel.hung at 05:16, 15 February 2016

2016-02-15T05:16:14Z

Daniel.hung at 05:15, 15 February 2016

2016-02-15T05:15:34Z

Daniel.hung at 04:34, 15 February 2016

2016-02-15T04:34:46Z

Daniel.hung at 03:33, 15 February 2016

2016-02-15T03:33:23Z

Daniel.hung at 03:19, 15 February 2016

2016-02-15T03:19:32Z

Daniel.hung at 02:43, 15 February 2016

2016-02-15T02:43:50Z

@@ Line 106: / Line 106: @@
 Advantech implements an Alljoyn service sample for SUSI APIs. It uses AllJoyn Thin Core Library (AJTCL), so that you can apply it on both embedded systems and general-purpose devices. This Alljoyn application supports About Announcement, ControlPanel service & Event/Action feature.
 ===Build Sample===
-. Follow [https://wiki.allseenalliance.org/develop/downloading_the_source the page] to get Alljoyn source code, or directly download from https://allseenalliance.org/framework/download
+. Follow [https://wiki.allseenalliance.org/develop/downloading_the_source the page] to get Alljoyn source code, or directly download from [https://allseenalliance.org/framework/download Alljoyn Download]
 '''''Note:''''' We use '''v14.12''' for SUSI Alljoyn service application.
@@ Line 112: / Line 112: @@
 . Set $AJ_ROOT
   $ export AJ_ROOT=`pwd`
-. Get Alljoyn SUSI Service source code and put it under ''services/base_tcl/sample_apps''
+. Get [https://github.com/ADVANTECH-Corp/AlljoynSusiService Alljoyn SUSI Service source code] and put it under ''$AJ_ROOT/services/base_tcl/sample_apps''
-. Set environment variables
+. Set environment variables (Cross-Compiler & SUSI4 lib path)
   $ export CROSS_PATH=/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi
   $ export CROSS_PREFIX=arm-poky-linux-gnueabi-
 . Build Thin Core Library
   $ cd $AJ_ROOT/core/ajtcl
@@ Line 125: / Line 127: @@
 ===Run Sample===
-After building, you can get the application binary named '''SusiService''' in ''build'' folder.
+After building, you can get the application binary named ''SusiService'' in '''build''' folder.
 Just copy it into your device and execute it!
-About verification tools, you can use these two APK on Android system.
+About verification tools, you can use these two APKs on Android system.
-*[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-controlpanel-service-framework-14.12.00-android-sdk-rel.zip ControlPanelBrowser.apk] is under alljoyn-controlpanel-14.12.00-rel\tools\
+*[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-controlpanel-service-framework-14.12.00-android-sdk-rel.zip ControlPanelBrowser.apk] is under ''alljoyn-controlpanel-14.12.00-rel\tools\''
-*[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-14.12.00b-android-sdk-rel.zip Event_Action_Browser.apk] is under alljoyn-14.12.00b-rel\cpp\samples\eventaction\Android\bin\
+*[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-14.12.00b-android-sdk-rel.zip Event_Action_Browser.apk] is under ''alljoyn-14.12.00b-rel\cpp\samples\eventaction\Android\bin\''
 Or use AllJoynExplorer on Windows 10.
 *[https://ms-iot.github.io/content/en-US/win10/AllJoyn.htm IoT Explorer for AllJoyn (AllJoyn Explorer)]
 ==Demo==

← Older revision		Revision as of 03:01, 16 February 2016
Line 155:		Line 155:
	*[https://allseenalliance.org/framework/documentation/develop/api-guide/controlpanel/c-thin Thin Core API Guide - ControlPanel]		*[https://allseenalliance.org/framework/documentation/develop/api-guide/controlpanel/c-thin Thin Core API Guide - ControlPanel]
	*[https://allseenalliance.org/docs/api/thin-client/index.html Thin Core API Reference]		*[https://allseenalliance.org/docs/api/thin-client/index.html Thin Core API Reference]
		+
		+	[[Category:Technique]]

@@ Line 105: / Line 105: @@
 ==SUSI Alljoyn Service==
 Advantech implements an Alljoyn service sample for SUSI APIs. It uses AllJoyn Thin Core Library (AJTCL), so that you can apply it on both embedded systems and general-purpose devices. This Alljoyn application supports About Announcement, ControlPanel service & Event/Action feature.
-===Build===
+===Build Sample===
-. Follow [https://wiki.allseenalliance.org/develop/downloading_the_source the page] to get Alljoyn source code, or download from https://allseenalliance.org/framework/download
+. Follow [https://wiki.allseenalliance.org/develop/downloading_the_source the page] to get Alljoyn source code, or directly download from https://allseenalliance.org/framework/download
-'''Note:''' We use v14.12 for SUSI Alljoyn service application.
+'''''Note:''''' We use '''v14.12''' for SUSI Alljoyn service application.
 . Set $AJ_ROOT
@@ Line 134: / Line 134: @@
 *[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-14.12.00b-android-sdk-rel.zip Event_Action_Browser.apk] is under alljoyn-14.12.00b-rel\cpp\samples\eventaction\Android\bin\
 Or use AllJoynExplorer on Windows 10.

@@ Line 107: / Line 107: @@
 ===Build===
 . Follow [https://wiki.allseenalliance.org/develop/downloading_the_source the page] to get Alljoyn source code, or download from https://allseenalliance.org/framework/download
 . Set $AJ_ROOT

@@ Line 129: / Line 129: @@
 About verification tools, you can use these two APK on Android system.
-[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-controlpanel-service-framework-14.12.00-android-sdk-rel.zip ControlPanelBrowser.apk] is under alljoyn-controlpanel-14.12.00-rel\tools\
+*[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-controlpanel-service-framework-14.12.00-android-sdk-rel.zip ControlPanelBrowser.apk] is under alljoyn-controlpanel-14.12.00-rel\tools\
-[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-14.12.00b-android-sdk-rel.zip Event_Action_Browser.apk] is under alljoyn-14.12.00b-rel\cpp\samples\eventaction\Android\bin\
+*[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-14.12.00b-android-sdk-rel.zip Event_Action_Browser.apk] is under alljoyn-14.12.00b-rel\cpp\samples\eventaction\Android\bin\
 Or use AllJoynExplorer on Windows 10.
-[https://ms-iot.github.io/content/en-US/win10/AllJoyn.htm IoT Explorer for AllJoyn (AllJoyn Explorer)]
+*[https://ms-iot.github.io/content/en-US/win10/AllJoyn.htm IoT Explorer for AllJoyn (AllJoyn Explorer)]
 ==Demo==

← Older revision		Revision as of 04:34, 15 February 2016
Line 104:		Line 104:

	==SUSI Alljoyn Service==		==SUSI Alljoyn Service==
		+	Advantech implements an Alljoyn service sample for SUSI APIs. It uses AllJoyn Thin Core Library (AJTCL), so that you can apply it on both embedded systems and general-purpose devices. This Alljoyn application supports About Announcement, ControlPanel service & Event/Action feature.
		+	===Build===
		+	1. Get Alljoyn source code
		+
		+	2. Set $AJ_ROOT
		+	$ export AJ_ROOT=`pwd`
		+	3. Get Alljoyn SUSI Service source code and put it under ''services/base_tcl/sample_apps''
		+	4. Set environment variables
		+	$ export CROSS_PATH=/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi
		+	$ export CROSS_PREFIX=arm-poky-linux-gnueabi-
		+	5. Build Thin Core Library
		+	$ cd $AJ_ROOT/core/ajtcl
		+	$ scons WS=off TARG=linux
		+	6. Build SUSI service
		+	$ cd $AJ_ROOT/services/base_tcl/sample_apps/SusiService
		+	$ scons WS=off TARG=linux AJ_TCL_ROOT=$AJ_ROOT/core/ajtcl
		+
		+	===Run Sample===
		+	After building, you can get the application binary named '''SusiService''' in ''build'' folder.
		+	Just copy it into your device and execute it!
		+
		+
		+	About verification tools, you can use these two APK on Android system.
		+
		+	[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-controlpanel-service-framework-14.12.00-android-sdk-rel.zip ControlPanelBrowser.apk] is under alljoyn-controlpanel-14.12.00-rel\tools\
		+
		+	[https://allseenalliance.org/releases/alljoyn/14.12/alljoyn-14.12.00b-android-sdk-rel.zip Event_Action_Browser.apk] is under alljoyn-14.12.00b-rel\cpp\samples\eventaction\Android\bin\
		+
		+
		+	Or use AllJoynExplorer on Windows 10.
		+
		+	[https://ms-iot.github.io/content/en-US/win10/AllJoyn.htm IoT Explorer for AllJoyn (AllJoyn Explorer)]

	==Demo==		==Demo==

@@ Line 95: / Line 95: @@
 The following figure shows a hypothetical arrangement of how all of these pieces are related.
-[[File:Alljoyn interface.png]]
+[[File:Alljoyn interface.png|800px]]
 At the center is the dark line representing the AllJoyn bus. The bus has "exits" which are the BusAttachments assigned the unique names :1.1 and :1.4. In the figure, the BusAttachment with the unique name of :1.1 has requested to be known as org.alljoyn.samples.chat.a and has been assigned the corresponding well-known bus name. The "a" has been added to ensure that the bus name is unique.

@@ Line 46: / Line 46: @@
 [[File:alljoyn_session_port.png|500px]]
-===Bus Attachment & BusObject===
+===Bus Attachment & Bus Object===
 AllJoyn applications communicate with one another via the BusObject abstraction. Typically, an application that is offering a service creates a BusObject. Remote applications can effectively remotely open the BusObject and call methods on it, similar to a remote procedure call.
 A BusObject can implement a set of interfaces. Each interface clearly defines a set of ''BusMethods'', ''BusProperties'', and ''BusSignals''. BusMethods allow a remote entity to call a method. BusProperties can be get and set. BusSignals are signals emitted from the application offering the service.
@@ Line 52: / Line 52: @@
 A ProxyBusObject is the object that is created by the remote application to gain access to the BusObject.
-Summing up, an application offering a service implements a BusObject to expose access to its services. A remote application creates a session with this application, and connects to its BusObject on a specific object path by creating a ProxyBusObject. Then, it can call BusMethods, access BusProperties, and receive BusSignals.
+Summing up, an application offering a service implements a BusObject to expose access to its services. A remote application creates a session with this application, and connects to its BusObject on a specific ''Object Path'' by creating a ProxyBusObject. Then, it can call BusMethods, access BusProperties, and receive BusSignals.
 [[File:Alljoyn_bus_attachment.png]]
@@ Line 60: / Line 60: @@
 Prior to session creation, the application can create any number of bus objects and place them at a specific object path. Each bus object can implement a set of interfaces, defined by a set of methods, properties, and signals.
 After the session is created, the remote application will typically communicate with the application by creating a local ProxyBusObject to interact with the BusObject by invoking methods, getting and setting properties, receiving signals.
 ===D-Bus (Distributed Bus)===
 The AllJoyn framework utilizes an easy-to-understand object model and Remote Method Invocation (RMI) mechanism. The AllJoyn model re-implements the wire protocol set forth by the D-Bus specification and extends the D-Bus wire protocol to support distributed devices.
 The following figure shows how the distributed bus may appear to a user of the bus. A component (for example, the Smartphone connection labeled :1.2) can make a procedure call to the component labeled :1.5 on the Linux host without having to worry about the location of that component. The logical distributed bus is actually split up into a number of segments, each running on a different device. The AllJoyn functionality that implements these logical bus segments is called an '''AllJoyn router'''.
 [[File:Alljoyn_dbus.png|400px]]
@@ Line 77: / Line 88: @@
-Here is the workflow diagram for advertisement & discovery. In the AllJoyn bubble diagrams, the connections to the bus are labeled as clients (C) and services (S). The AllJoyn router that implements the core of the distributed bus is labeled (D).
+Here is the workflow diagram for advertisement & discovery.
 [[File:Alljoyn advertisement.png|650px]]
-===Well-Known Name, Interface & Port===
+===Put it all together===
 ==SUSI Alljoyn Service==

← Older revision		Revision as of 02:43, 15 February 2016
Line 77:		Line 77:


−	Here is the workflow diagram for advertisement & discovery.	+	Here is the workflow diagram for advertisement & discovery. In the AllJoyn bubble diagrams, the connections to the bus are labeled as clients (C) and services (S). The AllJoyn router that implements the core of the distributed bus is labeled (D).

	[[File:Alljoyn advertisement.png\|650px]]		[[File:Alljoyn advertisement.png\|650px]]