CN105592425A - Realization method and system for restoration from non-transmitting state and non-transmitting and non-receiving state of cluster terminal - Google Patents
Realization method and system for restoration from non-transmitting state and non-transmitting and non-receiving state of cluster terminal Download PDFInfo
- Publication number
- CN105592425A CN105592425A CN201410577464.9A CN201410577464A CN105592425A CN 105592425 A CN105592425 A CN 105592425A CN 201410577464 A CN201410577464 A CN 201410577464A CN 105592425 A CN105592425 A CN 105592425A
- Authority
- CN
- China
- Prior art keywords
- distant
- terminal
- instruction
- state
- dizzy
- 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.)
- Granted
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention provides a realization method for restoration from a non-transmitting state and a non-transmitting and non-receiving state of a cluster terminal. The method comprises: a scheduling platform sends an instruction for indicating a terminal to enter one of states including a non-transmitting state, a non-transmitting and non-receiving state and a normal state; after a home subscriber server, a cluster service control center, and a mobile management entity receives the instruction, the cluster terminal is recorded to enter a corresponding state; and the cluster terminal enters the corresponding state after receiving the instruction. According to the invention, restoration from a non-transmitting state and a non-transmitting and non-receiving state of a cluster terminal becomes accurate and efficient.
Description
Technical field
The present invention relates to wireless communication field, distant dizzy distant implementation method and the system of getting killed and bringing back to life of colony terminal.
Background technology
Distant dizzy referring to, system utilization eats dishes without rice or wine to issue distant dizzy instruction, and terminal enters distant dizzy shape after receiving distant dizzy instructionState, terminal cannot apply for or accept the business of any network under distant dizzy state, but search and registration,The service such as authentication, location also retains effectively; Resurrection refers to, in the terminal of distant dizzy state, system is utilized emptyMouth issues resurrection instruction, and terminal enters normal condition after receiving and bringing back to life instruction, and terminal is recovered before distant dizzy stateAll functions, if " prohibit words " before distant dizzy state, remove while resurrection and prohibit words; Distant getting killed refers to, system utilizationEat dishes without rice or wine to issue the distant instruction of getting killed, terminal enters the distant state of getting killed after receiving the distant instruction of getting killed, terminal under the distant state of getting killed notCan apply for or accept the business of any network.
In the cluster private network of command scheduling, the safety issue of terminal is received extensive concern. When situation is special,System can control terminal, to its carry out distant dizzy/bring back to life, the distant operation of getting killed, to reach security control terminalObject.
, in system, there are 6 SOT states of termination in the existing distant dizzy distant resurrection scheme of getting killed: in distant swooning, in distant getting killed,In resurrection, distantly dizzyly, distant get killed, normally. Design distant dizzy in/distant getting killed in/bring back to life medium 3 states, be forGroup service control centre can control instruction retransmit. When user enters network, group service control centre is sentencedDisconnected user in distant dizzy in/distant getting killed in/bring back to life medium state, send the distant dizzy distant resurrection instruction of getting killed to user.Until user distant dizzy distant get killed brings back to life successfully after, mobile management entity is understood recording user state. This realizes and has 3 placesNot enough: 1) state is too much, must bring the complexity of each network element processing in system; 2) state is inconsistent asksTopic: get killed successfully if terminal is distant, record the distant state of getting killed, but group service control centre does not receive that terminal is distant and gets killed intoMerit response, now gets killed and does not receive any information because terminal is distant, occurs group service control centre, ownershipThe user terminal state of client server record is " in distant getting killed ", and cannot change; 3) if mobile managementEntity is not received distant dizzy distant the getting killed while bringing back to life success response of terminal, because group service control centre record is " distant dizzyIn/distant getting killed in/in bringing back to life " state, and not recording user state of mobile management entity exists terminal passableDo data service and cannot do the situation of speech business.
Summary of the invention
For overcoming the above problems, the present invention proposes the distant dizzy distant implementation method of getting killed and bringing back to life of a kind of colony terminal, bagDraw together: dispatching desk sends instruction, and described instruction is used to indicate described terminal and enters one of following state: distant dizzy,Distantly get killed, normally; Home subscriber server, group service control centre and mobile management entity are received described fingerAfter order, record described colony terminal and enter corresponding state; Described colony terminal enters after receiving described instructionCorresponding state.
Preferably, when the state recording in the state of described colony terminal and home subscriber server is inconsistentTime, described instruction is resend terminal.
Preferably, described instruction comprises and distantly dizzyly, distant gets killed and bring back to life instruction: described distant dizzy instruction is used to indicate instituteState colony terminal and enter distant dizzy state, terminal is only searched under distant dizzy state and registration, authentication, positioning serviceRetain effectively; Described resurrection instruction is used to indicate distant dizzy colony terminal and enters normal condition, and it is distant that terminal is recoveredAll functions before dizzy state; The described distant instruction of getting killed is used to indicate described colony terminal and enters the distant state of getting killed, eventuallyAny business can not be applied for or accept to end under the distant state of getting killed.
Preferably, after the described distant dizzy or distant instruction of getting killed is sent out, if described terminal is in individual calling business,Or be in group-calling service and be the promoter of described group calling, described individual calling or described group calling are released;If described terminal is in the speaker of group-calling service, but not the promoter of described group calling, described terminalRight of speech be released; If described terminal is in the obedient party of group-calling service, and it not the initiation of described group callingPerson, described terminal exits described group calling; If described terminal is in data service, described data industryBusiness is terminated.
Preferably, described release is triggered by described colony terminal or core network side triggers; Described data serviceTermination by base station triggers.
Based on identical design, the present invention also proposes the distant dizzy distant system of getting killed and bringing back to life of a kind of colony terminal, comprising:Described dispatching desk sends instruction, and described instruction is used to indicate described terminal and enters one of following state: distant dizzy,Distantly get killed, normally; Described home subscriber server, group service control centre and mobile management entity are received instituteState after instruction, record described colony terminal and enter corresponding state; Described colony terminal is received after described instructionEnter corresponding state.
Preferably, when the state recording in the state of described colony terminal and home subscriber server is inconsistentTime, described instruction is resend terminal.
Preferably, described instruction comprises and distantly dizzyly, distant gets killed and bring back to life instruction: described distant dizzy instruction is used to indicate instituteState colony terminal and enter distant dizzy state, terminal is only searched under distant dizzy state and registration, authentication, positioning serviceRetain effectively; Described resurrection instruction is used to indicate distant dizzy colony terminal and enters normal condition, and it is distant that terminal is recoveredAll functions before dizzy state; The described distant instruction of getting killed is used to indicate described colony terminal and enters the distant state of getting killed, eventuallyAny business can not be applied for or accept to end under the distant state of getting killed.
Preferably, after the described distant dizzy or distant instruction of getting killed is sent out, if described terminal is in individual calling business,Or be in group-calling service and be the promoter of described group calling, described individual calling or described group calling are released;If described terminal is in the speaker of group-calling service, but not the promoter of described group calling, described terminalRight of speech be released; If described terminal is in the obedient party of group-calling service, and it not the initiation of described group callingPerson, described terminal exits described group calling; If described terminal is in data service, described data industryBusiness is terminated.
Preferably, described release is triggered by described colony terminal or core network side triggers; Described data serviceTermination by base station triggers.
The method and system that the present invention proposes, makes the group system can control terminal state, it is carried out distant dizzy/ bring back to life, the distant operation of getting killed, reach the object of security control terminal; Meanwhile, solve existing realization deficiency itPlace, make terminal distant dizzy distant get killed bring back to life more accurately, more efficient.
Brief description of the drawings
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, below will be to implementingIn example or description of the Prior Art, the accompanying drawing of required use is briefly described, and apparently, the following describesIn accompanying drawing be some embodiments of the present invention, for those of ordinary skill in the art, do not paying woundUnder the prerequisite of the property made work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the network equipment link composition of the embodiment of the present invention;
Fig. 2 is distant dizzy successful flow chart while being the terminal free time;
Fig. 3 is distant dizzy successful flow chart in terminal individual calling;
When Fig. 4 registers for user, HSS recording user state is that distant dizzy, terminal recording status is normal placeReason flow chart.
Detailed description of the invention
For making object, technical scheme and the advantage of the embodiment of the present invention clearer, below in conjunction with the present inventionAccompanying drawing in embodiment, is clearly and completely described the technical scheme in the embodiment of the present invention, obviously,Described embodiment is the present invention's part embodiment, instead of whole embodiment; It should be noted that,In the situation that not conflicting, the feature in embodiment and embodiment in the application can combine mutually. Based onEmbodiment in the present invention, those of ordinary skill in the art obtain not making under creative work prerequisiteEvery other embodiment, all belong to the scope of protection of the invention.
The distant dizzy distant implementation method of getting killed and bringing back to life of a kind of colony terminal provided by the invention, is applicable to mobile radio communicationNetwork, transforms for home subscriber server, group service control centre, mobile management entity. MainlyComprise: dispatching desk sends instruction, and described instruction is used to indicate described terminal and enters one of following state: distant dizzy,Distantly get killed, normally; Home subscriber server, group service control centre and mobile management entity are received described fingerAfter order, record described colony terminal and enter corresponding state; Described colony terminal enters after receiving described instructionCorresponding state. When the state recording in the state of described colony terminal and home subscriber server inconsistentTime, described instruction is resend terminal, and indicating terminal enters with network side and records consistent state.
Wherein, described instruction comprises and distantly dizzyly, distant gets killed and bring back to life instruction: described in described distant dizzy instruction is used to indicateColony terminal enters distant dizzy state, and terminal is only searched under distant dizzy state and registration, authentication, positioning service are protectedLeave effect; Described resurrection instruction is used to indicate distant dizzy colony terminal and enters normal condition, and it is distant dizzy that terminal is recoveredAll functions before state; The described distant instruction of getting killed is used to indicate described colony terminal and enters the distant state of getting killed, terminalUnder the distant state of getting killed, can not apply for or accept any business.
After the described distant dizzy or distant instruction of getting killed is sent out, if described terminal is in individual calling business, or justIn group-calling service and be the promoter of described group calling, described individual calling or described group calling will be released; IfDescribed terminal is in the speaker of group-calling service, but be not the promoter of described group calling, described terminalRight of speech is released; If described terminal is in the obedient party of group-calling service, and not the promoter of described group calling,Described terminal exits described group calling; If described terminal is in data service, described data service quiltStop. Described releasing operation wherein can be triggered by described colony terminal, also can by core-network side (asMobile management entity) trigger; The termination of described data service is by can be by base station triggers.
In the specific implementation of said method, mainly comprise the steps:
1, dispatching desk carries out distant swooning/resurrection, the distant operation of getting killed to user, sends distant dizzy distant getting killed and brings back to life order.
2, dispatching desk side group service control centre receives distant dizzy distant getting killed and brings back to life order, and this order is transmitted toUser attaching client server.
3, user attaching client server receives distant dizzy distant getting killed and brings back to life order, by User Status be revised as distant dizzy/Distant getting killed/normal.
4, user attaching client server judges that user is online, sends to user's side group service control centreSubscription data update request.
5, user's group service control centre recording user state be distant dizzy/distant getting killed/normal.
6, user's group service control centre sends the distant dizzy distant resurrection instruction of getting killed to mobile management entity.
7, mobile management entity receives instruction, recording user state be distant dizzy/distant getting killed/normal, and by this orderBe transmitted to user terminal.
8, user terminal receives that distant swooning/resurrection, the distant instruction of getting killed enter corresponding state, carry out respective handling.
When user registers, group service control centre judges the shape of home subscriber server recording status and terminalWhether state is consistent. If inconsistent, group service control centre sends distant dizzy distant getting killed again to mobile management entityInstruction alive, this order is transmitted to user by mobile management entity.
Elaborate the specific implementation of the present invention under different application scene below by several embodiment.
Taking the implementation method based on the distant dizzy distant resurrection of getting killed of LTE network cluster terminal as example, please refer to accompanying drawing 1,The function declaration of the each part of network is as follows:
Wireless terminal: the termination function module that realizes LTE broadband multimedia cluster system network.
ENB:LTE base station, realizes air interface function, comprise air interface physical layer, MAC layer andNetwork layer function, and user is linked into different business service networks.
MME: mobile management entity is the functional module of controlling data service, mainly responsible Access Control,The functions such as mobile management, session management and Route Selection. Data industry under the distant dizzy distant state of getting killed of this programme controlThe processing of business.
S-CSCF: service cluster Service control center is the functional module of controlling speech business, is responsible for placeReason registration process, carries out route judgement, peace preservation association's speech phase and storage service configuration. This programme control is distantThe processing of speech business under the dizzy distant state of getting killed.
HSS: home subscriber server, for the main number of all users and data-voice service related dataAccording to memory cell, key data comprises user identity, log-on message, access parameter and Service Trigger Information.
DC: dispatching desk, as control centre, carries out distant dizzy distant getting killed to user and brings back to life operation.
Embodiment 1:
Please refer to accompanying drawing 2, terminal is comprised by distant dizzy successful idiographic flow under idle condition:
Step 101, DC send SIP (MESSAGE) message, MESSAGE to the CSCF at its placeMessage is carried distant dizzy user profile;
Step 102, CSCF to user attaching HSS send distant dizzy/distant getting killed/bring back to life request command TSR;
Step 103, HSS are designated as User Status distant dizzy, to TCF2 return distant dizzy/distant getting killed/brings back to life response to orderMake TSA;
Step 104, CSCF return to SIP (200OK) message to DC, represent that distant swoon/distant getting killed/bringing back to life pleaseAsk acceptance;
Step 105, HSS judge User Status: if user's registration, inquiring user positional information, Xiang YongFamily S-CSCF sends the order of user contracting data update request;
Step 106, S-CSCF are recorded as User Status distant dizzy, return to user contracting data more to HSSNew response command;
Step 107, S-CSCF send SIP (MESSAGE) message to MME, send distant dizzy distant to userGet killed to bring back to life and ask;
Step 108, MME return to 200OK, User Status are recorded as distant dizzy;
Step 109, MME initiate paging flow process to UE;
After step 110, paging success, MME is by the distant dizzy terminal of NAS message, and opening timing device T1,Acquiescence 5s;
Step 111, UE receive that distant dizzy instruction enters corresponding state, and return successfully.
If timer T1 is overtime, MME will retransmit the distant dizzy terminal of NAS message.
Embodiment 2:
Please refer to accompanying drawing 3, terminal is comprised by distant dizzy successful idiographic flow in individual calling:
Step 201, DC send SIP (MESSAGE) message, MESSAGE to the CSCF at its placeMessage is carried distant dizzy user profile;
Step 202, CSCF to user attaching HSS send distant dizzy/distant getting killed/bring back to life request command TSR;
Step 203, HSS are designated as User Status distant dizzy, to CSCF return distant dizzy/distant getting killed/bring back to life responseOrder;
Step 204, CSCF return to SIP (200OK) message, represent distant dizzy/distant getting killed/brings back to life request acceptance;
Step 205, HSS judge user's registration, and inquiring user positional information, sends out to user S-CSCFSend subscription data information updating request command;
Step 206, S-CSCF are revised as User Status distant dizzy, and return to user contracting data to HSSUpgrade response command;
Step 207, S-CSCF send SIP (MESSAGE) message to MME, send distant dizzy distant to userGet killed to bring back to life and ask;
Step 208, MME return to 200OK, User Status are recorded as distant dizzy;
Step 209, MME are by the distant dizzy terminal of NAS message, and opening timing device, acquiescence 5s;
Step 210, S-CSCF receive 200OK, initiate individual calling and discharge flow process; Individual calling herein discharges alsoCan be initiated receiving after distant dizzy instruction by terminal;
Step 211, UE receive that distant dizzy instruction enters corresponding state, and return successfully.
Wherein, individual calling discharges also and can be initiated receiving after distant dizzy instruction by terminal.
Based on the present embodiment, if terminal is in group-calling service and be the promoter of described group calling, described inIndividual calling or described group calling will be released; If described terminal is in the speaker of group-calling service, but described in not beingThe promoter of group calling, the right of speech of described terminal is released; If described terminal is in the obedient of group-calling serviceSide, and be not the promoter of described group calling, described terminal exits described group calling; If described terminal is inIn data service, described data service is terminated. Same, described releasing operation can be triggered by terminal,Also can be triggered by network side; The termination of described data service can be by base station triggers.
Embodiment 3:
Please refer to accompanying drawing 4, when endpoint registration, HSS recording user state is that distant dizzy, the SOT state of termination is for normalSituation under, concrete handling process comprises:
Step 301, terminal are initiated AttachResquest to MME;
Step 302, MME are to HSS launch position update request;
Step 303, HSS home position upgrade response;
Step 304, MME return to AttachAccept to terminal;
Step 305, terminal are returned to AttachComplete;
Step 306, terminal are initiated cluster registration TrunkingRegisterRequest to MME, carry endHold the distant dizzy distant resurrection state of getting killed: normal;
Step 307, the distant dizzy distant resurrection state of getting killed of MME recording user: normal, send to S-CSCFSIP_Register message, the distant dizzy distant resurrection state of getting killed of carried terminal: normal;
Step 308, S-CSCF send service log-on request SAR to HSS;
Step 309, HSS return to SAA, carry User Status " distant dizzy ";
Step 310, S-CSCF recording user state: distant dizzy, return to 200OK to MME, represent registrationSuccess;
Step 311, MME return to TrunkingRegisterAttach to terminal;
Step 312, terminal send TrunkingRegisterComplete to MME;
Step 313, HSS judge user MME registration, and sending canceling position to the MME of former service pleaseAsk CLR. If MME is identical, there is no step 313 and 314;
Step 314, former serving MME are returned to CLA;
Step 315, HSS judge user S-CSCF registration, and HSS sends industry to the S-CSCF of former serviceBusiness subscription data is deleted message SCR. If S-CSCF is identical, there is no step 315 and 316;
Step 316, former serving CSCF return deletes response SCA;
If step 317 S-CSCF judges that the User Status of HSS record is different from the state of terminal record,Send SIP (MESSAGE) message, distant dizzy terminal to MME;
Step 318, MME return to 200OK, and amendment User Status is distant dizzy;
Step 319, MME are by the distant dizzy terminal of NAS message, and opening timing device, acquiescence 5s;
Step 320, UE receive that distant dizzy instruction enters corresponding state, and return successfully.
Based on identical design, the present invention also proposes the distant dizzy distant system of getting killed and bringing back to life of a kind of colony terminal, comprising:Described dispatching desk sends instruction, and described instruction is used to indicate described terminal and enters one of following state: distant dizzy,Distantly get killed, normally; Described home subscriber server, group service control centre and mobile management entity are received instituteState after instruction, record described colony terminal and enter corresponding state; Described colony terminal is received after described instructionEnter corresponding state.
Preferably, when the state recording in the state of described colony terminal and home subscriber server is inconsistentTime, described instruction is resend terminal.
Preferably, described instruction comprises and distantly dizzyly, distant gets killed and bring back to life instruction: described distant dizzy instruction is used to indicate instituteState colony terminal and enter distant dizzy state, terminal is only searched under distant dizzy state and registration, authentication, positioning serviceRetain effectively; Described resurrection instruction is used to indicate distant dizzy colony terminal and enters normal condition, and it is distant that terminal is recoveredAll functions before dizzy state; The described distant instruction of getting killed is used to indicate described colony terminal and enters the distant state of getting killed, eventuallyAny business can not be applied for or accept to end under the distant state of getting killed.
Preferably, after the described distant dizzy or distant instruction of getting killed is sent out, if described terminal is in individual calling business,Or be in group-calling service and be the promoter of described group calling, described individual calling or described group calling are released;If described terminal is in the speaker of group-calling service, but not the promoter of described group calling, described terminalRight of speech be released; If described terminal is in the obedient party of group-calling service, and it not the initiation of described group callingPerson, described terminal exits described group calling; If described terminal is in data service, described data industryBusiness is terminated.
Preferably, described release is triggered by described colony terminal or core network side triggers; Described data serviceTermination by base station triggers.
Can be found out by above each embodiment, the distant dizzy distant resurrection scheme of getting killed provided by the invention has solved existing sideThe deficiency of case. In the present invention, only there are 3 states (distant dizzy, distant get killed, normally) in system, has simplifiedThe processing of each network element; Bring back to life operation once dispatching desk carries out distant dizzy distant getting killed to user, home subscriber server justRecording distant dizzy distant getting killed brings back to life successfully. Online as user, home subscriber server is revised user's service cluster businessThe User Status of control centre, group service control centre issues distant dizzy distant getting killed and brings back to life order, and this order can be throughCross mobile management entity, mobile management entity immediate record User Status, if now user terminal receives distantDizzy distant getting killed brought back to life order, and the SOT state of termination will be consistent with network side, there will not be the existing state of realizingInconsistence problems. When user registers, group service control centre judge home subscriber server recording status withWhether the state of terminal is consistent. If inconsistent, group service control centre sends distant to mobile management entityThe dizzy distant resurrection instruction of getting killed, this order is transmitted to user by mobile management entity. Meanwhile, because group service controlIn center processed, mobile management entity, User Status is consistent, there will not be and can do data service and cannot do languageThe problem of sound business.
One of ordinary skill in the art will appreciate that: all or part of step that realizes said method embodiment canTo complete by the relevant hardware of programmed instruction, aforesaid program can be stored in an embodied on computer readable and depositIn storage media, this program, in the time carrying out, is carried out the step that comprises said method embodiment; And aforesaid storageMedium comprises: the various media that can be program code stored such as ROM, RAM, magnetic disc or CD.
Finally it should be noted that: above embodiment is only in order to technical scheme of the present invention to be described, but not to its limitSystem; Although the present invention is had been described in detail with reference to previous embodiment, those of ordinary skill in the artBe to be understood that: its technical scheme that still can record aforementioned each embodiment is modified, or to itMiddle part technical characterictic is equal to replacement; And these amendments or replacement do not make appropriate technical solutionEssence departs from the spirit and scope of various embodiments of the present invention technical scheme.
Claims (10)
1. the distant dizzy distant implementation method of getting killed and bringing back to life of colony terminal, is characterized in that, comprising:
Dispatching desk sends instruction, and described instruction is used to indicate described terminal and enters one of following state: distant dizzy,Distantly get killed, normally;
Home subscriber server, group service control centre and mobile management entity are received after described instruction, noteRecord described colony terminal and enter corresponding state;
Described colony terminal enters corresponding state after receiving described instruction.
2. method according to claim 1, is characterized in that, also comprises: when described colony terminalState and home subscriber server in the state that records when inconsistent, described instruction is resend endEnd.
3. method according to claim 1, is characterized in that, described instruction comprises distant dizzy, distant getting killedWith bring back to life instruction:
Described distant dizzy instruction is used to indicate described colony terminal and enters distant dizzy state, terminal under distant dizzy state onlySearch and registration, authentication, positioning service retain effectively;
Described resurrection instruction is used to indicate distant dizzy colony terminal and enters normal condition, and terminal is recovered distant dizzy stateFront all functions;
The described distant instruction of getting killed is used to indicate described colony terminal and enters the distant state of getting killed, terminal under the distant state of getting killed notCan apply for or accept any business.
4. method according to claim 3, is characterized in that, also comprises: described distant dizzy or distant getting killedAfter instruction is sent out,
If described terminal is in individual calling business, or is in group-calling service and is the initiation of described group callingPerson, described individual calling or described group calling are released;
If described terminal is in the speaker of group-calling service, but be not the promoter of described group calling, described inThe right of speech of terminal is released;
If described terminal is in the obedient party of group-calling service, and be not the promoter of described group calling, described inTerminal exits described group calling;
If described terminal is in data service, described data service is terminated.
5. method according to claim 4, is characterized in that, described release is by described colony terminalTrigger or network side triggering; The termination of described data service is by base station triggers.
6. the distant dizzy distant system that realizes of getting killed and bringing back to life of colony terminal, described system comprises dispatching desk, ownershipClient server, group service control centre, mobile management entity and colony terminal, is characterized in that, bagDraw together:
Described dispatching desk sends instruction, and described instruction is used to indicate described terminal and enters one of following state: distantDizzy, distantly get killed, normally;
Described home subscriber server, group service control centre and mobile management entity are received described instructionAfter, record described colony terminal and enter corresponding state;
Described colony terminal enters corresponding state after receiving described instruction.
7. system according to claim 6, is characterized in that, also comprises: when described colony terminalState and home subscriber server in the state that records when inconsistent, described instruction is resend endEnd.
8. system according to claim 6, is characterized in that, described instruction comprises distant dizzy, distant getting killedWith bring back to life instruction:
Described distant dizzy instruction is used to indicate described colony terminal and enters distant dizzy state, terminal under distant dizzy state onlySearch and registration, authentication, positioning service retain effectively;
Described resurrection instruction is used to indicate distant dizzy colony terminal and enters normal condition, and terminal is recovered distant dizzy stateFront all functions;
The described distant instruction of getting killed is used to indicate described colony terminal and enters the distant state of getting killed, terminal under the distant state of getting killed notCan apply for or accept any business.
9. system according to claim 8, is characterized in that, also comprises: described distant dizzy or distant getting killedAfter instruction is sent out,
If described terminal is in individual calling business, or is in group-calling service and is the initiation of described group callingPerson, described individual calling or described group calling are released;
If described terminal is in the speaker of group-calling service, but be not the promoter of described group calling, described inThe right of speech of terminal is released;
If described terminal is in the obedient party of group-calling service, and be not the promoter of described group calling, described inTerminal exits described group calling;
If described terminal is in data service, described data service is terminated.
10. system according to claim 9, is characterized in that, described release is by described colony terminalTrigger or network side triggering; The termination of described data service is by base station triggers.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410577464.9A CN105592425B (en) | 2014-10-24 | 2014-10-24 | The method and system of the distant distant resurrection of getting killed of swooning of colony terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410577464.9A CN105592425B (en) | 2014-10-24 | 2014-10-24 | The method and system of the distant distant resurrection of getting killed of swooning of colony terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105592425A true CN105592425A (en) | 2016-05-18 |
| CN105592425B CN105592425B (en) | 2019-02-22 |
Family
ID=55931573
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410577464.9A Expired - Fee Related CN105592425B (en) | 2014-10-24 | 2014-10-24 | The method and system of the distant distant resurrection of getting killed of swooning of colony terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105592425B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107135491A (en) * | 2017-05-19 | 2017-09-05 | 哈尔滨海能达科技有限公司 | A kind of terminal control method and base station |
| CN109246589A (en) * | 2017-06-14 | 2019-01-18 | 普天信息技术有限公司 | A kind of method and apparatus for realizing distant dizzy terminal positioning business |
| CN112714403A (en) * | 2019-10-24 | 2021-04-27 | 普天信息技术有限公司 | Multimode converged cluster system and communication method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917669A (en) * | 2005-08-19 | 2007-02-21 | 中兴通讯股份有限公司 | Control method for mobile station to remote killing/reviving operation in CDMA digital group system |
| CN101137108A (en) * | 2006-09-29 | 2008-03-05 | 中兴通讯股份有限公司 | Method to implement roaming terminal inhibition/revival of cluster system |
| CN103167479A (en) * | 2011-12-12 | 2013-06-19 | 鼎桥通信技术有限公司 | Method, device and system for achieving remote inhibition and remote activation of terminal |
-
2014
- 2014-10-24 CN CN201410577464.9A patent/CN105592425B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917669A (en) * | 2005-08-19 | 2007-02-21 | 中兴通讯股份有限公司 | Control method for mobile station to remote killing/reviving operation in CDMA digital group system |
| CN101137108A (en) * | 2006-09-29 | 2008-03-05 | 中兴通讯股份有限公司 | Method to implement roaming terminal inhibition/revival of cluster system |
| CN103167479A (en) * | 2011-12-12 | 2013-06-19 | 鼎桥通信技术有限公司 | Method, device and system for achieving remote inhibition and remote activation of terminal |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107135491A (en) * | 2017-05-19 | 2017-09-05 | 哈尔滨海能达科技有限公司 | A kind of terminal control method and base station |
| CN107135491B (en) * | 2017-05-19 | 2020-05-12 | 哈尔滨海能达科技有限公司 | Terminal control method and base station |
| CN109246589A (en) * | 2017-06-14 | 2019-01-18 | 普天信息技术有限公司 | A kind of method and apparatus for realizing distant dizzy terminal positioning business |
| CN109246589B (en) * | 2017-06-14 | 2020-10-30 | 普天信息技术有限公司 | Method and equipment for realizing positioning service of remote halo terminal |
| CN112714403A (en) * | 2019-10-24 | 2021-04-27 | 普天信息技术有限公司 | Multimode converged cluster system and communication method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105592425B (en) | 2019-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110915248B (en) | Data enhancement for ESIM profile operation callbacks | |
| US9967723B2 (en) | Roaming LTE emergency call with call back number retrieval | |
| US10187786B2 (en) | System and method for handling inactive SIM cards | |
| US20180034974A1 (en) | Method and system for dynamic cellular networking activation for virtual sim service | |
| CN106576227A (en) | Method, device and system for interconnecting trunking DMR/PDT and conventional DMR/PDT | |
| CN105592425A (en) | Realization method and system for restoration from non-transmitting state and non-transmitting and non-receiving state of cluster terminal | |
| EP3742771B1 (en) | M2m sm-sr to sm-dp notification | |
| CN106792627B (en) | Method and system for realizing multi-device communication | |
| WO2016078406A1 (en) | Service opening method and apparatus and hss server | |
| CN104717180A (en) | Method and system used for suppressing triggering of called service in IMS network | |
| US10827338B1 (en) | Scam mitigation back-off | |
| EP2953388A1 (en) | System and method for handling inactive SIM cards | |
| WO2017218177A1 (en) | Roaming lte emergency call with call back number retrieval | |
| CN101237678B (en) | Activation and registration method, system and device for personal management circuit domain terminal | |
| CN101924995A (en) | Callback method, callback device and visit mobile switching center in emergency call service | |
| BR112012031025B1 (en) | GROUP CALL PARTICIPATION METHOD AND GROUP CALL PARTICIPATION SYSTEM | |
| WO2020216063A1 (en) | Method and apparatus for implementing service call, and device | |
| CN103220823A (en) | Point-to-point call release method and device in time division-long term evolution (TD-LTE) digital trunked communication system | |
| KR101929389B1 (en) | Method and apparatus for sensing piracy terminal | |
| CN101707744B (en) | Method and device for controlling call in trunking communication system | |
| US9980124B2 (en) | System and method for handling unused SIM cards | |
| CN103152714B (en) | The methods, devices and systems of call reminding | |
| CN109729042A (en) | A kind of transmission of information, processing method and processing device | |
| CN106332073B (en) | A kind of cluster group root key update method | |
| WO2022127587A1 (en) | Multi-card terminal emergency call method and apparatus, and electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PP01 | Preservation of patent right |
Effective date of registration: 20191121 Granted publication date: 20190222 |
|
| PP01 | Preservation of patent right | ||
| PD01 | Discharge of preservation of patent |
Date of cancellation: 20200710 Granted publication date: 20190222 |
|
| PD01 | Discharge of preservation of patent | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20190222 Termination date: 20201024 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |