CN103731802A - Device management method based on Android mobile terminal - Google Patents
Device management method based on Android mobile terminal Download PDFInfo
- Publication number
- CN103731802A CN103731802A CN201210389007.8A CN201210389007A CN103731802A CN 103731802 A CN103731802 A CN 103731802A CN 201210389007 A CN201210389007 A CN 201210389007A CN 103731802 A CN103731802 A CN 103731802A
- Authority
- CN
- China
- Prior art keywords
- message
- android mobile
- mobile device
- server
- service end
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The invention provides a device management method based on an Android mobile terminal. The method includes the following steps that first, a message push server and a device management server are deployed; second, a user runs a client side application of the Android mobile terminal, and information of the mobile terminal is sent to the device management server to be registered; third, the information of the Android mobile terminal is checked by a server side; fourth, after the check passes, the server side returns the message to the mobile terminal; fifth, the message or the device management instruction is pushed to the Android mobile device from the server side, the message push server pushes the message to the Android mobile device through an XMPP; sixth, the client side of the Android mobile device applies actuating device management operation or responds to and displays the push message on the interface of the client side. With the method, the mobile device can be easily and effectively managed, the business notification requirement of an enterprise for the mobile device and safety management needs are met.
Description
Technical field
The present invention relates to Android mobile terminal, particularly, relate to message push mechanism (the Push Notification based on Android mobile terminal, be called for short PN), can be widely used in the equipment control (Mobile Device Management is called for short MDM) of Android mobile terminal.
Background technology
In recent years, along with gradually becoming strong of the develop rapidly of development of Mobile Internet technology and the function of intelligent mobile device, the use of mobile device was more and more extensive.For enterprise, use mobile device access enterprises service, check business data, carry out business operation and become trend.Thing followed problem is, user's mobile device Bu Shou enterprise controls, once this just means, occurs that mobile device is lost, the situation such as stolen, and the sensitive data of enterprise and vital strategic secrets are just faced with the danger of being revealed.For the problems referred to above, Android platform has proposed the solution of oneself, by the mode of message push, reaches the object of controlling concrete mobile device from service end.
So-called message push, refers to the equipment sending message that device management server can initiatively be managed to it.
So-called mobile device management, refer to can unified management registration by application server mobile device.Comprise locking device screen, change screen locking password, the functions such as erasing apparatus data.
Since Android 2.2 versions, Google has introduced Cloud to Device Messaging (C2DM) framework, C2DM is a kind of Android message push mechanism that Google official proposes, at up-to-date Android4.0 version, Google has proposed again Google Cloud Messaging scheme, and no longer supports original C2DM scheme.(but can move to GCM from C2DM) above-mentioned two schemes is all that the server by Google carrys out PUSH message.
Use C2DM or GCM all to require the Android device systems will be more than 2.2, and system should comprise GoogleServiceFrameWork(GSF) module, on the version lower than 4.04, also need to login especially an effective Google account.
End is got up, and uses existing technical scheme to have following two problems:
1. due to when using C2DM service, need to be in the server registration C2DM of Google account, and general Android mobile device does not comprise GoogleServicesFramework service module, therefore cannot realize and the communicating by letter of Google server.
2. the whole transport process that message is pushed to mobile device terminal from service end all will forward by the server of Google, and within the scope of China's Mainland, Google server cannot connect sometimes, and stability cannot guarantee.
Therefore to sum up analyze, this technical scheme that Google proposes is very insecure at home.
Chinese Patent Application No. is 200710175902.9 patent of invention, this invention relates to a kind of customized information pushing system and method based on mobile terminal management service, comprise the mobile terminal that carries out communication by wireless carrier network, terminal management business operating platform, terminal management business server, information service customization device and Information Push Server, after mobile terminal registration, by terminal management business server, obtain the terminal ability information relevant to mobile terminal and customized information is accepted configuration data, generation meets the customized information of described capacity of mobile terminal and customized information receiving ability, and be distributed to corresponding described Information Push Server and carry out information pushing, thereby described customized information is sent to described mobile terminal.
The kind of 200710175902.9 pairs of mobile devices of foregoing invention does not require and can push and comprises short message, multimedia message, the information such as mail, equipment manager and message push service device deployment request are relatively high. and the realization of the message push mechanism of foregoing invention more depends on information service operator, the propelling movement of message can produce service fee, not the propelling movement on essential meaning.And the information pushing can only make notice and use, systemic-function that can not trigger equipment, obliterated data for example, lock-screen etc., the safety management requirement that does not reach MDM.
Because enterprise-level moves promoting the use of of application, the fail safe of mobile device is more and more paid attention to.Thereby enterprise is also more and more urgent to the regulatory requirement of mobile device.The important content of mobile device management is exactly the message push mechanism of management end and mobile terminal.The present invention is directed to the limitation that the message push mechanism (C2DM and GCM) of Android self exists, propose a new message push scheme and for equipment control.
Summary of the invention
For defect of the prior art, the object of this invention is to provide a kind of equipment control scheme based on Android mobile terminal, can the simple and effective management of carrying out Android mobile device, meet enterprise the service announcements of mobile device is required and safety management needs.
To achieve these goals, the invention provides a kind of equipment control scheme based on Android mobile terminal.This scheme need to be disposed independently message push service device, Android mobile device equipment requiring installation administrative client application (hereinafter to be referred as client application).
Described scheme totally comprises the steps:
Step 1: dispose message push service device and device management server
For fear of use restriction and the lot of unstable factor of the server of Google, the present invention, with reference to the realization mechanism of C2DM, has customized server, and server comprises device management server and message push service device.Device management server stores the server of the Android mobile device information of registration, and message push service device is for being responsible for the server from service end to registered Android mobile device PUSH message.Whole service end also provides an administration interface, by the mode of web browser, implements concrete push operation.
The MINA framework of Apache has been used in the realization of server, and message push is used XMPP agreement, and final service end is deployed in Jetty container.
Step 2: user moves the client application of Android mobile terminal, is sent to device management server by the information of Android mobile terminal and registers
The client application that Android mobile terminal is installed to describe in step 1 device management server registration time, need to use APIKey that service end provides and the address of service end.Log-on message comprises the IMEI number (unique) of equipment, operating system version, unit type, network type.
Step 3: service end is examined the information of Android mobile device
The APIKey that service end checking needs the Android mobile device of registration, determines that this equipment is by service end mandate.And verify the log-on message of Android mobile device, and generate UUID according to the IMEI number of Android mobile device, for the Android mobile device of unique definite registration.
Step 4: after audit is passed through, service end is to mobile terminal return messages.So far step mobile device is successfully registered to device management server.
Service end administrative staff examine after facility registration information, and the equipment Management Function of authorizing Android mobile device to use service end to provide is provided.
Step 5: service end provides a web-based management operation interface, by browser, from service end to Android mobile device PUSH message or device management instruction.Message push service device passes through XMPP agreement to Android mobile device PUSH message.
Service end administrative staff are by the operation interface of service end, the presence (whether whether Android mobile device starts network is connected) of current registered all devices and equipment be can check, by message push interface, common simple message or equipment associated instructions inputted.Message push is used XMPP agreement.
The client application of step 6:Android mobile device receives and pushes after instruction, carries out corresponding device management operations.While receiving common message, in client end interface response, show PUSH message.
In Android mobile device management client, the present invention is calling function class ServiceManager in main thread, for starting service class NotificationService.This service class is responsible for the message receiving to process.When Server end (service end) sends message, by function class, NotificationReceiver is responsible for reception, and transmits the message in function class Notifier.Class Notifier is responsible for message judge and screen, and invocation facility Administration API, carries out the corresponding command.
Compared with prior art, the present invention has following beneficial effect: the present invention is the lot of unstable factor of avoiding the links such as Google server registration, connection, message push, the facility management client application of having built the message push service device of oneself and having developed Android mobile device.Apparatus manager directly pushes supervisory instruction by XMPP agreement to mobile device by service end management tool, mobile device is after receiving instruction, client application by mobile device management manages equipment, and organize content comprises wipes all data, change screen locking password, lock-screen etc.The present invention can the simple and effective management of carrying out Android mobile device, meets enterprise the service announcements of mobile device is required and safety management needs.
Accompanying drawing explanation
By reading the detailed description of non-limiting example being done with reference to the following drawings, it is more obvious that other features, objects and advantages of the present invention will become:
Fig. 1 is the inventive method flow chart;
Fig. 2 is the C2DM realization flow figure of Google;
Fig. 3 is functional module call graph;
Fig. 4 is for pushing common message schematic diagram;
Fig. 5 is interface display message schematic diagram;
Fig. 6 is for pushing screen locking instruction schematic diagram;
Fig. 7 is lock-screen schematic diagram.
Embodiment
Below in conjunction with specific embodiment, the present invention is described in detail.Following examples will contribute to those skilled in the art further to understand the present invention, but not limit in any form the present invention.It should be pointed out that to those skilled in the art, without departing from the inventive concept of the premise, can also make some distortion and improvement.These all belong to protection scope of the present invention.
As shown in Figure 1, the present embodiment can be implemented as follows:
Step 1: service end administrative staff start server, opens device management operations interface by browser;
The MINA framework of Apache has been used in the realization of server, and message push is used XMPP agreement, and final service end is deployed in Jetty container.The key code that server is realized is described in detail in step 5.
Step 2: open an Android mobile device that facility management client has been installed, and guarantee to have opened network connection (WIFI, 3G, GPRS etc.), now equipment can, according to the address of service active connection server configuring in client application, establish a connection.
Connect after foundation, the client application that Android mobile device is installed is to server registration.In Android mobile device when registration, need to be used APIKey that server provides and the address of server.These information by server authorizes to facility management client.The log-on message of Android mobile device self comprises the IMEI number (unique) of equipment, operating system version, unit type, network type.In this step corresponding diagram 1, process 1..
Step 3: the APIKey of the Android mobile device that server authentication need to be registered, determine that this equipment is by server authorizes, and verify the log-on message of Android mobile device, according to the IMEI number of Android mobile device, generate UUID, for the Android mobile device of unique definite registration.
Server admin personnel examine after facility registration information, and the equipment Management Function of authorizing Android mobile device to use service end to provide is provided.After audit is passed through, service end is to mobile terminal return messages.In this step corresponding diagram 1, process 2..
Step 4: server provides a web-based management operation interface (as described in step 1), by browser, from server to Android mobile device PUSH message or device management instruction.In this step corresponding diagram 1, process 3..
Step 5: administrative staff can find to have installed at equipment control interface the Android mobile device of facility management client, after message push interface input message, can carry out concrete message push operation;
In the present embodiment, while pushing common message, as shown in Figure 4, the message content that administrative staff input in input frame is ' This is a MDM application of iPlat4M ';
While pushing screen locking instruction, as shown in Figure 6; The command content that administrative staff input in input frame is ' iPlat4M_MDM_Command_LockScreen ';
In the present embodiment, message push service device passes through XMPP agreement to Android mobile device PUSH message.The key code of message push service device XMPPServer specific implementation:
Above-mentioned code has mainly been described establishment XMPPServer example, starts and stop the interface of XMPPServer.In the present embodiment, message push service device is responsible for the main code of message push:
Above-mentioned code description the propelling movement interface of message push administrative class, message push comprises the broadcast Android mobile device of all registrations (message push to) and pushes to the Android mobile device of the registration of appointment.
Step 6:Android equipment receives after the PUSH message of server, in interface display message (as shown in Figure 5), receive after supervisory instruction, client application can be according to the equipment control interface of command content calling system (DeviceAdministration API), management and control devices (as shown in Figure 7, lock-screen), thus reach from the object of service end management mobile device.As process in Fig. 1 4..
In the present embodiment, the specific implementation of Android mobile device management client application:
Calling function class ServiceManager in the main thread of client application, for starting service class NotificationService.This service class is responsible for the message receiving to process.When Server end (message promotion server) sends message, by function class, NotificationReceiver is responsible for reception, and transmits the message in function class Notifier.Class Notifier is responsible for message judge and screen, and invocation facility Administration API, carries out the corresponding command.As shown in Figure 3.
Facility management client realizes the remote lock of mobile device and data erase by calling DeviceAdministration API (equipment control API).Equipment control API comprises following three function classes:
DeviceAdminReceiver a: base class of realizing device management component
DevicePolicyManager: for the treatment of the security strategy of equipment, the operation of actuating equipment management must realize class DeviceAdminReceiver before
DeviceAdminInfo: the information that is used to specify an apparatus assembly
The step that realizes remote device management function is as follows:
Authorisation device administration authority
Before using the Device Administration API of Android, need in xml file, define two security strategies: device lock fixed sum data is wiped
Then create the subclass of DeviceAdminReceiver and in AndroidMainfest.xml file, this Receiver registered and added " BIND_DEVICE_ADMIN " authority.
Equipment control initialization
After completing user is to the mandate of equipment, need to carry out initialization to the correlation function class of equipment control:
Far-end message sink
By the long-range transmission message of service end, it is as follows that mobile terminal is responsible for the code of receipt message:
Actuating equipment locking/data erase
After receiving message, message is judged and is screened, and call API and carry out message:
Above specific embodiments of the invention are described.It will be appreciated that, the present invention is not limited to above-mentioned specific implementations, and those skilled in the art can make various distortion or modification within the scope of the claims, and this does not affect flesh and blood of the present invention.
Claims (6)
1. the device management method based on Android mobile terminal, is characterized in that described method comprises the steps:
Step 1: dispose message push service device and device management server: with reference to the realization mechanism customization server of C2DM, server comprises device management server and message push service device, device management server stores the server of the Android mobile device information of registration, and message push service device is for being responsible for the server from service end to registered Android mobile device PUSH message; Whole service end also provides an administration interface, by the mode of web browser, implements concrete push operation;
Step 2: user moves the client application of Android mobile terminal, is sent to device management server by the information of Android mobile terminal and registers; The client application that Android mobile terminal is installed to describe in step 1 device management server registration time, need to use APIKey that service end provides and the address of service end;
Step 3: service end is examined the information of Android mobile device: service end checking needs the APIKey of the Android mobile device of registration, determine that this equipment is by service end mandate, and verify the log-on message of Android mobile device, and generate UUID according to the IMEI number of Android mobile device, for the Android mobile device of unique definite registration;
Step 4: after audit is passed through, service end is to mobile terminal return messages; So far step mobile device is successfully registered to device management server;
Step 5: service end provides a web-based management operation interface, by browser, from service end to Android mobile device PUSH message or device management instruction, message push service device passes through XMPP agreement to Android mobile device PUSH message;
The client application of step 6:Android mobile device receives and pushes after instruction, carries out corresponding device management operations; While receiving common message, in client end interface response, show PUSH message.
2. the device management method based on Android mobile terminal according to claim 1, is characterized in that, in step 1, the MINA framework of Apache is used in the realization of server, and message push is used XMPP agreement, and final service end is deployed in Jetty container.
3. the device management method based on Android mobile terminal according to claim 1, is characterized in that, in step 2, log-on message comprises the IMEI number of equipment, operating system version, unit type, network type.
4. the device management method based on Android mobile terminal according to claim 1, it is characterized in that, in step 4, service end administrative staff examine after facility registration information, and the equipment Management Function of authorizing Android mobile device to use service end to provide is provided.
5. the device management method based on Android mobile terminal according to claim 1, it is characterized in that, in step 5, service end administrative staff are by the operation interface of service end, can check the presence of current registered all devices and equipment, whether whether Android mobile device starts network connects, and by message push interface, inputs common simple message or equipment associated instructions, and message push is used XMPP agreement.
6. the device management method based on Android mobile terminal according to claim 1, it is characterized in that, in step 6, in Android mobile device management client, calling function class ServiceManager in main thread, for starting service class NotificationService, this service class is responsible for the message receiving to process, when service end sends message, by function class, NotificationReceiver is responsible for reception, and transmits the message in function class Notifier; Function class Notifier is responsible for message judge and screen, and invocation facility Administration API, carries out the corresponding command.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210389007.8A CN103731802A (en) | 2012-10-12 | 2012-10-12 | Device management method based on Android mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210389007.8A CN103731802A (en) | 2012-10-12 | 2012-10-12 | Device management method based on Android mobile terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103731802A true CN103731802A (en) | 2014-04-16 |
Family
ID=50455694
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210389007.8A Pending CN103731802A (en) | 2012-10-12 | 2012-10-12 | Device management method based on Android mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103731802A (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104821939A (en) * | 2015-04-10 | 2015-08-05 | 百度在线网络技术（北京）有限公司 | Method for realizing asynchronous communication between computer and mobile equipment, and device thereof |
| CN105005201A (en) * | 2015-06-04 | 2015-10-28 | 广东康宝电器股份有限公司 | Multi-mobile-terminal data synchronization and push system for intelligent household |
| CN105450514A (en) * | 2015-12-31 | 2016-03-30 | 惠州Tcl移动通信有限公司 | Message pushing method and system based on XMPP |
| CN105634912A (en) * | 2014-11-19 | 2016-06-01 | 镇江金软计算机科技有限责任公司 | Message pushing method based on Android system |
| CN105897884A (en) * | 2016-04-07 | 2016-08-24 | 四川大学 | Android mobile phone push platform based on eXtensive messaging presence protocol (XMPP) |
| CN105959152A (en) * | 2016-06-23 | 2016-09-21 | 北京北信源软件股份有限公司 | Terminal management method and system |
| CN106487767A (en) * | 2015-08-31 | 2017-03-08 | 阿里巴巴集团控股有限公司 | The update method of checking information and device |
| CN107741884A (en) * | 2017-10-09 | 2018-02-27 | 武汉斗鱼网络科技有限公司 | The method and apparatus that a kind of stratification state machine realizes message push |
| CN108270798A (en) * | 2018-03-25 | 2018-07-10 | 上海金亥通信设备有限公司 | A kind of mobile terminal device safety management system |
| CN109314713A (en) * | 2016-06-30 | 2019-02-05 | 华为技术有限公司 | Support system, equipment and the process of the mobile device management of multiple containers in virtualized environment |
| CN109347649A (en) * | 2018-08-01 | 2019-02-15 | 北京奇安信科技有限公司 | A kind of strong management-control method of mobile device and device |
| US10616035B1 (en) * | 2018-01-30 | 2020-04-07 | EMC IP Holding Company LLC | Methods and apparatus for device chat and management |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1665199A (en) * | 2004-11-19 | 2005-09-07 | 中国移动通信集团公司 | Method for push of service parameter information actively initiated by network management center |
| CN101141698A (en) * | 2007-10-15 | 2008-03-12 | 中兴通讯股份有限公司 | Customized information pushing system and method based on mobile terminal management service |
| US20110029598A1 (en) * | 2009-07-31 | 2011-02-03 | Z2Live Technologies | Mobile device notification controls system and method |
| CN102395102A (en) * | 2011-10-25 | 2012-03-28 | 华为终端有限公司 | Processing method of lost mobile terminal, related apparatus and communication system |
| CN102724324A (en) * | 2012-06-28 | 2012-10-10 | 用友软件股份有限公司 | Information pushing and integrating device and information pushing and integrating method |
-
2012
- 2012-10-12 CN CN201210389007.8A patent/CN103731802A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1665199A (en) * | 2004-11-19 | 2005-09-07 | 中国移动通信集团公司 | Method for push of service parameter information actively initiated by network management center |
| CN101141698A (en) * | 2007-10-15 | 2008-03-12 | 中兴通讯股份有限公司 | Customized information pushing system and method based on mobile terminal management service |
| US20110029598A1 (en) * | 2009-07-31 | 2011-02-03 | Z2Live Technologies | Mobile device notification controls system and method |
| CN102395102A (en) * | 2011-10-25 | 2012-03-28 | 华为终端有限公司 | Processing method of lost mobile terminal, related apparatus and communication system |
| CN102724324A (en) * | 2012-06-28 | 2012-10-10 | 用友软件股份有限公司 | Information pushing and integrating device and information pushing and integrating method |
Non-Patent Citations (2)
| Title |
|---|
| CHENGDOU237: "Androidpn消息推送协议", 《百度文库》 * |
| PS5123: "Android推送框架androidpn", 《百度文库》 * |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634912A (en) * | 2014-11-19 | 2016-06-01 | 镇江金软计算机科技有限责任公司 | Message pushing method based on Android system |
| CN104821939B (en) * | 2015-04-10 | 2018-06-05 | 百度在线网络技术（北京）有限公司 | It is a kind of to be used to implement computer and the method and apparatus of mobile equipment room asynchronous communication |
| CN104821939A (en) * | 2015-04-10 | 2015-08-05 | 百度在线网络技术（北京）有限公司 | Method for realizing asynchronous communication between computer and mobile equipment, and device thereof |
| CN105005201A (en) * | 2015-06-04 | 2015-10-28 | 广东康宝电器股份有限公司 | Multi-mobile-terminal data synchronization and push system for intelligent household |
| CN106487767B (en) * | 2015-08-31 | 2020-01-21 | 阿里巴巴集团控股有限公司 | Method and device for updating verification information |
| CN106487767A (en) * | 2015-08-31 | 2017-03-08 | 阿里巴巴集团控股有限公司 | The update method of checking information and device |
| US10880306B2 (en) | 2015-08-31 | 2020-12-29 | Alibaba Group Holding Limited | Verification information update |
| CN105450514A (en) * | 2015-12-31 | 2016-03-30 | 惠州Tcl移动通信有限公司 | Message pushing method and system based on XMPP |
| CN105450514B (en) * | 2015-12-31 | 2020-05-15 | 惠州Tcl移动通信有限公司 | XMPP-based message pushing method and system |
| CN105897884A (en) * | 2016-04-07 | 2016-08-24 | 四川大学 | Android mobile phone push platform based on eXtensive messaging presence protocol (XMPP) |
| CN105959152A (en) * | 2016-06-23 | 2016-09-21 | 北京北信源软件股份有限公司 | Terminal management method and system |
| CN109314713A (en) * | 2016-06-30 | 2019-02-05 | 华为技术有限公司 | Support system, equipment and the process of the mobile device management of multiple containers in virtualized environment |
| CN109314713B (en) * | 2016-06-30 | 2021-02-05 | 华为技术有限公司 | System, device and method for mobile device management supporting multiple virtual containers |
| CN107741884A (en) * | 2017-10-09 | 2018-02-27 | 武汉斗鱼网络科技有限公司 | The method and apparatus that a kind of stratification state machine realizes message push |
| US10616035B1 (en) * | 2018-01-30 | 2020-04-07 | EMC IP Holding Company LLC | Methods and apparatus for device chat and management |
| CN108270798A (en) * | 2018-03-25 | 2018-07-10 | 上海金亥通信设备有限公司 | A kind of mobile terminal device safety management system |
| CN108270798B (en) * | 2018-03-25 | 2021-04-02 | 上海金亥通信设备有限公司 | Mobile terminal equipment safety management system |
| CN109347649A (en) * | 2018-08-01 | 2019-02-15 | 北京奇安信科技有限公司 | A kind of strong management-control method of mobile device and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103731802A (en) | Device management method based on Android mobile terminal | |
| US20150207893A1 (en) | Push message service system and method | |
| KR101436202B1 (en) | Method for providing mobile device security management and mobile device security system there of | |
| CN102821085B (en) | Third party authorizes login method, open platform and system | |
| CN105592168A (en) | Remotely locating and commanding a mobile device | |
| CN103167031B (en) | Method, device and system for communication between Web applications | |
| CN105577662B (en) | Terminal environments method of controlling security and server | |
| CN104468119B (en) | A kind of disposal password Verification System and authentication method | |
| CN104168557A (en) | Upgrading method for operating systems and upgrading device for operating systems | |
| US20100217852A1 (en) | Wireless Terminal Device and Server Therefor | |
| CN103227799A (en) | Implementing method of unified user management and single sign-on platform based on multiple application systems | |
| CN105094996A (en) | Security-enhancing method and system of Android system based on dynamic authority verification | |
| CN112565439B (en) | Internet of things communication method and system | |
| CN103402195A (en) | Application processing method of enterprise-level mobile terminal and enterprise-level mobile application platform | |
| EP2579621A1 (en) | Method of reducing message transmission between DM client and DM server and related communication device | |
| CN107274222A (en) | Advertisement placement method and device | |
| CN101622821A (en) | The method and apparatus that is used for the hotwired of heterogeneous communication system | |
| CN107566396A (en) | A kind of method based on dynamic password enhancing server VPN protocol securitys | |
| CN113296744A (en) | Application development system and method | |
| CN104504492A (en) | Railway scheduling command system information sharing method and apparatus based on mobile platform | |
| KR101408276B1 (en) | Security system and method of portable device control with rights management policy in based | |
| US11064271B2 (en) | Selective delivery state change of valve of remote metering device | |
| CN102137044A (en) | Method and system for safely interacting group information based on community platform | |
| KR20170048536A (en) | Device troubleshooting service method, device, and system for internet of things | |
| CN103778490A (en) | Acquisition method of ERP service object dynamic information, device thereof and system thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140416 |