KR20140055058A - Method for deactivating non-emergency bearers and maintaining forbidden ta lists when ue having both emergency and non-emergency bearer moves to a unknown forbidden ta in radio communication system - Google Patents

Abstract

The present invention relates to a method and an apparatus to manage a forbidden TA and control a bearer for a general call in a wireless communication UE and, more specifically, to a method and an apparatus to deactivate a bearer for a general call when UE with the general call and an emergency call moves to a service-unavailable TA. Furthermore, the present invention proposes a method and an apparatus to manage a forbidden TA and control a bearer for a general call in UE, which are capable of reducing the waste of a control message and the connection delay when reconnecting to a general call service after ending an emergency call service.

Description

METHOD FOR DEACTIVATING NON-EMERGENCY BEARERS AND MAINTAINING FORBIDDEN TA LISTS WHEN UE HAVING BOTH EMERGENCY AND NON- EMERGENCY BEARER MOVES TO A UNKNOWN FORBIDDEN TA IN RADIO COMMUNICATION SYSTEM}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and apparatus for managing a Forbidden TA (Tracking Area) of a user equipment (UE) and a bearer of a general call in a wireless communication system, To a method and apparatus for controlling a Forbidden TA and a general call bearer in a UE in order to reduce unnecessary control message generation and access delay when a UE having a general call and an emergency call moves to a TA that is not serviceable.

In a wireless communication system, a communication network operator may limit a subscription restriction or connection in a specific area for various reasons. Therefore, when the terminal moves to the specific area (for example, a specific TA), the service for the general call becomes impossible.

Accordingly, the MME (Mobility Management Entity) sends a rejection cause together with a Tracking Area Update (TAU) reject message to the TA in the Tracking Area Update (TAU) request message transmitted from the TA, It is intended to inform that it is impossible. For example, the UE may generate a Tracking Area Update (TAU) including # 12 (TA not allowed), # 13 (Roaming not allowed in this TA) and # 15 (No suitable cell in TA) You can receive a reject message.

Then, the terminal recognizes that the service is unavailable, adds the corresponding TA to the Forbidden list according to the reason for each rejection, and does not attempt to access the corresponding TA for a certain period of time in the future. For example, update the Forbidden list "forbidden tracking areas for regional provision of service" for # 12, and update Forbidden list "forbidden tracking areas for roaming" for # 13 and # 15.

However, in the case of a terminal having both a general call and an emergency call, even if the terminal moves to a TA which can not perform a general service, a method for providing continuous service for the existing emergency call, There is a need for a management method for a Forbidden TA list including information on the service and the service-incapable TA.

According to another aspect of the present invention, there is provided a method of controlling access to a network, the method comprising: receiving an access request message for a service restricted cell from a terminal; Transmitting a connection permission message for the emergency call to the terminal; And transmitting the connection rejection reason information for the general call to the terminal.

Further, a method of controlling a connection of a terminal according to the present invention includes: transmitting an access request message to a service restricted cell to a network; Receiving a connection admission message for the emergency call from the network; Receiving from the network connection rejection reason information for a general call; And storing the cell in a prohibition list based on the rejection reason information.

Meanwhile, a network according to the present invention includes a transmitting / receiving unit for transmitting / receiving signals to / from a terminal; And a controller for receiving an access request message for the service restricted cell from the terminal, transmitting a connection permission message for emergency call to the terminal, and controlling access rejection reason information for the general call to the terminal .

Further, a terminal according to the present invention includes a transmitting / receiving unit for transmitting / receiving signals to / from a network; And a connection request message for the service restricted cell to the network, receives a connection permission message for the emergency call from the network, and receives connection rejection reason information for the general call from the network, And a controller for storing the cell in the forbidden list.

More specifically, the method proposed by the present invention comprises: In the case of a terminal having both a general call and an emergency call in a wireless communication system, if the terminal moves to an TA whose general service is impossible, if the terminal is in an EMM-IDLE state, the terminal sends a TAU request message, The MME recognizes that the non-emergency bearer service is not available, deactivates the EPS bearer context for the PDN connection of the general call, and leaves the EPS bearer context for the PDN connection of the emergency call as is, And the UE receiving the TAU accept message deactivates the EPS bearer context for the PDN connection of the general call without a separate network access stratum (NAS) message from the MME, .

Another method proposed by the present invention is as follows. In the case of a terminal having both a general call and an emergency call in a wireless communication system, if the terminal moves to an TA whose general service is impossible, if the terminal is in an EMM-IDLE state, the terminal sends a TAU request message, The MME recognizes that the non-emergency bearer service is not available, deactivates the EPS bearer context for the PDN connection of the general call, and leaves the EPS bearer context for the PDN connection of the emergency call as is, , # 13, or # 15 in order to notify the UE of the process of including the EPS bearer context status IE in the TAU accept message and deactivation of the EPS bearer context of the general call in the TAU accept message Includes an EMM cause IE that indicates the reason for rejection, and accepts a TAU accept message including the rejection reason # 12, # 13, or # 15 It includes that the mobile station correct the Forbidden TA list for each reject reason. Another solution is to not include the EMM cause cause IE indicating the reason for refusal # 12, # 13, or # 15 in the TAU accept message, but rather, after the terminal completes the emergency call service, Including an EMM cause IE indicating the rejection reason # 12, # 13, or # 15 in the Detach accept message when the Detach request message is sent to the Detach request message and the Detach accept message including the reject reason # 12, # 13, Includes modifying the Forbidden TA list according to each rejection reason.

Another method proposed by the present invention is as follows. In the case of a UE having both a general call and an emergency call in a wireless communication system, if the UE moves to an TA that can not be a general service, if the UE is in an EMM-CONNECTED state, the UE sends a TAU request message, The MME recognizes that the non-emergency bearer service is impossible and sends the Deactivate EPS bearer context request messages to disable the EPS bearer context for the general call immediately after sending the TAU accept message do.

Another method proposed by the present invention is as follows. In the case of a UE having both a general call and an emergency call in a wireless communication system, if the UE moves to an TA that can not be a general service, if the UE is in an EMM-CONNECTED state, the UE sends a TAU request message, The MME recognizes that the non-emergency bearer service is not available, deactivates the EPS bearer context for the PDN connection of the general call, and leaves the EPS bearer context for the PDN connection of the emergency call as is, , # 13, or # 15 in order to notify the UE of the process of including the EPS bearer context status IE in the TAU accept message and deactivation of the EPS bearer context of the general call in the TAU accept message Includes an EMM cause IE indicating the TAU accept message including the reject reason # 12, # 13, or # 15 Includes modifying the Forbidden TA list according to each rejection reason. Another solution is to not include the EMM cause cause IE indicating the reason for refusal # 12, # 13, or # 15 in the TAU accept message, but rather, after the terminal completes the emergency call service, Including an EMM cause IE indicating the rejection reason # 12, # 13, or # 15 in the Detach accept message when the Detach request message is sent to the Detach request message and the Detach accept message including the reject reason # 12, # 13, Includes modifying the Forbidden TA list according to each rejection reason.

Another method proposed by the present invention is as follows. In the case of a UE having both a general call and an emergency call in a wireless communication system, if the UE moves to an TA that can not be a general service, if the UE is in an EMM-CONNECTED state, the UE sends a TAU request message, The MME recognizes that the non-emergency bearer service is impossible and sends the Deactivate EPS bearer context request messages to disable the EPS bearer context for the general call immediately after sending the TAU accept message do. At this time, the Deactivate EPS bearer context request message includes an ESM Cause IE to notify the reason for deactivating the EPS bearer context for the general call, and the terminal receiving the Deactivate EPS bearer context request message transmits Forbidden And modifying the TA list. As another solution, the ESM cause IE indicating the reason for rejection is not included in the Deactivate EPS bearer context request message. After the UE completes the emergency call service, a Detach request message is sent to the MME to resume the service for the general call When receiving a Detach accept message including an EMM cause IE indicating the reject reason # 12, # 13 or # 15 in the Detach accept message and a Detach accept message including the reject reason # 12, # 13 or # 15, This includes modifying the Forbidden TA list for each reason for rejection.

The present invention provides a method for efficiently deactivating a general call in a case where a terminal having both a general call and an emergency call in a wireless communication system moves to a TA in which a general service is not possible, It is possible to reduce the number of messages and improve the user experience by decreasing the number of messages by providing a method of avoiding unnecessary connection failure when resuming service for a general call in the future.

1 is a block diagram illustrating related entities in an EPS in accordance with an embodiment of the present invention.
2 is a signal flow diagram schematically illustrating operations of a UE and a network updating a Forbidden TA list through a TAU accept message in a situation where the UE is in EMM-IDLE according to an embodiment of the present invention.
3 is a signal flow diagram schematically illustrating operation of a UE and a network updating a Forbidden TA list through a Detach accept message in a situation where the UE is in EMM-IDLE according to an embodiment of the present invention.
FIG. 4 schematically illustrates the operation of a UE and a network for updating a Forbidden TA list through a Detach accept message by disabling an EPS bearer of an ordinary call through an ESM message in a situation where the terminal is EMM-CONNECTED according to an embodiment of the present invention; Fig.
5 is a signal flow diagram schematically illustrating the operation of a UE and a network updating a Forbidden TA list through a TAU accept message in a situation where the UE is in an EMM-CONNECTED state according to an embodiment of the present invention.
6 schematically illustrates operations of a UE and a network for locally deactivating an EPS bearer of a general call and updating a Forbidden TA list through a detach accept message in a situation where the terminal is EMM-CONNECTED according to an embodiment of the present invention Fig.
FIG. 7 schematically illustrates operations of a UE and a network for updating a Forbidden TA list through an ESM message and disabling an EPS bearer of a general call in a situation where the terminal is in an EMM-CONNECT state according to an embodiment of the present invention; Fig.
8 is a flowchart schematically showing the operation of a terminal according to embodiments of the present invention.
9 is a flowchart schematically showing the operation of the MME according to embodiments of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Hereinafter, a detailed description of known functions and configurations that may obscure the gist of the present invention will be omitted.

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and apparatus for managing a Forbidden TA (Tracking Area) of a user equipment (UE) in a wireless communication system and a bearer in a general call,

In particular, the present invention proposes a method and apparatus for deactivating a bearer for a general call when a terminal having a general call and an emergency call moves to a service-incapable TA. In addition, we propose a method and apparatus for forbidden TA management and general call bearer control of UE to reduce control message wastage and access delay when reconnecting for general call service after emergency call service termination.

Considering that an operation of a terminal and an MME (Mobility Management Entity) may be changed according to a situation where the terminal is an EMM (EPS Mobility Management) -IDLE and an EMM-CONNECTED state, when EMM-IDLE and EMM-CONNECTED Embodiments are presented for each.

In the present specification, the wireless communication system may include an evolved packet system (EPS). However, the present invention is not limited to LTE (Long-Term Evolution) mobile communication systems such as EPS and LTE-A (Long-Term Evolution Advanced) mobile communication systems. That is, the present invention can be applied to other mobile communication systems such as GPRS (General Packet Radio Service) mobile communication system and IEEE (Institute of Electrical and Electronics Engineers) 802.16m communication system. It should be noted that in the case of the GPRS mobile communication system, the SGSN (Serving GPRS Support Node) can perform the same network congestion resolution scheme that the MME performs in the present invention.

Figure 1 is a block diagram illustrating related entities in an EPS that are the basis of embodiments of the present invention.

FIG. 1 shows only the entities constituting the EPS according to the embodiment of the present invention. Of course, the entities not shown in FIG. 1 may exist in the EPS. Further, the description of the entities shown in FIG. 1 is only a part related to the present invention, and it goes without saying that additional functions may be included.

Referring to FIG. 1, a UE (User Equipment) 100 represents a user terminal, and the eNB 102 is connected to the UE 100 through a radio channel as an entity for controlling radio resources. The Mobility Management Entity (MME) 104 manages the UE 100 in the idle mode with the mobility management entity and performs functions related to roaming and authentication of the UEs.

The MME 104 also processes the bearer signal generated by the UE 100. [ The Home Subscriber Server (HSS) 106 stores subscription information for each UE 100 and transmits information related to the UE 100 to the MME 104 when the UE 100 accesses the network, (104) to control the UE (100).

In the EPS, the UE 100 establishes a radio bearer with the eNB 102 for data transmission and reception, and the eNB 102 and the MME 108 establish a context setup and an S1 connection a connection is established. After the data transmission / reception is completed, if the certain condition is satisfied, the MME 104 or the eNB 102 releases the eNB context. This involves releasing the S1 connection. In addition, the eNB 102 performs connection release of RRC (Radio Resource Control) with the UE 100, and transitions the UE 100 to the idle state.

The UE 100, the eNB 102, the MME 104, and the HSS 106 according to the embodiment of the present invention each include a transceiver capable of transmitting and receiving data with other components, And a control unit for controlling the operation of each of the components including the storage unit for storing data, the transmission / reception unit, and the storage unit.

Forbidden tracking areas for roaming 114 and forbidden tracking areas for regional provision of service 116 may be used to prevent the UE 100 from accessing a TA that can not receive normal service even if it is connected. When storing a TA list and sending a message such as an Attach request, a TAU request, or a Service Request, the TA in the forbidden TA list should not send the above messages.

In particular, the network may include the configuration of the EPS excluding the UE 100, and the network herein is a concept including the configuration of the EPS excluding the UE.

2 is a diagram for explaining a process of receiving a TAU accept message including an EMM cause value IE and updating a Forbidden TA list in a situation where a terminal according to the present invention is in EMM-IDLE.

In describing the embodiment of the present invention, for convenience of explanation, the name of the TA that can not be generalized service for the terminal is referred to as TA1.

In FIG. 2, the terminal 200 has both a general call and an emergency call (step 211), and moves to TA1 where EMM-IDLE is not available. At this time, since TA1 does not exist in the tracking area identity (TAI) list of the terminal, the terminal 200 does not recognize that the TA1 is a TA that can not service the general call. (Step 213)

Accordingly, the terminal 200 can transmit the TAU request message (step 215). Thereafter, the MME 210 recognizes that the service for the general call is impossible and deactivates the EPS bearer context for the PDN connection of the general call. (Step 217)

In addition, the MME 210 may transmit a TAU accept message including an EPS bearer context status IE including information on an EPS bearer context for an active emergency call. (Step 219) At this time, the TAU accept message 219 may include an EMM cause value IE indicating a reason for rejection as shown in Table 1 to notify the UE 200 of the reason why the EPS bearer context of the general call is inactivated.

Table 2 lists examples of rejection reasons. As shown in Table 2, there are Reject Cause # 12 (TA not allowed), # 13 (Roaming not allowed in TA), or # 15 (No suitable cell in TA). The reason for rejection, that is, the EMM cause value IE, may be included in the TAU accept according to an embodiment of the present invention as shown in Table 1.

Upon receiving the TAU accept 219, the terminal 200 recognizes that the EPS bearer context for the general call is inactivated and deletes it from the included EPS bearer context status IE. TA1 is added to the forbidden TA list according to the rejection reason included in the EMM cause value IE. (Step 221)

For example, in case # 12, TA1 is added to Forbidden list "forbidden tracking areas for regional provision of service". For # 13 and # 15, TA1 is added to Forbidden list "forbidden tracking areas for roaming".

The UE 200 operates as if performing emergency attach because the UE only has a bearer for the emergency call (step 223).

3 is a view for explaining another embodiment of the present invention. More specifically, a description will be given of a process of updating a Forbidden TA list through a Detach accept message in the process of detaching for a general call service after receiving a service for an emergency call through a TAU process in a situation where the UE is in EMM-IDLE FIG.

As shown in FIG. 3, the terminal 300 having both the general call and the emergency call can move to the TA1 where the general service can not be performed in the EMM-IDLE state. Since TA1 does not exist in the tracking area identity (TAI) list stored in the terminal, the terminal 300 does not recognize that the TA1 is unable to service the general call. (Step 313)

Accordingly, the terminal 300 can transmit a TAU request message to the MME 310. [ (Step 315)

The MME 310 recognizes that the service for the general call is not available. The MME 310 deactivates the bearer context for the PDN connection of the general call (317) and transmits the EPS bearer context including the information about the bearer context for the active emergency call and sends a TAU accept message (319) including the status IE. Upon receiving the TAU accept 319, the terminal 300 recognizes that the EPS bearer context for the general call is inactivated and deletes it from the included EPS bearer context status IE.

The UE 300 operates as if performing an emergency attach because the UE only has a bearer for the emergency call (321).

However, if the general call service is to be resumed, the terminal receives notification of service termination for the emergency call from the upper layer. (Step 323), the UE 300 transmits a Detach Request message 325 to perform a detach process for the emergency attach. The MME 310 transmits a Detach accept message 327 to the UE 300. [

At this time, the MME 310 transmits a Detach accept message including the EMM cause value IE and the identity of the TA1 to the UE as shown in Table 3, and notifies the TA1 that the service for the general call is impossible. The identity of TA1 may follow the format shown in Table 4. If the UE 300 continues to stay in TA1, the detach accept message may not include the TAI.

 For example, referring to Table 2, it is assumed that Reject cause # 12 (TA not allowed), # 13 (Roaming not allowed in this TA) and # 15 (No suitable cell in TA) .

In step 329, the UE may add TA1 to the forbidden TA list according to the reject reason included in the EMM cause value IE.

For example, if the reason for rejection is # 12, the UE adds TA1 to the Forbidden list forbidden tracking areas for regional provision of service. For # 13 and # 15, the Forbidden list forbidden tracking areas for roaming is TA1 And stores it.

FIGS. 4 to 7 are diagrams for explaining an embodiment in which the UE is an EMM-CONNECTED.

4, when a terminal 400 having both a general call and an emergency call is in an EMM-CONNECTED state, the terminal moves to a TA1 that can not be a general service, and TA1 The terminal 400 recognizes that the terminal 400 is not in the TAI list, and the terminal 400 can not recognize that the TA1 can not provide the service for the general call 413. Accordingly, And sends a TAU request 415 to the MME 410.

The MME 410 recognizes that the service for the general call is impossible (417). After transmitting the TAU accept message 419 to the MME 410, the MME 410 transmits a TAU accept message 419 to the terminal 400 in order to deactivate the EPS bearer context for the PDN connections of the general call. And sends an EPS bearer context request (421).

Upon receiving the deactivate EPS bearer context request 421, the terminal 400 deletes the corresponding EPS bearer context and sends a Deactivate EPS bearer context accept message 423 to the MME 410 to notify that the corresponding EPS bearer context has been deactivated , The MME 410 completes the process of deactivating the EPS bearer context for the PDN connections of the general call. Since the UE only has a bearer for the emergency call, the UE 400 operates as if performing emergency attach (425).

If the emergency call service is notified of the termination (427), the UE 400 transmits a Detach Request (429) to perform the detach process for the emergency attach, Message.

The MME 410 transmits a Detach accept message 431 to the UE 400

do. At this time, the MME 410 may transmit a Detach accept message including the EMM cause value IE and the identity of the TA1 to the UE as shown in Table 3, and notify that the service for the general call is impossible in the TA1. The identity of TA1 may follow the format as shown in Table 4. If the UE 400 continues to stay in TA1, the Detach accept message may not include the TAI.

 For example, if the reason for rejection cause # 12 (TA not allowed), # 13 (Roaming not allowed in TA), or # 15 (No suitable cell in TA) . The UE adds TA1 to the forbidden TA list according to the rejection reason included in the EMM cause value IE. (433)

For example, the UE adds TA1 to the Forbidden list forbidden tracking areas for the reason # 12, and TA1 to the Forbidden list forbidden tracking areas for roaming if # 13 or # 15. Can be added.

5 is a diagram for explaining a process of receiving a rejection reason through a TAU accept message and updating a Forbidden TA list in a situation where the terminal is EMM-CONNECTED according to another embodiment of the present invention.

As shown in FIG. 5, when the terminal 500 having both the general call and the emergency call moves to the TA1 in which the general service can not be performed in the EMM-CONNECTED state and the TA1 moves to the TAI the terminal 500 recognizes that the TA1 request is not in the tracking area identity list and the terminal 500 does not recognize that the TA1 can not provide the service for the general call 513, 510).

The MME 510 recognizes that the service for the general call is impossible. Then, the EPS bearer context for the PDN connection of the general call is deactivated (517), and a TAU accept message (519) including the EPS bearer context status IE including information on the EPS bearer context for the activated emergency call is transmitted.

At this time, the TAU accept message 519 includes an EMM cause value IE indicating a reason for rejection as shown in Table 1 to notify the UE 500 of the reason why the EPS bearer context of the general call is inactivated. For example, referring to Table 2, it is assumed that Reject cause # 12 (TA not allowed), # 13 (Roaming not allowed in this TA) and # 15 (No suitable cell in TA) .

Upon receiving the TAU accept 519, the terminal 500 recognizes that the EPS bearer context for the general call is inactivated and deletes it from the included EPS bearer context status IE. TA1 is added to the forbidden TA list according to the rejection reason included in the EMM cause value IE.

For example, in case # 12, TA1 is added to Forbidden list "forbidden tracking areas for regional provision of service". For # 13 and # 15, TA1 is added to Forbidden list "forbidden tracking areas for roaming".

Since the UE only has a bearer for the emergency call, the UE 500 operates as if performing emergency attach (523).

FIG. 6 is a diagram for explaining a process of locally disabling an EPS bearer of a general call and updating a Forbidden TA list through a Detach accept message in a situation where the terminal is EMM-CONNECTED according to an embodiment of the present invention.

Referring to FIG. 6, when the terminal 600 having both the general call and the emergency call moves to the TA1 in which the general service can not be performed in the EMM-CONNECTED state and the TA1 moves the TAI the terminal 600 recognizes that the TA1 is not in the area identity list and the terminal 600 does not recognize that the TA1 can not provide the service for the general call 613 and therefore the terminal 600 transmits the TAU request 615 to the MME 610, Lt; / RTI >

The MME 610 recognizes that the service for the general call is not available. The MME 610 deactivates the EPS bearer context for the PDN connection of the general call (617) and transmits the EPS bearer context including the information about the EPS bearer context for the activated emergency call and sends a TAU accept message 619 including the status IE.

Upon receiving the TAU accept 619, the terminal 600 recognizes that the EPS bearer context for the general call is inactivated and deletes it from the included EPS bearer context status IE.

Since the UE only has a bearer for the emergency call, the UE 600 operates as if performing emergency attach (621).

If the emergency call service is terminated (623), the UE 600 transmits a Detach Request 625 to perform a detach process for the emergency attach, Message.

 The MME 610 transmits a Detach accept message 627 to the UE 600. At this time, the MME 610 informs the UE that the service for the general call is impossible in the TA1 including the EMM cause value IE as shown in Table 3, and includes the identity of the TA1 (see Table 4). 600) remains in TA1, TAI may not be included.

 For example, referring to Table 2, it is assumed that Reject cause # 12 (TA not allowed), # 13 (Roaming not allowed in this TA) and # 15 (No suitable cell in TA) . TA1 is added to the forbidden TA list according to the rejection reason included in the EMM cause value IE.

For example, in case # 12, TA1 is added to Forbidden list "forbidden tracking areas for regional provision of service". For # 13 and # 15, TA1 is added to Forbidden list "forbidden tracking areas for roaming".

7 is a flowchart illustrating an operation of the UE and the network updating the Forbidden TA list through the ESM message and disabling the EPS bearer of the general call in the situation that the terminal is EMM-CONNECTED according to another embodiment of the present invention. Fig.

As shown in FIG. 7, when the terminal 700 having both the general call and the emergency call moves to the TA1 in which the general service can not be performed in the EMM-CONNECTED state and the TA1 moves to the TAI the terminal 700 recognizes that the TA1 is not in the tracking area identity list and the terminal 700 does not recognize that the TA1 can not provide the service for the general call 713. The terminal 700 transmits the TAU request 715 to the MME 710).

The MME 710 recognizes that the service for the general call is impossible (717). The MME 710 transmits a TAU accept message 719 to the terminal 700 and then deactivates the EPS bearer context for the PDN connection to the terminal 700 in order to deactivate the EPS bearer context for the PDN connections of the general call EPS bearer context request (721) is sent.

At this time, the MME 710 includes an ESM cause value IE indicating a reason for rejection as shown in Table 5 to notify the terminal 700 of the reason for deactivating the EPS bearer context for the PDN connection of the general call. For example, referring to Table 6, it is assumed that Reject cause # xxx (TA not allowed), #yyy (Roaming not allowed in this TA), and #zzz (No suitable cell in TA) .

Upon receiving the Deactivate EPS bearer context request 721, the terminal 700 deletes the corresponding EPS bearer context. Also, TA1 is added to the forbidden TA list according to the reason for rejection included in the ESM cause value IE.

For example, for #xxx, add TA1 to Forbidden list "forbidden tracking areas for regional provision of service", and for #yyy and #zzz add TA1 to Forbidden list "forbidden tracking areas for roaming".

The UE 700 informs the MME 710 of the Deactivate EPS bearer context accept message 723 indicating that the corresponding EPS bearer context is deactivated and the MME 710 deactivates the EPS bearer context for the PDN connections of the general call . Since the UE only has bearer for the emergency call, the UE 700 operates as if performing emergency attach (725).

8 is a flowchart for schematically explaining an operation of a terminal according to an embodiment of the present invention.

The UE according to the above-mentioned inventions operates in the following manner as shown in FIG.

A UE having both a general call and an emergency call moves to a new tracking area TA1 that is not in the TA list, and a terminal that has confirmed that TA1 is not in the forbidden TA list sends a TAU request (800).

The UE receiving the TAU accept message transmitted by the MME deactivates the EPS bearer context of the UE according to the EPS bearer context status IE sent (801). At this time, if the MME deactivates the EPS bearer context for the general call, the terminal is in the service state only in the emergency call (806).

If the EMM cause is # 12, the UE confirms that there is an EMM cause in the TAU accept message received from the MME, adds TA1 to the Forbidden list forbidden tracking areas for the global provision of service (804) If the EMM cause is # 13 or # 15, TA1 is added to the Forbidden list forbidden tracking areas for roaming (805).

If the terminal is in the EMM-CONNECT state and does not deactivate the EPS bearer for the general call in step 801, after receiving the Deactivate EPS bearer context request for the general call sent by the MME, the EPS bearer context for the corresponding general call is deactivated (811). Accordingly, the terminal is in the state of being in service only in the emergency call (806).

 If the Deactivate EPS bearer context request message includes an ESM cause IE (812), if ESM cause is #xxx, TA1 is added to the Forbidden list " forbidden tracking areas for global provision of service " If the ESM cause is #yyy or #zzz, TA1 is added to the Forbidden list forbidden tracking areas for roaming (805).

If the terminal receiving the emergency call only receives an emergency call service termination notification from the upper layer (806), the terminal transmits a Detach request message to the MME to resume the normal call service (808) detach process (step 810).

If an EMM cause is included in the 0detach accept message received by the AT in step 809 and the EMM cause is # 12, TA1 is added to the Forbidden list forbidden tracking areas for the global provision of service in step 804, If the EMM cause is # 13 or # 15, TA1 is added to the Forbidden list forbidden tracking areas for roaming (805).

9 is a flowchart for explaining the operation of the MME according to an embodiment of the present invention.

 The MME according to the inventions operates in the following manner as shown in FIG.

Upon receiving the TAU request from the UE having both the general call and the emergency call, the MME recognizes that the UE can not perform the general call service in the new tracking area TA1 and stores the reason why the UE can not perform the service. The MME may disable the EPS bearer for the general call locally without using an Enhanced Session Management (ESM) message with the mobile station (901). In this case, the MME may include the EMM cause IE in the TAU accept message and send it to the terminal (902, 904). The EMM cause may include # 12 (TA not allowed), # 13 (TA not allowed), or # 15 (TA not allowed) depending on the situation.

If the MME uses the Enhanced Session Management (ESM) message with the terminal to perform the EPS bearer deactivation for the general call in step 901, the MME transmits a TAU accept message to the EPS bearer for the general call Deactivate the EPS bearer context process (905).

The MME includes the ESM cause IE in the Deactivate EPS bearer context request message (906), and the ESM cause IE may include ESM cause #xxx (TA not allowed), #yyy TA not allowed), or #zzz (TA not allowed).

 If the MME does not include the ESM cause IE in the Deactivate EPS bearer context request message, the MME stores the non-serviceable state and the TAI's tracking area identity (TAI). The MME transmits a deactivate EPS bearer context request message and receives a deactivate EPS bearer context accept message from the terminal to terminate the deactivation of the EPS bearers for the general call in step 908. The MME can recognize that only the service for the emergency call is in progress (909).

If the MME does not include the EMM Cause IE in the TAU accept message in step 902, it stores the TAI (tracking area identity) of the corresponding TA1 and the situation in which the service is impossible.

Meanwhile, if a detach request message is received from the terminal that is in the service of the emergency call only service (910), the MME performs a detach process and transmits a detach accept message (912). At this time, the MME may include an EMM cause IE in the detach accept message and a TAI of TA1 in which the general call service is impossible. However, if the terminal is still in TA1, TAI of TA1 may not be included. The EMM cause may include # 12 (TA not allowed), # 13 (TA not allowed), or # 15 (TA not allowed) depending on the situation.

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not limited to the disclosed embodiments, but is capable of various modifications within the scope of the invention. Therefore, the scope of the present invention should not be limited by the illustrated embodiments, but should be determined by the scope of the appended claims and equivalents thereof.

Claims (20)

A method of controlling access to a network in a wireless communication system,
Receiving an access request message for a service restricted cell from a terminal;
Transmitting a connection permission message for the emergency call to the terminal; And
And transmitting the connection rejection reason information for the general call to the terminal. The method according to claim 1,
Wherein the access permission message includes the rejection reason information. The method according to claim 1,
After the step of transmitting the connection permission message,
Receiving a connection release request message from the terminal; And
Further comprising the step of transmitting a connection release permission message to the terminal,
And the disconnection permission message includes the rejection reason information. 4. The method according to claim 2 or 3,
After receiving the connection request message,
Further comprising the step of deactivation of an Evolved Packet System (EPS) bearer context for a general call when the terminal is in an EMM (EPS Mobility Management) connection state,
Wherein the access permission message further includes information on the EPS bearer context state. The method according to claim 1,
After the step of transmitting the connection permission message,
Further comprising transmitting an EPS bearer context deactivation request message for a general call when the terminal is in an EMM connected state,
Wherein the EPS bearer context deactivation request message includes the reject reason information. A method of controlling connection of a terminal in a wireless communication system,
Transmitting an access request message to a service restricted cell to a network;
Receiving a connection admission message for the emergency call from the network;
Receiving from the network connection rejection reason information for a general call; And
And storing the cell in a forbidden list based on the reject reason information. The method according to claim 6,
Wherein the access permission message includes the rejection reason information. The method according to claim 6,
After receiving the connection grant message,
Sending a disconnection request message to the network; And
Further comprising receiving from the network a disconnection grant message,
And the disconnection permission message includes the rejection reason information. 9. The method according to claim 7 or 8,
After receiving the connection request message,
Wherein the access permission message further includes information on an EPS bearer context state when the terminal is in an EMM connection state. The method according to claim 6,
After receiving the connection grant message,
Receiving an EPS () bearer context deactivation request message for a general call when the terminal is in an EMM connected state,
And the EPS () bearer context disable request message includes the reject reason information. A network for controlling connections in a wireless communication system,
A transmitting and receiving unit for transmitting and receiving signals to and from the terminal; And
And a controller for receiving an access request message for the service restricted cell from the terminal, transmitting a connection permission message for the emergency call to the terminal, and controlling access rejection reason information for the general call to the terminal Network feature. 12. The method of claim 11,
Wherein the access permission message includes the rejection reason information. 12. The method of claim 11,
Wherein,
Receives a connection release request message from the terminal and controls the terminal to transmit a connection release permission message to the terminal,
And the disconnection permission message includes the rejection reason information. The method according to claim 12 or 13,
Wherein the control unit deactivates the EPS bearer context for the general call when the terminal is in the EMM connected state,
Wherein the access permission message further includes information on the EPS bearer context state. 12. The method of claim 11,
Wherein the control unit controls to transmit an EPS bearer context deactivation request message for a general call when the terminal is in an EMM connection state,
Wherein the EPS bearer context deactivation request message includes the reject reason information. A terminal for controlling connection in a wireless communication system,
A transmitting and receiving unit for transmitting and receiving signals to and from a network; And
The access control unit controls the access request message for the service restricted cell to the network, receives the connection permission message for the emergency call from the network, receives the access rejection reason information for the general call from the network, And a controller for storing the cell in the forbidden list based on the control information. 17. The method of claim 16,
Wherein the access permission message includes the rejection reason information. 17. The method of claim 16,
The control unit transmits a connection release request message to the network and controls to receive a connection release permission message from the network,
Wherein the disconnection permission message includes the rejection reason information. The method according to claim 17 or 18,
Wherein the access grant message further includes information on the EPS bearer context state when the terminal is in an EMM connected state. 12. The method of claim 11,
When the terminal is in the EMM connection state, the control unit controls to receive the EPS bearer context disable request message for the general call,
Wherein the EPS bearer context deactivation request message includes the reject reason information.

Images