LE Central Extended Scan

The ble_bt5_central sample demonstrates how to develop many different Central Role-based applications.

Supported features:

Extended scan for advertising packets on the primary advertising channel (LE 1M PHY or LE Coded PHY).
Scan for a duration or period scan.
Can initiate connection and become a Central role in the link on LE 1M PHY, LE 2M PHY or LE Coded PHY.

Overview

Central device with LE Advertising Extensions can communicate with a device using legacy advertising PDUs or extended advertising PDUs and set the duration of the scan.
If a central device uses LE Advertising Extensions, compatibility with peer devices of different Bluetooth versions is shown as below:

Compatibility of Central Devices with LE Advertising Extensions
Bluetooth 5 Feature	Bluetooth 4.0	Bluetooth 4.1	Bluetooth 4.2	Bluetooth 5.0 (Not Use LE Advertising Extensions)	Bluetooth 5.0 (Use LE Advertising Extensions)
LE Advertising Extensions	Y	Y	Y	Y	Y

Requirements

The sample supports the following development kits:

Development Kits
Hardware Platforms	Board Name
RTL87x2G HDK	RTL87x2G EVB

To quickly set up the development environment, please refer to the detailed instructions provided in Quick Start.

Wiring

Please refer to RTL87x2G EVB Interfaces and Modules in Quick Start.

The sample requires support for user command interface. For specific wiring instructions, please refer to Data UART Connection in User Command Interface.

Configurations

Configurable Items

All contents that can be configured for the sample are in samples\bluetooth\ble_bt5_central\src\app_flags.h, developers can configure according to actual needs.

/** @brief Configure coding scheme of LE Coded PHY: 0 - S = 2, 1 - S = 8 */
 #define LE_CODED_PHY_S8            0
 /** @brief Configure APP LE link number */
 #define APP_MAX_LINKS  1
 /** @brief Configure APP to recombine advertising data: 0 - Disable recombine advertising data feature, 1 - recombine advertising data */
 #define APP_RECOMBINE_ADV_DATA  0

Developers can use APP_RECOMBINE_ADV_DATA to configure the sample to recombine advertising data. The procedure of recombining advertising data is introduced in Recombine advertising data of Code Overview.

Generating System Config File

Developers shall configure the following items through MP Tool:

MP Tool Configuration
Configurable Item	Value
LE Maser Link Num	≥ APP_MAX_LINKS

For more information about MP Tool Configuration, please refer to Generating System Config File in Quick Start.

Building and Downloading

This sample can be found in the SDK folder:

Keil

Project file: samples\bluetooth\ble_bt5_central\proj\rtl87x2g\mdk

GCC

Project file: samples\bluetooth\ble_bt5_central\proj\rtl87x2g\gcc

To build and run the sample, follow the steps listed below:

Open project file.
To build the target, follow the steps listed in the Generating App Image section in Quick Start.
After a successful compilation, the APP bin app_MP_sdk_xxx.bin will be generated in the directory samples\bluetooth\ble_bt5_central\proj\rtl87x2g\mdk\bin.
To download the APP bin into the EVB, follow the steps listed in the MP Tool Download section in Quick Start.
Press the reset button on the EVB to start running.

Experimental Verification

After downloading the sample bin to the EVB, developers can test it using another kit that is running the LE Peripheral Extended ADV sample.

Testing with Another Kit

Prepare two development boards named DUT and Tester respectively, and use Debug Analyzer tool to Log Verification .

Primary Advertising Channel is LE 1M PHY, Secondary Advertising Channel is LE 2M PHY

Preparation Phase

Use MP Tool to set the DUT address to [00:11:22:33:44:92], then build the ble_bt5_central sample and download images into DUT.
First, set the macro definition ADVERTISING_PHY to APP_PRIMARY_1M_SECONDARY_2M. Use MP Tool to set the Tester address to [00:11:22:33:44:91], then build the ble_bt5_peripheral sample and download images into Tester. For more information, please refer to Building and Downloading in LE Peripheral Extended ADV.

For details about how to change the Bluetooth Address, please refer to Generating System Config File in Quick Start.

Testing Phase

Press the reset button on Tester and Tester will start sending connectable undirected advertising events.

If the advertisement is successfully enabled, the following Debug Analyzer log will be printed. If developers do not see the following log, it means that the advertisement failed to start. Please check if the software and hardware environment is configured correctly.
[APP] !**GAP_MSG_LE_EXT_ADV_ENABLE:cause 0x0
[APP] !**app_handle_ext_adv_state_evt: adv_handle = 0 oldState = 1
[APP] !**app_handle_ext_adv_state_evt: adv_handle = 0 newState = 2
[APP] !**EXT_ADV_STATE_ADVERTISING: adv_handle 0, cause 0x0

Press the reset button on DUT and developers can enter the user command in the serial port assistant tool on the PC.

If the DUT successfully boots up and the serial port assistant tool configuration is successful, developers will see the following log. The serial port assistant tool will display the local address. If developers do not see the following log, please check if the software and hardware environment is configured correctly.
local bd addr: xx:xx:xx:xx:xx:xx
One link test flow is shown as below:

Step

DUT User Command

Description

DUT Log

1

escan 2 5

DUT scan mode is set to 2, continue scanning until duration has expired. Scan PHYs are set to 5 (LE 1M PHY and LE Coded PHY). The sample starts extended scanning for duration, and examines information on nearby LE devices whose primary advertising channel is LE 1M PHY or LE Coded PHY.

Serial port assistant tool shows:

GAP scan start

2

stopescan

DUT stops extended scanning.

Serial port assistant tool shows:

GAP scan stop

3

showdev

Show scan device list.

Serial port assistant tool shows:

dev list

……

RemoteBd[8] = [00:11:22:33:44:91]

……

4

condev 8 x001

Scan connectable advertising events on LE 1M PHY, and initiate connection. Secondary advertising channel is LE 2M PHY, and then TX PHY type and RX PHY type are LE 2M PHY.

Serial port assistant tool shows:

Connected success conn_id 0, tx_phy 2, rx_phy 2

5

showcon

Show connection information.

Serial port assistant tool shows:

conn_id 0 state 0x00000002 role 1

RemoteBd = [00:11:22:33:44:91] type = 0

active link num 1, idle link num 0

6

disc 0

Disconnect with Tester.

Serial port assistant tool shows:

Disconnect conn_id 0, dis_cause 0x00000116

7

condev 8 x001

Reconnect with Tester.

Serial port assistant tool shows:

Connected success conn_id 0, tx_phy 2, rx_phy 2

In the above Step 2, when the macro definition APP_RECOMBINE_ADV_DATA is set to 1, the first advertising report from Tester is shown as below. The advertising report indicates that Tester sends connectable undirected advertising with extended advertising PDUs, and the primary advertising PHY is LE 1M PHY, the secondary advertising PHY is LE 2M PHY. Since there is more data to come, the DUT starts recombination and waits for more data.

[APP] app_gap_callback: cb_type = 0x50

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:connectable 1, scannable 0, direct 0, scan response 0, legacy 0, data status 0x1

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:event_type 0x1, bd_addr 00::11::22::33::44::00, addr_type 0, rssi -45, data_len 229

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:primary_phy 1, secondary_phy 2, adv_sid 0, tx_power 127, peri_adv_interval 0

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:direct_addr_type 0x0, direct_addr 00::00::00::00::00::00

[APP] !**app_handle_ext_adv_report: Old ext_adv_data->flag is 0, data status is 0x1

[APP] !**app_handle_ext_adv_report:First Data from bd_addr 00::11::22::33::44::00, data length is 229, and waiting more data

[APP] !**app_handle_ext_adv_report: New ext_adv_data->flag is 1

The last advertising report from Tester is shown below. The advertising report indicates that the data is complete. DUT completes the recombination, the length of advertising data received from Tester is 245 bytes.

[APP] app_gap_callback: cb_type = 0x50

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:connectable 1, scannable 0, direct 0, scan response 0, legacy 0, data status 0x0

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:event_type 0x1, bd_addr 00::11::22::33::44::00, addr_type 0, rssi -45, data_len 16

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:primary_phy 1, secondary_phy 2, adv_sid 0, tx_power 127, peri_adv_interval 0

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:direct_addr_type 0x0, direct_addr 00::00::00::00::00::00

[APP] !**app_handle_ext_adv_report: Old ext_adv_data->flag is 1, data status is 0x0

[APP] !**app_handle_ext_adv_report: Data from bd_addr 00::11::22::33::44::00 is complete, event type is 0x1, total data length is 245

[APP] !**app_handle_ext_adv_report: First five datas are 0x2, 0x1, 0x5, 0x13, 0x9

[APP] !**app_handle_ext_adv_report: Last five datas are 0xd5, 0xd6, 0xd7, 0xd8, 0xd9

[APP] !**app_handle_ext_adv_report: New ext_adv_data->flag is 0

Primary Advertising Channel is LE Coded PHY, Secondary Advertising Channel is LE Coded PHY

Preparation Phase

Use MP Tool to set DUT address to [00:11:22:33:44:92], and then build the ble_bt5_central sample, and download images into DUT.
Firstly, set macro definition ADVERTISING_PHY to APP_PRIMARY_CODED_SECONDARY_CODED. Use MP Tool to set Tester address to [00:11:22:33:44:91], and then build the ble_bt5_peripheral sample, and download images into Tester. For more information, please refer to Building and Downloading in LE Peripheral Extended ADV.

For details about how to change the Bluetooth Address, please refer to Generating System Config File in Quick Start.

Testing Phase

Press the reset button on Tester and Tester will start sending connectable undirected advertising events.

If the advertisement is successfully enabled, the following Debug Analyzer log will be printed. If developers do not see the following log, it means that the advertisement failed to start. Please check if the software and hardware environment is configured correctly.
[APP] !**GAP_MSG_LE_EXT_ADV_ENABLE:cause 0x0
[APP] !**app_handle_ext_adv_state_evt: adv_handle = 0 oldState = 1
[APP] !**app_handle_ext_adv_state_evt: adv_handle = 0 newState = 2
[APP] !**EXT_ADV_STATE_ADVERTISING: adv_handle 0, cause 0x0

Press the reset button on DUT and developers can enter the user command in the serial port assistant tool on the PC.

If the DUT successfully boots up and the serial port assistant tool configuration is successful, developers will see the following log. The serial port assistant tool will display the local address. If developers do not see the following log, please check if the software and hardware environment is configured correctly.
local bd addr: xx:xx:xx:xx:xx:xx
One link test flow is shown below:

Step

DUT User Command

Description

DUT Log

1

escan 0 5

DUT scan mode is set to 0, continuing scanning until scanning is disabled. Scan PHYs is set to 5 (LE 1M PHY and class LE Coded PHY). Start extended scanning and view information on a LE device nearby whose primary advertising channel is LE 1M PHY or LE Coded PHY.

Serial port assistant tool shows:

GAP scan start

2

stopescan

DUT stops extended scanning.

Serial port assistant tool shows:

GAP scan stop

3

showdev

Show scan device list.

Serial port assistant tool shows:

dev list

……

RemoteBd[3] = [47:78:39:48:32:1a]

RemoteBd[4] = [00:11:22:33:44:91]

4

condev 4 x100

Scan connectable advertising events on LE Coded PHY, and initiate connection. Secondary advertising channel is LE Coded PHY, and then TX PHY type and RX PHY type are LE Coded PHY.

Serial port assistant tool shows:

Connected success conn_id 0, tx_phy 3, rx_phy 3

5

showcon

Show connection information.

Serial port assistant tool shows:

ShowCon conn_id 0 state 0x00000002 role 1

RemoteBd = [00:11:22:33:44:91] type = 0

active link num 1, idle link num 0

6

disc 0

Disconnect with Tester.

Serial port assistant tool shows:

Disconnect conn_id 0, dis_cause 0x00000116

7

condev 4 x100

Reconnect with Tester.

Serial port assistant tool shows:

Connected success conn_id 0, tx_phy 3, rx_phy 3

In Step 2, when the macro definition APP_RECOMBINE_ADV_DATA is set to 1, the first advertising report from Tester is shown below. The advertising report indicates that Tester sends connectable undirected advertising with extended advertising PDUs, and the primary advertising PHY is LE Coded PHY, the secondary advertising PHY is LE Coded PHY. Since there is more data to come, DUT starts the recombination and waits for more data.

[APP] app_gap_callback: cb_type = 0x50

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:connectable 1, scannable 0, direct 0, scan response 0, legacy 0, data status 0x1

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:event_type 0x1, bd_addr 00::11::22::33::44::00, addr_type 0, rssi -41, data_len 229

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:primary_phy 3, secondary_phy 3, adv_sid 0, tx_power 127, peri_adv_interval 0

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:direct_addr_type 0x0, direct_addr 00::00::00::00::00::00

[APP] !**app_handle_ext_adv_report: Old ext_adv_data->flag is 0, data status is 0x1

[APP] !**app_handle_ext_adv_report:First Data from bd_addr 00::11::22::33::44::00, data length is 229, and waiting more data

[APP] !**app_handle_ext_adv_report: New ext_adv_data->flag is 1

The last advertising report from Tester is shown below. The advertising report indicates that the data is complete. The DUT completes the recombination, the length of advertising data received from Tester is 245 bytes:

[APP] app_gap_callback: cb_type = 0x50

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:connectable 1, scannable 0, direct 0, scan response 0, legacy 0, data status 0x0

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:event_type 0x1, bd_addr 00::11::22::33::44::00, addr_type 0, rssi -41, data_len 16

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:primary_phy 3, secondary_phy 3, adv_sid 0, tx_power 127, peri_adv_interval 0

[APP] !**GAP_MSG_LE_EXT_ADV_REPORT_INFO:direct_addr_type 0x0, direct_addr 00::00::00::00::00::00

[APP] !**app_handle_ext_adv_report: Old ext_adv_data->flag is 1, data status is 0x0

Code Overview

This chapter will be introduced according to the following several parts:

The directories of the project and source code files will be introduced in chapter Source Code Directory.
The Bluetooth Host will be introduced in chapter Bluetooth Host Overview.
The main function and configurable GAP parameters of this sample will be introduced in chapter Initialization.
The GAP message handler of this sample will be introduced in chapter GAP Message Handler.
The GAP callback handler of this sample will be introduced in chapter GAP Callback Handler.
The procedure of recombining advertising data will be introduced in chapter Recombine Advertising Data.

Source Code Directory

Project directory: samples\bluetooth\ble_bt5_central\proj.
Source code directory: samples\bluetooth\ble_bt5_central\src.

Source files in ble_bt5_central sample project are currently categorized into several groups as below.

└── Project: bt5_central
    └── secure_only_app
        └── Device                   includes startup code
        ├── CMSE Library             Non-secure callable library
        ├── Lib                      includes all binary symbol files that user application is built on
            ├── ROM_NS.lib
            └── lowerstack.lib
            └── rtl87x2g_sdk.lib
            └── gap_utils.lib
        ├── peripheral               includes all peripheral drivers and module code used by the application
        ├── Profile                  includes LE profiles or services used by the sample application
        └── APP                      includes the ble_bt5_central user application implementation
            ├── app_task.c
            ├── main.c
            ├── bt5_central_app.c
            ├── link_mgr.c
            ├── user_cmd.c
            ├── data_uart.c
            └── data_cmd_parse.c

The sample uses default GAP LIB that matches with bt_host_0_0, please refer to Usage of GAP LIB in Host Image for more information.

Bluetooth Host Overview

The sample uses default Bluetooth Host image in bt_host_0_0, please refer to Host Image for more information.

For the details of bluetooth technology features supported by the Bluetooth Host, please refer to the file bin\rtl87x2g\bt_host_image\bt_host_0_0\bt_host_config.h.

Initialization

main() function is invoked when the EVB is powered on and the chip is reset, and it performs the following initialization functions:

int main(void)
{
   board_init();
   le_gap_init(APP_MAX_LINKS);
   gap_lib_init();
   app_le_gap_init();
   pwr_mgr_init();
   task_init();
   os_sched_start();

   return 0;
 }

le_gap_init() function is used to initialize GAP and configure link number.
app_le_gap_init() function is used to initialize the GAP parameters, developers can configure the following parameters: Device name and device appearance, GAP Bond Manager parameters, LE Advertising Extensions parameters（please refer to the chapter Configure Device Name and Device Appearance, Configure Bond Manager Parameters, Configure LE Advertising Extensions Parameters, Configure Other Parameters of LE Host).

void app_le_gap_init(void)
{
   /* Device name and device appearance */
   ......

   /* GAP Bond Manager parameters */
   ......

   /* LE Advertising Extensions parameters */
   bool use_extended = true;

   /* Allocate memory for recombining advertising data */
#if APP_RECOMBINE_ADV_DATA
   ext_adv_data = os_mem_zalloc(RAM_TYPE_DATA_ON, sizeof(T_EXT_ADV_DATA));
   ext_adv_data->flag = false;
#endif

   le_set_gap_param(GAP_PARAM_DEFAULT_DATA_LEN_MAX_TX_OCTETS, sizeof(max_data_len_tx_oct),
                   &max_data_len_tx_oct);
   le_set_gap_param(GAP_PARAM_DEFAULT_DATA_LEN_MAX_TX_TIME, sizeof(max_data_len_tx_time),
                   &max_data_len_tx_time);

   /* Set device name and device appearance */
   le_set_gap_param(GAP_PARAM_DEVICE_NAME, GAP_DEVICE_NAME_LEN, device_name);
   le_set_gap_param(GAP_PARAM_APPEARANCE, sizeof(appearance), &appearance);

   /* Setup the GAP Bond Manager */
   gap_set_param(GAP_PARAM_BOND_PAIRING_MODE, sizeof(auth_pair_mode), &auth_pair_mode);
   gap_set_param(GAP_PARAM_BOND_AUTHEN_REQUIREMENTS_FLAGS, sizeof(auth_flags), &auth_flags);
   gap_set_param(GAP_PARAM_BOND_IO_CAPABILITIES, sizeof(auth_io_cap), &auth_io_cap);
   gap_set_param(GAP_PARAM_BOND_OOB_ENABLED, sizeof(auth_oob), &auth_oob);
   le_bond_set_param(GAP_PARAM_BOND_FIXED_PASSKEY, sizeof(auth_fix_passkey), &auth_fix_passkey);
   le_bond_set_param(GAP_PARAM_BOND_FIXED_PASSKEY_ENABLE, sizeof(auth_use_fix_passkey),
                     &auth_use_fix_passkey);
   le_bond_set_param(GAP_PARAM_BOND_SEC_REQ_REQUIREMENT, sizeof(auth_sec_req_flags),
                     &auth_sec_req_flags);

   /* Use LE Advertising Extensions */
   le_set_gap_param(GAP_PARAM_USE_EXTENDED_ADV, sizeof(use_extended), &use_extended);

   /* Register gap message callback */
   le_register_app_cb(app_gap_callback);
}

More information on LE GAP initialization and startup flow can be found in the chapter GAP Parameters Initialization of LE Host.

GAP Message Handler

app_handle_gap_msg() function is invoked whenever a GAP message is received from the Bluetooth Host. More information on GAP messages can be found in the chapter Bluetooth LE GAP Message of LE Host.

When the message GAP_MSG_LE_CONN_STATE_CHANGE is received, APP will update link state.

void app_handle_conn_state_evt(uint8_t conn_id, T_GAP_CONN_STATE new_state, uint16_t disc_cause)
{
   APP_PRINT_INFO4("app_handle_conn_state_evt: conn_id %d, conn_state(%d -> %d), disc_cause 0x%x",
                   conn_id, gap_conn_state, new_state, disc_cause);
   switch (new_state)
   {
   case GAP_CONN_STATE_DISCONNECTED:
       {
           if ((disc_cause != (HCI_ERR | HCI_ERR_REMOTE_USER_TERMINATE))
               && (disc_cause != (HCI_ERR | HCI_ERR_LOCAL_HOST_TERMINATE)))
           {
               APP_PRINT_ERROR1("app_handle_conn_state_evt: connection lost cause 0x%x", disc_cause);
           }
       }
       data_uart_print("Disconnect conn_id %d, dis_cause 0x%x\r\n", conn_id, disc_cause);
       break;
   case GAP_CONN_STATE_CONNECTED:
       {
           uint8_t tx_phy;
           uint8_t rx_phy;
           uint16_t conn_interval;
           uint16_t conn_latency;
           uint16_t conn_supervision_timeout;
           uint8_t  remote_bd[6];
           T_GAP_REMOTE_ADDR_TYPE remote_bd_type;
           le_get_conn_param(GAP_PARAM_CONN_INTERVAL, &conn_interval, conn_id);
           le_get_conn_param(GAP_PARAM_CONN_LATENCY, &conn_latency, conn_id);
           le_get_conn_param(GAP_PARAM_CONN_TIMEOUT, &conn_supervision_timeout, conn_id);
           le_get_conn_addr(conn_id, remote_bd, (uint8_t *)&remote_bd_type);
           APP_PRINT_INFO5("GAP_CONN_STATE_CONNECTED:remote_bd %s, remote_addr_type %d, conn_interval 0x%x, conn_latency 0x%x, conn_supervision_timeout 0x%x",
                           TRACE_BDADDR(remote_bd), remote_bd_type,
                           conn_interval, conn_latency, conn_supervision_timeout);

           le_get_conn_param(GAP_PARAM_CONN_TX_PHY_TYPE, &tx_phy, conn_id);
           le_get_conn_param(GAP_PARAM_CONN_RX_PHY_TYPE, &rx_phy, conn_id);
           data_uart_print("Connected success conn_id %d, tx_phy %d, rx_phy %d\r\n", conn_id, tx_phy, rx_phy);
       }
       break;
   default:
       break;
   }
   gap_conn_state = new_state;
 }

GAP Callback Handler

app_gap_callback() function is used to handle GAP callback messages. More information on GAP callback can be found in the chapter Bluetooth LE GAP Callback of LE Host.

If the device starts extended scanning and receives advertising data or scan response data, the GAP Layer will use GAP_MSG_LE_EXT_ADV_REPORT_INFO message to inform the application. Sample code is listed below:

T_APP_RESULT app_gap_callback(uint8_t cb_type, void *p_cb_data)
{
   T_APP_RESULT result = APP_RESULT_SUCCESS;
   T_LE_CB_DATA *p_data = (T_LE_CB_DATA *)p_cb_data;

   APP_PRINT_TRACE1("app_gap_callback: cb_type = 0x%x", cb_type);

   switch (cb_type)
   {
   case GAP_MSG_LE_EXT_ADV_REPORT_INFO:
      ......
      link_mgr_add_device(p_data->p_le_ext_adv_report_info->bd_addr,
                           p_data->p_le_ext_adv_report_info->addr_type);

#if APP_RECOMBINE_ADV_DATA
      if (!(p_data->p_le_ext_adv_report_info->event_type & GAP_EXT_ADV_REPORT_BIT_USE_LEGACY_ADV))
      {
            /* If the advertisement uses extended advertising PDUs, recombine advertising data. */
            app_handle_ext_adv_report(p_data->p_le_ext_adv_report_info->event_type,
                                    p_data->p_le_ext_adv_report_info->data_status, p_data->p_le_ext_adv_report_info->bd_addr,
                                    p_data->p_le_ext_adv_report_info->data_len, p_data->p_le_ext_adv_report_info->p_data);
      }
#endif
      break;
   ......
}

Recombine Advertising Data

Recombination of advertising data implements a recombination for one advertising data or scan response data, and recombined advertising data is deleted before the next recombination. The process of recombination can be used as a framework for recombining multi-advertising data at a time.

Memory for recombining advertising data is allocated in GAP Initialization:

void app_le_gap_init(void)
{
   ......
   /* Allocate memory for recombining advertising data */
#if APP_RECOMBINE_ADV_DATA
   ext_adv_data = os_mem_zalloc(RAM_TYPE_DATA_ON, sizeof(T_EXT_ADV_DATA));
   ext_adv_data->flag = false;
#endif
   ......
}
//Message data structure is T_EXT_ADV_DATA.
typedef struct
{
   uint8_t      bd_addr[GAP_BD_ADDR_LEN];           /**< remote BD */
   bool
   flag;                               /**< flag of recombining advertising data, true: recombining, false: waiting extended advertising PDUs */
   uint16_t     event_type;                         /**< advertising event type */
   uint16_t     data_len;                           /**< length of recombined advertising data */
   uint8_t      p_data[APP_MAX_EXT_ADV_TOTAL_LEN];  /**< recombined advertising data */
} T_EXT_ADV_DATA;

ble_bt5_peripheral sample handles GAP_MSG_LE_EXT_ADV_REPORT_INFO message which indicates the receipt of the advertising data or scan response data in app_gap_callback(). For more information, please refer to GAP Callback Handler.

If the extended advertising report indicates using extended advertising PDU, APP calls app_handle_ext_adv_report() function to recombine advertising data. The following sections describe the recombination of advertising data.

GAP_EXT_ADV_EVT_DATA_STATUS_COMPLETE

GAP_EXT_ADV_EVT_DATA_STATUS_COMPLETE indicates that the data is complete. The process of advertising report with data status GAP_EXT_ADV_EVT_DATA_STATUS_COMPLETE is shown below:

GAP_EXT_ADV_EVT_DATA_STATUS_MORE

GAP_EXT_ADV_EVT_DATA_STATUS_MORE indicates that the data is incomplete, and more data will be received. The process of advertising report with data status GAP_EXT_ADV_EVT_DATA_STATUS_MORE is shown below

After processing the advertising report with GAP_EXT_ADV_EVT_DATA_STATUS_MORE, APP waits for the advertising report to complete the recombination. The last advertising report with GAP_EXT_ADV_EVT_DATA_STATUS_COMPLETE indicates that the recombination process is completed.

GAP_EXT_ADV_EVT_DATA_STATUS_TRUNCATED

GAP_EXT_ADV_EVT_DATA_STATUS_TRUNCATED indicates that the data is incomplete, data truncated, and no more data to come. If advertising report with truncated data is the expected report, APP will terminate the current recombination by resetting recombination parameters and wait for advertising report to start next recombination.