CN103167479B - Realize that terminal is distant gets killed or the distant methods, devices and systems opened - Google Patents
Realize that terminal is distant gets killed or the distant methods, devices and systems opened Download PDFInfo
- Publication number
- CN103167479B CN103167479B CN201110411581.4A CN201110411581A CN103167479B CN 103167479 B CN103167479 B CN 103167479B CN 201110411581 A CN201110411581 A CN 201110411581A CN 103167479 B CN103167479 B CN 103167479B
- Authority
- CN
- China
- Prior art keywords
- remote
- terminal
- core network
- identifier
- inhibition
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 238000012790 confirmation Methods 0.000 claims abstract description 29
- 230000005764 inhibitory process Effects 0.000 claims description 84
- 230000004913 activation Effects 0.000 claims description 64
- 230000004044 response Effects 0.000 claims description 50
- 230000009849 deactivation Effects 0.000 claims description 41
- 230000008033 biological extinction Effects 0.000 claims 1
- 230000011664 signaling Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 12
- 230000000875 corresponding effect Effects 0.000 description 9
- 208000033748 Device issues Diseases 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 206010048669 Terminal state Diseases 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides and a kind ofly realize that terminal is distant gets killed or the distant methods, devices and systems opened, wherein method comprises: receive the non access stratum NAS message that equipment of the core network sends, and carries distant mark and the distant type of getting killed of getting killed, or carry the knowledge of distant opening of bid in described NAS message; Perform according to described distant get killed mark and distant type of getting killed and distantly to get killed, or open according to distant opening of bid knowledge execution is distant; Distantly get killed if perform or be distantly split into merit, then described terminal sends order to described equipment of the core network and accepts confirmation; Distantly get killed if perform or distantly open failure, then described terminal receives the described NAS message that described equipment of the core network sends again.Of the present inventionly realize that terminal is distant gets killed or the distant methods, devices and systems opened, equipment of the core network issues distant getting killed or distant instruction of opening by NAS message to terminal, achieve distant distant the opening of getting killed to terminal in LTE and 3G digital cluster system, and alleviate the impact on base station.
Description
Technical Field
The present invention relates to communications technologies, and in particular, to a method, an apparatus, and a system for implementing remote deactivation or remote activation of a terminal.
Background
In real life, a problem that the UE is lost (e.g. stolen) sometimes occurs, and based on the security requirement, the UE lost person may request an operation maintainer to remotely kill the UE, that is, under the condition that the UE is not recovered, the UE is restricted from performing services in the network. The remote kill can be divided into a temporary remote kill and a permanent remote kill, and the UE on the temporary remote kill can attach to the network and perform the flow related to mobility management, but cannot perform the rest services provided by the network; the permanently killed UE can never access the network. For the UE which is temporarily remotely killed, the operation maintainer can remotely open the UE as needed, that is, the service performed in the network is recovered without withdrawing the UE, and the UE which is permanently remotely killed cannot be remotely opened. The remote killing and remote opening may be performed for an International Mobile Subscriber Identity (IMSI) and an International Mobile Equipment Identity (IMEI) of the UE.
The method for remote killing and remote opening of the terminal in the cluster system in the prior art needs the participation of the base station, namely, the network equipment of the cluster system sends a remote killing and remote opening command to the base station, and the base station sends the command to the terminal, so that the technical problem caused by the fact that the interaction process of the base station, UE and core network equipment is increased inevitably due to the fact that one more network element is used for interaction, the burden and the network load of the base station are increased, the network performance where the base station is located is possibly influenced by the remote killing and remote opening command sent to the terminal by the base station, and more abnormal processing is possibly caused; in addition, with the development of mobile communication technology, Long Term Evolution (LTE) project has been applied more and more widely, but no method for implementing remote switch-on of a terminal exists in the current LTE network, and the user requirements can not be met.
Disclosure of Invention
The invention aims to provide a method, a device and a system for realizing remote inhibition or remote opening of a terminal, so as to realize remote inhibition and remote opening of the terminal in LTE and 3G digital trunking systems and reduce the influence on a base station.
The invention provides a method for realizing remote killing or remote opening of a terminal on one hand, which comprises the following steps:
a terminal receives a non-access stratum (NAS) message sent by core network equipment, wherein the NAS message carries a remote inhibition identifier and a remote inhibition type or carries a remote activation identifier;
the terminal executes remote inhibition according to the remote inhibition identification and the remote inhibition type, or executes remote inhibition according to the remote inhibition identification;
if the remote killing or the remote opening is successfully executed, the terminal sends a command acceptance confirmation to the core network equipment; and if the remote killing is executed or the remote opening fails, the terminal receives the NAS message sent again by the core network equipment.
Another aspect of the present invention provides a method for implementing remote deactivation or remote activation of a terminal, including:
the method comprises the steps that core network equipment sends a non-access stratum (NAS) message to a terminal, wherein the NAS message carries a remote inhibition identifier and a remote inhibition type or a remote activation identifier, so that the terminal executes remote inhibition according to the remote inhibition identifier and the remote inhibition type or executes remote activation according to the remote activation identifier;
the core network equipment starts a timer; and if the command acceptance confirmation returned by the terminal is not received yet after the timing time set by the timer is up, the core network equipment sends the NAS message to the terminal again.
Yet another aspect of the present invention provides a terminal, including:
a command receiving unit, configured to receive a non-access stratum NAS message sent by a core network device, where the NAS message carries a remote inhibition identifier and a remote inhibition type, or carries a remote activation identifier; and, further configured to receive the NAS message sent again by the core network device if remote deactivation is performed or remote activation fails;
a command executing unit, configured to execute remote inhibition according to the remote inhibition identifier and the remote inhibition type, or execute remote activation according to the remote activation identifier;
and the command confirmation unit is used for executing the remote inhibition according to the remote inhibition identifier and the remote inhibition type or executing the remote activation according to the remote activation identifier, and if the remote inhibition is executed or the remote activation is successful, sending a command acceptance confirmation to the core network equipment.
Yet another aspect of the present invention provides a core network device, including:
a command sending unit, configured to send a non-access stratum NAS message to a terminal, where the NAS message carries a remote inhibition identifier and a remote inhibition type, or carries a remote activation identifier, so that the terminal performs remote inhibition according to the remote inhibition identifier and the remote inhibition type, or performs remote activation according to the remote activation identifier;
the timing unit is used for starting a timer after the NAS message is sent to the terminal; and when the timing time set by the timer reaches but the command acceptance confirmation returned by the terminal is not received, the command sending unit is instructed to send the NAS message to the terminal again.
In another aspect, the present invention provides a system for implementing remote deactivation or remote activation of a terminal, including: the core network equipment and the terminal are provided by the invention.
According to the method, the device and the system for realizing the remote inhibition or remote opening of the terminal, the core network equipment issues the remote inhibition or remote opening instruction to the terminal through the NAS message, so that the remote inhibition and remote opening of the terminal in the LTE and 3G digital cluster system are realized, and the influence on a base station is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
FIG. 1 is a flowchart illustrating an embodiment of a method for implementing remote deactivation or remote activation of a terminal according to the present invention;
fig. 2 is a signaling diagram of another embodiment of a method for implementing remote deactivation or remote activation of a terminal according to the present invention;
fig. 3 is a signaling diagram of another embodiment of a method for implementing remote deactivation or remote activation of a terminal according to the present invention;
fig. 4 is a signaling diagram of another embodiment of a method for implementing remote deactivation or remote activation of a terminal according to the present invention;
FIG. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an embodiment of a core network device according to the present invention;
fig. 7 is a schematic structural diagram of an embodiment of a system for implementing remote deactivation or remote activation of a terminal according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
The main technical scheme of the invention is that core network equipment transmits a remote killing or remote opening command to terminal UE through Non-access stratum (NAS) information, and the UE executes the remote killing or remote opening according to the command; the scheme is suitable for both TD-LTE and 3G digital trunking systems, so that remote killing and remote opening of the terminal in the LTE are realized, and the NAS information is interaction directly carried out between the UE and the core network equipment, so that the base station does not need to participate, and the influence on the base station is avoided.
The technical solution of the present invention is further described in detail by the accompanying drawings and the specific embodiments.
Example one
Fig. 1 is a schematic flow chart of an embodiment of a method for implementing remote deactivation or remote activation of a terminal in the present invention, where the method for implementing remote deactivation or remote activation of a terminal in this embodiment may be executed by a terminal UE, and as shown in fig. 1, the method may include:
101. a terminal receives a non-access stratum (NAS) message sent by core network equipment, wherein the NAS message carries a remote inhibition identifier and a remote inhibition type or carries a remote activation identifier;
for example, in an LTE network, the core network device is a Mobility Management Entity (MME); correspondingly, the terminal receives the NAS message sent by the MME. For example, in a 3G digital trunking system, the core network device is a Mobile Switching Center (MSC) or a GPRS service support node (SGSN); correspondingly, the terminal receives the NAS message sent by the MSC or the SGSN;
the remote-killing mark is used for indicating the terminal to perform remote killing, and the remote-killing type comprises permanent remote killing or temporary remote killing; the remote-on mark is used for indicating the terminal in the temporary remote-off state to execute remote-on and restore the service, and the terminal which is permanently remote-off can not be remotely switched on.
102. The terminal executes remote inhibition according to the remote inhibition identification and the remote inhibition type, or executes remote opening according to the remote opening identification;
if the remote deactivation or the remote opening is successfully executed, the terminal sends a command acceptance confirmation to the core network equipment; and if the remote killing is executed or the remote opening fails, the terminal receives the NAS message sent again by the core network equipment.
Wherein, the core network equipment starts a timer; and if the command acceptance confirmation returned by the terminal is not received yet after the timing time set by the timer is up, the core network equipment sends the NAS message to the terminal again.
In the method for implementing the remote kill or remote turn-on of the terminal in this embodiment, the core network device issues the remote kill or remote turn-on instruction to the terminal through the NAS message, so that the remote kill and remote turn-on of the terminal in the LTE and 3G digital trunking systems are implemented, and the influence on the base station is reduced.
The following describes the specific processes of remote killing and remote opening executed by the technical solution of the present invention through three embodiments, and further, on this basis, the process of status alignment performed after execution failure is described, where the status alignment process is performed when remote killing or remote opening failure is executed by using NAS message.
Example two
Fig. 2 is a signaling diagram of another embodiment of the method for implementing remote deactivation or remote activation of a terminal in the present invention, where the method for implementing remote deactivation or remote activation of a terminal in this embodiment is a flow for performing remote deactivation on a terminal UE by using an NAS message, and as shown in fig. 2, the method may include:
201. the core network equipment receives a command of remotely killing the UE;
specifically, the core network device may receive the above command sent by the operation maintainer or other authorized client through the management interface. The command for remote kill of the UE includes the ID of the UE and the remote kill type. The core network equipment is an MME if the core network equipment is in an LTE network; if in the 3G digital trunking system, it is MSC or SGSN.
202. The core network equipment establishes signaling connection with the UE;
for example, before performing step 202, the core network device may detect whether a signaling connection exists with the UE. If the core network device finds that no signaling connection exists between the core network device and the UE, the core network device can send paging to the UE to trigger the UE to carry out a signaling connection establishment process;
if the core network device finds that there is a signaling connection with the UE, it may directly perform 203.
203. The core network equipment sends NAS information carrying the remote inhibition identification and the remote inhibition type to the UE;
the NAS message carrying the remote-kill identifier and the remote-kill type can also be called a remote-kill command, and the remote-kill command carries the ID of the UE, the remote-kill identifier and the remote-kill type. The remote-killing mark is used for indicating the UE to perform remote-killing operation, and the remote-killing type is used for indicating that the remote-killing is permanent remote-killing or temporary remote-killing.
The core network equipment transmits the remote kill command to the UE by using the NAS message without the participation of the base station, thereby reducing the burden and the network load of the base station and reducing the influence on the network where the base station is located.
204. The core network equipment starts a timer and waits for the confirmation of the UE;
in order to prevent the occurrence of the situation that the UE fails to execute the command but the core network device cannot know, in this embodiment, the core network device starts the timer after sending the remote kill command to the UE. In addition, in this embodiment, it is configured that after receiving the NAS message, the UE performs remote kill, and if the remote kill is successfully performed, sends a command acceptance confirmation to the core network device to notify the core network device that the UE has successfully performed the remote kill; otherwise, if the UE does not receive the NAS message or fails to perform the remote kill, it is not necessary to send a command acceptance confirmation to the core network device.
205. And if the timing time set by the timer is up and the core network equipment still does not receive the command acceptance confirmation returned by the UE, the core network equipment sends the NAS message to the UE again.
Through the scheme that the core network equipment starts the timer and retransmits the remote dead command, the guarantee degree of the execution of the remote dead command is improved, and the situation that the core network equipment does not know and process the command execution failure of the UE end is prevented.
In this embodiment, the core network device re-transmits the remote kill command with the limitation of the number of re-transmission times, that is, the maximum number of re-transmission times can be preset; if the command acceptance confirmation of the UE is not obtained after the maximum retransmission times are reached, the retransmission is not performed, and all service resources of the UE are released.
Specifically, when the UE performs the remote kill, the UE can perform a corresponding remote kill operation according to the remote kill type in the remote kill command. For example, remote killing includes temporary remote killing (also called as "telepresence") and permanent remote killing, where a UE on the temporary remote killing can attach to a network and perform a flow related to mobility management, but cannot perform other services provided by the network; the UE that is permanently killed can never access the network, and the UE can take measures such as key/mobile phone destruction, so that the UE can not access the network permanently. If the remote kill type carried in the remote kill command is temporary remote kill, the UE executes temporary remote kill; if the remote kill type carried in the remote kill command is a permanent remote kill, the UE performs the permanent remote kill.
For example, in LTE where the core network device is MME, there is usually a default bearer between the permanently online UE and the MME; when the temporary remote deactivation is performed, the default bearer can be selected to be deleted (when the temporary remote deactivation is performed, the bearer needs to be reestablished and the IP needs to be allocated), and the deletion of the bearer, the establishment of the bearer and the like can be initiated by the MME and performed in cooperation with the UE; or not deleting the default bearer, and only releasing the S1 interface resource of the default bearer, where the S1 interface is an interface between the core network device and the UE.
206. The UE performs remote killing;
207. and the UE returns a command acceptance confirmation to the core network equipment.
In the method for implementing remote kill or remote turn-on of the terminal of this embodiment, the core network device issues the remote kill instruction to the terminal through the NAS message, thereby implementing remote kill to the terminal in the LTE and 3G digital trunking systems, and reducing the influence on the base station.
EXAMPLE III
Fig. 3 is a signaling diagram of another embodiment of the method for implementing remote deactivation or remote activation of a terminal according to the present invention, where the method for implementing remote deactivation or remote activation of a terminal according to the present embodiment is a procedure for executing remote activation on a terminal UE by using an NAS message, and the remote activation procedure is substantially the same as the remote deactivation procedure shown in fig. 2, except that a command sent by a core network device to the UE is different. As shown in fig. 3, the method may include:
301. a core network device receives a command for remotely opening the UE;
specifically, the core network device may receive the above command sent by the operation maintainer or other authorized client through the management interface. The command for remote kill of the UE includes the ID of the UE and the remote kill type. The core network equipment is an MME if the core network equipment is in an LTE network; if in the 3G digital trunking system, it is MSC or SGSN.
302. The core network equipment establishes signaling connection with the UE;
for example, before performing step 202, the core network device may detect whether a signaling connection exists with the UE. If the core network device finds that no signaling connection exists between the core network device and the UE, the core network device can send paging to the UE to trigger the UE to carry out a signaling connection establishment process;
if the core network device finds that there is a signaling connection with the UE, 303 may be performed directly.
303. The core network equipment sends an NAS message carrying a remote opening identifier to the UE;
the NAS message carrying the remote-open identifier may also be referred to as a remote-open command, where the remote-open command carries an ID of the UE (the ID of the UE is optionally carried), and a remote-open parameter; the remote-on parameter may include, for example, a remote-on identifier, which is used to instruct the UE in the temporary remote-off state to perform a remote-on operation.
The core network equipment transmits the remote-open command to the UE by using the NAS message without the participation of the base station, thereby reducing the burden and the network load of the base station and reducing the influence on the network where the base station is positioned.
304. The core network equipment starts a timer and waits for the confirmation of the UE;
in order to prevent the UE from failing to execute the command but the core network device cannot know the command, in this embodiment, the core network device starts the timer after sending the remote-on command to the UE. In addition, in this embodiment, it is set that after the UE successfully executes the remote-on command, it needs to send a command acceptance confirmation to the core network device to notify the core network device that the UE has successfully executed the remote-on command; otherwise, if the UE fails to execute the remote-on command, it is not necessary to send a command acceptance confirmation to the core network device.
If the timing time set by the timer is up, but the core network device still does not receive the command acceptance confirmation returned by the UE, the core network device continues to execute 305, otherwise, execute 306.
305. The core network device sends the NAS message to the UE again, i.e. resends the remote-on command.
By the scheme that the core network equipment starts the timer and retransmits the remote opening command, the execution guarantee degree of the remote opening command is improved, and the situation that the core network equipment does not know and process the command due to the failure of the execution of the UE end command is prevented.
In this embodiment, the core network device retransmits the remote open command with the limitation of the retransmission times, that is, the maximum retransmission times can be preset; if the command acceptance confirmation of the UE is not obtained after the maximum retransmission times are reached, the retransmission is not performed, and all service resources of the UE are released.
306. The UE performs remote opening;
wherein, the UE can perform the remote-on operation according to the remote-on command. For example, in LTE where the core network device is MME, there is usually a default bearer between the permanently online UE and the MME; if the default bearer has been deleted when the remote kill is temporarily performed, then at this time, the bearer needs to be reestablished and the IP needs to be allocated when the remote kill is performed; if the default bearer is not deleted but the resource of the S1 port of the bearer is released when the user temporarily goes to die, the resource of the S1 port needs to be re-established when the user goes to die.
307. And the UE returns a command acceptance confirmation to the core network equipment.
In the method for implementing remote deactivation or remote activation of the terminal in this embodiment, the core network device issues the remote activation instruction to the terminal through the NAS message, thereby implementing remote activation of the terminal in the LTE and 3G digital trunking systems, and reducing the influence on the base station.
Example four
Fig. 4 is a signaling diagram of another embodiment of the method for implementing remote deactivation or remote activation of a terminal according to the present invention, where a remote deactivation command sent by a core network device to a UE may fail to be executed due to some reason, which causes inconsistency between states of the UE and the core network device side, for example, a due state of the UE stored in the core network device side is temporary remote deactivation, but an actual state of the UE side is remote activation due to execution failure. The above situation of inconsistent states needs to be corrected by state alignment, that is, the UE state is kept consistent with the state of the core network device side by the state alignment procedure.
In this embodiment, which is a method for implementing the remote deactivation of the terminal, the alignment procedure when the above states are inconsistent occurs includes two independent cases, as shown in fig. 4, that is, 401 + 404 carries the state identifier cell in the state update response returned to the UE to enable the UE to be aligned, and 405 + 408 carries the state identifier cell in the service rejection returned to the UE to enable the UE to be aligned. The method can comprise the following steps:
401. UE sends request message to core network device, the request message includes state updating request, attachment request;
in the network, the UE basically has a periodic status update mechanism, for example, a Routing Area Update (RAU), a Location Area Update (LAU), a Tracking Area Update (TAU) and an attach request initiated when the UE is powered on each time, where the Routing Area Update (RAU) is sent by the UE in the 3G digital trunking communication system, and the location area update (TAU) is sent by the UE in LTE.
The request message carries the remote kill status of the UE itself, specifically, may carry a status identifier indicating whether the terminal is in the temporary remote kill status; for example, if the UE finds that it is in the state of temporarily remote killing, the remote killing identifier is carried in the request message and sent to the core network device, and the identifier may not be carried in other states. Correspondingly, if the core network device finds that the request message carries the remote inhibition identifier, it indicates that the UE is temporarily remotely inhibited, otherwise, if the request message does not carry the identifier, it indicates that the UE is in the remote activation state.
402. The core network equipment compares whether the stored UE state is consistent with the state in the request message sent by the UE;
the core network device may compare the actual state of the terminal determined according to the state identifier in the request message with an expected state of the terminal stored at the core network side (i.e., the stored terminal state corresponding to the remote-kill or remote-start identifier corresponding to the UE), and determine whether the states of the core network device side and the UE side are consistent.
If the expected state of the terminal stored in the core network device itself is not consistent with the actual state of the UE determined by the state identifier in the request message, for example, the due state of the UE stored in the core network device itself is remote kill (the state may be recorded when the core network device sends a remote kill command to the UE but has not received a command acceptance confirmation of the UE all the time, for example), but the state of the UE in the request message is not remote kill, then continue to execute 403. Otherwise, if the expected state of the terminal stored in the core network device is consistent with the actual state of the UE determined by the state identifier in the request message, no alignment is required, and the process ends.
When the two states do not coincide with each other, the state of the UE needs to be aligned with the state of the core network device, based on the state stored in the core network device.
403. The core network equipment sends a response message to the UE, wherein the response message comprises a state updating response or an attachment response;
the core network device carries a state identifier stored at the core network side and corresponding to the UE, such as a remote inhibition identifier and a remote inhibition type, or a remote activation identifier, in a state update response or an attachment response returned to the UE.
For example, the core network device checks the request message to know that the state of the UE is normal, that is, the UE is not remotely killed, but the state stored in the core network device and corresponding to the UE is remotely killed, and the remote kill type is temporary remote kill, which indicates that the core network device has previously issued a command of temporary remote kill to the UE, but the UE fails to execute for some reason, resulting in inconsistent states of the two at present; then, at this moment, the core network device carries the remote-killing identifier in the response message returned to the UE, the remote-killing type is temporary remote killing, so as to instruct the UE to perform remote killing again according to the above parameters, and perform state alignment with the core network side. If the core network device side detects that the state of the NAS message is consistent with the state of the UE, the response message may not carry the state identifier, so as to reduce the length of the NAS message.
The state identifier is carried by the response message of some request messages sent to the core network equipment by the UE, so that the UE aligns the state with the core network equipment side according to the state identifier, the flow is simple, and the implementation is convenient.
404. UE carries out state alignment;
after receiving the response message, the UE updates the state based on the identifier of the remote-on or remote-off state provided by the core network device side, and performs a corresponding action to keep state alignment with the core network device side, so that the actual state of the terminal is consistent with the expected state of the terminal stored in the core network device. For example, the UE performs remote killing according to the remote killing identifier sent by the core network side, or performs remote opening according to the remote opening identifier sent by the core network side.
The above 401-404 is to make the UE align the state by carrying the state identifier cell in the state update response returned to the UE, and the following 405-408 is to make the UE align the state by carrying the state identifier cell in the service rejection returned to the UE.
405. UE sends request message to core network device, the request message includes service request, request to use certain service;
406. the core network equipment detects the state of the UE and checks whether the UE is remotely killed;
if the core network equipment side UE is not in the remote deactivation state, the core network equipment directly provides the UE with the service requested by the core network equipment; if the UE on the core network device side is in the remote deactivation state, the process continues to execute 407.
407. The core network equipment sends service rejection to the UE;
the core network device carries the reject reason in the service rejection returned to the UE, that is, the UE has been killed, which is equivalent to sending the UE status identifier stored at the core network device side to the UE.
408. UE carries out state alignment;
after receiving the response message, the UE updates the status based on the remote status identifier provided by the core network device side, and performs a corresponding action to keep status alignment with the core network device side.
In the method for implementing the remote deactivation or remote opening of the terminal of the embodiment, the core network device carries the status identifier by using the response message of some request messages sent to the core network device by the UE, so that the UE aligns the status with the core network device side according to the status identifier, and the method has a simple flow and is convenient to implement.
EXAMPLE five
Fig. 5 is a schematic structural diagram of an embodiment of the terminal of the present invention, where the terminal of this embodiment may execute a method for implementing remote inhibition of the terminal according to any embodiment of the present invention, and this embodiment only briefly describes the structure of the terminal, and its specific principle may be described with reference to the method embodiment.
As shown in fig. 5, the terminal may include: a command receiving unit 51, a command executing unit 52, and a command confirming unit 53. Wherein,
a command receiving unit 51, configured to receive a non-access stratum NAS message sent by a core network device, where the NAS message carries a remote inhibition identifier and a remote inhibition type, or carries a remote activation identifier;
a command executing unit 52, configured to execute the remote kill according to the remote kill identifier and the remote kill type, or execute the remote kill according to the remote kill identifier;
and a command confirmation unit 53, configured to, after performing the remote kill according to the remote kill identifier and the remote kill type or performing the remote start according to the remote start identifier, send a command acceptance confirmation to the core network device if the remote kill is performed or the remote start is successful. Correspondingly, the command receiving unit 51 is further configured to receive the NAS message sent again by the core network device if the remote deactivation is performed or the remote start fails.
Further, the core network device is an MME, and the command receiving unit 51 is specifically configured to receive an NAS message sent by the mobility management entity MME; or, the core network device is an MSC or an SGSN, and the command receiving unit 51 is specifically configured to receive an NAS message sent by a mobile switching center MSC or a GPRS service support node SGSN.
Further, the terminal may further include a request sending unit 54 and a response receiving unit 55. Wherein,
a request sending unit 54, configured to send a request message to the core network device, where the request message carries a status identifier indicating whether the terminal is in a temporary remote kill state;
a response receiving unit 55, configured to receive a response message returned by the core network device, where the response message carries a remote inhibition identifier and a remote inhibition type, or a remote inhibition identifier, and the response message is generated when the core network device determines, according to the state identifier of the request message, that an actual state of the terminal is inconsistent with a stored expected state of the terminal;
correspondingly, the command executing unit 52 is specifically configured to execute the remote kill according to the remote kill identifier and the remote kill type in the response message, or execute the remote kill according to the remote kill identifier in the response message, so that the actual state of the terminal is consistent with the expected state of the terminal stored in the core network device.
Further, when the remote deactivation type is temporary remote deactivation and the core network device is MME. The command executing unit 52 is specifically configured to execute the temporary remote kill by deleting the default bearer between the terminal and the MME.
In the terminal of this embodiment, by setting the command receiving unit and the command executing unit, the core network device issues the remote-open instruction to the terminal through the NAS message, so that remote opening of the terminal in the LTE and 3G digital trunking systems is realized, and the influence on the base station is reduced.
EXAMPLE six
Fig. 6 is a schematic structural diagram of an embodiment of a core network device of the present invention, where the core network device of this embodiment may execute a method for implementing remote deactivation of a terminal in any embodiment of the present invention, and this embodiment only briefly describes the structure of the core network device, and a specific principle of the method may be described in combination with the embodiment.
As shown in fig. 6, the core network device may include: a command transmitting unit 61, a timing unit 62, wherein,
a command sending unit 61, configured to send an NAS message to a terminal, where the NAS message carries a remote inhibition identifier and a remote inhibition type, or carries a remote activation identifier, so that the terminal performs remote inhibition according to the remote inhibition identifier and the remote inhibition type, or performs remote activation according to the remote activation identifier;
a timing unit 62, configured to start a timer after sending the NAS message to the terminal; and when the timing time set by the timer reaches but the command acceptance confirmation returned by the terminal is not received, the command sending unit is instructed to send the NAS message to the terminal again.
Further, the core network device may further include a request receiving unit 63, a status comparing unit 64, and a response sending unit 65. Wherein,
a request receiving unit 63, configured to receive a request message sent by a terminal, where the request message carries a status identifier used to indicate whether the terminal is in a temporary remote kill state;
a state comparing unit 64, configured to compare the actual state of the terminal determined according to the state identifier in the request message with an expected state of the terminal stored in a core network device;
response sending unit 65 is used for when the comparison result of state comparing element is inconsistent, to the response message is returned to the terminal, the response message includes state update response, attached response or service rejection, carry the remote-kill sign and the remote-kill type that correspond with the terminal that core network equipment stored in the response message, perhaps remote-open sign, so that the terminal according to remote-kill sign and remote-kill type in the response message carry out remote-kill, perhaps carry out remote-open according to remote-open sign in the response message, so that the actual state of terminal with the core network equipment stored the expected state of terminal is consistent.
The core network device of this embodiment may be an MME, a mobile switching center MSC, or a GPRS service support node SGSN.
The core network device of this embodiment, by setting the command sending unit and the like, issues the remote-open instruction to the terminal through the NAS message, thereby implementing remote-open of the terminal in the LTE and 3G digital trunking systems, and reducing the influence on the base station.
EXAMPLE seven
Fig. 7 is a schematic structural diagram of an embodiment of a system for implementing remote deactivation or remote activation of a terminal according to the present invention, where the system of this embodiment can execute a method for implementing remote deactivation or remote activation of a terminal according to any embodiment of the present invention, and this embodiment only briefly describes the structure of the system, and the specific principle of the system can be described with reference to the method embodiment.
As shown in fig. 7, the system may include: a core network device 71 according to any embodiment of the present invention and a terminal 72 according to any embodiment of the present invention. The core network device 71 is configured to send an NAS message to a terminal, where the NAS message carries a remote inhibition identifier and a remote inhibition type, or carries a remote activation identifier; the terminal 72 is configured to perform remote killing according to the remote killing identifier and the remote killing type, or perform remote opening according to the remote opening identifier.
In the system for implementing remote deactivation or remote activation of the terminal in this embodiment, the core network device issues the remote activation instruction to the terminal through the NAS message, thereby implementing remote activation of the terminal in the LTE and 3G digital trunking systems, and reducing the influence on the base station.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (7)
1. A method for implementing remote deactivation or remote activation of a terminal is characterized by comprising the following steps:
a terminal receives a non-access stratum (NAS) message sent by core network equipment, wherein the NAS message carries a remote inhibition identifier and a remote inhibition type or carries a remote activation identifier;
the terminal executes remote inhibition according to the remote inhibition identification and the remote inhibition type, or executes remote inhibition according to the remote inhibition identification;
if the remote killing or the remote opening is successfully executed, the terminal sends a command acceptance confirmation to the core network equipment; if the remote killing is executed or the remote opening fails, the terminal receives the NAS message sent again by the core network equipment;
the method further comprises the following steps:
the terminal sends a request message to the core network equipment, wherein the request message carries a state identifier indicating whether the terminal is in a temporary remote killing state;
the terminal receives a response message returned by the core network device, wherein the response message carries a remote inhibition identifier and a remote inhibition type or a remote activation identifier, and the response message is generated when the core network device determines that the actual state of the terminal is inconsistent with the stored expected state of the terminal according to the state identifier in the request message;
the terminal executes remote inhibition according to the remote inhibition identification and the remote inhibition type in the response message, or executes remote activation according to the remote activation identification in the response message, so that the actual state of the terminal is consistent with the expected state of the terminal stored by the core network equipment.
2. The method of claim 1, wherein the remote-kill type is temporary remote-kill, and the core network device is MME;
the terminal according to the remote-killing identification and the remote-killing type are executed to kill, specifically are: deleting a default bearer between the terminal and the MME; accordingly, the method can be used for solving the problems that,
the terminal executes remote opening according to the remote opening identification, and specifically comprises the following steps: and establishing a default bearer between the terminal and the MME.
3. A method for implementing remote deactivation or remote activation of a terminal is characterized by comprising the following steps:
the method comprises the steps that core network equipment sends a non-access stratum (NAS) message to a terminal, wherein the NAS message carries a remote inhibition identifier and a remote inhibition type or a remote activation identifier, so that the terminal executes remote inhibition according to the remote inhibition identifier and the remote inhibition type or executes remote activation according to the remote activation identifier;
the core network equipment starts a timer; if the command acceptance confirmation returned by the terminal is not received yet after the timing time set by the timer is up, the core network equipment sends the NAS message to the terminal again;
the method further comprises the following steps:
the core network equipment receives a request message sent by a terminal, wherein the request message carries a state identifier for indicating whether the terminal is in a temporary remote killing state or not;
the core network equipment is according to state sign in the request message is confirmed the actual condition at terminal and storage when the expectation state at terminal is inconsistent, to the response message is returned to the terminal, carry the teleblemish sign and the teleblemish type in the response message, perhaps the teleblemish sign, so that the terminal basis the teleblemish sign in the response message and the teleblemish type execution teleblemish, perhaps carry out the teleblemish according to the teleblemish sign in the response message, so that the actual condition at terminal with the core network equipment storage the expectation state at terminal is unanimous.
4. A terminal, comprising:
a command receiving unit, configured to receive a non-access stratum NAS message sent by a core network device, where the NAS message carries a remote inhibition identifier and a remote inhibition type, or carries a remote activation identifier; and, further configured to receive the NAS message sent again by the core network device if remote deactivation is performed or remote activation fails;
a command executing unit, configured to execute remote inhibition according to the remote inhibition identifier and the remote inhibition type, or execute remote activation according to the remote activation identifier;
a command confirmation unit, configured to send a command acceptance confirmation to the core network device if the remote kill is executed or the remote start is successful after the remote kill is executed according to the remote kill identifier and the remote kill type or the remote start is executed according to the remote start identifier;
the terminal further comprises:
a request sending unit, configured to send a request message to the core network device, where the request message carries a status identifier indicating whether the terminal is in a temporary remote kill state;
a response receiving unit, configured to receive a response message returned by the core network device, where the response message carries a remote inhibition identifier and a remote inhibition type, or a remote inhibition identifier, and the response message is generated when the core network device determines, according to the state identifier of the request message, that an actual state of the terminal is inconsistent with a stored expected state of the terminal;
the command execution unit is specifically configured to execute the remote kill according to the remote kill identifier and the remote kill type in the response message, or execute the remote kill according to the remote kill identifier in the response message, so that the actual state of the terminal is consistent with the expected state of the terminal stored in the core network device.
5. The terminal of claim 4, wherein the remote deactivation type is temporary remote deactivation, and the core network device is an MME;
the command execution unit is specifically configured to delete a default bearer between the terminal and the MME, or to establish a default bearer between the terminal and the MME.
6. A core network device, comprising:
a command sending unit, configured to send a non-access stratum NAS message to a terminal, where the NAS message carries a remote inhibition identifier and a remote inhibition type, or carries a remote activation identifier, so that the terminal performs remote inhibition according to the remote inhibition identifier and the remote inhibition type, or performs remote activation according to the remote activation identifier;
the timing unit is used for starting a timer after the NAS message is sent to the terminal; when the timing time set by the timer reaches but a command acceptance confirmation returned by the terminal is not received, indicating the command sending unit to send the NAS message to the terminal again;
the core network device further includes:
a request receiving unit, configured to receive a request message sent by a terminal when states of the terminal and a core network device side are inconsistent, where the request message carries a state identifier used to indicate whether the terminal is in a temporary remote extinction state;
a state comparing unit, configured to compare the actual state of the terminal determined according to the state identifier in the request message with an expected state of the terminal stored in a core network device;
response sending element, be used for when the comparison result of state comparing element is inconsistent, to the response message is returned to the terminal, carry the teleing sign and the teleing type in the response message, perhaps teleing sign, so that the terminal according to teleing sign and teleing type in the response message carry out the teleing, perhaps carry out the teleing according to the teleing sign in the response message, so that the actual state at terminal with the core network equipment storage the expectation state at terminal is unanimous.
7. The utility model provides a system for realize that terminal remote is closed or is opened, its characterized in that includes: core network apparatus according to claim 6 and a terminal according to claim 4 or 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110411581.4A CN103167479B (en) | 2011-12-12 | 2011-12-12 | Realize that terminal is distant gets killed or the distant methods, devices and systems opened |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110411581.4A CN103167479B (en) | 2011-12-12 | 2011-12-12 | Realize that terminal is distant gets killed or the distant methods, devices and systems opened |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103167479A CN103167479A (en) | 2013-06-19 |
| CN103167479B true CN103167479B (en) | 2016-04-20 |
Family
ID=48590137
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110411581.4A Active CN103167479B (en) | 2011-12-12 | 2011-12-12 | Realize that terminal is distant gets killed or the distant methods, devices and systems opened |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103167479B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105592425B (en) * | 2014-10-24 | 2019-02-22 | 北京信威通信技术股份有限公司 | The method and system of the distant distant resurrection of getting killed of swooning of colony terminal |
| CN104683432B (en) * | 2014-11-26 | 2018-12-11 | 海能达通信股份有限公司 | Activate or disable the method and system, terminal and central apparatus of colony terminal |
| WO2016082131A1 (en) * | 2014-11-26 | 2016-06-02 | 海能达通信股份有限公司 | Method and system for activating or disabling cluster terminal, terminal and central device |
| CN107135491B (en) * | 2017-05-19 | 2020-05-12 | 哈尔滨海能达科技有限公司 | Terminal control method and base station |
| CN111083806B (en) * | 2018-10-18 | 2022-03-22 | 力同科技股份有限公司 | Method and device for realizing data transmission based on DMR standard |
| CN109618360A (en) * | 2018-12-20 | 2019-04-12 | 新华三技术有限公司成都分公司 | SOT state of termination synchronous method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| CN101568113A (en) * | 2008-04-21 | 2009-10-28 | 大唐移动通信设备有限公司 | Method, device and system for realizing synchronization of loading state |
-
2011
- 2011-12-12 CN CN201110411581.4A patent/CN103167479B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| CN101568113A (en) * | 2008-04-21 | 2009-10-28 | 大唐移动通信设备有限公司 | Method, device and system for realizing synchronization of loading state |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103167479A (en) | 2013-06-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103167479B (en) | Realize that terminal is distant gets killed or the distant methods, devices and systems opened | |
| CN107371208B (en) | Switching method and device | |
| CN113228736A (en) | Pause-resume in conditional switch | |
| WO2020063666A1 (en) | User equipment and method executed thereby, base station and method executed thereby, and mobile control entity and method executed thereby | |
| US8805395B2 (en) | Implementation method for improving service call completion ratio and radio network controller | |
| EP2139280B1 (en) | A method for processing the bearing and a mobile managing device | |
| JP6482097B2 (en) | Core network device and control method of core network device | |
| WO2018126961A1 (en) | Communication method, access network device, and terminal | |
| CN105265009A (en) | Network nodes and methods | |
| US20230098825A1 (en) | Short message service ability updating method, device and apparatus | |
| EP3001702B1 (en) | Support of mobile-terminated application services in a mobile system | |
| EP3534562A1 (en) | Data transmission method, apparatus, and system, and storage medium | |
| CN110419248A (en) | Method and apparatus for the secret protection in paging user equipment | |
| CN110460961B (en) | Method and system for reporting group terminal position | |
| CN103249096A (en) | Switching processing method, equipment and system | |
| EP2611231A1 (en) | Signaling trace method and device | |
| CN103428668A (en) | Tracking area updating method and device | |
| CN108307452B (en) | Connection recovery method and device, base station and user terminal | |
| CN105530593A (en) | Method and device for state synchronization between user equipment | |
| CN102833743B (en) | Transmission, update method and the relevant device of public warning system key updating information | |
| CN114467361A (en) | Restoring radio connection in multi-radio dual connectivity | |
| EP2429255A1 (en) | Method, system and evolved node b for implementing service release | |
| CN103458499A (en) | Off-line processing method and equipment | |
| CN103108305B (en) | A kind of terminal trigger message effective time control method and system | |
| CN110545253A (en) | information processing method, device, equipment and computer readable 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 | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |