CN1852138A - Terminal management method and system - Google Patents
Terminal management method and system Download PDFInfo
- Publication number
- CN1852138A CN1852138A CN 200510088340 CN200510088340A CN1852138A CN 1852138 A CN1852138 A CN 1852138A CN 200510088340 CN200510088340 CN 200510088340 CN 200510088340 A CN200510088340 A CN 200510088340A CN 1852138 A CN1852138 A CN 1852138A
- Authority
- CN
- China
- Prior art keywords
- terminal
- management server
- device management
- operational order
- loss
- 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
Abstract
The disclosed method and system for managing terminals includes following steps: (1) server for managing equipment learns of an event of losing terminal; (2) the said server sends down commands of operation to the lost terminal; the said commands of operation are carried by DM protocol; (3) the said terminal converts commands of operation carried by DM protocol to commands of operation executable by the terminal; (4) the said terminal executes the commands of operation. Using DM protocol to carry out operation of management in multiple modes for lost terminals is in order to guarantee safety of users' data information farthest.
Description
Technical field
The present invention relates to the communications field, relate in particular to a kind of terminal management method and system.
Background branch art
Portable terminal is an important component part in the whole mobile operation service system.Increasingly sophisticated along with termination function promoted the difficulty of new business and the possibility that goes wrong also significantly increases.Between the following operator, competition between the equipment supplier is growing more intense, how effectively to guarantee user experience, height user's loyalty, keep the significant concern point that service quality efficiently and low-cost device are safeguarded has become operator, equipment supplier.
Wireless network open mobile alliance device management standard (OMA DM) V1.2 (hereinafter to be referred as the DM standard) is the equipment control unified standard standard of the up-to-date formulation of OMA DM WG.The DM system provides a kind of lower cost solution, be mainly used in third party management and the environment and the configuration information of terminal in the wireless network (such as the functional object in mobile phone terminal and the terminal) are set, solve the problem that these network equipments in use run into, carry out the operation such as installation, upgrading of software and firmware by OTA (wireless network) mode, and hommization more and personalized service are provided, improve user experience.The third party can be mobile operator, the information management department of service provider or partner.
At the loss problem of portable terminal, DM should provide a kind of mode to allow the user to open the managing terminal loss function under the situation of lost terminal, guarantees the safety of user's information.
Existing portable terminal has terminal password protection and SIM card password protection function mostly, and the user can open password protection on terminal.Though the password protection function can ensure the safety of user data to a certain extent; but this mode needs the user to open password protection in advance; password protection has brought inconvenience to the user in the use; most of terminal use uses for convenience can not open this function; in case it is stolen terminal to occur, user's private data can't be protected.And the password protection problem that also exists password to be decrypted, fail safe is not enough.
Summary of the invention
The invention provides a kind of terminal management method and system, in order to solve the problem that can't manage operation that exists in the prior art to the terminal of losing.
The inventive method comprises:
Beneficial effect of the present invention is as follows:
A kind of terminal management method, described terminal is supported equipment control (OMA DM) agreement of Open Mobile Alliance, terminal is managed by device management protocol by device management server, it is characterized in that may further comprise the steps:
A, device management server are known terminal loss;
B, device management server issue operational order to terminal, and described operational order is carried with the DM agreement;
But C, terminal are converted to the terminal operation command with the operational order of DM agreement carrying;
D, terminal are carried out described operational order.
Described steps A is notified terminal loss by the user to the system manager, then system manager's announcement apparatus management server terminal loss.
In the described steps A, set in advance the condition of announcement apparatus management server terminal loss, device management server is known terminal loss according to the appearance of described condition.
The trigger condition of described announcement apparatus management server terminal loss is that separation between machine and card information occurs, and when described terminal separation between machine and card, separation between machine and card information is sent to device management server.
Described method is provided with endpoint registration information in advance in device management server, terminal sends terminal feature information to device management server, and the condition of described announcement apparatus management server terminal loss is that terminal feature information and log-on message are inconsistent.
Described steps A realizes to the device management server logon mode by terminal.
Described steps A, further:
A1, terminal power-on, and generate terminal feature information;
A2, terminal are sent to device management server with described terminal feature information;
A3, device management server judge according to described terminal feature information whether terminal is lost.
Described steps A 2 is finished by the short message form.
In the described steps A 1, described terminal feature information can comprise one of following content or combination:
User ID (MSISDN), device identification (IMEI), terminal models (Model).
Among described step C or the D, described operational order can comprise one of following content or combination:
Terminal locking, end message backup, end message are destroyed, terminal is scrapped.
Described method also comprises step:
E: device management server is to system manager's return command execution results.
Described steps A also comprises the step of identification terminal legitimacy:
The system manager judges according to user ID (MSISDN) and device identification (IMEI) whether described terminal is legal.
A kind of terminal management system comprises terminal and device management server, it is characterized in that, between described device management server and the terminal, by the DM protocol communication, described terminal is provided with DM proxy module, DM interface module and terminal control module;
The operational order that described DM proxy module, receiving equipment management server send, and described operational order sent to the DM interface module;
Described DM interface module receives described operational order, and described operational order is changed, and sends to the control module of terminal;
Described terminal control module is operated terminal according to described operational order.
Described system is characterized in that, described terminal also is provided with DM management tree module, and this DM management tree is a node with the resource of managed devices.
By the DM agreement terminal of losing is carried out the bookkeeping of multiple mode, farthest ensure terminal use's data information security.
Description of drawings
Fig. 1 is a terminal management system structure chart of the present invention;
Fig. 2 is the structural representation of DM management tree of the present invention;
Fig. 3 defines the structural representation of a general management object on the DM management tree for the present invention;
Fig. 4 is a schematic flow sheet of the present invention;
Fig. 5 is the schematic flow sheet of foundation of the present invention, management phase;
Fig. 6 is the schematic flow sheet of the embodiment of the invention 1;
Fig. 7 is the schematic flow sheet of the embodiment of the invention 2;
Fig. 8 is the schematic flow sheet of pattern 1 in the embodiment of the invention 2;
Fig. 9 is the schematic flow sheet of pattern 2 in the embodiment of the invention 2;
Figure 10 is the schematic flow sheet of the embodiment of the invention 3;
Figure 11 is the schematic flow sheet of pattern 1 in the embodiment of the invention 3;
Figure 12 is the terminal D M management tree structural representation of the present invention in illustrating.
Embodiment
Below in conjunction with Figure of description the specific embodiment of the present invention is described.
Overall architecture, agreement and the communication mechanism of the DM system of DM normalized definition, and the safety issue in the equipment control.Device management tree can be considered to the interface that a device management server manages terminal by the DM agreement, and comprising some basic management objects, device management server reaches the purpose of control terminal resource by the operation to the management tree object.The present invention utilizes above-mentioned DM agreement exactly, and terminal is managed.
As shown in Figure 1, be terminal management system structural representation of the present invention, as can be seen from Fig. 1, terminal management system of the present invention mainly comprises: terminal and device management server.
Between described device management server and the terminal, by the DM protocol communication.
Described terminal is provided with DM proxy module, DM interface module and control module.
The operational order that described DM proxy module, receiving equipment management server send, and described operational order sent to the DM interface module.
Described DM interface module receives described operational order, and described operational order is changed, and sends to the control module of terminal.
Described control module is operated terminal according to described operational order.
Also be provided with DM management tree module on the terminal, this DM management tree is a node with the resource of managed devices.
Support the equipment of OMA DM standard must comprise a management tree, management tree is organized into tree with all available management objects in the equipment, and all here nodes all have unique unified resource sign (URI) expression.As shown in Figure 2, be the structural representation of a DM management tree, can send the associative operation instruction to the node of management tree by the DM agreement.The packet structure of this agreement is based on XML (eXtend Makeup Language expands identifiable language) presentation protocol.The node of management tree may comprise one group of environment configurations parameter in this equipment, dissimilar objects, associative operation and some trigger mechanisms etc.
The DM management tree is a kind of tree data structure; the management tree node is divided into internal node and leaf node; can articulate leaf node on the internal node; leaf node has been described terminal resource; as shown in Figure 2; comprised Ring signals (cell phone incoming call the tinkle of bells), Screen Saver (mobile phone screen defence program) and Operator (XM that the related management operation triggers).
The DM management tree plays a function served as bridge at DMS and terminal equipment, and at the loss management of terminal, the present invention can define a general management object on the DM management tree.Its structure is as shown in Figure 3:
Be that described management object tree is described in detail below:
<DevLM>
| Occurrence number | Form | Access right |
| One | Node | Get |
Lose the root node of the management object of management, comprised the loss terminal iidentification, lose bookkeeping, SOT state of termination and expand four child nodes.
<DevLM>/<DevID>
| Occurrence number | Form | Access right |
| One | Node | Get |
This node is to lose the terminal iidentification node, has comprised IMSI, IMEI information below the node.
<DevLM>/<DevID>/<IMEI>
| Occurrence number | Form | Access right |
| One | Chr | Get |
This node has been described the international mobile equipment identific of terminal.
<DevLM>/<DevID>/<IMSI>
| Occurrence number | Form | Access right |
| One | Chr | Get |
This node has been described the international mobile subscriber identity of terminal.
<DevLM>/<Operation>
| Occurrence number | Form | Access right |
| One | Node | Get |
This node has been described loss bookkeeping type father node, has comprised terminal locking, the end message backup, and end message is destroyed, and terminal is destroyed, and bookkeeping is lost in terminal releases etc.
<DevLM>/<Operation>/<DevLock>
| Occurrence number | Form | Access right |
| OneOrZero | Boolean | Exec |
This node has been described the XM of losing terminal locking operation in the management.
<DevLM>/<Operation>/<InfoBackup>
| Occurrence number | Form | Access right |
| OneOrZero | Boolean | Exec |
This node has been described the XM of losing end message backup in the management.
<DevLM>/<Operation>/<InfoDelete>
| Occurrence number | Form | Access right |
| OneOrZero | Boolean | Exec |
This node has been described and has been lost the XM that end message is destroyed in the management.
<DevLM>/<Operation>/<DevDestory>
| Occurrence number | Form | Access right |
| OneOrZero | Boolean | Exec |
This node has been described and has been lost the XM that terminal is destroyed in the management.
<DevLM>/<Operation>/<DevUnlock>
| Occurrence number | Form | Access right |
| OneOrZero | Boolean | Exec |
This node has been described and has been lost the XM that terminal locking is removed in the management.
<DevLM>/<Status>
| Occurrence number | Form | Access right |
| One | Boolean | Get |
This node has been described the SOT state of termination of losing in the management, such as: whether terminal is locked.
<DevLM>/<Ext>
| Occurrence number | Form | Access right |
| OneOrZero | Boolean | Get |
This node has been described the expanding node of losing management object.
As shown in Figure 4, be the schematic flow sheet of terminal management method of the present invention, as can be seen from Fig. 4, the present invention mainly may further comprise the steps:
S1, device management server are known terminal loss;
Behind the terminal loss, device management server is in time known this loss message, with the operational administrative behind the startup terminal loss.Here to know that the method for terminal loss has multiple for device management server, will further specify in the embodiment of back.
S2, device management server issue operational order to terminal, and described operational order is carried with the DM agreement;
Device management server is according to described terminal loss incident, and to the terminal transmit operation order of losing, this operational order is used the DM agreement.
But S3, terminal are converted to the terminal operation command with the operational order of DM agreement carrying;
After the terminal of losing received the operational order of described DM agreement carrying, according to terminal capability, the operational order that described DM agreement is carried was converted to the operational order that terminal can be carried out.
S4, terminal are carried out described operational order.
Terminal is operated accordingly according to the operational order that device management server issues, and finishes losing the management of terminal.
In the bookkeeping process after device management server of the present invention is lost terminal equipment, also relate to a problem, in the technical scheme that realizes, need carry out legitimate verification the loss terminal of being managed to terminal use's legitimate verification.Therefore in the such scheme, can also before step S1, increase the step that terminal legality is verified.
Carry out the loss bookkeeping, just must under legal terminal use authorizes, carry out, so just must have a cover mechanism to come terminal use's legitimacy is verified.In general the system manager is MSISDN (phone number) by the user identity of coming identifying user, but simple pass through MSISDN and realize verifying to be not enough, if being certain lawless person, terminal illegally obtains, as long as change so one number, it is validated user that the system manager just gives tacit consent to this user, and obviously this is irrational.IMEI is the international unique identifier of terminal equipment, the system manager can identify by this and confirm terminal equipment, suppose that user A is the registration validated user of terminal, no matter user B still is that user C has obtained this terminal, the system manager only confirms that user A is the validated user of this terminal so.But so also brought a problem, supposed that user A is legal terminal has been transferred user B, user B still has the administration authority of this terminal there in the process of using this terminal the system manager, and this obviously also is irrational.
Confirm whether the terminal use legal, the system manager must the maintenance customer sign (MSISDN) and two kinds of characteristics of device identification (IMEI), the present invention can be in the following way for this reason:
1, the user for legal new purchase terminal can pass through note, phone, and Internet, modes such as business hall are registered oneself MSISDN and terminal to the system manager place, and the system manager is as the foundation of terminal validated user checking from now on.
2, for the situation of legal transfer, such as: user A is with the legal user B that transfers of terminal, user A can pass through note, phone, Internet, mode reporting system keepers such as business hall authorize the process of registration, after the system manager confirms user A legal identity by user A sign and password, the terminal legal title of cancellation user A is registered MSISDN and the terminal of user B simultaneously, and user B just has the ownership of this terminal.
If 3 machine cards are changed, just unpaired phenomenon has appearred in the IMEI of the MSISDN of validated user and terminal, the system manager can take a kind of strategy, such as: the system manager does not receive this user's notice within a certain period of time, then this user's of acquiescence cancellation terminal management is weighed, and administration authority is given the user of new logo.Take the mode of acquiescence mandate like this can avoid registering loaded down with trivial details process to the system manager in the validated user replacing number process.
Take top several mode logon mode, the legitimacy that the system manager just can the verification terminal user, guaranteeing to lose bookkeeping is to carry out under legal terminal use authorizes.
The present invention terminal and device management server manage with by in the process of managing, relate to the handling process of foundation, management phase, as shown in Figure 5, it is the schematic flow sheet that loss terminal and device management server establish a communications link, terminal and device management server are set up relevant connection and are issued the bookkeeping order by data-bag interacting information among the figure.
S11, device management server are initiated operational notification to terminal;
Device management server is initiated operational notification by packet 0 to terminal.
S12, terminal are initiated initial session and are connected, to device management server report identity information and facility information;
Terminal responds to the content of described packet 0, initiates initial session and connects, and by packet 1 the associated terminal characteristic information is sent to device management server, and this terminal feature information comprises the identity information of terminal and facility information etc.
S13, device management server send identity information, and issue bookkeeping or interactive operation to terminal;
Device management server sends identity information and issues bookkeeping or the interactive operation order to terminal by packet 2.
The identity information here, can be the identity information of terminal identity information and device management server, referring to the mutual authentication information of setting up session at the DM protocol layer, is to be handed down to terminal by device management server in advance, and purpose is in order to guarantee the secure session of DM agreement.Not to lose the user of management kind and the identification information of terminal.
S14, the operation of terminal actuating equipment management server and response operating result;
Terminal is according to the content of packet 2, the operation that the actuating equipment management server issues, and operating result sent to device management server by packet 3.
If the not suspended word of this session of S15, repeating step S13 and step S14;
If session is not ended, by packet 2, repeating step S13 and step S14.
Embodiment 1: direct bookkeeping mode:
When user terminal generation loss situation, the user can pass through phone, the Internet immediately, mode reporting system keepers such as business hall carry out the bookkeeping of lost terminal, and wherein bookkeeping includes but not limited to terminal locking, the end message backup, end message is destroyed, and terminal is scrapped etc.
As shown in Figure 6, be the handling process of this mode of operation, it mainly may further comprise the steps:
S111, user lose management (can pass through phone, the Internet, modes such as business hall) to the system manager requesting terminal;
S112, system manager issue the loss bookkeeping to device management server (DMS);
S113, DMS initiate to connect notice to losing terminal;
S114, terminal and DMS set up session connection;
S115, DMS issue the loss bookkeeping by the DM agreement;
S116, terminal are to DMS return executing state;
S117, DMS return final execution result to the system manager;
S118, system manager notify the user mode of operation.
The action type of the step S112 of embodiment 1 and step S115 decides according to user's request and terminal capability, the action need terminal of losing management provides corresponding executive capability, at different terminals, the loss bookkeeping that the system manager can provide also respectively is not quite similar.
The advantage of embodiment 1 is that the user can lose after the terminal at any time that the reporting system keeper loses management, need not be beforehand with any processing.
Embodiment 2: the task management operation mode.
Embodiment 2 requires user's advance notification system keeper to open the loss management, and the system manager issues the loss management role to terminal.
After terminal was accepted management role, management role was monitored the operating position of terminal, triggered some actions under some particular event conditions, such as: switching on and shutting down reporting terminal characteristic information monitors separation between machine and card and carries out associative operation etc.
As shown in Figure 7, be the schematic flow sheet of embodiment 2, specifically describe the task setting handling process of this mode below.
S211, user lose task management (can pass through phone, the Internet, modes such as business hall) to the system manager requesting terminal in advance;
S212, system manager notify DMS to issue the loss management role;
S213, DMS initiate to connect notice to losing terminal;
S214, terminal and DMS set up session connection;
S215, DMS collection terminal characteristic information;
S216, terminal notify the user to confirm;
S217, user select to confirm to authorize;
S218, terminal backout feature information are given DMS;
S219, DMS store the characteristic information of this terminal;
S2110, DMS issue to terminal and lose the management role operation;
S2111, terminal are returned set condition;
S2112, DMS reporting system keeper operating result;
S2113, system manager notify the user set condition.
Wherein the terminal feature information that illustrates among the step S215 includes but not limited to the MSISDN of terminal, IMEI, MODEL characteristic information.The purpose of collection terminal characteristic information is for from now on to losing distinguishing of terminal.
The management role that the DMS that mentions among the step S2110 is handed down to terminal has comprised the operation of trigger condition and execution, and wherein trigger condition includes but not limited to specific incident, such as, switching on and shutting down, separation between machine and card, the variation of some state parameter of terminal.Executable operations includes but not limited to that SOT state of termination reports, and carries out the loss bookkeeping of setting etc.For example: the locking monitor task that issues monitors the situation that terminal is changed SIM card, locking terminal immediately.
Among the embodiment 2, the task customization can have various modes.
S221, terminal generation particular event (such as: switching on and shutting down);
The operation that management role is lost in S222, triggering, the reporting terminal characteristic information;
Whether S223, DMS analyze is that the user reports the loss terminal;
It is to lose terminal that S224, step 3 analyze, and DMS issues the loss bookkeeping;
S225, terminal return executing state;
Among the step S223 whether be terminal that user report the loss to DMS if analyzing, and (such as MSISDN, IMEI) compares, if find that the machine card information of terminal is unpaired, then depend on the IMEI of terminal according to the previous terminal feature information of collecting of DMS.
Pattern 2 is under the situation of the management role machine card replacement that monitors terminal, triggers the bookkeeping of carrying out terminal locking, and the state and the characteristic information of notice DMS terminal, is convenient to from now on tracking and control.Precondition be the terminal use the reporting system keeper issue the loss management role, and user notification system manager terminal is lost.As shown in Figure 9, be the schematic flow sheet of pattern 2, mainly may further comprise the steps:
SIM card is changed (start back) on S231, the terminal;
S232, management role monitor separation between machine and card, carry out the terminal locking operation;
S233, reporting terminal state and characteristic information are given DMS;
Whether S234, DMS analyze is that the user reports the loss terminal
S235, DMS issue the loss bookkeeping;
S236, terminal return executing state.
Lose the task management advantage and be that DMS need not to be concerned about the state of terminal, terminal is carried out according to the task that issues in advance and is lost management behaviour operation, and DMS can trace into the state of terminal according to particular event in addition, is convenient to issue the loss bookkeeping.
Embodiment 3: the endpoint registration way to manage.
For the terminal of DM management, require it in start, to register DMS collection terminal information at DMS.Such as: IMSI, IMEI, terminal identification information such as MODEL.If DMS judges the user of this terminal and asked to lose management, DMS issues the loss bookkeeping according to request.As shown in figure 10, be the endpoint registration schematic flow sheet of this mode, mainly may further comprise the steps:
S311, user's starting hand-set power supply;
S312, mobile phone are collected characteristic information, and (MSISDN, IMEI Model), send note to sms center;
S313, sms center send note to Short Message Service Gateway;
S314, Short Message Service Gateway are uploaded to the DM server with the mobile phone characteristic information;
S315, DM server are received the mobile phone characteristic information, upgrade the corresponding relation of this mobile phone characteristic information;
S316, DM server return result and give Short Message Service Gateway;
S317, Short Message Service Gateway pass to sms center;
S318, sms center upgrade the result by short message mode notice mobile phone;
Because each DM terminal all can arrive DMS and register, so DMS can confirm whether this terminal loses terminal according to the characteristic information of the terminal that reports, if lose terminal, DMS can be according to the operation that manages of user's request.As shown in figure 11, be the concrete process chart under this pattern, mainly comprise:
S321, user lose management to the system manager requesting terminal;
S322, record terminal feature information;
Terminal is lost in S323, unlatching;
S324, terminal are collected characteristic information, and (MSISDN, IMEI Model), send to DMS;
Whether S325, DMS analyze is that the user reports the loss terminal;
S326, issue the loss bookkeeping;
S327, return executing state;
S328, informing user terminal state information.
Whether the DMS analysing terminal is reported the loss in the terminal procedures among the step S325, can use IMEI to come terminal is differentiated, IMEI is the unique identification of terminal, no matter whether terminal user changes SIM card.
The endpoint registration way to manage can track terminal under terminal one open state, and characteristic information that can collection terminal.Be convenient to the bookkeeping of losing of DMS.
Below how DMS is made a specific description by DM consultative management terminal, Figure 12 is the structure of the DM management tree of terminal, and the node of black is a root node of losing the bookkeeping object among the setting figure.Then do following operation:
DMS issues the terminal locking operational order:
<Exec>
<CmdID>2</CmdID>
<Item>
<Target>
<LocURI>Operator/DevLM/Operation/DevLock</LocURI>
</Target>
</Item>
</Exec>
The DM client receives the loss administration order that DMS issues, and just notice is lost management devices and carried out associative operation, the back notice DM client that is finished, again by DM client return state to DMS.
<Status>
<MsgRef>2</MsgRef>
<CmdID>4</CmdID>
<CmdRef>2</CmdRef>
<Cmd>Exec</Cmd>
＜Data〉200＜/Data 〉/
*Expression runs succeeded
*/
</Status>
The operating interactive process of whole loss management meets the DM standard, and concrete definition is no longer described.
The invention provides the data security mechanism that a kind of portable terminal is lost, the terminal of having lost is carried out device management operations by the DM system, such as: terminal locking, the end message backup, end message is destroyed, and terminal scraps and wait operation, reaches guarantee user data information purpose of safety.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (14)
1, a kind of terminal management method, described terminal is supported equipment control (OMADM) agreement of Open Mobile Alliance, terminal is managed by device management protocol by device management server, it is characterized in that may further comprise the steps:
A, device management server are known terminal loss;
B, device management server issue operational order to terminal, and described operational order is carried with the DM agreement;
But C, terminal are converted to the terminal operation command with the operational order of DM agreement carrying;
D, terminal are carried out described operational order.
2, the method for claim 1 is characterized in that, described steps A is notified terminal loss by the user to the system manager, then system manager's announcement apparatus management server terminal loss.
3, the method for claim 1 is characterized in that, in the described steps A, sets in advance the condition of announcement apparatus management server terminal loss, and device management server is known terminal loss according to the appearance of described condition.
4, method as claimed in claim 3 is characterized in that, the trigger condition of described announcement apparatus management server terminal loss is that separation between machine and card information occurs, and when described terminal separation between machine and card, separation between machine and card information is sent to device management server.
5, method as claimed in claim 3, it is characterized in that, endpoint registration information is set in device management server in advance, terminal sends terminal feature information to device management server, the condition of described announcement apparatus management server terminal loss is that terminal feature information and log-on message are inconsistent.
6, method as claimed in claim 3 is characterized in that, described steps A realizes to the device management server logon mode by terminal.
7, method as claimed in claim 6 is characterized in that, described steps A, further:
A1, terminal power-on, and generate terminal feature information;
A2, terminal are sent to device management server with described terminal feature information;
A3, device management server judge according to described terminal feature information whether terminal is lost.
8, method as claimed in claim 7 is characterized in that, described steps A 2 is finished by the short message form.
9, method as claimed in claim 7 is characterized in that, in the described steps A 1, described terminal feature information can comprise one of following content or combination:
User ID (MSISDN), device identification (IMEI), terminal models (Model).
10, the method for claim 1 is characterized in that, among described step C or the D, described operational order can comprise one of following content or combination:
Terminal locking, end message backup, end message are destroyed, terminal is scrapped.
11, the method for claim 1 is characterized in that, also comprises step:
E: device management server is to system manager's return command execution results.
12, the method for claim 1 is characterized in that, described steps A also comprises the step of identification terminal legitimacy:
The system manager judges according to user ID (MSISDN) and device identification (IMEI) whether described terminal is legal.
13, a kind of terminal management system comprises terminal and device management server, it is characterized in that, between described device management server and the terminal, by the DM protocol communication, described terminal is provided with DM proxy module, DM interface module and terminal control module;
The operational order that described DM proxy module, receiving equipment management server send, and described operational order sent to the DM interface module;
Described DM interface module receives described operational order, and described operational order is changed, and sends to the control module of terminal;
Described terminal control module is operated terminal according to described operational order.
14, system as claimed in claim 13 is characterized in that, described terminal also is provided with DM management tree module, and this DM management tree is a node with the resource of managed devices.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200510088340 CN1852138A (en) | 2005-07-30 | 2005-07-30 | Terminal management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200510088340 CN1852138A (en) | 2005-07-30 | 2005-07-30 | Terminal management method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1852138A true CN1852138A (en) | 2006-10-25 |
Family
ID=37133608
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200510088340 Pending CN1852138A (en) | 2005-07-30 | 2005-07-30 | Terminal management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1852138A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009049456A1 (en) * | 2007-10-16 | 2009-04-23 | Zte Corporation | Method and system of managing a lost terminal |
| WO2009067941A1 (en) * | 2007-11-22 | 2009-06-04 | Huawei Technologies Co., Ltd. | Locking management method, terminal and system |
| WO2010124571A1 (en) * | 2009-04-30 | 2010-11-04 | 中兴通讯股份有限公司 | Node information acquirement method, client, and server |
| WO2010148814A1 (en) * | 2009-12-30 | 2010-12-29 | 中兴通讯股份有限公司 | Method, device and system for updating security algorithm of mobile terminals |
| WO2010148819A1 (en) * | 2009-12-25 | 2010-12-29 | 中兴通讯股份有限公司 | Terminal management method, communication system and terminal |
| CN101188839B (en) * | 2007-12-10 | 2011-01-19 | 中兴通讯股份有限公司 | Data processing method and system for mobile terminal |
| CN102752741A (en) * | 2007-10-17 | 2012-10-24 | 华为技术有限公司 | Method, system and device for protecting terminal data |
| CN101499922B (en) * | 2008-02-02 | 2012-12-12 | 华为技术有限公司 | Data conversion method, apparatus, terminal and server |
| CN104811312A (en) * | 2015-05-25 | 2015-07-29 | 王旭东 | Terminal course identity authentication method based on center authorization |
| CN105592101A (en) * | 2016-01-28 | 2016-05-18 | 江苏省邮电规划设计院有限责任公司 | Multi-phone-terminal clustering control method based on short messages |
| CN106304033A (en) * | 2016-08-31 | 2017-01-04 | 北京握奇数据系统有限公司 | A kind of cellphone information defence method based on binding machine and card and system |
-
2005
- 2005-07-30 CN CN 200510088340 patent/CN1852138A/en active Pending
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009049456A1 (en) * | 2007-10-16 | 2009-04-23 | Zte Corporation | Method and system of managing a lost terminal |
| CN101415264B (en) * | 2007-10-16 | 2011-11-30 | 中兴通讯股份有限公司 | Method and system for managing terminal loss |
| CN102752741B (en) * | 2007-10-17 | 2016-01-27 | 华为技术有限公司 | To the method, system and device of protecting terminal data |
| CN102752741A (en) * | 2007-10-17 | 2012-10-24 | 华为技术有限公司 | Method, system and device for protecting terminal data |
| CN101415182B (en) * | 2007-10-17 | 2013-01-30 | 华为技术有限公司 | Method, system and apparatus for protecting terminal data |
| WO2009067941A1 (en) * | 2007-11-22 | 2009-06-04 | Huawei Technologies Co., Ltd. | Locking management method, terminal and system |
| CN101442581B (en) * | 2007-11-22 | 2011-06-01 | 华为技术有限公司 | Method and terminal for managing locking |
| CN101188839B (en) * | 2007-12-10 | 2011-01-19 | 中兴通讯股份有限公司 | Data processing method and system for mobile terminal |
| CN101499922B (en) * | 2008-02-02 | 2012-12-12 | 华为技术有限公司 | Data conversion method, apparatus, terminal and server |
| US8892711B2 (en) | 2009-04-30 | 2014-11-18 | Zte Corporation | Method for acquiring node information, and client and server |
| WO2010124571A1 (en) * | 2009-04-30 | 2010-11-04 | 中兴通讯股份有限公司 | Node information acquirement method, client, and server |
| WO2010148819A1 (en) * | 2009-12-25 | 2010-12-29 | 中兴通讯股份有限公司 | Terminal management method, communication system and terminal |
| WO2010148814A1 (en) * | 2009-12-30 | 2010-12-29 | 中兴通讯股份有限公司 | Method, device and system for updating security algorithm of mobile terminals |
| CN104811312A (en) * | 2015-05-25 | 2015-07-29 | 王旭东 | Terminal course identity authentication method based on center authorization |
| CN105592101A (en) * | 2016-01-28 | 2016-05-18 | 江苏省邮电规划设计院有限责任公司 | Multi-phone-terminal clustering control method based on short messages |
| CN105592101B (en) * | 2016-01-28 | 2018-12-11 | 中通服咨询设计研究院有限公司 | A kind of more telephone terminal cluster control methods based on short message |
| CN106304033A (en) * | 2016-08-31 | 2017-01-04 | 北京握奇数据系统有限公司 | A kind of cellphone information defence method based on binding machine and card and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1852138A (en) | Terminal management method and system | |
| CN1889741A (en) | Method and apparatus for realizing scheduled operation in equipment management | |
| CN1852094A (en) | Method and system for protecting account of network business user | |
| CN1801743A (en) | Terminal equipment managing method | |
| CN1889730A (en) | Wireless user identification module, communication terminal equipment and communication control method | |
| CN1859177A (en) | Method for processing customized task in equipment management | |
| CN1794657A (en) | Method and system for managing terminal equipment | |
| CN101052167A (en) | Automatic renewing system for communication number and its realizing method | |
| CN1773937A (en) | Device management apparatus, device, and device management method | |
| CN1719795A (en) | Device and process for wireless local area network association and related products | |
| CN1968283A (en) | Network management system and method | |
| CN1794647A (en) | Method and its system upload terminal information in equipment management | |
| CN1674577A (en) | Router and SIP server | |
| CN1925688A (en) | Multimode communication device and its method for recognizing wireless resource | |
| CN101068383A (en) | Student terminal configuration method and system based on terminal management business | |
| CN1863172A (en) | Method and system for issuing and presenting information | |
| CN1520123A (en) | Answering method to address inquire and program and appts. thereof, and address notifying method, program and appts. | |
| CN1812383A (en) | System and method for provisioning component applications | |
| CN1878092A (en) | Domain management system, method for building local domain and method for acquisition of local domain licence | |
| CN1738248A (en) | Information-processing method, information-processing apparatus and computer program | |
| CN1691578A (en) | A method of self validity verification for an equipment | |
| CN101047552A (en) | Distribution service management method, system and distribution authorization capacibility discrimination and authorization method, system | |
| CN101068408A (en) | Self log-on method, terminal and server for multi-standby terminal | |
| CN1661962A (en) | Information-processing apparatus, information-processing method, and computer program | |
| CN1716874A (en) | Remote management system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20061025 |