WO2025071112A1

WO2025071112A1 - Method and apparatus for providing service to user equipment in wireless communication system

Info

Publication number: WO2025071112A1
Application number: PCT/KR2024/014147
Authority: WO
Inventors: Hoyeon Lee; Ashok Kumar Nayak
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2023-09-26
Filing date: 2024-09-20
Publication date: 2025-04-03
Anticipated expiration: 2026-03-26

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retail businesses, and security and safety-related services), based on 5G communication technology and IoT-related technology.

Description

METHOD AND APPARATUS FOR PROVIDING SERVICE TO USER EQUIPMENT IN WIRELESS COMMUNICATION SYSTEM

The disclosure relates to an apparatus and a method for providing a service to a newly connected user equipment in a wireless communication system.

5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

Moreover, there has been ongoing standardization in air interface architecture/protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture/service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

The above information is presented as background information only to assist with an understanding of the disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the disclosure.

This disclosure relates to wireless communication networks, and more particularly to a terminal and a communication method thereof in a wireless communication system.

In accordance with an aspect of the disclosure, a method for processing a control signal in a wireless communication system includes receiving a first control signal transmitted from a base station, processing the received first control signal, and transmitting a second control signal generated based on the processing to the base station.

Aspects of the disclosure are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide efficient communication methods in a wireless communication system.

The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an example of an S-NSSAI information element (IE) format according to an embodiment of the disclosure;

FIG. 2 illustrates a structure of a mobile communication system according to an embodiment of the disclosure;

FIG. 3 illustrates a UE registration procedure in a wireless communication system according to an embodiment of the disclosure;

FIG. 4 illustrates a procedure for providing UE policy information in a wireless communication system according to an embodiment of the disclosure;

FIG. 5 illustrates a procedure for providing UE policy information in a wireless communication system according to an embodiment of the disclosure;

FIG. 6 is a block diagram illustrating a configuration of a UE according to an embodiment of the disclosure;

FIG. 7 is a block diagram illustrating a configuration of a base station according to an embodiment of the disclosure; and

FIG. 8 is a block diagram illustrating a configuration of a network entity according to an embodiment of the disclosure.

Aspects of the disclosure are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a terminal and a communication method thereof in a wireless communication system.

According to an embodiment of the disclosure, there may be provided a method and an apparatus for providing a service to a newly connected user equipment in a wireless communication system.

A disclosed embodiment provides an apparatus and a method for effectively providing a service in a mobile communication system.

In describing the disclosure below, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements.

Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Furthermore, each block of the flowchart illustrations may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

As used herein, the "unit" refers to a software element or a hardware element, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), which performs a predetermined function. However, the "unit" does not always have a meaning limited to software or hardware. The "unit" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The elements and functions provided by the "unit" may be either combined into a smaller number of elements, or a "unit", or divided into a larger number of elements, or a "unit". Moreover, the elements and "units" or may be implemented to reproduce one or more CPUs within a device or a security multimedia card. Furthermore, the "unit" in the embodiments may include one or more processors.

In the following description of the disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the disclosure unnecessarily unclear.

In the following description, terms for identifying access nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, and the like are illustratively used for the sake of descriptive convenience. Therefore, the disclosure is not limited by the terms as used below, and other terms referring to subjects having equivalent technical meanings may be used.

In the following description, the terms "physical channel" and "signal" may be interchangeably used with the term "data" or "control signal". For example, a physical downlink shared channel (PDSCH) is a term referring to a physical channel over which data is transmitted, but the PDSCH may be used to refer to data. That is, in the disclosure, the expression "transmit a physical channel" may be construed as having the same meaning as "transmit data or a signal over a physical channel".

In the following description of the disclosure, higher signaling may mean a signal transmission method in which a base station transmits a signal to an electronic device by using a downlink data channel in a physical layer or an electronic device transmits a signal to a base station by using an uplink data channel in a physical layer. The higher signaling may be understood as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).

In the following description of the disclosure, terms and names defined in the 3rd generation partnership project new radio (3GPP NR) or the 3rd generation partnership project long term evolution (3GPP LTE) standards will be used for the sake of descriptive convenience. However, the disclosure is not limited by these terms and names, and may be applied in the same way to systems that conform other standards. In the disclosure, the term "eNB" may be interchangeably used with the term "gNB" for the sake of descriptive convenience. That is, a base station described as "eNB" may indicate "gNB". Furthermore, the term "terminal" may refer to not only mobile phones, MTC devices, NB-IoT devices, and sensors, but also other wireless communication devices.

In the following description, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Of course, examples of the base station and the terminal are not limited thereto.

In particular, the disclosure may be applied to the 3GPP NR (5th generation mobile communication standards). The disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail business, security and safety-related services, etc.) on the basis of 5G communication technology and Internet of things (IoT)-related technology. In the disclosure, the term "eNB" may be interchangeably used with the term "gNB" for the sake of descriptive convenience. That is, a base station described as "eNB" may indicate "gNB". Furthermore, the term "terminal" may refer to not only mobile phones, MTC devices, NB-IoT devices, and sensors, but also other wireless communication devices.

A wireless communication system is advancing to a broadband wireless communication system for providing high-speed and high-quality packet data services using communication standards, such as high-speed packet access (HSPA) of 3GPP, LTE {long-term evolution or evolved universal terrestrial radio access (E-UTRA)}, LTE-Advanced (LTE-A), LTE-Pro, high-rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), IEEE 802.16e, and the like, as well as typical voice-based services.

As a typical example of the broadband wireless communication system, an LTE system employs an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and employs a single carrier frequency division multiple access (SC-FDMA) scheme in an uplink (UL). The uplink indicates a radio link through which a user equipment (UE) (or a mobile station (MS)) transmits data or control signals to a base station (BS) (eNode B), and the downlink indicates a radio link through which the base station transmits data or control signals to the UE. The above multiple access scheme separates data or control information of respective users by allocating and operating time-frequency resources for transmitting the data or control information for each user so as to avoid overlapping each other, that is, so as to establish orthogonality.

Since a 5G communication system, which is a post-LTE communication system, must freely reflect various requirements of users, service providers, and the like, services satisfying various requirements must be supported. The services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), ultra-reliability low-latency communication (URLLC), and the like.

According to an embodiment, eMBB aims at providing a data rate higher than that supported by existing LTE, LTE-A, or LTE-Pro. For example, in the 5G communication system, eMBB must provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink for a single base station. Furthermore, the 5G communication system must provide an increased user-perceived data rate to the UE, as well as the maximum data rate. In order to satisfy such requirements, transmission/reception technologies including a further enhanced multi-input multi-output (MIMO) transmission technique are required to be improved. In addition, the data rate required for the 5G communication system may be obtained using a frequency bandwidth more than 20 MHz in a frequency band of 3 to 6 GHz or 6 GHz or more, instead of transmitting signals using a transmission bandwidth up to 20 MHz in a band of 2 GHz used in LTE.

In addition, mMTC is being considered to support application services such as the Internet of Things (IoT) in the 5G communication system. mMTC has requirements, such as support of connection of a large number of UEs in a cell, enhancement coverage of UEs, improved battery time, a reduction in the cost of a UE, and the like, in order to effectively provide the Internet of Things. Since the Internet of Things provides communication functions while being provided to various sensors and various devices, it must support a large number of UEs (e.g., 1,000,000 UEs/km2) in a cell. In addition, the UEs supporting mMTC may require wider coverage than those of other services provided by the 5G communication system because the UEs are likely to be located in a shadow area, such as a basement of a building, which is not covered by the cell due to the nature of the service. The UE supporting mMTC must be configured to be inexpensive, and may require a very long battery life-time such as 10 to 15 years because it is difficult to frequently replace the battery of the UE.

Lastly, URLLC, which is a cellular-based mission-critical wireless communication service, may be used for remote control for robots or machines, industrial automation, unmanned aerial vehicles, remote health care, emergency alert, and the like. Thus, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 ms, and also requires a packet error rate of 10-5 or less. Therefore, for the services supporting URLLC, a 5G system must provide a transmit time interval (TTI) shorter than those of other services, and also may require a design for assigning a large number of resources in a frequency band in order to secure reliability of a communication link.

The above-described three services considered in the 5G communication system, that is, eMBB, URLLC, and mMTC, may be multiplexed and transmitted in a single system. In order to satisfy different requirements of the respective services, different transmission/reception techniques and transmission/reception parameters may be used between the services. However, the above mMTC, URLLC, and eMBB are merely examples of different types of services, and service types to which the disclosure is applied are not limited to the above examples.

Furthermore, in the following description, LTE, LTE-A, LTE Pro, 5G (or NR), or 6G systems will be described by way of example, but the embodiments of the disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. In addition, based on determinations by those skilled in the art, the embodiments of the disclosure may also be applied to other communication systems through some modifications without significantly departing from the scope of the disclosure.

Hereinafter, the disclosure relates to an apparatus and a method for providing a network slice in a wireless communication system. Specifically, the disclosure explains a technique for controlling and managing UE configuration information in a mobile communication network providing a network slice function in a wireless communication system.

3GPP standards standardize 5G network system architecture and procedures. A mobile network operator may provide various services in a 5G network. To provide each service, the mobile network operator needs to satisfy different service requirements (e.g., a delay time, a communication range, a data rate, a bandwidth, and reliability) for each service. To this end, the mobile network operator (or wireless service provider) may configure a network slice, and may allocate a network resource suitable for a specific service for each network slice or each set of network slices. A network resource may refer to a network function (NF), a logical resource provided by an NF, or radio resource allocation of a base station.

For example, the mobile network operator may configure network slice A to provide a mobile broadband service, network slice B to provide a vehicular communication service, and network slice C to provide an IoT service. That is, in the 5G network, each service may be provided on a network slice specialized for a characteristic of the service. Single-network slice selection assistance information (S-NSSAI) defined by the 3GPP may be used as an identifier to distinguish a network slice.

FIG. 1 illustrates an example of an S-NSSAI information element (IE) format according to an embodiment of the disclosure. One piece of S-NSSAI may include at least one of a length of S-NSSAI contents 110, a slice/service type (SST) 116 used in a home public land mobile network (home PLMN: HPLMN), a slice differentiator (SD) 118 used in the HPLMN, an SST 112 used in a serving PLMN, and an SD 114 used in the serving PLMN. The S-NSSAI is not limited to this example, and an S-NSSAI IE may include more or less information than the format illustrated in FIG. 1.

According to an embodiment of the disclosure, in non-roaming, the SST 112 used in the serving PLMN may be the SST 116 used in the HPLMN, and the SD 114 used in the serving PLMN may be the SD 118 used in the HPLMN.

According to an embodiment of the disclosure, in roaming, the SST 112 used in the serving PLMN may be an SST used in a visited PLMN (VPLMN), and the SD 114 used in the serving PLMN may be an SD used in the VPLMN.

According to an embodiment of the disclosure, each SST and SD forming the one piece of S-NSSAI may or may not have a value depending on a situation.

Network slice selection assistance information (NSSAI) may include one or more pieces of S-NSSAI. Examples of NSSAI may include Configured NSSAI stored in a UE, Requested NSSAI requested by the UE, Allowed NSSAI that the UE is allowed to use, which is determined by an NF (e.g., an AMF or an NSSF) of a 5G core network, Subscribed NSSAI to which the UE subscribes, and Default Configured NSSAI available when configured NSSAI for a PLMN is not configured in the UE. However, the foregoing examples are only for illustration, and the NSSAI is not limited to the foregoing examples.

According to an embodiment of the disclosure, a maximum of one piece of Configured NSSAI for each PLMN may be stored in the UE. That is, when the UE receives new Configured NSSAI for the PLMN, the UE may update previously stored Configured NSSAI to the newly received Configured NSSAI. However, the disclosure is not limited to this example.

According to an embodiment of the disclosure, Subscribed NSSAI may include one or more pieces of Subscribed S-NSSAI. Some of the Subscribed S-NSSAI included in the Subscribed NSSAI may be marked as a default, and information about the Default Subscribed S-NSSAI may be stored in a UDM. Default Configured NSSAI may be configuration information applicable to any PLMN, which is configured in the UE by the HPLMN, and may be used in a PLMN in which there is no Configured NSSAI for the PLMN. S-NSSAI included in the Default Configured NSSAI may be part of the Subscribed S-NSSAI. Thus, when there is a change in the Subscribed S-NSSAI, the Default Configured NSSAI may also be updated. When there is no Configured NSSAI or Allowed NSSAI for a connected PLMN, the UE configure Requested NSSAI, based on the Default Configured NSSAI.

FIG. 2 illustrates a structure of a mobile communication system according to an embodiment of the disclosure.

A 5G system (5GS) may include a UE, a new radio (NR) base station (NG-RAN), and a 5G core network. Referring to FIG. 2, the 5G core network may include an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a unified data management (UDM), a network slice selection function (NSSF), an authentication server function (AUSF), and a unified data repository (UDR). The 5G core network is not limited to the foregoing example, and may include more components than those illustrated in FIG. 2. The components included in the 5G core network may be referred to as functions or network entities.

According to an embodiment of the disclosure, the UE may connect to the 5G core network through the base station ((R)AN). Hereinafter, the UE may be referred to as a UE, and the (R)AN may be referred to as a base station. The 5G core network may further include an application function (AF) and a data network (DN).

According to an embodiment of the disclosure, the AMF is a network function (NF) that manages radio network access and mobility for the UE.

According to an embodiment of the disclosure, the SMF is an NF that manages a session for the UE, and session information includes quality-of-service (QoS) information, charging information, and information about packet processing.

According to an embodiment of the disclosure, the UPF is an NF that processes user traffic (e.g., user plane traffic), and is controlled by the SMF.

According to an embodiment of the disclosure, the PCF is an NF that manages an operator policy (PLMN policy) for providing a service in a wireless communication system. In addition, the PCF may be divided into a PCF in charge of an access and mobility (AM) policy and a UE policy and a PCF in charge of a session management (SM) policy. The PCF in charge of the AM/UE policy and the PCF in charge of the SM policy may be logically or physically separate NFs or may be logically or physically one NF.

According to an embodiment of the disclosure, the UDM is an NF that stores and manages subscriber information about the UE (UE subscription).

According to an embodiment of the disclosure, the UDR is an NF or database (DB) that stores and manages data. The UDR may store the subscription information about the UE, and may provide the subscription information about the UE to the UDM. Further, the UDR may store operator policy information, and may provide the operator policy information to the PCF.

According to an embodiment of the disclosure, the NSSF may be an NF that performs a function of selecting a network slice instance serving the UE or determining network slice selection assistance information (NSSAI).

According to an embodiment of the disclosure, the AUSF may be an NF that performs a function of supporting authentication for 3GPP access and non-3GPP access.

According to an embodiment of the disclosure, the AF may be an NF that provides a function for a service according to the disclosure.

According to an embodiment of the disclosure, the DN may refer to a data network that may provide an operator service, Internet access, or a third-party service.

FIG. 3 illustrates a UE registration procedure in a wireless communication system according to an embodiment of the disclosure.

Referring to FIG. 3, in operation 310, the UE may be configured with Default Configured NSSAI, and may store the same. According to an embodiment, the Default Configured NSSAI may include first S-NSSAI. The UE may not store information about Configured NSSAI and/or Allowed NSSAI for a PLMN (serving PLMN) with which the UE wishes to register.

In operation 312, a UDM may store UE subscription information. The UE subscription information may include subscribed NSSAI. The subscribed NSSAI may include the first S-NSSAI and second S-NSSAI. According to an embodiment of the disclosure, the second S-NSSAI may be stored along with an indicator indicating a default network slice.

In operation 314, the UE may transmit a registration request message to an AMF. Since the Configured NSSAI and/or Allowed NSSAI for the serving PLMN are not stored in the UE and the Default Configured NSSAI applicable to any PLMN is stored in the UE, the UE may configure (or set) Requested NSSAI, based on the Default Configured NSSAI. That is, the Requested NSSAI may include the first S-NSSAI included in the Default Configured NSSAI, and the registration request message may include the Requested NSSAI. Additionally, an indicator (Default Configured NSSAI indication, hereinafter DCN indication) indicating that the Requested NSSAI is generated based on the Default Configured NSSAI may be included in the registration request message.

In operation 316, the AMF may transmit a UE subscription information request message to the UDM to process the registration request message. The UE subscription information request message may include a UE ID (e.g., UE identification information).

In operation 318, the UDM may transmit the UE subscription information corresponding to the requested UE ID to the AMF. The UE subscription information may include the subscribed NSSAI. The subscribed NSSAI may include the first S-NSSAI and the second S-NSSAI. The second S-NSSAI may be transmitted to the AMF along with an indicator (e.g., a default network slice).

According to an embodiment of the disclosure, in operation 320, the AMF may determine Allowed NSSAI. The Allowed NSSAI may be determined based on at least one of the Requested NSSAI received from the UE, the subscribed NSSAI received from the UDM, and information about a network slice providable at a current location of the UE. The AMF may determine that the UE does not include the Configured NSSAI for the current serving PLMN, based on the DCN indication included in the registration request message.

When the Requested NSSAI is based on the Default Configured NSSAI, that is, when the Configured NSSAI for the serving PLMN is not stored in the UE, the AMF may transmit Allowed NSSAI including the subscribed S-NSSAI marked as the default network slice. When the AMF receives the subscribed S-NSSAI having the indicator (e.g., the default network slice) from the UDM in operation 318, the AMF may transmit the Allowed NSSAI including the subscribed S-NSSAI. Here, even though the subscribed S-NSSAI received from the UDM is not included in the Requested NSSAI, the AMF may transmit the Allowed NSSAI including the subscribed S-NSSAI received from the UDM.

That is, according to an embodiment of the disclosure, the Allowed NSSAI provided by the AMF may include the first S-NSSAI and the second S-NSSAI. Since the first S-NSSAI is a network slice included in the Requested NSSAI requested by the UE and the subscribed NSSAI received from the UDM, the first S-NSSAI may be included in the Allowed NSSAI according to determination of the AMF. Further, since the second S-NSSAI is a network slice not included in the Requested NSSAI requested by the UE but is stored along with the indicator (e.g., the default network slice) in the subscribed NSSAI received from the UDM, the second S-NSSAI may be included in the Allowed NSSAI by the determination of the AMF. When the DCN indication is not received, that is, when the Requested NSSAI of the UE is generated based on the Configured NSSAI for the serving PLMN, the subscribed S-NSSAI marked as the default network slice may not be included in the Allowed NSSAI by the determination of the AMF. The AMF may determine Configured NSSAI for the serving PLMN to be provided to the UE. The Configured NSSAI may include the subscribed NSSAI (first S-NSSAI and second S-NSSAI) received from the UDM.

According to another embodiment of the disclosure, the AMF may determine Allowed NSSAI through interaction with an NSSF. To this end, operation 322 and operation 324 may be performed. According to an embodiment of the disclosure, operation 322 and operation 324 may be performed separately from or together with operation 310 to operation 320. In operation 322, the AMF may transmit a network slice selection request message to the NSSF. The network slice selection request message may include at least one of the Requested NSSAI received from the UE and the subscribed NSSAI received from the UDM. Further, the network slice selection request message may include the DCN indication. The NSSF may determine Allowed NSSAI, based on information received from the AMF. For example, when receiving the DN indication, the NSSF may transmit the Allowed NSSAI including the subscribed S-NSSAI marked as the default network slice. Here, even though the subscribed S-NSSAI marked as the default network slice is not included in the Requested NSSAI, the NSSF may include the subscribed S-NSSAI marked as the default network slice in the Allowed NSSAI. That is, according to an embodiment of the disclosure, the NSSF may include the first S-NSSAI and the second S-NSSAI in the Allowed NSSAI. Since the first S-NSSAI is a network slice included in the Requested NSSAI requested by the UE and the subscribed NSSAI received from the UDM, the first S-NSSAI may be included in the Allowed NSSAI according to determination of the NSSF. Further, since the second S-NSSAI is a network slice not included in the Requested NSSAI requested by the UE but is stored along with the indicator (e.g., the default network slice) in the subscribed NSSAI, the second S-NSSAI may be included in the Allowed NSSAI by the determination of the NSSF. When the DCN indication is not received, that is, when the Requested NSSAI of the UE is generated based on the Configured NSSAI for the serving PLMN, the subscribed S-NSSAI marked as the default network slice may not be included in the Allowed NSSAI by the determination of the NSSF. The NSSF may determine Configured NSSAI for the serving PLMN to be provided to the UE. The Configured NSSAI may include the subscribed NSSAI (first S-NSSAI and second S-NSSAI) received from the UDM.

In operation 324, the NSSF may transmit a network slice selection response message to the AMF. The response message may include the Allowed NSSAI (including the first S-NSSAI and the second S-NSSAI) determined by the NSSF. Further, the response message may include the Configured NSSAI (including the first S-NSSAI and the second S-NSSAI) according to a change in network slice subscription information.

According to an embodiment of the disclosure, the AMF and/or the NSSF may perform NSSAI mapping in

operation

320 or 322. The Default Configured NSSAI is configuration information configured by a HPLMN for the UE, and may use S-NSSAI understandable to a PLMN as a roaming partner determined by PLMNs as roaming partners of the HPLMN, for example, a standardized S-NSSAI value. That is, the S-NSSAI forming the Default Configured NSSAI and the S-NSSAI included in the Requested NSSAI determined based on the Default Configured NSSAI may include an SST 112, and may additionally include an SD 116. However, the disclosure is not limited to the above example. In addition, the S-NSSAI forming the Default Configured NSSAI and the S-NSSAI included in the Requested NSSAI determined based on the Default Configured NSSAI may not include a mapped HPLMN SST 116 and a mapped HPLMN SD 118.

However, the Configured NSSAI determined by the AMF and/or the NSSF may include S-NSSAI used in the current serving PLMN. That is, the S-NSSAI forming the Configured NSSAI and S-NSSAI forming the Allowed NSSAI including at least part of the Configured NSSAI may include an SST 112 and a mapped HPLMN SST 116, and may additionally include an SD 116 and a mapped HPLMN SD 118.

Table 1 shows an example of the first S-NSSAI forming the Requested NSSAI according to an embodiment of the disclosure. The first S-NSSAI included in the Requested NSSAI may have only a value of an SST 112. The first S-NSSAI included in Requested NSSAI may have a value of an SD 114.

Table 2 and Table 3 show examples of the first S-NSSAI and the second S-NSSAI that forming the Allowed NSSAI according to an embodiment of the disclosure. The first S-NSSAI included in the Allowed NSSAI may have values of an SST 112 and a mapped HPLMN SST 116. The mapped HPLMN SST 116 (and additionally an HPLMN SD 118) of the first S-NSSAI included in the Allowed NSSAI may correspond to the SST 112 (and additionally the SD 114) of the first S-NSSAI included in the Requested NSSAI. Further, the mapped HPLMN SST 116 (and additionally the HPLMN SD 118) of the first S-NSSAI included in the Allowed NSSAI may be a value corresponding to the subscribed S-NSSAI received by the AMF from the UDM. The SST 112 (and additionally the SD 114) of the first S-NSSAI included in the Allowed NSSAI may be a network slice value used in the serving PLMN.

A mapped HPLMN SST 116 (and additionally an HPLMN SD 118) of the second S-NSSAI included in the Allowed NSSAI may be a value corresponding to the subscribed S-NSSAI received by the AMF from the UDM. An SST 112 (and additionally an SD 114) of the second S-NSSAI included in the Allowed NSSAI may be a network slice value used in the serving PLMN.

In operation 326, the AMF may transmit a registration response message to the UE. The registration response message may include the Allowed NSSAI (including the first S-NSSAI and the second S-NSSAI) determined according to an embodiment of the disclosure. The registration response message may include mapping information of the S-NSSAI included in the Allowed NSSAI. In addition, the registration response message may include the Configured NSSAI. The UE may know, based on the received Allowed NSSAI, that the UE may connect to a network and use the first S-NSSAI and the second S-NSSAI. Accordingly, the UE may establish a PDU session by using the first S-NSSAI and/or the second S-NSSAI in a subsequent procedure.

According to an embodiment of the disclosure, the AMF and/or the NSSF may transmit the Allowed NSSAI including at least part of the S-NSSAI (e.g., the default network slice) of the Configured NSSAI to the UE at the same time as transmitting the Configured NSSAI to the UE through the procedure illustrated in FIG. 3. The S-NSSAI may be S-NSSAI not included in the Requested NSSAI. The AMF and/or the NSSF may perform a function shown in 3 even under a specific condition (e.g., when receiving the DCN indication or when transmitting the Configured NSSAI to the UE).

The wireless communication system according to an embodiment of the disclosure may simultaneously transmit network slice configuration information (Configured NSSAI) and an allowed slice (Allowed NSSAI) to the UE when the UE having no Configured NSSAI for the serving PLMN connects to the PLMN according to the procedure shown in FIG. 3. Accordingly, the UE may use at least some (e.g., subscribed S-NSSAI(s) marked as a default) of network slices included in the UE subscription information without an additional registration request procedure. Accordingly, the wireless communication system may prevent the UE from not registering and not using a network slice configured for the UE.

FIG. 4 illustrates a procedure for providing UE policy information in a wireless communication system according to an embodiment of the disclosure.

Referring to FIG. 4, a UE may not have stored configuration information related to a network slice, because the UE has never connected to a PLMN and may thus have no network slice configuration information (Configured NSSAI) related to the PLMN.

Alternatively, the UE may have stored first S-NSSAI configuration information (Configured NSSAI) in operation 410. The first S-NSSAI configuration information may be configuration information received when the UE connects to the PLMN.

In operation 412, the UE may transmit a registration request message to an AMF. The AMF may process the registration request message.

In operation 412, when there is no network slice information configured for the UE, the UE may not include Requested NSSAI in the registration request message. When no Requested NSSAI is included in the registration request message received from the UE, the AMF may determine that Allowed NSSAI includes a network slice (third S-NSSAI) marked as a default among subscribed S-NSSAI.

Alternatively, in operation 412, when the UE does not have the Configured NSSAI for the PLMN but stores Default Configured NSSAI (including second S-NSSAI), the UE may generate Requested NSSAI (second S-NSSAI), based on the Default Configured NSSAI. The UE may transmit a registration request message including the Requested NSSAI. When the Requested NSSAI included in the registration request message is based on the Default Configured NSSAI, that is, when a DCN indication is included in the registration request message, the AMF may determine that Allowed NSSAI includes a network slice (third S-NSSAI) marked as a default among subscribed S-NSSAI.

Alternatively, in operation 412, when the Configured NSSAI (first S-NSSAI) for the PLMN is stored in the UE, the UE may generate Requested NSSAI, based on the Configured NSSAI. The UE may transmit a registration request message including the Requested NSSAI (first S-NSSAI). When there is a change in network slice subscription information about the UE (e.g., when new S-NSSAI is added to subscribed NSSAI), the AMF determines that Allowed NSSAI includes fourth S-NSSAI newly added to UE subscription information. That is, the AMF according to an embodiment of the disclosure may determine to add the fourth S-NSSAI, which is not included in a Requested NSSAI form in the registration request message in operation 412, to the Allowed NSSAI.

The third S-NSSAI and/or the fourth S-NSSAI may be S-NSSAI not configured in the UE, that is, S-NSSAI in a case where the Configured NSSAI for the serving PLMN is absent in the UE or S-NSSAI that is not included in the Configured NSSAI stored in the UE. In this case, the AMF may determine to provide the UE with UE policy information for using the third S-NSSAI and/or the fourth S-NSSAI. The AMF may perform operation 414 to provide the UE with the UE policy information for the third S-NSSAI and/or fourth S-NSSAI.

In operation 414, the AMF may transmit a request message to transmit/update the UE policy information to a PCF. The AMF may transmit network slice information (e.g., the third S-NSSAI and/or the fourth S-NSSAI and the subscribed NSSAI) for which a UE policy is required to the PCF.

In operation 416, the PCF may transmit URSP information for using S-NSSAI requested by the AMF or subscribed to by the UE to the AMF. The URSP information may include the S-NSSAI and information about an application that may the S-NSSAI. Table 4 shows an example of the URSP information. The disclosure is not limited to the following example.

In operation 418, the AMF may transmit a registration response message to the UE. The registration response message may include the Allowed NSSAI (including S-NSSAI). The Allowed NSSAI may include S-NSSAI (third S-NSSAI and/or fourth S-NSSIA) not included in the Requested NSSAI (including the first S-NSSAI and/or the second S-NSSAI). That is, the Allowed NSSAI may include at least one of the first S-NSSAI, the second S-NSSAI, the third S-NSSAI, and the fourth S-NSSAI. The registration response message may include new/updated Configured NSSAI. The Configured NSSAI may include a subscribed slice (subscribed NSSAI) of the UE received by the AMF from a UDM. That is, the Configured NSSAI may include at least one of the first S-NSSAI, the second S-NSSAI, the third S-NSSAI, and the fourth S-NSSAI. The registration response message may include the URSP (including S-NSSAI-related route selection information) information.

Alternatively, the URSP information may be transmitted to the UE as an independent message (e.g., a UE configuration update message) separate from the registration response message in operation 420. When the URSP is transmitted to the UE as the independent message separate from the registration response message, a message in operation 416 may not include a URSP.

Based on the information received in operation 418 (and operation 420), the UE may perform a protocol data unit (PDU) session establishment procedure by using the S-NSSAI included in the Allowed NSSAI received in a subsequent operation. According to an embodiment of the disclosure, a network (AMF or PCF) may transmit the network slice configuration information (Configured NSSAI) including the third S-NSSAI and/or the fourth S-NSSAI not configured in the UE to the UE, and may also transmit the Allowed NSSAI including the third S-NSSAI and/or the fourth S-NSSAI and the URSP to the UE. That is, the network may allow the UE to use the S-NSSAI included in the Allowed NSSAI.

In operation 422, the UE may select a route by using the received Allowed NSSAI and the URSP information. For example, the UE may determine that S-NSSAI for using Application 1 is the fourth S-NSSAI, based on the URSP. The UE may identify that the fourth S-NSSAI is included in the Allowed NSSAI. Accordingly, the UE may determine to establish a PDU session with the fourth S-NSSAI in order to use Application 1.

In operation 424, the UE may transmit a PDU session establishment request message. The PDU session establishment request message may include the fourth S-NSSAI.

FIG. 5 illustrates a procedure for providing UE policy information in a wireless communication system according to an embodiment of the disclosure.

Referring to FIG. 5, operation 510 and operation 512 may correspond to operation 410 and operation 412 of FIG. 4 .

In operation 514, an AMF may transmit a registration response message to a UE. The registration response message may include Allowed NSSAI (including S-NSSAI). The Allowed NSSAI may include S-NSSAI (third S-NSSAI and/or fourth S-NSSAI) not included in Requested NSSAI (including first S-NSSAI and/or second S-NSSAI). That is, the Allowed NSSAI may include at least one of the first S-NSSAI, the second S-NSSAI, the third S-NSSAI, and the fourth S-NSSAI. The registration response message may include new/updated Configured NSSAI. The Configured NSSAI may include a subscribed slice (subscribed NSSAI) of the UE received by the AMF from a UDM. That is, the Configured NSSAI may include at least one of the first S-NSSAI, the second S-NSSAI, the third S-NSSAI, and the fourth S-NSSAI.

According to an embodiment of the disclosure, the UE may store the received Allowed NSSAI. Further, the UE may identify a URSP related to the S-NSSAI included in the received Allowed NSSAI, stored in the UE, in order to establish a PDU session by using the S-NSSAI included in the received Allowed NSSAI. When at least some of the S-NSSAI included in the Allowed NSSAI is not included in the URSP, the UE may determine to request an update on a UE policy. The UE may perform operation 516.

In operation 516, the UE may transmit a request message to transmit/update UE policy information to a PCF. The message in operation 516 may be transmitted to the PCF through the AMF. The request message may include URSP information stored by the UE. The UE may request network slice information (e.g., S-NSSAI) for which a UE policy is required, that is, S-NSSAI received by the UE via the Allowed NSSAI or Configured NSSAI but not included in the URSP of the UE, from the PCF.

In operation 518, the PCF may transmit URSP information for using S-NSSAI to the UE. The URSP information may include the S-NSSAI and information about an application that may use the S-NSSAI. Operation 518 may correspond to

operation

418 or 420 of FIG. 4.

The UE may select a route by using the received Allowed NSSAI and URSP information in operation 520, and may request establishment of a PDU session in operation 522. Operation 522 and operation 524 may correspond to operation 422 and operation 424 of FIG. 4 .

FIG. 6 is a block diagram illustrating a structure of a UE according to an embodiment of the disclosure.

As illustrated in FIG. 6, the UE according to the disclosure may include a processor 620, a transceiver 600, and a memory 610. However, the UE is not limited to the foregoing components. For example, the UE may include more components or fewer components than the foregoing components. The processor 620, the transceiver 600, and the memory 610 may be configured as a single chip.

According to an embodiment of the disclosure, the processor 620 may control a series of processes such that the UE may operate according to the foregoing embodiments of the disclosure. For example, the processor 620 may control the components of the UE to perform a method for providing a network slice to provide a service according to the foregoing embodiments. The processor 620 may control the components of the UE to perform the foregoing embodiments of the disclosure by executing a program stored in the memory 610. The processor 620 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

According to an embodiment of the disclosure, the transceiver 600 may transmit and receive a signal to and from a network entity, another UE, or a base station. The signal transmitted to and received from the network entity, the other UE, or the base station may include control information and data. The transceiver 600 may include an RF transmitter to upconvert and amplify the frequency of a transmitted signal and an RF receiver to perform low-noise amplification of a received signal and to downconvert the frequency of the received signal. However, the transceiver 600 is only an embodiment, and components of the transceiver 600 are not limited to the RF transmitter and the RF receiver. The transceiver 600 may receive a signal through a radio channel to output the signal to the processor 620, and may transmit a signal output from the processor 620 through the radio channel.

According to an embodiment of the disclosure, the memory 610 may store a program and data necessary for an operation of the UE. Further, the memory 610 may store control information or data included in a signal transmitted and received by the UE. The memory 610 may be configured as a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. There may be a plurality of memories 610. According to an embodiment, the memory 610 may store a program to perform the foregoing method for providing the network slice to provide the service.

FIG. 7 is a block diagram illustrating a structure of a base station according to an embodiment of the disclosure.

As illustrated in FIG. 7, the base station according to the disclosure may include a processor 720, a transceiver 700, and a memory 710. However, the base station is not limited to the foregoing components. For example, the base station may include more components or fewer components than the foregoing components. The processor 720, the transceiver 700, and the memory 710 may be configured as a single chip.

According to an embodiment of the disclosure, the processor 720 may control a series of processes such that the base station may operate according to the foregoing embodiments of the disclosure. For example, the processor 720 may control the components of the base station to provide a method for providing a network slice to provide a service according to the foregoing embodiments. The processor 720 may control the components of the base station to perform the foregoing embodiments of the disclosure by executing a program stored in the memory 710. The processor 720 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

According to an embodiment of the disclosure, the transceiver 700 may transmit and receive a signal to and from a network entity, another base station, or a UE. The signal transmitted to and received from the network entity, the other base station, or the UE may include control information and data. The transceiver 700 may include an RF transmitter to upconvert and amplify the frequency of a transmitted signal and an RF receiver to perform low-noise amplification of a received signal and to downconvert the frequency of the received signal. However, the transceiver 700 is only an embodiment, and components of the transceiver 700 are not limited to the RF transmitter and the RF receiver. The transceiver 700 may receive a signal through a radio channel to output the signal to the processor 720, and may transmit a signal output from the processor 720 through the radio channel.

According to an embodiment of the disclosure, the memory 710 may store a program and data necessary for an operation of the base station. Further, the memory 710 may store control information or data included in a signal transmitted and received by the base station. The memory 710 may be configured as a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. There may be a plurality of memories 710. According to an embodiment, the memory 710 may store a program to perform the foregoing method for providing the network slice to provide the service.

FIG. 8 is a block diagram illustrating a structure of a network entity according to an embodiment of the disclosure.

As illustrated in FIG. 8, the network entity according to the disclosure may include a processor 820, a transceiver 800, and a memory 810. However, the network entity is not limited to the foregoing components. For example, the network entity may include more components or fewer components than the foregoing components. The processor 820, the transceiver 800, and the memory 810 may be configured as a single chip.

According to an embodiment of the disclosure, the processor 820 may control a series of processes such that the network entity may operate according to the foregoing embodiments of the disclosure. For example, the processor 820 may control the components of the network entity to provide a method for providing a network slice to provide a service according to the foregoing embodiments. The processor 820 may control the components of the network entity to perform the foregoing embodiments of the disclosure by executing a program stored in the memory 810. The processor 820 may be an application processor (AP), a communication processor (CP), a circuit, an application-specific circuit, or at least one processor.

According to an embodiment of the disclosure, the transceiver 800 may transmit and receive a signal to and from another network entity, a base station, or a UE. The signal transmitted to and received from the other network entity, the base station, or the UE may include control information and data. The transceiver 800 may include an RF transmitter to upconvert and amplify the frequency of a transmitted signal and an RF receiver to perform low-noise amplification of a received signal and to downconvert the frequency of the received signal. However, the transceiver 800 is only an embodiment, and components of the transceiver 800 are not limited to the RF transmitter and the RF receiver. The transceiver 800 may receive a signal through a radio channel to output the signal to the processor 820, and may transmit a signal output from the processor 820 through the radio channel.

According to an embodiment of the disclosure, the memory 810 may store a program and data necessary for an operation of the network entity. Further, the memory 810 may store control information or data included in a signal transmitted and received by the network entity. The memory 810 may be configured as a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. There may be a plurality of memories 810. According to an embodiment, the memory 810 may store a program to perform the foregoing method for providing the network slice to provide the service.

The methods according to various embodiments described in the claims or the specification of the disclosure may be implemented by hardware, software, or a combination of hardware and software.

When the methods are implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium may be configured for execution by one or more processors within the electronic device. The at least one program may include instructions that cause the electronic device to perform the methods according to various embodiments of the disclosure as defined by the appended claims and/or disclosed herein.

The programs (software modules or software) may be stored in non-volatile memories including a random access memory and a flash memory, a read only memory (ROM), an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other type optical storage devices, or a magnetic cassette. Alternatively, any combination of some or all of them may form a memory in which the program is stored. Furthermore, a plurality of such memories may be included in the electronic device.

In addition, the programs may be stored in an attachable storage device which may access the electronic device through communication networks such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), and Storage Area Network (SAN) or a combination thereof. Such a storage device may access the electronic device via an external port. Further, a separate storage device on the communication network may access a portable electronic device.

In the above-described detailed embodiments of the disclosure, an element included in the disclosure is expressed in the singular or the plural according to presented detailed embodiments. However, the singular form or plural form is selected appropriately to the presented situation for the convenience of description, and the disclosure is not limited by elements expressed in the singular or the plural. Therefore, either an element expressed in the plural may also include a single element or an element expressed in the singular may also include multiple elements.

Although specific embodiments have been described in the detailed description of the disclosure, it will be apparent that various modifications and changes may be made thereto without departing from the scope of the disclosure. Therefore, the scope of the disclosure should not be defined as being limited to the embodiments, but should be defined by the appended claims and equivalents thereof. That is, it will be apparent to those skilled in the art that other variants based on the technical idea of the disclosure may be implemented. Furthermore, the above respective embodiments may be employed in combination, as necessary. For example, a part of an embodiment may be combined with a part of another embodiment to operate a base station and a terminal. Moreover, the embodiments of the disclosure may be applied to other communication systems, and other variants based on the technical idea of the embodiments may also be implemented.

Claims

A method performed by an access and mobility management function (AMF) entity in a wireless communication system, the method comprising:

transmitting, to an unified data management (UDM) entity, user equipment (UE) subscription information request message based on register request of the UE, wherein the subscription information request message includes requested network slice selection assistance information (NSSAI) and a default configured NSSAI (DCN) indication;

receiving, from the UDM entity, UE subscription information including subscribed NSSAI; and

identifying allowed NSSAI based on at least one of the requested NSSAI, the subscribed NSSAI, or information on a network slice providable at a current location of the UE,

wherein the DCI indication indicates that the requested NSSAI is generated based on the default configured NSSAI.
The method of claim 1, further comprising:

transmitting, to a network slice selection function (NSSF) entity, a network slice selection request message including at least one of the requested NSSAI, the subscribed NSSAI, or the DCN indication; and

receiving, from the NSSF entity, a network slice selection response message including the allowed NSSAI, or configured NSSAI based on a change of network slice subscription information.
The method of claim 2, further comprising:

transmitting, to the UE, a registration response message including at least one of the allowed NSSAI, mapping information of single NSSAI (S-NSSAI) included in the allowed NSSAI, or the configured NSSAI.
The method of claim 3,

wherein the allowed NSSAI includes first S-NSSAI and second S-NSSAI, and

wherein the first S-NSSAI and the second S-NSSAI are available for the UE based on the allowed NSSAI.
A method performed by a user equipment (UE) in a wireless communication system, the method comprising:

storing UE subscription information including subscribed network slice selection assistance information (NSSAI), wherein the subscribed NSSAI includes first single NSSAI (S-NSSAI) and second S-NSSAI; and

transmitting, to an access and mobility management function (AMF) entity, a register request message, wherein the register request message includes requested NSSAI and a default configured NSSAI (DCN) indication,

wherein the DCI indication indicates that the requested NSSAI is generated based on the default configured NSSAI.
The method of claim 5, further comprising:

receiving, from the AMF entity, a registration response message including at least one of allowed NSSAI, mapping information of S-NSSAI included in the allowed NSSAI, or configured NSSAI from a network slice selection function (NSSF) entity.
The method of claim 6,

wherein the allowed NSSAI is based on at least one of the requested NSSAI, the subscribed NSSAI stored in an unified data management (UDM) entity, or information on a network slice providable at a current location of the UE.
The method of claim 6, further comprising:

identifying that the first S-NSSAI and the second S-NSSAI are available for the UE based on the allowed NSSAI.
An access and mobility management function (AMF) entity in a wireless communication system, the AMF entity comprising:

a transceiver; and

at least one processor coupled with the transceiver and configured to:

transmit, to an unified data management (UDM) entity, user equipment (UE) subscription information request message based on register request of the UE, wherein the subscription information request message includes requested network slice selection assistance information (NSSAI) and a default configured NSSAI (DCN) indication,

receive, from the UDM entity, UE subscription information including subscribed NSSAI, and

identify allowed NSSAI based on at least one of the requested NSSAI, the subscribed NSSAI, or information on a network slice providable at a current location of the UE,

wherein the DCI indication indicates that the requested NSSAI is generated based on the default configured NSSAI.
The AMF entity of claim 9, wherein the at least one processor is further configured to:

transmit, to a network slice selection function (NSSF) entity, a network slice selection request message including at least one of the requested NSSAI, the subscribed NSSAI, or the DCN indication, and

receive, from the NSSF entity, a network slice selection response message including the allowed NSSAI, or configured NSSAI based on a change of network slice subscription information.
The AMF entity of claim 10, wherein the at least one processor is further configured to:

transmit, to the UE, a registration response message including at least one of the allowed NSSAI, mapping information of single NSSAI (S-NSSAI) included in the allowed NSSAI, or the configured NSSAI.
The AMF entity of claim 11,

wherein the allowed NSSAI includes first S-NSSAI and second S-NSSAI, and

wherein the first S-NSSAI and the second S-NSSAI are available for the UE based on the allowed NSSAI.
A user equipment (UE) in a wireless communication system, the UE comprising:

a transceiver; and

at least one processor coupled with the transceiver and configured to:

store UE subscription information including subscribed network slice selection assistance information (NSSAI), wherein the subscribed NSSAI includes first single NSSAI (S-NSSAI) and second S-NSSAI, and

transmit, to an access and mobility management function (AMF) entity, a register request message, wherein the register request message includes requested NSSAI and a default configured NSSAI (DCN) indication,

wherein the DCI indication indicates that the requested NSSAI is generated based on the default configured NSSAI.
The UE of claim 13, wherein the at least one processor is further configured to:

receive, from the AMF entity, a registration response message including at least one of allowed NSSAI, mapping information of S-NSSAI included in the allowed NSSAI, or configured NSSAI from a network slice selection function (NSSF) entity,

wherein the allowed NSSAI is based on at least one of the requested NSSAI, the subscribed NSSAI stored in an unified data management (UDM) entity, or information on a network slice providable at a current location of the UE.
The UE of claim 14, wherein the at least one processor is further configured to:

identify that the first S-NSSAI and the second S-NSSAI are available for the UE based on the allowed NSSAI.