WO2016006622A1

WO2016006622A1 - Terminal device, mme, pgw, communication system and communication control method

Info

Publication number: WO2016006622A1
Application number: PCT/JP2015/069592
Authority: WO
Inventors: 陽子増田; 真史新本
Original assignee: シャープ株式会社
Priority date: 2014-07-09
Filing date: 2015-07-08
Publication date: 2016-01-14
Also published as: JP2017152754A

Abstract

In order to clarify the method by which a UE acquires a globally reroutable IP address, in a PDN connectivity request, the UE requests acquisition of a globally reroutable IP address, and a globally reroutable IP address is acquired through the PDN connectivity accept.

Description

Terminal device, MME, PGW, communication system, and communication control method

The present invention relates to a terminal device, an MME, a PGW, a communication system, a communication control method, and the like.

In recent 3GPP (The 3rd Generation Partnership Project) that conducts standardization activities for mobile communication systems, the specification of the EPS (Evolved Packet System) described in Non-Patent Document 1 is realized. In 3GPP, not only LTE (LongＥＰTerm Evolution) but also a wireless LAN is considered as an access system connected to EPS.

Furthermore, ProSe (Proximity based Service) described in Non-Patent Document 2 is being studied in the 3GPP EPS specification. ProSe has a function (discovery) for detecting neighboring communication terminals between UEs (User Equipment) as communication terminals and a function (direct communication) for establishing direct communication between UEs without using a core network or a base station. It aims to realize the services it provides.

In the specification of 3GPP EPS, eICBD (Enhancements for infrastructure data Communication Between Devices) described in Non-Patent Document 3 is also being studied. In eICBD, it is possible to solve the problems that arise in the current communication mode due to the diversification of applications accompanying the spread of P2P (Peer to Peer) and the like, and the diversification of terminals such as various M2M (Machine to Machine) terminals It is aimed. In eICBD, as one of the communication methods between terminals, it is considered to permit the use of ProSe for direct communication.

In eICBD, since a P2P application communicates between terminals connected to different mobile operator networks, it is considered as one use case to use globally routed IP address (hereinafter, GRIP address). ing. The GRIP address is requested to be assigned to each mobile communication carrier by each UE that intends to start communication by the P2P application.

EICBD is studying requirements for communication services using GRIP addresses. Non-Patent Document 3 describes that each mobile communication carrier assigns a GRIP address to a UE registered in an application server. However, the method for obtaining the GRIP address of the UE is not clear.

The present invention has been made in view of such circumstances, and an object of the present invention is to provide a suitable means for obtaining a GRIP address so as not to affect the current procedure as much as possible.

The terminal device of the present invention includes a transmission unit that transmits a PDN connectivity request message to a MME (Mobility Management Entity), and at least an APN, a PDN type, and a globally routable IP in a PDN connectivity request message. First identification information indicating that an address allocation is requested, and a reception unit that receives a PDN connectivity accept message from the base station apparatus as a response to the PDN connectivity request message, and a PDN connectivity accept message Includes at least an APN, a PDN type, and a globally routable IP address, and based on the transmission of the first identification information, the global router And having a storage unit that acquires Le IP address, the.

The MME (Mobility Management Entity) of the present invention includes at least an APN, a PDN type, and a globally routable IP in a receiving unit that receives a PDN (Packet Data Network) connectivity request message from a terminal device, and a PDN connectivity request message. A PDN connectivity accept message is transmitted to the base station apparatus as a response to the PDN connectivity request message, and the PDN connectivity accept message includes at least A PDN connectivity network including an APN, a PDN type, and a globally routable IP address, based on receiving the first identification information. And having a transmitter which transmits including Gurobari routable IP address to the concept message.

The PGW (PDN Gateway) of the present invention includes a receiving unit that receives a session establishment request message from an SGW (Serving Gateway) based on the transmission of a terminal device PDN (Packet Data Network) connectivity request message, and a session establishment request message. Includes at least an APN, a PDN type, and first identification information indicating a request for assignment of a globally routable IP address, and based on reception of the first identification information, a globally routable IP address And a transmission unit that transmits a session establishment response message to the SGW as a response to the session establishment request message. The session establishment response message message includes at least an APN and And the PDN type, include Gurobari routable IP address, characterized in that.

The terminal apparatus of the present invention transmits a PDN (Packet Data Network) connectivity request message to the MME (Mobility Management Entity) and sends a first request message requesting to change the IP address to a globally routable IP address. Alternatively, the transmission unit to be transmitted to the base station apparatus and the PDN connectivity request message include at least an APN and a PDN type, and a PDN connectivity accept message is received from the base station apparatus as a response to the PDN connectivity request message. The PDN connectivity accept message includes at least an APN, a PDN type, and a globally routable IP address, and includes a first request message. A receiver for receiving a response message to chromatography di, based on the reception of the response message, and having a storage unit for changing the IP address to Gurobari routable IP address.

The communication control method for a terminal device according to the present invention includes a step of transmitting a PDN connectivity request message to an MME (Mobility Management Entity), and at least an APN, a PDN type, and a global router in the PDN connectivity request message. Receiving a PDN connectivity accept message from the base station device as a response to the PDN connectivity request message, and PDN connectivity accept The message includes at least an APN, a PDN type, and a globally routable IP address, and based on the transmission of the first identification information, Wherein the inclusion of acquiring low Routable IP addresses.

The MME (Mobility Management Entity) communication control method of the present invention includes a step of receiving a PDN (Packet Data Network) connectivity request message from a terminal device, and at least an APN, a PDN type, and a global router in the PDN connectivity request message. Transmitting a PDN connectivity accept message to the base station apparatus as a response to the PDN connectivity request message, and PDN connectivity accept The message includes at least an APN, a PDN type, and a globally routable IP address. Wherein the inclusion of the step of transmitting including the connection Kuti Byi tee Gurobari routable IP address to accept message.

According to the PGW (PDN Gateway) communication control method of the present invention, a session establishment request message is received from an SGW (Serving Gateway) based on transmission of a PDN (Packet Data Network) connectivity request message of a terminal device, and a session establishment The request message includes at least an APN, a PDN type, and first identification information indicating that a globally routable IP address assignment request is requested. Based on the reception of the first identification information, the globally routable A session establishment response message including at least an APN, a PDN type, and a globally routable IP address as a response to the session establishment request message. The characterized to include the steps of transmitting to the SGW.

The communication control method of the terminal device of the present invention includes a step of transmitting a PDN (Packet Data Network) connectivity request message including at least an APN and a PDN type in MME (Mobility Management Entity), and a response to the PDN connectivity request message. Receiving a PDN connectivity accept message including at least an APN, a PDN type, and a globally routable IP address from the base station apparatus, and requesting to change the IP address to a globally routable IP address. 1 request message to the MME or the base station apparatus, receiving a response message to the first request message, Based on the reception of the message, and wherein the inclusion of the step of changing the IP address to Gurobari routable IP address.

The communication system of the present invention is a communication system that includes at least a terminal device, a base station device, an MME (Mobility Management Entity), an SGW (Serving Gateway), and a PGW (PDN Gateway). A PDN (Packet Data Network) connectivity request message is transmitted. The PDN connectivity request message includes at least an APN, a PDN type, and first identification information indicating that a globally routable IP address is requested to be allocated. , The MME receives the PDN connectivity request message from the terminal device, and based on the reception of the PDN connectivity request message, the MME sends a session establishment request message to S And the session establishment request message includes at least an APN, a PDN type, and first identification information, and the SGW receives the session establishment request message from the MME and is based on reception of the session establishment request message. The session establishment request message is transmitted to the PGW, and the session establishment request message includes at least the APN, the PDN type, and the first identification information. The PGW receives the session establishment request message from the SGW, On the basis of the reception of the identification information 1, a globally routable IP address is assigned to the terminal device, and a session establishment response message is transmitted to the SGW as a response to the session establishment request message. , PDN type, The SGW receives a session establishment response message from the PGW, and, based on the reception of the session establishment response message, the SGW sends a session establishment response message as a response to the session establishment request message. A response message is transmitted to the MME, and the session establishment response message is transmitted including at least the APN, the PDN type, and the globally routable IP address. The MME receives the session establishment response message from the SGW, and establishes the session. Based on the reception of the response message, a PDN connectivity accept message is transmitted to the base station as a response to the PDN connectivity request message transmitted by the MME, and the PDN connectivity accept message is transmitted. Is transmitted including at least the APN, the PDN type, and the globally routable IP address, and the base station apparatus receives the PDN connectivity accept message from the MME, and based on the reception of the session establishment response message, A PDN connectivity accept message is transmitted to the terminal device. The PDN connectivity accept message includes at least an APN, a PDN type, and a globally routable IP address, and the terminal device transmits the PDN connectivity accept message. An accept message is received from a base station apparatus, and a globally routable IP address is acquired based on transmission of identification information.

According to the present invention, the conventional PDN connectivity procedure is extended, and the UE can acquire a globally routable IP address from the mobile communication carrier.

It is a figure for demonstrating the outline of a mobile communication system. It is a figure for demonstrating the structure of an IP mobile communication network, etc. It is a figure for demonstrating the function structure of UE. It is a figure for demonstrating the function structure of an application server. It is a figure for demonstrating the function structure of MME. It is a figure for demonstrating the function structure of PGW. It is a figure for demonstrating the authentication procedure of an application server It is a figure for demonstrating the acquisition method of a GRIP address. It is a figure for demonstrating the communication using a GRIP address. It is a figure for demonstrating the MME reassignment procedure accompanying TAU. It is a figure for demonstrating the authentication procedure of a ProSe server It is a figure for demonstrating the announcement procedure of ProSe It is a figure for demonstrating the change procedure of the IP address using a service request It is a figure for demonstrating the IP address change procedure using the bearer change procedure started from UE

Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings. In the present embodiment, as an example, an embodiment of a mobile communication system or the like when the present invention is applied will be described.

[1. First Embodiment]
Hereinafter, a wireless communication technique according to an embodiment of the present invention will be described in detail with reference to the drawings. In the present embodiment, the GRIP address is not limited to a globally unique IP address, and may be an IP address that can be routed globally. For example, the GRIP address may be a private IP address. In this case, the GRIP address may be an IP address that is converted into a globally unique IP address by using a NAT (Network Access Transportation) function by the core network.

Furthermore, the GRIP address is an IP address assigned to a terminal device by a certain mobile communication carrier network when a mobile communication carrier network such as a different core network is configured by a plurality of mobile communication carriers, The IP address may be an IP address that can be routed from the mobile carrier network assigned the IP address to another mobile carrier network. Thus, the GRIP address is an IP address acquired by a terminal device connected to a certain mobile communication carrier network, and the terminal device communicates with a terminal device connected to another mobile communication carrier network. It may be an IP address used at the time.

Alternatively, the GRIP address may be an IP address used for communication between terminals connected to a single mobile carrier network.

In this embodiment, the terminal device may acquire a conventional IP address that is not a GRIP address based on a conventional method. The conventional IP address may be an IP address that does not execute a special process for the GRIP address by a device included in the IP mobile network including the terminal device described through the present embodiment. The conventional IP address may be a local routability IP address that can be routed only within an IP mobile communication network operated by a single operator. In this embodiment, such an IP address is expressed as a conventional IP address.

In the present embodiment, the terminal device may have both the GRIP address and the conventional IP address at the same time. Further, when acquiring the IP address, the terminal device explicitly requests whether the IP address assignment is requested from the core network by requesting the GRIP address assignment or the conventional IP address assignment. An address may be acquired. Furthermore, when actually transmitting / receiving user data by executing an application or the like, the terminal device may select and use either the GRIP or the conventional IP address.

[1.1. Overview of communication system]
FIG. 1 is a diagram for explaining the outline of a mobile communication system in the present embodiment. As shown in the figure, the mobile communication system 1 includes a UE (terminal device) 10, an IP mobile communication network 5, and an application server 20.

The IP mobile communication network 5 may be, for example, a network that includes a core network or a broadband network. The broadband network is a wired access network that realizes broadband communication, and is constructed by, for example, ADSL (Asymmetric Digital Subscriber Linear) or an optical fiber. However, the present invention is not limited to this, and the broadband network may be a wireless access network such as WiMAX (Worldwide Interoperability for Microwave Access).

The UE 10 is a terminal device connected to LTE, WLAN, or WiMAX, and is connected to the IP mobile communication network 5 by being mounted with a 3GPP LTE communication interface, a WLAN communication interface, a WiMAX communication interface, or the like. It is possible.

The application server 20 is a server device that manages a specific application, and has a management function such as authentication of a UE that uses the application. For example, the application server 20 may be a ProSe server. The ProSe server is a server device having a management function such as UE authentication for a service that provides a function related to ProSe such as detection of a neighboring terminal.

Next, a configuration example of the IP mobile communication network 5 will be described with reference to FIG. As shown in FIG. 2, the IP mobile communication network 5 is connected to the UE 10 and the PDN 9. The PDN 9 is a network that transmits and receives data to and from the UE 10 in packets, and is a service network that provides specific services such as services related to the Internet, IMS, and ProSe, for example.

The IP mobile communication network 5 may be a network operated by a communication carrier with which the UE 10 has a contract. Furthermore, the IP mobile communication network 5 may be the Home PLMN of the UE 10. In addition to the UE 10, a plurality of UEs can be connected to the IP mobile communication network 5.

The IP mobile communication network 5 may include a core network 7 and each radio access network (LTE AN80, WLAN ANb75, WLAN ANa70). Furthermore, the core network 7 and each radio access network (LTE AN80, WLAN ANb75, WLAN ANa70) may be connected.

The core network 7 includes an HSS (Home Subscriber Server) 50, an AAA (Authentication, Authorization, Accounting) 55, a PCRF (Policy and Charging Rules Rules) 60, a PGW (Packet Data Network Gateway) 30, an ePDG (enhanced Packet Packet Data Gateway). ) 65, SGW (Serving Gateway) 35, and MME (Mobile Management Entity) 40.

The application server 20 described with reference to FIG. 1 may be configured to be included in the PDN 9, or may be configured to be included in the IP mobile communication network 5 independently of the PDN 9, or may be configured as a core network. 7 may be included.

The radio access network may be composed of a plurality of different access networks. Each access network is connected to the core network 7. Furthermore, the UE 10 can wirelessly connect to the radio access network.

In the radio access network, an LTE access network (LTE AN80) that can be connected by an LTE access system and an access network (WLAN ANb75, WLAN ANa70) that can be connected by a WLAN access system can be configured.

Further, the access network connectable by the WLAN access system includes a WLAN access network b (WLAN ANb75) for connecting the ePDG 65 as a connection device to the core network 7, and a WLAN access network a (WLAN for connecting the PGW 30, the PCRF 60, and the AAA 55). ANa75) can be configured.

In addition, since each apparatus is comprised similarly to the conventional apparatus in the mobile communication system using EPS, detailed description is abbreviate | omitted. Hereinafter, each device will be briefly described.

The PGW 30 is connected to the PDN 9, the SGW 35, the ePDG 65, the WLAN ANa 70, the PCRF 60 and the AAA 55, and performs user data delivery as a gateway device of the PDN 9 and the core network 7.

The SGW 35 is connected to the PGW 30, the MME 40, and the LTE AN 80, and performs user data delivery as a gateway device between the core network 7 and the LTE AN 80.

The MME 40 is connected to the SGW 35, the LTE AN 80, and the HSS 50, and is an access control device that performs location information management and access control of the UE 10 via the LTE AN 80. The core network 7 may include a plurality of location management devices. For example, an MME different from the MME 40 may be included as a location management device different from the MME 40. Here, an MME different from the MME 40 is referred to as MME-A90. The MME-A 90 may be connected to the SGW 35, the LTE AN 80, and the HSS 50 in the same manner as the MME 40. Further, the MME-A 90 may be connected to a gateway different from the SGW 35 configured in the core network 7 instead of the SGW 35 to which the MME 40 is connected.

Further, the MME-A 90 and the MME 40 may be connected. Thereby, MME-A90 and MME40 may perform transmission / reception of the context of UE10.

The HSS 50 is connected to the MME 40 and the AAA 55, and is a management node that manages subscriber information. The subscriber information of the HSS 50 is referred to at the time of access control of the MME 40, for example.

AAA 55 is connected to PGW 30, HSS 50, PCRF 60, and WLAN ANa 70, and performs access control for UE 10 connected via WLAN ANa 70.

PCRF 60 is connected to PGW 30, WLAN ANa 75, AAA 55, and PDN 9, and performs QoS management for data delivery. For example, QoS management of the communication path between the UE 10 and the PDN 9 is performed.

The ePDG 65 is connected to the PGW 30 and the WLAN ANb 75, and delivers user data as a gateway device between the core network 7 and the WLAN ANb 75.

Further, as shown in FIG. 2B, each radio access network includes a device (for example, a base station device or an access point device) to which the UE 10 is actually connected. As a device used for connection, a device adapted to a radio access network can be considered.

In this embodiment, the LTE AN 80 includes the eNB 45. The eNB 45 is a radio base station to which the UE 10 is connected in the LTE access system, and the LTE AN 80 may be configured to include one or a plurality of radio base stations.

The WLAN ANa 70 includes a WLAN APa 72 and a GW (Gateway) 74. The WLAN APa 72 is a radio base station to which the UE 10 is connected with a WLAN access system that is reliable to the operator operating the core network 7, and the WLAN ANa 70 includes one or more radio base stations. Good. The GW 74 is a gateway device for the core network 7 and the WLAN ANa 70. Further, the WLAN APa 72 and the GW 74 may be configured by a single device.

Even if the operator operating the core network 7 and the operator operating the WLAN ANa 70 are different, it is possible to realize such a configuration by contracts and rules between the operators.

In addition, WLAN ANb75 is configured to include WLAN APb76. The WLAN APb 76 is a radio base station to which the UE 10 is connected in the WLAN access system when a trust relationship is not established with the operator operating the core network 7, and the WLAN ANb 75 includes one or more radio base stations. It may be configured to be included.

In this way, the WLAN ANb 75 is connected to the core network 7 using the ePDG 65, which is a device included in the core network 7, as a gateway. The ePDG 65 has a security function for ensuring safety.

In this specification, the fact that the UE 10 is connected to each radio access network means that the UE 10 is connected to a base station apparatus, an access point, etc. included in each radio access network. Also via a base station device or access point.

[1.2. Device configuration]
Next, each device configuration will be briefly described with reference to the drawings.

[1.2.1. Configuration of UE]
Fig.3 (a) shows the structure of UE10 in this embodiment. In the UE 10, an LTE interface unit 110 and a storage unit 140 are connected to the control unit 100 via a bus.

The control unit 100 is a functional unit for controlling the UE 10. The control unit 100 implements various processes by reading and executing various programs stored in the storage unit 140.

The LTE interface unit 110 is a functional unit for the UE 10 to connect to the LTE base station and connect to the IP access network. An external antenna 112 is connected to the LTE interface unit 110.

The storage unit 140 stores permission information 144, GRIP address information 146, and IP address information 148.

The permission information 144 may be permission information notified from the application server 20 as shown in FIG. Further, the permission information may be information indicating that the use of a specific application is permitted. Here, the specific application may be, for example, an application that performs communication using a GRIP address or an application that performs communication in a P2P communication mode. The permission information may be permission information associated with an application group identified for each application attribute, such as an application that performs communication using a GRIP address or an application that performs communication according to a P2P communication mode. .

Thus, the UE 10 may store application information and permission information in association with each other.

Furthermore, the UE 10 may store the permission information in association with the APN (Access Point Name). For example, as illustrated in FIG. 3B, the permission information 144 may store a plurality of APNs for one UE. The APN is identification information that can identify a communication service for the UE 10 and a service network to which the UE 10 is connected to the core network. In the example illustrated in FIG. 3B, the APN 1 is a communication service in which the UE 10 uses a GRIP address, or GRIP. Identification information corresponding to a service network that provides a communication service using an address, and APN2 uses a conventional IP address that is not a GRIP address, or a conventional IP address that is not a GRIP address. It indicates that the identification information corresponds to a service network that provides a communication service.

The GRIP address information 146 can store an APN, a GRIP address, and application identification information. An example of the GRIP address information 146 is shown in FIG. As shown in FIG. 3C, the UE 10 associates the GRIP address information 146 with the APN information of the UE, the GRIP address, and application identification information for identifying an application that can communicate using the GRIP address. You may remember. The UE 10 may perform communication of a specific application using the associated GRIP address from the GRIP address information 146.

The IP address information 148 stores a conventional IP address that is not a GRIP address. FIG. 3D shows an example of the IP address information 148. Note that the UE 10 may store the IP address, the APN, the IP address, and the application identification information in association with each other.

The UE 10 can execute communication using a conventional IP address in addition to communication using a GRIP address by storing the GRIP and the conventional IP address. When the UE 10 stores the GRIP address information 146 and the IP address information 148 at the same time, the UE 10 selects and uses the corresponding IP address based on the application identification information or the APN at the time of application communication. May be. As a specific usage method, the UE 10 may use the selected IP address as the source IP address in the transmission of user data. More specifically, when the application identification information used for the service started by the UE 10 is App ID A, the application data of the App ID A is transmitted, and the UE 10 transmits based on the correspondence shown in FIG. A GRIP address may be selected as the source IP address of the IP packet to be transmitted.

[1.2.2. Application server configuration]
Next, the configuration of the application server 20 will be described with reference to FIG. As shown in FIG. 4A, in the application server 20, an IP mobile communication network interface unit 210 and a storage unit 240 are connected to the control unit 200 via a bus.

The control unit 200 is a functional unit for controlling the application server 20. The control unit 200 implements various processes by reading and executing various programs stored in the storage unit 240.

Application server 20 stores permission information 244 and GRIP address information 246 in storage unit 240.

As shown in FIG. 4B, the permission information 244 can store application usage permission information for registered UEs. In FIG. 4B, the UE 10 is permitted to use an application managed by the application server 20.

As shown in FIG. 4C, the GRIP address information 246 can store a GRIP address notified from the UE 10 that has authenticated use of the application.

Note that the permission information 244 may be information indicating permission to use a specific application. Here, the specific application may be, for example, an application that performs communication using a GRIP address or an application that performs communication in a P2P communication mode. Further, the permission information 244 may be permission information associated with an application group identified for each application attribute, such as an application that performs communication using a GRIP address or an application that performs communication according to a P2P communication mode. good.

As described above, the application server 20 may store the application information and the permission information in association with each terminal device.

[1.2.3. Configuration of MME]
Next, the configuration of the MME 40 will be described. The device configuration of the MME 40 is shown in FIG. As shown in FIG. 5A, in the MME 40, an IP mobile communication network interface unit 320 and a storage unit 340 are connected to the control unit 300 via a bus.

The control unit 300 is a functional unit for controlling the MME 40. The control unit 300 implements various processes by reading and executing various programs stored in the storage unit 340.

Permission information 342 is stored in the storage unit 340. As shown in FIG. 5B, the permission information 342 can store the permission information for each UE managed by the MME 40. Further, identification information of an application server registered by the UE may be registered. Or MME40 may memorize | store the permission information 342 of communication for which UE used the GRIP address for every APN.

Further, the HSS 50 may manage the permission information 342 of the UE instead of the MME 40. In this case, the HSS 50 may store the permission information 342 in association with the identifier of the UE, or may store registration information for each APN.

Note that the permission information 342 may be information indicating permission to use a specific application. Here, the specific application may be, for example, an application that performs communication using a GRIP address or an application that performs communication in a P2P communication mode. The permission information may be permission information associated with an application group identified for each application attribute, such as an application that performs communication using a GRIP address or an application that performs communication according to a P2P communication mode. .

Thus, the MME 40 may store the application information and the permission information in association with each terminal device.

Further, the MME 40 may store the permission information in association with the APN (Access Point Name). For example, in the permission information 342, a plurality of APNs may be stored for one UE. APN is a communication service for UE 10 and identification information corresponding to a service network to which UE 10 is connected via a core network. APN 1 is a service for UE 10 to provide a communication service using a GRIP address or a communication service using a GRIP address. This is identification information corresponding to the network, and the APN 2 corresponds to a service network in which the UE 10 provides a communication service using a conventional IP address that is not a GRIP address or a communication service using a conventional IP address that is not a GRIP address. This indicates identification information.

[1.2.4. Configuration of PGW]
Next, the configuration of the PGW 30 will be described. The apparatus configuration of the PGW 30 is shown in FIG. As shown in FIG. 6A, in the PGW 30, an IP mobile communication network interface unit 420 and a storage unit 440 are connected to the control unit 400 via a bus.

The control unit 400 is a functional unit for controlling the PGW 30. The control unit 400 implements various processes by reading and executing various programs stored in the storage unit 440.

The storage unit 440 can store a GRIP address management table. As shown in FIG. 6B, the GRIP address management table can manage the GRIP address of each UE assigned by the PGW.

Note that the PGW 30 confirms the IP header of the IP packet including the user data received from the UE 10 and forwards it to the destination if the source IP address is a GRIP address. Otherwise, the packet is discarded or the packet Processing such as stopping the transfer may be executed.

[1.3. Explanation of processing]
Next, processing in which the UE acquires a GRIP address will be described. In the following, a procedure for authentication until the UE 10 searches for the application server 20, transmits an authentication request to the application server 20, and receives a response, and a procedure for acquiring a GRIP address by extending the PDN connectivity procedure will be described.

[1.3.1. Application server registration procedure]
A registration procedure from the UE 10 to the application server 20 will be described with reference to FIG.

First, the UE 10 executes an attach procedure and connects to the core network (S502). As a result, the UE 10 establishes a PDN connection with the PGW 30. The PDN connection is a communication path for transmitting / receiving data to / from the PDN 9. The attach procedure may be executed as an initial procedure such as when the UE 10 is powered on.

More specifically, the attach procedure starts when the UE 10 transmits an attach request to the MME 40. The attach request may be transmitted by including UE identification information such as APN or IMSI (International Mobile Subscriber Identity). The APN is not necessarily included in the attach request message, and may be notified from the UE 10 to the MME 40 by a control message in the attach procedure. The APN transmitted here may not be an APN associated with an application that performs communication using a GRIP address or a communication service that performs communication using a GRIP address. Alternatively, the APN may be an APN associated with permission information that prohibits assignment of a GRIP address. Therefore, the IP address acquired by the UE 10 by transmitting the APN in the attach procedure may be a conventional IP address instead of the GRIP address.

The MME 40 confirms the permission information based on the received UE identification information or APN. That is, as shown in FIG. 5B, when the permission information corresponds to the identification information of the UE, the identification information of the UE is used for confirmation of the permission information. If the permission information of UE10 can be confirmed, MME40 will select PGW30 based on received APN, and will determine the end point of the PDN connection with respect to UE10. Furthermore, establishment of a PDN connection and connection to a core network are permitted, and an attach permission message serving as a response to the attach request message is transmitted to the UE 10. The attach permission message may be transmitted directly from the MME 40 to the UE 10 or may be transmitted via the eNB 45 included in the LTE AN 80.

Further, the MME 40 may notify that the UE 10 is permitted to connect to the core network by transmitting an attach permission message. Further, the MME 40 may notify that the PDN connection has been established by transmitting an attach permission message. Further, the attach permission message may be transmitted including the IP address associated with the PDN connection or the APN. Further, identification information for identifying a communication flow or application such as a TFT (Traffic Flow Template) corresponding to the IP address may be included in the message and transmitted.

Through the above procedure, the UE 10 can acquire the conventional IP address from the core network and execute communication using the conventional IP address.
UE10 may perform the registration procedure to an application server, in order to acquire GRIP, after acquiring a conventional IP address.

The following describes the registration procedure for the application server. First, the UE 10 searches for the application server 20 and secures secure communication with the searched application server 20 (S504). The application server 20 may be an application server corresponding to an application with which the UE 10 communicates using a GRIP address. Further, in the registration procedure, the application server 20 may perform processing such as authentication for use of the application to the UE 10 and approval for acquisition of the GRIP of the UE 10.

The UE 10 searches for the application server 20 by, for example, pre-holding application server identification information such as FQDN (Fully Qualified Domain Name) of the application server, and the UE 10 based on the identification information. The application server 20 can be searched by transmitting control information for making an inquiry to a DNS (Domain Name System) server and acquiring the IP address of the application server together with a response to the control information. In addition, the search method of the application server 20 is not limited to this, You may search using other methods, such as UE10 memorize | stored previously.

Also, IPSec may be used as a method for establishing a secure communication path between the UE 10 and the application server 20. The communication path establishment method is not particularly limited to this, and it is sufficient that a secure communication path can be established between the UE 10 and the application server 20.

Next, the UE 10 transmits to the application server 20 an authentication request for using the application that the UE 10 communicates with using the GRIP address (S506). This request includes a request for assigning a GRIP address in addition to a registration request for using a specific application, as in the conventional request. That is, the UE 10 may request the application server 20 to authenticate use of a specific application that performs communication using the GRIP address and to assign a GRIP address by transmitting an authentication request message. This request may be an authentication request for the use of such a specific application when an application that performs communication using the GRIP address is determined in advance.

Specifically, the authentication request to the application server 20 may include the location information of the UE 10 and the identification information of the UE 10. The location information of the UE may include Cell ID of the LTE base station apparatus, TAI (Tracking Area ID), and GPS (Global Positioning System) information.

The application server 20 receives the authentication request from the UE 10 and transmits an authentication response to the UE 10 based on the reception (S508). The application server 20 may include authentication information indicating an authentication result in the authentication response. Further, the application server 20 may include information that can identify the application, such as a TFT and an APN, in the authentication response. Moreover, you may include both of these.

The UE 10 receives a control message indicating an authentication response as a response to the authentication request message. The UE 10 may acquire authentication information included in the control message.

Note that the application server 20 may manage user information and permission information in association with each other in advance, and may determine an authentication result for the UE 10 that transmits an authentication request based on such management information.

UE 10 receives an authentication response message as a response to the authentication request message from application server 20. Here, information included in the authentication response message may be stored. Further, the UE 10 may start a procedure for acquiring a GRIP address based on reception of a message indicating that the application server 20 has authenticated. As a specific GRIP address acquisition procedure, the UE 10 may start a PDN connectivity procedure including a request for a GRIP address (S510).

[1.3.2. GRIP address assignment with PDN connectivity procedure]
Details of the PDN connectivity procedure (S510) of FIG. 7 will be described with reference to FIG. The UE 10 transmits a PDN connectivity request to the MME 40 (S602). The PDN connectivity request includes at least an APN, a PDN type, and identification information indicating that a GRIP address is requested. Further, the authentication information for using the application received from the application server 20 may be included in the PDN connectivity request.

Here, the identification information indicating that the GRIP address is requested may be an APN. Note that the APN transmitted here may be an APN associated with an application that performs communication using the GRIP address or a communication service that performs communication using the GRIP address. The UE 10 may request assignment of a GRIP address by performing a PDN connectivity procedure for transmitting such an APN. Further, when the UE 10 holds a plurality of APNs, such an APN may be selected and transmitted in a PDN connectivity request message in order to acquire a GRIP address. Alternatively, identification information indicating that a GRIP address is requested may be included in the PDN type. The conventional PDN type was able to identify an IPv4 address, an IPv6 address, or both, but in addition to these, the PDN type in this embodiment is an IPv4 address of a GRIP address, an IPv6 address of a GRIP address, and further a GRIP It may be information that identifies both addresses. When the UE 10 requests acquisition of a GRIP address, the UE 10 may request a GRIP address by transmitting a PDN connectivity request including a PDP type indicating the IPv6 address of the GRIP address.

Note that the present invention is not limited thereto, and a flag or the like may be used as identification information indicating that a GRIP address is requested.

The MME 40 receives the PDN connectivity request from the UE 10. The MME 40 may receive identification information indicating that an APN, a PDN type, and a GRIP address are requested, which are included in the PDN connectivity request. The MME 40 determines the SGW 35 and the PGW 30 based on the received APN included in the PDN connectivity request. Thereby, the gateway which is a relay apparatus in the communication path between UE10 and PDN9 is determined.

Next, the MME 40 transmits a session establishment request to the SGW 35 (S604). The MME 40 may transmit the session establishment request including the APN, the PDN type, information for identifying the PGW 30, and identification information indicating that a GRIP address is requested. Further, APN may be used as identification information indicating that a GRIP address is requested.

The MME 40 manages user information and permission information indicating whether to assign a GRIP address to the user in advance, performs authentication of GRIP address assignment based on the management information, and based on the authentication result. A session establishment request may be transmitted. Specifically, when the UE 10 is permitted to assign a GRIP address, a session establishment request is transmitted to the SGW 35. In addition, when the allocation is not permitted, the MME 40 transmits a response to the PDN connectivity request to the UE 10 and notifies that the GRIP address is not allocated or the establishment of the PDN connection is not permitted. Good. Moreover, MME40 may transmit a response message to UE10 via eNB45.

The permission information indicating whether the user needs to assign a GRIP address includes the UE 10a indicating a connection using an APN associated with an application that performs communication using the GRIP address or a communication service that performs communication using the GRIP address. Whether or not to allow applications that communicate using the GRIP address and communication services that communicate using the GRIP address, managed in association with the user or the UE 10a. May be subscriber information.

Note that the MME 40 may request establishment of a PDN connection between the UE 10 and the PGW 30 by transmitting a session establishment request, or may request a GRIP address.

The SGW 35 receives a session establishment request from the MME. The SGW 35 may receive the APN included in the session establishment request, the PDN type, the PGW identification information, and the identification information indicating that the GRIP address is requested.

Furthermore, the SGW 35 transmits a session establishment request to the PGW 30 (S606). The session establishment request transmitted by the SGW 35 may include at least APN, PDN type, PGW identification information, and identification information indicating that a GRIP address is requested. Accordingly, the SGW 35 may request the PGW 30 to establish a PDN connection between the UE 10 and the PGW 30, or may request the UE 10 to assign a GRIP address.

The PGW 30 receives a session establishment request from the SGW 35. The PGW 30 may receive identification information indicating that an APN, a PDN type, and a GRIP address are included in the session establishment request.

The PGW 30 assigns a GRIP address to the UE 10 based on the reception of the session establishment request (S608).

Note that the PGW 30 may assign a GRIP address based on information indicating that a GRIP address is requested. Specifically, when the information indicating that the GRIP address is requested is received, the PGW 30 assigns the GRIP address, and when the information indicating that the GRIP address is requested is not received, the conventional IP address May be assigned.

When the information indicating that a GRIP address is requested is an APN, the received APN is an APN associated with an application that performs communication using the GRIP address or a communication service that performs communication using the GRIP address. Alternatively, the PGW 30 may assign a GRIP address to the UE 10, and when receiving an APN associated with another application or communication service, the PGW 30 may assign a conventional IP address.

The PGW 30 transmits a session establishment response message to the SGW 35 as a response message to the session establishment request (S610). The PGW 30 may transmit the session establishment response message including the APN, the PDN type, and the IP address assigned to the UE. Further, a timer indicating that the use of the IP address is valid may be included in the session establishment response message.

The SGW 35 receives the session establishment response message from the PGW 30 and acquires the GRIP address assigned to the UE 10. Next, the SGW 35 transmits a session establishment response message to the MME 40 as a response to the session establishment request received from the MME 40 (S612). The session establishment response message includes the APN, PDN type, and IP address. The MME 40 may receive the APN included in the session establishment response, the PDN type, and the IP address assigned to the UE. Further, a timer indicating that the use of the IP address is valid may be included in the session establishment response message.

Next, the MME 40 transmits a PDN connectivity accept to the eNB 45 as a response message of the PDN connection request transmitted by the UE 10 (S614). The PDN connectivity accept may be transmitted including at least the APN, the PDN type, and the IP address assigned to the UE 10. Here, the MME 40 may transmit the IP address including the GRIP address.

Furthermore, the MME 40 may include a timer indicating that the use of the GRIP address is valid in the PDN connectivity accept in the message.

The eNB 45 may receive the PDN connectivity accept and receive the UE identification information included in the PDN connectivity accept, the GRIP address assigned to the UE 10, and the information identifying the APN to be connected.

The eNB 45 may allocate radio resources established between the UE 10 and the eNB 45 based on this reception.

Furthermore, the eNB 45 may transmit a PDN connectivity accept including the RRC connection reconfiguration message to the UE 10 (S616). The PDN connectivity accept may include UE identification information, a GRIP address assigned to the UE, and information identifying the APN to be connected. Furthermore, information including resources and a timer indicating the validity period of the GRIP address may be transmitted.

UE 10 receives the PDN connectivity accept and RRC connection reset message. The UE 10 may receive the UE identification information, the GRIP address assigned to the UE, the information identifying the APN to be connected, and the PDN type included in the PDN connectivity accept. The UE 10 acquires a GRIP address based on the reception of the PDN connectivity accept message.

Furthermore, the UE 10 may detect that the connectivity to the APN has been established by receiving the PDN connectivity accept and the RRC reconnection setup message. Further, the UE 10 may detect that a communication path for performing communication corresponding to the APN has been established. Moreover, UE10 may acquire the GRIP address used for globally routable communication corresponding to APN.

The UE 10 may establish a PDN connection with the PGW based on the reception of the PDN connectivity accept message.

Next, the UE 10 transmits an RRC connection reconfiguration completion message to the eNB 45 (S618). Further, the direct transfer message is transmitted to the eNB 45 (S622).

The eNB 45 transmits an initial context setting response message to the MME 40 upon reception of the RRC connection reconfiguration completion message (S620). Moreover, eNB45 transmits an attachment completion message to MME40 with reception of a direct transfer message (S640).

As described above, the UE 10 can establish a PDN connection with the PGW 30. The UE 10 may perform communication of an application managed by the application server 20 using the established PDN connection.

Next, the UE 10 associates the GRIP address received from the eNB 45 with the application identification information (S626). Here, the application identification information is identification information for identifying an application that performs communication using the GRIP address. The specific application identification information may be APN. Further, the APN stored here may be an APN associated with an application that performs communication using a GRIP address or a communication service that performs communication using a GRIP address. Alternatively, the application identification information may be a TFT that identifies an application flow. Alternatively, both APN and TFT may be stored as application identification information. Thereby, when performing communication of an application, the UE 10 selects a corresponding GRIP address based on the application identification information, and transmits / receives application data identified by the application identification information using the selected GRIP address. it can.

As described above, the UE 10 can perform communication of the application identified by the application identification information by using the PDN connection established with the PGW 30.

[1.3.3. Example of communication between terminals using a GRIP address]
Next, a service example of communication between terminals using a GRIP address is shown. Here, the application identified by the application identification information is an application that realizes communication between devices such as P2P.

FIG. 9 shows an overall view of a system for explaining an example of communication between terminals using a GRIP address. The communication system 2 shown in FIG. 9 includes a UE 10a, a UE 10b, an IP mobile communication network 5, and an application server 20.

In FIG. 9, it is assumed that the mobile communication carriers with which the UE 10a and the UE 10b make a contract are the same, but they are connected to the same IP mobile communication network 5, but they may have contracts with different mobile communication carriers. That is, the UE 10a and the UE 10b may be connected to different IP mobile communication networks. At that time, IP mobile communication networks of different communication carriers may be connected to each other. More specifically, IP mobile communication network verbs may be connected by connecting PGWs configured in respective IP networks.

Note that the GRIP address may be an IP address permitted to deliver a packet from an IP mobile communication network operated by a certain mobile communication carrier to an IP mobile communication network operated by another mobile communication carrier. In other words, when the source address of the packet received from the UE 10a is a GRIP address, the PGW transmits the packet to the PGW configured in the IP mobile communication network operated by a different mobile communication carrier, and receives the packet received from the UE 10a. If the source address is a conventional IP address and not a GRIP address, the packet may not be transmitted and a process such as discarding the packet may be executed.

As described above, the GRIP address may be an address for delivery between different mobile communication carrier networks.

Alternatively, the UE 10a and the UE 10b may be an IP mobile communication network operated by a single communication carrier. Note that the GRIP address may be an IP address that permits delivery of a packet to be transmitted / received between terminals within the IP mobile communication network. In other words, since the source address of the packet received from the UE 10a is a GRIP address, the PGW may deliver the packet not to the PDN but to the communication partner terminal. Alternatively, when the IP mobile communication network is configured to include a plurality of PGWs, the PGW establishes a PDN connection when the packet is received from the UE 10a because the source address of the packet is a GRIP address. May be delivered to the PGW. If the source address of the packet received from the UE 10a is a conventional IP address or the like and is not a GRIP address, processing such as discarding the packet may be performed without transmitting the packet.

The configuration of the UE 10a and the UE 10b may be the same as the configuration shown in FIG. 3, and the configuration of the application server 20 is the same as the configuration shown in FIG. In addition, when an IP mobile communication network is configured by a plurality of mobile communication carriers, and when the IP mobile communication networks are interconnected, the application server is configured by a single device, and all IP mobile networks It may be connected to a communication network, or a plurality of IP mobile communication networks may be configured. Further, it is assumed that the UE 10a and the UE 10b have the same application ID.

First, each of the UE 10a and the UE 10b performs an authentication process for using an application from the application server 20. The application usage authentication process may be the process shown in FIG.

The UE 10a acquires the GRIP address from the PGW 30 in the process shown in FIG. 8 during the PDN connectivity procedure.

The UE 10a transmits a control message for notifying the acquired GRIP address to the application server 20. The UE 10a may transmit the control message including at least the GRIP address and the application ID. Further, a timer indicating the identification information of the UE and the validity period of the GRIP address may be included.

Application server 20 receives a control message for notifying the GRIP address from UE 10a. The application server 20 acquires the GRIP address of the UE 10a included in the GRIP address notification signal and stores it in the GRIP address information 246 of the storage unit 240. At this time, a timer indicating the validity period of the GRIP address may be stored in association with it. In this case, the timer count may be started, the time until the timer is consumed, the GRIP address may be stored, and the GRIP address may be deleted from the storage unit 240 when triggered by the timer being consumed.

Thereby, the application server 20 may store the UE 10a and the GRIP address in association with each other and manage that the UE 10a acquires the GRIP address.

Next, the UE 10b detects the GRIP address of the UE 10a stored in the application server 20, and requests the application server 20 for permission for the UE 10b to perform P2P communication with the UE 10a using the GRIP address of the UE 10a.

At this time, the application server 20 may determine permission of P2P communication using the GRIP address for the UE 10b. Or the application server 20 may request | require permission of P2P communication using UE10b and a GRIP address from UE10a based on the request | requirement from UE10b. At this time, the application server 20 may receive permission information for P2P communication using the GRIP address of the UE 10b from the UE 10a.

Application server 20 transmits permission information of the GRIP address to UE 10b.

The UE 10b receives permission information on the use of the GRIP address from the application server 20 to the UE 10a, and when permitted, starts the P2P communication with the UE 10a using the GRIP address.

When the UE 10b acquires a timer together with the GRIP address from the application server 20, the UE 10b starts counting the timer. When the timer is consumed, the UE 10b may stop communication with the UE 10a through the IP connection using the GRIP address. Good.

Alternatively, the PGW 30 may transmit a message notifying the UE 10a of a schedule to stop using the GRIP address. In this case, the UE 10a may stop using the GRIP address based on the received notification message and notify the application server 20 that the GRIP address cannot be used. Furthermore, the UE 10a may notify the UE 10b that is the communication partner that the use of the GRIP address is stopped. Alternatively, the application server 20 may notify the UE 10b that the use of the GRIP address is stopped.

Thus, the application server 20 may detect that the UE 10a has acquired the GRIP address. Furthermore, the application server 20 may manage a period during which the UE 10a can perform communication using the GRIP address.

[1.3.4. Tracking area update procedure]
Next, a tracking area update procedure accompanying the movement of the UE 10 will be described. In the following, when a UE that is permitted to use an application using a GRIP address changes an MME that manages location information of the UE 10 by a tracking area update procedure accompanying movement, permission information regarding the use of the GRIP address of the UE 10 is displayed. A method for maintaining the permission state regarding the use of the GRIP address of the UE by transferring between the MMEs will be described.

In the core network 7, a plurality of location management devices may be configured separately from the MME 40. For example, the MME 40 and the MME-A 90 may be configured in the core network 7. The MME-A 90 is different from the MME 40 only in the management of the tracking area, and the other configuration is the same as the MME 40. Therefore, the description of the configuration of the MME-A 90 is omitted.

Here, the MME 40 establishes connectivity with a plurality of base station apparatuses including the eNB 45, and configures an area called a tracking area. For example, the MME 40 can manage a group of base stations configured in an area close to a physical position, and configure such an area as a tracking area. In addition, the base station group associated with the tracking area may be configured by selecting and configuring a base station that the communication carrier wants to manage and distinguish in operation regardless of whether the location is physically close or not. it can. That is, the MME 40 can manage a plurality of base stations in association with the tracking area and configure the tracking area.

When the UE 10 in the idle mode executes the tracking area update procedure, the UE 10 may connect to different base stations before and after executing the tracking area update procedure due to movement of the UE 10. Furthermore, the location management device that manages each base station may be different. For example, the UE 10 may move from the base station device managed by the MME 40 to the vicinity of the base station device managed by the MME-A 90 and execute the tracking area update procedure.

In the following, the tracking area update procedure for moving to a tracking area of a different location management device as described above will be described. The tracking area update procedure is a procedure in which the MME-A 90 detects that the UE 10 has moved from the base station managed by the MME 40 to the base station managed by the MME-A 90. For the UE 10, it is a procedure for moving from the tracking area managed by the MME 40 to the tracking area managed by the MME-A 90. In the tracking area update procedure, relocation (MME-Relocation) of the location management device is executed.

Referring to FIG. 10, the tracking area update procedure including relocation of the position management device will be described. First, an initial state of the tracking area update procedure that is led and executed by the UE 10 will be described.

The UE 10 is connected to the core network 7 via the eNB 45 and establishes a PDN connection with the PGW 30 according to the procedure described above. Furthermore, it registers with the application server 20, acquires a GRIP address, and establishes IP connection using GRIP address with other UE. UE10 performs transmission / reception using such a communication path.

Furthermore, the UE 10 does not perform data transmission / reception using the PDN connection and the IP connection using the GRIP address for a predetermined time or more, the radio bearer between the UE 10 and the eNB 45 is released, and transitions to the idle mode.

Here, the initial state when performing the tracking area update procedure is not limited to this, and may be any state including a conventional state in which the UE 10 updates the tracking area. Further, the UE 10 may execute the tracking update procedure in the active mode regardless of whether or not the UE 10 is in the idle mode.

Also, the UE 10 may transmit a tracking area update request message to the eNB-A 95, which is a base station device different from the eNB 45, with movement. Hereinafter, the tracking update procedure will be described.

UE10 transmits a tracking area update request message to eNB-A95 (S1002). The message may include the identification information of the UE 10, the information for identifying the tracking area, the identification information of the location management device, the application identification information, the application user identification information, and the application permission information. Further, when the UE 10 is a UE that can use ProSe, the ProSe ID may be used as the identification information of the UE 10. Further, ProSe capability information may be included. The ProSe capability information may be capability information indicating that a ProSe service indicating that a direct communication path with a neighboring UE can be established can be enjoyed. Alternatively, it may be information indicating that a ProSe service is enjoyed and a direct communication path is established with a neighboring terminal. In addition, these pieces of information are included as different identification information in the message as different identification information. Also good.

Further, the information for identifying the location management device may include information for identifying the MME 40 that has been executing location management of the UE 10 so far. The information included in the message is not limited to this, and may be included together with the information included in the conventional tracking area update request message.

Application identification information is identification information for identifying an application used when the UE 10 establishes a communication path with another UE.

The application user identification information may be identification information for identifying the user or the UE 10 in the application identified by the application identification information.

Furthermore, the information for identifying the UE may be subscriber identification information such as IMSI, may be temporarily assigned identification information such as TEID, or may be application user identification information. Good.

The application permission information is identification information indicating whether or not the application server 20 is permitted to communicate using the application indicated by the application identification information, and the application identification information may be used.

The trigger for the UE 10 to transmit the tracking area update request message may determine the transmission timing based on a timer that is executed from the timing when the UE 10 in the idle mode transitions to the idle mode. In addition, the timer that determines the interval at which the tracking area update request message is transmitted may be held in advance by the UE 10 and the timer value may be determined.

ENB-A95 receives the tracking area update request message. The eNB-A 95 is a base station device that has connectivity with the MME-A 90, and may be a base station device that belongs to a tracking area managed by the MME-A 90. In other words, the eNB-A 95 is a base station device managed by the MME-A 90, and is a base station device belonging to the tracking area configured by the MME-A 90. Here, the eNB-A 95 may be a base station device different from the eNB 45 configured in the LTE AN80. Also, the tracking area to which the eNB-A 95 belongs and the tracking area to which the eNB 45 belongs may be different tracking areas. Further, each tracking area may be a tracking area managed by the MME 40, a tracking area to which the eNB-A 95 belongs is managed by the MME-A 90, a tracking area to which the eNB 45 belongs is managed by the MME 40, and so on. It may be managed by the position management device. Further, the configuration of the eNB-A 95 may be the same as the configuration of the eNB 45 already described, and thus detailed description thereof is omitted here.

Here, the UE 10 periodically executes the tracking area update procedure. In the previously executed tracking update procedure, the UE 10 transmits the tracking area update request message to the eNB 45 and executes the tracking area update procedure. Also good.

The eNB 45 is a base station device having connectivity with the MME 40, and may be a base station device belonging to a tracking area managed by the MME 40. In other words, the eNB 45 is a base station device managed by the MME 40, and is a base station device belonging to the tracking area formed by the MME 40.

That is, the UE 10 transmits a tracking area update request message to a base station apparatus different from the base station that previously transmitted the tracking area update request message by this tracking area update. Furthermore, the base station that has received the tracking area update request message is a base station that is managed by a location management device that is different from the previous base station.

The eNB-A 95 may transmit the tracking area update request to the MME-A 90 based on the reception of the tracking area update request from the UE 10 (S1004). The message may also include UE 10 identification information, tracking area identification information, location management apparatus identification information, base station identification information identifying eNB-A 95, application identification information, and application user identification information. Good.

Further, when the UE 10 is a UE that can use ProSe, the ProSe ID may be used as the identification information of the UE 10. Further, ProSe capability information may be included in the message.

The ProSe capability information may be capability information indicating that a ProSe service indicating that a direct communication path with a neighboring UE can be established can be enjoyed. Alternatively, it may be information indicating that a ProSe service is enjoyed and a direct communication path is established with a neighboring terminal. In addition, these pieces of information are included as different identification information in the message as different identification information. Also good.

Application identification information is identification information for identifying an application used in a service in which the UE 10 establishes a communication path with another UE.

The ProSe code may be information transmitted when announcing that the UE is located in the vicinity to other UEs located in the vicinity. Further, it may be information received when monitoring that another UE located in the vicinity is located in the vicinity. The ProSe code may be configured by combining application identification information, information for identifying a UE, and identification information for identifying an operator network such as a PLMN. Furthermore, the information for identifying the UE may be subscriber identification information such as IMSI, may be temporarily assigned identification information such as TEID, or may be application user identification information. Good.

The MME-A 90 may transmit a context request message to the MME 40 based on the reception of the tracking area update request message transmitted from the eNB-A 95 (S1006). The MME-A 90 may lead and execute the relocation (MME-Relocation) of the location management device by transmitting the context supply message.

The MME-A 90 may select a location management device that transmits a context request message based on information included in the received tracking area update request message. For example, the tracking area information and the position management device may be associated and managed in advance, the position management device associated with the received tracking area information may be selected, and the message may be determined to be transmitted to the MME 40. Further, the location management device may be selected from the information for identifying the location management device included in the tracking area update request message received from the eNB-A 95, and the context request message may be transmitted to the MME 40.

The context request message includes UE 10 identification information, tracking area identification information, location management apparatus identification information, eNB-A 95 identification base station identification information, application identification information, and application user identification information. May be.

Further, when the UE 10 is a UE that can use ProSe, the ProSe ID may be used as the identification information of the UE 10. Further, ProSe capability information may be included in the message. The ProSe capability information may be capability information indicating that a ProSe service indicating that a direct communication path with a neighboring UE can be established can be enjoyed. Alternatively, it may be information indicating that a ProSe service is enjoyed and a direct communication path is established with a neighboring terminal. In addition, these pieces of information are included as different identification information in the message as different identification information. Also good.

Further, the information for identifying the location management device may include information for identifying the MME 40 that has been executing location management of the UE 10 so far. Furthermore, information for identifying the MME-A 90 may be included. The information included in the message is not limited to these, and may be included together with information included in the conventional context request message.

Application identification information is identification information for identifying an application used by the UE 10 to establish a communication path with another UE.

Further, the message may include a flag requesting identification information of the application server 20 registered by the UE 10.

The MME 40 may transmit a context response message to the MME-A 90 based on the reception of the context request message (S1008).

The MME 40 may manage the permission information 342 managed in association with the UE 10, and may transmit the message including the permission information 342.

Here, the MME 40 may select and include the permission information 342 managed in association with the UE 10 based on the identification information of the UE 10 included in the context request message. Accordingly, the MME 40 may notify the MME-A 90 of permission information indicating that the UE 10 is permitted to use the service using the GRIP address, the GRIP address of the UE 10, and information related to the UE 10. As described above, the MME 40 may notify the MME-A 90 that the UE 10 is permitted to use the GRIP and that the UE 10 is currently acquiring the GRIP.

Further, the MME 40 may transmit a context response including the identification information of the application server 20.

Further, whether or not to include information for identifying the application server 20 in the context response message may be determined depending on the presence or absence of a flag for requesting the identification information of the application server 20 included in the context request message.

For example, when a context request message including a flag requesting identification information of the application server 20 is received, a message including the identification information of the application server 20 managed in association with the UE 10 held by the MME-A 90 is transmitted. To do.

Also, if the context request message does not include the flag for requesting the identification information of the application server 20, the message is transmitted without including the identification information of the application server 20.

If the identification information of the application server 20 is not managed for the UE 10, the context response may be transmitted without including the identification information of the application server 20.

Further, whether or not to include information for identifying the application server 20 may be determined depending on the presence or absence of application identification information or application user identification information included in the context request message.

For example, when a context request message including application identification information or application user identification information is received, the message including the identification information of the application server 20 managed in association with the UE 10 held by the MME-A 90 is transmitted.

Also, if the context request message does not include application identification information, application user identification information, or ProSe code, the message is transmitted without including the message including the identification information of the application server 20.

The MME 40 uses the application server 20 based on either a flag requesting identification information of the application server 20, capability information indicating that the ProSe service can be enjoyed, or information indicating that a direct communication path has been established with a neighboring terminal. It may be transmitted including the identification information of the server 20, or it may be determined to include a combination of these information, such as including a plurality of such information, and transmitted including the identification information of the application server 20. Also good.

The MME-A 90 receives a context response from the MME 40. When the identification information of the application server 20 is included in the context response, the MME-A 90 stores the identification information of the application server 20 in the permission information 342. Further, the database to be stored is not limited to the permission information 342 but may be a database such as an MM context. Further, the identification information of the application server 20 may be stored in association with the identification information of the UE 10.

The MME-A 90 stores the context of the UE based on the reception of the context response message.

Here, the MME-A 90 may perform processing for determining whether or not the GRIP address can be used. Hereinafter, the determination process will be described.

Further, the MME-A 90 may acquire permission information for using the GRIP address of the UE and the GRIP address of the UE 10 from the message, and store them in the storage unit. In addition, when the MME-A 90 stores a policy such as an operator policy regarding use of the GRIP address, permission information for use of the GRIP address of the UE may be stored based on the policy.

Specifically, when the operator policy stored in the MME-A 90 prohibits the UE in the service area of the MME-A 90 from using an application using the GRIP address, the MME-A 90 moves from the MME 40 to the UE. Even if the permission information on the use of the GRIP address of the UE is acquired, the permission information on the use of the GRIP address of the UE may not be stored according to the operator policy.

As described above, the MME-A 90 can permit or deny the use of GRIP to the terminal device connected to the base station to which the MME is connected in accordance with the tracking area update procedure. When the terminal device is not permitted to use GRIP, the MME-A 90 may transmit a response message to the UE 10 in response to the received tracking area update request. Note that the MME-A 90 may notify that the tracking area update has failed due to the transmission of the response message or that the use of GRIP is not permitted. Here, the MME-A 90 may transmit a tracking area update accept message as a response message, and may include information indicating these pieces of notification information in the message.

Furthermore, the PDN connection associated with the application executed using the GRIP address, such as the PDN connection that executes communication using the GRIP address or the PDN connection established when the GRIP address is acquired, is deleted from the response message. You may transmit including the information which requests to do.

At this time, the MME-A 90 does not need to transmit a bearer update request message to the SGW 35.

Furthermore, the UE 10 may receive the response message and delete the PDN connection based on the information included in the response message. When deleting the PDN connection, the UE 10 uses a GRIP address such as a PDN connection that executes communication using the GRIP address or a PDN connection that is established when the GRIP address is acquired based on the response message. The deletion may be executed by selecting the PDN connection associated with the application to be executed. Specifically, the UE 10 may delete a PDN connection, which may be performed by executing a PDN deletion procedure started by transmitting a PDN deletion request message to the MME-A 90.

The method of deleting the PDN connection is not limited to this, and other methods may be used. For example, when the MME-A 90 does not allow the use of GRIP to the terminal device connected to the base station to which the MME is connected in accordance with the tracking area update procedure, the MME-A 90 takes the initiative to delete such a PDN connection. Also good. Specifically, the MME-A 90 may delete the PDN connection, which may be performed by executing a PDN deletion procedure that starts by transmitting a session deletion request message to the SGW 35.

As described above, the MME-A 90 may execute a process for determining whether or not the GRIP address can be used. As described above, the MME-A 90 can restrict the use of the GRIP address of the UE connected to the base station to which the MME-A 90 is connected based on the determination process. Therefore, it is possible to control whether or not the GRIP address can be used on an area basis, such as an area composed of a plurality of base stations connected to the MEM-A 90.

Next, based on the determination process, the ME-A 90 does not execute the determination process itself when the use of GRIP is permitted for the terminal device connected to the base station to which the MME is connected in accordance with the tracking area update procedure. The procedure in such a case will be described with reference to FIG.

The MME-A 90 transmits a context ACK to the MME 40, and completes the relocation (MME-Relocation) of the location management device (S1010).

Further, the MME-A 90 may transmit a bearer update request message to the SGW 35 (S1012). Accordingly, the MME-A 90 and the UE 10 may request to update the QoS information of the PDN connection established with the PGW 30. Moreover, you may request | require the update of the QoS information of the bearer matched with a PDN connection. Or you may request | require update of the QoS information of IP connection between other UEs which UE10 has established.

The message may include PDN connection identification information or communication path identification information such as an IP connection established with another UE. Furthermore, you may transmit including the QoS information corresponding to a communication channel.

The SGW 35 receives the bearer request message, and the SGW 35 and the PGW 30 execute a bearer update procedure based on the reception of the bearer request message (S1014). In the bearer update procedure, the QoS information of the PDN connection established by the UE 10 with the PGW 30 may be updated. Moreover, you may request | require the update of the QoS information of the bearer matched with a PDN connection. Or you may update the QoS information of the communication path of IP connection between other UEs which UE10 has established.

After completing the bearer update procedure of the SGW 35 and PGW 30, the SGW 35 transmits a bearer update response message to the MME-A 90 (S1016).

The MME-A 90 transmits a tracking area update accept message to the UE 10 based on the reception of the bearer update response message (S1018). The MME-A 90 may notify that the tracking area has been updated in response to the tracking area update request requested by the UE 10 by transmitting a tracking area update accept message.

The message may include the updated QoS information of the PDN connection established between the UE 10 and the PGW 30. Further, the MME-A 90 may transmit the message including information that can identify the application such as TFT and APN. Further, the MME-A 90 may transmit the message including both pieces of identification information.

Furthermore, the updated QoS information of the communication path of the IP connection established between the UE 10 and another UE may be included and transmitted.

Furthermore, information regarding the radio bearers of these communication paths may be included. For example, you may transmit including the information regarding the radio | wireless resource of a communication path, such as time information, such as a frequency and a transmission timing. The information regarding the radio resource may be allocated again by the MME-A 90 and notified in the message, or may be acquired from the information included in the bearer update response message from the SGW 35 and notified to the UE 10.

Furthermore, the tracking area update accept message may include the MME-A90 identification information. Thus, the MME-A 90 may notify that the location management device has been relocated (MME-Relocation) by transmitting a message including the identification information of the MME-A 90 to the UE 10.

The UE 10 may receive the tracking area update accept from the MME-A 90 and transmit a tracking area update completion message to the MME-A 90 based on the reception. Along with this, the UE 10 completes the tracking area update procedure accompanied by the relocation (MME-Relocation) of the location management device.

Furthermore, the UE 10 may update information on the radio bearer based on information included in the tracking area update accept. For example, information related to radio resources of the communication path such as frequency and time information such as transmission timing may be updated. The information regarding the radio resource may be updated with respect to the PDN connection with the PGW 30.

Through the above procedure, the UE 10 can update the tracking area accompanied by the relocation (MME-Relocation) of the location management device in the idle mode.

Further, in the above-described procedure, the MME-A 90 that is a location management device that manages the destination base station even if the location management device is rearranged due to the movement of the UE 10 in the idle mode, the MME 40 before the migration is Since the application information to be held can be acquired, the application server 20 is not changed, and the UE 10 can maintain transmission / reception of data using a GRIP address with another UE or the like.

Further, the UE 10 may transmit the tracking area update request including request information for requesting that the MME-A 90 obtain the identification information of the application server 20.

This request information only needs to detect that the MME-A 90 needs to acquire the identification information of the application server 20, and may be a flag or the like requesting acquisition of the identification information of the application server.

Further, the eNB-A 95 receives the tracking area update request message including the request information for requesting the MME-A 90 to acquire the identification information of the application server 20, and transmits the tracking area update request message to the MME-A 90. May be.

Based on whether or not the tracking area update request message transmitted to the MME-A 90 includes request information requesting to acquire the identification information of the application server 20 in the tracking area update request message received from the UE 10. You may transmit including the received request information.

Further, the MME-A 90 transmits a context to be transmitted to the MME 40 based on whether or not the received tracking area update request message includes request information for requesting the MME-A 90 to acquire the identification information of the application server 20. The request message may include a flag for requesting identification information of the application server 20 that permits the UE 10 to communicate using the GRIP address.

For example, the MME-A 90 uses the GRIP address for the UE 10 when the received tracking area update request message includes request information requesting that the MME-A 90 obtain the identification information of the application server 20. The context request message including the flag requesting the identification information of the application server 20 that permits the received communication is transmitted to the MME 40.

In addition, when the received tracking area update request message does not include request information for requesting that the MME-A 90 obtain the identification information of the application server 20, the application that permits the UE 10 to communicate using the GRIP address. A context request message is transmitted to the MME 40 without including a flag for requesting identification information of the server 20.

Thereby, the MME-A 90 may receive the identification information of the application server 20 from the MME 40 and notify the ProSe server that the location management device that manages the location of the UE-R 15 has been updated.

[1.4. Modified example]
Next, as a modification, a method of acquiring a GRIP address when using a GRIP address in ProSe communication will be described. However, in this modification, it is assumed that the UE 10 is a UE that can use ProSe.

[1.4.1. Registration procedure to ProSe application server]
The UE 10 performs an authentication procedure for proximity terminal detection (ProSe Direct Discovery) provided as a ProSe service and communication using a direct communication path (ProSe Direct Communication). The authentication procedure may authenticate each of the neighboring terminal detection and the communication using the direct communication path by different procedures, or may be authenticated by one authentication procedure.

Hereinafter, the authentication procedure in this embodiment will be described with reference to FIG.

First, the UE 10 executes an attach procedure and connects to the core network (S702). As a result, the UE 10 establishes a PDN connection with the PGW 30. The PDN connection is a communication path for transmitting / receiving data to / from the PDN 9. The attach procedure may be executed as an initial procedure such as when the UE 10 is powered on.

More specifically, the attach procedure starts when the UE 10 transmits an attach request to the MME 40. The UE 10 may transmit the attach request including the APN and UE identification information such as IMSI. The APN is not necessarily included in the attach request message, and may be notified from the UE 10 to the MME 40 by a control message in the attach procedure.

The MME 40 selects the PGW 30 based on the received APN, and determines the end point of the PDN connection for the UE 10. Furthermore, establishment of a PDN connection and connection to a core network are permitted, and an attach permission message serving as a response to the attach request message is transmitted to the UE 10. The attach permission message may be transmitted directly from the MME 40 to the UE 10 or may be transmitted via the eNB 45 included in the LTE AN 80.

Further, the MME 40 may notify that the UE 10 is permitted to connect to the core network by transmitting an attach permission message. Further, the MME 40 may notify that the PDN connection has been established by transmitting an attach permission message. Further, the attach permission message may be transmitted including the IP address associated with the PDN connection or the APN.

Further, the MME 40 may transmit the attach permission message including the ProSe UE ID. For example, the MME 40 may transmit the message including the attach permission message ProSe UE ID based on the fact that the APN transmitted by the UE 10 in the attach procedure is the APN associated with the ProSe service. At this time, the MME 40 may assign ProSe UE ID to the UE_A8. Moreover, you may acquire from HSS50. In this case, the HSS 50 or the like may store the ProSe UE ID in the subscriber information in advance.

Next, the UE 10 transmits a ProSe registration request message to the ProSe server (S706). At this time, the ProSe server is a server device that manages communication between UEs having the ProSe function, and performs authentication when providing a ProSe service or the like. The ProSe server may be configured to be included in the PDN 9 or may be independent of the PDN 9.

The UE 10 may request permission of communication using a neighboring terminal detection and a direct communication path by transmitting a ProSe registration request message. Further, it is possible to transmit information including information for identifying the neighboring terminal detection and the permission of communication using the direct communication path, and request permission for each of them.

Also, the ProSe registration request may be transmitted using the PDN connection established by the attach procedure. Further, the ProSe registration request message may be transmitted using the IP address acquired in the attach procedure as the transmission source address.

In addition, the ProSe server that is the transmission destination of the ProSe registration request message may hold the information of the ProSe server associated with the home PLMN that is the contracted communication carrier in advance and use it as the transmission destination.

Alternatively, a list of communication carriers that can provide the ProSe service is held as a local PLMN, and further, a ProSe server associated with the local PLMN may be held and used as a transmission destination.

The local PLMN may be an arbitrary communication carrier determined based on a contract relationship with the Home PLMN, or may be a communication carrier operating in the same country as the Home PLMN.

As described above, the UE 10 may hold the PLMN ID for identifying the PLMN and the ProSe server in association with each other, and request authentication using the transmission destination.

Also, the PLMN ID and ProSe server information may be obtained from the HomePLMN. For example, an inquiry may be made to the ProSe server of Home PLMN, and it may be acquired and retained by a response to the inquiry.

The ProSe server may receive the ProSe registration request, execute detection of neighboring terminals and authentication of communication using the direct communication path, and transmit a ProSe registration response (S708).

The ProSe server may send the ProSe registration response including the authentication result. Further, the ProSe server may transmit the message including identification information such as TFT and APN that can identify the application.

The ProSe server may store information for authentication in association with the UE 10, and may determine whether the authentication result is acceptable or not based on the information.

In addition, the ProSe server may execute allocation of the ProSe UE ID based on the reception of the ProSe registration request (S707). Further, the ProSe UE ID may be included in the ProSe registration response and transmitted to the UE 10. The ProSe UE ID may be an ID associated with the UE 10, and the UE 10 may be used as information for identifying a terminal when detecting a neighboring terminal or notifying the neighboring terminal of itself. More specifically, the UE 10 may transmit the ProSe UE ID included in the announcement signal.

UE10 receives the ProSe registration response and acquires the authentication result. Further, the ProSe UE ID included in the ProSe registration response may be acquired and held. As described above, the UE 10 may be authenticated by the ProSe server.

Thereby, the UE 10 starts the PDN connectivity procedure (S710).

[1.4.2. PDN connectivity procedure]
The procedure for obtaining the GRIP address by the PDN connectivity procedure may be equal to the PDN connectivity procedure of FIG. Detailed description is omitted here. Through the PDN connectivity procedure, the UE 10 can acquire the GRIP address and store it in association with the GRIP address and the application ID.

[1.4.3. ProSe Announcement Procedure]
A ProSe announcement procedure using a GRIP address will be described with reference to FIG. The UE 10 that has acquired the GRIP address and associates the application ID with the GRIP address establishes a secure connection with the ProSe server, and transmits a discovery request to the ProSe server (S804).

The discovery request may include a ProSe application ID, a UE identifier such as IMSI or MSISDN, a command indicating a request for announcement, and an application ID.

The ProSe application ID is an identifier for identifying a terminal that can use ProSe.

The ProSe server receives a discovery request from the UE 10. The ProSe server acquires the ProSe application ID and the UE identifier, the command indicating the request for announcement, the application ID, and the GRIP address included in the discovery request.

The ProSe server checks whether the management information of the UE 10 exists in the storage unit of the ProSe server. If there is no management information of the UE 10 in the storage unit of the ProSe server, the ProSe server confirms the authentication information of the UE 10 with the HSS 50 and creates new management information of the UE 10 (S806). As a result, the UE 10 has been authenticated for discovery by the ProSe server.

When the ProSe server authenticates the UE 10, it sends a discovery response to the UE 10. The ProSe server may include a ProSe application code and a timer in the discovery response. Thereby, the ProSe server can instruct the UE 10 to maintain the valid state of the application identified by the ProSe application code until the timer count ends.

UE 10 receives the discovery response from the ProSe server. The UE 10 may acquire the ProSe application code and timer included in the message, and may make the announcement identified by the ProSe application code valid for the time managed by the timer.

UE10 receives the discovery response from the ProSe server. The UE 10 acquires a ProSe application code and a timer included in the discovery response.

UE10 starts the announcement based on the reception of the discovery response (S810). Note that the UE 10 may start an announcement of discovery based on the reception of the PDN connectivity accept message. The announcement signal transmitted by the UE 10 includes at least identification information indicating that the GRIP address has been acquired and application identification information such as an application ID.

Thus, the UE 10 and the neighboring UE different from the UE 10 that has received the announcement signal are detected that the UE 10 and the UE 10 can perform communication of the application identified by the application ID using the GRIP address.

Note that the GRIP address acquired by the UE 10 may be used as identification information indicating that the GRIP address has been acquired.

From the above, the GRIP address can be used in the announcement function of ProSe.

[1.5. IP address change procedure]
Next, a procedure for changing the GRIP address of the UE 10 starting from the UE 10 will be described.

The UE 10 will explain the initial state below. The UE 10 obtains the authentication of the use of the application and the acquisition of the GRIP address from the application server 20 that provides the communication using the GRIP address by the authentication procedure to the application server 20.

Furthermore, the UE 10 requests acquisition of a conventional IP address in the PDN connectivity procedure, acquires a conventional local IP address, establishes a PDN connection, and realizes communication. At this time, when the UE 10 wants to switch to communication using the GRIP address, an IP address changing procedure for using the already acquired local IP address as the GRIP address will be described.

At this time, the UE 10 transmits a control message requesting the change of the IP address to the MME 40 using any of the control procedures, and the MME 40 authenticates the IP address change procedure of the UE 10 based on the received message.

Further, the MME 40 requests the PGW 30 for authentication permission in the IP address change procedure, and when receiving the IP address authentication permission, transmits a response message to the IP address change request to the UE 10.

Here, the control procedure for requesting the change of the IP address is not particularly limited, but in the following, the method for extending the service request procedure initiated by the UE and the bearer change request procedure requested by the UE are expanded. Explain the method.

[1.5.1. Change of IP address using service request]
First, an IP address changing procedure using a UE-initiated service request will be described with reference to FIG. The initial state may be a state in which the UE 10a acquires an IP address by executing an attach procedure. Note that the specific attachment procedure is the same as the method already described, and thus detailed description thereof is omitted.
In addition, the initial state is not limited to after the attach procedure is executed, and the UE 10a may execute the PDN connectivity procedure and obtain a conventional IP address. More specifically, the UE 10a transmits a PDN connectivity request to the core network including the APN and the PDN type, and a PDN including the APN, the PDN type, and the conventional IP address as a message response. A response to the connectivity request may be received from the eNB 45.

UE 10 transmits a service request message to eNB 45 (S902). The message may include UE identification information, application identification information, and identification information requesting to change the IP address to a GRIP address. As described above, the UE 10a may implement a request to change the already acquired IP address to the GRIP address by transmitting the service request message. Note that the UE 10a may make such a request based on the fact that the application server 20 is authenticated by a registration procedure with the application server or the like. Further, the UE 10a may transmit the request message further including information identifying that it is authenticated.

Further, the UE identification information may be any information element that can identify the UE 10, and may be, for example, IMSI. Also, it may be an information element that can identify the UE and the MME, such as S-TMSI (SAE Temporary Mobile Subscriber Identity).

Further, the identification information for requesting to change the IP address to the GRIP address may be application identification information, application permission information, or the like. Moreover, a flag etc. may be sufficient.

ENB 45 receives a service request message from UE 10. The eNB 45 transfers the message to the MME 40 (S904).

The MME 40 receives a service request message from the eNB 45. The MME 40 executes an authentication process based on the reception of the message. As specific authentication processing, the authentication information of the HSS 50 and the UE 10 is confirmed (S906). At this time, the identification information of the UE 10 included in the message received by the MME 40 may be used for confirmation of the authentication information. Moreover, you may confirm the authentication information of UE10 only by MME40.

Note that the authentication information may be management information that manages user information in association with permission information indicating whether to assign a GRIP address to the user.

At this time, if the authentication information of the UE 10 cannot be confirmed or if the UE 10 is not permitted to assign a GRIP address, the process may be stopped. Or you may notify that authentication information cannot be confirmed to UE10 via MME40 and eNB45. Alternatively, it may be notified that the change or assignment to the GRIP address is not permitted.

Furthermore, the MME 40 may execute an authentication process for changing to such a GRIP address based on an information element indicating an IP address change request included in the message.

When the confirmation of the authentication information of the UE 10 is completed and the change of the GRIP address is further authenticated, the MME 40 transmits an initial context setting request message to the eNB 45 (S908). The eNB 45 receives the initial context setting request message from the MME 40. The eNB 45 performs a radio bearer establishment or change procedure between the UE 10 and the eNB 45 based on the reception of the message (S910).

Next, the eNB 45 transmits an initial context setting response message to the MME 40 (S912).

The MME 40 receives the initial context setting response message from the eNB 45. Based on the reception of the message, the MME 40 transmits a bearer change request message to the PGW (S914). The MME 40 transmits a bearer change request message including identification information indicating that the IP address is changed to the GRIP address based on the result of the above-described authentication process such as confirming that the UE 10 can use the GRIP address. May be.

Note that the identification information indicating that the IP address is changed to the GRIP address may be application identification information or the IP address of the UE 10 may be a GRIP address.

The PGW 30 receives a bearer change request message from the MME 40. The message may include UE identification information, application identification information, and identification information indicating that the IP address of the UE 10 is a GRIP address. The PGW 30 stores the IP address of the UE 10 in the GRIP address management table 442 in the PGW 30 based on the notification of the IP address change of the UE 10 included in the message.

The PGW 30 transmits a bearer change response message to the MME 40 based on the reception of the bearer change request message (S916). The message may include identification information indicating the change to the GRIP address.

Note that the PGW 30 can deliver the packet received from the UE 10a with the changed IP address as the transmission source address to the PGW between different mobile communication network based on the reception of the bearer change request message. The route setting such as may be executed.

The MME 40 receives a bearer change response message from the PGW 30. Based on the reception of the message, the MME 40 transmits an IP address change response message to the UE 10 as a response to the IP address change request included in the service request message (S918).

The MME 40 may include identification information for identifying the application, such as TFT or APN, in the message. Further, both pieces of identification information may be included in association with each other.

Furthermore, the IP address change response message may include information indicating that the IP address has been changed to the GRIP address, and notify the UE 10a that the address attribute change has been completed.

By receiving an IP address change response message from the MME 40, the UE 10 is notified that the change of the IP address has been authenticated by the MME 40, the management table stored in the storage unit of the PGW 30 has been changed, and the IP held by the UE 10 The address can be used as a GRIP address.

Thereby, when performing communication of an application, the UE 10 selects a corresponding GRIP address based on the application identification information, and transmits / receives application data identified by the application identification information using the selected GRIP address. it can.

Thus, even if the UE 10 transmits to the PGW 30 using the conventional IP address, the PGW 30 can handle the address of the UE 10 as a GRIP address and can transfer it to the destination.

[1.5.2. IP address change procedure using bearer change request procedure from UE]
Furthermore, as a specific example of the IP address change procedure, a method using a bearer change procedure started from the UE will be described. The initial state is a state in which the UE 10 is attached to the network, the registration procedure with the application server 20 is completed, and communication is performed using a conventional IP address. Description is omitted.

In this specific example, the UE 10 expands and executes the bearer change procedure, thereby changing the conventional IP address to the GRIP address. Note that the UE 10 may start an IP address change procedure using a bearer change request procedure triggered by movement or QoS change, or in conjunction with activation of an application that performs communication using the GRIP address. You may start. Or you may use the trigger for starting the change procedure of the bearer started from the conventional UE.

Hereinafter, an IP address changing procedure using a bearer changing procedure started from a conventional UE will be described with reference to FIG.

UE10 transmits a bearer change request message to MME40 based on an above described trigger (S1102). The message may include UE identification information, application identification information, and identification information requesting to change the IP address to a GRIP address.

The UE identification information may be an information element that can identify the UE 10, and may be, for example, IMSI. Also, it may be an information element that can identify the UE and the MME, such as S-TMSI (SAE Temporary Mobile Subscriber Identity).

Alternatively, the identification information that requests changing the IP address to the GRIP address may be identification information that identifies the communication flow. The identification information for identifying the communication flow may be identification information associated with an application that performs communication using the GRIP address.

The identification information for identifying a specific communication flow may be a TFT. The UE 10 may use, as identification information for identifying a communication flow, a TFT that can identify traffic of an application that performs communication using the GRIP address, or the UE 10 may use an application that performs communication using the GRIP address. A TFT ID for identifying a TFT capable of identifying traffic may be used as identification information for identifying a communication flow.

Furthermore, the UE 10 may request to change the IP address to the GRIP address by using both the flow identification information such as TFT and TFT ID and the identification information for requesting the GRIP address.

The message may further include information elements included in the conventional bearer update request message such as bearer ID and QoS.

The MME 40 receives a bearer change request message from the UE 10. A bearer resource instruction message is transmitted to the SGW 35 based on the identification information included in the message that requests changing the IP address to the GRIP address (S1104).

The message may include UE identification information, application identification information, and identification information requesting to change the IP address to a GRIP address.

The UE identification information may be an information element that can identify the UE 10, and may be, for example, IMSI. Further, it may be an information element that can identify the UE and the MME, such as S-TMSI.

The message may further include information elements included in the conventional bearer resource instruction message such as bearer ID and QoS.

The SGW 35 receives the bearer resource message from the MME 40 and selects the PGW 30 based on the received bearer ID. The SGW 35 transmits a bearer resource instruction message to the selected PGW 30 (S1106).

The PGW 30 receives the bearer resource instruction message from the SGW 35. When the identification information requesting to change the IP address is included in the message, the PGW 30 stores the conventional IP address used by the UE 10 in the GRIP address management table 442 stored in the storage unit 440. Change to a GRIP address.

Alternatively, the IP address of the UE 10 may be changed to the GRIP address by including the identification information of the application without including the identification information requesting to change the IP address. Alternatively, the IP address of the UE 10 may be changed to a GRIP address by including application permission information.

In a specific change process, the PGW 30 may execute path setting such that a packet having the changed IP address as a transmission source address can be delivered between different mobile communication carrier networks. .

When the change of the IP address is completed in the PGW 30, processing such as enabling the bearer, disabling the bearer, or changing the bearer may be started.

When the IP address is changed, the PGW 30 transmits a bearer establishment (update) message to the SGW 35 (S1108).

The message may include UE identification information, application identification information, and identification information indicating that the IP address has been changed to the GRIP address.

Further, the identification information indicating that the IP address has been changed to the GRIP address may be application identification information or the like.

The message may further include an information element included in a conventional bearer establishment (update) message such as QoS.

The SGW 35 receives a bearer establishment (update) message from the PGW 30. If the message includes identification information indicating that the IP address has been changed to the GRIP address, the SGW 35 transmits a bearer establishment (update) message to the MME 40 (S1110).

The MME 40 receives a bearer update (establishment) request message from the SGW 35. When the received message includes identification information indicating that the IP address has been changed to the GRIP address, the MME 40 transmits an IP address change notification to the UE 10 as a response to the bearer change request received from the UE 10 (S1112).

The MME 40 may include a TFT or APN identifying the application in the message. Further, both pieces of identification information may be included.

Further, the MME 40 may include identification information indicating that the IP address has been changed to the GRIP address in the message.

UE10 receives IP address change notification from MME40. When the received message includes identification information indicating that the IP address has been changed to the GRIP address, the UE 10 can use the held IP address as the GRIP address.

As described above, even if the UE 10 transmits data to the PGW 30 using the conventional IP address, the PGW 30 can handle the address of the UE 10 as a GRIP address and can transfer it to the destination.

As mentioned above, although embodiment and modification of this invention were explained in full detail with reference to drawings, the concrete structure is not restricted to this embodiment, and the design etc. of the range which does not deviate from the summary of this invention are patents. Included in the claims.

In each embodiment, a program that operates in each device is a program that controls a CPU or the like (a program that causes a computer to function) so as to realize the functions of the above-described embodiments. Information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) at the time of processing, then stored in various ROM or HDD storage devices, and read and corrected by the CPU as necessary. • Writing is performed.

Here, as a recording medium for storing the program, a semiconductor medium (for example, ROM, a non-volatile memory card, etc.), an optical recording medium / a magneto-optical recording medium (for example, DVD (Digital Versatile Disc), MO (Magneto Optical) Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.), magnetic recording medium (eg, magnetic tape, flexible disk, etc.), etc. In addition, by executing the loaded program, not only the functions of the above-described embodiment are realized, but also based on the instructions of the program, the processing is performed in cooperation with the operating system or other application programs. The functions of the invention may be realized.

In addition, when distributing to the market, the program can be stored in a portable recording medium for distribution, or transferred to a server computer connected via a network such as the Internet. In this case, of course, the storage device of the server computer is also included in the present invention.

Further, a part or all of each device in the above-described embodiment may be realized as an LSI (Large Scale Integration) which is typically an integrated circuit. Each functional block of each device may be individually formed as a chip, or a part or all of them may be integrated into a chip. Further, the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. In addition, when integrated circuit technology that replaces LSI appears due to progress in semiconductor technology, it is of course possible to use an integrated circuit based on this technology.

In the above-described embodiment, LTE and WLAN (for example, IEEE802.11a / b / n) are described as examples of the radio access network, but they may be connected by WiMAX instead of WLAN.

1 Communication System 5 IP Mobile Communication Network 7 Core Network 9 PDN
10 UE
20 Application server 30 PGW
35 SGW
40 MME
45 eNB
50 HSS
55 AAA
60 PCRF
65 ePDG
70 WLAN_ANA
72 WLAN APa
74 GW
75 WLAN_ANb
76 WLAN_APb
80 LTE_AN

Claims

A terminal device,
A transmission unit that transmits a PDN (Packet Data Network) connectivity request message to an MME (Mobility Management Entity);
The PDN connectivity request message includes at least an APN, a PDN type, and first identification information indicating requesting assignment of a globally routable IP address;
As a response to the PDN connectivity request message, a receiving unit that receives a PDN connectivity accept message from the base station device;
The PDN connectivity accept message includes at least the APN, the PDN type, and the globally routable IP address,
A storage unit for acquiring the globally routable IP address based on the transmission of the first identification information;
A terminal device.
The transmitter is
By sending an authentication request message to the application server,
Requesting the application server to authenticate the use of an application that communicates using the globally routable IP address;
Sending the PDN connectivity request message to the MME based on receipt of a control message;
The receiver is
Receiving the control message, which is a response to the authentication request message and indicates that the authentication transmitted by the application server has been completed.
The terminal device according to claim 1.
The storage unit
Obtaining authentication information contained in the control message;
The transmitter is
Sending the PDN connectivity request message to the MME including at least the authentication information;
The terminal device according to claim 2.
The storage unit
Storing second identification information for identifying an application that performs communication using a globally routable IP address;
Storing the application and the globally routable IP address in association with each other;
The transmitter and the receiver are
Communication of the application is performed using the globally routable IP address.
The terminal device according to claim 1.
A control unit for establishing a PDN connection with a PGW (PDN Gateway) based on the reception of the PDN connectivity accept message;
The transmitter and the receiver are
Communication of the application is performed using the PDN connection.
The terminal device according to claim 4.
The transmitter is
Based on the reception of the PDN connectivity accept message, at least third identification information indicating that the globally routable IP address has been acquired and an announcement signal including the second information are broadcast to the neighborhood With that
Allowing the terminal device to detect that the terminal device can perform communication of the application using the globally routable IP address;
The terminal device according to claim 4.
The third identification information is the globally routable IP address.
The terminal device according to claim 6.
MME (Mobility Management Entity),
A receiving unit for receiving a PDN (Packet Data Network) connectivity request message from the terminal device;
The PDN connectivity request message includes at least an APN, a PDN type, and first identification information indicating requesting assignment of a globally routable IP address;
In response to the PDN connectivity request message, a PDN connectivity accept message is transmitted to the base station apparatus,
The PDN connectivity accept message includes at least the APN, the PDN type, and the globally routable IP address,
A transmission unit configured to transmit the PDN connectivity accept message including the globally routable IP address based on the reception of the first identification information;
MME with
PGW (PDN Gateway),
A receiving unit that receives a session establishment request message from an SGW (Serving Gateway) based on transmission of a PDN (Packet Data Network) connectivity request message of the terminal device;
The session establishment request message includes at least an APN, a PDN type, and first identification information indicating that an assignment of a globally routable IP address is requested,
A control unit that assigns a globally routable IP address based on reception of the first identification information;
A transmission unit that transmits a session establishment response message to the SGW as a response to the session establishment request message;
The session establishment response message includes at least the APN, the PDN type, and the globally routable IP address.
PGW.
A terminal device,
Send a PDN (Packet Data Network) connectivity request message to MME (Mobility Management Entity),
A transmission unit that transmits a first request message requesting to change an IP address to a globally routable IP address to the MME or the base station device;
The PDN connectivity request message includes at least an APN and a PDN type,
In response to the PDN connectivity request message, a PDN connectivity accept message is received from the base station device,
The PDN connectivity accept message includes at least the APN, the PDN type, and the globally routable IP address,
A receiving unit for receiving a response message to the first request message;
A storage unit that changes an IP address to the globally routable IP address based on reception of the response message;
A terminal device.
A communication control method for a terminal device,
Transmitting a PDN (Packet Data Network) connectivity request message to an MME (Mobility Management Entity);
The PDN connectivity request message includes at least an APN, a PDN type, and first identification information indicating requesting assignment of a globally routable IP address;
Receiving a PDN connectivity accept message from the base station apparatus as a response to the PDN connectivity request message;
The PDN connectivity accept message includes at least the APN, the PDN type, and the globally routable IP address,
Obtaining the globally routable IP address based on the transmission of the first identification information;
Control method for a terminal device including
Sending an authentication request message to an application server to request authentication for use of an application that communicates using the globally routable IP address;
Receiving a control message that is a response to the authentication request message and indicates that the authentication sent by the application server has been completed;
Sending the PDN connectivity request message to the MME based on receipt of the control message;
The communication control method of the terminal device according to claim 11.
Further comprising obtaining authentication information included in the control message;
Sending the PDN connectivity request message to the MME including at least the authentication information;
The communication control method of the terminal device according to claim 12.
Storing second identification information for identifying an application that performs communication using the globally routable IP address;
Associating and storing the application and the globally routable IP address;
Communicating the application using the globally routable IP address;
The communication control method for a terminal device according to claim 11, further comprising:
Establishing a PDN connection with a PGW (PDN Gateway) based on the reception of the PDN Connectivity Accept message,
Communication of the application is performed using the PDN connection.
The communication control method of the terminal device according to claim 14.
In order for the terminal device to detect that the terminal device can perform communication of the application using the globally routable IP address,
Based on the reception of the PDN connectivity accept message, at least third identification information indicating that the globally routable IP address has been acquired and an announcement signal including the second identification information are broadcast to the neighborhood Include steps to
The communication control method of the terminal device according to claim 14.
The third identification information is the globally routable IP address.
The communication control method of the terminal device according to claim 16.
A communication control method of MME (Mobility Management Entity),
Receiving a PDN (Packet Data Network) connectivity request message from the terminal device;
The PDN connectivity request message includes at least an APN, a PDN type, and first identification information indicating requesting assignment of a globally routable IP address;
As a response to the PDN connectivity request message, transmitting a PDN connectivity accept message to the base station device;
The PDN connectivity accept message includes at least the APN, the PDN type, and a globally routable IP address,
Transmitting the PDN connectivity accept message including the globally routable IP address based on receiving the identification information;
MME communication control method.
A communication control method of PGW (PDN Gateway),
Receiving a session establishment request message from an SGW (Serving Gateway) based on the transmission of a PDN (Packet Data Network) connectivity request message of the terminal device;
The session establishment request message includes at least an APN, a PDN type, and first identification information indicating that an assignment of a globally routable IP address is requested,
Assigning a globally routable IP address based on receiving the first identification information;
Sending a session establishment response message to the SGW including at least the APN, the PDN type, and the globally routable IP address as a response to the session establishment request message;
PGW communication control method including
A communication control method for a terminal device,
Transmitting a PDN (Packet Data Network) connectivity request message including at least an APN and a PDN type to MME (Mobility Management Entity);
Receiving a PDN connectivity accept message including at least an APN, a PDN type, and a globally routable IP address as a response to the PDN connectivity request message;
Transmitting a first request message requesting to change an IP address to a globally routable IP address to the MME or the base station device;
Receiving a response message to the first request message;
Changing an IP address to the globally routable IP address based on receiving the response message;
Control method for a terminal device including
A communication system including at least a terminal device, a base station device, an MME (Mobility Management Entity), an SGW (Serving Gateway), and a PGW (PDN Gateway),
The terminal device
A PDN (Packet Data Network) connectivity request message is sent to the MME;
The PDN connectivity request message includes at least an APN, a PDN type, and first identification information indicating requesting assignment of a globally routable IP address;
The MME is
Receiving the PDN connectivity request message from the terminal device;
Based on the reception of the PDN connectivity request message, a first session establishment request message is sent to the SGW;
The first session establishment request message includes at least the APN, the PDN type, and the first identification information,
The SGW is
Receiving the first session establishment request message from the MME;
Based on receiving the first session establishment request message, sending a second session establishment request message to the PGW;
The second session establishment request message includes at least the APN, the PDN type, and the first identification information,
The PGW is
Receiving the second session establishment request message from the SGW;
Based on the reception of the first identification information, a globally routable IP address is assigned to the terminal device,
Sending a first session establishment response message to the SGW as a response to the second session establishment request message;
The first session establishment response message includes at least the APN, the PDN type, and the globally routable IP address,
The SGW is
Receiving the first session establishment response message from the PGW;
Based on the reception of the first session establishment response message, a second session establishment response message is transmitted to the MME as a response to the first session establishment request message transmitted by the MME;
The second session establishment response message includes at least the APN, the PDN type, and the globally routable IP address,
The MME is
Receiving the second session establishment response message from the SGW;
Based on the reception of the second session establishment response message, a first PDN connectivity accept message is transmitted to the base station as a response to the PDN connectivity request message transmitted by the MME;
The first PDN connectivity accept message includes at least the APN, the PDN type, and the globally routable IP address;
The base station device
Receiving the first PDN connectivity accept message from the MME;
Based on the reception of the first PDN connectivity accept message, a second PDN connectivity accept message is transmitted to the terminal device;
The second PDN connectivity accept message includes at least an APN, a PDN type, and the globally routable IP address;
The terminal device
Receiving the second PDN connectivity accept message from the base station device;
Obtaining the globally routable IP address based on the transmission of the identification information;
Communications system.