CN101222750B - Method for processing urgent call and called subscriber in urgent call call-back and its application - Google Patents

Abstract

The invention discloses a method for processing a called user in an emergency call. An access control node receives a paging message from a core network CN, and the paging message indicates that this paging is an emergency call; The called user in the emergency call performs paging, and indicates that the paging is an emergency call; the called user in the emergency call ignores the SSACB, and directly accesses the access control node. The invention also discloses a method for processing the called user in the emergency call back, a method for the called user to process the emergency call, and a user side device for processing the emergency call. Through the technical solution mentioned in the present invention, the call pass rate related to emergency calls is improved.

Description

Method for handling emergency call and called user in emergency call callback and its application

technical field

The present invention relates to a method for processing an emergency call, in particular to a method for processing a called user in an emergency call, a method for processing a called user in an emergency call back, and a method for the called user to process an emergency call.

Background technique

In the existing communication system, the calling user can also dial 110, 119 and other emergency numbers when certain services or places are limited, so as to ensure that the user can send emergency help information to the outside world at the first time.

The following takes UE (User Equipment, user equipment) A's call to 110 police station as an example to introduce the processing process of the existing emergency call.

(1) UE A dials 110;

(2) After the police control center in the CN (Core Network, core network) receives the emergency call, it finds a specific user equipment UE B under it according to a predetermined algorithm (such as a fixed telephone in an office inside the police station or a certain policeman's mobile phone), map the emergency call to UE B. Thereafter, the CN sends a paging (paging) message to the ENODE B (enhanced Node B) in LTE, and the paging message is used to instruct the ENODE B to perform paging to the UE B.

(3) ENODE B then sends a paging message to UE B;

(4) After UE B receives the paging, it decides whether to reject or allow the paging according to its current situation.

There are many reasons for UE B to reject paging. For example, when the system is overloaded, in order to limit the paging response, the UE sets the variable "Paging Response to CS Services Restriction" at the MM (Mobility Management, mobility management) layer to be restricted. , and then, UE B will reject the paging received thereafter. For another example, if the system wants to ban a certain service or certain cells, it will send the prohibited items in the system broadcast message, and then the UE will store them, and the "Access Class Barred list" method will be used Prohibited items are stored. In turn, rejecting all pages it receives relating to said prohibited item. Generally speaking, all content including but not limited to the above prohibited items is coordinated as "Special Service Access Class Barring (SSACB, Service Specific Access Class Barring). In a word, after the UE receives the paging message from ENODE B, it will according to SSACB The content decides whether to reject the paging. If the paging involves the prohibited items in SSACB, then reject the paging and do not perform subsequent access processing; if the paging does not involve the prohibited items in SSACB, allow For this paging, continue to perform subsequent access processing with ENODE B in order to talk to the calling UE A.

(5) If UE B allows this paging, it will initiate a connection request to ENODE B, and then ENODE B will decide whether to allow this access according to the current system resource situation.

UE B can be both the called user of an emergency call and the called user of an ordinary call. When UE B is called as an ordinary user UE C (such as a relative of UE B) to call UE B, The processing flow is as follows:

(1) UE C dials UE B's number

(2) The core network CN sends a paging (paging) message to the ENODE B, and the paging message is used to instruct the ENODE B to perform paging to the UE B.

The subsequent processing flow is exactly the same as steps (3) to (5) in the emergency call, and will not be repeated here.

Comparing the above-mentioned emergency call and ordinary call processing flow where UE B is also called, it can be seen that the paging message sent by CN to ENODE B to page UE B, and the subsequent access connection between ENODE B and UE B, etc. Both are exactly the same. In other words, the ENODEB on the access side treats the called party as an emergency call and the called party as an ordinary call in the same way, because there are many possible situations in the access process that make the emergency call unreachable, such as system overload, etc. involving SSACB Therefore, it is impossible to guarantee that the called party in the emergency call has a higher call pass rate, and then the calling party in the emergency call cannot obtain the called rescue in time.

In addition, sometimes after the user dials an emergency call, the other party (such as the police) may be busy, so he will contact you after a while. Afterwards, when the other party (the police) calls again, the calling party of the previous emergency call becomes the called party, that is, the called party in the emergency call back call. For the same reason as above, there is still no guarantee that the caller in the emergency call back call will be called. of called parties have a high call completion rate.

Contents of the invention

The problem to be solved by the embodiments of the present invention is to provide a method for handling called users in an emergency call, so that the called users in the emergency call can maintain a high call success rate. The purpose of the present invention is also to provide a method for processing the called party in the emergency call back, so that the called party in the emergency call back can maintain a high call success rate.

In order to solve the above technical problems, the purpose of the embodiments of the present invention is achieved through the following technical solutions:

A method for processing a called user in an emergency call, the method comprising: an access control node receiving a paging message from a core network CN, the paging message indicating that this paging is an emergency call; the access control node sending The called user in the emergency call performs paging, and indicates that the paging is an emergency call; the called user in the emergency call ignores the special service access level and prohibits SSACB, and directly accesses the access control node .

A method for processing a called user in an emergency call back, the method comprising: the CN records the corresponding relationship between the calling party and the called party of the emergency call; The callback of the emergency call; in the case of recognizing the callback of the emergency call, send a paging message to the called user of the emergency call callback through the access control node, and indicate that this paging is Emergency call: The called user in the emergency call callback ignores the SSACB and directly accesses the access control node.

A method for a called user to process an emergency call, the method comprising: the called user receives a paging message indicating an emergency call from an access control node; the called user ignores SSACB and directly connects to the access control node enter.

A user-side device for processing emergency calls, the device comprising: a receiving unit, configured to receive a paging message from an access control node; a message parsing unit, configured to parse the content of the paging message; an access processing unit , for ignoring the SSACB and directly accessing the access control node when the message parsing unit parses out that the paging is an emergency call.

It can be seen from the above technical solutions that in the present invention, when it comes to the paging of an emergency call or an emergency call back, by indicating to the called user that the call is an emergency call, the called user can ignore the SSACB and directly answer the call. input, thereby improving the call success rate of emergency calls or emergency callbacks.

Description of drawings

Fig. 1 is the flow chart of the first embodiment of the method for handling the called user in the emergency call in the present invention;

Fig. 2 is the concrete sub-flow A of step 140 shown in Fig. 1;

Fig. 3 is the flow chart of the first embodiment of the method for processing the called user in the emergency call callback according to the present invention;

FIG. 4 is a specific subflow C of step 330 shown in FIG. 3;

Fig. 5 is the flow chart of the second embodiment of the method for processing the called user in the emergency call according to the present invention;

Fig. 6 is the flow chart of the second embodiment of the method for processing the called user in the emergency call callback according to the present invention;

Fig. 7 is the flow chart of the third embodiment of the method for processing the called user in the emergency call according to the present invention;

FIG. 8 is a schematic structural diagram of a user-side device for processing an emergency call according to the present invention.

Detailed ways

Various embodiments of the present invention will be described in more detail below with reference to the accompanying drawings.

Please refer to FIG. 1 , which is a flow chart of the first embodiment of the method for processing a called user in an emergency call according to the present invention.

The main idea of this embodiment is to add a value emergency for the paging cause in the paging (paging) message; add an indication indication in the broadcast message to indicate whether the system allows MT EC to ignore SSACB (Service Specific Access Class Barring, special service access level prohibition), for the convenience of the following description, this indication is called an emergency permission indication; a variable "ignoreSSACB (ignore SSACB)" is added to the CM (Connection Management) layer on the UE (User Equipment) side, according to The emergency permission indication in the aforementioned broadcast message sets this variable, and then indicates whether MT EC (Mobile Terminating Emergency Call, the called user in the emergency call) can ignore SSACB.

Step 110: ENODEB (Enhanced Node B) in the LTE system sends a system broadcast message to the UE, and an indication is added to the system broadcast message, that is, the aforementioned emergency permission indication. It should be noted that the ENODEB described in each embodiment of the present invention can also be other access control nodes such as RNC (Radio Network Control). In other words, the access control nodes described in the technical solution of the present invention include but are not limited to The ENODEB in the LTE system and the RNC in the UMTS system may also be, for example, the BSC in the GSM system.

Step 120: UE1 in the system receives the above-mentioned system broadcast message, and sets a variable "ignore (ignore) SSACB" according to the emergency permission indication in the system broadcast message.

If the emergency permission indication indicates that the system allows the MT EC to ignore SSACB, then the UE sets the CM layer variable "ignoreSSACB" to "MT EC ignores SSACB", otherwise sets the variable to "MT EC performs SSACB normally".

Step 130: Cn (Core Network, core network) receives an emergency call from UE2, it finds an idle phone according to certain algorithms, maps to this phone, that is, on MT EC UE1, and then, the master of this emergency call The calling user is UE2, and the called user is UE1. Then, send a paging message to UE1 through ENODEB. The paging cause value in the paging message is "emergency (emergency)".

Step 140: UE1 performs subsequent processing according to the variable "ignore SSACB" and the value of pagingcause after receiving the paging message. For the specific process of this step, please refer to sub-process A shown in FIG. 2 .

Sub-step S141: The CM layer checks whether the variable "ignore SSACB" is equal to "MT EC ignores SSACB". If yes, execute step S142; if no, execute sub-step S144.

Sub-step S142: Check whether the value of paging cause is equal to "emergency". If yes, execute step S143; if no, execute step S144.

Sub-step S143: MT EC ignores SSACB and directly accesses. Specifically, MT EC copies the pagingcause (emergency) into the access reason, and sends an access request message including the access reason to ENODE B. Thereafter, sub-step S145 is executed. It should be noted that it is also possible not to send the access reason when the access request is made. After ENODEB allows MT EC to access, it can notify ENODEB that the reason for this access is an emergency call, and then ENODEB will give this access in terms of allocating resources, etc. higher priority.

Sub-step S144: MT EC executes SSACB as usual, and performs the same processing as the existing called user access, so no more details are given. Thereafter, sub-step S145 is executed.

Sub-step S145: ENODE B judges whether the system allows access. This step only exists in some special cases, for example, ENODE B does not allow access no matter what the access reason is. If the system allows access, execute sub-step 146; if not allow access, end the access process.

Sub-step S146: ENODE B judges whether the access reason is "emergency". If yes, execute sub-step S147; if no, execute sub-step S148.

Sub-step S147: ENODE B gives the access request the highest access service class ASC (Accessservice classes) (such as ASC0), that is, allows it to have a higher priority for direct access. If cell reselection occurs during an emergency call, all cells within the PLMN (Public Land Mobile Network) are considered "normal" and can be reselected. If the current PLMN exceeds the coverage area, UE1 may perform PLMN reselection to select another PLMN. For EC, the network side considers that all PLMNs are "normal" and not limited.

Sub-step S148: ENODEB performs processing according to the existing conventional access procedure, and details are not repeated here.

Please refer to FIG. 3 , which is a flow chart of the first embodiment of the method for processing the called user in the emergency call callback of the present invention. This embodiment is the same as the aforementioned first embodiment of the method for processing the called user in the emergency call. The called user of the emergency call (emergency call or its callback) has a similar technical solution in the process.

Step 310: ENODEB in the LTE system sends a system broadcast message to the UE, the system broadcast message includes the aforementioned emergency permission indication, and the emergency permission indication is used to indicate whether the system allows the MTEC to ignore the SSACB.

Step 320: UE2 in the system receives the above-mentioned system broadcast message, and sets the variable "ignore SSACB" according to the emergency permission indication in the system broadcast message.

If the emergency permission indication indicates that the system allows MT EC to ignore SSACB, then UE2 sets the variable "ignoreSSACB" of the CM layer to "MT EC ignores SSACB", otherwise sets the variable to "MT EC does not ignore SSACB".

Step 330: Cn handles the emergency call from UE2 and the callback of the emergency call. For the specific process, refer to sub-process C shown in FIG. 4 .

Sub-step S331: After Cn receives the emergency call from UE2, it performs phone mapping according to some algorithms.

Specifically, if an idle phone MT EC UE1 is found, it is directly paged. If the found MT EC is not idle at this time, the CN will give the called phone UE1 a special prompt tone or short message, and the called party will decide whether to cut off the current call and switch to an emergency call. If the called party decides to cut off the current call, it will switch directly to the emergency call; if the called party decides not to cut off the current call, it is up to the called party to decide whether to call back after a while. Thereafter, sub-step S332 is executed.

Sub-step S332: CN records the corresponding relationship between the calling party and the called party of this emergency call (such as in the form of an information table). For example, the calling user recording this emergency call is UE2, and the called user is UE1. There are many ways to realize the specific correspondence relationship, for example, the way of using IMSI or EMSI, and so on. If you have a SIM (Subscriber Identity Module, Subscriber Identity) card, you can use the IMSI (Subscriber Identity) to carry out the corresponding relationship between the calling party and the called party. If you don’t have a SIM card, you can use EMSI (Equipment Identity) or other device identification numbers. In addition, a mark such as "emergencySSACB" may be added to the corresponding relationship to indicate that the corresponding relationship belongs to the corresponding relationship between the calling party and the called party of an emergency call. Simultaneously, set a timer and start the timer for the caller and called correspondence records of the emergency call, and to distinguish it from other timers in the system, it is called "emergency call callback timer 1", The effective time of the timer 1 can be set as required, such as 30 minutes. If the "emergency call callback timer 1" exceeds the preset valid time, the CN deletes the corresponding relationship record. In addition, the CN can also send a message to the calling UE2 of the original emergency call through ENODEB, informing UE2 to also start a timer. For consistency, it can be called "emergency call callback timer 2", and the UE2 "Emergency call callback timer 2" and "Emergency call callback timer 1" on the side are synchronized, and the values set for both are the same. Of course, the values of the above two timers can also be agreed upon in advance by the user side and the CN side, and the "emergency call callback timer 2" will be started when UE2 initiates an emergency call, or triggered by other specific messages. .

Sub-step S333: When the "emergency call callback timer 1" has not timed out, the CN finds that a special number (such as the police station) has initiated a call, so the CN searches for the "emergency SSACB" recorded in sub-step S332 The corresponding relationship between the calling party and the called party.

Sub-step S334: CN judges whether this call is a callback of the previous emergency call according to the recorded correspondence between the calling party and the called party of the emergency call. If yes, execute sub-step S335; if no, execute sub-step S336. For example, assuming that the call from the special number is from UE1 and the caller is UE2, then according to the record about the emergency call in substep S336: the calling user of the emergency call is UE2, and the called user is UE1. It is determined that the call is a callback of an emergency call previously initiated by UE2, that is, the calling user in the callback of the emergency call recorded above is UE1, and the called user is UE2.

Sub-step S335: CN sends a paging message, which indicates that the call is an emergency call, specifically, the value of paging cause in the paging message is "emergency".

Sub-step S336: CN sends a paging message to UE through ENODEB, and the paging cause value in the paging message is "unknown (unknown)" or "Terminating call" or "other non-emergency". In other words, the callback of non-emergency calls is handled according to the existing normal calls, and the specific process will not be repeated.

Step 340: UE2 performs subsequent processing according to the variable "ignore SSACB" and the value of pagingcause after receiving the paging message. The specific process of this step is the same as steps 130 and 140 in the foregoing embodiments, that is, UE2 can ignore the SSACB and directly access, and the ENODEB on the access side gives it the highest access service level. Therefore, it is ensured that the called user in the emergency call back can maintain a high call success rate. In addition, in order to successfully complete the CALLBACK of the emergency call, within the time range of "emergency call callback timer 2", the UE can choose any PLMN and camp on any cell. If the PLMN is restricted in the PLMN list of UE2, or the cell is restricted in the CELL list, Paging cause is detected when receiving paging, and the paging is accepted as long as the value is "emgergency"; Otherwise the paging is rejected. If the timer expires, the selection and residency of PLMN and CELL are carried out according to the normal process.

Please refer to FIG. 5 , which is a flow chart of the second embodiment of the method for processing a called user in an emergency call according to the present invention. This embodiment adopts a technical solution similar to that of the second embodiment of the method for processing a called user in an emergency call.

Step 500: whether ENODEB/RNC allows the called party (MT EC) of the emergency call to ignore SSACB, which can be set by O&M or global variables. Then ENODEB of LTE (RNC of UMTS system) sets this variable "emergency SSACB". If MT EC is required to ignore SSACB, set this variable to "MT EC ignores SSACB", otherwise set it to "normally process SSACB"

Step 510: After CN receives an emergency call (the called user of the emergency call is UE1 of the police station), it sends a paging message to ENODEB of LTE (RNC of UMTS system), wherein the value of paging cause is "emergency".

Step 520: Enodeb receives the paging message, checks the variable "emergency SSACB", if the variable value is "MT EC ignores SSACB", then the paging sent to UE1 has a paging cause value of "emergency". Otherwise, the value of paging cause is set to "unknown" or "other non-emergency".

Step 530: UE1 checks the paging cause after receiving the paging message, and if it is "emergency", ignores SSACB and directly accesses it. Otherwise, proceed with the normal access process. The specific flow of this step is the same as the sub-steps S142 to S148 in the first embodiment of the method for handling the called user in an emergency call, so it will not be described again.

Please refer to FIG. 6 , which is a flow chart of the second embodiment of the method for processing a called user in an emergency call back according to the present invention.

Step 600: whether ENODEB/RNC allows the called party (MT EC) of the emergency call to ignore SSACB, which can be set by O&M or global variables. Then ENODEB of LTE (RNC of UMTS system) sets this variable "emergency SSACB". If MT EC is required to ignore SSACB, set this variable to "MT EC ignores SSACB", otherwise set it to "normally process SSACB".

Step 610: CN handles the emergency call from UE2 and the emergency call callback from UE1. If it is a callback of an emergency call, the paging cause value in the paging message sent to ENODE is "emergency", otherwise the paging cause value is "unknown" or "Terminating call" or "other non-emergency", etc. The specific process of this step is the same as the specific process of the aforementioned step 330, see sub-process C shown in FIG. 4 for details, and will not be repeated here.

Step 620: Enodeb receives the paging message, checks the variable "emergency SSACB", if the variable value is "MT EC ignores SSACB", then the paging sent to UE2 has a paging cause value of "emergency". Otherwise, the value of paging cause is set to "unknown" or "Terminating call" or "other non-emergency".

Step 630: UE2 performs follow-up processing according to whether the received paging message indicates an emergency call. The processing of this step is the same as step 530 in the preceding embodiment, that is, after receiving the paging message, check the paging cause, if it is "emergency", ignore SSACB, and directly access. Otherwise, proceed with the normal access process. In addition, in order to successfully complete the emergency call callback (CALLBACK), UE2 starts the "emergency call callback timer 2" under the instruction of the CN side (substep S332 also provides other conditions for timer 2 startup, here Within the time range not described in detail), UE2 can choose any PLMN and camp in any cell. If the PLMN is restricted in the PLMN list of UE2, or the cell is restricted in the CELL list, the paging cause is detected when receiving the paging, as long as the value is "emgergency", the paging is accepted; Otherwise the paging is rejected. If the timer expires, the selection and residency of PLMN and CELL are carried out according to the normal process.

Through the two embodiments of the method for processing the called user in the emergency call and the two embodiments of the method for processing the called user in the emergency call callback of the present invention disclosed above, it can be concluded that ENODEB can notify the user through a broadcast message that it is Whether to ignore the SSACB operation when an emergency call is called, or whether ENODEB controls itself through global variables, and whether to indicate to the called user in the emergency call that this paging is an emergency call. The purpose of this operation is that the system can control the emergency call Whether the called party in the emergency call or the called party in the emergency call callback is allowed to ignore SSACB, when the system does not allow the called party involved in the emergency call to ignore the SSACB, the processing flow of the existing normal call is exactly the same. Those skilled in the art should be aware that the system can also default the called party in the emergency call or the called party in the emergency call back must perform the operation of ignoring SSACB. Whether to perform the ignore SSACB operation when being called does not require ENODEB to decide whether to indicate to the called user in the emergency call (or call back) that this paging is an emergency call. Specifically, there is no need to set the "ignore SSACB" variable in the UE. As long as the paging message sent by ENODEB indicates that the call is an emergency call, the UE will ignore SSACB, and otherwise process SSACB normally; similarly, there is no need Set the "emergency SSACB" variable in ENODEB, as long as the paging message sent by CN to ENODEB indicates that this call is an emergency call, then ENODEB also indicates that this call is an emergency call when paging the UE. This processing situation is simpler than the foregoing embodiments. Please refer to FIG. 7 , which is a flowchart of a third embodiment of the method for processing a called user in an emergency call according to the present invention.

Step 700: If the CN receives an emergency call, it sends a paging message to the ENODEB of LTE (the RNC of the UMTS system), wherein the paging cause value is "emergency"; otherwise, the paging cause value sent is "non-emergency".

Step 720: After receiving the paging message, the ENODEB forwards it to the UE. If the paging cause value in the paging message received by ENODEB from the CN is "emergency", the paging cause value delivered to the UE side is also "emergency"; otherwise, the paging cause value delivered to the UE side is "non-emergency".

Step 730: After receiving the paging message, the UE checks the paging cause, and if it is "emergency", ignores SSACB and directly accesses it. Otherwise, proceed with the normal access process. Since the specific processing process of this step has been introduced in detail in the aforementioned multiple embodiments, it will not be repeated here.

Based on the same inventive concept as the multiple embodiments of the aforementioned method for processing a called user in an emergency call, the embodiment of the present invention also discloses a user-side device for processing an emergency call, which can be installed in various user equipments, Such as landlines, mobile phones, etc. Please refer to FIG. 8 , which is a schematic structural diagram of an embodiment of a user-side device of the present invention. Meanwhile, in order to describe the device of this embodiment more clearly, the figure also shows an access control node directly communicating with the device. Similarly, the access control nodes in this embodiment include but are not limited to ENODEB in the LTE system, RNC in the UMTS system, and BSC in the GSM system. Combining with the working principle of the device, its internal structure will be further revealed below. Of course, since many of the same or corresponding technical features have been disclosed in the aforementioned multiple method embodiments, only a brief description will be given below.

First, the receiving unit 81 receives the paging message from the access control node, and then the message parsing unit 82 parses the paging reason or the emergency call indication in the paging message from the paging message, the paging reason or the paging message The emergency call indication in the paging message may be an emergency call or a non-emergency call. The specific content of the paging message has been described in detail above, so it will not be repeated here.

After the message parsing unit 82 parses out the paging cause or the emergency call indication in the paging message, it is handed over to the access processing unit 83 for subsequent processing. Specifically, the access processing unit 83 includes an emergency access processing subunit 831 and a normal access processing subunit 832. If the paging reason parsed out by the message parsing unit 82 or the emergency call indication in the paging message call, then the normal access processing subunit 832 normally executes SSACB to perform conventional access; if the paging reason analyzed by the message analysis unit 82 or the emergency call indication in the paging message is an emergency call, then the emergency access processing subunit 832 The subunit 831 ignores the SSACB and directly accesses the access control node. As far as the emergency access processing subunit 831 is concerned, it specifically includes an access reason processing module and an access request processing module, wherein the emergency call as the paging reason is copied to the access reason through the access reason processing module or The access reason is set according to the emergency call indication in the paging message, and then the access request processing module sends an access request to the access control node that includes the access reason as an emergency call, and the access reason in the access reason is emergency The call is used as the basis for the access control node to give the highest priority to this access request. In other words, the access control node gives the highest access service level to the access request whose access reason is an emergency call, and gives the access the highest priority, so that the emergency call or the emergency call callback can be called through as much as possible .

Further, a control subunit can also be set in the access processing unit 83, through which the emergency access processing subunit is controlled to be prohibited, for example, controlled by a global variable whose value can be broadcast by the system Set the emergency permission indication in (see the previous article for details in this part). If the emergency access processing subunit 831 is prohibited (such as the system does not allow the called user to ignore SSACB), then the paging reason parsed out by the message analysis unit 82 or the emergency call indication in the paging message is an emergency call In this case, the control subunit will control the ordinary access processing subunit 832 to replace the emergency access processing subunit 831 to perform processing. In other words, in this case, although the paging information issued by the access control node indicates that this time The call is an emergency call, but it is still treated as a normal paging call on the user side. If the emergency access processing subunit 831 is not prohibited, then in the case that the paging reason analyzed by the message analysis unit 82 or the emergency call indication in the paging message is an emergency call, the emergency access processing subunit Step 831 performs subsequent access processing. It can be seen from the above multiple specific embodiments that in the technical solution of the present invention, by indicating to the called user in the emergency call or emergency call back that this paging is an emergency call, and the called user ignores SSACB and directly proceeds The operation of access makes the called user no longer restricted by SSACB and has a higher priority, thus improving the call pass rate of paging involving emergency calls, so that the trapped user can get help at the first time .

Furthermore, since the called user involved in the emergency call accesses the access control node, it informs that the access reason is an emergency call, and furthermore, the access control node gives the access request the highest access service level, so that The access request can preferentially obtain various allocated resources, so that the called user involved in the emergency call can preferentially access the system, thereby further ensuring the success rate of the emergency call or its callback.

The third embodiment of the method for processing the called user in an emergency call according to the present invention has been introduced above. Correspondingly, the technical solution of this embodiment is also applicable to paging the called user during the emergency call callback process, and will not be repeated here. .

The method for handling emergency calls or emergency call callbacks provided by the present invention and the method for handling emergency calls provided by the present invention have been described in detail above. In this paper, specific examples are used to illustrate the principles and implementation methods of the present invention. Explain that the description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and application scope In summary, the contents of this specification should not be construed as limiting the present invention.

A method for handling the called user in an emergency call, a method for handling the called user in an emergency call back, and a method for the called user to handle an emergency call provided by the present invention have been introduced in detail above, and a specific example is used in this paper The principle of the present invention and the implementation mode have been set forth, and the description of the above examples is only used to help understand the method of the present invention and its core idea; meanwhile, for those of ordinary skill in the art, according to the thought of the present invention, in the specific implementation mode There will be changes in the scope of application and the scope of application. In summary, the content of this specification should not be construed as limiting the present invention.

Claims (14)

1. a method of processing called subscriber in urgent call, is characterized in that:

Access control node is to subscriber equipment transmitting system broadcast, described system broadcast message comprises urgent permission instruction, and whether described urgent permission instruction allows called subscriber MT EC in urgent call to ignore particular service access rank to forbid SSACB in order to indicate system; Subscriber equipment arranges variable " ignore SSACB " according to described urgent permission instruction, and whether the called subscriber that described variable " ignore SSACB " is used to indicate in urgent call can ignore SSACB;

Described method also comprises:

Access control node receives the beep-page message from core net CN, and it is urgent call that described beep-page message is indicated this paging;

Access control node carries out paging to the called subscriber in described urgent call, and to indicate this paging be urgent call;

When called subscriber in described variable " ignore SSACB " indicating emergency is called out can ignore SSACB, called subscriber in described urgent call ignores particular service access rank according to received beep-page message and forbids SSACB, directly accesses to access control node.

2. the method for claim 1, is characterized in that,

Called subscriber in described urgent call directly accesses and is specially to access control node: the called subscriber in described urgent call sends access request to access control node, and notifies this access of access control node former because urgent call;

Described method also comprises: access control node accesses former because the highest access service rank of access request of urgent call.

3. the method for claim 1, is characterized in that,

Called subscriber in described urgent call directly accesses and is specially to access control node: the called subscriber in described urgent call sends access request to access control node, and this access of notice access control node is former because urgent call after access control node allows its access;

Described method also comprises: access control node accesses former because the highest access service rank of access request of urgent call.

4. a method of processing called subscriber in urgent call call-back, is characterized in that:

Access control node is to subscriber equipment transmitting system broadcast, described system broadcast message comprises urgent permission instruction, and whether described urgent permission instruction allows called subscriber MT EC in urgent call to ignore particular service access rank to forbid SSACB in order to indicate system; Subscriber equipment arranges variable " ignore SSACB " according to described urgent permission instruction, and whether the called subscriber that described variable " ignore SSACB " is used to indicate in urgent call can ignore SSACB;

Described method also comprises:

CN records the calling and called corresponding relation of urgent call;

CN, according to the calling and called corresponding relation of the urgent call of above-mentioned record, identifies the callback of described urgent call;

In the callback situation that identifies described urgent call, the called subscriber's issuing page message by access control node to described urgent call call-back, and to indicate this paging be urgent call;

When called subscriber in described variable " ignore SSACB " indicating emergency is called out can ignore SSACB, the called subscriber in described urgent call call-back ignores SSACB, directly accesses to access control node.

5. method as claimed in claim 4, is characterized in that, described method also comprises: when CN records urgent call calling and called corresponding relation, start urgent call timer.

6. method as claimed in claim 5, is characterized in that, the calling and called corresponding relation that described CN records urgent call is specially: the calling and called corresponding relation that records urgent call by IMSI user ID, EMSI device identification or other device identification number.

7. method as claimed in claim 4, is characterized in that,

Called subscriber in described urgent call call-back directly accesses and is specially to access control node: the called subscriber in described urgent call call-back sends access request to access control node, and notifies this access of access control node former because urgent call;

Described method also comprises: access control node accesses former because the highest access service rank of access request of urgent call.

8. method as claimed in claim 4, is characterized in that,

Called subscriber in described urgent call call-back directly accesses and is specially to access control node: the called subscriber in described urgent call call-back sends access request to access control node, and this access of notice access control node is former because urgent call after access control node allows its access; Described method also comprises:

Access control node accesses former because the highest access service rank of access request of urgent call.

9. called subscriber processes a method for urgent call, it is characterized in that:

Access control node is to subscriber equipment transmitting system broadcast, described system broadcast message comprises urgent permission instruction, and whether described urgent permission instruction allows called subscriber MT EC in urgent call to ignore particular service access rank to forbid SSACB in order to indicate system; Subscriber equipment arranges variable " ignore SSACB " according to described urgent permission instruction, and whether the called subscriber that described variable " ignore SSACB " is used to indicate in urgent call can ignore SSACB;

Described method also comprises:

Called subscriber receives the beep-page message that is designated as urgent call from access control node;

When called subscriber in described variable " ignore SSACB " indicating emergency is called out can ignore SSACB, described called subscriber ignores SSACB, directly accesses to access control node.

10. method as claimed in claim 9, it is characterized in that, called subscriber in described urgent call directly accesses and is specially to access control node: the called subscriber in described urgent call sends access request to access control node, and notifies this access of access control node former because urgent call.

Process the user-side device of urgent call for 11. 1 kinds, it is characterized in that, described device comprises:

Receiving element, in order to receive the beep-page message from access control node;

Message parse unit, in order to resolve the content of described beep-page message;

Access processing unit, is urgent call in order to go out paging in message parse unit resolves, and called subscriber in variable " ignore SSACB " indicating emergency is called out is can ignore SSACB time, ignores SSACB and directly accesses to access control node.

12. install as claim 11, it is characterized in that, described access processing unit specifically comprises that subelement is processed in urgent access and subelement is processed in common access, wherein,

Subelement is processed in described urgent access, is urgent call in order to go out described paging in message parse unit resolves, and in the time that described variable " ignore SSACB " instruction called subscriber can ignore SSACB, ignores SSACB and directly access to access control node;

Subelement is processed in described common access, in order to go out described paging in message parse unit resolves be non-emergency call in the situation that, normally carries out the conventional access of SSACB and processes.

Whether 13. devices as claimed in claim 12, is characterized in that, described access processing unit also comprises control subelement, be prohibited in order to control described urgent access processing subelement;

Be prohibited if subelement is processed in described urgent access, go out described paging be urgent call in the situation that in message parse unit resolves, control common access and process subelement on behalf of processing.

14. devices as described in claim 11 or 12, is characterized in that, described emergency treatment subelement specifically comprises:

Access reason processing module, in order to be designated as urgent call in access reason;

Access request processing module, comprises the former access request because of urgent call of access in order to send to access control node, and the urgent call in described access reason gives the foundation of this access request highest priority as access control node.