CN101119539B - Method to implement inhibition, revival function in digital cluster system - Google Patents

Method to implement inhibition, revival function in digital cluster system Download PDF

Info

Publication number
CN101119539B
CN101119539B CN200710147458XA CN200710147458A CN101119539B CN 101119539 B CN101119539 B CN 101119539B CN 200710147458X A CN200710147458X A CN 200710147458XA CN 200710147458 A CN200710147458 A CN 200710147458A CN 101119539 B CN101119539 B CN 101119539B
Authority
CN
China
Prior art keywords
life
distant
pds
state
terminal
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.)
Expired - Fee Related
Application number
CN200710147458XA
Other languages
Chinese (zh)
Other versions
CN101119539A (en
Inventor
李曦滨
朱常宝
卢熙源
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN200710147458XA priority Critical patent/CN101119539B/en
Publication of CN101119539A publication Critical patent/CN101119539A/en
Application granted granted Critical
Publication of CN101119539B publication Critical patent/CN101119539B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The present invention provides a method used for realizing the remote resurrection function in the digital cluster system, used in the field of the digital cluster telecommunications. The technical proposal of the present invention is that when having a mobility management, and the terminal status carried in the demand message which is sent from the PDS, namely the scheduling server is different and discontinuous with the status of the recorded customer in the system, the authentication is passed, but the system does not deliver the terminal status; when the remote resurrection is acknowledged, and the terminal status carried in the demand message which is sent from the PDS is different and discontinuous with the status of the recorded customer in the system, the authentication is rejected, the message delivered from the system carries the real customer status; The DAC namely, the dispatcher station client is capable of obeying a redivious operation to the customer who is recorded into an active status in the system. The present invention provides a more careful implementation scheme of the remote resurrection in the CDMA2000 digital cluster, satisfying the functionality request of the remote resurrection, and the request to security and confidentiality of the cluster system.

Description

Realize the method for the distant resurrection function of getting killed in a kind of digital cluster system
Technical field
The present invention relates to the digital cluster communication field, relate in particular to the method that realizes the distant resurrection function of getting killed in a kind of digital cluster system.
Background technology
Mobile communication technology has developed into the third generation, and wherein trunking communication also becomes a kind of indispensable communication traffic day by day.Trunking communication is meant a kind of dispatching communication mode of special use, comprises special-purpose commander and dispatching communication, and in use cluster user can add calling simultaneously, and conversation is with simplex mode work.In broad terms, comprise that the various wireless communication systems with dispatching communication function of wireless intercom system all can include the category of trunked communication system in.
Historically, the development of trunking communication will be far away early than public mobile communication.Because technical sophistication, with high costs; Originally trunking communication must need such as army, railway, navigation etc. just to be used for the special sector and the unit of command scheduling; Afterwards along with the reduction and the expanding economy of development of technology, cost; The public mobile communication of social individual consumer's radio communication needs just occurred being fit to, even so, current cluster communication still belongs to personal communication system basically.
Trunking communication experienced simple intercom system (intercommunication form one to one) to single base station mini system (joining common-frequency simplex network construction form, alien frequencies list (two) worker network construction form, single channel get ready to go into action in hundreds form, band selective call form, multichannel dial automatically form); Arrive the development course of big capacity multizone system (the multichannel user shares form) again; After experienced again from the simulation cluster to the leap of Digital Clustering, this leap makes trunking communication all can adopt digital processing mode more reliably at the aspects such as multi-access mode, speech coding, modulation-demodulation technique, simultaneous techniques, error-detection error-correction and diversity technique of signalling coding, employing.
Two kinds of digital cluster systems of extensive use at present are based on iDEN that TDMA is a tdma (integrated Digital Enhanced Network) and TETRA (Terrestrial TrunkedRadio); In order to promote the sizable application of digital cluster system; Further boost the efficiency of frequency resources utilization simultaneously, trunked communication system a new application trend occurred on using, and a plurality of digital cluster systems is combined unify to use and manage exactly; Thereby be able to share channel and channel; Share overlay area, communication service, carry on a shoulder pole the purpose of expense altogether, cluster application realizes the common network operation from developing into towards indivedual professional users towards a plurality of group users the most at last.
Trunking communication has been promoted to go up the research that realizes Clustering at existing public network (GSM, CDMA) by the development of private network to common network.
Distant being explained as follows of getting killed and bring back to life in the CDMA2000 mobile communcations system: distant getting killed is meant system from security consideration, and travelling carriage is forbidden its part or all of function by force; Resurrection is meant that system activates recovery again to the travelling carriage that is in the distant state of getting killed; This function through aerial signaling travelling carriage is carried out positive lock or release realizes.
Patents more both domestic and external have been mentioned through high-level managing mobile phone to the note of being sent specific format by managing mobile phone, to reach the implementation method of remote activation/deexcitation travelling carriage partial function.Distant getting killed brought back to life the basic implementation method of function in group system, the existing argumentation in existing patent CN200510090588 " control method of remote deactivation/resurrection in the code division multiple access digital cluster system "; The distant implementation method of bringing back to life function of getting killed, the network element that relates to and basic signaling process have been introduced to this patent outlined.
The distant resurrection implementation method of getting killed that patent CN200510090588 introduces, the distant state of getting killed of system side distant get killed state and travelling carriage are independent the preservations, and the remote deactivation state is kept on the terminal, and system side is to be recorded on the user sim card.
Use terminal A and sim card A like user A (system side notion), user B uses terminal B and sim card B; System side is carried out user A can bring back to life distant getting killed, and will write down on the A of terminal oneself is " can bring back to life distant getting killed " state, at this moment; If when the sim card of active user B is inserted into the enterprising line position registration of terminal A; The state that reports is the distant state of getting killed of terminal A, and the state that system side detects user B (corresponding to sim card B) is " activity ", and system will issue and bring back to life instruction this moment; Terminal A is brought back to life, caused the user distant terminal of getting killed to be brought back to life like this through the mode of changing the sim card.Distant getting killed is that user terminal is stolen, loses or other security considerations and the measure taked does not just reach effect thus, and this problem is the leak that the present distant function of getting killed realizes, has influenced the fail safe of system greatly.
Summary of the invention
The present invention proposes the method that realizes the distant resurrection function of getting killed in a kind of digital cluster system, solved existing distant getting killed targetedly and brought back to life the security breaches that the sim card that is replaced with active state that exists in the implementation just can bring back to life the distant terminal of getting killed.
The present invention provides a kind of more perfect distant implementation method of getting killed and bringing back to life, even make user's replacing activity sim card can not bring back to life distant terminal of getting killed; Its general thought is: system gets killed to mobile management and distant and brings back to life when confirming request, and terminal to report state and system side recording status are inconsistent, and are the situation of discontinuous state, have carried out optimization process.Particularly, when the terminal to report state is distant getting killed, and the User Status of system side record is when be movable, and the system side authentication is passed through, and brings back to life and instructs but no longer issue the terminal; Distant getting killed when bring back to life confirming request, when the terminal to report state is distant getting killed, and the User Status of system side record is when be movable, the system side authentication is refused, and carries the active user state that system side writes down; Must bring back to life by hand on dispatching desk this moment, evades the terminal by illegal situation of bringing back to life with this.
Technical scheme of the present invention may further comprise the steps:
Step 1, during mobile management, when the state of the SOT state of termination of carrying in the request message and system side recording user was inconsistent and discontinuous, authentication was passed through, but system side does not issue the SOT state of termination;
Step 2, distant getting killed brought back to life when confirming, and when the state of the SOT state of termination of carrying in the request message and system side recording user was inconsistent and discontinuous, the authentication refusal carried real User Status in the message that system side issues;
Step 3, DAC is that the dispatching desk client can be carried out the user that system side is recorded as active state and brings back to life operation.
Further, in the present invention, further comprising the steps of in the step 1:
Steps A: the terminal is that dispatch server sends position register request to PDS, carries out location registers
Step B:PDS is that dispatching home location register is sent the mobile management request to PHR;
Step C:PHR analyzes the mobile management request message receive, parses the SOT state of termination that message carries and is distant getting killed, and further Query Database obtains the user and is in active state;
Step D:PHR sends mobile management to PDS and accepts message, and this replys and accept not carry in the message any state, PDS initiatively triggering terminal bring back to life flow process.
Further; In the present invention; In the step 1; The state of the SOT state of termination and system side recording user is inconsistent to be meant: the SOT state of termination for movable, wait for bring back to life, wait for distant get killed, wait for forever distantly get killed, distantly get killed, the permanent distant state of getting killed, and the state of corresponding system side recording user difference with it.
Further, in the present invention, in the step 1, discontinuous being meant of state of the SOT state of termination and system side recording user: between the User Status of the SOT state of termination and system side record is not the continuum of states transition process.
Further, in the present invention, further comprising the steps of in the step 2:
Step e: PDS sends distant getting killed to the terminal/bring back to life instruction, and after distant getting killed/bring back to life operation carried out at the terminal, this moment, the terminal was sent distant getting killed/brings back to life and confirm to ask through base station, PDS to PHR;
Step F: PHR analyzes receive distant and gets killed to bring back to life and confirm request message, parse the SOT state of termination that message carries and be distant getting killed, and Query Database to draw the system side recording user be active state;
Step G:PHR returns distant getting killed to PDS and brings back to life the message that rejects response, and the User Status of carrying in the response message is for movable, and PDS can the active triggering terminal not bring back to life flow process.
Further, in the present invention, further comprising the steps of in the step 3:
The resurrection operation requests that step K: DAC sends active user is a dispatch server to DAS, and DAS is converted into distant getting killed with the resurrection operation requests of DAC and brings back to life demand signalling and send to PDS;
Step L:DAS notice DAC brings back to life successfully;
Step M:PDS obtains the SOT state of termination and customer location area information from PHR;
Step N:PDS issues to the terminal and brings back to life instruction, and the terminal is carried out and brought back to life the operation back to PDS echo reply message;
Step P:PDS sends distant getting killed and brings back to life the affirmation request to PHR, and PHR revises User Status.
The invention provides the distant implementation of getting killed and bringing back to life in the more careful CDMA2000 Digital Clustering, both satisfied distant getting killed and brought back to life functional requirement, also meet the requirement of the right fail safe of group system, confidentiality.
Description of drawings
Fig. 1 supports distant getting killed to bring back to life the network operating structure chart in the prior art;
Fig. 2 is that the SOT state of termination is distant getting killed among the present invention, and system log (SYSLOG) is the mobile management flow chart of active user;
Fig. 3 is that the SOT state of termination is distant getting killed among the present invention, and system log (SYSLOG) to be active user distant get killed to bring back to life confirms flow chart;
Fig. 4 is the flow chart that the dispatching desk client is brought back to life active terminal among the present invention.
Embodiment
Below in conjunction with accompanying drawing the present invention is elaborated.
Fig. 1 supports distant getting killed to bring back to life the network operating structure chart in the prior art, each part is explained as follows:
(1) MS: colony terminal equipment;
(2) BSS: base station sub-system, comprise the transceiver (BTS) of supporting trunked call, base station controller (BSC) and with the mutual dispatching client (PDC) of network side;
(3) PDS: dispatch server, realize the calling control of trunked call.This network element receives from distant the getting killed of dispatching desk server (DAS) and brings back to life instruction; Initiate to obtain user information request to dispatching home location register (PHR); As satisfy condition and then issue the distant resurrection signaling of getting killed the terminal, distant get killed bring back to life operate successfully after, send distant getting killed to PHR and bring back to life affirmation and ask;
(4) PHR: dispatching home location register, preserve the log-on message and the positional information of cluster user, group, realize authentication, mandate and the billing function of group system, and mobile management, the distant functions such as bringing back to life affirmation of getting killed.Among the present invention, user profile is managed, obtained to the PHR receiving mobility, distant getting killed brought back to life the affirmation request, and judge whether whether the terminal to report state consistent with system side recording user state in the request message, provides correct replying according to analysis result;
(5) DAS: the dispatching desk server, dispatching desk client (DAC) is brought back to life operation to distant the getting killed at terminal, be converted into the distant resurrection demand signalling of getting killed and send to PDS;
(6) DAC: the dispatching desk client, comprise dispatching desk and turnkey console, dispatching desk is the platform that the dispatcher dispatched, initiated the distant operations such as bringing back to life of getting killed.
Fig. 2 is the user that system side is recorded as active state, and uploaded state is distant mobile management process chart of getting killed, and comprises that step is following:
Step 201: location registers is carried out at the distant terminal of getting killed;
Step 202:PDS sends this user's mobile management request to PHR;
Step 203:PHR receives the mobile management request from PDS, and analyze in the request message carried terminal state and be distant getting killed, and the inquiry system database, drawing the system side User Status is active state; Then PHR returns the mobile management authentication and accepts message, and this replys the not carried terminal state of message of accepting, and PDS just can not initiate the terminal and brings back to life request like this;
Step 204:PDS returns customer location registration successful respond.
The mobile management request of active user reports distant getting killed during state, and its mobile management response message is carried terminal state not just, comes the realization system can not trigger the resurrection flow process at the distant terminal of getting killed automatically with this.
Fig. 3 is that the SOT state of termination is distant getting killed among the present invention, and system log (SYSLOG) to be active user distant get killed to bring back to life confirms flow chart; This flow process may further comprise the steps:
Step 301: the terminal by distant get killed bring back to life after, distant the getting killed of replying PDS brought back to life instruction;
Step 302:PDS sends distant getting killed to PHR and brings back to life the affirmation request, with the notice PHR distant resurrection result that gets killed in terminal;
Step 303:PHR analyzes the distant resurrection confirmation message of getting killed receive, parse the SOT state of termination of carrying in the message and be distant getting killed, and the inquiry system database to obtain the user be active state; Then PHR return PDS distant get killed to bring back to life reject response, carry User Status in the response message for movable; PDS can not initiate distant getting killed once more and bring back to life operation.
The PDS only SOT state of termination in successful respond message brings back to life, waits for distant when getting killed, waiting for forever distant getting killed for waiting for; Just can do further operation to the terminal; Other states can't cause that PDS operates the terminal, realize that with this PDS can not bring back to life illegal terminal.
Fig. 4 is the flow chart that the dispatching desk client is brought back to life active terminal among the present invention, may further comprise the steps:
Step 401:DAC initiates the resurrection operation to active user;
Step 402:DAS is converted into the resurrection operation of DAC the distant resurrection demand signalling of getting killed and sends to PDS;
Step 403:PDS accepts the distant request of bringing back to life of getting killed;
Step 404:DAS notice DAC brings back to life successfully;
Step 405:PDS sends and obtains user information request to PHR;
Step 406:PHR inquiring user log-on message, legal like the user, then the user profile successful respond is obtained in response, and message carries the correct SOT state of termination and customer location area information;
The current information that step 407:PDS searches this travelling carriage according to the mobile identification code and the position area information of travelling carriage is validated user and normal start like this terminal, then issues the resurrection instruction through the base station to this travelling carriage;
Step 408: terminal such as normal the execution are brought back to life operation, then return distant getting killed and bring back to life completion message;
Step 409: after the terminal was brought back to life and operated successfully, PDS sent distant getting killed to PHR and brings back to life the affirmation request, brings back to life operation with notice PHR and completes successfully;
Step 410:PHR is changed to active state with User Status, and sends the distant resurrection successful respond of getting killed to PDS.
So far, dispatching desk success restoring system side is recorded as the user terminal of active state.
In sum, the present invention proposes a kind of implementation method of the distant resurrection function of getting killed in the Digital Clustering of realizing based on the CDMA2000 technology.This method has solved present user through changing the potential safety hazard that movable sim card just can bring back to life the distant terminal of getting killed, and has satisfied the trunking communication security requirement.

Claims (6)

1. realize in the digital cluster system that distant getting killed bring back to life the method for function, it is characterized in that, may further comprise the steps:
Step 1, during mobile management, when the state of the SOT state of termination of carrying in the request message and system side recording user was inconsistent and discontinuous, authentication was passed through, but system side does not issue the SOT state of termination;
Step 2, distant getting killed brought back to life when confirming, and when the state of the SOT state of termination of carrying in the request message and system side recording user was inconsistent and discontinuous, the authentication refusal carried real User Status in the message that system side issues;
Step 3, DAC carries out the resurrection operation to the user that system side is recorded as active state.
2. method according to claim 1 is characterized in that, and is further comprising the steps of in the step 1:
Steps A: position register request is sent to PDS in the terminal, carries out location registers;
Step B:PDS sends the mobile management request message to PHR;
Step C:PHR analyzes the mobile management request message receive, parses the SOT state of termination that message carries and is distant getting killed, and further Query Database obtains the user and is in active state;
Step D:PHR sends mobile management to PDS and accepts message, and this mobile management accepts not carry in the message any state, PDS initiatively triggering terminal bring back to life flow process.
3. method according to claim 1; It is characterized in that; In the step 1; The state of the SOT state of termination and system side recording user is inconsistent to be meant: the SOT state of termination for movable, wait for bring back to life, wait for distant get killed, wait for forever distantly get killed, distant getting killed or the forever distant state of getting killed, and the state of corresponding system side recording user difference with it.
4. method according to claim 1 is characterized in that, in the step 1, discontinuous being meant of state of the SOT state of termination and system side recording user: between the User Status of the SOT state of termination and system side record is not the continuum of states transition process.
5. method according to claim 1 is characterized in that, and is further comprising the steps of in the step 2:
Step e: PDS sends distant the getting killed at terminal is brought back to life instruction, and after the distant resurrection operation of getting killed had been carried out at the terminal, the terminal was sent distant getting killed through base station, PDS to PHR and brought back to life the affirmation request message at this moment;
Step F: PHR analyzes receive distant and gets killed to bring back to life and confirm request message, parse the SOT state of termination that message carries and be distant getting killed, and Query Database to draw the system side recording user be active state;
Step G:PHR returns distant getting killed to PDS and brings back to life the message that rejects response, and the User Status of carrying in the response message is for movable, and PDS can the active triggering terminal not bring back to life flow process.
6. method according to claim 1 is characterized in that, and is further comprising the steps of in the step 3:
Step K: DAC sends and to give DAS to the resurrection operation requests of active user, and DAS is converted into distant getting killed with the resurrection operation requests of DAC and brings back to life demand signalling and send to PDS;
Step L:DAS notice DAC brings back to life successfully;
Step M:PDS obtains the SOT state of termination and customer location area information from PHR;
Step N:PDS issues to the terminal and brings back to life instruction, and the terminal is carried out and brought back to life the operation back to PDS echo reply message;
Step P:PDS sends distant getting killed and brings back to life the affirmation request to PHR, and PHR revises User Status.
CN200710147458XA 2007-09-12 2007-09-12 Method to implement inhibition, revival function in digital cluster system Expired - Fee Related CN101119539B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN200710147458XA CN101119539B (en) 2007-09-12 2007-09-12 Method to implement inhibition, revival function in digital cluster system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN200710147458XA CN101119539B (en) 2007-09-12 2007-09-12 Method to implement inhibition, revival function in digital cluster system

Publications (2)

Publication Number Publication Date
CN101119539A CN101119539A (en) 2008-02-06
CN101119539B true CN101119539B (en) 2012-07-11

Family

ID=39055427

Family Applications (1)

Application Number Title Priority Date Filing Date
CN200710147458XA Expired - Fee Related CN101119539B (en) 2007-09-12 2007-09-12 Method to implement inhibition, revival function in digital cluster system

Country Status (1)

Country Link
CN (1) CN101119539B (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101521876B (en) * 2009-03-27 2011-02-23 中兴通讯股份有限公司 System and method for remote-closing/ resurrection of value aggregate terminal
CN102404693A (en) * 2011-12-21 2012-04-04 北京国基科技股份有限公司 Digital clustering system and using method thereof
CN103297951B (en) * 2012-02-29 2016-03-02 鼎桥通信技术有限公司 State adjustment method and system, equipment in digital cluster system
CN103581903B (en) * 2012-07-24 2016-12-21 普天信息技术研究院有限公司 A kind of digital cluster system realizes the distant method got killed or bring back to life
CN104683432B (en) * 2014-11-26 2018-12-11 海能达通信股份有限公司 Activate or disable the method and system, terminal and central apparatus of colony terminal
CN109246589B (en) * 2017-06-14 2020-10-30 普天信息技术有限公司 Method and equipment for realizing positioning service of remote halo terminal

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1512799A (en) * 2002-12-26 2004-07-14 �ɶ���ʿͨ��Ϣ��ҵ�ɷ����޹�˾ Method for realizing remote cipher key destruction for secret mobile phone
CN1599326A (en) * 2003-09-16 2005-03-23 华为技术有限公司 Method for dynamic changing group information in group service
CN1917669A (en) * 2005-08-19 2007-02-21 中兴通讯股份有限公司 Control method for mobile station to remote killing/reviving operation in CDMA digital group system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1512799A (en) * 2002-12-26 2004-07-14 �ɶ���ʿͨ��Ϣ��ҵ�ɷ����޹�˾ Method for realizing remote cipher key destruction for secret mobile phone
CN1599326A (en) * 2003-09-16 2005-03-23 华为技术有限公司 Method for dynamic changing group information in group service
CN1917669A (en) * 2005-08-19 2007-02-21 中兴通讯股份有限公司 Control method for mobile station to remote killing/reviving operation in CDMA digital group system

Also Published As

Publication number Publication date
CN101119539A (en) 2008-02-06

Similar Documents

Publication Publication Date Title
CN101141705B (en) Method for cluster terminal to exit group calling actively
CN101060663B (en) A method for realizing the dynamic reconstruction service of cluster system
CN101119539B (en) Method to implement inhibition, revival function in digital cluster system
CN100455070C (en) Establishment and control for CDMA digital packet calling
EP2566279B1 (en) Method and system for querying group's dispatching area information
CN101626573B (en) Paging method and dispatch server
CN101707745B (en) Method, system and device for selecting call groups
CN102857882A (en) Group calling establishing method, group information sending method, corresponding user equipment (UE) and network element
CN101521876B (en) System and method for remote-closing/ resurrection of value aggregate terminal
CN100499845C (en) Method for control traditional packet scheduling platform of CDMA digital cluster system
CN101262654B (en) Call establishment method for digital cluster system
CN100370852C (en) Method and system for realizing dynamic grouping and cancelling grouping of mobile terminal
CN101141707B (en) Digital cluster system and cluster call establishment and release method
CN101090530A (en) Method for terminal in digital trunking communication system active late into group calling
CN101137121B (en) Method of controlling non-limitation traditional group calling of scheduling section
CN100461901C (en) Method for realizing CDMA traditional packet digital calling talk process
CN101141706A (en) Cluster communication system of cluster terminal active exit group calling
CN100479542C (en) A method for voice monitoring in the cluster communication system
CN101005707B (en) Method for roaming terminal inquiry, exciting/de-exciting complementary service in cluster system
CN100463575C (en) Method for combining traditional call with enhanced call in CDMA digital packet
CN101316394B (en) Method for call conversation right scheduling and speech forwarding control
CN100512555C (en) Position-based group allocation method
CN101800944B (en) The method of triggering trunk information updating by sending message through acceptance side and device
CN101835104B (en) The group information updating method of number cancelling mobile terminal and trunking dispatching subsystem
CN101883332A (en) Method, system and device for realizing call back requesting business in trunking communication 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
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20120711

Termination date: 20160912