[SAMPLE APP][Bluetooth LE Collector] Discovered device's service data acquisition...

Change-Id: I941a8988765337729de159907a83a56e3018b2e1
Signed-off-by: Michal Pawluk <m.pawluk@samsung.com>

diff --git a/org.tizen.sampledescriptions/html/mobile_n/bluetooth_le_collector_sd_mn.htm b/org.tizen.sampledescriptions/html/mobile_n/bluetooth_le_collector_sd_mn.htm
index 8ffa74f..ed6ff6d 100644 (file)
--- a/org.tizen.sampledescriptions/html/mobile_n/bluetooth_le_collector_sd_mn.htm
+++ b/org.tizen.sampledescriptions/html/mobile_n/bluetooth_le_collector_sd_mn.htm
@@ -369,21 +369,12 @@ All the acquired information is binded to the remote device name (<span style="f
 Finally, the user interface is updated with <span style="font-family: Courier New,Courier,monospace">view_main_update_peer_info()</span> function to reflect received data.
 </p>
 
-<h3 id="svc-details">Discovered device's details acquisition and browsing</h3>
+<h3 id="svc-details">Discovered device's service data acquisition</h3>
 
 <p>
-Once the devices are discovered and the list is populated with available advertisers, the user is able to select one from all discovered peers. After selection, the UI is changed to the device's detailed view where the
-following information is displayed:
-       <ul>
-               <li>appearance,</li>
-               <li>manufacturer,</li>
-               <li>TX power,</li>
-               <li>number of provided services,</li>
-               <li>number of provided solicitation services.</li>
-       </ul>
-All the above information is gathered by <span style="font-family: Courier New,Courier,monospace">__bt_le_scan_data_process()</span> function invoked from the
-<span style="font-family: Courier New,Courier,monospace">__bt_le_scan_cb()</span> callback function on scan response message received event (for details see the
-<a href="#dev-discovery">Devices discovery</a> section).
+The device's service data acquisition procedure is very similar to that described in <a href="#dev-details">Discovered device's details acquisition</a> section. The process starts in
+<span style="font-family: Courier New,Courier,monospace">__bt_le_scan_cb()</span> callback function (refer to the <a href="#dev-discovery">Devices discovery</a> section) with the
+<span style="font-family: Courier New,Courier,monospace">__bt_le_scan_data_process()</span> function invocation.
 </p>
 
 <pre class="prettyprint">
@@ -425,9 +416,12 @@ When a scan response message is received, then one has to obtain the sender's na
 it is already registered (<span style="font-family: Courier New,Courier,monospace">__bt_le_is_device_registered()</span>). If a received message concerns the registered and selected device, the
 received data is processed further by <span style="font-family: Courier New,Courier,monospace">__scan_data_process()</span> function. The scan response message may contain the same information set
 as the advertisement message extended with the service/solicitation service data.
-<br>
-This function's implementation is very similar to <span style="font-family: Courier New,Courier,monospace">__adv_data_process()</span> (see the <a href="#dev-discovery">Devices discovery</a> section).
-The only difference concerns the service's data acquisition (<span style="font-family: Courier New,Courier,monospace">bt_le_get_scan_service_data_list()</span>) and its storage in model's structure
+</p>
+
+<p>
+This function's implementation is very similar to <span style="font-family: Courier New,Courier,monospace">__adv_data_process()</span> (see the
+<a href="#dev-details">Discovered device's details acquisition</a> section). The only difference concerns the service's data acquisition
+(<span style="font-family: Courier New,Courier,monospace">bt_le_get_scan_service_data_list()</span>) and its storage in model's structure
 (<span style="font-family: Courier New,Courier,monospace">model_set_device_data()</span>).
 </p>
 
@@ -491,10 +485,15 @@ static void __scan_data_process(bt_adapter_le_device_scan_result_info_s *info, b
 </pre>
 
 <p>
-If the number of services/solicitation services is non-zero, then the 'Check' button in device's detailed view becomes enabled. Once clicked, the popup with a list of all available services/solicitation
-services exposed by the advertiser appears.
-<br>
-All the acquired information is binded to the previously obtained remote device name and stored internally for further use.
+In contrast to <span style="font-family: Courier New,Courier,monospace">__adv_data_process()</span> function (see the <a href="#dev-details">Discovered device's details acquisition</a> section),
+the <span style="font-family: Courier New,Courier,monospace">bt_le_get_scan_<b>{scan_info_name}</b>()</span> functions are invoked to acquire the same set of information as from the advertisement
+message extended with service's data acquisition (<span style="font-family: Courier New,Courier,monospace">bt_le_get_scan_service_data_list()</span>).
+</p>
+
+<p>
+All the acquired information and service's data is binded to the remote device name (<span style="font-family: Courier New,Courier,monospace">model_set_device_info()</span> and
+<span style="font-family: Courier New,Courier,monospace">model_set_device_data()</span>, respectively) previously obtained and referenced by the
+<span style="font-family: Courier New,Courier,monospace">dev_info</span> variable.
 <br>
 Finally, the user interface is updated with <span style="font-family: Courier New,Courier,monospace">view_main_update_peer_info()</span> function to reflect received data.
 </p>