Patent Description:
Wireless communication systems have been widely deployed to provide various types of communication services such as voice or data. In general, a wireless communication system is a multiple access system that supports communication of multiple users by sharing available system resources (a bandwidth, transmission power, etc.) among them. For example, multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and a multi-carrier frequency division multiple access (MC-FDMA) system. The following exemplarily documents are concerned with voice support signals:.

The object of the present disclosure is to provide a method by which an NG-RAN checks UE capability and network configurations regarding the continuity of IMS voice.

Technical tasks obtainable from the present disclosure are non-limited by the above-mentioned technical task. And, other unmentioned technical tasks can be clearly understood from the following description by those having ordinary skill in the technical field to which the present disclosure pertains.

Features of certain embodiments are defined in the dependent claims.

According to the present disclosure, not only a problem that an NG-RAN does not check the IMS voice related capability of a UE and a problem that whether voice support matches is incorrectly informed but also many other problems caused thereby may be solved.

The accompanying drawings, which are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this application, illustrate embodiments of the present disclosure and together with the description serve to explain the principle of the disclosure.

The embodiments below are combinations of components and features of the present invention in a prescribed form. Each component or feature may be considered as selective unless explicitly mentioned as otherwise. Each component or feature may be executed in a form that is not combined with other components and features. Further, some components and/or features may be combined to configure an embodiment of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some components or features of an embodiment may be included in another embodiment or may be substituted with a corresponding component or feature of the present invention.

Specific terms used in the description below are provided to help an understanding of the present invention, and the use of such specific terms may be changed to another form within the scope of the technical concept of the present invention.

In some cases, in order to avoid obscurity of the concept of the present invention, a known structure and apparatus may be omitted, or a block diagram centering on core functions of each structure or apparatus may be used. Moreover, the same reference numerals are used for the same components throughout the present specification.

The embodiments of the present invention may be supported by standard documents disclosed with respect to at least one of IEEE (Institute of Electrical and Electronics Engineers) <NUM> group system, 3GPP system, 3GPP LTE & LTE-A system and 3GPP2 system. Namely, the steps or portions having not been described in order to clarify the technical concept of the present invention in the embodiments of the present invention may be supported by the above documents. Furthermore, all terms disclosed in the present document may be described according to the above standard documents.

The technology below may be used for various wireless communication systems. For clarity, the description below centers on 3GPP LTE and 3GPP LTE-A, by which the technical idea of the present invention is non-limited.

Terms used in the present document are defined as follows.

<FIG> is a schematic diagram showing the structure of an evolved packet system (EPS) including an evolved packet core (EPC).

The EPC is a core element of system architecture evolution (SAE) for improving performance of 3GPP technology. SAE corresponds to a research project for determining a network structure supporting mobility between various types of networks. For example, SAE aims to provide an optimized packet-based system for supporting various radio access technologies and providing an enhanced data transmission capability.

Specifically, the EPC is a core network of an IP mobile communication system for 3GPP LTE and can support real-time and non-real-time packet-based services. In conventional mobile communication systems (i.e. second-generation or third-generation mobile communication systems), functions of a core network are implemented through a circuit-switched (CS) sub-domain for voice and a packet-switched (PS) sub-domain for data. However, in a 3GPP LTE system which is evolved from the third generation communication system, CS and PS sub-domains are unified into one IP domain. That is, In 3GPP LTE, connection of terminals having IP capability can be established through an IP-based business station (e.g., an eNodeB (evolved Node B)), EPC, and an application domain (e.g., IMS). That is, the EPC is an essential structure for end-to-end IP services.

The EPC may include various components. <FIG> shows some of the components, namely, a serving gateway (SGW), a packet data network gateway (PDN GW), a mobility management entity (MME), a serving GPRS (general packet radio service) supporting node (SGSN) and an enhanced packet data gateway (ePDG).

SGW (or S-GW) operates as a boundary point between a radio access network (RAN) and a core network and maintains a data path between an eNodeB and the PDN GW. When a terminal moves over an area served by an eNodeB, the SGW functions as a local mobility anchor point. That is, packets. That is, packets may be routed through the SGW for mobility in an evolved UMTS terrestrial radio access network (E-UTRAN) defined after 3GPP release-<NUM>. In addition, the SGW may serve as an anchor point for mobility of another 3GPP network (a RAN defined before 3GPP release-<NUM>, e.g., UTRAN or GERAN (global system for mobile communication (GSM)/enhanced data rates for global evolution (EDGE) radio access network).

The PDN GW (or P-GW) corresponds to a termination point of a data interface for a packet data network. The PDN GW may support policy enforcement features, packet filtering and charging support. In addition, the PDN GW may serve as an anchor point for mobility management with a 3GPP network and a non-<NUM> GPP network (e.g., an unreliable network such as an interworking wireless local area network (I-WLAN) and a reliable network such as a code division multiple access (CDMA) or WiMax network).

Although the SGW and the PDN GW are configured as separate gateways in the example of the network structure of <FIG>, the two gateways may be implemented according to a single gateway configuration option.

The MME performs signaling and control functions for supporting access of a UE for network connection, network resource allocation, tracking, paging, roaming and handover. The MME controls control plane functions associated with subscriber and session management. The MME manages numerous eNodeBs and signaling for selection of a conventional gateway for handover to other <NUM>/<NUM> networks. In addition, the MME performs security procedures, terminal-to-network session handling, idle terminal location management, etc..

The SGSN handles all packet data such as mobility management and authentication of a user for other 3GPP networks (e.g., a GPRS network).

The ePDG serves as a security node for a non-3GPP network (e.g., an I-WLAN, a Wi-Fi hotspot, etc.).

As described above with reference to <FIG>, a terminal having IP capabilities may access an IP service network (e.g., an IMS) provided by an operator via various elements in the EPC not only based on 3GPP access but also based on non-3GPP access.

Additionally, <FIG> shows various reference points (e.g. S1-U, S1-MME, etc.). In 3GPP, a conceptual link connecting two functions of different functional entities of an E-UTRAN and an EPC is defined as a reference point. Table <NUM> is a list of the reference points shown in <FIG>. Various reference points may be present in addition to the reference points in Table <NUM> according to network structures.

Among the reference points shown in <FIG>, S2a and S2b correspond to non-3GPP interfaces. S2a is a reference point which provides reliable non-3GPP access and related control and mobility support between PDN GWs to a user plane. S2b is a reference point which provides related control and mobility support between the ePDG and the PDN GW to the user plane.

<FIG> is a diagram exemplarily illustrating architectures of a typical E-UTRAN and EPC.

As shown in the figure, while radio resource control (RRC) connection is activated, an eNodeB may perform routing to a gateway, scheduling transmission of a paging message, scheduling and transmission of a broadcast channel (BCH), dynamic allocation of resources to a UE on uplink and downlink, configuration and provision of eNodeB measurement, radio bearer control, radio admission control, and connection mobility control. In the EPC, paging generation, LTE_IDLE state management, ciphering of the user plane, SAE bearer control, and ciphering and integrity protection of NAS signaling.

<FIG> is a diagram exemplarily illustrating the structure of a radio interface protocol in a control plane between a UE and a base station, and <FIG> is a diagram exemplarily illustrating the structure of a radio interface protocol in a user plane between the UE and the base station.

The radio interface protocol is based on the 3GPP wireless access network standard. The radio interface protocol horizontally includes a physical layer, a data link layer, and a networking layer. The radio interface protocol is divided into a user plane for transmission of data information and a control plane for delivering control signaling which are arranged vertically.

The protocol layers may be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the three sublayers of the open system interconnection (OSI) model that is well known in the communication system.

Hereinafter, description will be given of a radio protocol in the control plane shown in <FIG> and a radio protocol in the user plane shown in <FIG>.

The physical layer, which is the first layer, provides an information transfer service using a physical channel. The physical channel layer is connected to a medium access control (MAC) layer, which is a higher layer of the physical layer, through a transport channel. Data is transferred between the physical layer and the MAC layer through the transport channel. Transfer of data between different physical layers, i.e., a physical layer of a transmitter and a physical layer of a receiver is performed through the physical channel.

The physical channel consists of a plurality of subframes in the time domain and a plurality of subcarriers in the frequency domain. One subframe consists of a plurality of symbols in the time domain and a plurality of subcarriers. One subframe consists of a plurality of resource blocks. One resource block consists of a plurality of symbols and a plurality of subcarriers. A Transmission Time Interval (TTI), a unit time for data transmission, is <NUM>, which corresponds to one subframe.

According to 3GPP LTE, the physical channels present in the physical layers of the transmitter and the receiver may be divided into data channels corresponding to Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) and control channels corresponding to Physical Downlink Control Channel (PDCCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid-ARQ Indicator Channel (PHICH) and Physical Uplink Control Channel (PUCCH).

The second layer includes various layers.

First, the MAC layer in the second layer serves to map various logical channels to various transport channels and also serves to map various logical channels to one transport channel. The MAC layer is connected with an RLC layer, which is a higher layer, through a logical channel. The logical channel is broadly divided into a control channel for transmission of information of the control plane and a traffic channel for transmission of information of the user plane according to the types of transmitted information.

The radio link control (RLC) layer in the second layer serves to segment and concatenate data received from a higher layer to adjust the size of data such that the size is suitable for a lower layer to transmit the data in a radio interval.

The Packet Data Convergence Protocol (PDCP) layer in the second layer performs a header compression function of reducing the size of an IP packet header which has a relatively large size and contains unnecessary control information, in order to efficiently transmit an IP packet such as an IPv4 or IPv6 packet in a radio interval having a narrow bandwidth. In addition, in LTE, the PDCP layer also performs a security function, which consists of ciphering for preventing a third party from monitoring data and integrity protection for preventing data manipulation by a third party.

The Radio Resource Control (RRC) layer, which is located at the uppermost part of the third layer, is defined only in the control plane, and serves to configure radio bearers (RBs) and control a logical channel, a transport channel, and a physical channel in relation to reconfiguration and release operations. The RB represents a service provided by the second layer to ensure data transfer between a UE and the E-UTRAN.

If an RRC connection is established between the RRC layer of the UE and the RRC layer of a wireless network, the UE is in the RRC Connected mode. Otherwise, the UE is in the RRC Idle mode.

Hereinafter, description will be given of the RRC state of the UE and an RRC connection method. The RRC state refers to a state in which the RRC of the UE is or is not logically connected with the RRC of the E-UTRAN. The RRC state of the UE having logical connection with the RRC of the E-UTRAN is referred to as an RRC_CONNECTED state. The RRC state of the UE which does not have logical connection with the RRC of the E-UTRAN is referred to as an RRC_IDLE state. A UE in the RRC_CONNECTED state has RRC connection, and thus the E-UTRAN may recognize presence of the UE in a cell unit. Accordingly, the UE may be efficiently controlled. On the other hand, the E-UTRAN cannot recognize presence of a UE which is in the RRC_IDLE state. The UE in the RRC_IDLE state is managed by a core network in a tracking area (TA) which is an area unit larger than the cell. That is, for the UE in the RRC_IDLE state, only presence or absence of the UE is recognized in an area unit larger than the cell. In order for the UE in the RRC_IDLE state to be provided with a usual mobile communication service such as a voice service and a data service, the UE should transition to the RRC_CONNECTED state. A TA is distinguished from another TA by a tracking area identity (TAI) thereof. A UE may configure the TAI through a tracking area code (TAC), which is information broadcast from a cell.

When the user initially turns on the UE, the UE searches for a proper cell first. Then, the UE establishes RRC connection in the cell and registers information thereabout in the core network. Thereafter, the UE stays in the RRC_IDLE state. When necessary, the UE staying in the RRC_IDLE state selects a cell (again) and checks system information or paging information. This operation is called camping on a cell. Only when the UE staying in the RRC_IDLE state needs to establish RRC connection, does the UE establish RRC connection with the RRC layer of the E-UTRAN through the RRC connection procedure and transition to the RRC_CONNECTED state. The UE staying in the RRC_IDLE state needs to establish RRC connection in many cases. For example, the cases may include an attempt of a user to make a phone call, an attempt to transmit data, or transmission of a response message after reception of a paging message from the E-UTRAN.

The non-access stratum (NAS) layer positioned over the RRC layer performs functions such as session management and mobility management.

Hereinafter, the NAS layer shown in <FIG> will be described in detail.

The eSM (evolved Session Management) belonging to the NAS layer performs functions such as default bearer management and dedicated bearer management to control a UE to use a PS service from a network. The UE is assigned a default bearer resource by a specific packet data network (PDN) when the UE initially accesses the PDN. In this case, the network allocates an available IP to the UE to allow the UE to use a data service. The network also allocates QoS of a default bearer to the UE. LTE supports two kinds of bearers. One bearer is a bearer having characteristics of guaranteed bit rate (GBR) QoS for guaranteeing a specific bandwidth for transmission and reception of data, and the other bearer is a non-GBR bearer which has characteristics of best effort QoS without guaranteeing a bandwidth. The default bearer is assigned to a non-GBR bearer. The dedicated bearer may be assigned a bearer having QoS characteristics of GBR or non-GBR.

A bearer allocated to the UE by the network is referred to as an evolved packet service (EPS) bearer. When the EPS bearer is allocated to the UE, the network assigns one ID. This ID is called an EPS bearer ID. One EPS bearer has QoS characteristics of a maximum bit rate (MBR) and/or a guaranteed bit rate (GBR).

<FIG> is a flowchart illustrating a random access procedure in 3GPP LTE.

The random access procedure is used for a UE to obtain UL synchronization with an eNB or to be assigned a UL radio resource.

The UE receives a root index and a physical random access channel (PRACH) configuration index from an eNodeB. Each cell has <NUM> candidate random access preambles defined by a Zadoff-Chu (ZC) sequence. The root index is a logical index used for the UE to generate <NUM> candidate random access preambles.

Transmission of a random access preamble is limited to a specific time and frequency resources for each cell. The PRACH configuration index indicates a specific subframe and preamble format in which transmission of the random access preamble is possible.

The UE transmits a randomly selected random access preamble to the eNodeB. The UE selects a random access preamble from among <NUM> candidate random access preambles and the UE selects a subframe corresponding to the PRACH configuration index. The UE transmits the selected random access preamble in the selected subframe.

Upon receiving the random access preamble, the eNodeB sends a random access response (RAR) to the UE. The RAR is detected in two steps. First, the UE detects a PDCCH masked with a random access (RA)-RNTI. The UE receives an RAR in a MAC (medium access control) PDU (protocol data unit) on a PDSCH indicated by the detected PDCCH.

<FIG> illustrates a connection procedure in a radio resource control (RRC) layer.

As shown in <FIG>, the RRC state is set according to whether or not RRC connection is established. An RRC state indicates whether or not an entity of the RRC layer of a UE has logical connection with an entity of the RRC layer of an eNodeB. An RRC state in which the entity of the RRC layer of the UE is logically connected with the entity of the RRC layer of the eNodeB is called an RRC connected state. An RRC state in which the entity of the RRC layer of the UE is not logically connected with the entity of the RRC layer of the eNodeB is called an RRC idle state.

A UE in the Connected state has RRC connection, and thus the E-UTRAN may recognize presence of the UE in a cell unit. Accordingly, the UE may be efficiently controlled. On the other hand, the E-UTRAN cannot recognize presence of a UE which is in the idle state. The UE in the idle state is managed by the core network in a tracking area unit which is an area unit larger than the cell. The tracking area is a unit of a set of cells. That is, for the UE which is in the idle state, only presence or absence of the UE is recognized in a larger area unit. In order for the UE in the idle state to be provided with a usual mobile communication service such as a voice service and a data service, the UE should transition to the connected state.

When the user initially turns on the UE, the UE searches for a proper cell first, and then stays in the idle state. Only when the UE staying in the idle state needs to establish RRC connection, the UE establishes RRC connection with the RRC layer of the eNodeB through the RRC connection procedure and then performs transition to the RRC connected state.

The UE staying in the idle state needs to establish RRC connection in many cases. For example, the cases may include an attempt of a user to make a phone call, an attempt to transmit data, or transmission of a response message after reception of a paging message from the E-UTRAN.

In order for the UE in the idle state to establish RRC connection with the eNodeB, the RRC connection procedure needs to be performed as described above. The RRC connection procedure is broadly divided into transmission of an RRC connection request message from the UE to the eNodeB, transmission of an RRC connection setup message from the eNodeB to the UE, and transmission of an RRC connection setup complete message from the UE to eNodeB, which are described in detail below with reference to <FIG>.

In a next generation system (i.e., <NUM> core network (CN)), the functionality of an MME in the legacy EPC may be divided into a Core Access and Mobility Management Function (AMF) and a Session Management Function (SMF). The AMF is in charge of NAS interaction with the UE and mobility management (MM), and the SMF is in charge of session management (SM). In addition, the SMF manages a user plane function (UPF), which corresponds to a gateway for routing user traffic, i.e., managing a user plane. This may be interpreted to mean that the SMF manages the control plane of an S-GW and a P-GW in the legacy EPC and the UPF manages the user plane thereof. For user traffic routing, at least one UPF may exist between a RAN and a data network (DN). In other words, the legacy EPC may be implemented in the <NUM> system as illustrated in <FIG>. The <NUM> system defines a protocol data unit (PDU) session as a concept related to a PDN connection in the legacy EPS. The PDU session refers to association between the UE and the DN that provides PDU connectivity services and may be divided into a PDU session of IP type, a PDU session of Ethernet type, and a PDU session of unstructured type. Unified data management (UDM) serves as an HSS of the EPC, and a policy control function (PCF) serves as a PCRF of the EPC. To satisfy the requirements of the <NUM> system, these functions may be extended and provided. Details of the <NUM> system architecture, individual functions, and individual interfaces may be found in TS <NUM>.

<FIG> illustrates a general registration procedure in the <NUM> system. The general registration procedure may be initiated when a UE transmits a registration request to an (R)AN. Details of each step may be found in clause <NUM>. <NUM> of TS <NUM>. During Registration Accept transmission of step <NUM> in the registration procedure, an AMF may inform the UE whether IMS voice over PS (i.e., a voice service based on packet switching) is supported within a registration area through IMS voice over PS Session Supported Indication. Specifically, the AMF configures the IMS voice over PS Session Supported Indication as described in clause <NUM>. <NUM> of TS <NUM>. To configure the IMS voice over PS Session Supported Indication, the AMF may need to check the radio capabilities of the UE and RAN, which are related to the IMS voice over PS, by performing a UE/RAN Radio Information and Compatibility Request procedure described in clause <NUM>. <NUM> of TS <NUM>. If the AMF has not received a voice support match indicator from a next generation radio access network (NG-RAN), the AMF may configure the IMS voice over PS Session Supported Indication and then update the IMS voice over PS Session Supported Indication in a next step based on implementation.

The Registration Accept transmission of step <NUM> will be described in detail. To configure the IMS voice over PS Session Supported Indication, the AMF may check the compatibility between the UE and RAN radio capabilities related to the IMS voice by performing the UE/RAN Radio Information and Compatibility Request procedure (see clause <NUM>. <NUM> of TS <NUM>) or a UE Capability Match Request procedure towards the NG-RAN. For example, when the NG-RAN provides the IMS voice in the TDD mode, if the UE is capable of using the IMS voice only in the FDD mode, the NG-RAN may inform the AMF that the voice support thereof does not match with that for the UE (using a parameter such as the voice support match indicator).

When the AMF receives from the NG-RAN information indicating that the voice support thereof does not match with that for the UE, that is, the IMS voice related capability of the UE does not match with that of the NG-RAN, the AMF may inform the UE that the IMS voice is not supported using a Registration Accept message. How the UE operates when being informed that the IMS voice is not supported may be found in clause <NUM>. <NUM> (Domain selection for UE originating sessions / calls) of TS <NUM>. If the UE is informed that the IMS voice is supported, the UE may use the IMS voice after IMS registration.

As described above, the AMF provides information on whether the UE is capable of using the IMS voice in the registration area. However, when no IMS voice is supported in the registration area (for example, when radio features are not suitable for voice), the UE may be informed that the IMS voice is not available. However, according to clause <NUM>. <NUM> (IMS voice over PS Session Supported Indication) of TS <NUM>, when the network is incapable of successfully providing the IMS voice over PS session over the NR connected to a <NUM> core network (5GC), if one of the following operations is enabled:.

A serving PLMN AMF may inform the UE that the IMS voice over PS session is supported.

That is, when the UE is camping on the NR system (i.e., gNB), if the NR system (or gNB) does not support the IMS voice but is capable of handing over the UE to the E-UTRA connected to the 5GC (i.e., ng-eNB) or the EPS in order to provide the IMS voice, the NR system (or gNB) may inform the UE that the IMS voice is supported.

In this case, to configure the IMS Voice over PS session supported Indication, the AMF may check the compatibility between the UE and RAN radio capabilities related to the IMS voice by performing the UE/RAN Radio information and Compatibility Request procedure or UE Capability Match Request procedure towards the NG-RAN (gNBs and/or ng-eNBs). However, in the above operation, if the NG-RAN does not actually support the IMS voice, the following problems may occur. That is, the NG-RAN may not check the IMS voice related capability of the UE (as a result, the NG-RAN may provide the AMF no response regarding the voice support match) or inform the AMF that the voice support thereof does not match with that for the UE.

In addition, when the NG-RAN provides the AMF no response regarding the voice support match, the AMF may autonomously determine that the IMS voice is supported and inform the UE that the IMS voice is supported. When there is a voice call, if the UE is fallen back to the EPS or another radio access technology (RAT) in the 5GC, the voice call may not be supported since the UE and RAN capabilities are not compatible with each other in terms of the voice support, whereby user experience may be degraded. When the NG-RAN informs the AMF that the voice support thereof does not match with that for the UE, the AMF may inform the UE that the IMS voice is not supported. The voice-centric UE may move to a system capable of supporting the voice (e.g., EPS) (Details thereof may be found in clause <NUM>. <NUM> (Domain selection for UE originating sessions / calls) of TS <NUM>). As a result, in this case, even though the UE may be served with high quality of data services in a <NUM> system (5GS) in usual and use the EPS or a RAT capable of supporting voice services in the 5GC when there is a voice call, the UE may not be provided with the services in the 5GS. Hereinafter, a method of solving such a problem will be described.

With reference to <FIG>, an embodiment of the present disclosure will be described. Referring to <FIG>, an NG-RAN (i.e., an (R)AN of <FIG>) receives a request for UE capability related to IMS voice (UE Capability Match Request) from an AMF (S901). That is, the AMF may inform whether the AMF desires to receive a voice support match indicator. The request may include UE radio capability information, which is previously received from the NG-RAN, or the registration area of a UE. In addition, when transmitting the UE Capability Match Request to the NG-RAN, the AMF may include information on EPS fallback or information on RAT fallback. This may be interpreted to mean that the AMF provides an EPS fallback indication or a RAT fallback indication to the NG-RAN since it is configured in the core network that the IMS voice is provided by the EPS fallback or the RAT fallback.

The NG-RAN may check whether the UE capability is compatible with a network configuration.

The network configuration, of which the compatibility with the UE capability is checked by the NG-RAN, includes a network configuration of the NG-RAN and a network configuration of a network node capable of the IMS voice even though the NG-RAN does not support the IMS voice. That is, according to the present disclosure, it is checked whether the network configuration of the network node capable of the IMS voice is compatible with the UE capability in terms of the IMS voice even though the NG-RAN does not support the IMS voice, compared to a conventional compatibility check for checking whether the network configuration of the NG-RAN is compatible with the UE capability in terms of the IMS voice.

Even though the NG-RAN does not support the IMS voice, the IMS voice may be enabled as follows: when there is a voice call for the UE, the UE may be handed over or redirected to an EPS so that the UE is capable of using the IMS voice. This means that the NG-RAN is configured to support the EPS fallback for the IMS voice. In other words, when the NG-RAN is configured to support the EPS fallback for the IMS voice, it may mean that when there is a voice call for the UE, the NG-RAN hands over or redirects the UE to the EPS so that the UE is capable of using the IMS voice. The related operation may be found in clause <NUM>. <NUM> (EPS fallback for IMS voice) of TS <NUM>. In this case, the network node capable of the IMS voice is a network node available as an EPS fallback target. For example, an eNB may be used as the network node capable of the IMS voice.

Even though the NG-RAN does not support the IMS voice, the IMS voice may be enabled as follows: when there is a voice call for the UE, the UE may be handed over or redirected to an NG-RAN supporting the IMS voice so that the UE is capable of using the IMS voice. This means that the NG-RAN is configured to support the RAT fallback for the IMS voice. In other words, when the NG-RAN is configured to support the RAT fallback for the IMS voice, it may mean that when there is a voice call for the UE, the NG-RAN (e.g., gNB) hands over or redirects the UE to the NG-RAN supporting the IMS voice (e.g., ng-eNB) so that the UE is capable of using the IMS voice. The related operation may be found in clause <NUM>. <NUM> (Inter RAT Fallback in 5GC for IMS voice) of TS <NUM>. In this case, the network node capable of the IMS voice is a network node available as an RAT fallback target. For example, an ng-eNB may be used as the network node capable of the IMS voice.

In summary, when the NG-RAN is configured to support the EPS or RAT fallback for the IMS voice although it does not supports the IMS voice, the NG-RAN checks whether the UE radio capabilities related to voice services (i.e., IMS voice) are compatible with the configuration of the target network node (or whether the UE supports certain capabilities required for Voice continuity of voice calls using IMS PS), using information on the configuration of the network node available as the ESP or RAT fallback target (it may refer to an EPS/E-UTRAN/eNB or a 5GS/NG-RAN/ng-eNB/gNB). This may mean that the NG-RAN checks the compatibility with respect to the voice services for the UE in consideration of the EPS fallback or RAT fallback.

When determining the network node available as the EPS or RAT fallback target, the NG-RAN may use configured information (e.g., information configured according to an O&M method) or the registration area of the UE if it is provided by the AMF in step S901. The NG-RAN may be configured to support the EPS or RAT fallback for the IMS voice. Alternatively, the NG-RAN may check the compatibility with respect to the voice services for the UE based on the EPS fallback indication or RAT fallback indication provided by the AMF in step S901.

When the NG-RAN does not support the IMS voice, the network configuration of the network node capable of the IMS voice is obtained in one of the following ways: the network configuration may be obtained when the NG-RAN sets up an interface with the network node; and the network configuration may be obtained when the NG-RAN requests the network node. Specifically, I) the NG-RAN may obtain the network configuration when the NG-RAN sets up an interface with a candidate network node (normally, during a deployment) and exchanges network configuration information related to voice services, or II) the NG-RAN may obtain the network configuration by sending a request therefor to a candidate network node. There is an interface therebetween. In this case, the NG-RAN may request the network configuration related to the voice services and obtain information thereon only. In addition, the NG-RAN may obtain the network configuration information for another UE and store the obtained network configuration information. The NG-RAN may use the stored network configuration information.

To determine proper UE Radio Capability Match Response, the NG-RAN may be configured by its operator to check whether a specific capability is supported for voice continuity of voice calls using the IMS voice. In a common network, the NG-RAN may maintain a configuration separately for each PLMN. A check that should be performed may depend on the network configuration. For example, the following may be considered:.

To ensure the voice service continuity of voice calls initiated by the IMS, the NG-RAN provides the AMF the voice support match indicator indicating whether the UE capabilities are compatible with the network configuration. In this case, the NG-RAN may explicitly or implicitly inform that its network configuration is not related to the voice support match information, which is provided by the NG-RAN to the AMF. Additionally or alternatively, the NG-RAN may explicitly or implicitly inform that the voice support match information is related to the network configuration of an eNB (connected to the EPC) or the network configuration of an ng-eNB (connected to the 5GC). Additionally or alternatively, the NG-RAN may explicitly or implicitly inform that the voice support match information is related to EPS fallback or RAT fallback. The AMF may store the received voice support match indicator in 5GMM contexts and use it as an input for configuring the IMS voice over PS Session Supported Indication.

In steps S902 and S903, the NG-RAN performs a procedure for checking the UE capability towards the UE. This procedure may be performed before the aforementioned check procedure of the NG-RAN. However, the procedure may not be necessarily performed before the check procedure.

When the NG-RAN receives a UE Capability Match Request message in step S901, if the NG-RAN does not receive the UE radio capabilities from the UE or AMF in step <NUM>, the NG-RAN requests to update UE radio capability information in step S902. The UE provides UE radio capabilities sending the RRC UE Capability Information to the NG-RAN (S903).

In step S904, the NG-RAN transmits, to the AMF, a response including the result of checking whether the UE capability is compatible with the network configuration.

The AMF may perform the UE Capability Match Request procedure in the following cases in addition to the cases described in clause <NUM>. 8a of TS <NUM>.

As described above, when the NG-RAN checks the capability, the following problems may be solved. First, the NG-RAN does not check the IMS voice related capability of the UE and as a result, the NG-RAN provides the AMF no response regarding the voice support match. Second, the NG-RAN responds to the AMF that the voice support thereof does not match with that for the UE. Third, when the NG-RAN provides the AMF no response regarding the voice support match, the AMF may autonomously determine that the IMS voice is supported. When there is a voice call, if the UE is fallen back to the EPS or another RAT in the 5GC, the voice call may not be supported since the UE and RAN capabilities are not compatible with each other in terms of the voice support. Last, when the NG-RAN responds to the AMF that the voice support thereof does not match with that for the UE, the voice-centric UE may move to a system capable of supporting the voice (e.g., EPS) As a result, in this case, even though the UE may be served with high quality of data services in the 5GS in usual and use the EPS or a RAT capable of supporting voice services in the 5GC when there is a voice call, the UE may not be provided with the services in the 5GS.

Although <FIG> is similar to <FIG>, they are different in that <FIG> shows an example in which an AMF transmits to an NG-RAN (i.e., an (R)AN of <FIG>) Feature Specific UE/RAN Information and Compatibility Request. Although messages have different names, the basic principles are the same as described in <FIG>. Thus, the following details are applicable to <FIG> unless they collide with those of <FIG>. In addition, the details of <FIG> are applicable to <FIG> unless the details collide with those of <FIG>.

In step S1001, when transmitting the Feature Specific UE/RAN Information and Compatibility Request to the RAN, the AMF may contain the registration area of a UE. The AMF may include the registration area at all times or when sending the request in order to request the RAN to send RAN-related information about voice services.

In step S1004, if the RAN that receives the Feature Specific UE/RAN Information and Compatibility Request in step S1001 is a gNB and the gNB (here, the gNB may be interpreted as a cell thereof) does not support the IMS voice but is capable of handing over the UE to an E-UTRA (here, the E-UTRA may be connected to the 5GC or mean an EPS connected to the 5GC), the gNB (i.e., the NG-RAN) may operate as follows to provide a response to the AMF.

The candidate eNB(s) to which the UE may be handed over to receive the voice services may be configured in the gNB (for example, based on the O&M method) or may be derived based on the registration area of the UE if the AMF provides the registration area of the UE in step S1001. The eNB may be an ng-eNB connected to the 5GC or an eNB connected to the EPC. In the present disclosure, both the ng-eNB connected to the 5GC and the eNB connected to the EPC are commonly called the eNB. The gNB may obtain the network configuration of the candidate eNB(s), which is related to the voice services, in the same way as described in <FIG>.

The operation mentioned in <NUM>) may be performed after the Feature Specific UE/RAN Information and Compatibility Request is received from the AMF in step S1001 or before the Feature Specific UE/RAN Information and Compatibility Request is transmitted to the AMF in step S1004. In addition to the operation in <NUM>), when the gNB transmits Feature Specific UE/RAN Information and Compatibility Response to the AMF, the gNB may implicitly or explicitly inform that the voice support match information is not related to its network configuration. Additionally or alternatively, the gNB may implicitly or explicitly inform that the voice support match information is related to the network configuration of an eNB (connected to the EPC) or the network configuration of an ng-eNB (connected to the 5GC).

Referring again to <FIG>, according to another embodiment, when <NUM> QoS Flow that supports IMS voice is not successfully supported, the AMF may not perform the UE Capability Match Request procedure towards the NG-RAN in step <NUM>.

<FIG> illustrates the configurations of a UE device and a network node device according to embodiments of the present disclosure.

Referring to <FIG>, the network node device <NUM> may include a transceiver <NUM>, a processor <NUM>, and a memory <NUM>. The transceiver <NUM> may be configured to transmit and receive various signals, data, and information to and from an external device. The network node device <NUM> may be connected to the external device by wire and/or wirelessly. The processor <NUM> may be configured to control the overall operations of the network node device <NUM> and process information exchanged between the network node device <NUM> and external device. The memory <NUM> may be configured to store the processed information for a predetermined time and replaced with a component such as a buffer (not shown in the drawing). In addition, the processor <NUM> may be configured to perform the network node operations proposed in the present disclosure.

Specifically, a processor of an NG-RAN device may be configured to control a transceiver to receive a request for the capability of a UE related to IMS voice from an AMF, check whether the capability of the UE is compatible with a network configuration, and control the transceiver to transmit a response including the result of the checking to the AMF. The network configuration may include the network configuration of the NG-RAN and the network configuration of a network node capable of the IMS voice even though the NG-RAN does not support the IMS voice.

In addition, a processor of an AMF device is configured to control a transceiver to transmit a request for the capability of a UE related to IMS voice to an NG-RAN and control the transceiver to receive, from the NG-RAN, a response including the result of checking whether the capability of the UE is compatible with a network configuration. The network configuration may include the network configuration of the NG-RAN and the network configuration of a network node capable of the IMS voice even though the NG-RAN does not support the IMS voice.

Continuing to refer to <FIG>, the UE device <NUM> according to the present disclosure may include a transceiver <NUM>, a processor <NUM>, and a memory <NUM>. The transceiver <NUM> may be configured to transmit and receive various signals, data, and information to and from an external device. The UE device <NUM> may be connected to the external device by wire and/or wirelessly. The processor <NUM> may be configured to control the overall operations of the UE device <NUM> and process information exchanged between the UE device <NUM> and the external device. The memory <NUM> may be configured to store the processed information for a predetermined time and replaced with a component such as a buffer (not shown in the drawing). In addition, the processor <NUM> may be configured to perform the UE operations proposed in the present disclosure.

Regarding the configurations of the UE device <NUM> and the network device <NUM>, the above-described various embodiments of the present disclosure may be applied independently, or two or more embodiments of the present disclosure may be applied at the same time. Redundant description has been omitted for clarity.

The embodiments of the present disclosure may be implemented through various means, for example, hardware, firmware, software, or a combination thereof.

In a hardware configuration, the embodiments of the present disclosure may be achieved by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.
In a firmware or software configuration, a method according to embodiments of the present disclosure may be implemented in the form of a module, a procedure, a function, etc. Software code may be stored in a memory unit and executed by a processor. The memory unit is located at the interior or exterior of the processor and may transmit and receive data to and from the processor via various known means.

Claim 1:
A method performed by a next generation-radio access network, NG-RAN, that transmits and receives signals for indicating support of Internet protocol, IP, multimedia subsystem, IMS, voice in a wireless communication system, the method comprising:
receiving (S901), by the NG-RAN that supports radio access technology, RAT, fallback or evolved packet system, EPS, fallback for the IMS voice, a request message for capability of a user equipment, UE, related to the IMS voice from an access and mobility management function, AMF;
checking (S902, <NUM>), by the first NG-RAN, whether the capability of the UE is compatible with at least one network configuration; and
transmitting (S904), by the NG-RAN, to the AMF, a response message indicating whether the capability of the UE is compatible with the at least one network configuration or not,
wherein the at least one network configuration includes a first network configuration of the NG-RAN and a second network configuration of a network node, that is a target for the RAT fallback or the EPS fallback, capable of the IMS voice even though the NG-RAN does not support the IMS voice,
wherein the checking whether the capability of the UE is compatible with the at least one network configuration comprises, determining that the capability of the UE is compatible with the at least one network configuration, in case that the capability of the UE is compatible with the second network configuration even though the NG-RAN does not support the IMS voice, and
wherein when the NG-RAN does not support the IMS voice the second network configuration is obtained in one of the following ways: the second network configuration being obtained while the NG-RAN sets up an interface with the network node and exchanges network configuration information related to voice services; and the second network configuration being obtained by requesting the network node on an interface therebetween.