KR20160145525A - Wireless communication system and method for establishing connection between user equipment and mobility management entity - Google Patents

Abstract

The present invention relates to a wireless communication system and a method for establishing the connection between user equipment and a mobility management entity, capable of efficiently supporting a mobility management entity (MME). According to one embodiment of the present invention, a method of transceiving a signal from the MME in a communication system includes the steps of: receiving a first request message from a terminal; transmitting a second request message related to the terminal to a server based on the first request message; receiving a first response message including subscription information of the terminal, in response to the second request message from the server; allocating a tracking area update (TAU) timer value of the terminal based on the subscription information of the terminal; and transmitting a second response message including the TAU timer value to the terminal. According one embodiment of the subject application, communication can be effectively made.

Description

TECHNICAL FIELD [0001] The present invention relates to a wireless communication system, a wireless communication system, and a connection method between a user terminal and a mobility management entity,

 The present invention relates to a wireless communication system and a communication method thereof, and more particularly, to a wireless communication system and a connection method between a user terminal and a mobility management entity.

In general, Universal Mobile Telecommunications System (UMTS) is a third generation wireless communication system based on Global System for Mobile communications (GSM) and General Packet Radio Services (GPRS) and using Wideband Code Division Multiple Access (WCDMA). The 3rd Generation Partnership Project (3GPP) for standardization of UMTS proposes a UMTS Evolved Packet System (EPS) such as an LTE (Long Term Evolution) system. At this time, the LTE system is a technology for implementing high-speed packet-based communication. The LTE system includes a Mobility Management Entity (MME) for managing mobility of a user terminal connected to a user equipment (UE).

 However, as a variety of communication services are provided in the above-described wireless communication system, additional functions of the user terminal have been diversified. And the mobility management entity is implemented to support the additional function of the user terminal. Accordingly, in order to use the communication service according to the additional function, the user terminal must be connected to the mobility management entity corresponding to the additional function.

Accordingly, an object of the present invention is to efficiently connect a user terminal to a mobility management entity corresponding to the additional function.

According to an aspect of the present invention, there is provided a method for transmitting and receiving signals in a mobility management entity (MME) of a communication system, the method comprising: receiving a first request message from a terminal; Transmitting a second request message related to the terminal to the server based on the first request message; Receiving a first response message including subscription information of the terminal in response to the second request message from the server; Allocating a tracking area update (TAU) timer value of the AT based on subscription information of the AT; And transmitting a second response message including the TAU timer value to the terminal.

According to another embodiment of the present invention, there is provided a method of transmitting / receiving signals in a terminal of a communication system, comprising: transmitting a first request message to a mobility management entity (MME); And receiving a response message including a tracking area update (TAU) timer value from the MME, wherein the TAU timer value is based on subscription information of the terminal received from the server And is allocated in the MME.

According to another aspect of the present invention, a mobility management entity (MME) of a communication system includes a transceiver for transmitting and receiving signals; Receiving a first request message from the terminal, transmitting a second request message related to the terminal on the basis of the first request message to the server, controlling the transmitter / receiver in response to the second request message , Receiving a first response message including subscription information of the subscriber station, allocating a tracking area update (TAU) timer value of the subscriber station based on the subscription information of the subscriber station, And a second response message including a timer value to the terminal.

According to another aspect of the present invention, there is provided a terminal of a communication system including: a transceiver for transmitting and receiving signals; And a controller for controlling the transceiver and for transmitting a first request message to a mobility management entity and receiving a response message including a tracking area update (TAU) timer value from the MME, And the TAU timer value is allocated in the MME based on subscription information of the terminal received from the server.

According to an aspect of the present invention, there is provided a wireless communication system, and a method of connecting a user terminal and a mobility management entity, the mobility management entity being capable of efficiently connecting a user terminal to a mobility management entity corresponding to the additional function. That is, the MTC terminal can be efficiently connected to the MTC MME supporting the MTC characteristic for the corresponding MTC terminal. Accordingly, in the wireless communication system, the MTC MME can more efficiently support the MTC, and the MTC terminal can perform the MTC more efficiently.

1 is a block diagram showing a configuration of a wireless communication system according to a first embodiment of the present invention;
2 is a flowchart illustrating a connection procedure in a wireless communication system according to a first embodiment of the present invention;
3 is a flowchart showing a connection procedure in the wireless communication system according to the first embodiment of the present invention;
FIG. 4 is a flowchart showing an operation procedure of the mobility management entity in FIG. 2;
FIG. 5 is a flowchart showing an operation procedure of the mobility management entity in FIG. 3;
FIG. 6 is a flowchart showing an operation procedure of the user terminal in FIGS. 2 and 3;
7 is a block diagram showing a configuration of a wireless communication system according to a second embodiment of the present invention;
8 is a flowchart illustrating a connection procedure in a wireless communication system according to a second embodiment of the present invention;
FIG. 9 is a flowchart showing an operation procedure of the mobility management entity in FIG. 8, and
10 is a flowchart showing the operation procedure of the user terminal in FIG.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the same components are denoted by the same reference symbols as possible in the accompanying drawings. Further, the detailed description of known functions and configurations that may obscure the gist of the present invention will be omitted.

1 is a block diagram showing a configuration of a wireless communication system according to a first embodiment of the present invention.

1, the wireless communication system of the present embodiment includes a user terminal 110, an enhanced Node B (eNB) 120, a mobility management entity 130, a home subscriber server (HSS) 140, A Serving Gateway (S-GW) 150 and a Packet Data Network Gateway (P-GW) 160.

The user terminal 110 may be fixed or mobile. In this case, the user terminal 110 may be a normal terminal for performing a general communication function, or may be an MTC terminal for performing a specific additional function, for example, a machine type communication (MTC) function. Here, the MTC technology includes, for example, Smart Metering for supporting automatic communication between a power company server and a home power system, an alarm system for supporting automatic communication between a server of a security company and a trespasser at home, And the like.

The base station 120 manages a cell. At this time, the base station 120 is a macro base station, and the cell is a cell of a general cellular system, and may be a macro cell. Here, the base station 120 and the cell may be used in the same sense. The base station 120 is connected to the user terminal 110 through a wireless channel, and controls radio resources. For example, the base station 120 generates control information in the cell as system information and broadcasts it, or allocates radio resources for transmitting / receiving packet data or control information to / from the user terminal 110 have. In this case, the system information includes a PLMN ID of a public land mobile network (PLMN), an eNB Cell Global ID (ECGI), a tracking area to which each cell belongs, Tracking Area ID (TAI), and the like. The base station 120 may collect handover result information of the current cell and neighboring cells from the user terminal 110 to determine a handover and instruct handover. To this end, the base station 120 has a control protocol such as a Radio Resource Control Protocol related to radio resource management.

The mobility management entity 130 manages the idle mode user terminal 110 and selects the serving gateway 150 and the packet data network gateway 160 for the user terminal 110. The mobility management entity 130 performs functions related to roaming and authentication. The mobility management entity 130 also processes the bearer signal generated by the user terminal 110. The mobility management entity 130 allocates identification information to the user terminal 110 and manages the user terminal 110 by connecting to the user terminal 110 using the identification information. At this time, the mobility management entity 130 may be a normal MME for supporting a normal terminal, for example, an MTC MME for supporting the MTC terminal.

The mobility management entity 130 is connected to the base station 120 through a wireless channel and is connected to the user terminal 110 through the base station 120. Here, the mobility management entity 130 is connected to the base station 120 via the S1-MME interface. At this time, the mobility management entity 130 communicates with the user terminal 110 using a NAS (Non Access Stratum) message. The mobility management entity 130 supports a plurality of tracking zones and is connected to the base stations 120 that support each tracking zone information. That is, a plurality of base stations 120 supporting the same tracking zone information may be connected to the same mobility management entity 130. Or a plurality of base stations 120 that support different tracking zone information may each be associated with a different mobility management entity 130. Or a plurality of base stations 120 supporting different tracking zone information may be associated with the same mobility management entity 130.

At this time, various MTC features (MTC features) are defined for efficient support of MTC technology in a wireless communication system. Here, the MTC characteristics are classified into low mobility, time controlled, time tolerant, packet switched only (PS), small data transmissions, Mobile Originated Only, Infrequent Mobile Terminated, MTC Monitoring, Priority Alarm Message (PAM), Secure Connection, Location Specific Trigger, Or a Group-based MTC (MTC), as shown in FIG.

And, for MTC terminals and MTC MME, some of the MTC characteristics may be required, and the rest of the MTC characteristics are not essential, but may optionally be required for optimization of the MTC. For example, since MTC terminal transmits data of several hundreds bytes or less for smart metering in which MTC terminal periodically reports the usage amount measured over a certain period of time through MTC MME, 'May be necessary. In this case, the 'location-specific trigger' at which the MTC should be initiated at the MTC terminal at a particular location may not be necessary at the MTC terminal and the MTC MME. Thus, in order to efficiently perform the MTC, the MTC terminal must be registered in the MTC MME supporting the desired MTC characteristics.

Thus, in the following description, the term 'essential MTC feature' represents the MTC characteristic that is essential for performing MTC in the MTC terminal. That is, since the MTC terminal supports the essential MTC characteristic in the wireless network, the MTC terminal can perform the MTC through the MTC MME of the wireless network. And the term 'optional MTC feature' indicates an MTC characteristic that is not essentially required to perform MTC in the MTC terminal. At this time, the selective MTC characteristic may be required for the optimization of the MTC in the wireless network. That is, the MTC terminal can perform the MTC through the MTC MME of the wireless network even if it does not support the selective MTC feature in the wireless network.

In addition, in the following description, the term 'supported MTC feature' refers to an MTC characteristic for supporting in the MTC MME of the wireless network to perform MTC in the MTC terminal. At this time, the supporting MTC characteristic of the MTC MME may be configured to include the essential MTC characteristic of the MTC terminal and may be configured not to include the essential MTC characteristic of the MTC terminal. And the supporting MTC characteristic of the MTC MME may be configured to include the selected MTC characteristic of the MTC terminal and may be configured not to include the required MTC characteristic of the MTC terminal.

That is, if the supporting MTC characteristic includes the required MTC characteristic, the MTC MME can support the MTC terminal's MTC. And MTC terminal can perform MTC through MTC MME using essential MTC characteristic. At this time, if the supporting MTC characteristic further includes the selective MTC characteristic, the MTC terminal can further utilize the selective MTC characteristic to perform the MTC. Also, if the supporting MTC characteristic does not include the required MTC characteristic, the MTC MME does not support the MTC terminal's MTC. In other words, the MTC terminal can not perform the MTC through the MTC MME. Here, even if the supporting MTC characteristic includes the selected MTC characteristic, the MTC terminal can not perform the MTC through the MTC MME. Therefore, in order for the MTC terminal to perform the MTC through the MTC MME, the MTC terminal must be registered with the MTC MME supporting the required MTC characteristics.

The home subscriber server 140 stores subscription data for each user terminal 110. When the user terminal 110 is registered in the mobility management entity 130, the home subscriber server 140 updates the subscription information of the user terminal 110. Then, the home subscriber server 140 delivers the subscription information of the user terminal 110 for use in controlling the user terminal 110 in the mobility management entity 130. At this time, the subscription information may include MTC subscription information for the MTC terminal. Here, the MTC subscription information includes the required MTC characteristic and the selected MTC characteristic of the corresponding MTC terminal.

The serving gateway 150 is connected to the base station 120 and the mobility management entity 130 via a wireless channel. Here, the serving gateway 150 is connected to the base station 120 via the S1-U interface. The serving gateway 150 performs a mobility control function of the user terminal 110 and the like. That is, when the user terminal 110 moves between the base stations 120 in the handover of the user terminal 110 or between the 3GPP wireless networks, the serving gateway 170 serves as a mobility anchor of the user terminal 110 .

The packet data network gateway 160 is connected to the serving gateway 150 via a wireless channel. Here, the packet data network gateway 160 is connected to the serving gateway 150 through the S5 interface. The packet data network gateway 160 connects to an Internet Protocol network (IP network) 170. The packet data network gateway 160 performs an IP address assignment function, a packet data related function, and the like to the user terminal 110. The packet data network gateway 160 delivers the packet data provided from the Internet protocol network 170 to the user terminal 110 through the serving gateway 150 and the base station 120. In addition, when the user terminal 110 moves between the 3GPP wireless network and the non-3GPP wireless network, the packet data network gateway 160 acts as a mobility anchor of the user terminal 110. In addition, the packet data network gateway 160 determines the bearer band for the user terminal 110, and performs forwarding and routing functions of the packet data.

The user terminal 110 is connected to the Internet protocol network 170 through a data transmission path via the base station 120, the serving gateway 170 and the packet data network gateway 70. [ To transmit and receive packet data. The user terminal 110 may transmit a NAS request message to the mobility management entity 130 through the base station 120. At this time, the NAS request message may include, for example, a request made up of at least one of an attach request, a tracking area update request, and a service request. Also, upon receiving the NAS request message, the BS 120 selects the mobility management entity 130 according to the NNSF (Network Node Selection Function) function and delivers the NAS request message. This is because the base station 120 can be connected to multiple mobility management entities 130 individually via the S1-MME interface.

In this case, it is assumed that the user terminal 110 is an MTC terminal and the base station 120 is connected to the normal MME and the MTC MME through the S1-MME interface. However, the present invention is not limited thereto. That is, the present invention can be applied even if the MTC terminal is replaced with another terminal different from the normal terminal by replacing the MTC MME with another MME for supporting another terminal. In this embodiment, it is assumed that the MTC MME determines whether or not the MTC terminal can register according to whether the MTC terminal can support the required MTC characteristic. That is, in the normal MME or the MTC MME, all other requirements for determining whether or not to permit registration of the MTC terminal are satisfied.

2 is a flowchart illustrating a connection procedure in the wireless communication system according to the first embodiment of the present invention.

2, in the wireless communication system according to the present embodiment, the MTC terminal 111 requests the mobility management entity 130 to attach via the base station 120 in step 211 . At this time, the MTC terminal 111 stores the essential MTC characteristic and the selected MTC characteristic. That is, the MTC terminal 111 selects any one of the wireless networks accessible from the base station 120 and requests registration to the mobility management entity 130 of the corresponding wireless network. Here, the MTC terminal 111 may store information on each of the wireless networks accessible by the base station 120. At this time, the MTC terminal 111 can request registration in the MTC MME 131 and request registration in the normal MME (133 in FIG. 3). Then, the MTC terminal 111 may transmit the unique International Mobile Subscriber Identity (IMSI) to the mobility management entity 130.

When registration is requested in the MTC terminal 111, the MTC MME 131 requests the home subscriber server 140 for the subscription information of the MTC terminal 111 in step 213. At this time, the MTC MME 131 can request the subscription information of the MTC terminal 111 by reporting the location of the MTC terminal 111 to the home subscriber server 140. Here, the MTC MME 131 transmits the subscription identification information of the MTC terminal 111 to the home subscriber server 140. When the subscription information of the MTC terminal 111 is requested, the home subscriber server 140 responds to the MTC MME 131 with the subscription information of the MTC terminal 111 in step 215. At this time, the home subscriber server 140 updates the location of the MTC terminal 111 and notifies the MTC terminal 111 of the location of the MTC terminal 111, thereby transmitting the subscription information of the MTC terminal 111. That is, the home subscriber server 140 searches subscription information of the MTC terminal 111 using the subscription identification information, and transmits the subscription information to the MTC MME 131. At this time, the subscription information includes MTC subscription information for the MTC terminal 111. Here, the MTC subscription information includes the required MTC characteristic and the selected MTC characteristic of the corresponding MTC terminal 111. [

Next, when the subscription information of the MTC terminal 111 is answered, the MTC MME 131 analyzes the subscription information in step 217 and determines whether the MTC terminal 111 can support the essential MTC characteristic. At this time, the MTC MME 131 stores supporting MTC characteristics that can be supported in the corresponding wireless network. That is, the MTC MME 131 grasps the essential MTC characteristic from the subscription information of the MTC terminal 111 and determines whether or not it matches the supported MTC characteristic. If the supporting MTC characteristic includes the required MTC characteristic of the MTC terminal 111, the MTC MME 131 determines that the MTC terminal 111 can support the essential MTC characteristic. If the supported MTC characteristic does not include the required MTC characteristic of the MTC terminal 111, the MTC MME 131 determines that the support of the essential MTC characteristic of the MTC terminal 111 is impossible.

If it is determined in step 217 that the MTC terminal 111 can support the required MTC characteristics, the MTC MME 131 accepts the registration to the MTC terminal 111 in step 219. At this time, the MTC MME 131 notifies the MTC terminal 111 of the supported MTC characteristics.

Next, if the mobility management entity 130 permits registration, the MTC terminal 111 determines whether the mobility management entity 130 supports MTC in step 221. In step 221, That is, the MTC terminal 111 determines whether the mobility management entity 130 is the MTC MME 131 or not. At this time, the MTC terminal 111 determines whether or not the mobility management entity 130 has been notified of the MTC characteristic, thereby determining whether the mobility management entity 130 is the MTC MME 131 or not. Here, if the MTC characteristic has been notified, the MTC terminal 111 determines that the mobility management entity 130 is the MTC MME 131. If the MTC characteristic has not been notified, the MTC terminal 111 determines that the mobility management entity 130 is the normal MME 133. Thereafter, the MTC terminal 111 performs the MTC through the MTC MME 131 in step 223. At this time, the MTC terminal 111 can perform the MTC using the essential MTC characteristic. Or the MTC terminal 111 may perform the MTC using the supported MTC characteristics of the MTC MME 131. [ In other words, the MTC terminal 111 can use the supported MTC characteristic of the MTC MME 131 to grasp the selected MTC characteristic and perform the MTC.

On the other hand, if it is determined in step 217 that the MTC terminal 111 can not support the required MTC characteristic, the MTC MME 131 rejects the registration to the MTC terminal 111 in step 227. [ At this time, the MTC MME 131 can notify the cause of rejecting the registration of the MTC terminal 111. [ That is, the MTC MME 131 can notify the MTC terminal 111 that the essential MTC function can not be supported. Then, the MTC MME 131 may notify the MTC terminal 111 of a re-trial period for retrying registration. In addition, the MTC MME 131 may notify the MTC terminal 111 of the carrier information of each of the other wireless networks for use in retrying registration.

3 is a flowchart illustrating a connection procedure in a wireless communication system according to the first embodiment of the present invention.

Referring to FIG. 3, the connection procedure in the wireless communication system of the present embodiment starts from requesting the MTC terminal 111 to register with the mobility management entity 130 through the base station 120 in step 311. At this time, the MTC terminal 111 stores the essential MTC characteristic and the selected MTC characteristic. That is, the MTC terminal 111 selects any one of the wireless networks accessible from the base station 120 and requests registration to the mobility management entity 130 of the corresponding wireless network. Here, the MTC terminal 111 may store information on each of the wireless networks accessible by the base station 120. At this time, the MTC terminal 111 can request registration to the MTC MME 131 and request registration to the normal MME 133. And the MTC terminal 111 may transmit unique subscription identification information to the mobility management entity 130. [

When registration is requested in the MTC terminal 111, the normal MME 133 requests the home subscriber server 140 for subscription information of the MTC terminal 111 in step 313. At this time, the normal MME 133 can request the subscription information of the MTC terminal 111 by reporting the location of the MTC terminal 111 to the home subscriber server 140. Here, the normal MME 133 delivers the subscription identification information of the MTC terminal 111 to the home subscriber server 140. When the subscription information of the MTC terminal 111 is requested, the home subscriber server 140 replies with the subscription information of the MTC terminal 111 to the normal MME 133 in step 315. The home subscriber server 140 updates the location of the MTC terminal 111 and informs the normal MME 133 of the location of the MTC terminal 111 so as to transmit the subscription information of the MTC terminal 111. [ That is, the home subscriber server 140 retrieves the subscription information of the MTC terminal 111 using the subscription identification information, and transmits the subscription information to the normal MME 133. At this time, the subscription information includes MTC subscription information for the MTC terminal 111. Here, the MTC subscription information includes the required MTC characteristic and the selected MTC characteristic of the corresponding MTC terminal 111. [

Next, when the subscription information of the MTC terminal 111 is answered, the normal MME 133 permits the MTC terminal 111 to register it in step 317. At this time, the normal MME 133 can not process the MTC subscription information in the subscription information of the MTC terminal 111. [ Namely, the normal MME 133 can not distinguish the MTC terminal 111 from a normal terminal (not shown). Accordingly, the normal MME 133 regards the MTC terminal 111 as a normal terminal, and allows the MTC terminal 111 to register.

Next, if the mobility management entity 130 permits registration, the MTC terminal 111 determines whether the mobility management entity 130 supports MTC in step 319. [ That is, the MTC terminal 111 determines whether the mobility management entity 130 is the MTC MME 131 or not. At this time, the MTC terminal 111 determines whether or not the mobility management entity 130 has been notified of the MTC characteristic, thereby determining whether the mobility management entity 130 is the MTC MME 131 or not. Here, if the MTC characteristic has been notified, the MTC terminal 111 determines that the mobility management entity 130 is the MTC MME 131. If the MTC characteristic has not been notified, the MTC terminal 111 determines that the mobility management entity 130 is the normal MME 133. In step 321, the MTC terminal 111 deletes the registration with the normal MME 133. That is, since the normal MME 133 does not support the essential MTC characteristic, the MTC terminal 111 releases the registration with the normal MME 133. [

4 is a flow chart showing the operational procedure of the mobility management entity in Fig. Here, it is assumed that the mobility management entity is the MTC MME in the present embodiment.

Referring to FIG. 4, the operation procedure of the mobility management entity 130 in this embodiment starts with the MTC MME 131 detecting the registration request of the MTC terminal 111 in step 411. At this time, the MTC MME 131 grasps the subscription identification information of the MTC terminal 111. In step 413, the MTC MME 131 requests the subscriber information of the MTC terminal 111 to the home subscriber server 140. At this time, the MTC MME 131 can request the subscription information of the MTC terminal 111 by reporting the location of the MTC terminal 111 to the home subscriber server 140. Here, the MTC MME 131 transmits the subscription identification information of the MTC terminal 111 to the home subscriber server 140.

When the subscriber information of the MTC terminal 111 is answered in the home subscriber server 140, the MTC MME 131 detects this in step 415, analyzes the subscription information in step 417, It is determined whether or not support of the MTC characteristic is possible. At this time, the MTC MME 131 stores supporting MTC characteristics that can be supported in the corresponding wireless network. That is, the MTC MME 131 grasps the essential MTC characteristic from the subscription information of the MTC terminal 111 and determines whether or not it matches the supported MTC characteristic. If the supporting MTC characteristic includes the required MTC characteristic of the MTC terminal 111, the MTC MME 131 determines that the MTC terminal 111 can support the essential MTC characteristic. If the supported MTC characteristic does not include the required MTC characteristic of the MTC terminal 111, the MTC MME 131 determines that the support of the essential MTC characteristic of the MTC terminal 111 is impossible.

Lastly, if it is determined in step 417 that the MTC terminal 111 can support the required MTC characteristic, the MTC MME 131 permits the MTC terminal 111 to register the MTC terminal 111 in step 419. FIG. At this time, the MTC MME 131 notifies the MTC terminal 111 of the supported MTC characteristics. In step 421, the MTC MME 131 performs the MTC and the MTC. At this time, the MTC MME 131 can perform the MTC by supporting the essential MTC characteristic for the MTC terminal 111. Or the MTC MME 131 may support the MTC feature for the MTC terminal 111 to perform the MTC. That is, in order to optimize the MTC, the MTC MME 131 can identify and support the selected MTC characteristic for the MTC terminal 111 in the supported MTC characteristic.

On the other hand, if it is determined in step 417 that the MTC terminal 111 can not support the essential MTC characteristic, the MTC MME 131 rejects registration in the MTC terminal 111 in step 427. At this time, the MTC MME 131 can notify the reason for rejecting the registration of the MTC terminal 111. That is, the MTC MME 131 can notify the MTC terminal 111 that the essential MTC function can not be supported. Then, the MTC MME 131 may notify the MTC terminal 111 of a re-trial period for retrying registration. In addition, the MTC MME 131 may notify the MTC terminal 111 of the carrier information of each of the other wireless networks for use in retrying registration.

FIG. 5 is a flowchart showing an operation procedure of the mobility management entity in FIG. 3; FIG. Here, it is assumed that the mobility management entity is the normal MME in the present embodiment.

Referring to FIG. 5, the operation procedure of the mobility management entity 130 in this embodiment starts with the normal MME 133 detecting the registration request of the MTC terminal 111 in step 511. At this time, the normal MME 133 grasps the subscription identification information of the MTC terminal 111. In step 513, the normal MME 133 requests the subscriber information of the MTC terminal 111 to the home subscriber server 140. At this time, the normal MME 133 can request the subscription information of the MTC terminal 111 by reporting the location of the MTC terminal 111 to the home subscriber server 140. Here, the normal MME 131 transmits the subscription identification information of the MTC terminal 111 to the home subscriber server 140.

Finally, when the subscription information of the MTC terminal 111 is answered in the home subscriber server 140, the normal MME 133 detects it in step 515 and permits the registration to the MTC terminal 111 in step 517. [ At this time, the normal MME 133 can not process the MTC subscription information in the subscription information of the MTC terminal 111. [ Namely, the normal MME 133 can not distinguish the MTC terminal 111 from the normal terminal. Accordingly, the normal MME 133 regards the MTC terminal 111 as a normal terminal, and allows the MTC terminal 111 to register. Thereafter, in step 519, the normal MME 133 releases the registration with the MTC terminal 111. At this time, the normal MME 133 cancels the registration according to the request of the MTC terminal 111. [ Namely, since the normal MME 133 does not support the essential MTC characteristic, the normal MME 133 releases the registration with the MTC terminal 111.

FIG. 6 is a flowchart illustrating an operation procedure of the user terminal in FIGS. 2 and 3. FIG. Here, it is assumed that the user terminal is an MTC terminal in the present embodiment.

Referring to FIG. 6, the operation procedure of the user terminal 110 in this embodiment starts with the MTC terminal 111 selecting the mobility management entity 130 in step 611. That is, the MTC terminal 111 selects the mobility management entity 130 by selecting any one of the wireless networks accessible from the base station 120. At this time, the MTC terminal 111 may store the carrier information of each of the wireless networks accessible by the base station 120. The MTC terminal 111 stores the required MTC characteristic and the selected MTC characteristic. Thereafter, the MTC terminal 111 requests registration to the mobility management entity 130 in step 613. At this time, the MTC terminal 111 can request registration to the MTC MME 131 and request registration to the normal MME 133. And the MTC terminal 111 may transmit unique subscription identification information to the mobility management entity 130. [

If registration is permitted in the mobility management entity 130, the MTC terminal 111 detects this in step 615 and determines whether the mobility management entity 130 supports the MTC in step 617. That is, the MTC terminal 111 determines whether the mobility management entity 130 is the MTC MME 131 or not. At this time, the MTC terminal 111 determines whether or not the mobility management entity 130 has been notified of the MTC characteristic, thereby determining whether the mobility management entity 130 is the MTC MME 131 or not. Here, if the MTC characteristic has been notified, the MTC terminal 111 determines that the mobility management entity 130 is the MTC MME 131. If the MTC characteristic has not been notified, the MTC terminal 111 determines that the mobility management entity 130 is the normal MME 133.

If it is determined in step 617 that the mobility management entity 130 supports the MTC, the MTC terminal 111 performs MTC through the mobility management entity 130, i.e., the MTC MME 131 in step 619. At this time, the MTC terminal 111 can perform the MTC using the essential MTC characteristic. Or the MTC terminal 111 may perform the MTC using the supported MTC characteristics of the MTC MME 131. [ In other words, the MTC terminal 111 can use the supported MTC characteristic of the MTC MME 131 to grasp the selected MTC characteristic and perform the MTC.

On the other hand, if it is determined in step 617 that the mobility management entity 130 does not support the MTC, the MTC terminal 111 cancels the registration with the mobility management entity 130 in step 627. That is, since the normal MME 133 does not support the essential MTC characteristic, the MTC terminal 111 releases the registration with the normal MME 133. [ At this time, the MTC terminal 111 may store the carrier information of the corresponding wireless network in response to the normal MME 133 for later reference to select the mobility management entity 130. [ In other words, the MTC terminal 111 can store the provider information of the corresponding wireless network as selection prohibition information (forbidden PLMN ID) so that the MTC terminal 111 does not request registration to the corresponding normal MME 133 thereafter.

On the other hand, if registration is not permitted in the mobility management entity 130 in step 615 and registration is rejected in the mobility management entity 130, the MTC terminal 111 detects this in step 635, and in step 637, . At this time, the MTC terminal 111 can wait according to the previously stored retry waiting time. Or the MTC terminal 111 may wait for a retry waiting time as notified by the mobility management entity 130. Thereafter, the MTC terminal 111 reselects the mobility management entity 130 in step 639, and then proceeds to step 615. [ Then, the MTC terminal 111 repeats at least a part of steps 615 to 639.

At this time, the MTC terminal 111 may previously store the carrier information of each of the wireless networks accessible by the base station 120, and may be used to select another mobility management entity 130. Or the MTC terminal 111 may use the carrier information of each of the other wireless networks notified by the MTC MME 131 to select another mobility management entity 130. For example, if the provider information of each of the wireless networks is stored in advance, the MTC terminal 111 may use it to select another mobility management entity 130, otherwise, as instructed by the MTC MME 131 Another mobility management entity 130 may be selected. Here, the MTC terminal 111 can select another mobility management entity 130 with reference to previously stored selection prohibition information. That is, the MTC terminal may select the other mobility management entity 130 after excluding the selection prohibition information from the carrier information of each of the other wireless networks stored in advance or notified by the MTC MME 131.

According to the present embodiment, the user terminal 110 can be efficiently connected to the mobility management entity 130 corresponding to the additional function in the wireless communication system. That is, the MTC terminal 111 can be efficiently connected to the MTC MME 131 supporting the required MTC characteristic. Accordingly, in the wireless communication system, the MTC MME 131 can more efficiently support the MTC, and the MTC terminal 111 can more efficiently perform the MTC.

On the other hand, in the above-described embodiment, an example of determining whether or not the MTC terminal can register is determined by determining whether it is possible to support the essential MTC characteristic, but the present invention is not limited thereto. That is, it is possible to implement the present invention by determining whether the MTC terminal supports the essential MTC characteristic in the MTC MME and determining whether to maintain the registration. At this time, a criterion for determining whether to maintain registration with the MTC MME in the MTC terminal can be set by an external server.

7 is a block diagram showing a configuration of a wireless communication system according to a second embodiment of the present invention.

7, the wireless communication system of the present embodiment includes a policy server 700, a user terminal 710, a base station 720, a mobility management entity 730, a home subscriber server 740, a serving gateway 750 and a packet data network gateway 760. The configuration of the user terminal 710, the base station 720, the mobility management entity 730, the home subscriber server 740, the serving gateway 750, and the packet data network gateway 760 in the wireless communication system of this embodiment, Since the function is similar to the above-described embodiment, detailed description will be omitted.

The policy server 700 determines the MTC policy for each MTC terminal in the user terminal 710. At this time, the policy server 700 delivers the MTC policy to the MTC terminal through the base station 720 to set the MTC policy. Here, the MTC policy includes a required MTC characteristic for the MTC terminal, a selected MTC characteristic, and whether or not the registration with the wireless network that does not support the essential MTC characteristic in the MTC terminal can be maintained. The policy server 700 may be, for example, an Open Mobile Alliance-Device Management (OMA-DM) server.

8 is a flowchart illustrating a connection procedure in a wireless communication system according to a second embodiment of the present invention. In this case, in this embodiment, the MTC terminal will communicate with the policy server or the MTC MME through the base station, but this will be omitted.

Referring to FIG. 8, the connection procedure in the wireless communication system of the present embodiment starts from the policy server 700 setting the MTC policy in the MTC terminal 711 in step 811. At this time, the MTC policy includes a mandatory MTC characteristic for the MTC terminal 711, a selected MTC characteristic, and whether or not the registration with the wireless network that does not support the essential MTC characteristic in the MTC terminal 711 can be maintained. Thereafter, the MTC terminal 711 requests registration to the mobility management entity 730 in step 813. That is, the MTC terminal 711 selects any one of the wireless networks accessible from the base station 720 and requests registration to the mobility management entity 730 of the corresponding wireless network. Here, the MTC terminal 711 can store the carrier information of each of the wireless networks accessible by the base station 720. At this time, the MTC terminal 711 can request registration to the MTC MME 731 and request registration to the normal MME (not shown). And the MTC terminal 711 may transmit unique subscription identification information to the mobility management entity 730. [

When registration is requested in the MTC terminal 711, the MTC MME 731 requests the subscriber information of the MTC terminal 711 from the home subscriber server 740 in step 815. At this time, the MTC MME 731 can request the subscription information of the MTC terminal 711 by reporting the location of the MTC terminal 711 to the home subscriber server 740. Here, the MTC MME 731 transmits the subscription identification information of the MTC terminal 711 to the home subscriber server 740. When the subscription information of the MTC terminal 711 is requested, the home subscriber server 740 responds with the subscription information of the MTC terminal 711 to the MTC MME 731 in step 817. At this time, the home subscriber server 740 updates the location of the MTC terminal 711 and notifies the MTC MME 731 of the location of the MTC terminal 711, thereby transmitting the subscription information of the MTC terminal 711. That is, the home subscriber server 740 retrieves the subscription information of the MTC terminal 711 using the subscription identification information, and transmits the subscription information to the MTC MME 731. At this time, the subscription information includes MTC subscription information for the MTC terminal 711. Here, the MTC subscription information includes the required MTC characteristic and the selected MTC characteristic of the corresponding MTC terminal 711.

Next, when the subscription information of the MTC terminal 711 is answered, the MTC MME 731 permits the MTC terminal 711 to register it in step 819. [ At this time, the MTC MME 731 stores supporting MTC characteristics that can be supported in the corresponding wireless network. Upon allowing the MTC terminal 711 to register the MTC terminal 711, the MTC MME 731 notifies the MTC terminal 111 of the supported MTC characteristics.

Next, if registration is permitted in the mobility management entity 730, the MTC terminal 711 determines in step 821 whether the mobility management entity 730 supports MTC. That is, the MTC terminal 711 judges whether the mobility management entity 730 is the MTC MME 731 or not. At this time, the MTC terminal 711 determines whether or not the mobility management entity 730 has notified the MTC characteristic, thereby determining whether or not the mobility management entity 730 is the MTC MME 731. Here, if the MTC characteristic has been notified, the MTC terminal 711 determines that the mobility management entity 730 is the MTC MME 731. If the MTC characteristic has not been notified, the MTC terminal 711 determines that the mobility management entity 730 is the normal MME.

Next, in step 823, the MTC terminal 711 determines whether to use the supported MTC characteristic of the MTC MME 731. At this time, the MTC terminal 711 determines whether to use the supported MTC characteristic according to the MTC policy. That is, the MTC terminal 711 judges whether or not the required MTC characteristic conforms to the supported MTC characteristic in accordance with the MTC policy. Here, if the supporting MTC characteristic includes the required MTC characteristic, the MTC terminal 711 determines that the supporting MTC characteristic is to be used. If the supported MTC characteristic does not include the required MTC characteristic, the MTC terminal 711 determines whether to maintain registration with the MTC MME 731 according to the MTC policy. Here, if it is determined that registration should be maintained, the MTC terminal 711 determines that the supported MTC characteristic is to be used. If it is determined that registration should not be maintained, the MTC terminal 711 determines that the supported MTC characteristic is not to be used.

Next, if it is determined in step 823 that the supported MTC characteristic is to be used, the MTC terminal 711 performs MTC through the MTC MME 731 in step 825. At this time, if the supporting MTC characteristic includes the required MTC characteristic, the MTC terminal 711 can perform the MTC using the essential MTC characteristic. Here, the MTC terminal 711, in addition to the essential MTC characteristic, can utilize the selected MTC characteristic in the supported MTC characteristic of the MTC MME 731 to perform the MTC. Or if the supporting MTC characteristic does not include the required MTC characteristic, the MTC terminal 711 can perform the MTC using the supported MTC characteristic of the MTC MME 731. [ Here, the MTC terminal 711 can utilize the MTC characteristic of the MTC 731 to grasp the selected MTC characteristic and perform the MTC.

On the other hand, if it is determined in step 823 that the supported MTC characteristic is not to be used, the MTC terminal 711 cancels the registration with the MTC MME 731 in step 833.

FIG. 9 is a flowchart showing an operation procedure of the mobility management entity in FIG. Here, it is assumed that the mobility management entity is the MTC MME in the present embodiment. In addition, in the present embodiment, when the mobility management entity is the normal MME, the operation procedure of the normal MME is similar to the above-described embodiment, and therefore, detailed description thereof will be omitted.

Referring to FIG. 9, the operation procedure of the mobility management entity 730 in this embodiment starts with the MTC MME 731 detecting the registration request of the MTC terminal 711 in step 911. At this time, the MTC MME 731 grasps the subscription identification information of the MTC terminal 711. In step 913, the MTC MME 731 requests subscription information of the MTC terminal 711 to the home subscriber server 740. At this time, the MTC MME 731 can request the subscription information of the MTC terminal 711 by reporting the location of the MTC terminal 711 to the home subscriber server 740. Here, the MTC MME 731 transmits the subscription identification information of the MTC terminal 711 to the home subscriber server 740.

If the subscriber information of the MTC terminal 711 is answered in the home subscriber server 740, the MTC MME 731 detects this in step 915 and permits the registration in the MTC terminal 711 in step 917. At this time, the MTC MME 731 notifies the MTC terminal 711 of the supported MTC characteristics. Thereafter, the MTC MME 731 determines in step 919 whether the registration with the MTC terminal 711 is released. At this time, if the MTC terminal 711 requests the deregistration, the MTC MME 731 detects this and permits the deregistration.

Finally, if registration cancellation is not detected in step 919, the MTC MME 731 performs MTC with the MTC terminal 711 in step 921. [ At this time, if the supporting MTC characteristic includes the required MTC characteristic, the MTC MME 731 can support the essential MTC characteristic for the MTC terminal 711 to perform the MTC. Here, in order to optimize the MTC, the MTC MME 731 can further support the selective MTC characteristic for the MTC terminal 711 in the supported MTC characteristic. Or the MTC MME 731 may support the MTC feature for the MTC terminal 711 to perform the MTC. Here, for the optimization of the MTC, the MTC MME 731 can grasp and support the selective MTC characteristic for the MTC terminal 711 in the supported MTC characteristic.

10 is a flowchart showing the operation procedure of the user terminal in FIG. Here, it is assumed that the user terminal is an MTC terminal in the present embodiment.

Referring to FIG. 10, the operation procedure of the user terminal 110 in this embodiment starts from the MTC terminal 711 setting the MTC policy in step 1001. FIG. At this time, the MTC terminal 711 sets the MTC policy according to the command of the policy server 700. [ Here, the MTC policy includes a required MTC characteristic for the MTC terminal 711, a selected MTC characteristic, and whether or not the registration with the wireless network that does not support the essential MTC characteristic in the MTC terminal 711 can be maintained. Thereafter, the MTC terminal 711 selects the mobility management entity 130 in step 1003. That is, the MTC terminal 711 selects the mobility management entity 730 by selecting any one of the wireless networks accessible at the base station 720. At this time, the MTC terminal 711 can store the carrier information of each of the wireless networks accessible by the base station 720. In step 1005, the MTC terminal 711 requests registration to the mobility management entity 730. At this time, the MTC terminal 711 can request registration to the MTC MME 731 and request registration to the normal MME. And the MTC terminal 711 may transmit unique subscription identification information to the mobility management entity 730. [

If registration is permitted in the mobility management entity 730, the MTC terminal 711 detects this in step 1007 and determines whether the mobility management entity 730 supports the MTC in step 1009. [ That is, the MTC terminal 711 judges whether the mobility management entity 730 is the MTC MME 731 or not. At this time, the MTC terminal 711 determines whether or not the mobility management entity 730 has notified the MTC characteristic, thereby determining whether or not the mobility management entity 730 is the MTC MME 731. Here, if the MTC characteristic has been notified, the MTC terminal 711 determines that the mobility management entity 730 is the MTC MME 731. If the MTC characteristic has not been notified, the MTC terminal 711 determines that the mobility management entity 730 is the normal MME.

If it is determined in step 1009 that the mobility management entity 730 supports the MTC, the MTC terminal 711 determines whether to use the supported MTC characteristic of the MTC MME 731 in step 1011. At this time, the MTC terminal 711 determines whether to use the supported MTC characteristic according to the MTC policy. That is, the MTC terminal 711 judges whether or not the required MTC characteristic conforms to the supported MTC characteristic in accordance with the MTC policy. Here, if the supporting MTC characteristic includes the required MTC characteristic, the MTC terminal 711 determines that the supporting MTC characteristic is to be used. If the supported MTC characteristic does not include the required MTC characteristic, the MTC terminal 711 determines whether to maintain registration with the MTC MME 731 according to the MTC policy. Here, if it is determined that registration should be maintained, the MTC terminal 711 determines that the supported MTC characteristic is to be used. If it is determined that registration should not be maintained, the MTC terminal 711 determines that the supported MTC characteristic is not to be used.

Finally, if it is determined in step 1011 that the supported MTC characteristic is to be used, the MTC terminal 711 performs MTC through the mobility management entity 730, i.e., the MTC MME 731 in step 1013. At this time, if the supporting MTC characteristic includes the required MTC characteristic, the MTC terminal 711 can perform the MTC using the essential MTC characteristic. Here, the MTC terminal 711, in addition to the essential MTC characteristic, can utilize the selected MTC characteristic in the supported MTC characteristic of the MTC MME 731 to perform the MTC. Or if the supporting MTC characteristic does not include the required MTC characteristic, the MTC terminal 711 can perform the MTC using the supported MTC characteristic of the MTC MME 731. [ Here, the MTC terminal 711 can utilize the MTC characteristic of the MTC 731 to grasp the selected MTC characteristic and perform the MTC.

On the other hand, if it is determined in step 1009 that the MTC is not supported or if it is determined in step 1011 that the supported MTC characteristic is not to be used, the MTC terminal 711 cancels the registration with the mobility management entity 730 in step 1021. [ At this time, the MTC terminal 711 can store the carrier information of the corresponding wireless network in correspondence with the mobility management entity 730 for later reference in selecting the mobility management entity 730. [ In other words, the MTC terminal 711 can store the carrier information of the corresponding wireless network as selection prohibition information, so that the MTC terminal 711 does not request registration to the mobility management entity 730 thereafter.

On the other hand, if registration is not permitted in the mobility management entity 730 in step 1007 and registration is rejected in the mobility management entity 730, the MTC terminal 711 detects this in step 1037 and waits for the retry waiting time . At this time, the MTC terminal 711 can wait according to the previously stored retry waiting time. Or the MTC terminal 711 may wait for a retry wait time as reported by the mobility management entity 730. [ After that, the MTC terminal 711 reselects the mobility management entity 730 in step 1041, and proceeds to step 1005. The MTC terminal 711 repeats steps 1005 through 1041 at least once.

At this time, the MTC terminal 711 may previously store the carrier information of each of the wireless networks accessible by the base station 720, and may be used to select another mobility management entity 730. Or the MTC terminal 711 may use the carrier information of each of the other wireless networks advertised in the MTC MME 731 to select another mobility management entity 730. For example, if the provider information of each of the wireless networks is stored in advance, the MTC terminal 711 uses it to select another mobility management entity 730, otherwise, as instructed by the MTC MME 731 Another mobility management entity 730 may be selected. Here, the MTC terminal 711 can select another mobility management entity 730 by referring to previously stored selection prohibition information. In other words, the MTC terminal may select the other mobility management entity 730 after excluding the selection prohibition information from the carrier information of each of the other wireless networks stored in advance or notified by the MTC MME 731.

According to the present embodiment, in the wireless communication system, the user terminal 710 can be efficiently connected to the mobility management entity 730 corresponding to the additional function. That is, the MTC terminal 711 can be efficiently connected to the MTC MME 731 supporting the required MTC characteristic. Accordingly, in the wireless communication system, the MTC MME 731 can more efficiently support the MTC, and the MTC terminal 711 can perform the MTC more efficiently.

It should be noted that the embodiments of the present invention disclosed in the present specification and drawings are only illustrative examples of the present invention and are not intended to limit the scope of the present invention. That is, it will be apparent to those skilled in the art that other modifications based on the technical idea of the present invention are possible.

Claims (1)

A method for transmitting and receiving signals in a mobility management entity (MME) of a communication system,
Receiving a first request message from a terminal;
Transmitting a second request message related to the terminal to the home subscriber server based on the first request message;
Receiving subscription information corresponding to the second request message from the home subscriber server, the subscription information including time information related to a tracking area update (TAU) of the terminal; And
And transmitting a response message including time information related to the TAU to the terminal.

Images