mobile CCTV,mobile surveillance,police body worn cameras

标题: 认证问题 [打印本页]

author: Aiwinn time: 2019-5-22 18:10
标题: 认证问题
现遇到如下情况：
1，使用wifi 进行认证后再使用电信4g卡的情况下需要重新认证，经发现仅wifi情况下获取的imei和电信卡获取的imei（其实获取的是meid）是不一样的，
就导致同一台设备在使用wifi  和电信卡的时候需要认证两次。
电信卡认证日志：
{"stEntity":{"iAPILevel":27,"iDensityDpi":160,"iHeightPixels":320,"iWidthPixels":240,"szAndroidID":"382f3519bf0ec2f6","szBoard":"msm8953","szBrand":"DSJ","szBuildTime":"1556129687000","szDeviceID":"99000843131692","szFingerPrint":"DSJ/LB1807/LB1807:8.1.0/OPM1.171019.011/LB1807.4.01.03.00:userdebug/release-keys","szHardware":"qcom","szMacAddress":"02:00:00:00:00:00","szModel":"LB01","szRadio":".TA.2.3.c1-00652-8953_GEN_PACK-1"},"szAuthParam":"NULL","szLicense":"F88291D8-E4AD-45E7-8B79-B081E93BB586","szPath":"/storage/emulated/0"}
auth---->{"iAuthStatus": 200, "szAuthType":"auth.type.imei"}

设备id 23131692 图传认证id  38101

wifi认证日志：
{"stEntity":{"iAPILevel":27,"iDensityDpi":160,"iHeightPixels":320,"iWidthPixels":240,"szAndroidID":"382f3519bf0ec2f6","szBoard":"msm8953","szBrand":"DSJ","szBuildTime":"1556129687000","szDeviceID":"990008431316921","szFingerPrint":"DSJ/LB1807/LB1807:8.1.0/OPM1.171019.011/LB1807.4.01.03.00:userdebug/release-keys","szHardware":"qcom","szMacAddress":"02:00:00:00:00:00","szModel":"LB01","szRadio":".TA.2.3.c1-00652-8953_GEN_PACK-1"},"szAuthParam":"ky62otrHVz8VCLe29kWqn7fU1URkTtQws/asOVr0BND9qmsBYXPjogKHm4YFClv6C894giiEraRC+8g4qo0skgGz+JUx8V86b0/Aql56HhJ3FFASydooE77e84Ohnx6E9S8kgVI2KwXexvc+f10n1Zd6fX7Nh4StMO3YjbMQS8jipPrhD2lhiKQlxpBaxI9dlXkFke80KCnCTj0dqDqmWA6BDDmCEVzCo4KGP45M14wvvV2IA/WylbUbTmJXxCba","szLicense":"F88291D8-E4AD-45E7-8B79-B081E93BB586","szPath":"/storage/emulated/0"}
auth---->{"iAuthStatus": 200, "szAuthType":"auth.type.imei"}

设备id  图传认证id  38101

从上诉日志可以看出  两次得到的szDeviceID 是不一样的 4g电信卡的szDeviceID 是 99000843131692  wifi 的szDeviceID  是 990008431316921

2，发现上述问题后，我们对认证的代码进行了优化，wifi和4g电信卡的情况下都上传的是imei号码
电信4g卡认证的日志：
{"stEntity":{"iAPILevel":27,"iDensityDpi":160,"iHeightPixels":320,"iWidthPixels":240,"szAndroidID":"382f3519bf0ec2f6","szBoard":"msm8953","szBrand":"DSJ","szBuildTime":"1556129687000","szDeviceID":"990008431316921","szFingerPrint":"DSJ/LB1807/LB1807:8.1.0/OPM1.171019.011/LB1807.4.01.03.00:userdebug/release-keys","szHardware":"qcom","szMacAddress":"02:00:00:00:00:00","szModel":"LB01","szRadio":".TA.2.3.c1-00652-8953_GEN_PACK-1"},"szAuthParam":"NULL","szLicense":"F88291D8-E4AD-45E7-8B79-B081E93BB586","szPath":"/storage/emulated/0"}
auth---->{"iAuthStatus": 400, "szAuthType":"auth.type.trial"}

获取认证id的时候提示认证失败

wifi认证的日志：
{"stEntity":{"iAPILevel":27,"iDensityDpi":160,"iHeightPixels":320,"iWidthPixels":240,"szAndroidID":"382f3519bf0ec2f6","szBoard":"msm8953","szBrand":"DSJ","szBuildTime":"1556129687000","szDeviceID":"990008431316921","szFingerPrint":"DSJ/LB1807/LB1807:8.1.0/OPM1.171019.011/LB1807.4.01.03.00:userdebug/release-keys","szHardware":"qcom","szMacAddress":"02:00:00:00:00:00","szModel":"LB01","szRadio":".TA.2.3.c1-00652-8953_GEN_PACK-1"},"szAuthParam":"NULL","szLicense":"F88291D8-E4AD-45E7-8B79-B081E93BB586","szPath":"/storage/emulated/0"}
auth---->{"iAuthStatus": 200, "szAuthType":"auth.type.imei"}

可以获取到认证id

从上诉的两份log可以看出电信4g  和wifi  认证时上传的 szDeviceID 都是  990008431316921  （整个认证上传的参数都是一样的）
但是返回的结果不一样，电信4g卡的返回结果中szAuthType 是 auth.type.trial  而 wifi认证返回的结果szAuthType 是 auth.type.imei

总结上面论述的结论是，wifi 和电信4g卡的认证存在差异，当上传的认证参数不一样时，同一台设备需要认证两次；
当优化后上传相同的认证参数时返回的结果不同，导致4g卡情况下无法认证，无法使用图传。

author: Aiwinn time: 2019-5-24 10:17
请问这个问题有在关注吗？要怎么解决？

author: xuwei time: 2019-5-24 18:57

Aiwinn post on2019-5-24 10:17
请问这个问题有在关注吗？要怎么解决？

下个星期给你更新下库

author: admin time: 2019-5-25 08:40
也同时给他们更新为新的认证机制吧。
aiwinn是我们的算法伙伴，互为依存，对他们我们可以更加的开放。

author: Aiwinn time: 2019-5-27 17:14

admin post on2019-5-25 08:40
也同时给他们更新为新的认证机制吧。
aiwinn是我们的算法伙伴，互为依存，对他们我们可以更加的开放。

反射获取imei号的代码
  /**
   * 获取imei号码
   *
   * @param context 上下文
   * @param slotID  卡槽id  0 1
   * @return imei号
   */
private String getImei(Context context, int slotID) {
      String imei = "";
      TelephonyManager telephony = (TelephonyManager) context.getSystemService(Context.TELEPHONY_SERVICE);
      try {
         Class<?> telephonyClass = Class.forName(telephony.getClass().getName());
         Class<?>[] parameter = new Class[1];
         parameter[0] = int.class;
         Method getSimID = telephonyClass.getMethod("getImei", parameter);
         Object[] obParameter = new Object[1];
         obParameter[0] = slotID;
         Object ob_phone = getSimID.invoke(telephony, obParameter);
         if (ob_phone != null) {
            imei = ob_phone.toString();
         }
      } catch (Exception e) {
         e.printStackTrace();
      }
      return imei;
}

author: Aiwinn time: 2019-5-28 11:54

Aiwinn post on2019-5-27 17:14
反射获取imei号的代码
  /**
   * 获取imei号码

电信4g
[ BillTool ] {"stEntity":{"iAPILevel":25,"iDensityDpi":240,"iHeightPixels":960,"iWidthPixels":640,"szAndroidID":"d0cdf09baac05b28","szBoard":"msm8953","szBrand":"DSJ-HECH1A1","szBuildTime":"1557973942000","szDeviceID":"861263030015070","szFingerPrint":"Android/msm8953_64_c350/msm8953_64_c350:7.1.2/N2G47H/server05161032:user/release-keys","szHardware":"qcom","szMacAddress":"02:00:00:00:00:00","szModel":"DSJ-HECH1A1","szRadio":".TA.2.3.c1-00361-8953_GEN_PACK-1"},"szAuthParam":"NULL","szLicense":"F88291D8-E4AD-45E7-8B79-B081E93BB586","szPath":"/storage/emulated/0"}
[ BillTool ] auth---->{"iAuthStatus": 400, "szAuthType":"auth.type.trial"}

wifi
[ BillTool ] {"stEntity":{"iAPILevel":25,"iDensityDpi":240,"iHeightPixels":960,"iWidthPixels":640,"szAndroidID":"d0cdf09baac05b28","szBoard":"msm8953","szBrand":"DSJ-HECH1A1","szBuildTime":"1557973942000","szDeviceID":"861263030015070","szFingerPrint":"Android/msm8953_64_c350/msm8953_64_c350:7.1.2/N2G47H/server05161032:user/release-keys","szHardware":"qcom","szMacAddress":"02:00:00:00:00:00","szModel":"DSJ-HECH1A1","szRadio":".TA.2.3.c1-00361-8953_GEN_PACK-1"},"szAuthParam":"NULL","szLicense":"F88291D8-E4AD-45E7-8B79-B081E93BB586","szPath":"/storage/emulated/0"}
[ BillTool ] auth---->{"iAuthStatus": 200, "szAuthType":"auth.type.imei"}

新的libbill.so 目前还是出现电信卡和wifi 包装的参数一样返回的结果不一样的问题

author: Aiwinn time: 2019-5-29 15:19

admin post on2019-5-25 08:40
也同时给他们更新为新的认证机制吧。
aiwinn是我们的算法伙伴，互为依存，对他们我们可以更加的开放。

请问现在还有在帮我们看imei号的问题吗

author: xuwei time: 2019-5-30 11:21

Aiwinn post on2019-5-29 15:19
请问现在还有在帮我们看imei号的问题吗

下午会更新SDK包给你

author: Aiwinn time: 2019-5-30 16:42

xuwei post on2019-5-30 11:21
下午会更新SDK包给你

请问新的SDK包和旧的SDK包在认证这部分的修改主要是哪一块，因为我们对旧的SDK修改也比较多，直接替换的话工作量太大了，可以给出这一部分的修改意见吗？

author: xuwei time: 2019-5-30 16:58

Aiwinn post on2019-5-30 16:42
请问新的SDK包和旧的SDK包在认证这部分的修改主要是哪一块，因为我们对旧的SDK修改也比较多，直接替换 ...

认证接口改了，依赖的jar包和NDK库改了，NDK库改成了armeabi-v7a，可以先替换libs和jnilibs的所有库文件，对比修改下新的gradle文件，然后如果有问题，再根据新工程的代码调整

author: xuwei time: 2019-5-30 17:16

Aiwinn post on2019-5-30 16:42
请问新的SDK包和旧的SDK包在认证这部分的修改主要是哪一块，因为我们对旧的SDK修改也比较多，直接替换 ...

原来的armeabi库可以删除了

author: Aiwinn time: 2019-5-30 17:16
如微信沟通：
@4GBodyCam ：
我们刚刚看了一下，新给过来的MPU APK和我们现有的MPU APK 改动比较大。就为了解决IMEI这个问题，合并这个代码代价有点大啊。而且也不知道这个新MPU APK 是否有其他的潜在Bug。我们很多地方都在试点，这个时候在我们不敢这么改动。
我建议，我们把现有的MPU APK 给你们发一份，执法仪我们那边也有一台给你们那边，你们直接在我们的MPU版本基础上面帮忙把这个问题处理一下。（只要插入电信卡就可以复现）这个问题，在扬州、惠州等地都有反馈问题。

author: Aiwinn time: 2019-5-30 18:33

xuwei post on2019-5-30 16:58
认证接口改了，依赖的jar包和NDK库改了，NDK库改成了armeabi-v7a，可以先替换libs和jnilibs的所有库文件 ...

新的SDK包运行mpu时选择认证的时候提示请先获取扫描信息，请问怎么获取扫描信息？

author: xuwei time: 2019-5-31 11:21

Aiwinn post on2019-5-30 18:33
新的SDK包运行mpu时选择认证的时候提示请先获取扫描信息，请问怎么获取扫描信息？

右上角有扫描二维码的button,点击后扫描对接的本公司销售人员提供的二维码即可。

author: Aiwinn time: 2019-6-13 18:00

xuwei post on2019-5-30 16:58
认证接口改了，依赖的jar包和NDK库改了，NDK库改成了armeabi-v7a，可以先替换libs和jnilibs的所有库文件 ...

你好，我们现在合入了新的认证，但是发现登录图传服务器失败，弹下面的log，想问下是什么。
I/BVPU: ----------------->PostMessageToNative login
I/BVPU: ----------------->S_ID -> login
I/BVPU: ----------------->S_RESULT -> {"bAECEnable":false,"bNativePlayerEnable":true,"iAECDelay":150,"iAECRoutingMode":2,"iAECSuppressionLevel":1,"iBitrate":32000,"iChannelNum":1,"iEncoder":0,"iSamplePrecision":16,"iSampleRate":8000}
I/BVPU: ----------------->S_FUNCTION -> {"bGPSEnable":1,"iBootDuration":0,"iCmdProtoType":0,"iDeviceID":536957040,"iLatitude":225739300,"iLongitude":1139269570,"iMediaDir":13,"iOnlineThrough":4,"iPlatform":0,"iSerialPortCount":1,"iServerPort":9702,"iStreamPathWay":0,"iVersionCode":1890,"stVideoEncode":{"iBitrate":600000,"iColorFormat":1,"iEncoderType":1,"iFramerate":20,"iHeight":720,"iWidth":1280,"iYUVConvert":6},"szChannelName":"video","szDeviceName":"DSJ-HECH1A1","szDeviceType":"PU","szManufacturer":"smartvideo","szServerAddr":"192.168.102.104","szVersionName":"NA20190524_1890"}
I/BVPU: <-----------------PostMessageToNative
I/BVPU: 192.168.102.104 536957040 13 9702
I/BVPU: bAECEnable = 0,audioCfg->iAECSuppressionLevel = 1,audioCfg->iAECDelay = 150
I/SIP: pMsg->iAction = 0
I/SIP: BVCSP_Login failed!
bResult = -65522
I/BVPU: login ret = 0
I/BVPU: 2019-06-13_17:56:25.650283 <FAIL> RefObject [0xffeaefb8] destroyed with count=2
I/BVPU: 2019-06-13_17:56:25.650613 <FAIL> RefObject::deref() called with count=0 [0xffeaefb8]
I/System.out: szServerAddr=192.168.102.104,szDeviceName=DSJ-HECH1A1,szChannelName=video,iServerPort=9702,iDeviceID=536957040,iMediaDir=13,bGPSEnable=1,iVersionCode=1890,szVersionName=NA20190524_1890,szDeviceType=PU,szManufacturer=smartvideo
I/System.out: bOpenCVManager=0,bFaceDetection=0,bFaceRecognition=0,bFaceRecognitionList=0,iFaceSize=80,iFaceDetectRate=4,iFaceMatchThrd=600

author: Arthur time: 2019-6-13 18:12

Aiwinn post on2019-6-13 18:00
你好，我们现在合入了新的认证，但是发现登录图传服务器失败，弹下面的log，想问下是什么。
I/BVPU: -- ...

没有通过认证，你确定认证过?看下TAG：bvauth。回复1024是认证成功，1025是试用成功。

author: Aiwinn time: 2019-6-13 18:26

Arthur post on2019-6-13 18:12
没有通过认证，你确定认证过?看下TAG：bvauth。回复1024是认证成功，1025是试用成功。

没看到这个TAG，看下这段log
I/BVPU: ------------------>PostToJavaHandler auth
I/BVPU: ------------------>S_ID -> auth
I/BVPU: ------------------>S_RESULT -> {"iAuthStatus": 200, "szAuthType":"auth.type.imei"}
I/BVPU: <------------------PostToJavaHandler
D/AIWINN_BASE: [ MPUService ] onMessageFromNative auth
I/AIWINN_BASE: [ BillTool ] auth---->{"iAuthStatus": 200, "szAuthType":"auth.type.imei"}
I/BVPU: ------------------>PostToJavaHandler auth.update.param
I/BVPU: ------------------>S_ID -> auth.update.param
I/BVPU: ------------------>S_RESULT -> ky62otrHVz8VCLe29kWqn7fU1URkTtQws/asOVr0BND9qmsBYXPjogKHm4YFClv6C894giiEraRC+8g4qo0skgGz+JUx8V86b0/Aql56HhL2vHFS+zKj6eWezkpDudTd9S8kgVI2KwXexvc+f10n1Zd6fX7Nh4StNJMR9tfuHLbfO0bC+v/Uxg7SZH6q6aPulXkFke80KCmeHgm1M7PQYFIeSETCDJDGWItMElWTOnVC+8g4qo0skhjZ7pZIpHmU
I/BVPU: <------------------PostToJavaHandler
D/AIWINN_BASE: [ MPUService ] onMessageFromNative auth.update.param
D/BillTool: param -> ky62otrHVz8VCLe29kWqn7fU1URkTtQws/asOVr0BND9qmsBYXPjogKHm4YFClv6C894giiEraRC+8g4qo0skgGz+JUx8V86b0/Aql56HhL2vHFS+zKj6eWezkpDudTd9S8kgVI2KwXexvc+f10n1Zd6fX7Nh4StNJMR9tfuHLbfO0bC+v/Uxg7SZH6q6aPulXkFke80KCmeHgm1M7PQYFIeSETCDJDGWItMElWTOnVC+8g4qo0skhjZ7pZIpHmU

author: Aiwinn time: 2019-6-13 18:27

Aiwinn post on2019-6-13 18:26
没看到这个TAG，看下这段log
I/BVPU: ------------------>PostToJavaHandler auth
I/BVPU: ----------- ...

我在群里已经授权了id34237

author: Arthur time: 2019-6-13 18:35
那就是调错接口了，要调用BVPU.NewAuth

author: Arthur time: 2019-6-13 18:47
获取Auth_ID用BVPU.NewIMEI。两个接口多了一些必须要填的：billEntity.setSzAppType("MPU"); billEntity.setUserLabel(“你扫描二维码里的Label_ID”);

author: Aiwinn time: 2019-6-13 20:00

Arthur post on2019-6-13 18:47
获取Auth_ID用BVPU.NewIMEI。两个接口多了一些必须要填的：billEntity.setSzAppType("MPU"); billEntity.s ...

另外两个设置了，NewIMEI没设置，我试下，代码改动比较多，对比漏了

author: Aiwinn time: 2019-6-13 20:08

Arthur post on2019-6-13 18:47
获取Auth_ID用BVPU.NewIMEI。两个接口多了一些必须要填的：billEntity.setSzAppType("MPU"); billEntity.s ...

可以了，目前我们没有打算用扫描二维码，我能写死Label_ID么

author: Arthur time: 2019-6-13 20:44

Aiwinn post on2019-6-13 20:08
可以了，目前我们没有打算用扫描二维码，我能写死Label_ID么

写死是可以的，但是以后就只能找拥有这个二维码的人授权了

欢迎光临 mobile CCTV,mobile surveillance,police body worn cameras (http://bbs.besovideo.com:8067/)