• System Overview

• P2PBridge: It connects to the same IP subnetwork with XBridges and organizes the P2P substrate with other P2PBridges. We implemented a prototype of P2PBridge on JXTA as a P2P application platform.
• JXME Application (ParticleBrowser): It is an application using JXME, which is an implementation of JXTA on J2ME (Java 2 Micro Edition). We implemented an application called ParticleBrowser that can discover and access desired Particle on PDA.
  

• Proxy: It is a proxy for JXME applications to participate with JXTA P2P substrate, because J2ME can only use HTTP for its communication. It should be specified when a JXME application is firstly executed.
  
• Rendezvous: It works as a rendezvous point for JXTA P2P peers located in different networks. It should be specified when a P2PBridge is firstly executed.
  
• Relay: It is required for JXTA P2P peers behind a firewall to traverse NAT (Network Address Translation) or packet filtering. It should be specified when a P2PBridge located behind a firewall.

• Detect & Publish: A P2PBridge detects a Particle by receiving packets from XBridge and publishes an advertisement that contains attributes (sender Id, location Id, artifact type, etc.) of it to JXTA P2P substrate.
• Node Discovery: P2P Peer (P2PBridges, JXTA/JXME applications) can send query to discover the advertisement of the desired Particle by using an attribute as a query key.
• Remote Access: Once the desired Particle is discovered, it is possible to establish a connection to the corresponding P2PBridge that published the advertisement. After establishing the connection, the P2PBridge forwards data from the Particle to the connected P2P peer.
  
• Inter Sensor Network Communication: If a P2PBridge finds that a received data from a Particle has a ACL tuple that represents the destination of the data, the P2PBridge tries to discover destined Particles and forwards the data to them by establishing connections to the corresponding P2PBridges.

P2PBridge for Particle

• Download

Latest Release (17 Oct. 2005): We newly add a wrapper program (P2PBridgeWrapper) to skip Equiator framework in the package.

• Source code with compiled classes (It is compiled by Java2 SDK 1.4.2 06)
• Source code only (Build tool "ANT" is necessary to compile)

Second Release (26 Aug. 2005):

• Source code with compiled classes (It is compiled by Java2 SDK 1.4.2 06)
• Source code only (Build tool "ANT" is necessary to compile)

First Release (17 Jun. 2005): Expired

• Source code with compiled classes (It is compiled by Java2 SDK 1.4.2 06)
• Source code only (Build tool "ANT" is necessary to compile)
  

• Quick Start (without compile)
  

• At least 2 PCs with Java2 JRE 1.4.2. Each PC should be connected to a different IP subnetwork with others.
  
• Particles
• XBridges

2. Download "Source code with compiled classes".
   
3. Extract the archive wherever you want.
4. Go to "[Installed Directory]/Equator/equip4j/infrastructure/install".
5. Execute "runEquipDataSpace.bat" to run Equip server.
6. Execute "runExporterGUI.bat" to export all components to the server (A warning message for Bluetooth related component might be shown, but you can ignore it).
   
7. Execute "runComponentBrowser.bat" to run component browser.
8. Create one instance of P2PBridge component and two instance of ParticleFactory component as the following screen shot. Please refer this page to know how to use EQUIP Component Browser.
   

9. After creating the ParticleP2PBridge, the following window is appeared to configure JXTA related parameters (only at first time). In basic settings, input proper peer name and its password as you like (ex. "P2PBridge").
   

9. In advanced settings, select trace level. "fatal" shows only critical errors (Recommended). Other settings should be as default.
   

9. In Rendezvous/Relay settings, select "Use a relay" if your PC is connected behind a firewall (Recommended).

9. Press "OK" to start ParticleP2PBridge.
   
10. One ParticleFactory (upper) is used for listening/sending UDP broadcast packet from/to XBridges. Therefore, confirm that the listenport is configured as "5555" and sendport is configured as "5556" as default. Another ParticleFactory (lower) is used for listening/sending UDP broadcast packet from/to Particle dedicated applications, such as Particle Analyzer. Therefore, set the listenport as "5556" and the sendport as "5555". If you do not need to receive/send UDP broadcast packet for the Particle dedicated applications, the latter configuration can be ignored.

2. Create link between ParticleP2PBridge and two ParticleFactories as follows.

• connect "recievedclpacket" of ParticleFactory for Particle (upper) to "clpacketFromXBridge" of ParticleP2PBridge.
• connect "recievedclpacket" of ParticleFactory for Particle application (lower) to "clpacketFromApplication" of ParticleP2PBridge.
• connect "clpacketToApplication" of ParticleP2PBridge to "transmitclpacket" of ParticleFactory for Particle application.
• connect "clpacketToXBridge" of ParticleP2PBridge to "clpacketFromXBridge" of ParticleFactory for Particle .

2. Start both ParticleFactories by setting "true" in startflag. Status becomes "OK", when ParticleFactory becomes to work.
   

• How to Compile/Rebuild from the Source Code
  

1. Confirm that "Java2 JDK 1.4.2" is properly installed to your PC.
   
2. Confirm that "ANT" is properly installed to your PC.
3. Download source file with/without compiled classes.
4. Extract files to wherever you want.
5. Go to " [extract directory]/Equator/equip4j/infrastructure".
6. If you download with compiled classes, perform "ant clean" beforehand.
   
7. Perform "ant" to build.
8. "install" directory is created and it holds all runtime batch files and classes.
   

• Changes
  

• Add particleP2Pbridge component in Equator/equip4j/infrastructure/src/equip/ect/components/
• Extend particleFactory component in Equator/equip4j/infrastructure/src/equip/ect/components/
  
• Add build rules for particleP2Pbridge in Equator/equip4j/infrastructure/build.xml
• Add JXTA libraries to Equator/equip4j/infrastructure/resource/common
  
• Add classpath for JXTA libraries to runExporterGUI.bat in Equator/equip4j/infrastructure/script
  

ParticleBrowser for J2ME

• Download
  

• Source code with compiled classes (It is compiled by Java2 SDK 1.4.2 06)
• Source code only (Build tool "ANT" is necessary to compile)

• How to Compile
  

• How to Configure PDA

1. Prepare PDA with Windows PocketPC 2003.
2. Connect PDA to a network (ex. use "Configuration" "System" "WLAN Manager").
3. Install following utility applications.

• NotePAD to edit shortcut file.
• NetTools to check IP connectivity.

4. Install IBM J9VM as Java Virtual Machine for PDA. It is required to execute the downloaded file on your PC to extract CAB files for PDA.
   
5. In order to emulate J2ME environment on PDA, install me4se.jar in <extract directory of ParticleBrowser>/particle-jxme/lib/ to /My Documents/Java/lib/ of PDA . ME4SE is a wrapper class to run MIDlet applications and this jar file is little modified from original me4se to incorporate the screen height of Window PocketPC.
   
6. Copy particle-jxme.jar, particle-jxme.jad in <extract directory of ParticleBrowser>/particle-jxme/deployed/ to /My Documents/Java/lib/ of PDA.
7. Create shortcut of /Program/J9/PPRO10/j9.exe on PDA.
   
8. Open the shortcut and edit it as follows. In the shortcut on Windows PocketPC, directory of the execution file should be separated by backslash, otherwise use slash. And, absolute path should be used.

• How to run ParticleBrowser on PC

• How to run Proxy on PC

Proxy for JXME is necessary for ParcileBrowser to participate with JXTA P2P substrate. It  is originally included in JXTA source code repository (See JXME page in detail). For easy set up, we  include minimal set of compiled classes and batch files in ParticleBrowser archive.

1. On your PC (It is recommended using another PC to run Proxy than using same PC on which ParticleP2PBridge is running), execute <extract directory of ParticleBrowser>/particle-jxme/rendezvous/runRundezvous.bat to start Proxy.
2. After executing the batch file, JXTA configuration screen is appeared as described above (only at first time).
3. In Basic setting, input proper a peer name and password as you like (ex. "Proxy") as mentioned above.
4. In advanced settings, it requires to check "Act as a JXME proxy" and "Enable Incoming Connections" for HTTP settings. Trace level is recommended to choose as "fatal" to reduce unnecessary logging messages.
   

5. In Rendezvous/Relays setting, it is recommended to choose "use Relay" as mentioned above.
6. Press "OK" to start Proxy.
   

• How to Use Particle Browser
  

• XBridgeGroup: All advertisements of XBridge are published in this group.
  
• ParticleGroup: All advertisements of Particle are published in this group.
• LocationGroup X: All advertisements of XBridge and Particle that have Location ID of "X" are published in this group.
• ArtifactTypeGroup Y: All advertisements of XBridge and Particle that have ArtifactType of "Y" are published in this group.

The next figure illustrates a diagram of ParticleBrowser.

The following process describes how to discover the groups and Paritcles and access discovered Particle.

1. Execute ParticleP2PBridges and Proxy, and check IP address of the Proxy.
2. On PDA, perform ping to the IP address by NetTools to confirm the reachability to Proxy.
3. Start ParticleBrowser by clicking the shortcut icon on PDA.
4. Confirm that the IP address in "Relay host" is correctly configured and then press "OK" button.
   

5. Press "Connect" button to connect Proxy.
   

6. When the application success to connect Proxy, it automatically joins with "netPeerGroup", which is the default group of JXTA. Then, press "Menu" to open menu.

7. In this menu, select "Group List" to discover the dedicated group of this system, called "ParitlceLocationGroup".
   

8. Press "Menu" to open group list menu.
   

9. Select "Search" to discover "ParitlceLocationGroup".
   

10. Press "OK" to perform group discovery, now.
    

11. If "ParticleLocationGroup" is discovered, it appears on the screen. Press "Join" button to join with the group.
    

12. This screen represents that the application now joins with "ParticleLocationGroup". Press "Menu" to perform further group discovery.
    

13. Select "Group List".
    

14. Press "Menu".
    

15. Select "Search".
    

16. When subsidiary groups are discovered, they appear on the screen. Select "ParticleGroup" for example and press "Join" to join the group.
    

17. This screen shows that the application now joins with "ParticleGroup" that holds  advertisements of all Particles in JXTA P2P substrate. Press "Menu" to discover Particles in this group.
    

18. Select "ParticleList".
    

19. This screen will show discovered Particle list in "ParticleGroup". Press "Menu".
    

20. Select "Search".
    

21. Press "OK" to perform discovery.
    

22. Discovered Particles are listed on the screen. Choose appropriate Particle and press "Select".
    

23. Press "Connect" to perform Remote Access to the selected Particle.
    

24. When the connection is establishmed, all data from the selected Particle are forwarded from the corresponding ParticleP2PBridge to this application via Proxy. If you want to stop receiving the data, press "Menu".
    

25. Select "Disconnect" to stop receiving data. In addition, you can try to access other Particles by selecting "Partice List" in this menu.
    

•  Changes from original  ME4SE

• Defects of JXME Application
  

• IMPORTANT: Each discovery (group/particle) should be performed more than once, when it is a first time to access Proxy since it has launched,  because current Proxy can not inform discovered advertisements to the application at first time (it only stores them in its cache). It becomes possible to inform the advertisements after they are cached in Proxy.
  
• The connection between ParticleBrowser and ParticleP2PBridge via Proxy may remain after the disconnection.
• In this system, advertisements are managed by lifetime basis. However, some old advertisements may remain in the cache of Proxy or ParticleP2PBridge. You can delete the cache deleting <extract directory of ParticleBrowser>/rendezvous/.jxta/cf directory. It also requires restarting Proxy or ParticleP2PBridge.
  

• Download

• How to compile

• How to use
  

Appendix

• Location ID

• ACL tuples that specifies destinations
  

• C HE HELLO : 8byte=Particle ID
  
• C EH OLLEH : 8byte=Particle ID
• C TR Triangulation : 8byte=Particle ID
• C SR Set Sync Rate : 8byte=Particle ID, 1byte= data
• C RT Remote Control : 8byte=Particle ID, 1byte= data
• C RR Remote Shutdown : 8byte=Particle ID, 1byte= data
• C FS Field Strength Regulation : 8byte=Particle ID, 1byte= data
• C AD Address Control Field : 8byte=Particle ID

• C RI : 8 byte=Receiver Particle ID
  
• C RL : 44 byte=Receiver Location ID
• C RA : 2 byte=Receiver Artifact Type (3in2)
• C RS : N byte=Receiver Semantic Location Description
• C RS : ? byte=Receiver Geographical Location