JP6847892B2 - UE and communication control method - Google Patents

Description

The present invention relates to UEs and core network devices.

The 3GPP (3rd Generation Partnership Project), which has been working on the standardization of mobile communication systems in recent years, is studying SAE (System Architecture Evolution), which is the system architecture of LTE (Long Term Evolution). 3GPP is specifying EPS (Evolved Packet System) as a communication system that realizes all IP (Internet Protocol). The core network that composes EPS is called EPC (Evolved Packet Core), and the access network that composes EPS is called E-UTRAN (Evolved Universal Terrestrial Radio Access Network).

In addition, in order to provide an emergency call service on an all-IP network, it is necessary to support a system called IMS (IP Multimedia Subsystem).

In recent years, 3GPP has also been studying the next-generation communication technology and system architecture of 5G (5th Generation) mobile communication systems, which are next-generation mobile communication systems. In particular, 5GS (5GS) is a system that realizes 5G mobile communication systems. 5G System) is being specified (see Non-Patent Document 1 and Non-Patent Document 2). 5GS extracts technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions.

For example, specifications such as optimization of core network, access network, and IMS for supporting emergency call service are being studied (Non-Patent Document 1, Non-Patent Document 2, Non-Patent Document 5, and Non-Patent Document). 9).

3GPP TS 23.501 v15.1.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15) 3GPP TS 23.502 v15.1.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15) 3GPP TS 24.501 v1.0.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15) 3GPP TS 24.502 v0.4.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks; Stage 3 (Release 15) 3GPP TS 24.301 V15.2.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (Release 15) 3GPP TS 23.401 V15.3.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 15) 3GPP TS 24.229 v15.2.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 15) 3GPP TS 23.228 v15.2.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 15) 3GPP TS 23.167 v15.2.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) emergency sessions (Release 15)

In 5GS, consideration is being given to applying conventional IMS to 5GS in order to support mobile communication voice call services.

More specifically, it exchanges various capability information in the emergency call service between the terminal (UE; User Equipment), access network and / or core network device, and exchanges various capability information in the emergency call service between the UE and the IMS device. As a result, specifications are being studied to provide mobile communication emergency call services suitable for UEs and network devices.

In response to the registration request from the UE, the network notifies various network capability information related to the emergency call service. When making an emergency call, the UE connects to the optimal access network and / or core network based on the capability information to realize an emergency call. Regarding the emergency call service, the ability information that the network notifies the UE is roughly divided into whether it supports the voice service or the emergency call service, and the access network is the most suitable access network and / or the emergency call service. There are three ways in which the core network supports features that allow handover and / or redirection. The UE selects the best access domain for emergency calls based on the capacity information of the received network.

Optimal access to network emergency call services Handover and / or redirection to the network and / or core network is performed based on a dedicated service request message from the UE, but some UEs support this feature. Some UEs do not support it.

Here, since the above-mentioned network capability information generation process is generated based on the network capability, it is not considered whether the UE supports a dedicated service request message. As a result, even if there is a difference in the capabilities supported by the network and the UE, for example, the network may unilaterally notify the optimal access network and / or core network of handover and / or redirection. If the UE does not support the function, the UE may not perform the emergency call operation expected by the network, which may lead to a deterioration in the quality of the emergency call service. No solution to this problem has been disclosed.

Nor is there a solution for performing the procedure to switch to the optimal access network and / or core network if the PDU session dedicated to emergency calls by the UE fails.

In addition, the optimal emergency call access domain selection method based on network capability information when the UE has dual registration for 4G and 5G is not disclosed.

In addition, if both 4G and 5G support emergency call services, no method of which system the UE chooses is disclosed.

The present invention has been made in view of such circumstances, and an object thereof is most suitable for an emergency call service based on exchanging various capability information in the emergency call service between various access networks and / or core network devices. It is to provide a means for realizing a connection to a network.

The UE of one embodiment of the present invention can be connected to the 5GC (5G Core Network) via the first access network or the second access network, and EPC (Evolved Packet Core) via the third access network. A UE (User Equipment) that can connect to the UMTS (Universal Mobile Telecommunications System) and sends a registration request message to the core network in the first access network or the second access network. The registration request message includes a transmitter / receiver that receives a registration acceptance message from the core network, and the registration request message is handed over to an access network and / or a core network that is most suitable for an emergency call connection included in the registration acceptance message. Alternatively, a UE characterized by including the UE's ability for information indicating that the access network supports features that allow redirection.

According to the present invention, the terminal can quickly connect to the most suitable network in the emergency call service. In addition, 5GS and IMS can control the terminal behavior so as to connect to the network most suitable for emergency calls under the initiative of the network, and can provide a safer and more secure mobile communication service.

It is a figure which shows the outline of the mobile communication system. It is a figure which shows an example of the configuration of a core network and an access network in a mobile communication system. It is a figure which shows the connection outline of an emergency table, IMS, and a core network for a normal voice call and an emergency call connection service. It is a figure which shows the service request procedure for an emergency call. It is a figure which shows the device configuration of UE. It is a figure which shows the structure of the access network apparatus. It is a figure which shows the apparatus configuration of MME / AMF. It is a figure which shows the apparatus configuration of SMF / PGW / UPF. It is a figure which shows the apparatus configuration of CSCF. It is a figure which shows various procedures for each embodiment. It is a figure which shows the registration procedure. It is a figure which shows the IMS registration procedure. It is a figure which shows the connection procedure of an IMS emergency call. It is a figure which shows the request procedure of a UE function. It is a figure explaining the attachment procedure in EPS.

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

[1. System overview]
The mobile communication system in this embodiment will be described with reference to FIGS. 1, 2, and 3.

FIG. 1 is a diagram illustrating an outline of the mobile communication system 1. FIG. 2 is a diagram showing an example of the configuration of the access network and the core network in the mobile communication system of FIG. FIG. 3 is a diagram showing an example of a connection configuration between an IP Multimedia Subsystem (IMS) and a core network among the mobile communication systems of FIG.

As shown in FIG. 1, the mobile communication system 1 in the present embodiment includes UE (User Equipment) _A10 (also referred to as user equipment, terminal equipment, or mobile terminal equipment), CN (Circuit Switched) network_A290 (circuit switching). Network), Access Network (AN) _A80, Access Network _A'81, Access Network _B120, Core Network (CN) _B190, Core Network _A90, Data Network (DN) It consists of _A5, Circuit Data Network (PDN) _B6, and IMS_A7. For simplification, core network_A and / or core network B and / or CS network_A or a combination thereof may also be referred to as core network, and access network_A and / or access network_A. ', And / or access network_B and / or CS network_A or a combination thereof may also be referred to as an access network or wireless access network, and DN_A5, PDN_A6 or a combination thereof may also be referred to as DN, in particular. CS network_A may be referred to as a circuit-switched network or CS network.

In addition, core network_A and / or core network_B, and / or CS network_A, and / or one or more devices / functions included in these core networks are referred to as core network or core network device. May be done.

That is, the fact that the core network and / or the core network device sends and receives messages and / or executes the procedure means that the core network_A and / or the core network_B, and / or the CS network_A, and / Or it may mean that one or more devices / functions included in these core networks send / receive messages and / or perform procedures.

In addition, EPS, which is a 4G system, is configured to include UE and access network_A and core network_A, but may further include PDN.

Further, 5GS, which is a 5G system, is configured to include a UE and an access network_B, an access network_A', and a core network_B, and may further include a DN. Also, the base station of access network_A'(eNB and / or ng-eNB) and the base station of access network_B (gNB) may or may not be connected to each other, for example, by means of an Xn interface. You may.

In addition, 3G, which is an old system, is composed of UMTS (Universal Mobile Telecommunications System) and includes UTRAN (UMTS Terrestrial Radio Access Network). The old system, 2G, consists of GSM (registered trademark) (global system for mobile communications) and includes GERAN (GSM (registered trademark) EDGE Radio Access Network). The wireless access provided by the old systems of UMTS and GSM (registered trademark) may be referred to as 2G / 3G.

In addition, core network_A corresponds to EPC (Evolved Packet Core). For example, MME, SGW, PGW, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. are arranged in EPC.

In addition, core network_B corresponds to 5GC (5G Core Network). For example, AMF, UPF, SMF, PCF (Policy Control Function), UDM (Unified Data Management), etc. are arranged in 5GC.

Also, CN Network_A290 is a network of 2G / 3G systems and may include a radio access network of 2G / 3G systems and / or devices for voice services described below.

Here, UE_A10 can connect to network services via 3GPP access (also referred to as 3GPP access or 3GPP access network) and / or non-3GPP access (also referred to as non-3GPP access or non-3GPP access network). It may be a device. In addition, UE_A10 may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Further, UE_A10 may be a terminal device capable of wireless connection, or may be an ME (Mobile Equipment), MS (Mobile Station), CIoT (Cellular Internet of Things) terminal (CIoT UE), or the like.

UE_A10 can also connect to the access network and / or the core network. UE_A10 can also connect to DN_A5 and / or PDN_A6 via the access network and / or core network. UE_A10 sends and receives user data to and from DN_A5 and / or PDN_A6 using a PDU (Protocol Data Unit or Packet Data Unit) session and / or PDN connection (PDN connection; Packet Data Network (PDN) Connection). (connect. Further, the communication of user data is not limited to IP (Internet Protocol) communication, and may be non-IP communication.

Here, IP communication is data communication using IP, and is data communication realized by sending and receiving an IP packet to which an IP header is added. The payload portion constituting the IP packet may include user data sent and received by UE_A10. Further, non-IP communication is data communication that does not use IP, and is data communication that is realized by sending and receiving data to which an IP header is not added. For example, non-IP communication may be data communication realized by sending and receiving application data to which an IP header is not added, or another header such as a MAC (Media Access Control) header or an Ethernet (registered trademark) frame header may be used. User data that is given and sent / received by UE_A10 may be sent / received.

Also, a PDU session or PDN connection is the connectivity established between UE_A10 and DN_A5 and / or PDN_A6 to provide a PDU connection service. More specifically, the PDU session or PDN connection may be the connectivity established between UE_A10 and the external gateway. Here, the external gateway may be UPF, PGW (Packet Data Network Gateway), SCEF (Service Capability Exposure Function), or the like. Further, the PDU session or PDN connection may be a communication path established for transmitting / receiving user data between UE_A10 and the core network and / or DN, or may be a communication path for transmitting / receiving PDU. In addition, the PDU session or PDN connection may be a session established between UE_A10 and the core network and / or DN, with one or more flows or transfer paths such as bearers between each device in mobile communication system 1. It may be a logical communication path to be constructed. More specifically, the PDU session or PDN connection may be a connection established by UE_A10 between the core network and / or an external gateway, or a connection established between UE_A10 and UPF_A235 or PGW_A30. The PDN connection may be a connection and / or a connection between UE_A10 and PGW_A30 via eNB (evolved Node B) _A45 and / or SGW (Serving Gateway) _A35, or eNB_A45 and / or MME (Mobility Management Entity). ) Connectivity and / or connection between UE_A10 and SCEF via _A40. In addition, the PDU session may be connectivity and / or connection between UE_A10 and UPF_A235 via gNB_A122 or eNB_B145. Further, the PDN connection may be identified by the PDN connection ID, and the PDU session may be identified by the PDU session ID. In addition, PDN connections and PDU sessions may be identified by EPS bearer ID. For simplification, a PDU session and / or a PDN connection may be referred to as a PDU session.

UE_A10 can transmit and receive user data by using a PDU session or PDN connection with a device such as an application server arranged in DN_A5 and / or PDN_A6. In other words, a PDU session or PDN connection can transfer user data sent and received between UE_A10 and a device such as an application server located at DN_A5 and / or PDN_A6. In addition, each device (UE_A10, device in the access network, and / or device in the core network) may manage one or more identifications associated with a PDU session or PDN connection. These identification information includes APN (Access Point Name), TFT (Traffic Flow Template), session type, application identification information, DN_A5 and / or PDN_A6 identification information, NSI (Network Slice Instance) identification information, and DCN. (Dedicated Core Network) At least one of the identification information and the identification information of the access network may be included, and other information may be further included. Further, when a plurality of PDU sessions are established, the identification information associated with the PDU session or the PDN connection may have the same content or different contents. Further, the NSI identification information is information that identifies NSI, and may be hereinafter NSI ID or Slice Instance ID.

The access network_A and / or access network_A'and / or access network_B include E-UTRAN (Evolved Universal Terrestrial Radio Access Network) _A80, UTRAN_A20, GERAN_A25, WLAN ANb75, WLAN ANa70, NG-RAN_A120. , WLAN ANc125. E-UTRAN_A80 and / or NG-RAN_A120 and / or UTRAN_A20 and / or GERAN_A25 may be referred to as a 3GPP access network, and WLAN ANb75 and / or WLAN Ana70 and / or WLAN ANc125 may be referred to as a non-3GPP access network. Each radio access network includes a device (for example, a base station device or an access point) to which the UE_A10 actually connects. In this specification, the wireless access network and the devices constituting the wireless access network are also referred to as a wireless access system.

For example, E-UTRAN_A80 is an LTE access network and is configured to include one or more eNB_A45s. eNB_A45 is a radio base station to which UE_A10 connects with E-UTRA (Evolved Universal Terrestrial Radio Access). Further, when there are a plurality of eNBs in E-UTRAN_A80, each eNB may be connected to each other.

In addition, NG-RAN_A120 is a 5G access network, and is configured to include one or more gNB (NR node B) _A122. gNB_A122 is a radio base station to which UE_A10 connects with 5G radio access. Further, when there are a plurality of gNB_A122s in NG-RAN_A120, each gNB_A122 may be connected to each other. In addition, gNB may also be referred to as an NR node (New Radio Access Technology node).

The NG-RAN_A120 may be an access network composed of E-UTRA and / or 5G Radio Access. In other words, NG-RAN_A120 may contain eNB_A45 and / or gNB_A122 and / or eNB_B145. In this case, eNB_A45 and gNB_A122 may be similar devices. Therefore, gNB_A122 can be replaced with eNB_A45 and / or eNB_B145.

In this specification, the eNB connected to the core network_A is also referred to as eNB_A, and the eNB connected to the core network_B is also referred to as eNB_B145 or Ng-eNB, and is connected to the core network_A. The existing gNB may be referred to as en-gNB. Further, the radio access network including gNB connected to the 5G network is also referred to as a first radio access system or access network_A', and the radio access network including eNB_B connected to the 5G network is also referred to as a second radio access system. .. Furthermore, the access network_B connected to the core network_B is the first access network, the access network_A'connected to the core network_B is the second access network, and the access connected to the core network_A. Network_A is also referred to as the third access network.

Further, the access network and the core network connection form in the present specification include the access network_B (NR (New Radio) connected to 5GC) connected to the core network_B and / or the core network_B. Access network _A'(E-UTRA connected to 5GC) and / or access network _A (E-UTRA connected to EPC) connected to core network _A and / or CS network (for simplicity, for simplicity) There may be an access network and a core network (represented as one network).

In addition, an interface for communication between access network devices may be provided, and the interface between access network devices connected to core network_A may be referred to as an X2 interface, which is connected to core network_B. The interface between the access network devices may be referred to as an Xn interface. In other words, for example, the Xn interface may be used for communication between a plurality of gNBs connected to the core network_B and / or between a plurality of Ng-eNBs and / or between a plurality of gNBs and the Ng-eNB. The X2 interface may be used for communication between a plurality of gNBs connected to the network_A and / or between a plurality of Ng-eNBs and / or between a plurality of gNBs and the Ng-eNB. Here, the communication between the access network devices may be the transmission / reception of control information, or may be the transfer of user data between UE_A10 and the network, and is not limited thereto.

In this specification, the fact that UE_A10 is connected to each radio access network means that it is connected to a base station device, an access point, or the like included in each radio access network, and data, signals, etc. to be transmitted and received. It also means that it goes through a base station device or an access point. The control message sent / received between UE_A10 and the core network_B190 may be the same control message regardless of the type of access network. Therefore, sending and receiving a message between UE_A10 and core network_B190 via gNB_A122 may be the same as sending and receiving a message between UE_A10 and core network_B190 via eNB_A45 and / or eNB_B145.

Further, the access network is a wireless network connected to UE_A10 and / or the core network. The access network may be a 3GPP access network or a non-3GPP access network. The 3GPP access network may be UTRAN_A20 and / or GERAN and / or E-UTRAN_A80 and / or NG-RAN (Radio Access Network) _A120, and the non-3GPP access network may be WLAN ANb75 and / or WLAN ANa72 and /. Alternatively, it may be WLAN ANc125. In addition, UE_A10 may be connected to the access network in order to connect to the core network, or may be connected to the core network via the access network.

Further, DN_A5 and / or PDN_A6 is a data network (Data Network) or a packet data network (Packet Data Network) that provides a communication service to UE_A10, and may be configured as a packet data service network or is configured for each service. You may. For example, there may be DN_A5 and / or PDN_A6 that provide IMS service, or DN_A5 and / or PDN_A6 may include a device for providing IMS service. In other words, DN_A5 and / or PDN_A6 may be configured as IMS_A7, DN_A5 and / or PDN_A6 may contain IMS_A7, and IMS_A7 may have UE_A10 with a normal call connection service for voice service and / or An emergency call connection service and / or a normal call connection service and / or an emergency call connection service for a text message service may be provided. In the following, only the normal call connection service and / or the emergency call connection service for the voice service is described, but the normal call connection service and / or the emergency call connection service for the text message service is also executed in the same manner. Good. Further, DN_A5 and / or PDN_A6 may include a connected communication terminal. Therefore, connecting to DN_A5 and / or PDN_A6 may be connecting to a communication terminal or server device arranged in DN_A5 and / or PDN_A6. Further, transmitting and receiving user data with DN_A5 and / or PDN_A6 may be transmitting and receiving user data with a communication terminal or server device arranged in DN_A5 and / or PDN_A6. Further, DN_A5 and / or PDN_A6 are outside the core network in FIG. 1, but may be inside the core network.

Further, the core network_A90 and / or the core network_B190 and / or the CS network_A290 may be configured as one or more core network devices. Here, the core network device may be a device that executes a part or all of the processing or function of each device included in the core network_A90 and / or the core network_B190 and / or the CS network_A290.

Further, the core network is an IP mobile communication network operated by a mobile network operator (MNO) connected to an access network and / or a DN. The core network may be a core network for a mobile communication operator that operates and manages the mobile communication system 1, or a virtual mobile communication operator such as MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler) or a virtual network. It may be a core network for mobile communication service providers. The core network_A90 may be an EPC (Evolved Packet Core) constituting an EPS (Evolved Packet System), and the core network_B190 may be a 5GC (5G Core Network) constituting a 5GS. Conversely, the EPC may be the core network_A90 and the 5GC may be the core network_B190. Further, the core network_B190 may be the core network of the system that provides the 5G communication service. The core network_A90 and / or the core network_B190 and / or the CS network_A290 is not limited to this, and may be a network for providing a mobile communication service. Hereinafter, in the present specification, 5GS may be referred to as a first network system, and EPS may be referred to as a second network system. Furthermore, 5GC may be referred to as the first core network, and EPC may be referred to as the second core network. Further, the above-mentioned first wireless access system and / or second wireless access system and / or first network system and / or second network system are collectively referred to as a network.

Next, the core network will be described. In this embodiment, a configuration example of the core network_A90 and the core network_B190 will be described. The core network may be core network_A90, core network_B190, CS network_A290, or a combination thereof.

Core network _A90 includes HSS (Home Subscriber Server) _A50, AAA (Authentication Authorization Accounting), PCRF (Policy and Charging Rules Function), PGW_A30, ePDG, SGW_A35, MME (Mobility Management Entity) _A40, SGSN (Serving GPRS Support) Node), SCEF, at least one may be included. Then, these may be configured as NF (Network Function). NF may refer to a processing function configured in the network. In addition, the core network_A90 can be connected to a plurality of wireless access networks (UTRAN_A20, GERAN_A25, E-UTRAN_A80, WLAN ANb75, WLAN ANa70).

For simplification, Figure 2 shows only PGW (PGW_A30), SGW (SGW_A35) and MME (MME_A40), but does not include other devices and / or NFs. It does not mean that. For simplification, UE_A10 is also referred to as UE, HSS_A50 is referred to as HSS, PGW_A30 is referred to as PGW, SGW_A35 is referred to as SGW, MME_A40 is referred to as MME, and DN_A5 and / or PDN_A6 is also referred to as DN.

Further, in FIG. 2, a solid line or a dotted line is shown as an interface connecting the devices. Here, the solid line is the interface for U-Plane, and the dotted line is the interface for C-Plane.

First, a brief description of each device included in the core network_A90 will be given.

PGW_A30 is a relay device that is connected to DN, SGW_A35, ePDG, WLAN ANa70, PCRF, and AAA, and transfers user data as a gateway between DN (DN_A5 and / or PDN_A6) and core network_A90. The PGW_A30 may be a gateway for IP communication and / or non-IP communication. Further, PGW_A30 may have a function of transferring IP communication, and may have a function of converting non-IP communication and IP communication. A plurality of such gateways may be arranged in the core network_A90. Further, the plurality of gateways to be arranged may be a gateway connecting the core network_A90 and a single DN.

The U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data, and may be composed of a plurality of bearers. Further, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages, and may be composed of a plurality of bearers.

Further, PGW_A30 may be connected to UPF (User Plane Function) and SMF (Session Management Function), or may be connected to UE_A10 via U-Plane. In addition, PGW_A30 may be configured with UPF_A235 and / or SMF_A230.

SGW_A35 is connected to PGW_A30, MME_A40, E-UTRAN_A80, SGSN and UTRAN_A20, and relays user data as a gateway to core network_A90 and 3GPP access networks (UTRAN_A20, GERAN_A25, E-UTRAN_A80). It is a device.

MME_A40 is a control device that is connected to SGW_A35, an access network, HSS_A50, and SCEF, and performs location information management including mobility management of UE_A10 and access control via the access network. Further, the MME_A40 may include a function as a session management device that manages the sessions established by the UE_A10. Further, a plurality of such control devices may be arranged in the core network_A90, and for example, a position management device different from the MME_A40 may be configured. A location management device different from the MME_A40 may be connected to the SGW_A35, the access network, the SCEF, and the HSS_A50, similar to the MME_A40.

Further, when a plurality of MMEs are included in the core network_A90, the MMEs may be connected to each other. As a result, the context of UE_A10 may be sent and received between MMEs. In this way, the MME_A40 is a management device that transmits and receives control information related to mobility management and session management to and from the UE_A10, in other words, it may be a control device of the control plane (C-Plane; CP).

Further, although the example in which MME_A40 is configured to be included in core network_A90 has been described, MME_A40 may be one or more core networks or a management device composed of DCN or NSI, or one or more core networks or. It may be a management device connected to a DCN or NSI. Here, a plurality of DCNs or NSIs may be operated by a single telecommunications carrier or may be operated by different telecommunications carriers.

Further, the MME_A40 may be a relay device that transfers user data as a gateway between the core network_A90 and the access network. The user data transmitted / received using MME_A40 as a gateway may be small data.

Further, MME_A40 may be an NF such as UE_A10 that plays a role of mobility management, or an NF that manages one or more NSIs. Further, MME_A40 may be an NF that plays one or more of these roles. The NF may be one or more devices arranged in the core network_A90, and may also be a CP function (hereinafter, CPF (Control Plane Function)) for control information and / or a control message, or a Control Plane Network Function. It may be a shared CP function shared between multiple network slices.

Here, NF is a processing function configured in the network. That is, the NF may be a functional device such as MME, SGW, PGW, CPF, AMF, SMF, or UPF, or may be function or capability capability information such as MM (Mobility Management) or SM (Session Management). Further, the NF may be a functional device for realizing a single function or a functional device for realizing a plurality of functions. For example, the NF for realizing the MM function and the NF for realizing the SM function may exist separately, or there is an NF for realizing both the MM function and the SM function. You may.

HSS_A50 is a management node that is connected to MME_A40, AAA, and SCEF and manages subscriber information. The subscriber information of HSS_A50 is referred to when the access control of MME_A40 is performed, for example. Further, the HSS_A50 may be connected to a position management device different from that of the MME_A40. For example, HSS_A50 may be connected to CPF_A140.

Further, HSS_A50 may be configured as UDM (Unified Data Management) _A245 as a different device and / or NF, or may be configured as the same device and / or NF.

AAA is connected to PGW30, HSS_A50, PCRF and WLAN ANa70, and controls access to UE_A10 connected via WLAN ANa70.

The PCRF is connected to PGW_A30, WLAN ANa75, AAA, DN_A5 and / or PDN_A6 and performs QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and DN_A5 and / or PDN_A6. Further, the PCRF may be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules that each device uses when transmitting and receiving user data.

The PCRF may also be a PCF that creates and / or manages policies. More specifically, the PCRF may be connected to UPF_A235.

The ePDG is connected to PGW30 and WLAN ANb75, and delivers user data as a gateway between core network _A90 and WLAN ANb75.

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

SCEF is a relay device that is connected to DN_A5 and / or PDN_A6, MME_A40 and HSS_A50, and transfers user data as a gateway connecting DN_A5 and / or PDN_A6 and core network_A90. SCEF may be a gateway for non-IP communication. In addition, SCEF may have the ability to convert between non-IP communication and IP communication. In addition, a plurality of such gateways may be arranged in the core network_A90. Further, a plurality of gateways connecting the core network_A90 and a single DN_A5 and / or PDN_A6 and / or DN may be arranged. The SCEF may be configured outside the core network or inside the core network.

Next, the core network_B190 includes AUFF (Authentication Server Function), AMF (Access and Mobility Management Function) _A240, SDSF (Structured Data Storage network function), UDSF (Unstructured Data Storage network function), and NEF (Network Exposure Function). ), NRF (NF Repository Function), PCF (Policy Control Function), SMF (Session Management Function) _A230, SMF (Session Management Function) _B232, UDM (Unified Data Management) _A245, UPF (User Plane Function) _A235, UPF ( At least one of User Plane Function) _B237, AF (Application Function), and N3IWF (Non-3GPP InterWorking Function) may be included. Then, these may be configured as NF (Network Function). NF may refer to a processing function configured in the network. In addition, the core network_B190 can be connected to a plurality of radio access networks (E-UTRAN_A80, NG-RAN_A120, WLAN). The radio access network may be configured to be connected to a plurality of different access networks, or may be configured to be connected to any one of the access networks.

For simplicity, FIG. 2 shows only AMF_A240, SMF_A230, and UPF_A235, which means that other than these (equipment and / or NF) are not included. is not it. For simplification, UE_A10 is also referred to as UE, AMF_A240 is referred to as AMF, SMF_A230 is referred to as SMF, UPF_A235 is referred to as UPF, and DN_A5 and / or PDN_A6 is also referred to as DN.

Further, FIG. 2 shows an N1 interface (hereinafter, also referred to as a reference point), an N2 interface, an N3 interface, an N4 interface, an N6 interface, an N11 interface, and an N26 interface. Here, the N1 interface is the interface between the UE and AMF, the N2 interface is the interface between (R) AN (access network) and AMF, and the N3 interface is (R) AN (access network). The interface between UPF, the N4 interface is the interface between SMF and UPF, the N6 interface is the interface between UPF and DN, and the N11 interface is the interface between AMF and SMF. The N26 interface is the interface between AMF in core network_B190 and MME in core network_A90. Communication can be performed between the devices by using these interfaces. Further, in FIG. 2, the interface connecting the devices is shown by a solid line or a dotted line. Here, the solid line is the interface for U-Plane, and the dotted line is the interface for C-Plane.

Next, a brief description of each device included in the core network_B190 will be given.

First, AMF_A240 is connected to other AMFs, SMF_A230s, access networks (ie E-UTRAN_A80 and NG-RAN_A120 and WLAN ANc125 and WLAN ANa70 and WLAN ANb75), UDM_A245, AUSF, PCF. AMF_A240 is used for registration management, connection management, reachability management, mobility management such as UE_A10, and transfer of SM (Session Management) messages between UE and SMF. , Access Authentication (Access Authorization), Security Anchor Function (SEA), Security Context Management (SCM), N2 interface support for N3IWF, NAS signals with UE via N3IWF It may play a role of supporting transmission / reception, authenticating UEs connected via N3IWF, managing RM states (Registration Management states), managing CM states (Connection Management states), and so on. Further, one or more AMF_A240 may be arranged in the core network_B190. In addition, AMF_A240 may be an NF that manages one or more NSIs (Network Slice Instances). Further, AMF_A240 may be a shared CPNF (Control Plane Network Function) (CCNF) shared among a plurality of NSIs.

Further, as the RM state, for example, there are a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered in the network, so the UE context in AMF does not have valid location information or routing information for that UE, so AMF cannot reach the UE. is there. Also, in the RM-REGISTERED state, the UE is registered in the network, so the UE can receive services that require registration with the network.

Further, as the CM state, for example, there are a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-IDLE state, the UE does not have an N2 interface connection (N2 connection) and an N3 interface connection (N3 connection). On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection established with AMF via the N1 interface. Further, in the CM-CONNECTED state, the UE may have an N2 interface connection (N2 connection) and / or an N3 interface connection (N3 connection).

In addition, SMF_A230 is connected to AMF_A240, UPF_A235, UDM_A245, and PCF. SMF_A230 is used for session management such as PDU sessions, IP address allocation for UEs, selection and control of UPFs, UPF settings for routing traffic to appropriate destinations, and downlink data. Ability to notify that has arrived (Downlink Data Notification), AN-specific (per AN) SM information identifier sent to AN via AMF via N2 interface, SSC mode for session (Session) It may play a role of determining and Service Continuity mode), roaming function, etc.

The UPF_A235 is also connected to DN_A5, SMF_A230, other UPFs, and access networks (ie E-UTRAN_A80, NG-RAN_A120, WLAN ANc125, WLAN ANa70, and WLAN ANb75). UPF_A235 is an anchor for intra-RAT mobility or inter-RAT mobility, Packet routing & forwarding, UL CL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, Routing point function that supports multi-homed PDU session, QoS processing for User Plane, verification of uplink traffic, buffering of downlink packets, downlink data notification. It may play a role such as a trigger function. Further, UPF_A235 may be a relay device that transfers user data as a gateway between DN_A5 and core network_B190. UPF_A235 may be a gateway for IP communication and / or non-IP communication. Further, UPF_A235 may have a function of transferring IP communication, and may have a function of converting non-IP communication and IP communication. Further, the plurality of gateways to be arranged may be a gateway connecting the core network_B190 and a single DN. The UPF_A235 may have connectivity with other NFs, or may be connected to each device via other NFs.

In addition, AUSF is connected to UDM_A245 and AMF_A240. AUSF acts as an authentication server.

SDSF provides NEF with the ability to store and retrieve information as structured data.

UDSF provides the ability for all NFs to store and retrieve information as unstructured data.

NEF provides a means to securely provide the services and capabilities provided by the 3GPP network. Information received from other NFs is saved as structured data.

When the NRF receives an NF Discovery Request from an NF instance, it provides the NF with information on the discovered NF instance, information on available NF instances, and information on services supported by that instance. Or hold.

The PCF is connected to SMF_A230, AF and AMF_A240. Provides policy rules, etc.

UDM_A245 is connected to AMF_A240, SMF_A230, AUSF and PCF. UDM_A245 includes UDM FE (application front end) and UDR (User Data Repository). UDM FE processes credentials, location management, subscription management, and so on. UDR stores the data required by UDM FE and the policy profiles required by PCF.

AF is connected to PCF. AF influences traffic routing and is involved in policy control.

N3IWF establishes IPsec tunnel with UE, relays NAS (N1) signaling between UE and AMF, processes N2 signaling transmitted from SMF and relayed by AMF, and establishes IPsec Security Association (IPsec SA). , Provides functions such as relaying User Plane packets between UE and UPF, and AMF selection.

Next, IMS_A7 includes P-CSCF (Proxy Call Session Control Function; Proxy-CSCF) _A300, P-CSCF_B310, I-CSCF (Interrogating Call Session Control Function; Interrogating-CSCF), S-CSCF (Serving Call Session Control Function). At least one of Serving-CSCF) _A320 and E-CSCF (Emergency Call Session Control Function; Emergency-CSCF) _A330 may be included. These may be configured as NF (Network Function). NF may refer to a processing function configured in the network. Here, CSCF (Call Session Control Function) is for processing SIP (Session Initiation Protocol) signal packets in IMS (IP Multimedia subsystem), for example, P-CSCF and / or S-CSCF and / or E. -A generic term for devices and / or NFs that act as servers and / or proxies, such as CSCF and / or I-CSCF.

For simplicity, Figure 3 shows only P-CSCF_A300, P-CSCF_B310, S-CSCF_A320, and E-CSCF_A330, but does not include anything else (equipment and / or NF). Does not mean. For simplification, P-CSCF_A300 and / or P-CSCF_B310 are also referred to as P-CSCF, S-CSCF_A320 is also referred to as S-CSCF, and E-CSCF_A330 is also referred to as E-CSCF.

Further, the emergency table / emergency table network (PSAP (Public Safety Answering Point)) shown in FIG. 3 may be the connection destination and / or the connection destination network of the emergency call connection required by UE_A10.

Next, a brief description of each device included in IMS_A7 will be given.

First, the P-CSCF is connected to the core network_A and / or the core network_B and / or the UPF and / or the PWG and / or the S-CSCF and / or the E-CSCF and the like. P-CSCF is a SIP proxy server when UE_A10 connects to IMS_A7. The P-CSCF is the device of IMS_A7 to which the UE_A10 connects first, and is assigned to the UE_A10 in the registration procedure described later, and the UE_A10 may acquire the destination address of the P-CSCF during the procedure. Further, the P-CSCF may execute the processing of the normal call connection and the processing of the emergency call connection required by UE_A10 in different devices and / or NFs, or may be executed in the same device and / or NF.

Further, the S-CSCF is connected to HSS_A50 and / or UDM_A245 and / or P-CSCF and / or I-CSCF and / or E-CSCF and the like. S-CSCF is a SIP server that controls the session of IMS related to UE_A10 and / or authenticates the user.

The E-CSCF is connected to the P-CSCF and / or the S-CSCF and / or the I-CSCF and / or the emergency table / emergency table network (PSAP) and the like. The E-CSCF is a CSCF for processing emergency calls, and may, for example, route an emergency call request to an appropriate emergency table / emergency table network (PSAP).

[2. Configuration of each device]
Hereinafter, the configuration of each device will be described. Note that some or all of the following devices and the functions of each part of each device may operate on physical hardware, or logical hardware virtually configured on general-purpose hardware. It may work on hardware.

[2.1. UE Configuration]
First, an example of the device configuration of UE_A10 is shown in FIG. As shown in FIG. 5, UE_A10 is composed of a control unit_A500, a transmission / reception unit_A520, and a storage unit_A540. The transmission / reception unit_A520 and the storage unit_A540 are connected to the control unit_A500 via a bus. An external antenna 510 is connected to the transmitter / receiver _A520. In addition, the storage unit_A540 stores the UE context 442.

The control unit_A500 is a functional unit for controlling the entire UE_A10, and realizes various processes of the entire UE_A10 by reading and executing various information and programs stored in the storage unit_A540.

The transmission / reception unit_A520 is a functional unit for UE_A10 to connect to the base stations (E-UTRAN_A80 and NG-RAN_A120) and / or the access point (WLAN ANc125) in the access network and to connect to the access network. In other words, the UE_A10 can be connected to a base station and / or an access point in the access network via an external antenna 510 connected to the transmitter / receiver_A520. Specifically, the UE_A10 transmits / receives user data and / or control information to / from a base station and / or an access point in the access network via an external antenna 510 connected to the transmission / reception unit_A520. Can be done.

The storage unit_A540 is a functional unit that stores programs and data required for each operation of UE_A10, and is composed of, for example, a semiconductor memory, an HDD (Hard Disk Drive), an SSD (Solid State Drive), and the like. The storage unit_A540 stores identification information, control information, flags, parameters, and the like included in the control messages transmitted and received in the communication procedure described later. The UE context stored in the storage unit_A540 may be, for example, a UE context used when connecting to the access network_B120 and a UE context used when connecting to the core network_B190. Further, the UE context 442 may include a UE context stored for each UE, a UE context stored for each PDU session, and a UE context stored for each bearer. The UE context stored for each UE may include IMSI, EMM State, GUTI, and ME Identity. Further, the UE context stored for each PDU session may include APN in Use, Assigned Session Type, IP Address (es), and Default Bearer. Further, the UE context stored for each bearer may include EPS Bearer ID, TI, and TFT.

[2.2. Access network device configuration]
Next, a configuration example of the access network device is shown in FIG. Access network devices may include, but are not limited to, for example, eNB_A45 and / or eNB_B and / or gNB_A122 and / or WAG_A126. As shown in FIG. 6, the access network device is composed of a control unit_B600, a network connection unit_B620, a transmission / reception unit_B630, and a storage unit_B640. The network connection unit_B620, the transmission / reception unit_B630, and the storage unit_B640 are connected to the control unit_B600 via a bus. An external antenna 610 is connected to the transmitter / receiver _B630.

The control unit_B600 is a functional unit for controlling the entire access network device, and by reading and executing various information and programs stored in the storage unit_B640, the eNB_A45, gNB_A122, and WAG_A126 as a whole. Achieve various processes.

The network connection unit_B620 is a functional unit for the access network device to connect to AMF_A240 and UPF_A235 in the core network. In other words, the access network device can be connected to AMF_A240 and UPF_A235 in the core network via the network connection part_B620. Specifically, the access network device can send and receive user data and / or control information to and from AMF_A240 and / or UPF_A235 via the network connection unit_B620.

The transmission / reception unit_B630 is a functional unit for the access network device to connect to the UE_A10. In other words, the access network device can send and receive user data and / or control information to and from UE_A10 via the transmission / reception unit_B630.

The storage unit_B640 is a functional unit that stores programs, data, etc. required for each operation of the access network device. The storage unit_B640 is composed of, for example, a semiconductor memory, an HDD, an SSD, or the like. The storage unit_B640 stores identification information, control information, flags, parameters, and the like included in the control messages transmitted and received in the communication procedure described later. The storage unit_B640 may store this information as a context for each UE_A10.

[2.3. MME / AMF configuration]
Next, an example of device configuration of MME_A40 and / or AMF_A240 is shown in FIG. As shown in FIG. 7, the MME_A40 and / or AMF_A240 is composed of a control unit_C700, a network connection unit_C720, and a storage unit_C740. The network connection unit_C720 and the storage unit_C740 are connected to the control unit_C700 via a bus. The storage unit_C740 stores the context 742.

The control unit_C700 is a functional unit for controlling the entire MME_A40 and / or AMF_A240, and by reading and executing various information and programs stored in the storage unit_C740, the MME_A40 and / or AMF_A240 Realize various processing as a whole.

In the network connection part_C720, MME_A40 and / or AMF_A240 is another AMF_240, SMF_A230, base stations (E-UTRAN_A80 and NG-RAN_A120) and / or access points (WLAN ANc125), UDM_A245, AUSF, PCF in the access network. It is a functional part for connecting to. In other words, MME_A40 and / or AMF_A240 sends and receives user data and / or control information to and from base stations and / or access points, UDM_A245, AUSF, and PCF in the access network via network connection_C720. can do.

The storage unit_C740 is a functional unit that stores programs, data, etc. required for each operation of MME_A40 and / or AMF_A240. The storage unit_C740 is composed of, for example, a semiconductor memory, an HDD, an SSD, or the like. The storage unit_C740 stores identification information, control information, flags, parameters, and the like included in the control messages transmitted and received in the communication procedure described later. The context 742 stored in the storage unit_C740 may include a context stored for each UE, a context stored for each PDU session, and a context stored for each bearer. The contexts stored for each UE include IMSI, MSISDN, MM State, GUTI, ME Identity, UE Radio Access Capability, UE Network Capability, MS Network Capability, Access Restriction, MME F-TEID, SGW F-TEID, and eNB Address. , MME UE S1AP ID, eNB UE S1AP ID, gNB Address, gNB ID, WAG Address, WAG ID may be included. Further, the context stored for each PDU session may include APN in Use, Assigned Session Type, IP Address (es), PGW F-TEID, SCEF ID, and Default bearer. The contexts stored for each bearer include EPS Bearer ID, TI, TFT, SGW F-TEID, PGW F-TEID, MME F-TEID, eNB Address, gNB Address, WAG Address, eNB ID, gNB ID, It may include a WAG ID.

[2.4. SMF configuration]
Next, an example of the device configuration of SMF_A230 is shown in FIG. As shown in FIG. 8, the SMF_A230 is composed of a control unit_D800, a network connection unit_D820, and a storage unit_D840, respectively. The network connection unit _D820 and the storage unit _D840 are connected to the control unit _D800 via a bus. The storage unit_D840 stores the context 842.

The control unit_D800 of SMF_A230 is a functional unit for controlling the entire SMF_A230, and realizes various processes of the entire SMF_A230 by reading and executing various information and programs stored in the storage unit_D840. To do.

The network connection part_D820 of SMF_A230 is a functional part for SMF_A230 to connect with AMF_A240, UPF_A235, UDM_A245, and PCF. In other words, the SMF_A230 can send and receive user data and / or control information to and from the AMF_A240, UPF_A235, UDM_A245, and PCF via the network connection_D820.

The storage unit_D840 of SMF_A230 is a functional unit that stores programs, data, etc. required for each operation of SMF_A230. The storage unit_D840 of SMF_A230 is composed of, for example, a semiconductor memory, an HDD, an SSD, or the like. The storage unit_D840 of the SMF_A230 stores identification information, control information, flags, parameters, etc. included in the control messages transmitted and received in the communication procedure described later. The context 842 stored in the storage unit_D840 of SMF_A230 includes a context stored for each UE, a context stored for each APN, a context stored for each PDU session, and a context stored for each bearer. There may be a context. The context stored for each UE may include IMSI, ME Identity, MSISDN, RAT type. The context stored for each APN may include APN in use. The context stored for each APN may be stored for each Data Network Identifier. The context stored for each PDU session may include Assigned Session Type, IP Address (es), SGW F-TEID, PGW F-TEID, Default Bearer. The context stored for each bearer may include EPS Bearer ID, TFT, SGW F-TEID, PGW F-TEID.

[2.5. PGW / UPF configuration]
Next, an example of device configuration of PGW_A30 and / or UPF_A235 is shown in FIG. As shown in FIG. 8, PGW_A30 and / or UPF_A235 is composed of a control unit_D800, a network connection unit_D820, and a storage unit_D840, respectively. The network connection unit _D820 and the storage unit _D840 are connected to the control unit _D800 via a bus. The storage unit_D840 stores the context 842.

The control unit_D800 of PGW_A30 and / or UPF_A235 is a functional unit for controlling the entire UPF_A235, and by reading and executing various information and programs stored in the storage unit_D840, PGW_A30 and / or PGW_A30 and / Or, realize various processing of the entire UPF_A235.

In addition, the network connection part_D820 of PGW_A30 and / or UPF_A235 has PGW_A30 and / or UPF_A235 as DN (that is, DN_A5 and / or PDN_A6), SMF_A230, other PGW_A30 and / or UPF_A235, and the access network (that is, that is). It is a functional part for connecting E-UTRAN_A80, NG-RAN_A120, WLAN ANc125, WLAN ANa70 and WLAN ANb75). In other words, UPF_A235 is via network connection_D820 with DN (ie DN_A5 and / or PDN_A6), SMF_A230, other UPF_A235, and access networks (ie E-UTRAN_A80 and NG-RAN_A120 and WLAN ANc125). User data and / or control information can be sent and received between WLAN ANa70 and WLAN ANb75).

The storage unit_D840 of PGW_A30 and / or UPF_A235 is a functional unit that stores programs, data, etc. required for each operation of PGW_A30 and / or UPF_A235. The storage unit_D840 of PGW_A30 and / or UPF_A235 is composed of, for example, a semiconductor memory, an HDD, an SSD, or the like. The storage unit_D840 of PGW_A30 and / or UPF_A235 stores identification information, control information, flags, parameters, etc. included in the control messages transmitted and received in the communication procedure described later. The context 842 stored in the storage unit_D840 of PGW_A30 and / or UPF_A235 includes a context stored for each UE, a context stored for each APN, a context stored for each PDU session, and a bearer. There may be a context that is remembered for each. The context stored for each UE may include IMSI, ME Identity, MSISDN, RAT type. The context stored for each APN may include APN in use. The context stored for each APN may be stored for each Data Network Identifier. The context stored for each PDU session may include Assigned Session Type, IP Address (es), SGW F-TEID, PGW F-TEID, Default Bearer. The context stored for each bearer may include EPS Bearer ID, TFT, SGW F-TEID, PGW F-TEID.

[2.6. CSCF configuration]
Next, a configuration example of CSCF is shown in FIG. As shown in FIG. 9, the CSCF is composed of a control unit_E900, a network connection unit_E920, and a storage unit_E940, respectively. The network connection unit _E920 and the storage unit _E940 are connected to the control unit _E900 via a bus. The storage unit_E940 stores the context 942.

The CSCF control unit_E900 is a functional unit for controlling the entire CSCF, and realizes various processes for the entire CSCF by reading and executing various information and programs stored in the storage unit_E940. To do.

The network connection part_E920 of CSCF is a functional part for CSCF to connect with other CSCF, UPF_A235, PGW_A30, HSS_A50, UDM_A245. In other words, the CSCF can send and receive user data and / or control information to and from other CSCFs, UPF_A235, PGW_A30, HSS_A50, UDM_A245 via the network connection part_E920.

The CSCF storage unit_E940 is a functional unit that stores programs and data required for each operation of the CSCF. The storage unit_E940 is composed of, for example, a semiconductor memory, an HDD, an SSD, or the like. The storage unit_E940 stores identification information, control information, flags, parameters, etc. included in the control messages transmitted and received in the communication procedure described later. The context 942 stored in the storage unit_E940 may be a context stored for each UE, such as IMSI, MSISDN, UE Address, Public User ID (s), Private User ID (s), and access network. It may include the type, session state information.

[2.7. Information stored in the storage unit of each device]
Next, each information stored in the storage unit of each of the above devices will be described.

IMSI (International Mobile Subscriber Identity) and / or SUPI (Subscriber Permanent Identifier) is permanent identification information of a subscriber (user), and is identification information assigned to a user who uses a UE. The IMSI and / or SUPI stored by UE_A10 and MME_A40 / CPF_A140 / AMF_A2400 and SGW_A35 may be equal to the IMSI and / or SUPI stored by HSS_A50 and / or UDM_A245. Here, SUPI may include IMSI.

EMM State / MM State indicates the Mobility management status of UE_A10 or MME_A40 / CPF_A140 / AMF_A240. For example, the EMM State / MM State may be an EMM-REGISTERED state (registered state) in which UE_A10 is registered in the network, and / or an EMM-DEREGISTERD state (unregistered state) in which UE_A10 is not registered in the network. Further, the EMM State / MM State may be an ECM-CONNECTED state in which the connection between UE_A10 and the core network is maintained, and / or an ECM-IDLE state in which the connection is released. The EMM State / MM State may be information that can distinguish between the state in which UE_A10 is registered in the EPC and the state in which it is registered in the NGC or 5GC.

GUTI (Globally Unique Temporary Identity) is temporary identification information of UE_A10. GUTI consists of MME_A40 / CPF_A140 / AMF_A240 identification information (GUMMEI (Globally Unique MME Identifier)) and UE_A10 identification information (M-TMSI (M-Temporary Mobile Subscriber Identity)) within the specific MME_A40 / CPF_A140 / AMF_A240. Will be done. ME Identity is UE_A10 or ME ID, and may be, for example, IMEI (International Mobile Equipment Identity) or IME ISV (IMEI Software Version). MSISDN represents the basic telephone number of UE_A10. The MSISDN stored by MME_A40 / CPF_A140 / AMF_A240 may be the information indicated by the storage unit of HSS_A50. The GUTI may include information that identifies CPF_140.

MME F-TEID is information that identifies MME_A40 / CPF_A140 / AMF_A240. The MME F-TEID may include the IP address of MME_A40 / CPF_A140 / AMF_A240, the TEID (Tunnel Endpoint Identifier) of MME_A40 / CPF_A140 / AMF_A240, or both. May be good. Further, the IP address of MME_A40 / CPF_A140 / AMF_A240 and the TEID of MME_A40 / CPF_A140 / AMF_A240 may be stored independently. Further, the MME F-TEID may be identification information for user data or identification information for control information.

SGW F-TEID is information that identifies SGW_A35. The SGW F-TEID may include the IP address of SGW_A35, the TEID of SGW_A35, or both. Further, the IP address of SGW_A35 and the TEID of SGW_A35 may be stored independently. Further, the SGW F-TEID may be identification information for user data or identification information for control information.

PGW F-TEID is information that identifies PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235. The PGW F-TEID may include the IP address of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235, the TEID of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235, or both. Good. Further, the IP address of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 and the TEID of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 may be stored independently. Further, the PGW F-TEID may be identification information for user data or identification information for control information.

The eNB F-TEID is information that identifies eNB_A45. The eNB F-TEID may include the IP address of eNB_A45, the TEID of eNB_A45, or both. Further, the IP address of eNB_A45 and the TEID of SGW_A35 may be stored independently. Further, the eNB F-TEID may be identification information for user data or identification information for control information.

Further, the APN may be identification information that identifies the core network and the external network such as the DN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30 / UPGW_A130 / UPF_A235 that connects the core network_A90. The APN may be a DNN (Data Network Name). Therefore, APN may be expressed as DNN, and DNN may be expressed as APN.

The APN may be identification information that identifies such a gateway, or identification information that identifies an external network such as a DN. When a plurality of gateways connecting the core network and the DN are arranged, there may be a plurality of gateways that can be selected by the APN. Furthermore, one gateway may be selected from a plurality of these gateways by another method using identification information other than APN.

UE Radio Access Capability is identification information indicating the radio access capability of UE_A10. UE Network Capability includes security algorithms and key derivation functions supported by UE_A10. MS Network Capability is information that includes one or more information required for SGSN for UE_A10 having GERAN_A25 and / or UTRAN_A20 functions. Access Restriction is registration information for access restrictions. eNB Address is the IP address of eNB_A45. The MME UE S1AP ID is information that identifies UE_A10 in MME_A40 / CPF_A140 / AMF_A240. The eNB UE S1AP ID is information that identifies UE_A10 in eNB_A45.

APN in Use is a recently used APN. APN in Use may be a Data Network Identifier. This APN may consist of network identification information and default operator identification information. Further, APN in Use may be information that identifies the DN to which the PDU session is established.

Assigned Session Type is information indicating the type of PDU session. The Assigned Session Type may be the Assigned PDN Type. The type of PDU session can be IP or non-IP. In addition, if the type of PDU session is IP, it may further include information indicating the type of PDN assigned by the network. The Assigned Session Type may be IPv4, IPv6, or IPv4 v6.

Unless otherwise specified, IP Address is the IP address assigned to the UE. The IP address may be an IPv4 address, an IPv6 address, or an IPv6 prefix. If the Assigned Session Type indicates non-IP, the IP Address element may not be included.

The DN ID is identification information that distinguishes the core network_B190 from an external network such as a DN. Furthermore, the DN ID can also be used as information for selecting a gateway such as UPGW_A130 or PF_A235 that connects the core network_B190.

The DN ID may be identification information that identifies such a gateway, or identification information that identifies an external network such as a DN. When a plurality of gateways connecting the core network_B190 and the DN are arranged, there may be a plurality of gateways that can be selected by the DN ID. Furthermore, one gateway may be selected from the plurality of these gateways by another method using identification information other than the DN ID.

Furthermore, the DN ID may be information equal to or different from the APN. If the DN ID and the APN are different information, each device may manage the information indicating the correspondence between the DN ID and the APN, or may carry out a procedure for inquiring the APN using the DN ID. Alternatively, the procedure for inquiring the DN ID using the APN may be carried out.

The SCEF ID is the IP address of the SCEF used in the PDU session. The Default Bearer is information acquired and / or generated when the PDU session is established, and is EPS bearer identification information for identifying the default bearer associated with the PDU session.

The EPS Bearer ID is the identification information of the EPS bearer. Further, the EPS Bearer ID may be identification information for identifying SRB (Signalling Radio Bearer) and / or CRB (Control-plane Radio Bearer), or identification information for identifying DRB (Data Radio Bearer). TI (Transaction Identifier) is identification information that identifies a bidirectional message flow (Transaction). The EPS Bearer ID may be EPS bearer identification information that identifies the dedicated bearer. Therefore, the identification information that identifies the EPS bearer different from the default bearer may be used. TFT shows all packet filters associated with EPS bearers. The TFT is information that identifies a part of the user data to be transmitted / received, and UE_A10 transmits / receives the user data identified by the TFT using the EPS bearer associated with the TFT. In other words, UE_A10 sends and receives user data identified by the TFT using the RB (Radio Bearer) associated with the TFT. Further, the TFT may associate user data such as application data to be transmitted / received with an appropriate transfer path, or may be identification information for identifying the application data. In addition, UE_A10 may send and receive user data that cannot be identified by TFT using the default bearer. UE_A10 may also store the TFT associated with the default bearer in advance.

Default Bearer is EPS bearer identification information that identifies the default bearer associated with a PDN connection / PDU session. The EPS bearer may be a logical communication path established between UE_A10 and PGW_A30 / UPGW_A130 / UPF_A235, or may be a communication path constituting a PDN connection / PDU session. Further, the EPS bearer may be a default bearer or a dedicated bearer. In addition, the EPS bearer may be configured to include an RB established between UE_A10 and a base station and / or access point in the access network. Furthermore, there may be a one-to-one correspondence between RB and EPS bearer. Therefore, the RB identification information may be associated with the EPS bearer identification information on a one-to-one basis, or may be the same identification information. The RB may be SRB and / or CRB, or may be DRB. The Default Bearer may be information acquired by UE_A10 and / or SGW_A35 and / or PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 from the core network when the PDU session is established. The default bearer is an EPS bearer that is first established in a PDN connection / PDU session, and is an EPS bearer that can be established only once in one PDN connection / PDU session. The default bearer may be an EPS bearer that can be used to communicate user data that is not associated with a TFT. A decadeted bearer is an EPS bearer that is established after the default bearer is established during a PDN connection / PDU session, and is an EPS bearer that can be established multiple times during a single PDN connection / PDU session. is there. A decadeted bearer is an EPS bearer that can be used to communicate user data associated with a TFT.

User Identity is information that identifies the subscriber. The User Identity may be IMSI or MSISDN. Further, the User Identity may be identification information other than IMSI and MSISDN. Serving Node Information is information that identifies MME_A40 / CPF_A140 / AMF_A240 used in the PDU session, and may be the IP address of MME_A40 / CPF_A140 / AMF_A240.

eNB Address is the IP address of eNB_A45. The eNB ID is information that identifies the UE in eNB_A45. MME Address is the IP address of MME_A40 / CPF_A140 / AMF_A240. The MME ID is information that identifies MME_A40 / CPF_A140 / AMF_A240. gNB Address is the IP address of gNB_A122. The gNB ID is information that identifies gNB_A122. WAG Address is the IP address of WAG_A126. The WAG ID is information that identifies WAG_A126.

[3. Explanation of various procedures and terms / identification information in each embodiment]
Next, before explaining the detailed procedures of the various procedures in each of the embodiments in the present embodiment, in order to avoid duplicate explanations, terms specific to the present embodiment and main identification information used in each procedure will be described in advance. Hereinafter, various procedures in each embodiment are also referred to as this procedure.

First, the first state is a state in which UE_A10 acquires and / or holds network capability information of the network (access network and / or core network).

Here, the network capability information acquired and / or held by UE_A10 may be based on the identification information included in the message transmitted as the broadcast information from the access network and / or the device constituting the access network, or may be based on the identification information included in the RRC procedure. It may be based on the identification information contained in the message received between the UE_A and the access network and / or the devices constituting the access network, or it is transmitted and received with the UE_A in the core network registration procedure. It may be based on the identification information contained in the message, or it may be based on a combination of any two or more of these.

In addition, UE_A10 in the first state is notified from the access network and / or the core network (hereinafter also referred to as the network), and the network capability information acquired and / or retained is the support of the voice service by the network and / or the emergency call. It may be information indicating whether or not the service is supported and / or the function that enables handover and / or redirection to the network most suitable for the emergency call service is supported, and a combination of two or more of these may be used. It may be other information.

Further, the first state may be a state in which UE_A10 acquires and retains the capability information of the network that has not undergone the registration procedure during the registration procedure. Here, the network for which the registration procedure has not been performed may be another network within the same PLMN.

In other words, the first state may be a state in which UE_A10 requests, acquires, and holds the capability information of core network_B190 in the registration procedure to core network_A90, or UE_A10 is registered to core network_B190. In the procedure, the ability information of the core network_A may be requested, acquired, and retained. Here, the network capability information may include information on support for the voice call service function and / or bearer support dedicated to emergency calls.

The S1 mode is a UE mode in which messages can be sent and received using the S1 interface. The S1 interface may be composed of an S1-MME interface, an S1-U interface, and an X2 interface that connects radio base stations.

The UE in S1 mode can access the EPC via the eNB that provides the E-UTRA function and the EPC via the en-gNB that provides the NR function, for example.

Access to the EPC via eNB that provides the E-UTRA function and access to the EPC via en-gNB that provides the NR function are set to S1 mode, but they may be configured as different modes individually. ..

The N1 mode is a UE mode in which the UE can access 5GC via a 5G access network. Further, the N1 mode may be a UE mode capable of transmitting and receiving messages using the N1 interface. The N1 interface may be composed of an N1 interface and an Xn interface that connects radio base stations.

The UE in N1 mode can access, for example, 5GC via ng-eNB that provides the E-UTRA function and 5GC via gNB that provides the NR function.

The access to 5GC via ng-eNB that provides the E-UTRA function and the access to 5GC via gNB that provides the NR function are set to N1 mode, but they may be configured as different modes individually. .. The single registration mode is a UE mode indicating the operational status of mobility management registered by the UE in the core network of either the 4G system or the 5G system. The dual registration mode is a UE mode indicating the operational status of mobility management registered in the core network of the 4G system and / or the 5G system by the UE. Further, the UE may simultaneously and independently manage the state of mobility management in S1 mode and the state of mobility management in N1 mode.

The UE mode may be composed of the S1 mode and the N1 mode.

Next, the identification information in this embodiment will be described.

First, the first identification information in this embodiment supports voice services and / or emergency call services (including emergency call bearer or PDU session function support) via the core network_B190 that UE_A10 attempts to register. It may be information asking whether or not it is.

The first identifying information is that the core network_B190 that UE_A10 attempts to register has support for voice service and / or emergency call services (including emergency call bearer or PDU session function support). It may be information indicating a preference (Prf) that prioritizes this.

In addition, the core network_B190 that receives the request message containing the first identity from UE_A10 queries another core network within the same PLMN for network capability information, including support for voice and / or emergency call services. Alternatively, the AMF_A240 in the core network_B190 may hold or set the network capability information in advance.

When the first identification information is transmitted in the registration procedure, it is preferable that the first identification information is included in the registration request and transmitted, but any control message other than the registration request (registration request). For example, it may be transmitted by NAS message). Further, when the first identification information is transmitted in the PDU session establishment procedure, it is preferable that the first identification information is included in the PDU session establishment request (PDU Session Establishment Request) and transmitted. It may be sent by any control message other than Session Establishment Request (eg NAS message). Further, the first identification information may be transmitted by an arbitrary control message (for example, NAS message; (Periodic) Registration Update) at an arbitrary timing even after the registration procedure and / or the PDU session establishment procedure is completed. ..

Next, the second identification information in the present embodiment is the emergency call fallback to the access network connected by UE_A10 / the access network in the service area and / or the access network other than the core network and / or the core network in the emergency call connection. It may indicate whether or not the function is supported.

Here, the emergency call fallback support is information indicating whether or not the UE has a function of executing a dedicated service request (SERVICE REQUEST) for invoking a handover and / or redirection procedure by the network. It may be there.

Next, the tenth identification information in the present embodiment is ability information indicating whether or not the access network B and / or the core network_B190 supports the voice call service.

Further, the tenth identification information may be information indicating whether or not the access network and / or the core network different from the connected / local access network and the core network supports the voice call service. ..

For example, the tenth identification information may indicate whether or not the voice call service via the access network A'connecting to the core network_B190 is supported, or the core network A in the same PLMN as the core network_B190. It may indicate whether or not the voice call service via is supported.

Also, the tenth identification information is that when the connected / located access network and core network do not support the voice call service, the access network is redirected via another access network within the same PLMN. / Or it may be information indicating whether or not the redirection function is supported.

For example, if the connected / connected access network B and core network_B190 do not support voice call service, access network B supports voice call service based on the PDU session establishment request by UE_A10. It may be information indicating whether or not the function of handover and / or redirection via the access network A'or the access network A is supported.

UE_A10 may execute the processing of the subsequent emergency call connection based on the reception of the eleventh identification information.

The tenth identification information is, for example, IMS in the PS session in the information element (5GS network feature support IE) related to 5GS network function support included in the registration acceptance (REGISTRATION ACCEPT) message in the registration procedure to the network. It may be information about voice support (IMS voice over PS session indicator; IMS VoPS).

Next, the eleventh identification information in the present embodiment is ability information indicating whether or not the access network B and / or the core network_B190 supports the emergency call service. In other words, the eleventh identification information is information indicating whether or not the emergency call service is supported for each route of the emergency call connection via the core network B or for each access network.

For example, the eleventh identification information may be information indicating the presence or absence of emergency call service support via access network B and core network_B190, or may be information indicating the presence or absence of emergency call service support via access network B and core network_B190. It may be information indicating the presence / absence, information indicating the presence / absence of emergency call service support in both access network B and access network A'connecting to the core network_B190, and the core network regardless of the access network. It may be information indicating whether or not the emergency call service via _B190 is supported.

In other words, the eleventh identification information may be set for each access network and / or for each core network.

In addition, the eleventh identification information is that when the connected / located access network and core network do not support the emergency call service, the access network makes an emergency call connection request from UE_A10 separately within the same PLMN. Information indicating whether or not the function of handover and / or redirection via the access network of the above is supported may be used.

For example, if the connected / connected access network B and core network_B190 do not support the emergency call service, access network B will hand over the emergency call connection request from UE_A10 via access network A'and / /. Alternatively, it may be information indicating whether or not the redirection function is supported.

UE_A10 may execute the processing of the subsequent emergency call connection based on the reception of the eleventh identification information.

The eleventh identification information is, for example, the support of the emergency call service in the information element (5GS network feature support IE) related to the 5GS network function support included in the registration acceptance (REGISTRATION ACCEPT) message in the registration procedure to the network. It may be information about (Emergency service support indicator; EMC).

Next, the twelfth identification information in the present embodiment is the connected core network when the connected / local access network and the core network do not support the voice service and / or the emergency call service. It may be information indicating whether voice service and / or emergency call service via another core network in the same PLMN is supported, and voice service and / or emergency via another access network connected to core network B. It may be information indicating whether the calling service is supported.

For example, it may be information indicating whether voice service and / or emergency call service via core network_A90, which is another core network in the same PLMN as the connected core network_B190, is supported, and may be core. It may be information indicating whether voice service and / or emergency call service via access network A', which is another access network connected to network_B190, is supported.

UE_A10 may execute the processing of the subsequent emergency call connection based on the reception of the twelfth identification information.

In other words, if the emergency call service via the connected core network is possible in the 11th identification information, UE_A10 does not perform the processing based on the 12th identification information in the subsequent emergency call connection processing. Is also good.

In addition to this, the twelfth identification information may be information indicating a detailed emergency call procedure method executed by UE_A10 in combination with the eleventh identification information. In this case, UE_A10 executes the subsequent emergency call connection processing based on the 12th identification information even if the emergency call service via the connected core network is possible in the 11th identification information. You may.

Specifically, the support indicated by the twelfth identification information here is a handover in which the access network and / or the core network initiates the core network based on a SERVICE REQUEST containing the thirtieth identification information. And / or information indicating that the redirection function is supported, or information indicating that the core network executes SERVICE REQUEST including the 30th identification information for UE_A10. Further, here, the non-support indicated by the twelfth identification information may be information indicating that the access network and / or the core network does not support the SERVICE REQUEST including the thirtieth identification information by UE_A10.

In other words, the twelfth identification information may be set for each access network and / or for each core network. For example, when UE_A is located in the access network B connected to the core network B190, and the access network B connected to the core network B190 has the function of the emergency call service handover and / or the redirection procedure. , It may be shown that the access network B connected to the core network B190 has the function of handover and / or redirection procedure of the emergency call service. Further, the access network B connected to the core network B190 does not have the function of the emergency call service handover and / or the redirect procedure, and the access network A'connected to the core network B190 does not have the function of the emergency call service handover and / or the emergency call service handover. / Or if it has a redirection procedure function, the twelfth identification information may indicate that the access network A'connecting to the core network B190 has the emergency call service handover and / or redirection procedure function. In this case, in UE_A10, in the first condition determination for selecting an appropriate access domain for the emergency call connection, the access network A'connecting to the core network B190 indicated by the twelfth identification information is the handover of the emergency call service. And / or having the function of the redirection procedure may be determined to be unsupported.

The eleventh identification information is, for example, a fall of the emergency call service in the information element (5GS network feature support IE) related to 5GS network function support included in the registration acceptance (REGISTRATION ACCEPT) message in the registration procedure to the network. It may be information about the back (Emergency service fallback indicator; EMF) and may indicate the presence or absence of emergency call fallback support.

Next, the thirtieth identification information in the present embodiment is the handover and / or redirection to the connected / existing access network and / or the access network other than the core network and / or the core network in the emergency call connection. It may be information indicating that the request is made.

Next, the 40th identification information in the present embodiment is the handover and / or redirection to the connected / existing access network and / or the access network other than the core network and / or the core network in the emergency call connection. The thirtieth identification information indicating that the request is made may be information indicating that the information has been rejected, or may be a reason value indicating that the information has been rejected.

Further, the 40th identification information may be information indicating an access domain and / or a domain capable of emergency call reconnection by UE_A10 after the rejection is received.

For example, the thirtieth identification information received via the access network B and the core network_B190 may be rejected. In this case, the 40th identification information may indicate, in addition to the rejection, whether the access network A'connecting to the core network_B190 or the emergency call service via the core network A is supported.

More specifically, the 40th identification information may be information indicating a CS domain, information indicating core network A and / or access network A which is the same PLMN as core network B_190, or core network_B190. And / or information indicating access network A', or information indicating core network_B190 and / or access network B.

Next, various procedures in each embodiment will be described with reference to FIG. Hereinafter, various procedures in each embodiment are also referred to as this procedure, and this procedure includes reception of notification information (S1000) and / or RRC procedure (S1010), and registration procedure to the core network (Registration procedure) (S1020). And the decision to execute an emergency call connection by the UE (S1040), and the service request procedure (S1050) and the first procedure (S1060) for the emergency call, and / or the access network selection by the UE (S1065), and the second. Includes procedure (S1070) and IMS procedure for urgent emergency calls (S1080).

Here, the procedure (A) in this procedure may include the procedure (B) in this procedure and / or the procedure (C) in this procedure. The procedure (B) in this procedure is the reception of notification information, and the procedure (C) in this procedure may be an RRC procedure. In addition, the procedure (D) during this procedure includes the procedure (E) during this procedure and / or the procedure (F) during this procedure. The procedure (E) in this procedure may include the service request procedure for emergency call and / or the first procedure, and the procedure (F) in this procedure is the access network selection by the UE. May include.

In addition, the first procedure may include a handover procedure and / or a handover procedure or a redirection procedure. For example, the first procedure may be a handover procedure to the access network_A'connected to the core network_B, a handover procedure between the 5GS and EPS systems, or an RRC redirection to EPS (RRC redirection to EPS). RRC Redirection) procedure may be used.

The second procedure is any or a combination of the UE network (access network, core network, CS network, PDN, DN) registration procedure and / or session establishment procedure and / or bearer establishment procedure. May be executed. Here, for example, the registration procedure to the network may be a registration procedure to 5GC (Registration Procedure), an attachment procedure for an emergency call to an EPC (Attach Procedure), or a CS. The location may be registered in the network. In addition, the session establishment may be a PDU session establishment procedure for an emergency call to the core network_B, or a PDN connection procedure for an emergency bearer to an EPC (Emergency Bearer). PDN Connectivity Procedure) may be used.

Also, the IMS procedure for emergency calls may include IMS Registration and / or IMS emergency call connection procedures for emergency calls.

In addition, notification information, RRC procedure, registration procedure to the core network, service request procedure (for emergency call), PDU session establishment procedure (for emergency call), IMS registration procedure (for emergency call), IMS Details of the emergency call connection procedure will be described later.

Specifically, in this procedure, UE_A10 and each device first execute the procedure (A) in this procedure, so that UE_A10 acquires the capability information of the core network and / or the access network. Here, UE_A10 acquires or stores one or more capability information of the wireless access system and / or the core network during the procedure of (B) during this procedure and / or during the procedure of (C) during this procedure. You may.

Then, the registration procedure to the core network is executed (S1020). Based on the completion of the registration procedure of UE_A10 in the core network, each device transitions to the first state (S1030). Here, UE_A10 and each device may transition to the state in which UE_A10 is registered in the network (RM-REGISTERED state) by executing the registration procedure in the core network.

Next, UE_A10 in the first state determines the emergency call connection execution (S1040). The decision to execute the emergency call connection by the UE may be based on the operation of the user of the UE, or may be based on the software processing inside the UE. Furthermore, even if the subsequent behavior is executed based on the information acquired from the network (access network and / or core network) by the UE in the procedure (A) in this procedure and / or the registration procedure in the core network. The details will be described later.

Next, (S1040) UE_A10, which has decided to execute the emergency call connection, may execute the first condition determination in this procedure. The first condition determination is also for determining whether the network registered by the UE (core network and / or access network) supports the emergency call connection, and is an appropriate access domain for the emergency call connection. This is to select. Here, the first condition determination may be based on various information acquired by UE_A10 in the procedure so far. If the first condition determination is true, UE_A10 does not execute the procedure (D) in this procedure, but executes the subsequent procedure (second procedure and IMS procedure for emergency call). If the first condition determination is false, the procedure (D) in this procedure is executed.

Next, if the first condition determination is false, UE_A10 executes the second condition determination in this procedure. UE_A10 may start the procedure (E) in this procedure or the procedure (F) in this procedure based on the second condition determination. UE_A10 executes the service request procedure for emergency call (S1050) in the procedure (E) during this procedure, and performs the first procedure based on the execution and / or completion of the service request procedure. It may or may not be executed. In addition, UE_A10 may execute the procedure (F) in this procedure and select an appropriate network (access network and / or core network) for an emergency call connection. Details of procedure (D) during this procedure will be described later. UE_A10 may complete procedure (D) during this procedure based on the completion of procedure (F) during this procedure and / or (F) during this procedure.

Next, UE_A10 executes the second procedure in this procedure. As the second procedure in this procedure, as described above, the registration procedure to the UE network (access network, core network, CS network, PDN, DN), and / or the session establishment procedure, and / or the bearer establishment procedure. Any one of these or a combination thereof may be executed. In addition, UE_A10 may execute the second procedure based on the information acquired and / or stored so far in this procedure. In addition, the UE may execute the second procedure based on the network policy, the UE policy, etc., not limited to this information. The details of the second procedure will be described later.

UE_A10 then performs the IMS procedure (S1080) for the emergency call. As mentioned above, UE_A10 may perform IMS Registration and / or IMS emergency call connection procedures for emergency calls. UE_A10 provides IMS service via the core network by executing the IMS procedure for emergency calls via the network (access network and / or core network) connected in the second procedure described above. UE_A10 registration with and IMS emergency call connection established. Here, the IMS registration may be an IMS registration for an emergency call connection.

This procedure is complete.

In addition, each device exchanges various capability information and / or various request information of each device in the notification information and / or RRC procedure and / or the registration procedure in the core network and / or the service request procedure for emergency call. / Or may be obtained.

In addition, each device involved in this procedure sends and receives one or more identification information included in each control message by transmitting and receiving each control message described in this procedure, and stores each transmitted and received identification information as a context. May be good.

For simplification, the service request procedure and / or the PDU session establishment procedure and / or the IMS registration procedure and / or the IMS emergency call connection procedure may be referred to as an emergency call connection process.

[3.1. Overview of notification information]
First, the outline of the notification information will be described. The notification information corresponds to the notification information (S1000) shown in FIG. 10 described above.

The broadcast information may be included in a message and / or signal and / or beacon frame transmitted to UE_A10 from any of the devices of the wireless access system that constitutes AN and / or AN. Further, the broadcast information may include the tenth and / or eleventh identification information.

Here, for example, UE_A10 supports the establishment of a wireless connection for the emergency call service by the wireless access system attempting to connect by including the tenth and / or eleventh identification information in the notification information. You may recognize either whether or not you are doing so. In addition, UE_A10 may store this information in the context it holds. In addition, UE_A10 may store this information in the context it holds.

Further, UE_A10 may transition to the state 1 based on the reception of the broadcast information / and / or the completion of the RRC procedure described later and the registration procedure in the core network described later.

[3.2. Outline of RRC procedure]
Next, the RRC procedure will be described. Hereinafter, the RRC procedure is also referred to as this procedure. This procedure corresponds to the RRC procedure (S1010) shown in FIG. 10 described above.

In the RRC procedure, UE_A10 executes the transmission of a message and / or signal for requesting the establishment of a wireless connection for making an emergency call connection to AN and / or the device of the wireless access system constituting AN, and UE_A10. Execution of transmission of a reply message and / or signal from the device of the wireless access system to the message and / or signal from. In addition, the message and / or signal that UE_A10 sends to the device of the wireless access system in the RRC procedure may include information indicating that UE_A10 requires the establishment of a wireless connection to make an emergency call connection. Further, in the RRC procedure, the message and / or signal received from the device of the wireless access system received by UE_A10 may include the tenth and / or eleventh identification information.

Here, for example, UE_A10 may request the establishment of a wireless connection for making an emergency call connection by transmitting information indicating that UE_A10 requests the establishment of a wireless connection for making an emergency call connection. Alternatively, by receiving the tenth and / or eleventh identification information, it may be recognized that the request has been accepted.

Further, for example, UE_A10 is a wireless connection for the wireless access system to make an emergency call connection because the message and / or signal from the device of the wireless access system contains the 10th and / or 11th identification information. You may recognize whether or not it supports. In addition, UE_A10 may store this information in a context that holds and / or stores it.

[3.3. Outline of registration procedure to core network]
Next, the outline of the registration procedure will be described. Hereinafter, the registration establishment procedure is also referred to as this procedure.

This procedure is for UE_A10 to take the lead in registering with the network (access network and / or core network_B190 and / or DN (DN_A5 and / or PDN_A6)). UE_A10 can execute this procedure at any time, such as when the power is turned on, as long as it is not registered in the network. In other words, UE_A10 may start this procedure at any time as long as it is in the unregistered state (RM-DEREGISTERED state). Further, each device may transition to the registration state (RM-REGISTERED state) based on the completion of the registration procedure.

In addition, this procedure updates the location registration information of UE_A10 in the network and / or periodically notifies the network of the status of UE_A10 from UE_A10 and / or updates specific parameters regarding UE_A10 in the network. It may be the procedure of.

In the present embodiment, the tracking area (TA; also referred to as Tracking Area) is a range that can be represented by the position information of UE_A10 managed by the core network, and may be composed of, for example, one or more cells. Further, the TA may be a range in which a control message such as a paging message is broadcast, or a range in which UE_A10 can move without performing a handover procedure.

The TA list in this embodiment is a list including one or more TAs assigned to UE_A10 by the network. Note that UE_A10 may be able to move without executing the registration procedure while moving within one or more TAs included in the TA list. In other words, the TA list may be a set of information indicating the areas that UE_A10 can move to without performing the registration procedure.

UE_A10 may start this procedure when it has mobility across the TA (tracking area). In other words, UE_A10 may start this procedure when it moves to a TA different from the TA shown in the held TA list. In addition, UE_A10 may start this procedure when the running timer expires. In addition, UE_A10 may initiate this procedure when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. In addition, UE_A10 may initiate this procedure if there is a change in capability information and / or preferences regarding UE_A10's PDU session establishment. In addition, UE_A10 may initiate this procedure on a regular basis. UE_A10 is not limited to these, and this procedure can be executed at any timing as long as the PDU session is established.

The above-mentioned registration procedure to the core network may be a registration procedure for the emergency call service, and UE_A10 requests registration for the emergency call service in the registration request message in this procedure. As the identification information, for example, Emergency Registration may be set in the registration type and transmitted.

Further, after the registration procedure to the core network is completed, each device may transition to the first state, and each device in the first state executes the subsequent processes and procedures shown in FIG. 10 described above. You may.

[3.3.1. Example of registration procedure to core network]
An example of the procedure for executing the registration procedure to the core network will be described with reference to FIG. Hereinafter, this procedure refers to the registration procedure to the core network. This procedure corresponds to the registration procedure (S1020) for the core network shown in FIG. 10 described above.

Each step of this procedure will be described below.

First, UE_A10 starts the registration procedure (S1100) (S1102) (S1104) by sending a registration request message to AMF_A240 via gNB_A122 or eNB_B145. In addition, UE_A10 sends an SM (Session Management) message (for example, a PDU session establishment request message) in the registration request message, or sends an SM message (for example, a PDU session establishment request message) together with the registration request message. By doing so, the procedure for SM such as the PDU session establishment procedure may be started during the registration procedure.

Specifically, UE_A10 sends an RRC message containing a registration request message to gNB_A122 or eNB_B145 (S1100). When gNB_A122 or eNB_B145 receives an RRC message including a registration request message, it selects AMF_A240 as the NF or shared CP function to which the registration request message is routed (S1102). gNB_A122 or eNB_B145 extracts the registration request message from the received RRC messages, and sends or forwards the registration request message to the selected AMF_A240 (S1104). Here, gNB_A122 or eNB_B145 may select AMF_A240 based on the information contained in the RRC message. The registration request message may be a NAS (Non-Access-Stratum) message sent and received on the N1 interface. The RRC message may be a control message sent and received between UE_A10 and gNB_A122 or eNB_B145. Further, the NAS message is processed by the NAS layer, the RRC message is processed by the RRC layer, and the NAS layer may be a layer higher than the RRC layer.

In addition, UE_A10 may send a registration request message for each NSI when there are multiple NSIs requesting registration, or may send a plurality of registration request messages by including them in one or more RRC messages. Good. Further, the above-mentioned plurality of registration request messages may be included in one or more RRC messages as one registration request message and transmitted.

UE_A10 may include the first identity in the registration request message, which may include information regarding support for voice and / or emergency call services on the network attempting to connect.

AMF_A240 receives a registration request message and / or a control message different from the registration request message, and executes the first condition determination. The first conditional determination is for determining whether or not the network accepts the request of UE_A10. AMF_A240 starts the procedure (A) in this procedure when the first condition judgment is true, and starts the procedure (B) in this procedure when the first condition judgment is false.

Hereinafter, each step of the procedure (A) in this procedure will be described. AMF_A240 executes the fourth condition determination and starts the procedure (A) during this procedure. The fourth condition determination is for determining whether or not AMF_A240 sends and receives SM messages to and from SMF_A230. AMF_A240 selects SMF_A230 when the fourth condition determination is true, and sends and receives SM messages to and from the selected SMF_A230, and omits them when the fourth condition determination is false. (S1106).

In addition, AMF_A240 sends a Registration Accept message to UE_A10 via gNB_A122 or eNB_B145 based on the receipt of the registration request message from UE_A10 and / or the completion of sending and receiving SM messages to and from SMF_A230. (S1108). Here, the registration acceptance message may be sent and received included in the control message and the RRC message of the N2 interface. Furthermore, the registration acceptance message may be a NAS message sent and received on the N1 interface. Further, the registration acceptance message may be a response message to the registration request message.

When AMF_A240 receives an SM message indicating refusal from SMF_A230, it may cancel the procedure (A) during this procedure and start the procedure (B) during this procedure.

Further, if the fourth condition determination is true, AMF_A240 sends the registration acceptance message including an SM message such as a PDU session establishment acceptance message (for example, a PDU session establishment acceptance message), or the registration acceptance message. At the same time, an SM message such as a PDU session establishment acceptance message (for example, a PDU session establishment acceptance message) may be transmitted. Further, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Further, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included together with the registration request message and the fourth condition determination is true. AMF_A240 may indicate that the procedure for SM has been accepted by performing such a transmission method.

In addition, AMF_A240 may include the identification information of the 10th and / or 11 and / or 12 in the registration acceptance message, and by including these identification information, the request of UE_A10 is accepted and the wireless access. It may provide capability information indicating whether the system and / or core network supports the PDU session feature for voice and / or emergency call services, and the same or another network (access) within the same PLMN. It may indicate capability information indicating whether the network and / or core network) supports voice and / or emergency call services.

In addition, AMF_A240 determines whether or not to include the 10th and / or 11th and / or 12th identification information in the registration acceptance message, the received identification information and / or the network capability information, and / or the operator policy. And / or may be determined based on network conditions and / or user subscription information and the like.

UE_A10 receives a registration acceptance message via gNB_A122 or eNB_B145 (S1108). UE_A10 recognizes the contents of various identification information included in the registration acceptance message by receiving the registration acceptance message.

In addition, UE_A10 is voiced by the wireless access system and / or core network attempting to register by this procedure because the registration acceptance message contains the 10th and / or 11th and / or 12th identification information. It may recognize whether it supports the PDU session function for services and / or emergency call services, and the same or network (access network and / or core network) within the same PLMN is the voice service. And / or may recognize whether or not they support emergency call services. In addition, UE_A10 may store this information in the context it holds.

Here, for example, UE_A10 indicates that the wireless access system and / or the core network does not support the PDU session function for the emergency call service in the registration procedure to the core network. / Or, based on the receipt of the twelfth identification information, (E) and / or (F) in the procedure (D) in the procedure shown in FIG. 10 after the completion of this procedure may be executed. Conversely, for example, UE_A10 indicates that the wireless access system and / or the core network supports the PDU session function for voice service or emergency call service in the registration procedure to the core network. If it is decided to execute the emergency call connection after the completion of this procedure based on the reception of the 11th and / or 12th identification information (S1040), the second procedure (S1070) and the procedure shown in FIG. / Or you may perform the IMS procedure (S1080) for emergency calls.

UE_A10 may also send a Registration Complete message to AMF_A240 (S1110). When UE_A10 receives an SM message such as a PDU session establishment acceptance message, it may send the registration completion message including the SM message such as the PDU session establishment completion message, or by including the SM message. , May indicate that the procedure for SM is completed. Here, the registration completion message may be a NAS message sent and received on the N1 interface. Further, the registration completion message may be a response message to the registration acceptance message. Further, the registration completion message may be sent and received included in the RRC message and the control message of the N2 interface.

AMF_A240 receives a registration completion message (S1110). In addition, each device completes the procedure (A) in this procedure based on the transmission / reception of the registration acceptance message and / or the registration completion message.

Next, each step of the procedure (B) in this procedure will be described. AMF_A240 initiates the procedure (B) during this procedure by sending a Registration Reject message to UE_A10 via gNB_A122 or eNB_B145 (S1112). Further, UE_A10 recognizes that the request of UE_A10 has been rejected by receiving the registration refusal message or by not receiving the registration acceptance message. Each device completes the procedure (B) during this procedure based on the transmission and reception of the registration refusal message.

If the fourth condition determination is true, AMF_A240 may send the registration refusal message including an SM message meaning refusal such as a PDU session establishment refusal message, or send an SM message meaning refusal. Inclusion may indicate that the procedure for SM has been rejected. In that case, UE_A10 may further receive an SM message indicating rejection such as a PDU session establishment refusal message, or may recognize that the procedure for SM has been rejected.

Further, the registration refusal message may be a NAS message sent and received on the N1 interface. Further, the registration refusal message may be a response message to the registration request message. Further, the registration refusal message transmitted by AMF_A240 is not limited to this as long as it is a message that rejects the request of UE_A10. Further, the registration refusal message may be transmitted and received included in the control message and the RRC message of the N2 interface.

UE_A10 recognizes the contents of various identification information included in the registration refusal message by receiving the registration refusal message.

Further, the first condition determination may be executed based on the identification information and / or the subscriber information included in the registration request message and / or the operator policy. For example, the first condition determination may be true if the network allows the request for UE_A10. Further, the first condition determination may be false if the network does not allow the request of UE_A10. Further, the first condition determination may be true if the network to which UE_A10 is registered and / or the device in the network supports the function required by UE_A10, and false if it does not support it. Good. The condition for determining the truth of the first condition determination does not have to be limited to the above-mentioned condition.

Further, the fourth condition determination may be executed based on whether or not AMF_A240 has received the SM, and may be executed based on whether or not the registration request message includes the SM message. For example, the fourth condition determination may be true if AMF_A240 receives SM and / or if the registration request message contains an SM message, if AMF_A240 does not receive SM, and / Or it may be false if the registration request message does not contain the SM message. The condition for determining the truth of the fourth condition determination does not have to be limited to the above-mentioned condition.

[3.4. Outline of service request procedure]
Next, the outline of the service request procedure will be described. Hereinafter, the service request procedure is also referred to as this procedure. The service request procedure includes a network-led procedure and a UE-led procedure. In this embodiment, the UE-led service request procedure is targeted.

This procedure is a procedure led by the UE in the non-connected state (CM-IDLE state) to request the establishment of a connection with the AMF in the core network_B via the N1 interface. After executing, the state may be changed to the connection state (CM-CONNECTED state). It is also a procedure for an disconnected or connected UE to activate a U-Plane connection for an already established PDU session.

The procedure may also be performed as part of the procedure for an emergency service fallback. In addition, UE_A10 is from AMF in core network_B via access network_B to tenth and / or eleventh and / or tenth and / or eleventh and / or including another access network in the same PLMN that supports emergency call services. It may be executed when a registration acceptance message during the above-mentioned registration procedure containing 12 identification information is received. Such a service request procedure is also referred to as a service request procedure for an emergency call.

Based on the reception of the service acceptance message or service rejection message received in the service request procedure for the emergency call or the RRC message containing these, the UE performs the first procedure (S1060) and / or the access network selection shown in FIG. (S1065) may be executed.

[3.4.1. Example of service request procedure for emergency call]
The service request procedure for an emergency call will be described with reference to FIG. Hereinafter, this procedure refers to a service request procedure for an emergency call. This procedure corresponds to the service request procedure (S1050) for the emergency call shown in FIG. 10 described above. In addition, this procedure example relates to a service request procedure for an emergency call via access network_B and core network_B.

Each step of this procedure will be described below.

First, UE_A10 sends a service request message for an emergency call to AMF_A240 via access network_B (S400). Here, UE_A10 is a thirtieth identification requesting a handover and / or redirection to a network different from the connected network (access network and / or core network) in the service request message for an emergency call. Information may be included. In other words, UE_A may indicate that it is a service request for an emergency call by including the thirtieth identification information in the service request message.

Next, AMF_A may execute the first condition determination based on the service request message for the emergency call received from UE_A via the access network. The first condition determination is the identification information and / or network (access network and / or core network) capability information and / or network policy and / or user subscription information contained in the service request message received by AMF_A from UE_A. And / or may be performed based on a combination thereof.

Here, the first process in this procedure performed by AMF_A may include, for example, sending and receiving SM messages to SMF_A, or sending N2 request messages to the access network for emergency fallback. It may be included.

Further, AMF_A may execute the first process if the first condition determination is true, or may execute the subsequent steps without executing the first process if it is false. Good. In other words, AMF_A may execute (A) or (B) in this procedure based on the completion of the first process, or if it does not execute the first process, it receives a service request message. You may later execute (A) or (B) during this procedure.

Next, AMF_A determines the second condition based on the identification information contained in the service request message for the emergency call from UE_A and / or the completion of the first process and / or the result of the first process. May be executed. The second condition determination is for determining whether or not the network accepts the request from UE_A. AMF_A240 starts the procedure (A) in this procedure when the first condition judgment is true, and starts the procedure (B) in this procedure when the first condition judgment is false.

Further, in the procedure (A) during this procedure, AMF_A may send a service acceptance message (S404) to UE_A via the access network. In addition, UE_A may recognize that the request from UE_A has been accepted by the network by receiving a service acceptance message or an RRC message containing or meaning a service acceptance message via the access network.

In addition, in the procedure (B) during this procedure, AMF_A sends a service refusal message to UE_A via the access network (S406). Here, AMF_A may send a denial of service message to UE_A10 including a denial of service request for an emergency call and / or a 40th identification information indicating the access domain of the emergency call reconnection by UE_A. In addition, UE_A may recognize that the request from UE_A has been rejected by the network by receiving a denial of service message or an RRC message containing or meaning a denial of service message via the access network. An emergency call reconnection may be performed after the completion of this procedure based on the identification information contained in the service refusal message.

In addition, this procedure may be completed based on the completion of procedure (A) during this procedure or procedure (B) during this procedure.

[3.5. Outline of PDU session establishment procedure]
Next, the outline of the PDU session establishment procedure performed to establish the PDU session for the DN will be described. Hereinafter, the PDU session establishment procedure is also referred to as this procedure. This procedure is an example of the procedure executed in the second procedure (S1070) shown in FIG. 10 described above.

This procedure is a procedure for each device to establish a PDU session. The PDU session established in this procedure may be a procedure for establishing a PDU session for an emergency call service, and UE_A10 includes information that explicitly indicates the establishment of a PDU session dedicated to an emergency call in this procedure. However, a registration signal may be transmitted. Here, UE_A10 and / or each device in the network may execute this procedure based on the completion of the procedure up to the second procedure of FIG. 10 described above. In addition, each device may establish a PDU session based on the completion of this procedure. Further, each device may establish a plurality of PDU sessions by executing this procedure a plurality of times.

In addition, UE_A10 executes this procedure when it receives identification information indicating that the wireless access system and the core network support the PUD session function for emergency calls in the above-mentioned registration procedure for the core network. You may.

In addition, UE_A10 may obtain a P-CSCF address during or upon completion of this procedure. Further, here, the address of P-CSCF acquired by UE_A10 may be the address of P-CSCF_B capable of handling a PDU session for an emergency call. Specifically, the core network that receives the above-mentioned information explicitly indicating the establishment of the PDU session dedicated to the emergency call from UE_A10 may select an external gateway that can handle the PDU session dedicated to the emergency call, and the emergency call may be selected. The gateway in the core network that can handle the dedicated PDU session selects P-CSCF_B310 that can handle the PDU session dedicated to the emergency call, and responds to the PDU session establishment request dedicated to the emergency call by the PDU dedicated to the emergency call. It may be sent to UE_A10 including the address of P-CSCF_B310 that can handle the session.

[3.6. Overview of IMS registration procedure]
Next, the outline of the IMS registration procedure will be described. Hereinafter, this procedure refers to the IMS registration procedure. The IMS registration procedure is a procedure for UE_A10 to take the initiative in registering with IMS.

The initiation of this procedure may be carried out on the basis of UE_A10 completing the second procedure (S1070) during the procedure described in FIG. Based on the completion of the second procedure, registration to the UE network (access network, core network, CS network, PDN, DN) and / or session establishment and / or bearer establishment, or a combination thereof. May be completed.

Specifically, for example, the start of this procedure may be at any time when UE_A10 and / or each device in the network is in an established state of a PDU session. Here, the established PDU session may be based on the PDU session establishment procedure for an emergency call performed as the second procedure (S1080) of the procedure described in FIG. 10 above. The PDU session establishment procedure may be a PDU session establishment procedure for an emergency call. Furthermore, if UE_A10 that has completed the PDU session establishment procedure is not registered in IMS, that is, if the IP address of UE_A10 and the Public User Identity assigned from the network are not linked, this procedure can be performed at any time. May be started. In addition, UE_A10 and each IMS device may recognize that the registration state, that is, the IP address of UE_A10 and the Public User Identity assigned from the network are linked based on the completion of IMS registration.

Furthermore, this procedure determines the route of SIP (Session Initiation Protocol) messages in the IMS procedure after the IMS registration procedure.

[3.6.1. IMS registration procedure example]
An example of the procedure for executing the IMS registration procedure will be described with reference to FIG. Hereinafter, this procedure refers to the IMS registration procedure. This procedure may be included in the IMS registration procedure (S1080) for emergency calls. In addition, this procedure may be executed at the time of emergency call connection via core network_A and / or core network_B. Each step of this procedure will be described below.

First, UE_A10 transmits a REGISTER signal (S1200) requesting IMS registration for an emergency call to P-CSCF_B310 dedicated to emergency calls indicated by the network in the second procedure (S1070) described above. .. The second procedure may be, for example, a PDU session establishment procedure for an emergency call.

Next, the P-CSCF_B310 that received the REGISTER signal for the emergency call calls the E-CSCF_A330 via the I-CSCF, ATCF, or IBCF based on the UE_A10's territory information and the operator policy regarding the signal path. Transfer the REGISTER signal for (S1202). Specifically, UE_A10 transmits a REGISTER signal (S1204) to the P-CSCF_B310 dedicated to the emergency call, which includes information explicitly indicating that it is an IMS registration for an emergency call connection in the Contact header. To do.

Next, the P-CSCF_B310 that has received the REGISTER signal transfers the REGISTER signal to the E-CSCF via the I-CSCF, ATCF, or IBCF based on the territorial information of UE_A10 and the operator policy regarding the signal path.

Next, the E-CSCF_A330 that received the REGISTER signal for the emergency call is the IMS for the emergency call connection based on the information contained in the Contact header that explicitly indicates that it is the IMS registration for the emergency call connection. Creates and retains IMS registration information by associating the contact address in the Contact header with the information that explicitly indicates that it is an IMS registration for emergency call connection, and the public user identity to be registered. To do.

In addition, the S-CSCF that created the IMS registration information for the emergency call sends "200 OK" to UE_A10 as a response to the IMS registration request, including information indicating that the IMS registration for the emergency call connection has been completed. Send (S1206) (S1208) and this procedure is completed.

[3.7. Overview of IMS emergency call connection procedure]
Next, the outline of the IMS emergency call connection procedure will be described. Hereinafter, the IMS emergency call connection procedure is also referred to as this procedure. This procedure includes an IMS emergency call connection procedure using an emergency call dedicated PDU session and / or an IMS emergency call connection procedure using a normal PDU session and / or a CS (Circuit Switching) emergency call connection procedure. You can stay. Details of each procedure will be described below. This procedure is a procedure during the IMS procedure (S1080) for an emergency call shown in FIG. 10, and is for an emergency call during the second procedure (S1070) and / or the IMS procedure for an emergency call. It may be started based on the completion of the execution of the IMS registration procedure of.

[3.7.1. Example of IMS emergency call connection procedure using PDU session dedicated to emergency call]
The IMS emergency call connection procedure using the emergency call dedicated PDU session will be described with reference to FIG. Hereinafter, this procedure refers to the IMS emergency call connection procedure. This procedure may be included in the IMS registration procedure (S1080) for emergency calls. In addition, this procedure may be executed at the time of emergency call connection via core network_A and / or core network_B. For example, UE_A10 may send an IMS emergency call connection signal using an established emergency call dedicated PDU session. Each step of this procedure will be described below.

After completing the IMS registration for the emergency call connection described above, UE_A10 transmits an INVITE containing information indicating that the signal is dedicated to the emergency call to the P-CSCF_B310 (S1506), and is dedicated to the emergency call. Make a SIP dialog formation request.

Specifically, UE_A10 sets the route of the SIP signal based on the route information received in the IMS registration for the emergency call connection, and makes an emergency call connection to the P-CSCF_B310 dedicated to the emergency call for which the route has been set. The INVITE signal with the emergency service URN indicating that is set in the request URI and To header is transmitted (S1506). Upon receiving the INVITE, the P-CSCF_B310 creates an emergency call dedicated connection route, transfers the INVITE signal to the emergency stand via the emergency call dedicated CSCF (E-CSCF), etc., and requests the formation of a dialog dedicated to the emergency call. Upon receiving the notification of successful dialog formation, P-CSCF_B310 sends "200 OK" to UE_A10 to notify that the dialog formation dedicated to the emergency call has been successful (S1510).

[3.7.2.CS Emergency Call Connection Procedure Example]
Next, the CS emergency call connection procedure (hereinafter also referred to as this procedure) will be described. This procedure may be included in the IMS registration procedure (S1080) for emergency calls. In addition, this procedure may be executed at the time of emergency call connection via the CS network.

This procedure is a procedure for emergency call connection via CS network, and UE_A10 is the procedure described above and / or various information received in each procedure described above, and / or the network policy, and / or UE. The emergency call connection procedure via the CS network may be executed based on the policy. Further, UE_A10 may execute this procedure after executing location registration for an emergency call to the CS network as the second procedure described above.

Upon receiving a rejection or redirect message from IMS_A7, UE_A10 detects whether the connected core network supports the emergency call-only PDU session function, and if it does not support the emergency call-only PDU session function, and Another core network in the same PLMN does not support the voice service function, or another core network in the same PLMN supports the voice service function but does not support the emergency call-only PDU session function. If so, a CS (Circuit Switching) emergency call connection may be made.

Specifically, UE_A10 detects that the core network that is trying to connect or is connected does not support the emergency call dedicated PDU session function by the registration procedure or notification information, and further, the above-mentioned registration procedure. Based on the network function information or network capability information of another core network in the same PLMN acquired in step 1, if another core network in the same PLMN does not support the voice service function, CS (Circuit Switching; Circuit Switching) ) You may make a CS emergency call connection over the network.

Based on the network function information of another core network in the same PLMN obtained in the registration procedure, another core network in the same PLMN supports the voice service function, but supports the emergency call-only PDU session function. If not, UE_A10 confirms the location. At this time, if you are in another network, you may execute a CS emergency call connection.

Also, if the redirect message does not contain information prompting an IMS emergency call connection to another core network that supports the voice service function within the same PLMN and the emergency call-only PDU session function, UE_A10 is present. Check the service area position. At this time, if you are in another network, you may execute this procedure.

[3.8. Outline of UE function request procedure]
Next, the procedure for requesting the UE function will be described. Hereinafter, the procedure for requesting the UE function is also referred to as this procedure. This procedure may be executed during the core network registration procedure (S1020) shown in FIG. 10 described above, and is not limited to the core network registration procedure (S1020), and is executed at any time. You may.

Each step of this procedure will be described below.

First, in connection with the process of determining the twelfth identification information to be included in the registration acceptance message described above, AMF_A240 is sent to the access network and / or the core network other than the connected / territory access network and / or the core network. Send N2: UE Capability Match Request message to access network _B120 and / or access network _A'81 if it determines that it is necessary to obtain UE feature information, including information about whether or not the emergency call fallback feature is supported. (S1400).

N2: The access network_B120 and / or access network_A'81 that received the UE Capability Match Request message is to the access network and / or the access network other than the core network and / or the core network. If UE function information including information on whether or not the emergency call fallback function is supported is not retained, an emergency call fall to an access network other than the connected / local access network and / or the core network and / or the core network. Send an RRC: UE Capability Enquiry message to UE_A10 to request UE feature information, including information about whether back features are supported (S1402).

Upon receiving the RRC: UE Capability Inquiry message, UE_A10 sends an RRC: UE Capability Information message to access network _B120 and / or access network_A'81 (S1404), connecting / territory access network and / Or notify UE function information including information on access networks other than the core network and / or whether or not the emergency call fallback function is supported to the core network.

RRC: The access network_B120 and / or access network_A'81 that receives the UE Capability Information message has UE feature information and access, including information about whether the emergency call fallback feature is supported for the access network and / or the core network. Determine the functional compatibility of the network and UE for the emergency call service based on the support of the emergency call fallback function of the network and / or the core network.

The access network_B120 and / or the access network_A'81 sends N2: UE Capability Match Indication and / or N2: UE Capability Info Response to AMF_A240 (S1406) (S1408) to notify the above-mentioned determination result.

At this time, the access network_B120 and / or the access network_A'81 also provides UE function information including information on whether or not the emergency call fallback function is supported for the access network and / or the core network N2: UE Capability Match. Indication and / or N2: May be posted on UE Capability Info Response and sent to AMF_A240 (S1406) (S1408).

[3.9. Attach procedure]
First, the attachment procedure will be described with reference to FIG. The attach procedure is a procedure in EPS. Hereinafter, this procedure refers to the attachment procedure. This procedure is for the UE to be registered in the core network_A. Each step of this procedure will be described below.

First, the UE initiates the attach procedure by sending an Attach Request message to the MME via the eNB (S1502). The UE may send the attach request message including the PDN connection request message, or may request that the PDN connection procedure be performed during the attach procedure by including the PDN connection request message.

The MME sends an Attach Accept message to the UE via the eNB based on the receipt of the attach request message and / or the session generation response message and / or the completion of the PDN connection (S1504).

Here, the MME may send the attach acceptance message including information regarding support for the emergency call service via the core network A90.

When the UE receives the attach acceptance message, it sends an attach completion message to the MME via the eNB (S1506).

[3.10. Tracking area update procedure]
Next, the outline of the tracking area update procedure will be described. Hereinafter, this procedure refers to the tracking area update procedure. This procedure updates the location registration information of the UE in the network (access network and / or core network_A) and / or periodically notifies the network of the UE status from the UE and / or This is a procedure for updating specific parameters related to UE in the network. The UE can execute this procedure at any time as long as the PDN connection is established.

The procedure for updating the tracking area may be the same as the procedure for the attach procedure.

In the tracking area update procedure procedure, the control message sent and received in the attach procedure can be replaced with the control message for the tracking area update procedure. For example, an attach request message sent or received in an attach procedure may be replaced with a Tracking Area Update request message, and an attach accept message may be replaced with a Tracking Area Update accept message. .. In addition, the attachment completion message may be replaced with a Tracking Area Update complete message.

Further, the identification information included in the control message during the attach procedure and transmitted / received may be transmitted / received including the control message during the tracking area update procedure. Further, the behavior of each device implemented based on the reception of the control message during the attach procedure and / or the reception of the identification information contained in the control message during the attach procedure is the reception of the control message during the tracking area update procedure. And / or may be implemented based on the receipt of identification information contained in the control message during the tracking area update procedure. Further, the behavior of each device implemented based on the completion of the attach procedure may be implemented based on the completion of the tracking area update procedure.

[4. Each embodiment]
Each embodiment of the present invention will be described below.

[4.1. First Embodiment]
A first embodiment of the present invention will be described with reference to FIGS. 10 and 11. Hereinafter, the first embodiment is also referred to as the present embodiment.

This embodiment mainly includes the registration procedure for the core network shown in FIG. 10 (S1020; hereinafter also simply referred to as the registration procedure) and (D) in the procedure shown in FIG. 10 based on the completion of the registration procedure. Related to the behavior of the procedure. Further, in the present embodiment, in the registration procedure to the core network (S1020), when the registration acceptance message (S1108) received by UE_A from the core network_B contains the 11th and / or 12th identification information. Regarding.

First, UE_A is operating in Single registration mode, operating in N1 mode, and in the state of being in the access network_B connected to the core network_B. That is, the UE is in a state where the position is registered in the AMF.

In this case, it is decided to execute the emergency call connection (S1040) after the registration procedure to the core network (S1020) is completed according to the contents of the 11th and / or 12th identification information included in the registration acceptance message received by UE_A. The UE_A and / or each device may perform the emergency call connection process described below.

More specifically, UE_A and / or each device may perform the first procedure example described below.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support. In this case, it may mean that the emergency call service via the access network A'and the access network B connected to the core network B190 is not supported.

In addition, if UE_A has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, an emergency call included in the registration acceptance message received by UE_A. If the twelfth identification information indicating the connection method indicates support, in executing the emergency call connection process, UE_A10 issues a service request (SERVICE REQUEST) (S1050) including the thirtieth identification information as the emergency call connection method. Select and initiate and execute redirection and / or handover processing by the network to the core network A90 (S1060).

Note that the UE_A and / or each device may execute the second procedure example described below, which is different from the first procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support. In this case, it may mean that the emergency call service via the access network A'and the access network B connected to the core network B190 is not supported.

In addition, if UE_A has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, an emergency call included in the registration acceptance message received by UE_A. If the twelfth identification information indicating the connection method indicates that it is not supported, UE_A10 stops N1 mode, selects access network A, and makes an emergency call connection via core network A90 in executing emergency call connection processing. If the twelfth identity indicates support for fallback of emergency call services over access network A', select access network A'and redirect the network to core network A90. And / or the handover process may be started and executed (S1060).

Note that UE_A and / or each device may execute a third procedure example described below, which is different from the first procedure example and the second procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core. The emergency call service via network B190 may be a procedure indicating non-support. In this case, it may mean that the emergency call service via the access network A'and the access network B connected to the core network B190 is not supported.

In addition, if UE_A does not have the ability to perform a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, the emergency call connection included in the registration acceptance message received by UE_A. Regardless of the twelfth identification information indicating the method, in executing the emergency call connection process, UE_A10 stops the N1 mode, selects the access network A, and executes the emergency call connection via the core network A90.

Note that the UE_A and / or each device may execute the fourth procedure example described below, which is different from the first procedure example to the third procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via the access network A'connecting to B190 may be the procedure indicating support.

In addition, if UE_A has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, an emergency call included in the registration acceptance message received by UE_A. If the twelfth identification information indicating the connection method indicates support, in executing the emergency call connection process, UE_A10 issues a service request (SERVICE REQUEST) (S1050) including the thirtieth identification information as the emergency call connection method. Select and initiate and execute redirection and / or handover processing by the network to the core network A90 (S1060).

Note that the UE_A and / or each device may execute the fifth procedure example described below, which is different from the first procedure example to the fourth procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via the access network A'connecting to B190 may be the procedure indicating support.

In addition, if UE_A has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, an emergency call included in the registration acceptance message received by UE_A. If the twelfth identification information indicating the connection method indicates that it is not supported, UE_A10 stops N1 mode, selects access network A, and makes an emergency call connection via core network A90 in executing emergency call connection processing. Or you may select access network A'and make an emergency call connection via access network A'that connects to core network B190, or the twelfth identification information is access network A'. Access network A'may be selected to initiate and execute redirection and / or handover processing by the network to core network A90 if it indicates support for fallback of the via emergency call service (S1060).

Furthermore, if UE_A does not have the ability to execute a dedicated service request (SERVICE REQUEST) to invoke network handover and / or redirection procedures, UE_A10 will enter N1 mode in the emergency call connection process execution. You may stop and select access network A to make an emergency call connection via core network A90, or select access network A'and make an emergency call via access network A'to connect to core network B190. You may make a connection.

Note that the UE_A and / or each device may execute the sixth procedure example described below, which is different from the first procedure example to the fifth procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The procedure may be such that the emergency call service via access network B connecting to B190 or via access network A'and access network B connecting to core network B190 indicates support.

In this case, whether or not it has a function to execute a dedicated service request (SERVICE REQUEST) for invoking the handover and / or redirection procedure by the UE_A network and the emergency included in the registration acceptance message received by UE_A. An emergency call connection is executed via the access network B connected to the core network B190 without depending on the twelfth identification information indicating the call connection method.

[4.2. Second Embodiment]
A second embodiment of the present invention will be described with reference to FIGS. 10 and 11. Hereinafter, the second embodiment is also referred to as the present embodiment.

This embodiment mainly includes the registration procedure for the core network shown in FIG. 10 (S1020; hereinafter also simply referred to as the registration procedure) and (D) in the procedure shown in FIG. 10 based on the completion of the registration procedure. Related to the behavior of the procedure. Further, in the present embodiment, in the registration procedure to the core network (S1020), when the registration acceptance message (S1108) received by UE_A from the core network_B contains the 11th and / or 12th identification information. Regarding.

First, UE_A is operating in Single registration mode, operating in N1 mode, and in the state of being in the access network_A'connecting to the core network_B. That is, the UE is in a state where the position is registered in the AMF.

In this case, it is decided to execute the emergency call connection (S1040) after the registration procedure to the core network (S1020) is completed according to the contents of the 11th and / or 12th identification information included in the registration acceptance message received by UE_A. The UE_A and / or each device may perform the emergency call connection process described below.

More specifically, the UE_A and / or each device may execute a seventh procedure example described below, which is different from the first procedure example to the sixth procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support. In this case, it may mean that the emergency call service via the access network A'and the access network B connected to the core network B190 is not supported.

In addition, if UE_A has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, an emergency call included in the registration acceptance message received by UE_A. If the twelfth identification information indicating the connection method indicates support, in executing the emergency call connection process, UE_A10 issues a service request (SERVICE REQUEST) (S1050) including the thirtieth identification information as the emergency call connection method. Select and initiate and execute redirection and / or handover processing by the network to the core network A90 (S1060).

Note that the UE_A and / or each device may execute the eighth procedure example described below, which is different from the first procedure example to the seventh procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support. In this case, it may mean that the emergency call service via the access network A'and the access network B connected to the core network B190 is not supported.

In addition, if UE_A has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, an emergency call included in the registration acceptance message received by UE_A. If the twelfth identification information indicating the connection method indicates that it is not supported, UE_A10 stops N1 mode, selects access network A, and makes an emergency call connection via core network A90 in executing emergency call connection processing. If the twelfth identity indicates support for fallback of emergency call services over access network B, select access network B and network redirection to core network A90 and /. Alternatively, the handover process may be started and executed (S1060).

Note that the UE_A and / or each device may execute the ninth procedure example described below, which is different from the first procedure example to the eighth procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support. In this case, it may mean that the emergency call service via the access network A'and the access network B connected to the core network B190 is not supported.

In addition, if UE_A does not have the ability to perform a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, the emergency call connection included in the registration acceptance message received by UE_A. Regardless of the twelfth identification information indicating the method, in executing the emergency call connection process, UE_A10 stops the N1 mode, selects the access network A, and executes the emergency call connection via the core network A90.

Note that the UE_A and / or each device may execute the tenth procedure example described below, which is different from the first procedure example to the ninth procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via access network B connecting to B190 may be the procedure indicating support.

In addition, if UE_A has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, an emergency call included in the registration acceptance message received by UE_A. If the twelfth identification information indicating the connection method indicates support, in executing the emergency call connection process, UE_A10 issues a service request (SERVICE REQUEST) (S1050) including the thirtieth identification information as the emergency call connection method. Select and initiate and execute redirection and / or handover processing by the network to the core network A90 (S1060).

Note that UE_A and / or each device may execute the eleventh procedure example described below, which is different from the first procedure example to the tenth procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via access network B connecting to B190 may be the procedure indicating support.

In addition, if UE_A has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures, an emergency call included in the registration acceptance message received by UE_A. If the twelfth identification information indicating the connection method indicates that it is not supported, UE_A10 stops the N1 mode function, selects access network A, and makes an emergency call via the core network A90 in executing the emergency call connection process. The connection may be made, access network B may be selected and an emergency call connection via access network B connecting to core network B190 may be made, or the twelfth identification information may be via access network B. If it indicates support for fallback of the emergency call service, access network B may be selected to initiate and execute redirection and / or handover processing by the network to core network A90 (S1060).

Furthermore, if UE_A does not have the ability to execute a dedicated service request (SERVICE REQUEST) to invoke network handover and / or redirection procedures, UE_A10 will have the N1 mode function in executing emergency call connection processing. You may stop and select access network A to make an emergency call connection via core network A90, or select access network B and connect to core network B190. May be executed.

Note that the UE_A and / or each device may execute the twelfth procedure example described below, which is different from the first procedure example to the eleventh procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The procedure may be such that the emergency call service via access network A'connecting to B190 or via access network A'and access network B connecting to core network B190 indicates support.

In this case, whether or not it has a function to execute a dedicated service request (SERVICE REQUEST) for invoking the handover and / or redirection procedure by the UE_A network and the emergency included in the registration acceptance message received by UE_A. An emergency call connection is executed via the access network A'connecting to the core network B190 without depending on the twelfth identification information indicating the call connection method.

Further, the behavior after the registration acceptance message including the 11th and / or 12th identification information is transmitted and received may not be limited to these.

[4.3. Third Embodiment]
A third embodiment of the present invention will be described with reference to FIGS. 10 and 11. Hereinafter, the third embodiment is also referred to as the present embodiment.

This embodiment mainly describes (D) in the procedure for registering to the core network shown in FIG. 10 (S1020; hereinafter also simply referred to as the registration procedure) and the procedure shown in FIG. 10 based on the completion of the registration procedure. Related to the behavior of the procedure. Further, in the present embodiment, in the registration procedure to the core network (S1020), the content of the 11th and / or 12th identification information included in the registration acceptance message (S1108) transmitted from the core network is determined and to UE_A. Regarding the transmission of.

The following behavior may be performed in determining the content of the 11th and / or 12th identification information to be included in the registration acceptance message sent from the core network and in sending to UE_A.

For example, if the core network shows the twelfth identification information in the registration acceptance message in the registration procedure, not only the emergency call service is supported, but also the voice call service is supported and / or UE_A is handed over by the network and / or The twelfth identification information may be shown in consideration of the second identification information indicating whether or not the user has a function to execute a dedicated service request (SERVICE REQUEST) for invoking the redirection procedure.

More specifically, the core network_B190 may execute the first procedure example shown below.

If the core network_B190 notifies the UE_A10 of the twelfth identity, and the eleventh identity indicates that the emergency call service via the core network_B190 does not support it regardless of the access network, the core Network_B190 is supported with a twelfth identity only if voice and / or emergency call services are supported via core network A, another core network in the same PLMN as core network_B190. May be notified.

Note that the core network_B190 may execute the second procedure example shown below, which is different from the first procedure example.

Indicates that the core network_B190 notifies UE_A10 of the twelfth identification information, and that the eleventh identification information supports emergency call service only via the access network A'connecting to the core network_B190. In that case, the core network_B190 may notify the support with the twelfth identification information only if the access network A'connecting to the core network_B190 supports voice service and / or emergency call service. ..

The core network_B190 may execute the third procedure example to the fourth procedure example shown below.

First, UE_A is operating in Single registration mode and / or dual registration mode, and is in a state of being in the access network_B connected to the core network_B. In this case, the core network_B190 considers the second identification information in addition to the consideration of whether or not the voice call service is supported described in the first procedure example and the second procedure example in the notification of the twelfth identification information. You can do it.

In the third procedure example, for example, when the eleventh identification information indicates that the emergency call service via the core network B190 is not supported, and the emergency call service via access network A'and / or access network B is used. If fallback is possible, the core network_B190 may notify non-support with a twelfth identity indicating the emergency call connection method if the second identity indicates support.

Further, in the fourth procedure example, for example, when the emergency call service via the access network A'where the eleventh identification information connects to the core network B190 indicates support, and via the access network A'and / or the access network. If emergency call service fallback via B is possible, core network_B190 will notify non-support with a twelfth identity indicating the emergency call connection method if the second identity indicates support. You can do it.

The core network_B190 may execute the sixth procedure example from the fifth procedure example shown below.

First, UE_A is operating in Single registration mode and / or dual registration mode, is operating in N1 mode, and is in a state of being in the access network_A'connected to the core network_B. That is, the UE is in a state where the position is registered in the AMF. In this case, the core network_B190 considers the second identification information in addition to the consideration of whether or not the voice call service is supported described in the first procedure example and the second procedure example in the notification of the twelfth identification information. You can do it.

In the fifth procedure example, for example, when the eleventh identification information indicates that the emergency call service via the core network B190 is not supported, and the emergency call service via access network A'and / or access network B is used. If fallback is possible, the core network_B190 may notify non-support with a twelfth identity indicating the emergency call connection method if the second identity indicates support.

Further, in the sixth procedure example, for example, when the eleventh identification information indicates that the emergency call service via the core network B190 is not supported, and the emergency call is made via the access network A'and / or the access network B. If service fallback is possible, the core network_B190 may notify non-support with a twelfth identity indicating the emergency call connection method if the second identity indicates support.

Here, when the emergency call service can be fallback, the service request including the thirtieth identification information via the access network A'connecting to the core network B190 and / or via the access network B connecting to the core network B190. It may mean whether the access network and / or the core network has a handover and / or redirection function to be performed based on (SERVICE REQUEST).

In other words, for a method of setting the twelfth identification information based on whether the access network and / or the core network has the ability to initiate the handover and / or redirection procedure of the emergency call service. In the procedure example to the sixth procedure example, the second identification information is shown in addition to the setting method based on the ability of the access network and / or the core network to activate the handover and / or redirection procedure of the emergency call service. A twelfth identification may be set based on whether UE_A10 has the ability to execute a dedicated SERVICE REQUEST to invoke network handover and / or redirection procedures.

Further, the method in which the core network determines the function of the UE does not have to be limited to the method based on the second identification information.

For example, the core network may acquire the UE capability in the UE function request procedure shown in FIG.

Furthermore, regarding the method in which the core network sets the twelfth identification information so far, the method based on the access network and / or the ability of the core network to activate the handover and / or redirection procedure of the emergency call service and / or the second method. Although the method based on the identification information has been described, the twelfth identification information may be determined based on the method described below in addition to the method described above.

Specifically, the twelfth identification information may be set based on the setting information of the operator operating the access network and / or the core network. The configuration information may be, or is not limited to, network policy and / or operator policy and / or service policy and / or local policy and / or network implementation matter.

For example, even if the access network and / or the core network has the ability to initiate the handover and / or redirection procedures for the emergency call service, it is based on the configuration information of the operator operating the access network and / or the core network. Therefore, the twelfth identification information may be set as unsupported.

The setting information may be set for each specific geographical area.

Here, the geographical area may be one or more registration areas and / or tracking areas.

In other words, in the case of AMFs belonging to the same geographical area, even if they are different AMFs, the setting information is set in common in order to ensure the common operation regarding the emergency call fallback of the UEs belonging to the same geographical area. You may be.

Further, in the present embodiment, the twelfth identification information notified by the core network may further include not only the support of the emergency call service but also the information meaning the support of the voice call service.

At this time, UE_A10 is a service including the 30th identification information for handover or redirection to the access network and / or the core network supporting the emergency call service based on the 12th identification information. Send a request (SERVICE REQUEST) (S1050) to the core network.

UE_A and / or each device that decides to execute an emergency call connection (S1040) after completing the registration procedure (S1020) to the core network based on the contents of the 11th and / or 12th identification information included in the above registration acceptance message. , The following procedure may be executed.

[4.4. Fourth Embodiment]
A fourth embodiment of the present invention will be described with reference to FIG. Hereinafter, the fourth embodiment will also be referred to as the present embodiment.

This embodiment mainly describes the above-mentioned registration procedure for the core network (S1020; hereinafter also simply referred to as registration procedure) and / or the service request procedure (S1050) and / or FIG. 10 shown in FIG. It is related to the behavior of procedure (D) in the procedure and the subsequent procedures.

Specifically, this embodiment is in the process of handling the 11th and / or 12th identification information included in the registration acceptance message received in the registration procedure and the procedure described in FIG. 10 executed based on these. It is related to the behavior of UE_A and each device after receiving the 40th identification information included in the rejection message sent from the network in the procedure of E) (service request procedure; S1050).

So far, in the first to third embodiments, the UE_A and / or the core network has prevented the failure of the emergency call connection by executing the process based on the 11th and / or the twelfth identification information. We have described the method for realizing an immediate call connection. Further, in the present embodiment, in the process related to the emergency call service, after the erroneous emergency call connection is activated, the process to be performed to relieve the emergency call connection may be executed. To do.

Specifically, the terminal and the core network may execute the 21st procedure example shown below.

UE_A10 may retain the eleventh identification information and / or the twelfth identification information after executing the registration procedure in the initial procedure.

Subsequently, UE_A10 is a service request containing the thirtieth identification information based on the eleventh identification information and / or the twelfth identification information already held after the decision to execute the emergency call connection (S1040). The emergency call connection procedure using SERVICE REQUEST) is executed, but the procedure may be rejected by the core network_B190. The refusal message may include the 40th identification information.

Here, the eleventh identification information held by UE_A10 may be information indicating that the emergency call service via the core network_B190 is not supported regardless of the access network.

In this case, UE_A10 will receive an access domain and / or a SERVICE REJECT message from the 11th and / or 12th identification information and / or core network_B190 in an emergency call reconnection. Alternatively, the CS domain may be selected as the domain selection process.

Further, the terminal and the core network may execute the 22nd procedure example shown below, which is different from the 21st procedure example.

UE_A10 may retain the eleventh identification information and / or the twelfth identification information after executing the registration procedure in the initial procedure.

After the decision to execute the emergency call connection (S1040), UE_A10 then makes a service request (SERVICE) containing the 30th identification information based on the 11th identification information and / or the 12th identification information already held. The emergency call connection procedure using REQUEST) is executed, but the procedure may be rejected by the core network_B190. The refusal message may include the 40th identification information.

Here, the eleventh identification information held by UE_A10 may be information indicating that the emergency call service via the access network A'connecting to the core network_B190 is supported.

In this case, UE_A10 puts UE_A10 in S1 mode on an emergency call reconnection based on the 11th identification information and / or the 12th identification information and / or the reception of a SERVICE REJECT message from the core network_B190. If the above is supported, core network A may be selected as the access domain and / or domain selection process. If UE_A10 does not support S1 mode, the CS domain may be selected as the access domain and / or domain selection process.

Further, the terminal and the core network may execute the 23rd procedure example shown below, which is different from the 21st and 22nd procedure examples.

UE_A10 may retain the eleventh identification information and / or the twelfth identification information after executing the registration procedure in the initial procedure.

After the decision to execute the emergency call connection (S1040), UE_A10 then makes a service request (SERVICE) containing the 30th identification information based on the 11th identification information and / or the 12th identification information already held. The emergency call connection procedure using REQUEST) is executed, but the procedure may be rejected by the core network_B190. The refusal message may include the 40th identification information.

Here, the eleventh identification information held by UE_A10 may be information indicating that the emergency call service via the access network B connected to the core network_B190 and the access network A'is supported.

In this case, UE_A10 will have UE_A10 S1 based on the 11th identification information and / or the 12th identification information and / or the reception of the SERVICE REJECT rejection message from the core network_B190 in the emergency call reconnection. If the mode is supported, the access domain and / or the access network A'or connecting to the core network_B190 may be selected as the domain selection process. If UE_A10 does not support S1 mode, access network A'connecting to the CS domain or core network_B190 may be selected as the access domain and / or domain selection process.

Further, the terminal and the core network may execute the 24th procedure example shown below, which is different from the 21st to 23rd procedure examples.

UE_A10 may retain the eleventh identification information and / or the twelfth identification information after executing the registration procedure in the initial procedure.

After the decision to execute the emergency call connection (S1040), UE_A10 then makes a service request (SERVICE) containing the 30th identification information based on the 11th identification information and / or the 12th identification information already held. The emergency call connection procedure using REQUEST) is executed, but the procedure may be rejected by the core network_B190. The refusal message may include the 40th identification information.

Here, the 40th identification information may include information indicating a CS domain.

In this case, UE_A10, in an emergency call reconnection, CS as an access domain and / or domain selection process based on the receipt of the 40th identification information contained in the SERVICE REJECT message from the core network_B190. You may select a domain.

Further, the terminal and the core network may execute the 25th procedure example shown below, which is different from the 21st to 24th procedure examples.

UE_A10 may retain the eleventh identification information and / or the twelfth identification information after executing the registration procedure in the initial procedure.

After the decision to execute the emergency call connection (S1040), UE_A10 then makes a service request (SERVICE) containing the 30th identification information based on the 11th identification information and / or the 12th identification information already held. The emergency call connection procedure using REQUEST) is executed, but the procedure may be rejected by the core network_B190. The refusal message may include the 40th identification information.

Here, the 40th identification information may include information indicating the core network A and / or the access network A which is the same PLMN as the core network_B190.

In this case, UE_A10 performs the core as an access domain and / or domain selection process based on the reception of the 40th identification information contained in the SERVICE REJECT message from the core network_B190 in the emergency call reconnection. Access network A connected to network A may be selected.

Further, the terminal and the core network may execute the 26th procedure example shown below, which is different from the 21st to 25th procedure examples.

UE_A10 may retain the eleventh identification information and / or the twelfth identification information after executing the registration procedure in the initial procedure.

After the decision to execute the emergency call connection (S1040), UE_A10 then makes a service request (SERVICE) containing the 30th identification information based on the 11th identification information and / or the 12th identification information already held. The emergency call connection procedure using REQUEST) is executed, but the procedure may be rejected by the core network_B190. The refusal message may include the 40th identification information.

Here, the 40th identification information may include information indicating the core network_B190 and / or the access network A'.

In this case, UE_A10 performs the core as an access domain and / or domain selection process based on the reception of the 40th identification information contained in the SERVICE REJECT message from the core network_B190 in the emergency call reconnection. You may select access network A'connected to network_B190.

[4.5. Fifth Embodiment]
A fifth embodiment of the present invention will be described. Hereinafter, the fifth embodiment is also referred to as the present embodiment.

In the fourth embodiment, the processing when the service request (SERVICE REQUEST) related to the emergency call connection processing is received (SERVICE REJECT) has been described.

Specifically, UE_A10 selects the appropriate emergency call connection access domain based on the 11th identification information and / or the 12th identification information and / or the reception of the SERVICE REJECT message that it holds. Execute access domain and / or domain selection process for.

Further, in the present embodiment, UE_A10 performs the same processing even if the second procedure (S1070) relating to the emergency call connection is rejected.

Specifically, if the PDU session executed by UE_A10 is rejected by the network to establish a PDU session for emergency call services, UE_A10 will retain the eleventh identifying information and / or the twelfth. Performs an access domain and / or domain selection process for appropriate emergency call connection access domain selection based on the identity information and / or PDU session rejection (PDU SESSION REJECT) message reception.

[4.6. Sixth Embodiment]
A sixth embodiment of the present invention will be described with reference to FIGS. 10 and 11. Hereinafter, the sixth embodiment is also referred to as the present embodiment.

This embodiment mainly includes the registration procedure for the core network shown in FIG. 10 (S1020; hereinafter also simply referred to as the registration procedure) and (D) in the procedure shown in FIG. 10 based on the completion of the registration procedure. Related to the behavior of the procedure. Further, in the present embodiment, in the registration procedure to the core network (S1020), when the registration acceptance message (S1108) received by UE_A from the core network_B contains the 11th and / or 12th identification information. Regarding.

First, UE_A is operating in dual registration mode and is in the state of being in the access network_B connected to the core network_B.

In this case, it is decided to execute the emergency call connection (S1040) after the registration procedure to the core network (S1020) is completed according to the contents of the 11th and / or 12th identification information included in the registration acceptance message received by UE_A. The UE_A and / or each device may perform the emergency call connection process described below.

More specifically, UE_A and / or each device may perform the 61st procedure example described below.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via the access network A'connecting to B190 may be the procedure indicating support.

Further, the emergency call service via the core network A90 may be the case of support.

UE_A10 is based on the presence / absence of the support of the emergency call service via the core network A90 received in the attachment procedure to the core network_A90 and / and the tracking area update procedure shown in FIG. You may decide to support the emergency call service via.

At this time, UE_A may select access network A'and make an emergency call connection via access network A'connecting to core network B190, or select access network A and go through core network A90. You may make an emergency call connection.

Furthermore, if the twelfth identification information indicating the emergency call connection method included in the registration acceptance message received by UE_A indicates support, in the emergency call connection processing execution, UE_A10 is the thirtieth emergency call connection method. Select the SERVICE REQUEST (S1050) containing the identification information and start the process to start the redirection and / or handover process to the access network A'connected to the core network A90 or core network B_190 by the network. (S1050) may be used.

In addition, if the twelfth identity in the registration acceptance message received by UE_A indicates the emergency call connection method indicates support for fallback of the emergency call service via access network A', select access network A'. Then, the process for invoking the redirection and / or handover process to the core network A90 by the network may be started (S1050).

Note that UE_A and / or each device may execute the 62nd procedure example described below, which is different from the 61st procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via the access network A'connecting to B190 may be the procedure indicating support.

In addition, the emergency call service via the core network A90 may be unsupported.

UE_A10 is based on the presence / absence of the support of the emergency call service via the core network A90 received in the attachment procedure to the core network_A90 and / and the tracking area update procedure shown in FIG. You may decide to support the emergency call service via.

At this time, UE_A may select access network A'and execute an emergency call connection via access network A'connecting to core network B190.

Furthermore, if the twelfth identification information indicating the emergency call connection method included in the registration acceptance message received by UE_A indicates support, in the emergency call connection processing execution, UE_A10 is the thirtieth emergency call connection method. Select the service request (SERVICE REQUEST) (S1050) containing the identification information, and start the process for invoking the redirection and / or handover process to the access network A'connected to the core network B_190 by the network (S1050). You may.

Note that the UE_A and / or each device may execute the 63rd procedure example described below, which is different from the 61st procedure example to the 62nd procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support.

In addition, the emergency call service via the core network A90 may be unsupported.

In addition, UE_A10 is an emergency call via core network A90 based on the presence or absence based on the information regarding the support of the emergency call service via core network A90 received in the attachment procedure to core network_A90 and / and the tracking area update procedure. You may decide to support the service. At this time, UE_A selects the CS domain for the emergency call connection. In addition, UE_A10 is an emergency call, even if the twelfth identity in the registration acceptance message received by UE_A indicates the emergency call connection method to support fallback of the emergency call service over access network A'. Select the CS domain for the connection.

Note that the UE_A and / or each device may execute the 64th procedure example described below, which is different from the 61st procedure example to the 63rd procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support.

Further, the emergency call service via the core network A90 may be the case of support.

In addition, UE_A10 is an emergency call via core network A90 based on the presence or absence based on the information regarding the support of the emergency call service via core network A90 received in the attachment procedure to core network_A90 and / and the tracking area update procedure. You may decide to support the service.

At this time, UE_A may select access network A and execute an emergency call connection via core network A90.

Furthermore, if the twelfth identification information indicating the emergency call connection method included in the registration acceptance message received by UE_A indicates support, in the emergency call connection processing execution, UE_A10 is the thirtieth emergency call connection method. The service request (SERVICE REQUEST) (S1050) including the identification information may be selected and the process for invoking the redirection and / or handover process to the core network A90 by the network may be started (S1050).

In addition, if the twelfth identity in the registration acceptance message received by UE_A indicates the emergency call connection method indicates support for fallback of the emergency call service via access network A', select access network A'. Then, the process for invoking the redirection and / or handover process to the core network A90 by the network may be started (S1050).

Note that the UE_A and / or each device may execute the 65th procedure example described below, which is different from the 61st procedure example to the 64th procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The procedure may be such that the emergency call service via access network B connecting to B190 or via access network A'and access network B connecting to core network B190 indicates support.

Furthermore, if the emergency call service via the core network A90 is not supported, whether or not it has a function to execute a dedicated service request (SERVICE REQUEST) for invoking the handover and / or redirection procedure by the UE_A network. Kaya Executes an emergency call connection via access network B that connects to core network B190 without depending on the twelfth identification information that indicates the emergency call connection method included in the registration acceptance message received by UE_A.

In addition, if emergency call service via core network A90 is supported, does it have the ability to execute a dedicated SERVICE REQUEST to invoke the UE_A network handover and / or redirection procedure? You may make an emergency call connection via access network B that connects to core network B190 without relying on the twelfth identification information that indicates the emergency call connection method included in the registration acceptance message received by UE_A or UE_A. Access network A may be selected to make an emergency call connection via access network A and core network A90.

In the present embodiment, when the network handover and / or redirection procedure is not executed, UE_A executes a dedicated service request (SERVICE REQUEST) for invoking the network handover and / or redirection procedure. It may be the case that does not have.

So far, UE_A10 goes through either core network_A90 or core network B_190 based on the support status for the emergency call service of core network_A90 or core network B_190 included in the registration acceptance message from the core network. It was determined whether to execute the emergency call connection, but it is not limited to this.

Specifically, in addition to the above-mentioned emergency call service support status of the network, the determination may be made based on preset information.

At this time, if the terminal setting is set to give priority to the emergency call connection via the core network_A90, the emergency call connection via the core network_A90 may be executed. If the emergency call connection via the core network_B190 is set to be prioritized, the emergency call connection via the core network_B190 may be executed.

The setting information may be included in the registration acceptance message from the core network and / or the PDU session establishment acceptance message, or in the MO (Management Object) received from the application server included in the core network_B190 or DN_A. It may be included.

[4.7. Seventh Embodiment]
A seventh embodiment of the present invention will be described with reference to FIGS. 10 and 11. Hereinafter, the seventh embodiment is also referred to as the present embodiment.

This embodiment mainly includes the registration procedure for the core network shown in FIG. 10 (S1020; hereinafter also simply referred to as the registration procedure) and (D) in the procedure shown in FIG. 10 based on the completion of the registration procedure. Related to the behavior of the procedure. Further, in the present embodiment, in the registration procedure to the core network (S1020), when the registration acceptance message (S1108) received by UE_A from the core network_B contains the 11th and / or 12th identification information. Regarding.

First, UE_A is operating in dual registration mode and is in the state of being in the access network_A'connecting to the core network_B.

In this case, it is decided to execute the emergency call connection (S1040) after the registration procedure to the core network (S1020) is completed according to the contents of the 11th and / or 12th identification information included in the registration acceptance message received by UE_A. The UE_A and / or each device may perform the emergency call connection process described below.

More specifically, the UE_A and / or each device may execute the 66th procedure example described below, which is different from the 61st procedure example to the 64th procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The procedure may be such that the emergency call service via access network B connecting to B190 or via access network A'and access network B connecting to core network B190 indicates support.

Further, the emergency call service via the core network A90 may be the case of support.

UE_A10 is based on the presence / absence of the support of the emergency call service via the core network A90 received in the attachment procedure to the core network_A90 and / and the tracking area update procedure shown in FIG. You may decide to support the emergency call service via.

At this time, UE_A may execute an emergency call connection via the access network A'connecting to the core network B190, or select access network A and execute an emergency call connection via the core network A90. May be good.

Note that the UE_A and / or each device may execute the 67th procedure example described below, which is different from the 61st procedure example to the 66th procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via the access network A'connecting to B190 may be the procedure indicating support.

In addition, the emergency call service via the core network A90 may be unsupported. At this time, UE_A may execute an emergency call connection via the access network A'connecting to the core network B190.

Note that the UE_A and / or each device may execute the 68th procedure example described below, which is different from the 61st procedure example to the 67th procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support.

In addition, the emergency call service via the core network A90 may be unsupported.

UE_A10 is based on the presence / absence of the support of the emergency call service via the core network A90 received in the attachment procedure to the core network_A90 and / and the tracking area update procedure shown in FIG. You may decide to support the emergency call service via. At this time, UE_A selects the CS domain for the emergency call connection. In addition, UE_A10 is urgent, even if the twelfth identity in the registration acceptance message received by UE_A indicates the emergency call connection method, which indicates support for fallback of emergency call services, including via access network A'. Select the CS domain for the call connection.

Note that the UE_A and / or each device may execute the 69th procedure example described below, which is different from the 61st procedure example to the 67th procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via B190 may be a procedure indicating non-support.

In addition, the emergency call service via the core network A90 may be unsupported.

UE_A10 is based on the presence / absence of the support of the emergency call service via the core network A90 received in the attachment procedure to the core network_A90 and / and the tracking area update procedure shown in FIG. You may decide to support the emergency call service via.

At this time, UE_A may select access network A and execute an emergency call connection via core network A90.

Furthermore, if the twelfth identification information indicating the emergency call connection method included in the registration acceptance message received by UE_A indicates support, in the emergency call connection processing execution, UE_A10 is the thirtieth emergency call connection method. The service request (SERVICE REQUEST) (S1050) including the identification information may be selected and the process for invoking the redirection and / or handover process to the core network A90 by the network may be started (S1050).

In addition, if the twelfth identification information in the registration acceptance message received by UE_A indicates the emergency call connection method indicates support for fallback of the emergency call service via access network B, select access network B and select access network B. The process for invoking the redirection and / or handover process to the core network A90 by the network may be started (S1050).

Note that the UE_A and / or each device may execute the 70th procedure example described below, which is different from the 61st procedure example to the 69th procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via access network B connecting to B190 may be the procedure indicating support.

Further, the emergency call service via the core network A90 may be the case of support.

UE_A10 is based on the presence / absence of the support of the emergency call service via the core network A90 received in the attachment procedure to the core network_A90 and / and the tracking area update procedure shown in FIG. You may decide to support the emergency call service via.

At this time, UE_A may select access network B and execute an emergency call connection via access network B connected to core network B190, or select access network A and make an emergency via core network A90. A call connection may be made.

Furthermore, if the twelfth identification information indicating the emergency call connection method included in the registration acceptance message received by UE_A indicates support, in the emergency call connection processing execution, UE_A10 is the thirtieth emergency call connection method. The service request (SERVICE REQUEST) (S1050) including the identification information may be selected and the process for invoking the redirection and / or handover process to the core network A90 by the network may be started (S1050).

In addition, if the twelfth identification information in the registration acceptance message received by UE_A indicates the emergency call connection method indicates support for fallback of the emergency call service via access network B, select access network B and select access network B. The process for invoking the redirection and / or handover process to the core network A90 by the network may be started (S1050).

Note that the UE_A and / or each device may execute the 71st procedure example described below, which is different from the 61st procedure example to the 70th procedure example.

In the registration procedure to the core network (S1020; hereinafter simply referred to as the registration procedure) shown in FIG. 10, the eleventh identification information included in the registration acceptance message (S1108) received by UE_A from the core network_B is the core network. The emergency call service via access network B connecting to B190 may be the procedure indicating support.

In addition, the emergency call service via the core network A90 may be unsupported.

UE_A10 is based on the presence / absence of the support of the emergency call service via the core network A90 received in the attachment procedure to the core network_A90 and / and the tracking area update procedure shown in FIG. You may decide to support the emergency call service via.

At this time, UE_A may select access network B and execute an emergency call connection via access network B connected to core network B190.

Furthermore, if the twelfth identification information indicating the emergency call connection method included in the registration acceptance message received by UE_A indicates support, in the emergency call connection processing execution, UE_A10 is the thirtieth emergency call connection method. Select the service request (SERVICE REQUEST) (S1050) containing the identification information, and start the process for invoking the redirection and / or handover process to the access network B connected to the core network B_190 by the network (S1050). May be good.

[4.8. Eighth Embodiment]
An eighth embodiment of the present invention will be described with reference to FIGS. 10 and 11. Hereinafter, the eighth embodiment is also referred to as the present embodiment.

Until now, regarding the method of selecting the core network to be routed through the emergency call connection, UE_A10 has been used for the attach acceptance message from the core network_A90 and / or the tracking area update acceptance and / or the registration acceptance message from the core network_B_190. Although the method of selecting based on the support information for each emergency call service included has been described, the selection method is not limited to this.

For example, if an emergency call connection service is available via both core network_A90 and core network_B_190, it will be based on pre-configured UE information in addition to the network emergency call service support information described above. , You may select the core network to go through by emergency call connection.

At this time, if the UE setting is set to give priority to the emergency call connection via the core network_A90, the emergency call connection via the core network_A90 may be executed. If the emergency call connection via the core network_B190 is set to be prioritized, the emergency call connection via the core network_B190 may be executed.

The setting information may be included in the registration acceptance message from the core network and / or the PDU session establishment acceptance message, or in the MO (Management Object) received from the application server included in the core network_B190 or DN_A. It may be included.

Also, if emergency call connection service is possible via both core network_A90 and core network_B_190, in addition to the emergency call service support information for the network mentioned above, based on the access network in which UE_A10 resides, You may select the core network to go through in the emergency call connection.

For example, if UE_A10 is located in access network B, emergency call connection processing via access network B may be executed, and if UE_A10 is located in access network A', access network A may be executed. You may execute the emergency call connection process via', or if you are in the access network A, you may execute the emergency call connection process via the access network A.

[5. Others]
So far, UE_A10 has described an embodiment in which UE_A10 first attempts to register for an emergency call and connect to an emergency call service via the access network_B120 connected to the core network_B. However, the present invention is not limited to this, and the following procedures may be executed after attempting to connect / register to the system composed of the access network_A'and the core network_B.

For example, UE_A10 first fails to register for an emergency call through access network_A'connected to core network_B and connects to the emergency call service, and then access connected to core network_B. An emergency call reconnection may be performed via either network_B, access network_A connected to core network_A, or CS network.

Since the behavior in this case is the same as the procedure already described, detailed description will be omitted.

[6. Modification example]
The program that operates in the apparatus according to the present invention may be a program that controls the Central Processing Unit (CPU) or the like to operate the computer so as to realize the functions of the embodiments according to the present invention. The program or information handled by the program is temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, Hard Disk Drive (HDD), or other storage device system.

The program for realizing the function of the embodiment according to the present invention may be recorded on a computer-readable recording medium. It may be realized by having a computer system read a program recorded on this recording medium and executing the program. The "computer system" as used herein is a computer system built into a device, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another recording medium that can be read by a computer. May be good.

Also, each functional block, or feature, of the device used in the embodiments described above may be implemented or implemented in an electrical circuit, such as an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein are general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others. Programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when an integrated circuit technology that replaces the current integrated circuit appears due to advances in semiconductor technology, one or more aspects of the present invention can also use a new integrated circuit according to the technology.

The invention of the present application is not limited to the above-described embodiment. In the embodiment, an example of the device has been described, but the present invention is not limited to this, and the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device or a kitchen device. , Cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as living equipment.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within a range not deviating from the gist of the present invention are also included. Further, the present invention can be variously modified within the scope of the claims, and the technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments. Is done. In addition, the elements described in each of the above embodiments include a configuration in which elements having the same effect are replaced with each other.

1 Mobile communication system
5 DN_A
6 PDN_A
7 IMS_A
10 UE_A
30 PGW_A
35 SGW_A
45 eNB_A
40 MME_A
50 HSS_A
80 Access Network_A
81 Access Network_A'
90 Core Network_A
120 Access Network_B
122 gNB_A
145 eNB_B
190 Core network_B
230 SMF_A
235 UPF_A
240 AMF_A
245 UDM_A
290 CS Network_A
300 P-CSCF_A
310 P-CSCF_B
320 S-CSCF_A
330 E-CSCF_A

Claims (2)

A UE (User Equipment) having a control unit and a transmission / reception unit.
When the control unit fails in the connection attempt of the first emergency call using the non-CS (Circuit Switched) domain, the control unit can execute the connection attempt of the second emergency call using the non-CS domain.
The transmission / reception unit receives a PDU (Packet Data Unit) session establishment refusal message as the failure of the connection attempt of the first emergency call.
The control unit uses the first access network for the connection attempt of the first emergency call.
The control unit uses the second access network for the connection attempt of the second emergency call.
UE characterized by that. A communication control method executed by a UE (User Equipment), wherein the communication control method is
If the first emergency call connection attempt using the non-CS (Circuit Switched) domain fails, the second emergency call connection attempt using the non-CS domain can be executed.
Receiving a PDU (Packet Data Unit) session establishment refusal message as the failure of the first emergency call connection attempt.
Using the first access network for the first emergency call connection attempt,
The second emergency call connection attempt includes using a second access network.
A communication control method characterized by that.

Images