JP5756705B2 - Network reconnection system - Google Patents

Description

  The present invention relates to a network reconnection system, and more particularly to a network reconnection system for reconnecting a bearer in a mobile phone service that is always connected.

  The mobile phone service is indispensable for daily life, but the current third generation mobile phone service provides various services such as Internet connection. For example, it is possible to enjoy video program content such as dramas. The mobile phone service is evolving to the next generation service of LTE (Long Term Evolution) that can provide a service of higher capacity communication.

  Now, as shown in FIG. 26, in the current mobile phone service network 100 as described in Non-Patent Document 1, a mobile device (UE) 101 possessed by a user, a service for providing content, and the like A providing apparatus 102 is connected to an S-GW (Serving Gateway) 101 that is a first gateway apparatus and a P-GW (Packet Data Network Gateway) 102 that is a second gateway apparatus. Therefore, in order to establish a connection between the UE 101 and the service providing apparatus 102, interface processing S1 between the UE 101 and the S-GW 103, interface processing S5 between the S-GW 103 and the P-GW 104, P- It is necessary to perform interface processing SGi between the GW 104 and the service providing apparatus 102.

  However, in the next-generation service network 200, the S-GW 103 and the P-GW 104 are accommodated in the same casing. For this reason, when establishing a connection between the UE 101 and the service providing apparatus 102, it is not necessary to perform the interface process S5 between the S-GW 103 and the P-GW 104.

3GPP (Third Generation Partnership Project) TS 23.401 V10.3.0

  However, when the UE 101 moves from the current area to another area in the next-generation service network that is assumed to be always connected, the S-GW of the destination area is selected instead of the S-GW 103. -The GW 104 may be in a state where the P-GW 104 in the area when the power is turned on remains selected.

  For example, as shown in FIG. 27, when Mr. A having a UE 101A arrives at an airport and the UE 101A is turned on in the area A where the airport is located, the UE 101A passes through the S-GW 103 and the P-GW 104. And the service providing apparatus 102 are connected. However, when returning to the office where Mr. A works, the S-GW 106 in the area B where the office is located is selected. However, the P-GW 107 in the area A when the power is turned on is still selected without the P-GW 107 in the area B being selected.

  Similarly, as shown in FIG. 28, when Mr. B having UE 101B and Mr. C having UE 101C arrive at the airport and the UE 101B and UE 101C are turned on in the area A where the airport is located, the area A where the airport is located S-GW 103 and P-GW 104 are selected. However, when returning to the office where Mr. B and Mr. C work, the S-GW 106 in the area B where the office is located is selected, but the P-GW 104 in the area A when the power is turned on is still selected. State.

  In a network such as LTE that assumes a constant connection, there is no trigger for reconnecting a bearer that is a logical packet transmission path. For this reason, when the UE moves to a different area, the S-GW of the destination area is selected for the S-GW, but the P-GW of the area when the power is turned on remains selected for the P-GW. It is a state. Then, the interface processing S5 between the S-GW 103 and the P-GW 104 must be performed. By performing this processing, each S-GW and P-GW of the network 200, and also for relaying the network 200 In some cases, the amount of traffic such as a switching device, a network device such as a relay router, and a transmission path between stations where each device is accommodated increases.

Such a situation does not occur only when the user moves between the airport and the office. For example, this occurs when the user moves between the office and home, and also when the user moves between the metropolitan areas of Tokyo and Osaka.
As described above, when a connection (outgoing) is performed, a network topology with the best resource utilization efficiency is selected by a known technique. However, a connection topology is inefficient due to user mobility or the like. May result in a connection configuration.
Therefore, in view of the above problems, the present invention can reconstruct a connection configuration with an efficient topology when the connection configuration becomes an inefficient network topology due to user mobility or the like. An object of the present invention is to provide a network reconnection system that can be used.

In order to achieve the above object, a network reconnection system according to the present invention is configured as follows.
A first network reconnection system according to the present invention includes a trigger detection unit that detects a reconnection trigger for reconnecting a bearer in a constantly connected network, and a bearer in which the reconnection trigger is detected by the trigger detection unit. Reconnection timing determination unit for determining reconnection timing for performing reconnection processing, and reconnection processing of the bearer in which the reconnection trigger is detected based on the reconnection timing determined by the reconnection timing determination unit A reconnection instruction unit that outputs a reconnection instruction so as to perform communication processing control for performing reconnection processing of a bearer in which the reconnection trigger is detected based on the reconnection instruction output from the reconnection instruction unit and a section, the reconnection timing determining unit bearer the reconnection trigger is detected, performs the reconnection process必A service determination unit that determines whether the service is used for a certain service, and the reconnection timing determination unit needs to perform reconnection processing by the service determination unit among bearers in which the reconnection trigger is detected to determine the reconnection timing of the determined bearers and are used in a service, characterized in Rukoto.

According to said 1st network reconnection system, a trigger detection part detects the trigger for reconnecting the bearer of the always-connected network. Then, the reconnection timing determination unit determines the reconnection timing for reconnecting the bearer used for the service requiring the reconnection whose trigger is detected by the trigger detection unit. A reconnection instruction | indication part reconnects the bearer used for the service which requires reconnection based on reconnection timing. In an always-connected network, when a mobile device moves to a different area, the gateway devices (P-GW and S-GW) may remain selected across the two areas. It was. Therefore, the reconnection instructing unit reconnects the bearer used for the service that requires reconnection (reconnects after disconnecting the bearer). By disconnecting the bearer, the gateway device in the area before the movement is no longer used, and immediately after that, the gateway device in the current area is newly selected by connecting the bearer. In other words, according to the first network reconnection system, even if the mobile device moves to different areas, the gateway device does not remain in the selected state across the two areas. Select a gateway device for the area. In this way, when the connection configuration becomes a connection configuration in an inefficient network topology due to user mobility or the like, the connection configuration in the efficient topology can be reconstructed by prompting reconnection. It becomes possible.
Moreover, according to said 1st network reconnection system, a service determination part determines whether the bearer is used for the service which needs reconnection. Accordingly, when the reconnection timing determination unit determines the reconnection timing of the bearer used for the service that requires reconnection, the reconnection timing determination unit determines the reconnection timing for each service. And it becomes possible to reconnect only the bearer of a specific service.

The second network reconnection system according to the present invention is characterized in that the trigger detection unit detects, as the reconnection trigger, that transmission processing has been performed in the bearer.
According to said 2nd network reconnection system, a trigger detection part detects that the transmission process was performed in the network as a trigger of the reconnection process of a bearer. Thereby, a transmission is performed from the user's mobile device, and the bearer can be reconnected after the transmission process.

In a third network reconnection system according to the present invention, the trigger detection unit uses, as the reconnection trigger, that a gateway device in an area different from the gateway device in the area of the current mobile station is selected in the bearer. It is characterized by detecting.
According to said 3rd network reconnection system, a trigger detection part detects that another gateway apparatus (S-GW) was selected by the network as a trigger of the reconnection process of a bearer. As a result, the outgoing call processing is performed on the network, and when the user actually moves to another area and another gateway device (S-GW) is selected, the bearer can be reconnected. It becomes.

The fourth network reconnection system according to the present invention is characterized in that the reconnection timing determination unit sets the reconnection timing immediately after the trigger detection unit detects the trigger.
According to the fourth network reconnection system described above, the reconnection timing determination unit sets the reconnection timing immediately after the trigger described above is detected as the reconnection timing. And it becomes possible to reconnect a bearer at this connection timing.

In a fifth network reconnection system according to the present invention, the reconnection timing determination unit includes a timer unit for measuring time, and after the trigger is detected by the trigger detection unit, a time measured by the timer unit is predetermined. Immediately after the time elapses, the reconnection timing is set as the reconnection timing.
According to the fifth network reconnection system described above, the reconnection timing determination unit reconnects immediately after the trigger described above is detected and the time measured by the timer unit has passed a predetermined time. Timing. And it becomes possible to reconnect a bearer at this connection timing.

  In a sixth network reconnection system according to the present invention, the reconnection timing determination unit monitors whether or not the communication state of the bearer in which the reconnection trigger is detected is a non-communication state, A timer unit for timing, and after determining that the communication state of the bearer in which the reconnection trigger is detected by the non-communication monitoring unit is a non-communication state, the timer unit detects the reconnection trigger. The non-communication state time in which the detected bearer's communication state is a non-communication state is counted, and the reconnection timing determination unit is immediately after the non-communication state time measured by the timer unit has passed a predetermined time. Is the reconnection timing.

  According to the sixth network reconnection system described above, the reconnection timing determination unit determines that the bearer used for the service that requires reconnection by the non-communication monitoring unit is in a non-communication state for a predetermined time. Immediately after being set as the reconnection timing. And it becomes possible to reconnect a bearer at this connection timing.

A seventh network reconnection system according to the present invention includes a trigger detection unit that detects a reconnection trigger for reconnecting a bearer in a constantly connected network, and a bearer in which the reconnection trigger is detected by the trigger detection unit. Reconnection timing determination unit for determining reconnection timing for performing reconnection processing, and reconnection processing of the bearer in which the reconnection trigger is detected based on the reconnection timing determined by the reconnection timing determination unit A reconnection instruction unit that outputs a reconnection instruction so as to perform communication processing control for performing reconnection processing of a bearer in which the reconnection trigger is detected based on the reconnection instruction output from the reconnection instruction unit And the trigger detection unit uses the reconnection trigger to indicate that the call processing has been performed in the bearer. Detected, the reconnection timing determination section includes a non-communication monitoring unit communication state of bearer said reconnection trigger is detected to monitor whether the non-communication state, the non-communication monitoring unit, Pr when the mobile station based on the e Servation control procedure transitions to Pr e servation state, communication state of bearer said reconnection trigger is detected, characterized in that it is determined that the non-communication state.
The eighth network reconnection system according to the present invention includes a trigger detection unit that detects a reconnection trigger for reconnecting a bearer in a constantly connected network, and the trigger detection unit detects the reconnection trigger. A reconnection timing determination unit that determines a reconnection timing for performing a reconnection process of a bearer, and a reconnection of a bearer in which the reconnection trigger is detected based on the reconnection timing determined by the reconnection timing determination unit A reconnection instruction unit that outputs a reconnection instruction so as to perform processing, and communication that performs reconnection processing of a bearer in which the reconnection trigger is detected based on the reconnection instruction output from the reconnection instruction unit A processing control unit, wherein the trigger detection unit is a gateway device in a current mobile device area in the bearer. The gateway device in the area is selected as the reconnection trigger, and the reconnection timing determination unit determines whether the bearer communication state in which the reconnection trigger is detected is a no-communication state. comprising a non-communication monitoring unit that monitors, the non-communication monitoring unit, Pr e when Servation control procedure the mobile station on the basis of the transitions in Pr e servation state, communication state of bearer said reconnection trigger is detected no It is determined that the communication state is established.
According to the network reconnection system of the seventh and eighth above, non-communication monitoring unit, when the mobile station based on Pr e servation control procedure transitions to Pr e servation state, used in services requiring reconnect It is determined that the bearer being in the no-communication state. Thus, non-communication monitoring unit, even when provided in the construction unit of the network can not be monitored that direct communication bearer is a non-communication state, based on the Pr e servation control procedure It is possible to determine whether or not a bearer used for a service that requires reconnection is in a no-communication state.

Ninth network re-connection system according to the present invention, the bearers reconnection trigger is detected, the reconnection process includes determining the service determination unit whether used in service that needs to perform the re connection timing determination unit, wherein among the bearers reconnection trigger is detected, determining a reconnection timing of the service determination unit and I Ri is used to require a service re-connection process performed on the determined bearer It is characterized by doing.

According to said 9th network reconnection system, a service determination part determines whether the bearer is used for the service which needs reconnection. Accordingly, when the reconnection timing determination unit determines the reconnection timing of the bearer used for the service that requires reconnection, the reconnection timing determination unit determines the reconnection timing for each service. And it becomes possible to reconnect only the bearer of a specific service.

  According to the present invention, in an always-connected network, when the connection configuration becomes a connection configuration with an inefficient network topology due to user mobility or the like, by prompting reconnection, Rebuild the connection configuration. For this reason, when UE moves to a different area, it becomes unnecessary to perform the interface process between gateway apparatuses (S-GW and P-GW).

  Therefore, it is possible to suppress an increase in the amount of network traffic caused by performing the above interface processing, and to effectively use network resources. In particular, network devices such as network gateway devices, other network switching devices, network routers such as relay routers, and the amount of traffic on the transmission path between the stations where each device is housed can be suppressed. it can. Moreover, when the hardware and software which comprise a network are licensed products and the license fee is a pay-as-you-go system, these expenses can be suppressed.

It is a block diagram which shows schematic structure of the network 10 comprised using the network reconnection system of this invention. It is a block diagram which shows the function structure of MME12 in the case of reconnecting a bearer after detecting the trigger of a reconnection process in MME12 of the network which concerns on 1st Embodiment. It is a 1st sequence diagram which shows the flow of operation | movement of each apparatus which comprises the network 10 in the case of reconnecting a bearer after detecting transmission processing as a trigger of reconnection processing in MME12 of the network which concerns on 1st Embodiment. It is a 2nd sequence diagram which shows the operation | movement flow of each apparatus which comprises the network 10 in the case of reconnecting a bearer after detecting a transmission process as a trigger of a reconnection process in MME12 of the network which concerns on 1st Embodiment. It is a 3rd sequence diagram which shows the flow of operation | movement of each apparatus which comprises the network 10 in the case of reconnecting a bearer after detecting transmission processing as a trigger of reconnection processing in MME12 of the network which concerns on 1st Embodiment. It is a sequence diagram which shows the flow of operation | movement of each apparatus which comprises the network 10 in the case of reconnecting a bearer after detecting S-GW change process as a trigger of reconnection process in MME12 of the network which concerns on 1st Embodiment. It is a block diagram which shows the function structure of MME12 in the case of reconnecting a bearer after implementing the non-communication monitoring after detecting the trigger of a reconnection process in MME12 of the network which concerns on 2nd Embodiment. The flow of operation | movement of each apparatus which comprises the network 10 in the case of reconnecting a bearer after carrying out non-communication monitoring after detecting transmission processing as a trigger of reconnection processing in the MME 12 of the network according to the second embodiment is shown. It is a sequence diagram. After detecting the S-GW change process as a trigger for the reconnection process in the MME 12 of the network according to the second embodiment, and further performing non-communication monitoring, the operation of each device constituting the network 10 when the bearer is reconnected It is a sequence diagram which shows a flow. It is a block diagram which shows the function structure of P-GW104 in the case of reconnecting a bearer after detecting the trigger of a reconnection process in P-GW104 of the network which concerns on 3rd Embodiment. It is a sequence diagram which shows the flow of operation | movement of each apparatus which comprises the network 10 in the case of reconnecting a bearer after detecting transmission processing as a trigger of reconnection processing in P-GW104 of the network which concerns on 3rd Embodiment. The first flow chart showing the operation flow of each device constituting the network 10 when the S-GW change process is detected as a trigger of the reconnection process in the network P-GW 104 according to the third embodiment and then the bearer is reconnected. It is a sequence diagram. 2nd shows the operation | movement flow of each apparatus which comprises the network 10 in the case of reconnecting a bearer after detecting S-GW change process as a trigger of reconnection process in P-GW104 of the network which concerns on 3rd Embodiment. It is a sequence diagram. It is a block diagram which shows the function structure of P-GW104 in the case of reconnecting a bearer after implementing the non-communication monitoring after detecting the trigger of a reconnection process in P-GW104 of the network which concerns on 4th Embodiment. Operation flow of each device constituting the network 10 when the bearer is reconnected after detecting the transmission process as a trigger of the reconnection process in the P-GW 104 of the network according to the fourth embodiment and further performing the non-communication monitoring. FIG. After detecting the S-GW change process as a trigger for the reconnection process in the P-GW 104 of the network according to the fourth embodiment, and further performing non-communication monitoring, each device constituting the network 10 in the case of reconnecting the bearer It is a 1st sequence diagram which shows the flow of operation | movement. After detecting the S-GW change process as a trigger for the reconnection process in the P-GW 104 of the network according to the fourth embodiment, and further performing non-communication monitoring, each device constituting the network 10 in the case of reconnecting the bearer It is a 2nd sequence diagram which shows the flow of operation | movement. It is a block diagram which shows the function structure of PCRF14 in the case of reconnecting a bearer after detecting the trigger of a reconnection process in PCRF14 of the network which concerns on 5th Embodiment. It is a sequence diagram which shows the flow of operation | movement of each apparatus which comprises the network 10 in the case of reconnecting a bearer after detecting a transmission process as a trigger of a reconnection process in PCRF14 of the network which concerns on 5th Embodiment. It is a sequence diagram which shows the flow of operation | movement of each apparatus which comprises the network 10 in the case of reconnecting a bearer after detecting S-GW change process as a trigger of a reconnection process in PCRF14 of the network which concerns on 5th Embodiment. It is a block diagram which shows the function structure of P-GW104 in the case of reconnecting a bearer after implementing the non-communication monitoring after detecting the trigger of a reconnection process in PCRF14 of the network which concerns on 6th Embodiment. In the PCRF 14 of the network according to the sixth embodiment, after detecting the calling process as a trigger for the reconnection process, and further performing the non-communication monitoring, the operation flow of each device constituting the network 10 when the bearer is reconnected is shown. FIG. 3 is a first sequence diagram. In the PCRF 14 of the network according to the sixth embodiment, after detecting the calling process as a trigger for the reconnection process, and further performing the non-communication monitoring, the operation flow of each device constituting the network 10 when the bearer is reconnected is shown. It is a 2nd sequence diagram. After detecting the S-GW change process as a trigger for the reconnection process in the PCRF 14 of the network according to the sixth embodiment, and further performing the no-communication monitoring, the operation of each device constituting the network 10 when the bearer is reconnected It is a 1st sequence diagram which shows a flow. After detecting the S-GW change process as a trigger for the reconnection process in the PCRF 14 of the network according to the sixth embodiment, and further performing the no-communication monitoring, the operation of each device constituting the network 10 when the bearer is reconnected It is a 2nd sequence diagram which shows a flow. It is a schematic diagram which shows schematic structure of the networks 100 and 200 on the assumption of the conventional continuous connection. It is the 1st schematic diagram which shows S-GW103 and P-GW104 selected in the network 200 on the assumption of the conventional continuous connection. It is the 2nd schematic diagram which shows selected S-GW103 and P-GW104 in the network 200 on the assumption of the conventional continuous connection.

Hereinafter, preferred embodiments of a network configured using a network reconnection system of the present invention will be described in detail with reference to the accompanying drawings.
(Configuration of network 10)
First, a schematic configuration of a network 10 according to an embodiment of the present invention will be described with reference to FIG.
A network 10 illustrated in FIG. 1 includes a service providing apparatus 102, an S-GW 103, and a P-GW 104 that configure the network 100 described with reference to FIG. 26 described in the background art. Further, the network 10 includes, as devices other than those devices, an eNB (evolutional Node B) 11, an MME (Mobility Management Entity) 12, an HSS (Home Subscriber Server) 13, and a PCRF (Policy and Charging Rule 14). And is configured.

The UE 101 is a mobile phone, a smartphone, a data communication card, or the like possessed by the user. Therefore, the UE 101 is connected to the service providing apparatus 102 via each apparatus configuring the network 10 such as the S-GW 103, the P-GW 104, and the MME 12.
The service providing apparatus 102 performs control for providing a service such as an Internet connection service of a communication carrier. Further, the network 10 is not limited to the service providing apparatus 102 but may be provided with a service providing apparatus that provides a service different from the service providing apparatus 102.

S-GW 103 and P-GW 104 are gateway devices. The S-GW 103 mainly performs packet routing control. Further, the P-GW 104 mainly performs control for connecting to an external network such as the Internet.
The eNB 11 is a base station and is an interface between the UE 101 owned by the user and the network 10.
The MME 12 accommodates a base station and mainly performs mobility control of the UE 101 and the like.
The HSS 13 manages subscriber information. The subscriber information is, for example, information on whether or not the user has subscribed to the LTE mobile phone service.
The PCRF 14 performs priority control, billing control, etc. according to the service.

In the always-on network 10, the bearer can be reconnected by any one of the MME 12, the P-GW 104, and the PCRF 14.
In addition, eNB11, MME12, S-GW103, and P-GW104 demonstrated above are apparatuses corresponding to the area A. FIG. And as an apparatus corresponding to these apparatuses, there are eNB15, MME16, S-GW106, and P-GW107. These devices are devices corresponding to the area B which is an area different from the area A as described in the background art.

There are two methods for reconnecting the always-connected bearer. The first is a method of reconnecting a bearer immediately after each device detects a trigger for reconnection processing. The second method is a method of reconnecting a bearer after detecting whether or not the communication state of the bearer is a non-communication state after each device detects the trigger of the reconnection process.
Furthermore, there are two types of triggers for reconnection. First, the time when each device performs a transmission process from the UE 101 is a trigger for the reconnection process. The second is a trigger for reconnection processing when an S-GW different from the S-GW currently connected to each device is connected to each device.
In other words, there are a total of four methods for reconnecting each device in combination with the above. First, the case where a bearer is reconnected in the MME 12 will be described.

(First embodiment)
(Functional configuration of the MME 12 when the bearer is reconnected after detecting the reconnection processing trigger in the MME 12)
First, with reference to FIG. 2, the functional configuration of the MME 12 in the case where the bearer is reconnected after detecting the trigger of the reconnection process in the MME 12 of the network 10 will be described.
The MME 12 illustrated in FIG. 2 includes a communication processing control unit 21, a trigger detection unit 22, a reconnection timing determination unit 23, and a bearer reconnection instruction unit 24.

The communication processing control unit 21 transmits / receives a request, a response, and the like to / from each device configuring the network 10 and collectively controls each unit in the MME 12.
The trigger detection unit 22 detects a trigger for reconnecting a constantly connected bearer. The trigger detection unit 22 confirms that the call processing has been performed by the always-connected bearer from the UE 101 or that an S-GW different from the S-GW currently connected to each device is connected to each device. Detect as a trigger to reconnect the always-connected bearer.

Based on the trigger detected by the trigger detection unit 22, the reconnection timing determination unit 23 determines a reconnection timing that is a timing for reconnecting a constantly connected bearer. For example, the reconnection timing determination unit 23 sets the reconnection timing immediately after the trigger detection unit 22 detects the trigger.
The reconnection timing determination unit 23 includes a timer unit 31. When the trigger is detected by the trigger detection unit 22 and the bearer is reconnected after a predetermined time has elapsed, the timer unit 31 measures the time. For example, the reconnection timing determination unit 23 sets the reconnection timing immediately after a trigger is detected by the trigger detection unit 22 and a predetermined time has elapsed.

  Note that an operator on the network side sets an optimal time for a predetermined time from when the time is started by the timer unit 31 or the like described above until reconnection is executed. Of course, the optimal time is set so as not to give a sense of incongruity to the user who uses the always-connected network 10 due to the reconnection of the bearer, although it varies depending on the network traffic model and the service provision form. Just do it.

In the case where the bearer is reconnected immediately after the trigger is detected by the trigger detection unit 22, the timer unit 31 is not necessary. Alternatively, the process of counting time by the timer unit 31 may be stopped.
Furthermore, the reconnection timing determination unit 23 includes a service determination unit 32. The service determination unit 32 confirms the APN (Access Point Name) to determine whether the bearer whose trigger is detected by the trigger detection unit 22 is used to provide a service that requires reconnection. judge.

  For example, there are three services a to c, and the service requiring reconnection is only service a. In this case, the reconnection timing determination unit 23 determines the reconnection timing of the bearer only when it is determined that the bearer whose trigger is detected by the service determination unit 32 is used to provide the service a. . In addition, when a trigger is detected regardless of a service, it is not necessary to provide the service determination unit 32 when reconnecting bearers of all users.

The bearer reconnection instruction unit 24 outputs an instruction to the communication processing control unit 21 so as to reconnect the always-connected bearer at the reconnection timing determined by the reconnection timing determination unit 23.
The communication processing control unit 21, the trigger detection unit 22, the reconnection timing determination unit 23, and the bearer reconnection instruction unit 24 described above function as a network reconnection system.

(Operations of each device constituting the network 10 when the MME 12 detects the calling process as a trigger for the reconnection process and then reconnects the bearer)
Next, with reference to FIG. 3 to FIG. 5, the operation of each device configuring the network 10 when the bearer is reconnected after detecting the calling process as a trigger for the reconnection process in the MME 12 of the network 10 will be described. Note that each sequence diagram showing the operation of each device constituting the network 10 shows only the devices necessary for explanation.

  As shown in FIG. 3, first, the MME 12 holds an APN of a service that needs to be reconnected (step S101). Thereafter, when the user makes a call, each device configuring the network 10 performs a call process shown in step S102. Since the calling process is publicly known, only the process necessary for explaining the bearer reconnection process is extracted from the calling process. The transmission processing here includes transmission by Attach and transmission by Multi-PDN.

First, the UE 101 transmits an EMM_Attach Request to the eNB 11 (Step S102-1). Further, the eNB 11 transmits an EMM_Attach Request to the MME 12 (Step S102-2).
Authentication and NAS Security processing is performed between the devices of the network 10 (steps S102-3 and S102-4).

By transmitting / receiving Diameter_Update Location Request and Diameter_Update Location Answer between the MME 12 and the HSS 13, the HSS 13 determines the contract status of the always-on mobile phone service (steps S102-5 to S102-7).
The MME 12 performs control for selecting the S-GW 103 in a DNS (Domain Name System) procedure (step S102-8). Subsequently, the MME 12 performs control for selecting the P-GW 104 using the DNS procedure (step S102-9).

  Subsequently, as illustrated in FIG. 4, the MME 12 transmits a GTPv2_Create Session Request to the S-GW 103 (Step S102-10). By transmitting and receiving Diameter_CC-Request and Diameter_CC-Answer between the S-GW 103 and the PCRF 14 (steps S102-11 and S102-12), the PCRF 14 transmits QoS information and event triggers to the S-GW 103. Etc. are generated.

  Furthermore, the S-GW 103 transmits PMIPv6_Proxy Binding Update to the P-GW 104 (step S102-13). By transmitting and receiving Diameter_CC-Request and Diameter_CC-Answer between the P-GW 104 and the PCRF 14 (steps S102-14 and S102-15), the PCRF 14 sends QoS information and charging-related parameters to the P-GW 104. Etc. are generated. Finally, the P-GW 104 transmits PMIPv6_Proxy Binding Ack to the S-GW 103 (step S102-16).

The S-GW 103 transmits a GTPv2_Delete Session Response, which is a response to the GTPv2_Create Session Request, to the MME 12 (Step S102-17).
The MME 12 transmits an EMM_Attach Accept indicating that the EMM_Attach process has been accepted to the eNB 11 (step S102-18). Then, NAS Security processing is performed between the devices of the network 10 (step S102-19).

  Thereafter, the eNB 11 transmits RRC_RRC Connection Reconfiguration to the UE 101 (step S102-20). When the process based on the RRC_RRC Connection is completed, the UE 101 transmits an RRC_RRC Connection Reconfiguration Complete to the eNB 11 (Step S102-21). Thereafter, the eNB 11 transmits an S1 AP_Initial Context Setup Response to the MME 12 (step S102-22).

  Finally, UE101 transmits RRC_Direct Transfer to eNB11 (step S102-23). Furthermore, eNB11 transmits EMM_Attach Complete which shows that the EMM_Attach process was completed with respect to MME12 (step S102-24). On the other hand, MME12 transmits EMM Information with respect to UE101 (step S102-25).

  And the trigger detection part 22 detects that the transmission process was performed. As illustrated in FIG. 5, when the reconnection timing determination unit 23 of the MME 12 determines that the service provided using the bearer is a service that needs to be reconnected (YES in step S103), The bearer is stored as a bearer to be reconnected. Specifically, the reconnection timing determination unit 23 stores an identifier or the like for identifying a bearer. Then, the timer unit 31 of the reconnection timing determination unit 23 starts measuring time (step S104). The timer unit 31 keeps counting until a predetermined time has elapsed (NO in step S105). And the bearer reconnection instruction | indication part 24 will carry out the reconnection of the bearer shown to step S106 with respect to the communication process control part 21, if the time which the timer part 31 has timed passes predetermined time (YES of step S105). An instruction for executing the process is output.

  As an example of this reconnection process, first, the MME 12 transmits a GTPv2_Delete Bearer Request to the S-GW 103 (step S106-1). Then, Diameter_Gateway Control Session Termination and Diameter_Ack Gateway Control Termination are transmitted / received between S-GW 103 and PCRF 14 (steps S106-2 and S106-3). Thereby, a process for releasing a session is performed between the S-GW 103 and the PCRF 14.

  During this time, the MME 12 transmits an S1-AP_UE Context Release Command to the NB 11 (step S106-4). When the process for the command ends, the NB 11 outputs S1-AP_UE Context Release Complete (step S106-5). Thereby, a release process is performed between MME12 and NB11.

  Finally, the S-GW 103 transmits a GTPv2_Delete Bearer Response for the request in step S104-1 (step S106-6). Then, after each device constituting the network 10 performs a process for disconnecting the bearer, the bearer reconnection process is completed by performing the connection process in the same manner as the transmission process illustrated in step S102. Note that the disconnection processing includes disconnection by initiate detach and disconnection by PDN deactivation.

If the reconnection timing determination unit 23 determines in step S103 that the bearer is not used for a service that needs to be reconnected (NO in step S103), the bearer reconnection instruction unit 24 performs communication processing. An instruction for performing the bearer reconnection process in step S104 is not output to the control unit 21.
In this way, by using the calling process as a trigger for the bearer reconnection process, the MME 12 can perform the reconnection process on the bearer whose communication state has been established.

(Operation of each device constituting network 10 when reconnecting bearer after detecting S-GW change process as trigger of reconnection process in MME 12)
Next, with reference to FIG. 6, an operation of each device configuring the network 10 when the SME GW change process is detected as a trigger of the reconnection process in the MME 12 of the network 10 and then the bearer is reconnected will be described.
As shown in FIG. 6, first, the MME 12 holds an APN of a service that needs to be reconnected (step S201). Thereafter, each device constituting the network 10 performs the calling process shown in step S202. This outgoing call process may be performed in the same procedure as the outgoing call process shown in step S102 described in FIG. 3 and FIG.

  And the trigger detection part 22 detects that the transmission process was performed. Thereafter, when the UE 101 moves to another area, each device configuring the network 10 performs an S-GW change process for changing the connection to another S-GW (step S203). For example, as a process for connecting to another S-GW, there is the following process. Since these processes are known in the same manner as the calling process, only the processes necessary for reconnecting the bearer are extracted from the processes for connecting the S-GW in another area. To do.

  The MME 12 transmits a GTPv2_Create Bearer Request to the S-GW 103 (Step S203-1). Further, the S-GW 103 transmits a GTPv2_Create Bearer Response to the MME 12 as a response to the GTPv2_Create Bearer Request (step S203-2). Thereafter, processing for connecting S-GWs in different areas is performed in each device constituting the network 10.

  Then, the trigger detection part 22 of MME12 detects that the process for connecting with another S-GW demonstrated above was performed. When the reconnection timing determination unit 23 of the MME 12 determines that the service provided using the bearer is a service that needs to be reconnected (YES in step S204), the bearer reconnection instruction unit 24 Outputs an instruction for performing the bearer reconnection process to the communication process control unit 21 (step S205).

Note that the reconnection process in step S205 may be performed in the same manner as the process in step S104 described with reference to FIG. Then, after disconnecting the bearer, the connection process is performed in the same manner as the transmission process shown in step S202, whereby the bearer reconnection process is completed.
In step S204, when the reconnection timing determination unit 23 determines that the bearer is not used for a service that needs to be reconnected (NO in step S204), the bearer reconnection instruction unit 24 performs communication processing. An instruction for performing the reconnection process in step S205 is not output to the control unit 21.
Thus, by using the trigger of the bearer reconnection process that the GW change process has been performed, the MME 12 can perform the bearer reconnection process when another S-GW is actually selected. Can do.

(Second Embodiment)
(Functional configuration of the MME 12 when the bearer is reconnected after detecting the trigger of the reconnection process in the MME 12 and further performing non-communication monitoring)
Next, with reference to FIG. 7, the functional configuration of the MME 12 when the bearer is reconnected after detecting the trigger of the reconnection process in the MME 12 of the network 10 and further performing the non-communication monitoring will be described.
The MME 12 shown in FIG. 7 has substantially the same configuration as the MME 12 shown in FIG. However, the configuration of the MME 12 shown in FIG. 7 is different from the configuration of the MME 12 shown in FIG. 2 in that the reconnection timing determination unit 23 configuring the MME 12 includes a non-communication monitoring unit 41 instead of the timer unit 31. It is a point.
After detecting the reconnection trigger, the non-communication monitoring unit 41 continues to monitor whether the bearer communication state is a non-communication state in which no communication is performed.

(Operation of each device constituting the network 10 when the bearer is reconnected after detecting the outgoing call processing as a trigger of the reconnection processing in the MME 12 and further performing non-communication monitoring)
Subsequently, referring to FIG. 8, after detecting the calling process as a trigger for the reconnection process in the MME 12 of the network 10 and further performing the non-communication monitoring, each apparatus constituting the network 10 in the case of reconnecting the bearer The operation will be described.

As shown in FIG. 8, first, the MME 12 holds an APN of a service that needs to be reconnected (step S301). After that, each device configuring the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S302).
And the trigger detection part 22 detects that the transmission process of step S302 was performed. Thereafter, the no-communication monitoring unit 41 continues to monitor that the bearer communication state is in the no-communication state (NO in step S303). Note that the S-GW 103 and the P-GW 104 monitor the actual no-communication state. Therefore, when UE101 transitions to Pr e servation state based on Pr e servation control procedures, non-communication monitoring unit 41 of MME12 determines as became non-communication state.

The non-communication monitoring unit 41, when the UE101 is judged to have transitioned to Pr e servation state (YES in step S303), the service being provided using the bearers that need to reconnect processing performed services It is determined whether or not.
When the reconnection timing determination unit 23 determines that the service provided using the bearer is a service that needs to be reconnected (YES in step S304), the bearer reconnection instruction unit 24 performs communication processing. An instruction to perform bearer reconnection processing is output to the control unit 21 (step S305).

  In step S304, when the reconnection timing determination unit 23 determines that the service provided by using the bearer is a service that does not need to be reconnected (NO in step S304), the reconnection timing determination unit 23 The unit 24 does not output an instruction for performing the reconnection process in step S305 to the communication processing control unit 21.

As described above, after the trigger of the reconnection process is detected, the bearer reconnection process can be performed after the bearer communication state actually becomes the no communication state by monitoring the no communication state. .
Further, the MME 12 cannot directly monitor whether or not the bearer is in a no-communication state. However, the UE101 transitions to Pr e servation state, non-communication monitoring unit 41 of MME12, it is judged as having become non-communication state, MME12 can perform reconnection process bearer.

(Operations of each device constituting the network 10 when the bearer is reconnected after detecting the S-GW change process as a trigger for the reconnection process in the MME 12 and further performing non-communication monitoring)
Subsequently, referring to FIG. 9, after detecting the S-GW change process as a trigger for the reconnection process in the MME 12 of the network 10 and further performing the non-communication monitoring, the network 10 in the case of reconnecting the bearer is configured. The operation of each device will be described.

As shown in FIG. 9, first, the MME 12 holds an APN of a service that needs to be reconnected (step S401). After that, each device constituting the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S402).
Thereafter, when the UE 101 moves to another area, the devices configuring the network 10 perform S-GW change processing for changing from the currently selected S-GW to another S-GW (step S403). The trigger detection unit 22 detects that processing for changing from the currently selected S-GW to another S-GW has been performed.

  When the reconnection timing determination unit 23 determines that the service provided using the bearer is a service that needs to be reconnected (YES in step S404), the reconnection timing determination unit 23 The flag for controlling whether or not to execute the reconnection process is changed from the off state to the on state (step S405).

Subsequently to the originating process at step S402, no communication monitoring unit 41, UE 101 continues to monitor the communication state to transition to Pr e servation state (NO in step S406). Thereafter, non-communication monitoring unit 41, when the UE101 transitions to Pr e servation state (YES in step S406), the flag for controlling whether to execute the reconnection process bearer is determined to be ON state (step The bearer reconnection instructing unit 24 outputs an instruction to perform the bearer reconnection process to the communication processing control unit 21 (step S408).

  In step S404, when the reconnection timing determination unit 23 determines that the service provided using the bearer is a service that does not need to be reconnected (NO in step S404), the bearer reconnection is performed. The instruction unit 24 does not output an instruction for performing the reconnection process in step S408 to the communication processing control unit 21.

Similarly, if it is determined in step S407 that the flag for controlling whether or not the bearer reconnection process can be executed is in an off state (NO in step S407), the bearer reconnection instructing unit 24 notifies the communication processing control unit 21. On the other hand, an instruction for performing the reconnection process in step S407 is not output.
So far, in MME12, the flow in the case of reconnecting a bearer was demonstrated. Next, the flow in the case of reconnecting a bearer in the P-GW 104 will be described.

(Third embodiment)
(Functional configuration of the P-GW 104 when the bearer is reconnected after detecting the trigger of the reconnection process in the P-GW 104)
First, with reference to FIG. 10, a functional configuration of the P-GW 104 when the P-GW 104 of the network 10 detects the reconnection process trigger and then reconnects the bearer will be described.
A P-GW 104 illustrated in FIG. 10 includes the same processing unit as the MME 12 illustrated in FIG. The apparatus for performing the reconnection process has changed from the MME 12 to the P-GW 104, but the configuration necessary for performing the reconnection process is not substantially changed.

(Operation of each device constituting network 10 when bearer is reconnected after detecting transmission process as trigger of reconnection process in P-GW 104)
Next, with reference to FIG. 11, the operation of each device constituting the network 10 when the bearer is reconnected after detecting the transmission process as a trigger for the reconnection process in the P-GW 104 of the network 10 will be described.
As shown in FIG. 11, first, the P-GW 104 holds an APN of a service that needs to be reconnected (step S501). After that, each device configuring the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S502).

The trigger detection unit 22 detects that the transmission process described above has been performed, and the reconnection timing determination unit 23 of the P-GW 104 performs the reconnection process for the service provided using the bearer. If it is determined that the service is necessary (YES in step S503), the timer unit 31 of the reconnection timing determination unit 23 starts measuring time (step S504).
The timer unit 31 keeps counting until a predetermined time elapses (NO in step S505). When the time counted by the timer unit 31 has passed a predetermined time (YES in step S505), the bearer reconnection instruction unit 24 performs bearer reconnection processing on the communication processing control unit 21. Is output (step S506).

  In step S503, the reconnection timing determination unit 23 of the P-GW 104 determines that the bearer is not used for a service that needs to be reconnected (NO in step S503). Then, the bearer reconnection instruction unit 24 does not output an instruction for performing the reconnection process in step S506 to the communication processing control unit 21.

(Operations of devices configuring the network 10 when the bearer is reconnected after detecting the S-GW change process as a trigger for the reconnection process in the P-GW 104)
Subsequently, referring to FIG. 12 and FIG. 13, after detecting the S-GW change process as a trigger for the reconnection process in the P-GW 104 of the network 10, each apparatus configuring the network 10 when the bearer is reconnected is detected. The operation will be described.

As shown in FIG. 12, first, the P-GW 104 holds an APN of a service that needs to be reconnected (step S601). After that, each device configuring the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S602).
Thereafter, when the reconnection timing determination unit 23 of the P-GW 104 determines that the service provided using the bearer is a service that needs to be reconnected (YES in step S603), the reconnection of the bearer A flag for controlling whether to execute the process is turned on (step S604).

  And if UE101 moves to another area, each apparatus which comprises the network 10 will perform S-GW change process for changing from S-GW currently selected to another S-GW (step S605). . As an example of the process of changing the connection destination of this S-GW, the S-GW 106 in the moved area transmits a Diameter_Gateway Control Establishment Establishment to the PCRF 14 (step S605-1). In response to this, the PCRF 14 transmits a Diameter_Acknowledge Gateway Control Session Establishment to the S-GW 106 (step S605-2).

Furthermore, the S-GW 106 transmits PMIPv6_Proxy Binding Update to the P-GW 14 (step S605-3). In response to this, the P-GW 14 transmits PMIPv6_Proxy Binding Ack to the S-GW 106 (step S605-4).
As described above, the trigger detection unit 22 performs the process of changing the S-GW based on the PMIPv6_Proxy Binding Update in step S605-3 transmitted from the S-GW 106 in the moved area when changing the S-GW. It is possible to detect what has been done.

If the flag for controlling whether or not the bearer reconnection process is executable is ON (YES in step S606), the bearer reconnection instruction unit 24 performs the reconnection process in step S607 (step S607). S607).
In step S603, when the reconnection timing determination unit 23 of the P-GW 104 determines that the bearer is not used for a service that needs to be reconnected (NO in step S603), the bearer reconnection instruction unit 24 Does not output an instruction for performing the reconnection process in step S607 shown in FIG. 13 to the communication process control unit 21.
Similarly, in step S606, if the flag for controlling execution / non-executability of bearer reconnection processing is off (NO in step S606), the P-GW 104 performs communication processing control. An instruction for performing the reconnection process in step S607 shown in FIG. 13 is not output to the unit 21.

(Fourth embodiment)
(Functional configuration of the P-GW 104 when the bearer is reconnected after detecting the trigger of the reconnection process in the P-GW 104 and further performing no communication monitoring)
Next, the functional configuration of the P-GW 104 when the bearer is reconnected after detecting the trigger of the reconnection process in the P-GW 104 of the network 10 and further performing non-communication monitoring will be described with reference to FIG. .

  The P-GW 104 shown in FIG. 14 has substantially the same configuration as the MME 12 shown in FIG. However, the configuration of the P-GW 104 illustrated in FIG. 14 is different from that of the MME 12 illustrated in FIG. 7 in that the reconnection timing determination unit 23 includes a timer unit 31. The timer unit 31 has the same function as the timer unit 31 provided in the MME 12 described above.

(Operations of each device constituting the network 10 when the bearer is reconnected after the call processing is detected as a trigger for the reconnection process in the P-GW 104 and further after monitoring for no communication)
Subsequently, referring to FIG. 15, each of the components constituting the network 10 in the case where the bearer is reconnected after detecting the transmission process as a trigger of the reconnection process in the P-GW 104 of the network 10 and further performing the non-communication monitoring. The operation of the apparatus will be described.

As shown in FIG. 15, first, the P-GW 104 holds the APN of the service that needs to be reconnected, the time for determining that the no-communication monitoring unit 41 is in the no-communication state, etc. S701). After that, each device configuring the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S702).
The trigger detection unit 22 detects that the transmission process described above has been performed, and the reconnection timing determination unit 23 of the P-GW 104 needs to perform the reconnection process for the service provided using the bearer. If it is determined that the service is a certain service (YES in step S703), the non-communication monitoring unit 41 starts monitoring whether or not the communication is in a non-communication state (step S704). Further, the timer unit 31 of the reconnection timing determination unit 23 starts measuring time (step S705).

The reconnection timing determination unit 23 determines that the bearer reconnection instruction unit 24 instructs the communication processing control unit 21 to perform step S706 until a predetermined time elapses when the bearer is in a no-communication state (NO in step S706). Does not output instructions for performing reconnection processing. The reconnection timing determination unit 23 continues to monitor whether or not it is in a no-communication state after resetting the time being measured.
Further, when the reconnection timing determination unit 23 determines that the predetermined time has elapsed after the bearer is in a no-communication state (YES in step S706), the bearer reconnection instruction unit 24 instructs the communication processing control unit 21 to Then, an instruction for performing the reconnection process is output (step S707).

In step S703, when the reconnection timing determination unit 23 of the P-GW 104 determines that the bearer is not used for a service that needs to be reconnected (NO in step S703), the bearer reconnection instruction unit 24 Does not output an instruction for performing the reconnection processing in step S706 to the communication processing control unit 21.
In this way, the P-GW 104 can directly monitor whether or not the bearer is in a no-communication state by the own device, and perform bearer reconnection processing.

(Operations of each device constituting the network 10 when the bearer is reconnected after the S-GW change process is detected as a trigger of the reconnection process in the P-GW 104, and further after performing non-communication monitoring)
Next, referring to FIG. 16 and FIG. 17, in the case where the P-GW 104 of the network 10 detects the S-GW change process as a trigger for the reconnection process, and further performs no communication monitoring, and then reconnects the bearer. The operation of each device constituting the network 10 will be described.

As shown in FIG. 16, first, the P-GW 104 holds the APN of the service that needs to be reconnected, the time for determining that there is no communication state by the no communication monitoring unit 41, and the like (steps). S801). After that, each device configuring the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S802).
Thereafter, when the reconnection timing determination unit 23 of the P-GW 104 determines that the bearer is used for a service that needs to be reconnected (YES in step S803), it controls whether or not the bearer reconnection process can be performed. The flag for turning on is turned on (step S804).

  And if UE101 moves to another area, each apparatus which comprises the network 10 will perform S-GW change process for changing from S-GW currently selected to another S-GW (step S805). . If the flag for controlling whether or not the bearer reconnection process can be executed is on (YES in step S806), the non-communication monitoring unit 41 monitors whether or not the non-communication state is present. Start (step S807). Further, the timer unit 31 of the reconnection timing determination unit 23 starts measuring time (step S808).

  The reconnection timing determination unit 23 determines that the bearer reconnection instruction unit 24 instructs the communication processing control unit 21 to perform step S810 until a predetermined time elapses when the bearer is in a no-communication state (NO in step S809). Does not output instructions for performing reconnection processing. At this time, the reconnection timing determination unit 23 resets the time being measured and continues to monitor whether or not there is a no-communication state.

Further, when the reconnection timing determination unit 23 determines that the predetermined time has elapsed after the bearer is in a no-communication state (YES in step S809), the bearer reconnection instruction unit 24 instructs the communication processing control unit 21 to Then, an instruction to perform bearer reconnection processing is output (step S810).
In step S803, when the reconnection timing determination unit 23 of the P-GW 104 determines that the service provided using the bearer is a service that does not need to be reconnected (NO in step S803), The bearer reconnection instruction unit 24 does not output an instruction for performing the reconnection process in step S810 illustrated in FIG. 17 to the communication processing control unit 21.

Similarly, in step S806, if the flag for controlling whether or not the bearer reconnection process is executable is off (NO in step S806), the P-GW 104 causes the communication process control to be performed. The instruction for performing the reconnection process in step S810 is not output to the unit 21.
So far, the flow in the case of reconnecting bearers in the P-GW 104 has been described. Next, a flow when reconnecting a bearer in the PCRF 14 will be described.

(Fifth embodiment)
(Functional configuration of the PCRF 14 when the bearer is reconnected after detecting the trigger of the reconnection process in the PCRF 14)
First, the functional configuration of the PCRF 14 when the bearer is reconnected after detecting the trigger of the reconnection process in the PCRF 14 of the network 10 will be described with reference to FIG.
The PCRF 14 shown in FIG. 18 includes the same processing unit as the P-GW 104 shown in FIG. Although the apparatus for performing the bearer reconnection process has been changed from the MME 12 or the P-GW 104 to the PCRF 14, the configuration necessary for performing the bearer reconnection process is not substantially changed.

(Operation of each device constituting the network 10 when the bearer is reconnected after detecting the originating process as a trigger of the reconnection process in the PCRF 14)
Next, with reference to FIG. 19, the operation of each device constituting the network 10 when the bearer is reconnected after detecting the calling process as a trigger for the reconnection process in the PCRF 14 of the network 10 will be described.
As shown in FIG. 19, first, the PCRF 14 holds an APN of a service that needs to be reconnected (step S901). After that, each device configuring the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S902).

  The trigger detection unit 22 detects that the transmission process described above has been performed, and the reconnection timing determination unit 23 of the PCRF 14 requires that the service provided using the bearer perform the reconnection process. If it is determined that the service is a certain service (YES in step S903), the timer unit 31 of the reconnection timing determination unit 23 starts measuring time (step S904).

The timer unit 31 keeps counting until a predetermined time elapses (NO in step S905). When the time counted by the timer unit 31 has passed a predetermined time (YES in step S905), the bearer reconnection instruction unit 24 performs bearer reconnection processing on the communication processing control unit 21. Is output (step S906).
In step S903, the reconnection timing determination unit 23 of the PCRF 14 determines that the bearer is not used for a service that needs to be reconnected (NO in step S903). Then, the bearer reconnection instructing unit 24 does not output an instruction for performing the reconnection processing in step S906 to the communication processing control unit 21.

(Operation of each device constituting the network 10 when the bearer is reconnected after detecting the S-GW change process as a trigger of the reconnection process in the PCRF 14)
Next, with reference to FIG. 20, the operation of each device configuring the network 10 when the PCRF 14 detects the S-GW change process as a trigger for the reconnection process and then reconnects the bearer will be described.
As shown in FIG. 20, first, the PCRF 14 holds an APN of a service that needs to be reconnected (step S1001). After that, each device constituting the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S1002).

  The trigger detection unit 22 detects that the transmission process described above has been performed, and the reconnection timing determination unit 23 of the PCRF 14 requires that the service provided using the bearer perform the reconnection process. If it is determined that the service is a certain service (YES in step S1003), a flag for controlling execution of bearer reconnection processing is turned on (step S1004).

  And if UE101 moves to another area, each apparatus which comprises a network will perform the S-GW change process for changing from S-GW currently selected to another S-GW (step S1005). The S-GW change process shown in step S1005 is the same procedure as the S-GW change process shown in step S605. The trigger detection unit 22 performs processing for changing the S-GW based on the Diameter_Gateway Control Establishment of Step S605-1 transmitted from the S-GW 106 of the moved area when changing the S-GW. Can be detected.

If the flag for controlling whether or not the bearer reconnection process can be executed is ON (YES in step S1006), the PCRF 14 instructs the communication process control unit 21 in step S1007. An instruction for performing reconnection processing is output.
In step S1003, the reconnection timing determination unit 23 of the PCRF 14 determines that the bearer is not used for a service that needs to be reconnected (NO in step S1003). Then, the bearer reconnection instructing unit 24 does not output an instruction to the communication processing control unit 21 to perform the reconnection process in step S1007.
Similarly, in step S1006, if the flag for controlling whether or not to execute the bearer reconnection process is off (NO in step S1006), the PCRF 14 determines that the bearer reconnection instruction unit 24 is the communication process control unit 21. On the other hand, an instruction for performing the reconnection process in step S1007 is not output.

(Sixth embodiment)
(Functional configuration of the P-GW 104 when the bearer is reconnected after detecting the trigger of the reconnection process in the PCRF 14 and further performing non-communication monitoring)
Next, a functional configuration of the P-GW 104 when the bearer is reconnected after detecting the trigger of the reconnection process in the PCRF 14 of the network 10 and further performing the non-communication monitoring will be described with reference to FIG.
The PCRF 14 illustrated in FIG. 21 includes a communication processing control unit 21, a trigger detection unit 22, and a reconnection instruction unit 24 among the processing units included in the P-GW 104 illustrated in FIG. That is, the PCRF 14 does not include the reconnection timing determination unit 23. Instead, the P-GW 104 includes a reconnection timing determination unit 23.

  This is because the PCRF 14 cannot directly monitor whether the bearer is in a no-communication state. However, the configuration for reconnecting the bearer is not substantially different from the configuration of the P-GW 104 shown in FIG. Note that the S-GW 103 may include the reconnection timing determination unit 23 instead of the P-GW 104, and the S-GW 103 may monitor the bearer non-communication state.

(Operations of each device constituting the network 10 when the bearer is reconnected after the call processing is detected as a trigger of the reconnection process in the PCRF 14 and the non-communication monitoring is further performed)
First, referring to FIG. 22 and FIG. 23, after detecting the call process as a trigger for the reconnection process in the PCRF 14 of the network 10, and further performing the no-communication monitoring, The operation of the apparatus will be described.

  As shown in FIG. 22, first, the P-GW 104 holds the APN of a service that needs to be reconnected, the time for determining that there is no communication by the no communication monitoring unit 41, and the like (step S1101). After that, each device configuring the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S1102). Note that the transmission processing shown in steps S1102 and S1108 is substantially the same as the transmission processing shown in step S102.

  Then, in the calling process, the PCRF 14 receives Diameter_CC-Request from the P-GW 104 (step S1103). When the reconnection timing determination unit 23 of the PCRF 14 determines that the service provided using the bearer is a service that needs to be reconnected (YES in step S1104), the P-GW 104 does not communicate. Diameter_CC-Answer for requesting monitoring of whether or not there is a no-communication state is transmitted to the monitoring unit 41 (step S1105). Specifically, Diameter_CC-Answer causes the no-communication monitoring unit 41 to monitor whether or not the bearer is in a no-communication state, and then outputs an instruction to perform bearer reconnection processing to the bearer reconnection instruction unit 24 It is for making it happen.

  The no-communication monitoring unit 41 of the P-GW 104 starts monitoring whether the bearer is in the no-communication state (step S1106). Further, the timer unit 31 of the reconnection timing determination unit 23 starts measuring time (step S1107). Thereafter, each device constituting the network 10 continues the call processing shown in Step 1102 (Step S1108).

Then, the reconnection timing determination unit 23 determines that the bearer reconnection instruction unit 24 performs communication processing of the P-GW 104 (not illustrated) until the time during which the bearer is in the no-communication state has passed a predetermined time (YES in step S1109). An instruction to perform bearer reconnection processing is output to the control unit or the like (step S1110).
When the reconnection timing determination unit 23 determines that the predetermined time has elapsed after the bearer is in a no-communication state (NO in step S1109), the bearer reconnection instruction unit 24 instructs the communication processing control unit 21 to An instruction for performing the reconnection process in step S1110 is not output.

In step S1104, when the reconnection timing determination unit 23 of the P-GW 104 determines that the service provided using the bearer is a service that does not need to be reconnected (NO in step S1104). As shown in FIG. 23, the PCRF 14 transmits Diameter_CC-Answer to instruct the non-communication monitoring unit 41 of the P-GW 104 not to monitor whether or not it is in the no-communication state (step S1151). Thereafter, each device constituting the network 10 continuously performs the same call process as the call process shown in S1108 (step S1152). And the bearer reconnection instruction | indication part 24 does not output the instruction | indication for performing the reconnection process of step S1110 with respect to the communication process control part 21. FIG.
Thus, the PCRF 14 cannot directly monitor whether the bearer is in a no-communication state. However, since the S-GW 103 includes the reconnection timing determination unit 23, the PCRF 14 can perform the bearer reconnection process after the S-GW 103 monitors the non-communication state of the bearer.

(Operation of each device constituting the network 10 when the bearer is reconnected after the S-GW change process is detected as a trigger of the reconnection process in the PCRF 14 and after further monitoring of no communication)
Next, referring to FIG. 24 and FIG. 25, after detecting the S-GW change process as a trigger for the reconnection process in the PCRF 14 of the network 10 and further performing no communication monitoring, the network 10 in the case of reconnecting the bearer The operation of each device constituting the system will be described.

As shown in FIG. 24, first, the PCRF 14 holds the APN of the service that needs to be reconnected, the time for determining that the communication is not performed by the communicationless monitoring unit 41, and the like (step S1201). . After that, each device configuring the network 10 performs a transmission process similar to step S102 described in FIG. 4 (step S1202).
Thereafter, when the PCRF 14 determines that the service provided using the bearer is a service that needs to be reconnected (YES in step S1203), the PCRF 14 controls whether or not the bearer reconnection process can be executed. The flag is turned on (step S1204).

  And if UE101 moves to another area, each apparatus which comprises the network 10 will perform S-GW change process for changing from S-GW currently selected to another S-GW (step S1205). . If the flag for controlling whether or not the bearer reconnection process can be performed is on (YES in step S1206), the PCRF 14 determines whether the bearer is in a non-communication state with respect to the reconnection timing determination unit 23. Transmits Diameter_Re-Auth-Request for monitoring (step S1207). Then, the no-communication monitoring unit 41 starts monitoring whether the bearer is in a no-communication state (step S1208). Further, the timer unit 31 of the reconnection timing determination unit 23 starts measuring time (step S1209). The P-GW 104 transmits Diameter_Re-Auth-Answer to the PCRF 14 (step S1210).

  As illustrated in FIG. 25, the reconnection timing determination unit 23 is configured to use the communication processing control unit until the time during which the bearer is in a no-communication state passes a predetermined time (NO in step S <b> 1211). 21 does not output an instruction for performing the reconnection process in step S1212. When the reconnection timing determination unit 23 determines that the predetermined time has elapsed for the bearer in the no-communication state (YES in step S1211), the bearer reconnection instruction unit 24 performs bearer reconnection processing. (Step S1212).

In step S1203, when the PCRF 14 determines that the service provided using the bearer is a service that does not need to be reconnected (NO in step S1203), the communication process control is performed as illustrated in FIG. The bearer reconnection instruction unit 24 does not output an instruction for performing the reconnection process in step S1212 to the unit 21.
Similarly, in step S1206, if the flag for controlling whether or not the bearer reconnection process is executable is off (NO in step S1206), the PCRF 14 determines that the bearer reconnection instruction unit 24 is the communication process control unit 21. In response to this, the instruction for performing the reconnection process in step S1212 is not output.

(Summary of network 10 configured using network reconnection system)
In the always-connected network 10 described above, any one of the MME 12, the P-GW 104, and the PCRF 14 is used as a point for performing bearer reconnection processing by the network reconnection system. The reconnection process may be performed by any of the above devices. And in the network 10, a bearer can be reconnected according to the trigger of each reconnection, the time of a no-communication state, etc.

  Even if the UE 101 moves to a different area and the P-GW and the S-GW are selected across the two areas, by reconnecting the bearer, The P-GW and S-GW corresponding to the area can always be selected. Since P-GW and S-GW are not selected across the two areas, interface processing S5 between P-GW and S-GW becomes unnecessary.

  In the network 10 as described above, an increase in traffic volume can be suppressed by performing the interface process S5, so that resources of the network 10 can be effectively used. In particular, each P-GW and S-GW of the network, network devices such as a network switching device, a router for relaying, and traffic such as a transmission path between stations in which each device is accommodated. The amount can be reduced. Moreover, when the license cost of the hardware and software constituting the network is a pay-as-you-go system, these costs can be suppressed.

  Note that the network reconnection system described above is realized by providing each part of the system in a single device such as the MME 12 or the P-GW 104, or provided in a plurality of devices. It is realized by being connected via the network 10. In either case, it corresponds to the network reconnection system of this specification. That is, the network reconnection system of the present specification is such that each part constituting the system operates in a coordinated manner, and any part of the network 10 is provided with a single unit regardless of which part constituting the system is provided. The effect obtained is the same as that realized when each part is provided in the apparatus. Moreover, as an apparatus for providing each unit, an apparatus such as the MME 12 or the P-GW 104 has been described as an example. However, if the series of processes for reconnection described above can be performed, an apparatus for providing each unit is The present invention is not limited to these apparatuses.

  In addition, the scope of the present invention is not limited to the illustrated and described exemplary embodiments, and includes all embodiments that provide the same effects as those intended by the present invention. Furthermore, the scope of the invention is not limited to the combinations of features of the invention defined by the claims, but can be defined by any desired combination of particular features among all the disclosed features.

  The network reconnection system of the present invention can be used for each device constituting a network as a network reconnection system for reconnecting bearers, particularly in a network premised on constant connection.

10 …… Network 101 …… UE
102 …… Service providing device 103 …… S-GW
104 …… P-GW
11 …… eNB
12 …… MME
13 …… HSS
14 …… PCRF
22 …… Trigger detection unit 23 …… Reconnection timing determination unit 24 …… Reconnection instruction unit 31 …… Timer unit 32 …… Service determination unit 41 …… Non-communication monitoring unit

Claims (9)

A trigger detection unit that detects a reconnection trigger for reconnecting a bearer in an always-connected network;
A reconnection timing determination unit for determining a reconnection timing for performing reconnection processing of a bearer in which the reconnection trigger is detected by the trigger detection unit;
Based on the reconnection timing determined by the reconnection timing determination unit, a reconnection instruction unit that outputs a reconnection instruction so as to perform reconnection processing of a bearer in which the reconnection trigger is detected;
A communication processing control unit that performs reconnection processing of the bearer in which the reconnection trigger is detected based on the reconnection instruction output from the reconnection instruction unit , and
The reconnection timing determination unit
A service determination unit that determines whether the bearer in which the reconnection trigger is detected is used for a service that needs to perform reconnection processing;
The reconnection timing determination unit determines a reconnection timing of a bearer that is determined to be used for a service that needs to be reconnected by the service determination unit among bearers in which the reconnection trigger is detected. the network re-connection system, wherein to Rukoto. The trigger detection unit
2. The network reconnection system according to claim 1, wherein a transmission process is performed in the bearer is detected as the reconnection trigger. The trigger detection unit
2. The network reconnection system according to claim 1, wherein the reconnection trigger detects that a gateway device in an area different from the gateway device in the area of the current mobile station is selected in the bearer. . The reconnection timing determination unit
The network reconnection system according to claim 2 or 3 , wherein the reconnection timing is set immediately after the trigger is detected by the trigger detection unit. The reconnection timing determination unit
It has a timer part to keep time,
4. The reconnection timing according to claim 2 , wherein, after the trigger is detected by the trigger detection unit, the reconnection timing is set immediately after the time counted by the timer unit passes a predetermined time. 5. Network reconnection system. The reconnection timing determination unit
A no-communication monitoring unit for monitoring whether the communication state of the bearer in which the reconnection trigger is detected is a no-communication state;
A timer section for timing,
With
The timer unit is
After determining that the communication state of the bearer for which the reconnection trigger is detected by the no communication monitoring unit is a no communication state, the communication state of the bearer for which the reconnection trigger is detected is a no communication state. Time the communication status,
The reconnection timing determination unit
4. The network reconnection system according to claim 2, wherein the reconnection timing is set immediately after the non-communication state time measured by the timer unit passes a predetermined time. 5. A trigger detection unit that detects a reconnection trigger for reconnecting a bearer in an always-connected network;
A reconnection timing determination unit for determining a reconnection timing for performing reconnection processing of a bearer in which the reconnection trigger is detected by the trigger detection unit;
Based on the reconnection timing determined by the reconnection timing determination unit, a reconnection instruction unit that outputs a reconnection instruction so as to perform reconnection processing of a bearer in which the reconnection trigger is detected;
A communication processing control unit that performs reconnection processing of a bearer in which the reconnection trigger is detected based on the reconnection instruction output from the reconnection instruction unit;
With
The trigger detection unit
Detecting that the call processing has been performed in the bearer as the reconnection trigger,
The reconnection timing determination unit
A no-communication monitoring unit that monitors whether the communication state of the bearer in which the reconnection trigger is detected is a no-communication state;
The no-communication monitoring unit is
When the mobile station based on Pr e servation control procedure transitions to Pr e servation state, the network reconnection system, wherein a communication state of the bearers reconnection trigger is detected is judged to be no communication . A trigger detection unit that detects a reconnection trigger for reconnecting a bearer in an always-connected network;
A reconnection timing determination unit for determining a reconnection timing for performing reconnection processing of a bearer in which the reconnection trigger is detected by the trigger detection unit;
Based on the reconnection timing determined by the reconnection timing determination unit, a reconnection instruction unit that outputs a reconnection instruction so as to perform reconnection processing of a bearer in which the reconnection trigger is detected;
A communication processing control unit that performs reconnection processing of a bearer in which the reconnection trigger is detected based on the reconnection instruction output from the reconnection instruction unit;
With
The trigger detection unit
It is detected as the reconnection trigger that a gateway device in an area different from the gateway device in the area of the current mobile device is selected in the bearer,
The reconnection timing determination unit
A no-communication monitoring unit that monitors whether the communication state of the bearer in which the reconnection trigger is detected is a no-communication state;
The no-communication monitoring unit is
When the mobile station based on Pr e servation control procedure transitions to Pr e servation state, the network reconnection system, wherein a communication state of the bearers reconnection trigger is detected is judged to be no communication . The reconnection timing determination unit
The bearers reconnection trigger is detected, the reconnection process includes determining the service determination unit whether used in service that needs to perform,
The reconnection timing determination unit, wherein among the bearers reconnection trigger is detected, reconnection timing of the service determination unit and I Ri is used to require a service re-connection process performed on the determined bearer The network reconnection system according to claim 7 or 8 , wherein the network reconnection system is determined.

Images