From Mobitouch cube
A node is the logical representation of a physical entity (WLP-500 hot-spot). In the Mobitouch CUBE system a node maps to a WLP-500 unit.
In order to see a node in your system, the node has to be previously activated.
All of the activated nodes are shown in the Node Manager window.
A node has a series of parameters that can be edited to change its behavior.
Editing a Node
To modify the settings of a node just click on the Nodes and zones menu bar item and than on the Nodes and zones manager.
You can select a specific node and than click on Edit node displays the node parameters form you can use to modify any specific node setting.
Node Parameters
The parameters a user can modify in the Edit Node window (from the Nodes and zones manager, select a node and click on Edit).
Not all of the node parameters are shown by default. To edit advanced parameters you need to click the "Enable advanced parameters" check box on the right side of the edit window.
Hereafter the meaning of each parameter is explained.
Basic parameters are shown in bold
Advanced parameters are shown in bold and italic
General Settings
General settings are used to give you information about the node in all the relevant screens of the CMS. These parameters include
- Name: the name of the node
- Description: a brief description field you can use for annotating something about the node you wish to remember (i.e. SIM card code used in GPRS modem, etc...)
- Serial Number: this field is not editable and shows the unique serial number of the node in the Mobitouch CUBE system.
Geo localization
Geo-localization parameters are used by the system to evaluate the positioning on the node. In the future these data will be used to place your nodes on a map and get real-time information in a graphic form.
These parameters are pretty straightforward and do not require an explanation.
- Address
- Zip Code
- City
- Country
Blacklist timing
These parameters are related to Blacklist management on a node-basis:
- Blacklist success time: time to wait before trying to send content for a specific campaign to a mobile phone that received those content yet during a previous connection
- Blacklist reject time: time to wait before trying to send content for a specific campaign to a mobile phone that refused a notification message
- Blacklist transfer failure time: time to wait before trying to send a content for a specific campaign to a mobile phone, that failed in receiving a content
- Blacklist notification message expired time: time to wait before trying to send content for a specific campaign to a mobile phone that let expire a notification message.
- Number of notification messages retries: indicates the number of notification messages retries before the device become blacklisted.
- Number of transfer retries on failure: indicates the number of transfer retries on failure before the device become blacklisted.
- Blacklist monitor devices time: you have to set the time that will elapse before the WLP-C sends the statistics to your monitor device. So if you set 5 minutes it will wait 5 minutes before send another Statistics report to your monitor device.
- Permanent blacklist devices: you can insert one or more Bluetooth Addresses to permanently insert devices in blacklists.
- Blacklist clear before campaign starts: clears blacklists every time a new campaign starts.
- Blacklist persistent enabled: This flag tells the system how to behave when power-off occurs. If this flag is checked, the system periodically saves blacklist data to persistent flash memory (every 5 minutes). If it is not checked, then the system doesn't do this and a power off can clear all blacklists.
- Bluetouch enabled: the Bluetouch option permits to bypass blacklists. If a mobile phone is inside the Bluetouch range, it will receive the content although it is blacklisted.
- Bluetouch RSSI range: the RSSI range of Bluetouch option.
Bluetooth
- Bluetooth sender name: the name displayed on the user mobile phone screen when contacted by the node.
- Bluetooth connections limit (for each transmitter): Sets the limit of simultaneously connected phones for each transmitter
- Bluetooth page timeout : Set the timeout for establish the connection with the phones.
If you set an high value, you'll keep busy a BT connection for more time, also for that ones that will be exipired, so if you have many people in the area with an high timeout value, you'll contact them so slowly. With a low value you'll receive as expired all the slow people.
Bluetooth - Inquiry
The inquiry procedure enables the WLP to discover which devices are in range, a phone can be inquired if it's in the inquiry scan state.
The delay time is chosen by WLP, in the range Min Max, it depends by how many devices the WLP has to serve at the moment.
- Inquiry timeout (sec): Inquiry life time
- Min delay between two inquiries (sec): the minimum pause between two inquiries
- Max delay between two inquiries (sec): the maximum pause between two inquiries
Bluetooth - Authentication
WLP doesn't require a PIN, if the Checkbox is unchecked and the phone (some Samsung ad BlackBerry) ask for a PIN, that mean that this phone require a Bluetooth authentication for the file transfer.
- Always force Bluetooth authentication: with this box enabled the WLP require a PIN for all its connections
- PIN code: when a Phone (or the WLP) requires Authentication, WLP uses this one
Bluetooth - OBEX Push Profile
Pay attention when change this settings!!!
- OBEX connection timeout: The amount of time in seconds for which the WLP will attempt to successfully transmit a file after a phone acceptance.
If you set an an high value, you'll keep busy a connection also for the ones that go through the WLP area, so if you have many people in the area with an high value you'll contact them so slowly. With a low value, all the people that have to accept for every single file, and select where to save it, couldn't have the time to answer.
- OBEX transfer timeout: The amount of time in seconds for which the WLP will attempt to successfully transmit a file after a connection problem.
If you set an high value, you'll keep busy a connection also for the ones that go through the WLP area, so if you have many people in the area with an high value you'll contact them so slowly. If there are any problem with an high values you'll spend a lot of time with transfer that can easily fails, successfully connection usually don't need to high value. With a low value you can have a lot of failure in zones with high noise.
- OBEX transfer MTU: (2048 - 8192): Specifies the MTU of your device, i.e. the maximum length of the packet in bytes it can accept. Defaults to: 8192
You can change this value only if you have particular needs for your "hypothetical not standard application", default works with all phones, so don't change it.
- OBEX transfer delay between two contents: Defaults to: 0
- OBEX push continue on reject: When you accept contents with your phone it will accept all the package, in some Sony Ericsson you have to accept to download files from the WLP, and you have to authorize every single file. With this box enable WLP continue to send next contents to a phone that as accepted a conncetion from the wlp but has negate a contents. With this box unchecked When a phone reject a content, WLP close the connection.
Statistics
The Monitor Device list and the format of the statistics sent to them. It is possible to insert into the system a specific mobile phone bluetooth address as Monitor device. The mobile phones registered as Monitor device won't never receive the contents specified by the active campaigns executed by the node instead they will receive a file containing informations related to statistics and diagnostics of the node.
Scheduler
- Bluetooth RSSI coverage range, the values for the coverage area are far,long,medium and short. Approximately far corresponds to 35 meters, long corresponds to 25 meters, medium corresponds to 15 meters and short corresponds to 5 meters (Please note that the above coverage area estimation can be vary depending on the scenario where the nodes are installed and depending on the mobile phone used to receive the files).
- Scheduler algorithm
There are three different alghoritms to set which mobile phone the node will serve first:
- Standard scheduler (oldest device first): instructs the node to serve the mobile phone which has been in the queue for a longer time;
- Nearest scheduler (nearest device first): instructs the node the serve the nearest mobile phone;
- Fair scheduler (balanced alghoritm): this is a mix of the first two.
Every time there aren't free resources to serve a Mobile phone a queue is created, the position of the queue where to insert the mobile phone waiting to be served depends on the Scheduler algorithm. Basically a mobile phone is inserted in the first place if it's the oldest cellular waiting to be contacted and the Scheduler algorithm property of the node is set to Standard scheduler and is inserted at the first position of the queue if it's the nearest mobile phone and the Scheduler algorithm property of the node is set to Nearest scheduler.
Device Identification
- Fingerprint dump enabled: When you enable this flag when the WLP-C discover a new Phone fingerprint, it will push it to the server.
- Fingerprint match algorithm: Whit the Perfect one you'll receive a specified content on your phone (i.e. whit a Device Identification Campaing) only if the matching of the phone is 100%. Heuristic algorithm works like the Perfect one when he knows a phone, and also when the WLP-C doesn't know with a reasonable certainty which is phone, it tries to assign which is the phone with some accuracy.
- Fingerprint database auto-learning enabled: When you enable this flag when the WLP-C discover an unknown Phone fingerprint, it will push it to the server.
- Fingerprint match threshold (%): You can decide the minimum accuracy for the Heuristic algorithm.
System
- Timezone, the timezone of your country or everywhere the WLP will be used
- Server synchronization frequency, elapsed time between the synchronizations of the node (note that you can force at any time the syncronization process operating on the Reset button).
Editing multiple nodes at the same time
It is possible to edit more than one node at the same time, just select from the Nodes and zones manager window all the nodes you want to configure.
Operating on several nodes won't let you modify the General Information properties of every single node.