WO2011035702A1

WO2011035702A1 - Call handling method, equipment and system

Info

Publication number: WO2011035702A1
Application number: PCT/CN2010/077087
Authority: WO
Inventors: 吴健
Original assignee: 华为技术有限公司
Priority date: 2009-09-23
Filing date: 2010-09-19
Publication date: 2011-03-31
Also published as: CN102026131A

Abstract

A call handling method, equipment and system are disclosed by the present invention, which relates to wireless communication technique. Said method includes: assigning context resource for the user terminal which initiates an emergency call and is attached to HNB, and allowing said UE to perform emergency call conversation; after the emergency call is finished, for the non-admission user, releasing the context resource assigned for the UE. The technical solutions provided by the embodiments of the present invention can enhance the security of admission control.

Description

Call processing method, device and system

The present application claims priority to Chinese Patent Application No. 200910190706.8, entitled "Call Processing Method, Apparatus and System", filed on September 23, 2009, the entire contents of . TECHNICAL FIELD The present invention relates to wireless communication technologies, and in particular, to a call processing method, apparatus, and system. . BACKGROUND A Home NodeB (HNB) is a home micro base station, which is mainly used to provide indoor coverage in a home, a business, or a public place. It is characterized by the adoption of the Third Generation Partnership Projects (3GPP) protocol, which supports standard Wideband Code Division Multiple Access (WCDMA) terminals and uses Internet Protocol (Internet Protocol, Referred to as IP) network backhaul, support plug and play.

HNB supports user admission control. There are currently three admission modes: Open Open, Closed Close, Hybrid Hybrid. In the Open mode, the HNB does not perform admission control. In the Close mode, the HNB allows the admitted user to initiate normal services, but rejects the non-admission user to initiate the service in the HNB. In the Hybrid mode, all users are allowed to initiate services in the HNB. , but the priority of the admitted users is higher.

At the same time, according to the Closed Subscriber Group (CSG) capabilities of the UE and the network, there are two processes for user admission: CSG admission and non-CSG admission. When the UE and the network support CSG, CSG admission is adopted, otherwise, non-CSG admission is adopted. The CSG admission is carried out on the core network, and the non-CSG admission is carried out on the access network.

Currently, 3GPP is developing HNB related protocols. In terms of emergency call security, the Close mode CSG cell is only directed to the user to open the service, but allows the non-access user to make an emergency call.

In the process of implementing the present invention, the inventor of the present invention finds that the current CSG cell emergency call has the following problems: After the non-admission user initiates an emergency call, the normal service can be performed. SUMMARY OF THE INVENTION The main technical problem to be solved by embodiments of the present invention is to provide a call processing method, device, and system, which can improve the security of admission control.

In order to solve the above technical problem, an embodiment of the present invention provides a call processing method, including: allocating a context resource to a user terminal UE that initiates an emergency call under the HNB, allowing the UE to make an emergency call call; Admit the user, release the context resource allocated for the UE.

An embodiment of the present invention provides another method for processing a call, including: determining whether a call initiated by a user equipment UE under a home base station HNB is an emergency call, and determining whether the UE is a non-access user, wherein, due to the UE and the HNB The establishment cause in the establishment of the RRC connection RRC connection request is an emergency call, the UE is directly allowed to be admitted, or the UE is directly allowed to access because the establishment cause in the RRC initial direct transmission message is an emergency call; if the UE If the emergency call is not initiated, and the user is a non-admission user, the UE is rejected to initiate the current call.

An embodiment of the present invention provides a call processing device, including: a first unit, configured to allocate a context resource to a user terminal UE that initiates an emergency call in an HNB, to allow the UE to make an emergency call call; and a second unit, where After the emergency call ends, for the non-admission user, the context resource allocated for the UE is released.

An embodiment of the present invention provides a call processing device, including: a determining unit, configured to determine whether a call initiated by a user equipment UE under a home base station HNB is an emergency call, and determine whether the UE is a non-access user, where The UE is directly allowed to be admitted because the establishment cause in the RRC connection request for establishing the RRC connection between the UE and the HNB is an emergency call, or the UE is directly allowed to access because the establishment cause in the RRC initial direct transmission message is an emergency call. And a rejecting unit, configured to: when the determining unit determines that the call initiated by the UE is not an emergency call, and the UE is a non-admission user, rejecting the UE to initiate the current call.

Embodiments of the present invention provide a call processing system including the aforementioned call processing device. Compared with the prior art, the main differences and effects of the embodiments of the present invention are as follows:

An embodiment of the present invention provides a technical solution for preventing a non-access user from using an emergency call to initiate a non-access user after the emergency call is terminated. Allowed services improve the security of admission control. According to another embodiment of the present invention, it is determined whether the UE initiated call under the HNB is an emergency call, and whether the UE is a non-admission user, the UE has been allowed to enter, if the UE initiates an emergency Calling and the UE is a non-admission user, rejecting the UE to initiate the current call. Through such an admission mechanism, the non-access user can also prevent the non-admission user from using the emergency call to initiate the disallowed service, thereby improving the security of the admission control. . BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic flowchart of a call processing method according to Embodiment 1 of the present invention;

2 is a schematic flowchart of a call processing method according to Embodiment 2 of the present invention;

3 is a schematic diagram of a UE deregistration process in the method according to Embodiment 2 of the present invention;

4 is a schematic diagram of another UE de-registration process in the method according to the second embodiment of the present invention; FIG. 5 is a schematic flowchart of a call processing method according to Embodiment 3 of the present invention;

6 is a schematic flowchart of a call processing method according to Embodiment 4 of the present invention;

7 is a schematic structural diagram of a call processing device according to Embodiment 5 of the present invention;

FIG. 8 is a schematic structural diagram of a call processing apparatus according to Embodiment 6 of the present invention. DETAILED DESCRIPTION OF THE INVENTION In order to make the objects, technical solutions and advantages of the present invention more comprehensible, the present invention will be further described in detail with reference to the accompanying drawings.

It should be noted that the technical solution provided by the embodiment of the present invention can be applied to various communication systems, such as Long Term Evolution (LTE) and Wideband Code Division Multiple Access (WCDMA). Or Global System for Mobile Communications (GSM).

It can be understood that the HNB and the cell have a corresponding relationship. If the HNB base station supports the CSG, the corresponding cell is a CSG cell. In the prior art solution, the Close mode CSG cell only aligns with the user to open the service, but allows the non-admission user to make an emergency call. The HNB judges the emergency call according to the reason of the call. If it is an emergency call, the HNB/HNB GW (Gateway, GW for short) does not make an admission judgment, allocates a Context ID, and allows the user to talk. Non-access user After the emergency call ends, because the Context ID has been assigned, the user will not be allowed to enter other services.

The present invention provides various embodiments in response to the problems in the prior art.

Embodiment 1:

For the above technical problem, the embodiment of the present invention provides a call processing method. As shown in FIG. 1, the method includes the following steps:

Step 101: Allocating a context resource to the user terminal UE that initiates the emergency call in the HNB, and allowing the UE to make an emergency call call;

In this step, whether the UE is an admission UE or not, if it initiates an emergency call, it needs to allocate a context resource to the UE and allow it to make an emergency call. The allocated context resource may be a context ID established for the UE.

The context ID is the UE context ID, which is used as a flag of the UE context to record the UE context and identify the UE. The context ID is also the signaling connection ID. In the HNB scenario, the context ID is allocated when the UE first resides, and is subsequently maintained by the aging timer.

Step 102: If the UE is a non-admission user, release the context resource allocated for the UE after the emergency call of the UE ends.

In the prior art, if the HNB/HNB gateway finds that the UE already has the Context ID, it indicates that the UE has already camped and will not make the admission judgment again. Therefore, according to the prior art scheme, when the non-access user emergency call ends, since the Context ID is already allocated, the user does not make an access when performing other services, so that the non-access user can also be in the Close The mode of the CSG cell to conduct business.

For this problem, the processing in this step is as follows: After the emergency call ends, the context ID established for the non-admission user is released, that is, the UE context is released.

Specifically, the HNB may determine whether the UE is a non-admission user according to whether the identifier of the UE is in the admission list. If the judgment result is yes, the HNB may initiate the UE registration process to release the context resource allocated for the UE. (such as context ID). Alternatively, the HNB gateway may determine whether the UE is a non-admission user according to whether the identifier of the UE is in the admission list. If the judgment result is yes, the HNB gateway initiates the UE registration process, and releases the context resource allocated for the UE. (such as context ID). Further, the method may further include: determining whether the call initiated by the UE is an emergency call, and

Whether the UE is a non-admission user; if the UE initiates an emergency call and the UE is a non-admission user, the UE is rejected to initiate the current call.

It can be seen from the description of this embodiment that after the emergency call ends, the context resource of the non-admission user is released, and the non-admission user is prevented from using the emergency call to initiate the disallowed service, thereby improving the security of the admission control.

Embodiment 2:

The following describes the call processing method provided in the second embodiment in detail with reference to FIG. 2. In this embodiment, the network element involved includes: a UE, an HNB, an HNB GW, and a core network (Core network).

Step 201: After the UE camps on the HNB cell, establish an RRC connection with the HNB. In this step, the UE establishes a Radio Resource Control (RRC) connection with the HNB. During the establishment of the R C, the UE may carry information such as the UE identity information UE identity, the UE capability information UE capabilities, and the establishment cause value Establishment Cause to the HNB. The establishment cause value may indicate whether the call is an emergency call.

Specifically, the UE may initiate a Non-Access Stadium (NAS) process by establishing an RRC connection, for example, a Location Area Update (LAU) process.

Step 202: After the RRC is established, the UE initiates an RRC direct transmission message.

In this step, the RRC direct transmission message may be an RRC initial direct transmission Initial Direct Transfer message, and the RRC initial direct transmission message may carry the identifier of the UE. The RRC initial direct transmission message may be a location update request message.

Step 203: The HNB checks the UE capability obtained in step 201.

In this step, the HNB checks the UE capability obtained in step 201. If the UE does not support the CSG, the non-CSG admission is adopted, and the non-CSG admission is performed on the access network (HNB GW/HNB).

If the HNB does not have the context ID of the UE, step 205 is performed, and the HNB initiates a UE registration process to the HNB GW, and the registration process may support allocation of the Context ID to record the UE context and identify the UE. In addition, optionally, before initiating the UE registration process, the HNB may first determine whether the UE reports the identity information in the RRC establishment process. The identification information may be an International Mobile Subscriber Identity (IMSI) information or other identification information that can identify the UE, such as Temporary Mobile Subscriber Identity (TMSI), but the present invention The embodiment is mainly described by taking IMSI as an example. If the HNB determines that the UE does not report the IMSI in the RC establishment process, and is not an emergency call procedure, the UE's HNB initiates an Identity procedure for acquiring the IMSI to obtain its IMSI.

If the context ID of the UE already exists in the HNB, the UE registration procedure is not triggered. Step 204: If the HNB enables auxiliary admission, the HNB may perform IMSI-based admission control;

This step is optional. Specifically, the HNB determines whether the UE is allowed to be admitted according to whether the IMSI of the UE is in the admission list. It should be noted that if the call cause in the RRC connection request is an emergency call, the HNB does not Make an admission judgment and directly allow admission of the UE;

Step 205: The HNB initiates a UE registration process to the HNB GW.

In this step, the HNB initiates a UE registration procedure to the HNB GW, and sends a UE registration request UE Register Request message to the HNB GW. The message may carry information such as UE Identity (such as IMSI), UE capability information, and establishment cause value Establishment Cause.

Step 206: The HNB GW performs admission control on the UE.

In this step, the HNB GW may determine whether to allow the UE to enter according to whether the IMSI of the UE is in the admission list. It should be noted that if the establishment cause value indicates that the UE initiates an emergency call, the HNB GW does not allow admission. It is judged that the admission of the UE is directly allowed, and the registration request of the UE is accepted.

Step 207: The HNB GW accepts the UE registration request, and allocates a context ID to the UE.

In this scenario, an emergency call is taken as an example. In this scenario, the HNB GW accepts the UE registration request, allocates a Context ID context ID to the UE, and returns a registration acceptance message HNB AP UE Register Accept message to the HNB, where the message includes the context ID. .

It can be understood that if the HNB GW rejects the UE registration request, the HNB is returned with the registration rejection message HNBAP UE Register Reject message.

Step 208: After receiving the registration acceptance message of the HNB GW, the HNB initiates RUA Connect. Message

In this step, the HNB initiates a RANAP User Adaptation (RUA) Connect message, where the RUA Connect message may include a Radio Access Network Application Part (RANAP) Initial UE message. .

Step 209: The HNB GW receives the RUA CONNECT message, establishes a Signalling Connection Control Part (SCCP) connection with the CN, and forwards the RANAP Initial UE message to the CN.

Step 210: CN responds to the SCCP connection confirmation;

Step 211: The NAS process is continued between the UE and the CN.

Step 212: After the emergency call ends, the non-access user initiates the UE registration process, releasing the Context ID.

In this step, according to the user admission situation (if the admission control has been done, the admission result is referred to, if not, the UESI is determined according to whether the IMSI of the UE belongs to the admission list), and the non-access user initiates the UE to register. Process.

The entity that initiates the UE to the registration process may be the HNB GW, or may be initiated by the HNB if the HNB does the admission control of the HNB. It can be understood that for a user who cannot obtain IMSI, since it can be regarded as a non-admission user, the same processing can be performed, that is, the UE is started to register the process, and the Context ID is released.

As described above, in the prior art, if the HNB/HNB GW finds that the UE already has the Context

The ID indicates that the UE has already been parked, and will not make the admission judgment again, which makes it possible for non-access users to initiate unallowed services. Therefore, the technical solution of the embodiment of the present invention, for the emergency call scenario, takes into consideration the security requirement, initiates the UE registration process after the emergency call ends, and releases the Context ID, which can improve the security of the CSG cell admission control and prevent non- Admission users (illegal users) use emergency calls to initiate unallowed services.

Specifically, the embodiment of the present invention further provides multiple implementation manners to implement a UE deregistration process, which will be described below with reference to the accompanying drawings.

As shown in FIG. 3, it is a schematic diagram of a UE deregistration process initiated by an HNB according to an embodiment of the present invention. The process includes: The HNB starts the UE to register the process by sending a UE to register a DE-Register message. Upon receiving the UE to register the message, the HNB GW shall release all resources related to the UE, including the Context ID.

As shown in FIG. 4, it is a schematic diagram of a UE deregistration process initiated by an HNB GW according to an embodiment of the present invention.

The process includes: The HNB GW initiates a UE deregistration process by sending a UE DE-Register message. When receiving the UE to register the message, the HNB shall release all resources related to the UE, including the Context ID.

It can be understood that the implementation of the solution of the embodiments of the present invention is more flexible.

Embodiment 3:

In addition to the problems in the prior art, the embodiment of the present invention further provides an implementation method, as shown in FIG. 5, including:

501: Determine whether the user equipment initiated by the user equipment UE in the HNB is an emergency call, and determine whether the UE is a non-access user;

502: If the UE initiates an emergency call and the UE is a non-admission user, the UE is rejected to initiate the current call.

Specifically, the UE can determine whether the UE is an admission user according to whether the identifier of the UE is in the admission list (the admission list can be configured at the HNB) to determine whether the UE is a non-access user; or, the HNB gateway Whether the UE is a non-access user depends on whether the identity of the UE is in the admission list (the admission list can be configured at the HNB GW;).

Further, after determining whether the call initiated by the UE is an emergency call, the method further includes: checking whether the emergency call number initiated by the UE is illegal, and if the emergency call number is illegal, and the UE is a non-admission user, rejecting the UE to initiate This call.

It can be seen that the technical solution provided by the embodiment of the present invention determines the correctness of the emergency call flow when the call is initiated. If the UE initiates an emergency call and the UE is a non-access user, the UE is rejected to initiate the call. Through such an access mechanism, non-access users can be prevented from using the emergency call to initiate an impermissible service, and the security of the admission control is improved.

Embodiment 4: For the problems existing in the prior art, the embodiment of the present invention further provides another implementation method, which is specifically described below with reference to FIG. 6. The method includes:

Step 601-602: The UE establishes an RRC connection with the HNB, and the UE sends an RRC initial direct transmission message to the HNB.

In this embodiment, it is assumed that the establishment cause in the RC connection request is an emergency call, or the RRC initial direct transmission message is a Connection Management (CM) service request message CM Service Request, and the establishment reason in the CM Service Request is assumed. For an emergency call, the HNB/HNB GW does not make an admission decision, that is, directly allows admission of the UE.

As mentioned above, if the solution in the prior art in the previous paragraph is adopted, if the subsequent UE initiates Call Setup instead of Emergency Call Setup, it will cause a security risk.

Steps 603-610: Steps 603-610 of the embodiment of the present invention are substantially similar to the corresponding steps of the previous embodiment, and will not be described in detail. It should be noted that, in the embodiment of the present invention, the CN network element is described by taking a Mobile Switching Centre (MSC) as an example.

Optionally, an authentication process and a security mode control process may also be included, which are not shown in the figure. Step 611: The UE initiates call setup by using a NAS message.

In this step, the NAS message may be a Call Setu message.

Step 612: Verify the correctness of the emergency call process;

It can be understood that this step can be performed by the HNB or by the HNB GW. Specifically, for an emergency call that meets the non-CSG admission condition, check whether the NAS message is Emergency Call Setup. If it is not Emergency Call Setup, and the user does not have permission to access (if the admission control has been done, the referral result is referred to, and if it has not been done, the UESI's IMSI is judged according to the admission list), it indicates that the emergency call is not met. Flow, refuse to initiate this call, go to step 613.

Optionally, it is further possible to check whether the emergency call number is legal. If the emergency call number is illegal (that is, it does not belong to the list of emergency call numbers allowed by the government, the list can be pre-configured on the HNB/HNB GW), and the user does not have permission to enter, the call is refused to be initiated, and step 613 is performed.

In addition, for users who cannot obtain the IMSI, the non-access user can also be regarded as the same process. Optionally, after performing step 612, the short message may also be sent to prompt the user, for example, to prompt the call initiated by the UE to be rejected.

Step 613: Disconnect and release the relevant resources.

This step 613 can be specifically implemented by a call release procedure. It should be noted that the release process is not limited to the following examples.

Specifically, the HNB/HNB GW determines to initiate release during the call; HNB/HNB

The GW sends a downlink direct transmission message (such as Release Complete) to the UE, and releases a Mobility Management (MM) connection; the HNB/HNB GW sends a direct transmission message (such as CM Service Abort) to the MSC to release the MM connection; Iu Release

Command message, releasing the Iu link; the HNB returns an Iu Release Complete message to the MSC;

The HNB sends an RRC Connect Release Request message to the UE to release the RRC link. The UE returns an RRC Connect Release Complete message and completes the release.

The technical solution provided by the embodiment of the present invention, if it is previously admitted due to the UE initiating an emergency call, the subsequent UE needs to check the correctness of the emergency call process when the call setup is initiated, and refuses to initiate if the emergency call process is not met. This call. This ensures that non-access users can avoid impermissible services by using emergency calls, and the security of admission control is improved.

Further, the legitimacy of the emergency call number can be further checked to avoid the use of illegal emergency call number access.

It can be understood that various implementations provided by the embodiments of the present invention may exist independently or in combination to solve the problems in the prior art.

For example, the UE user initiates a call in the HNB, and the HNB/HNB GW checks the correctness of the emergency call process. Optionally, the validity of the emergency call number can be further checked. If the check fails, the UE is rejected to initiate the call. Moreover, after the call is released, the HNB/HNB GW can check whether the UE user is an admission user, and if it is not an admission user, release its Context ID.

In this way, the Context ID can be further checked when the call is initiated, and the Context ID can be further released after the emergency call is completed. The security of the access control can be more fully ensured, and non-access users can be prevented from initiating services, maintaining network security and Operator benefits.

Embodiment 5: The embodiment of the present invention further provides a call processing device, which may be an HNB GW or an HNB. The embodiment of the present invention mainly uses the device as an HNB GW as an example.

The device includes: a first unit 701, configured to allocate a context resource to a user terminal UE that initiates an emergency call in the home base station HNB, to allow the UE to make an emergency call call; and a second unit 702, configured to: after the emergency call ends, The non-access user releases the context resource allocated for the UE.

Optionally, the second unit 702 is implemented by the determining subunit 7021 and the releasing subunit 7022, where the determining subunit 7021 is configured to determine whether the UE is a non-admission user; and the releasing subunit 7022 is configured to determine the subunit 7021. When it is determined that the UE is a non-admission user, after the emergency call ends, the context resource allocated for the UE is released.

Specifically, the determining sub-unit 7021 determines whether the UE is a non-admission user, and the method described in the method embodiment is used, and details are not described herein again.

Further, the determining sub-unit 7021 is further configured to: determine whether the call initiated by the UE is an emergency call; correspondingly, the device may further include a third unit 703, configured to determine, by the determining sub-unit 7021, that the UE is a non-access user If the call initiated by the UE is not an emergency call, the UE is rejected to initiate the current call.

The call processing device provided by one embodiment of the present invention prevents the non-admission user from using the emergency call to initiate the disallowed service by releasing the context resource allocated for the non-admission user after the emergency call ends, thereby improving the admission control. Security.

Example 6:

The embodiment of the present invention further provides a call processing device, which may be an HNB GW or an HNB. The embodiment of the present invention mainly uses the device as an HNB GW as an example.

The device includes: a determining unit 801, configured to determine whether the call initiated by the user equipment UE under the home base station HNB is an emergency call, and whether the UE is a non-admission user; and the rejecting unit 802, configured to determine, by the determining unit 801, the UE When the initiated call is not an emergency call and the UE is a non-admission user, the UE is rejected to initiate the current call.

Optionally, the determining unit 801 is further configured to determine whether the emergency call number initiated by the UE is illegal. Correspondingly, the rejecting unit 802 is further configured to: if the determining unit 801 determines that the emergency call number is illegal and the UE is a non-access user, Then the UE is rejected to initiate the call. The technical solution provided by the embodiment of the present invention, if it is previously admitted due to the UE initiating an emergency call, the subsequent UE needs to check the correctness of the emergency call process when the call setup is initiated, and refuses to initiate if the emergency call process is not met. This call. This ensures that non-access users are prevented from using the emergency call to initiate unallowed services, and the security of the admission control is improved.

The embodiment of the present invention further provides a call processing system, which may include the call processing device of the device embodiment 5 and the sixth embodiment.

It can be understood that if the call processing device is an HNB GW, the call processing system may further include an HNB that communicates with the HNB GW; if the call processing device is an HNB, the call processing system may further include an HNB that communicates with the HNB. GW.

It should be noted that the processes and functions involved in the method embodiments may be implemented by the device provided by the device embodiment or the system provided by the system embodiment, and may be implemented by corresponding functional modules, and some of the functional modules are already It is described in the device embodiment, but some of them are not described in detail in the device embodiment, but the call processing device provided by the device embodiment does not implement the corresponding functions and features. For example, if the call control device is an HNB, it has the functions of establishing an RRC connection with the UE, checking the UE capability, admission control, and the like, and interacting with the HNB GW through the Iuh interface (such as completing the UE registration process); The control device is an HNB GW, which has functions of interacting with the HNB (such as completing the UE registration process), functions of interacting with the CN, and the like. The method of the embodiment of the present invention can be implemented by using a software, so the embodiment of the present invention can also be implemented by a data carrier or a data storage device that carries the software.

It will be understood that, although in the description of the method embodiments, the steps of the method have been described in order to facilitate understanding, it should be noted that the order of the above steps is not strictly limited.

While the invention has been illustrated and described with reference to the preferred embodiments embodiments The spirit and scope of the invention.

Claims

Rights request

A call processing method, comprising:

Allocating a context resource to the user terminal UE that initiates the emergency call by the home base station HNB, allowing the UE to make an emergency call;

After the emergency call ends, for the non-admission user, the context resource allocated for the UE is released.

2. The method according to claim 1, wherein for the non-admission user, releasing the context resource allocated for the UE comprises:

Whether the HNB determines whether the UE is a non-access user according to whether the identifier of the UE is in the admission list;

If it is determined that the UE is a non-admission user, the HNB initiates a UE deregistration process, and releases the context resource allocated for the UE.

The method according to claim 1, wherein for the non-admission user, releasing the context resource allocated to the UE includes:

The HNB gateway determines whether the UE is a non-access user according to whether the identifier of the UE is in the admission list.

If it is determined that the UE is a non-admission user, the HNB gateway initiates a UE deregistration process, and releases the context resource allocated for the UE.

The method according to any one of claims 1 to 3, wherein the method further comprises:

Determining whether the call initiated by the UE is an emergency call, and whether the UE is a non-access user;

If the UE initiates an emergency call and the UE is a non-admission user, the UE is rejected to initiate the current call.

The method according to any one of claims 1 to 3, wherein, before allocating a context resource to a UE that initiates an emergency call under the HNB, the method further includes: determining according to the capability information of the UE, if the UE does not support blocking The user group CSG adopts a non-CSG admission mode for admission control in the access network.

6. A call processing method, comprising: Determining whether the call initiated by the user equipment UE in the home base station HNB is an emergency call, and determining whether the UE is a non-admission user, where the UE establishes a radio resource control RRC connection RRC connection request by the UE The reason for the establishment is an emergency call, the UE is directly allowed to be admitted, or the UE is directly allowed to access because the establishment cause in the RRC initial direct transmission message is an emergency call;

The method according to claim 6, wherein the determining whether the UE is a non-access user comprises:

Whether the HNB determines whether the UE is a non-access user according to whether the identifier of the UE is in the admission list; or

The HNB gateway determines whether the UE is a non-access user according to whether the identity of the UE is in the admission list.

The method according to claim 6 or 7, wherein after determining whether the call initiated by the UE is an emergency call, the method further includes:

Checking whether the emergency call number initiated by the UE is illegal. If the emergency call number is illegal and the UE is a non-admission user, the UE is rejected to initiate the current call.

9. A call processing device, comprising:

a first unit, configured to allocate a context resource to a user terminal UE that initiates an emergency call in the home base station HNB, and allow the UE to make an emergency call call;

The second unit is configured to release, for the non-admission user, the context resource allocated to the UE after the emergency call ends.

The device according to claim 9, wherein the second unit comprises a judging subunit and a releasing subunit, wherein

The determining subunit is configured to determine whether the UE is a non-access user;

And the releasing subunit is configured to release, when the determining subunit determines that the UE is a non-admission user, release the context resource allocated to the UE after the emergency call ends.

The device of claim 10, wherein the determining subunit is further configured to: determine whether the call initiated by the UE is an emergency call; The device further includes a third unit, configured to, when the determining subunit determines that the UE is a non-admission user, and the call initiated by the UE is not an emergency call, rejecting the UE to initiate the current call.

12. A call processing device, comprising:

a determining unit, configured to determine whether the call initiated by the user equipment UE in the home base station HNB is an emergency call, and determining whether the UE is a non-admission user, where the UE establishes a radio resource control RRC connection with the HNB The establishment of the RRC connection request is an emergency call, the UE is directly allowed to be admitted, or the UE is directly allowed to access because the establishment cause in the RRC initial direct transmission message is an emergency call;

And a rejecting unit, configured to: when the determining unit determines that the call initiated by the UE is not an emergency call, and the UE is a non-admission user, rejecting the UE to initiate the current call.

The device according to claim 12, wherein the determining unit is further configured to determine whether the emergency call number initiated by the UE is illegal;

The rejecting unit is further configured to: if the determining unit determines that the emergency calling number is illegal, and the UE is a non-admission user, rejecting the UE to initiate the current call.

A call processing system, comprising: the call processing device according to any one of claims 9 to 11, or

A call processing device as claimed in claim 12 or 13.