JP6767012B2 - Gateway device, communication method, and program - Google Patents

Description

The present invention relates to gateway devices, communication methods, and programs, and more particularly to gateway devices, communication methods, and programs that transmit messages.

In recent years, along with the spread of smartphones and the like, IoT (Internet Of Things) services have also become widespread. The IoT service is implemented, for example, by using a terminal or the like that autonomously communicates without any user operation. In general, it is known that terminals such as smartphones and terminals used for IoT services have different traffic characteristics. For example, in IoT services, a small amount of data is often transmitted as compared with smartphones and the like. Further, the IoT service may have a traffic characteristic that data is transmitted at a predetermined timing in a day.

In this way, since general services using terminals such as smartphones and IoT services have different traffic characteristics, the core network that provides general services and the core network that provides IoT services are separated and independent of each other. It is being considered for operation. By separating the core network, it becomes possible to design equipment according to the traffic characteristics of each service.

Patent Document 1 discloses a configuration of a gateway device having traffic characteristics suitable for distinguishing user terminals having different traffic characteristics and connecting the user terminals. Specifically, the packet distribution control unit of the gateway device determines the transfer destination of the packet based on the MAC address or domain information of the user terminal included in the packet. Further, the packet distribution control unit changes the IP address of the packet transmission destination to the IP address of the transfer destination gateway device.

JP-A-2015-43522

However, in a network constructed based on a standard such as 3GPP (3rd Generation Partnership Project), various protocols are defined between node devices. Therefore, when forwarding a packet, there is a problem that the information does not match the protocol specified between the node devices and the packet cannot be forwarded appropriately only by changing the IP address of the destination. ..

An object of the present invention is to provide a gateway device, a communication method, and a program capable of appropriately distributing packets in a network constructed based on the 3GPP standard.

The gateway device according to the first aspect of the present invention is between a node device that executes communication according to GTP (GPRS (General Packet Radio Service) Tunneling Protocol) and S-GW (Serving-Gateway), or according to GTP. A gateway device arranged between a node device that executes communication and a P-GW (PDN (Packet Data Network) -Gateway), and a communication unit that terminates a GTP message transmitted from the node device, and the above. The determination unit that determines the terminal type of the mobile station associated with the GTP message and the source address set in the GTP message transmitted from the node device are determined from the identifier of the node device and the first of the gateway device. The communication unit includes a conversion unit that changes to the identifier of the above, and the communication unit transmits the GTP message whose source address has been converted to the S-GW or P-GW determined according to the terminal type. is there.

The communication method according to the second aspect of the present invention is between a node device that executes communication according to GTP (GPRS (General Packet Radio Service) Tunneling Protocol) and S-GW (Serving-Gateway), or according to GTP. It is a communication method in a gateway device arranged between a node device that executes communication and a P-GW (PDN (Packet Data Network) -Gateway), and terminates a GTP message transmitted from the node device. The terminal type of the mobile station associated with the GTP message is determined, and the source address set in the GTP message transmitted from the node device is changed from the identifier of the node device to the first identifier of the gateway device. The GTP message that has been changed and the source address has been converted is transmitted to the S-GW or P-GW that is determined according to the terminal type.

The program according to the third aspect of the present invention communicates between a node device that executes communication according to GTP (GPRS (General Packet Radio Service) Tunneling Protocol) and S-GW (Serving-Gateway), or according to GTP. It is a program to be executed by a computer which is a gateway device arranged between a node device and a P-GW (PDN (Packet Data Network) -Gateway) that executes the above, and terminates a GTP message transmitted from the node device. Then, the terminal type of the mobile station associated with the GTP message is determined, and the source address set in the GTP message transmitted from the node device is determined from the identifier of the node device to be the first of the gateway device. The computer is made to execute the GTP message in which the source address is converted by changing to the identifier of the above to the S-GW or P-GW determined according to the terminal type.

According to the present invention, it is possible to provide a gateway device, a communication method, and a program capable of appropriately distributing packets in a network constructed based on the 3GPP standard.

It is a block diagram of the communication system which concerns on Embodiment 1. FIG. It is a block diagram of the communication system which concerns on Embodiment 2. FIG. It is a figure which shows the flow of the Attach process which concerns on Embodiment 2. It is a figure which shows the flow of the Detach process which concerns on Embodiment 2. It is a block diagram of the communication system which concerns on Embodiment 2. FIG. It is a block diagram of the communication system which concerns on Embodiment 3. FIG. It is a figure which shows the flow of the Attach process which concerns on Embodiment 3. It is a figure which shows the flow of the Detach process which concerns on Embodiment 3. It is a block diagram of the communication system which concerns on Embodiment 4. FIG. It is a figure which shows the flow of the Attach process which concerns on Embodiment 4. It is a figure which shows the flow of the Detach process which concerns on Embodiment 4. It is a block diagram of the communication system which concerns on Embodiment 5. It is a figure which shows the information managed by the DB which concerns on Embodiment 5. It is a figure which shows the flow of the packet distribution processing which concerns on Embodiment 5. It is a block diagram of the communication system which concerns on Embodiment 5. It is a block diagram of the communication system which concerns on Embodiment 6. It is a figure which shows the flow of the packet distribution processing which concerns on Embodiment 6. It is a block diagram of the communication system which concerns on Embodiment 7. It is a figure which shows the flow of the packet distribution processing which concerns on Embodiment 7. It is a block diagram of the gateway device which concerns on each embodiment.

(Embodiment 1)
Hereinafter, embodiments of the present invention will be described with reference to the drawings. A configuration example of the communication system according to the first embodiment of the present invention will be described with reference to FIG. The communication system of FIG. 1 includes a RAN (Radio Area Network) device 10, a node device 20, a gateway device 30, S (Serving) / P ((PDN) Packet Data Network) -GW (Gateway) 40, and S / P-GW 50. , And has a UE 60. S / P-GW indicates that it is S-GW or P-GW. Alternatively, S / P-GW may indicate that it is S-GW and P-GW. The RAN device 10, the node device 20, the gateway device 30, the S / P-GW 40, the S / P-GW 50, and the UE 60 may be computer devices operated by the processor executing a program stored in the memory. ..

The RAN device 10 may be a base station or a base station control device that controls a base station. Alternatively, the RAN device 10 may include a base station and a base station control device. The base station may be, for example, an eNB which is a base station that supports LTE (Long Term Evolution) in 3GPP, or may be a NodeB that supports a so-called 2G or 3G wireless communication system. The base station control device may be, for example, an RNC (Radio Network Controller) specified in 3GPP. The RAN device 10 wirelessly communicates with the UE 60. UE60 is a general term for mobile stations used in 3GPP.

The node device 20 is a device that manages the position information of the UE 60 in 3GPP and further executes call processing control regarding the UE 60. The node device 20 may be, for example, an MME (Mobility Management Entity) or an SGSN (Serving GPRS (General Packet Radio Service) Support Node) defined in 3GPP. Alternatively, the node device 20 may be an S-GW that transmits user data related to the UE 60.

The S / P-GW 40 and S / P-GW 50 transmit user data regarding the UE 60.

The gateway device 30 is arranged between the node device 20 and the S / P-GW 40, and further between the node device 20 and the S / P-GW 50. The gateway device 30 relays control data transmitted between the node device 20 and the S / P-GW 40 or S / P-GW 50. The control data may be data for executing call processing control of the S / P-GW 40. Alternatively, the control data may be data used for setting a transmission path of user data relating to the UE 60. The control data may be referred to as a control signal, control information, C-Plane data, or the like. Further, text data, image data, moving image data, etc. transmitted and received by the UE 60 are referred to as user data. The user data may be referred to as user information, U-Plane data, or the like.

The node device 20 executes communication with the S / P-GW 40 and S / P-GW 50 in accordance with GTP (GPRS (General Packet Radio Service) Tunneling Protocol). That is, the node device 20 sets various information in the GTP message, which is the control message defined in the GTP, and transmits the GTP message between the S / P-GW 40 and the S / P-GW 50. The GTP message used as the control message may be referred to as, for example, a GTP-C message.

Subsequently, a configuration example of the gateway device 30 will be described. The gateway device 30 has a communication unit 31, a determination unit 32, and a conversion unit 33. The communication unit 31, the determination unit 32, and the conversion unit 33 may be software or modules whose processing is executed by the processor executing a program stored in the memory. Alternatively, the communication unit 31, the determination unit 32, and the conversion unit 33 may be hardware such as a circuit or a chip.

The communication unit 31 terminates the GTP message transmitted from the node device 20, the S / P-GW 40, or the S / P-GW 50. When the communication unit 31 terminates the GTP message, the communication unit 31 may analyze the information set in the GTP message, change the information set in the GTP message, or the like. The communication unit 31 outputs the received GTP message to the determination unit 32 and the conversion unit 33.

The determination unit 32 determines the terminal type of the UE 60 associated with the GTP message. The GTP message is a message used to control call processing of the UE 60. That is, the GTP message is transmitted for each UE.

The terminal type may be, for example, identification information of a service executed by the UE 60, information defining the traffic characteristics of the UE 60, or other identification information for identifying the UE 60. For example, the terminal type may be information that identifies a terminal that executes the IoT service and a terminal other than the terminal.

The conversion unit 33 changes the source address set in the GTP message transmitted from the node device 20 from the node device 20 to the identifier A of the gateway device 30. The identifier A is an identifier used for communication between the gateway device 30 and the S / P-GW 40, or between the gateway device 30 and the S / P-GW 50.

Here, the communication unit 31 transmits the GTP message to which the source address has been converted to the S / P-GW 40 or the S / P-GW 50, which is determined according to the terminal type. For example, the S / P-GW 40 and S / P-GW 50 transmit user data relating to the UE 60 of a particular terminal type. In this case, the communication unit 31 transmits a GTP message to the S / P-GW associated with the determined terminal. In other words, the communication unit 31 distributes the GTP message to a plurality of S / P-GWs according to the terminal type.

As described above, the gateway device 30 of FIG. 1 is used for communication between the node device 20 and the S / P-GW 40 in 3GPP, and further for communication between the node device 20 and the S / P-GW 50. GTP messages can be terminated. Further, the gateway device 30 can distribute the GTP message to a plurality of S / P-GWs according to the terminal type of the UE 60.

Further, the gateway device 30 can change the source address of the GTP message transmitted from the node device 20 from the node device 20 to the gateway device 30. In this way, the gateway device 30 changes the source identification information defined in the GTP message, and transmits the GTP message in which the source identification information is changed to the S / P-GW. As a result, even when the gateway device 30 is arranged between the node device 20 and the S / P-GW 40 and further between the node device 20 and the S / P-GW 50 and terminates the GTP message, it is normal. GTP message can be transmitted to. That is, the S / P-GW 40 and the S / P-GW 50 set the identification information of the gateway device 30 as the destination of the GTP message, so that the node device 20 and the S / P-GW 40 are further connected to each other. The GTP message transmitted between the device 20 and the S / P-GW 50 can be transmitted via the gateway device 30.

(Embodiment 2)
Subsequently, a configuration example of the communication system according to the second embodiment of the present invention will be described with reference to FIG. The communication system of FIG. 2 has an eNB 11, an MME 21, a gateway device 30, a general network 45, an IoT network 55, and a UE 60. Further, the general network 45 has S-GW 41 and P-GW 42. The IoT network 55 has an S-GW 51 and a P-GW 52.

The eNB 11 corresponds to the RAN device 10 of FIG. The MME 21 corresponds to the node device 20 of FIG. The S-GW 41 corresponds to the S / P-GW 40 in FIG. The S-GW 51 corresponds to the S / P-GW 50 in FIG. The gateway device 30 and the UE 60 are the same as those in FIG.

The IoT network 55 is a network that transmits data related to the UE used for the IoT service. For example, the IoT network 55 may be a network that transmits control data and user data related to the UE used for the IoT service.

The general network 45 is a network that transmits data related to UEs other than UEs used for IoT services. For example, the UE other than the UE used for the IoT service may be a mobile phone, a smartphone, or the like that involves user operation when using the service.

The IoT service often transmits a small amount of data as compared with smartphones and the like. Further, the IoT service may have a traffic characteristic that data is transmitted at a predetermined timing in a day.

On the other hand, terminals such as smartphones may receive a large amount of moving image data. Further, it is possible to use various services using a smartphone terminal, and it is considered that the amount of data transmitted and received by the smartphone terminal is increasing in recent years. As described above, the terminals used for the IoT service and the terminals used for other services have different traffic characteristics. Here, the network can be efficiently designed by handling the traffic related to the terminals having the same traffic characteristics in the same network.

For example, in the IoT network 55, which is a network that handles traffic related to terminals with a small amount of user data to be transmitted, the number of node devices such as S-GW that relay user data may be reduced.

On the other hand, the general network 45 handles traffic related to terminals having a large amount of transmitted user data. Therefore, in the general network 45, the number of node devices such as S-GW that relay user data may be increased.

The gateway device 30 determines whether or not the UE 60 is a terminal used for the IoT service, and distributes a message regarding the UE 60 to the S-GW 41 or the S-GW 51.

Subsequently, the flow of Attach processing relating to the UE 60 will be described with reference to FIG. First, the UE 60 transmits an Attach Request message, which is a NAS (Non Access Stratum) message, to the MME 21 via the eNB 11 (S11). The UE 60 may set information regarding the terminal type in the Attach Request message. The information regarding the terminal type may be, for example, information indicating whether or not the terminal is used for the IoT service. Specifically, the UE 60 may set information regarding the terminal type in Device-Properties, which is a parameter set in the NAS message.

Next, the MME 21 transmits a Create Session Request message, which is a GTP message, to the gateway device 30 (S12). The gateway device 30 may be set as the destination of the Create Session Request message, or any S-GW may be set. The MME 21 may set the terminal type set in the Attach Request message to the Signaling Priority Indication which is a parameter in the GTP message.

The destination of the Create Session Request message is determined by the gateway device 30. Therefore, when an arbitrary S-GW is set as the destination of the Create Session Request message, the destination of the Create Session Request message is changed in the gateway device 30. Further, even when an arbitrary S-GW is set as the destination of the Create Session Request message, the communication path is set so that the Create Session Request message is transmitted to the gateway device 30.

Next, the gateway device 30 determines the distribution destination of the Create Session Request message, which is a GTP message (S13). In other words, the gateway device 30 determines the destination of the Create Session Request message. The gateway device 30 determines the distribution destination of the Create Session Request message by using the information regarding the terminal type set in the Create Session Request message. When the information indicating that the terminal is used for the IoT service is set in the terminal type, the gateway device 30 determines that the distribution destination of the Create Session Request message is the S-GW 51. FIG. 3 describes a case where the gateway device 30 determines that the distribution destination of the Create Session Request message is the S-GW 51.

Next, the gateway device 30 changes or replaces the address of the source of the Create Session Request message from the identifier of the MME 21 to the identifier of the gateway device 30 (S14). TEID (Tunnel Endpoint Identifier) specified in GTP is used as the source address of the Create Session Request message. The TEID is information that identifies a tunnel set on a route for transmitting control data between the MME 21 and the S-GW 51. The TEID is information used to identify the node devices at both ends of the tunnel. In other words, the TEID indicating the source of the Create Session Request message is information used to identify the tunnel on the MME21 side.

For example, the TEID indicating MME21 is TEID # A. For example, when the gateway device 30 receives the Create Session Request message in which TEID # A is set as the information indicating the source, the gateway device 30 changes the information indicating the source to TEID # C. The gateway device 30 manages TEID # A and TEID # C in association with each other. In other words, the gateway device 30 assigns TEID # C to TEID # A.

Next, the gateway device 30 transmits a Create Session Request message in which the TEID indicating the source is changed to the S-GW 51, and the S-GW 51 transmits the received Create Session Request message to the P-GW 52 (S15).

Next, the P-GW 52 transmits a Create Session Response message, which is a GTP message, to the S-GW 51, and the S-GW 51 transmits the received Create Session Response message to the gateway device 30 (S16). The S-GW 51 sets TEID # C as the destination of the Create Session Response message. Further, the S-GW 51 sets TEID # D as information indicating the source of the Create Session Response message.

Next, the gateway device 30 changes or replaces the information indicating the source of the Create Session Response message from the identifier of the S-GW 51 to the identifier of the gateway device 30. For example, when the gateway device 30 receives the Create Session Response message in which TEID # D is set as the information indicating the source, the gateway device 30 changes the information indicating the source to TEID # B. The gateway device 30 manages TEID # D and TEID # B in association with each other. In other words, the gateway device 30 assigns TEID # B to TEID # D.

Next, the gateway device 30 transmits a Create Session Response message in which the information indicating the source is changed to the MME 21 (S18). The gateway device 30 sets TEID # A as information indicating the destination of the Create Session Response message.

After that, the normal Attach process specified in 3GPP is continued (S19). Since the normal Attach process is a well-known process, detailed description thereof will be omitted. Further, in the Attach process, the gateway device 30 relays the control data transmitted between the MME 21 and the S-GW 51. The MME 21 sets TEID # B as a TEID indicating the destination of the control data to be transmitted to the S-GW 51, and the S-GW 51 sets TEID # C as a TEID indicating the destination of the control data to be transmitted to the MME 21. As a result, the control data transmitted between the MME 21 and the S-GW 51 is transmitted via the gateway device 30.

When the Attach process is completed, the user data relating to the UE 60 is transmitted via the S-GW 51 and the P-GW 52 (S20).

Subsequently, the flow of the Detach process according to the second embodiment of the present invention will be described with reference to FIG. First, the UE 60 transmits a Detach Request message to the MME 21 via the eNB 11 (S31).

Next, the MME 21 transmits a Delete Session Request message, which is a GTP message, to the S-GW 51 via the gateway device 30 in order to release the EPS (Evolved Packet System) bearer related to the UE 60. Further, the S-GW 51 transmits the received Delete Session Request message to the P-GW 52 (S32). In step S32, the gateway device 30 performs address translation in the same manner as in step S14 of FIG.

Next, the P-GW 52 transmits a Delete Session Response message, which is a GTP message, to the S-GW 51 as a response to the Delete Session Request message (S33). Further, the S-GW 51 transmits the received Delete Session Response message to the MME 21 via the gateway device 30 (S33). In step S33, the gateway device 30 performs address translation in the same manner as in step S17 of FIG.

Next, the MME 21 transmits a Detach Response message to the UE 60 via the eNB 11 as a response to the Detach Request message received in step S31 (S34).

Next, the gateway device 30 releases or deletes the management information associated with TEID # A and TEID # C, and the management information associated with TEID # B and TEID # D in the Attach process of FIG. (S35). In other words, the gateway device 30 releases TEID # C assigned to TEID # A and TEID # B assigned to TEID # D.

As described above, by executing the Attach process according to the second embodiment of the present invention, the gateway device 30 selects the S-GW according to the terminal type of the UE 60, and sends a GTP message to the selected S-GW. Can be sorted. Further, the gateway device 30 terminates and transfers the GTP message between the MME 21 via the gateway device 30 and the S-GW 41 or S-GW 51 by converting the address information set in the GTP message. be able to. That is, the gateway device 30 can relay the GTP message transmitted between the MME and the S-GW by translating the address of the GTP message transmitted between the MME and the S-GW.

In the second embodiment, the Attach process and the Detach process in the communication system of FIG. 2 have been described, but the Attach process and the Detach process in the communication system different from FIG. 2 will be described.

For example, the communication system of FIG. 5 may be used instead of the communication system of FIG. The communication system of FIG. 2 shows a configuration in which LTE is used in a radio access network. The communication system of FIG. 5 shows a configuration in which a wireless access system defined as 3G in 3GPP is used in a wireless access network.

In the communication system of FIG. 5, RNC12 is arranged in place of the eNB 11 in the communication system of FIG. Further, in the communication system of FIG. 5, SGSN22 is arranged instead of MME21 in the communication system of FIG. The configuration other than RNC12 and SGSN22 in the communication system of FIG. 5 is the same as that of the communication system of FIG.

Also in the communication system of FIG. 5, the Attach process described in FIG. 3 and the Detach process described in FIG. 4 are executed.

(Embodiment 3)
Subsequently, a configuration example of the communication system according to the third embodiment of the present invention will be described with reference to FIG. In the communication system of FIG. 6, the gateway device 30 is arranged between the S-GW 46 and the P-GW 47, and further between the S-GW 46 and the P-GW 57. The communication system of FIG. 2 shows a configuration in which the gateway device 30 selects either S-GW 41 or S-GW 51, whereas in the communication system of FIG. 6, the gateway device 30 has P-GW 47 and P-. It differs from the communication system of FIG. 2 in that one of the GW 57 is selected.

Further, the communication system of FIG. 6 is different from the configuration of the communication system of FIG. 5 in that the SGSN 22 connects to the P-GW via the gateway device 30 in that the SGSN 22 connects to the S-GW 46.

Subsequently, the flow of Attach processing relating to the UE 60 in FIG. 6 will be described with reference to FIG. 7. First, the UE 60 transmits an Attach Request message, which is a NAS (Non Access Stratum) message, to the MME 21 via the eNB 11 (S41). The UE 60 may set information regarding the terminal type in the Attach Request message. The information regarding the terminal type may be, for example, information indicating whether or not the terminal is used for the IoT service. Specifically, the UE 60 may set information regarding the terminal type in Device-Properties, which is a parameter set in the NAS message.

Next, the MME 21 transmits a Create Session Request message, which is a GTP message, to the S-GW 46 (S42). The MME 21 may set the terminal type set in the Attach Request message to the Signaling Priority Indication which is a parameter in the GTP message.

Further, the S-GW 46 transmits the received Create Session Request message to the gateway device 30 (S42). The destination of the Create Session Request message is determined by the gateway device 30. Therefore, when an arbitrary P-GW is set as the destination of the Create Session Request message, the destination of the Create Session Request message is changed in the gateway device 30. Further, even if an arbitrary P-GW is set as the destination of the Create Session Request message, the communication path is set so that the Create Session Request message is transmitted to the gateway device 30.

Next, the gateway device 30 determines the distribution destination of the Create Session Request message, which is a GTP message (S43). In other words, the gateway device 30 determines the destination of the Create Session Request message. The gateway device 30 determines the distribution destination of the Create Session Request message by using the information regarding the terminal type set in the Create Session Request message. When the information indicating that the terminal is used for the IoT service is set in the terminal type, the gateway device 30 determines that the distribution destination of the Create Session Request message is P-GW 57. In FIG. 7, a case where the gateway device 30 determines that the distribution destination of the Create Session Request message is P-GW 57 will be described.

Next, the gateway device 30 changes or replaces the address of the source of the Create Session Request message from the identifier of the S-GW 46 to the identifier of the gateway device 30 (S44).

For example, the TEID indicating S-GW46 is TEID # A. For example, when the gateway device 30 receives the Create Session Request message in which TEID # A is set as the information indicating the source, the gateway device 30 changes the information indicating the source to TEID # C. The gateway device 30 manages TEID # A and TEID # C in association with each other. In other words, the gateway device 30 assigns TEID # C to TEID # A.

Next, the gateway device 30 transmits a Create Session Request message in which the TEID indicating the source is changed to the P-GW 57 (S45).

Next, the P-GW 57 transmits a Create Session Response message, which is a GTP message, to the gateway device 30 (S46). The P-GW 57 sets TEID # C as the destination of the Create Session Response message. Further, the P-GW 57 sets TEID # D as information indicating the source of the Create Session Response message.

Next, the gateway device 30 changes or replaces the information indicating the source of the Create Session Response message from the identifier of the P-GW 57 to the identifier of the gateway device 30 (S47). For example, when the gateway device 30 receives the Create Session Response message in which TEID # D is set as the information indicating the source, the gateway device 30 changes the information indicating the source to TEID # B. The gateway device 30 manages TEID # D and TEID # B in association with each other. In other words, the gateway device 30 assigns TEID # B to TEID # D.

Next, the gateway device 30 transmits a Create Session Response message in which the information indicating the source is changed to the S-GW 46 (S48). The gateway device 30 sets TEID # A as information indicating the destination of the Create Session Response message. Further, the S-GW 46 transmits the received Create Session Response message to the MME 21 (S48).

After that, the normal Attach process specified in 3GPP is continued (S49). Since the normal Attach process is a well-known process, detailed description thereof will be omitted. Further, in the Attach process, the gateway device 30 relays the control data transmitted between the S-GW 46 and the P-GW 57. The S-GW 46 sets TEID # B as a TEID indicating the destination of the control data to be transmitted to the P-GW 57, and the P-GW 57 sets the TEID # C as the TEID indicating the destination of the control data to be transmitted to the S-GW 46. To do. As a result, the control data transmitted between the S-GW 46 and the P-GW 57 is transmitted via the gateway device 30.

When the Attach process is completed, the user data regarding the UE 60 is transmitted via the S-GW 46 and the P-GW 57 (S50).

Here, the TEID of the tunnel used for transmitting the user data may be set in the Create Session Request message in steps S42 and S45 and the Create Session Response message in step S46. For example, in the Create Session Request message in step S42, the TEID on the S-GW46 side of the tunnel used for transmitting user data may be set between the S-GW and the P-GW. The gateway device 30 may or may not convert the TEID on the S-GW46 side of the tunnel used for transmitting user data in step S44. Further, the gateway device 30 may or may not convert the TEID on the P-GW57 side of the tunnel used for transmitting user data in step S47.

When the gateway device 30 converts the TEID on the S-GW46 side and the TEID on the P-GW57 side of the tunnel used for transmitting user data, the user data transmitted between the S-GW46 and the P-GW57. Is relayed by the gateway device 30. Further, when the gateway device 30 does not convert the TEID on the S-GW46 side and the TEID on the P-GW57 side of the tunnel used for transmitting user data, the data is transmitted between the S-GW46 and the P-GW57. User data is not relayed by the gateway device 30.

Although the flow of the Attach process for the UE 60 has been described with reference to FIG. 7, the same process as that shown in FIG. 7 is executed for the Attach process for the UE 61. In the Attach process for the UE 61, the eNB 11 in FIG. 7 is replaced with the RNC 12, and the MME 21 in FIG. 7 is replaced with the SGSN 22.

Subsequently, the flow of the Detach process according to the third embodiment of the present invention will be described with reference to FIG. First, the UE 60 transmits a Detach Request message to the MME 21 via the eNB 11 (S61).

Next, the MME 21 transmits a Delete Session Request message, which is a GTP message, to the S-GW 46 in order to release the EPS (Evolved Packet System) bearer relating to the UE 60. Further, the S-GW 46 transmits the received Delete Session Request message to the P-GW 57 via the gateway device 30 (S62). In step S62, the gateway device 30 performs address translation in the same manner as in step S44 of FIG.

Next, the P-GW 57 transmits a Delete Session Response message, which is a GTP message, to the S-GW 46 via the gateway device 30 as a response to the Delete Session Request message (S63). In step S63, the gateway device 30 performs address translation in the same manner as in step S47 of FIG.

Next, the MME 21 transmits a Detach Response message to the UE 60 via the eNB 11 as a response to the Detach Request message received in step S31 (S64).

Next, in the Attach process of FIG. 7, the gateway device 30 releases or deletes the management information associated with TEID # A and TEID # C, and further, the management information associated with TEID # B and TEID # D. (S65). In other words, the gateway device 30 releases TEID # C assigned to TEID # A and TEID # B assigned to TEID # D.

As described above, by executing the Attach process according to the third embodiment of the present invention, the gateway device 30 selects the P-GW according to the terminal type of the UE 60, and sends a GTP message to the selected P-GW. Can be sorted. Further, the gateway device 30 terminates the GTP message between the S-GW 46 via the gateway device 30 and the P-GW 47 or P-GW 57 by converting the address information set in the GTP message. Can be transferred. That is, the gateway device 30 relays the GTP message transmitted between the S-GW and the P-GW by converting the address of the GTP message transmitted between the S-GW and the P-GW. be able to.

(Embodiment 4)
Subsequently, a configuration example of the communication system according to the fourth embodiment of the present invention will be described with reference to FIG. The communication system of FIG. 9 shows that the gateway device 30 is arranged between the SGSN 22 and the P-GW 47, and further between the SGSN 22 and the P-GW 57. The communication system of FIG. 9 shows that the gateway device 30 selects either P-GW 47 or P-GW 57. Further, the communication system of FIG. 9 shows that the UE 61 communicates with the SGSN 22 via the RNC 12.

Subsequently, the flow of the Attach process relating to the UE 61 in FIG. 9 will be described with reference to FIG. First, the UE 61 transmits an Attach Request message, which is a NAS (Non Access Stratum) message, to the SGSN 22 via the RNC 12 (S71). The UE 61 may set information regarding the terminal type in the Attach Request message. The information regarding the terminal type may be, for example, information indicating whether or not the terminal is used for the IoT service. Specifically, the UE 61 may set information regarding the terminal type in Device-Properties, which is a parameter set in the NAS message.

Next, the SGSN 22 transmits a Create PDP Context Request message, which is a GTP message, to the gateway device 30 (S72). The SGSN 22 may set the terminal type set in the Attach Request message to the Signaling Priority Indication which is a parameter in the GTP message. Here, the GTP message transmitted between the SGSN and the P-GW without going through the S-GW follows GTP version 1 (GTPv1). The GTP message transmitted between the MME and the P-GW described in the other embodiments, and the GTP message transmitted between the SGSN and the P-GW via the S-GW are Follow GTP version 2 (GTPv2).

The destination of the Create PDP Context Request message is determined by the gateway device 30. Therefore, when an arbitrary P-GW is set as the destination of the Create PDP Context Request message, the destination of the Create PDP Context Request message is changed in the gateway device 30. Further, even if an arbitrary P-GW is set as the destination of the Create PDP Context Request message, the communication route is set so that the Create PDP Context Request message is transmitted to the gateway device 30.

Next, the gateway device 30 determines the distribution destination of the Create PDP Context Request message, which is a GTP message (S73). In other words, the gateway device 30 determines the destination of the Create PDP Context Request message. The gateway device 30 determines the distribution destination of the Create PDP Context Request message by using the information regarding the terminal type set in the Create PDP Context Request message. When the information indicating that the terminal is used for the IoT service is set in the terminal type, the gateway device 30 determines that the distribution destination of the Create PDP Context Request message is P-GW 57. In FIG. 10, a case where the gateway device 30 determines that the distribution destination of the Create PDP Context Request message is P-GW 57 will be described.

Next, the gateway device 30 changes or replaces the address of the source of the Create PDP Context Request message from the identifier of SGSN 22 to the identifier of the gateway device 30 (S74).

For example, the TEID indicating SGSN22 is TEID # A. For example, when the gateway device 30 receives the Create PDP Context Request message in which TEID # A is set as the information indicating the source, the gateway device 30 changes the information indicating the source to TEID # C. The gateway device 30 manages TEID # A and TEID # C in association with each other. In other words, the gateway device 30 assigns TEID # C to TEID # A.

Next, the gateway device 30 transmits a Create PDP Context Request message in which the TEID indicating the source is changed to the P-GW 57 (S75).

Next, the P-GW 57 transmits a Create PDP Context Response message, which is a GTP message, to the gateway device 30 (S76). The P-GW 57 sets TEID # C as the destination of the Create PDP Context Response message. Further, P-GW 57 sets TEID # D as information indicating the source of the Create PDP Context Response message.

Next, the gateway device 30 changes or replaces the information indicating the source of the Create PDP Context Response message from the identifier of the P-GW 57 to the identifier of the gateway device 30 (S77). For example, when the gateway device 30 receives the Create PDP Context Response message set as TEID # D as the information indicating the source, the gateway device 30 changes the information indicating the source to TEID # B. The gateway device 30 manages TEID # D and TEID # B in association with each other. In other words, the gateway device 30 assigns TEID # B to TEID # D.

Next, the gateway device 30 transmits a Create PDP Context Response message in which the information indicating the source is changed to the SGSN 22 (S78). The gateway device 30 sets TEID # A as information indicating the destination of the Create PDP Context Response message.

After that, the normal Attach process specified in 3GPP is continued (S79). Since the normal Attach process is a well-known process, detailed description thereof will be omitted. Further, in the Attach process, the gateway device 30 relays the control data transmitted between the SGSN 22 and the P-GW 57. The SGSN 22 sets TEID # B as a TEID indicating the destination of the control data to be transmitted to the P-GW 57, and the P-GW 57 sets TEID # C as the TEID indicating the destination of the control data to be transmitted to the SGSN 22. As a result, the control data transmitted between the SGSN 22 and the P-GW 57 is transmitted via the gateway device 30.

When the Attach process is completed, the user data regarding the UE 60 is transmitted via the SGSN22 and the P-GW57 (S80).

Subsequently, the flow of the Detach process according to the fourth embodiment of the present invention will be described with reference to FIG. First, the UE 61 transmits a Detach Request message to the SGSN 22 via the RNC 12 (S91).

Next, the SGSN 22 transmits a Delete PDP Context Request message, which is a GTP message, to the P-GW 57 via the gateway device 30 in order to release the EPS (Evolved Packet System) bearer related to the UE 61 (S92). In step S92, the gateway device 30 performs address translation in the same manner as in step S74 of FIG.

Next, the P-GW 57 transmits a Delete PDP Context Response message, which is a GTP message, to the SGSN 22 via the gateway device 30 as a response to the Delete PDP Context Request message (S93). In step S93, the gateway device 30 performs address translation in the same manner as in step S77 of FIG.

Next, the SGSN 22 transmits a Detach Response message to the UE 61 via the RNC 12 as a response to the Detach Request message received in step S91 (S94).

Next, in the Attach process of FIG. 10, the gateway device 30 releases or deletes the management information associated with TEID # A and TEID # C, and further, the management information associated with TEID # B and TEID # D. (S95). In other words, the gateway device 30 releases TEID # C assigned to TEID # A and TEID # B assigned to TEID # D.

As described above, by executing the Attach process according to the fourth embodiment of the present invention, the gateway device 30 selects the P-GW according to the terminal type of the UE 61, and sends a GTP message to the selected P-GW. Can be sorted. Further, the gateway device 30 terminates and transfers the GTP message between the SGSN 22 via the gateway device 30 and the P-GW 47 or P-GW 57 by converting the address information set in the GTP message. be able to. That is, the gateway device 30 can relay the GTP message transmitted between the SGSN and the P-GW by converting the address of the GTP message transmitted between the SGSN and the P-GW.

(Embodiment 5)
Subsequently, a configuration example of the communication system according to the fifth embodiment of the present invention will be described with reference to FIG. In the communication system of FIG. 12, a DB (database) 100 is added to the communication system of FIG. Further, the IoT core network 91, the IoT core network 92, and the IoT core network 93 exist in the IoT network 55, and the S-GW 71 and the P-GW 72 are arranged in the IoT core network 91, and the IoT core network 92 S-GW73 and P-GW74 are arranged in the IoT core network 93, and S-GW75 and P-GW76 are arranged in the IoT core network 93. Further, the server device 81 is connected to the P-GW 72, the server device 82 is connected to the P-GW 74, and the server device 83 is connected to the P-GW 76.

In the IoT network 55, the IoT core network is divided into the IoT core network 91, the IoT core network 92, the IoT core network 93, and the like for each IoT service provided. Alternatively, a plurality of IoT services may be provided in one IoT core network.

IoT services include, for example, smart meter management services, traffic control services, services related to government offices or emergency agencies, logistics management services, security services, inventory management services, etc. , There are various services.

Further, the server device 81, the server device 82, and the server device 83 may be server devices managed by a service provider that provides the IoT service. That is, the IoT core network 91 may be referred to as an IoT core network provided to the service provider that manages the server device 81. The IoT core network 92 and the IoT core network 93 are similar to the IoT core network 91.

The gateway device 30 terminates the GTP message transmitted from the MME 21 and identifies the core network for transmitting the GTP message from the plurality of IoT core networks. The gateway device 30 uses the DB 100 when specifying the core network for transmitting the GTP message.

The DB 100 manages the identification information of the UE 60 in association with the identification information of the IoT core network in which the UE 60 is registered. The gateway device 30 extracts the identification information of the IoT core network associated with the UE 60 from the DB 100 by using the identification information of the UE 60 included in the GTP message. Further, the gateway device 30 transmits a GTP message to the S-GW located in the specified IoT core network.

Subsequently, the information managed by the DB 100 will be described with reference to FIG. The DB 100 has an information management unit 101 and an information management unit 102. The information management unit 101 and the information management unit 102 may be a memory or the like in the DB 100, or may be an external memory or the like attached to the DB 100.

The information management unit 101 manages the information related to the IoT type and the information related to the CN (core network) type in association with each other. The information regarding the IoT type may be, for example, information that identifies the IoT service. In FIG. 13, numbers such as 1 to 4 are used as information regarding the IoT type. Further, the information regarding the CN type is information for identifying the IoT core network. In FIG. 13, reference numerals such as 91 to 93 assigned to each IoT core network in FIG. 12 are used as information regarding the CN type.

The information management unit 102 manages the information regarding the subscriber number in association with the information regarding the IoT type. The information regarding the subscriber number may be, for example, a telephone number or an aircraft number assigned to the UE 60. Alternatively, the information regarding the subscriber number may be IMSI (International Mobile Subscriber Identity). In FIG. 13, characters such as A to D are used as information regarding the subscriber number.

Further, the information managed in the DB 100 may be distributed and managed in a plurality of devices. For example, the information managed by the information management unit 102 may be arranged in the core network and managed by the HSS (Home Subscriber Server) or the HLR (Home Location Register) that manages the subscriber information.

Subsequently, the flow of the packet distribution processing according to the fifth embodiment of the present invention will be described with reference to FIG. First, the DB 100 registers the information shown in FIG. 13 (S101). For example, the DB 100 may acquire the information shown in FIG. 13 from another server device or the like, or may input the information shown in FIG. 13 from a user or the like who manages the DB 100.

Next, the UE 60 transmits a packet communication start request message to the MME 21 via the eNB 11 in order to start the packet communication (S102). The UE 60 sets the subscriber number in the packet communication start request message. Here, it is assumed that the UE 60 sets the subscriber number A in the packet communication start request message. Next, the MME 21 transmits a packet communication start request message, which is a GTP message, to the gateway device 30 (S103). A subscriber number A is set in the packet communication start request message, which is a GTP message.

Next, the gateway device 30 terminates the packet communication start request message, which is a GTP message transmitted from the MME 21, and extracts the subscriber number of the UE 60. Further, the gateway device 30 transmits a Query message in which the extracted subscriber number A is set to the DB 100 (S104). When the DB 100 receives the Query message in which the subscriber number is set, the information management unit 102 is used to specify the IoT type associated with the subscriber number. Further, the DB 100 uses the information management unit 101 to specify the CN type associated with the IoT type. Here, since the subscriber number A is set in the Query message, the DB 100 specifies the IoT type: 2 and the CN type: 92.

Next, the DB 100 transmits an Answer message for which the CN type: 92 is set to the gateway device 30 (S105). Next, the gateway device 30 determines the distribution destination of the packet communication start request message (S106). In other words, the gateway device 30 determines the destination of the packet communication start request message. The gateway device 30 determines to transmit the packet communication start request message to the S-GW 73 located in the IoT core network 92 corresponding to the CN type: 92 set in the Answer message.

Next, the gateway device 30 changes the source address of the packet communication start request message, which is a GTP message to be transmitted to the S-GW 73, from the identifier of the MME 21 to the identifier of the gateway device 30 (S107). Since the address translation process in step S107 is the same as the address translation process in steps S14 and S17 of FIG. 3, detailed description thereof will be omitted.

Next, the gateway device 30 transmits a packet communication start request message to the S-GW 73 (S108). Further, the S-GW 73 transmits the received packet communication start request message to the P-GW 74 (S108).

As described above, by using the communication system according to the fifth embodiment of the present invention, when there is an IoT core network separated for each IoT service, the gateway device 30 has data on the IoT service used by the UE 60. Data related to the UE 60 can be relayed to the IoT core network that transmits the data.

Further, in the fifth embodiment, as shown in FIG. 15, RNC12 may be used instead of eNB11, and SGSN22 may be used instead of MME21.

Further, also in the first to fourth embodiments, as described in the fifth embodiment, the gateway device 30 may determine the distribution destination of the message by using the DB 100.

Further, when the information managed by the information management unit 102 is managed by the HSS, the DB 100 transmits the Query message received in the step S104 to the HSS. The HSS identifies the IoT type associated with the subscriber number set in the Query message. Next, the HSS sends a message in which the specified IoT type is set to the DB 100. The DB 100 specifies the CN type associated with the IoT type set in the message.

(Embodiment 6)
Subsequently, a configuration example of the communication system according to the sixth embodiment of the present invention will be described with reference to FIG. In the communication system of FIG. 16, a DB (database) 100 is added to the communication system of FIG. Further, the IoT core network 91, the IoT core network 92, and the IoT core network 93 exist in the IoT network 55, the P-GW 77 is arranged in the IoT core network 91, and the IoT core network 92 contains the IoT core network 92. The P-GW 78 is arranged, and the P-GW 79 is arranged in the IoT core network 93. Further, the server device 81 is connected to the P-GW 77, the server device 82 is connected to the P-GW 78, and the server device 83 is connected to the P-GW 79.

The gateway device 30 terminates the GTP message transmitted from the S-GW 46 and identifies the core network for transmitting the GTP message from the plurality of IoT core networks. The gateway device 30 uses the DB 100 when specifying the core network for transmitting the GTP message.

The DB 100 manages the identification information of the UE 60 in association with the identification information of the IoT core network in which the UE 60 is registered. Further, the DB 100 manages the identification information of the UE 61 in association with the identification information of the IoT core network in which the UE 61 is registered. The gateway device 30 extracts the identification information of the IoT core network associated with the UE 60 or UE 61 from the DB 100 by using the identification information of the UE 60 or UE 61 included in the GTP message. Further, the gateway device 30 transmits a GTP message to the P-GW located in the specified IoT core network.

Subsequently, the flow of the packet distribution processing according to the sixth embodiment of the present invention will be described with reference to FIG. Since the process of step S111 is the same as that of step S101 of FIG. 14, detailed description thereof will be omitted.

Next, the UE 60 transmits a packet communication start request message to the MME 21 via the eNB 11 in order to start the packet communication (S112). The UE 60 sets the subscriber number in the packet communication start request message. Here, it is assumed that the UE 60 sets the subscriber number A in the packet communication start request message. Next, the MME 21 transmits a packet communication start request message, which is a GTP message, to the gateway device 30 via the S-GW 46 (S113). A subscriber number A is set in the packet communication start request message, which is a GTP message.

Next, the gateway device 30 terminates the packet communication start request message, which is a GTP message transmitted from the S-GW 46, and extracts the subscriber number of the UE 60. Further, the gateway device 30 transmits a Query message in which the extracted subscriber number A is set to the DB 100 (S114). When the DB 100 receives the Query message in which the subscriber number is set, the information management unit 102 is used to specify the IoT type associated with the subscriber number. Further, the DB 100 uses the information management unit 101 to specify the CN type associated with the IoT type. Here, since the subscriber number A is set in the Query message, the DB 100 specifies the IoT type: 2 and the CN type: 92.

Next, the DB 100 transmits an Answer message for which the CN type: 92 is set to the gateway device 30 (S115). Next, the gateway device 30 determines the distribution destination of the packet communication start request message (S116). In other words, the gateway device 30 determines the destination of the packet communication start request message. The gateway device 30 determines to transmit the packet communication start request message to the S-GW 78 located in the IoT core network 92 corresponding to the CN type: 92 set in the Answer message.

Next, the gateway device 30 changes the source address of the packet communication start request message, which is a GTP message transmitted to the P-GW 78, from the identifier of the S-GW 46 to the identifier of the gateway device 30 (S117). Since the address translation process in step S117 is the same as the address translation process in steps S44 and S47 of FIG. 7, detailed description thereof will be omitted.

Next, the gateway device 30 transmits a packet communication start request message to the P-GW 78 (S118).

Here, the distribution processing of the packet communication start request message regarding the UE 61 in FIG. 16 can be executed by replacing the eNB 11 in FIG. 17 with the RNC 12 and the MME 21 with the SGSN 22.

As described above, by using the communication system according to the sixth embodiment of the present invention, when there is an IoT core network separated for each IoT service, the gateway device 30 has data on the IoT service used by the UE 60. Data related to the UE 60 can be relayed to the IoT core network that transmits the data.

(Embodiment 7)
Subsequently, a configuration example of the communication system according to the seventh embodiment of the present invention will be described with reference to FIG. In the communication system of FIG. 18, a DB (database) 100 is added to the communication system of FIG. Further, the IoT core network 91, the IoT core network 92, and the IoT core network 93 exist in the IoT network 55, the P-GW 77 is arranged in the IoT core network 91, and the IoT core network 92 contains the IoT core network 92. The P-GW 78 is arranged, and the P-GW 79 is arranged in the IoT core network 93. Further, the server device 81 is connected to the P-GW 77, the server device 82 is connected to the P-GW 78, and the server device 83 is connected to the P-GW 79.

The gateway device 30 terminates the GTP message transmitted from the SGSN 22 and identifies the core network for transmitting the GTP message from the plurality of IoT core networks. The gateway device 30 uses the DB 100 when specifying the core network for transmitting the GTP message.

The DB 100 manages the identification information of the UE 61 in association with the identification information of the IoT core network in which the UE 61 is registered. The gateway device 30 extracts the identification information of the IoT core network associated with the UE 61 from the DB 100 by using the identification information of the UE 61 included in the GTP message. Further, the gateway device 30 transmits a GTP message to the P-GW located in the specified IoT core network.

Subsequently, the flow of the packet distribution processing according to the seventh embodiment of the present invention will be described with reference to FIG. Since the process of step S121 is the same as that of step S101 of FIG. 14, detailed description thereof will be omitted.

Next, the UE 61 transmits a packet communication start request message to the SGSN 22 via the RNC 12 in order to start the packet communication (S122). The UE 61 sets the subscriber number in the packet communication start request message. Here, it is assumed that the UE 61 sets the subscriber number A in the packet communication start request message. Next, the SGSN 22 transmits a packet communication start request message, which is a GTP message, to the gateway device 30 (S123). A subscriber number A is set in the packet communication start request message, which is a GTP message.

Next, the gateway device 30 terminates the packet communication start request message, which is a GTP message transmitted from the SGSN 22, and extracts the subscriber number of the UE 61. Further, the gateway device 30 transmits a Query message in which the extracted subscriber number A is set to the DB 100 (S124). When the DB 100 receives the Query message in which the subscriber number is set, the information management unit 102 is used to specify the IoT type associated with the subscriber number. Further, the DB 100 uses the information management unit 101 to specify the CN type associated with the IoT type. Here, since the subscriber number A is set in the Query message, the DB 100 specifies the IoT type: 2 and the CN type: 92.

Next, the DB 100 transmits an Answer message for which the CN type: 92 is set to the gateway device 30 (S125). Next, the gateway device 30 determines the distribution destination of the packet communication start request message (S126). In other words, the gateway device 30 determines the destination of the packet communication start request message. The gateway device 30 determines to transmit the packet communication start request message to the P-GW 78 located in the IoT core network 92 corresponding to the CN type: 92 set in the Answer message.

Next, the gateway device 30 changes the source address of the packet communication start request message, which is a GTP message to be transmitted to the P-GW 78, from the identifier of the SGSN 22 to the identifier of the gateway device 30 (S127). Since the address translation process in step S127 is the same as the address translation process in steps S74 and S77 of FIG. 10, detailed description thereof will be omitted.

Next, the gateway device 30 transmits a packet communication start request message to the P-GW 78 (S128).

As described above, by using the communication system according to the seventh embodiment of the present invention, when there is an IoT core network separated for each IoT service, the gateway device 30 has data on the IoT service used by the UE 61. Data related to the UE 61 can be relayed to the IoT core network that transmits the data.

FIG. 20 is a block diagram showing a configuration example of the gateway device 30. Referring to FIG. 20, the gateway device 30 includes a network interface 1201, a processor 1202, and a memory 1203. Network interface 1201 is used to communicate with network nodes (e.g., eNB, MME, P-GW,). The network interface 1201 may include, for example, an IEEE 802.3 series compliant network interface card (NIC).

The processor 1202 reads the software (computer program) from the memory 1203 and executes it to perform the processing of the gateway device 30 described with reference to the sequence diagram and the flowchart in the above-described embodiment. Processor 1202 may be, for example, a microprocessor, MPU, or CPU. Processor 1202 may include a plurality of processors.

The memory 1203 is composed of a combination of a volatile memory and a non-volatile memory. Memory 1203 may include storage located away from processor 1202. In this case, processor 1202 may access memory 1203 via an I / O interface (not shown).

In the example of FIG. 20, memory 1203 is used to store software modules. The processor 1202 can perform the processing of the gateway device 30 described in the above-described embodiment by reading these software modules from the memory 1203 and executing them.

As described with reference to FIG. 20, each of the processors included in the gateway device 30 in the above embodiment comprises one or more programs including instructions for causing the computer to perform the algorithm described with reference to the drawings. Execute.

In the above example, the program can be stored and supplied to a computer using various types of non-transitory computer readable media. Non-transitory computer-readable media include various types of tangible storage media. Examples of non-temporary computer-readable media include magnetic recording media (eg, flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg, magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / W, semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)) are included. The program may also be supplied to the computer by various types of transient computer readable media. Examples of temporary computer-readable media include electrical, optical, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.

The present invention is not limited to the above embodiment, and can be appropriately modified without departing from the spirit.

10 RAN equipment 11 eNB
12 RNC
20-node device 21 MME
22 SGSN
30 Gateway device 31 Communication unit 32 Judgment unit 33 Conversion unit 40 S / P-GW
41 S-GW
42 P-GW
45 General network 46 S-GW
47 P-GW
50 S / P-GW
51 S-GW
52 P-GW
55 IoT Network 57 P-GW
60 UE
61 UE
71 S-GW
72 P-GW
73 S-GW
74 P-GW
75 S-GW
76 P-GW
77 P-GW
78 P-GW
79 P-GW
81 Server device 82 Server device 83 Server device 84 Server device 91 IoT core network 92 IoT core network 93 IoT core network 100 DB
101 Information Management Department 102 Information Management Department

Claims (7)

A node device that executes communication according to GTP (GPRS (General Packet Radio Service) Tunneling Protocol) and S-GW (Serving-Gateway), or a node device that executes communication according to GTP and P-GW (PDN (PDN) Packet Data Network)-Gateway device located between Gateway)
A communication unit that terminates the GTP message transmitted from the node device, and
A determination unit that determines the terminal type of the mobile station associated with the GTP message, and
A conversion unit that changes the source address set in the GTP message transmitted from the node device from the identifier of the node device to the first identifier of the gateway device is provided.
The communication unit
The GTP message source address is converted, and sends to the S-GW or P-GW, which is determined in accordance with the terminal type,
The conversion unit
The source address set in the GTP message transmitted from the S-GW or the P-GW is changed from the identifier of the S-GW or the P-GW to the second identifier of the gateway device, and the above. The identifier of the node device and the first identifier are associated and managed, and further, the identifier of the S-GW or the P-GW and the second identifier are associated and managed.
The communication unit
When a GTP message destined for the first identifier is received from the S-GW or the P-GW, a GTP message whose destination is changed to the identifier of the node device is transmitted to the node device, and the node device sends the GTP message. When a GTP message destined to the second identifier is received, a gateway device that transmits a GTP message whose destination is changed to the S-GW or the P-GW identifier to the S-GW or the P-GW. .. The determination unit
Using the GTP message transmitted in the Attach process of the mobile station, the terminal type of the mobile station is determined.
The communication unit
The gateway device according to claim 1, wherein the GTP message is transmitted to the S-GW or the P-GW arranged in the registration network of the mobile station determined according to the terminal type. The identifier of the node device, the identifier of the S-GW or the P-GW, the first identifier, and the second identifier identify a tunnel used for transmitting a control message, TEID (Tunnel Endpoint Identifier). ), The gateway device according to claim 1 or 2 . The conversion unit
The TEID that identifies the tunnel used for transmitting user data included in the GTP message transmitted from the node device is converted from the TEID that identifies the node device to the TEID that identifies the gateway device, and the TEID is described. A TEID that identifies a tunnel used for transmitting user data included in a GTP message transmitted from the S-GW or the P-GW is obtained from the TEID that identifies the S-GW or the P-GW. The gateway device according to claim 3 , which is converted into a TEID that identifies the gateway device. The conversion unit
When a session release instruction message between the node device and the S-GW or a session release instruction message between the node device and the P-GW is received, the identifier of the node device and the first The gateway device according to claim 1 or 2 , wherein the association with the identifier of 1 and further the association between the identifier of the S-GW or the P-GW and the identifier of the second identifier are canceled. A node device that executes communication according to GTP (GPRS (General Packet Radio Service) Tunneling Protocol) and S-GW (Serving-Gateway), or a node device that executes communication according to GTP and P-GW (PDN (PDN) Packet Data Network)-A communication method in a gateway device located between Gateway).
Terminate the GTP message transmitted from the node device,
The terminal type of the mobile station associated with the GTP message is determined, and
The source address set in the GTP message transmitted from the node device is changed from the identifier of the node device to the first identifier of the gateway device.
The GTP message source address is converted, and sends to the S-GW or P-GW, which is determined in accordance with the terminal type,
The source address set in the GTP message transmitted from the S-GW or the P-GW is changed from the identifier of the S-GW or the P-GW to the second identifier of the gateway device, and the above. The identifier of the node device and the first identifier are associated and managed, and further, the identifier of the S-GW or the P-GW and the second identifier are associated and managed.
When a GTP message destined for the first identifier is received from the S-GW or the P-GW, a GTP message whose destination is changed to the identifier of the node device is transmitted to the node device, and the node device sends the GTP message. A communication method in which when a GTP message destined to the second identifier is received, a GTP message whose destination is changed to the S-GW or the P-GW identifier is transmitted to the S-GW or the P-GW. .. A node device that executes communication according to GTP (GPRS (General Packet Radio Service) Tunneling Protocol) and S-GW (Serving-Gateway), or a node device that executes communication according to GTP and P-GW (PDN (PDN) Packet Data Network)-A program that is executed by a computer that is a gateway device placed between (Gateway).
Terminate the GTP message transmitted from the node device,
The terminal type of the mobile station associated with the GTP message is determined, and
The source address set in the GTP message transmitted from the node device is changed from the identifier of the node device to the first identifier of the gateway device.
The GTP message to which the source address has been converted is transmitted to the S-GW or P-GW determined according to the terminal type .
The source address set in the GTP message transmitted from the S-GW or the P-GW is changed from the identifier of the S-GW or the P-GW to the second identifier of the gateway device, and the above. The identifier of the node device and the first identifier are associated and managed, and further, the identifier of the S-GW or the P-GW and the second identifier are associated and managed.
When a GTP message destined for the first identifier is received from the S-GW or the P-GW, a GTP message whose destination is changed to the identifier of the node device is transmitted to the node device, and the node device sends the GTP message. When a GTP message destined to the second identifier is received , the computer sends a GTP message whose destination is changed to the S-GW or the P-GW identifier to the S-GW or the P-GW. Program to be executed by.

Images