Method executed by user equipment, user equipment and semiconductor chipset

Abstract

The invention provides a method executed by user equipment, the user equipment and a semiconductor chip set. The method may comprise the steps of: receiving a registration acceptance message including a valid time for at least one S-NSSAI; if the at least one S-NSSAI is included in the allowed or partially allowed NSSAA, establishing at least one PDU session associated with the at least one S-NSSAI; if at least one PDU session is established for at least one S-NSSAI included in the partially permitted NSSAIs and the current TAI is not included in a TA list in which the S-NSSA1 is permitted, not initiating an NAS transmission process initiated by a UE for transmitting CIoT user data and a service request process for transmitting CIoT user data, and if the at least one PDU session is established for at least one S-NSSAI included in the partially permitted NSSAIs and the current TAI is not included in the TA list in which the S-NSSA1 is permitted; if the UE does not trigger the mobility registration update procedure and the allowed NSSAI becomes null after expiration of the valid time, the UE implicitly enters a logout state.

Description

TECHNICAL FIELD

[0001] The present specification relates to a 3GPP wireless communication system. BACKGROUND

[0002] Thanks to the success of LTE (long term evolution) / LTE-Advanced (LTE-A) for the fourth generation mobile communication, attention to the next generation (i.e., the fifth generation (so-called 5G)) mobile communication is also increasing, and research is also being conducted.

[0003] The fifth generation mobile communication defined by the International Telecommunication Union (ITU) refers to providing a data transmission speed of up to 20 Gbps, and providing at least 100 Mbps of actual experience transmission speed anywhere, and is officially called "IMT-2020".

[0004] The fifth generation mobile communication supports multiple numerologies or subcarrier spacings (SCSs) for supporting multiple services. For example, when the SCS is 15 kHz, a wide area in a legacy cellular band is supported; when the SCS is 30 kHz / 60 kHz, a dense city, lower latency, and a wider carrier bandwidth are supported; and when the SCS is greater than or equal to 60 kHz, a bandwidth greater than 24.25 GHz is supported to overcome phase noise.

[0005] The NR frequency band is defined as a frequency range of two types of FR1 and FR2. FR1 is 410 MHz - 7125 MHz, and FR2 is 24250 MHz - 52600 MHz, which can represent millimeter waves (mmW).

[0006] For convenience of explanation, in the frequency range used in the NR system, FR1 can represent a "sub 6 GHz range", and FR2 can represent an "above 6 GHz range" and be referred to as millimeter waves (mmW).

[0007] [Table 1]

[0008]

[0009] The numerical value of the frequency range of the NR system can change. For example, as shown in Table 1 below, FR1 can include a frequency band of 410 MHz to 7125 MHz. That is, FR1 can include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 can include a licensed unlicensed band. The licensed unlicensed band can be used for various purposes, for example, communication for vehicles (e.g., autonomous driving).

[0010] Figure 1 A wireless communication system is shown;

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

[0012] A user equipment (UE) 10 is connected to a data network via a UPF 44 through a next generation radio access network (NG-RAN).

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

[0014] Figure 2 An example diagram showing the structure of a wireless communication system from a node perspective is shown.

[0015] As Figure 2 shown, a UE is connected with a data network (DN) through a radio access network (RAN).

[0016] A control plane function (CPF) node shown performs all or part of the functions of a mobility management entity (MME) of a fourth-generation mobile communication, all or part of the control plane functions of a serving gateway (S-GW) and a PDN gateway (P-GW). The CPF node includes an access and mobility management function (AMF) and a session management function (SMF).

[0017] A user plane function (UPF) node shown is one kind of gateway for transmitting and receiving user data. The UPF node can perform all or part of the user plane functions of an S-GW and a P-GW of a fourth-generation mobile communication.

[0018] A policy control function (PCF) shown is a node that controls an operator policy.

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

[0020] A unified data management (UDM) shown is one kind of server that manages user information, such as a home subscriber server (HSS) of a fourth-generation mobile communication. The UDM stores and manages the user information in a unified data repository (UDR).

[0021] An authentication server function (AUSF) shown authenticates and manages a UE.

[0022] A network slice selection function (NSSF) shown is a node of a network slice, as described below.

[0023] A UE can simultaneously connect to two data networks using multiple protocol data unit or packet data unit (PDU) sessions.

[0024] Figure 3 is another example diagram illustrating a wireless communication system structure from a node perspective.

[0025] Figure 3 Architecture is shown in which a UE accesses two data networks simultaneously using one PDU session.

[0026] With Figure 2 and Figure 3 The matters related to the reference points shown in FIGS. 1 to 3 are as follows.

[0027] N1 denotes a reference point between a UE and an AMF.

[0028] N2 denotes a reference point between a (R)AN and an AMF.

[0029] N3 denotes a reference point between a (R)AN and a UPF.

[0030] N4 denotes a reference point between an SMF and a UPF.

[0031] N5 denotes a reference point between a PCF and an AF.

[0032] N6 denotes a reference point between a UPF and a DN.

[0033] N7 denotes a reference point between an SMF and a PCF.

[0034] N8 denotes a reference point between a UDM and an AMF.

[0035] N9 denotes a reference point between UPFs.

[0036] N10 denotes a reference point between a UDM and an SMF.

[0037] N11 denotes a reference point between an AMF and an SMF.

[0038] N12 denotes a reference point between an AMF and an AUSF.

[0039] N13 denotes a reference point between a UDM and an AUSF.

[0040] N14 denotes a reference point between AMFs.

[0041] N15 denotes a reference point between a PCF and an AMF.

[0042] N16 denotes a reference point between SMFs.

[0043] N22 denotes a reference point between an AMF and an NSSF.

[0044] N33 denotes a reference point between a network exposure function (NEF) and an AF.

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

[0046] The radio interface protocol is based on 3GPP radio access network specifications. The radio interface protocol horizontally includes a physical (Physical) layer, a data link (Data Link) layer, and a network (Network) layer, and is vertically divided into a user plane (User Plane) for data information transmission and a control plane (Control Plane) for control signal transmission.

[0047] Based on the lower three layers of the Open System Interconnection (OSI) reference model well known in communication systems, the protocol layer can be divided into L1 (first layer), L2 (second layer), and L3 (third layer).

[0048] Hereinafter, each layer of the radio interface protocol will be described.

[0049] The physical layer, which is the first layer, uses a physical channel (Physical Channel) to provide an information transfer service (Transfer Service). The physical layer is connected with a medium access control layer of an upper layer through a transport channel, and data between the medium access control layer and the physical layer is transferred through the transport channel. Also, data is transferred via a physical channel between different physical layers, i.e., between the physical layers of a transmission side and a reception side.

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

[0051] The third layer includes a radio resource control (RRC) layer. The RRC layer is defined only in the control plane and is responsible for the control of logical, transport, and physical channels in association with the configuration, re-configuration, and release of radio bearers (RBs) that are used for the transmission of data between the terminal and the RAN. The RB indicates a service provided by the second layer for data transmission between the terminal and the RAN.

[0052] A non-access stratum (NAS) layer performs functions such as session management, mobility management, etc.

[0053] The NAS layer is divided into a NAS entity for mobility management (MM) and a NAS entity for SM (Session Management).

[0054] 1) The NAS entity for MM generally provides the following functions:

[0055] As NAS procedures related to the AMF, include:

[0056] - Registration management and connection management procedures. The AMF supports the following functions:

[0057] - Secure NAS signaling connection between the UE and the AMF (integrity protection, encryption)

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

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

[0060] - For SM signaling transmission,

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

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

[0063] On the other hand, in Figure 4 , the RRC layer, the RLC layer, the MAC layer, the PHY layer located below the NAS layer are bundled together, also called Access Stratum (AS).

[0064] The network system of 5G (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 WLAN and untrusted WLAN.

[0065] In the 5G system, the AMF performs registration management (RM) and connection management (CM) for 3GPP access as well as non-3GPP access. SUMMARY

[0066] The disclosure of the present specification is intended to provide a method for determining transmission of CIoT user data related to S-NSSAI.

[0067] The present disclosure provides a method performed by a user equipment, UE. The method can comprise the steps of: receiving a registration accept message including a validity time for at least one single network slice selection assistance information; establishing at least one protocol data unit session associated with the at least one single network slice selection assistance information if the at least one single network slice selection assistance information is included in allowed network slice selection assistance information or partially allowed network slice selection assistance information; not initiating a user equipment initiated non-access stratum transmission procedure for transmitting cellular internet of things user data nor initiating a service request procedure for transmitting cellular internet of things user data if at least one protocol data unit session is established for at least one single network slice selection assistance information included in partially allowed network slice selection assistance information and a current tracking area identifier is not included in a tracking area list allowing the single network slice selection assistance information; and implicitly entering a deregistered state if the user equipment does not trigger a mobility registration update procedure and allowed network slice selection assistance information becomes empty after the validity time expires.

[0068] The present disclosure provides a user equipment (UE). The user equipment can comprise: a transceiver; and a processor configured to control the transceiver. The processor can perform the steps of: receiving a registration accept message including a validity time for at least one single network slice selection assistance information; establishing at least one protocol data unit session associated with the at least one single network slice selection assistance information if the at least one single network slice selection assistance information is included in allowed network slice selection assistance information or partially allowed network slice selection assistance information; not initiating a user equipment initiated non-access stratum transmission procedure for transmitting cellular internet of things user data nor initiating a service request procedure for transmitting cellular internet of things user data if at least one protocol data unit session is established for at least one single network slice selection assistance information included in partially allowed network slice selection assistance information and a current tracking area identifier is not included in a tracking area list allowing the single network slice selection assistance information; and implicitly entering a deregistered state if the user equipment does not trigger a mobility registration update procedure and allowed network slice selection assistance information becomes empty after the validity time expires.

[0069] The disclosure of the present specification provides a chipset installed on a UE. The chipset can include at least one processor; and at least one memory storing instructions and operatively electrically connected to the at least one processor. Based on the instructions executed by the at least one processor, the executed operations can include: receiving a registration accept message including a validity time for at least one single network slice selection assistance information; establishing at least one protocol data unit session associated with the at least one single network slice selection assistance information if the at least one single network slice selection assistance information is included in allowed network slice selection assistance information or partially allowed network slice selection assistance information; if at least one protocol data unit session is established for at least one single network slice selection assistance information included in partially allowed network slice selection assistance information, and a current tracking area identifier is not included in a tracking area list allowing the single network slice selection assistance information, not initiating a user equipment initiated non-access stratum transmission procedure for transmitting cellular internet of things user data, nor initiating a service request procedure for transmitting cellular internet of things user data; and if a user equipment does not trigger a mobility registration update procedure and allowed network slice selection assistance information becomes empty after the validity time expires, implicitly entering a deregistered state.

[0070] The present disclosure provides a non-volatile computer readable storage medium recording instructions. The storage medium can include instructions. When executed by one or more processors installed on a device, the instructions can cause the one or more processors to perform operations. The operations can include: receiving a registration accept message including a validity time for at least one single network slice selection assistance information; establishing at least one protocol data unit session associated with the at least one single network slice selection assistance information if the at least one single network slice selection assistance information is included in allowed network slice selection assistance information or partially allowed network slice selection assistance information; if at least one protocol data unit session is established for at least one single network slice selection assistance information included in partially allowed network slice selection assistance information, and a current tracking area identifier is not included in a tracking area list allowing the single network slice selection assistance information, not initiating a user equipment initiated non-access stratum transmission procedure for transmitting cellular internet of things user data, nor initiating a service request procedure for transmitting cellular internet of things user data; and if a user equipment does not trigger a mobility registration update procedure and allowed network slice selection assistance information becomes empty after the validity time expires, implicitly entering a deregistered state.

[0071] The method or operations can further comprise the step of initiating the user equipment initiated NAS transport procedure for transmitting the cellular internet of things user data or the service request procedure for transmitting the cellular internet of things user data if the at least one protocol data unit session is established for the at least one single network slice selection assistance information comprised in the part allowed network slice selection assistance information and if a current tracking area identifier is in the tracking area list allowing the single network slice selection assistance information.

[0072] The method or operations can further comprise the step of transmitting a registration request message.

[0073] The method or operations can further comprise the step of transmitting a registration request message including requested network slice selection assistance information including the single network slice selection assistance information if the validity time indicates that the single network slice selection assistance information is available.

[0074] The method or operations can further comprise the step of not including the single network slice selection assistance information in the requested network slice selection assistance information if the validity time indicates that the single network slice selection assistance information is not available.

[0075] According to the present disclosure, procedures related to S-NSSAI are provided. BRIEF DESCRIPTION OF DRAWINGS

[0076] Figure 1 A wireless communication system is illustrated;

[0077] Figure 2 is an example diagram illustrating a structure of a wireless communication system from a node perspective.

[0078] Figure 3 is yet another example diagram illustrating a structure of a wireless communication system from a node perspective.

[0079] Figure 4 is an example diagram illustrating a structure of a radio interface protocol between a terminal and a network;

[0080] Figure 5a and 5b is a signal flow diagram illustrating an example registration procedure.

[0081] Figure 6a and 6b is a signal flow diagram illustrating an example PDU session establishment procedure.

[0082] Figure 7a and 7b is a signal flow diagram illustrating an example modification procedure of a PDU session.

[0083] Figure 8 is an example diagram for explaining the concept of network slicing.

[0084] Figure 9 is an example diagram of steps according to the present disclosure.

[0085] Figure 10 is a block diagram showing a configuration of a terminal according to one embodiment of the present disclosure.

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

[0087] It should be noted that the technical terms used in the present specification are used only to describe the specific embodiments, and are not intended to limit the content of the present specification. In addition, unless specifically defined otherwise herein, the technical terms used herein are to be understood as the meanings commonly understood by those of ordinary skill in the art to which the present disclosure pertains, and should not be interpreted as overly comprehensive or overly narrow meanings. In addition, when the technical terms used in the present specification are erroneous technical terms that cannot correctly express the content and idea of the present specification, they should be understood to be replaced with technical terms that can be correctly understood by those skilled in the art. In addition, the general terms used herein should be interpreted according to the previous definition or according to the context, and should not be interpreted in an overly reduced meaning.

[0088] In addition, unless the context clearly indicates otherwise, as used herein, the singular forms "a," "an," and "the" include plural referents. In this application, the term "configuration" or "branch" should not be interpreted to include any of the plurality of elements or steps described in the specification, but can not include some of them, or can further include additional elements or steps.

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

[0090] When it is mentioned that one component is connected to or connected to another component, it can be directly connected to or connected to the other component, but there can be another component in the middle. On the other hand, when it is mentioned that a certain component is directly connected to or directly connected to another component, it should be understood that there is no other component in the middle.

[0091] Hereinafter, 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 repetitive description thereof will be omitted. Also, in explaining the contents of the present specification, if it is judged that a detailed description of the related art will obscure the gist of the present specification, the detailed description thereof will be omitted. It should also be noted that the accompanying drawings are merely to facilitate the understanding of the contents and spirit of the present specification, and should not be interpreted as limiting the contents and ideas of the present specification. In addition to the accompanying drawings, the contents and spirit of the present specification should be understood to extend to all modifications, equivalents, or alternatives.

[0092] In the present specification, "A or B" can mean "A only", "B only", or "A and B". In other words, "A or B" in this document can be interpreted as "A and / or B". For example, "A, B, or C" in this document can mean "A, B, or C only" or "any and all combinations of A, B, and C".

[0093] 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 "A only", "B only", or "A and B". For example, "A, B, C" can mean "A, B, or C".

[0094] In the present specification, "at least one of A and B" can mean "A only", "B only", or "both A and B". Also, in this document, the expression "at least one of A or B" or "at least one of A and / or B" can be interpreted as the same as "at least one of A and B".

[0095] Also, in this document, "at least one of A, B, and C" can mean "A only", "B only", "C only", or "any and all combinations of A, B, and C". Also, "at least one of A, B, or C" or "at least one of A, B, and / or C" can mean "at least one of A, B, and C".

[0096] Also, the parentheses used herein can mean "for example". In particular, when expressed as "control information (PDCCH)", "PDCCH" can be proposed as an example of "control information". In other words, "control information" in the present specification is not limited to "PDCCH", and "PDDCH" can be proposed as an example of "control information". Also, even in the case of being marked as "control information (i.e., PDCCH)", "PDCCH" can be proposed as an example of "control information".

[0097] The technical features described herein individually in one drawing can be implemented individually or simultaneously.

[0098] Although a user equipment (UE) is exemplarily shown in the drawings, the UE shown can be referred to as a terminal (UE 100), a mobile equipment (ME), etc. Further, the UE can be a portable device such as a notebook, a cell phone, a PDA, a smart phone, a multimedia device, etc., or a non-portable device such as a PC, a car-mounted device, etc.

[0099] <Definitions of terms>

[0100] CIoT: Abbreviation of Cellular Internet of Things, means to be based on IoT communication.

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

[0102] User plane CIoT optimization: Signaling optimization on the user plane, which allows efficient transfer of user data (IP-based or non-IP-based or SMS-based user data)

[0103] CIoT optimization supporting UE: UE supporting control plane CIoT optimization or user plane CIOT optimization and one or more other CIoT optimization

[0104] <Registration procedure>

[0105] The UE needs to be authorised for mobility tracking, data reception and service reception. For this, the UE has to register with the network. The registration procedure is performed when the UE needs to perform initial registration with the 5G system. In addition, the registration procedure is performed when the UE performs periodic registration update, moves from idle mode to a new tracking area (TA), and the UE needs to perform periodic registration update.

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

[0107] Figure 5a And 5b is a signal flow diagram showing an exemplary registration procedure.

[0108] 1) The UE can send an AN message to the RAN. The AN message can include an AN parameter, a registration request message. The registration request message can include information such as a registration type, a subscriber permanent ID or a temporary user ID, a security parameter, an NSSAI, a 5G capability of the UE, a PDU session status, etc.

[0109] In case of a 5G RAN, the AN parameters can include SUPI or temporary user ID, selected network and NSSAI.

[0110] The registration type can indicate whether the UE is "initial registration" (i.e., the UE is in the non-registered state), "mobility registration update" (i.e., the UE is in the registered state and starts the registration procedure due to mobility), or "periodic registration update" (e.g., the UE is in the registered state and starts the registration procedure due to periodic update timer expiry); if a temporary user ID is included, the temporary user ID represents the last serving AMF. If the UE has registered in a different PLMN than the PLMN of the 3GPP access through non-3GPP access, the UE can not provide the UE temporary ID allocated by the AMF during the registration procedure through non-3GPP access.

[0111] The security parameters can be used for authentication and integrity protection.

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

[0113] 2) If SUPI or temporary user ID is included and does not represent a valid AMF, the RAN can select an AMF based on the (R)AT and NSSAI.

[0114] If the AN is not able to select a suitable AMF, any AMF is selected according to local policy and the registration request is forwarded to the selected AMF. If the selected AMF is not able to serve the UE, the selected AMF selects a more suitable other AMF for the UE.

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

[0116] When a 5G-RAN is used, the N2 parameters include location information associated with the cell in which the UE is camping, cell identifier and RAT type.

[0117] If the registration type indicated by the UE is periodic registration update, procedure 4-17 described below can not be performed.

[0118] 4) The newly selected AMF can send an information request message, e.g., Namf_Communication_UEContextTransfer, to the previous AMF.

[0119] If the UE's temporary user ID is included in the registration request message and the serving AMF has changed since the last registration, the new AMF can send an information request message to the previous AMF including the complete registration request information to request the UE's SUPI and MM context.

[0120] 5) The previous AMF sends an information response message, e.g. Namf_Communication_UEContextTransfer response, to the new selected AMF. The information response message can include the SUPI, MM context and SMF information.

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

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

[0123] 6) If the UE did not provide the SUPI or did not retrieve the SUPI from the previous AMF, the new AMF sends an identity request message to the UE.

[0124] 7) The UE sends an identity response message including the SUPI to the new AMF.

[0125] 8) The AMF can decide to trigger the AUSF. In this case, the AMF can select the AUSF based on the SUPI.

[0126] 9) The AUSF can start the authentication of the UE and the NAS security functions.

[0127] 10) The new AMF can send a Namf_Communication_RegistrationCompleteNotify message to the previous AMF.

[0128] 11) The new AMF can send an identity request message to the UE.

[0129] If the UE did not provide the PEI or did not retrieve the PEI from the previous AMF, an identity request message can be sent so that the AMF retrieves the PEI.

[0130] 12) The new AMF checks the identifiers.

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

[0132] 14) The new AMF performs a registration procedure in the UDM.

[0133] 15) The new AMF can select a PCF based on the SUPI.

[0134] 16) The new AMF performs establishment of a policy association with the PCF.

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

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

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

[0138] If the previous AMF previously requested establishment of a UE context in the PCF, the previous AMF can delete the UE context from the PCF.

[0139] 21) The PCF sends a UE context termination accept message to the previous AMF.

[0140] 22) The new AMF sends a registration accept message to the UE. The registration accept message can include a temporary user ID, a registration area, a mobility restriction, a PDU session status, a NSSAI, a periodic registration update timer, and an allowed MICO mode.

[0141] The temporary user ID can be further included in the registration accept message when the AMF allocates a new temporary user ID. If a mobility restriction is applied to the UE, information indicating the mobility restriction can be further included in the registration accept message. The AMF can include information indicating the PDU session status of the UE in the registration accept message. The UE can remove any internal resources associated with PDU sessions that are not indicated as active in the received PDU session status. If PDU session status information is in the registration request, the AMF can include information indicating the PDU session status to the UE in the registration accept message.

[0142] 23) The UE sends a registration complete message to the new AMF.

[0143] <PDU Session Establishment Procedure>

[0144] The protocol data unit (PDU) session establishment procedure can have two types of PDU session establishment procedures:

[0145] - UE initiated PDU session establishment procedure

[0146] - Network initiated PDU session establishment procedure. For this, the network can send a device trigger message to the UE's application.

[0147] Figure 6a and 6b is a signal flow diagram illustrating an exemplary PDU session establishment procedure.

[0148] Figure 6a and 6b The procedure shown assumes that the UE has registered on the AMF according to a registration procedure. Thus, it is assumed that the AMF has obtained the user subscription data from the UDM.

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

[0150] In particular, the UE includes S-NSSAI from the allowed NSSAI of the current access type. If the UE is provided with information on mapped NSSAI, the UE can provide S-NSSAI based on the allowed NSSAI and corresponding S-NSSAI based on the information of the mapped NSSAI. Among them, the information of the mapped NSSAI is information that maps each S-NSSAI of the allowed NSSAI to an S-NSSAI in the NSSAI set for a home public land mobile network (HPLMN, Home Public Land Mobile Network).

[0151] More specifically, the UE can extract and store the information of the allowed S-NSSAI and the mapped S-NSSAI included in the registration accept message received from the network (i.e., the AMF) in the registration procedure. Thus, the UE can transmit 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.

[0152] To establish a new PDU session, the UE can generate a new PDU session ID.

[0153] The UE can initiate a UE initiated PDU session establishment procedure by transmitting a NAS message including a PDU session establishment request message in N1 SM information. The PDU session establishment request message can include a request type, a session and service continuity (SSC) mode, and a protocol configuration option.

[0154] The request type indicates an "initial request" when a PDU session is established for establishing a new PDU session. However, if there is an existing PDU session between 3GPP access and non-3GPP access, the request type can indicate an "existing PDU session".

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

[0156] The N1 SM information can include an SM PDU DN request container including information on PDU session authentication for an external DN.

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

[0158] If the NAS message does not include an S-NSSAI, the AMF can determine a default configuration S-NSSAI for the requested PDU session according to a UE subscription. The AMF can store the PDU session ID in association with the ID of the SMF.

[0159] The AMF can select an SMF.

[0160] 3) The AMF can send the Nsmf_PDUSession_CreateSMContext request message or the Nsmf-PDUSession-UpdateSMContext request message to the selected SMF.

[0161] The Nsmf_PDUSession_CreateSMContext request message can 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, Trace Requirements. The SM Container can include a PDU Session Establishment Request message.

[0162] The Nsmf_PDUSession_UpdateSMContext request message can 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 can include a PDU Session Establishment Request message.

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

[0164] 4) The SMF sends a Subscriber Data Request message to the UDM. The Subscriber Data Request message can include a Subscriber Permanent ID, DNN. The UDM can send a Subscription Data Response message to the SMF.

[0165] In the above procedure 3, if the Request Type indicates "Existing PDU Session", the SMF determines that the request is due to a handover between 3GPP access and non-3GPP access. The SMF can identify the existing PDU Session based on the PDU Session ID.

[0166] If the SMF has not retrieved SM-related subscription data for the UE related to the DNN, the SMF can request the subscription data.

[0167] The subscription data can include information about authentication request type, authentication SSC mode, and basic QoS profile.

[0168] The SMF can check whether the UE request complies with the user subscription and local policies. Alternatively, the SMF rejects the UE request by means of NAS SM signaling (including the relevant SM rejection cause) sent by the AMF, and the SMF informs the AMF that the PDU session ID shall be considered as released.

[0169] 5) The SMF sends an Nsmf_PDUSession_CreateSMContext Response message or an Nsmf_PDUSession_UpdateSMContext Response message to the AMF.

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

[0171] In the above procedure 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 transfers the SM context ID to the AMF.

[0172] 6) Optionally, a second authentication / authorization is performed.

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

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

[0175] 8) If the request type of procedure 3 indicates "initial request", the SMF selects an SSC mode for the PDU session. If procedure 5 is not performed, the SMF can also select a UPF. For request type IPv4 or IPv6, the SMF can allocate an IP address / prefix for the PDU session.

[0176] 9) The SMF performs an SM policy association modification procedure to provide information about policy control request tree-like conditions.

[0177] 10) Request Type indicates "Initial Request", the SMF can initiate N4 Session Establishment procedure using the selected UPF, else can initiate N4 Session Modification procedure using the selected UPF.

[0178] 10a) The SMF sends N4 Session Establishment / Modification Request message to the UPF. Also, the SMF can provide packet detection, enforcement and reporting rules to be installed in the UPF for the PDU Session. When the SMF is allocated CN tunnel information, the CN tunnel information can be provided to the UPF.

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

[0180] 11) The SMF sends Namf_Communication_N1N2MessageTransfer message to the AMF. The Namf_Communication_N1N2MessageTransfer message can include PDU Session ID, N2 SM information and N1 SM container.

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

[0182] The N1 SM container can include PDU Session Establishment Accept message.

[0183] The PDU Session Establishment Accept message can include authorized QoS rules, SSC mode, S-NSSAI, allocated IPv4 address.

[0184] 12) The AMF sends N2 PDU Session Request message to the RAN. The message can include N2 SM information, NAS message. The NAS message can include PDU Session ID, PDU Session Establishment Accept message.

[0185] The AMF can send a NAS message including the PDU Session ID and the PDU Session Establishment Accept message. Also, the AMF includes the N2 SM information received from the SMF in the N2 PDU Session Request message and sends to the RAN.

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

[0187] The RAN also allocates RAN N3 tunnel information for the PDU Session.

[0188] The RAN sends the NAS message provided in step 10 to the UE. The NAS message can include the PDU Session ID, N1 SM information. The N1 SM information can include the PDU Session Establishment Accept message.

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

[0190] 14) The RAN sends the N2 PDU Session Response message to the AMF. The message can include the PDU Session ID, cause, N2 SM information. The N2 SM information can include the PDU Session ID, (AN) tunnel information, allowed / rejected QoS profile list.

[0191] The RAN tunnel information can correspond to an access network address of the N3 tunnel corresponding to the PDU Session.

[0192] 15) The AMF can send the Nsmf_PDUSession_UpdateSMContext Request message to the SMF. The Nsmf_PDUSession_UpdateSMContext Request message can include the N2 SM information. Wherein, the AMF can forward the N2 SM information received by the RAN to the SMF.

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

[0194] 16b) The UPF can send the N4 Session Modification Response message to the SMF.

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

[0196] After the procedure, the AMF can convey the relevant event to the SMF.

[0197] 18) The SMF sends the Nsmf_PDUSession_SMContextStatusNotify message.

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

[0199] 20) If the PDU session establishment is not successful during the procedure, the SMF informs the AMF.

[0200] <PDU Session Modification Procedure>

[0201] The protocol data unit (PDU) session establishment procedure can have two types of PDU session establishment procedures:

[0202] - UE initiated PDU session establishment procedure

[0203] - Network initiated PDU session establishment procedure. For this, the network can send a device trigger message to the UE's application.

[0204] Figure 7a and 7b is a signal flow diagram showing an exemplary PDU session modification procedure.

[0205] The PDU session can be established / managed based on the PDU session modification procedure.

[0206] The PDU session modification procedure can be initiated by the UE or by the network.

[0207] 1a) When the UE initiates, the UE can initiate the PDU session modification procedure by sending a NAS message. The NAS message can include an N1 SM container. The N1 SM container can include information on a PDU session modification request message, a PDU session ID, and an integrity protection maximum data rate of the UE. The PDU session modification request message can include a PDU session ID, a packet filter, information on a requested QoS, a 5GSM (5G Session Management) core network capability, and the number of packet filters. The integrity protection maximum data rate of the UE refers to the maximum data rate that the UE can support for UP integrity protection. The number of packet filters indicates the number of packet filters supported by the QoS rule.

[0208] The NAS message is forwarded to the appropriate AMF via RAN according to the location information of the UE. Then, the AMF sends Nsmf_PDUSession_UpdateSMContext message to SMF. The message can include Session Management (SM) Context ID, N1 SM container. The N1 SM container can include PDU Session Modification Request message.

[0209] 1b) When initiated by the PCF in the network node, the PCF can inform the SMF of the change of policy by initiating the SM Policy Association Modification procedure.

[0210] 1c) When initiated by the UDM in the network node, the UDM can update the subscription data of the SMF by sending Nudm_SDM_Notification message. The SMF can update the Session Management Subscriber Data and send an ACK message to the UDM.

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

[0212] When triggered according to the above 1a-1d, the SMF can perform the PDU Session Modification procedure.

[0213] 1e) When initiated by the RAN in the network node, the RAN can inform the SMF when the AN resources mapped by the QoS flow are released. The RAN can send N2 message to the AMF. The N2 message can include PDU Session ID, N2 SM information. N2 SM information can include QFI (QoS Flow ID), user location information and an indication indicating that the QoS flow is released. The AMF can send Nsmf_PDUSession_UpdateSMContext message. The message can include SM Context ID, N2 SM information.

[0214] 2) The SMF can send the report of the subscription event by performing the SM Policy Association Modification procedure. If the PDU Session Modification procedure is triggered by 1b or 1d, this step can be skipped. If dynamic PCC is not deployed in the network, the SMF can apply internal policy to determine the change of QoS profile.

[0215] If the PDU session modification only requires the operation of UPF, the following procedures 3 to 7 can not be performed.

[0216] 3a) When initiated by the UE or the RAN, the SMF can respond to the AMF by sending the Nsmf_PDUSession_UpdateSMContext message. The message can include N2 SM information, N1 SM container. The N2 SM information can include PDU Session ID, QFI, QoS profile, Session AMBR. The N1 SM container can include PDU Session Modification Command. The PDU Session Modification Command can include PDU Session ID, QoS rules, QoS rules operation, QoS parameters per QoS flow, Session AMBR.

[0217] The N2 SM information can include information that the AMF should transfer to the RAN. The N2 SM information can include QFI and QoS profile to inform the RAN that one or more QoS flows have been added or modified. If the UE requests PDU Session Modification without user plane resources established, the N2 SM information to be transferred to the RAN can include information about the establishment of user plane resources.

[0218] The N1 SM container can include PDU Session Modification Command that causes the AMF to forward the command to the UE. The PDU Session Modification Command can include QoS rules, QoS flow level QoS parameters.

[0219] 3b) When initiated by the SMF, the SMF can send the Namf_Communication_N1N2MessageTransfer message. The message can include N2 SM information, N1 SM container. The N2 SM information can include PDU Session ID, QFI, QoS profile, Session AMBR. The N1 SM container can include PDU Session Modification Command. The PDU Session Modification Command can include PDU Session ID, QoS rules, QoS flow level QoS parameters.

[0220] If the UE is in 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, i.e. when the UE enters CM-CONNECTED state, the AMF can send N1 message to synchronize the UE context with the UE.

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

[0222] 5) The RAN performs AN signaling exchange with the UE associated with the information received from the SMF. For example, for the case of NG-RAN, the RRC Connection Reconfiguration procedure with the UE can be performed to modify the necessary AN resources associated with the PDU Session.

[0223] 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 can include the N2 SM information and the user location information. The N2 SM information can include the list of accepted / rejected QFIs, AN tunnel information, PDU Session ID, etc.

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

[0225] 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.

[0226] In case of new QoS flow is created, the SMF updates the UL packet detection rule for the new QoS flow together with the UPF.

[0227] 9) The UE sends a NAS message in response to receiving the PDU Session Modification Command. The NAS message can include the PDU Session ID, N1 SM container. The N1 SM container can include the PDU Session Modification Command ACK.

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

[0229] 11a), 11b) The AMF can forward the N1 SM container and user location information received from the RAN to the SMF via the Nsmf_PDUSession_UpdateSMContext message. The N1 SM container can include a PDU Session Modification Command ACK. The SMF can send the Nsmf_PDUSession_UpdateSMContext response message to the AMF.

[0230] 12a), 12b) The SMF sends the N4 Session Modification Request message to the UPF to update the N4 session of the UPF included in the PDU Session Modification. The message can include the N4 Session ID.

[0231] 13) If the SMF interacts with the PCF in step 1b or step 2, the SMF can inform the PCF whether it can perform PCC decisions via the SM Policy Association Modification procedure.

[0232] The SMF can inform the requesting entity about the user location information related to the PDU session change.

[0233] A. Collaboration or coordination between 5G Session Management (5GSM) and EPS Session Management (ESM) using the N26 interface

[0234] a) The PDU Session Type of a PDU Session is mapped to the Packet Data Network (PDN) Type of a default Evolved Packet System (EPS) Bearer as follows:

[0235] a-1) If the PDU Session Type is “Unstructured”, the PDN Type is set to “non-IP”.

[0236] a-2) If the PDU Session Type is “IPv4”, the PDN Type is set to “IPv4”.

[0237] a-3) If the PDU Session Type is “IPv6”, the PDN Type is set to “IPv6”.

[0238] a-4) If the PDU Session Type is “IPv4v6”, the PDN Type is set to “IPv4v6”.

[0239] a-5) If the PDU Session Type is “Ethernet” and if neither the UE nor the network supports Ethernet PDN Type in S1 mode, or if neither the UE nor the network supports Ethernet PDN Type in S1 mode, the PDN Type is set to “non-IP”.

[0240] a-6) If the PDU session type is "Ethernet", and if both the UE and the network support Ethernet PDN type in S1 mode, the PDN type is set to "Ethernet".

[0241] b) The PDU address of the PDU session is mapped to the PDN address of the default EPS bearer as follows:

[0242] b-1) If the PDU session type is "IPv4", "IPv6" or "IPv4v6", the PDN address of the default EPS bearer context is set to the PDU address of the PDU session.

[0243] b-2) If the PDU session type is "Ethernet" or "Unstructured", the PDN address of the default EPS bearer context is set to 0 (zero).

[0244] B. PDU session type

[0245] The following PDU session types can be supported:

[0246] IPv4;

[0247] IPv6;

[0248] IPv4v6;

[0249] Ethernet (EtherType as defined in IEEE Std 802.3 [31A]); and

[0250] Unstructured.

[0251] C. IP address allocation through NAS signaling

[0252] If the UE requests IP connectivity, the UE can set the PDU session type in the PDU session modification request message based on its own IP stack capability as follows:

[0253] a) The UE:

[0254] 1) If both IPv6 and IPv4 are possible, the PDU session type can be set to IPv4, IPv6 or IPv4v6 according to the UE's setting or received policy.

[0255] 2) If only IPv6 is possible, the PDU session type can be set to IPv6.

[0256] 3) If only IPv4 is possible, the PDU session type can be set to IPv4.

[0257] b) If the IP version capability within the UE is not known (Mobile Termination (MT) and Terminal Equipment (TE) are separated, and the MT does not know the capability of the TE), the UE can set the PDU session type to IPv4v6.

[0258] If the UE wishes to use DHCPv4 for IPv4 address allocation, the UE can inform the network using the Extended Protocol Set Option Information Element (IE) in the PDU session modification request message.

[0259] When the UE sends the PDU session modification request message, in order to allocate the IP address, the network can consider the PDU session type, the policy of the network operator, and the subscription information of the UE.

[0260] a) If the network sets the selected PDU session type IE to IPv4, the network can cause the IPv4 address to be included in the PDU address IE.

[0261] b) If the network sets the selected PDU session type IE to IPv6, the network can cause the interface identifier for the IPv6 link-local address to be included in the PDU address IE.

[0262] c) If the network sets the selected PDU session type IE to IPv4v6, the network can include the interface identifier for the IPv4 address and the IPv6 link-local address in the PDU address IE.

[0263] D. UE-requested PDU session modification procedure

[0264] D-1. Initiating UE-requested PDU session modification procedure

[0265] In order to allow the UE to request PDU session modification, the UE-requested PDU session modification procedure can be used.

[0266] In order to enable the UE to initiate the PDU session modification procedure, the UE generates a PDU session modification request message.

[0267] If the UE requests to establish a new emergency PDU session, the UE sets the PDU session type information element (IE) to the IP version capability and causes it to be included in the PDU session modification request message.

[0268] If the UE supports reflective QoS, the UE can set the RQoS bit to "Reflective QoS supported" in the 5GSM capability IE in the PDU session modification request message.

[0269] a) The UE can request a new PDU session of "IPv4", "IPv6", "IPv4v6" or "Ethernet" PDU session type.

[0270] b) If the UE requests to forward an existing PDN connection in EPS of "IPv4", "IPv6", "IPv4v6" or "Ethernet" PDN type or mapping to an existing PDN connection in EPS of "non-IP" PDN type of "Ethernet" PDU session type to 5GS; or

[0271] c) If the UE requests to transfer an existing PDN connection in untrusted non-3GPP access connected to EPC of "IPv4", "IPv6" or "IPv4v6" PDN type to 5GS,

[0272] For a PDU connection established in S1 mode, if the UE operates in single registration mode in a network supporting N26 interface after changing from S1 mode to N1 mode inter-system, and if the UE supports receiving DNS server address in protocol setting option, and if the UE has not successfully performed PDU session modification procedure requested by the UE previously, the UE can include the following in the extended protocol setting option IE in the PDU session modification request message:

[0273] a) If the PDU session is of "IPv4" or "IPv4v6" PDU session type, the UE can include DNS server IPv4 address request.

[0274] b) If the PDU session is of "IPv6" or "IPv4v6" PDU session type, the UE can include DNS server IPv6 address request.

[0275] D-2. If the network accepts the PDU session modification procedure requested by the UE

[0276] If the network accepts the PDU session modification procedure requested by the UE, the SMF initiates the network requested PDU session modification procedure. To do so, the SMF generates a PDU session modification request message.

[0277] The SMF sets the selected PDU session type IE in the PDU session modification request message to the selected PDU session type, i.e. the PDU session type of the PDU session.

[0278] D-3. If the network does not accept the PDU session modification procedure requested by the UE

[0279] If the connection of the requested DN is rejected by the network, the SMF generates a PDU Session Modification Reject message.

[0280] The SMF can set the 5GSM cause IE in the PDU Session Modification Reject message to indicate the cause of rejecting the PDU session modification.

[0281] The 5GSM cause IE can represent one of the following SM cause values:

[0282] #8 Operator determined barring;

[0283] #26 Insufficient resources;

[0284] #27 Loss or unknown of DNN;

[0285] #28 Unknown PDU session type;

[0286] #29 Authentication or authorization failure

[0287] #31 Request rejected (unspecified);

[0288] #32 Service option not supported;

[0289] #33 Requested service option not subscribed;

[0290] #35 Procedure Transaction Identity (PTI);

[0291] #38 Network failure;

[0292] #39 Reactivation requested;

[0293] #50 PDU session type IPv4 only allowed;

[0294] #51 PDU session type IPv6 only allowed;

[0295] #54 PDU session does not exist;

[0296] #57 Only PDU Session Type IPv4v6 is allowed;

[0297] #58 Only untrusted PDU Session Type is allowed;

[0298] #61 Only PDU Session Type Ethernet is allowed;

[0299] #67 Resource is insufficient for specific slice and DNN;

[0300] #68 SSC mode is not supported;

[0301] #69 Resource is insufficient for certain slices;

[0302] If the PDU Session Modification Request message includes a PDU Session Type IE set to IPv6, and either the subscriber information or the SMF settings or both the subscriber information and the SMF settings are restricted to only IPv4 for the requested DNN, the SMF can cause the inclusion of the 5GSM cause value #50 "Only PDU Session Type IPv4" in the 5GSM cause IE in the PDU Session Modification Reject message.

[0303] If the PDU Session Modification Request message includes a PDU Session Type IE set to IPv6, and either the subscriber information or the SMF settings or both the subscriber information and the SMF settings are restricted to "IPv4" PDU Session Type and "IPv6" PDU Session Type for the requested DNN not supported, the SMF can cause the inclusion of the 5GSM cause value #28 "Unknown PDU Session Type" in the 5GSM cause IE in the PDU Session Modification Reject message.

[0304] If the PDU Session Modification Request message includes a PDU Session Type IE set to "IPv4", and if either the subscriber information or the SMF settings or both the subscriber information and the SMF settings are restricted to only IPv6 for the requested DNN, the SMF can cause the inclusion of the 5GSM cause value #51 "Only PDU Session Type IPv6" in the 5GSM cause IE in the PDU Session Modification Reject message.

[0305] If the PDU Session Modification Request message includes a PDU Session Type IE set to "IPv4", and if either the subscriber information or the SMF settings or both the subscriber information and the SMF settings do not support the Session Type "IPv4" for the requested DNN, the SMF can cause the inclusion of the 5GSM cause value #28 "Unknown PDU Session Type" in the 5GSM cause IE of the PDU Session Modification Reject message.

[0306] If the PDU Session Modification Request message includes a PDU Session Type IE set to "IPv4v6", and if neither the subscriber information nor the SMF settings or both the subscriber information and SMF settings support "IPv4v6" for the PDU Session Type and "IPv4" and "IPv6" for the PDU Session Type for the requested DNN, the SMF can cause a 5GSM cause value #28 "Unknown PDU Session Type" to be included in the 5GSM cause IE of the PDU Session Modification Reject message.

[0307] If the PDU Session Modification Request message includes a PDU Session Type IE set to "Not Established" or "Ethernet", and if neither the subscriber information nor the SMF settings or both the subscriber information and SMF settings support the PDU Session Type for the requested DNN, the SMF can cause a 5GSM cause value #28 "Unknown PDU Session Type" to be included in the 5GSM cause IE of the PDU Session Modification Reject message.

[0308] If the PDU Session Modification Request message is for establishing a MA PDU Session, and if the PDU Session Modification Request message includes a PDU Session Type IE set to "Unstructured", and if the SMF settings do not support the PDU Session Type, the SMF can include a 5GSM cause value #28 "Unknown PDU Session Type" in the 5GSM cause IE of the PDU Session Modification Reject message.

[0309] The network can cause a Back-off timer value IE to be included in the PDU Session Modification Reject message.

[0310] If the 5GSM cause value is #50 "PDU Session Type IPv4 only allowed", #51 "PDU Session Type IPv6 only allowed", #57 "PDU Session Type IPv4v6 only allowed", #58 "PDU Session Type Unstructured only allowed", or #61 "PDU Session Type Ethernet only allowed", the network can include the Re-attempt indicator without a back-off timer value in order to indicate whether the UE is allowed to attempt a PDU session modification procedure in an equivalent PLMN in N1 mode of the same PDU session type using the same DNN and the same S-NSSAI.

[0311] The SMF can send the PDU session modification reject message.

[0312] Upon receiving a PDU session modification reject message and a PDU session ID through a NAS transport procedure, the UE can stop timer T3580, release the allocated PTI value, and consider the PDU session not established.

[0313] If the 5GSM cause value is #28 "Unknown PDU session type" and the PDU session modification request message includes a PDU session IE indicating a PDU session type, the UE can ignore the back-off timer value IE and the re-timing indicator provided by the network. The UE can send another PDU session modification request message to establish a new PDU session using a PDU session type IE indicating another PDU session type.

[0314] If the 5GSM cause value is #50 "PDU Session Type IPv4 only allowed", #51 "PDU Session Type IPv6 only allowed", #57 "PDU Session Type IPv4v6 only allowed", #58 "PDU Session Type Unstructured only allowed" or #61 "PDU Session Type Ethernet only allowed", the UE can ignore the re-attempt timer value IE provided by the network. The UE can evaluate the available USRP rules. The UE cannot directly send a different PDU session modification request message to the same DNN and the same HPLMN S-NSSAI for obtaining a different PDU session type than the one allowed by the network until one of the following conditions is met.

[0315] a) if at the reception of the PDU session modification reject message, the UE is registered to a new PLMN which is not listed in the list of equivalent PLMNs,

[0316] b) if at the reception of the PDU session modification reject message, the UE is registered in a new PLMN which is present in the list of equivalent PLMNs, and if the network does not include a Re-attempt indicator in the PDU session modification reject message, or if the network does not include a Re-atempt indicator in the message indicating that a retry is allowed in the equivalent PLMN,

[0317] c) if the UE is powered off, or

[0318] d) if the USIM is removed, or if the entry in the "Subscriber Data List" for the current SNPN is updated because the UE does not support access to SNPNs, or if the entry in the "Subscriber Data List" is updated although the UE supports access to SNPNs,

[0319] Then for 5GSM cause value #50 "PDU Session Type IPv4 only allowed", 5GSM cause value #51 "PDU Session Type IPv6 only allowed", 5GSM cause is value #57 "PDU Session Type IPv4v6 only allowed", 5GSM cause is value #58 "PDU Session Type Unstructured only allowed" and 5GSM cause is value #61 "PDU Session Type Ethernet only allowed", the UE can ignore the value of the Radio Access Technology Change (RATC) bit in the Re-attempt indicator IE provided by the network.

[0320] <Packet Switching Data Off Functionality>

[0321] Data service usage of users is increasing dramatically and data usage of mobile communication networks is increasing. Therefore, schemes are discussed for operators to limit unnecessary background traffic or unwanted data (or signaling) usage of users by terminals. Among these schemes, PS Data Off is introduced in EPS and 5GS.

[0322] When 3GPP PS Data Off is activated by a user, it prevents traffic (traffic of all IP (Internet Protocol) packets, unstructured and Ethernet data) over 3GPP access except for data related to 3GPP Data Off Exempt Services (hereinafter also referred to as "exempt services").

[0323] 3GPP Data Off Exempt Services are services that are allowed even if 3GPP PS Data Off is activated by a user. 3GPP Data Off Exempt Services are a set of operator services. 5GC supports 3GPP PS Data Off operation in non-roaming and roaming scenarios.

[0324] Examples of 3GPP Data Off Exempt Services are as follows:

[0325] - MMTel (Multimedia Telephony) Voice;

[0326] - SMS over IMS (IP Multimedia Subsystem);

[0327] - USSD (Unstructured Supplementary Services Data) over IMS (USSI: USSD simulation service in IMS);

[0328] - MMTel Video;

[0329] - particular IMS services not defined by 3GPP, where each such IMS service is identified by an IMS communication service identifier;

[0330] - Device Management over PS; and

[0331] - IMS Supplementary Service configuration via the Ut interface using XCAP.

[0332] Basically, if the user activates PS Data Off, the UE cannot perform uplink transmissions (e.g. mobile originating data transmissions) and downlink data reception (e.g. mobile terminated data reception) except for exempted services.

[0333] The terminal can cause the PSData OFF status (activated or deactivated) to be included in the protocol configuration option (PCO) of the Attach Request, PDN connectivity Request (per APN), Bearer Resource Modification Request (per APN) message, PDU Session Modification Request message and indicate to the network. The network can inform the support of PSData OFF for this APN by accepting (Accept) or rejecting (Reject).

[0334] Even if the operation related to PSData Off is performed between the terminal and the network, for the operator-defined exempted services, the transmission of uplink data and downlink data must be able to be performed in the state in which PSData Off is activated. Such an exempted service list can be provided to the terminal in advance by the operator's network through MO (Management Object; NAS configuration MO or new MO configuration) via OMA DM (Open Mobile Alliance Device Management) or through USIM.

[0335] In other words, when the user activates PSData Off, the terminal cannot perform uplink data transmission to the PDN associated with a service other than the service included in the exempted service list. The activation or deactivation of PSData Off can be generally set by the user.

[0336] For a UE, a list of up to two 3GPP data off exempted services can be provisioned to the UE by the HPLMN (Home PLMN) through Device Management or UICC provisioning. If two lists are provisioned for the UE, one list is valid for the UE camping in the HPLMN and the other list is valid for any VPLMN in which the UE is roaming. If only one list is provisioned for the UE without indicating which PLMN the list is applicable to, the list can be valid for the home PLMN and any PLMN in which the UE is roaming.

[0337] NOTE 1: The operator must ensure the list of 3GPP data off exempted services provisioned to the UE and established in the network.

[0338] During the UE request PDU session establishment procedure, the UE can include its 3GPP PS Data Off status in the PCO and report to the (H-)SMF.

[0339] NOTE 2: The UE reporting of the 3GPP PS Data Off status during the UE request PDU session establishment procedure can also apply to the scenario where the UE switches to 3GPP access in the state where the UE is connected only through non-3GPP access after the user activates / deactivates 3GPP PS Data Off.

[0340] When 3GPP PS Data Off is activated, the UE blocks uplink transmission of uplink IP packets, unstructured and Ethernet data based on the pre-configured list of 3GPP Data Off exempted services.

[0341] The UE shall include the change of the UE's 3GPP PS Data Off in the PCO and report immediately using the UE initiated PDU session modification procedure. This also applies to the inter-RAT mobility scenario to NG-RAN and the scenario where the 3GPP PS Data Off status changes during the session management back-off timer running. For the UE moving out of the LADN area and the PDU session still remains, the UE has to report the change of the 3GPP PS Data Off status of the PDU session immediately.

[0342] The additional actions of the SMF on 3GPP Data Off can be controlled by local settings or policies of the PCF.

[0343] For PDU sessions used for IMS services, the 3GPP Data Off exempted services are performed in the IMS domain. The policies set in the (H-)SMF / PCF shall ensure that these services are always allowed when the UE's 3GPP Data Off status is set to "activated".

[0344] As mentioned above, for a UE supporting 3GPP PS data off, a list of up to two 3GPP Data Off exempted services can be set. The EF 3GPP PS DATA OFF USIM file can also set the list of exempted services. Where EF stands for elementary file and EF 3GPP PS DATA OFF stands for the EF associated with 3GPP PS Data Off. An example of the two exempted service lists is as follows:

[0345] A) the list of 3GPP PS data off exempted services used in the HPLMN or equivalent HPLMN (EHPLMN, Equivalent HPLMN); and

[0346] B) a list of 3GPP PS data off exempt services for VPLMN.

[0347] If only the list of A) above is set for the UE, this list can also be used for VPLMN.

[0348] If the UE supports 3GPP PS data off, the UE can include and provide the 3GPP ps data off UE status in the extended PCO IE during the UE request PDU session establishment procedure and the UE request PDU session modification procedure.

[0349] The network must support 3GPP PS data off.

[0350] The UE can indicate a change of the 3GPP PS data off status of a PDU session by using the UE request PDU session modification procedure.

[0351] When the 3GPP PS data off status is "active", the UE can perform the following example operations:

[0352] A) the UE does not send uplink IP packets over 3GPP access unless:

[0353] A-i) when the UE is in the HPLMN or EHPLMN of the UE, services specified in the list of 3GPP PS data off exempt services used in the HPLMN or EHPLMN;

[0354] A-ii) if only a list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN is set for the UE, when the UE is in the VPLMN of the UE, services specified in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN;

[0355] A-iii) if a list of 3GPP PS data off exempt services to be used in the VPLMN is set for the UE, services specified in the list of 3GPP PS data off exempt services to be used in the VPLMN;

[0356] A-iv) services specified in the EF3GPPPSDATAOFF USIM file; and

[0357] A-vi) uplink traffic according to the Extensible Markup Language (XML) Configuration Access Protocol (XCAP) of the procedures associated with the management of supplementary services for the Ut interface.

[0358] B) the UE does not send uplink Ethernet user data packets over 3GPP access; and

[0359] C) the UE does not send uplink non-typical user data packets over 3GPP access.

[0360] When the 3GPP PS data off status is not "active", the UE can send uplink user data packets without restriction.

[0361] 3GPP PS data off does not restrict the transmission of uplink user data packets over non-3GPP access.

[0362] <Network Slicing>

[0363] Figure 8 is an example diagram for explaining the concept of network slicing.

[0364] Network slicing (network slicing) means dividing one physical network into multiple virtual networks. Each divided network can be operated for a specific form of application service or subscriber and optimized. Based on cloud computing and virtualization technology, shared physical network resources can be dynamically and efficiently scheduled to logical network slices according to changes in user demand.

[0365] 5G network slicing consists of a set of network functions and settings for a specific use case or business model. Referring to FIG. 5, network slice 1 (Network Slice 1) represents eMBB (enhanced mobile broadband), network slice 2 represents V2X (vehicle to all), and network slice 3 represents an example of a 5G network slice that applies MIoT (massive IoT).

[0366] One network slice can span several domains, including a distributed cloud infrastructure and a wireless access network, in which a transport network operates, a core network. The basic principle of 5G network slicing design is to provide only the customized functions required to handle traffic for a specific use case. The network slice has the necessary customization capabilities and the ability to adapt to changes in demand.

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

[0368] In the ongoing 3GPP 5G mobile communication network of the IETF (Internet Engineering Task Force) DetNet (Deterministic Networking) WG (Working Group), the network slice is operated based on the Core Network (CN), and basically operates based on the Network Slice Instance information. The Network Slice Instance refers to the collective information of the resource and network function instances required to form the network slice. One network slice can be used in the entire Public Land Mobile Network (PLMN), or can be used in one or more Tracking Areas (TAs). One Network Slice Instance can be associated with one or several Single Network Slice Selection Assistance Information (S-NSSAI), and one S-NSSAI can be associated with one or several Network Slice Instances.

[0369] In the 3GPP 5G mobile communication network, one network slice is identified by one S-NSSAI. The S-NSSAI is composed of SST (Slice / Service type) and SD (Slice Differentiator), and the SST must be included in the S-NSSAI, while the SD can be selectively included or not included. In the current 3GPP technical specification, as shown in Table 2, a total of 6 SST types and values are defined as standards.

[0370] [Table 2]

[0371]

[0372] In addition, one or more S-NSSAI sets are referred to as NSSAI (Network Slice Selection Assistance Information). In the registration procedure of the 5G mobile communication network, the terminal requests a network slice connection to the core network using the NSSAI, 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 configured NSSAI is the configured NSSAI provided from the serving PLMN, the default configured NSSAI is the set NSSAI provided from the home PLMN, and the requested NSSAI is the NSSAI used when the terminal requests a connection to a specific network slice to the core network. The allowed NSSAI refers to the NSSAI in which the core network allows the terminal to connect to a specific network slice. In addition, the subscribed S-NSSAI means the S-NSSAI contained in the subscriber information.

[0373] The terminal can set and store the default set NSSAI in advance, or can be provided or updated from the core network. Each S-NSSAI in the default set NSSAI corresponds to the S-NSSAI of the subscriber NSSAI. The S-NSSAI in the requested NSSAI by the terminal means the S-NSSAI in the NSSAI previously established or allowed from the network. Finally, in general, the NSSAI or S-NSSAI used by the terminal means the NSSAI or S-NSSAI previously established or allowed from the network.

[0374] On the other hand, the terminal and the 5G mobile communication network basically receive or use the NSSAI information in the registration procedure process in order to support and manage the network slice connection. First, the terminal generally has a set NSSAI and an allowed NSSAI which is previously set and stored, and the allowed NSSAI is previously allowed and used by the network. If there is no allowed NSSAI from the network before, there can be no allowed NSSAI. During the registration procedure, the terminal transmits a registration request message including request NSSAI information to the network to request a connection with a specific network slice. At this time, the request NSSAI information refers to the case where there is no set NSSAI stored in the terminal or no allowed NSSAI stored, that is, the case where there is no available set NSSAI information. If there is no allowed NSSAI stored and there is a set NSSAI available, the set NSSAI is used as the request NSSAI information. Finally, if there is an allowed NSSAI available, the allowed NSSAI is used as the request NSSAI information. The core network, upon confirming the request NSSAI included in the registration request message transmitted by the terminal, responds to the terminal by including all of the set NSSAI, the allowed NSSAI, and the rejected NSSAI information set in the registration accept message. The terminal stores the set NSSAI, the allowed NSSAI, and the rejected NSSAI information provided through the registration accept message transmitted from the network, and uses it when requesting a network slice connection. However, in the case of the rejected NSSAI, since it is the NSSAI information rejected for use in the network, the terminal does not use the rejected NSSAI in principle. In this way, through the registration request procedure, the terminal and the network provide each other with the NSSAI information for network slice connection support and management, and set and manage it.

[0375] In addition, when the terminal transmits a PDU session establishment request message for data transmission to the network, the terminal transmits S-NSSAI information about a network slice to which an application involved in data transmission wants to be connected from the stored allowed NSSAI to the network, and the network confirms the S-NSSAI information included in the PDU session establishment request message transmitted by the terminal, and responds to accept if there is no problem.

[0376] In addition, in a case where network slice related information including NSSAI is changed due to a change in subscriber information or a mobile communication network policy, etc., the network can notify the terminal of the changed NSSAI information. In this case, the network can provide the terminal with modified NSSAI information through a generic UE configuration update procedure in which the AMF transmits a configuration update command message including configured NSSAI, allowed NSSAI, and rejected NSSAI information in the configuration update command message to the terminal, and the terminal updates and stores the received configured NSSAI, allowed NSSAI, and rejected NSSAI information. Then, the terminal performs a network slice connection request using the modified NSSAI information.

[0377] On the other hand, in the recent 3GPP Release 18 standard specification, an alternative S-NSSAI is defined when an S-NSSAI (e.g., S-NSSAI#1) for which a non-usable or congestion situation has occurred is referred to as an S-NSSAI (e.g., S-NSSAI#2) that is compatible / replacable in the existing allowed NSSAI. When a non-usable or congestion situation S-NSSAI (e.g., S-NSSAI#1) occurs in the network, a compatible / replacable S-NSSAI, i.e., an alternative S-NSSAI, is provided to the terminal to update. At this time, the alternative S-NSSAI can be provided to the terminal to update using a generic UE configuration update (Generic UE Configuration Update) procedure.

[0378] On the other hand, in the 3GPP Release 18 standard specification, a partial allowed NSSAI is defined, and the existing allowed NSSAI refers to an NSSAI that the network (AMF and / or SMF) informs that a requested NSSAI that the terminal wants to use in the terminal registration area allows a network slice service associated with the NSSAI information. At this time, the allowed NSSAI is applied on the PLMN or all TA list of the registration area. On the other hand, the partial allowed NSSAI is applied to the PLMN or some TA list of the registration area. Accordingly, in some TAs on the registration area, a network slice service associated with a corresponding partial allowed NSSAI (e.g., partial allowed NSSAI#1 - actually a specific S-NSSAI#1) is allowed, and in other TAs, a network slice service associated with a corresponding partial allowed NSSAI (e.g., partial allowed NSSAI#1 - actually a specific S-NSSAI#1) is not allowed. The partial allowed NSSAI information is provided to update through a registration procedure or a generic UE configuration update procedure.

[0379] <Optimization of data transmission and reception for CIoT devices>

[0380] CIoT IoT (Cellular Internet of Things) devices transmit and receive a small amount of data. Even though CIoT devices transmit and receive a small amount of data as described above, CIoT devices need to exchange a considerable amount of signals with a base station, and thus there is a problem of low efficiency.

[0381] In particular, it is expected that CIoT devices have a considerably high density within the coverage of a base station, and in this case, a considerably large amount of signals can overload the network.

[0382] Therefore, in order to solve these problems, attempts are made to optimize using a control plane (CP) for CIoT, and attempts are made to optimize using a user plane. This is explained as follows, respectively.

[0383] 1. Control Plane (CP) CIoT Optimization

[0384] This is a scheme that causes data to be transmitted by being included in a PDU at the NAS layer. This is a way of transmitting data on a control plane for transmitting a NAS message, without using a user plane setup required for existing data transmission.

[0385] 2. User Plane (UP) CIoT Optimization

[0386] In the case of no data transmission and reception, it does not release (delete) the UE context (i.e., UE id, AS security information, etc.) stored in the CIoT device and the base station, but allows the context to be maintained. In addition, in the case of no data transmission and reception, the CIoT device performs an RRC connection suspend (Suspend) procedure, instead of performing a release procedure. Therefore, when the CIoT device requests an RRC connection again, it can be quickly switched from an RRC idle mode to an RRC connected mode. That is, an RRC connection resume (Resume) procedure is performed, instead of a service request procedure for establishing a user plane. Therefore, the number of RRC signals that the CIoT device needs to transmit and receive in order to switch from an RRC idle mode (IDLE) to an RRC connected mode (CONNECTED) is significantly reduced.

[0387] <ciot5gsoptimizations>< / ciot5gsoptimizations>

[0388] CIoT 5GS optimization provides enhanced support for small amount of data and SMS transfer. A UE (User Equipment) that supports CIoT 5GS optimization can indicate in the registration procedure the 5GS CIoT network operation that the UE supports and prefers. The UE can indicate support for control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, N3 data transfer and header compression. In addition to the above indications, you can also indicate whether you prefer control plane CIoT 5GS optimization or user plane CIoT 5GS optimization, which is considered as a usage request. A UE that supports CIoT EPS optimization can also indicate in the registration procedure the EPS CIoT network operation that the UE can support. In addition to the support indication, it can also be indicated whether control plane CIoT EPS optimization or user plane CIoT EP optimization is preferred.

[0389] When requesting usage of CIoT 5GS optimization in the registration procedure, the UE can operate in NB-N1 mode or WB-N1 mode. A UE in NB-N1 mode can be indicated to always support control plane CIoT 5GS optimization.

[0390] In NB-N1 mode, when the UE requests CIoT 5GS optimization usage, the UE can not:

[0391] - can not require initial registration for emergency services.

[0392] - does not request establishment of a PDU session for emergency PDU session.

[0393] - does not indicate the UE's usage settings in the registration procedure. When the UE is in NB-N1 mode, the network can not indicate emergency service support to the UE.

[0394] Control plane CIoT 5GS optimization allows efficient transfer of user data (IP, Ethernet and unstructured data) or SMS messages over the control plane through the AMF without triggering user plane resource setup. Control plane CIoT 5GS optimization is mandatory in NB-N1 mode and optional in WB-N1 mode. Optional header compression for IP data and Ethernet data can be applied to PDU sessions of IP PDU session type and Ethernet PDU session type that are set to support header compression. IP header compression uses the robust header compression (ROHC) protocol specified in IETF RFC 5795 [39B] and Ethernet header compression (EHC) protocol.

[0395] For UEs supporting Location Services (LCS) notification mechanism in N1 mode, Control Plane CIoT 5GS optimization allows sending location service messages in 5GMM-IDLE mode using the CONTROL PLANE SERVICE REQUEST message when location services are requested.

[0396] User Plane CIoT 5GS optimization allows switching from 5GMM-IDLE mode to 5GMM-CONNECTED mode with 3GPP access support without using the service request procedure.

[0397] If the UE supports User Plane CIoT 5GS optimization, it also needs to support N3 data transfer.

[0398] The UE indicates that it supports one or more CIoT 5GS optimizations, and if the network supports one or more CIoT 5GS optimizations and decides to accept the registration request, the network indicates to the UE that it supports the CIoT 5GS optimizations per registration area upon acceptance of the UE request. The network's support indication is the authorization that the UE can use the feature. After the registration procedure is completed, the UE and the network can use the accepted CIoT 5GS optimizations to send user data (IP, Ethernet, unstructured data, and SMS).

[0399] A UE in NB-N1 mode or WB-N1 mode can request the use of SMS over NAS by setting the SMS request bit of the 5GS update type information element (IE) in the REGISTRATION REQUEST message. The AMF sets the SMS allowed bit of the 5GS registration result information element (IE) in the REGISTRATION ACCEPT message to indicate whether the UE in NB-N1 mode or WB-N1 mode is allowed to use SMS over NAS.

[0400] If the UE and the network support both Control Plane CIoT 5GS optimization and N3 data transfer, upon receiving the UE's PDU session establishment request, the AMF determines whether the PDU session should be a NEF PDU session or a N6 PDU session and performs the following operations:

[0401] a) If a NEF PDU session is set for unstructured data type, the AMF causes the inclusion of a control plane only indication in the SMF for the requested PDU session.

[0402] b) If a N6 PDU session is established and the DNN or S-NSSAI of the newly requested N6 PDU session supports association with EPS:

[0403] 1) For this UE, if there exists an N6 PDU session that supports interworking with EPS and contains only a control plane indication, the AMF sends an AMF containing only a control plane indication in the SMF for a newly requested N6 PDU session.

[0404] 2) For this UE, if there exists an N6 PDU session that previously supported interworking with EPS and contained only a control plane indication, the AMF causes an indication of only a control plane to be included in the SMF for a newly requested N6 PDL session and does not send the indication.

[0405] If no existing N6 PDU session supports interworking with the EPS of this UE, the AMF determines whether to include an indication of only a control plane in the SMF for a newly requested N6 PDU session based on local policy, the preferred CIoT network operation of the UE, and the supported CIoT network operation.

[0406] c) If an N6 PDU session is established and the DNN or S-NSSAI of the N6 PDU session does not support linking with EPS, the AMF determines whether to include an indication of only a control plane for a newly requested N6 PDU session in the SMF based on local policy, the preferred CIoT network operation of the UE, and the supported CIoT network operation.

[0407] In NB-N1 mode, if the UE or the network does not support N3 data transfer, when receiving a PDU session establishment request of the UE, the AMF determines whether the PDU session should be an NEF PDU session or an N6 PDU session, and includes only a control plane indication in the SMF for the requested PDU session to send.

[0408] If the network supports user plane CIoT 5GS optimization, it should also support N3 data transfer.

[0409] Broadcast system information can provide information about CIoT 5GS optimization support. Upon receiving new broadcast system information, the sublayer forwards it to the 5GMM layer of the UE. The information provided by the sublayer is provided per PLMN and is used by the UE to determine whether a particular CIoT 5GS optimization is supported in the unit.

[0410] The UE should not attempt to use a CIoT 5GS optimization that is indicated as not supported.

[0411] In NB-N1 mode, for PDU sessions that exceed the maximum number of user plane resources supported by the UE at a particular point in time, user plane resources cannot be set. The UE in NB-N1 mode does not do the following:

[0412] a) For PDU Sessions that exceed the maximum number of user plane resources supported by the UE, no user plane resource setup is requested.

[0413] b) If the following conditions are met, no initiation of a new PDU Session establishment or request to switch a PDU Session from non-3GPP access to 3GPP access is performed:

[0414] 1) The UE indicates preference for user plane CIoT 5GS optimization

[0415] 2) The network authorizes the use of user plane CIoT 5GS optimization.

[0416] 3) The number of PDU Sessions with current user plane resource setup by the UE is equal to the maximum number of user plane resources supported by the UE.

[0417] The AMF limits the number of PDU Sessions with active user plane resources for a UE in NB-N1 mode based on the maximum number of user plane resources supported by the UE:

[0418] a) If the multi-user plane resource support bit is set to "multi-user plane resource not supported", there can be active user plane resources for at most one PDU Session.

[0419] b) If the multi-user plane resource support bit is set to "multi-user plane resource supported", there can be active user plane resources for at most two PDU Sessions.

[0420] A PDU Session for a UE in NB-N1 mode has only one QoS rule, which is the basic QoS rule. Reflective QoS is not supported in NB-N1 mode. Reflective QoS is not applicable for PDU Sessions with an indication of control plane only.

[0421] In NB-N1 mode, when the UE requests to establish an RRC connection to lower layers and requests to use user plane CIoT 5GS optimization, the UE shall pass to lower layers an indication of the requested CIoT 5GS optimization. If the UE requests to use N3 data transfer without user plane CIoT 5GS optimization, the UE must also send to lower layers an indication of user plane CIoT 5GS optimization.

[0422] In WB-N1 mode, when the UE requests to establish an RRC connection to lower layers and requests to use control plane CIoT 5GS optimization or user plane CIoT 5GS optimization, the UE must pass to lower layers an indication of the requested CIoT 5GS optimization.

[0423] Control plane CIoT 5GS optimization: includes selective header compression for IP data and Ethernet data with signal optimization that allows efficient transmission of user data (IP, Ethernet, unstructured data, or SMS) over the control plane by the AMF.

[0424] User plane CIoT 5GS optimization: signal optimization that enables efficient transmission of user data (IP, Ethernet, or unstructured data) over the user plane.

[0425] UE supporting CIoT 5GS optimization: refers to a UE that supports control plane CIoT 5GS optimization or user plane CIoT 5GS optimization and one or more other CIoT 5GS optimization in N1 mode.

[0426] Status of registration to 5GS service through control plane CIoT 5GS optimization: status in which a UE supporting CIoT 5GS optimization is registered to a 5GS service, control plane CIoT 5GS optimization and one or more other CIoT 5GS optimization have been authorized by a network.

[0427] Status of registration of user plane CIoT 5GS optimization to 5GS service: status in which a UE supporting CIoT 5GS optimization is registered to a 5GS service, user plane CIoT 5GS optimization and one or more other CIoT 5GS optimization have been authorized by a network.

[0428] Status of registration of CIoT 5GS optimization to 5GS service: status in which a UE is registered to a 5GS service for control plane CIoT 5GS optimization or is registered to a 5GS service for user plane CIoT 5GS optimization.

[0429] UE using 5GS service using control plane CIoT 5GS optimization: refers to a UE registered to a 5GS service in the case in which control plane CIoT 5GS optimization is authorized by a network.

[0430] Figure 9 FIG. 1 is an example diagram illustrating a procedure according to one embodiment of the disclosure.

[0431] As Figure 9 shown, a UE transmits a registration request message.

[0432] At this time, the UE can transmit by including a UE MM core network capability in the registration request message. The UE MM core network capability can include information indicating that it supports a UE configuration of network-controlled slice usage policy. Alternatively, the UE MM core network capability can include information indicating that it supports temporarily available network slices.

[0433] The UE receives a registration accept message.

[0434] The registration accept message can include at least one of a valid time for at least one single network slice selection assistance information (S-NSSAI).

[0435] When the at least one S-NSSAI is included in an allowed NSSAI or a partially allowed NSSAI, the UE can establish at least one protocol data unit (PDU) session associated with the at least one S-NSSAI.

[0436] If at least one PDU session is set for at least one S-NSSAI included in the partially allowed NSSAI, and a current tracking area identifier (TAI) is not included in a tracking area (TA) list of the allowed S-NSSAI, the UE can not initiate a UE-initiated non-access stratum (NAS) transfer procedure for transmitting CIoT user data or a request procedure for transmitting a service of a CIoT user.

[0437] If the UE does not trigger a mobility registration update procedure, and the allowed NSSAI becomes empty after the valid time expires, the UE can implicitly enter a deregistered state.

[0438] <Organization of Embodiments of the Present Specification>

[0439] I. Optimized Processing of Temporarily Available Network Slices

[0440] A network slice can be offered to all UEs and to a subset of UEs for a limited time known in advance in the network. For example, the limited time usage can occur if the network slice is in a temporary or periodic active state in the deployment environment (e.g., activated only for a limited time to support an event, or UEs have access to the network slice only for a limited time known in advance), or if the network slice is planned to be released after a specific point in time. This feature is handled by S-NSSAI validity time to reduce the signaling load related to RM and SM state switching with the network and the UE.

[0441] The UE can indicate whether support of a network slice that is temporarily available in the UE MM core network functions of the registration request. AMF The UE can be based on information received from OAM configuration or UDM or NSSF, by the registration accept message for the supported UE the configuration NSSAI or UE configuration update procedure, indicating the validity time of one or more S-NSSAI For roaming, the AMF can include the validity time of S-NSSAIs in the NSSAI configured due to limited availability of VPLMN S-NSSAI or mapped S-NSSAI of HPLMN.

[0442] a) if the validity time indicates that the S-NSSAI is available, then:

[0443] The UE can cause the inclusion of S-NSSAI in the requested NSSAI of the registration request, and if the S-NSSAI is included in the allowed NSSAI or partially allowed NSSAI, the UE can establish a PDU session associated with the S-NSSAI. b) if the validity time indicates that the S-NSSAI is not available, then: if the UE does not trigger mobility registration update, and the allowed NSSAI becomes empty after the validity time expires, the UE must implicitly enter the RM-DEREGISTERED state

[0444] if the S-NSSAI is included in the partially allowed NSSAI, then:

[0445] - Regardless of whether the validity time information is received, the UE shall not cause the S-NSSAI to be included in the requested NSSAI for all access types.

[0446] - If the S-NSSAI is already allowed NSSAI or part of allowed NSSAI, the UE shall remove the S-NSSAI from the locally stored allowed NSSAI or part of allowed NSSAI and shall also locally release the PDU session associated with the S-NSSAI.

[0447] - If the validity time indicates that the S-NSSAI is no longer available, the UE must remove the S-NSSAI from the locally stored configured NSSAI.

[0448] A UE supporting only a temporarily available network slice includes only one S-NSSAI in the allowed NSSAI with a valid time with a predetermined expiry and, if there is no waiting NSSAI, the UE can trigger a mobility registration update in order to attempt registration with the other still available S-NSSAI if there is one in the configured NSSAI. if the existing PDU session is set for the S-NSSAI included in the partially allowed NSSAI, and the current TAI is in the TA list allowing the S-NSSAI, then: - initiate the UE-initiated NAS transport procedure or service request procedure to send CIoT user data to the SMF. if the existing PDU session is set for the S-NSSAI included in the partially allowed NSSAI, and the current TAI is not in the TA list allowing the S-NSSAI, then: .

[0449] For a supporting UE, if a valid time applies to an S-NSSAI, the AMF supporting a temporarily available network slice must perform the following operations:

[0450] If the UE includes an S-NSSAI in the requested NSSAI of the registration request and the valid time indicates that the S-NSSAI is not available but will be available again (i.e., if it is detected that the UE does not have the latest valid time information), the AMF sends the configured NSSAI of the registration accept message to the UE including the valid time for the S-NSSAI. If the valid time indicates that the S-NSSAI is not available and will not be available again, the AMF excludes the S-NSSAI from the configured NSSAI and sends it to the UE.

[0451] If an S-NSSAI is contained in the allowed NSSAI or the partial allowed NSSAI of the UE and the valid time indicates that the S-NSSAI is not available, the S-NSSAI is removed locally at the allowed NSSAI or the partial allowed NSSAI (i.e., not signaled to the UE). If a PDU session is set for the S-NSSAI, the AMF requests the release of the PDU session from the SMF:

[0452] When the UE is in CM-CONNECTED state, the AMF requests the PDU session release from the SMF by Nsmf_PDUSession_UpdateSMContext request and forwards the N2 SM request to release the AN resources associated with the PDU session.

[0453] When the UE is in CM-IDLE state, the AMF releases the PDU session locally without paging the UE and releases the SM context for the UE locally by Nsmf_PDUSession_ReleaseSMContext. The PDU session status is synchronized when the UE subsequently connects to the network.

[0454] If, after the expiry of the valid time, the S-NSSAI is no longer present in the allowed NSSAI or the partial allowed NSSAI after the AMF removes it locally, the AMF must implicitly enter the RM-DEREGISTERED state for the UE.

[0455] II. Session management for partial network slices

[0456] 2) do not initiate the UE-initiated NAS transport procedure to send CIoT user data to the SMF, nor initiate the service request procedure to send CIoT user data to the SMF.

[0457] a) If the current Tracking Area Identifier (TAI) is in the list of TA(s) allowed for the S-NSSAI, the UE can initiate the UE-requested PDU session establishment procedure for the S-NSSAI.

[0458] b) If the current TAI is not in the list of TA(s) allowed for the S-NSSAI, the UE shall not initiate the UE-requested PDU session establishment procedure for the S-NSSAI.

[0459] 2) do not initiate the network-initiated NAS transport procedure for transferring CIoT user data to the UE. b) initiate the network-initiated NAS transport procedure for transferring CIoT user data to the UE.

[0460] a) The UE can perform:

[0461] - initiate a service request procedure in order to re-establish user plane resources for the established PDU session.

[0462] if the UE is outside the NS-AoS (network slice allowed service area) of the S-NSSAI, then the UE shall not perform the following actions:

[0463] b) The SMF can initiate the network-initiated NAS transport procedure to transport CIoT user data to the UE.

[0464] b) the UE-initiated NAS transport procedure for transferring CIoT user data to the SMF, or the service request procedure for transferring CIoT user data to the SMF. b) shall not initiate the network-initiated NAS transport procedure for transferring CIoT user data to the UE.

[0465] a) The UE must perform:

[0466] 1) preserve the 5GSM context for the established PDU session.

[0467] b) initiate the network-initiated NAS transport procedure for transferring CIoT user data to the UE. Figure 10

[0468] The UE can perform the following operations:

[0469] i) initiate the UE-requested PDU session release procedure; or

[0470] ii) initiate the UE-requested PDU session modification procedure to set the 3GPP PS data off status to "deactivated".

[0471] b) The SMF must:

[0472] 1) preserve the 5GSM context for the established PDU session.

[0473] Figure 11

[0474] 3) initiate the network-requested PDU session release procedure.

[0475] If the SMF cannot determine whether the UE is located in a TA of the TA list associated with the S-NSSAI, the SMF can perform the following actions according to operator's policy:

[0476] a) attempt to establish user plane resources for the PDU session, or

[0477] Figure 11

[0478] III. Session management aspects of network slice handling with NS-AoS (Network Slice Allowed Service Area) that does not match the distributed tracking area

[0479] ​ ​

[0480] a) shall not attempt to set up user plane resources for the PDU session associated with the S-NSSAI.

[0481] ​ ​

[0482] If the UE is outside the NS-AoS of the S-NSSAI, the SMF shall not perform the following actions:

[0483] a) shall not attempt to set up user plane resources for the PDU session associated with the S-NSSAI.

[0484] ​

[0485] If the UE is outside the NS-AoS of the S-NSSAI, the UE can initiate a UE-initiated NAS transport procedure including the following 5GSM messages for the PDU session associated with the S-NSSAI:

[0486] a) a PDU session release request message or

[0487] b) a PDU session modification request (PDU SESSION MODIFICATION REQUEST) message to set the 3GPP PS data off status to "deactivated".

[0488] If the SMF cannot determine whether the UE is located in the NS-AoS of the S-NSSAI for which an existing PDU session has been established, the SMF can perform the following actions according to operator's policy:

[0489] a) attempt to set up user plane resources for the PDU session, or

[0490] ​

[0491] ​ is a block diagram illustrating a configuration of a terminal according to one embodiment of the disclosure.

[0492] The 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.

[0493] The processor 1020 can be configured to implement proposed functions, procedures, and / or methods described herein. Layers of the radio interface protocol can be implemented in the processor 1020. The processor 1020 can include an application processor (AP). The processor 1020 can include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem, or a communication processor (CP). An example of the processor 1020 can be a series of SNAPDRAGON™ processors manufactured by Qualcomm, a series of EXYNOS™ processors manufactured by Samsung, a series of A processors manufactured by Apple, a series of HELIO™ processors manufactured by MediaTek, a series of ATOM™ processors manufactured by INTEL, or corresponding next-generation processors.

[0494] The power management module 1091 manages 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 a result processed by the processor 1020. The input unit 1053 receives an input to be used by the processor 1020. The input 1053 can be displayed on the display 1041. The SIM card is an integrated circuit for securely storing an international mobile subscriber identity (IMSI) and related key, which is used to identify and authenticate subscribers in mobile telecommunication devices such as mobile phones and computers. Contact information can be stored on many SIM cards.

[0495] The memory 1010 is operatively coupled to the processor 1020 and stores information related to various functions of the processor 1020. The memory 1010 can include read-only memory (ROM), random-access memory (RAM), flash memory, memory cards, storage media and / or other storage devices. When the embodiments are implemented in software, the techniques described herein can be implemented using a suitably programmed processor 1020. The processor 1020 can be programmed using software and / or firmware. The software and / or firmware can be stored in the memory 1010 and / or other storage medium. The memory 1010 can be implemented within the processor 1020 or external to the processor 1020 in which case it can be communicatively coupled to the processor 1020 via various means as is known in the art.

[0496] The transceiver 1031 is operatively coupled to the processor 1020 and transmits and / or receives a radio signal. The transceiver 1031 includes a transmitting unit and a receiving unit. The transceiver 1031 can include a baseband circuit for processing a radio frequency signal. The transceiver 1031 controls one or more antennas to transmit and / or receive a radio signal. The processor 1020 transmits instruction information to the transceiver 1031 in order to transmit a radio signal, for example, constituting voice communication data, to initiate communication. The antenna is used to transmit and receive a radio signal. When a radio signal is received, the transceiver 1031 can transmit the signal and convert the signal to a baseband in order to be processed by the processor 1020. The processed signal can be converted into audible or readable information output via the speaker 1042.

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

[0498] The user inputs command information, such as a phone number, for example, by pressing (or touching) a button of the input unit 1053 or by voice activation using the microphone 1052. The processor 1020 receives the instruction information and performs an appropriate function, for example, dialing the phone number. Operation data can be extracted from the SIM card or the memory 1010. In addition, the processor 1020 can display the instruction information or driving information on the display 1041 to facilitate user recognition and convenience.

[0499] ​ A configuration block diagram of a processor in which the present disclosure is implemented is shown.

[0500] As will be appreciated by those skilled in the art, the present disclosure can be embodied in a processor that operates as a standalone device or can be embodied in a processor that forms part of a multi-processor system. As will also be appreciated by those skilled in the art, aspects of the present disclosure can be embodied as a method, an apparatus such as a special purpose apparatus, an system, a device such as a computer program product, an apparatus, or as an article of manufacture that can be used in the practice of the technology. The computer program product can be implemented in a non-transitory computer readable storage medium such as a flash drive, a floppy drive, a CD-ROM, and the like, and can contain digital information, e.g., software, delivered either in a pre-compiled form or in human language that can be translated and compiled or interpreted to be executed by a machine. ​Among the seen, the processor 1020 implementing the disclosure can include a plurality of circuits to implement the proposed functions, processes, and / or methods described herein. For example, the processor 1020 can include a first circuit 1020-1, a second circuit 1020-2, and a third circuit 1020-3. Also, although not shown, the processor 1020 can include more circuits. Each circuit can include a plurality of transceivers.

[0501] The first circuit 1020-1 can receive a registration accept message including a validity time for at least one S-NSSAI (single network slice selection support information).

[0502] The second circuit 1020-2 can establish at least one protocol data unit (PDU) session associated with the at least one S-NSSAI in a case where the at least one S-NSSAI is included in an allowed NSSAI or a partially allowed NSSAI.

[0503] The third circuit 1020-3 can not initiate a UE-initiated non-access stratum (NAS) transport procedure for transmitting cellular internet of things (CIoT) user data or a service request procedure for transmitting cellular internet of things (CIoT) user data in a case where at least one PDU session is set for at least one S-NSSAI included in a partially allowed NSSAI and a current tracking area identifier (TAI) is not included in an allowed tracking area (TA) list for the S-NSSAI.

[0504] The fourth circuit (not shown) can implicitly enter a deregistered state in a case where the UE does not trigger a mobility registration update procedure and the allowed NSSAI becomes empty after the validity time expires.

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

[0506] The processor can be mounted on the UE.

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

[0508] In the above exemplary systems, the methods are described as a series of steps or blocks in a flowchart according to the flowcharts, but are not limited to the order of the steps described, and certain steps can occur in different orders or concurrently with the steps described above. Also, a person having ordinary skill in the art will understand that the steps shown in the flowcharts are not exclusive and other steps can be included or one or more of the steps in the flowcharts can be deleted without affecting the scope of the claims.

[0509] The claims described herein can be combined in various ways. For example, the technical features of the method claims of the present specification can be combined to be implemented as an apparatus, and the technical features of the apparatus claims of the present specification can be combined to be implemented as an apparatus. Furthermore, the technical features of the method claims can be combined with the technical features of the apparatus claims to be implemented as an apparatus, and the technical features of the method claims can be combined with the technical features of the apparatus claims to be implemented.

Claims

1. A method executed by a user equipment, characterized in that, Includes the following steps: Receive a registration acceptance message, which includes the validity period for selecting auxiliary information for at least one single network slice; If the at least one single network slice selection assistance information is included in the allowed network slice selection assistance information or in the partially allowed network slice selection assistance information, then at least one protocol data unit session associated with the at least one single network slice selection assistance information is established. If at least one Protocol Data Unit session is established for at least one single network slice selection assistance information included in partially permitted network slice selection assistance information, and the current tracking area identifier is not included in the tracking area list that allows said single network slice selection assistance information, then a non-access stratum transmission procedure initiated by the user equipment for transmitting cellular IoT user data is not initiated, nor is a service request procedure for transmitting cellular IoT user data initiated. as well as If the user equipment does not trigger the mobility registration update process and the allowed network slice selection assistance information becomes empty after the expiration of the validity period, it implicitly enters the deregistration state.

2. The method according to claim 1, characterized in that, It also includes the following steps: If a protocol data unit session is established for at least one single network slice selection assistance information included in the partially allowed network slice selection assistance information, and if the current tracking area identifier is in the tracking area list that allows the single network slice selection assistance information, then the user equipment initialization NAS transmission procedure for sending the cellular IoT user data or the service request procedure for sending the cellular IoT user data is initiated.

3. The method according to claim 1, characterized in that, It also includes the following steps: Send a registration request message.

4. The method according to claim 1, characterized in that, It also includes the following steps: If the validity period indicates that the single network slice selection assistance information is available, a registration request message including the requested network slice selection assistance information is sent.

5. The method according to claim 1, characterized in that, It also includes the following steps: If the validity period indicates that the single network slice selection assistance information is unavailable, then the single network slice selection assistance information is not included in the requested network slice selection assistance information.

6. A user equipment, characterized in that, The user equipment includes: At least one processor; and At least one computer memory operably connected to the at least one processor and storing instructions. When executed by the at least one processor, the instruction performs the following steps: Receive a registration acceptance message, which includes the validity period for selecting auxiliary information for at least one single network slice; If the at least one single network slice selection assistance information is included in the allowed network slice selection assistance information or in the partially allowed network slice selection assistance information, then at least one protocol data unit session associated with the at least one single network slice selection assistance information is established. If at least one Protocol Data Unit (TCP / IP) session is established for at least one single network slice selection assistance information included in partially permitted network slice selection assistance information, and the current tracking area identifier is not included in the tracking area list that allows said single network slice selection assistance information, then a non-access stratum transmission procedure initiated by the user equipment (UE) for transmitting cellular IoT user data, and a service request procedure for transmitting cellular IoT user data, are not initiated; and If the user equipment does not trigger the mobility registration update process and the allowed network slice selection assistance information becomes empty after the expiration of the validity period, it implicitly enters the deregistration state.

7. The user equipment according to claim 6, characterized in that, The operation may also include the following steps: If a protocol data unit session is established for at least one single network slice selection assistance information included in the partially allowed network slice selection assistance information, and if the current tracking area identifier is in the tracking area list that allows the single network slice selection assistance information, then the user equipment initialization NAS transmission procedure for sending the cellular IoT user data or the service request procedure for sending the cellular IoT user data is initiated.

8. The user equipment according to claim 6, characterized in that, The operation may also include the following steps: Send a registration request message.

9. The user equipment according to claim 6, characterized in that, The operation may also include the following steps: If the validity period indicates that the single network slice selection assistance information is available, a registration request message including the requested network slice selection assistance information is sent.

10. The user equipment according to claim 6, characterized in that, The operation may also include the following steps: If the validity period indicates that the single network slice selection assistance information is unavailable, then the single network slice selection assistance information is not included in the requested network slice selection assistance information.

11. A semiconductor chipset equipped in a user equipment, characterized in that, include: At least one processor; as well as At least one memory capable of storing instructions and operatively electrically connected to the at least one processor. The operations performed when the instruction is executed by the at least one processor include the following steps: Receive a registration acceptance message, which includes the validity period for selecting auxiliary information for at least one single network slice; If the at least one single network slice selection assistance information is included in the allowed network slice selection assistance information or in the partially allowed network slice selection assistance information, then at least one protocol data unit session associated with the at least one single network slice selection assistance information is established. If at least one Protocol Data Unit session is established for at least one single network slice selection assistance information included in partially permitted network slice selection assistance information, and the current tracking area identifier is not included in the tracking area list that allows said single network slice selection assistance information, then a non-access stratum transmission procedure initiated by the user equipment for transmitting cellular IoT user data is not initiated, nor is a service request procedure for transmitting cellular IoT user data initiated. as well as If the user equipment does not trigger the mobility registration update process and the allowed network slice selection assistance information becomes empty after the expiration of the validity period, it implicitly enters the deregistration state.

12. The semiconductor chipset according to claim 11, wherein, The operation may also include the following steps: If a protocol data unit session is established for at least one single network slice selection assistance information included in the partially allowed network slice selection assistance information, and if the current tracking area identifier is in the tracking area list that allows the single network slice selection assistance information, then the user equipment initialization NAS transmission procedure for sending the cellular IoT user data or the service request procedure for sending the cellular IoT user data is initiated.

13. The semiconductor chipset according to claim 11, characterized in that, The operation may also include the following steps: Send a registration request message.

14. The semiconductor chipset according to claim 11, characterized in that, The operation may also include the following steps: If the validity period indicates that the single network slice selection assistance information is available, a registration request message including the requested network slice selection assistance information is sent.

15. The semiconductor chipset according to claim 11, characterized in that, The operation may also include the following steps: If the validity period indicates that the single network slice selection assistance information is unavailable, then the single network slice selection assistance information is not included in the requested network slice selection assistance information.

Images