Method and device for mutually exclusive access of roaming terminals to network slices in a wireless communication system

Abstract

The present disclosure relates to a communication method and system for integrating IoT technology with a 5G communication system to support a higher data transmission rate than a 4G system. The present disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.).

Description

Technical Field

[0001] The present disclosure relates to a method for providing network slicing during movement of a mobile communication terminal between mobile communication service providers in a wireless communication system. Background Art

[0002] In order to meet the growing demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called "super 4G network" communication systems or "post-LTE systems". In order to achieve higher data transmission rates, 5G communication systems are being considered for implementation in ultra-high frequency (millimeter wave (mmWave)) bands (e.g., 60GHz bands). In order to reduce the path loss of radio waves and increase the transmission distance of radio waves in ultra-high frequency bands, beamforming, massive multiple input multiple output (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are being discussed for 5G communication systems. In addition, in 5G communication systems, development of system network improvements is being carried out based on evolved small cells, advanced small cells, cloud radio access networks (cloudRANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. In addition, in the 5G system, hybrid FSK with QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) systems, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0003] On the other hand, the Internet as a human-centered connection network in which people generate and consume information is now evolving into an Internet of Things (IoT) network in which distributed entities (such as things) exchange and process information without human intervention. Internet of Everything (IoE) technology that combines IoT technology and big data processing technology by connecting with cloud servers has emerged. For IoT implementation, technical elements such as "sensing technology", "wired / wireless communication and network facilities", "service interface technology", and "security technology" are required; therefore, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine type communication (MTC) for connection between things have recently been studied. Such an IoT environment can provide intelligent Internet technology (IT) services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services, through the integration and combination between existing information technology (IT) and various industrial applications.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M) communications, and machine type communications (MTC) corresponding to 5G communication technologies can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RANs) as the above-mentioned big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology. Summary of the invention

[0005] Technical issues

[0006] An aspect of the present disclosure provides an apparatus and method for efficiently providing mobile communication services based on network slicing even when a mobile communication terminal in a mobile communication system moves to a mobile communication service provider that provides network slicing.

[0007] Solution to the problem

[0008] In one aspect of the present disclosure for solving the above-mentioned problem, a method performed by an apparatus for performing an access management function (AMF) in a wireless communication system includes: receiving a registration request message sent from a terminal through a base station; identifying subscriber information about the terminal; determining network slice configuration information based on the subscriber information; and sending a registration response message including the network slice configuration information, wherein the network slice configuration information includes a network slice identifier and a slice group identifier for the terminal.

[0009] In another aspect of the present disclosure to solve the above-mentioned problem, a method performed by a terminal in a wireless communication system includes: sending a registration request message to a base station; and receiving a registration response message including network slice configuration information determined based on subscriber information about the terminal, wherein the network slice configuration information includes a network slice identifier and a slice group identifier for the terminal.

[0010] In another aspect of the present disclosure to solve the above-mentioned problem, an apparatus for performing an access management function (AMF) in a wireless communication system includes: a transceiver; and a controller, configured to: receive a registration request message sent from a terminal through a base station, identify subscriber information about the terminal, determine network slice configuration information based on the subscriber information, and send a registration response message including the network slice configuration information, wherein the network slice configuration information includes a network slice identifier and a slice group identifier for the terminal.

[0011] In another aspect of the present disclosure to solve the above-mentioned problem, a terminal in a wireless communication system includes: a transceiver; and a controller, configured to: send a registration request message to a base station, and receive a registration response message including network slice configuration information determined based on subscriber information about the terminal, wherein the network slice configuration information includes a network slice identifier and a slice group identifier for the terminal.

[0012] Advantageous Effects of the Invention

[0013] According to an embodiment of the present disclosure, even in a mobile communication system, when a mobile communication terminal moves to a mobile communication service provider that provides network slicing, the terminal can access the mobile communication system of the corresponding service provider, and the corresponding mobile communication system can effectively provide mobile communication services based on the network slice subscribed by the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 A 5G network slicing structure according to an embodiment of the present disclosure is shown.

[0015] Figure 2 A method for configuring information related to network slicing according to an embodiment of the present disclosure is shown.

[0016] Figure 3 The network registration process of a terminal according to an embodiment of the present disclosure is shown.

[0017] Figure 4 The network registration process of a terminal according to an embodiment of the present disclosure is shown.

[0018] Figure 5 The network registration process of a terminal according to an embodiment of the present disclosure is shown.

[0019] Figure 6 A network registration process of a terminal according to another embodiment of the present disclosure is shown.

[0020] Figure 7 is a diagram showing a configuration of a terminal according to the present disclosure.

[0021] Figure 8 is a diagram showing a configuration of a network entity according to the present disclosure. DETAILED DESCRIPTION

[0022] Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. When describing the present disclosure, if it is determined that the detailed description of the relevant known functions or configurations obscures the present disclosure with unnecessary details, it will be omitted. For the same reason, in the accompanying drawings, the sizes and relative sizes of some components may be enlarged, omitted or briefly shown. In addition, the sizes of the various components do not fully reflect their actual sizes. In the accompanying drawings, the same reference numerals are used for the same or corresponding elements in each drawing.

[0023] In addition, the terms described later are terms defined in consideration of their functions in the present disclosure, but may differ according to the intention or custom of a user or operator. Therefore, they should be defined based on the contents of the entire specification of the present disclosure.

[0024] By referring to the embodiments that will be described in detail with reference to the accompanying drawings, various aspects and features of the present disclosure and methods for implementing these aspects and features will become apparent. However, the present disclosure is not limited to the embodiments disclosed below and can be implemented in various forms. The contents defined in the specification, such as detailed construction and elements, are only specific details provided to help ordinary technicians in the field fully understand the present disclosure, and the present disclosure is defined only within the scope of the attached claims. Throughout the description of the present disclosure, the same reference numerals are used for the same elements in the various drawings.

[0025] In this case, it will be understood that each block of the flowchart illustration and the combination of blocks in the flowchart illustration can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions specified in one or more blocks of the flowchart. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to act in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article including an instruction device, which implements the functions specified in one or more blocks of the flowchart. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps performed on the computer or other programmable data processing device produce a computer-implemented process, so that the instructions executed on the computer or other programmable data processing device provide steps for implementing the functions specified in one or more blocks of the flowchart.

[0026] In addition, each box of the flowchart diagram may represent a module, segment or portion of code, which includes one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the box may not occur in order. For example, depending on the functions involved, two boxes shown in succession may actually be executed substantially simultaneously, or sometimes these boxes may be executed in an inverted order.

[0027] In this case, the term "~ unit" used in the embodiment refers to but is not limited to software or hardware components that perform certain tasks, such as FPGA or ASIC. However, "~ unit" does not mean to be limited to software or hardware. The term "~ unit" can be advantageously configured to reside on an addressable storage medium and configured to execute on one or more processors. Therefore, "~ unit" can include components (such as software components), object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and variables by way of example. The functions provided in components and "~ units" can be combined into fewer components and "~ units", or further separated into additional components and "~ units". In addition, components and "~ units" can be implemented as operating one or more CPUs in a device or a security multimedia card.

[0028] In the following, a base station is a subject that performs resource allocation on a terminal, and it may be at least one of a node B, a base station (BS), an eNode B (eNB), a gNode B (gNB), a radio access unit, a base station controller, or a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system that can perform a communication function. In addition, embodiments of the present disclosure may be applied to other communication systems having a technical background or channel type similar to the embodiments of the present disclosure to be described below. In addition, embodiments of the present disclosure may also be applied to other communication systems by partially modifying them within the scope of not greatly departing from the scope of the present disclosure as determined by those skilled in the art.

[0029] In the following description, for the convenience of description, terms for identifying access nodes, terms for indicating network entities, terms for indicating messages, terms for indicating interfaces between network entities, and terms for indicating various types of identity information have been exemplified. Therefore, the present disclosure is not limited to the terms described later, and other terms may be used to indicate objects having equivalent technical meanings.

[0030] For ease of explanation, in the present disclosure, terms and names defined in the standards of the 5G system are used. However, the present disclosure is not limited to these terms and names and can be equally applied to systems that comply with other standards.

[0031] In describing the embodiments of the present disclosure in detail, although the communication standards defined in 3GPP will be the main target, the main subject matter of the present disclosure will be able to be applied even to other communication systems with similar technical backgrounds by slightly modifying them within the scope that does not deviate greatly from the scope of the present disclosure at the judgment of technicians in the field to which the present disclosure belongs.

[0032] When describing the embodiments of the present disclosure, slices, services, network slices, network services, application slices, and application services may be used interchangeably.

[0033] So far, communication systems have been designed independently of the applications provided on the communication systems. After first accessing the communication system, services can be provided to users by selecting the application they intend to use. This communication technology has been developed in the following way: by developing technologies with network function virtualization (NFV) and software defined networking (SDN) to migrate each application in a huge network to configure network slices optimized for application characteristics.

[0034] A network slice consists of an end-to-end (E2E) logical network, which includes a terminal and a corresponding node (relative terminal or relative application server). Services can be provided to users by accessing a dedicated network slice in the application. In other words, the user terminal can access one or more network slices at the same time.

[0035] 3GPP, which is responsible for the standardization of mobile communication technology, has completed the 5G Phase I standard in Release 15 (Rel-15), and 5G Phase I includes network slicing functions. In Release 16 (Rel-16), the network slicing Phase II standard is underway.

[0036] Hereinafter, in the present disclosure, a slice structure is defined which cannot be provided with the following network slices (i.e., mutually exclusive): which can be provided with each other in the case where several network slices are provided in the slice structure of the 5G-based network. In addition, in the present disclosure, a method is defined in which terminal configuration (UE configuration) information of mutually exclusive slice structures is provided to a terminal. In addition, in the present disclosure, a registration process of a terminal based on the terminal configuration information is defined. In addition, in the present disclosure, a process for updating terminal configuration information is defined.

[0037] In addition, the present disclosure may provide a method for processing a control signal in a wireless communication system, the method comprising: receiving a first control signal sent from a network entity; processing the received first control signal; and sending a second control signal generated based on the first control signal processing to the network entity, or sending the second control signal generated based on the first control signal processing to another network entity.

[0038] A mobile communication service provider may provide various services in a mobile communication network, and various services need to meet different service requirements (e.g., latency, communication range, data rate, bandwidth, reliability, etc.). The mobile communication service provider may allocate network resources suitable for the corresponding service for each slice or for each specific slice group. Network resources may refer to logical resources or radio resource allocations provided by a network function (NF) or a device that executes an NF.

[0039] The mobile communication service provider may sign a contract with the service provider and may configure network slices for services provided by a specific service provider. In the case where the mobile communication service provider configures the network slices, the specific network slices may be provided together or mutually exclusively through a contract between the mobile communication service provider and the service provider, through a policy of the mobile communication service provider, or through government regulations.

[0040] Figure 1 A 5G network slicing structure according to an embodiment of the present disclosure is shown.

[0041] As an identifier for distinguishing network slices, for example, Single Network Slice Selection Assistance Information (S-NSSAI) may be used.

[0042] Reference Figure 1 , a case where three network slices S-NSSAI#1 160, S-NSSAI#2 165, and S-NSSAI#3 170 are provided in a network of a mobile communication service provider will be described as an example. A network slice may be composed of network functions (NFs) necessary to provide services supported by the network slice.

[0043] The entities that perform network functions may be core network entities (e.g., access management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), etc.) and wireless network entities (e.g., base station, radio access network (RAN), access network (AN), gNodeB (gNB), eNodeB (eNB), etc.). Hereinafter, in the present disclosure, base station may be used interchangeably with RAN. In the present disclosure, for the sake of convenience, a device or entity that performs an access management function (AMF) may be represented as an AMF. In addition, in the present disclosure, for the sake of convenience, a device or entity that performs a session management function (SMF) may be represented as an SMF. In addition, for the sake of convenience, a device or entity that performs a user plane function (UPF) may be represented as an UPF. In addition, in the present disclosure, for the sake of convenience, a device or entity that performs a policy control function (PCF) may be represented as a PCF. In addition, for the sake of convenience, the entity that performs the function may be abbreviated and described as the function name.

[0044] Reference Figure 1 , specific network slices can share specific network functions. For example, S-NSSAI#1 160 and S-NSSAI#2 165 can share AMF 120, and NFs (SMFs 125 and 135 and UPFs 130 and 140) dedicated to each network slice can be selected. In addition, referring to Figure 1 , a specific network slice may consist only of NFs dedicated to the corresponding network slice. For example, S-NSSAI #3 170 may consist only of NFs 145, 150, and 155 belonging only to S-NSSAI #3, without any NFs shared with other network slices.

[0045] Reference Figure 1, network slices that can share a specific network function can be bundled and classified into a slice group. For example, S-NSSAI#1 160 and S-NSSAI#2 165 that share AMF 120 can be indicated as slice group 1 175. S-NSSAI#3 170 that does not share a network function with other network slices can be indicated as slice group 2 180 as another slice group.

[0046] In the AMF according to an embodiment of the present disclosure, slice information (S-NSSAI) that can be provided by the AMF and slice group information (slice group ID) including the AMF can be configured and stored in the AMF. For example, the AMF 120 can store information indicating that the slices that can be provided by the AMF 120 are S-NSSAI #1 160 and S-NSSAI #2 165, and the slice group including the AMF 145 is the slice group 1175.

[0047] In addition, refer to Figure 1 , the radio network resources RAN can be shared by several network slices. For example, the base station 115 can be connected to the AMF 120 supporting S-NSSAI#1 160 and S-NSSAI#2 165 and the AMF 145 supporting S-NSSAI#3 170.

[0048] Figure 2 A method for configuring information related to network slicing according to an embodiment of the present disclosure is shown.

[0049] According to this embodiment, configuration information for a terminal supporting a function of mutually exclusive access to network slices using a network slice provided by a mobile communication service provider may be stored in the terminal or may be sent to the terminal. The configuration information related to the network slice may be referred to as a configured NSSAI.

[0050] According to an embodiment of the present disclosure, the configuration information related to network slicing stored in the terminal can follow the following format.

[0051] [Table 1] List of SG IDs and subscribed S-NSSAIs

[0052] S-NSSAI SG ID S-NSSAI 1 SG ID 1 S-NSSAI 2 SG ID 2 S-NSSAI 3

[0053] For example, in Figure 1 In the case where the terminal 110 shown in can use three network slices S-NSSAI#1, S-NSSAI#2 and S-NSSAI#3, the terminal configuration information can be expressed as follows.

[0054] [Table 2]

[0055] S-NSSAI SG ID S-NSSAI 1 SG ID 1 S-NSSAI 2 SG ID 1 S-NSSAI 3 SD ID 2

[0056] As another embodiment of the present disclosure, in the case where a certain network slice does not belong to only one mutually exclusive network slice but can be used with other network slices, the SG ID value of the corresponding network slice may be configured as a specific value indicating that the network slice can coexist with other network slices. Figure 2 As shown, if S-NSSAI 4 can coexist with other network slices, the SG ID value can be set to "0" to indicate this. In this case, S-NSSAI 4 can be used with S-NSSAI 1 and S-NSSAI 2 belonging to SG ID 1, or can be used with S-NSSAI 3 belonging to SG ID 2.

[0057] The terminal may request the network to use a network slice, and in this case, the network slice information that may be requested by the terminal for use may include only the network slice information that may coexist as described above. For example, only S-NSSAI 1 and S-NSSAI 2, or S-NSSAI 3 and S-NSSAI 4 may be requested at the same time.

[0058] Figure 3 The network registration process of a terminal according to an embodiment of the present disclosure is shown.

[0059] In the embodiments of the present disclosure, a case where a terminal does not have configured NSSAI information will be described as an example. Specifically, a case where a terminal does not have configured NSSAI information available for a corresponding service provider (i.e., a case where a terminal according to the present disclosure accesses a mobile communication network subscribed by the terminal), a case where a terminal does not have configured NSSAI information, or a case where a terminal accesses a mobile communication network that is not a mobile communication network subscribed by the terminal but belongs to another service provider will be described as an example.

[0060] In this case, the terminal can send a registration request message that does not include request information for the network slice (step 2).

[0061] The base station that receives the registration request message in step 2 can identify whether the terminal is a roaming user subscribed to another mobile communication service provider based on the ID information of the terminal included in the registration request message received from the terminal or the information indicating whether the terminal is a roaming user sent together with the registration request message (step 3).

[0062] In this case, the ID information of the terminal may be a value corresponding to a temporary ID (e.g., a 5G Global Unique Temporary Identifier (5G-GUTI), etc.), or a unique ID including information about the mobile communication network to which the terminal subscribes (e.g., a Subscription Permanent Identifier (SUPI), etc.) value. In addition, the information that may indicate whether the terminal is a roaming user may be an identifier indicating roaming or an S-NSSAI value for roaming (defined for roaming).

[0063] In addition, the base station can select a dedicated AMF for roaming terminals or a default AMF for general terminals based on the identification result (step 4).

[0064] If the terminal is identified as a roaming terminal, the base station may transmit to an AMF (dedicated AMF) designated to process a connection request message of a roaming terminal (step 5).

[0065] In this case, the dedicated AMF may be an AMF that can be configured to be connected not only to all network devices or some network devices (e.g., AMF) included in the corresponding network slice but also to all network devices or some network devices (e.g., AMF) included in a certain network slice.

[0066] If the terminal is not identified as a roaming terminal, the base station transmits the registration request message received from the terminal to a predetermined default AMF. In this case, the dedicated AMF may be an AMF included in a specific network slice like a dedicated AMF and configured to be connected not only to all network devices or some network devices (such as AMF) included in the corresponding network slice but also to all network devices or some network devices (such as AMF) included in a certain network slice.

[0067] According to the operation policy of the mobile communication network service provider, the dedicated AMF and the default AMF can exist independently or can be implemented as one network device.

[0068] The AMF that receives the registration request message of the terminal from the base station in step 5 may request the subscription information of the terminal from the user data management (UDM) of the mobile communication network to which the terminal subscribes, and may obtain the subscription information of the terminal from the UDM (step 6).

[0069] The subscription information of the terminal may include the network slice information subscribed by the terminal. The network slice information subscribed by the terminal may include the S-NSSAI information and slice group ID information available to the terminal. The AMF may perform a separate authentication process with the terminal before or after receiving the subscription information from the UDM according to the situation.

[0070] If the AMF is the default AMF, the AMF can receive the network slice information of the terminal from the UDM in step 6, and then use the predetermined information in the default AMF in step 7 to configure or update the configured NSSAI based on all network slice information and slice group ID information subscribed by the terminal (not limited to a specific slice group).

[0071] As another embodiment of the present disclosure, AMF may receive the network slice information of the terminal from UDM in step 6, and then may use NSSF in step 7 to configure or update the configured NSSAI based on all network slice information and slice group ID information subscribed by the terminal (not limited to a specific slice group).

[0072] In addition, when configuring the configured NSSAI, the AMF can additionally configure network slice information (allowed NSSAI) that the terminal can use directly in the mobile communication network or by using the NSSF.

[0073] If the AMF has identified that the terminal is a roaming terminal, the AMF may receive the network slice information of the terminal from the UDM in step 6, and then may perform mapping from the network slice information and slice group ID information subscribed by the terminal to the network slice information and slice group ID used in the mobile communication network to which the AMF belongs, respectively, based on predetermined information. That is, the AMF may identify the network slice information and slice group ID information of the mobile communication network to which the dedicated AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, based on predetermined information, and may be notified of the mapping related information of the network slice information and slice group information. If the network slice information and slice group ID subscribed by the terminal are intended to be used, the terminal may determine the network slice information and slice group ID available in the mobile communication network to which the AMF belongs through the connection information notified by the AMF, and may use the corresponding network slice information and slice group ID. That is, in the case where the mobile communication network subscribed by the terminal and the mobile communication network accessed by the terminal are different from each other due to the movement of the terminal (e.g., roaming), the network slices allocated in the mobile communication network subscribed by the terminal and the network slices of the mobile communication network to which the AMF belongs are not identical to each other, and therefore, the AMF may send the mapping information and the terminal may use the mapping information.

[0074] As another embodiment, in step 7, AMF may use NSSF to obtain mapping information between the network slice information and slice group ID information subscribed by the terminal and the network slice information and slice group ID information used in the mobile communication network to which AMF belongs. That is, AMF may use NSSF to identify the network slice information and slice group ID of the mobile communication network to which AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, and may be notified of the mapping-related information between the network slice information and the slice group ID.

[0075] In addition, based on the mapping information, the AMF may configure mapping information between the configured NSSAI including the slice information and slice group ID available in the mobile communication network to which the AMF belongs and the network slice information and slice group ID subscribed by the terminal. In addition, the AMF may further configure mapping information between the network slice information (allowed NSSAI) available to the terminal in the mobile communication network to which the terminal currently requests subscription and the network slice information available in the mobile communication network subscribed by the terminal.

[0076] If the AMF is a dedicated AMF, the AMF may receive the network slice information of the terminal from the UDM in step 6, and then may use the predetermined information to perform mapping from the network slice information and slice group ID information subscribed by the terminal to the network slice information and slice group ID used in the mobile communication network to which the dedicated AMF belongs in step 7. That is, the AMF may identify the network slice information and slice group ID information of the mobile communication network to which the dedicated AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, based on the predetermined information, and may be notified of the mapping information of the network slice information and slice group ID.

[0077] As another embodiment, in step 7, AMF may use NSSF to obtain mapping information between the network slice information and slice group ID information subscribed by the terminal and the network slice information and slice group ID information used in the mobile communication network to which AMF belongs. That is, AMF may use NSSF to identify the network slice information and slice group ID of the mobile communication network to which AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, and may be notified of the mapping-related information between the network slice information and the slice group ID.

[0078] In addition, based on the mapping information, the AMF may configure mapping information between the configured NSSAI including the slice information and slice group ID available in the mobile communication network to which the AMF belongs and the network slice information and slice group ID subscribed by the terminal. In addition, the AMF may additionally configure mapping information between the network slice information (allowed NSSAI) available to the terminal in the mobile communication network to which the terminal currently requests subscription and the network slice information available in the mobile communication network subscribed by the terminal.

[0079] In this embodiment, the AMF may include the configured NSSAI and mapping information configured in step 7, and at least one of the allowed NSSAI and mapping information additionally configured in the registration acceptance message in step 8, and the registration acceptance message may be sent to the base station through the AMF.

[0080] In step 9, the base station that has received the registration response may send the registration response to the terminal.

[0081] Based on the allowed NSSAI and mapping information received together, the terminal that receives the registration response in step 9 can perform the PDU session process required for the subsequent necessary service, or can configure the requested NSSAI by reselecting the network slice requiring the service based on the received configured NSSAI and mapping information, and can resend the registration request including the requested NSSAI.

[0082] Figure 4 A network registration process of a terminal according to another embodiment of the present disclosure is shown.

[0083] In the embodiments of the present disclosure, a case where the terminal does not have configured NSSAI information will be described as an example. Specifically, a case where the terminal does not have configured NSSAI information available for the corresponding service provider (i.e., a case where the terminal according to the present disclosure accesses a mobile communication network subscribed by the terminal), a case where the terminal does not have configured NSSAI information, or a case where the terminal accesses a mobile communication network that is not a mobile communication network subscribed by the terminal but belongs to another service provider will be described as an example.

[0084] In this case, the terminal can send a registration request message that does not include request information for the network slice (step 2).

[0085] The base station that receives the registration request message in step 2 can use the ID information of the terminal included in the registration request message received from the terminal or the information indicating whether the terminal is a roaming user sent together with the registration request message to identify whether the terminal is a roaming user subscribed to another mobile communication service provider (step 3).

[0086] In this case, the ID information of the terminal may be a value corresponding to a temporary ID allocated from a previous mobile communication network, or a unique ID value including information about a mobile communication network subscribed by the terminal. The details are the same as above, and thus will be omitted hereinafter.

[0087] In addition, the base station can select a dedicated AMF for the roaming terminal or a default AMF for the general terminal based on the identification result (step 4).

[0088] If it is identified that the terminal is a roaming terminal, the base station may transmit to an AMF (dedicated AMF) designated to process a connection request message of a roaming terminal (step 5).

[0089] In this case, the dedicated AMF may be an AMF that can be configured to be connected not only to all network devices or certain network devices (e.g., AMF) included in the corresponding network slice but also to all network devices or certain network devices (e.g., AMF) included in a certain network slice.

[0090] If the terminal is not identified as a roaming terminal, the base station transmits the registration request message received from the terminal to a predetermined default AMF. In this case, the default AMF may be an AMF that is included in a specific network slice (such as a dedicated AMF), and that can be configured to be connected not only to all network devices or some network devices (such as AMF) included in the corresponding network slice, but also to all network devices or some network devices (such as AMF) included in a certain network slice.

[0091] The AMF that receives the registration request message of the terminal from the base station in step 5 may request the subscription information of the terminal from the UDM of the mobile communication network to which the terminal subscribes, and may acquire the subscription information of the terminal from the UDM (step 6).

[0092] The subscription information of the terminal may include the network slice information subscribed by the terminal. The network slice information subscribed by the terminal may include the S-NSSAI information and slice group ID information available to the terminal. The AMF may perform a separate authentication process with the terminal before or after receiving the subscription information from the UDM according to the situation.

[0093] If the AMF is the default AMF, the AMF may receive the network slice information of the terminal from the UDM in step 6, and may then use the predetermined information in step 7 to configure or update the configured NSSAI based on all network slice information and slice group ID information subscribed by the terminal (not limited to a specific slice group).

[0094] As another embodiment of the present disclosure, AMF may receive the network slice information of the terminal from UDM in step 6, and may then use NSSF in step 7 to configure or update the configured NSSI based on all network slice information and slice group ID information subscribed by the terminal (not limited to a specific slice group).

[0095] In addition, when configuring the configured NSSAI, the AMF can additionally configure network slice information (allowed NSSAI) that the terminal can use directly in the mobile communication network or by using the NSSF.

[0096] If the AMF has identified that the terminal is a roaming terminal, the AMF may receive the network slice information of the terminal from the UDM in step 6, and may then perform mapping from the network slice information and slice group ID information subscribed by the terminal to the network slice information and slice group ID used in the mobile communication network to which the AMF belongs, respectively, based on predetermined information. That is, the AMF may identify the network slice information and slice group ID information of the mobile communication network to which the dedicated AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, based on predetermined information, and may be notified of information about the mapping relationship between the network slice information and the slice group information. If the network slice information and slice group ID subscribed by the terminal are to be used, the terminal may determine the network slice information and slice group ID available in the mobile communication network to which the AMF belongs through the connection information notified by the AMF, and may use the corresponding network slice information and slice group ID.

[0097] As another embodiment, in step 7, AMF may use NSSF to obtain mapping information between the network slice information and slice group ID information subscribed by the terminal and the network slice information and slice group ID information used in the mobile communication network to which AMF belongs. That is, AMF may use NSSF to identify the network slice information and slice group ID of the mobile communication network to which AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, and may be notified of the mapping-related information between the network slice information and the slice group ID.

[0098] In addition, based on the mapping information, the AMF may configure the mapping information between the configured NSSAI including the slice information and slice group ID available in the mobile communication network to which the AMF belongs and the network slice information and slice group ID subscribed by the terminal. In addition, the AMF may additionally configure the mapping information between the network slice information (allowed NSSAI) available to the terminal in the mobile communication network to which the terminal currently requests to subscribe and the network slice information available in the mobile communication network subscribed by the terminal.

[0099] If the AMF is a dedicated AMF, the AMF may receive the network slice information of the terminal from the UDM in step 6, and then may use the predetermined information to perform mapping from the network slice information and slice group ID information subscribed by the terminal to the network slice information and slice group ID used in the mobile communication network to which the dedicated AMF belongs in step 7. That is, the AMF may identify the network slice information and slice group ID of the mobile communication network to which the dedicated AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, based on the predetermined information, and may be notified of the mapping information of the network slice information and slice group ID.

[0100] As another embodiment, in step 7, AMF may use NSSF to obtain mapping information between the network slice information and slice group ID information subscribed by the terminal and the network slice information and slice group ID information used in the mobile communication network to which AMF belongs. That is, AMF may use NSSF to identify the network slice information and slice group ID of the mobile communication network to which AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, and may be notified of the mapping-related information between the network slice information and the slice group ID.

[0101] In addition, based on the mapping information, the AMF may configure the mapping information for notifying the connection between the configured NSSAI and slice information used in the mobile communication network and the mobile communication network subscribed by the terminal. In addition, the AMF may additionally configure the mapping information between the network slice information (allowed NSSAI) that the terminal can use in the mobile communication network to which the terminal currently requests to subscribe and the network slice information that can be used in the mobile communication network to which the terminal subscribes.

[0102] The AMF may determine a new AMF (AMF_2) suitable for serving the network slice indicated as the allowed NSSAI based on the configured NSSAI configured in step 7 and the additionally configured allowed NSSAI (step 8).

[0103] In order to determine the new AMF (AMF_2), the AMF can obtain the new AMF information by using predetermined information or by requesting from the NSSF.

[0104] In step 9, the AMF transmits terminal information including at least one of the following to AM_2: a registration request received from the terminal, configured NSSAI and mapping information configured for the terminal, and allowed NSSAI and mapping information and information about the address of the base station that has transmitted the request of the terminal.

[0105] In step 10, as a response to the registration request of the terminal received from the AMF, AMF_2 transmits a registration response message to the base station. In this case, the registration response includes at least one of the following: configured NSSAI and mapping information, or allowed NSSAI and mapping information.

[0106] If necessary, AMF_2 may perform the process of configuring a connection to the base station before sending the Registration Response.

[0107] In step 11, the base station sends the registration response received in step 10 to the terminal.

[0108] In step 11, based on the received allowed NSSAI and mapping information, the terminal that has received the registration acceptance can perform the PDU session process required for the subsequent necessary services, or can configure the requested NSSAI by reselecting the network slice requiring the service based on the received configured NSSAI and mapping information, and can resend the registration request including the requested NSSAI.

[0109] Figure 5 The network registration process of a terminal according to another embodiment of the present disclosure is shown.

[0110] In the embodiments of the present disclosure, a case where the terminal does not have configured NSSAI information will be described as an example. Specifically, a case where the terminal does not have configured NSSAI information available for the corresponding service provider (i.e., a case where the terminal according to the present disclosure accesses a mobile communication network subscribed by the terminal), a case where the terminal does not have configured NSSAI information, or a case where the terminal accesses a mobile communication network that is not a mobile communication network subscribed by the terminal but belongs to another service provider will be described as an example.

[0111] In this case, the terminal can send a registration request message that does not include request information for the network slice (step 2).

[0112] The base station that receives the registration request message in step 2 can use the ID information of the terminal included in the registration request message received from the terminal or the information indicating whether the terminal is a roaming user sent together with the registration request message to identify whether the terminal is a roaming user subscribed to another mobile communication service provider (step 3).

[0113] In this case, the ID information of the terminal may be a value corresponding to a temporary ID allocated from a previous mobile communication network, or a unique ID value including information on a mobile communication network to which the terminal subscribes.

[0114] In addition, the base station can select a dedicated AMF for the roaming terminal or a default AMF for the general terminal based on the identification result (step 4).

[0115] If it is identified that the terminal is a roaming terminal, the base station may transmit to an AMF (dedicated AMF) designated to process a connection request message of a roaming terminal (step 5).

[0116] In this case, the dedicated AMF may be an AMF that can be configured to be connected not only to all network devices or certain network devices (e.g., AMF) included in the corresponding network slice but also to all network devices or certain network devices (e.g., AMF) included in a certain network slice.

[0117] If the terminal is not identified as a roaming terminal, the base station transmits the registration request message received from the terminal to a predetermined default AMF. In this case, the default AMF may be an AMF that is included in a specific network slice (such as a dedicated AMF), and that can be configured to be connected not only to all network devices or some network devices (such as AMF) included in the corresponding network slice, but also to all network devices or some network devices (such as AMF) included in a certain network slice.

[0118] The AMF that receives the registration request message of the terminal from the base station in step 5 may request the subscription information of the terminal from the UDM of the mobile communication network to which the terminal subscribes, and may acquire the subscription information of the terminal from the UDM (step 6).

[0119] The subscription information of the terminal may include the network slice information subscribed by the terminal. The network slice information subscribed by the terminal may include the S-NSSAI information and slice group ID information available to the terminal. The AMF may perform a separate authentication process with the terminal before or after receiving the subscription information from the UDM according to the situation.

[0120] If the AMF is the default AMF, the AMF may receive the network slice information of the terminal from the UDM in step 6, and may then use the predetermined information in step 7 to configure or update the configured NSSAI based on all network slice information and slice group ID information subscribed by the terminal (not limited to a specific slice group).

[0121] As another embodiment of the present disclosure, AMF may receive the network slice information of the terminal from UDM in step 6, and may then use NSSF in step 7 to configure or update the configured NSSI based on all network slice information and slice group ID information subscribed by the terminal (not limited to a specific slice group).

[0122] In addition, when configuring the configured NSSAI, the AMF can additionally configure network slice information (allowed NSSAI) that the terminal can use directly in the mobile communication network or by using the NSSF.

[0123] If the AMF has identified that the terminal is a roaming terminal, the AMF may receive the network slice information of the terminal from the UDM in step 6, and may then perform mapping from the network slice information and slice group ID information subscribed by the terminal to the network slice information and slice group ID used in the mobile communication network to which the AMF belongs, respectively, based on predetermined information. That is, the AMF may identify the network slice information and slice group ID information of the mobile communication network to which the dedicated AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, based on predetermined information, and may notify information about the mapping relationship between the network slice information and the slice group information. If the network slice information and slice group ID subscribed by the terminal are to be used, the terminal may determine the network slice information and slice group ID available in the mobile communication network to which the AMF belongs through the connection information notified by the AMF, and may use the corresponding network slice information and slice group ID.

[0124] As another embodiment, in step 7, AMF may use NSSF to obtain mapping information between the network slice information and slice group ID information subscribed by the terminal and the network slice information and slice group ID information used in the mobile communication network to which AMF belongs. That is, AMF may use NSSF to identify the network slice information and slice group ID of the mobile communication network to which AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, and may be notified of the mapping-related information between the network slice information and the slice group ID.

[0125] In addition, based on the mapping information, the AMF may configure the mapping information between the configured NSSAI including the slice information and slice group ID available in the mobile communication network to which the AMF belongs and the network slice information and slice group ID subscribed by the terminal. In addition, the AMF may additionally configure the mapping information between the network slice information (allowed NSSAI) available to the terminal in the mobile communication network to which the terminal currently requests to subscribe and the network slice information available in the mobile communication network subscribed by the terminal.

[0126] If the AMF is a dedicated AMF, the AMF may receive the network slice information of the terminal from the UDM in step 6, and then may use the predetermined information to perform mapping from the network slice information and slice group ID information subscribed by the terminal to the network slice information and slice group ID used in the mobile communication network to which the dedicated AMF belongs in step 7. That is, the AMF may identify the network slice information and slice group ID of the mobile communication network to which the dedicated AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, based on the predetermined information, and may notify the mapping information of the network slice information and slice group ID.

[0127] As another embodiment, in step 7, AMF may use NSSF to obtain mapping information between the network slice information and slice group ID information subscribed by the terminal and the network slice information and slice group ID information used in the mobile communication network to which AMF belongs. In addition, based on the mapping information, AMF may configure the configured NSSAI and mapping information. That is, AMF may use NSSF to identify the network slice information and slice group ID of the mobile communication network to which AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, and may be notified of the mapping-related information between the network slice information and the slice group ID.

[0128] In addition, the terminal can further configure the network slice information (allowed NSSAI) and mapping information that can be used in the mobile communication network to which the terminal currently requests to subscribe.

[0129] The AMF may determine a new AMF (AMF_2) suitable for serving the network slice indicated as the allowed NSSAI based on the configured NSSAI configured in step 7 and the additionally configured allowed NSSAI (step 8).

[0130] In order to determine the new AMF (AMF_2), the AMF can obtain the new AMF information by using predetermined information or by requesting from the NSSF.

[0131] In step 9, the AMF may send a reroute NAS message to AMF_2 for requesting the transfer of the registration request message received from the terminal. In this case, in addition to the registration request message received from the terminal, the reroute NAS message may also include information about the selected AMF_2, the configured NSSAI and mapping information configured for the terminal, and at least one of the allowed NSSAI and mapping information.

[0132] In step 10, the base station transmits an initial UE message to AMF_2 through the information about AMF_2 received in step 9, and the initial UE message includes the registration request of the terminal received in step 9, the configured NSSAI configured for the terminal, and at least one of the allowed NSSAI.

[0133] In step 11, AMF_2 sends a registration response (registration acceptance) to the base station in response to the registration request of the terminal included in the initial UE message received from the base station. In this case, the registration response (registration acceptance) includes at least one of the following: configured NSSAI and mapping information, or allowed NSSAI and mapping information.

[0134] In step 12, the base station sends the registration response received from AMF_2 to the terminal.

[0135] In step 12, based on the allowed NSSAI and mapping information received together, the terminal that has received the registration acceptance can perform the PDU session process required for the subsequent necessary service, or can configure the requested NSSAI by reselecting the network slice requiring the service based on the received configured NSSAI and mapping information, and can resend the registration request including the requested NSSAI.

[0136] Figure 6 The network registration process of a terminal according to another embodiment of the present disclosure is shown.

[0137] In an embodiment of the present disclosure, the following situation will be exemplarily described: in the case of accessing another mobile communication network, the terminal has default configured NSSAI information for notifying that the terminal is a roaming terminal and requesting an update of the configured NSSAI information. The default configured NSSAI may be configured differently by each mobile communication network, and may be configured as a separate default configured NSSAI information commonly used in all mobile communication networks.

[0138] In this case, if the terminal accesses a mobile communication network that is not the mobile communication network subscribed by the terminal and belongs to another service provider, the terminal may send a registration request message including a default configured NSSAI belonging to the mobile communication network (step 2). In this case, the registration message may include the above information in the form of a request NSSAI, and the default configured NSSAI may be selected or determined as the requested NSSAI.

[0139] In step 2, the base station that has received the registration request message selects an AMF to process the connection request message of the terminal based on the NSSAI requested by the terminal included in the registration request message received from the terminal. If the base station cannot select an AMF based on the requested NSSAI, the base station may use a method according to another embodiment of the present disclosure (e.g., a method for identifying whether the terminal is a roaming user subscribed to other mobile communication service providers from terminal ID information included in the registration request message or information capable of indicating whether the terminal is a roaming user, or a method for selecting a default AMF to be predetermined as selected when no information is available) to select an AMF designated to process the registration request of the terminal.

[0140] In step 3, the AMF selected by the base station may be an AMF selected based on a default configured NSSAI, a dedicated AMF for a roaming terminal selected when the terminal is a roaming terminal, or a default AMF configured to be basically connected to the terminal. In this case, the AMF may be an AMF included in a specific network slice, and may be configured to be connected not only to all network devices or some network devices (such as AMF) included in the corresponding network slice, but also to all network devices or some network devices (such as AMF) included in a certain network slice.

[0141] In step 4, the base station transmits the terminal's registration request message to the selected AMF.

[0142] The AMF that has received the registration request message of the terminal from the base station can request the subscription information of the terminal from the UDM of the mobile communication network to which the terminal subscribes, and can obtain the subscription information of the terminal from the UDM (step 5).

[0143] The subscription information of the terminal may include the network slice information subscribed by the terminal. The network slice information subscribed by the terminal may include S-NSSAI information and slice group ID information that the terminal can use. The AMF may perform a separate authentication process with the terminal before or after receiving the subscription information from the UDM according to the situation.

[0144] Therefore, the AMF can receive the network slice information of the terminal from the UDM, and then in step 6, the predetermined information can be used to configure or update the configured AMF based on all network slice information and slice group ID information subscribed by the terminal (not limited to a specific slice group).

[0145] As another embodiment of the present disclosure, AMF may receive network slice information of the terminal from UDM, and then may use NSSF in step 6 to configure or update the configured NSSAI based on all network slice information and slice group ID information (not limited to a specific slice group) subscribed by the terminal.

[0146] In addition, when configuring the configured NSSAI, the AMF can additionally configure the network slice information (allowed NSSAI) that the terminal can use directly in the mobile communication network or through the NSSF.

[0147] In addition, after receiving the network slice information of the terminal from the UDM, the AMF can perform mapping from the network slice information and slice group ID information subscribed by the terminal to the network slice information and slice group ID used in the mobile communication network to which the AMF belongs, respectively, through predetermined information in step 6. That is, the AMF can identify the network slice information and slice group ID information of the mobile communication network to which the dedicated AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, based on the predetermined information, and can notify information about the mapping relationship between the network slice information and the slice group information.

[0148] As another embodiment, in step 6, AMF may obtain, through NSSF, mapping information between the network slice information and slice group ID information subscribed by the terminal and the network slice information and slice group ID information used in the mobile communication network to which AMF belongs. That is, AMF may use NSSF to identify the network slice information and slice group ID of the mobile communication network to which AMF belongs, corresponding to the network slice information and slice group ID information subscribed by the terminal, and may be notified of mapping-related information between the network slice information and slice group information.

[0149] In addition, based on the mapping information, the AMF may configure mapping information between the configured NSSAI including the slice information and slice group ID available in the mobile communication network to which the AMF belongs and the network slice information and slice group ID subscribed by the terminal. In addition, the AMF may further configure mapping information between the network slice information (allowed NSSAI) available to the terminal in the mobile communication network to which the terminal currently requests subscription and the network slice information available in the mobile communication network subscribed by the terminal.

[0150] According to this embodiment, the registration acceptance message sent to the base station through the AMF in step 7 includes at least one of the following: the configured NSSAI and mapping information configured in step 6, and the additionally configured allowed NSSAI and mapping information.

[0151] In step 8, the base station having received the Registration Accept sends the Registration Accept to the terminal.

[0152] Based on the received allowed NSSAI and mapping information, the terminal that has received the registration acceptance can perform the PDU session process required for the subsequent necessary services, or can configure the requested NSSAI by reselecting the network slice requiring the service based on the received configured NSSAI and mapping information, and can resend the registration request including the requested NSSAI.

[0153] According to this embodiment, the AMF that has configured the configured NSSAI and the allowed NSSAI in step 6 may select another AMF suitable for supporting the network slice indicated as the terminal and the allowed NSSA based on the allowed NSSAI. If another AMF is selected, the AMF may transmit the terminal information including at least one of the registration request of the terminal, the configured NSSAI and mapping information, and the allowed NSSAI and mapping information to the selected another AMF directly or through the base station. In this case, the AMF that has received this information configures the connection to the base station and sends the registration acceptance to the terminal. In this case, the registration response (registration acceptance) may include at least one of the configured NSSAI and mapping information, and the allowed NSSAI and mapping information.

[0154] Figure 7 is a diagram showing a configuration of a terminal according to the present disclosure.

[0155] Reference Figure 7 , the terminal may include a controller 710 and a transceiver 720. In the present disclosure, the controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0156] The transceiver 720 may be composed of a transmitter 723 and a receiver 726 , and may transmit / receive a signal with another network entity through the transmitter 723 and the receiver 726 .

[0157] The controller 710 may control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the controller 710 may control the signal flow between the various blocks to perform operations according to the above-mentioned flowchart.

[0158] Figure 8 is a diagram showing a configuration of a network entity according to the present disclosure.

[0159] Reference Figure 7 , the network entity may include a controller 810 and a transceiver 820. In the present disclosure, a controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0160] The transceiver 820 may be composed of a transmitter 823 and a receiver 826 , and may transmit / receive a signal with another network entity through the transmitter 823 and the receiver 826 .

[0161] The controller 810 may control the overall operation of the network entity according to the embodiments proposed in the present disclosure. For example, the controller 810 may control the signal flow between the various blocks to perform operations according to the above flowchart.

[0162] The methods according to the claims of the present disclosure and the embodiments described in the specification may be implemented in the form of hardware, software, or a combination of hardware and software.

[0163] In the case of software implementation, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to execute the method according to the embodiments described in the claims or description of the present disclosure.

[0164] Such a program (software module or software) may be stored in a non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage device, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other type of optical storage device, or magnetic tape cassette. In addition, the program may be stored in a memory consisting of a combination of some or all of them. Furthermore, multiple memories may be included.

[0165] In addition, the program can be stored in an attachable storage device, which can be accessed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), or a storage area network (SAN), or a communication network composed of a combination thereof. The storage device can be accessed through an external port by a device that performs an embodiment of the present disclosure. In addition, a separate storage device on a communication network can access the device that performs an embodiment of the present disclosure.

[0166] Meanwhile, in the drawings for explaining the method according to the present disclosure, the order of explanation does not necessarily correspond to the order of execution, and the order relationship between them may be changed, or they may be executed in parallel.

[0167] Furthermore, in the drawings for explaining the method according to the present disclosure, some constituent elements may be omitted, and only some constituent elements may be included within a range not impairing the essence of the present disclosure.

[0168] In the above detailed embodiments of the present disclosure, the elements included in the present disclosure may be represented in singular or plural form, depending on the detailed embodiments proposed. However, singular or plural representations have been appropriately selected for the situations proposed for ease of description, and the present disclosure is not limited to singular or plural elements. Although the element has been represented in plural form, it may be configured in singular form. Although the element has been represented in singular form, it may be configured in plural form.

[0169] Although detailed embodiments of the present disclosure have been described in the detailed description of the present disclosure, the present disclosure may be modified in various ways without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the above embodiments, but should be limited not only by the claims but also by their equivalents.

Claims

1. A method performed by an apparatus for performing an access management function in a communication system, the method comprising: Receiving, via a base station, a registration request message including requested network slice selection assistance information NSSAI from a user equipment UE; acquiring, in response to a request for subscription information of the UE, subscription information from an apparatus for managing data of a user, the subscription information comprising network slice group information for each of at least one subscribed single NSSAIS-NSSAI and at least one subscribed S-NSSAI; determining, based on the subscription information, allowed NSSAIs including at least one S-NSSAI that shares a common network slice group; as well as A registration accept message including allowed NSSAI and mapping information of allowed NSSAI is sent to the UE via the base station.

2. The method according to claim 1, wherein: At least one subscribed S-NSSAI is mapped to at least one S-NSSAI included in the allowed NSSAI.

3. The method according to claim 1, wherein: At least one S-NSSAI included in the allowed NSSAI is synchronously provided to the UE.

4. The method according to claim 1, wherein: The requested NSSAI is associated with the default configured NSSAI, and The registration acceptance message also includes the configured NSSAI and mapping information of the configured NSSAI.

5. A method performed by a user equipment UE in a communication system, the method comprising: Sending, via the base station, a registration request message including requested network slice selection assistance information NSSAI to an apparatus for performing an access management function; as well as receiving, as a response to the registration request message, a registration accept message including allowed NSSAIs and mapping information of allowed NSSAIs from an apparatus for performing an access management function via a base station, the allowed NSSAIs including at least one single NSSAI S-NSSAI sharing a common network slice group, The allowed NSSAI is associated with the UE's subscription information, and the UE's subscription information includes at least one subscribed S-NSSAI and network slice group information for each of the at least one subscribed S-NSSAI.

6. The method according to claim 5, wherein: At least one subscribed S-NSSAI is mapped to at least one S-NSSAI included in the allowed NSSAI.

7. The method according to claim 5, wherein: At least one S-NSSAI included in the allowed NSSAI is synchronously provided to the UE.

8. The method according to claim 5, wherein: The requested NSSAI is associated with the default configured NSSAI, and The registration acceptance message also includes the configured NSSAI and mapping information of the configured NSSAI.

9. An apparatus for performing access management functions in a communication system, comprising: Transceiver; as well as A controller coupled to the transceiver is configured to: receiving, via a base station, from a user equipment UE, a registration request message including requested network slice selection assistance information NSSAI, acquiring, in response to a request for subscription information of the UE, subscription information from an apparatus for managing data of a user, the subscription information including network slice group information for each of at least one subscribed single NSSA I S-NSSAI and at least one subscribed S-NSSAI, determining, based on the subscription information, allowed NSSAIs including at least one S-NSSAI that shares a common network slice group, and A registration accept message including allowed NSSAI and mapping information of allowed NSSAI is sent to the UE via the base station.

10. The apparatus for performing access management functions according to claim 9, wherein: At least one subscribed S-NSSAI is mapped to at least one S-NSSAI included in the allowed NSSAI.

11. The apparatus for performing access management functions according to claim 9, wherein: At least one S-NSSAI included in the allowed NSSAI is synchronously provided to the UE.

12. The apparatus for performing access management functions according to claim 9, wherein: The requested NSSAI is associated with the default configured NSSAI, and The registration acceptance message also includes the configured NSSAI and mapping information of the configured NSSAI.

13. A user equipment UE in a communication system, the UE comprising: Transceiver; as well as The controller is configured as: sending a registration request message including requested network slice selection assistance information NSSAI to an apparatus for performing an access management function via a base station, and As a response to the registration request message, a registration acceptance message including allowed NSSAIs and mapping information of allowed NSSAIs is received from an apparatus for performing an access management function via a base station, wherein the allowed NSSAIs include at least one single NSSAI S-NSSAI that shares a common network slice group, wherein the allowed NSSAIs are associated with subscription information of the UE, and the subscription information of the UE includes network slice group information of each of the at least one subscribed S-NSSAI and the at least one subscribed S-NSSAI.

14. The UE of claim 13, wherein at least one subscribed S-NSSAI is mapped to at least one S-NSSAI included in the allowed NSSAI.

15. The UE according to claim 13, wherein: At least one S-NSSAI included in the allowed NSSAI is synchronously provided to the UE.

16. The UE according to claim 13, wherein: The requested NSSAI is associated with the default configured NSSAI, and The registration acceptance message also includes the configured NSSAI and mapping information of the configured NSSAI.

Images