IP Device Handler

IP Device handler manages unified traffic for Non-IP and IP devices and distributes the traffic to respective components.

This module is developed using API Gateway Actions framework. The IP Device handler is connected to the T8 API blocks in API gateway in request path (uses API gateway one push script).

IP Device handler relies on a database table to identify the device type. The database schema for the table is defined in Table 2-8

Table 2-8 IP Device Table schema

Table Name	Column Name	Data Type
scef_ip_device_info	external_id	varchar(256)
	msisdn	bigint(20)
	imsi	bigint(20)
	device_id	varchar(256)
	apn	varchar(120)
	ip	varchar(50)
	type	tinyint(4) (2- MQTT)
	active_appserver	varchar(20)
	status	varchar(20)
	aaa_session_id	varchar(256)

When the API Gateway receives a "Nidd Downlink Data Delivery" or "Monitoring Eventsubscription" request then IP device handler checks if the header "Xscef-mqtt-topic-name" is present for "Nidd Downlink Data Delivery" request and header "Xscef-message-type" is present for "Monitoring Eventsubscription" request. If these headers are not present for the corresponding requests, then those requests are Non IP requests and are forwarded to Non IP flow. If headers are present as mentioned, then IP device handler retrieves the device identifier from the request and checks it in scef_ip_device_info table. Based on the device type, the request is passed to MQTT Broker service for further processing. Refer to MQTT Broker for more information.