Patent Description:
To meet the demand for wireless data traffic having increased since deployment of <NUM>th generation (<NUM>) communication systems, efforts have been made to develop an improved 5th generation (<NUM>) or pre-<NUM> communication system. Therefore, the <NUM> or pre-<NUM> communication system is also called a 'Beyond <NUM> Network' or a 'Post Long Term Evolution (LTE) System'.

In the <NUM> system, Hybrid frequency shift keying (FSK) and quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.

Due to the development of various information technologies (ITs), network equipment has evolved into virtualized network functions (NFs) by applying virtualization technology thereto, and virtualized NFs are implemented in a form of software beyond physical limitations and thus may be installed/operated in various types of clouds or data centers (DCs). In particular, NFs can be freely scaled up or down, installed (initiated), or terminated according to service requirements, system capacity, and network load.

In order to support various services in these various network structures, network slicing technology has been introduced. Network slicing is a technology for logically configuring a network using a set of network functions (NFs) for supporting a specific service, and separating the network from other slices. One terminal may access two or more slices in the case of receiving various services.

<CIT> is concerned with allowing dual-registration (DR) capable UEs to fallback from 5GC to EPC.

<CIT> is concerned with a method of requesting/indicating to establish a PDU session using a UE's registration procedure.

<CIT> is concerned with transmitting, to a user terminal, a registration accept message indicating that a registration request of the user terminal for a network has been accepted; and when a <NUM> globally unique temporary identifier (<NUM>-GUTI) included in the registration accept message is newly allocated, receiving a registration complete message from the user terminal.

Based on the discussion as described above, the disclosure provides a method and apparatus for supporting various services by supporting mobility of a terminal in a wireless communication system.

In order to achieve the technical problem described above, various embodiments provide a method for operating a terminal in a wireless communication system. The method for operating a terminal includes: performing communication with an access and mobility management function (AMF) in a first network; and transmitting a radio resource control (RRC) message including information on the AMF in a second network.

Various embodiments provide an apparatus for a terminal in a wireless communication system. The apparatus for the terminal includes a transceiver, and at least one processor, wherein the at least one processor is configured to: perform communication with an access and mobility management function (AMF) in a first network; and transmit a radio resource control (RRC) message including information on the AMF in a second network.

According to various embodiments, the disclosure may provide a method and apparatus for supporting various services by supporting the mobility of a terminal in a wireless communication system.

Effects obtainable from the disclosure may not be limited to the above mentioned effects, and other effects which are not mentioned may be clearly understood, through the following descriptions, by those skilled in the art to which the disclosure pertains.

The terms used in the disclosure are only used to describe specific embodiments, and are not intended to limit the disclosure. A singular expression may include a plural expression unless they are definitely different in a context. Unless defined otherwise, all terms used herein, including technical and scientific terms, have the same meaning as those commonly understood by a person skilled in the art to which the disclosure pertains. Such terms as those defined in a generally used dictionary may be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the disclosure. In some cases, even the term defined in the disclosure should not be interpreted to exclude embodiments of the disclosure.

Hereinafter, various embodiments of the disclosure will be described based on an approach of hardware. However, various embodiments of the disclosure include a technology that uses both hardware and software, and thus the various embodiments of the disclosure may not exclude the perspective of software.

Hereinafter, the disclosure relates to a method and apparatus for supporting various services in a wireless communication system. Specifically, the disclosure describes a technology for supporting various services by supporting mobility of a terminal in a wireless communication system.

Hereinafter, in the disclosure, terms used to identify an access node, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to an interface between network entities, terms referring to various pieces of identification information, and the like are exemplified for convenience of explanation. Accordingly, the disclosure is not limited to the terms described below, and other terms indicating objects having equivalent technical meanings may be used.

Hereinafter, for convenience of explanation, the disclosure uses terms and names defined in the 3rd generation partnership project long term evolution (3GPP LTE) and the <NUM> standard. However, the disclosure is not limited by the terms and names, and can be applied to systems conforming to other standards.

<FIG> illustrates a wireless communication system according to various embodiments. <FIG> illustrates a base station <NUM>, a terminal <NUM>, and a terminal <NUM>, as a part of nodes which use a wireless channel in a wireless communication system. <FIG> illustrates only one base station, but other base stations identical or similar to the base station <NUM> may be further included.

The base station <NUM> is a network infrastructure for providing wireless access to the terminals <NUM> and <NUM>. The base station <NUM> includes a coverage which is defined as a predetermined geographic area based on a distance in which signal transmission is possible. The base station <NUM> may be referred to as, in addition to a base station, an "access point (AP)", an "eNodeB (eNB)", a "5th generation node (<NUM> node)", a "wireless point", a "transmission/reception point (TRP)" or other terms having an equivalent technical meaning thereof.

Each of the terminal <NUM> and the terminal <NUM> is a device used by a user, and performs communication with the base station <NUM> through a wireless channel. In some cases, at least one of the terminal <NUM> and the terminal <NUM> may be operated without user involvement. That is, at least one of the terminal <NUM> and the terminal <NUM> is a device for performing machine type communication (MTC), and may not be carried by a user. Each of the terminal <NUM> and the terminal <NUM> may be referred to as, in addition to a terminal, a "user equipment" (UE), a "mobile station", a "subscriber station", or a "remote terminal", a "wireless terminal", a "user device", or other terms having an equivalent technical meaning thereof.

The base station <NUM>, the terminal <NUM>, and the terminal <NUM> may transmit or receive a radio signal in a mmWave band (e.g., <NUM>, <NUM>, <NUM>, and <NUM>). Here, in order to improve a channel gain, the base station <NUM>, the terminal <NUM>, and the terminal <NUM> may perform beamforming. Here, beamforming may include transmission beamforming and reception beamforming. That is, the base station <NUM>, the terminal <NUM>, and the terminal <NUM> may give directivity to a transmission signal or a reception signal. To this end, the base station <NUM> and the terminals <NUM>, <NUM> may select serving beams <NUM>, <NUM>, <NUM>, and <NUM> through a beam search or beam management procedure. After the serving beams <NUM>, <NUM>, <NUM>, and <NUM> are selected, the subsequent communication is performed through a resource which is in a quasi- co-located (QCL) relationship with a resource having transmitted the serving beams <NUM>, <NUM>, <NUM>, and <NUM>.

<FIG> illustrates a configuration of a base station in a wireless communication system according to various embodiments. The configuration illustrated in <FIG> may be understood as a configuration of the base station <NUM>. The term "unit" or terms ending with suffixes "-er" and "-or" used in the following description refer to a unit which processes at least one function or operation, and may be implemented by hardware, software, or a combination of hardware and software.

Referring to <FIG>, the base station <NUM> includes a wireless communication unit <NUM>, a backhaul communication unit <NUM>, a storage <NUM>, and a controller <NUM>.

The wireless communication unit <NUM> performs functions for transmitting or receiving signals through a wireless channel. For example, the wireless communication unit <NUM> performs a conversion function between a baseband signal and a bit string according to a physical layer standard of a system. For example, at the time of data transmission, the wireless communication unit <NUM> generates complex symbols by encoding and modulating a transmission bit string. In addition, at the time of data reception, the wireless communication unit <NUM> reconstructs a reception bit string by demodulating and decoding the baseband signal. In addition, the wireless communication unit <NUM> up-converts a baseband signal into a radio frequency (RF) band signal and transmits the signal through an antenna, and down-converts an RF band signal received through the antenna into a baseband signal.

To this end, the wireless communication unit <NUM> may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital converter (ADC), and the like. Further, the wireless communication unit <NUM> may include a plurality of transmission/reception paths. Furthermore, the wireless communication unit <NUM> may include at least one antenna array configured by a plurality of antenna elements. In the hardware aspect, the wireless communication unit <NUM> may include a digital unit and an analog unit, and the analog unit may include a plurality of sub-units according to operating power, operating frequency, etc..

The wireless communication unit <NUM> transmits or receives signals as described above. Accordingly, all or part of the wireless communication unit <NUM> may be referred to as a "transmitter", a "receiver", a "transmitter/receiver", or a "transceiver". In addition, in the following description, transmission or reception performed through a wireless channel may include performing processing by the wireless communication unit <NUM> as described above.

The backhaul communication unit <NUM> provides an interface for performing communication with other nodes in a network. That is, the backhaul communication unit <NUM> converts a bit string, which is transmitted from the base station <NUM> to another node, for example, another access node, another base station, an upper node, and a core network, into a physical signal, and converts a physical signal, which is received from another node, into a bit string.

The storage <NUM> stores data, such as a basic program, an application program, and configuration information for the operation of the base station <NUM>. The storage <NUM> may include a volatile memory, a nonvolatile memory, or a combination of a volatile memory and a nonvolatile memory. Then, the storage <NUM> provides the stored data at the request of the controller <NUM>.

The controller <NUM> controls overall operations of the base station <NUM>. For example, the controller <NUM> transmits or receives signals through the wireless communication unit <NUM> or the backhaul communication unit <NUM>. In addition, the controller <NUM> records or reads data in and from the storage <NUM>. In addition, the controller <NUM> may perform functions of a protocol stack required in the communication standard. To this end, the controller <NUM> may include at least one processor.

<FIG> illustrates a configuration of a terminal in a wireless communication system according to various embodiments. The configuration illustrated in <FIG> may be understood as a configuration of the terminal <NUM>. The term "unit" or terms ending with suffixes "-er" and "-or" used hereinafter refer to a unit which processes at least one function or operation, and may be implemented by hardware, software, or a combination of hardware and software.

Referring to <FIG>, the terminal <NUM> includes a communication unit <NUM>, a storage <NUM>, and a controller <NUM>.

The communication unit <NUM> performs functions for transmitting or receiving signals through a wireless channel. For example, the communication unit <NUM> performs a conversion function between a baseband signal and a bit string according to a physical layer standard of the system. For example, at the time of data transmission, the communication unit <NUM> generates complex symbols by encoding and modulating a transmission bit string. In addition, at the time of data reception, the communication unit <NUM> reconstructs the received bit string by demodulating and decoding the baseband signal. In addition, the communication unit <NUM> up-converts a baseband signal into an RF band signal and transmits the signal through an antenna, and down-converts an RF band signal received through the antenna into a baseband signal. For example, the communication unit <NUM> may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC.

Further, the communication unit <NUM> may include a plurality of transmission/reception paths. Furthermore, the communication unit <NUM> may include at least one antenna array including a plurality of antenna elements. In the hardware aspect, the communication unit <NUM> may include a digital circuit and an analog circuit (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuit and the analog circuit may be implemented in one package. In addition, the communication unit <NUM> may include a plurality of RF chains. Furthermore, the communication unit <NUM> may perform beamforming.

The communication unit <NUM> transmits or receives signals as described above. Accordingly, all or a part of the communication unit <NUM> may be referred to as a "transmitter", a "receiver," a "transmitter/receiver", or a "transceiver". In addition, in the following description, transmission and reception performed through a wireless channel may include performing processing which is performed by the communication unit <NUM> as described above.

The storage <NUM> stores data, such as a basic program, an application program, and configuration information for the operation of the terminal <NUM>. The storage <NUM> may include a volatile memory, a nonvolatile memory, or a combination of a volatile memory and a nonvolatile memory. Then, the storage <NUM> provides the stored data at the request of the controller <NUM>.

The controller <NUM> controls overall operations of the terminal <NUM>. For example, the controller <NUM> transmits or receives signals through the communication unit <NUM>. In addition, the controller <NUM> records or reads data in or from the storage <NUM>. In addition, the controller <NUM> may perform functions of a protocol stack required by the communication standard. To this end, the controller <NUM> may include at least one processor or microprocessor, or may be a part of the processor. Also, a part of the communication unit <NUM> and the controller <NUM> may be referred to as a communication processor (CP).

<FIG> illustrates a configuration of a communication unit in a wireless communication system according to various embodiments. <FIG> illustrates an example of a detailed configuration of the wireless communication unit <NUM> of <FIG> or the communication unit <NUM> of <FIG>. Specifically, <FIG> illustrates elements for performing beamforming, as a part of the wireless communication unit <NUM> of <FIG> or as a part of the communication unit <NUM> of <FIG>.

Referring to <FIG>, the wireless communication unit <NUM> or the communication unit <NUM> includes an encoding and modulation unit <NUM>, a digital beamformer <NUM>, a plurality of transmission paths <NUM>-<NUM> to <NUM>-N, and an analog beamformer <NUM>.

The encoding and modulation unit <NUM> performs channel encoding. In order to perform channel encoding, at least one of a low density parity check (LDPC) code, a convolution code, and a polar code may be used. The encoding and modulation unit <NUM> generates modulation symbols by performing constellation mapping.

The digital beamformer <NUM> performs beamforming of a digital signal (e.g., modulation symbols). To this end, the digital beamformer <NUM> multiplies the modulation symbols by beamforming weights. Here, the beamforming weights are used to change the magnitude and the phase of the signal, and may be referred to as a "precoding matrix", a "precoder", or the like. The digital beamformer <NUM> outputs the digital-beamformed modulation symbols via the plurality of transmission paths <NUM>-<NUM> to <NUM>-N. Here, according to a multiple-input multiple-output (MIMO) transmission scheme, the modulation symbols may be multiplexed, or the same modulation symbols may be provided via the plurality of transmission paths <NUM>-<NUM> to <NUM>-N.

The plurality of transmission paths <NUM>-<NUM> to <NUM>-N convert the digital-beamformed digital signals into analog signals. To this end, each of the plurality of transmission paths <NUM>-<NUM> to <NUM>-N may include an inverse Fast Fourier transform (IFFT) operation unit, a cyclic prefix (CP) inserter, a DAC, and an up-converter. The CP inserter is for an orthogonal frequency division multiplexing (OFDM) scheme, and may be excluded when another physical layer scheme (e.g., filter bank multi-carrier (FBMC)) is applied. That is, the plurality of transmission paths <NUM>-<NUM> to <NUM>-N provide independent signal processing processes to a plurality of streams generated through digital beamforming. However, some of elements of the plurality of transmission paths <NUM>-<NUM> to <NUM>-N may be used in common according to the implementation scheme.

The analog beamformer <NUM> performs beamforming of analog signals. To this end, the digital beamformer <NUM> multiplies the analog signals by beamforming weights. Here, the beamforming weights are used to change the magnitude and the phase of a signal.

<FIG> is a flowchart illustrating a terminal operation in a wireless communication system according to various embodiments. <FIG> illustrates a method for operating a terminal.

Referring to <FIG>, in operation <NUM>, the terminal performs communication with an access and mobility management function (AMF) in a first network. According to an embodiment, the AMF is selected by considering a network slice, which is used by the terminal in the first network.

In operation <NUM>, the terminal transmits a radio resource control (RRC) message including information on the AMF in a second network. According to an embodiment, the RRC message includes a tracking area update (TAU) request or an initial access request in the second network.

According to various embodiments, the disclosure may further include: receiving, from an AMF, information of a network slice in a first network which is allowed to a UE; and generating an identifier of a dedicated core network (DCN) using the information of the network slice.

According to an embodiment, the information on the AMF includes an identifier of the AMF or an identifier of a dedicated core network (DCN), and the identifier of the DCN includes information of a network slice, which is used when the terminal moves from the first network to the second network. According to an embodiment, the information on the AMF includes an identifier of a mobility management entity (MME) or a temporary identifier of the UE.

<FIG> illustrates an example of an SBA-based <NUM> system structure in a wireless communication system according to various embodiments.

In order to support various services of <NUM>, a new system structure and a protocol are required, and 3GPP determines to introduce a new technology called service-based architecture (SBA). The main characteristics of the service-based architecture are to divide the functionalities of NFs, defined in the 3GPP standard, into service units, by considering the virtualization technology, introduction of cloud environment, and expansion of web-based services, and to use the HTTP/<NUM> protocol in implementing the services.

Referring to <FIG>, an access and mobility management function (AMF) is a network function (NF) for managing mobility and wireless network access to a UE. A session management function (SMF) is an NF for managing a session for the UE, and session information includes quality of service (QoS) information, charging information, and information about packet processing. A user plane function (UPF) is an NF for processing user plane traffic and is controlled by the SMF. Although not shown in <FIG>, the <NUM> system may include an unstructured data storage network function (UDSF), and the UDSF is an NF for storing unstructured data, and may store or retrieve any type of data at the request of the NF. The functions and services provided by AMF are similar to functions and services of a mobility management entity (MME) in a <NUM> network, and functions of AMF and MME may be integrated with each other, or may be implemented or built in a way that the functions thereof are included in each other.

Meanwhile, a network may be built/operated in the form of a network slice in order to provide various services or to provide convenience of isolation or management/operation of a network for each service in a <NUM>/<NUM> communication system. One network slice is a set of NF/NEs for configuring a network in order to provide communication services. The <NUM>-based network slice may include an AMF, an SMF, a UPF, a next generation radio access network (NG-RAN), and other network functions/network entities (NFs/NEs) interworking. The <NUM>-based network slice may include a mobility management entity (MME), a serving gateway (SGW), a packet data network gateway (PGW), and an evolved universal terrestrial radio access network (E-UTRAN), and other NFs/NEs interworking.

The level of isolation to be applied to each network slice may differ according to service requirements and operator policies. Network slices of some services types are completely isolated and thus information exchange with other network slices may be completely blocked, network slices of different service types may expose the minimal pieces of information, or other network slices of different types may expose all pieces of information. Since a network slice is understood as a concept of allocating a dedicated network to a specific service, the network slice and the dedicated network have similar meanings in the disclosure. In addition, in the case where units for realization of the concept of network slice are configured as network slice instances, the subject matter of the disclosure is equally applied. That is, the disclosure may apply the case where the network slice is to be replaced with a network slice instance.

<FIG> illustrates an example of a network structure in a wireless communication system according to various embodiments.

Referring to <FIG>, an example of a structure for providing service continuity by linking <NUM> and <NUM> networks is illustrated. In order to control the same subscriber, unified data management (UDM) and a home subscriber subsystem (HSS) needs to be linked to each other, and SMF/UPF needs to support the function of PGW in order to support session continuity (such as maintaining an IP address). In addition, the AMF and the MME may exchange information for supporting UE mobility between <NUM> and <NUM> through an N26 interface.

<FIG> illustrates a concept of a network slice, that is, a dedicated network, in a wireless communication system according to various embodiments.

Referring to <FIG>, an example in which each slice is completely isolated from each other is illustrated, and the example corresponds to an aspect in which each slice has the highest security level. That is, when <NUM>/<NUM> interworking is supported in each slice, <NUM> and <NUM> networks in the slice may exchange information with each other, but information exchange with other slices may not occur. In the network construction described above, RAN (NR-RAN or E-UTRAN) may be shared for each slice.

In the network configuration described above, the UE may access a <NUM> network in slice #<NUM> and receive a service, and then may shift to <NUM>. Here, status information (UE context) and security information (security context) for providing a communication service to a UE may be exchanged only inside the slice. However, if a base station, accessed by the UE, selects an evolve packet core (EPC) belonging to slice #<NUM> other than an EPC belonging to slice #<NUM>, the EPC may not provide continuity for a communication service to the UE since the EPC may not receive UE information from a <NUM> core network (5GC), and the UE is in a state of not being registered in the corresponding operator network. In this case, since the service is temporarily unavailable to the user, the quality of service experienced by the user may deteriorate.

<FIG> illustrates an example of a process of supporting various services in a wireless communication system according to various embodiments.

In operation <NUM>, a UE performs a registration process in order to receive a service through a <NUM> network. Detailed operations of the UE, a RAN, and a core network follows the standard, and in this case, an AMF is selected by considering a network slice to be used by the UE.

During the registration process, in operation <NUM>, if there is service/slice information (UE usage type) allocated to the UE in the <NUM> network, a server (UDM/HSS), which includes subscription information about a user, transmits, to the AMF, the subscription information of the UE (a user of the UE) having requested the registration, including the service/slice information (UE usage type).

In operation <NUM>, the AMF stores the received UE usage type of the UE. The stored UE usage type is one of status information (UE context), and may be transferred to another AMF.

In operation <NUM>, the UE shifts to a <NUM> network according to wireless conditions, service types, mobility, and the like. In operation <NUM>, the UE transmits a request for receiving a service in a <NUM> network to an evolved packet core (EPC, <NUM> core) through E-UTRAN. Here, the UE transmits a tracking area update (TAU) request or an initial attach request according to an operation mode of the UE. The operation mode of the UE is determined according to whether the UE allows an attach state in which a protocol data unit session (PDU session) does not exist. A message relating to the TAU request or the initial access is included in a radio resource control (RRC) message transmitted by the UE to the E-UTRAN. The request message transmitted by the UE includes information capable of finding an AMF which has been previously serving the UE in the <NUM> network. The information may be transmitted via a mapped MME identifier or a temporary identifier assigned to the UE.

In operation <NUM>, the E-UTRAN selects an MME for transferring the request (TAU or initial access) from the UE. Here, the E-UTRAN selects the MME using the information received in operation <NUM>. Here, since the mapped MME information transferred by the UE may be information substantially indicating the AMF and may include insufficient information to find an MME associated with the AMF (that is, the MME and AMF belonging to the same slice), the E-UTRAN may select a third MME, that is, an MME that does not belong to the same slice.

In operation <NUM>, the E-UTRAN transfers a non-access stratum (NAS) request, transmitted by the UE, to the selected MME. A message relating to the NAS request includes the identifier (or address) of the AMF which has been previously serving the UE.

In operation <NUM>, the MME determines whether the AMF, which includes existing status information (UE context) of the UE, is capable of interworking with the MME itself or whether the MME and AMF belong to the same slice, using the identifier of the AMF included in the request message of the UE. If interworking is possible, the MME directly transmits a message (context request) requesting status information (UE context) about the UE to the AMF. If interworking is not possible, the MME transmits, to the UDM/HSS, a request for receiving additional information about the UE instead of requesting the status information (UE context) (indicated in operation <NUM>).

Operation <NUM> corresponds to the case where the MME has difficulty in receiving status information (UE context) about the UE from the AMF, or to the case where the MMF cannot find the AMF associated with the MMF itself via the identifier transmitted by the UE. Here, before transmission of the status information (UE context) request, the MME requests additional information for determining whether it is necessary to transmit the request from the UE to another MME (i.e., belonging to a different slice/dedicated network) from the UDM/HSS. Here, the message used by the MME is an authentication information request (AIR), and in this case, the MME configures and transmits a flag explicitly requesting slice/dedicated network information (UE usage type) for a subscriber (UE).

In operation <NUM>, the UDM/HSS makes a response to the MME according to the request, and the MME transmits, in response to the request, if the subscriber includes slice/dedicated network information (UE usage type), an authentication information answer (AIA) message including the slice/dedicated network information.

This process is to be performed in order to receive information for selecting an MME according to a slice/dedicated network structure rather than actually performing authentication for the UE. Accordingly, the MME may include, in the authentication information request (AIR) message, an indication indicating the request described above and accordingly, UDM/HSS may include only requested information, other than the authentication information, in the authentication information answer (AIA) message.

In operation <NUM>, the MME determines whether it is necessary to process the request from the UE in another MME (i.e., another slice/dedicated network), using the information received from the UDM/HSS. Here, the MME may use, as configuration information, the address/identifier of the MME mapped to the specific UE usage type. Here, information of an MME (an MME group, an MME identifier, etc.) for processing the request from the UE is specified.

In operation <NUM>, the MME transfers, to the E-UTRAN, a request indicating to transfer the request from the UE to another MME (or an MME group) selected in operation <NUM>.

In operation <NUM>, the E-UTRAN selects a new MME using the information transferred by the MME, and the subsequent operation performs the remaining of the tracking area update (TAU) or initial attach process.

In operation <NUM>, a UE performs a registration process in order to receive a service through a <NUM> network. Detailed operations of the UE, a RAN, and a core network follow the standard, and in this case, an AMF is selected by considering a network slice to be used by the UE.

In operation <NUM>, the AMF stores the received UE usage type of the UE. The stored UE usage type is one of the status information (UE context), and may be transferred to another AMF.

In operation <NUM>, the UE shifts to a <NUM> network according to wireless conditions, service types, mobility, and the like. In operation <NUM>, the UE transmits a request for receiving a service in the <NUM> network to an evolved packet core (EPC, <NUM> core) through E-UTRAN. Here, the UE transmits a tracking area update (TAU) request or an initial attach request according to an operation mode of the UE. The UE transmits a radio resource control (RRC) message, transmitted by the UE to the E-UTRAN, including the TAU request or the initial access request therein. The request message transmitted by the UE includes information capable of finding an AMF which has been previously serving the UE in the <NUM> network. The information may be transmitted via a mapped MME identifier or a temporary identifier assigned to the UE.

In operation <NUM>, the E-UTRAN selects an MME for transferring the request (tracking area update (TAU) or initial access) from the UE. Here, the E-UTRAN selects the MME using the information received in operation <NUM>. Here, since the mapped MME information, transferred by the UE, may be information substantially indicating the AMF and may include insufficient information to find an MME associated with the AMF (that is, the MME and AMF belong to the same slice), the E-UTRAN may select a third MME, that is, an MME that does not belong to the same slice.

In operation <NUM>, the E-UTRAN transfers an NAS request, transmitted by the UE, to the selected MME. A message relating to the NAS request includes the identifier (or address) of the AMF which has been previously serving the UE.

In operation <NUM>, the MME determines whether the AMF, which includes existing status information (UE context) of the UE, is capable of interworking with the MME itself or whether the MME and AMF belong to the same slice, using the identifier of the AMF included in the request message of the UE. If normal processing is possible since interworking of the MME and the AMF is possible and the MME and the AMF belong to the same slice, the MME directly transmits a message (context request) requesting status information (UE context) about the UE to the AMF. Otherwise, the MME needs to receive additional information from the AMF to determine whether it is necessary to transmit the request from the UE to another MME (i.e., belonging to a different slice/dedicated network). Here, a method is to be used in which the MME transfers a separate message or indication for receiving a UE usage type of the UE to the AMF, and in response thereto, the AMF notifies of the UE usage type. Another method is that if the MME transmits a status information (UE context) request message including the identifier (or address) of the MME itself, similar to normal processing, the AMF may determine that the MME having transmitted the message enables interworking with the AMF itself or that the MME and the AMF do not belong to the same slice. If transmission of the entire status information (UE context) according to the request from the MME is impossible, the AMF may transmit information for transferring the request to another MME. Here, the AMF may notify the MME of the UE usage type, and may induce the MME, which has made the request, to select another MME (or a MME group) corresponding to the UE usage type (indicated in operation <NUM>), otherwise, the AMF itself may select information of MME (or MME group) and notify of the selected information.

In operation <NUM>, the MME transmits, to the E-UTRAN, a request indicating to transfer a request from the UE to another MME (or an MME group) selected in operation <NUM>.

In operation <NUM>, the E-UTRAN selects a new MME using the information transferred by the MME, and the remaining of the tracking area update (TAU) or initial attach process is performed in subsequent operations.

In operation <NUM>, a UE performs a registration process in order to receive a service through a <NUM> network. Detailed operations of a UE, a RAN, and a core network follow the standard, and in this case, an AMF is selected by considering a network slice to be used by the UE. During the above process, the UE may additionally include a capability of notifying the AMF of whether the UE itself requests a specific slice/dedicated network from the E-UTRAN using a dedicated core network identifier (DCN ID) in the <NUM> network, that is, a capability of notifying of whether the UE supports enhancements of dedicated core networks (eDECOR).

During the registration process, in operation <NUM>, if there is service/slice information (UE usage type) allocated to the UE in the <NUM> network, a server (UDM/HSS), which includes subscription information about a user, transmits, to the AMF, the subscription information of the UE (a user of the UE) having requested the registration, including the service/slice information (UE usage type) allocated to the UE.

In operation <NUM>, the AMF determines the slice/dedicated core network information (DCN ID) to be used for the UE at the time of moving to the <NUM> network. Here, in the case of determining the DCN ID, slice information allowed in the <NUM> network (allowed network slice selection assistance information, allowed NSSAI), a UE-usage type which is received via subscription information in operation <NUM>, and information configured for the AMF are considered. In addition, the AMF considers whether there is a subscribed DNN to which the <NUM> interworking is allowed, among the subscribed DNNs of the UE, based on the subscription information for the UE, and considers the capability of the UE having transmitted the request.

In operation <NUM>, the AMF transmits a registration accept message to the UE, and the message includes, if there is a slice allowed for the UE, the allowed slice information (allowed NSSAI) and the DCN ID determined in operation <NUM>. Here, the DCN ID may be configured in the form of mapping for each single network slice selection assistance information (S-NSSAI) included in the allowed slice information (allowed NSSAI), or may be transferred as one representative value for a UE rather than a value for each S-NSSAI.

In operation <NUM>, the UE shifts to a <NUM> network according to wireless conditions, service types, mobility, and the like. In operation <NUM>, the UE transmits a request for receiving a service in the <NUM> network to an evolved packet core (EPC, <NUM> core) through E-UTRAN. Here, the UE transmits a tracking area update (TAU) request or an initial attach request according to an operation mode of the UE. A message relating to the TAU request or the initial access request is included in a radio resource control (RRC) message transmitted by the UE to the E-UTRAN. The request message transmitted by the UE includes information capable of finding an AMF which has been previously serving the UE in the <NUM> network. The information may be transmitted via a mapped MME identifier or a temporary identifier assigned to the UE. In addition, the UE may transmit the RRC message including the DCN ID received in operation <NUM>.

In operation <NUM>, the E-UTRAN selects an MME for transferring the request (tracking area update (TAU) or initial access) from the UE. Here, the E-UTRAN selects the MME using the DCN ID, which is explicitly transmitted by the UE in operation <NUM>. If the MME selected using the DCN ID differs from the MME selected using a mapped MME identifier (or MME group identifier), the E-UTRAN may preferentially use the MME selected using the DCN ID.

In operation <NUM>, the MME transmits a request for status information (UE context) to the AMF using the identifier of the AMF, included in the request message of the UE, and in operation <NUM>, the MME receives the status information (UE context) in response thereto. In operation <NUM>, since the MME belonging to the same slice/dedicated network as that of the AMF may be selected, a request for status information (UE context) may be successfully processed.

From operation <NUM>, the remaining of a tracking area update (TAU) or initial attach process is performed. During this process, the MME may compare information received from the AMF, information received from the UDM/HSS, and the DCN ID requested by the UE, and may perform verification of the request from the UE.

In operation <NUM>, a UE performs a registration process in order to receive a service through a <NUM> network. Detailed operations of a UE, a RAN, and a core network follow the standard, and in this case, an AMF is selected by considering a network slice to be used by the UE.

During the registration process, in operation <NUM>, if there is service/slice information (UE usage type) allocated to the UE in the <NUM> network, a server (UDM/HSS), which includes subscription information about a user, transmits, to the AMF, the subscription information of a UE (a user of the UE) having requested the registration, including the service/slice information (UE usage type).

In operation <NUM>, the AMF determines the slice/dedicated core network information (DCN ID) to be used for the UE at the time of moving to the <NUM> network. Here, in the case of determining the DCN ID, allowed slice information (allowed NSSAI) in the <NUM> network, a UE-usage type which is received via subscription information in operation <NUM>, and information configured for the AMF are considered. In addition, the AMF considers whether there is a subscribed DNN to which the <NUM> interworking is allowed, among subscribed DNNs of the UE, based on the subscription information for the UE, and considers the capability of the UE having transmitted the request.

In operation <NUM>, the AMF transmits a registration accept message to the UE, and the message includes, if there is a slice allowed for the UE, the allowed slice information (allowed NSSAI).

In operation <NUM>, the UE may generate a protocol data unit (PDU) session according to the allowed slice information and traffic condition of the UE itself.

In operation <NUM>, the UE shifts to a <NUM> network according to wireless conditions, service types, mobility, and the like. In operation <NUM>, the UE transmits a request for receiving a service in the <NUM> network to an evolved packet core (EPC, <NUM> core) through E-UTRAN. Here, the UE transmits a tracking area update (TAU) request or an initial attach request according to an operation mode of the UE. A message relating to the TAU request or the initial access request is included in a radio resource control (RRC) message transmitted by the UE to the E-UTRAN. The request message transmitted by the UE includes information capable of finding an AMF which has been previously serving the UE in the <NUM> network. The information may be transmitted via a mapped MME identifier or a temporary identifier assigned to the UE.

During the process described above, the UE may generate a DCN ID according to whether or not a slice is used in <NUM> network of the UE itself, and include the generated DCN ID in the RRC message and transmit the same. In the current embodiment, since the UE does not explicitly receive the DCN ID from the network, the UE generates a mapped DCN ID using slice information.

The UE may generate the mapped DCN ID by copying only a slice/service type (SST) portion in the slice information (S-NSSAI) used by the UE itself, or may generate the DCN ID by copying <NUM> bits in the S-NSSAI. If the UE uses a plurality of slices, selection of S-NSSAI, which is to be used by the UE at the time of generating the mapped DCN ID may differ according to UE implementation.

In operation <NUM>, the E-UTRAN selects an MME for transferring a request (tracking area update (TAU) or initial access) from the UE. Here, the E-UTRAN selects the MME using the DCN IN, which is explicitly transmitted by the UE in operation <NUM>. If the MME selected using the DCN ID differs from the MME selected using a mapped MME identifier (or MME group identifier), the E-UTRAN may preferentially use the MME selected using the DCN ID. If it is not possible to select the MME associated with the E-UTRAN, via the DCN ID transmitted by the UE, the MME selected using the MME identifier (or MME group identifier) mapped to the MME may be preferentially used.

In operation <NUM>, the MME transmits a request for status information (UE context) to the AMF using the identifier of the AMF, included in the request message of the UE, and in operation <NUM>, the MME receives the status information (UE context) in response thereto.

In operation <NUM>, the MME may compare information received from the AMF, information received from the UDM/HSS, and the DCN ID requested by the UE, and may perform verification of the request from the UE.

From operation <NUM>, the remaining process of tracking area update (TAU) or initial attach is performed.

Meanwhile, various embodiments propose a technology which enables a user plane function (UPF) and a session management function (SMF), which support <NUM>-<NUM> interworking in a network in which a <NUM> core network (5GC) is introduced, to be used in a <NUM> dedicated UE. According to an embodiment, the SMF supports a function of a packet data network gateway control plane (PGW-C), and the UPF supports a function of a packet data network gateway user plane (PGW-U). In this case, a target UE is a UE supporting <NUM> (LTE/evolved packet system (EPS)) (that is, a UE supporting only EPC NAS), and the subscription information needs to be configured to allow access to <NUM> system (5GS). The access allowance to 5GS may be specifically expressed such that 5GC is not included in core network type restriction among subscription information.

The UE performs an access request (tracking area update (TAU) or initial attach) through the E-UTRAN, and the MME having received the access request receives, from the UDM/HSS, subscription information including the 5GS access allowance for the UE. Here, in the process of generating/adding a PDN connection, in a network configuration in which <NUM> service through SMF/UPF is allowed, the MME may select the SMF/UPF in a PGW selection process for a <NUM> UE.

Here, since session management function + packet data network gateway-control.

(SMF + PGW-C) is a device for <NUM>, but the UE supports only <NUM>, new parameters newly added for <NUM> need not be added to parameters transmitted to the UE. Further, unlike the <NUM> UE, the <NUM> UE itself cannot generate the PDU session ID, but the PDU session ID needs to be generated for the operation of the SMF/UPF. Therefore, the SMF/UPF generates a PDU session ID, instead of the UE, only when the <NUM> UE is connected, and uses the PDU session ID for interworking with unified data management (UDM)/policy control function (PCF).

Meanwhile, during the above process, a method for identifying, by the SMF + PGW-C, whether a UE is a UE supporting <NUM>, is required. According to an embodiment, the UE transmits whether the UE itself supports <NUM> (i.e., whether the UE supports <NUM> NAS) through protocol control options (PCO) or extended PCO (ePCO) included in a request message, which is transmitted to the SMF-PGW-C in order to establish a PDN connection. Whether <NUM> is supported in the direction in which the UE performs transmission to the network in the PCO/ePCO may be added as an information element (IE) of an additional parameter list among PCOs. In order to achieve the above configuration, a container includes, as contents thereof, a container identifier indicating whether the container includes a specific IE for indicating whether the UE supports <NUM>, a length thereof, and information indicating whether the UE supports <NUM>.

The SMF/PGW-C receives information on whether the UE supports <NUM> through PCO/ePCO during the process of generating the PDN connection. In the case where information on whether the UE supports <NUM> is explicitly included, the SMF/PGW-C determines that the UE supports <NUM>, and if not, the SMF/PGW-C determines that the UE does not support <NUM>.

According to another embodiment, in the case where the UE includes parameters, which are newly added in <NUM>, in the PCO or ePCO of the request message, rather than the case where the UE explicitly notifies the SMF/PGW-C of whether the UE support <NUM>, the SMF/PGW-C determines that the UE supports <NUM>. When the PDU session ID, among the parameters newly added in <NUM>, is included in the PCO or ePCO of a message requested in order to establish a PDN connection, the SMF/PGW-C determines that the UE supports <NUM>, and if the PDU session ID is not included in the PCO or ePCO, the SMF/PGW-C determines that the UE does not support <NUM> and generates the PUD session ID by itself.

Alternatively, the UE may notify the SMF/PGW-C of whether the UE supports <NUM> and a <NUM> session management (5GSM) cause value, among parameters, which are newly added for <NUM> in the PCO or ePCO of a message requested in order to establish a PDN connection. That is, if the 5GSM cause value is included in the request from the UE, the SMF/PGW-C determines that the UE supports <NUM>, and if not, the SMF/PGW-C determines that the UE does not support <NUM>.

In the above embodiment, when it is determined that the UE supports only <NUM>, the SMF/PGW-C needs not add the newly added parameters for <NUM> to parameters transmitted to the UE, and <NUM> parameters need not be included the PCO/ePCO in the direction in which the parameters are transmitted from the network to the UE. Further, unlike the <NUM> UE, the <NUM> UE cannot generate the PDU session ID by itself, but the PDU session ID needs to be generated for the operation of the SMF/UPF. Therefore, the SMF/UPF generates a PDU session ID, instead of the UE, only in the case where the <NUM> UE performs access, and uses the PDU session ID for interworking with the UDM/PCF.

The embodiment of <FIG> may be performed by a <NUM> network. The embodiment of <FIG> may be performed by any network function (NF) configuring a <NUM> network. However, the embodiment of <FIG> mainly describes the operation of an AMF.

In operation <NUM>, the AMF may receive a de-registration request message from a UE. The de-registration request message includes a temporary identifier (e.g., SG-globally unique temporary identifier (GUTI)) of the UE, a type of a deregistration request (switch-off, etc.) from the UE, or an access type to be deregistered (for example, 3GPP, Non-3GPP, or both).

In operation <NUM>, the AMF may determine whether there is a PDU session established for a UE which currently performs a request. Whether the PDU session is established may be determined, if the UE specifies an access type, based on whether a PDU session, which is in an established state for a corresponding access type, exists. The AMF may consider whether the PDU session, which is established for the UE having performed a request, is activated. The activation of the PDU session may denote that a resource, that is, a tunnel, is configured for the corresponding UE such that user plane data can be transmitted or received between an access node (AN) and a UPF. If there is an established or activated PDU session, the AMF may determine whether a public land mobile network (PLMN) has activated a secondary (<NUM>nd) RAT usage report. More specifically, the AMF may determine that a condition is satisfied in the case where the PLMN performs configuration such that the <NUM>nd RAT usage report is applied to the established or activated PDU session.

In the following operations <NUM> to <NUM> or operations <NUM> to <NUM>, only one procedure, which is selected between operations <NUM> to <NUM> and operations <NUM> to <NUM>, is performed according to the determination made in operation <NUM> described above. If two or more PDU sessions are established for the UE, the AMF may selectively apply operations <NUM> to <NUM> or operations <NUM> to <NUM> according to whether the <NUM>nd RAT usage report is applied to each PDU session.

In operation <NUM>, if the <NUM>nd RAT usage report is not needed to be applied, the AMF may transmit a message for a PDU session release request to the SMF. This process may be performed for each PDU session if a plurality of PDU sessions have been established for the UE.

In operation <NUM>, the AMF may receive a PDU session release response from the SMF. In addition, the remaining operations (e.g., PCF and policy termination) for PDU session release may be performed.

In operation <NUM>, if a response to the deregistration request, which has been received from the UE, needs to be transmitted, the AMF may transmit, in response thereto, a deregistration accept message, to the UE. In addition, the AMF may perform an operation of releasing an N2 signaling connection with a base station.

In operation <NUM>, if the <NUM>nd RAT usage report needs to be applied to the UE, the AMF may not immediately perform a procedure of releasing a PDU session together with the SMF. The AMF may transmit the deregistration accept message to the UE, as needed.

In operation <NUM>, if the <NUM>nd RAT usage report needs to be applied to the UE, the AMF may not immediately perform a procedure of releasing a PDU session together with the SMF, and may wait until a signaling connection with an access node (AN) is released. The above operation may be performed in order to receive <NUM>nd RAT usage data information from the AN during the operation of releasing the signaling connection with the AN, and to transmit the <NUM>nd RAT usage data information together with a PDU session release request to the SMF. The releasing of the signaling connection with the AN corresponds to the case where the AMF transmits an N2 UE context release request to the AN and receives a response thereto, or the case of receiving a message notifying that the UE context release has occurred from the AN.

In operation <NUM>, the AMF transmits a PDU session release request message to the SMF after the signaling connection with the AN is released. This process may be performed for each PDU session if multiple PDU sessions have been established for the UE. If the <NUM>nd RAT usage report to a target PDU session is required and the <NUM>nd RAT usage data information is received from the AN, the AMF may include the <NUM>nd RAT usage data information in a PDU session release request message (Nsmf_PDUSession_ReleaseSMContext Request).

In operation <NUM>, the AMF may receive a message indicating a PDU session release response from the SMF. In addition, the AMF may perform the remaining operations (e.g., PCF and policy termination) for the PDU session release.

Meanwhile, the embodiment of <FIG> may also be applied to the case where the <NUM> network deregisters the UE (i.e., NW-initiated deregistration) instead of the case where the AMF receives a request for deregistration from the UE. The case where the <NUM> network deregisters the UE (NW-initiated deregistration) may include at least one of cases where the AMF receives, if the subscription information of the UE is deleted, a request for deregistering the UE from the UDM, where communication with the UE is not performed until a timer inside the AMF expires, or where the UE needs to be deregistered by the intervention of the operator. When the <NUM> network deregisters the UE (NW-initiated deregistration), operation <NUM> may not be performed in the embodiment of <FIG>, and subsequent operations from operation <NUM> may be applied after the AMF determines to deregister the UE.

Claim 1:
A method for operating a network node in a wireless communication system, the method comprising:
receiving, from a user equipment, UE, supporting a first radio access technology, RAT, and a second RAT, a UE-initiated deregistration request message;
determining whether a protocol data unit, PDU, session is established for the UE;
characterised in that the method comprises:
determining whether a usage reporting for the second RAT is required for the PDU session, in case that the PDU session is established for the UE; and
based on the determination that the usage reporting for the second RAT is required for the PDU session, to receive the usage reporting for the second RAT, transmitting, to the UE, a deregistration accept message, and transmitting, to a radio access node, RAN, connected to the UE, a N2 UE context release request message for a signaling connection release of the RAN.