Sample program showing how to connect GR-PEACH into Watson IoT through mbed Connector and Watson's Connector Bridge

Dependencies:   AsciiFont DisplayApp GR-PEACH_video LCD_shield_config LWIPBP3595Interface_STA_for_mbed-os USBDevice

Overview

This sample program shows how to connect GR-PEACH into Watson IoT through mbed Connector and Watson's Connector Bridge. Note that this program is derived from https://github.com/ARMmbed/mbed-ethernet-sample-techcon2016.

In this program, at first, the barcode data input from camera is decoded on GR-PEACH using ZXing which is an open-source, multi-format 1D/2D barcode image processing library. Then, the decoded string is sent to Watson IoT via mbed Device Connector and Watson's Connector Bridge. At last, the delivered string is confirmed via NodeRED flow.

Required hardware

Application setup

  1. Select the connection type. For details, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Connection-type.
  2. Set the client credentials. For details, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Client-credentials.
  3. Change Ethernet settings. For details, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Ethernet-settings.
  4. Change Wifi settings. For details, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Wifi-settings.

Building this sample program

  1. Import this sample program onto mbed Compiler.
  2. Configure this sample program in accordance with Application setup.
  3. Compile the example on mbed Compiler and download the resultant binary file.
  4. Plug the Ethernet cable into GR-PEACH if you are using Ethernet mode. /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen7.png
  5. Plug the micro-USB cable into the OpenSDA port with lies on the next to the RESET button.
  6. Copy the binary previously downloaded to your PC to GR-PEACH to flash this sample program. When the copy is successfully completed, the board is ready to work.
  7. Press the RESET button on the board to run this sample program.
  8. For verification, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Monitoring-the-application.

Application resources

This sample program exposes two resources listed below:

  1. /311/0/5850 : Trigger to toggle LED on GR-PEACH (PUT). When "1" is sent to this resource by PUT method, LED should be turned off. Otherwise, LED should be turned on.
  2. /888/0/7700: Decode result of barcode data input from camera (GET)

Setup of Watson IoT

  1. You should create Watson IoT Instance by the following procedure:
    • Login IBM Bluemix from https://console.ng.bluemix.net/ and login it.
    • Select Services as follows: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen6.png
    • Select Internet of Things" as follows: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen7_1.png
    • Press Get Started as follows: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen8.png
    • Configure Watson IoT Instance
      • Leave unbound /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen9.png
      • Select the Free plan, then click Create /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen10.png

  2. You should create Watson IoT Application Credentials Once you successfully create Watson IoT Instance, you should see the following Watson IoT dashboard: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen11.png
    • On dashboard, launch the Connect your devices dashboard /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen12.png
    • Click APPS /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen13.png
    • Click Generate API Key /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen14_1.png
    • Record the API Key and Authenticatoin Token. Then click Generate after adding a comment /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen15.png Note that these two values will be needed in the later step.
  3. Watson IoT NodeRED Application should be created in accordance with the following procedure:
    • Go back to your Bluemix Dashboard: https://console.ng.bluemix.net
    • Click Create Application /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen16.png
    • Select Node-RED Starter /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen17.png
    • Enter a unique App name and Click Create /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen18.png
    • Application will Stage after a few minutes
    • Application will report app is running when the staging has completed
  4. Watson NodeRED Application should be binded to Watson IoT instance
    • You can now see the dashboard below: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen19.png
    • Click Connections. Then, press Connect Existing /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen20.png
    • Click on Watson IoT Instance badge. Then, press Connect /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen21.png
    • NodeRED application will restage. This will take a while. Please wait for Your app is running state /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen22.png /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen23.png
  5. You should acquire mbed Device Connector DOMAIN value
    • Go to the mbed Device Connector Dashboard: https://connector.mbed.com and log in /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen41.png
    • Select Access Key in order to create a new token /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen42.png
    • Click CREATE NEW ACCESS KEY and enter a unique name. Then, push ADD bution /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen43.png
    • an API token is generated. Need to save the generated string for later steps /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen44.png
  1. You should configure Watson IoT ARM mbed Connector Bridge
    • Go back to the Watson IoT Dashboard and select Extensions /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen24.png
    • Press Add Extension /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen25.png
    • Add ARM mbed Connector /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen26_1.png
    • Setup the bridge /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen27.png
    • Enter your Connector API Token to Access Key and MBED_DOMAIN to Domain Id, respectively. Then, click Check Connection /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen28.png
    • If the connection is successfully established, you can see Connection Established. Then, press Done /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen29.png
  2. NodeRED Flow Example should be imported
    • Open NODEFLOW_GR-PEACH.txt
    • Navigate to the URL that you recorded earlier for your Watson IoT NodeRED Application (i.e. http://<app name>.mybluemix.net) and Select Go to your NodeRED flow editor /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen30.png
    • Select menu, Import and Clipboard /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen31.png
    • Paste the entire contents of JSON code described in NODEFLOW_GR-PEACH.txt and click Import /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen32.png
  3. Watson IoT Application Node Flow should be configured
    • Double-click input node and link them to your Watson IoT instance. /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen33.png
    • Click on the edit button /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen34.png
    • First enter arbitrary name. Then, Watson API Key and Watson Auth Token previously acquired. Finally, press Add to save /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen35.png
    • Enter MBED_ENDPOINT_NAME in security.h as Device ID. Then, press Done to save /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen36.png
    • Double-click output node /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen37.png
    • Edit API Key and Device Id in the same manner as that for input node
    • Click LED OFF and LED ON node and replace MBED_ENDPOINT_NAME_GOES_HERE with MBED_ENDPOINT_NAME as shown below: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen38.png
    • Click Deproy to deploy NodeRED application /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen39.png
  4. Invoke sample program
    • Press the reset button on GR-PEACH
    • The decode result of barcode data should be shown in debug window /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen40_1.png
    • Also, you can toggle LED by clicking Turn LED OFF and Turn LED ON injection node /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen40_2.png
Committer:
Osamu Nakamura
Date:
Thu Nov 24 13:59:16 2016 +0900
Revision:
0:ad834d403a8c
Initial Commit

Who changed what in which revision?

UserRevisionLine numberNew contents of line
Osamu Nakamura 0:ad834d403a8c 1 /**
Osamu Nakamura 0:ad834d403a8c 2 * @file Endpoint.h
Osamu Nakamura 0:ad834d403a8c 3 * @brief mbed CoAP Endpoint base class
Osamu Nakamura 0:ad834d403a8c 4 * @author Doug Anson/Chris Paola
Osamu Nakamura 0:ad834d403a8c 5 * @version 1.0
Osamu Nakamura 0:ad834d403a8c 6 * @see
Osamu Nakamura 0:ad834d403a8c 7 *
Osamu Nakamura 0:ad834d403a8c 8 * Copyright (c) 2014
Osamu Nakamura 0:ad834d403a8c 9 *
Osamu Nakamura 0:ad834d403a8c 10 * Licensed under the Apache License, Version 2.0 (the "License");
Osamu Nakamura 0:ad834d403a8c 11 * you may not use this file except in compliance with the License.
Osamu Nakamura 0:ad834d403a8c 12 * You may obtain a copy of the License at
Osamu Nakamura 0:ad834d403a8c 13 *
Osamu Nakamura 0:ad834d403a8c 14 * http://www.apache.org/licenses/LICENSE-2.0
Osamu Nakamura 0:ad834d403a8c 15 *
Osamu Nakamura 0:ad834d403a8c 16 * Unless required by applicable law or agreed to in writing, software
Osamu Nakamura 0:ad834d403a8c 17 * distributed under the License is distributed on an "AS IS" BASIS,
Osamu Nakamura 0:ad834d403a8c 18 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
Osamu Nakamura 0:ad834d403a8c 19 * See the License for the specific language governing permissions and
Osamu Nakamura 0:ad834d403a8c 20 * limitations under the License.
Osamu Nakamura 0:ad834d403a8c 21 */
Osamu Nakamura 0:ad834d403a8c 22
Osamu Nakamura 0:ad834d403a8c 23 #ifndef __CONNECTOR_ENDPOINT_H__
Osamu Nakamura 0:ad834d403a8c 24 #define __CONNECTOR_ENDPOINT_H__
Osamu Nakamura 0:ad834d403a8c 25
Osamu Nakamura 0:ad834d403a8c 26 // mbed-client support
Osamu Nakamura 0:ad834d403a8c 27 #include "mbed-client/m2minterfacefactory.h"
Osamu Nakamura 0:ad834d403a8c 28 #include "mbed-client/m2minterfaceobserver.h"
Osamu Nakamura 0:ad834d403a8c 29 #include "mbed-client/m2minterface.h"
Osamu Nakamura 0:ad834d403a8c 30 #include "mbed-client/m2mobjectinstance.h"
Osamu Nakamura 0:ad834d403a8c 31 #include "mbed-client/m2mresource.h"
Osamu Nakamura 0:ad834d403a8c 32 #include "mbed-client/m2mdevice.h"
Osamu Nakamura 0:ad834d403a8c 33 #include "mbed-client/m2mfirmware.h"
Osamu Nakamura 0:ad834d403a8c 34
Osamu Nakamura 0:ad834d403a8c 35 // Support for Logging/Debug output
Osamu Nakamura 0:ad834d403a8c 36 #include "mbed-connector-interface/Logger.h"
Osamu Nakamura 0:ad834d403a8c 37
Osamu Nakamura 0:ad834d403a8c 38 // Options support
Osamu Nakamura 0:ad834d403a8c 39 #include "mbed-connector-interface/Options.h"
Osamu Nakamura 0:ad834d403a8c 40
Osamu Nakamura 0:ad834d403a8c 41 // ConnectionStatusInterface support
Osamu Nakamura 0:ad834d403a8c 42 #include "mbed-connector-interface/ConnectionStatusInterface.h"
Osamu Nakamura 0:ad834d403a8c 43
Osamu Nakamura 0:ad834d403a8c 44 // ObjectInstanceManager support
Osamu Nakamura 0:ad834d403a8c 45 #include "mbed-connector-interface/ObjectInstanceManager.h"
Osamu Nakamura 0:ad834d403a8c 46
Osamu Nakamura 0:ad834d403a8c 47 // Connector namespace
Osamu Nakamura 0:ad834d403a8c 48 namespace Connector {
Osamu Nakamura 0:ad834d403a8c 49
Osamu Nakamura 0:ad834d403a8c 50 /** Endpoint class
Osamu Nakamura 0:ad834d403a8c 51 */
Osamu Nakamura 0:ad834d403a8c 52 class Endpoint : public M2MInterfaceObserver {
Osamu Nakamura 0:ad834d403a8c 53
Osamu Nakamura 0:ad834d403a8c 54 public:
Osamu Nakamura 0:ad834d403a8c 55 /**
Osamu Nakamura 0:ad834d403a8c 56 Default Constructor
Osamu Nakamura 0:ad834d403a8c 57 */
Osamu Nakamura 0:ad834d403a8c 58 Endpoint(const Logger *logger,const Options *ob);
Osamu Nakamura 0:ad834d403a8c 59
Osamu Nakamura 0:ad834d403a8c 60 /**
Osamu Nakamura 0:ad834d403a8c 61 Copy Constructor
Osamu Nakamura 0:ad834d403a8c 62 @param ob input endpoint instance to deep copy
Osamu Nakamura 0:ad834d403a8c 63 */
Osamu Nakamura 0:ad834d403a8c 64 Endpoint(const Endpoint &ep);
Osamu Nakamura 0:ad834d403a8c 65
Osamu Nakamura 0:ad834d403a8c 66 /**
Osamu Nakamura 0:ad834d403a8c 67 Destructor
Osamu Nakamura 0:ad834d403a8c 68 */
Osamu Nakamura 0:ad834d403a8c 69 virtual ~Endpoint();
Osamu Nakamura 0:ad834d403a8c 70
Osamu Nakamura 0:ad834d403a8c 71 /**
Osamu Nakamura 0:ad834d403a8c 72 Build out the endpoint.
Osamu Nakamura 0:ad834d403a8c 73 */
Osamu Nakamura 0:ad834d403a8c 74 void buildEndpoint();
Osamu Nakamura 0:ad834d403a8c 75
Osamu Nakamura 0:ad834d403a8c 76 /**
Osamu Nakamura 0:ad834d403a8c 77 Plumb the lower RF network stack
Osamu Nakamura 0:ad834d403a8c 78 @param device_manager input optional device manager (DeviceManager type)
Osamu Nakamura 0:ad834d403a8c 79 @param canActAsRouterNode input boolean indicating whether this node can act as a router node or not.
Osamu Nakamura 0:ad834d403a8c 80 */
Osamu Nakamura 0:ad834d403a8c 81 static void plumbNetwork(void *device_manager = NULL,bool canActAsRouterNode = false);
Osamu Nakamura 0:ad834d403a8c 82
Osamu Nakamura 0:ad834d403a8c 83 /**
Osamu Nakamura 0:ad834d403a8c 84 Initialize the endpoint's configuration and begin the endpoint's main even loop
Osamu Nakamura 0:ad834d403a8c 85 */
Osamu Nakamura 0:ad834d403a8c 86 static void start();
Osamu Nakamura 0:ad834d403a8c 87
Osamu Nakamura 0:ad834d403a8c 88 /**
Osamu Nakamura 0:ad834d403a8c 89 Set the ConnectionStatusInterface instance
Osamu Nakamura 0:ad834d403a8c 90 @param csi input instance pointer to the ConnectionStatusInterface implementation to be used
Osamu Nakamura 0:ad834d403a8c 91 */
Osamu Nakamura 0:ad834d403a8c 92 static void setConnectionStatusInterface(ConnectionStatusInterface *csi);
Osamu Nakamura 0:ad834d403a8c 93
Osamu Nakamura 0:ad834d403a8c 94 // register the endpoint
Osamu Nakamura 0:ad834d403a8c 95 void register_endpoint(M2MSecurity *server_instance, M2MObjectList resources);
Osamu Nakamura 0:ad834d403a8c 96
Osamu Nakamura 0:ad834d403a8c 97 // re-register endpoint
Osamu Nakamura 0:ad834d403a8c 98 void re_register_endpoint();
Osamu Nakamura 0:ad834d403a8c 99
Osamu Nakamura 0:ad834d403a8c 100 // de-register endpoint and stop scheduling
Osamu Nakamura 0:ad834d403a8c 101 void de_register_endpoint(void);
Osamu Nakamura 0:ad834d403a8c 102
Osamu Nakamura 0:ad834d403a8c 103 // mbed-client : object registered
Osamu Nakamura 0:ad834d403a8c 104 virtual void object_registered(M2MSecurity *server_instance, const M2MServer &server);
Osamu Nakamura 0:ad834d403a8c 105
Osamu Nakamura 0:ad834d403a8c 106 // mbed-client : registration updated
Osamu Nakamura 0:ad834d403a8c 107 virtual void registration_updated(M2MSecurity *server_instance, const M2MServer &server) ;
Osamu Nakamura 0:ad834d403a8c 108
Osamu Nakamura 0:ad834d403a8c 109 // mbed-client : object unregistered
Osamu Nakamura 0:ad834d403a8c 110 virtual void object_unregistered(M2MSecurity *server_instance);
Osamu Nakamura 0:ad834d403a8c 111
Osamu Nakamura 0:ad834d403a8c 112 // mbed-client : bootstrap done
Osamu Nakamura 0:ad834d403a8c 113 virtual void bootstrap_done(M2MSecurity *server_instance);
Osamu Nakamura 0:ad834d403a8c 114
Osamu Nakamura 0:ad834d403a8c 115 // mbed-client : resource value updated
Osamu Nakamura 0:ad834d403a8c 116 virtual void value_updated(M2MBase *resource, M2MBase::BaseType type) ;
Osamu Nakamura 0:ad834d403a8c 117
Osamu Nakamura 0:ad834d403a8c 118 // mbed-client : error handler
Osamu Nakamura 0:ad834d403a8c 119 virtual void error(M2MInterface::Error error);
Osamu Nakamura 0:ad834d403a8c 120
Osamu Nakamura 0:ad834d403a8c 121 // get our Options
Osamu Nakamura 0:ad834d403a8c 122 void setOptions(Options *options);
Osamu Nakamura 0:ad834d403a8c 123
Osamu Nakamura 0:ad834d403a8c 124 // get our Options
Osamu Nakamura 0:ad834d403a8c 125 Options *getOptions();
Osamu Nakamura 0:ad834d403a8c 126
Osamu Nakamura 0:ad834d403a8c 127 // get our Endpoint Interface
Osamu Nakamura 0:ad834d403a8c 128 M2MInterface *getEndpointInterface();
Osamu Nakamura 0:ad834d403a8c 129
Osamu Nakamura 0:ad834d403a8c 130 // get our Endpoint Security
Osamu Nakamura 0:ad834d403a8c 131 M2MSecurity *getEndpointSecurity();
Osamu Nakamura 0:ad834d403a8c 132
Osamu Nakamura 0:ad834d403a8c 133 // get our Endpoint Object List
Osamu Nakamura 0:ad834d403a8c 134 M2MObjectList getEndpointObjectList();
Osamu Nakamura 0:ad834d403a8c 135
Osamu Nakamura 0:ad834d403a8c 136 // configure to act as router node
Osamu Nakamura 0:ad834d403a8c 137 void asRouterNode(bool canActAsRouterNode);
Osamu Nakamura 0:ad834d403a8c 138
Osamu Nakamura 0:ad834d403a8c 139 // access the logger
Osamu Nakamura 0:ad834d403a8c 140 Logger *logger();
Osamu Nakamura 0:ad834d403a8c 141
Osamu Nakamura 0:ad834d403a8c 142 // set the device manager
Osamu Nakamura 0:ad834d403a8c 143 void setDeviceManager(void *device_manager);
Osamu Nakamura 0:ad834d403a8c 144
Osamu Nakamura 0:ad834d403a8c 145 // get the device manager
Osamu Nakamura 0:ad834d403a8c 146 void *getDeviceManager(void);
Osamu Nakamura 0:ad834d403a8c 147
Osamu Nakamura 0:ad834d403a8c 148 // underlying network is connected (SET)
Osamu Nakamura 0:ad834d403a8c 149 void isConnected(bool connected);
Osamu Nakamura 0:ad834d403a8c 150
Osamu Nakamura 0:ad834d403a8c 151 // underlying network is connected (GET)
Osamu Nakamura 0:ad834d403a8c 152 bool isConnected();
Osamu Nakamura 0:ad834d403a8c 153
Osamu Nakamura 0:ad834d403a8c 154 // Registered with mDC/mDS
Osamu Nakamura 0:ad834d403a8c 155 bool isRegistered();
Osamu Nakamura 0:ad834d403a8c 156
Osamu Nakamura 0:ad834d403a8c 157 /**
Osamu Nakamura 0:ad834d403a8c 158 Set the ConnectionStatusInterface instance
Osamu Nakamura 0:ad834d403a8c 159 @param csi input instance pointer to the ConnectionStatusInterface implementation to be used
Osamu Nakamura 0:ad834d403a8c 160 */
Osamu Nakamura 0:ad834d403a8c 161 void setConnectionStatusInterfaceImpl(ConnectionStatusInterface *csi);
Osamu Nakamura 0:ad834d403a8c 162
Osamu Nakamura 0:ad834d403a8c 163 // Set ObjectInstanceManager
Osamu Nakamura 0:ad834d403a8c 164 void setObjectInstanceManager(ObjectInstanceManager *oim);
Osamu Nakamura 0:ad834d403a8c 165
Osamu Nakamura 0:ad834d403a8c 166 // Get ObjectInstanceManager
Osamu Nakamura 0:ad834d403a8c 167 ObjectInstanceManager *getObjectInstanceManager();
Osamu Nakamura 0:ad834d403a8c 168
Osamu Nakamura 0:ad834d403a8c 169 private:
Osamu Nakamura 0:ad834d403a8c 170 Logger *m_logger;
Osamu Nakamura 0:ad834d403a8c 171 Options *m_options;
Osamu Nakamura 0:ad834d403a8c 172 bool m_canActAsRouterNode;
Osamu Nakamura 0:ad834d403a8c 173 bool m_connected;
Osamu Nakamura 0:ad834d403a8c 174 bool m_registered;
Osamu Nakamura 0:ad834d403a8c 175
Osamu Nakamura 0:ad834d403a8c 176 // mbed-client support
Osamu Nakamura 0:ad834d403a8c 177 M2MInterface *m_endpoint_interface;
Osamu Nakamura 0:ad834d403a8c 178 M2MSecurity *m_endpoint_security;
Osamu Nakamura 0:ad834d403a8c 179 M2MObjectList m_endpoint_object_list;
Osamu Nakamura 0:ad834d403a8c 180
Osamu Nakamura 0:ad834d403a8c 181 // Device Manager
Osamu Nakamura 0:ad834d403a8c 182 void *m_device_manager;
Osamu Nakamura 0:ad834d403a8c 183
Osamu Nakamura 0:ad834d403a8c 184 // ConnectionStatusInterface implementation
Osamu Nakamura 0:ad834d403a8c 185 ConnectionStatusInterface *m_csi;
Osamu Nakamura 0:ad834d403a8c 186
Osamu Nakamura 0:ad834d403a8c 187 // ObjectInstanceManager
Osamu Nakamura 0:ad834d403a8c 188 ObjectInstanceManager *m_oim;
Osamu Nakamura 0:ad834d403a8c 189
Osamu Nakamura 0:ad834d403a8c 190 // mbed-client methods
Osamu Nakamura 0:ad834d403a8c 191 void createEndpointInterface();
Osamu Nakamura 0:ad834d403a8c 192 M2MSecurity *createEndpointInstance();
Osamu Nakamura 0:ad834d403a8c 193
Osamu Nakamura 0:ad834d403a8c 194 // DynamicResource Lookup
Osamu Nakamura 0:ad834d403a8c 195 DynamicResource *lookupDynamicResource(M2MBase *base);
Osamu Nakamura 0:ad834d403a8c 196
Osamu Nakamura 0:ad834d403a8c 197 // stop underlying observers
Osamu Nakamura 0:ad834d403a8c 198 void stopObservations();
Osamu Nakamura 0:ad834d403a8c 199 };
Osamu Nakamura 0:ad834d403a8c 200
Osamu Nakamura 0:ad834d403a8c 201 } // namespace Connector
Osamu Nakamura 0:ad834d403a8c 202
Osamu Nakamura 0:ad834d403a8c 203 #endif // __CONNECTOR_ENDPOINT_H__