WO2008083581A1

WO2008083581A1 - The method, device and application of processing the emergency call and the callee of calling back

Info

Publication number: WO2008083581A1
Application number: PCT/CN2007/071318
Authority: WO
Inventors: Michael Roberts; Ying Huang; Mingjiang Xie
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-01-09
Filing date: 2007-12-25
Publication date: 2008-07-17
Also published as: CN101222750B; CN101222750A

Abstract

A method of processing the callee of the emergency call, which comprises receiving the paging message which indicates the emergency call from the CN; paging the callee of the emergency call and indicating the emergency call. A means of accessing control node, a method of processing the callee of the callback of the emergency call and a CN means, a method of processing the emergency call for the callee and a user side means of processing the emergency call are also provided.

Description

Method, device and application for processing emergency call and called user in callback This application claims to be submitted to Chinese Patent Office on January 9, 2007, application number is 200710000601.2, and the invention name is "handling emergency call, emergency call callback" The priority of the Chinese Patent Application, the entire disclosure of which is hereby incorporated by reference. Technical field

The present invention relates to the processing of emergency calls, and more particularly to a method of processing a called subscriber in an emergency call, a method of handling a called subscriber in an emergency call callback, and a method and apparatus for handling an emergency call by a called subscriber.

Background technique

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

In the following, the UE (User Equipment) A dials 110 police station as an example to describe the processing of the existing emergency call.

(1) UE A dials 110;

(2) After receiving the emergency call, the police station control center in the CN (Core Network) finds a specific user equipment UE B (such as a fixed telephone in an office inside the police station) according to a predetermined algorithm. A police officer's cell phone) maps the emergency call to UE B. Thereafter, the CN sends a paging message to the ENODEB (Enhanced Node B) in the LTE, and the paging message is used to instruct the ENODE B to page to the UE B. ENODEB in LTE can also be RNC in UMTS or BSC in GSM. The following is an example of ENODEB.

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

(4) After receiving the page, UE B decides whether to reject or allow the page according to its current situation.

There are several reasons why UE B refuses to page. 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) layer to be subject to In addition, UE B will reject the page received thereafter. For another example, if the system is to prohibit a certain service or certain cells, the prohibited item will be sent in the system broadcast message, and then the UE is stored, and the access level prohibits the list Access Class. The Barred list" method stores the prohibited items. Further, it rejects all the pages it receives that involve the prohibited items. Generally, all content including but not limited to the above prohibited items is co-ordinated as "special service connection". SSACB (Service Specific Access Class Barring). In summary, after receiving the paging message from ENODE B, the UE decides whether to reject the paging according to the content of the SSACB. If the page involves a forbidden item in the SASAB, the page is rejected and no subsequent access processing is performed; if the page does not involve a forbidden condition in the SSAPB, the page is allowed to continue with ENODE B. Subsequent access processing is performed to talk to the calling UE A.

(5) If UE B allows the paging, it initiates a connection request to ENODE B, and ENODE B decides whether to allow the access according to the current system resources.

The UE B can be either a called user of an emergency call or a called user of a normal call. When it is called as a normal user UE C (such as the relative of UE B), the called party is called. The processing flow is as follows:

(1) UE C dials the number of UE B

The core network CN sends a paging message to the ENODE B, and the paging message is used to indicate that the ENODE B pages to the UE B.

The subsequent processing flow and steps (3) to (5) in the emergency call are identical and are not mentioned. Comparing the processing procedure of the UE B as the called emergency call and the ordinary call, the paging message of the paging UE B sent by the CN to the ENODE B, and the subsequent access connection between the ENODE B and the UE B, etc., It is exactly the same for both. In other words, the access side ENODE B treats the called party as an emergency call and the called party of the ordinary call in the same way. Due to the existence of multiple situations in the access process, the emergency call cannot be called, for example, system overload The prohibited items in the SSACB, therefore, cannot guarantee that the called party in the emergency call has a higher call rate, and thus the caller in the emergency call cannot obtain the called assistance in time.

In addition, sometimes after the user makes an emergency call, the other party (such as the police) may be busy, so they will contact after a while. Thereafter, when the other party (police) calls again, the previous emergency caller becomes the called party, that is, the called party in the emergency call callback. For the same reason as above, the emergency call back is still not guaranteed. The called party has a higher call rate.

Summary of the invention

Embodiments of the present invention provide a method and apparatus for processing a called user in an emergency call, so as to make an emergency The called party in the call can maintain a high call rate. The embodiment of the invention further provides a method and a device for processing a called party in an emergency call back call, so that the called party in the emergency call callback can maintain a high call rate.

The embodiment of the invention discloses a method for processing a called user in an emergency call: receiving a paging message from a core network CN, the paging message indicating that the paging is an emergency call; The user is called to page and the current page is indicated as an emergency call.

The embodiment of the present invention further discloses an access control node device, including: a unit for receiving a paging message from a core network CN, where the paging message indicates that the paging is an emergency call; The called user in the emergency call performs paging and indicates that the paging is an emergency call unit.

The embodiment of the invention further discloses a method for processing a called user in an emergency call back call: recording a primary and a callee correspondence relationship of an emergency call; and identifying the said main and called correspondence according to the recorded emergency call Callback of the emergency call; in the case of recognizing the callback of the emergency call, the access control node sends a paging message to the called user who is called back to the emergency call, and indicates that the paging is an emergency call. .

The embodiment of the present invention further discloses a CN device, including: a unit for recording a primary and a callee correspondence relationship of an emergency call; and identifying the emergency according to the primary and called correspondence of the emergency call recorded above a callback unit of the call; in the case of recognizing the callback of the emergency call, sending a paging message to the called user that is called back to the emergency call by the access control node, and indicating the current paging The unit for emergency calls.

The embodiment of the invention further discloses a method for a called user to process an emergency call: receiving a paging message from an access control node; parsing the paging message; if parsing the When the page is an emergency call, an emergency access process is performed for the page.

The embodiment of the invention further discloses a user side device for processing an emergency call, comprising: a unit for receiving a paging message from an access control node; a unit for parsing the paging message; When the paging message is parsed from the paging message, the emergency access procedure is performed for the paging.

The embodiment of the invention further discloses a user side device for processing an emergency call, comprising: a receiving unit, configured to receive a paging message from the access control node; and a message parsing unit, configured to parse the content of the paging message; An access processing unit, configured to parse the page as an emergency call in a message parsing unit In this case, the SSACB is ignored to directly access the access control node.

It can be seen from the above technical solution that, in the present invention, when the paging related to the emergency call or the emergency call callback is involved, the called user can be informed that the current call is made by indicating to the called user that the paging is an emergency call. The call is an emergency call, which is handled in a different way from the non-emergency call, thereby improving the call rate of the emergency call or the emergency callback.

DRAWINGS

1 is a flow chart of a first embodiment of a method for processing a called user in an emergency call; FIG. 2 is a specific sub-flow A of step 140 shown in FIG.

3 is a flow chart of a first embodiment of a method for processing a called party in an emergency call back call according to the present invention; FIG. 4 is a specific sub-flow C of step 330 shown in FIG.

FIG. 5 is a flowchart of a second embodiment of a method for processing a called user in an emergency call according to the present invention; FIG. 6 is a flowchart of a second embodiment of a method for processing a called user in an emergency call back call according to the present invention; The third embodiment of the method for the called party in the emergency call; FIG. 8 is a schematic structural diagram of the user side device for processing an emergency call according to the present invention.

detailed description

The embodiments of the present invention will be further described below in conjunction with the accompanying drawings.

Please refer to FIG. 1, which is a flow chart of a first embodiment of a 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 to the paging cause in the paging message; add an indication to the broadcast message to indicate whether the system allows the MT EC. (Mobile Terminating Emergency Call, the called user in the emergency call) ignores the Service Specific Access Class Barring (SSACB). For the convenience of the following description, the indication is called the emergency permission indication. The CM (Connection Management) layer on the side adds a variable "ignoring SSACB", which is set according to the emergency permission indication in the aforementioned broadcast message, thereby indicating whether the MT EC can ignore the SSAPB.

Step 110: The ENODEB (Enhanced Node B) in the LTE system sends a system broadcast message to the UE, and the system broadcast message adds an indication, that is, the foregoing emergency permission indication. It should be noted that the ENODEB described in the embodiments of the present invention may also be an RNC (other than the wireless network control). In other words, the access control node described in the technical solution of the present invention includes but is not limited to the ENODEB in the LTE system and the RNC in the UMTS system, and may also be, for example, a BSC in the GSM system.

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

If the emergency indication indicates that the system allows the MT EC to ignore the SSAPB, then the UE sets the CM layer variable " ignore SSACB" to "MT EC ignores SSAPB", otherwise sets the variable to "MT EC normal for SSACB" .

Step 130: Cn (Core Network) receives an emergency call from UE 2, which finds an idle call according to some algorithms, and maps to the phone, that is, MT EC UE 1, and then, the emergency call. The calling subscriber is UE 2 and the called subscriber is UE 1. Then, the paging message is sent to UE1 through ENODEB. The value of the paging cause in the paging message is "emergency".

Step 140: After receiving the paging message, UE1 performs subsequent processing according to the variable "ignorance SSACB" and the parking cause value. For the specific process of this step, please refer to sub-process A shown in Figure 2.

Sub-step S141: The CM layer checks if the variable " ignore SSACB" is equal to "MT EC ignores

SSACB" ₀ if yes, step S142 is performed; if no, sub-step S144 is performed.

Sub-step S142: It is checked whether the parking cause value is equal to "emergency", and if so, step S143 is performed; if not, step S144 is performed.

Sub-step S143: The MT EC ignores the SSACB, directly accesses, and gives the access access class ASC (Access service classes) (^ port ASC=0), which gives it a higher priority. Specifically, the MT EC copies the paging cause (emergency) into the access reason and sends an access request message containing the access reason to ENODE B. Thereafter, sub-step S145 is performed. It should be noted that the ASC may not be set to 0 first. After the ENODEB allows the MT EC to access, the ENODEB may be notified that the access is an emergency call, and the ENODEB will give the access higher in terms of allocating resources. Priority.

Sub-step S144: The MT EC performs SSACB as usual, and performs the same processing as the existing called user access, and no longer compliments. Thereafter, sub-step S145 is performed.

Sub-step S145: ENODE B determines if the system allows access. This step exists only in certain special cases. For example, ENODE B does not allow access regardless of the reason for the access. If the system allows If access is enabled, then sub-step 146 is performed; if access is not allowed, the access procedure is terminated.

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

Sub-step S147: ENODE B gives priority access to the MT EC. If a 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 a PLMN reselection to select another PLMN. For the EC, the network side considers all PLMNs to be "normal" and not limited.

Sub-step S148: ENODEB is processed according to the existing conventional access procedure, and will not be described again. Referring to FIG. 3, it is a flowchart of a first embodiment of a method for processing a called user in an emergency call back call according to the present invention. The first embodiment of the method for processing a called user in an emergency call in the foregoing embodiment is related to paging. The called user process of an emergency call (emergency call or its callback) has a similar technical solution.

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

Step 320: The UE 2 in the system receives the above system broadcast message, and sets the variable " ignore SSACB" according to the emergency permission indication in the system broadcast message.

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

Step 330: Cn processes the emergency call from UE2 and the callback of the emergency call. The specific process is shown in sub-process C shown in Figure 4.

Sub-step S331: After receiving the emergency call from UE2, Cn performs telephone mapping according to some algorithms. Specifically, if an idle telephone MT EC UE 1 is found, it is directly paged. If the found MT EC UE 1 is not idle at this time, the CN gives the called telephone UE 1 a special tone or short message, and the called party decides whether to cut off the current call and then connects to the emergency call. If the called party decides to cut off the current call, it will directly cut to the emergency call; if the called party decides not to cut off the current call, the called party decides whether to callback later. Thereafter, sub-step S332 is performed.

Sub-step S332: CN records the correspondence between the calling party and the called party of the emergency call (such as the information table) Form). For example, the calling user who recorded the emergency call is UE2, and the called user is UE1. There are various implementations of specific correspondences, such as the corresponding manner of using IMSI or EMSI, and the like. If there is a SIM (Subscriber Identity Module) card, the corresponding relationship between the calling party and the called party can be made through the IMSI (User Identity). If there is no SIM card, the EMSI (Device Identity) or other device identification number can be used. In addition, a mark may be made for the correspondence, such as "emergency SSACB", to indicate that the correspondence belongs to the primary and called correspondence of the emergency call. At the same time, a timer is set for the primary and called correspondence records of the emergency call, and the timer is started. In order to distinguish it from other timers in the system, it is called "emergency call callback timer 1". You can set the effective time of the timer 1, such as 30 minutes. If the "emergency call callback timer 1" exceeds the preset valid time, the CN deletes the correspondence record. In addition, the CN may also send a message to the calling UE2 of the original emergency call through the ENODEB, and notify the UE2 to also start a timer. For the sake of consistency, it may be referred to as an "emergency call callback timer 2", the UE2 The "Emergency Call Callback Timer 2" on the side is synchronized with the "Emergency Call Callback Timer 1", and the values set by both are the same. Of course, the value of the above two timers may be agreed by the user side and the CN side in advance, and the "emergency call callback timer 2" is started when the UE2 initiates an emergency call, or is triggered by another specific message. .

Sub-step S333: When the "emergency call callback timer 1" has not timed out, the CN finds a special number (such as a police station) to initiate a call, and then the CN goes to the sub-step S332 to record the marked "emergency SSACB". The relationship between the master and the called.

Sub-step S334: The CN determines whether the current call is a callback of the previous emergency call according to the recorded primary and called correspondence of the emergency call. If yes, sub-step S335 is performed; if no, sub-step S336 is performed. For example, assuming that the call of the special number is from the UE1 call and the object of the call is UE2, then according to the record of the emergency call in sub-step S336: the calling user of the emergency call is UE2, and the called user is UE1, It can be determined that the call is a callback of the emergency call initiated by the UE2, that is, the caller in the callback of the previously recorded emergency call is UE1, and the called user is UE2.

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

Sub-step S336: The CN sends a paging message to the UE through the ENODEB. The value of the paging cause in the paging message is "unknown" or "terminating call" or "other non-emergency". In other words, the callback for a non-emergency call is handled according to the existing normal call, and the specific process is no longer praised. Step 340: After receiving the paging message, UE2 performs subsequent processing according to the variable "ignorance SSACB" and the paging cause value. The specific process of this step is the same as steps 130 and 140 in the foregoing embodiment, that is, UE2 can ignore the SSAPB, directly access, and give the access the highest access service level. Thereby ensuring that the called user in the emergency call back call can maintain a high call rate. In addition, in order to successfully complete the callback of the emergency call, within the "emergency call callback timer 2" time range, the UE can select 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, the paging cause is detected when the paging is received, and the paging is accepted as long as the value is "emergency"; Otherwise reject the page. If the timer expires, the selection and residency of PLMN and CELL are performed according to the normal flow.

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

Step 500: Whether ENODEB/RNC allows the called party (MT EC) of the emergency call to ignore the SSACB, which can be set by preset parameters such as O&M (operation and management) or global variables. Then the LTE ENODEB (the RNC of the UMTS system) sets this variable "emergency SSACB". If the MT EC is required to ignore SSACB, set the variable to "MT EC ignore SSACB", otherwise set to "normal processing SSACB"

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

Step 520: Enodeb receives the paging message and checks the variable "emergency SSACB". If the variable value is "MT EC ignores SSAPB", the paging sent to UE1 carries the paging cause value of "emergency". No Bay ¹ J , the median value of the paging cause is set to "unknown" or "other non-emergency".

Step 530: After receiving the paging message, UE1 checks the paging cause, if yes

"emergency", ignore SSACB and access directly. Otherwise, the normal access process is performed. The specific process of this step is the same as the sub-steps S142 to S148 in the first embodiment of the method for processing the called user in the emergency call, and therefore will not be described again.

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

Step 600: Whether ENODEB/RNC allows the called party (MT EC) of the emergency call to ignore the SSACB, which can be set by preset parameters such as O&M or global variables. Then the LTE ENODEB (the RNC of the UMTS system) sets this variable "emergency SSACB". If the MT EC is required to ignore SSACB, set the variable to "MT EC ignore SSACB", otherwise set to "normal processing SSACB".

Step 610: The CN processes the emergency call from UE2, and the emergency call back from UE1. If a callback of an emergency call, the paging cause value to a paging message sent by the ENODE is "emergency", no shellfish ¹ J paging cause value is "unknown" or "Terminating call" or "other non-emergency" and so on. The specific process of this step is the same as the specific process of the foregoing step 330. For details, refer to the sub-flow C shown in FIG. 4, and details are not described herein again.

Step 620: Enodeb receives the paging message and checks the variable "emergency SSACB". If the variable value is "MT EC ignores SSAPB", the paging sent to UE2 carries the paging cause value "emergency". No Bay ¹ J , the median value of the paging cause is set to "unknown" or "terminating call," or "other non-emergency." Those skilled in the art can see that the purpose of ENODEB setting preset parameters such as "emergency SSACB" is to determine Whether it is necessary to indicate to UE2 that the current call is an emergency call (ie, whether the paging cause value is set to emergency) is essentially to determine whether the system allows UE2 to be called as an emergency call, and performs corresponding emergency processing.

Step 630: The UE2 performs subsequent processing according to whether the received paging message indicates that the emergency call is an emergency call. The processing of this step is the same as the step 530 in the foregoing embodiment, that is, after receiving the paging message, the paging cause is checked, and if it is "emergency", the SSAPB is ignored and the access is directly performed. Otherwise, the normal access process is performed. In addition, in order to successfully complete the callback of the emergency call (CALLBACK), the UE2 is in the "emergency call callback timer 2" activated according to the CN side indication (sub-step S332 also provides other conditions in which the timer 2 is started, this is UE2 can select any PLMN and camp on any cell within the time range of which is no longer mentioned. If the PLMN is restricted in the PLMN list of UE 2, or the cell is restricted in the CELL list, the paging cause is detected when the paging is received, and the paging is accepted as long as the value is "emergency"; otherwise refuse this page. If the timer expires, the selection and residency of PLMN and CELL are performed according to the normal flow. Two embodiments of a method for processing a called subscriber in an emergency call by the foregoing disclosed invention, and a method for processing a called subscriber in an emergency call callback can be summarized. ENODEB can notify the user of the Whether the SSACB operation is performed when the emergency call is called, or the ENODEB controls itself by the global variable, and indicates whether the page is an emergency call to the called user in the emergency call. The purpose of the operation is that the system can control the emergency call. Whether the called party in the called or emergency call back call is allowed to ignore the SSAPB, when the system does not allow the called party involved in the emergency call to ignore the SSACB, it is exactly the same as the existing normal call. Those skilled in the art should be aware that the system may also default that the called party in the emergency call or the called party in the emergency call back call must perform the ignore SSACB operation. In this case, ENODEB does not need to notify the user through the broadcast message that it is an emergency call. Whether the SSACB operation is ignored when the called party is performed, and it is not necessary for ENODEB to decide whether to call the called user in the emergency call (or callback) as the emergency call. Specifically, the "ignorance SSACB" variable is not required to be set in the UE. As long as the paging message sent by the ENODEB indicates that the call is an emergency call, the UE performs the ignore SSACB operation, and the SSACB is normally processed. Similarly, it is not necessary. Setting the "emergency SSACB" variable in ENODEB, as long as the CN sends a message to ENODEB indicating that the call is an emergency call, then ENODEB also indicates that the call is an emergency call when paging to the UE. This processing situation is simpler than the foregoing embodiments. Referring to FIG. 7, it is a flowchart of a third embodiment of a method for processing a called user in an emergency call according to the present invention.

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

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

Emergency".

Step 730: After receiving the paging message, the UE checks the paging cause. If it is "emergency", the SSACB is ignored and the access is directly performed. Otherwise, the normal access process is performed. The specific process of this step is the same as the sub-steps S142 to S148 in the first embodiment of the method for processing the called user in the emergency call, and therefore is not mentioned here. It can be seen from the above embodiment that the called UE can notify the access reason as an emergency call during the access process to the ENODEB, whether the emergency call or the call back of the emergency call, so that the ENODEB preferentially accesses the UE. Processing, such as preferential allocation of access resources, and the like. A person skilled in the art can understand that if, on the one hand, the UE ignores the SSACB to directly access the ENODEB (that is, access in a conventional manner), on the other hand, the UE notifies the ENODEB access reason that it is an emergency call, so that the ENODEB can be the UE. For priority access processing, the call rate for emergency calls or emergency call recalls can be very high. However, if only one of the above two technical means is adopted, the call rate of the emergency call or the emergency call callback can be improved to some extent as compared with the prior art.

For example, after ENODEB indicates to the UE that the call is an emergency call, the UE performs the SSACB operation (ie, the UE accesses according to the existing conventional manner) before accessing to the ENODEB, but notifies the ENODEB access reason that it is an emergency call.

In the above technical solution, although the UE does not ignore the SSAPB, since the ENODEB can perform the priority access processing for the UE according to the access reason (emergency call) notified by the called UE in the emergency call or the emergency call callback, Compared with the existing ENODEB for treating all kinds of accesses equally, the probability of successful access of the UE is improved, thereby improving the call rate of the emergency call or the emergency call callback.

Based on the same inventive concept as the foregoing method for processing a called user in an emergency call, the embodiment of the present invention further discloses a user side device for processing an emergency call, and the device can be set in various user equipments, such as fixed. Telephone, mobile phone, etc. Please refer to FIG. 8. FIG. 8 is a schematic structural diagram of an embodiment of a user side device according to the present invention. Meanwhile, in order to more clearly describe the device of the embodiment, an access control node that directly communicates with the device is also shown. Similarly, the access control node in this embodiment includes, but is not limited to, ENODEB in the LTE system, RNC in the UMTS system, and BSC in the GSM system. The internal structure of the device will be further revealed below in conjunction with the working principle of the device. Of course, many of the same or corresponding technical features have been disclosed in the foregoing plurality of method embodiments, and therefore, only the following is briefly described.

First, the receiving unit 81 receives the paging message from the access control node, and then the message parsing unit 82 parses the paging cause or the emergency call indication in the paging message from the paging message, the paging reason or seeking The emergency call indication in the call message may be an emergency call or a non-emergency call. The specific content of the paging message is described in detail in the foregoing, and therefore will not be described here.

After the message parsing unit 82 parses the paging cause or the emergency call indication in the paging message, it passes to the access processing unit 83 for subsequent processing. Specifically, the access processing unit 83 includes an emergency access processing sub-unit 831 and a normal access processing sub-unit 832. If the paging reason parsed by the message parsing unit 82 or the emergency call indication in the paging message is not an emergency If the call is normal, the normal access processing sub-unit 832 performs the normal access; if the paging cause parsed by the message parsing unit 82 or the emergency call indication in the paging message is an emergency call, the emergency access processing is performed. The subunit 831 ignores the SSAPB and directly accesses the access control node. The emergency access processing sub-unit 831 further includes an access reason processing module and an access request processing module, wherein the emergency call that is the cause of the paging is copied to the access reason by the access reason processing module or Setting an access reason according to the emergency call indication in the paging message, and then sending, by the access request processing module, an access request including an access reason as an emergency call to the access control node, where the access reason is urgent The call serves as the basis for the access control node to give the highest priority to the access request. In other words, the access control node gives the highest access service level for the access request for the emergency call, and gives the highest priority to the access, so that the call back of the emergency call or emergency call can be called as much as possible. .

Further, a control subunit may be further disposed in the access processing unit 83, and the control subunit controls whether the emergency access processing subunit is disabled, for example, by a global variable, and the value of the global variable may systematically broadcast a message. The emergency permission indication in the setting is made (see the previous section for details of this section). If the emergency access processing sub-unit 831 is disabled (if the system does not allow the called user to ignore the SSACB), the paging cause resolved in the message parsing unit 82 or the emergency call in the paging message is indicated as an emergency call. The control sub-unit controls the normal access processing sub-unit 832 to perform the processing instead of the emergency access processing sub-unit 831. In other words, in this case, the paging information sent by the access control node indicates this time. The call is an emergency call, but the user side still handles as a normal page. If the emergency access processing sub-unit 831 is not disabled, if the paging cause parsed by the message parsing unit 82 or the emergency call in the paging message is indicated as an emergency call, the emergency access processing sub-unit is still 831 performs subsequent access processing.

It can be seen from the foregoing specific embodiments that, in the technical solution of the present invention, the called party is indicated as an emergency call to the called party in the emergency call or the emergency call callback, and the called user ignores the SSAPB directly. The operation of accessing, so that the called user is no longer restricted by SCASB, It has a higher priority, thus increasing the call rate of the page involving the emergency call, so that the trapped user can get help in the first time.

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

The above detailed description of a method for processing a called user in an emergency call, a method for processing a called user in an emergency call callback, and a method for a called user to handle an emergency call are provided for assistance in understanding. The method of the present invention and its core idea; at the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and the scope of application. It is understood to be a limitation of the invention.

Claims

Rights request

A method for processing a called user in an emergency call, characterized in that:

Receiving a paging message from the core network CN, the paging message indicating that the paging is an emergency call;

Paging the called user in the emergency call and indicating that the current page is an emergency call.

2. The method according to claim 1, wherein: before paging to the called user in the emergency call, and indicating that the paging is an emergency call, the method further includes:

It is determined according to the preset parameters that the called user in the emergency call is allowed to perform emergency processing.

3. The method according to claim 1, wherein after paging to the called user in the emergency call and indicating that the paging is an emergency call, the method further includes:

The called user ignores the special service access level and prohibits the SSACB operation, and directly accesses the access control node.

The method of claim 3, wherein before the called user ignores the SSACB and directly accesses the access control node, the method further includes:

The called user determines, based on the broadcast message from the access control node, that the called user in the emergency call is allowed to perform the ignore SSACB operation.

The method according to claim 1, wherein after paging to the called user in the emergency call and indicating that the paging is an emergency call, the method further includes:

The called user accesses the access control node in a conventional manner.

The method according to any one of claims 1 to 5, characterized in that, after paging to the called user in the emergency call, and indicating that the paging is an emergency call, the method further comprises:

Receiving an access reason notification from the called user, where the access reason notification indicates that the reason for the current access is an emergency call;

Perform priority access processing for the called user.

7. An access control node device, comprising:

Means for receiving a paging message from the CN, the paging message indicating that the paging is an emergency call;

A unit for paging to a called user in the emergency call and indicating that the current paging is an emergency call.

8. The device according to claim 7, further comprising:

Means for receiving an access reason notification from the called user, where the access reason notification indicates that the reason for the current access is an emergency call;

A unit for performing priority access processing for the called user.

9. A method for handling a called user in an emergency call callback, characterized in that:

Record the relationship between the primary and the called of the emergency call;

Identifying the callback of the emergency call according to the primary and called correspondence of the emergency call recorded above;

In the case of recognizing the callback of the emergency call, the access control node sends a paging message to the called user who is called back to the emergency call, and indicates that the current paging is an emergency call.

10. The method of claim 9, further comprising:

The emergency call timer is started while the emergency call master and the called relationship are recorded.

The method according to claim 9, wherein after the paging is performed by the access control node to the called user in the emergency call, and the current paging is indicated as an emergency call, the method further includes:

The called user ignores the SSACB and directly accesses the access control node.

The method according to claim 11, wherein before the called user ignores the SSACB and directly accesses the access control node, the method further includes:

The called user determines, based on the broadcast message from the access control node, that the called user in the emergency call back call is allowed to perform the ignore SSACB operation.

13. The method according to claim 9, wherein: before the paging of the called party that is called back to the emergency call by the access control node, and indicating that the paging is an emergency call, the method further includes: The access control node determines, according to the preset parameters, that the called user in the emergency call callback is allowed to ignore the SSAPB operation.

The called user accesses the access control node in a conventional manner.

The method according to any one of claims 9 to 14, characterized in that After the control node pages the called user in the emergency call, and indicates that the paging is an emergency call, the method further includes:

The access control node receives an access reason notification from the called user, and the access reason notification indicates that the reason for the current access is an emergency call;

The access control node performs priority access processing for the called user.

16. A CN device, comprising:

a unit for recording the relationship between the primary and the called of the emergency call;

Means for identifying a callback of the emergency call according to the primary and called correspondence of the emergency call recorded above;

For the case of the callback that identifies the emergency call, the access control node sends a paging message to the called user that is called back to the emergency call, and indicates that the current paging is a unit of the emergency call.

17. A method for a called user to process an emergency call, characterized in that:

Receiving a paging message from an access control node;

Parsing the paging message;

If the page is parsed from the paging message as an emergency call, an emergency access procedure is performed for the page.

The method according to claim 17, wherein the performing the emergency access processing for the paging comprises:

Ignore SSACB and directly access the access control node.

Access is made to the access control node in a conventional manner.

The method according to claim 18 or 19, wherein the performing the emergency access processing for the paging further comprises:

The access control node is notified that the access reason is an emergency call.

A user side device for processing an emergency call, comprising:

a unit for receiving a paging message from an access control node;

a unit for parsing the paging message;

And configured to: when the paging is parsed from the paging message, the paging is an emergency call, Call the unit for emergency access processing.

The user side device according to claim 21, wherein the means for performing emergency access processing for the paging comprises:

Sub-unit for ignoring SSACB access directly to the access control node.

A subunit for accessing the access control node in a conventional manner.

The user side device according to claim 21 or 22, wherein the means for performing emergency access processing for the paging further comprises:

A unit for notifying the access control node that the access reason is an emergency call.

25. A user side device for processing an emergency call, 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;

The access processing unit is configured to: when the message parsing unit parses the page as an emergency call, ignore the SSACB to directly access the access control node.

The device of claim 25, wherein the access processing unit comprises an emergency access processing subunit and a normal access processing subunit, wherein

The emergency access processing sub-unit is configured to ignore the SSACB to directly access the access control node if the message parsing unit parses the paging as an emergency call;

The normal access processing sub-unit is configured to perform normal access processing by performing SSACB normally when the message parsing unit parses out that the paging is a non-emergency call.

The apparatus according to claim 26, wherein the emergency access processing sub-unit specifically includes:

An access reason processing module, configured to indicate an emergency call in the access reason;

The access request processing module is configured to send, to the access control node, an access request that includes an access reason as an emergency call.