WO2016208639A1 - Terminal device, gateway device, and communication control method - Google Patents

Abstract

The present invention comprises performing a control for detaching on the basis of whether a gateway device included in a WLAN access network supports a service for emergency communication, and a control for attaching to a gateway device that supports the service for emergency communication. The present invention thereby provides a communication control method, etc., for emergency communication via a WLAN access network.

Description

Terminal device, gateway device, and communication control method

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

In recent 3GPP (The 3rd Generation Partnership Project), which standardizes mobile communication systems, the specification of the EPS (Evolved Packet System) described in Non-Patent Document 1 is being realized to realize all-IP. EPS is a mobile communication system for mobile operators to provide mobile phone services, and is an EPC (Evolved Packet Core) core network or LTE (Long Term Evolution) wireless access standard based on wireless communication standards. Etc. are configured.

Furthermore, in the specification of 3GPP EPS, SEW (Study-on-System-impacts-of-IMS-emergency-sessions-over-WLAN) is being studied (Non-patent Document 1). The purpose of SEW is to organize and solve technical problems for establishing an emergency call via an access network connected using an interface other than 3GPP (for example, WLAN).

More specifically, in the SEW study, in order to communicate Emergency Call based on IMS (IP Multimedia Subsystem), an access network connected to the core network using an interface other than 3GPP (for example, WLAN) is used. A method for acquiring location information of a terminal device to be connected and a method for establishing a communication path for voice communication of an emergency call are being studied.

3GPP TR 23.771 Study On system System impacts IMS IMS emergency sessions sessions over WLAN (Release 13)

SEW does not stipulate detailed procedures for establishing an IMS Emergency Session and establishing a communication path for sending and receiving emergency call data.

More specifically, details of the procedure for establishing a PDN connection for an emergency communication service led by a terminal device via a WLAN access network have not been clarified.

The present invention has been made in view of such circumstances, and its purpose is to establish a PDN connection for an emergency communication service via a WLAN access network and a PDN connection for an emergency communication service. It is to provide a suitable means for realizing communication control using.

The terminal device of the present invention includes a control unit that starts a detach procedure for disconnecting a first PDN connection based on whether or not the first gateway device supports an emergency communication service, and a first PDN connection Is a PDN connection established via the first gateway device, and the control unit transmits a request message for establishing the second PDN connection to the second gateway device based on the completion of the detachment procedure The second PDN connection is a PDN connection for emergency communication service, and the second gateway is a gateway that supports the emergency communication service.

The gateway device of the present invention has a transmission / reception unit that receives an IKE_AUTH request message transmitted by a terminal device to establish a PDN connection. The transmission / reception unit supports an emergency communication service as a response to the IKE_AUTH request message. And transmitting an IKE_AUTH response message including at least information indicating to the terminal device.

The communication control method for a terminal device according to the present invention starts a detach procedure to disconnect a first PDN connection based on whether or not the first gateway device supports an emergency communication service, and the first PDN The connection is a PDN connection established via the first gateway device, and upon receiving the detach procedure, a request message for establishing a second PDN connection is transmitted to the second gateway device, and the second The PDN connection is an emergency communication service PDN connection, and the second gateway is a gateway that supports the emergency communication service.

According to the communication control method of the gateway device of the present invention, information indicating that the gateway device supports an emergency communication service is received as a response to the IKE_AUTH request message after receiving the IKE_AUTH request message transmitted by the terminal device to establish the PDN connection. An IKE_AUTH response message including at least the message is transmitted to the terminal device.

According to the present invention, the terminal device can establish a communication path for transmitting and receiving emergency call data.

It is a figure for demonstrating the outline of a mobile communication system. It is a figure for demonstrating the structure etc. of a mobile communication system. It is a figure for demonstrating the function structure of ePDG. It is a figure for demonstrating the structure of the memory | storage part of ePDG. It is a figure for demonstrating the function structure of UE. It is a figure for demonstrating the structure of the memory | storage part of UE. It is a figure for demonstrating the function structure of PGW. It is a figure for demonstrating the structure of the memory | storage part of PGW. It is a figure for demonstrating the procedure for establishing the communication path for emergency services. It is a figure for demonstrating the example of an attachment procedure. It is a figure for demonstrating the example of a PDN connection establishment procedure for emergency communication services. It is a figure for demonstrating the example of IMS registration procedure. It is a figure for demonstrating the example of a detaching procedure. It is a figure for demonstrating the detail of a structure of a mobile communication system.

[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.

[1.1. System overview]
FIG. 1 is a diagram for explaining an outline of a mobile communication system in the present embodiment. As shown in the figure, the mobile communication system 9 includes UE_A10 which is a terminal device, access point WLAN APb (WLAN Access Point) _A76 included in access network B (WLAN ANb) 75, and core network_A90. It consists of ePDG (Evolved Packet Data Gateway) _A65, PGW (PDN Gateway) _A30, and P-CSCF (Proxy-Call Session Control Function) _A112 included in the IMS network_A110. Here, the IMS network_A110 may be included in the PDN_A100.

Here, UE_A10 may be a terminal device, and may be UE (User Equipment), ME (Mobile Equipment), or MS (Mobile Station).

The access network B75 may be a WLAN (Wireless LAN) access network. The ePDG_A65 may be a gateway that connects the core network_A90 and the WLAN access network B75, which is connected to the PGW_A30 in the core network_A90. Further, ePDG_A65 may be a gateway that connects the core network_A90 and the UE_A10 connected to the PGW_A30 in the core network_A90 via the access network B75.

In this embodiment, UE_A10 can establish a PDN connection using the GTP / PMIPv6 transfer path between PGW_A30 and UE_A10 via access network B75. The transfer path may be a bearer.

Also, UE_A10 can establish an IMS connection between P-CSCF_A112 and UE_A10 via PDN connection via access network B75 and core network_A90.

Here, the core network_A90 may be a communication network operated by a mobile operator.

For example, the core network_A90 may be a core network for a mobile communication operator that operates and manages the mobile communication system 9, or a core for a virtual mobile communication operator such as MVNO (Mobile Virtual Network Operator). It may be a network.

MME_A40 is an MME (Mobility Management Entity), and is a control device that performs location management and access control of UE_A10 via access network A. Details of MME_A40 will be described later.

Further, SGW_A35 is an SGW (Serving Gateway), which is a gateway device between the core network_A90 and the access network A, and transfers user data between the UE_A10 and the PGW_A30.

EPDG_A65 is an ePDG (Evolved Packet Data Gateway), which is a gateway device between the core network_A90 and the access network B75. The ePDG transfers user data between the UE_A10 and the PGW_A30.

Note that a plurality of ePDGs may be included in the core network_A90. For example, ePDG_B66 different from ePDG_A65 may be arranged. Note that the configuration of ePDG_B66 may be the same as that of ePDG_A65. Further, in the core network_A90, an ePDG having an ability to provide an emergency communication service and an ePDG not having an ability to provide an emergency communication service may be arranged.

Here, the emergency communication service may be a voice communication service that has established Emergency Call (emergency call). Note that data transmission / reception for the emergency communication service may be set so that data transmission / reception is performed using the PDN connection for the emergency communication service.

PGW_A30 is a PGW (Packet Data Gateway), which is a packet data service network (PDN: Packet Data Network) gateway device that provides a communication service to UE_A 10.

In this embodiment, UE_A 10 can establish a PDN connection for emergency communication service and / or an IMS session for emergency communication service.

PDN connection for emergency communication service is used for transmission / reception of control information for establishing an IMS session for emergency communication service and / or transmission / reception of user data using an IMS session for emergency communication service PDN connection.

The IMS connection for the emergency communication service may be a connection established as user data on the PDN connection for emergency communication. Here, the emergency communication service may be a service such as an emergency call. That is, the IMS connection for the emergency communication service may be an IMS connection used for an emergency call.

Next, a configuration example of the core network_A90 will be described. FIG. 2 shows a configuration example of the communication system 9. As shown in FIG. 2, the communication system 9 may be configured by a PDN_A 100, an IP mobile communication network 5, and a UE. Further, the IP mobile communication network 5 may be configured by connecting the core network_A90 and one or a plurality of access networks. Furthermore, the core network_A90 is HSS (Home Subscriber Server) _A50, AAA (Authentication Authorization Accounting) _A55, PCRF (Policy) and Charging Rules Function) _A60, PGW_A30, ePDG (enhanced Packet Data Gateway) _A65, SGW_A35, MME_A, SG Consists of (Serving GPRS Support Node) _A45.

Also, the core network_A90 can be connected to a plurality of radio access networks (LTE AN_A80, WLAN ANB75, WLAN ANa70, UTRAN_A20, GERAN_A25).

The radio access network may be configured by a plurality of different access networks, or may be configured by any one access network. Furthermore, UE_A 10 can wirelessly connect to the radio access network.

In addition, the access networks that can be connected with the WLAN access system are the WLAN access network b (WLAN ANb) 75 that connects to the core network_A90 via ePDG_A65, and the WLAN access network a (WLAN that connects to PGW_A30, PCRF_A60, and AAA_A55) ANa) 80 can be configured.

Since each device is configured in the same manner as a conventional device in a mobile communication system using EPS, detailed description is omitted. Hereinafter, each device will be briefly described.

PGW_A30 is connected to PDN_A100, SGW_A35, ePDG_A65, WLAN ANa70, PCRF_A60 and AAA_A55, and is a relay device that transfers user data as a gateway device for PDN_A100 and core network_A90.

SGW_A35 is connected to PGW_A30, MME_A40, LTE AN_A80, SGSN_A45, and UTRAN_A20, and relay device that transfers user data as a gateway device between core network_A90 and 3GPP access networks (UTRAN_A20, GERAN_A25, LTE AN_A80) It is.

MME_A40 is connected to SGW_A35, LTE AN_A80, and HSS_A50, and is an access control device that performs location information management and access control of UE_A10 via LTE AN_A80. The core network_A90 may be configured to include a plurality of location management devices. For example, a location management device different from MME_A40 may be configured. A location management device different from MME_A40 may be connected to SGW_A35, LTE と AN_A80, and HSS_A50 in the same manner as MME_A40.

In addition, when a plurality of MMEs are included in the core network_A90, the MMEs may be connected to each other. Thereby, transmission / reception of the context of UE_A10 may be performed between MMEs.

HSS_A50 is connected to MME_A40 and AAA_A55, and is a management node that manages subscriber information. The subscriber information of HSS_A50 is referred to at the time of access control of MME_A40, for example. Further, the HSS_A50 may be connected to a location management device different from the MME_A40.

AAA_A55 is connected to PGW_A30, HSS_A50, PCRF_A60, and WLAN ANa70, and performs access control for UEs connected via WLAN ANa70.

PCRF_A60 is connected to PGW_A30, WLAN ANa75, AAA_A55, and PDN_A100, and performs QoS management for data delivery. For example, the QoS of the communication path between UE_A10 and PDN_A100 is managed.

EPDG_A65 is connected to PGW_A30 and WLAN ANB75, and delivers user data as a gateway device between core network_A90 and WLAN ANB75.

SGSN_A45 is connected to UTRAN_A20, GERAN_A25 and SGW_A35, and is a control device for location management between 3G / 2G access network (UTRAN / GERAN) and LTE access network (E-UTRAN). Furthermore, SGSN_A45 has a PGW and SGW selection function, a UE time zone management function, and an MME selection function at the time of handover to E-UTRAN.

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

In this embodiment, LTE AN_A80 may be E-UTRAN configured to include eNB_A45. eNB_A45 is a radio base station to which UE_A10 is connected in the LTE access system, and LTE-AN_A80 may include one or a plurality of radio base stations.

WLAN ANA70 is a reliable access network (Trusted Non-3GPP Access Network), and includes WLAN APa72 and TWAG_A74. WLAN APa72 is a reliable WLAN access system for operators operating the core network_A90 and is a wireless base station to which UE_A10 is connected. WLAN ANa70 is configured to include one or more wireless base stations. May be. GW74 is a gateway device for the core network_A90 and WLAN ANa70. Further, the WLAN APa72 and GW74 may be configured by a single device.

Even if the operator that operates Core Network_A90 and the operator that operates WLAN ANa70 are different, such a configuration can be realized by contracts and contracts between the operators.

Also, WLAN75ANB75 is an access network (Untrusted Non-3GPP い な い Access Network) that has not established reliability, and includes WLAN APb76. WLAN APb76 is a wireless base station to which UE_A10 is connected in the WLAN access system when a trust relationship is not established with the operator operating the core network_A90, and WLAN ANB75 is a wireless base station with one or more wireless base stations. It may be included.

In this way, the WLAN ANB75 is connected to the core network_A90 using ePDG_A65, which is a device included in the core network_A90, as a gateway. ePDG_A65 has a security function to ensure communication safety.

UTRAN_A20 includes RNC (Radio Network Controller) _A24 and eNB (UTRAN) _A22. eNB (UTRAN) _A22 is a radio base station to which UE_A10 is connected by UTRA (UMTS Terrestrial Radio Access), and UTRAN_A20 may be configured to include one or a plurality of radio base stations. The RNC_A24 is a control unit that connects the core network_A90 and the eNB (UTRAN) _A22, and the UTRAN_A20 may be configured to include one or a plurality of RNCs. The RNC_A 24 may be connected to one or a plurality of eNBs (UTRAN). Further, the RNC_A24 may be connected to a radio base station (BSS (Base Station Subsystem) _A26) included in the GERAN_A25.

GERAN_A25 includes BSS_A26. BSS_A26 is a radio base station to which UE_A10 is connected by GERA (GSM / EDGE Radio Access), and GERAN_A25 may be composed of one or a plurality of radio base stations BSS. A plurality of BSSs may be connected to each other. BSS_A26 may be connected to RNC_A24.

Further, as shown in FIG. 14 (b), the PDN_A100 includes a service network (IMS network_A110 or the like) or device to which the UE_A10 connects after establishing the PDN connection.

In this embodiment, the IMS network_A110 may be a service network that provides a voice call service. The IMS network_A110 may be configured to include the P-CSCF_A112. The IMS network_A110 may be a service network that permits an emergency communication service via the access network B75.

In this specification, UE_A10 being connected to each radio access network means being connected to a base station device, an access point, etc. included in each radio access network. Also via a base station device or access point.

[1.2 Equipment configuration]
Hereinafter, the configuration of each apparatus will be described.

[1.2.1.ePDG configuration]
First, the configuration of ePDG_A65 will be described. FIG. 3 shows the device configuration of ePDG_A65. As shown in the figure, the ePDG_A65 includes a network connection unit_A320, a control unit_A300, and a storage unit_A340. The network connection unit_A320 and the storage unit_A340 are connected to the control unit_A300 via a bus.

Control unit_A300 is a functional unit for controlling ePDG_A65. The control unit_A300 implements various processes by reading and executing various programs stored in the storage unit_A340.

The network connection unit_A320 is a data transmission / reception unit that transmits / receives user data and / or control messages, and the ePDG_A65 is a functional unit for connecting to the PGW_A30 and / or UE_A10 and / or AAA_A55 and / or WLAN_APb76. The network connection unit_A320 may include a transmission unit and a reception unit.

Storage unit_A340 is a functional unit that stores programs and data necessary for each operation of ePDG_A65. The storage unit_A340 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.

As shown in FIG. 3, the storage unit_A340 stores ePDG emergency capability_A342, emergency number list_A344, emergency configuration Data_A346, and EPS bearer context_A348. Hereinafter, the information elements stored in the storage unit_A340 will be described. The EPS bearer context_A348 is classified into an EPS bearer context for each PDN connection and an EPS bearer context for each transfer path and / or bearer.

FIG. 4 shows information elements stored in the storage unit_A340. FIG. 4 (a) shows ePDG emergency capability_A342. The ePDG emergency capability_A342 may include at least an ePDG ID and Emergency capability.

Here, the ePDG ID may be information for identifying ePDG_A65. That is, the ePDG ID may be identification information for identifying the own device.

Emergency capacity may be identification information indicating whether the ePDG supports an emergency communication service. More specifically, it may be identification information indicating whether PDN connection establishment for emergency communication is supported for each ePDG. In other words, Emergency capability may be identification information indicating whether or not an emergency communication service is supported for each ePDG. More specifically, for example, Emergency capability may include “allowed” or “Not allowed”. Further, Emergency capability may be Emergency number list.

Thus, Emergency capability may be capability information that supports emergency communication services. The ePDG_A65 may store Emergency capability as “allowed” when supporting the emergency communication service, and may store “Not allowed” when the emergency communication service is not supported.

Alternatively, Emergency capability may be information stored when supporting an emergency communication service. That is, it may be set to identify whether or not the emergency communication service is supported depending on the presence or absence of emergency capability. For example, the ePDG_A65 may store the emergency capacity when supporting the emergency communication service, and may not store the emergency capacity when not supporting the emergency communication service.

Note that Emergency capability may be associated with an ePDG ID that identifies ePDG_A65.

As described above, the ePDG emergency capability_A342 may be identification information indicating that the ePDG_A65 has the ability to establish a PDN connection for emergency communication. In other words, the presence of ePDGeemergency capability_A342 in the storage unit_A340 of ePDG_A65 may mean that ePDG_A65 has a function of establishing a PDN connection for emergency communication.

In other words, ePDG emergency capability_A342 may be identification information indicating that ePDG_A65 supports an emergency communication service. That is, the presence of ePDG emergency capability_A342 in the storage unit_A340 of the ePDG_A65 may mean that the ePDG_A65 supports the emergency communication service.

Figure 4 (b) shows Emergency number list_A344. Emergency number list_A344 may include at least Emergency number list.

“Emergency number” list is a list containing valid Emergency number for Emergency Call. Emergency number in Emergency number list may be a telephone number for an emergency call, or may be information for identifying a server that provides an emergency communication service. In other words, Emergency number may include identification information of one or more ePDGs having the ability to provide emergency communication services.

EPDG “emergency” capability_A342 and Emergency “number” list_A344 may be included in the EPS bearer context or may be information independent of the EPS bearer context. That is, ePDG_A65 may store ePDG emergency capability_A342 and Emergency number list_A344 in the EPS bearer context, or may store ePDG emergency capability_A342 and Emergency number list_A344 independently from the EPS bearer context.

Figure 4 (c) shows Emergency Configuration Data_A346. Emergency Configuration Data_A346 may include at least Emergency APN (Access Point Name) and / or Emergency QoS profile and / or Emergency APN-AMBR and / or Emergency PGW ID and / or 3GPP HO Emergency PGW ID.

Emergency APN may be information indicating an APN used for establishing a PDN connection for emergency communication. Here, APN is information associated with a PDN that is a service and / or a service network. In other words, the PDN can be identified using the APN. Therefore, the APN is identification information that can select the PGW that connects the PDN and the core network.

The Emergency QoS profile may be information indicating the QoS of the default bearer of the PDN connection established by the Emergency APN.

Emergency APN-AMBR may be information indicating the maximum bit rate shared by all non-GBR bearers connected to EmergencyEAPN.

Emergency PGW ID is information that identifies the PGW used for Emergency APN. The Emergency PGW ID may be an FQDN or an IP address.

3GPP HO Emergency PGW ID is information that identifies the PGW used for Emergency APN when PLMN supports handover from non-3GPP access to 3GPP access. The 3GPP HO Emergency PGW ID may be an FQDN or an IP address.

Fig. 4 (d) shows the EPS bearer context for each PDN connection. The EPS bearer context for each PDN connection may include an APN “Use”, an ePDG “MAC” address, and a User “Plane” connection “ID”.

“APN in Use” indicates the APN used to establish this PDN connection. Here, the APN may be a label indicating an access destination of the network in accordance with a DNS naming rule. Further, APN in Use may be an APN indicated by Emergency APN.

EPDG MAC address is the physical address of ePDG_A65.

User plane connection ID is identification information for identifying a connection used for transmitting user data when a UE establishes a transfer path via ePDG_A65.

Fig. 4 (e) shows an example of EPS bearer context for each transfer path and / or bearer. The EPS bearer context for each transfer path and / or bearer may include at least transfer path identification information.

Transfer path identification information is information for identifying a transfer path and / or bearer. The transfer path identification information may be an EPS bearer ID, for example.

Also, the transfer path identification information may be associated with TFT (Traffic Flow Template). The TFT may be communication flow identification information.

The configuration of ePDG_A65 has been described above, but when the core network_A90 includes a plurality of ePDGs, the configuration of these ePDGs may be the same as the configuration of ePDG_A65. For example, when the core network_A90 is configured to include ePDG_B66 different from ePDG_A65, the configuration of ePDG_B66 may be the same as the configuration of ePDG_A65.

[1.2.2.UE configuration]
Next, the configuration of UE_A10 will be described. FIG. 5 shows a device configuration of UE_A10. As shown in the figure, the UE_A 10 includes an LTE interface unit_A520, a WLAN interface unit_A540, a control unit_A500, and a storage unit_A550.

The LTE interface unit _A520, the WLAN interface unit _A540, and the storage unit _A550 are connected to the control unit _A500 via a bus.

Control unit_A500 is a functional unit for controlling UE_A10. The control unit_A500 realizes various processes by reading and executing various programs stored in the storage unit_A550.

The LTE interface unit_A520 is a data transmission / reception unit that transmits and receives user data and / or control messages, and is a functional unit for the UE_A10 to connect to the LTE base station and to connect to the IP access network. An external antenna 510 is connected to the LTE interface unit_A520. The LTE interface unit_A520 may include a transmission unit and a reception unit.

WLAN interface unit_A540 is a data transmission / reception unit that transmits and receives user data and / or control messages, and is a functional unit for UE_A10 to connect to a WLAN AP and connect to an IP access network. An external antenna 530 is connected to the WLAN interface unit_A540. The WLAN interface unit_A540 may include a transmission unit and a reception unit.

Control unit_A500 is a functional unit for controlling UE_A10. The control unit_A500 realizes various processes by reading and executing various programs stored in the storage unit_A550.

The storage unit 550 is a functional unit that stores programs, data, and the like necessary for each operation of the UE_A10. The storage unit_A550 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.

As shown in FIG. 5, the storage unit_A550 stores ePDG emergency capability_A552, Emergency number list_A554, and UE context_A556. Hereinafter, the information elements stored in the storage unit_A550 will be described. UE context_A556 is classified into a UE context for each UE, a UE context for each PDN connection, and a UE context for each transfer path and / or bearer.

FIG. 6 shows information elements stored in the storage unit_A550. FIG. 6 (a) shows ePDG emergency capability_A552. The ePDG emergency capability_A552 may be composed of at least an ePDGmerID and Emergency capability.

Here, the ePDG ID may be information for identifying ePDG_A65.

Emergency capacity may be identification information indicating whether or not PDN connection establishment for emergency communication is supported for each ePDG. In other words, Emergency capability may be identification information indicating whether or not an emergency communication service is supported for each ePDG. Alternatively, it may be identification information indicating whether or not the ePDG supports a function for an emergency communication service. More specifically, for example, Emergency capability may include “allowed” or “Not allowed”. Further, Emergency capability may be Emergency number list.

Note that Emergency capability may be associated with an ePDG ID that identifies ePDG_A65.

EPDG emergency capability_A552 may be used as UE function identification information indicating that UE_A10 has the ability to establish a PDN connection for emergency communication via ePDG_A65. In other words, the presence of ePDG emergency capability_A552 in the storage unit_A550 of UE_A10 means that UE_A10 has a function to establish a PDN connection for emergency communication via ePDG_A65 identified by ePDG ID Good.

In other words, ePDG emergency capability_A552 may be identification information indicating that UE_A10 supports an emergency communication service via a WLAN network. That is, the presence of ePDGAemergency capability_A552 in the storage unit_A550 of UE_A10 may mean that UE_A10 supports the emergency communication service via ePDG_A65 identified by the ePDG ID.

In other words, UE_A10 may establish an IMS connection for an emergency communication service via ePDG_A65 identified by the ePDG_ID when ePDG_emergency_capability_A552 exists in storage unit_A550 of UE_A10.

Figure 6 (b) shows Emergency number list_A554. Emergency number list_A554 may include at least Emergencymernumber list.

“Emergency number” list is a list containing valid Emergency number for Emergency Call. Emergency number in Emergency number list may be information that is valid only in the country where UE_A10 is located when Emergency_number list is received. Emergency number may be a telephone number for an emergency call or may be information for identifying a server that provides an emergency communication service.

UE_A10 may use Emergency number in Emergency number list_A554 to establish an IMS connection for emergency communication service.

In other words, UE_A 10 may establish an IMS connection for emergency communication service using Emergency number in Emergency number list_A554.

EPDG emergency capability_A552 and Emergency number list_A554 may be included in the UE context or may be information independent of the UE context.

In other words, UE_A10 may store ePDG emergency capability_A552 and Emergency number list_A554 in the UE context, or may store ePDG emergency capability_A552 and Emergency number list_A554 independently from the UE context.

Fig. 6 (c) shows an example of the UE context stored for each UE. The UE context for each UE may include IMSI, EMM State, GUTI, and ME Identity.

IMSI is identification information assigned to users (subscribers) who use UE_A10.

EMMM State indicates the mobility management state of UE_A10. For example, EMM-REGISTERED (registered state, registered state) in which UE_A10 is registered in the network, or EMM-DEREGISTERD (unregistered state, deregistered state) in which UE_A10 is not registered in the network may be used.

GUTI is an abbreviation for Globally Unique Unique Temporary Identity and is temporary identification information of UE_A10. GUTI includes MME_A40 identification information (GUMMEI: Globally Unique MME Identifier) and UE_A10 identification information (M-TMSI) in a specific MME_A40.

ME Identity is the ID of ME, and may be, for example, IMEI / IMISV.

Fig. 6 (d) shows an example of the UE context for each PDN connection. The UE context for each PDN connection may include at least APN Use, IP address, Default Bearer, and WLAN offload ability.

APN in Use is the APN used by UE_A10 to establish this PDN connection. The APN may include network identification information and default operator identification information.

IP Address is an IP address assigned to UE_A10 by PDN connection, and may be an IPv4 address or an IPv6 prefix.

Default Bearer is EPS bearer identification information that identifies the default bearer in this PDN connection.

WLAN offloadability indicates whether communication associated with the PDN connection is allowed to be offloaded to the WLAN using the interworking function between the WLAN and 3GPP, or whether to maintain 3GPP access. Load permission information.

Fig. 6 (e) shows the UE context for each bearer. The UE context for each bearer may include at least transfer path identification information.

Transfer path identification information is information for identifying a transfer path and / or bearer. The transfer path identification information may be an EPS bearer ID, for example.

Also, the transfer path identification information may be associated with identification information of a flow transmitted and received by UE_A 10 such as TFT (Traffic Flow Template).

[1.2.3.PGW components]
Next, components of PGW_A30 will be described. FIG. 7 shows the device configuration of PGW_A30. As shown in the figure, the PGW_A30 includes a network connection unit_A720, a control unit_A700, and a storage unit_A740. The network connection unit_A720 and the storage unit_A740 are connected to the control unit_A700 via a bus.

Control unit_A700 is a functional unit for controlling PGW_A30. The control unit_A700 implements various processes by reading and executing various programs stored in the storage unit_A740.

The network connection unit_A720 is a data transmission / reception unit that transmits and receives user data and / or control messages. The PGW_A30 is a functional unit for connecting the SGW_A35 and / or PCRF_A60 and / or ePDG_A65 and / or AAA_A55 and / or TWAG_A74. The network connection unit_A720 may include a transmission unit and a reception unit.

Storage unit_A740 is a functional unit that stores programs and data necessary for each operation of PGW_A30. The storage unit_A740 includes, for example, a semiconductor memory, a HDD (Hard Disk Drive), or the like.

The storage unit_A740 stores the EPS bearer context_A742 as shown in the figure. Some EPS bearer contexts are stored for each UE, stored for each APN, stored for each PDN connection, and stored for each transfer path and / or bearer. included.

As shown in FIG. 7, the storage unit_A740 stores the EPS bearer context_A742. Hereinafter, information elements stored in the storage unit_A740 will be described. The EPS bearer context_A 742 is classified into an EPS bearer context for each UE, an EPS bearer context for each PDN connection, and an EPS bearer context for each transfer path and / or bearer.

FIG. 8 shows information elements stored in the storage unit_A740. FIG. 8 (a) shows an example of an EPS bearer context for each UE. The EPS bearer context may include at least IMSI, ME Identity, and MSISDN. IMSI is information for identifying the user of UE_A10. ME Identity is the ID of ME, and may be, for example, IMEI / IMISV. MSISDN represents the telephone number of UE_A10.

Fig. 8 (b) shows an example of an EPS bearer context for each PDN connection. The EPS bearer context for each PDN connection may include at least IP address, PDN type, and APN in use.

IP Address indicates the IP address to which UE_A10 is assigned for this PDN connection. The IP address may be an IPv4 and / or IPv6 prefix.

PDN type indicates the type of IP address. PDN type indicates, for example, IPv4, IPv6, or IPv4v6.

“APN in Use” indicates the APN used to establish this PDN connection. Here, the APN may be a label indicating an access destination of the network in accordance with a DNS naming rule.

Fig. 8 (c) shows an example of EPS bearer context for each transfer path and / or bearer. The EPS bearer context for each transfer path and / or bearer may include at least transfer path identification information.

Transfer path identification information is information for identifying a transfer path and / or bearer. The transfer path identification information may be an EPS bearer ID, for example. The transfer path identification information may be associated with the TFT.

[1.3. Explanation of processing]
An outline of the emergency service communication path establishment procedure will be described with reference to FIG. The communication path establishment procedure for emergency service in the present embodiment includes an attach procedure (S902), a trigger detection process (S904), a detach procedure (S906), a PDN connection establishment procedure (S908) for emergency communication, IMS registration procedure (S910) may be configured.

Here, the detach procedure (S906) and / or the PDN connection establishment procedure (S908) for emergency communication can be omitted depending on the conditions. Details of the conditions under which each procedure is executed and the processing will be described below.

First, UE_A10 executes an attach procedure for establishing a PDN connection with core network_A90 via access network B75 (S902). Thereby, UE_A10 connects to core network_A90 via access network B75.

More specifically, UE_A10 establishes a PDN connection with PGW_A30 arranged in core network_A90 via ePDG_A65. Although details of the attach procedure will be described later, the PDN connection established by this attach procedure does not have to be a PDN connection for the emergency communication service. That is, a PDN connection may be established using an APN for performing general voice communication, an APN for connecting to the Internet, or the like.

Note that UE_A10 may acquire ePDGPDemergency capability_A342 and / or Emergency number list_A344 from ePDG_A65 based on the attach procedure.

Next, UE_A10 detects a trigger for performing emergency communication (S904). Specifically, the detection process is executed. In the trigger UE_A10 detection process, UE_A10 may trigger an application level event such as making an emergency call by a user operation.

Based on trigger detection, UE_A10 may execute ePDG selection processing. UE_A10 selects an ePDG that can establish a PDN connection for an emergency communication service by an ePDG selection process.

Note that the UE_A 10 does not have to execute the ePDG selection process when detecting that the ePDG_A 65 connected based on the attach procedure has the ability to establish a PDN connection for the emergency communication service.

Here, UE_A10 determines whether ePDG_A65 connected based on the attach procedure has the ability to establish a PDN connection for the emergency communication service, whether ePDGPDemergency capability_A342 and / or Emergency number obtained from ePDG_A65 based on the attach procedure. You may determine based on list_A344.

Alternatively, the UE_A 10 determines whether the ePDG_A65 connected based on the attach procedure has the ability to establish a PDN connection for the emergency communication service, whether the ePDG emergency capability_A342 and / or Emergency number list_A344 acquired from the ePDG_A65 based on the attach procedure. Instead, the determination may be made based on a list of ePDGs set in advance in UE_A10. Here, the ePDG list set in advance in UE_A10 may be information in which ePDG identification information is associated with capability information having the capability of ePDG_A65 to establish a PDN connection for an emergency communication service.

Furthermore, if the ePDG_A65 connected based on the attach procedure has the ability to establish a PDN connection for the emergency communication service, the UE_A 10 does not execute the detach procedure (S906), and the PDN connection for the emergency communication service The establishment procedure (S908) may be executed.

On the other hand, when it is detected that ePDG_A65 connected in the attach procedure (S902) does not have the ability to establish a PDN connection for the emergency communication service, ePDG selection processing may be executed. UE_A10 may select an ePDG having the ability to establish a PDN connection for emergency communication services listed in EmergencyEnumber list_A344 in the ePDG selection process.

In this way, the ePDG reselects and / or detaches the ePDG (S906) based on the fact that the ePDG connected in the attach procedure (S902) does not have the ability to establish a PDN connection for the emergency communication service. May be executed.

Or, even if the ePDG_A65 connected in the attach procedure (S902) has the ability to establish a PDN connection for emergency communication service, the UE_A10 executes the ePDG selection process based on the detection of the trigger. Also good. In this case, UE_A10 selects ePDG_A65 connected in the attach procedure (S902). Furthermore, when the ePDG selected in the ePDG selection process is the ePDG connected in the attach procedure (S902), UE_A10 performs the PDN connection for the emergency communication service without executing the detach procedure (S906). The establishment procedure (S908) may be executed.

Note that, based on the completion of the detach procedure (S906), the UE_A 10 may start the PDN connection establishment procedure (S908) for the emergency communication service. In the PDN connection establishment procedure for the emergency communication service, UE_A10 establishes a PDN connection via ePDG that can establish a PDN connection for the emergency communication service.

Furthermore, UE_A10 may start the IMS registration procedure based on the completion of the PDN connection establishment procedure (S908) for the emergency communication service (S910).

UE_A10 does not execute the detach procedure (S906) and the PDN connection establishment procedure (S908) for the emergency communication service when the PDN connection established by the attach procedure can be used for the emergency communication service. The IMS registration procedure (S910) may be executed.

Hereinafter, specific examples of the attach procedure (S902) and the detach procedure (S906), the PDN connection establishment procedure (S908) and the IMS registration procedure (S910) for emergency communication will be described.

[1.3.1. Attaching procedure example]
An example of the attachment procedure will be described with reference to FIG.

UE_A10 first executes an IKE_SA_INIT procedure for initializing a security association procedure based on IKEv2 with the core network_A90 (S1002).

More specifically, the UE_A 10 executes an encryption algorithm agreement and encryption key sharing between the ePDG_A 65 serving as a gateway between the access network B75 and the core network_A 90.

UE_A10 starts an attach procedure to establish a PDN connection with the core network_A90 via the access network B75 based on the initialization of the security association procedure. More specifically, UE_A10 establishes a PDN connection with PGW_A30 arranged in core network_A90 via ePDG_A65.

Specifically, UE_A10 transmits an IKE_AUTH request (IKE_AUTH Request) to ePDG_A65 (S1004). The UE_A 10 may transmit at least the configuration payload (Configuration Payload) and / or the APN (Access Point Name) and / or the attach type (attach type) in the IKE_AUTH request.

In this way, the IKE_AUTH request may be a request message for requesting establishment of a PDN connection.

Here, the configuration payload may be a payload including information on an IP address requested by the UE. Specifically, the UE_A 10 may include information indicating that an IPv4 IP address is desired or information indicating that an IPv6 IP address is desired in the configuration payload. Further, when both the IPv4 and IPv6 IP addresses are desired, UE_A10 may transmit the IPv4 configuration payload and the IPv6 configuration payload by including them in the IKE_AUTH request.

The APN may be a label indicating the network access destination according to the DNS naming rules. When the default APN is used, the UE_A 10 does not have to include the APN in the IKE_AUTH request.

The attach type may be information for identifying the type of attach procedure requested. For example, since UE_A10 performs initial connection with ePDG_A65, the attachment type may be Initial Attach.

EPDG_A65 receives the IKE_AUTH request sent by UE_A10. The ePDG_A65 selects a PGW for establishing a PDN connection based on the reception of the IKE_AUTH request and / or the APN included in the IKE_AUTH request. When the APN is not included in the IKE_AUTH request, the ePDG_A65 may select the PGW_A30 using the held default APN. Further, when the APN included in the IKE_AUTH request is not valid, the ePDG_A65 may select the PGW_A30 using the held default APN.

EPDG_A65 transmits a session generation request to PGW_A30 based on the selection of the PGW establishing the PDN connection (S1006). The ePDG may include the APN in the session creation request.

PGW_A30 receives the session creation request sent by ePDG_A65. PGW_A30 may assign the IP address of UE_A10 based on the reception of the session generation request.

PGW_A30 transmits a session generation response to ePDG_A65 based on the assignment of the IP address of UE_A10 (S1008). The PGW_A 30 may transmit the PDN address (PDN Address) and / or transfer path identification information included in the session generation response.

Here, the PDN address may be an IP address assigned to UE_A10. For example, it may be an IPv4 address, and may be an IPv6 prefix and an interface ID for constructing an IPv6 address. Here, PGW_A30 may assign the IP address of UE_A10. Furthermore, PGW_A30 may include the IP address assigned to UE_A10 in the PDN address.

Transfer path identification information is information for identifying a transfer path. The transfer path identification information may be bearer identification information for identifying a default bearer.

EPDG_A65 receives the session creation response sent by PGW_A30. The ePDG_A65 transmits an IKE_AUTH response (IKE_AUTH Response) to the UE_A10 based on the reception of the session generation response (S1010). The ePDG_A65 may transmit at least the configuration payload (Configuration Payload) and / or APN (Access Point Name) in the IKE_AUTH response.

Thus, the IKE_AUTH response is a response to a request message requesting establishment of a PDN connection, and may be an acceptance message indicating that the establishment of a PDN connection has been accepted.

Here, the configuration payload may be a payload in which the IP address assigned to UE_A is entered. In other words, the configuration payload may include a PDN address. Specifically, ePDG_A65 may include an IPv4 address in the configuration payload, may include an IPv6 prefix and an interface ID for constructing an IPv6 address, or include only an interface ID for constructing an IPv6 address. May be. Also, when the IP address assigned to UE_A10 includes both IPv4 and IPv6, ePDG_A65 may transmit the configuration payload for IPv4 and the configuration payload for IPv6 in the IKE_AUTH request.

The APN may be an APN used for establishing a PDN connection.

EPDG_A65 may also send information indicating the completion of establishment of the IPSec tunnel with UE_A10 in the IKE_AUTH response.

Furthermore, ePDG_A65 may transmit the first identification information and / or the second identification information included in the IKE_AUTH response.

Here, the first identification information may be ePDG emergency capability_A342 indicating whether the ePDG_A65 supports establishment of a PDN connection for emergency communication.

The second identification information may be Emergency number list_A344.

Alternatively, only when ePDG_A65 supports the establishment of a PDN connection for emergency communication, ePDG_A65 may send an IKE_AUTH response including the first identification information. Therefore, the first identification information may be information indicating that ePDG_A65 supports establishment of a PDN connection for emergency communication.

Furthermore, ePDG_A65 may send an IKE_AUTH response including the second identification information only when ePDG_A65 supports PDN connection establishment for emergency communication. Therefore, the second identification information is information indicating that PDN connection establishment for emergency communication is supported, and includes identification information of ePDG_A65 that supports PDN connection establishment for emergency communication. Information.

UE_A10 receives the IKE_AUTH response sent by ePDG_A65. Based on the reception of the IKE_AUTH response and / or the reception of information indicating the completion of the establishment of the IPSec tunnel between UE_A10 and ePDG_A65, UE_A10 may confirm the establishment of the IPSec tunnel between UE_A10 and ePDG (S1012). That is, a PDN connection may be established based on the fact that UE_A10 has received an IKE_AUTH response and / or has received information indicating the completion of establishment of an IPSec tunnel between UE_A10 and ePDG_A65.

As described above, the UE_A 10 can acquire the first identification information and / or the second identification information based on the reception of the IKE_AUTH response.

Thereby, the UE_A 10 can obtain information indicating whether the connected ePDG can establish a PDN connection for emergency communication. Furthermore, the UE_A 10 can acquire information on the ePDG that can establish a PDN connection for emergency communication that is different from the connected ePDG.

UE Upon completion of the attach procedure, UE_A10 and PGW_A30 establish a PDN connection.

[1.3.2. Detachment procedure example]
An example of the detaching procedure will be described with reference to FIG.

UE_A10 transmits a detach request message to ePDG_A65 (S2102), and receives a detach response as a response to the detach request message (S2110). If the request is accepted, the detach response may be a detach accept message.

UE_A10 disconnects the PDN connection established with PGW_A30 via ePDG_A65 based on the reception of the detach accept message.

Note that the ePDG_A65 transmits a session deletion request to the PGW_A30 based on the reception of the detach request (S2104). Further, the ePDG_A65 receives a session deletion response transmitted by the PGW_A30 as a response to the session deletion request (S2108). ePDG_A65 may transmit a detach response to UE_A10 based on reception of the session deletion response.

Also, PGW_A30 may execute an IP-CAN session update procedure with PCRF_A60 based on the reception of the session deletion request (S2106). Furthermore, PGW_A30 may transmit a session deletion response to ePGD_A65 based on the completion of the IP-CAN session update procedure.

Thus, UE_A10 may transmit a detach request message in order to disconnect the connection to ePDG_A65.

Alternatively, UE_A10 may send a detach request message to disconnect the PDN connection established via ePDG_A65. For example, when a plurality of PDN connections are established via ePDG_A65, UE_A10 transmits a detach request message for each PDN connection, deletes the PDN connection every time a detach response message is received, and finally ePDG_A65 You may delete all PDN connections via.

Thus, the detach request message may be a request message for deleting a single PDN connection, and the detach response message may be a response message indicating that a single PDN connection has been deleted.

Note that the above-described detach request message and detach response message may be control messages based on IKE. More specifically, the detach request message may be an IKE_INFOMATIONAL request message. Further, UE_A 10 may include information requesting deactivation of the PDN connection or information requesting detachment in the IKE_INFOMATIONAL request message.

Also, the detach response message may be an IKE_INFOMATIONAL request message. The ePDG_A65 may include information requesting deactivation of the PDN connection or information requesting detachment in the detach response message.

[1.3.3. PDN connection establishment procedure example for emergency communication]
An example of a PDN connection establishment procedure for emergency communication will be described with reference to FIG.

UE_A10 first executes an IKE_SA_INIT procedure for initializing a security association procedure based on IKEv2 with core network_A90 (S1102).

More specifically, the UE_A 10 executes an encryption algorithm agreement and encryption key sharing with the ePDG_A 65 that plays the role of the gateway between the access network B75 and the core network_A90.

Note that UE_A10 may be set not to execute the IKE_SA_INIT procedure (S1102) when the detach procedure is not performed.

Next, an attach procedure is started to establish a PDN connection with the core network_A90 via the access network B75. More specifically, UE_A10 establishes a PDN connection with PGW_A30 arranged in core network_A90 via ePDG_A65.

Specifically, UE_A10 transmits an IKE_AUTH request (IKE_AUTH Request) to ePDG_A65 (S1104). The UE_A 10 may transmit at least the configuration payload (Configuration Payload) and / or the APN (Access Point Name) and / or the attach type (attach type) in the IKE_AUTH request.

In this way, the IKE_AUTH request may be a request message for requesting establishment of a PDN connection.

Here, the configuration payload may be a payload including information on an IP address requested by the UE. Specifically, the UE_A 10 may include information indicating that an IPv4 IP address is desired or information indicating that an IPv6 IP address is desired in the configuration payload. Further, when both the IPv4 and IPv6 IP addresses are desired, UE_A10 may transmit the IPv4 configuration payload and the IPv6 configuration payload by including them in the IKE_AUTH request.

The APN may be a label indicating the network access destination according to the DNS naming rules. When the default APN is used, the UE_A 10 does not have to include the APN in the IKE_AUTH request.

The attach type may be information for identifying the type of attach procedure requested. For example, UE_A10 may include information indicating that a PDN connection for emergency communication is established in the attach type. More specifically, UE_A10 may represent requesting establishment of a PDN connection for emergency communication by including EPS emergency attach in the attach type.

Furthermore, UE_A10 may transmit at least the third identification information included in the IKE_AUTH request.

Here, the third identification information may be Emergency Indication indicating that a PDN connection for emergency communication is established. UE_A10 may transmit the IKE_AUTH request including the third identification information in the attach type included in the IKE_AUTH request, or may transmit the IKE_AUTH request separately from the attach type.

EPDG_A65 receives the IKE_AUTH request sent by UE_A10. The ePDG_A65 selects the PGW_A30 that establishes the PDN connection based on the reception of the IKE_AUTH request and / or the attach type and / or the third identification information included in the IKE_AUTH request. Regardless of whether or not the IKE_AUTH request includes an APN, the ePDG_A65 may select the PGW_A30 using the held Emergency APN based on the attachment type and / or the third identification information included in the IKE_AUTH request.

EPDG_A65 transmits a session generation request to PGW_A30 based on the selection of PGW_A30 for establishing a PDN connection (S1106). The ePDG may include at least Emergency APN in the session creation request.

Here, Emergency APN may be information indicating an APN used for establishing a PDN connection for emergency communication.

In addition, the APN may be a label indicating a network access destination according to the DNS naming rules.

PGW_A30 receives the session creation request sent by ePDG_A65. PGW_A30 may assign the IP address of UE_A10 based on the reception of the session generation request.

PGW_A30 transmits a session generation response to ePDG_A65 based on the assignment of the IP address of UE_A10 (S1108). The PGW_A 30 may transmit the PDN address (PDN Address) and / or the transfer path identification information included in the session generation response.

Here, the PDN address may be an IP address assigned to UE_A10. For example, it may be an IPv4 address, and may be an IPv6 prefix and an interface ID for constructing an IPv6 address. Here, PGW_A30 may assign the IP address of UE_A10. Furthermore, PGW_A30 may include the IP address assigned to UE_A10 in the PDN address.

Transfer path identification information is information for identifying a transfer path. The transfer path identification information may be bearer identification information for identifying a default bearer.

EPDG_A65 receives the session creation response sent by PGW_A30. The ePDG_A65 transmits an IKE_AUTH response (IKE_AUTH Response) to the UE_A10 based on the reception of the session generation response (S1110). The ePDG_A65 may transmit at least the configuration payload (Configuration Payload) and / or APN (Access Point Name) in the IKE_AUTH response.

Thus, the IKE_AUTH response is a response to a request message requesting establishment of a PDN connection, and may be an acceptance message indicating that the establishment of a PDN connection has been accepted.

Here, the configuration payload may be a payload in which the IP address assigned to UE_A is entered. In other words, the configuration payload may include a PDN address. Specifically, ePDG_A65 may include an IPv4 address in the configuration payload, may include an IPv6 prefix and an interface ID for constructing an IPv6 address, or include only an interface ID for constructing an IPv6 address. May be. Also, when the IP address assigned to UE_A10 includes both IPv4 and IPv6, ePDG_A65 may transmit the configuration payload for IPv4 and the configuration payload for IPv6 in the IKE_AUTH request.

The APN may be an APN used for establishing a PDN connection. As a specific example, ePDG_A65 may include EmergencyEAPN in the IKE_AUTH response.

EPDG_A65 may also send information indicating the completion of establishment of the IPSec tunnel with UE_A10 in the IKE_AUTH response.

Furthermore, ePDG_A65 may transmit the first identification information and / or the second identification information included in the IKE_AUTH response.

Here, the first identification information may be ePDG emergency capability_A342 indicating whether the ePDG_A65 supports establishment of a PDN connection for emergency communication.

The second identification information may be Emergency number list_A344.

Alternatively, only when ePDG_A65 supports the establishment of a PDN connection for emergency communication, ePDG_A65 may send an IKE_AUTH response including the first identification information. Therefore, the first identification information may be information indicating that ePDG_A65 supports establishment of a PDN connection for emergency communication.

Furthermore, ePDG_A65 may send an IKE_AUTH response including the second identification information only when ePDG_A65 supports PDN connection establishment for emergency communication. Therefore, the second identification information is information indicating that PDN connection establishment for emergency communication is supported, and includes identification information of ePDG_A65 that supports PDN connection establishment for emergency communication. Information.

UE_A10 receives the IKE_AUTH response sent by ePDG_A65. Based on the reception of the IKE_AUTH response and / or the reception of information indicating the completion of the establishment of the IPSec tunnel between UE_A10 and ePDG_A65, UE_A10 may confirm that the IPSec tunnel between UE_A10 and ePDG has been established (S1012). . In other words, based on the fact that UE_A10 has received an IKE_AUTH response and / or has received information indicating the completion of establishment of an IPSec tunnel between UE_A10 and ePDG_A65 and / or has received first identification information and / or second identification information, A PDN connection for communication may be established.

に よ り Upon completion of the attach procedure, UE_A10 and PGW_A30 establish a PDN connection for emergency communication.

In the above example of the procedure for establishing a PDN connection for emergency communication, UE_A10 explained an example in which the PDN connection is established by sending an IKE_AUTH request to ePDG_A65, but ePDG_A65 is a PDN connection for emergency communication service. If UE_A10 selects an ePDG that is different from ePDG_A65 in the ePDG selection process, UE_A10 does not respond to ePDG_A65 but to ePDG selected in the ePDG selection process. Send a IKE_AUTH request to establish a PDN connection.

For example, when UE_A10 selects ePGD_B66 as an ePDG having the capability of establishing a PDN connection for emergency communication service in the ePDG selection process, UE_A10 transmits an IKE_AUTH request to ePDG_A65 to establish a PDN connection.

The details of the procedure in that case may be the procedure and processing in which ePDG_A65 is replaced with ePDG_B66 in the example of the procedure for establishing a PDN connection for emergency communication already described. Therefore, detailed description is omitted.

In this way, UE_A10 establishes a PDN connection for emergency communication service with PGE_A30 via ePDG having the ability to establish a PDN connection for emergency communication service through a PDN connection establishment procedure for emergency communication. Can be established.

[1.3.4. IMS registration procedure example]
An example of the IMS registration procedure will be described with reference to FIG.

UE_A10 transmits SIP registration (SIP Register) to IMS network_A110 based on the establishment of the PDN connection for emergency communication (S1202). More specifically, the UE_A 10 receives the IKE_AUTH response during the PDN connection establishment procedure for emergency communication and / or the reception of information indicating the completion of the establishment of the IPSec tunnel between the UE_A 10 and the ePDG_A 65 and / or the first identification information and / or the first identification information. Based on the reception of the identification information of 2, the SIP registration is transmitted to P-CSCF_A112. UE_A10 may transmit the SIP registration including the third identification information. Also, based on the selection of ePDG_A65 and / or the determination of whether to execute the PDN connection establishment procedure for emergency communication, UE_A10 may transmit the SIP identification including the third identification information.

Here, the first identification information may be an ePDG emergency capability indicating whether the ePDG_A65 supports establishment of a PDN connection for emergency communication.

The second identification information may be an Emergency number list that is a list containing a valid Emergency number for Emergency Call. Note that the ePDG_A65 may transmit the second identification information included in the IKE_AUTH response only when the PDN connection establishment for emergency communication is supported. That is, ePDG_A65 may indicate that the PDN connection establishment for emergency communication is supported by including the second identification information in the IKE_AUTH response. In other words, the first identification information may be the second identification information.

Further, the third identification information may be Emergency Indication indicating that a PDN connection for emergency communication is established. UE_A10 may transmit the IKE_AUTH request including the third identification information in the attach type in the IKE_AUTH request, or may transmit the IKE_AUTH request separately from the attach type.

P-CSCF_A112 receives the SIP registration sent by UE_A10. The P-CSCF_A 112 transmits 200 OK to the UE_A 10 based on the reception of the SIP registration and / or the reception of the third identification information included in the SIP registration (S1204).

UE_A10 receives 200 OK sent by P-CSCF_A112. UE_A10 completes the IMS registration procedure based on the reception of 200 OK.

Upon completion of the IMS registration procedure, UE_A10 is registered with IMS network_A110. More specifically, upon completion of the IMS registration procedure, UE_A10 is registered in IMS network_A110 via P-CSCF_A112 as a UE that requests use of the emergency communication service. UE_A10 may start the IMS connection procedure for the emergency communication service based on the completion of the IMS registration procedure.

More specifically, UE_A10 sends a SIP Invite message to IMS network_A110 using a PDN connection for emergency communication to make an emergency call, and receives 200 OK as a response to the SIP Invite message. An IMS session for emergency calls may be established.

Note that UE_A 10 may include information for identifying an emergency call in a SIP Invite message for making an emergency call.

Note that the user can make a voice call through an IMS session. In other words, UE_A10 can transmit and receive voice call data of an emergency call using an IMS session. Furthermore, UE_A10 can transmit and receive voice call data of an emergency call using an IMS session using a PDN connection for emergency communication service.

[2. Modifications]
EPDG_A65 described in each embodiment may be TWAG_A74.

Note that the difference between the configurations of ePDG_A65 and TWAG_A74 is that ePDG_A65 is configured to be included in WLAN 75 ANB75 and the core network _A90 and WLAN ANB75 are connected, whereas TWAG_A74 is configured to be included in WLAN ANA70. The information stored in the storage unit may be the same except that the core network_A90 and the WLAN ANa70 are connected.

In addition, in each embodiment, the control message transmitted and received by UE_A10 and ePDG_A65 is a control message based on IKE, whereas the control message transmitted and received by UE_A10 and TWAG_A74 is a control message based on WLCP (WLAN Control Protocol). Good.

More specifically, the IKE_AUTH request (IKE_AUTH request) transmitted from the UE_A 10 to the ePDG_A65 in order to establish the PDN connection may be a PDN connection request message (PDN connectivity request).

Also, the IKE_AUTH response (IKE_AUTH Response) that ePDG_A65 sends to UE_A10 to establish the PDN connection may be a PDN connection acceptance message (PDN Connectivity Accept).

Therefore, the first identification information and / or the second identification information and / or the third identification information transmitted / received by the IKE_AUTH request and / or the IKE_AUTH response may be transmitted / received by the WLCP / PDN connection request and / or the WLCP / PDN connection acceptance.

Also, the IKE_AUTH request (IKE_AUTH Request) that UE_A10 sends and receives to ePDG_A65 for the detach procedure may be a PDN disconnection request message (PDN disconnect Request).

Furthermore, the IKE_AUTH response (IKE_AUTH Response) that ePDG_A65 sends to UE_A10 to disconnect the PDN connection may be a PDN disconnection acceptance message (PDN disconnect Accept).

Note that the PDN connection request message and the PDN disconnection request message may be control messages transmitted from the UE_A 10 to the TWAG_A 74, and the PDN connection acceptance message and the PDN disconnection acceptance message may be control messages transmitted from the TWAG 74 to the UE_A 10.

) Other procedures and processes will not be described in detail because ePDG_A65 can be replaced with TWAG_A74.

This enables UE_A10 to establish an emergency communication PDN connection via TWAG and receive an emergency communication service even when connecting to Trusted Non-3GPP Access Network.

In each embodiment, the program that operates in each device is a program that controls the CPU and 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 (e.g., RAM) during processing, then stored in various ROMs 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 nonvolatile 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 disc, 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.

In addition, a part or all of each device in the above-described embodiments may be realized as an LSI (Large Scale Integration) that is typically an integrated circuit. Each functional block of each device may be individually chipped, or a part or all of them may be integrated into a chip. Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. 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) have been described as examples of the radio access network, but they may be connected by WiMAX instead of WLAN.

9 Communication system
10 UE_A
30 PGW_A
35 SGW_A
40 MME_A
45 eNB_A
50 HSS_A
55 AAA_A
60 PCRF_A
65 ePDG_A
70 WLAN ANa
74 TWAG_A
75 WLAN ANb
80 LTE AN_A
90 Core network_A
100 PDN_A
110 IMS_A
112 P-CSCF_A

Claims (22)

A terminal device,
A controller that initiates a detach procedure to disconnect the first PDN connection based on whether the first gateway device supports an emergency communication service;
The first PDN connection is a PDN connection established via the first gateway device,
The control unit has a transmission / reception unit that transmits a request message for establishing a second PDN connection to the second gateway device based on the completion of the detachment procedure,
The second PDN connection is a PDN connection for emergency communication service,
The terminal device, wherein the second gateway device is a gateway that supports an emergency communication service. The first and second gateway devices are gateway devices that connect an untrusted Non3GPP Access Network and a core network,
2. The terminal device according to claim 1, wherein the request message is an IKE_AUTH message. The first and second gateway devices are gateway devices that connect the Trusted Non3GPP Access Network and the core network,
The terminal device according to claim 1, wherein the request message is a PDN Connectivity Request message. The control unit establishes the first PDN connection based on reception of an IKE_AUTH response message from the first gateway device,
3. The terminal device according to claim 2, wherein the detach procedure is started when the IKE_AUTH response message does not include information indicating that the first gateway device supports the emergency communication service. The control unit establishes the first PDN connection based on reception of an IKE_AUTH response message from the first gateway device,
If the IKE_AUTH response message includes information indicating that the first gateway device supports the emergency communication service, the detach procedure is not started.
3. The terminal device according to claim 2, wherein the transmitting / receiving unit transmits an IKE_AUTH request message to the first gateway device in order to establish the second PDN connection. 5. The terminal device according to claim 4, wherein the transmission / reception unit receives information indicating that the second gateway device included in the IKE_AUTH response message supports an emergency communication service. The control unit establishes the first PDN connection based on reception of the PDN Connectivity Accept message from the first gateway device,
4. The terminal device according to claim 3, wherein the detach procedure is started when the PDN Connectivity Accept message does not include information indicating that the first gateway device supports an emergency communication service. . The control unit establishes the first PDN connection based on reception of the PDN Connectivity Accept message from the first gateway device,
When the IKE_AUTH response message includes information indicating that the first gateway device supports the emergency communication service, the detach procedure is not started, and the transmission / reception unit transmits the second PDN connection. 4. The terminal device according to claim 3, wherein a PDN Connectivity request message is transmitted to the first gateway device for establishment. The terminal device according to claim 7, wherein the transmission / reception unit receives information indicating that the second gateway device included in the PDN Connectivity Accept message supports an emergency communication service. A gateway device,
A transmission / reception unit that receives an IKE_AUTH request message transmitted by a terminal device to establish a PDN connection;
The gateway device, as a response to the IKE_AUTH request message, transmits an IKE_AUTH response message including at least information indicating that the gateway device supports an emergency communication service to the terminal device. A gateway device,
A transmission / reception unit that receives an IKE_AUTH request message transmitted by a terminal device to establish a PDN connection;
The transmission / reception unit transmits, as a response to the IKE_AUTH request message, an IKE_AUTH response message including at least information on a gateway device that is different from the gateway device that supports an emergency communication service, to the terminal device. . A communication control method for a terminal device,
Initiating a detach procedure to disconnect the first PDN connection based on whether the first gateway device supports the emergency communication service,
The first PDN connection is a PDN connection established via the first gateway device,
Based on the completion of the detach procedure, a request message for establishing a second PDN connection is sent to the second gateway device,
The second PDN connection is a PDN connection for emergency communication service,
The communication control method for a terminal device, wherein the second gateway device is a gateway that supports an emergency communication service. The first and second gateway devices are gateway devices that connect an untrusted Non3GPP Access Network and a core network,
13. The communication control method for a terminal device according to claim 12, wherein the request message is an IKE_AUTH message. The first and second gateway devices are gateway devices that connect the Trusted Non3GPP Access Network and the core network,
13. The communication control method for a terminal device according to claim 12, wherein the request message is a PDN Connectivity Request message. Establishing the first PDN connection based on reception of an IKE_AUTH response message from the first gateway device,
14. The terminal device according to claim 13, wherein the detach procedure is started when the IKE_AUTH response message does not include information indicating that the first gateway device supports the emergency communication service. Communication control method. Establishing the first PDN connection based on reception of an IKE_AUTH response message from the first gateway device,
If the IKE_AUTH response message includes information indicating that the first gateway device supports the emergency communication service, the detach procedure is not started.
14. The communication control method for a terminal device according to claim 13, wherein an IKE_AUTH request message is transmitted to the first gateway device in order to establish the second PDN connection. 16. The communication control method for a terminal device according to claim 15, wherein information indicating that the second gateway device included in the IKE_AUTH response message supports an emergency communication service is received. Establishing the first PDN connection based on reception of a PDN Connectivity Accept message from the first gateway device,
15. The terminal device according to claim 14, wherein the detach procedure is started when the PDN Connectivity Accept message does not include information indicating that the first gateway device supports an emergency communication service. Communication control method. Establishing the first PDN connection based on reception of a PDN Connectivity Accept message from the first gateway device,
If the IKE_AUTH response message includes information indicating that the first gateway device supports the emergency communication service, the detach procedure is not started.
15. The communication control method for a terminal device according to claim 14, wherein a PDN Connectivity request message is transmitted to the first gateway device in order to establish the second PDN connection. 19. The communication control method for a terminal device according to claim 18, wherein information indicating that the second gateway device included in the PDN Connectivity Accept message supports an emergency communication service is received. A gateway device communication control method comprising:
Receive the IKE_AUTH request message sent by the terminal device to establish the PDN connection,
As a response to the IKE_AUTH request message, a communication control method for a gateway device, wherein an IKE_AUTH response message including at least information indicating that the gateway device supports an emergency communication service is transmitted to the terminal device. A gateway device communication control method comprising:
Receive the IKE_AUTH request message sent by the terminal device to establish the PDN connection,
As a response to the IKE_AUTH request message, a communication control method for a gateway device, wherein an IKE_AUTH response message including at least information on a gateway device different from the gateway device supporting an emergency communication service is transmitted to the terminal device.

Images