JP7262734B2 - Gateway device and communication control method - Google Patents

Description

The present invention relates to a gateway device and a communication control method.

Conventionally, in LTE communication systems, ePDG (enhanced packet data gateway) is known as a component for accommodating non-3GPP (non-3GPP) terminals that perform non-3GPP (Third Generation Partnership Project) radio access in EPC (Evolved Packet Core). (see Non-Patent Documents 1 and 2). In other words, the ePDG operates as a gateway to which mobile terminals connect when accommodating untrusted non-3GPP wireless access (Untrusted Non-3GPP IP Access) such as a public wireless LAN (Local Area Network).

”3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses (Release 15)”, 3GPP TS 23.402 V15.0.0 (217-06), P30-P31 Takehiro Nakamura, 5 others, ``Activities and Contributions to Completion of 3GPP LTE/SAE Standard Specifications'', NTT DOCOMO Technical Journal Vol.17 No.2, P36-P45

Conventional ePDG is for communication connection with other core nodes in EPC (for example, HSS (Home Subscriber Server), PGW (PDN Gateway (Packet Data Network Gateway)), PCRF (Policy and Charging Rule Function), 3GPP AAA Server) has many interfaces. In addition, when a non-3GPP terminal attempts to access a network (3GPP network (e.g., LTE network)) that communicates according to the 3GPP communication scheme, the traffic always passes through the ePDG. Therefore, when a large number of non-3GPP terminals access the LTE network, The processing load of ePDG increases. In addition, since the ePDG directly cooperates with other core nodes in the EPC, it is necessary to maintain the security of the ePDG.

In other words, the ePDG has many interfaces with other core nodes and is assumed to be arranged in the core network, and the requirements for ePDG functions, network capacity, and security are high. These requirements are difficult to meet when using a large number of ePDGs as nodes to accommodate non-3GPP terminals. In other words, the ePDG is not expected to have a large number of non-3GPP connections, making it difficult to meet these requirements.

The present invention has been made in view of the above-described conventional situation, and provides a gateway device and communication device capable of simplifying functions when accommodating non-3GPP terminals in a 3GPP network, suppressing network load concentration, and ensuring security. Provide a control method.

One aspect of the present invention is a gateway device that accommodates a non-3GPP terminal located in a non-3GPP (Third Generation Partnership Project) network in the 3GPP network and communicates with a core network device having the non-3GPP terminal and a plurality of nodes. an authentication unit that authenticates a user of the non-3GPP terminal in cooperation with a first processing node that is a node that processes control data and cooperates with a management node that manages subscriber information; a second processing node that relays the control data between and the non-3GPP terminal and processes user data and a communication unit that relays the user data between the non-3GPP terminal and the communication unit communicates with the core network device via an interface for communicatively connecting a base station according to the 3GPP communication scheme and the first processing node, and the communication unit is included in the interface, the core network A gateway device that communicates with the core network device via an interface that omits messages related to handover between the device and the gateway device.

One aspect of the present invention is a communication control method in a gateway device that accommodates a non-3GPP terminal arranged in a non-3GPP network in a 3GPP network and communicates with a core network device having the non-3GPP terminal and a plurality of nodes, authenticating a user of the non-3GPP terminal in cooperation with a first processing node that is a node that processes control data and cooperates with a management node that manages subscriber information; relaying the control data between a 3GPP terminal and relaying the user data between a second processing node that processes user data and the non-3GPP terminal, wherein the relaying comprises: communicating with the core network device via an interface for communicatively connecting a base station according to the 3GPP communication scheme and the first processing node; communicating with the core network device via the interface; a step of communicating with the core network device via an interface included in the interface in which a message related to handover between the core network device and the gateway device is omitted; be.

ADVANTAGE OF THE INVENTION According to this invention, the function at the time of accommodating a non-3GPP terminal in a 3GPP network can be simplified, network load concentration can be suppressed, and security can be ensured.

1 is a block diagram showing a schematic configuration example of an LTE communication system accommodating non-3GPP terminals according to an embodiment; FIG. Block diagram showing a configuration example of an LTE communication system accommodating a large number of non-3GPP terminals Block diagram showing a configuration example of an LTE communication system accommodating 3GPP terminals and non-3GPP terminals in a comparative example Block diagram showing a configuration example of an LTE communication system accommodating a large number of 3GPP terminals and non-3GPP terminals in a modification

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings.

(embodiment)
FIG. 1 is a diagram showing a schematic configuration example of an LTE communication system 5 in an embodiment. The LTE communication system 5 has a UE (User Equipment) 10A, a gateway 30, a control device 40, and an EPC device 50. The gateway 30 includes a processing section 31 , a storage section 32 and a communication section 33 . EPC device 50 includes PGW 51 , SGW 53 , MME (Mobility Management Entity) 54 , and HSS (Home Subscriber Server) 55 . The LTE communication system 5 accommodates non-3GPP terminals in the LTE network.

UE 10A communicates with gateway 30 via non-3GPP network N1. Non-3GPP networks N1 may include LANs (eg, wireless LANs, wired LANs), the Internet, and the like. UE 10A is a non-3GPP terminal. A non-3GPP terminal may be, for example, a terminal that communicates with another communication device via a LAN (eg, wireless LAN, wired LAN). UE 10A is owned by a user. A plurality of UEs 10A may exist.

The gateway 30 manages the UE 10A under the control of the gateway 30 and relays communication between the UE 10A and the EPC device 50. The gateway 30 may be installed outdoors, or may be installed in each building, for example. A plurality of gateways 30 may exist. One or more UE 10A may exist under each of the multiple gateways 30 . A conventional LTE communication system has a mechanism for managing a large number of distributed base stations (eNBs (eNodeBs)), and this mechanism is also exploited in the LTE communication system 5 accommodating non-3GPP accesses.

The gateway 30 has a part of the ePDG function, and may operate as a base station that accommodates the UE 10A under the gateway 30 in the EPC device 50 for performing LTE communication. However, unlike ePDG, it is not directly connected to the PGW 51 and HSS 55 of the EPC device 50, and cooperates with the MME 54 and SGW 53 of the EPC device 50 to perform the user authentication function of the UE 10A, the control data and user data relay function, etc. come true.

The gateway 30 performs authentication processing and data relay processing related to LTE communication. In this case, gateway 30 cooperates with MME 54 and HSS 55 that manage subscriber information in EPC device 50 to authenticate the user of UE 10A. In addition, the gateway 30 relays communication data (for example, control data or user data) from the UE 10A to the SGW 53, PGW 51, SGi (networks above EPC), etc., or relays communication data from the SGW 53, PGW 51, SGi, Relay to UE 10A. In this case, gateway 30 may relay control data between UE 10A and MME 54 . Also, the gateway 30 may relay user data between the UE 10A and the SGW 53.

The processing unit 31 of the gateway 30 implements various functions by executing a program held in a memory by a processor (for example, a CPU (Central Processing Unit)). The storage unit 32 of the gateway 30 may have, for example, ROM (Read Only Memory), RAM (Random Access Memory), and various storages (eg, HDD (Hard Disk Drive), SSD (Solid State Drive)), and stores various information, Holds data and programs. A communication unit 33 of the gateway 30 communicates (wired communication or wireless communication) with the UE 10A and the EPC device 50 .

The processing unit 31 cooperates with at least some nodes of the EPC device 50 to authenticate the user of the UE 10A. The processing unit 31 relays control data and user data via the communication unit 33 .

As shown in FIG. 1, gateway 30 communicates with UE 10A as a non-3GPP terminal and not with a 3GPP terminal. Therefore, the gateway 30 need not have a communication interface for communicating with 3GPP terminals.

The EPC device 50 is a device arranged in the LTE core network, and communicates with the gateway 30 according to the LTE protocol. Each node of the PGW 51, SGW 53, MME 54, and HSS 55 of the EPC device 50 may be either a logical node or a physical node. In other words, the functions may be integrated into one device (server), or the functions may be distributed among a plurality of individual devices (servers). The EPC device 50 may also include a PCRF node. Note that the EPC device 50 is not limited to this configuration and can include other incidental elements.

The MME 54 and HSS 55 process C-plane data, which is control data, together with the PCRF. The SGW 53 and PGW 51 process U-plane data, which is user data. Therefore, for example, U-plane data from the external network (on the upstream side of the EPC device 50) to the UE 10A, that is, U-plane traffic, reaches the EPC device 50 from the external network via the PGW 51, the SGW 53, and the gateway 30, It is transmitted to UE 10A.

The MME 54 is a node that provides mobility control and the like, and performs location registration, paging, mobility control such as handover, and establishment or deletion of bearers (data communication paths). Note that if the LTE communication system 5 does not include a 3GPP terminal, the MME 54 does not have to have a handover function.

The HSS 55 is a node having a subscriber management database in LTE, and manages subscriber contract information, authentication information, location information, and the like. MME54 implements user authentication based on the authentication information notified from HSS55.

The SGW 53 is a gateway that is connected to the gateway 30, accommodates non-3GPP access, and transmits data to the UE 10A and the PGW 51.

The PGW 51 is a gateway that assigns an IP address to the UE 10A, transfers packets, etc., at a connection point with an external network (PDN). By cooperating with the PCRF, the PGW 51 may operate according to the policy (policy control information) of the PCRF. The PGW 51 may control the amount of communication and the speed of communication through each bearer according to the policy of the PCRF.

The PCRF is a node that controls QoS (Quality of Service; communication quality control such as packet priority transfer) for user data transfer and charging. The QoS value determined by the PCRF is notified to the PGW 51 . The PGW 51 performs QoS control on U-plane data according to the notified QoS value. The QoS value may be, for example, a set value included in policy control information.

The EPC device 50 has a processing section, a storage section, and a communication section. When each node of the EPC device 50 is a logical node, one device may be provided with a processing unit, a storage unit, and a communication unit. When each node of the EPC device 50 is a physical node, each node may be provided with a processing unit, a storage unit, and a communication unit.

The processing unit of the EPC device 50 implements various functions by executing a program held in a memory by a processor (for example, CPU). The storage unit of the EPC device 50 may have, for example, ROM, RAM, and various storages (eg, HDD, SSD), and holds various information, data, and programs. The communication unit of the EPC device 50 communicates (wired communication or wireless communication) with various devices in the gateway 30 and an external network. Communication by the EPC device 50 includes LTE communication. LTE communication may include VoLTE communication.

FIG. 2 is a block diagram showing a configuration example of an LTE communication system 5 that accommodates UEs 10A as many non-3GPP terminals.

In the LTE communication system 5 shown in FIG. 2, an AP (Access Point) 20 that manages communication in a wireless LAN as an example of the non-3GPP network N1 is arranged. That is, the AP 20 relays communication between the UE 10A and the gateway 30. FIG. The AP 20 may be arranged in the LTE communication system 5 of FIG. 1 as well.

In FIG. 2, the architecture is such that a large number of gateways 30 accommodating UE 10A as non-3GPP terminals are arranged under the control of EPC device 50 and managed. Gateways 30 can also be numerically distributed, geographically distributed. The interface between the gateway 30 and the EPC device 50 may use the same S1 interface as when accommodating an eNB as a general base station of the LTE communication system. In this case, it is possible to use an interface that omits the messages related to the handover of S1AP (S1 Application Protocol) among the messages that the S1 interface has.

Details of the S1AP protocol are described in Reference 1 below.
(Reference Non-Patent Document 1: ``3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Access Network E-UTRAN); S1 Application Protocol (S1AP) (Release 8)'', 3GPP TS 36.413 V8.0.0 (2007 -12), P22-P27, P44-P50)

S1AP includes handover related messages such as HANDOVER REQUIRED, HANDOVER COMAND, HANDOVER PREPARATION FAILURE, HANDOVER REQUEST, HANDOVER REQUEST ACKNOWLEDGE, HANDOVER FAILURE, HANDOVER NOTIFY, HANDOVER CANCEL, HANDOVER CANCEL ACKNOWLEDGE. The gateway 30 may not respond to these handover related messages compared to the eNB if it does not perform the handover. Specifically, the gateway 30 does not need to have the function of transmitting and receiving messages related to handover while having some of the functions of the eNB.

Also, although the LTE communication system 5 accommodates non-3GPP terminals, an architecture similar to that of the LTE communication system accommodating 3GPP terminals is applied to the management of the non-3GPP network N1.

For example, it may be difficult to deploy the ePDG at the same site where the non-3GPP network N1 (eg, wireless LAN) is installed. On the other hand, the gateway 30, like an eNB (eNodeB), can be located in a remote location or in a facility different from the 3GPP network (eg, LTE network N2) and administrator.

Each node and link of the EPC device 50 can flexibly cope with an increase or decrease in the number of gateways 30 . For example, in response to an increase in traffic associated with an increase in the number of UE 10A terminals, the number of nodes and links may be increased. It is conceivable to increase the setting. For example, in a use case of an in-house base, the number of gateways 30 that effectively operate may be increased during the daytime hours, and the number of gateways 30 that effectively operate may be decreased during the nighttime hours. Also, the number of gateways 30 may be increased when the number of branch offices is increased.

Thus, the LTE communication system 5 does not need to increase the number of ePDGs even if the number of gateways 30 is increased or decreased. Therefore, the LTE communication system 5 can suppress the increase in cooperation information on the HSS and PGW side for increasing the cooperation between the ePDG and the HSS and PGW as the number of UEs 10A increases, can reduce labor, and can simplify the design. . In addition, the LTE communication system 5 does not require additional registration of subscriber information in the subscriber management database held in the HSS for ePDG, thereby simplifying the design. Therefore, the LTE communication system 5 can improve flexibility in increasing or decreasing the number of gateways 30 .

FIG. 3 is a block diagram showing a configuration example of an LTE communication system 5X accommodating 3GPP terminals and non-3GPP terminals in a comparative example. In FIG. 3, the 3GPP terminal is denoted UE 10B and the non-3GPP terminal is denoted UE 10A.

The LTE communication system 5X has an architecture assuming management of a large number of base stations (here, eNB 30X) and terminals (here, UE 10B as 3GPP terminals). Therefore, the LTE communication system 5X has an architecture that distributes and processes the processing load related to LTE communication. On the other hand, ePDG60X in the LTE communication system 5X is a function (node) added later for the purpose of offloading, so it is a centralized function that is different from the original design of the LTE communication system that manages the LTE network N2. Department. In other words, the ePDG 60X does not enjoy the merit of distributed processing in the LTE communication system 5X.

In FIG. 3, when a communication request occurs in the UE 10A as a non-3GPP terminal, communication data passes through the ePDG 60X via the AP 20 and the like. Also, when a communication request occurs in the UE 10B as a 3GPP terminal, communication data passes through the ePDG 60X via the eNB 30X, MME 54X, SGW 53X, HSS 55X, PGW 51X, and the like. In the LTE communication system 5X, an ePDG 60X is arranged at the boundary between the LTE network N2 and the non-3GPP network N1.

Therefore, in communication across the LTE network N2 and the non-3GPP network N1, all user traffic is concentrated on the ePDG 60X. Also, as shown in Reference Non-Patent Document 2, the ePDG 60X must have an S2b interface, a SWu interface, a SWn interface, a SWm interface, a Gxb interface, etc., and there are many required interfaces. Also, since the ePDG 60X is connected to a node that requires a high security level, such as the subscriber database of the HSS 55X, it is necessary to ensure security. In addition, the ePDG 60X has a function of cooperating with the HSS 55X of the MME 54X in order to cooperate with the HSS 55X without cooperating with other nodes. Therefore, in the LTE communication system 5X, the functions of the MME 54 (for example, the authentication function for authenticating the user) are redundantly provided.

In other words, the ePDG 60X does not cooperate with the MME 54X as can be understood from FIG. MME 54X has a function of cooperating with HSS 55X to authenticate the user of UE 10A. The ePDG 60X has a format in which the user authentication function of the MME 54X is re-implemented in the ePDG. That is, the MME 54X has a function of cooperating with the HSS 55X to authenticate the user of the UE 10B. Therefore, when increasing the number of ePDG 60X, it was necessary to create and manage many nodes corresponding to MME 54X for many ePDG 60X.

On the other hand, the LTE communication system 5 has the gateway 30, so that when accommodating the UE 10A as a non-3GPP terminal, an ePDG 60X having a cooperation function (authentication cooperation function) for user authentication of the MME 54 is separately prepared. There is no need to duplicate the functions of the MME 54, and the functions for LTE communication can be simplified.

In addition, in the LTE communication system 5X, the required number of ePDG60X is predicted based on the number of subscribers to the LTE communication system 5X, and the number of installed ePDG60X is fixed based on the prediction result. was not expected to change the number of Therefore, it does not have the flexibility to increase or decrease the number of ePDG 60X according to the increase or decrease of the number of subscribers.

In contrast, according to the LTE communication system 5 of the present embodiment, the architecture is such that the HSS 55, PGW 51, gateway 30, AP 20, UE 10A, and the like are integrated. Furthermore, the LTE communication system 5 has a configuration in which the gateway 30 has an authentication function and a relay function instead of the ePDG 60X. In addition, in the LTE communication system 5, the gateway 30 and the MME 54 and SGW 53 cooperate, and the MME 54 and SGW 53 cooperate with the HSS 55 and PGW 51 to accommodate the UE 10A as a non-3GPP terminal in the LTE network N2 of the LTE communication system 5. It is possible. Therefore, unlike the ePDG 60X, the LTE communication system 5 does not need to have an interface for direct cooperation with the PGW 51 and the HSS 55 . Therefore, the function for accommodating the UE 10A as a non-3GPP terminal in the LTE communication system 5 can be simplified.

Also, the LTE communication system 5 can use an existing S1 interface (S1AP) for communication between the gateway 30 that accommodates the UE 10A as a non-3GPP terminal and the EPC device 50 . Therefore, the LTE communication system 5 can eliminate the need to newly create an interface for communication between the gateway 30 and the EPC device 50 .

Also, in the LTE communication system 5, the gateway 30 does not have to have a handover function. This is because a device (for example, AP 20) in the non-3GPP network N1 performs handover-related processing or does not require handover-related processing. Since handover processing has a large processing load compared to other processing, it is beneficial to be able to omit it.

Also, unlike the ePDG 60X having the function of the MME 54X, the MME 54 of the EPC device 50 provided separately from the gateway 30 cooperates with the HSS 55, so that the gateway 30 does not need to implement the authentication cooperation function. .

In addition, unlike the ePDG 60X arranged for offloading in the LTE communication system 5X, the gateway 30 can use the distributed processing function of the LTE communication system 5, and the number of installations can be increased or decreased according to the number of terminals of the UE 10A. . Therefore, it is possible to suppress the concentration of communication traffic with the UE 10A as a non-3GPP terminal on the gateway 30 .

Further, since the gateway 30 is not directly connected to the HSS 55 or PCRF that handle subscriber information, the subscriber information can be safely handled.

Also, when managing the UE 10A as a non-3GPP terminal using the EPC device 50, the LTE communication system 5 can reduce the functions of the nodes used for management, and distribute the traffic passing through each node.

(Modification)
FIG. 4 is a block diagram showing a configuration example of an LTE communication system 5A that accommodates 3GPP terminals and non-3GPP terminals in a modified example. Although FIG. 2 illustrates that UE 10A as a non-3GPP terminal communicates within the LTE communication system 5, in FIG. 4, UE 10A as a non-3GPP terminal and UE 10B as a 3GPP terminal communicate within the LTE communication system 5A. exemplify what to do. In addition, since the SGW 53 includes the UE 10B as well as the UE 10A in communication terminals, the SGW 53 may accommodate 3GPP access.

When a communication request occurs in the UE 10A, the UE 10A communicates communication data with the gateway 30A via the AP20. In this case, gateway 30A has the same function as gateway 30 of LTE communication system 5 . The UE 10B communicates communication data with the gateway 30A without going through the AP20. That is, the gateway 30A also has functions similar to those of the eNB 30X of the LTE communication system 5X. Since the UE 10B may be connected, the communication interface for communicating with the UE 10B is provided without omission.

Also, the gateway 30A may determine whether or not the communication connection destination (for example, communication destination or communication source) is the UE 10A as a non-3GPP terminal and does not include the UE 10B as a 3GPP terminal. The gateway 30A determines whether the communication connection destination is a 3GPP terminal or a non-3GPP terminal, for example, a communication method (for example, a 3GPP communication method such as LTE communication, a non-3GPP terminal such as wireless LAN communication, etc.) in which the communication connection destination connects to the gateway 30A. communication method). The gateway 30 omits the function related to handover when determining that the communication connection destination does not include the 3GPP terminal, and does not omit the function related to handover when determining that the communication connection destination includes the 3GPP terminal. , the functions related to handover may be switched. As a result, the LTE communication system 5A can reduce the processing load when handover is unnecessary while realizing handover when handover is necessary.

Note that omitting handover-related functions may include not transmitting, not receiving, receiving but disabling, receiving but not analyzing, etc., S1AP handover-related messages.

In this way, the LTE communication system 5 supports LTE communication for both 3GPP terminals and non-3GPP terminals, and can suppress partial concentration of traffic when non-3GPP terminals are accommodated in the LTE network N2, thereby improving security. It can be easily secured and the number of required nodes can be reduced.

As described above, the gateway 30 (an example of a gateway device) of the present embodiment accommodates the UE 10A (an example of a non-3GPP terminal) located in the non-3GPP network N1 in the LTE network N2 (an example of a 3GPP network), and an EPC device 50 (an example of a core network device) having a plurality of nodes. The gateway 30 includes a processing section 31 (an example of an authentication section) and a communication section 33 . The processing unit 31 cooperates with the MME 54 to authenticate the user of the UE 10A. The MME 54 is a node that processes control data and is an example of a first processing node that cooperates with the HSS 55 . HSS 55 is an example of a management node that manages subscriber information. The communication unit 33 relays control data between the MME 54 and the UE 10A, and relays user data between the SGW 53 and the UE 10A. The SGW 53 is an example of a second processing node that processes user data. The communication unit 33 may communicate with the EPC device 50 via an S1 interface (an example of an interface) for communication connection between the eNB and the MME 54 . The eNB is an example of a base station that complies with the LTE communication scheme (an example of the 3GPP communication scheme).

As a result, when the UE 10A is accommodated in the LTE network N2, the gateway 30 can eliminate the need to separately prepare the ePDG 60X having the authentication cooperation function of the MME 54, and can eliminate the need to duplicate the functions of the MME 54. , the function for LTE communication can be simplified. In addition, the gateway 30 can aggregate communication connection destinations to the AP 20, the MME 54 of the EPC device 50, and the SGW 53, and can reduce the number of interfaces that the gateway 30 has compared to the case where the ePDG 60X is provided. In addition, since the gateway 30 can avoid direct connection to important information such as subscriber information and policy information possessed by the HSS 55 and PCRF, the security of the entire LTE communication system 5 can be avoided without increasing the security of the gateway 30. can be maintained. In addition, the gateway 30 can communicate on the EPC device 50 side using an existing communication interface, eliminating the need to provide a new communication interface, and easily constructing the LTE communication system 5 that can accommodate the UE 10A in the LTE network N2. can.

In this way, the gateway 30 simplifies functions when accommodating non-3GPP terminals in a 3GPP network such as the LTE network N2, suppresses network load concentration, and ensures security.

Further, the communication unit 33 may communicate with the EPC device 50 via an interface in which the handover-related message included in the S1 interface is omitted.

As a result, the gateway 30 can communicate with the EPC device 50 using a simplified existing communication interface, and can eliminate the need for relatively heavy processing load related to handover.

Further, the communication unit 33 may communicate with the UE 10B (an example of a 3GPP terminal) arranged in the LTE network N2. , control data may be relayed between MME 54 and UE 10B, and user data may be relayed between MME 54 and UE 10B.

This allows the gateway 30A to perform LTE communication not only with the UE 10A as a non-3GPP terminal, but also with the UE 10B as a 3GPP terminal. Therefore, the gateway 30A has a simple configuration, reduces network load, ensures security, and supports construction of the LTE communication system 5A that enables communication between both 3GPP terminals and non-3GPP terminals.

Various embodiments have been described above with reference to the drawings, but it goes without saying that the present invention is not limited to such examples. It is obvious that a person skilled in the art can conceive of various modifications or modifications within the scope described in the claims, and these also belong to the technical scope of the present invention. Understood.

Although one EPC device 50 is mainly illustrated in the above embodiment, a plurality of EPC devices may exist. In this case, each UE 10A may be connected to a different EPC device 50 to relay data. For example, the communication unit 33 of the first gateway 30 relays control data between the MME 54 of the first EPC device 50A and the first UE 10A, and the SGW 53 of the first EPC device 50A and the first UE 10A , the communication unit 33 of the second gateway 30 relays control data between the MME 54 of the second EPC device 50A and the second UE 10A, and the second EPC device 50A of User data may be relayed between the SGW 53 and the second UE 10A.

That is, the communication unit 33 may relay control data and user data to the EPC device 50 that differs for each UE 10A via the S1 interface. As a result, according to the contract for using the 3GPP network, the gateway 30 can use different EPC devices 50 (for example, SGW-PGW-SGi) according to contract details, settings of the UE 10A, etc., even if the terminals are under the same gateway. system) can relay the contents of communication.

INDUSTRIAL APPLICABILITY The present invention is useful for a gateway device, a communication control method, etc. that can simplify functions when accommodating non-3GPP terminals in a 3GPP network, suppress network load concentration, and ensure security.

5,5A LTE communication system 10,10A,10B UE
20 APs
30, 30A gateway 31 processing unit 32 storage unit 33 communication unit 50, 50X EPC device 51, 51X PGW
53, 53X SGW
54, 54X MME
55,55X HSS
N1 non-3GPP network N2 LTE network

Claims (5)

A gateway device that accommodates a non-3GPP terminal located in a non-3GPP (Third Generation Partnership Project) network in a 3GPP (registered trademark) network and communicates with a core network device having the non-3GPP terminal and a plurality of nodes,
an authentication unit that authenticates a user of the non-3GPP terminal in cooperation with a first processing node that is a node that processes control data and cooperates with a management node that manages subscriber information;
a communication unit that relays the control data between the first processing node and the non-3GPP terminal, and relays the user data between the second processing node that processes user data and the non-3GPP terminal;
with
The communication unit communicates with the core network device via an interface for communication connection between a base station conforming to the 3GPP communication scheme and the first processing node ,
The communication unit communicates with the core network device via an interface, which is included in the interface and omits messages related to handover between the core network device and the gateway device,
gateway device. the 3GPP network is an LTE network;
the core network device is an EPC device,
the first processing node is an MME;
the second processing node is an SGW;
the management node is an HSS;
The gateway device according to claim 1. a plurality of the core network devices,
The communication unit relays the control data and the user data to the core network device, which differs for each non-3GPP terminal, via the interface.
The gateway device according to claim 1 or 2 . The communication unit communicates with a 3GPP terminal located in the 3GPP network,
The authentication unit authenticates a user of the 3GPP terminal in cooperation with the first processing node,
The communication unit relays the control data between the first processing node and the 3GPP terminal, and relays the user data between the second processing node and the 3GPP terminal.
The gateway device according to any one of claims 1 to 3 . A communication control method in a gateway device that accommodates a non-3GPP terminal arranged in a non-3GPP network in a 3GPP network and communicates with a core network device having the non-3GPP terminal and a plurality of nodes,
authenticating a user of the non-3GPP terminal in cooperation with a first processing node that is a node that processes control data and that cooperates with a management node that manages subscriber information;
relaying the control data between the first processing node and the non-3GPP terminal and relaying the user data between a second processing node processing user data and the non-3GPP terminal;
has
The step of relaying includes a step of communicating with the core network device via an interface for communication connection between a base station conforming to the 3GPP communication scheme and the first processing node,
communicating with the core network device via the interface,
communicating with the core network device via an interface included in the interface in which a message related to handover between the core network device and the gateway device is omitted;
Communication control method.

Images