OneNET IoT Platform Platform Introduction Introduction Manual Guidline for Device Development Guideline for Application Development
API
API Usage API List SDK MQTT LwM2M EDP Modbus TCP
HTTP Push MQ
Other Service Common Question

Service Introduction

OneNET device management services are for IoT application device management needs, to provide device-card integration management features, device overview statistics, device information enhancement management, remote upgrade, fault tracking and other functions, for terminals & IoT card troubleshooting, device-card relationship management, terminal status query, communication business usage query and other scenarios.

Product entry

After logging into the Developer Center, switch to device management with the top title.

设备管理首页

Device Overview Statistics

-Device Statistics

  • Total number of devices: Total amount of device under the user
  • Number of online: Current number of online
  • Online rate: The proportion of devices online
  • Number of new devices added today: Number of new devices added on the day
    • API Statistics
    • Today's API call: Number of API calls today
    • Success rate: The call success rate of the API, that is, the proportion of access success (return 200 as successful)
    • Push statistics
    • Number of push messages: number of messages pushed today
  • Success rate: The proportion of the number of successful pushes
    • Command statistics
  • Command issued today: Number of commands issued today
  • Success rate: The devices that have been sent and the proportion of responded devices

Device Information Management

Device list page, users can quickly switch to other product management and view device information

The details page allows you to view device information, historical data, historical commands, online records (different protocol tabs may be different)

DMP based on OneNET basic device information development device information management, including: basic information, status information, location information, card information, version information

information collection method fixed datastream name description
basic information provide API interface No Add information to the current device information and fill in via page, or interface
status information platform record no no
location information fixed datastream name and field $OneNET_LBS report via interfaces or messages
Card information fixed datastream name and field $OneNET _cardinfo report via pages, interfaces, or messages
version information fixed datastream name and field $OneNET_versioninfo report via interfaces or messages
Note: datastream with $OneNET header is system datastream
  • Basic information module
English Chinese description source format requirement
id device id device id platform unique platform generation long string
title device name user-defined user fill-in string limited in 64 characters
APIkey APIkey Key of the device platform generation String
auth_info authentication information user-defined authentication information user fill-in Object, 64 bit
IMEI IMEI international standard User fill-in/Device report String, international standard 15-bit
desc Describtion Device describtion information user fill-in string, 512 characters
protocol protocol type protocol type on the platform user fill-in string
Manufacturer_id manufacturer manufacturer name, user-defined, global unique user fill-in String, 32 characters
Model Model model name, user-defined user fill-in string,32 Words
create_time creation time time of the new device automatically generate datetime
activated state activation status it is divided into activated and unactivated; it is unactivated if there is no online record server record boolean
first_active time activation time The time of the first connection to the access device server record datetime
location location address description user fill-in object
other other other customized information user fill-in object
  • Status Information
English Chinese Description Source Format requirement
online device status online, Offline server records boolean
last_connection_date last connection time last connection server time server records datetime
  • Location information ($OneNET _LBS)
English Chinese description source format requirement
cid base station encoding base station encoding device report/API interface int, maximum 32-bit
lac area code area code device report/API interface int, maximum 32-bit
mnc mobile network code mobile network code, optional device report/API interface int
mcc mobile country code optional device report/API interface int
networktype network type network type device report/API interface int
ss signal strength signal strength device report/API interface int
signalLength signal strength of current base station broadcast signal strength of current base station broadcast device report/API interface int
ta movebile table distance to determine the timing advance of its sending to the base station device report/API interface int
  • IoT card information ($OneNET_cardinfo)
English Chinese description source format requirement
imsi IMSI international standard Device report int, maximum 15-bit
msisdn IoT card number 13-digit Device report int, maximum 13-bit
iccid ICCid international standard Device report int, maximum 20-bit
  • Version information ($OneNET_versioninfo)
English Chinese description source format requirement
fw_version firmware version firmware version number device report String, length limit 32-bit
hw_version hardware version hardware version number device report String, length limit 32-bit
sw_version software version software version number device report String, length limit 32-bit

Report Example json data point section

{
    "$OneNET_cardinfo": {
        "IMSI": 1331231231231231, 
        "ICCID": 12312312312434324234324324324
    }
}
  • Information storage

Storage time is as follows

information storage mode description
basic information store the latest value no
status information store the latest value no
LBS Store values for nearly a period of time one year
card information store the latest values no
version information store the latest value no
The statistical time of other parts is deadlined to yesterday

Introduction to the integration function of device-card

OneNET provides device-card integration management features (mobile IoT card), for terminal & IoT card troubleshooting, device-card relationship management, terminal status query, communication business usage query and other scenarios.

Instructions for use

The use of the device-card integration function requires the first binding of the Onelink EC account; determine whether there is a corresponding card number of query permissions through the binding EC account.

EC account binding

When you create a new binding user, you need to jump to Onelink for login verification

Creation method of device-card relationship

method instructions for use
page new device-card relationship create a single relationship through the page, or batch import the card relationship through the page
API interface new device-card relationship create a new device-card relationship through the interface, see the next section
datapoint report create device-card relationship by reporting canonical datapoint to the specifying datastream of the system
Note: The system device-card datastream is $OneNET_cardinfo, and the json that reports the datapoints contains one or more keywords of imsi, msisdn, iccid 

results matching ""

    No results matching ""