That depends on what "side" of GATT link are you looking for;) BLE is asymmetric on pretty much every layer and NUS need GATT Client and GATT Server. ble_nus is GAP Peripheral + GATT Server (usual "embedded" option, that's why it is kind of "default"), ble_nus_c is GAP Central + GATT Client option (usually handled by device with higher power budget = bigger battery).
That depends on what "side" of GATT link are you looking for;) BLE is asymmetric on pretty much every layer and NUS need GATT Client and GATT Server. ble_nus is GAP Peripheral + GATT Server (usual "embedded" option, that's why it is kind of "default"), ble_nus_c is GAP Central + GATT Client option (usually handled by device with higher power budget = bigger battery).
That's a little bit philosophical question, isn't it?;) Nordic UART Service is defined on GATT as far as I understand (that's what BT SIG calls "Service definition") but that's not enough to make it work in real life. For that you need to say which GAP role (Central or Peripheral) hosts which GATT role (Client or Server). Theoretically you can do both combinations but in order to make it 100% work then both sides must do (= whatever GAP role you are you need to implement GATT Client and Server). As I understand Nordic guys in their examples don't go this route - which would probably be wasting of time and effort - but simply say GAP Central always hosts GATT Client which connects to GAP Peripheral and that hosts Nordic UART Service on GATT Server. This is what BT SIG normally calls "GAP Profile" definition (defines both GAP + GATT properties).
Do you have clear understanding what will be both sides of your NUS link and what GAP&GATT properties they support? Also consequences on power consumption and co-existence and interworking with other Profiles and Services (if any of these devices is multiapplicational)?
