KR102028271B1 - Mobile communication system, mobile management device, communication method, mobile communication terminal, and non-transitory computer readable medium - Google Patents

Abstract

An object of the present invention is to provide a mobile communication system capable of handover of a mobile communication terminal from the 3GPP communication area to the Non-3GPP communication area in a regular form even after restarting the subscriber information management device. A mobile communication system according to the present invention includes a PGW for establishing a PDN connection used for communication with a mobile communication terminal; A subscriber information management device which maintains a PGW ID which is an identifier of a PGW; And a mobility management device for performing mobility management of the mobile communication terminal. Upon receiving the Tracking Area Update message or the Routing Area Update message transmitted from the mobile communication terminal, the mobility management device transmits a message for which the PGW ID is set to the subscriber information management device.

Description

Mobile communication system, mobile management device, communication method, mobile communication terminal, and non-transitory computer readable medium

The present invention relates to a mobile communication system, a mobile management apparatus, a communication method and a program. In particular, the present invention relates to a mobile communication system, a mobile management apparatus, a communication method, and a program for performing a handover process.

In the 3rd Generation Partnership Project (3GPP), a service is continuously provided between a communication area in which a communication method specified in 3GPP is used (a 3GPP communication area) and a communication area in which communication methods not specified in 3GPP are used (Non-3GPP communication area). A method for providing handovers (ie, continuously) has been studied.

A method for handover from the 3GPP communication area currently studied in 3GPP to the Non-3GPP communication area is described below. First, in the 3GPP communication area, a user equipment (UE), which is a mobile communication terminal, uses a 3GPP radio access technology, in which a UE exists (hereinafter referred to as an "in-area network") (EPC: Evolved Packet Core) ) And then to an external network (PDN: Packet Data Network or the Internet) through a gateway (eg, a Packet Data Network Gateway (PGW)). PGW, which is a gateway for transmitting (sending / receiving) user data related to a UE between an internal network and an external network, establishes a PDN connection used for communication with the UE. The PDN Connection includes one or multiple communication bearers. PDN Connection is established for each service provided to the UE. Examples of such services include those related to Access Point Names (APNs) such as IP Multimedia Subsystem (IMS) and Internet access.

In this establishment of the PDN Connection in the 3GPP communication area, the Mobility Management Entity (MME) transmits a PGW ID, which is identification information of the PGW, to a Home Subscriber Server (HSS) that manages subscriber information related to the UE. The PGW ID is identification information of a PGW which has established a PDN connection used for communication with the UE. The MME is a node device that performs not only the establishment of the PDN connection but also mobility management and communication control related to the UE. The HSS is a server device for managing a PGW ID associated with each PDN connection, and managing subscriber information of a UE. The procedure by which the MME sends the PGW ID to the HSS is described in Non-Patent Document 1 in which the ATTACH procedure is described.

Next, when the UE moves to the Non-3GPP communication area, the UE connects to the IP access device using the Non-3GPP radio access technology. The IP access device issues a query to an Authentication Authorization Accounting (AAA) server about the PGW ID of the PGW that established the PDN Connection between the PGW and the UE, so that the UE can constantly receive the service from the external network. The AAA server authenticates the communication in the Non-3GPP communication area. Note that the AAA server working with the HSS can obtain the PGW ID managed by the HSS. The AAA server notifies the IP access device of the PGW ID obtained from the HSS.

The IP access device may select a PGW which has established a PDN Connection related to the UE using the PGW ID obtained from the AAA server. The IP access device also establishes a communication path or communication bearer between the UE and the PGW. In this way, the UE may continue to receive service from the external network via the PGW even where the UE has moved (hereinafter referred to as "movement destination"). That is, handover from the 3GPP communication area to the Non-3GPP communication area is performed using the PGW as an anchor point.

 Next, a case where a failure occurs in the HSS holding the PGW ID will be described. When a failure occurs in the HSS, the service in the HSS is temporarily suspended. Thereafter, an initialization operation is performed on the HSS and thus the HSS is restarted. The procedure performed after the HSS is restarted is described in Non-Patent Document 2. Specifically, upon restart, the HSS deletes all PGW IDs held in the HSS. The HSS also sends a Reset notification to the MME.

When the MME receives a Reset notification from the HSS, the MME manages (ie, records) "Location Information Confirmed in HSS" (hereinafter also referred to as "LICH") at the UE as "Not Confirmed". Note that the state where the LICH is "Not Confirmed" indicates that the HSS has been restarted and does not hold the PGW ID of the PGW that has established the PDN Connection used for communication with the UE.

In the 3GPP communication area, it should be noted that the UE transmits a Tracking Area Update (TAU) Request message to the MME to perform the TAU as the provision of location information at regular intervals. Upon receiving the TAU Request message, the MME sends an ULR (Update Location Request) message to the HSS to update the tracking area (TA) of the UE. In this process, the MME transmits to the HSS a ULR message in which an Active Access Point Name (APN) Attribute Value Pair (AVP) including a PGW ID of a PGW establishing a PDN Connection used for communication with the UE is set. In the above description, the case where the MME receives a TAU Request message is described. However, even when the MME receives some kind of message other than the TAU Request message, the MME may also include an Active Access Point Name (APN) attribute value pair (AVP) including a PGW ID of a PGW that has established a PDN connection used for communication with the UE. The ULR message may be transmitted to the HSS.

Accordingly, the HSS may receive the ULR message in which the Active APN AVP is set, and retain the deleted PGW ID while associating with the UE. In this way, the HSS can retain the PGW ID associated with the UE even after the HSS is restarted. Therefore, afterwards, when the UE is handed over to the Non-3GPP communication area, the AAA server can obtain the PGW ID of the PGW which has established a PDN Connection used for communication with the UE from the HSS. As a result, even in the Non-3GPP communication area, the UE can access the same PGW as the PGW accessed by the UE in the 3GPP communication area, and thus can perform handover using the PGW as an anchor point.

3GPP TS 23.401 V13.3.0 (2015-06), Section 5.3.2 3GPP TS 29.272 V13.2.0 (2015-06), Section 5.2.4 3GPP TS 23.402 V13.2.0 (2015-06), Section 4.3.1.2, Section 4.3.4, Chapter 16

The recovery procedure performed after restart of the HSS in Non-Patent Document 2, Section 5.2.4 is based on the premise that the UE performs a TAU in an area that does not (or requires) a change of the MME. Specifically, the UE transmits a TAU Request message to the MME managing (or recording) the LICH as "Not Confirmed". When the LICH of the UE sending the TAU Request message is "Not Confirmed", the MME transmits to the HSS a ULR message including an active APN AVP including the PGW ID of the PGW establishing the PDN Connection used for communication with the UE. .

As a recovery procedure performed after the restart of the HSS, a procedure performed when the UE moves to an area involving (or requesting) a change of the MME is described below. First, when the HSS is restarted, the HSS sends a Reset notification to each MME. In response, each MME manages (or records) the LICH of the UE under its management at that moment as "Not Confirmed". Next, when a particular UE moves to an area that involves a change of the MME, the UE sends a TAU Request message to the new MME (hereinafter also referred to as "after-changed MME"). However, after the change, the MME does not manage (ie, record) the LICH of the UE that has sent the TAU Request message as "Not Confirmed". Therefore, after the change, the MME does not transmit the PGW ID of the PGW which established the PDN connection used for communication with the UE to the HSS. However, even in such a case, the MME after the change can obtain the information of the PGW ID from the original MME (hereinafter also referred to as "before-change MME"). Therefore, after the change, the MME may use the acquired PGW ID to access the same PGW as the PGW to which the UE has connected before the UE moves to a new area.

Even in such a situation, if the UE is further handed over from the 3GPP communication area to the Non-3GPP communication area, the AAA server cannot obtain the PGW ID of the PGW which has established the PDN connection used for communication with the UE from the HSS. This is because the HSS does not hold its PGW ID. Therefore, the IP access device in the Non-3GPP communication area cannot detect the PGW used as the anchor point. As a result, there is a problem that the UE cannot be handed over from the 3GPP communication area to the Non-3GPP communication area.

An object of the present invention is to provide a mobile communication system, a mobile management apparatus, a communication method, and a method for enabling a UE to properly perform a handover from a 3GPP communication area to a Non-3GPP communication area even after the HSS is restarted in the above-described situation. To provide a program.

According to a first aspect of the present invention, there is provided a mobile communication system, comprising: a PGW configured to establish a PDN Connection used for communication with a mobile communication terminal; The HSS-PGW ID configured to hold a PGW ID is an identifier of the PGW; And a mobility management device configured to perform mobility management of the mobile communication terminal, and when the mobility management device receives a Tracking Area Update message sent from the mobile communication terminal, the mobility management device retains a PGW ID in the HSS. Irrespective of this, the Update Location Request message including the PGW ID set therein is transmitted to the HSS.

The mobile management apparatus according to the second aspect of the present invention, upon receiving the Tracking Area Update message transmitted from the mobile communication terminal, receives the PGW ID set therein regardless of the holding status of the PGW ID in the HSS holding the PGW ID. And a communication unit configured to transmit an Update Location Request message to the HSS, wherein the PGW ID is a PGW ID of a PGW that has established a PDN connection used for communication with the mobile communication terminal.

The communication method according to the third aspect of the present invention includes a PGW ID set internally when receiving a Tracking Area Update message transmitted from a mobile communication terminal, regardless of the retention status of the PGW ID in the HSS holding the PGW ID. Transmitting an Update Location Request message to the HSS, wherein the PGW ID is a PGW ID of a PGW that has established a PDN connection used for communication with the mobile communication terminal.

The program according to the fourth aspect of the present invention allows a computer to receive a Tracking Area Update message transmitted from a mobile communication terminal, regardless of the holding status of the PGW ID in the HSS holding the PGW ID. Transmitting an Update Location Request message including a message to the HSS, wherein the PGW ID is a PGW ID of a PGW that has established a PDN connection used for communication with the mobile communication terminal.

According to the present invention, there is provided a mobile communication system, a mobile management apparatus, a communication method, and a method for enabling a UE to properly perform a handover from a 3GPP communication area to a Non-3GPP communication area even after the HSS is restarted in the above-described situation. It is possible to provide a program.

1 is a block diagram of a mobile communication system according to a first exemplary embodiment.
Fig. 2 is a configuration diagram of a mobile communication system according to the second exemplary embodiment.
3 is a configuration diagram of an MME according to a second exemplary embodiment.
4 is a configuration diagram of a UE according to the second exemplary embodiment.
5 shows a TAU process flow according to a second exemplary embodiment.
6 shows a TAU process flow according to a second exemplary embodiment.
Fig. 7 illustrates an Update Location Request message according to the second exemplary embodiment.
8 illustrates a handover process flow according to the second exemplary embodiment.
Fig. 9 is a block diagram of a mobile communication system according to the second exemplary embodiment.
10 illustrates contents set in a Context Response message according to a third exemplary embodiment.
Fig. 11 shows contents set for Indication set in Indication Flags according to the third exemplary embodiment.
FIG. 12 illustrates contents configured for MME / SGSN UE EPS PDN Connections set in a Context Response message according to the third exemplary embodiment.
13 shows the contents of an ARD according to a fourth exemplary embodiment.
14 illustrates a handover process flow according to the fifth exemplary embodiment.
15 illustrates a flow of an authentication process performed between an AAA server, an HSS, and an MME according to a fifth exemplary embodiment.

(First Exemplary Embodiment)

Hereinafter, exemplary embodiments according to the present invention will be described with reference to the drawings. An example configuration of a mobile communication system according to the first exemplary embodiment of the present invention is described with reference to FIG. The mobile communication system shown in FIG. 1 includes a mobile communication terminal 10, a PGW 11, an HSS 12, and a mobility management device 100. The mobile communication system shown in FIG. 1 is constructed mainly using the node devices specified in 3GPP.

The mobile communication terminal 10 may be a mobile phone terminal, a smart phone terminal, a tablet terminal, or the like. Alternatively, the mobile communication terminal 10 may be a machine to machine (M2M) terminal, a machine type communication (MTC) terminal, or the like. In the alternative, the mobile communication terminal 10 may be a computer device that operates as a processor executes a program stored in memory. It is assumed that the mobile communication terminal 10 is a terminal capable of communicating in the 3GPP communication area and in the Non-3GPP communication area.

PGW 11, HSS 12, and mobility management device 100 are node devices in which functions and operations are specified in 3GPP. Each of the PGW 11, the HSS 12, and the mobility management device 100 may be a computer device that operates as a processor executes a program stored in a memory.

The PGW 11 establishes a PDN Connection used for communication with the mobile communication terminal 10. The PDN Connection is established between the mobile communication terminal 10 and the PGW 11 via an evolved Node B (eNB) (not shown) or a Radio Network Controller (RNC) (not shown). Each of an eNB and an RNC is an apparatus in which functions and operations are specified in 3GPP. An eNB is a base station that supports Long Term Evolution (LTE) as a wireless communication method. The RNC is a node device that supports a wireless communication method called "2G (2nd generation mobile phone)" or "3G (3rd generation mobile phone)". In addition, a PGW ID, which is an identifier uniquely identified in the communication system, is assigned to the PGW 11. The communication system may be, for example, an Evolved Packet System (EPS).

The HSS 12 holds a PGW ID of a PGW which has established a PDN Connection used for communication with the mobile communication terminal 10. The mobility management apparatus 100 performs mobility management for the mobile communication terminal 10 (or tracks the movement of the mobile communication terminal 10). For example, the movement management may be to manage location information that changes as the mobile communication terminal 10 moves. In addition, the mobility management apparatus 100 may be an MME or a Serving GPRS Support Node (SGSN).

Note that the mobile communication terminal 10 transmits a TAU Request message to the mobility management apparatus 100 at regular intervals. Specifically, the mobile communication terminal 10 transmits a TAU Request message to the mobile management apparatus 100 through the eNB.

The tracking area includes at least one cell. The tracking area is information managed by the movement management apparatus 100, for example. In other words, the mobility management apparatus 100 manages the tracking area as location information of the mobile communication terminal 10. In addition, when the mobile management apparatus 100 calls the mobile communication terminal 10, the mobile management apparatus 100 performs paging on all mobile communication terminals located in the tracking area associated with the mobile communication terminal 10. do.

When the mobile management apparatus 100 receives the TAU Request message transmitted from the mobile communication terminal 10, the mobile management apparatus 100 sets the PGW ID regardless of the retention status of the PGW ID in the HSS 12. The ULR message is transmitted to the HSS 12.

The mobility management apparatus 100 transmits a ULR message to the HSS 12 to update the location information of the mobile communication terminal 10 managed by the HSS 12. The HSS 12 generally acquires the PGW ID of the PGW 11 that established the PDN Connection used for communication with the mobile communication terminal 10 during the ATTACH process of the mobile communication terminal 10. The HSS 12 also holds the PGW ID of the PGW 11 in association with the mobile communication terminal 10. However, when the HSS 12 is restarted due to the occurrence of a failure or the like, the HSS 12 deletes all of the PGW IDs held by the HSS 12. Therefore, there is a case where the HSS 12 does not hold the PGW ID of the PGW 11 associated with the mobile communication terminal 10.

The mobility management apparatus 100 transmits a ULR message in which the PGW ID of the PGW 11 is set, regardless of whether the HSS 12 holds the PGW ID of the PGW 11 associated with the mobile communication terminal 10. . When the HSS 12 receives the ULR message while the HSS 12 already holds the PGW ID of the PGW 11 and the held PGW ID is the same as the received PGW ID, the HSS 12 is the mobile communication terminal. It is not necessary to update the PGW ID of the PGW 11 associated with (10). On the other hand, when the PGW ID held in the HSS 12 is different from the PGW ID set in the ULR message, the HSS 12 overwrites the held PGW ID with the PGW ID set in the ULR message to replace the new PGW ID. Save it.

When the HSS 12 receives the ULR message while the HSS 12 does not hold the PGW ID of the PGW 11, the HSS 12 associates the PGW ID set in the ULR message with the mobile communication terminal 10. While holding.

The above expression "regardless of whether or not the HSS 12 holds the PGW ID of the PGW 11" means that the mobile communication terminal 10 in which the mobile management apparatus 100 transmits a TAU Request message as "Not Confirmed". Can also be expressed as "regardless of whether or not to manage (ie, record) the LICH. That is, the mobility management apparatus 100 manages the PICH, regardless of whether the mobility management apparatus 100 manages (ie, records) the LICH for the mobile communication terminal 10 that has transmitted the TAU Request message as "Not Confirmed". The ULR message in which the ID is set is transmitted to the HSS 12.

As described above, the mobile management apparatus 100 holds a PGW ID of the PGW 11 that has established a PDN Connection used for communication with the mobile communication terminal 10 to which the HSS 12 has sent a TAU Request message. Irrespective of whether or not, the ULR message to which the PGW ID is set is transmitted to the HSS 12. In other words, regardless of whether the mobility management apparatus 100 manages (ie, records) the LICH for the mobile communication terminal 10 in which the mobility management apparatus 100 transmits a TAU Request message as "Not Confirmed", The ULR message in which the PGW ID is set is transmitted to the HSS 12.

In this manner, even when the mobile communication terminal 10 performs a move involving (or requesting) a change of the MME after the restart of the HSS 12, the HSS 12 is used for communication with the mobile communication terminal 10. The PGW ID of the PGW 11 which established the PDN connection can be acquired. Therefore, even when the MME in which the mobile communication terminal 10 transmits the TAU Request message before the restart of the HSS 12 is different from the MME in which the mobile communication terminal 10 transmits the TAU Request message after the HSS 12 restarts, The handover process of the mobile communication terminal 10 may be appropriately performed. In addition, even when the mobile communication terminal 10 moves from the 3GPP communication area to the Non-3GPP communication area, the handover process of the mobile communication terminal 10 may be appropriately performed.

That is, the HSS 12 may update the PGW ID of the PGW 11 in which the mobile communication terminal 10 establishes a PDN connection used for communication with the mobile communication terminal 10 at the timing of transmitting the TAU Request message. have. Therefore, even when the mobile communication terminal 10 moves (or requests) the change of the MME in the 3GPP communication area after the restart of the HSS 12, and then moves further to the Non-3GPP communication area, the HSS ( 12 may transmit the PGW ID associated with the mobile communication terminal 10 to the AAA server. Therefore, it is possible to identify the PGW ID of the PGW 11 to be used as the anchor point in the Non-3GPP communication area, and thereby to appropriately perform the handover process for the mobile communication terminal 10. Note that the HSS 12 shown in FIG. 1 may also be referred to as a “subscriber information management apparatus”.

(Second exemplary embodiment)

Next, a configuration example of a mobile communication system according to the second exemplary embodiment of the present invention is described with reference to FIG. The mobile communication system shown in FIG. 2 includes the PGW 11, the HSS 12, the MME 13, the MME 14, the UE 20, the AAA server 31, the IP access device 32, and the eNB 40. ), eNB 41, SGW 50, SGW 60, and PCRF 70. PGW 11 and HSS 12 are similar to those shown in FIG. 1 and therefore their detailed descriptions are omitted. In addition, in FIG. 2, explanations are given using the MME 13 as the mobility management apparatus 100.

The UE 20 corresponds to the mobile communication terminal 10 in FIG. 1. UE 20 is used as a generic term for mobile communication terminals in 3GPP. The AAA server 31 is a device for authenticating the UE 20 in the Non-3GPP communication area. In addition, the AAA server 31, which cooperates with the HSS 12, receives the PGW ID of the PGW 11 that has established the PDN Connection used for communication with the UE 20 from the HSS 12.

The IP access device 32 is a device that communicates with the UE 20 in the Non-3GPP communication area. For example, the IP access device 32 may be an apparatus for performing mobile communication with the UE 20 or an access point in a wireless LAN using a communication method different from the communication method specified in 3GPP. The IP access device 32 may be a Trusted non-3GPP Access network described in Non-Patent Document 3, Chapter 16, an Evolved Packet Data Gateway (ePDG), or a Trusted WLAN Access Network (TWAN). Alternatively, IP access device 32 may be a wireless LAN termination (WT).

The IP access device 32 also obtains a PGW ID associated with the UE 20 from the AAA server 31. The IP access device 32 accesses the PGW 11 using the obtained PGW ID. In this way, the IP access device 32 may relay the communication between the PGW 11 and the UE 20 used as the anchor point.

Each of the eNBs 40 and 41 communicates with the UE 20 using LTE as a wireless communication method. In addition, the SGW 50 relays the communication between the eNB 40 and the PGW 11, and the SGW 60 relays the communication between the eNB 41 and the PGW 11. The PCRF 70 is a node device that manages QoS policies and the like related to the UE 20.

2 shows the UE 20 moving from the Tracking Area managed by the MME 13 to the Tracking Area managed by the MME 14 and then to the Non-3GPP communication area. Solid lines in FIG. 2 indicate that control information or C-plane information is transmitted or received. Broken lines in FIG. 2 indicate that user data or U-plane information is transmitted or received. Also, the arrows between the UEs 20 in FIG. 2 indicate that the UE 20 is moving.

Further, in the second exemplary embodiment, after restarting the HSS 12, the UE 20 moves from the tracking area managed by the MME 13 to the tracking area managed by the MME 14, and then next. Processes in the case of moving to the Non-3GPP communication area are mainly described.

Next, a configuration example of the MME 13 according to the second exemplary embodiment of the present invention is described with reference to FIG. The configuration of the MME 14 is similar to that of the MME 13 and thus detailed description thereof is omitted. The MME 13 includes a communication unit 15 (which may also be referred to as a “transmission and reception unit”) 15 and a control unit 16. The communication unit 15 and the control unit 16 may be software or a module operated by causing a processor to execute a program stored in a memory. Alternatively, the communication unit 15 and the control unit 16 may be hardware such as a circuit and a chip.

The communication unit 15 communicates with the eNB 40, the HSS 12, and the MME 14. In addition, the communication unit 15 communicates with the UE 20 through the eNB 40. The controller 16 generates messages to be transmitted to the eNB 40, the MME 14, and the HSS 12 via the communication unit 15. In addition, the controller 16 analyzes messages received from the eNB 40, the MME 14, and the HSS 12.

For example, the controller 16 sends a Notify Request message in which the PGW ID of the PGW 11 that establishes the PDN connection used for communication with the UE 20 in the ATTACH process of the UE 20 is set to the communication unit 15. Transmit to the HSS 12 via the terminal. In addition, when the control unit 16 receives a TAU Request message transmitted from the UE 20 through the eNB 40, the control unit 16 establishes a PGW 11 that establishes a PDN connection used for communication with the UE 20. ) Transmits a ULR message in which the PGW ID is set to the HSS 12 through the communication unit 15.

In addition, when the control unit 16 receives the Reset notification from the HSS 12, the control unit 16 manages (ie, records) the LICH associated with the UE 20 as "Not Confirmed".

Next, a configuration example of the UE 20 according to the second exemplary embodiment of the present invention is described with reference to FIG. 4. The UE 20 includes a 3GPP communication unit 21 and a Non-3GPP communication unit 22. The 3GPP communication unit 21 and the Non-3GPP communication unit 22 may be software or a module operated by causing a processor to execute a program stored in a memory. Alternatively, the 3GPP communication unit 21 and the Non-3GPP communication unit 22 may be hardware such as a circuit and a chip.

The 3GPP communication unit 21 performs wireless communication with the eNB 40. For example, the 3GPP communication unit 21 communicates with the eNB 40 using LTE as a wireless communication method. When the UE 20 changes from the power-off state to the power-on state, the 3GPP communication unit 21 transmits an ATTACH Request message to the eNB 40. In addition, the 3GPP communication unit 21 transmits a TAU Request message for transmitting the location information of the UE 20 to the eNB 40 at regular intervals. Alternatively, the 3GPP communication unit 21 transmits a TAU Request message to the eNB 40 when the UE 20 performs a move involving (or requesting) a change of the MME.

The Non-3GPP communication unit 22 performs wireless communication with the IP access device 32. For example, Non-3GPP communication unit 22 may perform wireless LAN communication with IP access device 32 or communicate with IP access device 32 using other communication methods.

Next, the flows of the TAU process and the handover process in the 3GPP communication area according to the second exemplary embodiment of the present invention are described with reference to FIGS. 5 and 6. 5 and 6 are based on Figure 5.3.3.1-1 in 3GPP TS 23.401 V13.1.0 (2014-12). 5 and 6 also assume that the HSS 12 is restarted (S1) and then sending a Reset notification to the MMEs 13 and 14 (S2 and S3). First, the UE 20 determines to start the TAU process (S11). For example, when the UE 20 has made a move that involves (or requires) a change in the MME or detects a periodic timing at which the TAU process should be started, the UE 20 starts the TAU process. In FIG. 5, the TAU process flow in the case where the UE 20 performs the movement involving the change of the MME is described.

Next, the UE 20 transmits a TAU Request message to the MME 14 via the eNB 41 (S12 and S13). The MME 14 is an MME (new MME) that manages the UE 20 after the UE 20 moves. In addition, the MME 13 (formerly MME) that managed the UE 20 before the UE 20 moved is the MME 13.

Next, the MME 14 requests the MME 13 to transmit subscriber information and the like related to the UE 20, to request a Context Request to the MME 13 that has managed the UE 20 before the UE 20 moves. The message is transmitted (S14). Next, the MME 13 transmits to the MME 14 a Context Response message in which subscriber information including a PGW ID related to the UE 20 is set (S15). Next, an authentication process for the UE 20 is performed between the UE 20 and the MME 14, and then between the MME 14 and the HSS 12 (S16).

Next, the MME 14 instructs the MME 13 to change the gateway device that accommodates the UE 20 from the SGW 50 to the SGW 60 as the UE 20 moves. A context acknowledgment message is sent to the MME 13 (S17).

Next, the MME 14 transmits a Create Session Request message to the SGW 60 to instruct the SGW 60 to create a communication bearer between the SGW 60 and the PGW 11 (S18). Next, the SGW 60 transmits a Modify Bearer Request message to the PGW 11 for requesting creation of a communication bearer (S19). Next, in response to the Modify Bearer Request message, the PGW 11 transmits a Modify Bearer Response message to the SGW 60 (S20). Next, in response to the Create Session Request message sent in step S18, the SGW 60 transmits a Create Session Response message to the MME 14 (S21). In this way, the UE 20 establishes a PDN Connection between the UE 20 and the PGW 11 via the SGW 60.

Next, the MME 14 transmits to the HSS 12 an Update Location Request message in which an Active APN AVP including a PGW ID of the PGW 11 establishing a PDN Connection used for communication with the UE 20 is set. (S22). 7 illustrates an Update Location Request message in which Active APN AVP is set. FIG. 7 is based on 3GPP TS 29.272 V13.2.0 (2015-06) Table 5.2.1.1.1 / 1. The PMEW of the PGW 11 that established the PDN Connection used for communication with the UE 20, regardless of whether the MME 14 manages (ie, records) the LICH for the UE 20 as "Not Confirmed". Set Active APN AVP including ID in Update Location Request message. In other words, the MME 14 updates the Active APN AVP including the PGW ID regardless of whether the PGW ID in the HSS 12 needs to be reset due to the restart of the HSS 12 or due to the Reset process. Set in the Location Request message. In addition, the MME 14 obtains information of the PGW ID from the MME 13 through a Context Response message. Accordingly, the MME 14 may use the acquired PGW ID to access the same PGW as the PGW to which the MME 14 has connected before the UE moves, thereby allowing handover to be properly performed even after restarting the HSS.

Next, the flow of the handover process from the 3GPP communication area to the Non-3GPP communication area according to the second exemplary embodiment of the present invention is described with reference to FIG. 8 is based on Figure 8.2.2-1 of the non-patent literature. First, it is assumed that the UE 20 is performing communication in the 3GPP communication area. At this time, it is assumed that a communication bearer is established between the SGW 60 and the PGW 11 using PMIPv6 or GTP tunnel (S31).

Next, the case where the UE 20 moves from the 3GPP communication area to the Non-3GPP communication area is described. At this time, the UE 20 detects the IP access device 32 (S32). When the UE 20 detects the IP access device 32, an authentication process is performed between the UE 20 and the IP access device 32 (S33). In addition, authentication for the UE 20 is also performed in the network (S34). In the authentication process in step S34, the AAA server 31 issues an inquiry to the HSS 12, acquires the PGW ID of the PGW 11 that established the PDN Connection used for communication with the UE 20, and The PGW ID is sent to the AAA proxy 71. Note that the AAA proxy 71 is used as a Proxy server of the AAA server 31.

In addition, in the authentication process in step S34, the AAA proxy 71 transmits the PGW ID received from the AAA server 31 to the IP access device 32.

Next, the UE 20 performs an L3 Attach Trigger process between the UE 20 and the IP access device 32 (S35). In this way, for example, the UE 20 transmits information about the APN used for communication in the 3GPP communication area to the IP access device 32.

Next, a Gateway Control Session Establishment Procedure is performed between the IP access device 32 and the Policy and Charging Rules Function (vPCRF) 72 and then between the vPCRF 72 and the hPCRF 73 (S36). PCRFs are node devices that manage QoS policies, etc., associated with the UE 20. When the UE 20 roams, the vPCRF 72 performs policy control related to the UE 20 in the network in which the UE 20 roams. The hPCRF 73 performs policy control related to the UE 20 within the home network of the UE 20.

In step S36, the hPCRF 73 transmits QoS policy information and the like related to the UE 20 to the vPCRF 72. In addition, the vPCRF 72 transmits (i.e. transmits) QoS policy information and the like related to the UE 20 to the IP access device 32.

Next, the IP access device 32 transmits a Proxy Binding Update message to the PGW 11 using the PGW ID of the PGW 11 received in step S34 (S37). By receiving the Proxy Binding Update message, the PGW 11 associates the PDN Connection used for communication with the UE 20 in the 3GPP communication area with a communication bearer or communication connection in the Non-3GPP communication area, and the UE 20. Performs a handover process.

As described so far, using the mobile communication system according to the second exemplary embodiment of the present invention, the HSS 12 communicates with the UE 20 whenever the UE 20 performs a TAU process. The PGW ID of the PGW 11 that has established the PDN Connection used for can be obtained. In other words, the MME 14 is used to communicate with the UE 20 whenever the UE 20 performs a TAU process, regardless of whether the LICH is managed (ie, recorded) as "Not Confirmed". The PGW ID of the PGW 11 that established the connection is transmitted to the HSS 12.

In this manner, even when the UE 20 makes a move that involves (or requires) a change of the MME after the restart of the HSS 12, the HSS 12 moves with respect to the UE 20 after the UE 20 moves. The PGW ID of the PGW 11 establishing the PDN Connection used for communication with the UE 20 may be received from the MME 14 performing management (S22). Therefore, the AAA server 31 can obtain the PGW ID associated with the UE 20 from the HSS 12 even after restarting the HSS 12. As a result, the UE 20 can access after access the same PGW as the PGW accessed by the UE 20 before the move, thus using the PGW as an anchor point from the 3GPP communication area to the Non-3GPP communication area. Over can be performed properly. As a result, the UE can continue to receive service from the external network via the same PGW even from the area where the UE has moved.

Note that the second exemplary embodiment has been described using mainly the MME as the mobility management apparatus 100. However, as shown in FIG. 9, SGSN 110 and SGSN 111 may be used in place of MMEs. In this case, the MMEs 13 and 14 in FIG. 2 are replaced with SGSNs 110 and 111 respectively. Also, the eNBs 40 and 41 in FIG. 2 are replaced with RNCs 130 and 131, respectively. In addition, the HSS 12 in FIG. 2 is replaced with the HLR 120. In this case, the UE 20 performs a Routing Area Update (RAU) process instead of the TAU process and transmits a RAU Request message to the SGSN 111 via the RNC 131.

(Third Exemplary Embodiment)

Next, a TAU process flow according to the third exemplary embodiment is described. The TAU process flow according to the third exemplary embodiment is similar to that described in the second exemplary embodiment with reference to FIGS. 5 and 6 except for differences in the content set in the messages. Accordingly, the third exemplary embodiment is described with particular emphasis on messages in which contents are set different from those in the messages in the second exemplary embodiment shown in FIGS. 5 and 6.

Further, in the third exemplary embodiment, it is assumed that the HSS 12 is restarted and sends a Reset notification to the MME 13. In addition, as the MME 13 receives the Reset notification, the MME 13 manages (records) the LICH of the UE 20 as "Not Confirmed".

In addition, the UE 20 moves from a location where the UE 20 is managed by the MME 13 to a location where the UE 20 is managed by the MME 14. Even in such a situation, the UE 20 performs the TAU process in step S11 and subsequent steps in FIG. 5.

Steps S11 to S14 are similar to those in the second exemplary embodiment. When the MME 13 determines (or recognizes) that the TAU process for the UE 20 is performed in step S14, the MME 13 manages the LICH for the UE 20 as "Not Confirmed" in step S15. Or a Context Response message in which information to be recorded) is set is transmitted to the MME 14.

Hereinafter, contents set in the context response message will be described with reference to FIG. 10. FIG. 10 is based on 3GPP TS29.274 V13.2.0 (2015-06) Table 7.3.6-1. 10 shows that MME / SGSN UE EPS PDN Connections indicating that there is data set for each PDN Connection are set in the Context Response message. FIG. 10 also shows that an Information Element (IE) Type of MME / SGSN UE EPS PDN Connections is a PDN Connection. 10 illustrates that LICH is added to Indication Flags of a Context Response message. 10 illustrates that the IE Type of Indication Flags is Indication.

Indications set in Indication Flags of the Context Response message will be described below with reference to FIG. 11. FIG. 11 is based on 3GPP TS29.274 V13.2.0 (2015-06) Figure 8.12-1. 11 shows that a flag related to LICH is set to Bit 5 of Octet 9. For example, when "1" is set in Bit 5 of Octet 9, it indicates that Active APN needs to be set in Update Location Request message when MME 14 sends Update Location Request message to HSS 12. do. That is, when "1" is set in Bit 5 of Octet 9, it indicates that the LICH is "Not Confirmed".

Content set in the MME / SGSN UE EPS PDN Connections of the Context Response message will be described below with reference to FIG. 12. 12 is based on 3GPP TS29.274 V13.2.0 (2015-06) Table 7.3.6-2. 12 shows that a context identifier is added to indicate identification information of a PDN connection. Context Identifier is information used to identify a PDN Connection, and is used when an Active-APN AVP is transmitted as described later. Accordingly, the MME 13 sets a Context Identifier with a flag indicating that the LICH for the UE 20 is "Not Confirmed" in the Context Response message. In addition, the MME 13 transmits a Context Response message including the PGW ID of the PGW 11 to the MME 14. In this example, information about the PGW ID is transmitted from the MME 13 to the MME 14 using the MME / SGSN UE EPS PDN Connections IE. However, information about the PGW ID may be transmitted using a dedicated IE.

Referring again to FIGS. 5 and 6, steps S16 to S21 are similar to those in the second exemplary embodiment. In step S22, since the LICH for the UE 20 is "Not Confirmed", the MME 14 establishes an Active- containing PGW ID of the PGW 11 that has established a PDN Connection used for communication with the UE 20. The ULR message in which the APN AVP is set is transmitted to the HSS 12. For example, in step S15, when the MME 14 receives a Context Response message in which "1" is set to Bit 5 of Octet 9 corresponding to the area displaying Indication, the MME 14 receives the Context in step S15. Context Identifier set in Response is set as Active-APN AVP. As a result, in step S22, the MME 14 transmits a ULR message in which the Active-APN AVP including the PGW ID of the PGW 11 that established the PDN Connection used for communication with the UE 20 is set. Send to

As described above, the MME 14 in charge of managing the UE 20 after the movement is sent to the UE 20 via a Context Response message sent from the MME 13 that managed the UE 20 before the movement. The management state of the LICH can be recognized. That is, even when the MME managing the UE 20 is changed from the MME 13 to the MME 14 due to the movement of the UE 20, the MME 14 may inherit the management state of the LICH. Therefore, the HSS 12 can obtain the PGW ID of the PGW 11 that has established the PDN Connection used for communication with the UE 20 by receiving the ULR message from the MME 14.

As a result, even when the UE 20 moves (or requires) a change in the MME and then moves to the Non-3GPP communication area, the AAA server 31 is restarted from the restarted HSS 12 by the UE 20. The PGW ID of the PGW 11 which has established the PDN Connection used for communication with can be obtained. Accordingly, the UE 20 may appropriately perform handover from the 3GPP communication area to the Non-3GPP communication area.

(Fourth Exemplary Embodiment)

Next, a TAU process flow according to the fourth exemplary embodiment is described. The TAU process flow according to the fourth exemplary embodiment is similar to that described in the second exemplary embodiment with reference to FIGS. 5 and 6 except for the differences in the content set in the messages. Thus, the fourth exemplary embodiment is described with particular emphasis on messages in which contents are set different from those in the messages in the second exemplary embodiment shown in FIGS. 5 and 6.

Further, in the fourth exemplary embodiment, it is assumed that the HSS 12 is restarted and sends a Reset notification to the MME 13. In addition, as the MME 13 receives the Reset notification, the MME 13 manages (records) the LICH of the UE 20 as "Not Confirmed".

In addition, the UE 20 moves from a location where the UE 20 is managed by the MME 13 to a location where the UE 20 is managed by the MME 14. Even in such a situation, the UE 20 performs the TAU process in step S11 and subsequent steps in FIG. 5.

In addition, in 3GPP TS 29.272 V13.2.0 (2015-06) Table 7.7.31 / 1, an access-restriction-data (ARD) indicating an access network in which use of the UE 20 is restricted is held in the HSS 12. It is specified. As shown in FIG. 13, in the ARD, areas in which the ARD is set and restrictions associated with these areas are specified. For example, when " 1 " is set in Bit 5 corresponding to the area indicating the ARD, it indicates that the UE 20 is not allowed to be handed over to the Non-3GPP communication area. In addition, when " 0 " is set in each of the bits corresponding to the area indicating the ARD, it indicates that the use of the access network associated with the bit is not restricted.

The HSS 12 also transmits information about the ARD to the MME 13. For example, in the periodic TAU process of the UE 20, the HSS 12 sets information on the ARD in an Update Location Answer message, which is a response message to an Update Location Request message, and sends an Update Location Answer message to the MME 13. To be sent).

When the MME 13 determines (or recognizes) that the TAU process for the UE 20 is to be performed in step S14 in FIG. 5, the MME 13 corresponds to a bit corresponding to an area indicating the ARD of the UE 20. Check that "0" is set to 5. The fact that "0" is set in Bit 5 corresponding to the area indicating the ARD indicates that the UE 20 is not allowed to be handed over to the Non-3GPP communication area.

When the MME 13 determines that the TAU process for the UE 20 is performed, and the MME 13 confirms that "0" is set in Bit 5 corresponding to the area indicating the ARD of the UE 20, The MME 13 transmits command information to the MME 14. Specifically, the MME 13 instructs the HSS 12 to transmit a ULR message in which an Active-APN including an PGW ID of the PGW 11 that establishes a PDN Connection used for communication with the UE 20 is set. The information is set in the Context Response message, and the Context Response message is sent to the MME 14. Bit 5 corresponding to the area indicating the ARD is a flag indicating a state of Handover To Non 3GPP-Access Not Allowed (HTN3AA). Note that the information in this state can be defined using data other than ARD. The MME 13 may then set that information in a Context Response message and notify the MME 14 of this information.

Upon obtaining information instructing to transmit the ULR message including the Active-APN AVP to the HSS 12 in step S15, the MME 14 receives the ULR message in which the Active-APN including the PGW ID is set in step S22. 12).

In addition, when "0" is set in Bit 5 corresponding to the area indicating the ARD of the UE 20 and the LICH is managed (recorded) as "Not Confirmed", the MME 13 communicates with the UE 20. Information for instructing the HSS 12 to transmit an ULR message in which an Active-APN including a PGW ID of a PGW 11 that establishes a PDN Connection used for establishing a PDN Connection may be set in a Context Response message. Next, the MME 13 may send the Context Response message to the MME 14.

As described above, the MME 13 may transmit command information related to the contents of the ULR message to the MME 14 managing the UE 20 after the movement, using the restriction information indicated in the ARD. That is, the MME 13 may instruct the MME 14 to set the PGW ID of the PGW 11 in which the UE 20 sets up a communication bearer in the ULR message.

In addition, in the fourth exemplary embodiment, the MME 14 sets Active-APN in the ULR message only when the UE 20 is allowed to be handed over to the Non-3GPP communication area. Thus, when the process according to the fourth exemplary embodiment is performed, the amount of information in the ULR message may be reduced as compared to in the first or second exemplary embodiment in which Active-APN is always set in the ULR message. .

Note that in the third and fourth exemplary embodiments, SGSNs 110 and 111 may also be used instead of the MMEs 13 and 14. RNCs 130 and 131 may be used instead of eNBs 40 and 41. In addition, HLR 120 may be used instead of HSS 12. In this case, the UE 20 performs the RAU process instead of the TAU process and transmits a RAU Request message to the SGSN 111 via the RNC 131.

(Fifth Exemplary Embodiment)

Next, the flow of the handover process from the 3GPP communication area to the Non-3GPP communication area according to the fifth exemplary embodiment is described with reference to FIGS. 14 and 15. Figure 14 is based on Figure 8.2.2-1 of Non-Patent Document 3. First, it is assumed that the UE 20 is performing communication in the 3GPP communication area. At this time, it is assumed that a communication bearer is established between the SGW 60 and the PGW 11 using PMIPv6 or GTP tunnel (S31).

Next, the case where the UE 20 moves from the 3GPP communication area to the Non-3GPP communication area is described. At this time, the UE 20 detects the IP access device 32 (S32). When the UE 20 detects the IP access device 32, an authentication process is performed between the UE 20 and the IP access device 32 (S33). In addition, authentication for the UE 20 is also performed in the network (S34). In the authentication process in step S34, the HSS 12 / AAA server 31 needs to transmit the PGW ID of the PGW 11 that established the PDN Connection used for communication with the UE 20 to the AAA proxy 71. There is. However, there is a possibility that the PGW ID of the PGW 11 that established the PDN Connection used by the HSS 12 in communication with the UE 20 is deleted from the HSS 12 due to the restart of the HSS 12. In this case, the HSS 12 issues an inquiry to the MME 14 to which the UE 20 has moved, and thereby obtains the PGW ID of the PGW 11 that has established a PDN Connection used for communication with the UE 20. do. Next, the HSS 12 transmits the PGW ID of the PGW 11 to the AAA proxy 71. The AAA proxy 71 is used as a Proxy server of the AAA server 31.

The AAA server 31 when the PGW ID of the PGW 11 that established the PDN Connection used by the HSS 12 for communication with the UE 20 has been deleted from the HSS 12 due to the restart of the HSS 12, The authentication process performed between the HSS 12 and the MME 14 is described in detail below with reference to FIG. When the restart operation is started in the HSS 12 (S41), the HSS 12 transmits a RESET message to the relevant MME (S42). Upon receiving the RESET message, the MME 14 generates a list of all subscribers accepted (or recorded) on the HSS 12 to which the RESET message has been sent, sets the generated list in the RESET ANSWER message, and sends the RESET ANSWER message to the RESET ANSWER message. The data is transmitted to the HSS 12 (S43). The subscriber list set up in this process may include International Mobile Subscriber Identities (IMSIs) or may include other User Identities. By maintaining a list of subscribers for each MME, HSS 12 may manage the relationships between the MMEs and subscribers to which subscribers have moved during and after the RESET process. These relationships enable the operation of the query from the HSS 12 to the MME 14, which will be described below. However, these relationships may also be used for other operations such as subscriber location lookup and service provision from the MTC server at the start of the network. Here, it is assumed that the UE 20 moves from the 3GPP communication area to the Non-3GPP communication area (S44).

As an authentication request for the UE 20, the HSS 12 receives a STa Access Authentication and Authorization Request message from the AAA server 31 (S45). In the STa Access Authentication and Authorization Request message, a parameter corresponding to IMSI is set as a User Identity. When the HSS 12 does not hold a PGW ID corresponding to the User Identity, the HSS 12 also sends a Status request message to the MME (S46). This message includes an information element for requesting subscriber information corresponding to the IMSI and information about the PGW ID of the PGW 11 that established the PDN Connection used for communication with the UE 20. In addition, the Status request message may be a RESET REQUEST message or other messages. Upon receiving the Status request message, the MME 14 sets the PGW ID of the PGW 11 that established the PDN Connection used for communication with the UE 20 in the Status answer message, and sets the Status answer message to the HSS 12. (S47). In addition, the status answer message may be a RESET ANSWER message or other messages. The HSS 12 transmits to the AAA server 31 a Trusted non-3GPP Access Authentication and Authorization Answer message in which information about the PGW ID of the PGW 11 that established the PDN Connection used for communication with the UE 20 is set. (S48).

Here, referring again to FIG. 14, the description of step S34 and subsequent steps continues.

In the authentication process at step S34, the AAA proxy 71 transmits the PGW ID received from the HSS 12 / AAA server 31 to the IP access device 32.

Next, the UE 20 performs an L3 Attach Trigger process between the UE 20 and the IP access device 32 (S35). In this way, for example, the UE 20 transmits the information about the APN used for communication in the 3GPP communication area to the IP access device 32.

Next, a Gateway Control Session Establishment Procedure is performed between the IP access device 32 and the Policy and Charging Rules Function (vPCRF) 72 and then between the vPCRF 72 and the hPCRF 73 (S36). PCRFs are node devices that manage QoS policies, etc., associated with the UE 20. When the UE 20 roams, the vPCRF 72 performs policy control related to the UE 20 in the network where the UE 20 roams. The hPCRF 73 performs policy control related to the UE 20 within the home network of the UE 20.

In step S36, the hPCRF 73 transmits QoS policy information and the like related to the UE 20 to the vPCRF 72. In addition, the vPCRF 72 transmits (i.e. transmits) QoS policy information and the like related to the UE 20 to the IP access device 32.

Next, the IP access device 32 transmits a Proxy Binding Update message to the PGW 11 using the PGW ID of the PGW 11 received in step S34 (S37). By receiving the Proxy Binding Update message, the PGW 11 associates the PDN Connection used for communication with the UE 20 in the 3GPP communication area with a communication bearer or communication connection in the Non-3GPP communication area, and the UE 20. Performs a handover process.

As described above, by using the mobile communication system according to the fifth exemplary embodiment of the present invention, the HSS 12 uses the authentication process request sent from the AAA server 31 to allow the UE 20 to receive the request. An inquiry can be issued to the moved MME 14. As a result, the HSS 12 can acquire the PGW ID of the PGW 11 which has established the PDN connection used for communication with the UE 20.

In this manner, even when the UE 20 makes a move that involves (or requires) a change of the MME after the restart of the HSS 12, the HSS 12 moves with respect to the UE 20 after the UE 20 moves. The PGW ID of the PGW 11 establishing the PDN Connection used for communication with the UE 20 may be received from the MME 14 performing management. Therefore, the AAA server 31 can obtain the PGW ID associated with the UE 20 from the HSS 12 even after restarting the HSS 12. As a result, the UE 20 can access after the movement the same PGW as the PGW accessed by the UE 20 before the movement, and thus use that PGA as an anchor point to hand from the 3GPP communication area to the Non-3GPP communication area. Over can be performed properly. As a result, the UE can continue to receive service from the external network via the same PGW even from the area where the UE has moved.

Further, in the fifth exemplary embodiment, immediately after the HSS 12 is restarted and the MME receives the RESET signal, the UE 20 does not communicate with the MME at all and moves from the 3GPP communication area to the Non-3GPP communication area. Even when moving, the AAA server 31 can acquire the PGW ID of the PGW 11 which has established the PDN connection used for communication with the UE 20. Thus, beneficial effects similar to those described above can be achieved.

Note that the fifth exemplary embodiment has been described mainly using the MME as the mobility management apparatus 100. However, as shown in FIG. 9, SGSN 110 and SGSN 111 may be used in place of MMEs. In this case, the MMEs 13 and 14 in FIG. 2 are replaced with SGSNs 110 and 111 respectively. Also, the eNBs 40 and 41 in FIG. 2 are replaced with RNCs 130 and 131, respectively. In addition, the HSS 12 in FIG. 2 is replaced with the HLR 120. In this case, the UE 20 performs a Routing Area Update (RAU) process instead of the TAU process and transmits a RAU Request message to the SGSN 111 via the RNC.

Although the present invention is described as a hardware configuration in the exemplary embodiments described above, the present invention is not limited to the hardware configurations. In the present invention, processes in each of the node devices constituting the mobile communication system can also be implemented by causing a central processing unit (CPU) to execute a computer program.

In the examples described above, the program can be stored in various types of non-transitory computer readable media and supplied to the computers. Non-transitory computer readable media includes various types of tangible storage media. Examples of non-transitory computer readable media include magnetic recording media (such as flexible disks, magnetic tapes, and hard disk drives), optical-magnetic recording media (such as optical-magnetic disks), and read-only memory (CD-ROM). , CD-R, and CD-R / W, and semiconductor memory (such as ROM, Programmable ROM (PROM), Erratable PROM (EPROM), Flash ROM, and Random Access Memory (RAM)). In addition, the program may be supplied to the computers using various types of temporary computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. Temporary computer readable media can be used to supply programs to a computer via wired communication paths, such as electrical wiring and optical fibers, or via wireless communication paths.

It is noted that the present invention is not limited to the exemplary embodiments described above, and that various changes may be made without departing from the spirit and scope of the present invention.

Although the present invention is described above with reference to exemplary embodiments, the present invention is not limited to the exemplary embodiments described above. Various modifications that can be understood by those skilled in the art can be made to the construction and details of the invention within the scope of the invention.

This application is based on Japanese Patent Application No. 2015-193034, filed September 30, 2015, and claims the benefit therefrom, the disclosures of which are incorporated herein by reference in their entirety.

All or part of the exemplary embodiments described above may be described as, but not limited to, the following appendices.

(Book 1)

As a mobile communication system,

A PGW configured to establish a PDN Connection used for communication with a mobile communication terminal;

The HSS-PGW ID configured to hold a PGW ID is an identifier of the PGW; And

A mobility management device configured to perform mobility management of the mobile communication terminal,

When the mobile management device receives the Tracking Area Update message transmitted from the mobile communication terminal, regardless of the holding status of the PGW ID in the HSS, the mobile management device sends an HSS Update Location Request message including the PGW ID set therein. Send to

(Book 2)

A mobile communication system described in Appendix 1,

When the mobility management device which performs the mobility management of the mobile communication terminal is changed from the first mobility management device to the second mobility management device due to the movement of the mobile communication terminal,

The first mobility management apparatus transmits a Context Response message including registration information on the mobile communication terminal set therein to the second mobility management apparatus;

The second mobility management device transmits an Update Location Request message including the PGW ID set therein to the HSS when information indicating that the HSS has been restarted is set in the registration information.

(Appendix 3)

A mobile communication system described in Appendix 1,

When the mobility management device which performs the mobility management of the mobile communication terminal is changed from the first mobility management device to the second mobility management device due to the movement of the mobile communication terminal,

The first mobility management apparatus transmits a Context Response message to the second mobility management apparatus including command information set therein based on at least one of the Access-Restriction-Data and the information indicating that the HSS has been restarted. The information instructs the second mobility management device to send an HSS an Update Location Request message including the PGW ID set therein.

(Appendix 4)

A mobile communication system described in Appendix 2 or 3,

The first mobility management device sends a Context Response message including a Context Identifier set therein to the second mobility management device, where the Context Identifier is an identifier of the PDN Connection;

The second mobility management device transmits an Update Location Request message in which the Active APN AVP including the Context Identifier and the PGW ID is set, to the HSS.

(Appendix 5)

A mobile management device, when receiving a Tracking Area Update message transmitted from a mobile communication terminal, regardless of the holding status of the PGW ID in the HSS holding the PGW ID, the Update Location Request message including the PGW ID set therein is HSS. And a communication unit configured to transmit to the PGW ID, which is a PGW ID of a PGW that has established a PDN connection used for communication with the mobile communication terminal.

(Supplementary Note 6)

A mobility management device described in Appendix 5,

When the mobility management device which performs the mobility management of the mobile communication terminal is changed from the first mobility management device to its own device due to the movement of the mobile communication terminal,

The communication unit receives a Context Response message including registration information for the mobile communication terminal set therein, which is transmitted from the first mobile management apparatus, and is set internally when the information indicating that the HSS has been restarted is set in the registration information. The Update Location Request message including the PGW ID is transmitted to the HSS.

(Appendix 7)

A mobility management device described in Appendix 6,

The communication unit receives a Context Response message including a Context Identifier set internally from the first mobility management device, the Context Identifier is an identifier of the PDN Connection, and an Update Location where an Active APN AVP including a Context Identifier and a PGW ID is set. Send a request message to the HSS.

(Appendix 8)

A mobility management device described in Appendix 5,

When the mobility management device which performs the mobility management of the mobile communication terminal is changed from its own device to the second mobility management device due to the movement of the mobile communication terminal,

The communication unit transmits to the second mobility management apparatus a Context Response message in which the registration information for the mobile communication terminal including the information indicating that the HSS is restarted is set.

(Appendix 9)

A mobility management device described in Appendix 5,

When the mobility management device which performs the mobility management of the mobile communication terminal is changed from its own device to the second mobility management device due to the movement of the mobile communication terminal,

The communication unit, based on at least one of the Access-Restriction-Data and the information indicating that the HSS has been restarted, transmits a Context Response message including the command information set therein to the second mobility management apparatus. Instructs the mobility management device to send an HSS an Update Location Request message containing the PGW ID set internally-.

(Book 10)

A mobile management apparatus described in annex 8 or 9, wherein the communication unit transmits a Context Response message including a Context Identifier set therein to the second mobile management apparatus, where the Context Identifier is an identifier of the PDN Connection.

(Appendix 11)

As a communication method, upon receiving a Tracking Area Update message transmitted from a mobile communication terminal, an Update Location Request message including a PGW ID set therein is sent to the HSS, regardless of the state of possession of the PGW ID in the HSS having the PGW ID. Transmitting, wherein the PGW ID is a PGW ID of a PGW that has established a PDN connection used for communication with the mobile communication terminal.

(Appendix 12)

As the communication method described in Appendix 11,

When the mobility management device which performs the mobility management of the mobile communication terminal is changed from the first mobility management device to its own device due to the movement of the mobile communication terminal,

Receiving a Context Response message including registration information for a mobile communication terminal set therein, which is transmitted from a first mobility management device when receiving a Tracking Area Update message transmitted from a mobile communication terminal,

When the information indicating that the HSS has been restarted is set in the registration information, the method further includes transmitting an Update Location Request message including the PGW ID set therein to the HSS.

(Appendix 13)

As the communication method described in Appendix 11,

When the mobility management device which performs the mobility management of the mobile communication terminal is changed from its own device to the second mobility management device due to the movement of the mobile communication terminal,

The method may further include transmitting a Context Response message in which the registration information for the mobile communication terminal including the information indicating that the HSS is restarted is transmitted to the second mobile management device in a tracking area update process for the mobile communication terminal.

(Book 14)

When the computer receives the Tracking Area Update message transmitted from the mobile communication terminal, the computer sends an Update Location Request message including the PGW ID set therein to the HSS, regardless of the retention status of the PGW ID in the HSS having the PGW ID. Transmitting, wherein the PGW ID is a PGW ID of a PGW that has established a PDN connection used for communication with a mobile communication terminal.

10 mobile communication terminals
11 PGW
12 HSS
13 MME
14 MME
15 control unit
16 control unit
20 UE
21 3GPP Communications Department
22 Non-3GPP Communication Department
31 AAA Server
32 IP Access Device
40 eNB
41 eNB
50 SGW
60 SGW
70 PCRF
71 AAA Proxy
72 vPCRF
73 hPCRF
100 mobility management device
110 SGSN
111 SGSN
120 HLR
130 RNC
131 RNC

Claims (15)

As a communication system,
A Packet Data Network (PDN) Gateway configured to establish a PDN Connection between the P-GW and the user equipment;
A subscriber information management device configured to store a P-GW ID (P-GW Identity) which is an identifier for the P-GW;
Mobility Management Entity (MME) configured to perform mobility management for the user equipment supporting handover from a network to a non-3GPP (3rd Generation Partnership Project) network
Including,
When the MME is changed and the subscriber information management device is reset, the new MME sends a message in which a P-GW ID is set in a tracking area update (TAU) procedure or a routing area update (RAU) procedure. Communication system to send to. The method of claim 1,
When the MME is changed after the subscriber information management device is reset, in the TAU procedure or the RAU procedure, the new MME transmits a message for setting the P-GW ID to the subscriber information management device. . The method according to claim 1 or 2,
The new MME receives a TAU Request message or a RAU Request message from the user equipment, and the P-GW ID is set in the TAU procedure or the RAU procedure based on the TAU Request message or the RAU Request message. And transmit to the subscriber information management device. A mobility management entity (MME) for performing mobility management of user equipment supporting handover from a network to a non-3GPP (3rd Generation Partnership Project) network.
To store a P-GW ID (P-GW Identity) which is an identifier for a PDN (Packet Data Network) Gateway (P-GW) configured to change the MME and establish a PDN Connection between the P-GW and the user equipment. When the configured subscriber information management device is reset, a transmitter configured to transmit a message for setting the P-GW ID to the subscriber information management device in a tracking area update (TAU) procedure or a routing area update (RAU) procedure. Mobility Management Entity (MME) comprising a. The method of claim 4, wherein
The transmitter is configured to, when the MME is changed after the subscriber information management device is reset, send a message to the subscriber information management device in which the P-GW ID is set in the TAU procedure or in the RAU procedure. Mobility Management Entity (MME). The method according to claim 4 or 5,
A receiver configured to receive a TAU Request message or a RAU Request message from the user equipment,
The transmitter is further configured to transmit to the subscriber information management device a message for which the P-GW ID is set in the TAU procedure or the RAU procedure based on the TAU Request message or the RAU Request message. Management Entity). As a movement management method,
Mobility Management Entity (MME) that performs mobility management of user equipment supporting handover from network to non-3GPP (3rd Generation Partnership Project) network is changed and establish PDN connection between P-GW and the user equipment If the subscriber information management device configured to store a P-GW Identity (P-GW Identity), which is an identifier for a configured Packet Data Network (PDN) Gateway (P-GW), is reset, the Tracking Area Update (TAU) procedure Or transmitting a message to which the P-GW ID is set to the subscriber information management apparatus in a routing area update (RAU) procedure. The method of claim 7, wherein
And when the MME is changed after the subscriber information management device is reset, transmitting a message in which the P-GW ID is set in the TAU procedure or the RAU procedure to the subscriber information management device. Way. The method according to claim 7 or 8,
Receiving a TAU Request message or a RAU Request message from the user equipment; And
Transmitting, to the subscriber information management device, a message for which the P-GW ID is set in the TAU procedure or the RAU procedure based on the TAU Request message or the RAU Request message.
Movement management method further comprising. A computer readable storage medium,
When executed by a computer, cause the computer to:
Mobility Management Entity (MME) that performs mobility management of user equipment supporting handover from network to non-3GPP (3rd Generation Partnership Project) network is changed and establish PDN connection between P-GW and the user equipment If the subscriber information management device configured to store a P-GW Identity (P-GW Identity), which is an identifier for a configured Packet Data Network (PDN) Gateway (P-GW), is reset, the Tracking Area Update (TAU) procedure Or sending a message to which the P-GW ID is set in the Routing Area Update (RAU) procedure to the subscriber information management device. The method of claim 10,
If the MME is changed after the subscriber information management device is reset, sending a message to which the P-GW ID is set in the TAU procedure or the RAU procedure to the subscriber information management device. Possible storage medium. User equipment that supports handover from a network to a non-3GPP (3rd Generation Partnership Project) network.
Memory for storing instructions; And
At least one processor configured to process the instructions
Including, the instructions,
Establish a Packet Data Network (PDN) connection between a P-GW (P-GW) and the user equipment;
Sending a Tracking Area Update (TAU) Request message or Routing Area Update (RAU) Request message to the network,
When a mobility management entity (MME) that performs mobility management for the user equipment is changed and a subscriber information management device configured to store a P-GW ID (P-GW Identity), which is an identifier for the P-GW, is reset. And the at least one processor is further configured to process instructions for causing the new MME to send a message for which the PGW ID is set to the subscriber information management device by sending the TAU Request message or the RAU Request message to a new MME. User equipment composed. The method of claim 12,
If the MME is changed after the subscriber information management device is reset, the at least one processor transmits the TAU Request message or the RAU Request message to the new MME so that the new MME sets the PGW ID. User equipment configured to process instructions to send a message to the subscriber information management device. A communication method for user equipment that supports handover from a network to a non-3GPP (3rd Generation Partnership Project) network,
Establishing a packet data network (PDN) connection between a P-GW (P-GW) and the user equipment;
Transmitting a tracking area update (TAU) request message or a routing area update (RAU) request message to the network; And
When a mobility management entity (MME) that performs mobility management for the user equipment is changed and a subscriber information management device configured to store a P-GW ID (P-GW Identity), which is an identifier for the P-GW, is reset. Sending the TAU Request message or the RAU Request message to the new MME so that the new MME sends a message for setting the PGW ID to the subscriber information management apparatus.
Communication method comprising a. The method of claim 14,
Sending the TAU Request message or the RAU Request message to the new MME to cause the new MME to transmit a message for which the PGW ID is set to the subscriber information management device; The method of communication performed if it is changed after it is reset.

Images