Method and apparatus for managing terminal subscription information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method for processing control signals in a wireless communication system, of the present disclosure, may be characterized by comprising the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting, to the base station, a second control signal generated on the basis of the processing.

Description

Method and device for managing terminal subscription information in a wireless communication system

[0001] The present disclosure relates to a wireless communication system or a mobile communication system. Specifically, it relates to a method and device for managing terminal subscription information in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The present disclosure may provide a method and device for managing subscription information of a terminal in a wireless communication system or a mobile communication system. The technical challenges addressed by the present disclosure are not limited to those mentioned above, and other technical challenges not mentioned will be readily apparent to those skilled in the art to which the present disclosure pertains, based on the description below.

[0009] According to one embodiment of the present invention, a method for solving the above-described problem is characterized by comprising the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; generating a second signal based on the processing; and transmitting the generated second control signal to the base station.

[0010] According to embodiments proposed in the present disclosure, a method and device capable of effectively managing subscription information of a terminal in a wireless communication system are provided.

[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0012] FIG. 1 illustrates the configuration of a Single-Network Slice Selection Assistance Information Information Element (S-NSSAI IE) according to one embodiment of the present disclosure.

[0013] FIG. 2 illustrates a mobile communication system structure according to one embodiment of the present disclosure.

[0014] FIG. 3 illustrates a procedure for changing network slice subscription information in a wireless communication system according to one embodiment of the present disclosure.

[0015] FIG. 4 illustrates a procedure for changing network slice subscription information in a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 5 illustrates the structure of a terminal according to one embodiment of the present disclosure.

[0017] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.

[0018] In describing the embodiments in this specification, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary explanations.

[0019] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0020] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to make the present disclosure complete and to fully inform those skilled in the art of the present disclosure of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0021] The present disclosure relates to a device and method for providing network slicing in a wireless communication system. Specifically, the present disclosure describes techniques for controlling and managing terminal configuration information in a mobile communication network system that provides network slicing functionality in a wireless communication system.

[0022] The 3GPP standardized the 5G network system architecture and procedures. Mobile carriers can offer various services on 5G networks. To provide each service, mobile carriers must satisfy different service requirements (e.g., latency, communication range, data rate, bandwidth, reliability, etc.). To achieve this, mobile carriers can configure network slices and allocate network resources appropriate for specific services, either by network slice or by set of network slices. Network resources can refer to network functions (NFs), logical resources provided by NFs, or radio resource allocations from base stations.

[0023] For example, a mobile carrier may configure network slice A to provide mobile broadband services, network slice B to provide vehicular communication services, and network slice C to provide IoT services. In other words, in a 5G network, each service can be provided on a network slice specialized for its characteristics. The Single-Network Slice Selection Assistance Information (S-NSSAI) defined by 3GPP can be used as a delimiter to distinguish network slices.

[0024] FIG. 1 illustrates the configuration of a Single-Network Slice Selection Assistance Information Information Element (S-NSSAI IE) according to one embodiment of the present disclosure.

[0025] Referring to FIG. 1, one S-NSSAI may include at least one of an SST (Slice / Service Type, 116) used in an HPLMN (Home PLMN: Home Public Land Mobile Network), an SD (Slice Differentiator, 118) used in the HPLMN, an SST (112) used in a serving PLMN, and an SD (114) used in a serving PLMN. In addition, one S-NSSAI may include the length of the S-NSSAI content (110).

[0026] According to one embodiment of the present disclosure, in a non-roaming situation, the SST (112) used in the serving PLMN may be the SST (116) used in the HPLMN, and further, the SD (114) used in the serving PLMN may be the SD (118) used in the HPLMN.

[0027] According to one embodiment of the present disclosure, in a roaming situation, the SST (112) used in the serving PLMN may be the SST used in the VPLMN (Visited PLMN), and further, the SD (114) used in the serving PLMN may be the SD used in the VPLMN.

[0028] Meanwhile, each SST and SD value that constitutes one S-NSSAI may or may not have a value depending on the situation.

[0029] According to one embodiment of the present disclosure, network slice selection assistance information (NSSAI) may be composed of one or more S-NSSAIs. Examples of NSSAIs may include a Configured NSSAI stored in a terminal, a Requested NSSAI requested by a terminal, an Allowed NSSAI that the terminal is permitted to use as determined by an NF (e.g., AMF, NSSF, etc.) of a 5G core network, a subscribed NSSAI to which the terminal is subscribed, etc., but these are only examples and examples of NSSAIs are not limited to the above. At most one Configured NSSAI may be stored in a terminal per PLMN. That is, when a new Configured NSSAI for the corresponding PLMN is received, the terminal may update the previously stored Configured NSSAI with the newly received Configured NSSAI. The Subscribed NSSAI may include one or more subscribed S-NSSAIs. In one example, some of the subscribed S-NSSAIs included in the Subscribed NSSAI may be marked as default, and terminal subscription information including the subscribed S-NSSAIs may be stored in the UDM.

[0030] FIG. 2 illustrates a mobile communication system structure according to one embodiment of the present disclosure.

[0031] 5GS (5G System) can be composed of a terminal (UE), a New Radio (NR) base station (NG-RAN), and a 5G core network. Referring to FIG. 2, the 5G core network can be composed of 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). A terminal (UE) can access a 5G core network through a base station ((R)AN). Hereinafter, the UE may be referred to as a terminal, and the (R)AN may be referred to as a base station. In addition, the 5G core network may further include an Application Function (AF) and a Data Network (DN).

[0032] According to one embodiment of the present disclosure, AMF is a Network Function (NF) that manages wireless network access and mobility for a terminal.

[0033] SMF is an NF that manages sessions for terminals, and session information includes QoS (Quality of Service) information, charging information, and packet processing information.

[0034] UPF is an NF that handles user traffic (e.g., User Plane traffic) and is controlled by SMF.

[0035] The PCF is an NF that manages operator policy (PLMN policy) for providing services in a wireless communication system. Additionally, the PCF can be divided into a PCF responsible for AM (Access and Mobility) policy and UE policy, and a PCF responsible for SM (Session Management) policy. The PCF responsible for AM / UE policy and the PCF responsible for SM policy can be logically or physically separate NFs, or they can be a single NF.

[0036] UDM is a network function that stores and manages subscriber information (UE subscription) of a terminal. UDM can store the subscribed NSSAI of the terminal.

[0037] A UDR is a network function (NF) or database (DB) that stores and manages data. It stores terminal subscription information and can provide it to the UDM. Additionally, it can store operator policy information and provide it to the PCF.

[0038] NSSF may be an NF that performs the function of selecting network slice instances that serve a terminal or determining Network Slice Selection Assistance Information (NSSAI).

[0039] AUSF may be an NF that performs functions to support authentication for 3GPP access and non-3GPP access.

[0040] An AF may be an NF that provides functions for a service according to the present disclosure.

[0041] DN may refer to a data network that may provide business services, Internet access, or third-party services.

[0042] FIG. 3 illustrates a procedure for changing network slice subscription information in a wireless communication system according to one embodiment of the present disclosure.

[0043] Referring to FIG. 3, at step 310, the terminal (UE) (300) may store Configured NSSAI information for a serving PLMN. The first Configured NSSAI may include a first S-NSSAI. The first S-NSSAI (S-NSSAI for network slice A) (or S-NSSAI A) may be stored in the UDM as a subscribed S-NSSAI (subscribed NSSAI), which is part of the terminal subscription information.

[0044] At step 312, terminal subscription information may be updated in the UDM (304). According to an embodiment of the present disclosure, an S-NSSAI (second S-NSSAI) (or S-NSSAI B) for a new network slice (Slice B) may be added to the subscribed NSSAI of the terminal. That is, the subscribed NSSAI may include the first S-NSSAI and the second S-NSSAI. The UDM may store an indicator (Network Slicing Subscription Change Indicator, NSSCI) indicating a change in network slice subscription information. The NSSCI may be an indicator indicating that a change has occurred in the subscribed NSSAI of the terminal. That is, when at least some of the S-NSSAIs included in the subscribed NSSAI are deleted and / or when a new S-NSSAI is added to the subscribed NSSAI, the UDM may store the NSSCI indicator. The NSSCI indicator does not indicate changes per S-NSSAI. That is, even if one or more S-NSSAIs are added to the subscribed NSSAI, or one or more S-NSSAIs are deleted, or both the addition and deletion of S-NSSAIs occur simultaneously, only one NSSCI indicator can be stored. The NSSCI indicator can be transmitted to the AMF and used to notify the AMF and / or NSSF that a new Configured NSSAI should be provided to the terminal. In addition, the newly added second S-NSSAI can be stored in the UDM together with the indicator. The indicator can be stored for each S-NSSAI. That is, when multiple S-NSSAIs are added to the subscribed NSSAI, the indicator can be stored for each added S-NSSAI. That is, as many indicators as the number of added S-NSSAIs can be stored.The indicator set for each S-NSSAI may be transmitted to the AMF to notify that the S-NSSAI should be included in the Allowed NSSAI determined by the AMF and / or NSSF for the terminal. The indicator set for each S-NSSAI may be an indicator indicating that the corresponding S-NSSAI is newly added. Alternatively, the indicator set for each S-NSSAI may be an indicator indicating that the corresponding S-NSSAI should be provided to the terminal. The change in network slice subscription information in step 312 may not yet be transmitted to the terminal.

[0045] At step 314, the terminal (300) may transmit a registration request message to the AMF (302). The terminal (300) may configure a Requested NSSAI (or R. NSSAI) based on the first Configured NSSAI set in the terminal (300). The Requested NSSAI may include S-NSSAI A included in the first Configured NSSAI, i.e., the first S-NSSAI.

[0046] At step 316, AMF (302) may transmit a terminal subscription information request message to UDM (304) to process the registration request message. The terminal subscription information request message may include a terminal ID.

[0047] At step 318, the UDM (304) may transmit terminal subscription information corresponding to the terminal ID requested from the AMF (302) to the AMF (318). The terminal subscription information may include the NSSCI indicator stored in the UDM (304) at step 312. Additionally, the terminal subscription information may include a subscribed NSSAI. The subscribed NSSAI may include a first S-NSSAI and a second S-NSSAI. The second S-NSSAI may be transmitted to the AMF (302) together with an indicator (e.g., a new additional network slice, etc.).

[0048] At step 320, the AMF (302) according to one embodiment of the present disclosure may determine the Allowed NSSAI. The Allowed NSSAI may be determined based on at least one of the Requested NSSAI received from the terminal, the subscribed NSSAI received from the UDM, and network slice information available at the current location of the terminal. The AMF (302) may be able to determine that there is a change in the subscribed NSSAI of the terminal based on the received NSSCI. In addition, the AMF (302) may be able to determine that the S-NSSAI is a newly added S-NSSAI to the terminal subscription information (subscribed NSSAI) based on an indicator (e.g., a new additional network slice) received together with the S-NSSAI constituting the subscribed NSSAI. For example, if AMF (302) receives subscribed S-NSSAI having NSSCI and / or indicator (e.g., new additional network slice) from UDM (304) at step 318, AMF may decide to include the subscribed S-NSSAI in Allowed NSSAI. At this time, AMF (302) may decide to include the subscribed S-NSSAI in Allowed NSSAI even if it is not included in Requested NSSAI. That is, according to one embodiment of the present disclosure, AMF (302) may include a first S-NSSAI and a second S-NSSAI in Allowed NSSAI. Since the first S-NSSAI is a network slice included in the Requested NSSAI requested by the terminal and the subscribed NSSAI received from UDM, AMF may decide to include it in Allowed NSSAI.In addition, the second S-NSSAI may be determined to be included in the Allowed NSSAI since it is a network slice stored with an indicator (e.g., a new additional network slice) in the subscribed NSSAI received from the UDM, although it is not included in the Requested NSSAI requested by the terminal. In addition, the AMF (302) may decide to transmit the Configured NSSAI to the terminal based on the received NSSCI. The AMF (302) may determine the second Configured NSSAI according to a change in network slice subscription information. The second Configured NSSAI may include at least some or all of the subscribed NSSAIs received from the UDM. The second Configured NSSAI may include the first S-NSSAI and the second S-NSSAI.

[0049] According to another embodiment of the present disclosure, the AMF (302) may determine the Allowed NSSAI through interaction with the NSSF (306). To determine the Allowed NSSAI, the AMF (302) and the NSSF (306) may perform steps 322 and 324.

[0050] At step 322, the AMF (302) may transmit a network slice selection request message to the NSSF (306). The network slice selection request message may include at least one of the Requested NSSAI (or R. NSSAI) received from the terminal and the subscribed NSSAI (or S. NSSAI) received from the UDM. The NSSF (306) may determine the Allowed NSSAI based on the information received from the AMF (302). For example, when a subscribed S-NSSAI having an indicator (e.g., a new additional network slice) is received, the NSSF (306) may decide to include the subscribed S-NSSAI in the Allowed NSSAI. At this time, the NSSF (306) may decide to include the subscribed S-NSSAI in the Allowed NSSAI even if the subscribed S-NSSAI is not included in the Requested NSSAI. That is, according to one embodiment of the present disclosure, NSSF (306) may include a first S-NSSAI and a second S-NSSAI in Allowed NSSAI. Since the first S-NSSAI is a network slice included in the Requested NSSAI requested by the terminal and the subscribed NSSAI received from the UDM, it may be decided to include it in Allowed NSSAI. In addition, although the second S-NSSAI is not included in the Requested NSSAI requested by the terminal, it may be decided to include it in Allowed NSSAI since it is a network slice stored in the subscribed NSSAI with an indicator (e.g., a new additional network slice). In addition, NSSF may determine a second Configured NSSAI according to a change in network slice subscription information. The second Configured NSSAI may include the first S-NSSAI and the second S-NSSAI.

[0051] At step 324, the NSSF (306) may transmit a network slice selection response message to the AMF (302). The response message may include an Allowed NSSAI (including the first S-NSSAI and the second S-NSSAI) determined by the NSSF. Additionally, the response message may include a second Configured NSSAI (including the first S-NSSAI and the second S-NSSAI) (or C. NSSAI) according to a change in network slice subscription information.

[0052] According to another embodiment of the present disclosure, the AMF (302) may determine the Allowed NSSAI through interaction with the NSSF (306). To determine the Allowed NSSAI, the AMF (302) and the NSSF (306) may perform steps 326 to 330.

[0053] At step 326, the AMF (302) may transmit a network slice selection request message to the NSSF (306). The network slice selection request message may include at least one of the Requested NSSAI received from the terminal and the subscribed NSSAI received from the UDM. The network slice selection request message may include only the subscribed S-NSSAI included in the subscribed NSSAI, and may not include an indicator (e.g., a new additional network slice) associated with the subscribed S-NSSAI. The NSSF may determine the Allowed NSSAI based on the information received from the AMF. For example, the NSSF may determine to include the S-NSSAI included in the subscribed NSSAI among the Requested NSSAIs in the Allowed NSSAI. That is, according to one embodiment of the present disclosure, the NSSF (306) may include the first S-NSSAI in the Allowed NSSAI. The first S-NSSAI may be included in the Allowed NSSAI because it is a network slice included in the Requested NSSAI requested by the terminal and the subscribed NSSAI received from the UDM. The second S-NSSAI may be included in the subscribed NSSAI, but may not be included in the Requested NSSAI requested by the terminal, so it may be decided not to be included in the Allowed NSSAI. In addition, the NSSF (306) may determine the second Configured NSSAI according to a change in network slice subscription information. The second Configured NSSAI may include the first S-NSSAI and the second S-NSSAI.

[0054] At step 328, the NSSF (306) may transmit a network slice selection response message to the AMF (302). The response message may include an Allowed NSSAI (including the first S-NSSAI) determined by the NSSF. Additionally, the response message may include a second Configured NSSAI (including the first S-NSSAI and the second S-NSSAI) according to a change in network slice subscription information.

[0055] At step 330, the AMF (302) may decide to add the second S-NSSAI to the Allowed NSSAI received from the NSSF (306) at step 328. That is, for example, the AMF (302) may decide to include the second S-NSSAI in the Allowed NSSAI because it is not included in the Requested NSSAI requested by the terminal and therefore not included in the Allowed NSSAI received from the NSSF, but is a network slice stored in the subscribed NSSAI with an indicator (e.g., a new additional network slice).

[0056] At step 332, the AMF (302) may transmit a registration response message to the terminal (300). The registration response message may include an Allowed NSSAI (including a first S-NSSAI and a second S-NSSAI) determined according to an embodiment of the present disclosure. Additionally, the registration response message may include a second Configured NSSAI and an NSSCI indicator. Based on the received Allowed NSSAI, the terminal may know that the terminal can access the network and use the first S-NSSAI and the second S-NSSAI. By knowing that the first S-NSSAI and the second S-NSSAI can be used, the terminal may establish a PDU session using the first S-NSSAI or the second S-NSSAI in a subsequent procedure.

[0057] In step 334, the terminal (300) may transmit a registration completion message to the AMF (302). The registration completion message may be a message sent in response to the terminal (300) receiving the NSSCI in step 332. That is, the registration completion message may be an acknowledgement message indicating that the terminal has received the second Configured NSSAI according to the Network Slicing Subscription Change in step 332.

[0058] AMF (302) that has received the registration response message can perform step 336, knowing that the terminal has successfully received the second Configured NSSAI according to the Network Slicing Subscription Change.

[0059] At step 336, the AMF (302) may transmit an SDM (Subscription Data Management) message to the UDM (304). The SDM message may be an acknowledgement message indicating that the second Configured NSSAI has been successfully transmitted to the terminal.

[0060] At step 338, the UDM (304) can delete the Network Slice Subscription Information Change Indicator (NSSCI) since the second Configured NSSAI according to the change in terminal subscription information has been successfully transmitted to the terminal. In addition, the UDM (304) can delete an indicator (e.g., a newly added network slice) stored together with the newly added S-NSSAI.

[0061] FIG. 4 illustrates a procedure for changing network slice subscription information in a wireless communication system according to one embodiment of the present disclosure.

[0062] Referring to FIG. 4, at step 410, terminal subscription information stored in the UDM (304) may include a subscribed NSSAI. The subscribed NSSAI may include a first S-NSSAI (S-NSSAI for network slice A) (or S-NSSAI A).

[0063] At step 412, the terminal (300) can transmit a registration request message to the AMF (302).

[0064] To process the registration request message, AMF (302) may request terminal subscription information from UDM (304) at step 414. The terminal subscription information request message may include a terminal ID.

[0065] At step 416, the UDM (304) may transmit terminal subscription information corresponding to the terminal ID to the AMF (302). The terminal subscription information may include the first subscribed NSSAI (including the first S-NSSAI).

[0066] At step 418, AMF (302) may store the first subscribed NSSAI as a terminal context. Step 418 may occur after step 420.

[0067] At step 420, the AMF (303) may transmit a registration response message to the terminal. The registration response message may include the first Configured NSSAI. The first Configured NSSAI may include the S-NSSAI included in the first subscribed NSSAI, i.e., the first S-NSSAI.

[0068] At step 422, the terminal (300) may store the first Configured NSSAI information for the received serving PLMN. The first Configured NSSAI may include the first S-NSSAI. The first S-NSSAI may be stored in the UDM as a subscribed S-NSSAI (subscribed NSSAI), which is part of the terminal subscription information.

[0069] After step 422, while the terminal is not registered to a network (e.g., a 5G network) (e.g., the terminal is powered off or connected to a 4G network, which is a different type of network), the terminal subscription information may be updated in step 424. According to one embodiment of the present disclosure, an S-NSSAI (second S-NSSAI) (or S-NSSAI B) for a new network slice (Slice B) may be added to the subscribed NSSAI of the terminal. That is, the second subscribed NSSAI may include the first S-NSSAI and the second S-NSSAI. An indicator indicating a change in network slice subscription information (Network Slicing Subscription Change Indicator, NSSCI) may be stored in the UDM (304). The network slice subscription information change in step 424 may not yet be transmitted to the terminal.

[0070] At step 426, the terminal (300) may transmit a registration request message to the AMF (302). The terminal may configure a Requested NSSAI (or R. NSSAI) based on the first Configured NSSAI set in the terminal. The Requested NSSAI may include S-NSSAI A included in the first Configured NSSAI, i.e., the first S-NSSAI.

[0071] At step 428, AMF (302) may transmit a terminal subscription information request message to UDM (304) to process the registration request message. The terminal subscription information request message may include a terminal ID.

[0072] At step 430, the UDM (304) may transmit terminal subscription information corresponding to the terminal ID requested from the AMF (302) to the AMF (302). The terminal subscription information may include the NSSCI indicator stored in the UDM (304) at step 424. Additionally, the terminal subscription information may include a second subscribed NSSAI. The second subscribed NSSAI may include a first S-NSSAI and a second S-NSSAI.

[0073] According to one embodiment of the present disclosure, the AMF (302) may determine the Allowed NSSAI in step 432. The Allowed NSSAI may be determined based on at least one of the Requested NSSAI received from the terminal, the subscribed NSSAI received from the UDM, the network slice information available at the current location of the terminal, and the terminal context.

[0074] For example, based on the received NSSCI, the AMF (302) may determine that there is a change in the subscribed NSSAI of the terminal. Accordingly, in order to determine which S-NSSAI is newly added or deleted from the existing subscribed NSSAI, the AMF (302) may compare the first subscribed NSSAI (including the first S-NSSAI) stored by the AMF (302) as the terminal context in step 418 with the second subscribed NSSAI (including the first S-NSSAI and the second S-NSSAI) received from the UDM (304) in step 430. Based on the comparison result, the AMF (302) may determine that the second S-NSSAI is a network slice newly added to the terminal subscription information. Accordingly, the AMF (302) may decide to include the newly added network slice, i.e., the second S-NSSAI, in the Allowed NSSAI. At this time, the AMF (302) may decide to include the subscribed S-NSSAI in the Allowed NSSAI even if it is not included in the Requested NSSAI. That is, according to one embodiment of the present disclosure, the AMF (302) may include the first S-NSSAI and the second S-NSSAI in the Allowed NSSAI. The first S-NSSAI may be determined to be included in the Allowed NSSAI because it is a network slice included in the Requested NSSAI requested by the terminal and the subscribed NSSAI received from the UDM. In addition, the second S-NSSAI may be determined to be included in the Allowed NSSAI because it is a newly added network slice, although it is not included in the Requested NSSAI requested by the terminal. In addition, the AMF (302) may decide to transmit the Configured NSSAI to the terminal based on the received NSSCI. The AMF (302) may determine the second Configured NSSAI according to a change in network slice subscription information.The second Configured NSSAI may include at least some or all of the subscribed NSSAIs received from the UDM. The second Configured NSSAI may include the first S-NSSAI and the second S-NSSAI.

[0075] Additionally, at step 432, AMF (302) can update the first subscribed NSSAI stored as a terminal context to the second subscribed NSSAI.

[0076] According to another embodiment of the present disclosure, the AMF (302) may determine the Allowed NSSAI through interaction with the NSSF (306). To determine the Allowed NSSAI, the AMF (302) and the NSSF (306) may perform steps 434 to 436.

[0077] At step 434, the AMF (302) may transmit a network slice selection request message to the NSSF (306). The network slice selection request message may include at least one of the Requested NSSAI (or R. NSSAI) received from the terminal and the subscribed NSSAI (or S. NSSAI) received from the UDM. In addition, the AMF (302) may transmit an indicator indicating that the second S-NSSAI is a newly added network slice (or an indicator indicating that the second S-NSSAI is a network slice that should be provided to the terminal) to the NSSF (306) based on the comparison result at step 432. The NSSF (306) may determine an Allowed NSSAI based on the information received from the AMF (302). For example, when a subscribed S-NSSAI having an indicator (e.g., a newly added network slice) is received, the NSSF (306) may decide to include the subscribed S-NSSAI in the Allowed NSSAI. At this time, NSSF (306) may decide to include the subscribed S-NSSAI in Allowed NSSAI even if it is not included in Requested NSSAI. That is, according to one embodiment of the present disclosure, NSSF (306) may include a first S-NSSAI and a second S-NSSAI in Allowed NSSAI. The first S-NSSAI may be decided to be included in Allowed NSSAI because it is a network slice included in the Requested NSSAI requested by the terminal and the subscribed NSSAI received from the UDM. In addition, the second S-NSSAI may be decided to be included in Allowed NSSAI because it is a newly added network slice, although it is not included in the Requested NSSAI requested by the terminal. In addition, NSSF (306) may determine the second Configured NSSAI according to a change in network slice subscription information.The second Configured NSSAI may include the first S-NSSAI and the second S-NSSAI.

[0078] At step 436, the NSSF (306) may transmit a network slice selection response message to the AMF (302). The network slice selection response message may include an Allowed NSSAI (including the first S-NSSAI and the second S-NSSAI) determined by the NSSF. In addition, the response message may include a second Configured NSSAI (including the first S-NSSAI and the second S-NSSAI) (or C. NSSAI) according to a change in network slice subscription information.

[0079] According to another embodiment of the present disclosure, the AMF (302) may determine the Allowed NSSAI through interaction with the NSSF (306). To determine the Allowed NSSAI, the AMF (302) and the NSSF (306) may perform steps 438 to 442.

[0080] At step 438, the AMF (302) may transmit a network slice selection request message to the NSSF (306). The network slice selection request message may include at least one of the Requested NSSAI received from the terminal and the subscribed NSSAI received from the UDM. The network slice selection request message may include only the subscribed S-NSSAI included in the subscribed NSSAI. Additionally, the network slice selection request message may not include an indicator (e.g., a new additional network slice) associated with the subscribed S-NSSAI. The NSSF (306) may determine the Allowed NSSAI based on the information received from the AMF (302). For example, the NSSF (306) may determine to include the S-NSSAI included in the subscribed NSSAI among the Requested NSSAIs in the Allowed NSSAI. That is, according to one embodiment of the present disclosure, the NSSF (306) may include the first S-NSSAI in the Allowed NSSAI. The first S-NSSAI may be determined to be included in the Allowed NSSAI because it is a network slice included in the Requested NSSAI requested by the terminal and the subscribed NSSAI received from the UDM. The second S-NSSAI may be included in the subscribed NSSAI, but may not be included in the Requested NSSAI requested by the terminal, so it may be determined not to be included in the Allowed NSSAI. In addition, the NSSF (306) may determine the second Configured NSSAI according to a change in network slice subscription information. The second Configured NSSAI may include the first S-NSSAI and the second S-NSSAI.

[0081] At step 440, the NSSF (306) may transmit a network slice selection response message to the AMF (302). The network slice selection response message may include an Allowed NSSAI (including a first S-NSSAI) determined by the NSSF (306). In addition, the network slice selection response message may include a second Configured NSSAI (including a first S-NSSAI and a second S-NSSAI) according to a change in network slice subscription information.

[0082] At step 442, the AMF (302) may decide to add the second S-NSSAI to the Allowed NSSAI received from the NSSF (306) at step 440. That is, for example, the AMF (302) may decide to include the second S-NSSAI in the Allowed NSSAI because it is a newly added network slice, even though it is not included in the Requested NSSAI requested by the terminal and therefore not included in the Allowed NSSAI received from the NSSF.

[0083] At step 444, the AMF (302) may transmit a registration response message to the terminal (300). The registration response message may include an Allowed NSSAI (including a first S-NSSAI and a second S-NSSAI) determined according to an embodiment of the present disclosure. Additionally, the registration response message may include a second Configured NSSAI and an NSSCI indicator. Based on the received Allowed NSSAI, the terminal (300) may know that the terminal (300) can access the network and use the first S-NSSAI and the second S-NSSAI. By knowing that the first S-NSSAI and the second S-NSSAI can be used, the terminal (300) may establish a PDU session using the first S-NSSAI or the second S-NSSAI in a subsequent procedure.

[0084] In step 446, the terminal (300) may transmit a registration completion message to the AMF (302). The registration completion message may be a message sent in response to the terminal (300) receiving the NSSCI in step 444. That is, the registration completion message may be an acknowledgement message indicating that the terminal has received the second Configured NSSAI according to the Network Slicing Subscription Change in step 444.

[0085] AMF (302) that has received the registration response message can perform step 448, knowing that the terminal has successfully received the second Configured NSSAI according to the Network Slicing Subscription Change.

[0086] At step 448, the AMF (302) may transmit a Subscription Data Management (SDM) message to the UDM (304). The SDM message may be an acknowledgement message indicating that the second Configured NSSAI has been successfully transmitted to the terminal.

[0087] At step 450, the UDM (306) can delete the network slice subscription information change indicator (NSSCI) as the second Configured NSSAI according to the terminal subscription information change has been successfully transmitted to the terminal.

[0088] According to one embodiment of the present disclosure, the AMF (302) may store the subscribed NSSAI as a terminal context in step 418 or step 432. When the AMF is changed (e.g., when a terminal movement, handover, terminal registration procedure, etc. occur), the AMF (302) may transmit the terminal context to the new AMF, and at this time, the subscribed NSSAI may be excluded from the terminal context and the remaining information may be transmitted to the new AMF. That is, the embodiment illustrated in FIG. 4 may be applicable only to the same AMF. The embodiment illustrated in FIG. 4 may not be applicable when the AMF is changed.

[0089] According to one embodiment of the present disclosure, the AMF and / or NSSF may transmit Allowed NSSAI including at least a part of S-NSSAI among the Configured NSSAI to the terminal at the same time as transmitting Configured NSSAI to the terminal through the procedure illustrated in FIG. 3 or 4. The S-NSSAI may be S-NSSAI not included in Requested NSSAI. The AMF and / or NSSF may perform the function illustrated in FIG. 3 or 4 under specific conditions (e.g., when receiving subscribed S-NSSAI together with an indicator indicating that it is a newly added network slice from UDM, etc.). The wireless communication system according to one embodiment of the present disclosure may simultaneously transmit new network slice configuration information and allowed slices to the terminal when a change in network slice terminal subscription information occurs according to the procedure illustrated in FIG. 3 or 4. Accordingly, the terminal may use the network slice added to the terminal subscription information without an additional registration request procedure. Through this, the wireless communication system may prevent a situation in which the terminal does not register and does not use the newly added network slice.

[0090] FIG. 5 illustrates the structure of a terminal according to one embodiment of the present disclosure.

[0091] Referring to FIG. 5, the terminal may include a transceiver (510), a control unit (520), and a storage unit (530). The transceiver (510), the control unit (520), and the storage unit (530) may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. For example, the terminal may include a transceiver (510) and a control unit (520). In addition, the transceiver (510), the control unit (520), and the storage unit (530) may be implemented in the form of a single chip.

[0092] The transceiver (510) is a general term for the receiving unit and the transmitting unit of the terminal, and can transmit and receive signals with a base station, another terminal, or a network entity. The signals transmitted and received with the base station may include control information and data. The transceiver (510) may, for example, receive system information from the base station and may receive a synchronization signal or a reference signal. To this end, the transceiver (510) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts the received signal. However, this is only one embodiment of the transceiver (510), and the components of the transceiver (510) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (510) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals. In addition, the transceiver (510) can receive a signal through a wireless channel and output it to the control unit (520), and transmit the signal output from the control unit (520) through the wireless channel. In addition, the transceiver (510) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a network entity through a wired or wireless network.

[0093] The storage unit (530) can store programs and data necessary for the operation of the terminal. In addition, the memory (530) can store control information or data included in signals obtained from the terminal. The storage unit (530) can be configured as a storage medium such as a ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0094] In the present disclosure, the control unit (520) may be defined as a circuit or application-specific integrated circuit, or at least one processor. The processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (520) may control the overall operation of the terminal according to the embodiment proposed in the present disclosure. For example, the control unit (520) may control the signal flow between each block to perform operations according to the flowchart described above.

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

[0096] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present invention.

[0097] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0098] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present invention via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present invention.

[0099] In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.

[0100] While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.

Claims

1. A method performed by an AMF (access and mobility management function) entity in a wireless communication system, A step of receiving, from a terminal (user equipment), a registration request message including a requested NSSAI including a first S-NSSAI (single network slice selection assistance information); A step of receiving a message including terminal subscription information including a second S-NSSAI and a network slicing subscription change indicator (NSSCI) from a UDM (unified data management) entity; and comprising a step of transmitting a registration response message including an allowed NSSAI including a third S-NSSAI to the terminal; The above second S-NSSAI is not included in the requested NSSAI but is included in the allowed NSSAI, 2. In claim 1, A method wherein said allowed NSSAI further comprises said first S-NSSAI.

3. In claim 1, the method comprises: A step of comparing the requested NSSAI and the terminal subscription information based on the NSSCI; and A method comprising the step of identifying a second S-NSSAI included in the terminal subscription information and not included in the requested NSSAI as the third S-NSSAI.

4. In claim 1, A method wherein the registration response message further includes the NSSCI.

5. In a method performed by a terminal (user equipment) in a wireless communication system, A step of transmitting a registration request message including a requested NSSAI including a first S-NSSAI (single network slice selection assistance information) to an AMF (access and mobility management function) entity; comprising the step of receiving a registration response message including an allowed NSSAI including a third S-NSSAI from the AMF entity; The above allowed NSSAI includes a second S-NSSAI that is not included in the above requested NSSAI, A method wherein the above second S-NSSAI is associated with terminal subscription information.

6. In claim 5, A method wherein said allowed NSSAI further comprises said first S-NSSAI.

7. In claim 5, A method, wherein the above registration response message further includes a network slicing subscription change indicator (NSSCI).

8. In the AMF (access and mobility management function) entity in a wireless communication system, transceiver; and A controller coupled with the above transmitter and receiver is included, The above controller, Receive a registration request message including a requested NSSAI including a first S-NSSAI (single network slice selection assistance information) from a terminal (user equipment), Receives a message including terminal subscription information including a second S-NSSAI and a network slicing subscription change indicator (NSSCI) from a UDM (unified data management) entity, It is set to transmit a registration response message including an allowed NSSAI including a third S-NSSAI to the terminal, The above second S-NSSAI is an AMF entity that is not included in the above requested NSSAI but is included in the above allowed NSSAI.

9. In claim 8, An AMF entity, wherein the above allowed NSSAI further includes the first S-NSSAI.

10. In claim 8, the controller, Based on the above NSSCI, compare the requested NSSAI with the terminal subscription information, An AMF entity configured to identify a second S-NSSAI included in the terminal subscription information and not included in the requested NSSAI as the third S-NSSAI.

11. In claim 9, The above registration response message further includes the NSSCI, an AMF entity.

12. In a wireless communication system, in the terminal (user equipment), transceiver; and A controller coupled with the above transmitter and receiver is included, The above controller, Sending a registration request message including a requested NSSAI including a first S-NSSAI (single network slice selection assistance information) to an MF (access and mobility management function) entity, is configured to receive a registration response message from the above AMF entity containing an allowed NSSAI including a third S-NSSAI, The above allowed NSSAI includes a second S-NSSAI that is not included in the above requested NSSAI, The above second S-NSSAI is associated with terminal subscription information.

13. In claim 12, The terminal, wherein the above allowed NSSAI further comprises the first S-NSSAI.

14. In claim 12, The above registration response message further includes a network slicing subscription change indicator (NSSCI).

Images