Method for starting slice logout inactive timer and user equipment

Abstract

One example of the present specification relates to a method performed by a user equipment (UE). The method may include receiving a REGISTRATION ACCEPT message or a CONFIGRATION UPDATE COMMAND message including an on-demand network slice selection assistance information (on-demand NSSAI), and a slice cancellation inactive timer (slice cancellation), the REGISTRATION ACCEPT message or the CONFIGRATION UPDATE COMMAND message including an on-demand network slice selection assistance information (on-demand NSSAI) and a slice cancellation inactive timer (slice cancellation). The on-demand NSSAI may include one or more on-demand single network slice selection assistance information (on-demand S-NSSAI) (s). The method may include, in a case where a PDU (Protocol Data Unit) session related to a first on-demand S-NSSAI has been released, and a user plane resource of a Multi-Access (MA) PDU session related to the first on-demand S-NSSAI does not exist, and a PDU session related to the first on-demand S-NSSAI does not exist, transmitting a PDU session to the first on-demand S-NSSAI. And a slice logout inactive timer of the first on-demand S-NSSAI is started.

Description

Technical Field

[0001] This specification relates to a 3GPP wireless communication system. Background Art

[0002] Thanks to the success of LTE (long term evolution) / LTE-Advanced (LTE-A), the fourth generation of mobile communications, interest in the next generation, the fifth generation (so-called 5G), of mobile communications is increasing, and research is ongoing.

[0003] The fifth generation of mobile communications defined by the International Telecommunication Union (ITU) refers to providing data transmission speeds of up to 20Gbps and an actual experienced transmission speed of at least 100Mbps regardless of location. Its official name is "IMT-2020". Fifth-generation mobile communications support multiple new numerologies or subcarrier spacing (SCS) to support a variety of services. For example, when the SCS is 15kHz, it supports wide areas in the traditional cellular band; when the SCS is 30kHz / 60kHz, it supports dense urban areas, lower latency, and wider carrier bandwidth; when the SCS is greater than or equal to 60kHz, it supports bandwidths greater than 24.25GHz to overcome phase noise.

[0004] NR frequency bands are defined as two frequency ranges: FR1 and FR2. FR1 is 410MHz–7125MHz, and FR2 is 24250MHz–52600MHz, which can represent millimeter waves (mmW).

[0005] For ease of explanation, in the frequency range used in the NR system, FR1 may stand for "sub 6GHz range" and FR2 may stand for "above 6GHz range" and is referred to as millimeter wave (mmW).

[0006] [Table 1]

[0007] The numerical values ​​of the frequency range of the NR system can vary. For example, as shown in Table 1 below, FR1 can include frequency bands from 410 MHz to 7125 MHz. That is, FR1 can include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 can include both licensed and unlicensed frequency bands. Unlicensed frequency bands can be used for various purposes, such as vehicular communications (e.g., autonomous driving).

[0008] Figure 1A wireless communication system is shown.

[0009] The 5GC (5G Core) network may include various components, Figure 1 Including Access and Mobility Management Function (AMF) 41, Session Management Function (SMF) 42, Policy Control Function (PCF) 43, User Plane Function (UPF) 44, Application Function (AF) 45, Unified Data Management (UDM) 46, Non-3GPP InterWorking Function (N3IWF) 49 corresponding to some of them.

[0010] The user equipment (UE) 10 is connected to a data network via the UPF 44 through the Next Generation Radio Access Network (NG-RAN).

[0011] The UE 10 may also receive data services via an untrusted non-3GPP access, such as a wireless local area network (WLAN). To connect the non-3GPP access to the core network, an N3IWF 49 may be provided.

[0012] Figure 2 This is a diagram showing an example of the structure of a wireless communication system from a node perspective.

[0013] like Figure 2 As shown, the UE is connected to the data network (DN) through the radio access network (RAN).

[0014] The Control Plane Function (CPF) node shown performs all or part of the functions of the Mobility Management Entity (MME), the Serving Gateway (S-GW), and the PDN Gateway (P-GW) for fourth-generation mobile communications. The CPF node includes the Access and Mobility Management Function (AMF) and the Session Management Function (SMF).

[0015] The User Plane Function (UPF) node shown is a type of gateway used to send and receive user data. The UPF node can perform all or part of the user plane functions of the S-GW and P-GW of fourth-generation mobile communications.

[0016] The Policy Control Function (PCF) shown is a node that controls operator policies.

[0017] The application function (AF) shown is a server for providing various services to UE.

[0018] The Unified Data Management (UDM) shown is a type of server that manages user information, such as a Home Subscriber Server (HSS) in fourth-generation mobile communications. The UDM stores and manages the user information in a Unified Data Repository (UDR).

[0019] The Authentication Server Function (AUSF) shown authenticates and manages the UE.

[0020] The Network Slice Selection Function (NSSF) shown is a node of the network slice, as described below.

[0021] A UE can be connected to two data networks simultaneously using multiple protocol data units or packet data unit (PDU) sessions.

[0022] Figure 3 FIG. 4 is another exemplary diagram showing the structure of a wireless communication system from a node perspective.

[0023] Figure 3 The architecture of a UE using one PDU session to access two data networks simultaneously is shown.

[0024] and Figure 2 and Figure 3 Matters related to the reference points shown are as follows.

[0025] N1 represents the reference point between UE and AMF.

[0026] N2 represents the reference point between (R)AN and AMF.

[0027] N3 represents the reference point between (R)AN and UPF.

[0028] N4 represents the reference point between SMF and UPF.

[0029] N5 represents the reference point between PCF and AF.

[0030] N6 represents the reference point between UPF and DN.

[0031] N7 represents the reference point between the SMF and the PCF.

[0032] N8 represents the reference point between UDM and AMF.

[0033] N9 represents the reference point between UPFs.

[0034] N10 represents the reference point between UDM and SMF.

[0035] N11 represents the reference point between AMF and SMF.

[0036] N12 represents the reference point between AMF and AUSF.

[0037] N13 represents the reference point between UDM and AUSF.

[0038] N14 represents the reference point between AMFs.

[0039] N15 represents the reference point between PCF and AMF.

[0040] N16 represents the reference point between SMFs.

[0041] N22 represents the reference point between AMF and NSSF.

[0042] N33 indicates the reference point between Network Exposure Function (NEF) and AF.

[0043] Figure 4 is a diagram showing an example of the structure of a radio interface protocol between a terminal and a network.

[0044] The radio interface protocol is based on the 3GPP radio access network specification. It horizontally comprises the physical layer, data link layer, and network layer, and vertically divides into the user plane for data information transmission and the control plane for control signal transmission.

[0045] The protocol layers may be divided into L1 (first layer), L2 (second layer), and L3 (third layer) based on the lower three layers of the well-known Open Systems Interconnection (OSI) reference model in communication systems.

[0046] The following describes each layer of the wireless interface protocol.

[0047] The physical layer, the first layer, provides information transfer services using physical channels. The physical layer connects to the upper-layer media access control layer via the transfer channel. Data between the media access control layer and the physical layer is transmitted via the transfer channel. Furthermore, data is transferred between different physical layers, that is, between the transmitting and receiving physical layers, via the physical channel.

[0048] The second layer includes a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer.

[0049] Layer 3 includes the Radio Resource Control (RRC) layer. The RRC layer is defined only in the control plane and is responsible for controlling logical, transport, and physical channels associated with the configuration, reconfiguration, and release of radio bearers (RBs). RBs represent services provided by Layer 2 for data transfer between terminals and the RAN.

[0050] The Non-Access Stratum (NAS) layer performs functions such as session management and mobility management.

[0051] The NAS layer is divided into NAS entities for mobility management (MM) and NAS entities for session management (SM).

[0052] 1) The NAS entity for MM generally provides the following functions.

[0053] NAS processes related to AMF include: -Registration management and connection management process. AMF supports the following functions: - Secure NAS signalling connection between UE and AMF (integrity protection, encryption).

[0054] 2) The NAS entity for SM performs session management between the UE and the SMF.

[0055] SM signalling messages are handled, i.e. generated and processed, in the NAS-SM layer of the UE and SMF. The content of SM signalling messages is not interpreted by the AMF.

[0056] -For SM signaling transmission, - The NAS entity for MM generates a NAS-MM message that guides the method and location for transmitting the SM signaling message through a security header indicating NAS transmission of SM signaling, additional information about the received NAS-MM.

[0057] - When receiving SM signaling, the NAS entity for SM performs an integrity check of the NAS-MM message and interprets the additional information to guide the method and location where the SM signaling message is to be derived.

[0058] On the other hand, Figure 4 In the NAS layer, the RRC layer, RLC layer, MAC layer, and PHY layer are bundled together, also known as the access layer (Access Stratum: AS).

[0059] The 5G network system (i.e., 5GC) also supports non-3GPP access. An example of non-3GPP access is typically WLAN access. The WLAN access can include both trusted WLANs and untrusted WLANs.

[0060] In the 5G system, AMF performs registration management (RM) and connection management (CM) for 3GPP access and non-3GPP access. Summary of the Invention

[0061] The disclosure of this specification aims to provide a method for starting a slice deregistration inactivity timer.

[0062] According to one embodiment of the present specification, a method performed by a user equipment (UE) is provided. The method may include: receiving a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message including on-demand Network Slice Selection Assistance Information (NSSAI) and a slice deregistration inactivity timer. The on-demand NSSAI may include one or more on-demand single-NSSAIs (S-NSSAIs). The method may also include: when a protocol data unit (PDU) session associated with a first on-demand S-NSSAI is released, there are no user plane resources for a multiple access (MA) PDU session associated with the first on-demand S-NSSAI, and the PDU session associated with the first on-demand S-NSSAI does not exist, starting the slice deregistration inactivity timer for the first on-demand S-NSSAI.

[0063] According to one embodiment of the present specification, a user equipment (UE) is provided. The UE may include: a transmitting / receiving unit; and a processor that controls the transmitting / receiving unit to perform operations. The operations performed by the processor may include: receiving a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message containing an on-demand NSSAI and a slice deregistration inactivity timer; wherein the on-demand NSSAI may include one or more on-demand S-NSSAIs. The operations may also include: starting the slice deregistration inactivity timer for a first on-demand S-NSSAI when the following conditions are met, namely, the PDU session associated with the first on-demand S-NSSAI is released, the user plane resources of the MA PDU session do not exist, and the PDU session associated with the first on-demand S-NSSAI does not exist.

[0064] According to another embodiment of the present specification, a chipset installed in a user equipment (UE) is provided. The chipset may include: at least one processor; and at least one memory that can store instructions and can be electrically connected to the at least one processor for operation. Based on the execution of the instructions by the at least one processor, the operations performed may include: receiving a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message containing an on-demand NSSAI and a slice deregistration inactivity timer; wherein the on-demand NSSAI includes one or more on-demand S-NSSAIs. The operations may also include: starting the timer for the first on-demand S-NSSAI when the PDU session related to the first on-demand S-NSSAI is released, the user plane resources of the MA PDU session do not exist, and there are no other PDU sessions.

[0065] According to another embodiment of the present specification, a non-volatile computer-readable storage medium having recorded thereon instructions is provided. The storage medium includes instructions, and when the instructions are executed by one or more processors in a device, the one or more processors perform the following operations: receiving a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message containing an on-demand NSSAI and a slice deregistration inactivity timer; wherein the on-demand NSSAI includes one or more on-demand S-NSSAIs. The operation also includes: when a PDU session related to a first on-demand S-NSSAI has been released, user plane resources for an MA PDU session do not exist, and there is no PDU session, starting the timer for the first on-demand S-NSSAI.

[0066] According to the disclosure of this specification, the start or stop operation of the slice deregistration inactivity timer can also be performed. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 A wireless communication system is shown.

[0068] Figure 2 This is a diagram showing an example of the structure of a wireless communication system from a node perspective.

[0069] Figure 3 FIG. 4 is another exemplary diagram showing the structure of a wireless communication system from a node perspective.

[0070] Figure 4 is a diagram showing an example of the structure of a radio interface protocol between a terminal and a network.

[0071] Figure 5A and5B is a signal flow diagram illustrating an exemplary registration process.

[0072] Figure 6A and 6B is a signal flow diagram illustrating an exemplary PDU session establishment process.

[0073] Figure 7A and 7B is a signal flow diagram illustrating an exemplary PDU session modification process.

[0074] Figure 8A An example diagram illustrating the concept of network slicing.

[0075] Figure 8B is a flow chart according to an embodiment of this specification.

[0076] Figure 9 A block diagram illustrating a configuration of a terminal according to an embodiment of the present disclosure.

[0077] Figure 10 A block diagram of a configuration of a processor in which the present disclosure is implemented is shown. DETAILED DESCRIPTION

[0078] It should be noted that the technical terms used in this manual are only used to describe specific embodiments and are not intended to limit the content of this manual. In addition, unless particularly defined in this article with other meanings, the technical terms used in this article should be interpreted as the meaning generally understood by those of ordinary skill in the art to which this disclosure belongs, and should not be interpreted as too comprehensive or too narrow meaning. In addition, when the technical terms used in this manual are the wrong technical terms that cannot correctly express the content of this manual and thought, the technical terms that can be correctly understood by those skilled in the art should be replaced to understand. In addition, general terms used herein should be interpreted according to previous definition or according to context, and should not be interpreted with the implication of excessive reduction.

[0079] In addition, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" used herein include plural forms. In the present application, the term "configuration" or "branch" should not be interpreted as including any of the multiple elements or multiple steps described in the specification, but may exclude some of the elements or steps, or may further include additional elements or steps.

[0080] In addition, terms including ordinal numbers, such as first, second, etc., used herein may be used to describe various elements, but these elements should not be limited by these terms. The terms are only used to distinguish one component from another. For example, a first component may be named a second component, and similarly, a second component may be named a first component without departing from the scope of the invention.

[0081] When it is mentioned that a component is connected or connected to another component, it can be directly connected or connected to the other component, but another component can exist in between. On the other hand, when it is mentioned that a certain component is directly connected or directly connected to another component, it should be understood that another component does not exist in between.

[0082] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings, wherein the same or similar elements are given the same reference numerals regardless of the reference numerals, and repeated descriptions thereof are omitted. In addition, when describing the contents of this specification, if it is determined that a detailed description of the relevant known technology will obscure the gist of this specification, its detailed description will be omitted. It should also be noted that the drawings are only for facilitating the understanding of the content and spirit of this specification and should not be interpreted as limiting the content and ideas of this specification. In addition to the drawings, the content and spirit of this specification should be understood to extend to all modifications, equivalents or alternatives.

[0083] In this specification, "A or B" may mean "only A," "only B," or "A and B." In other words, "A or B" herein may be interpreted as "A and / or B." For example, "A, B, or C" herein may mean "only A," "only B," "only C," or "any and all combinations of A, B, and C."

[0084] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Thus, "A / B" can mean "only A," "only B," or "A and B." For example, "A, B, C" can mean "A, B, or C."

[0085] In this specification, "at least one A and B" may mean "only A", "only B", or "both A and B". In addition, herein, the expression "at least one A or B" or "at least one A and / or B" may be interpreted as being the same as "at least one A and B".

[0086] Furthermore, as used herein, “at least one of A, B, and C” may mean “only A,” “only B,” “only C,” or “any and all combinations of A, B, and C.” Furthermore, “at least one of A, B, or C” or “at least one of A, B, and / or C” may mean “at least one of A, B, and C.”

[0087] Furthermore, brackets used herein may indicate "for example." Specifically, when referring to "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDDCH" may be proposed as an example of "control information." Furthermore, even when labeled "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0088] The technical features described separately in one drawing in this document can be implemented separately or simultaneously.

[0089] Although a user equipment (UE) is exemplarily shown in the drawings, the UE shown may be referred to as a terminal (UE 100), a mobile equipment (ME), etc. In addition, the UE may be a portable device such as a notebook, a mobile phone, a PDA, a smart phone, a multimedia device, etc., or a non-portable device such as a PC, a vehicle-mounted device, etc.

[0090] <Definition of terms> CIoT: The abbreviation of Cellular Internet of Things, which means it is based on IoT communication.

[0091] Control plane CIoT optimization: Signaling optimization on the control plane, which allows efficient transmission of user data (IP-based or non-IP-based or SMS-based user data).

[0092] User Plane CIoT Optimization: Signaling optimization on the user plane that allows efficient transmission of user data (IP-based or non-IP-based or SMS-based user data).

[0093] CIoT-optimized UEs: UEs that support control plane CIoT optimization or user plane CIoT optimization and one or more other CIoT optimizations. <Registration Process> The UE needs to obtain authorization to enable mobility tracking, data reception, and service reception. To do this, the UE must register with the network. The registration process is performed when the UE initially registers with the 5G system. Furthermore, the registration process is performed when the UE performs periodic registration updates, when it moves from idle mode to a new tracking area (TA), and when the UE needs to perform periodic registration updates.

[0094] During the initial registration process, the UE ID can be obtained from the UE. The AMF can deliver the PEI (IMEISV) to the UDM, SMF and PCF.

[0095] Figure 5A and 5B is a signal flow diagram illustrating an exemplary registration process.

[0096] 1) The UE may send an AN message to the RAN. The AN message may include AN parameters and a registration request message. The registration request message may include information such as registration type, subscriber permanent ID or temporary user ID, security parameters, NSSAI, UE's 5G capabilities, and PDU session status.

[0097] In the case of 5G RAN, the AN parameters may include SUPI or Temporary User ID, selected network and NSSAI.

[0098] The Registration Type may indicate whether the UE is an "Initial Registration" (i.e., the UE is in a non-registered state), a "Mobility Registration Update" (i.e., the UE is in a registered state and the registration procedure is started due to mobility), or a "Periodic Registration Update" (e.g., the UE is in a registered state and the registration procedure is started due to expiration of the periodic update timer); if a Temporary User ID is included, it indicates the last serving AMF. If the UE has registered over a non-3GPP access in a PLMN different from the 3GPP access PLMN, the UE may not provide the UE Temporary ID assigned by the AMF during the registration procedure over the non-3GPP access.

[0099] Security parameters can be used for authentication and integrity protection.

[0100] The PDU session status indicates the (previously established) PDU sessions available at the UE.

[0101] 2) If the included SUPI or Temporary User ID does not indicate a valid AMF, the RAN may select an AMF based on the (R)AT and NSSAI.

[0102] If the AN cannot select a suitable AMF, it selects any AMF according to local policy and forwards the registration request to the selected AMF. If the selected AMF cannot serve the UE, the selected AMF selects another more suitable AMF for the UE.

[0103] 3) The RAN sends an N2 message to the new AMF. The N2 message includes N2 parameters and a registration request. The registration request may include registration type, subscriber permanent identifier or temporary user ID, security parameters, NSSAI and MICO mode default settings, etc.

[0104] When using 5G-RAN, the N2 parameters include location information associated with the cell where the UE resides, the cell identifier, and the RAT type.

[0105] If the registration type indicated by the UE is periodic registration update, process 4-17 described below may not be performed.

[0106] 4) The newly selected AMF may send an information request message, such as Namf_Communication_UEContextTransfer, to the previous AMF.

[0107] If the UE’s Temporary User ID was included in the Registration Request message and the serving AMF has changed since the last registration, the new AMF may send an Information Request message including the complete Registration Request information to the previous AMF to request the UE’s SUPI and MM context.

[0108] 5) The previous AMF sends an information response message, such as Namf_Communication_UEContextTransfer response, to the newly selected AMF. The information response message may include SUPI, MM context and SMF information.

[0109] Specifically, the previous AMF sends an information response message including the UE's SUPI and MM context.

[0110] - If the previous AMF has information about an active PDU session, the previous AMF may include SMF information including the ID of the SMF and the PDU session ID in the information response message.

[0111] 6) If the UE does not provide the SUPI or does not retrieve the SUPI from the previous AMF, the new AMF sends an Identity Request message to the UE.

[0112] 7) The UE sends an Identity Response message including the SUPI to the new AMF.

[0113] 8) AMF may decide to trigger AUSF. In this case, AMF may select AUSF based on SUPI.

[0114] 9) AUSF can start authenticating UE and NAS security functions.

[0115] 10) The new AMF may send a Namf_Communication_RegistrationCompleteNotify message to the previous AMF.

[0116] 11) The new AMF may send an Identity Request message to the UE.

[0117] If the UE does not provide the PEI or has not retrieved the PEI from the AMF previously, an Identity Request message may be sent in order for the AMF to retrieve the PEI.

[0118] 12) The new AMF check identifier.

[0119] 13) If the following procedure 14 is performed, the new AMF selects the UDM based on the SUPI.

[0120] 14) The new AMF performs a registration process in the UDM.

[0121] 15) The new AMF may select the PCF based on the SUPI.

[0122] 16) The new AMF shall establish a policy association with the PCF.

[0123] 17) The new AMF sends a PDU session update SM context message or a PDU session release SM context message to the SMF.

[0124] 18-19) The new SMF sends an AMF mobility request message to N3IWF and receives a mobility response message from the AMF.

[0125] 20) The previous AMF sends a UE context termination request message to the PCF.

[0126] If the previous AMF previously requested to establish a UE context in the PCF, the previous AMF may delete the UE context from the PCF.

[0127] 21) The PCF sends a UE Context Termination Accept message to the previous AMF.

[0128] 22) The new AMF sends a Registration Accept message to the UE. The Registration Accept message may include the Temporary User ID, Registration Area, Mobility Restriction, PDU Session Status, NSSAI, Periodic Registration Update Timer, and Allowed MICO Modes.

[0129] When the AMF allocates a new temporary user ID, the temporary user ID may be further included in the Registration Accept message. If mobility restrictions are applied to the UE, information indicating mobility restrictions may be further included in the Registration Accept message. The AMF may include information indicating the PDU session status of the UE in the Registration Accept message. The UE may remove any internal resources associated with a PDU session that is not indicated as active in the received PDU session status. If PDU session status information is in the Registration Request, the AMF may include information indicating the PDU session status to the UE in the Registration Accept message.

[0130] 23) The UE sends a registration completion message to the new AMF.

[0131] <PDU Session Establishment Process> The protocol data unit (PDU) session establishment process can have two types of PDU session establishment processes: - A PDU session establishment process initiated by the UE.

[0132] - A PDU session establishment process initiated by the network. For this, the network can send a trigger message to the UE's application.

[0133] Figure 6A and 6B are signal flow diagrams showing exemplary PDU session establishment processes.

[0134] Figure 6A and 6B The processes shown assume that the UE has registered with the AMF according to the registration process. Therefore, it is assumed that the AMF has obtained the user subscription data from the UDM.

[0135] 1) The UE sends a NAS message to the AMF. The message can include single network slice selection assistance information (S-NSSAI), data network name (DNN), PDU session ID, request type, session management (N1 SM) information, etc.

[0136] Specifically, the UE includes the S-NSSAI of the allowed NSSAI from the current access type. If information about the mapped NSSAI is provided to the UE, the UE can provide the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the information of the mapped NSSAI. Among them, the information of the mapped NSSAI is the information that maps each S-NSSAI of the allowed NSSAI to the S-NSSAI in the NSSAI set for the home public land mobile network (HPLMN).

[0137] More specifically, the UE can extract and store the information of the allowed S-NSSAI and the mapped S-NSSAI included in the registration acceptance message received from the network (i.e., the AMF) during the registration process. Therefore, the UE can send by including both the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the information of the mapped NSSAI in the PDU session establishment request message.

[0138] To establish a new PDU session, the UE may generate a new PDU session ID.

[0139] The UE may initiate a UE-initiated PDU session establishment procedure by sending a NAS message including a PDU session establishment request message in the N1 SM information. The PDU session establishment request message may include a request type, session and service continuity (SSC) mode, and protocol configuration options.

[0140] When the PDU Session Establishment is used to establish a new PDU Session, the Request Type indicates “Initial Request.” However, if there is an existing PDU Session between the 3GPP access and the non-3GPP access, the Request Type may indicate “Existing PDU Session.”

[0141] The NAS message sent by the UE is encapsulated by the AN in an N2 message. The N2 message is sent to the AMF and may include user location information and access technology type information.

[0142] - N1 SM information may include an SM PDU DN request container, which includes information about PDU session authentication of the external DN.

[0143] 2) If the message indicates that the request type is "initial request" and if the PDU Session ID is not used for an existing PDU Session of the UE, the AMF may determine that the message corresponds to a request for a new PDU Session.

[0144] If the NAS message does not include S-NSSAI, the AMF may determine the default configuration S-NSSAI for the requested PDU Session based on the UE subscription. The AMF may store the PDU Session ID in association with the SMF ID.

[0145] The AMF may select SMF.

[0146] 3) AMF may send the Nsmf_PDUSession_CreateSMContext request message or the Nsmf-PDUSession-UpdateSMContext request message to the selected SMF.

[0147] The Nsmf_PDUSession_CreateSMContext request message may include: SUPI (Subscription Permanent Identifier), DNN, S-NSSAI (s), PDU Session ID, AMF ID, Request Type, PCF ID, Priority Access, N1 SM container, User location information, Access Type, PEI (Permanent Equipment Identifiers), GPSI (Generic Public Subscription Identifier), UE presence in LADN service area, Subscriptions For PDU Session Status Notification, DNN Selection Mode, and Trace Requirements. The SM container may include a PDU session establishment request message.

[0148] The Nsmf_PDUSession_UpdateSMContext request message may include SUPI, DNN, S-NSSAI(s), SM context ID, AMF ID, request type, N1 SM container, user location information, access type, RAT type and PEI. The N1 SM container may include a PDU session establishment request message.

[0149] The AMF ID is used to identify the AMF serving the UE. The N1 SM information may include the PDU Session Establishment Request message received from the UE.

[0150] 4) The SMF sends a Subscriber Data Request message to the UDM. The Subscriber Data Request message may include the subscriber's permanent ID and DNN. The UDM may send a Subscribe Data Response message to the SMF.

[0151] In the above process 3, if the request type indicates "existing PDU session", the SMF determines that the request is due to handover between 3GPP access and non-3GPP access. The SMF can identify the existing PDU session based on the PDU session ID.

[0152] If the SMF has not yet retrieved the SM-related subscription data for the UE associated with the DNN, the SMF may request the subscription data.

[0153] The subscription data may include information about the authentication request type, authentication SSC mode, and basic QoS profile.

[0154] The SMF may check whether the UE request complies with the user subscription and local policy. Alternatively, the SMF rejects the UE request via NAS SM signalling (including the relevant SM rejection cause) sent by the AMF, and the SMF informs the AMF that the PDU Session ID should be considered released.

[0155] 5) SMF sends Nsmf_PDUSession_CreateSMContext Response message or Nsmf_PdUSession_UpdateSMContext ReSponse message to AMF.

[0156] The Nsmf_PDUSession_CreateSMContext Response message may include a cause, an SM context ID, or an N1 SM container. The N1 SM container may include a PDU session rejection.

[0157] In the above process 3, if the SMF has received the Nsmf_PDUSession_CreateSMContext request message and the SMF is able to process the PDU session establishment request message, the SMF generates an SM context and transmits the SM context ID to the AMF.

[0158] 6) Optionally perform a second authentication / authorization.

[0159] 7a) When dynamic PCC (Policy and Charging Control) is used for a PDU session, the SMF selects the PCF.

[0160] 7b) The SMF performs the SM policy association establishment process to establish an SM policy association with the PCF.

[0161] 8) If the request type in process 3 indicates "initial request", the SMF selects the SSC mode for the PDU session. If process 5 is not performed, the SMF may also select the UPF. For request types IPv4 or IPv6, the SMF may allocate an IP address / prefix for the PDU session.

[0162] 9) SMF performs the SM policy association modification process to provide information about the policy control request tree conditions.

[0163] 10) The request type indicates "initial request". The SMF can use the selected UPF to initiate the N4 session establishment process, otherwise it can use the selected UPF to initiate the N4 session modification process.

[0164] 10a) The SMF sends an N4 Session Establishment / Modification Request message to the UPF. Furthermore, the SMF may provide packet detection, enforcement, and reporting rules to be installed in the UPF for the PDU session. When the SMF is assigned CN tunnel information, the CN tunnel information may be provided to the UPF.

[0165] 10b) The UPF may respond by sending an N4 Session Establishment / Modification Response message. When the CN tunnel information is allocated by the UPF, the CN tunnel information may be provided to the SMF.

[0166] 11) The SMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF. The Namf_Communication_N1N2MessageTransfer message may include the PDU session ID, N2 SM information and N1 SM container.

[0167] The N2 SM information may include: PDU Session ID, QFI (QoS Flow ID), QoS Profile(s), CN Tunnel Information, S-NSSAI from the Allowed NSSAI, Session-AMBR (Aggregate Maximum BitRate), PDU Session Type, User Plane Security Enforcement information, and UE Integrity Protection Maximum Data Rate.

[0168] The N1 SM container may include a PDU session establishment accept message.

[0169] The PDU session establishment accept message may include authorized QoS rules, SSC mode, S-NSSAI, and allocated IPv4 address.

[0170] 12) The AMF sends an N2 PDU Session Request message to the RAN. The message may include N2 SM information and a NAS message. The NAS message may include a PDU Session ID and a PDU Session Establishment Accept message.

[0171] The AMF may send a NAS message including the PDU Session ID and the PDU Session Establishment Accept message. In addition, the AMF includes the N2 SM information received from the SMF in the N2 PDU Session Request message and sends it to the RAN.

[0172] 13) The RAN may exchange specific signaling with the UE associated with the information received from the SMF.

[0173] The RAN also allocates RAN N3 tunnel information for the PDU session.

[0174] The RAN sends the NAS message provided in step 10 to the UE. The NAS message may include a PDU session ID and N1 SM information. The N1 SM information may include a PDU session establishment accept message.

[0175] The RAN sends a NAS message to the UE only when the required RAN resources are established and the allocation of the RAN tunnel information is successful.

[0176] 14) The RAN sends an N2 PDU Session Response message to the AMF. The message may include the PDU Session ID, cause, and N2 SM information. The N2 SM information may include the PDU Session ID, (AN) tunnel information, and a list of allowed / rejected QoS profiles.

[0177] -RAN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.

[0178] 15) The AMF may send an Nsmf_PDUSession_UpdateSMContext request message to the SMF. The Nsmf_PDUSession_UpdateSMContext request message may include N2 SM information. The AMF may forward the N2 SM information received by the RAN to the SMF.

[0179] 16a) If an N4 session has not been established for the PDU session, the SMF may initiate an N4 session establishment procedure with the UPF. Otherwise, the SMF may initiate an N4 session modification procedure with the UPF. The SMF may provide both AN tunnel information and CN tunnel information. The CN tunnel information may only be provided if the SMF selected the CN tunnel information in step 8.

[0180] 16b) The UPF may send an N4 session modification response message to the SMF.

[0181] 17) The SMF sends an Nsmf_PDUSession_UpdateSMContext Response message to the AMF.

[0182] After this process ends, the AMF can convey relevant events to the SMF.

[0183] 18) The SMF sends an Nsmf_PDUSession_SMContextStatusNotify message.

[0184] 19) The SMF sends information to the UE via the UPF. Specifically, in the case of the PDU type IPv6, the SMF can generate an IPv6 router advertisement and send it to the UE via N4 and the UPF.

[0185] 20) If the PDU session establishment is not successful during the process, the SMF notifies the AMF.

[0186] <PDU Session Modification Process> The protocol data unit (PDU) session establishment process can have two types of PDU session establishment processes: - The PDU session establishment process initiated by the UE.

[0187] - The PDU session establishment process initiated by the network. For this, the network can send a device trigger message to the UE's application.

[0188] Figure 7A and 7B is a signal flow diagram showing an exemplary PDU session modification process.

[0189] The PDU session can be established / managed based on the PDU session modification process.

[0190] The PDU session modification process can be initiated by the UE or by the network.

[0191] 1a) When initiated by the UE, the UE can initiate the PDU session modification process by sending a NAS message. The NAS message can include an N1 SM container. The N1 SM container can include information about the PDU session modification request message, the PDU session ID, and the UE's maximum data rate for integrity protection. The PDU session modification request message can include the PDU session ID, packet filters, information about the requested QoS, 5GSM (5G session management) core network capabilities, and the number of packet filters. The UE's maximum data rate for integrity protection refers to the maximum data rate that the UE can support for UP integrity protection. The number of packet filters represents the number of packet filters supported by the QoS rules.

[0192] The NAS message is forwarded via the RAN to the appropriate AMF based on the UE's location information. The AMF then sends an Nsmf_PDUSession_UpdateSMContext message to the SMF. This message may include the Session Management (SM) Context ID and the N1 SM container. The N1 SM container may include the PDU Session Modification Request message.

[0193] 1b) When initiated by the PCF in a network node, the PCF may notify the SMF of policy changes by initiating an SM policy association modification procedure.

[0194] 1c) When initiated by the UDM in the network node, the UDM can update the subscription data of the SMF by sending a Nudm_SDM_Notification message. The SMF can update the session management subscriber data and send an ACK message to the UDM.

[0195] 1d) When initiated by the SMF in a network node, the SMF can trigger a QoS update.

[0196] When triggered according to 1a-1d above, the SMF may perform the PDU session modification procedure.

[0197] 1e) When the RAN in a network node initiates the release of AN resources mapped to a QoS flow, the RAN may notify the SMF. The RAN may send an N2 message to the AMF. The N2 message may include the PDU session ID and N2 SM information. The N2 SM information may include the QFI (QoS flow ID), user location information, and an indication that the QoS flow is released. The AMF may send an Nsmf_PDUSession_UpdateSMContext message. This message may include the SM context ID and N2 SM information.

[0198] 2) The SMF may send a report of the subscription event by executing the SM Policy Alliance Modification procedure. This step may be skipped if the PDU Session Modification procedure is triggered by 1b or 1d. If dynamic PCC is not deployed in the network, the SMF may apply internal policies to determine the change in QoS profile.

[0199] If the PDU session modification only requires the operation of the UPF, the following processes 3 to 7 may not be performed.

[0200] 3a) When initiated by the UE or RAN, the SMF may respond to the AMF by sending an Nsmf_PDUSession_UpdateSMContext message. The message may include N2 SM information and an N1 SM container. The N2 SM information may include the PDU session ID, QFI, QoS profile, and session AMBR. The N1 SM container may include a PDU session modification command. The PDU session modification command may include the PDU session ID, QoS rule, QoS rule operation, QoS parameters per QoS flow, and session AMBR.

[0201] The N2 SM information may include information that the AMF should pass to the RAN. The N2 SM information may include a QFI and QoS profile to inform the RAN that one or more QoS flows have been added or modified. If a UE without established user plane resources requests a PDU session modification, the N2 SM information to be passed to the RAN may include information about the establishment of user plane resources.

[0202] The N1 SM container may include a PDU session modification command that causes the AMF to forward the command to the UE. The PDU session modification command may include QoS rules and QoS flow level QoS parameters.

[0203] 3b) When initiated by the SMF, the SMF may send a Namf_Communication_N1N2MessageTransfer message. The message may include N2 SM information and an N1 SM container. The N2 SM information may include the PDU session ID, QFI, QoS profile, and session AMBR. The N1 SM container may include a PDU session modification command. The PDU session modification command may include the PDU session ID, QoS rules, and QoS flow-level QoS parameters.

[0204] If the UE is in the CM (Connection Management)-IDLE state and ATC (Asynchronous Type Communication) is activated, the AMF updates and stores the UE context based on the Namf_Communication_N1N2MessageTransfer message, and then skips the following procedures 3 to 7. When the UE enters the reachable state, that is, when the UE enters the CM-CONNECTED state, the AMF may send an N1 message to synchronize the UE context with the UE.

[0205] 4) The AMF may send an N2 PDU Session Request message to the RAN. The N2 PDU Session Request message may include the N2 SM information and NAS message received from the SMF. The NAS message may include the PDU Session ID and the N1 SM container. The N1 SM container may include the PDU Session Modify Command.

[0206] 5) The RAN exchanges AN signaling with the UE, and the UE is associated with the information received from the SMF. For example, in the case of NG-RAN, an RRC connection reconfiguration procedure with the UE can be performed to modify the necessary AN resources associated with the PDU session.

[0207] 6) The RAN sends an N2 PDU Session ACK message in response to the received N2 PDU Session Request. The N2 PDU Session ACK message may include N2 SM information and user location information. The N2 SM information may include a list of accepted / rejected QFIs, AN tunnel information, PDU Session ID, etc.

[0208] 7a) and 7b) The AMF forwards the N2 SM information and user location information received from the RAN to the SMF via the Nsmf_PDUSession_UpdateSMContext message. The SMF then sends the Nsmf_PDUSession_UpdateSMContext message to the AMF.

[0209] 8a), 8b) The SMF sends an N4 session modification request message to the UPF to update the N4 session of the UPF included in the PDU session modification.

[0210] In the case of generating a new QoS flow, the SMF and the UPF together update the UL packet detection rules of the new QoS flow.

[0211] 9) In response to receiving the PDU session modification command, the UE sends a NAS message. The NAS message may include the PDU session ID and an N1 SM container. The N1 SM container may include a PDU session modification command ACK.

[0212] 10) The RAN sends the NAS message to the AMF.

[0213] 11a) and 11b) The AMF may forward the N1 SM container and user location information received from the RAN to the SMF via an Nsmf_PDUSession_UpdateSMContext message. The N1 SM container may include a PDU session modification command ACK. The SMF may send an Nsmf_PDUSession_UpdateSMContext response message to the AMF.

[0214] 12a) and 12b) the SMF sends an N4 session modification request message to the UPF to update the UPF's N4 session included in the PDU session modification. The message may include an N4 session ID.

[0215] 13) If the SMF interacts with the PCF in step 1b or step 2, the SMF may inform the PCF whether the PCC decision can be executed through the SM policy association modification procedure.

[0216] The SMF may notify the requesting entity of user location information associated with the PDU session change.

[0217] Network Slicing Figure 8A This is an example diagram used to illustrate the concept of network slicing.

[0218] Network slicing involves dividing a physical network into multiple virtual networks. Each network can be customized and optimized for specific application services or subscribers. Leveraging cloud computing and virtualization technologies, shared physical network resources can be dynamically and efficiently allocated to logical network slices based on changing user needs.

[0219] A 5G network slice consists of a collection of network functions and settings for a specific use case or business model. Figure 8A , Network Slice 1 represents eMBB (enhanced Mobile Broadband), Network Slice 2 represents V2X (Vehicle-to-Everything), and Network Slice 3 represents an example of 5G network slicing to which MIoT (Mass IoT) is applied.

[0220] A network slice can span several domains, including distributed cloud infrastructure, the radio access network (RAN), the transport network, and the core network. The fundamental principle of 5G network slicing design is to provide only the customized functionality required to handle traffic for specific use cases. Network slices possess the necessary customization capabilities and the ability to adapt to changing requirements.

[0221] On the other hand, according to the Next Generation Mobile Networks (NGMN) definition, network slicing consists of three layers: the Service Instance Layer, the Network Slice Instance Layer, and the Resource Layer. The Service Instance Layer represents end-user services, with each service represented by a Service Instance. The Network Slice Service Instance Layer includes the provided network slice instances and provides them with the network features required by the service instances. The Resource Layer provides all virtual or physical resources and network functions required to create a network slice instance.

[0222] In the 3GPP 5G mobile communications network, currently under development by the DetNet (Deterministic Networking) WG (Working Group) of the Internet Engineering Task Force (IETF), network slicing is operated based on the Core Network (CN) and primarily on network slice instance information. A network slice instance is the aggregate information of the resources and network function instances required to form a network slice. A network slice can be used across the entire public land mobile network (PLMN) or in one or more tracking areas (TAs). A network slice instance can be associated with one or more single network slice selection assistance information (S-NSSAI), and an S-NSSAI can be associated with one or more network slice instances.

[0223] In 3GPP 5G mobile communication networks, a network slice is identified by an S-NSSAI. The S-NSSAI consists of an SST (Slice / Service Type) and an SD (Slice Differentiator). The SST must be included in the S-NSSAI, while the SD can be included or not. In the current 3GPP technical specifications, as shown in Table 2, a total of six SST types and values ​​are defined as standard.

[0224] [Table 2]

[0225] In addition, one or more S-NSSAI sets are referred to as NSSAI (Network Slice Selection Assistance Information). During the registration process of the 5G mobile communication network, the terminal uses NSSAI to request a network slice connection from the core network, and the core network is responsible for the authentication and authorization of such a network slice connection request of the terminal. The terminal can receive and set or store various forms of NSSAI information from the 5G core network. The configuration NSSAI is the configuration NSSAI provided from the serving PLMN, the default configuration NSSAI is the setting NSSAI provided from the home PLMN, and the request NSSAI is the NSSAI used when the terminal requests a connection to a specific network slice from the core network. The allowed NSSAI refers to the NSSAI that the core network allows the terminal to connect to a specific network slice. In addition, the subscribed S-NSSAI refers to the S-NSSAI contained in the subscriber information.

[0226] The terminal may pre-set and store a default NSSAI, or may be provided or updated with a setting from the core network. Each S-NSSAI in the default NSSAI corresponds to an S-NSSAI of the subscriber's NSSAI. The S-NSSAI in the terminal's requested NSSAI refers to the S-NSSAI in the NSSAI previously established or allowed from the network. Ultimately, the NSSAI or S-NSSAI used by the terminal generally refers to the NSSAI or S-NSSAI previously established or allowed from the network.

[0227] On the other hand, to support and manage network slice connections, the terminal and the 5G mobile communication network typically receive or use NSSAI information during the registration process. First, the terminal typically has a pre-set and stored set NSSAI and an allowed NSSAI, the allowed NSSAI previously allowed and used by the network. If no allowed NSSAI was previously received from the network, there may be no allowed NSSAI. During the registration process, the terminal sends a registration request message to the network, which includes request NSSAI information, requesting connection to a specific network slice. Requesting NSSAI information here means using basic default NSSA1 information if no set NSSAI or allowed NSSAI is stored in the terminal, i.e., if no set NSSAI information is available. If no allowed NSSAI is stored and an available set NSSAI is stored, the set NSSAI is used as the request NSSAI information. Finally, if an available allowed NSSAI is stored, the allowed NSSAI is used as the request NSSAI information. After confirming the requested NSSAI contained in the registration request message sent by the terminal, the core network includes all the NSSAI set in the registration accept message, the allowed NSSAI, and the rejected NSSAI information, and responds to the terminal. The terminal stores the set NSSAI, allowed NSSAI, and rejected NSSAI information provided by the registration accept message sent from the network, and uses it when requesting a network slice connection. However, in the case of a rejected NSSAI, since it is NSSAI information that is rejected by the network, the terminal does not use the rejected NSSAI in principle. In this way, through the registration request process, the terminal and the network will provide each other with NSSAI information for network slice connection support and management for setting and management.

[0228] In addition, when the terminal sends a PDU session establishment request message for data transmission to the network, the terminal sends S-NSSAI information about the network slice to which the application involved in the data transmission is to be connected from the stored allowed NSSAI to the network. The network confirms the S-NSSAI information contained in the PDU session establishment request message sent by the terminal, and responds with acceptance if there is no problem.

[0229] In addition, when the network slice related information including NSSAI is changed due to a change in subscriber information or mobile communication network policy, the network may notify the terminal of the changed NSSAI information. In this case, the network may provide the terminal with the modified NSSAI information through a general UE configuration update procedure, wherein the AMF sends a configuration update command message including the configured NSSAI, allowed NSSAI, and rejected NSSAI information in a configuration update command message to the terminal, and the terminal updates and stores the received configured NSSAI, allowed NSSAI, and rejected NSSAI information. The terminal then uses the modified NSSAI information to perform a network slice connection request.

[0230] On the other hand, the recent 3GPP Release 18 standard defines an alternative S-NSSAI. When an S-NSSAI (e.g., S-NSSAI#1) becomes unusable or congested, this S-NSSAI (e.g., S-NSSAI#1) is replaced with a compatible / alternative S-NSSAI (e.g., S-NSSAI#2) among the existing permitted NSSAIs. When an S-NSSAI (e.g., S-NSSAI#1) becomes unusable or congested in the network, a compatible / alternative S-NSSAI is provided to the terminal, i.e., the alternative S-NSSAI is updated. In this case, the Generic UE Configuration Update procedure can be used to provide the terminal with the alternative S-NSSAI for update.

[0231] 3GPP Release 18 defines partially allowed NSSAI. This existing allowed NSSAI refers to the NSSAI that the network (AMF and / or SMF) notifies the terminal (within its registration area) of the requested NSSAI that the terminal intends to use, indicating that the network slice service associated with that NSSAI is allowed. In this case, the allowed NSSAI applies to the PLMNs or all TAs in the registration area. On the other hand, partially allowed NSSAI applies to the PLMNs or some TAs in the registration area. Therefore, network slice services associated with the corresponding partially allowed NSSAI (e.g., partially allowed NSSAI#1—actually, a specific S-NSSAI#1) are allowed in some TAs within the registration area, while not allowed in other TAs. Partially allowed NSSAI information is updated through the registration process or the general UE configuration update procedure.

[0232] <Disclosure of this Specification> Figure 8B is a flow chart according to one embodiment of the present specification.

[0233] As reference Figure 8B As shown, the UE (User Equipment) sends a registration request message.

[0234] At this time, the UE may include UE MM Core Network Capability in the Registration Request message. The UE MM Core Network Capability may include configuration information indicating support for a network-controlled Slice Usage Policy. Alternatively, the UE MM Core Network Capability may include information indicating support for temporarily available network slices.

[0235] The UE receives a Registration Accept message, or the UE may receive a Configuration Update Command message.

[0236] The registration acceptance message or the configuration update command message may include a slice deregistration inactivity timer and on-demand network slice selection assistance information (NSSAI).

[0237] The on-demand NSSAI may include one or more on-demand single NSSAIs (S-NSSAIs).

[0238] The slice deregistration inactivity timer may be set separately according to the access type.

[0239] The UE may start the slice deregistration inactivity timer. Specifically, the UE may start the slice deregistration inactivity timer for the first on-demand S-NSSAI when all of the following conditions are met: The protocol data unit (PDU) session associated with the first on-demand S-NSSAI has been released; User plane resources for the multi-access (MA) PDU session associated with the first on-demand S-NSSAI do not exist; And the PDU session related to the first on-demand S-NSSAI does not exist.

[0240] On the other hand, the UE may release the PDU session associated with the first on-demand S-NSSAI.

[0241] More specifically, the UE may release the PDU session associated with the first on-demand S-NSSAI through session management (SM) signaling.

[0242] Alternatively, the UE may locally release the PDU session associated with the first on-demand S-NSSAI.

[0243] When at least one PDU session related to the first on-demand S-NSSAI is successfully established, the UE may stop and reset the slice deregistration inactivity timer of the first on-demand S-NSSAI.

[0244] When the UE enters the DEREGISTERED state, the UE may also stop and reset the slice deregistration inactivity timer of the first on-demand S-NSSAI.

[0245] <Order of Examples of This Specification> On-demand S-NSSAI: refers to an S-NSSAI that is allowed to register with the network only when the user equipment (UE) establishes a protocol data unit (PDU) session for user data transmission.

[0246] I. Network Slice Usage Control Based on Mobility Management When both the UE and the network support network slice usage control, the access and mobility management function (AMF) can start the slice deregistration inactivity timer based on the S-NSSAI and access type to monitor the usage of network slices.

[0247] The AMF may provide the UE with on-demand network slice selection assistance information (on-demand NSSAI) via a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message. The on-demand NSSAI may include one or more on-demand S-NSSAIs, and may optionally include a slice deregistration inactivity timer for each S-NSSAI.

[0248] The start of the slice deregistration inactivity timer can be triggered based on the following stored timer values: a) For a PDU session released via 5GSM signalling: when the PDU session is released and there is no longer any MA PDU session associated with the S-NSSAI established via the corresponding access type; b) For locally released PDU sessions: When the UE or AMF indicates through the PDU Session Status IE that the PDU session is currently in 5GSM inactive and there is no MA PDU session associated with the S-NSSAI established through the corresponding access type; Or when the UE or AMF indicates that a PDU session that was previously in 5GSM active state has become inactive and the PDU session status IE does not contain any MA PDU session associated with the S-NSSAI established over this access type.

[0249] The slice deregistration inactivity timer shall be stopped and reset when at least one PDU session (which may include MA PDU session) associated with the S-NSSAI is successfully established through the corresponding access type, or the S-NSSAI is removed from the allowed NSSAIs.

[0250] If the timer value is updated, the AMF may update the stored value and provide the updated timer value to the UE via a Registration Accept message, a subsequent mobility or periodic registration update procedure, or a Configuration Update Command message.

[0251] When the UE receives a registration accept message or configuration update command message containing the updated slice deregistration inactivity timer value from the AMF, the UE shall update the stored timer value.

[0252] When the slice deregistration inactivity timer expires, the AMF may internally remove the S-NSSAI on the corresponding access type from the allowed NSSAI and may send a configuration update command message containing the new allowed NSSAI to the UE.

[0253] The NSSAI requested by the UE during the registration process includes the required on-demand S-NSSAI. When the slice deregistration inactivity timer expires, the UE may also internally remove the S-NSSAI for the corresponding access type from the allowed NSSAI.

[0254] If the UE supports network slice usage control, the AMF may provide the UE with the on-demand NSSAI in the configured NSSAI in the Registration Accept message or Configuration Update Command message. The on-demand NSSAI may include one or more configured S-NSSAIs.

[0255] The on-demand NSSAI may be associated with the provisioned NSSAI. When the associated provisioned S-NSSAI is deleted from the stored provisioned NSSAI by the UE, the UE may also delete the on-demand S-NSSAI from the stored on-demand NSSAI.

[0256] Based on operator policy, the AMF may choose not to impose network slice usage control on the S-NSSAI for emergency services.

[0257] 2. When the UE accepts the PDU session release request from the network: If the UE receives an on-demand S-NSSAI configuration with a slice deregistration inactivity timer, it may start the timer for the corresponding access type if one of the following conditions is met: a) the PDU Session associated with the on-demand S-NSSAI is released, and there are no established user plane resources for the MA PDU Session associated with that S-NSSAI, and there are no other PDU Sessions associated with that S-NSSAI; b) The MA PDU session associated with the on-demand S-NSSAI is released. For each registered access type, if there is no PDU session associated with the S-NSSAI and there are no user plane resources for the MA PDU session established via this access type, the UE may start the timer corresponding to the registered access type. c) If the user plane resources of an MA PDU session associated with an on-demand S-NSSAI are released via a certain access type and there is no PDU session associated with that S-NSSAI and there are no user plane resources for an MA PDU session established via that access type, the UE may start the timer for the corresponding access type.

[0258] Figure 9 A block diagram illustrating a configuration of a terminal according to an embodiment of the present disclosure.

[0259] UE 100 includes a memory 1010 , a processor 1020 , a transmission / reception unit 1031 , a power management module 1091 , a battery 1092 , a display 1041 , an input unit 1053 , a speaker 1042 and a microphone 1052 , a subscriber identity module (SIM) card, and one or more antennas.

[0260] Processor 1020 may be configured to implement the functions, processes, and / or methods described herein. Layers of the wireless interface protocol may be implemented in processor 1020. Processor 1020 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Processor 1020 may be an application processor (AP). Processor 1020 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Examples of processor 1020 may include a SNAPDRAGON™ series processor manufactured by Qualcomm, an EXYNOS™ series processor manufactured by Samsung, an A-series processor manufactured by Apple, a HELIO™ series processor manufactured by MediaTek, an ATOM™ series processor manufactured by INTEL, or corresponding next-generation processors.

[0261] The power management module 1091 manages the power of the processor 1020 and / or the transceiver 1031. The battery 1092 supplies power to the power management module 1091. The display 1041 outputs the results processed by the processor 1020. The input unit 1053 receives input for use by the processor 1020. The input 1053 may be displayed on the display 1041. A SIM card is an integrated circuit used to securely store the International Mobile Subscriber Identity (IMSI) and related keys, which are used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Contact information can be stored on many SIM cards.

[0262] Memory 1010 is operably coupled to processor 1020 and stores various information used to operate processor 1010. Memory 1010 may include read-only memory (ROM), random access memory (RAM), flash memory, a memory card, a storage medium, and / or other storage devices. When the embodiments are implemented in software, the techniques described herein may be implemented in modules (e.g., procedures, functions, etc.) that perform the functions described herein. The modules may be stored in memory 1010 and executed by processor 1020. Memory 1010 may be implemented within processor 1020. Alternatively, memory 1010 may be implemented external to processor 1020 and may be communicatively coupled to processor 1020 via various means known in the art.

[0263] The transmit / receive unit 1031 is operably coupled to the processor 1020 and transmits and / or receives wireless signals. The transmit / receive unit 1031 includes a transmit unit and a receive unit. The transmit / receive unit 1031 may include a baseband circuit for processing radio frequency signals. The transmit / receive unit controls one or more antennas to transmit and / or receive wireless signals. The processor 1020 transmits instruction information to the transmit / receive unit 1031 to transmit a wireless signal, such as a voice communication data, to initiate communication. The antenna is used to transmit and receive wireless signals. When a wireless signal is received, the transmit / receive unit 1031 can transmit the signal and convert the signal to baseband for processing by the processor 1020. The processed signal can be converted into audible or readable information output via the speaker 1042.

[0264] The speaker 1042 outputs sound-related results processed by the processor 1020. The microphone 1052 receives sound-related input used by the processor 1020.

[0265] The user inputs command information, such as a phone number, by, for example, pressing (or touching) a button on input unit 1053 or through voice activation using microphone 1052. Processor 1020 receives this command information and executes the appropriate function, such as dialing a phone number. Operational data may be retrieved from a SIM card or memory 1010. Furthermore, processor 1020 may display command information or driving information on display 1041 for user recognition and convenience.

[0266] Figure 10 A block diagram of a configuration of a processor in which the present disclosure is implemented is shown.

[0267] like Figure 10 As shown, the processor (1020) implemented by the embodiments disclosed in this specification may include multiple circuits to implement the proposed functions, processes and / or methods described in this specification.

[0268] For example, the processor (1020) may include a first circuit (1020-1), a second circuit (1020-2), and a third circuit (1020-3). In addition, although not shown in the figure, the processor (1020) may also include more circuits. Each circuit may include multiple transistors.

[0269] The first circuit (1020-1) may send a registration request message.

[0270] The second circuit (1020-2) may receive a registration acceptance message or a configuration update command (ConfigurationUpdate Command) message.

[0271] The registration acceptance message or the configuration update command message may include a slice deregistration inactivity timer and on-demand network slice selection assistance information (NSSAI).

[0272] The on-demand NSSAI may include one or more on-demand single S-NSSAIs (Single-NSSAIs).

[0273] The slice deregistration inactivity timer can be set separately according to the access type.

[0274] The third circuit (1020-3) may start the slice deregistration inactivity timer.

[0275] Specifically, when the following conditions are all met: the protocol data unit (PDU) session associated with the first on-demand S-NSSAI is released; the user plane resources of the multi-access (MA) PDU session associated with the first on-demand S-NSSAI do not exist; and the PDU session associated with the first on-demand S-NSSAI does not exist, then the third circuit (1020-3) can start the slice deregistration inactivity timer for the first on-demand S-NSSAI.

[0276] The processor 1020 may be referred to as an application specific integrated circuit (ASIC) or an application processor (AP), and may include at least one of a digital signal processor (DSP), a central processing unit (CPU), and a graphic processing unit (GPU).

[0277] The processor may be installed on a UE.

[0278] Although preferred embodiments have been exemplarily described, the disclosure of this specification is not limited to these specific embodiments, but may be modified, changed, or improved in various forms within the spirit of this specification and the scope of the claims.

[0279] In the exemplary system described above, the method is described as a series of steps or blocks according to the flowchart, but is not limited to the order of the steps described. Some steps may occur in a different order than the above steps or simultaneously. In addition, those skilled in the art will understand that the steps shown in the flowchart are not exclusive and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the rights.

[0280] The claims described herein may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a device. Furthermore, the technical features of the method claims of this specification may be combined with the technical features of the device claims to implement a device, and the technical features of the method claims of this specification may be combined with the technical features of the device claims to implement a device.

Claims

1. A method for operating a user equipment, characterized in that: The steps include: receiving a registration accept message or a configuration update command message including on-demand network slice selection assistance information and a slice deregistration inactivity timer, wherein the on-demand network slice selection assistance information includes one or more on-demand single network slice selection assistance information; and When all of the following conditions are met, the slice deregistration inactivity timer is started for selecting assistance information for the first on-demand single network slice: The first on-demand single network slice selection assistance information related protocol data unit session has been released, User plane resources for the multiple access protocol data unit session associated with the first on-demand single network slice selection assistance information are not established, The protocol data unit session related to the first on-demand single network slice selection auxiliary information does not exist.

2. The method for operating a user equipment according to claim 1, wherein: Further comprising the steps of: Release the protocol data unit session associated with the first on-demand single network slice selection assistance information.

3. The method for operating a user equipment according to claim 1, wherein: The protocol data unit session associated with the first on-demand single network slice selection assistance information is released through session management signaling.

4. The method for operating a user equipment according to claim 1, wherein: Further comprising the steps of: Locally releasing the protocol data unit session associated with the first on-demand single network slice selection assistance information.

5. The method for operating a user equipment according to claim 1, wherein: Further comprising the steps of: When at least one protocol data unit session associated with the first on-demand single network slice selection assistance information is successfully established, stopping and resetting the slice deregistration inactivity timer, The at least one protocol data unit session includes any multiple access protocol data unit session.

6. The method for operating a user equipment according to claim 1, wherein: Further comprising the steps of: When the user equipment enters the deregistered state, the slice deregistration inactivity timer of the first on-demand single network slice selection assistance information is stopped and reset.

7. A user equipment, characterized in that: include: at least one processor; as well as At least one computer memory operably connected to the at least one processor, wherein instructions are stored, and when the instructions are executed by the processor, the user device performs the following operations: receiving a registration accept message or a configuration update command message including on-demand network slice selection assistance information and a slice deregistration inactivity timer, wherein the on-demand network slice selection assistance information includes one or more on-demand single network slice selection assistance information; and When all of the following conditions are met, the slice deregistration inactivity timer is started for selecting assistance information for the first on-demand single network slice: The first on-demand single network slice selection assistance information related protocol data unit session has been released, User plane resources for the multiple access protocol data unit session associated with the first on-demand single network slice selection assistance information are not established, The protocol data unit session related to the first on-demand single network slice selection auxiliary information does not exist.

8. The user equipment according to claim 7, wherein: The operations further include: Release the protocol data unit session associated with the first on-demand single network slice selection assistance information.

9. The user equipment according to claim 7, wherein: The operations further include: The protocol data unit session associated with the first on-demand single network slice selection assistance information is released through session management signaling.

10. The user equipment according to claim 7, wherein: The operations further include: Locally releasing the protocol data unit session associated with the first on-demand single network slice selection assistance information.

11. The user equipment according to claim 7, wherein: The operations further include: When at least one protocol data unit session associated with the first on-demand single network slice selection assistance information is successfully established, stopping and resetting the slice deregistration inactivity timer, The at least one protocol data unit session includes any multiple access protocol data unit session.

12. The user equipment according to claim 7, wherein: The operations further include: When the user equipment enters the deregistered state, the slice deregistration inactivity timer of the first on-demand single network slice selection assistance information is stopped and reset.

13. A semiconductor chipset for a user device, characterized in that: include: at least one processor; as well as at least one memory capable of storing instructions and electrically connected to the processor, When the processor executes the instruction, the following operations are performed: receiving a registration accept message or a configuration update command message including on-demand network slice selection assistance information and a slice deregistration inactivity timer, wherein the on-demand network slice selection assistance information includes one or more on-demand single network slice selection assistance information; and When all of the following conditions are met, the slice deregistration inactivity timer is started for selecting assistance information for the first on-demand single network slice: The first on-demand single network slice selection assistance information related protocol data unit session has been released, User plane resources for the multiple access protocol data unit session associated with the first on-demand single network slice selection assistance information are not established, The protocol data unit session associated with the first on-demand single network slice selection assistance information does not exist.

Images