Technical field
[0001]
　The present invention is a mobile communication system, a call process of the terminal and the terminal, for example, mobile communication systems configuring a ISR (Idle-mode Signaling Reduction), for a termination process of the terminal and the terminal.
Background technique
[0002]
　In 3GPP defining a standard technology for mobile network system (3rd Generation Partnership Project), EPC (Evolved Packet Core) is defined as the next-generation mobile network system. EPC, in addition to the radio access network is referred to as the second generation and third generation, which is a network system that also accommodates LTE (Long Term Evolution) access network.
[0003]
　Here will be described processing of reception packets in EPC. Non-Patent Document 1, processing of reception packets when UE indicating a user terminal (User Equipment) is in an idle state is disclosed. UE and is idle state is a state where the UE is not connected to the EPC. In other words, a state in which the radio bearer between the UE and the EPC is disconnected. In this case, if the incoming packet is generated with respect to UE, a bearer management apparatus S-GW (Serving Gateway) is, MME that manages UE (Mobility Management Entity) or SGSN (Serving GPRS Support Node ) relative to, and transmits an incoming notification message. Incoming MME or SGSN has received the notification message is a base station Paging message to invoke the UE eNB (evolved Node B) or to send to the NodeB. eNB or NodeB has received the Paging message carries the Paging processing for a plurality of UE which exists in the area where the own device is managed. Here, a is the UE calls to the target, and sends a response message to the eNB or NodeB, is connected to the EPC.
[0004]
　Thus, when the EPC incoming packets for the UE in an idle state of not connecting occurs also, by calling UE from the network side, it can be performed UE and data communications.
[0005]
　Further, UE, SGSN, MME, and the S-GW, if ISR is enabled, if it is in other words activated (activate), S-GW transmits an incoming notification message to the MME and SGSN. In this case, both the MME and the SGSN performs a Paging processing for UE. That is, if ISR is enabled, and the radio access network is referred to as the second generation and third generation, both in LTE access network, Paging processing is executed.
[0006]
　Here, the state ISR is valid, a state in which the UE is simultaneously ATTACH two devices SGSN and MME. By ISR is enabled, UE includes a radio access network is referred to as the second generation and third generation, even when the movement between the LTE access network, UE is, TAU (Tracking Area Update) and without transmitting RAU to (Routing Area Update), UE mobility management is performed.
CITATION
Non-Patent Document
[0007]
非特許文献1 : 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 12), 3GPP TS 23.401 V12.0.0 (2013-03), clauses 5.3.4.3, 5.3.3.2
Summary of the Invention
Problems that the Invention is to Solve
[0008]
　However, in the processing of reception packets disclosed in Non-Patent Document 1, problems occur as described below. Usually, if the MME UE moves out of the location registration area managed, UE transmits a location registration request message to the new MME which manages the location registration area of ​​the destination (Tracking Area Update Request). The new MME which has received the location registration request message, performs a location registration process of the UE. When location registration processing in the new MME is completed, UE is in a state of being registered in the new MME which manages the location registration area of ​​the destination.
[0009]
　Here, even after the UE has transmitted the location registration request message, when the incoming packet is generated for the UE before the moving processing in the new MME is completed, S-GW is located in front of the UE moving to send an incoming call notification message to the MME, which has been managing. MME which has received the incoming call notification message is transmits a Paging message to the base station under, for UE incoming object is moved to the area where the new MME manages, you can not call the call recipient of the UE . That, UE if the packet call has occurred while moving with the change of MME, UE has a problem that can not be accepted incoming packet.
[0010]
　An object of the present invention, the mobile communication system mobile terminal device is controlled so as to be able to accept reliably incoming packet that occurs when moving, it is to provide an incoming call process of the terminal and the terminal.
Means for Solving the Problems
[0011]
　Mobile communication system according to a first aspect of the present invention includes a terminal (UE), a MME (Mobility Management Entity), and SGSN (Serving GPRS Support Node), a mobile communication system including a SGW (Serving Gateway) Te, and the terminal, and the MME, in said SGSN, if ISR is enabled, the SGW, the the MME and the SGSN transmits a Downlink Data Notification message, other different from said MME and the SGSN when receiving the Modify Bearer Request message from the MME or other SGSN, the Modify Bearer Request message other MME or that transmitted the It means for retransmitting the other SGSN only to the Downlink Data Notification, those comprising a.
[0012]
　Terminal according to the second aspect of the present invention is a terminal for use in a mobile communication system (UE), ISR is enabled in the terminal, the terminal MME (Mobility Management Entity) and SGSN (Serving GPRS Support registered Node), when the MME is changed, after the old MME and the SGSN before change has received the terminal for Downlink Data Notification (DDN) messages, only the new MME after changing but when receiving the retransmitted the Downlink Data Notification message, a paging message to be caused by the Downlink Data Notification message the new Transmitted from ME to the base station, in which and a receiving means for receiving paging from the base station.
[0013]
　The third call method of a terminal according to an aspect of the present invention is a call method of a terminal for use in a mobile communication system (UE), wherein it ISR is enabled in the terminal, the terminal MME (Mobility Management Entity) and SGSN registered (Serving GPRS Support Node), when the MME is changed, after the old MME and the SGSN before change has received the terminal for Downlink Data Notification (DDN) messages, change paging menu only new MME after, once receiving the retransmitted the Downlink Data Notification message, due to the Downlink Data Notification message Sage is transmitted to the base station from the new MME, in which to receive paging from the base station.
Effect of the Invention
[0014]
　The present invention, a mobile communication system in which mobile terminal device is controlled so as to be able to accept reliably incoming packet that occurs when moving, it is possible to provide an incoming call process of the terminal and the terminal.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015]
FIG. 1 is a configuration diagram of a communication system in the first embodiment.
FIG. 2 is a configuration diagram of a mobile communication system defined in 3GPP according to the second embodiment.
3 is a configuration diagram of a mobile communication system defined in 3GPP according to the second embodiment.
4 is a configuration diagram of a mobile communication system defined in 3GPP according to the second embodiment.
5 is a configuration diagram of a mobile communication system defined in 3GPP according to the second embodiment.
6 is a configuration diagram of a SGW according to the second embodiment.
7 is a diagram for explaining the operation when ISR according to the second embodiment is effective.
8 is a block diagram of a UE according to the second embodiment.
[Figure 9] UE according to the second embodiment is a diagram showing the flow of connection processing when connecting to the mobile communication system.
UE according to [10] Embodiment 2 is a diagram showing the flow of connection processing when connecting to the mobile communication system.
11 is a diagram showing the flow of processing when the packet arrival occurs against UE according to the second embodiment.
12 is a diagram showing the flow of processing when the packet arrival occurs against UE according to the third embodiment.
DESCRIPTION OF THE INVENTION
[0016]
　(Embodiment 1)
　Hereinafter, with reference to the drawings will be described embodiments of the present invention. The configuration example of a communication system according to a first embodiment of the present invention will be described with reference to FIG. Communication system of Figure 1, the bearer management unit 10, the mobility management unit 20, and a mobile management device 30 and the mobile terminal device 40. Mobile management device 20 manages the position of the mobile terminal residing in the location registration area 21. Mobile management device 30 manages the position of the mobile terminal residing in the location registration area 31. Further, in FIG. 1, the mobile terminal device 40 shows a state of moving from the position registration area 21 to a location registration area 31. In this drawing, the radio base station that performs mobile terminal device 40 and the wireless communication is omitted. Mobile terminal device 40, by moving from the position registration area 21 to a location registration area 31, the mobile management device for managing the mobile terminal device 40 changes from the mobile management device 20 to the mobile management device 30. Mobile management device 30 notifies that the movement of the mobile terminal device 40 to the bearer management unit 10 has completed the registration process of the mobile terminal device 40 is completed.
[0017]
　Next, configuration examples of a bearer management unit 10. Bearer management unit 10 includes a reception control unit 11. Here, the mobile terminal device 40 is moved from the location registration area 21 to a location registration area 31, before the registering process of the mobile terminal device 40 is completed in the mobile management device 30, packet arrival occurs to the mobile terminal device 40 case will be described. In such case, receiving controller 11, even if incoming call to the mobile terminal device 40 is generated, until notified that the movement of the mobile terminal 40 from the mobility control apparatus 30 is completed, incoming call to the mobile terminal device 40 the process is suspended. Receiving controller 11, after being informed that the movement of the mobile terminal 40 from the mobility control apparatus 30 has been completed, and restarts the call processing for the mobile terminal device 40. For example, receiving controller 11, when performing the incoming call processing for the mobile management device 20, the mobile terminal apparatus 40 may acquire the information that it is moving from the mobile management device 20.
[0018]
　And incoming call processing, for example, to notify an incoming message to the mobile management device that manages the mobile terminal 40, the mobile terminal device 40 is a process for transmitting data addressed to the mobile terminal device 40. Incoming process and the interruption, for example, receiving controller 11 detects that the mobile terminal device 40 is moving, and transmits data to the mobile terminal device 40 and the destination (user data) to the mobile terminal device 40 stop making a transition to the process, after the completion of the movement the mobile terminal apparatus 40 is notified, the mobile terminal device 40 may be to transmit the data addressed to the mobile terminal device 40. Or, receiving controller 11, the mobile management device 30 to the completion of the displacement of the mobile terminal apparatus 40 is notified, it may be to stop sending incoming messages to the mobile management device. And during the movement of the mobile terminal device 40, for example, the mobile terminal device 40 from the transmission of the location registration request message to the mobile management device 30 for managing the location registration area 31 of the moving destination, moving management device 30 is bearer management device the completion of the displacement of the mobile terminal apparatus 40 to 10 may be up to notify a message indicating.
[0019]
　Incoming call processing and interrupting is to suspend the call processing, to pause the incoming call processing, to abort the incoming process assuming resumption of incoming process, or a like to hold the execution of the incoming call processing it may be.
[0020]
　As described above, by using a communication system of FIG. 1, the mobile terminal device 40, a packet call to the mobile terminal device 40 is generated in the midst of the movement with the change of the mobility management device that manages location even when the mobile terminal device 40 can accept a packet communication. In other words, the bearer management unit 10, after the movement completion from the mobile management device 30 for managing the location registration area of ​​the destination is notified, it is possible to resume the incoming call processing for the mobile terminal device 40. Therefore, even when the packet arrival occurs when the moving processing of the mobile terminal apparatus 40 has not been completed, the bearer management unit 10 can notify the incoming packet to the mobile terminal device 40.
[0021]
　(Second Embodiment)
　Subsequently, a configuration example of a communication system according to Embodiment 2 of the present invention will be described with reference to FIG. In this figure, as the communication system, the mobile communication system is defined in the 3GPP will be described. Communication system of FIG. 2 includes a PGW (Packet Data Network GateWay) 75 , SGW (Serving GateWay) 15, MME25, MME35, UE45, eNB55 and ENB65.
[0022]
　UE45 is a communication device which is defined as a mobile terminal device in 3GPP. UE45 may be a cellular phone, a smart phone, a personal computer or the like having a tablet terminal or communication function. Further, UE45 is, M2M performing autonomously communication (Machine To Machine) may be a device. M2M device, e.g., a vending machine having a communication function may be a device frequently moves is small as such appliances, it may be a clock or the like that the user wear.
[0023]
　eNB55 and eNB65 are node device is specified as a base station in 3GPP. eNB55 and eNB65 each form a wireless communication area and communicates with a UE device itself within the wireless communication area to be managed.
[0024]
　PGW75 is a node device located at the boundary of the mobile communication system and an external network. PGW75 the data transmitted from the external network, and transmits to the node devices in the mobile communication system. PGW75 sets communication bearer between SGW15. Communication bearer, for example, may be referred to as a communication path or a communication path or the like. PGW75 the data transmitted from the external network, and transmits to the SGW15 via the communication bearer.
[0025]
　Bearer management unit 10 in FIG. 1 is defined as SGW15 in 3GPP. SGW15, when packets incoming call to UE45 is notified, and notifies the incoming message to MME25 or MME35. Furthermore, SGW15, to the eNB55 or eNB65 which communicates with UE45, transmits data addressed to UE45.
[0026]
　Mobile management device 20 and 30 in FIG. 1 is defined in 3GPP as MME25 and MME35. MME25 and MME35 are respectively set the location registration area managed by the location of the UE. Multiple eNB may be arranged to MME25 and location registration area, each of which manage MME35. That is, the position registration area may comprise a plurality of radio communication area eNB forms.
[0027]
　UE45, when moved to the location registration area stipulated by MME35 from the location registration area MME25 stipulated, transmits a location registration request message to MME35. MME35 receives the location registration request message transmitted from the UE45, to move processing of UE45. Moving process UE45, for example, MME35 is a process of registering UE45 as a target device to be managed. Furthermore, MME35 receives the location registration request message transmitted from the UE45, to MME25 which manages the location registration area before the movement of the UE45, a message notifying that UE45 has moved to the location registration area to the provisions of the MME35 Send. UE45 is to MME35, it may transmit the location registration request message including an identifier of MME25 which manages the location registration area before the movement. Thus, MME35 can detect the MME25 which manages the location registration area before the movement of UE45. MME25, by being notified of the message from MME35, UE45 is, it is possible to detect that it has moved to a location registration area to the provisions of MME35.
[0028]
　MME35 has completed moving process UE45 transmits a message indicating that the process of moving UE45 to SGW15 is completed. SGW15, if packet arrival occurs UE45, until a message indicating that the process of moving UE45 from MME35 has been completed is transmitted, transmits an incoming notification message to MME25.
[0029]
　MME25, after receiving a message notifying the movement of UE45 from MME35, there is a case of receiving an incoming notification message for UE45 from SGW15. In this case, MME25 sends a message to inform the SGW15, UE45 has moved.
[0030]
　SGW15 is by receiving a message notifying that the UE45 transmitted from MME25 has moved, to detect that the UE45 is moving with a change in the MME. SGW15 is, UE45 if it detects that it is moving with a change of the MME, temporarily stores data addressed to the buffer UE45. SGW15, when a message indicating the completion of the displacement of the UE45 from MME35 is notified, and transmits an incoming notification message for UE45 to MME35. Thereafter, SGW15 is to UE45, transmits data addressed to UE45.
[0031]
　In the above description, the mobile management device 20 and 30 has been described as MME25 and 35, the mobile management device 20 and 30 may be SGSN27 and 37 as shown in FIG. SGSN27 and 37 are node device which manages the location of the UE for communicating with a radio access network called 2G or 3G in 3GPP. SGSN27 and 37 is connected to a 2G / 3G radio network controller 57 and 67 in the radio access network called 2G or 3G. 2G or 2G / 3G radio network controller in the radio access network called 3G, for example RNC may be referred to as (Radio Network Controller). Configuration shown in Figure 3 replaces the MME25 and 35 to SGSN27 and 37, but substituting eNB55 and 65 to 2G / 3G radio network controller 57 and 67 is similar to FIG.
[0032]
　Furthermore, SGW15, as shown in FIG. 4, may be connected to the MME25 and SGSN37. That, SGW15 may be arranged in a system MME and SGSN are mixed. Configuration shown in Figure 4 replaces the MME35 in Figure 2 to SGSN37, but substituting eNB65 to 2G / 3G radio network controller 67, the same as that of FIG. 4, UE45 is from location registration area MME25 stipulated shows how to move to the position registration area SGSN37 stipulated. Further, as shown in FIG. 5, UE45 is from location registration area SGSN27 stipulated, even when moved to the location registration area MME35 stipulated operates similarly to FIG.
[0033]
　Here, with reference to FIG. 4, UE45, MME25, SGSN37, and in SGW15, ISR is valid, further, SGSN37 If the already completed the location registration processing of the UE45, i.e., is SGSN37, manages will be described have completed the process of registering UE45 as the target device. In this case, UE45 is also moved to the location registration area SGSN37 stipulated, UE45 is not sending a location registration request message to SGSN37. Location registration request message may be, for example, a Routing Area Update Request message.
[0034]
　Next, with reference to FIG. 5, UE45, SGSN27, MME35, and in SGW15, ISR is valid and further, MME35 If the already completed the location registration processing of the UE45, will be described. In this case, UE45 is also moved to the location registration area MME35 stipulated, UE45 is not sending a location registration request message to MME35. Location registration request message may be, for example, a Tracking Area Update Request message.
[0035]
　Next, an example of the configuration of the SGW15 according to a second embodiment of the present invention will be described with reference to FIG. SGW15 includes a reception control unit 16 and the data storage unit 17. Receiving controller 16 is the same as the reception control unit 11 of FIG. 1.
[0036]
　Receiving controller 16, when the message informing the mobile from MME25 which manages the location registration area before the movement of the UE45 the UE45 is transmitted, and stores the data temporarily storing section 17 the data addressed to UE45. Furthermore, receiving controller 16, when a message notifying that the movement of the UE45 from MME35 which manages the location registration area of ​​the destination UE45 is completed is transmitted, transmits the incoming message to UE45 to MME35. Furthermore, receiving controller 16, the radio bearer is set between the UE45 and ENB65, transmits the data stored in the data storage unit 17 to UE45 through ENB65.
[0037]
　Further, receiving controller 16, UE, MME, SGSN, and SGW supports processing operation in the case of constituting the ISR. For example, UE, if MME, SGSN, and the SGW constitutes the ISR, receiving controller 16 sends the incoming message to both the MME and SGSN which the UE is registered.
[0038]
　Next, a configuration example of a communication system according to Embodiment 2 of the present invention will be described with reference to FIG. Communication system of FIG. 7 includes a SGW15, MME25, MME35, SGSN27 and UE45. In previous movement of UE45, MME25, SGSN27 and UE45 are, ISR is to be effective. Further, FIG. 7, with the movement of the UE45, MME which manages the UE45 have shown that it is changed from MME25 to MME35. In addition, SGSN27 to manage the UE45 is not to be changed. Even after the movement of the UE45, MME35, SGSN27 and UE45 are, ISR is to be effective.
[0039]
　UE45 before moving, and when ISR is enabled, SGW15 transmits the Downlink Data Notification message to MME25 and SGSN27 the incoming call occurs for UE45. Here, the SGW15, upon receiving the Modify Bearer Request message from a different MME35 and MME25, SGW15 retransmits the Downlink Data Notification message only to MME35.
[0040]
　SGW15 by sending a Downlink Data Notification message only to MME35, it is possible to avoid paging process in SGSN27.
[0041]
　Further, in FIG. 7, as with MME which manages the UE45 is, an example has been described of a case that has changed from MME25 to MME35, which is changed from MME25 may SGSN that manages the UE45 is changed to MME35 it is. Even in this case, by the SGSN after the change transmits a Modify Bearer Request message to the SGW15, SGW15 retransmits the Downlink Data Notification message only to SGSN after the change. Thereby, it is possible to avoid paging in MME25.
[0042]
　Subsequently, with reference to FIG. 8, illustrating an example of the configuration of UE45 according to the second embodiment of the present invention. UE45 includes a 2G / 3G communication unit 46, LTE communication unit 47, a packet communication unit 48 and the mobility management unit 49.
[0043]
　2G / 3G communication unit 46, the 2G / 3G radio network controller, receiving a signal according to the paging. That, 2G / 3G communication unit 46 executes processing in response to the paging performed in 2G / 3G radio network controller. In other words, 2G / 3G communication unit 46, once the page from the 2G / 3G radio network controller, executes processing in response to the page. Further, 2G / 3G communication unit 46, when the SGSN that manages the UE45 is changed, starting the Routing Area Update procedure. Specifically, 2G / 3G communication unit 46 transmits the Routing Area Update message to the 2G / 3G radio network controller.
[0044]
　LTE communication unit 47, from the eNB, receives a signal with the paging. That, LTE communication unit 47 executes processing in response to the paging performed in eNB. In other words, LTE communication unit 47 is a page from the eNB, executes processing in response to the page. Also, LTE communication unit 47, when the MME that manages the UE45 is changed, starting the Tracking Area Update procedure. Specifically, LTE communication unit 47 transmits the Tracking Area Update message to the eNB.
[0045]
　The packet communication unit 48 generates packet data to be transmitted via the 2G / 3G communication unit 46 or the LTE communication unit 47. Or, the packet communication unit 48 performs the reception processing of the packet data received via the 2G / 3G communication unit 46 or the LTE communication unit 47.
[0046]
　Mobility management unit 49, performs the mobility management of UE45. For example, the mobility management unit 49 manages the current Tracking Area or Routing Area of ​​UE45. Mobility management unit 49, when the Tracking Area or Routing Area of ​​UE45 is changed, the 2G / 3G communication unit 46 or the LTE communication unit 47, an instruction to start Routing Area Update procedure or Tracking Area Update procedure.
[0047]
　Subsequently, the flow of connection process to the mobile communication system of the UE according to the second embodiment of the present invention will be described with reference to FIG. First, UE45, when the power switch power is depressed is turned by the user, as the location registration request message to the ENB55, transmits an Attach Request message (S11). Then, ENB55 transmits an Attach Request message sent from the UE45 to MME25 (S12). MME25 receives the Attach Request message, creating a location registration information for UE45. The location registration information, for example, including information or UE45 subscriber information indicates that the UE45 is located in a location registration area managed by the own device. UE45 subscriber information may be acquired from the subscriber information is arranged in the mobile communication system management apparatus (not shown). Subscriber information management apparatus, for example, is defined as a HSS (Home Subscriber Server) in 3GPP. Then, MME25 notifies the subscriber information SGW15 to UE45 using the Create Session Request message (S13). Then, SGW15, as a response message to the Create Session Request message and sends the Create Session Response message to the MME25 (S14). SGW15 by receiving the the Create Session Request message can identify the MME that manages the position of UE45. Further, by the Create Session Response message is sent, a session is established about the UE45 between MME25 and SGW15.
[0048]
　Then, MME25 receives the the Create Session Response message to ENB55, as a response message Attach Request message, transmits an Attach Accept message (S15). MME25 by sending an Attach Accept message, completes the registration process of UE45. Completion of the registration process of the UE45, namely, is the same as it has completed the process of moving the UE45. Then, ENB55 transmits an Attach Accept message to UE45 (S16).
[0049]
　By UE45 receives Attach Accept message, UE45 is in a state connected to the mobile communication system. UE45 connects to the mobile communication system state may be referred to as a state where UE45 has Attach to the mobile communication system.
[0050]
　In the above description, a description of the flow of processing when the power source of the UE45 is turned on, even if you change the location registration area visited by the UE45, in order to create a location registration information in the new MME similar processing is executed. UE45, if the location registration area visited by the change, sends a Tracking Area Update Request message instead of the Attach Request message. Further, MME25 and SGW15 transmit and receive Modify Bearer Request / Modify Bearer Response message instead of Create Session Request / Create Session Response message.
[0051]
　Subsequently, with reference to FIG. 10, description will be given of a flow of connection process to the mobile communication system of the UE according to the second embodiment of the present invention. Figure 10 is a eNB55 and eNB65 in Figures 9 and 2G / 3G radio network controller 57 and 2G / 3G radio network controller 67. Further, FIG. 10 is a MME25 and MME35 9 and SGSN27 and SGSN37. Step S101 ~ S106 in FIG. 10 will be omitted and a detailed description for steps S11 ~ 16 to be similar in FIG.
[0052]
　Then, UE45 according to the second embodiment of the present invention will be described flow of processing when the packet arrival occurs for UE45 during that movement involving a change of MME with reference to FIG. Here, we assume that the process of FIG. 9 and FIG. 10 is completed, UE45 is to be located in the location registration area managed by MME25. Here, UE45, MME25, SGSN27, and between the SGW15, ISR may be constructed. In other words, UE45, between the MME25 and SGSN27, ISR may be effective.
[0053]
　First, UE45 transmits when it detects that it has moved from the location registration area managed by the MME25 to another location registration area, a Tracking Area Update Request message to eNB65 which manages a communication area of ​​the destination (S21). UE45, by receiving the broadcast information distributed from ENB65, may detect that the location registration area has been changed. That, UE45 includes a location registration area, which is distributed from eNB55 before the move, when the location registration area, which is distributed from eNB65 after the movement are different, may detect that the location registration area has been changed.
[0054]
　Then, ENB65 is to MME35 which manages the location registration area including the communication area of ​​the own device, transmits a Tracking Area Update Request message relating to UE45 (S23). At the same time, in order to communicate control messages between UE45 and MME35, it establishes the S1 Connection between eNB65 and MME35. Here, Tracking the Area Update Request message, and contains MME25 identifier was managing a location registration area before the movement of UE45.
[0055]
　Then, MME35, in order to acquire the location registration information UE45 from MME25, sends a Context Request message to request the transfer of the location registration information to the MME25 (S24). MME25 that by Context Request message to request the transfer of the location registration information UE45 from MME35 has been transmitted, it is possible to detect that the UE45 out location registration area where the own device manages moves. Furthermore, MME25 by receiving the Context Request message sent from MME35, it is possible to detect that the UE45 has moved to the position registration area managed by MME35.
[0056]
　Here, after the MME35 to MME25 Context Request message is transmitted in step S24, the packet arrival is reported for UE45 to SGW15 (S25). Packet arrival is notified to SGW15 via PGW75 from the external network.
[0057]
　SGW15, in the connection processing of FIG. 9, has been notified that the UE45 is located in the location registration area managed by MME25. Therefore, SGW15 transmits the Downlink Data Notification message to MME25 to notify the incoming packet against UE45 (S26). Further, during the UE45, MME25 and SGSN27, if ISR is constructed, in the connection processing of FIG. 10, SGW15 is also informed that the UE45 is located in the location registration area managed by the SGSN27 . Therefore, during the UE45, MME25 and SGSN27, if ISR is built, SGW15 transmits the Downlink Data Notification message to MME25 and SGSN27.
[0058]
　Then, MME25 has detected that UE45 by receiving the Context Request message in step S24 is moving. Therefore, MME25 is, UE45 is is moving, it sets the Cause indicating that can not be carried out temporarily the call processing of the UE45, and transmits the Downlink Data Notification Acknowledge message to SGW15 (S27). The Downlink Data Notification Acknowledge message, as a Cause set, Cause = Temporarily Rejected due to mobility is set. Cause = Temporarily Rejected due to mobility is the Cause, it shows that the information indicating the UE may not be able to be temporarily call processing in motion (Temporarily rejected) is set.
[0059]
　Here, SGW15 is, Cause = Temporarily Rejected due to the mobility receives a set Downlink Data Notification Acknowledge message, suspends the packet arrival process, Downlink Data Notification while continuing buffering packets destined for UE45 to start the timer (locally configured guard timer) to resend the message.
[0060]
　Then, MME25 performs an operation as a MME which manages the location registration area before the movement of the UE45 in Tracking Area Update Request message. That, MME25, as a response message Context Request message in step S24, sends a Context Response message to the MME35 (S28). MME which manages the location registration area before the movement of the UE45 may be referred to as Old side MME. Moreover, MME which manages the location registration area after movement of UE45 may be referred to as New side MME. MME25 notifies the MME35 the location registration information of the UE45 using Context Response message. MME35 sends a Context Acknowledge message to MME25 response message Context Response message (S29).
[0061]
　Then, MME35, in order to notify the switching of the session established between the MME25 and SGW15, sends a Modify Bearer Request message to the SGW15 (S30). Session established between the MME25 and SGW15 is a session established in step S13 and S14 in FIG. SGW15 by receiving the Modify Bearer Request message, detects that the moving process of the UE45 is completed in MME35. MME35 by sending an identifier that identifies the established session between the MME25 and SGW15 to SGW15, may notify the switching of the session established between the MME25 and SGW15. Identifier identifying the established session between the MME25 and SGW15 may be included in Context Response message in step S28.
[0062]
　Further, in step S30, MME35 indicates that ISR is valid, the information to be ISR activated set to Modify Bearer Request message may be transmitted.
[0063]
　SGW15 as a response message Modify Bearer Request message, transmits a Modify Bearer Response message to the MME35 (S31). At this time, SGW15 stops Downlink Data Notification Acknowledge message timer started upon receipt of a (locally configured guard timer) in step S27.
[0064]
　Then, MME35 receives the Modify Bearer Response message, as a response message of step S23, sends a Tracking Area Update Accept message to eNB65 (S32). Then, ENB65 transmits the transmitted Tracking Area Update Accept message to UE45 (S33).
[0065]
　Then, MME35 releases the S1 Connection between eNB65 the already established (S34).
[0066]
　Then, SGW15, in order to notify the incoming packet against the UE45, and transmits the Downlink Data Notification message to MME35 which manages the location registration area of ​​the destination UE45 (S35). That is, in step S35, in step S26, the transmission processing of the Downlink Data Notification message for MME25, will be performed on MME35 which manages the location registration area of ​​the destination UE45. Also MME35 and SGSN27 is a case where the enable ISR, MME35 by sending a Modify Bearer Request message to the SGW15, it is evident that the UE45 is present under ENB65. Therefore, SGW15 may perform transmit processing Downlink Data Notification message only to relative MME35. In other words, SGW15 is only for MME35, may be carried out retransmission processing Downlink Data Notification message. Note that step 35 has been described in the order in describing the process, step 35 than it is the operation of SGW15, Step 31 (Modify Bearer Response) may be performed immediately after the transmission. Then, MME35, in order to perform a call processing of the UE45, and sends a Paging message to eNB65 (S36), eNB65 performs Paging processing for the UE located in the communication area under (S37). In this way, UE45, after moving to a new location registration area can receive the incoming packet notification that occurs when moving a UE45.
[0067]
　Here, if the Downlink Data Notification Acknowledge message timer started upon receipt of a (locally configured guard timer) expires before receiving a Modify Bearer Request message in step S27, SGW15 ends the packet arrival process for UE45 it may be. Or, SGW15 sends to MME25 the Downlink Data Notification message again, it may be continued the packet arrival process.
[0068]
　Here, if the Downlink Data Notification Acknowledge message timer started upon receipt of a (locally configured guard timer) has expired without receiving the Modify Bearer Request message in step S27, SGW15 is a UE45 buffered destined packet may be to release the.
[0069]
　By using a communication system according to a second embodiment of the present invention described above, UE45 is in motion involving a change of MME, for UE45 while the process of moving UE45 is not completed in the new MME when the packet arrival occurs also, UE45 can receive packets normally incoming notification.
[0070]
　Further, when the MME35, SGSN27, and SGW15 is to enable ISR, SGW15 is by performing a process of transmitting Downlink Data Notification message only to MME35, it is possible to avoid the execution of the Paging processing in SGSN27.
[0071]
　Furthermore, as shown in FIG. 3, MME25 is replaced to SGSN27, MME35 is replaced to SGSN37, eNB55 replaces the 2G / 3G radio control apparatus 57, if the eNB65 is replaced to 2G / 3G radio network controller 67, Tracking Area Update Request message in step S21 and S23 are replaced by Routing Area Update Request message. Further, Tracking Area Update Accept message in step S32 and 33 are replaced by Routing Area Update Accept message. Further, S1 Connection release in step S34 is replaced by the Iu Connection release. Also MME25 and the SGSN37 is a case where the enable ISR (Idle-mode signaling reduction), SGSN37 by sending a Modify Bearer Request message to the SGW15, UE45 is existing under 2G / 3G radio network controller 67 it is evident that. Therefore, SGW15 may perform transmit processing Downlink Data Notification message only to relative SGSN37.
[0072]
　(Third Embodiment)
　Subsequently, with reference to FIG. 12, description will be given of a flow of connection process to the mobile communication system of the UE according to the third embodiment of the present invention. First, the packet arrival is reported for UE45 to SGW15 (S41). Then, SGW15 transmits the Downlink Data Notification message to MME25 (S42). Here, UE45, MME25, SGSN27, and between the SGW15, ISR is built. Therefore, SGW15 is adapted to transmit the Downlink Data Notification message to MME25, it transmits the Downlink Data Notification message against SGSN27.
[0073]
　Then, MME25 sends a Downlink Data Notification Acknowledge message to SGW15 (S43). In Figure 11, MME25 has been sent to Downlink Data Notification Acknowledge message set the Cause = Temporarily Rejected due to mobility, in step S43 in FIG. 12, not set the Cause = Temporarily Rejected due to mobility. At the time the MME25 receives the Downlink Data Notification message, MME25 is because not aware of the movement of the UE45.
[0074]
　Then, MME25, in order to perform a call processing of the UE45, and sends a Paging message to eNB55 (S44), eNB55 performs Paging processing for the UE located in the communication area under. (S45).
[0075]
　Then, UE45 transmits when it detects that it has moved from the location registration area managed by the MME25 to another location registration area, a Tracking Area Update Request message to eNB65 which manages a communication area of ​​the destination (S46). UE45, before Paging process is completed, transmits a Tracking Area Update Request message to ENB65. Or, UE45, before executing the Paging processing, sends a Tracking Area Update Request message to ENB65. That is, the Paging processing in step S45, since it is a state in which transmission and are interlaced Tracking Area Update Request message in step S46, while the Paging processing has not been completed, is performed sending Tracking Area Update Request message It was to be.
[0076]
　Following steps S47 ~ S50 to be executed is omitted step S23, S24, S28 and S29 and hence detailed similar description of Figure 11.
[0077]
　Then, MME35, in order to notify the switching of the session established between the MME25 and SGW15, sends a Modify Bearer Request message to the SGW15 (S51). SGW15 by receiving the Modify Bearer Request message, recognizes that was moved to UE45 to change the location registration area.
[0078]
　Step S52 ~ S58 are omitted steps S31 ~ S37 and hence detailed similar description of Figure 11. SGW15 In step S51, by recognizing that the UE45 has moved, in step S56, the MME35 which manages the location registration area of ​​the destination UE45, transmits the Downlink Data Notification message. At this time, SGW15 as in step S35 in FIG. 11, only the MME35, retransmits the Downlink Data Notification message. That, SGW15 also when ISR is effective in SGSN27 and MME35 Prefecture, does not retransmit the Downlink Data Notification message to SGSN27. Note that step 35 has been described in the order in describing the process, step 35 than it is the operation of SGW15, Step 31 (Modify Bearer Response) may be performed immediately after the transmission.
[0079]
　In the above example, the program may be stored using a non-transitory computer readable media of various types (non-transitory computer readable medium), it can be supplied to the computer. Non-transitory computer readable media include with various types of entities (tangible storage medium). Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tape, hard disk drive), magneto-optical recording medium (e.g. optical disk), CD-ROM (Read Only Memory), CD-R, CD-R / W, a semiconductor memory (e.g., a mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access memory)) includes a. The program may be provided to a computer using a temporary computer readable media of various types (transitory computer readable medium). Examples of transitory computer readable media include electric signals, optical signals, and electromagnetic waves. Transitory computer readable media, wired communication path such as electrical wires and optical fibers, or via a wireless communication path can provide the program to a computer.
[0080]
　The present invention is not limited to the above embodiments, but can be appropriately changed without departing from the spirit.
[0081]
　Although the present invention has been described with reference to the embodiments, the present invention is not limited by the foregoing. Configuration and details of the present invention, it is possible to make various modifications that those skilled in the art can understand within the scope of the invention.
[0082]
　This application claims priority based on Japanese Patent Application No. 2014-258414, filed on December 22, 2014, the entire disclosure of which is incorporated herein.
DESCRIPTION OF SYMBOLS
[0083]
　10 bearer management unit
　11 receiving controller
　15 SGW
　16 receiving controller
　17 the data accumulating unit
　20 mobile management device
　21 the location registration area
　25 MME
　27 SGSN
　30 mobile management device
　31 the location registration area
　35 MME
　37 SGSN
　40 mobile terminal device
　45 UE
　46 2G / 3G communication unit
　47 LTE communication unit
　48 the packet communication unit
　49 mobility management unit
　55 eNB
　57 2G / 3G radio network controller
　65 eNB
　67 2G / 3G radio network controller
　75 PGW

The scope of the claims
[Claim 1]
　A mobile communication system,
　a terminal (UE), a MME (Mobility Management Entity), SGSN (Serving GPRS Support Node), in the SGW (Serving Gateway), if ISR (Idle-mode Signaling Reduction) is valid the SGW includes means for transmitting the MME and the DDN to SGSN (Downlink Data Notification) message and receiving a packet call for the terminal, the MME and Modify Bearer from other different MME or other SGSN and the SGSN Upon receiving the Request message, the Modify Bearer Request message other that sent the MME or other SGSN Mobile communication system and means for retransmitting the DDN message to.
[Claim 2]
　The MME or the SGSN, the DDN message in response to the means for transmitting a Downlink Data Notification Acknowledge message including a cause value indicating that it is temporarily rejected due to processing associated with the movement of the terminal to the SGW the a mobile communication system according to claim 1.
[Claim 3]
　A SGW for use in a mobile communication system (Serving Gateway),
　the terminal and (UE), a MME (Mobility Management Entity), and SGSN (Serving GPRS Support Node), in the SGW, ISR (Idle-mode Signaling Reduction) If it is effective, means for transmitting the DDN (Downlink Data Notification) message to the and receive packets incoming to said terminal MME and the SGSN,
　the MME and Modify from other different MME or other SGSN and the SGSN when receiving the Bearer Request message, the Modify Bearer Request message other that sent the MME or other SG SGW having means for retransmitting the DDN message N to only a.
[Claim 4]
　The MME or the SGSN, the DDN message in response to the means for transmitting a Downlink Data Notification Acknowledge message including a cause value indicating that it is temporarily rejected due to processing associated with the movement of the terminal to the SGW the a, SGW according to claim 3.
[Claim 5]
　A terminal for use in a mobile communication system
　(UE), means for supporting the ISR (Idle-mode Signaling Reduction) function,
　when the ISR is enabled, SGW (Serving Gateway) receives a packet incoming call to the terminal and transmitting the MME (Mobility Management Entity) and SGSN (Serving GPRS Support Node) to DDN (Downlink Data Notification) message, receiving the Modify Bearer Request message from other different MME or other SGSN and the MME and the SGSN when the Modify Bearer Request the message transmitted only to other MME or other SGSN the DDN The by retransmitting, and it means to be paged by the other MME or any other base station or receives a paging message from the RNC SGSN (Radio Netwark Controller), terminal.
[Claim 6]
　The MME or the SGSN, the DDN message in response to the means for transmitting a Downlink Data Notification Acknowledge message including a cause value indicating that it is temporarily rejected due to processing associated with the movement of the terminal to the SGW the a terminal according to claim 5.
[Claim 7]
　　A call method of a mobile communication system,
　a terminal (UE), a MME (Mobility Management Entity), and SGSN (Serving GPRS Support Node), in the SGW (Serving Gateway), ISR ( Idle-mode Signaling Reduction) is when enabled, the SGW includes the steps of transmitting the DDN (Downlink Data Notification) message to the MME and the SGSN and receive packets incoming to said terminal,
　said the SGW, other different from said MME and the SGSN when receiving the Modify Bearer Request message from the MME or other SGSN, other that has transmitted the Modify Bearer Request message MME or only to another SGSN and a step of retransmitting the DDN message, incoming method for a mobile communication system.
[8.]
　The MME or the SGSN sending in response to the DDN message, the Downlink Data Notification Acknowledge message including a cause value indicating that it is temporarily rejected due to processing associated with the movement of the terminal to the SGW the a, call a method of a mobile communication system according to claim 7.
[Claim 9]
　A call method SGW for use in a mobile communication system (Serving Gateway),
　a terminal (UE), a MME (Mobility Management Entity), and SGSN (Serving GPRS Support Node), in the SGW, ISR (Idle-mode If Signaling Reduction) is valid, sending the MME and the SGSN to DDN (Downlink Data Notification) message and receiving a packet call for the terminal,
　the MME and the SGSN different other MME or other the when receiving the Modify Bearer Request message from SGSN, also other MME which sent the Modify Bearer Request message Ku is a step of retransmitting the DDN to only another SGSN, SGW how incoming.
[Claim 10]
　The MME or the SGSN sending in response to the DDN message, the Downlink Data Notification Acknowledge message including a cause value indicating that it is temporarily rejected due to processing associated with the movement of the terminal to the SGW the a, SGW incoming method of claim 9.
[Claim 11]
A call method of a terminal for use in a mobile communication system (UE),
　said terminal (UE) is, ISR support (Idle-mode Signaling Reduction) function,
　when the ISR is enabled, SGW (Serving Gateway) for transmitting the MME (Mobility Management Entity) and SGSN (Serving GPRS Support Node) to DDN (Downlink Data Notification) message and receiving the incoming packet, the MME and the SGSN different other MME or other and but the terminal when receiving the Modify Bearer Request message from SGSN, the Modify Bearer Request message other that sent the MME or other S By re-transmitting only to the DDN SN, the is paged by another MME or any other receives a paging message from the base station or RNC of SGSN (Radio Netwark Controller), a method of the receiving terminal.
[Claim 12]
　The MME or the SGSN sends in response to the DDN message, the Downlink Data Notification Acknowledge message including a cause value indicating that it is temporarily rejected due to processing associated with the movement of the terminal to the SGW, terminal how incoming of claim 11.