WO2014205788A1 - Procédé permettant de synchroniser automatiquement des données entre des dispositifs android intelligents - Google Patents

Procédé permettant de synchroniser automatiquement des données entre des dispositifs android intelligents Download PDF

Info

Publication number
WO2014205788A1
WO2014205788A1 PCT/CN2013/078395 CN2013078395W WO2014205788A1 WO 2014205788 A1 WO2014205788 A1 WO 2014205788A1 CN 2013078395 W CN2013078395 W CN 2013078395W WO 2014205788 A1 WO2014205788 A1 WO 2014205788A1
Authority
WO
WIPO (PCT)
Prior art keywords
master device
data
adb
synchronization
yes
Prior art date
Application number
PCT/CN2013/078395
Other languages
English (en)
Chinese (zh)
Inventor
翁杰军
Original Assignee
深圳市掌讯通讯设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市掌讯通讯设备有限公司 filed Critical 深圳市掌讯通讯设备有限公司
Priority to PCT/CN2013/078395 priority Critical patent/WO2014205788A1/fr
Publication of WO2014205788A1 publication Critical patent/WO2014205788A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Definitions

  • the present invention relates to automatic installation of computer software, and particularly relates to a method for automatically synchronizing data between Android (Intel) smart devices, especially between an intelligent in-vehicle system and a mobile phone/tablet.
  • Android Intel
  • MP3 audio files, MP4 video files are downloaded repeatedly; in the second aspect, after interrupting the application on one device and then switching to other devices, it is difficult to connect; there are some Android smart devices, such as: traditional intelligent car system, generally using 3rd generation mobile communication (3G) network, it is difficult to use wireless local area network (wifi), and downloading MP3 audio files, MP4 video files, huge traffic, limiting their application in intelligent in-vehicle systems. And the traditional way to save traffic, the operation is complex and requires users Mastering certain basic skills is therefore difficult to promote.
  • 3G 3rd generation mobile communication
  • wifi wireless local area network
  • the technical problem to be solved by the present invention is how to provide an automatic data synchronization method between Android smart devices, which can eliminate the need to repeatedly download the same data in multiple devices, and only need USB data line to realize data and software synchronization, saving 3G. Traffic, and further automated installation of licensed software.
  • step 101 Does the master detect its own USB port for device access? Yes, proceed to step 102), otherwise return to step 101);
  • the master device invokes the adb internal shell command to access the specified files that exist in all authorized slave devices or all slave devices;
  • the master device invokes the adb internal shell command to obtain the slave device synchronization list file;
  • Incremental synchronization The master device calls the adb internal shell command one by one for each file in the synchronization list. The data on the device is written to the slave device, or the adb internal shell command is invoked to acquire the data on the slave device and written to the master device; all the files in the synchronization list are all executed and proceed to step 110);
  • steps 101) and 102) further include the steps of opening the USB-OTG function:
  • the main device checks if the USB-OTG function is turned on normally? Yes, proceed to step 102), otherwise proceed to step 202);
  • USB-OTG USB-OTG
  • the adb internal shell command includes 'cat', 'pull' or 'push', and the specified file in this step is required to install the specified software application. Use the file.
  • step 104 after determining that the access fails, the software installation steps are also included:
  • the master device invokes the adb internal shell command to access the specified file that exists in all slave devices; [27] 402) Does the master device determine whether the access is successful? Yes, go to step 403), otherwise prompt the user
  • the main device prompts the user to choose to install the software application, to determine whether the user chooses to install? Yes, proceed to step 404), otherwise proceed to step 110);
  • the master device calls the adb internal 'install' shell command to send the specified APK to the slave device for software installation;
  • the adb internal shell command in step 401) includes 'cat', 'pull' or 'push', and the specified file is a core file of the Android system.
  • the synchronized data includes, but is not limited to, one or more of user setting data, audio files or video files in the software application, according to the present invention.
  • the master device determines whether the user selects whether to synchronize data? If yes, go to step 702), otherwise, directly exit the user selection step and proceed to step 110;
  • the method further includes, before step 107), the master device automatically generates a master device corresponding synchronization list by scanning the file in the specified directory or location. file.
  • the method if the master device corresponding to the synchronization list file is lost, the method skips steps 107) and 108) and proceeds directly to step 109).
  • the full synchronization further includes: incrementally or completely writing all the specified data of the master device. Into the slave device.
  • a method for automatically synchronizing data between in-vehicle Android smart devices is constructed, which is characterized in that the main device using the USB-OTG and the slave device running the adbd process include the following specific steps:
  • step 1001) Does the master detect its own USB port for device access? Yes, proceed to step 1002), otherwise return to step 1001);
  • step 1002 Does the master check if the USB-OTG function is normal? Go to step 1003), otherwise go to step 1003 after snoring;
  • the master device starts the adb service
  • the master device invokes the adb internal shell command to access the required installation files for the specified software application;
  • the master device determines whether the access is successful? Yes, go to step 1006), otherwise go to step Step 1011);
  • the master device invokes the adb internal shell command to obtain the slave device synchronization list file and read its corresponding synchronization list file;
  • step 1007 Is the master device successful? Yes, go to step 1008), otherwise go to step 1010)
  • the master device compares the synchronization list file acquired by the slave device with the corresponding synchronization list file to generate a synchronization list
  • Incremental synchronization The master device calls the adb internal shell command one by one according to each file in the synchronization list to write data on the master device to the slave device, or calls the adb internal shell command to obtain data from the slave device and writes it to the master device; All the files in the process are completed and proceed to step 1017);
  • the master device calls the adb internal shell command to obtain all specified data from the slave device and write it to the master device; the specified data is all data in the specified location or directory or all specified class data in the specified location or directory. Go to step 1017);
  • the master device invokes the adb internal shell command to access the core file of the Android system
  • the master device determines whether the access is successful? If yes, go to step 1013), otherwise prompt the user, including: Check whether the USB connection is unblocked or check whether the slave device adbd process is enabled, return to step 1011) or go to step 1017);
  • the master device prompts the user to choose to install the software application, and determines whether the user chooses to install. Yes, go to step 1014), otherwise go to step 1017);
  • the master device calls the adb internal 'install' shell command to send the specified APK to the slave device for software installation;
  • the master device receives and prompts the user
  • the full synchronization further includes: Advantageous effects of the invention
  • the method for automatically synchronizing data between Android smart devices provided by the present invention has the following advantages over the prior art:
  • FIG. 1 is a schematic structural diagram of an interconnection control model of an intelligent in-vehicle system and a mobile phone according to the present invention
  • FIG. 2 is a schematic diagram of an automatic program installation process in the intelligent in-vehicle system corresponding to FIG. 1;
  • FIG. 3 is a schematic diagram of a data synchronization process in the intelligent in-vehicle system corresponding to FIG. 1;
  • FIG. 4 is a schematic diagram of the control flow of the sync extension command used by the intelligent vehicle system in FIG.
  • the automatic installation and synchronization method of the software between the Android smart devices of the invention is implemented between the intelligent vehicle system and the mobile phone I tablet, and the intelligent vehicle system can automatically install the mobile phone companion software application to the mobile phone/tablet terminal, and can install the mobile phone with Automatic data synchronization between your partner's Android smartphone/tablet.
  • the USB communication connection control module architecture of the present invention is: The interconnection communication control of the intelligent vehicle system and the mobile phone is based on the USB cable connection, the intelligent vehicle system is the main device, and the mobile phone is the slave device.
  • the master device needs to support and play the USB-OTG function, then start the adb service, then call the adb shell command through the adb service, package/unpack the protocol layer and the underlying driver, and finally connect the slave device: the mobile phone, and the mobile terminal Need to hiccup and run the adbd process.
  • the smart in-vehicle system (master device) of the present invention it is directed to an Android smartphone (slave device)
  • the master device starts the adb service
  • the master device calls the adb internal cat/pull/push shell command to access all the specified files that exist in the slave device;
  • the specified file may be the core file of the Android system;
  • the master device calls the adb internal 'install' shell command to send the mobile companion APK to the slave device for software installation;
  • the slave device only has to run the adbd process.
  • a control program for automatically synchronizing data with a mobile phone (slave device) to which the mobile phone companion software application of the present invention is installed includes the following steps:
  • the master device starts the adb service
  • the master device calls the adb internal cat/pull/push shell command to access the specified files that exist in all the slave devices;
  • the specified file may be the mobile phone companion core file;
  • the master device determines whether the access is successful? If yes, go to step 3007), otherwise the user is prompted to go to step 3009) or not to go directly to step 3009);
  • the master device invokes the custom adb extension command 'sync' in the present invention to synchronize data with the slave device;
  • the slave device only has to run the adbd process.
  • the custom adb extension command 'sync' of the present invention specifically includes the following steps:
  • the master device calls the adb cat/pull shell command to read the slave device synchronization list file;
  • the master device compares the synchronization list file acquired by the slave device with its own corresponding synchronization list file to generate a synchronization list;
  • the master device calls the adb internal push shell command one by one to write the data on the master device to the slave device, or calls the adb cat/pull shell command to obtain the data on the slave device and write it to the master device. After the files in the synchronization list are all executed, proceed to step 4007);
  • the master device calls the adb cat/pull shell command to get all the file data in the specified directory from the slave device and write it to the master device;
  • the synchronized data mainly refers to an MP3 file, an MP4 file, and a mobile phone companion software user setting file data.
  • the method for automatically synchronizing data between Android smart devices provided by the present invention can also be applied between a mobile phone and a mobile phone, between a mobile phone and a tablet computer, between a tablet computer and an in-vehicle device, and the like.
  • the method for automatically synchronizing data between Android smart devices provided by the present invention is more direct, simple, and greatly reduces the outstanding advantages of repetitive work, and can avoid generating a large amount of network traffic, and is especially used by a large number of users.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention concerne un procédé permettant de synchroniser automatiquement des données entre des dispositifs Android intelligents à l'aide d'un dispositif maître USB-OTG et d'un dispositif esclave avec un processus adbd. Le procédé comprend les étapes suivantes : 101) le dispositif maître détecte si un dispositif USB est accédé; si tel est le cas, il passe à 102), dans le cas contraire, il retourne à 101); 102) il démarre un service adb; 103) il appelle une commande Shell adb pour accéder à un fichier spécifié; 104) il détermine si l'accès a réussi; si tel est le cas, il passe à 105), dans le cas contraire, il sort; 105) il acquiert des fichiers de listes synchrones d'extrémité de dispositif maître/esclave; 106) il détermine si l'acquisition a réussi; si tel est le cas, il passe à 107), dans le cas contraire, il va à 109); 107) il compare les fichiers de listes synchrones des deux parties pour générer une liste de synchronisation; 108) il appelle graduellement des commandes Shell adb, une par une, selon la liste de synchronisation pour écrire des données présentes sur le dispositif maître dans le dispositif esclave ou, inversement, jusqu'à ce que la liste soit terminée, et passe à 110); 109) il appelle des commandes Shell adb, acquiert toutes les données spécifiées à partir du dispositif esclave, et écrit les données dans le dispositif maître; et 110) fin.
PCT/CN2013/078395 2013-06-28 2013-06-28 Procédé permettant de synchroniser automatiquement des données entre des dispositifs android intelligents WO2014205788A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/078395 WO2014205788A1 (fr) 2013-06-28 2013-06-28 Procédé permettant de synchroniser automatiquement des données entre des dispositifs android intelligents

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/078395 WO2014205788A1 (fr) 2013-06-28 2013-06-28 Procédé permettant de synchroniser automatiquement des données entre des dispositifs android intelligents

Publications (1)

Publication Number Publication Date
WO2014205788A1 true WO2014205788A1 (fr) 2014-12-31

Family

ID=52140868

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/078395 WO2014205788A1 (fr) 2013-06-28 2013-06-28 Procédé permettant de synchroniser automatiquement des données entre des dispositifs android intelligents

Country Status (1)

Country Link
WO (1) WO2014205788A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453766A (zh) * 2015-08-04 2017-02-22 阿里巴巴集团控股有限公司 基于虚拟机的数据传输方法、装置及系统
CN107977318A (zh) * 2017-12-25 2018-05-01 暨南大学 一种Android应用程序的能耗和性能测试方法
CN108536491A (zh) * 2018-02-07 2018-09-14 武汉光庭信息技术股份有限公司 一种车载设备反向控制安卓移动终端的处理方法及系统
CN113672876A (zh) * 2021-10-21 2021-11-19 南京拓界信息技术有限公司 基于otg的手机快速取证方法和装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102681993A (zh) * 2011-03-07 2012-09-19 联想(北京)有限公司 一种文件同步方法、文件同步装置及第一电子设备
CN102932439A (zh) * 2012-10-26 2013-02-13 华为终端有限公司 一种内容同步的方法和装置
CN103077058A (zh) * 2013-01-06 2013-05-01 邓海勤 一种安装应用程序的方法及装置
CN103092495A (zh) * 2011-11-01 2013-05-08 茂杰国际股份有限公司 触控装置的同步操作系统及方法
CN103108050A (zh) * 2013-02-27 2013-05-15 广州长嘉电子有限公司 一种实现平板电脑同步移动终端电话薄的方法及系统
CN103369037A (zh) * 2013-06-28 2013-10-23 深圳市掌讯通讯设备有限公司 一种安卓智能设备间数据自动同步方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102681993A (zh) * 2011-03-07 2012-09-19 联想(北京)有限公司 一种文件同步方法、文件同步装置及第一电子设备
CN103092495A (zh) * 2011-11-01 2013-05-08 茂杰国际股份有限公司 触控装置的同步操作系统及方法
CN102932439A (zh) * 2012-10-26 2013-02-13 华为终端有限公司 一种内容同步的方法和装置
CN103077058A (zh) * 2013-01-06 2013-05-01 邓海勤 一种安装应用程序的方法及装置
CN103108050A (zh) * 2013-02-27 2013-05-15 广州长嘉电子有限公司 一种实现平板电脑同步移动终端电话薄的方法及系统
CN103369037A (zh) * 2013-06-28 2013-10-23 深圳市掌讯通讯设备有限公司 一种安卓智能设备间数据自动同步方法

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453766A (zh) * 2015-08-04 2017-02-22 阿里巴巴集团控股有限公司 基于虚拟机的数据传输方法、装置及系统
CN106453766B (zh) * 2015-08-04 2019-04-09 阿里巴巴集团控股有限公司 基于虚拟机的数据传输方法、装置及系统
CN107977318A (zh) * 2017-12-25 2018-05-01 暨南大学 一种Android应用程序的能耗和性能测试方法
CN107977318B (zh) * 2017-12-25 2020-07-03 暨南大学 一种Android应用程序的能耗和性能测试方法
CN108536491A (zh) * 2018-02-07 2018-09-14 武汉光庭信息技术股份有限公司 一种车载设备反向控制安卓移动终端的处理方法及系统
CN108536491B (zh) * 2018-02-07 2021-11-05 武汉光庭信息技术股份有限公司 一种车载设备反向控制安卓移动终端的处理方法及系统
CN113672876A (zh) * 2021-10-21 2021-11-19 南京拓界信息技术有限公司 基于otg的手机快速取证方法和装置
CN113672876B (zh) * 2021-10-21 2022-02-01 南京拓界信息技术有限公司 基于otg的手机快速取证方法和装置

Similar Documents

Publication Publication Date Title
CN103365688B (zh) 一种安卓智能设备间软件自动安装与同步方法
US8634761B2 (en) Cross-transport authentication
US8843664B2 (en) Re-enumeration of USB 3.0 compatible devices
CN101315605A (zh) 基于usb端口的平板电视软件自动升级方法
WO2014205788A1 (fr) Procédé permettant de synchroniser automatiquement des données entre des dispositifs android intelligents
WO2014194865A1 (fr) Procédé et appareil de mise à niveau de micrologiciel, et dispositif de communication
EP2476078A1 (fr) Authentification d'un dispositif accessoire
CN102402452B (zh) 一种编译方法及装置
CN103369037A (zh) 一种安卓智能设备间数据自动同步方法
WO2013178032A1 (fr) Procédé et système de commutation intelligente pour noyau de navigateur
CN105786606A (zh) 一种用于智能终端间的数据转移的方法和系统
CN104657161A (zh) 移动终端固件更新方法及装置
WO2020228033A1 (fr) Procédé et appareil de chargement de module d'extension sdk, et terminal mobile et support de stockage
CN102945178B (zh) 一种用于减少安卓电视第一次启动时间的处理方法及系统
WO2014205765A1 (fr) Procédé permettant une installation automatique et une synchronisation logicielle entre des dispositifs android intelligents
WO2015172283A1 (fr) Procédé, dispositif et terminal mobile permettant de réduire la consommation d'énergie
US10007529B2 (en) Data terminal running mode switching method, device, and data terminal
CN102314379B (zh) Pc操作系统与智能移动设备操作系统间交互的方法
KR102226379B1 (ko) 일종의 시스템 펌웨어의 버닝 스피드 향상 방법
CN111901651A (zh) 蓝牙遥控器唤醒处理方法、装置
CN103905647B (zh) 在静音模式下利用音量键设置静音时段的方法及移动终端
CN106815024A (zh) 一种优化移动终端开机时间的方法及系统
CN102237115A (zh) 一种测试方法和相应的测试系统
JP2006178534A (ja) 情報処理装置及びドライバソフトのインストール制御方法
CN103838603A (zh) 一种提升android电视首次开机速度的方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13887723

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13887723

Country of ref document: EP

Kind code of ref document: A1