IoT Platform:Use the advanced features

Specify configuration file paths

By default, the configuration file of a bridge is application.conf, and the configuration file of the device certificate mapping is devices.conf.

IoT as Bridge SDK allows you to specify custom file paths. Before you call the bootstrap() method, you can call the ConfigFactory.init() method to specify the path of a configuration file. You can also create an instance and implement the methods based on your business requirements.

Sample code:

private static DeviceConfigManager selfDefineDeviceConfigManager = new DeviceConfigManager() {
    @Override
    public DeviceIdentity getDeviceIdentity(String originalIdentity) {
        return devicesMap.get(originalIdentity);
    }

    @Override
    public String getOriginalIdentity(String productKey, String deviceName) {
        return null;
    }
};
BridgeBootstrap bridgeBootstrap = new BridgeBootstrap();
ConfigFactory.init(ConfigFactory.getBridgeConfigManager("application-self-define.conf"),selfDefineDeviceConfigManager);
bridgeBootstrap.bootstrap();

Dynamically register bridges

When you deploy bridges on a large number of servers, the deployment process is complex if you need to specify different bridges for different bridge servers. You can configure the application.conf bridge configuration file to dynamically register bridges.

You must specify the productKey and popClientProfile parameters of a bridge in the configuration file. Then, IoT as Bridge SDK calls an API operation of IoT Platform to register the bridge and uses the MAC address of the bridge server as the DeviceName of the bridge.

The following sample code shows how to configure a small-sized bridge. In this example, an Enterprise Edition instance is used.

// The sendpoint of services.
http2Endpoint = "https://${IotInstanceId}.http2.iothub.aliyuncs.com:443"
authEndpoint = "https://${IotInstanceId}.auth.iothub.aliyuncs.com/auth/bridge"

// The parameters of the bridge.
productKey = ${YourProductKey}

popClientProfile = {
    accessKey = ${YourAliyunAccessKey}
    accessSecret = ${YourAliyunAccessSecret}
    name = cn-shanghai
    region = cn-shanghai
    product = Iot
    endpoint = iot.cn-shanghai.aliyuncs.com
}

Call operations to submit TSL data

IoT as Bridge SDK encapsulates the operations to submit data. You can call the reportProperty operation to submit properties, call the fireEvent operation to submit events, and call the updateDeviceTag operation to update tags. A device can use these operations to report properties, report events, and update device tags.

Sample code:

TslUplinkHandler tslUplinkHandler = new TslUplinkHandler();
// Submit a property. 
// The testProp property is defined. 
String requestId = String.valueOf(random.nextInt(1000));
// The timestamp is not included in the submitted property data. 
tslUplinkHandler.reportProperty(requestId, originalIdentity, "testProp", random.nextInt(100));
// The timestamp is included in the submitted property data. 
//tslUplinkHandler.reportProperty(requestId, originalIdentity, "testProp", random.nextInt(100), System.currentTimeMillis());

// Submit an event. 
// The testEvent event is defined. 
requestId = String.valueOf(random.nextInt(1000));
HashMap<String, Object> params = new HashMap<String, Object>();
params.put("testEventParam", 123);
// The timestamp is not included in the submitted event data. 
tslUplinkHandler.fireEvent(originalIdentity, "testEvent", ThingEventTypes.INFO, params);
// The timestamp is included in the submitted event data.
//tslUplinkHandler.fireEvent(originalIdentity, "testEvent", ThingEventTypes.INFO, params, System.currentTimeMillis());

// Update a device tag. 
// The key of the tag is set to testDeviceTag. 
requestId = String.valueOf(random.nextInt(1000));
tslUplinkHandler.updateDeviceTag(requestId, originalIdentity, "testDeviceTag", String.valueOf(random.nextInt(1000)));

The following table describes the parameters.

Call operations to submit multiple properties and events at a time

IoT as Bridge SDK encapsulates the operations to submit multiple properties and events at a time. You must create a BatchPostEventPropertyMessage object and call the addProperty() and addEvent() methods to add property and event data. Then, create a TslUplinkHandler object and call the BatchPostEventPropertyMessage() method to submit data.

Sample code:

TslUplinkHandler tslUplinkHandler = new TslUplinkHandler();
// Submit multiple properties and events at a time.
String requestId = String.valueOf(random.nextInt(1000));
long startTime = System.currentTimeMillis() - 3000;

// Create a message to submit data.
BatchPostEventPropertyMessage batchPostEventPropertyMessage = new BatchPostEventPropertyMessage();
Map<String, Object> aiEventParams = new HashMap<>();
aiEventParams.put("EventContent", "hello world");
batchPostEventPropertyMessage
    .addProperty("PowerConsumption", 1000, startTime)
    .addProperty("PowerConsumption", 123, startTime + 1000)
    .addProperty("LightAdjustLevel", 23, startTime)
    .addProperty("LightAdjustLevel", 44, startTime + 1000)
    .addProperty("LightAdjustLevel", 47, startTime + 2000)
    .addEvent("AIEvent", aiEventParams, startTime);
batchPostEventPropertyMessage.setId(requestId);

// Submit the data.
tslUplinkHandler.batchPostEventPropertyMessage(originalIdentity, batchPostEventPropertyMessage);

The following table describes the parameters.

Call operations to set properties and call services

IoT as Bridge SDK encapsulates the PropertySetHandler operation to set properties and the ServiceInvokeHandler operation to call services. A device can use these operations to receive commands from IoT Platform to update data.

Sample code:

BridgeBootstrap bridgeBootstrap = new BridgeBootstrap();
// Set properties.
bridgeBootstrap.setPropertySetHandler(new PropertySetHandler() {
    @Override
    public void onPropertySet(PropertySetMessage msg) {
        log.info("on property set, {}", msg.getParams());
        // If you call the replySuccess() method, the SDK sends the /property/set_reply message to IoT Platform. The response code is 200.
        msg.replySuccess();
        // If you call the replyFail() method, the SDK sends the /property/set_reply message to IoT Platform. You can specify the response code based on your business requirements.
        //msg.replyFail(400);
    }
});

// Call services.
bridgeBootstrap.setServiceInvokeHandler(new ServiceInvokeHandler() {
    @Override
    public void onServiceInvoke(ServiceInvokeMessage message) {
        log.info("on service invoke, {}", message.getParams());
        // If you call the replySuccess() method, the SDK sends the /service/{service.identifier}_reply message to IoT Platform. The response code is 200.
        message.replySuccess();
        // If you call the replyFail() method, the SDK sends the /service/{service.identifier}_reply message to IoT Platform. You can specify the response code based on your business requirements.
        //msg.replyFail(400);
    }
});