电信物联网开放平台参考

创建批量任 查询单个任务创建批量任 查询单个任务信 查询任务详情信 1.2.7规 创建规 更新规 修改规则状 删除规 查找规 批量修改规则状 1.2.8消息推 注册直连设备的通 发现非直连设备的通 设备信息变化的通 设备数据变化的通 删除非直连设备的通 消息确认通 设备响应命令通 设备事件通 设备服务上报通 规则事件上报通 绑定设备通 批量设备数据变化上报通 常用数据结构体定 DeviceInfo结构体说 DeviceService结构体说 QueryDeviceDTOCloudNA结构体说 ServiceCommand结构体说 ServiceProperty结构体说 DeviceCommandResp结构体说 CommandDTOV4结构体说 GetDeviceRspDTO结构体说 CommandNA2CloudHeader结构体说 ApplicationSetEncrtptDTO结构体说 PutCarInfoData结构体说 1PlatformAPI参考(北向 1PlatformAPI参考(北向1.11.2Application侧接口除了鉴权接口Auth，其他接口调用都需要在requestheader中携带参为调用Auth接口获取到的accessToken。应用开发语言若是JAVA请使用JDK1.81.2.1权接口，获取鉴权token。请参考本文档2.1.1鉴权章节进行开发。Auth(鉴权 1.2.1权接口，获取鉴权token。请参考本文档2.1.1鉴权章节进行开发。Auth(鉴权 （Auth为参数中的appId，Authorization中{accessToken}的值即为调用Auth接口获取到的如果多次获取令牌，则之前的令牌失效最后一次获取的令牌才有效。请勿并发获取令token类型，默认值Oauth2.0Oauth2.0鉴权参数，用来刷新accessToken。（1个月 RefreshToken(刷2.1.1expiresIn的值。 RefreshToken(刷2.1.1expiresIn的值。 AppIdorsecretisnotappIdsecretStatusCode:200{} StatusCode:200{}{} StatusCode:200{}{}token类型，默认值Oauth2.0 StatusCode:204No StatusCode:204No {}调用鉴权接口获取到的2.0TheinputisRefreshaccesstokenAppIdorsecretisnotappIdsecret1.2.2Application（下文简称App）申请设备的增，删，改，查以及修改设AppIoTPlatform申请新的设备IoTPlatform分配对应的设备验证码，待设备携带验证码请求接入平台后，分配其deviceId和secret，允许其使用。平台提供了增，删，1.2.2Application（下文简称App）申请设备的增，删，改，查以及修改设AppIoTPlatform申请新的设备IoTPlatform分配对应的设备验证码，待设备携带验证码请求接入平台后，分配其deviceId和secret，允许其使用。平台提供了增，删，注册直连设 口获取到的accessToken。客户端给出verifyCode则返回的就是这个"Authorization:BearerContent-TheinputisStatusCode:204No https:{} https:{}设备唯一标识,如：MACSIM卡号或设备esn号等。与设备对接时，必须与设备上报的nodeId一致。备注：nodeId和verifyCode需要填写相同的值，SoftRadio的模拟环境，该值可自环境，该值通常为设备的IMEI号。单位秒，不填使用默认值(180s),填写0则永不发现非直连设InvalidaccessTheinputisAppIdforauthnot发现非直连设InvalidaccessTheinputisAppIdforauthnotbeenauthorized.BadrequestTheamountofdevicehasreachedthelimit.Invalidverifybeenbinded.InternalserverThelicenseisnotThelicensesalesisnotStatusCode:200{} 命令状态：sent已发送、deliveredexecuted见附录1.3.9 命令状态：sent已发送、deliveredexecuted见附录1.3.9取值http携带头域信息："Authorization:BearerContent- StatusCode:202Accepted{} StatusCode:202Accepted{}{{"to":null,"toType":null,"requestId":"*****************************************","body":"from":"************","sdp":"**********"}需要requestId关联对应命令执行结果查询设备激活状 "Authorization:BearerContent-Invalid查询设备激活状 "Authorization:BearerContent-InvalidaccessTheinputisThedataindataBaseisCommandNameisTheserviceTypeisnotThedeviceisnot InvalidaccessStatusCode: InvalidaccessStatusCode:200{}"Authorization:BearerContent-删除直连设 StatusCode:204No 删除直连设 StatusCode:204No 取值false时删除网关，并将下属传感器属携带头域信息"Authorization:BearerContent-ThedeviceisnotStatusCode:204No 删除非直连设 InvalidaccessStatusCode:204No 删除非直连设 InvalidaccessThedeviceisnotThedataindataBaseisCommandNameisTheserviceTypeisnotThedeviceisnot"Authorization:BearerContent- sent已发送delivered已送达executed已执行 sent已发送delivered已送达executed已执行需要requestId关联对应命令执行结果http携带头域信息："Authorization:BearerContent-InvalidaccessTheinputisInvalidaccessTheinputisStatusCode:202Accepted{}{{"to":null,"toType":null,"callbackURL":"https://server:port/callbackUri""body":"timeout":"mode":"ON"}修改设备信 修改设备信 "Authorization:BearerContent-ThedataindataBaseisCommandNameisTheserviceTypeisnotThedeviceisnotendUser必须为null。设备类型:endUser必须为null。设备类型:z-wave:ProductType+16XXXX-XXXX0对齐StatusCode:204No StatusStatusCode:204No StatusCode:204No 刷新设备密 "Authorization:BearerContent-{} {"verifyCode":"AE10-12424-"timeout":300} {"verifyCode":"AE10-12424-"timeout":300}验证码：null平台生成验证码，null使用，且返回该网关的唯一ID，平台用于判重设置加 InvalidaccessTheinputisAppIdforauthnot设置加 InvalidaccessTheinputisAppIdforauthnotBadrequestThedeviceisnotDeviceisnotDeviceisThenodeIdisnodeIdInvalidverifyStatusCode:200{"verifyCode":"AE10-12424-"timeout":}设置加密成功：StatusCode:200服务类型找不到：StatusCode:400Not StatusCode:200设置加密成功：StatusCode:200服务类型找不到：StatusCode:400Not StatusCode:200Content-Type:{}}serviceTypecarEncrypt时，data结构1.3.10ApplicationSetEncrtptDTO结serviceType取值carInfo、vehicleProperty"Authorization:BearerContent-.3.1按条件批量查询设备信息列 InvalidaccessTheinputis.3.1按条件批量查询设备信息列 InvalidaccessTheinputisThedeviceisnotIllegalTheencrtptivisnotTheencrtptkeyisnotTheencrtptflagisnotAddnewcarinfo,cannotbenull.新的carInfo,simNumber或者carModel不能为nullThesimNumberisalreadyThevinisalreadyTheresourceisnot备是直连设备时，gatewayId为设备本身的设备所关联的直连设备（即网关）deviceId。指定节点的类：ENDPOINT传感器.GATEWAY:网关.备是直连设备时，gatewayId为设备本身的设备所关联的直连设备（即网关）deviceId。指定节点的类：ENDPOINT传感器.GATEWAY:网关.pageNo=null时查询内容不分页；取值大于等于0的整数时分页查询,等于0设备状态,取值:ONLINE在线;OFFLINE不在线;ABNORMAL异常状态查询注册设备信息时间在startTime之后的记如：20151212T121212Z如：20151212T121212Z指定返回记录的排序，可取值ASC"Authorization:BearerContent- StatusCode:200{{ StatusCode:200{{Content->1.3.8GetDeviceRspDTOInvalidaccessTheapplicationinputisInvalidaccessTheapplicationinputisThegatewayIdandpageNocan'tbebothnull.能同时为null}]}查询单个设备信 返回结果：.3.2查询单个设备信 返回结果：1.3.8 StatusCode:200{"Authorization:BearerContent-64个字节Content-InvalidaccessTheapplicationisnotInvalidaccessTheapplicationisnotThedeviceisnotThedeviceDataisnotTheapplicationhasn'tbeen}Application订阅平台数 Application订阅平台数 StatusCode:201 端口。(说明：HTTP信道只可用于调测)"Authorization:BearerContent- StatusCode:201 查询设备历史数 StatusCode:201 查询设备历史数 gatewayId={gatewayId}&serviceId={serviceId}&pageNo={pageNo}&pageSizeInvalidaccessTherequestcallbackurlisossfailed.Getiotwsaddress{}连设备时，gatewayIddeviceId。连设备时，gatewayIddeviceId。联的直连设备（即网关）deviceId。查询参数，根据时间段查询的起始时间时间格式：yyyyMMdd’T’HHmmss’Z’如：查询参数，根据时间段查询的结束时间时间格式：yyyyMMdd’T’HHmmss’Z’如："Authorization:BearerContent- StatusCode:200gatewayId={gatewayId}&serviceId={serviceId}&pageNo={pageNo}&pageSizeContent- StatusCode:200gatewayId={gatewayId}&serviceId={serviceId}&pageNo={pageNo}&pageSizeContent-网关的设备唯一标识，1-64个字节。当设备是直连设备时，gatewayIddeviceId。当设备是非直连设备时，gatewayId为设备所关联的直连设备（即网关）deviceId。Profile文件中服务能力表里面的propertyties上述实例涉及的Profile 上述实例涉及的Profile {{"commands":null,"properties":[{"dataType":"int","min":0,"max":"step":"method":"RE",{"pageNo":"pageSize":10,{"deviceId":"0d34bb9d-73e1-4780-a12f-9243345a4567","appId":"c8855f40-d7a3-4d51-8b46-9f7747839ee2","data":{{"deviceId":"0d34bb9d-73e1-4780-a12f-9243345a4567","appId":"c8855f40-d7a3-4d51-8b46-9f7747839ee2","data":{}]}{} 查询设备能Invalid 查询设备能Invalidaccesscan'tbebothnull.deviceId{"services":{"commands":null,"properties":[{"dataType":"decimal","required":true,"min":"max":"step":null,"method":"R","unit":"C",}]}]}"unit":null,]}]} 与deviceId保持一致。当设备是非直连设备时，gatewayId为设备所关联的直连设备（即网关）的"Authorization:BearerContent->> StatusCode:200Body:{"serviceId":"serviceType":"Authorization:BearerContent- StatusCode:200Body:{"serviceId":"serviceType":"Authorization:BearerContent-访问方法：RWE可读R，可写WE.4.1创建设备命令 .4.1创建设备命令 InvalidaccessTheinputis"option":"","commands":null,"properties":[{"propertyName":"desc":"dataType":"","enumList":["",""],"min":0,"max":"step":"maxLength":"unit":null,"method":"","events":}]} HTTPS信道回调地址(说明：HTTP HTTPS信道回调地址(说明：HTTPNAPOST方式发送HTTP消息给应用，请求Body为json字符expireTime秒内有效，超过这个时间则默认为48小时设备命令的内用ID要与当"Authorization:BearerContent-CommandDTOV4投递成功：StatusCode201 CommandDTOV4投递成功：StatusCode201 {"command":{"method":"********","paras":{"paraName2":}}查询设备命令 Theinputis查询设备命令 TheinputisInternalserverTheapplicationisnotThedeviceDataisnotTheserviceTypeisnotStatusCode:201Created{"appId":"********","deviceId":"********","command":{"method":"********","paras":{"paraName2":}"expireTime":null,"result":null,"executeTime":null,"platformIssuedTime":null,"deliveredTime":null,"issuedTimes":null}查询成功：StatusCode200DeviceCommandQueryRespDeviceCommandResp结构体说明0查询成功：StatusCode200DeviceCommandQueryRespDeviceCommandResp结构体说明0如：如："Authorization:BearerContent-Pagination查询成功：StatusCode200 StatusCode:200Pagination查询成功：StatusCode200 StatusCode:200Content-{"pageNo":"data":{"appId":"********","deviceId":"********","command":{"method":"********","paras":{"paraName2":}"Authorization:BearerContent-InvalidaccessTheinputisInvalidaccessTheinputisTheapplicationisnotThedeviceDataisnotThedeviceisnotThedevicecommandisnot"expireTime":null,"result":null,"executeTime":null,"platformIssuedTime":null,"deliveredTime":null,"issuedTimes":null{"appId":"********","deviceId":"********","command":{"method":"********","paras":{"paraName2":}"expireTime":null,"result":null,"executeTime":null,"platformIssuedTime":null,"deliveredTime":null,"issuedTimes":null}]}修改设备命令 接⼝路径StatusCode:200 修改设备命令 接⼝路径StatusCode:200 命令ID用ID要与当"Authorization:BearerContent- The TheinputisGetAppKeyfromheaderStatusCode:200{"appId":"********","deviceId":"********","command":{"method":"********","paras":{"paraName2":}"expireTime":null,"result":null,"executeTime":null,"platformIssuedTime":null,"deliveredTime":null,"issuedTimes":null}{}创建设备命令撤销任务 创建设备命令撤销任务 用ID要与当"Authorization:BearerContent-TheapplicationisnotThedeviceDataisnotThedevicecommandisnotThedevicecommandalreadyCannotcancel.StatusCode:201 "Authorization:BearerStatusCode:201 "Authorization:BearerID命令的设备IDWAITTING表示等待执行中，RUNNING表示撤销任务正在执行，SUCCESS表FAILED表示撤销任务执行失败，PART_SUCCESS表ID，参见附录1.3.6DeviceCommandResp结构体说明结构体说明待撤销设备命令的将会撤销所有给该设备下发的设备命InvalidaccessTheinputInvalidaccessTheinputisStatusCode:201{"taskId":"********","appId":"********","status":"WAITTING","totalCount":1,"deviceCommands":[{"appId":"********","deviceId":"********","command":{"method":"********","paras":{"paraName2":}"expireTime":null,"result":null,"executeTime":null,"platformIssuedTime":null,"deliveredTime":null,"issuedTimes":null}]}{"deviceId":}查询设备命令撤销任务 0，默认0查询设备命令撤销任务 0，默认0指定任务ID指定设备ID"Authorization:BearerContent-TheapplicationisnotThedeviceDataisnot查询成功：StatusCode200Pagination查询成功：StatusCode200PaginationstartTime之后Hmmss'Z如：endTime之前Hmmss'Z如：用ID要与当 的任务ID所属的应用IDID 的任务ID所属的应用IDIDRUNNING表示撤SUCCESS表示撤FAILED表示撤销设备命令撤销任务1.3.6sp结构体说明结StatusCode:StatusCode:200Content-{"pageNo":"data":{"taskId":"********","appId":"********","status":"WAITTING","totalCount":1,"deviceCommands":[{"appId":"********","deviceId":"********","command":{"method":"********","paras":{"paraName2":}"expireTime":null,"result":null,"executeTime":null,"platformIssuedTime":null,"deliveredTime":null,"issuedTimes":null}]{"taskId":"********","appId":"********","status":"WAITTING","totalCount":1,"deviceCommands":"Authorization:BearerContent-设备服务调InvalidaccessTheinput设备服务调InvalidaccessTheinputisTheapplicationisnotThedeviceDataisnot{"appId":"********","deviceId":"********","command":{"method":"********","paras":{"paraName2":}"expireTime":null,"result":null,"executeTime":null,"platformIssuedTime":null,"deliveredTime":null,"issuedTimes":null}]}]}Application给设备发送命令消息，实现对传感器的实时控制。平台分别提供了下发至 APP按照下面的规则保证其唯一性：GenerateApplication给设备发送命令消息，实现对传感器的实时控制。平台分别提供了下发至 APP按照下面的规则保证其唯一性：Generate每个健都是profile中命令的参数"Authorization:BearerContent-命令已成功投递StatusCode200命令状态：sent已发送deliveriedtoType为CLOUDfailedtoTypeCLOUDHHmmss’Z命令已成功投递StatusCode200命令状态：sent已发送deliveriedtoType为CLOUDfailedtoTypeCLOUDHHmmss’ZtoType为GATEWAY，如果请求有requestId则同请求的requestId一致，如果请求无requestId则平台分配一个序 toType为CLOUD，则为null;seqNum：APP生成序列号seqNum，在POST请求BODY中携带，序列号规则采用：UUID_XXXX，UUID会根据JAVA自带算法生成，每次APP启动后生成一个新的值，后续使用时不变，直到下次APP重新启动再生成一个新的UUID值，XXXX的取值范围：0001-9999，达到9999后重新从0001开始，如此循环 回调的url地址。必须使用HTTPS信道回调地(说明：HTTP信道只可用于调测) InvalidaccessTheinputis InvalidaccessTheinputisThedataindataBaseStatusCode:200{"status":"sent","timestamp":"**********"}{{"method":"INVITE-INIT","body":"from":"************","sdp":"**********"}创建批量任 任务类型创建批量任 任务类型"Authorization:BearerContent-CommandNameisTheserviceTypeisnotThedeviceisnot，paramStatusCode:200批量命令类型：DeviceList/DeviceTypeDeviceAreaGroupList，paramStatusCode:200批量命令类型：DeviceList/DeviceTypeDeviceAreaGroupListmMethod:Invalidaccessreachedthelimit.10个时，返回Method:Invalidaccessreachedthelimit.10个时，返回BadrequestTheuserhasnoStatusCode:200{}{"appId":"******","timeout":1000,"param":{"fileId":}}查询单个任务信 StatusCode:200查询单个任务信 StatusCode:200"Authorization:BearerContent-，paramMethod:StatusCode:200"Authorization:BearerContent-批量命令类型：DeviceList/DeviceTypeDeviceAreaGroupList，paramMethod:StatusCode:200"Authorization:BearerContent-批量命令类型：DeviceList/DeviceTypeDeviceAreaGroupList查询任务详情信 查询任务详情信 Theinputis{"taskId":"********","taskName":"********","appId":"********","operator":"********","taskFrom":"********","status":"********","timeout":1000,"progress":"totalCnt":"successCnt":"failCnt":"timeoutCnt":"expiredCnt":"completeCnt":"param":{"fileName":}}StatusCode:200分页查询参数，pageNo=null时StatusCode:200分页查询参数，pageNo=null时"Authorization:BearerContent-Method:StatusCode:200{"pageNo":"pageSize":1,{"status":Method:StatusCode:200{"pageNo":"pageSize":1,{"status":Content-,.7.1创建规,.7.1创建规"Authorization:BearerContent-Theinputis"output":"error":"{\"error_code\":100007,\"error_desc\":\"Badrequestmessage.\"}""param":{"index":"nodeId":}}]}RuleDTO1.2id。List<Json表）RuleDTO1.2id。List<Json表）groupExpress二选一必填自定义结构体（见下表Condition-List<Json规则的动作。Action为自定义结构体。（见下面Action-DeviceCMD、Action-SMS、Action-email、Device-TriggerSource结构体GroupElementDevice-TriggerSource结构体GroupElementGroupExpressconidtions二选国际时区，如Asia/Shanghai、ListTriggerSource，只与GroupExpressDEVICE类型和TIMER类型则触发默认为pulse则触发默认为pulse比较表达式的右值(与between操2030，应用场景:温度在20到30之间触发规钟，默认为0不延时Strategybetween操作符联用时，右2030之间触发规分钟，默认为0不延时Integer(>=-between操作符联用时，右2030之间触发规"DoorWindow/status",属性支持多个,比如OBD需要两个属性,经度和纬度”,多个属性中间以结构体Strategy比如OBD需要两个属性,经度和纬度”,多个属性中间以逗号分隔分钟，默认为0不延时结构体StrategyCMD当action的编号，在一条规则CMD当action的编号，在一条规则规则Demo内容类型Content-Type：application/jsonInvalidaccessappIdTheapplicationisnotTheruleisnot内容类型Content-Type：application/jsonInvalidaccessappIdTheapplicationisnotTheruleisnotTherulenamealreadyThedataindataBaseisTherulecountofeachapphasreachedtheupperlimit,thecurrentuplimitis30entries.curl-X--header"Content-Type:--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-d"name":"rule1","description":curl-X--header"Content-Type:--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-d"name":"rule1","description":"thisisatestrule2015.12.23","status":"active",{"type":"path":"DoorWindow/status""operator":"value":"OPEN"，"strategy":{"trigger":}}"actions":{"type":"cmd":{"messageType":"MUTE",Theapplicationinputiswhencreaterule.TheruleinputisTheactionofruleisActionidduplicatedinsameActionidRuleapiparameterisConvertjsontoclass1.3betweencurl-X--header"Content-Type:--header"Accept:curl-X--header"Content-Type:--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-d"name":"rule1","description":"thisisatestrule2015.12.23","status":"active",{"type":"path":"DoorWindow/status""operator":"strategy":{"trigger":}}"actions":{"type":"cmd":{"messageType":"MUTE","messageBody":{"force":}}]"force":}}}]1.3geo.circle.in/out1.3geo.circle.in/outcurl-X--header"Content-Type:--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-d"name":"rule1","description":"thisisatestrule2015.12.23","status":"active",{--header"app_key:--header"Authorization:Bearer{accessToken}"-d"name":"rule1","description":"thisisatestrule2015.12.23","status":"active",{"type":"path":"Temperature/temperature""value":"20,30",}}"actions":{"type":"cmd":{"messageType":"MUTE","messageBody":{"force":}}]更新规更新规"Authorization:BearerContent-{}"type":"path":"Location/longitude,latitude""operator":"geo.circle.in",}}"actions":{"type":"cmd":{"messageType":"MUTE","messageBody":{"force":}}]内容类型Content-InvalidaccessRuleIdcannotbenulloremptywhenupdaterule.appIdTheapplicationisnot内容类型Content-InvalidaccessRuleIdcannotbenulloremptywhenupdaterule.appIdTheapplicationisnotTheruleisnotTherulenamealreadyThedataindataBaseisTherulecountofeachapphasreachedtheupperlimit,thecurrentuplimitis30entries.Theapplicationinputisid。curl-X--header"Content-Type:--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-dcurl-X--header"Content-Type:--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-d"name":"rule1","description":"thisisatestrule2015.12.23","status":"active",{"type":"path":"DoorWindow/status""operator":"value":}"actions":{"type":"cmd":{"messageType":"MUTE","messageBody":{"force":}}}]Internalservererrorhappenedwhencreaterule.TheruleinputisTheactionofruleisActionidduplicatedinsameActionidRuleapiparameterisConvertjsontoclass.3.3修改规则状{"ruleId":}curl-X--header"Content-Type:--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-d"name":"rule1","description":"thisisatestrule2015.12.23","status":"active",{"type":"path":"DoorWindow/status""operator":"value":}"actions":{"type":"cmd":{"messageType":"MUTE","messageBody":{"force":}}]InvalidaccessappIdTheapplicationisnotTheruleisnotInvalidaccessappIdTheapplicationisnotTheruleisnotTheapplicationhasn'tbeenTheruleinputis时返回的id"Authorization:BearerContent-删除规删除规时返回的id"Authorization:BearerContent-curl-X--header"Content-Type:--header"Accept:--header"app_key:--header"Authorization:Bearer-d"status":查找规查找规"Authorization:BearerContent-curl-X--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"InvalidaccessappIdTheapplicationisnotTheruleisnotTheapplicationhasn'tbeen返回结果：Rule列表，消息体参数定义查看RuleDTO1.2{"name":"author":"description":"thisisatestrule2015.12.23","type":"noType","status":{返回结果：Rule列表，消息体参数定义查看RuleDTO1.2{"name":"author":"description":"thisisatestrule2015.12.23","type":"noType","status":{"id":0,curl-X--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"Invalidaccess时返回的id批量修改规则状批量修改规则状时返回的id"Authorization:BearerContent-"path":"DoorWindow/status""operator":"value":}"actions":{"id":0,"appId":"pnS6yhwLszJ8kZF7HhuH7cOeoGQa","cmd":{"messageType":"MUTE","messageBody":{"force":}}}]}RuleStatusUpdateReqDTORuleResultBodyDTO为“PartialOK”RuleStatusUpdateReqDTORuleResultBodyDTO为“PartialOK”uestDTO为自curl-X--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-d}]Invalidaccesscurl-X--header"Accept:--header"app_key:--header"Authorization:Bearer{accessToken}"-d}]InvalidaccessappIdTheapplicationisnotTheruleisnotTheruleinputis否则为“Operationpartial 1.2.8 1.2.8，Applicatio注册直连设备的通NA调用中国电信物联网开放平台的接口添加新设备，获取设备验证码（通知给Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType为“deviceAdded”的回调通知地址，请参考Application订阅平台数据。{{"result_code":"PartialOK",{"response":{"error_desc":}"response":{"error_desc":}}]}{}}{}}发现非直连设备的通{{","manufacturer":"wulian",非直连设备时，gatewayId为设备所关联的直连设备（即网关）的deviceId。ENDPOINT传感器.GATEWAY:网关.1.3.1DeviceInfo结}}设备信息变化的通}}设备信息变化的通d，中{"notifyType":"deviceInfoChanged",非直连设备时，gatewayId为设备所关联的直连设备（即网关）的deviceId。1.3.1DeviceInfo结}}设备数据变化的通，中国电信物联网开放平台使用该接口功能将该信息通知给Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyTypeApplication}}设备数据变化的通，中国电信物联网开放平台使用该接口功能将该信息通知给Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyTypeApplicationgatewayIddeviceId。当设备的直连设备（即网关）的deviceId。{"requestId":"{requestId}",{"requestId":"{requestId}","serviceId":}}删除非直连设备的通此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType为“deviceDeleted”的回调通知地址，请参考Application订阅平台数据。HHmmss’Z{}消息确认通到该消息Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType为“{}消息确认通到该消息Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType为“messageConfirm”的回调通知地址，请参考Application订阅平台数据。非直连设备时，gatewayId为设备所关联的直连设备（即网关）的deviceId。{{"from":"to":"{to}",{{"from":"to":"{to}",息，1-128字节1-128sent已发送delivered已送达executed已执行HHmmss’Z’如：1-32}{}}设备响应命令通图等Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType}{}}设备响应命令通图等Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType为“commandRsp”的回调通知地址，请参考Application订阅平台数据。commandRsp对应的command1.2.5设备息，1-128个字节响应命令的消息体Body中的内{{{{HHmmss’Z’如：}}设备事件通将该消息通知给Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType为“deviceEvent”的回调通知地址，请参考Application订阅平台数据。}}设备事件通将该消息通知给Application。此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType为“deviceEvent”的回调通知地址，请参考Application订阅平台数据。}HHmmss’Z响应命令的消息体Body中的内{{}}设备服{{}}设备服务上报通HHmmss’Z’如：此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType参数说明Application{"serviceId":"{serviceId}","INVITE-INIT","INVITE",此处的接⼝路径是应用向平台订阅数据时注册的对应notifyType参数说明Application{"serviceId":"{serviceId}","INVITE-INIT","INVITE",非直连设备时，gatewayId为设备所关联的直连设备（即网关）的deviceId。{}}0规则事件上报通参数说明Reason{}}0规则事件上报通参数说明Reason条件类型，包括同规则接口中的>触发原因，对应DEVICE_CMD类型的动作携带的配的