Apparatus and method for providing interworking of network slices in a wireless communication system

Abstract

A method for selecting a network slice by a control entity is provided. The method includes: in response to a PDN connectivity request message sent by a terminal, receiving a create session request message from an S-GW, sending a request message for subscriber information including identification information of the terminal to a storage entity, receiving subscription data of the terminal corresponding to the identification information of the terminal from the storage entity, selecting at least one network slice based on the subscription data of the terminal and slice information supportable by the control entity, and sending a create session response message including information of the selected at least one network slice, wherein the subscription data of the terminal includes information about the subscribed network slice of the terminal and information about whether the subscribed network slice of the terminal is supported in an evolved packet core (EPC).

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to a method for providing network slicing in a wireless communication system. Background Art

[0002] In order to meet the growing demand for wireless data services after the commercialization of the fourth generation (4G) communication system, considerable efforts have been made to develop a quasi-fifth generation (5G) communication system or a 5G communication system. This is one reason why a "5G communication system" or a "quasi-5G communication system" is referred to as a "super-4G network communication system" or a "post-long term evolution (LTE) system". In order to achieve high data rates, 5G communication systems are being developed to be implemented in ultra-high frequency bands (millimeter waves (mmWave)), such as a frequency band of 60 GHz. In order to reduce the path loss of radio waves in such ultra-high frequency bands and increase the transmission distance of radio waves in 5G communication systems, various technologies have been discussed and are being studied, such as: beamforming, massive multiple-input multiple-output (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antennas. In order to improve the system network for 5G communication system, various technologies have been developed, such as evolved small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-point (CoMP), and interference cancellation. In addition, for 5G communication system, other technologies have been developed, such as hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) schemes, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access schemes.

[0003] The Internet has evolved from a human-based connected network where humans create and consume information to the Internet of Things (IoT), where distributed components (such as objects) exchange information with each other to process information. Internet of Everything (IoE) technology is emerging, in which technologies related to IoT are combined with technologies for processing big data by connecting cloud servers. In order to realize IoT, various technical components are required, such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, security technology, etc. In recent years, technologies including sensor networks for connecting objects, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied. In the IoT environment, smart Internet technology (IT) services can be provided to collect and analyze data obtained from objects connected to each other to create new value in human life. As existing information technology (IT) technologies and various industries merge and combine with each other, IoT can be applied to various fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, high-quality medical services, etc.

[0004] Various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies related to sensor networks, M2M communications, MTC, etc. are being implemented using 5G communication technologies including beamforming, MIMO, array antennas, etc. The above-mentioned application of cloud RAN as a big data processing technology may be an example of the integration of 5G communication technology and IoT technology.

[0005] As described above, due to the development of wireless communication systems, various services can be provided, and therefore, there is a need for methods for effectively providing such services, and in particular, multiple methods for effectively providing network slicing.

[0006] The above information is presented as background information only to assist in understanding the present disclosure. No determination has been made, and no assertion has been made, as to whether any of the above may be applicable as prior art to the present disclosure. Summary of the invention

[0007] Technical Solution

[0008] According to an aspect of the exemplary embodiments, there is provided a communication method in wireless communication.

[0009] Beneficial Effects

[0010] Aspects of the present disclosure provide an efficient communication method in a wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

[0012] Figure 1is a schematic diagram of an interworking solution between a fifth generation system (5GS) and an evolved packet system (EPS) under non-roaming conditions according to an embodiment of the present disclosure;

[0013] Figure 2 is a schematic diagram of an interworking solution between 5GS and EPS under local breakout roaming conditions according to an embodiment of the present disclosure;

[0014] Figure 3 is a schematic diagram of an interworking solution between 5GS and EPS under home routing roaming conditions according to an embodiment of the present disclosure;

[0015] Figure 4 The network slice-specific authentication and authorization process in the terminal registration process according to an embodiment of the present disclosure is shown;

[0016] Figure 5 A process for determining single network slice selection assistance information (S-NSSAI) for a packet data network (PDN) connection according to an embodiment of the present disclosure is shown;

[0017] Figure 6 shows a configuration of a terminal according to an embodiment of the present disclosure; and

[0018] Figure 7 The configuration of the network entity according to an embodiment of the present disclosure is shown.

[0019] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures.

[0020] Best Mode

[0021] Aspects of the present disclosure at least address the above-mentioned problems and / or disadvantages and provide at least the following advantages. Therefore, one aspect of the present disclosure is to provide a method and apparatus for interworking between a fifth generation (5G) network system architecture and an evolved packet system (EPS) network providing a network slicing function.

[0022] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0023] According to one aspect of the present disclosure, a method for selecting a network slice by a control entity is provided. The selection method includes: in response to a packet data network (PDN) connectivity request message sent by a terminal, receiving a create session request message from a service gateway (S-GW), sending a request message for subscriber information including identification information of the terminal to a storage entity, receiving subscription data of the terminal corresponding to the identification information of the terminal from the storage entity, selecting at least one network slice based on the subscription data of the terminal and slice information supportable by the control entity, and sending a create session response message including information of the selected at least one network slice, wherein the subscription data of the terminal includes information about the subscribed network slice of the terminal and information about whether the subscribed network slice of the terminal is supported in an evolved packet core (EPC).

[0024] The information about whether the subscribed network slice of the terminal is supported in the EPC may include information indicating whether the subscribed network slice of the terminal is subject to network slice-specific authentication and authorization (NSSAA).

[0025] The selection may include selecting a network slice from among the subscribed network slices of the terminal that is not subject to NSSAA and that is supportable by the control entity.

[0026] The PDN connectivity request message may include information of an access point name (APN) requested from the terminal, wherein the selection includes selecting a network slice from among the subscribed network slices of the terminal that is not subject to NSSAA, supports the APN, and is supportable by the control entity.

[0027] The PDN connectivity request may be rejected when there is no network slice selectable by the control entity.

[0028] The case where there is no network slice selectable by the control entity may include a case where all network slices supportable by the control entity from among the subscribed network slices of the terminal are subject to NSSAA.

[0029] The control entity may be a combined node of a Session Management Function (SMF) and a PDN Gateway Control (PGW-C), and the storage entity may be a combined node of a Home Subscriber Server (HSS) and a Unified Data Management (UDM).

[0030] According to another aspect of the present disclosure, a method for supporting selection of a network slice by a storage entity is provided. The supporting method includes receiving a request message for subscriber information including identification information of a terminal from a control entity, and sending subscription data of a terminal corresponding to the identification information of the terminal to the control entity, wherein the subscription data of the terminal includes information about the subscription network slice of the terminal and information about whether the subscription network slice of the terminal is supported in the EPC.

[0031] The information about whether the subscribed network slice of the terminal is supported in the EPC may include information indicating whether the subscribed network slice of the terminal is subject to NSSAA.

[0032] The control entity may be a combined node of SMF and PGW-C, and the storage entity may be a combined node of HSS and UDM.

[0033] According to another aspect of the present disclosure, a control entity for selecting a network slice is provided. The control entity for selecting a network slice includes a transceiver and a processor coupled to the transceiver, and is configured to: in response to a PDN connectivity request message sent by a terminal, receive a create session request message from an S-GW, send a request message for subscriber information including identification information of the terminal to a storage entity, receive subscription data of a terminal corresponding to the identification information of the terminal from the storage entity, select at least one network slice based on the subscription data of the terminal and slice information that can be supported by the control entity, and send a create session response message including information of the selected at least one network slice, wherein the subscription data of the terminal includes information about the subscribed network slice of the terminal and information about whether the subscribed network slice of the terminal is supported in the EPC.

[0034] The information about whether the subscribed network slice of the terminal is supported in the EPC may include information indicating whether the subscribed network slice of the terminal is subject to NSSAA.

[0035] The processor may also be configured to select a network slice from among the subscribed network slices of the terminal that is subject to NSSAA and that is supportable by the control entity.

[0036] The PDN connectivity request message may include information of the APN requested from the terminal, wherein the processor is further configured to select a network slice from among the subscribed network slices of the terminal that is not subject to NSSAA, supports the APN, and is supportable by the control entity.

[0037] The processor may also be configured to reject the PDN connectivity request when there are no network slices selectable by the control entity.

[0038] The case where there is no network slice selectable by the control entity may include a case where all network slices supportable by the control entity among the subscribed network slices of the terminal are subject to NSSAA.

[0039] The control entity may be a combined node of SMF and PGW-C, and the storage entity may be a combined node of HSS and UDM.

[0040] According to another aspect of the present disclosure, a storage entity for supporting selection of a network slice is provided. The storage entity for supporting selection of a network slice includes a transceiver and a processor coupled to the transceiver, and is configured to: receive a request message for subscriber information including identification information of a terminal from a control entity, and send subscription data of a terminal corresponding to the identification information of the terminal to the control entity, wherein the subscription data of the terminal includes information about the subscribed network slice of the terminal and information about whether the subscribed network slice of the terminal is supported in the EPC.

[0041] The information about whether the subscribed network slice of the terminal is supported in the EPC may include information indicating whether the subscribed network slice of the terminal is subject to NSSAA.

[0042] The control entity may be a combined node of SMF and PGW-C, or SMF or PGW-C, and the storage entity may be a combined node of HSS and UDM, or UDM or HSS.

[0043] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. DETAILED DESCRIPTION

[0044] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these are to be regarded as exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and conciseness.

[0045] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0046] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0047] It will be understood that each frame of the process diagram and the combination of frames in the process diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing equipment, so that the instructions run by the processor of the computer or other programmable data processing equipment generate a device for performing the function specified in the (multiple) process diagram block. These computer program instructions can also be stored in a computer executable or computer readable memory, which can instruct the computer or other programmable data processing equipment to run in a specific manner, so that the instructions stored in the computer executable or computer readable memory generate a product including an instruction device for performing the function specified in the (multiple) process diagram block. The computer program instructions can also be loaded onto a computer or other programmable data processing equipment so that a series of operations are performed on the computer or other programmable data processing equipment, thereby generating a computer executable process, so that the instructions running on the computer or other programmable data processing equipment provide operations for implementing the functions specified in one or more frames of the process diagram.

[0048] In addition, each frame can represent a module, segment or part of a code, which includes one or more executable instructions for realizing (multiple) specific logic functions. It should also be noted that in some optional implementations, the functions mentioned in the frame may not occur in the order given. For example, according to the functions involved, two frames shown in succession can actually be run substantially simultaneously, or these frames can sometimes be run in reverse order.

[0049] The term "unit" or "device" used herein represents a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and performs a specific function. However, the term "unit" or "device" is not limited to software or hardware. The term "unit" or "device" can be configured to be included in an addressable storage medium, or to copy one or more processors. Therefore, the term "unit" or "device" can include, for example, object-oriented software components, class components and task components, as well as processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and variables. The functions provided by components and "units" or "devices" can be combined into smaller numbers of components and "units" or "devices", or can be further divided into additional components and "units" or "devices". In addition, components and "units" or "devices" can be implemented to operate one or more central processing units (CPUs) in a device or a secure multimedia card.

[0050] Throughout this disclosure, the expression "at least one of a, b, or c" means only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof.

[0051] Examples of the terminal may include a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smart phone, a computer, a multimedia system capable of performing a communication function, and the like.

[0052] In this disclosure, a controller may also be referred to as a processor.

[0053] Throughout this specification, a layer (or a layer arrangement) may also be referred to as an entity.

[0054] In the following, a base station is an entity that assigns resources to a terminal, and may be at least one of a node B (NB), a base station (BS), an evolved node B (eNB), a next generation node B (gNB), a radio access unit, a base station controller, or a node on a network. The embodiments of the present disclosure may be applied to other communication systems having a technical background and channel configuration similar to the embodiments of the present disclosure. In addition, those skilled in the art should understand that the embodiments of the present disclosure may be applied to other communication systems, but modifications do not depart from the scope of the present disclosure.

[0055] For the convenience of description, examples are given of terms used to identify access nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. However, the present disclosure is not limited to the following terms, and other terms with equivalent technical meanings may be used.

[0056] The present disclosure relates to an apparatus and method for providing interworking of network slicing in a wireless communication system. More specifically, the present disclosure provides a description of interworking technology between a fifth generation (5G) network system architecture and an evolved packet system (EPS) network system that provide network slicing functionality in a wireless communication system.

[0057] As used below, for the convenience of description, terms indicating signals, terms indicating channels, terms indicating control information, terms indicating network entities, terms indicating device components, etc. will be given. However, the present disclosure is not limited to the following terms, and other terms with equivalent technical meanings may be used.

[0058] Although the present disclosure will be described with reference to various embodiments thereof using terms used in some communication standards (eg, 3rd Generation Partnership Project: 3GPP), these are merely examples for description. Various embodiments of the present disclosure may be easily modified to apply to other communication systems.

[0059] In the 3GPP standard, the 5G network system architecture and process are standardized. Mobile operators can provide a variety of services on 5G networks. In order to provide each service, mobile operators need to meet the different service requirements of each service (e.g., latency, communication range, data rate, bandwidth, reliability, etc.). To this end, mobile operators can configure network slices and assign network resources suitable for specific services to each network slice or each group of network slices. Network resources may refer to network functions (NFs) or the assignment of logical resources provided by NFs or the assignment of wireless resources of base stations, and are not limited to the above examples.

[0060] For example, a mobile operator can configure network slice A to provide mobile broadband services, configure network slice B to provide vehicle communication services, and configure network slice C to provide IoT services. That is, in a 5G network, corresponding services can be provided on specially designed network slices according to the characteristics of the services. Single Network Slice Selection Assistance Information (S-NSSAI) defined in 3GPP can be used as an identifier to identify a network slice.

[0061] Mobile operators can operate 5G networks and EPS (or Long Term Evolution (LTE) or 4G) networks together. The terminal can access the 5G network and move to the EPS network while using services. Alternatively, the terminal can access the EPS network and move to the 5G network while using services.

[0062] In the present disclosure, a method for interworking between a 5G network system architecture and an EPS network system providing a network slicing function is defined. Figure 1 , Figure 2 and Figure 3 The interworking scheme of 5G system (5GS) and EPS is shown.

[0063] In addition, in the present disclosure, network operations and terminal operations are defined, wherein a terminal that uses a communication service by establishing a session connection in EPS can seamlessly use the service even when the terminal moves to 5GS. According to an embodiment of the present disclosure, a network function may indicate a network entity (hereinafter, used interchangeably with "NE") or a network resource. Figure 1 1 is a schematic diagram of an interworking scheme between 5GS and EPS under non-roaming conditions according to an embodiment of the present disclosure. 5GS may include a new radio (NR) base station 150, an access and mobility management function (AMF) 145, a session management function (SMF) 120, a user plane function (UPF) 125, a policy control function (PCF) 115, and a unified data management (UDM) 110.

[0064] Reference Figure 1, AMF 145 may be a network function that manages the terminal's access to the wireless network and the terminal's mobility. In addition, SMF 120 may be a network function that manages the packet data network connection provided to the terminal. In addition, UPF 125 may act as a gateway for sending packets sent or received by the terminal, and may be controlled by SMF 120. In addition, PCF 115 may be a network function for applying service policies, charging policies, and policies regarding protocol data unit (PDU) sessions to the terminal by a mobile operator. In addition, UDM 110 may be a network function that stores and manages information about subscribers. However, the configuration of 5GS is not limited to the above examples.

[0065] According to an embodiment of the present disclosure, the EPS may include an evolved universal terrestrial radio access (E-UTRA) base station 140, a mobility management entity (MME) 135, a serving gateway (S-GW) 130, a PDN gateway-user plane (PGW-U) 125, a PDN gateway-control plane (PGW-C) 120, a policy and charging function (PCRF) 115, and a home subscriber server (HSS) 110.

[0066] According to an embodiment of the present disclosure, the MME 135 may be a network function that authenticates the terminal 155, manages sessions such as bearers, and manages the connectivity state of the terminal 155. In addition, according to an embodiment of the present disclosure, the S-GW 130 may be a network function that forwards data (or data packets). In addition, the PGW-C 120 and the PGW-U 125 may be network functions that provide connectivity between the terminal and a packet data network (PDN) as an external network (not shown). In addition, the PCRF 115 may be a network function that determines a charging policy and a quality of service (QoS) policy to be applied to the terminal 155, and in some embodiments, the HSS 110 may be a network function that includes information for authentication of the terminal 155. Figures 1 to 3 As shown, S1-MME, S6a, S11, S1-U, S-5C, S5-U, S-8C, and S8-U are interfaces for E-UTRAN connectivity, and N1, N2, N3, N4, N8, N9, N10, N11, N15, N16, N24, and N26 are interfaces for NG-RAN connectivity. However, the configuration of EPS is not limited to the above example.

[0067] Reference Figure 1, the UDM 110 of 5GS and the HSS 110 of EPS can be configured as a combined node. The SMF 120 of 5GS and the PGW-C 120 of EPS can be configured as a combined node. The UDM 110 of 5GS and the HSS 110 of EPS can be configured as a combined node, and the node of UDM+HSS 110 can store the subscriber information of the terminal. The UPF 125 of 5GS and the PGW-U 125 of EPS can be configured as a combined node. The terminal 155 can use the EPS network service by accessing the MME 135 of EPS via the E-UTRA base station 140. In addition, the terminal 155 can use the 5GS network service by accessing the AMF 145 of 5GS via the NR base station 150. Figure 2 FIG. 1 is a diagram of an interworking solution between 5GS and EPS under local breakout roaming conditions according to an embodiment of the present disclosure. Figure 2 , by reference Figure 1 , the terminal 260 can use the EPS network service by accessing the MME 240 of the EPS via the E-UTRA base station 245. In addition, the terminal 260 can use the 5GS network service by accessing the AMF 250 of the 5GS via the NR base station 255. In the interworking scheme between the 5GS and the EPS in the local export roaming, the node of the SMF+PGW-C 225 can be located in the visited public land mobile network (V-PLMN). Similar to Figure 1 , Figure 2 An SGW node 235, a HSS+UDM combination node 210, an h-PCF+h-PCRF combination node 215, a v-PCF+v-PCRF combination node 220, and a UPF+PGW-U combination node 230 are shown.

[0068] Figure 3 FIG. 1 is a diagram of an interworking solution between 5GS and EPS under home routing roaming conditions according to an embodiment of the present disclosure. Figure 3 , as referenced Figure 1 As described, the terminal 370 can use the EPS network service by accessing the MME 335 of the EPS via the E-UTRA base station 340. In addition, the terminal 370 can use the 5GS network service by accessing the AMF 360 of the 5GS via the NR base station 365. In the interworking scheme between the 5GS and the EPS in the home route roaming, the node of the SMF+PGW-C 320 can be located in the home PLMN. Similar to Figure 1 and Figure 2 , Figure 3An SGW node 330, a HSS+UDM combination node 310, an h-PCF+h-PCRF combination node 315, a v-PCF node 345, a v-SMF node 350, and a UPF+PGW-U combination node are shown.

[0069] Example 1

[0070] Figure 4 The network slice specific authentication and authorization (NSSAA) process in the terminal registration process according to an embodiment of the present disclosure is shown. That is, Figure 4 The method for performing the NSSAA process during the terminal registration process is shown. The AMF can store relevant information in the UDM according to the result (success or failure) of the NSSAA related to the S-NSSAI.

[0071] Reference Figure 4 In operation 401, the UE may generate a registration request message. The requested NSSAI to be used by the UE may be included in the registration request message. According to an embodiment of the present disclosure, the requested NSSAI may include one or more S-NSSAIs. For example, the requested NSSAI may include S-NSSAI A and S-NSSAI B.

[0072] According to an embodiment of the present disclosure, the UE may send a registration request message to the AMF via a base station (also referred to as a RAN). In operation 402, the base station may receive the registration request message sent by the UE. However, the name of the message is not limited to the above example.

[0073] In operation 403, the base station authenticates the received registration request message and may select an AMF based on the UE ID (such as 5G-GUTI), the requested NSSAI, etc.

[0074] In operation 404, the base station may send a registration request message to the selected AMF.

[0075] In operation 405, the AMF may obtain UE subscription data from the UDM to process the registration request message. According to an embodiment of the present disclosure, the UE subscription data may include at least one of the UE's subscription slice (subscribed S-NSSAI) or information indicating whether the subscription slice is subject to NSSAA (the subscribed S-NSSAI is marked as subject to network slice-specific authentication and authorization). For example, the UE's subscription may include S-NSSAI A and S-NSSAI B, and S-NSSAI A may be subject to NSSAA.

[0076] In operation 406, the AMF may determine the allowed NSSAI based on the UE subscription data received from the UDM in operation 405. According to an embodiment of the present disclosure, the allowed NSSAI may include one or more S-NSSAIs available to the UE. For example, when S-NSSAI A and S-NSSAI B are included in the requested NSSAI requested by the UE, and both S-NSSAI A and S-NSSAI B are included in the subscription slice, S-NSSAI A and S-NSSAI B requested by the UE may be used. However, since S-NSSAI A is subject to NSSAA, the AMF may determine that only S-NSSAI B is included in the allowed NSSAI.

[0077] In operation 407, the AMF may send a registration accept message to the UE. The registration accept message may include the allowed NSSAI determined in operation 406. In addition, the registration accept message may include information (e.g., an indication, an indicator, or a cause value) indicating that the S-NSSAI A is undergoing an NSSAA process. The registration accept message sent by the AMF may be sent to the UE through the base station. However, the name of the message is not limited to the above example.

[0078] In operation 408, the base station may transmit a registration accept message to the UE. The UE may use the S-NSSAI B included in the allowed NSSAI included in the registration accept message. In addition, the UE may know that the S-NSSAI A requested in operation 402 is undergoing the NSSAA process.

[0079] In operation 409, the AMF may store the UE context in the UDM. The UE context update message sent by the AMF to the UDM may be a Nudm_UECM_Registration message or a Nudm_UECM_Update message. However, the name of the message is not limited to the above example. The UE context update message may include the allowed NSSAI of the UE determined by the AMF in operation 406. In addition, the UE context update message may include information indicating that S-NSSAI A is undergoing the NSSAA process. The UDM may store the allowed NSSAI and the S-NSSAI undergoing NSSAA information as the UE context. For example, in the UDM, a UE context in which the allowed NSSAI is S-NSSAI B and the S-NSSAI undergoing NSSAA is S-NSSAI A may be stored.

[0080] In operation 410, the AMF may start the NSSAA procedure of the S-NSSAIA.

[0081] According to an embodiment of the present disclosure, operation 409 may be performed after operation 406. The AMF may perform operation 409 before operation 407.

[0082] The NSSAA procedure of the S-NSSAI A started in operation 409 is completed in operation 411. When the NSSAA of the S-NSSAI A succeeds (Extensible Authentication Protocol (EAP) succeeds), the AMF may add the S-NSSAI A to the allowed NSSAIs.

[0083] In operation 412, when NSSAA of S-NSSAI A succeeds, the AMF may send a new allowed NSSAI to the UE. The message of operation 412 may be a UE configuration update command message. However, the name of the message is not limited to the above example. S-NSSAI A for which NSSAA has succeeded and S-NSSAI B previously included in the previously allowed NSSAI may be added together in the new allowed NSSAI. The UE may use S-NSSAI A and S-NSSAI B included in the allowed NSSAI.

[0084] When NSSAA of S-NSSAI A fails (EAP failure), the AMF may include information indicating that NSSAA of S-NSSAI A has failed (e.g., an indication, an indicator, or a cause value, etc.) in the message of operation 412, and send the message to the UE. The message of operation 412 may be a UE configuration update command message. However, the name of the message is not limited to the above example. The UE continues to use S-NSSAI B included in the allowed NSSAI received in operation 408, and may know that S-NSSAI A is unavailable.

[0085] In operation 413, the AMF may store the UE context in the UDM. The UE context update message sent by the AMF to the UDM may be a Nudm_UECM_Registration message or a Nudm_UECM_Update message. However, the name of the message is not limited to the above example. The UE context update message may include information according to the result of the NSSAA (success or failure) of operation 411.

[0086] For example, when the NSSAA of S-NSSAI A has succeeded, and S-NSSAI A and S-NSSAI B are included in the allowed NSSAI, the message sent by the AMF to the UDM in operation 413 may include the new allowed NSSAI. In addition, the message sent by the AMF to the UDM in operation 413 may include information indicating that the NSSAA of S-NSSAI A is successful (e.g., an indicator indicating that the NSSAA of S-NSSAI A is successful). In addition, the message of operation 413 may include the effective time of the NSSAA success of S-NSSAI A. The UDM may store the information received from the AMF.

[0087] Optionally, for example, when the NSSAA of the S-NSSAI A has failed, the message sent by the AMF to the UDM in operation 413 includes information indicating that the NSSAA of the S-NSSAI A has failed (e.g., an indicator indicating that the NSSAA of the S-NSSAI A has failed). The UDM may store the information received from the AMF.

[0088] Example 2

[0089] Figure 5 FIG. 2 shows a process of determining S-NSSAI for PDN connectivity according to an embodiment of the present disclosure. Figure 5 , when a terminal connects to the Evolved Packet Core (EPC) to request PDN connectivity, the SMF+PGW-C can determine the S-NSSAI for PDN connectivity based on the information received from the UDM+HSS.

[0090] In operation 501, the terminal may send a PDN connectivity request to the MME to establish PDN connectivity. The PDN connectivity request message may include access point name (APN) information requested by the terminal. The PDN connectivity request message may be sent to the MME via an E-UTRA base station. The name of the message is not limited to the above example.

[0091] In operation 502, the MME, which has received the PDN connectivity request message in operation 501, may send a create session request to the S-GW. The name of the message is not limited to the above example.

[0092] In operation 503, the S-GW having received the create session request message in operation 502 may send a create session request message to the SMF+PGW-C. The name of the message is not limited to the above example.

[0093] In operation 504, the SMF+PGW-C, which has received the create session request message in operation 503, may perform an Internet Protocol (IP)-Connectivity Access Network (CAN) session setup or correction procedure with the PCF+PCRF.

[0094] In operation 505, the SMF+PGW-C that has received the create session request message in operation 503 may send a Nudm_SDM_Get request message to the UDM+HSS. According to an embodiment of the present disclosure, the Nudm_SDM_Get request message may include the data type of the requested subscriber information and key information of the data type via which the subscriber information may be accessed. According to an embodiment of the present disclosure, the key information of the data type via which the subscriber information may be accessed may be included in a "Subscription Permanent Identifier (SUPI)" as a terminal ID. In addition, the name of the message is not limited to the above example.

[0095] In operation 506, the UDM+HSS having received the Nudm_SDM_Get request message in operation 505 may transmit UE subscription data corresponding to the terminal corresponding to the SUPI to the SMF+PGW-C. The name of the message is not limited to the above example.

[0096] For example, when the subscription slice (subscribed S-NSSAI) is included in the UE subscription data, SMF+PGW-C can select an S-NSSAI that can be supported by SMF+PGW-C from the subscribed S-NSSAI.

[0097] For example, when a subscription slice and an APN list (or DNN list) supported by each subscription slice are included in the UE subscription data, the SMF+PGW-C can select an S-NSSAI supported by the SMF+PGW-C from the S-NSSAIs that support the subscription of the APN requested by the terminal.

[0098] For example, when a subscription slice and information indicating whether the subscription slice is subject to NSSAA (S-NSSAI marked as a subscription subject to network slice-specific authentication and authorization) are included in the UE subscription data, the SMF+PGW-C can select an S-NSSAI that can be supported by the SMF+PGW-C from among the S-NSSAIs that are not subject to NSSAA in the subscription slice. This can be to prevent the S-NSSAI subject to NSSAA from being selected because the NSSAA procedure is not supported in the EPC.

[0099] For example, when a subscription slice and information indicating whether the subscription slice is subject to NSSAA (S-NSSAI marked as a subscription subject to authentication and authorization specific to the network slice) are included in the UE subscription data, the SMF+PGW-C can select an S-NSSAI that can be supported by the SMF+PGW-C from the subscription slice. When the S-NSSAI selected by the SMF+PGW-C is subject to NSSAA, the SMF+PGW-C can include an indicator indicating that the S-NSSAI is subject to NSSAA in the create session response message to be sent to the S-GW in operation 507, and send a create session response message. The indicator indicating that the S-NSSAI is subject to NSSAA can be sent to the terminal by performing operations 508, 509, and 510. The name of the message is not limited to the above example. This can be to allow the terminal to move to the fifth generation core (5GC) and perform the NSSAA process when an S-NSSAI subject to NSSAA is selected, because the NSSAA process is not supported in the EPC.

[0100] For example, when a subscription slice, a list of APNs supported by each subscription slice, and information indicating whether the subscription slice is subject to NSSAA (S-NSSAI marked as a subscription subject to network slice-specific authentication and authorization) are included in the UE subscription data, the SMF+PGW-C can select an S-NSSAI supportable by the SMF+PGW-C from among the S-NSSAIs that support subscription to the APN requested by the terminal and that are not subject to NSSAA.

[0101] For example, when the subscription slice and NSSAA result information (e.g., an indicator indicating that the NSSAA of the S-NSSAI has succeeded, the effective time of the NSSAA success of the S-NSSAI, an indicator indicating that the NSSAA of the S-NSSAI has failed, etc.) are included in the UE subscription data, the SMF+PGW-C can select an S-NSSAI that can be supported by the SMF+PGW-C from the remaining subscription slices except the S-NSSAI for which the NSSAA has failed. This can be to allow the selection of an S-NSSAI that has successfully NSSAA in the 5GC from an S-NSSAI that has not undergone NSSAA or an S-NSSAI that has undergone NSSAA, because the NSSAA process is not supported in the EPC.

[0102] For example, when the UE subscription data includes allowed NSSAI, SMF+PGW-C can select S-NSSAI that can be supported by SMF+PGW-C from the allowed NSSAI. This can be to allow selection of S-NSSAI approved for use in 5GC because the NSSAA process or the method for determining allowed NSSAI is not supported in EPC.

[0103] When the S-NSSAI selected by the SMF+PGW-C is an S-NSSAI subject to NSSAA, the SMF+PGW-C may send an indicator indicating that the S-NSSAI related to the PDN connectivity (PDU session) is subject to NSSAA to the UDM+HSS. The UDM+HSS may store the PDN connectivity (PDU session) context received from the SMF+PGW-C. That is, by using the PDN connectivity (PDU session) context, the UDM+HSS may store the S-NSSAI selected by the SMF+PGW-C and an indicator indicating that the selected S-NSSAI is subject to NSSAA.

[0104] When there is no S-NSSAI selectable by the SMF+PGW-C, the SMF+PGW-C may select a default slice (default S-NSSAI) or no S-NSSAI at all.

[0105] When the SMF+PGW-C does not select S-NSSAI at all, the SMF+PGW-C may reject the request for PDN connectivity requested in operation 503. A PDN connectivity rejection message may be sent to the terminal by performing operations 507, 508, 509, and 510. Therefore, the terminal may not be able to establish PDN connectivity. The name of the message is not limited to the above example.

[0106] Optionally, when SMF+PGW-C does not select S-NSSAI at all, SMF+PGW-C may accept PDN connectivity without S-NSSAI. A PDN connectivity accept message may be sent to the terminal by performing operations 507, 508, 509, and 510. The PDN connectivity accept message may not include S-NSSAI.

[0107] In operation 507, the SMF+PGW-C may send a create session response message to the S-GW. The S-NSSAI selected by the SMF+PGW-C in operation 506 may be included in the create session response message in the form of a protocol configuration option (PCO). Optionally, when the SMF+PGW-C does not select the S-NSSAI in operation 506, no S-NSSAI may be included in the create session response message. The name of the message is not limited to the above example.

[0108] In operation 508, the S-GW may send a create session response message to the MME. The create session response message may include the slice information (S-NSSAI) received in operation 507.

[0109] In operation 509, the MME may send a bearer setup request message or a "downlink NAS transmission with PDN connectivity accept" message to the E-UTRA base station. The bearer setup request message or the "downlink NAS transmission with PDN connectivity accept" message sent by the MME to the E-UTRA base station may include the slice information (S-NSSAI) included in the create session response message received in operation 508. The name of the message is not limited to the above example.

[0110] In operation 510, the E-UTRA base station may send an RRC connection reconfiguration message or an RRC direct transfer message to the terminal. The RRC connection reconfiguration message or the RRC direct transfer message may include the slice information (S-NSSAI) included in the message received in operation 509. The name of the message is not limited to the above example.

[0111] The terminal that has received the RRC connection reconfiguration message or the RRC direct transfer message may store the S-NSSAI as the slice information included in the RRC connection reconfiguration message or the RRC direct transfer message and the PLMN ID using the S-NSSAI. The slice information may be included in the message in the form of PCO.

[0112] Example 3

[0113] According to an embodiment of the present disclosure, as described with respect to Embodiment 2, the terminal may access the EPC to establish PDN connectivity, and may receive S-NSSAI information related to the PDN connectivity from the SMF+PGW-C.

[0114] The terminal may move from the EPC network to the 5GC network, and here, the terminal may provide the 5GC network with information related to the PDN connectivity established on the EPC network.

[0115] When the terminal receives an indicator indicating that the S-NSSAI is subject to NSSAA in addition to the S-NSSAI in Example 2, the terminal can move to the 5GC and include at least one of the S-NSSAI received in Example 2 or the indicator indicating that the S-NSSAI is subject to NSSAA in the registration request message to be sent to the AMF, and send the registration request message.

[0116] In addition, according to an embodiment of the present disclosure, the terminal may include information about a certificate of NSSAA related to S-NSSAI stored in the terminal (an association between S-NSSAI and a corresponding certificate for network slice-specific authentication and authorization) in a registration request message and send it to the AMF.

[0117] In addition, according to an embodiment of the present disclosure, the terminal may include certificate information of NSSAA related to S-NSSAI in another message other than the registration request message and send it to the AMF.

[0118] When the terminal does not receive the S-NSSAI in Example 2, the terminal can move to the 5GC and include at least one of a PDU session ID related to the PDN connectivity established in the process of Example 2, an indicator indicating that there is no S-NSSAI associated with the PDU session or an indicator indicating that the S-NSSAI associated with the PDU session is empty, and an indicator indicating that the PDU session is subject to NSSAA in the registration request message to be sent to the AMF.

[0119] According to an embodiment of the present disclosure, the AMF that has received the registration request message may trigger the NSSAA procedure of the S-NSSAI.

[0120] For example, when EAP related information is not included in the UE context received from the MME during the registration procedure, the AMF may trigger the NSSAA procedure for S-NSSAI.

[0121] For example, when a Registration Request message received from a terminal during a registration procedure includes an indicator indicating that the S-NSSAI is subject to NSSAA or certificate information of the S-NSSAI, the AMF may trigger NSSAA of the S-NSSAI.

[0122] For example, when the information received from the UDM during the registration process includes information indicating that the S-NSSAI is subject to NSSAA as a PDN connectivity (PDU session) context, the AMF may trigger the NSSAA process for the S-NSSAI.

[0123] Figure 6 A configuration of a terminal according to an embodiment of the present disclosure is shown.

[0124] The terminal according to an embodiment of the present disclosure may include a processor 620 that controls the overall operation of the terminal, a transceiver 600 including a transmitter and a receiver, and a memory 610. However, the terminal is not limited to the above examples and may include more than Figure 6 More or fewer components as shown.

[0125] Reference Figure 6 , the transceiver 600 may send a signal to a network entity or other terminal or receive a signal from a network entity or other terminal. The signal sent to or from the network entity may include control information and data. In addition, the transceiver 600 may receive a signal via a wireless channel and output it to the processor 620, and send a signal output from the processor 620 via a wireless channel.

[0126] Reference Figure 6 , the processor 620 can control the terminal so that the terminal performs the operation of one of the above embodiments. The processor 620, the memory 610, and the transceiver 600 are not necessarily implemented as separate modules, but can also be implemented as a single component, for example, in the form of a single chip. In addition, the processor 620 and the transceiver 600 can be electrically connected to each other. In addition, the processor 620 can be an application processor (AP), a communicator processor (CP), a circuit, a dedicated circuit, or at least one processor.

[0127] According to an embodiment of the present disclosure, the memory 610 may store data, such as basic programs, applications, setting information, etc. for terminal operation. Specifically, the memory 610 provides the stored data according to a request from the processor 620. The memory 610 may be configured in a storage medium, such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a compact disk-ROM (CD-ROM) or a digital versatile disk (DVD) or a combination thereof. In addition, the memory 610 may include a plurality of. In addition, the processor 620 may run the above-mentioned embodiment based on the program stored in the memory 610, which is designed to execute the above-mentioned embodiment of the present disclosure.

[0128] Figure 7 The configuration of the network entity according to an embodiment of the present disclosure is shown.

[0129] The network entity according to an embodiment of the present disclosure may include a processor 720 that controls the overall operation of the network entity, a transceiver 700 including a transmitter and a receiver, and a memory 710. However, the network entity is not limited to the above examples and may include more than Figure 7 More or fewer components as shown.

[0130] Reference Figure 7 , the transceiver 700 may send a signal to or receive a signal from other network entities or at least one terminal. The signal sent to or received from other network entities or at least one terminal may include control information and data.

[0131] According to an embodiment of the present disclosure, the processor 720 may control the network entity so that the network entity performs the operation of one of the above embodiments. The processor 720, the memory 710, and the transceiver 700 are not necessarily implemented as separate modules, but may also be implemented as a single component, for example, in the form of a single chip. In addition, the processor 720 and the transceiver 700 may be electrically connected to each other. In addition, the processor 720 may be an AP, a CP, a circuit, a dedicated circuit, or at least one processor.

[0132] According to an embodiment of the present disclosure, the memory 710 may store data, such as basic programs, applications, setting information, etc., for the operation of the network entity. Specifically, the memory 710 provides the stored data according to a request from the processor 720. The memory 710 may be configured in a storage medium, such as a ROM, RAM, hard disk, CD-ROM, or DVD, or a combination thereof. In addition, the memory 710 may include a plurality of. In addition, the processor 720 may run the above-mentioned embodiments based on the program stored in the memory 710, which is designed to execute the above-mentioned embodiments of the present disclosure.

[0133] It should be noted that the above-mentioned structure diagram, the diagram of the method of sending control / data signal, the diagram of the operation process and the structure diagram are not intended to limit the scope of the present disclosure. That is, all components, entities or operation steps described in the embodiments of the present disclosure should not be interpreted as necessary components for implementing the present disclosure, and by only including some components, the present disclosure can be implemented within the scope of not damaging the essence of the present disclosure. In addition, the embodiments of the present disclosure can be combined with each other as needed. For example, parts according to the method of the present disclosure can be combined with each other to enable network entities and terminal operations.

[0134] The operations of the above-mentioned base station or terminal can be implemented by including a memory device storing relevant program codes in any element of the base station or terminal device. That is, the controller of the base station or terminal device can run the above-mentioned operations by using a processor or a central processing unit (CPU) to read the program codes stored in the memory device and run them.

[0135] Various components and modules of the entities, base stations or terminal devices described herein may also be operated using hardware circuits, for example, logic circuits based on complementary metal oxide semiconductors, firmware or software and / or hardware combinations or firmware and / or software combinations embedded in machine-readable media. For example, various electrical structures and methods may be implemented using transistors, logic gates and circuits such as special semiconductors.

[0136] When implemented as software, a computer-readable storage medium storing one or more programs (e.g., software modules) may be provided. One or more programs stored in the computer-readable storage medium are configured to be executable by one or more processors in an electronic device. One or more programs include instructions that cause the electronic device to execute the method according to the embodiments of the present disclosure described in this specification or the appended claims.

[0137] The program (e.g., software module or software) may be stored in RAM, non-volatile memory including flash memory, ROM, electrically erasable programmable read-only memory (EEPROM), magnetic disk storage, CD-ROM, DVD, another type of optical storage device, or cassette tape. Alternatively, the program may be stored in a memory system that includes a combination of some or all of the above memory devices. Furthermore, each memory device may include multiple.

[0138] The program may also be stored in an attachable storage device that may be accessed via a communication network such as the Internet, an intranet, a local area network (LAN), a wireless LAN (WLAN), or a storage area network (SAN), or a combination thereof. The storage device may be connected to the apparatus for executing the embodiments of the present disclosure via an external port. Another storage device on the communication network may also be connected to the apparatus for executing the embodiments of the present disclosure.

[0139] According to the devices and methods of various embodiments of the present disclosure, a method for intercommunication between a 5G network system architecture providing a network slicing function and an EPS network system is provided, thereby effectively providing services in a mobile communication system.

[0140] In the foregoing embodiments of the present disclosure, the elements included in the present disclosure are expressed in singular or plural form according to the embodiments of the present disclosure. However, for ease of explanation, singular or plural form is appropriately selected, and the present disclosure is not limited thereto. In this way, the elements expressed in plural form may also be configured as a single element, and the elements expressed in singular form may also be configured as multiple elements.

[0141] In other words, it is obvious to those skilled in the art that other modifications based on the technical spirit of the present disclosure can be implemented. In addition, the embodiments of the present disclosure can be combined with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to enable base station and terminal operations. Although the embodiments of the present disclosure have been described based on 5G and NR systems, modified examples based on the technical spirit of the embodiments can also be implemented in other systems such as LTE, LTE-A, LTE-A-Pro systems.

[0142] While the present disclosure has been described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A method for selecting a network slice performed by a control entity, the method comprising: In response to a packet data network (PDN) connectivity request message sent by the terminal, receiving a create session request message from a serving gateway (S-GW); Sending a request message for subscriber information to a storage entity, wherein the request message includes a data type and key information of the requested subscription information, wherein the key information is a subscription permanent identifier SUPI; receiving subscription data of the terminal corresponding to the SUPI from a storage entity, wherein the subscription data includes one or more subscribed single network slice selection assistance information S-NSSAI and information indicating whether the subscribed S-NSSAI is subject to network slice specific authentication and authorization NSSAA; selecting an S-NSSAI supportable by the control entity from among the one or more subscribed S-NSSAIs, wherein the S-NSSAI is selected based on additional criteria not subject to NSSAA; as well as Sending a create session response message including the selected S-NSSAI information to the S-GW, The control entity is a combined node of a session management function SMF and a PDN gateway control PGW-C, and the storage entity is a combined node of a home subscriber server HSS and a unified data management UDM.

2. The method according to claim 1, in, The PDN connectivity request message includes information of an access point name APN requested from the terminal, and The subscription data includes a list of APNs that can be supported by the one or more subscribed S-NSSAIs, and when performing the selection, the S-NSSAI is selected to additionally support the APN requested by the terminal.

3. The method according to claim 1, wherein: When there is no S-NSSAI selectable by the control entity when performing the selection, no S-NSSAI is selected, and a rejection message rejecting the PDN connectivity request from the terminal is sent.

4. The method according to claim 3, wherein: The case where there is no S-NSSAI selectable by the control entity includes the case where all of the one or more subscribed S-NSSAIs are subject to NSSAA.

5. A control entity for selecting a network slice, the control entity comprising: Transceiver; as well as A processor is coupled to the transceiver and is configured to: In response to a packet data network (PDN) connectivity request message sent by the terminal, receiving a create session request message from a serving gateway (S-GW), Sending a request message for subscriber information to a storage entity, wherein the request message includes the data type and key information of the requested subscription information, wherein the key information is a subscription permanent identifier SUPI, receiving subscription data of the terminal corresponding to the SUPI from a storage entity, wherein the subscription data includes one or more subscribed single network slice selection assistance information S-NSSAI and information indicating whether the subscribed S-NSSAI is subject to network slice-specific authentication and authorization NSSAA, selecting an S-NSSAI supportable by the control entity from among the one or more subscribed S-NSSAIs, wherein the S-NSSAI is selected based on additional criteria not subject to NSSAA, and Sending a create session response message including the selected S-NSSAI information to the S-GW, The control entity is a combined node of a session management function SMF and a PDN gateway control PGW-C, and the storage entity is a combined node of a home subscriber server HSS and a unified data management UDM.

6. The control entity according to claim 5, in, The PDN connectivity request message includes information of an access point name APN requested from the terminal, and The subscription data includes a list of APNs that can be supported by the one or more subscribed S-NSSAIs, and when performing the selection, the S-NSSAI is selected to additionally support the APN requested by the terminal.

7. The control entity according to claim 5, wherein: When there is no S-NSSAI selectable by the control entity, the processor is further configured to not select the S-NSSAI and send a rejection message rejecting the PDN connectivity request from the terminal.

8. The control entity according to claim 7, wherein: The case where there is no S-NSSAI selectable by the control entity includes the case where all of the one or more subscribed S-NSSAIs are subject to NSSAA.

Images