Communications related to PS data shutdown

Abstract

A disclosure of the present specification provides a method for a UE to perform communications related to PS data shutoff. The method may include the following steps: sending a first PDU session establishment request message to facilitate establishment of a PDU session associated with a non-3GPP access or a 3GPP access; and sending a second PDU session establishment request message to facilitate handover between the non-3GPP access and the 3GPP access of a PDU.

Description

Technical Field

[0001] The present disclosure relates generally to mobile communications. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for high-speed packet communications. Many proposals have been made for LTE, including those aimed at reducing user and provider costs, improving service quality, and expanding and increasing coverage and system capacity. 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of frequency bands, a simple architecture, open interfaces, and sufficient power consumption in terminals as upper layer requirements.

[0003] Work has begun within the International Telecommunication Union (ITU) and 3GPP to develop the requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary for successful standardization of the new RAT in a timely manner to meet both immediate market needs and the longer-term requirements outlined by the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR should be able to use any spectrum band up to at least 100 GHz, which will be available for wireless communications even in the more distant future.

[0004] NR aims to address all use cases, requirements, and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable and low-latency communications (URLLC), etc., with a single technology framework. NR should be inherently forward-compatible.

[0005] In addition, in 5G mobile communications, the 3rd Generation Partnership Project (3GPP) Packet Switched (PS) Data Off function can be used. However, conventionally, when 3GPP PS Data Off is used for Packet Data Unit (PDU) sessions associated with non-3GPP access, no method for supporting effective communication has been discussed. Summary of the Invention

[0006] Technical issues

[0007] Therefore, the disclosure of this specification has been made in an attempt to solve the above-mentioned problems.

[0008] Technical Solution

[0009] To solve the above problem, the present invention provides a method for a UE to perform communication related to PS data shutoff, wherein the method may include sending a first PDU session establishment request message to establish a PDU session associated with non-3GPP access or 3GPP access.

[0010] To address the above-mentioned issues, one disclosure of this specification provides a method for a network node to perform PS data off-related communications. The method includes the following steps: receiving last report information related to the PS data off state from a UE; and determining whether to apply PS data off to the PDU session based on the last report information and the access type of the UE's PDU session.

[0011] To address the above-mentioned issues, the present invention discloses a UE performing communications related to PS data shutoff. The UE includes: at least one processor; and at least one memory configured to store instructions and electrically connected to the at least one processor. The operations performed based on the instructions executed by the at least one processor include: sending a first PDU session establishment request message to establish a PDU session related to non-3GPP access or 3GPP access.

[0012] To address the above-mentioned issues, one disclosure of the present specification provides a network node that performs communications related to PS data off. The network node includes at least one processor; and at least one memory configured to store instructions and electrically connected to the at least one processor. Operations performed based on the instructions executed by the at least one processor include: receiving last reported information related to a PS data off state; and determining whether to apply PS data off to a PDU session of a UE based on the last reported information and an access type of the PDU session.

[0013] To address the aforementioned issues, one disclosure of this specification provides a mobile communication device. The mobile communication device includes at least one processor; and at least one memory storing instructions and electrically connected to the at least one processor, wherein the instructions are executed based on execution by the at least one processor. The operations may include generating a first PDU session establishment request message to establish a PDU session associated with a non-3GPP access or a 3GPP access.

[0014] To address the above-mentioned issues, one disclosure of this specification provides a non-volatile computer-readable storage medium recording instructions. When executed by one or more processors, the instructions cause the one or more processors to perform the following operations: generating a first PDU session establishment request message to establish a PDU session associated with a non-3GPP access or a 3GPP access.

[0015] Beneficial effects

[0016] According to the disclosure of this specification, the problems of the prior art can be solved.

[0017] The effects that can be obtained through the specific examples of this specification are not limited to the effects listed above. For example, there may be various technical effects that can be understood by a person of ordinary skill in the relevant field or derived from this specification. Therefore, the specific effects of this specification are not limited to those explicitly described herein, and may include various effects that can be understood or derived from the technical features of this specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 An example of a communication system to which an embodiment of the present disclosure is applied is shown.

[0019] Figure 2 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0020] Figure 3 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0021] Figure 4 It is a structural diagram of the next generation mobile communication network.

[0022] Figure 5 This is an example diagram illustrating the predicted structure of next-generation mobile communications based on nodes.

[0023] Figure 6 is an exemplary diagram illustrating an architecture that allows a UE to access two data networks simultaneously using one PDU session.

[0024] Figure 7 is another exemplary diagram showing the structure of the radio interface protocol between the UE and the gNB.

[0025] Figure 8a and Figure 8b is a signal flow diagram illustrating an exemplary registration process.

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

[0027] Figure 10a and Figure 10b is a signal flow diagram illustrating an exemplary PDU session modification procedure.

[0028] Figures 11a to 11c is a signal flow diagram illustrating an exemplary UE-initiated service request procedure.

[0029] Figure 12 is a signal flow diagram illustrating an exemplary network-initiated service request process.

[0030] Figure 13 An example of generating an MA PDU session is shown.

[0031] Figure 14a and Figure 14b An example of operations of a terminal and a network according to the first example of the disclosure of this specification is shown.

[0032] Figure 15 An example of the operation of the terminal according to the first example disclosed in this specification is shown.

[0033] Figure 16 An example of operations of a terminal and a network according to the second example of the disclosure of this specification is shown.

[0034] Figure 17 An example of operations of a terminal and a network according to the third example of the disclosure of this specification is shown. DETAILED DESCRIPTION

[0035] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented using radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE adopts OFDMA in the DL and SC-FDMA in the UL. 3GPP LTE's evolution includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0036] For ease of description, implementations of the present disclosure will be primarily described with respect to a 3GPP-based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is based on a mobile communication system corresponding to a 3GPP-based wireless communication system, aspects of the present disclosure that are not limited to 3GPP-based wireless communication systems are applicable to other mobile communication systems.

[0037] For terms and technologies used in this disclosure that are not specifically described, reference may be made to wireless communication standard documents published prior to this disclosure. For example, reference may be made to the following documents.

[0038] In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in the present disclosure may be interpreted as "A and / or B". For example, "A, B, or C" in the present disclosure may mean "only A", "only B", "only C", or "any combination of A, B, and C".

[0039] In the present disclosure, a slash ( / ) or a comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0040] In the present disclosure, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, the expression “at least one of A or B” or “at least one of A and / or B” in the present disclosure may be interpreted as being the same as “at least one of A and B”.

[0041] In addition, in the present disclosure, “at least one of A, B, and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.” In addition, “at least one of A, B, or C” or “at least one of A, B, and / or C” may mean “at least one of A, B, and C.”

[0042] In addition, the brackets used in this disclosure may mean "for example". Specifically, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, the "control information" in this disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when it is shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0043] The technical features described separately in one drawing of the present disclosure can be implemented separately or simultaneously.

[0044] Although not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0045] Hereinafter, the present disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise specified, the same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks and / or functional blocks.

[0046] In the accompanying drawings, for example, a user equipment (UE) is shown. UE may also be denoted as a terminal or mobile equipment (ME). Furthermore, a UE may be a laptop computer, mobile phone, PDA, smart phone, multimedia device, or other portable device, or may be a fixed device such as a PC or an in-vehicle device.

[0047] In the following, a UE is used as an example of a wireless communication device (or wireless device or wireless equipment) capable of wireless communication. Operations performed by a UE may be performed by a wireless communication device. A wireless communication device may also be referred to as a wireless device, a wireless device, etc. In the following, an AMF may refer to an AMF node, an SMF may refer to an SMF node, and a UPF may refer to a UPF node.

[0048] The term "base station" used below generally refers to a fixed station that communicates with wireless devices, and may be represented by other terms such as evolved Node B (eNode B), evolved Node B (eNB), base transceiver system (BTS), access point or next generation Node B (gNB).

[0049] The disclosed techniques and processes applicable to this specification

[0050] Figure 1 An example of a communication system to which an embodiment of the present disclosure is applied is shown.

[0051] Figure 1 The 5G usage scenarios shown in are only exemplary, and the technical features of the present disclosure can be applied to Figure 1 Other 5G usage scenarios not shown.

[0052] The three main requirement categories for 5G include (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable and low-latency communication (URLLC) category.

[0053] Some use cases may require multiple categories for optimization, and others may focus solely on key performance indicators (KPIs). 5G supports these various use cases with a flexible and reliable approach.

[0054] eMBB goes far beyond basic mobile internet access and encompasses a wide range of two-way work in the cloud and augmented reality, as well as media and entertainment applications. Data is one of the core drivers of 5G, and for the first time in the 5G era, dedicated voice services may not be provided. In 5G, it is expected that voice will be simply handled by applications using the data connection provided by the communication system. The main reasons for the increase in traffic volume are the increase in content size and the increase in the number of applications requiring high data transfer rates. As more devices connect to the internet, streaming services (audio and video), conversational video, and mobile internet access will become more widely used. Many of these applications require always-on connectivity to push real-time information and alerts to users. Cloud storage and applications are rapidly increasing in mobile communication platforms and can be applied to both work and entertainment. Cloud storage is a special use case that is accelerating the growth of uplink data transfer rates. 5G is also used for remote cloud work. When using tactile interfaces, 5G requires lower end-to-end latency to maintain a good user experience. Entertainment (e.g., cloud gaming and video streaming) is another core element that is increasing the demand for mobile broadband capabilities. Entertainment is essential for smartphones and tablets anywhere, including in highly mobile environments like trains, cars, and airplanes. Another use case is augmented reality for entertainment and information search. In this case, augmented reality requires very low latency and instantaneous data throughput.

[0055] One of the most anticipated 5G use cases involves the ability to smoothly connect embedded sensors in all areas (i.e., mMTC). The number of potential Internet of Things (IoT) devices is expected to reach 20.4 billion by 2020. Industrial IoT is one of the categories that will play a major role in enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.

[0056] URLLC includes new services (e.g., autonomous vehicles) that will transform industries through remote control and ultra-reliable / available low-latency links of key infrastructure. To control smart grids, automate industry, enable robotics, and control and regulate drones, the level of reliability and latency is critical.

[0057] 5G is a means of providing streaming services estimated at hundreds of megabits per second to gigabits per second, and can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speeds are needed to deliver 4K or higher (6K, 8K and higher) resolution TV as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. Specific applications may require special network configurations. For example, for VR games, gaming companies need to merge core servers into the network operator's edge network servers to minimize latency.

[0058] Along with numerous use cases for mobile communications in vehicles, automobiles are expected to become a significant new driver in 5G. For example, passenger entertainment requires high simultaneous capacity and mobile broadband with high mobility. This is because future users will continue to expect high-quality connections, regardless of their location and speed. Another use case in the automotive sector is augmented reality (AR) dashboards. AR dashboards allow drivers to identify objects in the dark, in addition to those visible through the front window, and display distance to objects and their movement by overlaying information with the driver. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices (e.g., devices accompanying pedestrians). Safety systems will guide alternative behavior processes to enable drivers to drive more safely, thereby reducing the risk of accidents. The next stage will be remotely controlled or autonomous vehicles. This requires extremely high reliability and extremely fast communication between different autonomous vehicles and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities, and drivers will only focus on unusual traffic events that the vehicle cannot identify. The technical requirements for autonomous vehicles require ultra-low latency and ultra-high reliability to increase traffic safety to a level unattainable by humans.

[0059] Smart cities and smart homes / buildings, often referred to as smart societies, will be embedded in high-density wireless sensor networks. Distributed networks of smart sensors will identify conditions for cost and energy conservation maintenance in cities or homes. Similar configurations can be implemented for individual homes. Temperature sensors, window and heating controls, burglar alarms, and household appliances will all be wirelessly connected. Many of these sensors typically have low data transmission rates, power consumption, and cost. However, certain types of devices may require real-time HD video for monitoring.

[0060] The consumption and distribution of energy, including heat and gas, is distributed at a higher level, necessitating automated control via distributed sensor networks. Smart grids collect information and use digital information and communication technologies to connect sensors to each other and act upon this information. Because this information can include the behavior of both utility companies and consumers, smart grids can improve the distribution of fuels, such as electricity, through methods that enhance efficiency, reliability, economic viability, sustainable production, and automation. Smart grids can also be considered another sensor network with low latency.

[0061] Mission-critical applications (e.g., e-health) are one of the 5G use cases. The health sector encompasses many applications that can benefit from mobile communications. Communication systems can support telemedicine, which provides clinical treatment in remote locations. Telemedicine can help reduce distance barriers and improve access to medical services that are often unavailable in remote rural areas. Telemedicine is also used to perform important treatments and save lives in emergency situations. Mobile-based wireless sensor networks can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0062] Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Therefore, the potential to replace cables with reconfigurable wireless links is an attractive opportunity in many industrial sectors. However, to achieve this replacement, wireless connections must be established with latency, reliability, and capacity similar to cables, and management of wireless connections must be simplified. When it comes to connecting to 5G, low latency and a very low probability of error are new requirements.

[0063] Logistics and freight tracking are important use cases for mobile communications, allowing inventory and packages to be tracked anywhere using location-based information systems. Logistics and freight use cases typically require low data rates but require location information with wide range and reliability.

[0064] Reference Figure 1 , the communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Figure 1 A 5G network is shown as an example of the network of the communication system 1 , but the embodiments of the present disclosure are not limited to the 5G system and may be applied to future communication systems other than the 5G system.

[0065] The BS 200 and the network 300 may be implemented as wireless devices, and certain wireless devices may operate as BSs / network nodes relative to other wireless devices.

[0066] Wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (e.g., 5G New RAT (NR) or LTE) and may be referred to as communication / radio / 5G devices. Wireless devices may include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices and may be implemented in the form of head-mounted devices (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliance devices, digital signage, vehicles, robots, and the like. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0067] In the present disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a tablet personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, an unmanned aerial vehicle (UAV), an AI module, a robot, an AR device, a VR device, an MR device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or financial device), a security device, a weather / environmental device, a device related to 5G services, or a device related to the Fourth Industrial Revolution.

[0068] A UAV may be, for example, an aircraft that is flown by wireless control signals without humans on board.

[0069] VR devices may include, for example, devices for realizing objects or backgrounds in a virtual world. AR devices may include, for example, devices that realize this by connecting objects or backgrounds in a virtual world to objects or backgrounds in the real world. MR devices may include, for example, devices that realize this by merging objects or backgrounds in a virtual world into objects or backgrounds in the real world. Holographic devices may include, for example, devices that realize 360-degree stereoscopic images by recording and reproducing stereoscopic information using the interference phenomenon of light generated when two lasers meet, known as holography.

[0070] Public safety devices may include, for example, image relay devices or image devices wearable on a user's body.

[0071] MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation, for example, such as smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

[0072] For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, or correcting an injury or disorder. For example, a medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a device for treatment, a device for surgery, a device for (in vitro) diagnosis, a hearing aid, or a device for surgery.

[0073] For example, a safety device may be a device installed to prevent possible danger and maintain safety. For example, the safety device may be a camera, a closed-circuit television (CCTV), a recorder, or a black box.

[0074] For example, a FinTech device may be a device that can provide financial services such as mobile payments. For example, a FinTech device may include a payment device or a point of sale (POS) system.

[0075] Weather / environmental devices may include, for example, devices for monitoring or predicting weather / environmental conditions.

[0076] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G network (e.g., LTE), a 5G network (e.g., NR), and a beyond 5G network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can perform direct communication (e.g., sidelink communication) with each other without going through BS 200 / network 300. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0077] Wireless communications / connections 150a, 150b, and 150c may be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS 200 and / or between BSs 200. Herein, wireless communications / connections may be established via various RATs (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, and inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)). Wireless devices 100a to 100f and BS 200 / wireless devices 100a to 100f may transmit / receive radio signals to / from each other via wireless communications / connections 150a, 150b, and 150c. For example, wireless communications / connections 150a, 150b, and 150c may transmit / receive signals via various physical channels. To this end, various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and at least a portion of the resource allocation process can be performed based on the various proposals of the present disclosure.

[0078] AI refers to the field that studies artificial intelligence or methods that can create it, and machine learning refers to the field that defines the various problems addressed in the field of AI and the methods used to solve them. Machine learning is also defined as algorithms that improve the performance of tasks through consistent experience with the task.

[0079] A robot is a machine that automatically processes or operates a given task through its own capabilities. Specifically, a robot that has the ability to recognize its environment and perform self-determination to perform actions can be called an intelligent robot. According to the purpose or field of use, robots can be classified as industrial, medical, household, military, etc. Robots can use actuators or motors to perform various physical operations such as moving robot joints. Mobile robots also include wheels, brakes, propellers, etc. on the drive, allowing them to drive on the ground or fly in the air.

[0080] Autonomous driving refers to the technology of self-driving, and autonomous vehicles refer to vehicles that drive without or with minimal user control. For example, autonomous driving can include maintaining lane movement, automatically adjusting speed (e.g., adaptive cruise control), automatically driving along a set route, and automatically setting a route when a destination is set. Autonomous vehicles can be considered robots with autonomous driving capabilities.

[0081] Extended reality is collectively referred to as VR, AR, and MR. VR technology only provides real-world objects and backgrounds through computer graphics (CG) images. AR technology provides virtual CG images on top of real-world object images. MR technology is a CG technology that combines virtual objects into the real world. MR technology is similar to AR technology in that they show real objects and virtual objects together. However, the difference is that in AR technology, virtual objects are used as a complementary form of real objects, while in MR technology, virtual objects and real objects are used as the same characteristics.

[0082] NR supports multiple parameter sets (and / or multiple subcarrier spacing (SCS)) to support various 5G services. For example, if the SCS is 15kHz, wide areas can be supported in traditional cellular bands, and if the SCS is 30kHz / 60kHz, dense cities, lower latency, and wider carrier bandwidths can be supported. If the SCS is 60kHz or higher, bandwidths greater than 24.25GHz can be supported to overcome phase noise.

[0083] The NR frequency band can be defined as two types of frequency ranges, namely, FR1 and FR2. The numerical values of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be shown in Table 1 below. For ease of explanation, in the frequency range used in the NR system, FR1 can mean "below 6 GHz range", FR2 can mean "above 6 GHz range", and can be referred to as millimeter wave (mmW).

[0084] [Table 1]

[0085] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450MHz–6000MHz 15kHz, 30kHz, 60kHz FR2 24250MHz–52600MHz 60kHz, 120kHz, 240kHz

[0086] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a frequency band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or higher. For example, a frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or higher included in FR1 may include an unlicensed frequency band. The unlicensed frequency band may be used for various purposes (e.g., for communication of vehicles (e.g., autonomous driving)).

[0087] [Table 2]

[0088] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz–7125MHz 15kHz, 30kHz, 60kHz FR2 24250MHz–52600MHz 60kHz, 120kHz, 240kHz

[0089] Here, the radio communication technology implemented in the wireless device in the present disclosure may include narrowband Internet of Things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of low-power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to as various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of various specifications such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine type communication and / or 7) LTE M, and may not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device of the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and may not be limited to the above names. For example, ZigBee technology can generate a personal area network (PAN) associated with low-power / low-power digital communication based on various specifications such as IEEE 802.15.4, and may be referred to by various names.

[0090] Figure 2 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0091] Reference Figure 2 , the first wireless device 100 and the second wireless device 200 can transmit / receive radio signals to / from an external device through various RATs (eg, LTE and NR).

[0092] exist Figure 2 In the example, {the first wireless device 100 and the second wireless device 200} may correspond to Figure 1 At least one of {wireless devices 100a to 100f and BS 200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS 200 and BS 200}.

[0093] The first wireless device 100 may include at least one transceiver (eg, transceiver 106 ), at least one processing chip (eg, processing chip 101 ), and / or one or more antennas 108 .

[0094] The processing chip 101 may include at least one processor (eg, processor 102 ) and at least one memory (eg, memory 104 ). Figure 2 The memory 104 is exemplarily shown to be included in the processing chip 101. Additionally and / or alternatively, the memory 104 may be located outside the processing chip 101.

[0095] The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flow charts described in the present disclosure. For example, the processor 102 may process information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104.

[0096] Memory 104 may be operatively connected to processor 102. Memory 104 may store various types of information and / or instructions. Memory 104 may store software code 105 that implements instructions that, when executed by processor 102, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed herein. For example, software code 105 may implement instructions that, when executed by processor 102, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed herein. For example, software code 105 may control processor 102 to execute one or more protocols. For example, software code 105 may control processor 102 to execute one or more layers of a wireless interface protocol.

[0097] In this document, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In this disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0098] The second wireless device 200 may include at least one transceiver (eg, transceiver 206 ), at least one processing chip (eg, processing chip 201 ), and / or one or more antennas 208 .

[0099] The processing chip 201 may include at least one processor (eg, processor 202 ) and at least one memory (eg, memory 204 ). Figure 2The memory 204 is exemplarily shown to be included in the processing chip 201. Additionally and / or alternatively, the memory 204 may be located outside the processing chip 201.

[0100] The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flow charts described in the present disclosure. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 106, and then store information obtained by processing the fourth information / signals in the memory 204.

[0101] Memory 204 may be operatively connected to processor 202. Memory 204 may store various types of information and / or instructions. Memory 204 may store software code 205 that implements instructions that, when executed by processor 202, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed in this disclosure. For example, software code 205 may implement instructions that, when executed by processor 202, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed in this disclosure. For example, software code 205 may control processor 202 to execute one or more protocols. For example, software code 205 may control processor 202 to execute one or more layers of a wireless interface protocol.

[0102] In this document, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In this disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.

[0103] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data, or information according to the description, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure, and provide the generated signal to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from the one or more transceivers 106 and 206 according to the description, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure, and obtain the PDU, SDU, message, control information, data, or information.

[0104] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. The firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in this disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, processes, suggestions, methods and / or operational flow charts disclosed in this disclosure may be implemented using software or firmware in the form of codes, commands and / or command sets.

[0105] One or more memories 104 and 204 can be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 can be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, registers, flash memory, computer-readable storage media and / or combinations thereof. One or more memories 104 and 204 can be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 can be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0106] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in this disclosure to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in this disclosure from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

[0107] One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas 108 and 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0108] The one or more transceivers 106 and 206 may convert received user data, control information, radio signals / channels, etc. from RF band signals into baseband signals so that the received user data, control information, radio signals / channels, etc. may be processed using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc. processed using the one or more processors 102 and 202 from baseband signals into RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, under the control of the one or more processors 102 and 202, the one or more transceivers 106 and 206 may up-convert an OFDM baseband signal into an OFDM signal through its (analog) oscillator and / or filter, and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers 106 and 206 may receive the OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal through its (analog) oscillator and / or filter under the control of one or more processors 102 and 202 .

[0109] In implementations of the present disclosure, a UE may operate as a transmitting device in the uplink (UL) and as a receiving device in the downlink (DL). In implementations of the present disclosure, a base station (BS) may operate as a receiving device in the UL and as a transmitting device in the DL. Hereinafter, for ease of description, it is primarily assumed that the first wireless device 100 acts as a UE and the second wireless device 200 acts as a base station (BS). For example, the processor 102 connected to, installed on, or activated in the first wireless device 100 may be configured to perform UE behavior according to implementations of the present disclosure, or to control the transceiver 106 to perform UE behavior according to implementations of the present disclosure. The processor 202 connected to, installed on, or activated in the second wireless device 200 may be configured to perform BS behavior according to implementations of the present disclosure, or to control the transceiver 206 to perform BS behavior according to implementations of the present disclosure.

[0110] In this disclosure, a BS is also referred to as a Node B (NB), an eNodeB (eNB), or a gNB.

[0111] Figure 3 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0112] Can be based on use case / service (refer to Figure 1 ) Wireless devices are implemented in various forms.

[0113] Reference Figure 3, the wireless devices 100 and 200 may correspond to Figure 2 The wireless devices 100 and 200 may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Figure 2 One or more processors 102 and 202 and / or Figure 2 One or more memories 104 and 204. For example, the transceiver 114 may include Figure 2 One or more transceivers 106 and 206 and / or Figure 2 The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 can control the electrical / mechanical operation of each of the wireless devices 100 and 200 based on the program / code / command / information stored in the memory unit 130. The control unit 120 can transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

[0114] The additional component 140 may be configured in various ways depending on the type of the wireless devices 100 and 200. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit (e.g., an audio I / O port, a video I / O port), a driving unit, and a computing unit. The wireless devices 100 and 200 may be configured in the form of, but not limited to, robots ( Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR devices ( Figure 1 100c), handheld device ( Figure 1 100d), household appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, FinTech device (or financial device), security device, climate / environmental device, AI server / device ( Figure 1 400), BS( Figure 1The wireless devices 100 and 200 may be implemented in the form of a UEFI 200 , a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed location depending on the use case / service.

[0115] exist Figure 3 In the wireless devices 100 and 200, the various elements, components, units / parts, and / or modules in their entirety may be connected to each other via a wired interface, or at least a portion thereof may be wirelessly connected via the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected via the communication unit 110. Each element, component, unit / part, and / or module within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a collection of one or more processors. As an example, the control unit 120 may be configured by a collection of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory unit 130 may be configured by RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0116] Figure 4 It is a structural diagram of the next generation mobile communication network.

[0117] 5GC (5G Core) may include various components including Access and Mobility Management Function (AMF) 410, Session Management Function (SMF) 420, Policy Control Function (PCF) 430, User Plane Function (UPF) 44, Application Function (AF) 450, Unified Data Management (UDM) Data Network 460 and Non-3GPP (3rd Generation Partnership Project) Interworking Function (N3IWF) 490, some of which are described in Figure 4 Shown in.

[0118] UE 100 is connected to a data network via UPF 440 through a next-generation radio access network (NG-RAN) including gNB 20.

[0119] Even over untrusted non-3GPP accesses, such as wireless local area networks (WLANs), data services may be provided to the UE 100. To connect the non-3GPP accesses to the core network, the N3IWF 490 may be deployed.

[0120] The N3IWF 490 shown performs the function of managing interworking between non-3GPP access and 5G system. When the UE 100 is connected to a non-3GPP access (e.g., WiFi known as IEEE 801.11), the UE 100 can connect to the 5G system through the N3IWF 490. The N3IWF 490 performs control signaling with the AMF 410 and is connected to the UPF 440 via the N3 interface for data transmission.

[0121] The AMF 410 shown can manage access and mobility in the 5G system. The AMF 410 can perform the function of managing non-access stratum (NAS) security. The AMF 410 can perform the function of handling mobility in the idle state.

[0122] The UPF 440 shown is a gateway through which user data is sent / received. The UPF 440 may perform all or part of the user plane functions of a serving gateway (S-GW) and a packet data network gateway (P-GW) of 4G mobile communications.

[0123] The UPF 440 serves as the boundary point between the Next Generation Radio Access Network (NG-RAN) and the core network, maintaining the data path between the gNB 20 and the SMF 420. Furthermore, when the UE 100 moves within the area served by the gNB 20, the UPF 440 serves as a mobility anchor point. The UPF 440 can handle PDUs. For mobility within the NG-RAN (defined after 3GPP Release 15), the UPF 440 can route packets. Furthermore, the UPF 440 can also serve as an anchor point for mobility with another 3GPP network (RAN defined before 3GPP Release 15, such as the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Evolved (E)-UTRAN, or Global System for Mobile Communications (GERAN) / Enhanced Data Rates for Global Evolution (EDGE) RAN). The UPF 440 can correspond to the endpoint of the data interface toward the data network.

[0124] The PCF 430 shown is a node that controls the operator's policies.

[0125] The illustrated AF 450 is a server for providing various services to the UE 100 .

[0126] The UDM 460 shown is a server that manages subscriber information (eg, a Home Subscriber Server (HSS) of 4G mobile communications). The UDM 460 stores and manages subscriber information in a unified data repository (UDR).

[0127] The SMF 420 shown may perform the function of allocating an Internet Protocol (IP) address of a UE. In addition, the SMF may control a protocol data unit (PDU) session.

[0128] For reference, hereinafter, the reference numerals of AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20) or UE (100) may be omitted.

[0129] Fifth-generation mobile communications support multiple parameter sets (e.g., multiple values of subcarrier spacing (SCS)) to facilitate supporting various services. For example, when the SCS is 15 kHz, it supports wide areas in traditional cellular bands. When the SCS is 30 kHz / 60 kHz, it supports dense urban areas, lower latency, and wider carrier bandwidths. When the SCS is 60 kHz or greater, it supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0130] Figure 5 This is a diagram showing an example of the predicted structure of next-generation mobile communications from the perspective of nodes.

[0131] Reference Figure 5 , the UE is connected to the data network (DN) through the next generation RAN (Radio Access Network).

[0132] Figure 5 The control plane function (CPF) node shown can perform all or part of the mobility management entity (MME) functions of the fourth generation mobile communication and all or part of the control plane functions of the serving gateway (S-GW) and PDN-gateway (P-GW) of the fourth generation mobile communication. The CPF node includes the access and mobility management function (AMF) node and the session management function (SMF) node.

[0133] The User Plane Function (UPF) node shown in the figure is a gateway through which user data is sent and received. The UPF node can perform all or part of the user plane functions of the S-GW and P-GW of the fourth generation mobile communication.

[0134] Figure 5 The Policy Control Function (PCF) node shown is configured to control the policies of the service provider.

[0135] The shown application function (AF) node refers to a server that provides various services to the UE.

[0136] As shown, a unified data management (UDM) node refers to a server that manages subscriber information, such as a home subscriber server (HSS) of 4th generation mobile communications. The UDM node stores and manages subscriber information in a unified data repository (UDR).

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

[0138] The Network Slice Selection Function (NSSF) node as shown refers to the node that performs network slicing as described below.

[0139] The Network Exposure Function (NEF) is a node that provides a mechanism to securely expose services and functions of the 5G core. For example, the NEF exposes functions and events, securely provides information from external applications to the 3GPP network, converts internal / external information, provides control plane parameters, and manages packet flow descriptions (PFDs).

[0140] exist Figure 6 In , the UE can use multiple PDU sessions to access two data networks simultaneously.

[0141] Figure 6 is an exemplary diagram illustrating an architecture that allows a UE to access two data networks simultaneously using one PDU session.

[0142] Figure 6 An architecture is shown that allows a UE to access two data networks simultaneously using one PDU session.

[0143] For reference, Figure 2 and Figure 3 A description of the reference points shown follows.

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

[0145] N2 represents the reference point between NG-RAN and AMF.

[0146] N3 represents the reference point between NG-RAN and UPF.

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

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

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

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

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

[0152] N9 represents the reference point between UPFs.

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

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

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

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

[0157] N14 represents the reference point between AMFs.

[0158] N15 represents the reference point between the PCF and AMF in a non-roaming scenario and the reference point between the AMF and PCF of the visited network in a roaming scenario.

[0159] N16 represents the reference point between SMFs.

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

[0161] N30 represents the reference point between PCF and NEF.

[0162] N33 indicates the reference point between AF and NEF.

[0163] exist Figure 2 and Figure 3 In 5GC, third-party AFs other than operators can be connected to 5GC through the Network Open Function (NEF).

[0164] Figure 7 is another example diagram showing the structure of the radio interface protocol between UE and gNB.

[0165] The radio interface protocol is based on the 3GPP radio access network standard. The radio interface protocol consists of a physical layer, a data link layer, and a network layer horizontally, and is vertically divided into a user plane for transmitting data information and a control plane for transmitting control signals (signaling).

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

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

[0168] The first layer, the physical layer, provides information transmission services using physical channels. The physical layer is connected to the upper media access control layer via a transport channel, and data between the media access control layer and the physical layer is transmitted via the transport channel. Furthermore, data is transmitted between different physical layers (i.e., between the physical layers on the transmitting and receiving sides) via the physical channel.

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

[0170] Layer 3 includes Radio Resource Control (RRC). The RRC layer is defined only in the control plane and is responsible for controlling logical channels, transport channels, and physical channels related to the configuration, reconfiguration, and release of radio bearers. In this context, RBs refer to services provided by Layer 2 for data transfer between the UE and the E-UTRAN.

[0171] The NAS layer performs functions such as connection management (session management) and mobility management.

[0172] The NAS layer is divided into a NAS entity for mobility management (MM) and a NAS entity for session management (SM).

[0173] The NAS entity for MM generally provides the following functions.

[0174] The NAS procedures related to AMF include the following items.

[0175] -Registration management and access management process.AMF supports the following functions.

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

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

[0178] The NAS-SM layer of the UE and SMF processes (i.e., generates and processes) SM signaling messages. The content of the SM signaling messages is not interpreted by the AMF.

[0179] - In case of SM signaling transmission,

[0180] - The NAS entity for MM creates a NAS-MM message, which deduce how and where to transmit the SM signaling message through the security header representing the NAS transmission of the SM signaling and additional information about the received NAS-MM.

[0181] - Upon receiving SM signaling, the NAS entity for SM performs an integrity check of the NAS-MM message, analyzes the additional information, and derives the method and location of the SM signaling message.

[0182] In addition, Figure 7 In the NAS layer, the RRC layer, RLC layer, MAC layer and PHY layer below the NAS layer are collectively referred to as the access layer (AS).

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

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

[0185] Multiple Access (MA) PDU sessions utilizing both 3GPP access and non-3GPP access may be used.

[0186] An MA PDU session is a PDU session that can be served simultaneously with 3GPP access and non-3GPP access using one PDU session.

[0187] <Registration Process>

[0188] The UE needs to obtain authorization to enable mobility tracking and receive data and services. To do this, the UE must register with the network. The registration process is performed when the UE needs to initially register with the 5G system. In addition, the registration process is performed when the UE performs a periodic registration update, when the UE is in idle mode and moves to a new tracking area (TA), and when the UE needs to perform a periodic registration update.

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

[0190] Figure 8a and Figure 8b is a signal flow diagram illustrating an exemplary registration process.

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

[0192] In the case of 5G RAN, the AN parameters may include SUPI or Temporary User ID, Selected Network, and NASSAI.

[0193] The registration type may indicate whether the registration is an "initial registration" (i.e., the UE is in a non-registered state), a "mobility registration update" (i.e., the UE is in a registered state and the registration procedure is initiated by mobility), or a "periodic registration update" (i.e., the UE is in a registered state and the registration procedure is initiated due to expiration of the periodic update timer). In the case where a temporary user ID is included, the temporary user ID indicates the last serving AMF. In the case where the UE has registered in a PLMN (Public Land Mobile Network) other than the PLMN of the 3GPP access through non-3GPP access, the UE may not provide the UE temporary ID allocated by the AMF during the registration procedure through the non-3GPP access.

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

[0195] The PDU session status indicates the available (and previously configured) PDU sessions in the UE.

[0196] 2) In case SUPI is included, or in case the temporary user ID does not indicate a valid AMF, the RAN may select an AMF based on the (R)AT and NSSAI.

[0197] If the (R)AN is unable to select an appropriate AMF, it selects any AMF according to local policy and forwards (or transmits) the Registration Request using the selected AMF. If the selected AMF is unable to provide service to the UE, the selected AMF may select another AMF that is more suitable for the UE.

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

[0199] When using 5G-RAN, the N2 parameters include location information related to the cell where the UE is camped, cell identifier, and RAT type.

[0200] If the registration type indicated by the UE is periodic registration update, processes 4 to 17, which will be described in detail later, may not be performed.

[0201] 4) The newly selected AMF may send an information request message to the previous AMF.

[0202] In the case where the UE's temporary user ID is included in the Registration Request message, and in the case where the serving AMF changes after the last registration, the new AMF may include an Information Request message including complete Registration Request information for requesting the UE's SUPI and MM context from the previous (or old) AMF.

[0203] 5) The previous (or old) AMF sends an Information Response message to the newly selected AMF. The Information Response message may include SUPI, MM context and SMF information.

[0204] More specifically, the previous (or old) AMF sends an Information Response message including the UE's SUPI and MM context.

[0205] -In the case where information about a valid PDU session is included in a previous (or old) AMF, SMF information including SMF ID and PDU session ID may be included in an information response message of the previous (or old) AMF.

[0206] 6) In case the SUPI is not provided by the UE, or in case the SUPI is not searched from the previous (or old) AMF, the new AMF sends an Identity Request message to the UE.

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

[0208] 8)AMF may determine the trigger for executing AUSF. In this case, AMF may select AUSF based on SUPI.

[0209] 9) AUSF can initiate UE authentication and NAS security functions.

[0210] 10) The new AMF may send an Information Response message to the previous (or old) AMF.

[0211] If the AMF changes, the new AMF may send an Information Response message in order to verify the forwarding of the UE MM context.

[0212] - If the authentication / security procedure fails, the registration is rejected and the new AMF may send a rejection message to the previous (or old) AMF.

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

[0214] In case the PEI is not provided by the UE, or in case the PEI is not searched from a previous (or old) AMF, an Identity Request message may be sent in order to allow the AMF to search for the PEI.

[0215] 12) The new AMF checks the ME identifier.

[0216] 13) If process 14 (to be described later) is performed, the new AMF selects the UDM based on the SUPI.

[0217] 14) If the AMF is modified after the final registration, the new AMF initiates an Update Location procedure if there is no valid subscription context for the UE in the AMF, or if the UE provides a SUPI where the AMF does not refer to a valid context. Alternatively, the Update Location procedure may be initiated even in the case where the UDM initiates a Cancel Location procedure to the previous AMF. The previous (or old) AMF discards the MM context and notifies all possible SMFs, and the new AMF generates the MM context for the UE after obtaining the AMF-related subscription data from the UDM.

[0218] In case of network slicing, the AMF obtains the allowed NSSAI based on the requested NSSAI and UE subscription and local policy. In case the AMF is not suitable to support the allowed NSSAI, the registration request is rerouted.

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

[0220] 16) The new AMF sends a UE context establishment request message to the PCF. The AMF may request the PCF for the UE's operator policy.

[0221] 17) The PCF sends a UE context establishment confirm message to the new AMF.

[0222] 18) The new AMF sends an N11 request message to the SMF.

[0223] More specifically, when the AMF changes, the new AMF notifies each SMF of the new AMF providing services to the UE. The AMF uses the available SMF information to authenticate the PDU session status from the UE. In the case of an AMF change, the available SMF information may be received from the previous (or old) AMF. The new AMF may send a request to the SMF to release (or cancel) network resources related to the PDU session that is not enabled in the UE.

[0224] 19) The new AMF sends an N11 response message to the SMF.

[0225] 20) The previous (or old) AMF sends a UE Context Termination Request message to the PCF.

[0226] In case the previous (or old) AMF has previously requested the UE context to be configured in the PCF, the previous (or old) AMF may delete the UE context from the PCF.

[0227] 21) The PCF may send a UE Context Termination Request message to the previous (or old) AMF.

[0228] 22) The new AMF sends a registration acceptance message to the UE. The registration acceptance message may include a temporary user ID, a registration area, mobility restrictions, PDU session status, NSSAI, a periodic registration update timer, and permission for the MICO mode.

[0229] The registration acceptance message may include information on permitted NSSAI and mapped NSSAI. Information on permitted NSSAI for the access type of the UE may be included in the N2 message containing the registration acceptance message. The information on mapped NSSAI is information that maps each S-NSSAI of the permitted NSSAI to the S-NASSI of the NSSAI configured for the home public land mobile network (HPLMN).

[0230] In the case where the AMF allocates a new temporary user ID, the temporary user ID may be further included in the registration acceptance message. In the case where mobility restrictions are applied to the UE, information indicating the mobility restrictions may be additionally included in the registration acceptance message. The AMF may include information indicating the PDU session status of the UE in the registration acceptance message. The UE may remove any internal resources related to PDU sessions not marked as valid from the received PDU session status. If the PDU session status information is included in the registration request, the AMF may include information indicating the PDU session status to the UE in the registration acceptance message.

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

[0232] <PDU Session Establishment Procedure>

[0233] For the PDU session establishment procedure, there may be two different types of PDU session establishment procedures as described below.

[0234] - The PDU session establishment procedure initiated by the UE.

[0235] - The PDU session establishment procedure initiated by the network. For this, the network may send a device trigger message to the UE's application (or applications).

[0236] Figure 9a And Figure 9b are signal flowcharts showing exemplary PDU session establishment procedures.

[0237] Figure 9a And Figure 9b The procedures shown assume that the UE has registered with the AMF according to the Figure 8a And Figure 8b shown registration procedures. Therefore, it is assumed that the AMF has obtained user subscription data from the UDM.

[0238] The UE sends a NAS message to the AMF. The message may include single network slice selection assistance information (S-NSSAI), DNN, PDU session ID, request type, N1 SM information (including PDU session request), etc.

[0239] Specifically, the UE includes the S-NSSAI from the allowed NSSAIs of the current access type. If information about mapped NSSAI is provided to the UE, the UE may provide both the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the information about mapped NSSAI. Here, the mapped NSSAI information is information that maps each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI configured for the HPLMN.

[0240] More specifically, the UE may Figure 8a and Figure 8b The UE extracts and stores the information of the allowed S-NSSAI and mapped S-NSSAI included in the Registration Accept message received from the network (i.e., AMF) during the registration process. Therefore, the UE can send a PDU Session Establishment Request message by including both the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the mapped NSSAI information.

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

[0242] The UE-initiated PDU session establishment procedure may be initiated by sending a NAS message with a PDU session establishment request message included in the N1 SM information. The PDU session establishment request message may include a request type, SSC mode, and protocol configuration options.

[0243] In the case where the PDU session establishment is for configuring a new PDU session, the request type indicates “initial access.” However, in the case where there is an existing PDU session between 3GPP access and non-3GPP access, the request type may indicate “existing PDU session.”

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

[0245] The N1 SM information may include an SM PDU DN request container including information about PDU session authentication performed by an external DN.

[0246] In case the Request Type indicates "Initial Request", and in case the PDU Session ID is not already used for an existing PDU Session for the UE, the AMF may determine that the message corresponds to a request for a new PDU Session.

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

[0248] 3) The AMF sends an SM request message to the SMF. The SM request message may include the subscriber permanent ID, DNN, S-NSSAI, PDU session ID, AMD IF, N1 SM information, user location information, and access technology type. The N1 SM information may include the PDU session ID and the PDU session establishment request message.

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

[0250] 4a) The SMF sends a subscriber data request message to the UDM. The subscriber data request message may include the subscriber permanent ID and DNN.

[0251] In the above process 3, when the request type indicates "existing PDU session", the SMF determines that the corresponding request is caused by the handover between 3GPP access and non-3GPP access. The SMF can identify the existing PDU session based on the PDU session ID.

[0252] If the SMF has not searched for the SN-related subscription data of the UE related to the DNN, the SMF may request the subscription data.

[0253] 4b) UDM may send a subscription data response message to SMF.

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

[0255] The SMF may verify that the UE request complies with the user subscription and local policy. Alternatively, the SMF may reject the UE request via NAS SM signaling (including the relevant SM rejection cause) forwarded (or transmitted) by the AMF, and the SMF may then notify the AMF that this should be considered as a release of the PDU Session ID.

[0256] 5)SMF sends a message to DN through UPF.

[0257] More specifically, in the case where SMF requires authorization / authentication PDU session establishment, SMT selects UPF and triggers PDU.

[0258] If the PDU session establishment authentication / authorization assignment fails, the SMF ends the PDU session establishment process and notifies the UE of the rejection.

[0259] 6a) If the dynamic PCC is distributed, the SMF selects the PCF.

[0260] 6b) The SMF may initiate a PDU-CAN session establishment towards the PCF in order to obtain the default PCC rules for the PDU session. In case the request type indicates "existing PDU session", the PCF may instead initiate a PDU-CAN session modification.

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

[0262] 8) When dynamic PCC is deployed and PDU-CAN session establishment has not been completed, SMF may start (or initiate) PDU-CAN session initiation.

[0263] 9) If the request type indicates "initial request" and if process 5 is not performed, the SMF may use the selected UPF and start the N4 session establishment process. Otherwise, the SMF may use the selected and start the N4 session modification process.

[0264] 9a) The SMF sends an N4 Session Establishment / Modification Request message to the UPF. Furthermore, the SMF may provide the packet discovery, enforcement, and reporting rules for the PDU session to be installed in the UPF. If the SMF allocates CN tunnel information, the CN tunnel information may be provided to the UPF.

[0265] 9b) The UPF may respond by sending an N4 Session Setup / Modify Response message. In the case where the CN tunnel information is allocated by the UPF, the CN tunnel information may be provided to the SMF.

[0266] 10) The SMF sends an SM Response message to the AMF. This message may include the cause, N2 SM information, and N1 SM information. The N2 SM information may include the PDU Session ID, QoS profile, and CN tunnel information. The N1 SM information includes a PDU Session Establishment Accept message. The PDU Session Establishment Accept message may include the allowed QoS rules, SSC mode, S-NSSAI, and allocated IPv4 address.

[0267] As information that should be forwarded by AMF to RAN, the N2 SM information may include the following.

[0268] -CN Tunnel Information: This corresponds to the core network address of the N3 tunnel corresponding to the PDU session.

[0269] - QoS Profile: This is used to provide the RAN with the mapping between QoS parameters and QoS Flow Identifier (QFI).

[0270] - PDU Session ID: This may be used to indicate to the UE via AN signaling for the UE the relationship between AN resources for the UE and the PDU session.

[0271] Additionally, the N1 SM information includes the PDU Session Establishment Accept message that shall be provided by the AMF to the UE.

[0272] Multiple QoS rules may be included in the N1 SM information and the N2 SM information within the PDU Session Setup Accept message.

[0273] - The SM Response message also includes the PDU Session ID and information that enables the AMF to determine not only which target UE to use, but also which access to use for the UE.

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

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

[0276] 12) The RAN may perform specific signaling exchanges with the UE regarding the information received from the SMF.

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

[0278] The RAN forwards the NAS message provided in procedure 10. The NAS message may include the PDU session ID and N1 SM information. The N1 SM information may include a PDU session setup accept message.

[0279] The RAN sends a NAS message to the UE only if the required RAN resources are configured and the allocation of the RAN tunnel information is successful.

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

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

[0282] 14) The AMF may send an SM request message to the SMF. The SM request message may include N2 SM information. Herein, the AMF may forward the N2 SM information received from the RAN to the SMF.

[0283] 15a) When the N4 session for the PDU session has not been configured, the SMF may initiate the N4 session establishment process together with the UPF. Otherwise, the SMF may use the UPF to initiate the N4 session modification process. The SMF may provide AN tunnel information and CN tunnel information. The CN tunnel information shall be provided only if the SMF selects the CN tunnel information in process 8.

[0284] 15b) The UPF may send an N4 session establishment / modification response message to the SMF.

[0285] 16) The SMF may send an SM response message to the AMF. When this process ends (or is completed), the AMF may forward the relevant event to the SMF. This occurs during a handover where the RAN tunnel information is modified or the AMF is redeployed.

[0286] 17) The SMF sends information to the UE via the UPF. More specifically, in the case of PDU type IPv6, the SMF may generate an IPv6 router advertisement and send the generated advertisement to the UE via N4 and the UPF.

[0287] 18) In the case where the PDU session establishment request is caused by a handover between 3GPP access and non-3GPP access, i.e., if the request type is configured as "existing PDU session", the SMF releases the user plane via the source access (3GPP or non-3GPP access).

[0288] 19) In the case where the ID of the SMF is not included in the UDM of the DNN subscription context in process 4b, the SMF may invoke (or page or summon) the "UDM_Register UE service NF service" including the SMF address and DNN. The UDM may store the ID, address, and DNN of the SMF.

[0289] During this process, if the PDU session establishment is not successful, the SMF notifies the AMF of this.

[0290] <PDU Session Modification Process>

[0291] Figure 10a and Figure 10b are signal flow diagrams showing an exemplary PDU session modification process.

[0292] This PDU session modification process may be used when modifying one or more quality of service (QoS) parameters exchanged between the UE and the network.

[0293] Figure 10a and Figure 10b The signal flow diagram shown is an example of a PDU session modification procedure, and specifically shows a PDU session modification procedure requested by a UE or a network (a non-roaming case and a roaming case with local breakout) as an example.

[0294] An example of a PDU Session Modification procedure may be triggered by the following exemplary events (steps 1a) to 1e)):

[0295] 1a) (UE initiated modification) The UE may initiate a PDU session modification procedure by sending a NAS message.

[0296] For example, the UE may send a PDU Session Modification Request message. Here, the NAS message may include an N1 SM container, a PDU Session ID, and the UE integrity protection maximum data rate. The N1 SM container may include the PDU Session Modification Request (PDU Session ID, packet filter, action, requested QoS, isolation, 5GSM core network capabilities, number of packet filters, and, if an always-on PDU session is requested, the requested always-on PDU session).

[0297] Depending on the access type, if the UE is in CM-IDLE state, a service request procedure may be performed before sending this SM-NAS message. (Depending on the access type, if the UE is in CM-IDLE state, this SM-NAS message is preceded by a service request procedure.) The (R)AN is transmitted to the AMF together with an indication of the user location information.

[0298] The AMF may call the SM context associated with the PDU session update. For example, the AMF may call Nsmf_PDUSession_UpdateSMContext. Nsmf_PDUSession_UpdateSMContext may include the SM context ID and the N1 SM container (including the PDU session modification request).

[0299] When the UE requests specific QoS treatment for a selected service data flow (SDF), the PDU session establishment request may include a packet filter describing the SDF, the requested packet filter action (addition, modification, or deletion) for the indicated packet filter, and the requested QoS. Optionally, the PDU session establishment request may include an isolation indication. When the UE requests the network to bind the applicable SDF to a different and dedicated QoS flow (e.g., even if an existing QoS flow can support the requested QoS), the isolation indication may be included in the PDU session establishment request. The network must comply with the UE's request, but the network may bind the selected SDF to an existing QoS flow instead of the UE's request.

[0300] NOTE 1: Only one QoS flow may be used for traffic isolation. When the UE makes a subsequent request for additional SDF isolation, the additional SDF is multiplexed in the existing QoS flow used for isolation.

[0301] If the UE is outside the available area of the LADN (Local Area Data Network), the UE does not trigger the PDU session modification procedure for the PDU session corresponding to the LADN.

[0302] For a PDU session established in EPS, when the UE first moves from EPS to 5GS, when the UE wants to change the PDU session to an always-on PDU session, the UE may include an indication of requesting an always-on PDU session in a PDU session modification request message.

[0303] 1b) (PCF Requested Modification) The PCF may perform a PCF-initiated SM Policy Association Modification procedure to notify the SMF of policy modification. The PCF-initiated SM Policy Association Modification procedure may be triggered, for example, by a policy decision or upon an Application Function (AF) request.

[0304] 1c) (SMF Requested Modification) The UDM may use a Subscriber Data Management (SDM) notification to update the SMF's subscription data. For example, the SDM notification may be a Nudm_SDM_Notification (including a Subscription Permanent Identifier (SUPI) and session management subscription data). The SMF may acknowledge this by updating the session management subscription data and returning the SUPI and Ack.

[0305] 1d) (SMF requested modification) The SMF may decide to modify the PDU Session. Step 1d) may also be triggered from a locally configured policy or (R)AN. Step 1d) may also be triggered when the SMF marks the UP (User Plane) connection as valid and the status of one or more QoS flows has been deleted in the 5GC but is not synchronized with the UE.

[0306] When the SMF receives one of the triggers of steps 1b) to 1d), the SMF may initiate the PDU session modification procedure requested by the SMF.

[0307] 1e) (AN-initiated modification) Regardless of whether notification control is set, the (R)AN must indicate to the SMF when the AN resources to which the QoS flow is mapped are released. The (R)AN may send an N2 message (including the PDU Session ID and N2 SM information) to the AMF. The N2 SM information may include the QoS Flow ID (QFI), user location information, and an indication that the QoS flow has been released.

[0308] The AMF may invoke an SM context request associated with the update of the PDU session. For example, the AMF may invoke Nsmf_PDUSession_UpdateSMContext (including the SM context ID and N2 SM information).

[0309] (AN initiated notification control) When notification control is set for a GBR flow, if the (R)AN determines that the QoS targets of the QoS flow cannot be met or that the QoS targets of the QoS flow can be met again, respectively, the (R)AN may send an N2 message (including a PDU session ID and N2 SM information) to the SMF. The N2 SM information may include an indication that the QoS targets of the QFI and QoS flow cannot be met or that the QoS targets of the QoS flow can be met again, respectively. The AMF may invoke an SM context request associated with the update of the PDU session. For example, the AMF may invoke Nsmf_PDUSession_UpdateSMContext (including SM context ID and N2 SM information). When the PCF subscribes to the event, the SMF may report the event to the PCF for each PCC rule for which notification control is set (see step 2). Alternatively, if dynamic PCC is not applied to the DNN and depends on the locally set policy, the SMF may initiate an SMF requested PDU session modification procedure as in the example of step 3b).

[0310] 2) The SMF may report some subscribed events to the PCF by executing the SMF-initiated SM Policy Association Modification procedure. When the PDU Session Modification procedure is triggered by steps 1b or 1d, step 2 may be omitted. If dynamic PCC is not deployed (deployed), the SMF may apply local policies to determine whether to change the QoS profile.

[0311] When the PDU session modification only requires operations in the UPF (e.g., gating), steps 3) to 7) may not be called.

[0312] 3a) For UE-initiated or AN-initiated modifications, the SMF may respond to the AMF via a PDU session update SM context. For example, the PDU session update SM context may be Nsmf_PDUSession_UpdateSMContext. Nsmf_PDUSession_UpdateSMContext may include N2 SM information (PDU session ID, QFI, QoS profile, session aggregate maximum bit rate (AMBR)) and N1 SM container (including the PDU session modification command). The PDU session modification command may include the PDU session ID, QoS rule, QoS rule operation, QoS flow-level QoS parameters if QoS related to the QoS rule is required, session AMBR, and the requested always-on PDU session if an always-on PDU session is requested.

[0313] When the UE has requested a PDU session modification, in order to modify the PDU session to an always-on PDU session, the SMF may include an always-on PDU session permission indication in the PDU session modification command. The always-on PDU session permission indication may be included to indicate whether the PDU session is changed to an always-on PDU session.

[0314] The N2 SM message may carry information to be provided by the AMF to the (R)AN. To inform the (R)AN that one or more QoS flows have been added or modified, the N2 SM message may include the QoS profile and the corresponding QFI. The N2 SM message may include only the QFI to inform the (R)AN that one or more QoS flows have been removed. If the PDU session modification is triggered by the (R)AN release in step 1e), the SM message may carry confirmation of the (R)AN release. When the UE requests a PDU session modification for a PDU session for which user plane resources have not been established, the N2 SM message provided to the (R)AN may include information for establishing user plane resources.

[0315] The N1 SM container carries the PDU Session Modification Command that the AMF shall provide to the UE. To inform the UE that one or more QoS rules have been added, removed or modified, the N1 SM container may include QoS rules, QoS rules and QoS related QoS rule operations, (if required) QoS flow-level QoS parameters and QoS flow-level QoS parameter operations.

[0316] 3b) For the modification requested by the SMF, the SMF may call Namf_Communication_N1N2MessageTransfer. The Namf_Communication_N1N2MessageTransfer may include N2 SM information (PDU Session ID, QFI, QoS Profile, Session AMBR) and N1 SM container (including PDU Session Modification Command). The PDU Session Modification Command may include PDU Session ID, QoS rules, QoS rules and QoS flow level QoS parameters if QoS related to QoS rule operation is required, and QoS rules, Session AMBR.

[0317] When the UE is in the CM-IDLE state and asynchronous communication (ATC) is enabled, the AMF may update and store the UE context based on Namf_Communication_N1N2MessageTransfer, and steps 4) to 7 may be omitted. For reference, when the ATC mode is enabled, paging is not performed for the UE in the IDLE state. When the UE is reachable (for example, when the UE enters the CM-CONNECTED state), the AMF may forward the N1 message to synchronize the UE and the UE context.

[0318] 4) The AMF may send an N2 PDU Session Request message to the (R)AN. The N2 PDU Session Request may include the N2 SM information received from the SMF, the NAS message (including the PDU Session ID and the N1 SM container (including the PDU Session Modification Command)).

[0319] 5. The (R)AN may initiate AN specific signaling exchanges with the UE related to the information received from the SMF. For example, in the case of NG-RAN, an RRC connection reconfiguration may occur when the UE modifies the necessary (R)AN resources related to a PDU session.

[0320] The (R)AN may confirm the N2 PDU session request by sending an N2 PDU session confirm message to the AMF. The N2 PDU session confirm message may include N2 SM information (accepted / rejected QFI list, AN tunnel information, PDU session ID, secondary RAT using data) and user location information. In the case of dual connectivity, when one or more QFIs are added to the PDU session, the primary RAN node allocates one or more of these QFIs to the NG-RAN node (the NG-RAN node that was not previously involved in the PDU session). In this case, the AN tunnel information may include a new N3 tunnel endpoint for the QFI allocated to the new NG-RAN node. Therefore, when one or more QFIs are removed from the PDU session, the (R)AN node no longer participates in the PDU session and removes the corresponding tunnel endpoint from the AN tunnel information. If the QFI cannot meet the user plane security enhancement information of the corresponding QoS profile (for example, due to exceeding the UE integrity protection maximum data rate), the NG-RAN may reject the QFI.

[0321] When the PLMN configures the second RAT usage report, the NG-RAN node may provide RAN usage data reporting.

[0322] 7) The AMF may transmit the N2 SM information and user location information received from the AN to the SMF via the Nsmf_PDUSession_UpdateSMContext service operation. The SMF may reply to the AMF with an Nsmf_PDUSession_UpdateSMContext response. The N2 SM information may include the second RAT usage data.

[0323] When the (R)AN rejects the QFI, the SMF is responsible for updating the QoS flow level QoS parameters (if required by the QoS rules at the UE) and the QoS flows associated with the QoS rules.

[0324] 8)SMF may update the N4 session of the UPF related to the PDU session modification by sending an N4 session modification request message to the UPF (refer to Note 3).

[0325] When a new QoS flow is generated, the SMF may update the UPF with the UL packet detection rules of the new QoS flow.

[0326] NOTE 2: UL packets with the QFI of the new QoS flow may be transmitted via update.

[0327] 9) The UE may confirm the PDU Session Modification Command by sending a NAS message. The NAS message may include the PDU Session ID and the N1SM container (including the PDU Session Modification Command Confirmation).

[0328] 10) (R)AN may forward the NAS message to the AMF.

[0329] 11)AMF may send the N1SM container (including PDU session modification command confirmation) and the user location information received from the AN to the SMF via the Nsmf_PDUSession_UpdateSMContext service operation.

[0330] The SMF may reply with a Nsmf_PDUSession_UpdateSMContext response.

[0331] If the PDU Session Modification procedure initiated by the SMF is to delete QoS flows that do not contain QoS flows associated with the default QoS rules (for example, when triggered by the PCF) and the SMF does not receive a response from the UE, the SMF marks the status of these QoS flows as synchronized with the UE.

[0332] 12) The SMF may update the UPF's N4 session that is not related to the modification of the PDU session by sending an N4 session modification request message (including the N4 session ID) to the UPF. For PDU sessions of Ethernet PDU session type, the SMF may notify the UPF to add or remove Ethernet packet filter sets and forwarding rules.

[0333] NOTE 3: The UPFs affected by the PDU Session Modification procedure depend on the modified QoS parameters and the deployment. For example, when the Session AMBR of a PDU Session with ULCL (Uplink Classifier) is changed, only the ULCL may be relevant. This note also applies to step 8).

[0334] 13) When the SMF interacts with the PCF in step 1b) or 2), the SMF may perform an SMF-initiated SM policy association modification procedure to inform the PCFPCC whether the decision is enforced or cannot be enforced.

[0335] The SMF may notify any entity subscribing to user location information related to a PDU session of changes.

[0336] When step 1b) is triggered to perform application function efficiency on service routing, the SMF may re-establish the user plane of the PDU session.

[0337] <Service Request Process>

[0338] The service request procedure is used to request the establishment of a secure connection to the AMF by the UE or the 5G core network (5GC). The service request procedure is used to activate the user plane connection of an established PDU session even when the UE is in the CM-IDLE state and the CM-CONNECTED state. For reference, in order to reflect the NAS signaling connection between the AMF and the UE, two CM states, CM-IDLE state and CM-CONNECTED state, are used.

[0339] If there is an ongoing service request procedure, the UE does not initiate the service request procedure.

[0340] The service request procedure includes a service request procedure initiated by the UE (ie, a UE-triggered service request) and a service request procedure initiated by the network (ie, a network-triggered service request).

[0341] In the following, reference will be made to Figures 11a to 11c An example of a UE-triggered service request procedure is described and reference will be made to Figure 12 Describes an example of a network-triggered service request process. Figures 11a to 11c The service request procedures described in FIG. 9 are merely examples, and the service request procedures in the present disclosure include all service request procedures triggered by the UE and all service request procedures triggered by the network.

[0342] Figures 11a to 11c is a signal flow diagram illustrating an exemplary UE-triggered service request procedure.

[0343] A UE in CM-ILDE state initiates a service request procedure to send a response, user data, or network paging request on an uplink signaling message. After receiving the service request message, the AMF may perform authentication. After establishing a signaling connection for the AMF, the UE or the network may send a signaling message (e.g., establishing a PDU session from the UE to the SMF via the AMF).

[0344] The Service Request procedure can be used by a UE in CM-CONNECTED state to request a user plane connection for an activated PDU session in response to a NAS Notification message received from the AMF.

[0345] For any service request procedure, the AMF may include the status information of the PDU Session in the SERVICE ACCEPT message, if necessary, to synchronize the PDU Session status between the UE and the network.

[0346] If the service request is not accepted by the network, the AMF responds to the UE with a service reject message. The service reject message may include an indication or a cause code for requesting the UE to perform a registration update procedure.

[0347] In the UE-triggered service request process, both the SMF and UPF belong to the PLMN serving the UE. For example, in the case of home-routed roaming, the SMF and UPF of the HPLMN are not affected by the service request process (i.e., the SMF and UPF of the HPLMN are not involved in the service request process).

[0348] In response to the service request according to the user data, the network may take additional actions if the user plane connection activation is unsuccessful.

[0349] The UE-triggered service request procedure can be applied to scenarios with or without an intermediate UPF and with or without intermediate UPF reselection.

[0350] Signaling from UE to (R)AN: The UE can send access network (AN) messages (including AN parameters, service request (PDU session list to be activated, allowed PDU session list), security parameters and PDU session status (status)) to the (R)AN.

[0351] When the UE attempts to reactivate a PDU Session, the UE provides a list of PDU Sessions to be activated. When the service request is a response to a NAS notification or paging of a PDU Session related to non-3GPP access, the UE provides a list of allowed PDU Sessions. The allowed PDU Session list identifies PDU Sessions that can be moved to 3GPP access.

[0352] In the case of NG-RAN:

[0353] The AN parameters include the selected PLMN ID and the establishment cause. The establishment cause provides the reason for requesting to establish an RRC connection.

[0354] The UE sends a service request message (message to AMF) encapsulated in an RRC message to the NG-RAN. The RRC message can be used to carry the 5G System Architecture Evolution (SAE)-Temporary Mobile Subscriber Identity (5G-S-TMSI).

[0355] When a service request is triggered for user data, the UE notifies the PDU sessions for the User Plane (UP) connection to be activated in the Service Request message using the PDU Session List to be activated.

[0356] When a service request is triggered for signalling only, the UE does not include a list of PDU sessions to be activated.

[0357] When the Service Request procedure is triggered for a paging response and the UE has user data to send simultaneously, the UE may notify the PDU sessions with UP connections to be activated in the Service Request message using the PDU Session List to be activated. Otherwise, the UE does not notify any PDU sessions in the Service Request for the paging response.

[0358] In specific cases, the UE may include the PDU session to the list of PDU sessions to be activated if there is no pending uplink data for the PDU session, if the service request is triggered only for signaling, or if the service request is triggered for a paging response.

[0359] When a service request via 3GPP access is triggered in response to a NAS notification indicating paging or non-3GPP access, the UE includes non-3GPP PDU sessions that can be reactivated via 3GPP in the list of allowed PDU sessions (see Figure 12 (see the example described in step 6 of ).

[0360] The PDU session status indicates the PDU sessions available in the UE.

[0361] When UE is located outside the available area of LADN, UE does not trigger the service request process for the PDU session corresponding to LADN. In addition, when triggering the service request due to other reasons, UE does not include the PDU session in the PDU session list to be activated.

[0362] When the UE is in the CM-CONNETED state, the service request may only include the PDU session list to be activated and the allowed PDU session list.

[0363] 2) (R)AN to AMF signaling: (R)AN may send an N2 message to the AMF. The N2 message may include N2 parameters, service request, and UE context request.

[0364] If the AMF cannot handle the service request, the AMF will reject the service request.

[0365] When using NG-RAN, the N2 parameters may include 5G-S-TMSI, selected PLMN ID, location information, and establishment cause.

[0366] When the UE is in CM-IDLE state, the NG-RAN can obtain the 5G-S-TMSI during the RRC process. The NG-RAN can select the AMF based on the 5G-S-TMSI. The location information is related to the cell where the UE resides.

[0367] Based on the PDU Session status, the AMF may perform the PDU Session Release procedure for a PDU Session indicated by the UE where the PDU Session ID is not available in the network.

[0368] 3a) Signaling from AMF to (R)AN: The AMF may send an N2 request to the (R)AN. Here, the N2 request may include a security context, a handover restriction list, and a list of recommended cell / TA / NG-RAN node identifiers.

[0369] When the 5G-AN requests a UE context or the AMF needs to provide a UE context (for example, when the AMF needs to initiate a fallback procedure for emergency services), the AMF may initiate an NG Application Protocol (NGAP) procedure. For UEs in the CM-IDLE state, the 5G-AN stores the security context in the UEAN context. The handover restriction list is related to mobility restrictions.

[0370] 5G-AN uses security context to protect messages exchanged with UE.

[0371] When the NG-RAN node provides a list of recommended cell / TA / NG-RAN node identifiers during the AN release procedure, the AMF may include the list of recommended cell / TA / NG-RAN node identifiers in the N2 request. The RAN may use this information to allocate a RAN notification area when the RAN determines to enable RRC Inactive state for the UE.

[0372] 3) If the Service Request is not sent as integrity protected or the integrity protection verification fails, the AMF may initiate NAS authentication / security procedures.

[0373] When a UE in CM-IDLE state initiates a service request for a signaling connection only, the UE and the network may exchange NAS signaling after successfully establishing the signaling connection and may omit Figures 11a to 11c Steps 4 to 11 and steps 15 to 22.

[0374] 4) [Conditional Operation] Signaling from AMF to SMF: AMF may send an Nsmf_PDUSession_UpdateSMContext request to SMF. Here, the Nsmf_PDUSession_UpdateSMContext request may include PDU session ID, operation type, UE location information, access type, RAT type, and the presence of the UE in the LADN service area.

[0375] The Nsmf_PDUSession_UpdateSMContext request is called in the following situations:

[0376] When the UE includes a list of PDU Sessions to be activated in the Service Request message;

[0377] When the procedure is triggered by the SMF, but the PDU Session identified by the UE is associated with a PDU Session ID that is different from the PDU Session ID that triggered the procedure;

[0378] - When the procedure is triggered by the SMF but the current UE location is outside the "valid area of N2 SM information" provided by the SMF (see Figure 12 In this case, the AMF does not send the N2 information provided by the SMF (see Figure 12 If the current UE location is outside the "N2SM information available area", steps 4 to 11 are omitted.

[0379] If the DNN corresponds to LADN, "UE is present in LADN service area" indicates whether the UE is inside (IN) or outside (OUT) the LADN service area. If the AMF does not provide an indication of "UE is present in LADN service area" and the SMF determines that the DNN corresponds to LADN, the SMF considers that the UE is outside the LADN service area.

[0380] The AMF determines whether the PDU session will be activated. In addition, the AMF sends an Nsmf_PDUSession_UpdateSMContext request related to the PDU session and the operation type set to "UP active" to the SMF to indicate the establishment of user plane resources for the PDU session. The AMF determines the access type and RAT type based on the global RAN node ID related to the N2 interface.

[0381] If the procedure is triggered in response to a paging or NAS notification indicating non-3GPP access and the UE is not on the allowed PDU Session list (provided by the UE) in the PDU Session of the page or notification, the AMF may inform the SMF that the user plane of the PDU Session cannot be reactivated. The service request procedure may be terminated without reactivating the user plane for other PDU Sessions in the allowed PDU Session list.

[0382] While maintaining the previous NAS signalling connection via NG-RAN, the AMF may receive a service request via NG-RAN to establish another NAS signalling connection. In this case, in order to release the previous NAS signalling connection, the AMF may trigger the AN release procedure towards the old NG-RAN according to the following logic:

[0383] For the PDU sessions indicated in the "PDU session list to be activated", the AMF may request the SMF to immediately activate the PDU session by performing this step 4.

[0384] For a PDU session included in the “List of PDU Session IDs with active N3 User Plane” but not included in the “List of PDU Sessions to be activated”, the AMF may request the SMF to deactivate the PDU session.

[0385] 5) If the PDU session ID corresponds to LADN and the SMF determines that the UE is outside the available area of LADN based on the "UE is present in the LADN service area" provided by the AMF, the SMF may determine to perform the following actions (based on local policy).

[0386] The SMF may maintain the PDU Session. However, the SMF may reject the activation of the user plane connection for the PDU Session and inform the AMF accordingly. Figure 12 When a service request initiated by the network is triggered, the SMF may notify the UPF (the UPF that has sent the data notification) that the UPF should discard the downlink data of the PDU session and / or should not provide additional data notification messages; or

[0387] SMF can release the PDU session: SMF can release the PDU session and notify AMF that the PDU session has been released.

[0388] In both cases above, the SMF responds to the AMF with an appropriate reject cause and the user plane activation of the PDU Session may be stopped.

[0389] When the SMF determines that the UE is located in a LADN available area, the SMF may check the UPF selection criteria based on the location information received from the AMF and determine to perform one of the following operations:

[0390] The SMF accepts the activation of the UP connection and can continue to use the current UPF;

[0391] When the UE moves outside the service area of the UPF (previously connected to the UPF of the AN), the SMF can accept the activation of the UP connection and select a new intermediate UPF (or add / remove the intermediate UPF (I-UPF)) while maintaining the UPF that serves as the PDU session anchor. The following describes the steps for adding / changing / removing the I-UPF through conditional steps.

[0392] Note 1: When the old I-UPF and / or the new I-UPF implements the UL Uplink Classifier (CL) or Branching Point (BP) functionality and the PDU Session Anchor for the connection for local access to the data network, the signaling described in this figure is intended as the signaling for adding, removing or changing the PDU Session Anchor, and the signaling for adding, releasing or changing the UL CL or BP should be performed by different procedures.

[0393] The SMF may reject the UP connection for activating a PDU Session in Session and Service Continuity (SSC) Mode 2. In addition, after the service request procedure, the SMF may trigger the re-establishment of the PDU Session in order to perform the allocation of a new UPF (the UPF used as the PDU Session anchor). (For example, this operation may be performed when the UE moves outside the service area of the anchor UPF connected to the NG-RAN)

[0394] 6a) [Conditional operation] Signaling from SMF to new UPF (or new I-UPF): SMF can send an N4 session establishment request to UPF.

[0395] When the SMF selects a new UPF to be used as the I-UPF for a PDU session or when the SMF selects an I-UPF to be inserted into a PDU session (which does not have an I-UPF), the SMF may send an N4 session establishment request to the UPF. Here, the N4 establishment request provides packet detection, data forwarding, enforcement, and reporting rules to be installed in the I-UPF. The PDU session anchor addressing information (PDU session anchor addressing information at the N9 reference point (reference point between two UPFs)) of the PDU session is also provided to the I-UPF.

[0396] When the network triggers a service request and the SMF selects a new UPF to replace the existing UPF (or existing I-UPF), the SMF may include a data forwarding indication in the N4 session establishment request. The data forwarding indication may indicate to the UPF that the second tunnel endpoint needs to be reserved for DL data buffered after being provided from the previous I-UPF.

[0397] 6b) Signaling from new UPF (or I-UPF) to SMF: The new UPF (or I-UPF) may send an N2 session establishment response (N4 session establishment response) to the SMF.

[0398] The new I-UPF may send an N4 session establishment response to the SMF. When the UPF allocates CN tunnel information, the new I-UPF may send the UPF's DL core network (CN) tunnel information, which serves as the PDU session anchor, and the new I-UPF's UL tunnel information to the SMF. Upon receiving a data transfer indication, the new UPF (or I-UPF), operating as an N3 termination point, may send the SMF's DL tunnel information to transfer data from the existing UPF (or I-UPF) to the SMF. If there are previous I-UPF resources, the SMF may activate a timer to be used in step 22a to release the corresponding resources.

[0399] 7a) [Conditional Action] Signaling from SMF to UPF (PSA: PDU Session Anchor): SMF can send an N4 session modification request to UPF.

[0400] When the SMF selects a new UPF as the I-UPF for a PDU session, the SMF may send an N4 Session Modification Request message to the PDU session anchor UPF to provide the DL tunnel information received from the new I-UPF. When a new I-UPF is added for a PDU session, the UPF (PSA) may provide DL data to the new I-UPF as indicated in the DL tunnel information.

[0401] If the service request is triggered by the network and the SMF removes the existing I-UPF and does not replace it with a new I-UPF, the SMF may include a data forwarding indication in the N4 session modification request. The data forwarding indication may indicate to the UPF (PSA) that a second tunnel endpoint needs to be reserved for the buffered DL data received from the existing I-UPF. In this case, the UPF (PSA) may start buffering DL data that may be received simultaneously from the N6 interface.

[0402] 7b)UPF (PSA) may send an N4 session modification response message to SMF.

[0403] When the UPF (PSA) receives the data forwarding indication, the UPF (PSA) becomes the N3 endpoint and sends the CN DL tunnel information of the previous UPF (or I-UPF) to the SMF. The SMF may start a timer. If there are previous I-UPF resources, the SMF may drive the timer to be used in step 22a to release the corresponding resources.

[0404] When the UPF connected to the RAN is the UPF (PSA) and the SMF receives the Nsmf_PDUSession_UpdateSMContext request (including the operation type set to "UP activation" to indicate the establishment of user plane resources for the PDU session), if the SMF finds that the PDU session is active, the SMF may initiate the N4 session modification procedure to remove the AN tunnel information and remove the AN tunnel information from the UPF.

[0405] 8a) [Conditional Action] Signaling from SMF to existing UPF (or I-UPF): SMF can send N4 session modification (including new UPF address, new UPF DL tunnel ID) to the existing UPF (or I-UPF).

[0406] When the network triggers a service request and the SMF removes the existing UPF (or I-UPF), the SMF may send an N4 Session Modification Request message to the existing UPF (or I-UPF) to provide DL tunnel information for buffered DL data. When the SMF assigns a new I-UPF, the DL tunnel information is received from the new UPF (or I-UPF) operating as the N3 endpoint. If the SMF does not assign a new I-UPF, the DL tunnel information is sent from the UPF (PSA) operating as the N3 endpoint. As in step 6b or 7b, the SMF may start a timer for monitoring the forwarding tunnel.

[0407] When the SMF receives the Nsmf_PDUSession_UpdateSMContext request of step 4 (including the operation type set to "UP activation" to indicate establishing user plane resources for the PDU session), if the SMF knows that the PDU session has been activated, the SMF can remove the AN tunnel information to remove the tunnel information of the AN in the UPF, and can initiate the N4 session modification process.

[0408] 8b) Signaling from existing UPF (or I-UPF) to SMF: The existing UPF (or I-UPF) can send an N4 session modification response message to the SMF.

[0409] 9) [Conditional operation] Signaling from existing UPF (or I-UPF) to new UPF (or I-UPF): The existing UPF (or I-UPF) can transfer downlink data buffered with the new UPF (or I-UPF).

[0410] When the I-UPF changes and a forwarding tunnel is established for the new I-UPF, the existing UPF (or I-UPF) transfers the buffered data to the new UPF (or I-UPF) operating as the N3 endpoint.

[0411] 10) [Conditional Operation] Signaling from existing UPF (or I-UPF) to UPF (PSA): The existing UPF (or I-UPF) can transfer the buffered downlink data to UPF (PSA).

[0412] When the existing I-UPF is removed, no PDU session is allocated for the new I-UPF in the PDU session, and a forwarding tunnel is established for the UPF (PSA), the existing UPF (or I-UPF) can transfer data buffered to the existing UPF (or I-UPF) to the new UPF (PSA) serving as the N3 endpoint.

[0413] 11) [Conditional Action] Signaling from SMF to AMF: SMF may send an Nsmf_PDUSession_UpdateSMContext response to AMF. The Nsmf_PDUSession_UpdateSMContext response may include N2 SM information (PDU session ID, QFI (QoS flow ID), Quality of Service (QoS) profile, CN N3 tunnel information, S-NSSAI, user plane security implementation, UE integrity protection maximum data rate, and cause. When the UPF connected to the RAN is the UPF (PSA), the CN N3 tunnel information is the UL tunnel information of the UPF (PSA). When the UPF connected to the RAN is the new I-UPF, the CN N3 tunnel information is the UL tunnel information of the I-UPF.

[0414] For the PDU session for which the SMF determines in step 5 to accept the activation of the UP connection, the SMF may only generate N2 SM information and send an Nsmf_PDUSession_UpdateSMContext response to the AMF to establish the user plane. The N2 SM information may include information to be provided by the AMF to the NG-RAN. When the SMF determines to change the PSA UPF for the SSC Mode 3 PDU session, the SMF may trigger a change of the SSC Mode 3 PDU session anchor as an independent process after accepting the UP activation of the PDU session.

[0415] The SMF may reject the UP of an activated PDU Session by including the reason in the Nsmf_PDUSession_UpdateSMContextResponse. The SMF may reject the UP of an activated PDU Session in the following circumstances, for example:

[0416] As in step 5, when the PDU session corresponds to a LADN and the UE is outside the available area of the LADN;

[0417] When the AMF informs the SMF that the UE is reachable only for regulatory prioritization services and the PDU Session to be activated is not for regulatory prioritization services; or

[0418] As shown in step 5, when the SMF determines to change the PSA UPF of the requested PDU session. In this case, after the SMF sends the Nsmf_PDUSession_UpdateSMContext response, the SMF may perform another procedure to instruct the UE to re-establish the PDU session for SSC mode 2.

[0419] If the SMF receives a negative response in step 6b due to unavailability of UPF resources.

[0420] When the EPS bearer ID is assigned to a PDU session, the SMF maps the EPS bearer ID and QFI to N2 SM information and sends it to the NG-RAN.

[0421] The user plane security implementation information is determined by the SMF during the PDU session establishment process. When integrity protection indicates "preferred" or "required", the SMF may also include the UE integrity protection maximum data rate in the user plane security implementation information.

[0422] 12) Signaling from AMF to (R)AN: The AMF may send an N2 request to the (R)AN. The N2 request may include the N2 SM information received from the SMF, security context, handover restriction list, subscribed UE aggregate maximum bit rate (AMBR), MM NAS service acceptance (list of recommended cell / TA / NG-RAN node identifiers), and UE radio capabilities. The allowed NSSAI for the UE's access type may be included in the N2 message.

[0423] When the UE triggers a service request while in CM-CONNECTED state, only the N2 SM information received from the SMF and MM NAS Service Acceptance may be included in the N2 request.

[0424] When the UE is in CM-CONNECTED state, when the network triggers the service request procedure, only the N2SM information received from the SMF can be included in the N2 request.

[0425] When the service request procedure is triggered, the NG-RAN may store the security context and NAS signaling connection ID for the UE in CM-IDLE state. When the service request is not triggered by the UE for a signaling connection only, the RAN may store the QoS information of the QoS flows of the activated PDU sessions, the N3 tunnel ID of the UE RAN context and the handover restriction list.

[0426] The MM NAS Service Accept message may include the PDU Session Status of the AMF. During the Session Request procedure, the UE may be notified of certain local PDU Session releases via the PDU Session Status. The Service Accept message includes the PDU Session Reactivation Result. The PDU Session Reactivation Result provides the activation result for a PDU Session in the Allowed PDU Session List, which has been generated in the list of Allowed PDU Sessions and Paging or NAS Notifications. If the PDU Session Reactivation Result for a PDU Session is Failure, the reason for the failure may also be provided.

[0427] When there are multiple PDU Sessions associated with multiple SMFs, the AMF does not need to wait for responses from all SMFs in step 11. However, the AMF must wait for all responses from multiple SMFs before sending the MM NAS Service Accept message to the UE.

[0428] When step 12 is triggered for PDU session user plane activation, the AMF may include at least one N2 SM information received from the SMF in the N2 request. When there is additional N2 SM information received from the SMF, the AMF may include the additional N2 SM information received from the SMF in a separate N2 message (e.g., N2 tunnel establishment request) and send the additional N2 SM information. Alternatively, when multiple SMFs are involved, the AMF may send one N2 request message to the (R)AN after receiving all Nsmf_PDUSession_UpdateSMContext response service operations related to the UE from the SMF.

[0429] When the NG-RAN node provides a list of recommended cell / TA / NG-RAN node identifiers during the AN release procedure, the AMF may include the list of recommended cell / TA / NG-RAN node identifiers in the N2 request. The NG-RAN may use this information to allocate a RAN notification area when it determines to enable RRC Inactive state for the UE.

[0430] The AMF based on network configuration may include the UE’s “RRC Inactivity Assistance Information” in the N2 request.

[0431] If possible, the AMF may include the UE radio capability information in the N2 request and send it to the NG-RAN node.

[0432] 13) Signaling from (R)AN to UE: The NG-RAN may perform RRC connection reconfiguration with the UE. Specifically, the NG-RAN may perform RRC connection reconfiguration with the UE based on the QoS information of all QoS flows of the data radio bearer and the PDU session for the activated UP connection. For a UE in the CM-IDLE state, if the service request is not triggered by the UE for a signaling connection only, user plane security may be established in this step. For a UE in the CM-IDLE state, when the UE triggers a service request for a signaling connection only, an AS security context may be established in this step.

[0433] When the N2 request includes a NAS message, the NG-RAN may deliver the NAS message to the UE. The UE deletes the context of the PDU session that is not available locally in the 5GC.

[0434] NOTE 2: Receipt of the SERVICE ACCEPT message may not mean that the user plane radio resources have been successfully activated.

[0435] After the user plane radio resources are established, uplink data from the UE can now be passed to the NG-RAN. The NG-RAN can send the uplink data to the UPF address and tunnel ID provided in step 11.

[0436] 14) [Conditional Operation] Signaling from (R)AN to AMF: The (R)AN may send an acknowledgment of the N2 request to the AMF. For example, the (R)AN may send an N2 request acknowledgment to the AMF. Here, the N2 request acknowledgment may include N2 SM information (including AN tunnel information, QoS flow acceptance list of the PDU session whose UP connection is activated, and QoS flow rejection list of the PDU session whose UP connection is activated) and PDU session ID.

[0437] The message including the N2 request confirmation may include N2 SM information (e.g., AN tunnel information). When the AMF sends a separate N2 message in step 11, the NG-RAN may respond to the N2 SM information with a separate N2 message.

[0438] When multiple N2 SM messages are included in the N2 Request message of step 12, the N2 Request Acknowledgement may include multiple N2SM information and information enabling the AMF to associate the response with the relevant SMF.

[0439] 15) [Conditional Operation] Signaling from AMF to SMF: AMF may send an Nsmf_PDUSession_UpdateSMContext request (including N2 SM information, RAT type and access type) for each PDU session to SMF. The AMF may determine the access type and RAT type based on the global RAN node ID associated with the N2 interface.

[0440] When the AMF receives the N2 SM information (one or more) in step 14, the AMF may deliver the N2 SM information to the relevant SMF according to the PDU session ID. When the UE time zone changes compared to the previously reported UE time zone, the AMF may include the UE time zone information element (IE) in the Nsmf_PDUSession_UpdateSMContext request.

[0441] 16) [Optional Action] Signaling from SMF to PCF: When a dynamic PCC is distributed, the SMF performs the SMF-initiated SM policy modification procedure to initiate notification of new location information to the PCF (if subscribed). The PCF can provide updated policies.

[0442] 17a) [Conditional Action] Signaling from SMF to new I-UPF: The SMF may send an N4 Session Modification Request to the new I-UPF. The N4 Session Modification Request may include AN tunnel information and a list of accepted QFIs.

[0443] When the SMF selects the new SMF as the I-UPF for the PDU session in step 5, the SMF may initiate an N4 session modification procedure for the new I-UPF and provide AN tunnel information. Downlink data from the new I-UPF may be delivered to the NG-RAN and the UE.

[0444] 17b) [Conditional Action] Signaling from UPF to SMF: UPF may send an N4 Session Modification Response to SMF.

[0445] 18a) [Conditional Operation] Signaling from SMF to UPF (PSA): SMF may send an N4 session modification request to UPF (PSA). The N4 session modification request may include AN tunnel information and QoS flow rejection list.

[0446] If the user plane is established or modified and if there is no I-UPF after the modification, the SMF can initiate the N4 session modification procedure for the UPF (PSA) and provide the AN tunnel information. The downlink data from the UPF (PSA) can now be delivered to the NG-RAN and the UE.

[0447] For QoS flows in the rejected QoS flow list, the SMF may instruct the UPF to remove the rules related to the corresponding QoS flow (e.g., packet detection rules, etc.).

[0448] 18b) [Conditional Action] Signaling from UPF to SMF: UPF may send an N4 Session Modification Response to SMF.

[0449] 19) [Conditional operation] Signaling from SMF to AMF: SMF can send Nsmf_PDUSession_UpdateSMContext response to AMF.

[0450] 20a) [Conditional Action] Signaling from SMF to new UPF (or I-UPF): SMF may send an N4 session modification request to the new UPF (or I-UPF).

[0451] When the forwarding tunnel is established for the new I-UPF and when the timer set by the SMF for the forwarding tunnel in step 8a expires, the SMF may send an N4 session modification request to the new UPF (or I-UPF) operating as the N3 endpoint to release the forwarding tunnel.

[0452] 20b) [Conditional Action] Signaling from new UPF (or I-UPF) to SMF: The new UPF (or I-UPF) may send an N4 Session Modification Response to the SMF.

[0453] The new UPF (or I-UPF) operating as the N3 endpoint may send an N4 session modification response to the SMF.

[0454] 21a) [Conditional Action] Signaling from SMF to UPF (PSA): SMF may send an N4 session modification request to UPF (PSA).

[0455] When the forwarding tunnel is established for the UPF (PSA) and when the timer set by the SMF for the forwarding tunnel in step 7b expires, the SMF may send an N4 session modification request to the UPF (PSA) operating as the N3 endpoint to release the forwarding tunnel.

[0456] 21b) [Conditional Action] Signaling from UPF (PSA) to SMF: UPF (PSA) may send an N4 Session Modification Response to SMF.

[0457] The UPF (PSA) operating as an N3 endpoint may send an N4 session modification response to the SMF.

[0458] 22a) [Conditional Action] Signaling from SMF to previous UPF: SMF may send an N4 session modification request or an N4 session release request to the previous UPF.

[0459] When the SMF determines in step 5 to continue using the previous UPF, the SMF may send an N4 session modification request to the previous UPF and provide AN tunnel information.

[0460] When the SMF selects a new UPF to operate as the I-UPF in step 5 and the previous UPF is not a PSA UPF, the SMF can initiate resource release by sending an N4 session release request (including the release cause) to the previous I-UPF after the timer in step 6b or 7b expires.

[0461] 22b) Signaling from previous I-UPF to SMF: The previous I-UPF may send an N4 session modification response or an N4 session release response to the SMF.

[0462] The previous UPF checks the modification or release of resources through N4 Session Modification Response or N4 Session Release Response.

[0463] The example of the UE-initiated service request process is the same as steps 1 to 22b above.

[0464] For mobility related events, the AMF may invoke the Namf_EventExposure_Notify service operation after step 4.

[0465] When receiving a Namf_EventExposure_Notify with an indication that the UE is reachable, if the SMF has pending DL data, the SMF may invoke the Namf_Communication_N1N2MessageTransfer service operation of the AMF to establish the user plane of the PDU session. In other cases, the SMF may resume sending DL data notifications to the AMF in the case of DL data.

[0466] Figure 12 is a signal flow diagram illustrating an exemplary network-initiated service request process.

[0467] The network initiated service request procedure is used when the user plane of a PDU session needs to be activated to transfer signaling (e.g., N1 signaling to the UE, mobile terminated short message service (SMS)), mobile terminated (data destined for the UE) user data with the UE.

[0468] When the network-initiated service request process is triggered by the Short Message Service Function (SMSF), PCF, Location Management Function (LMF), Gateway Mobile Location Center (GMLC), NEF or UDM, Figure 12 The SMF in the example can be replaced by the corresponding NF. For example, when the service request process initiated by the network is triggered by the PCF, the PCF can execute the Figure 12 The operations performed by the SMF in .

[0469] When the UE is in the CM-IDLE state or the CM-CONNECTED state in 3GPP access, the network initiates the network service request procedure.

[0470] When the UE is in the CM-IDLE state and asynchronous communication is not activated, the network can send a paging request to the (R)AN / UE. The paging request triggers the UE-initiated service request procedure in the UE. When asynchronous communication is activated, the network stores the received message and, when the UE enters the CM-CONNECTED state, the network can deliver the received message to the (R)AN and / or UE.

[0471] When the UE is in CM-IDLE state in non-3GPP access and the UE is registered for 3GPP access and non-3GPP access in one Public Land Mobile Network (PLMN) at the same time, the network may initiate a network initiated service request procedure via the 3GPP access.

[0472] When the UE is in CM-IDLE state in 3GPP access and in CM-CONNECTED state in non-3GPP access, and the UE is registered for 3GPP access and non-3GPP access in one PLMN at the same time, the network can initiate the network-initiated service request procedure over the 3GPP access.

[0473] In the service request process initiated by the network, both the SMF and UPF belong to the PLMN serving the UE. For example, in the case of home route roaming, the SMF and UPF of the HPLMN are not affected by the service request process (i.e., the SMF and UPF of the HPLMN are not involved in the service request process).

[0474] Figure 12 The procedure addresses the following non-exhaustive list of use cases for 3GPP access (the detailed conditions under which each step applies are described in the procedure below):

[0475] When the SMF needs to establish an N3 tunnel to deliver the downlink packets of the PDU session to the UE and the UE is in the CM-IDLE state: step 3a includes an N2 message and step 4b (paging) can be performed.

[0476] When the SMF needs to establish an N3 tunnel to deliver the downlink packets of the PDU session to the UE and the UE is in the CM-CONNECTED state: step 3a includes an N2 message and step 4a (UP activation) can be performed.

[0477] If the NF (e.g. SMF, SMSF, LMF or NEF) needs to send an N1 message to the UE and the UE is in CM-IDLE state: step 3a includes the N1 message, step 3b includes the cause "trying to reach UE", and step 4b (paging) occurs.

[0478] When the NF (e.g. SMSF, PCF or UDM) triggers the AMF to establish a NAS connection with the UE and the UE is in CM-IDLE state: step 4b (paging) occurs depending on the procedure trigger.

[0479] When the UPF receives downlink data of a PDU session and the AN tunnel information of the PDU session is not stored in the UPF, the UPF may buffer the downlink data or transmit the downlink data to the SMF based on an instruction received from the SMF.

[0480] 2a) Signaling from UPF to SMF: UPF may send a data notification to SMF. The data notification may include N4 session ID, information for identifying the QoS flow for DL data packets, and DSCP.

[0481] When the first downlink data of a certain QoS flow arrives, if the SMF has not previously notified the UPF not to send data notification to the SMF, the UPF may send a data notification message to the SMF. For reference, if the SMF has previously notified the UPF not to send data notification to the SMF, the subsequent steps may be omitted.

[0482] When the UPF receives downlink data packets of different QoS flows in the same PDU session, the UPF may send another data notification message to the SMF.

[0483] When the UPF supports the paging policy differentiation feature and the PDU session type is IP, the UPF may include the DSCP of the TOS (Type of Service) (IPv4) / TC (Traffic Class) (IPv6) received from the IP header of the downlink data packet and information for identifying the QoS flow of the DL data packet in the data notification.

[0484] 2b) Signaling from SMF to UPF: Data notification confirmation can be sent.

[0485] 2c) When the SMF instructs the UPF that it will buffer data packets, the UPF may deliver the downlink data packets to the SMF.

[0486] When the SMF supports the paging policy differentiation feature, the SMF can determine the paging policy indication based on the DSCP of the TOS (IPv4) / TC (IPv6) value received from the IP header of the downlink data packet and identify the QFI of the QoS flow for the DL data packet.

[0487] 3a) [Conditional Action] i) Signalling from SMF to AMF: SMF may send Namf_Communication_N1N2MessageTransfer (including SUPI, PDU Session ID, N2 SM information (including QFI, QoS configuration, CN N3 tunnel information, S-NSSAI and paging policy indication), valid area of N2 SM information, ARP (allocation and retention priority) including paging policy indication, 5QI and N1N2TransferFailure notification target address) to AMF. Alternatively, ii) Signalling from NF to AMF: NF may send Namf_Communication_N1N2MessageTransfer (including SUPI and N1 message) to AMF.

[0488] Upon receiving the data notification message, the SMF may perform operations to support the LADN for the PDU session corresponding to the LADN. The SMF may notify the UPF that sent the data notification to discard the downlink data of the PDU session and / or not provide an additional data notification message.

[0489] In other cases, SMF may determine whether to contact AMF. In the following cases, SMF may not contact AMF:

[0490] If the SMF previously notified that the UE is unreachable; or

[0491] If the UE is reachable only for regulatory priority services and the PDU Session is not for regulatory priority services.

[0492] The SMF determines the AMF and the SMF may call Namf_Communication_N1N2MessageTransfer to the AMF by including the PDU session ID derived from the N4 session ID received in step 2a.

[0493] If the SMF receives any additional data notification messages or downlink data packets while waiting for the user plane connection to be activated, and if the SMF buffers data packets for a QoS flow associated with a priority (e.g. ARP priority) that is higher than the priority associated with the previous data notification message or downlink data packet, the SMF may invoke a new Namf_Communication_N1N2MessageTransfer to the AMF indicating the higher priority ARP and PDU Session ID.

[0494] When the SMF receives a message from a new AMF (not the AMF whose Namf_Communication_N1N2MessageTransfer was previously called by the SMF), the SMF may re-call Namf_Communication_N1N2MessageTransfer to the new AMF while waiting for the user plane connection to be activated.

[0495] When paging policy differentiation is supported, the SMF may display the 5QI associated with the QFI of step 2a, the packet received in step 2c, or the paging policy indication associated with the downlink data received from the ARP or UPF, or the downlink data that triggers the data notification message in the Namf_Communication_N1N2MessageTransfer.

[0496] NOTE 1: The AMF may receive request messages from other Network Functions (NFs) to perform signaling to the UE / RAN (e.g., network-initiated deregistration, SMF-initiated PDU Session Modification, etc.). When the UE is in the CM-CONNECTED state and the AMF delivers only N1 messages to the UE, the flow continues in step 6 below.

[0497] The N2 SM information is optional. For example, when the SMF intends to send only a PDU Session Modification Command to update the UE to a PCO, the N2 SM information may be optional.

[0498] 3b) [Conditional operation] AMF can respond to SMF.

[0499] If the UE is in CM-IDLE state of the AMF and the AMF can page the UE, the AMF may send a Namf_Communication_N1N2MessageTransfer response with the cause "Trying to reach UE" directly to the SMF. The cause "Trying to reach UE" may indicate to the SMF that if the UE is reachable, the AMF may ignore the N2 SM information provided in step 3a and request the SMF to provide the N2 SM information again.

[0500] While waiting for the UE to respond to the previous paging request, the AMF may reject the Namf_Communication_N1N2MessageTransferRequest message when it receives a Namf_Communication_N1N2MessageTransferRequest message with the same or lower priority as the previous message that triggered paging, or when the AMF determines not to trigger an additional paging request for the UE based on local policy.

[0501] When the UE is in CM-CONNETED state in the AMF, the AMF may immediately send a Namf_Communication_N1N2MessageTransfer response with the cause "N1 / N2 transfer successful" to the SMF.

[0502] If the UE is in the CM-IDLE state and the AMF determines that the UE is not available for paging, the AMF may send a Namf_Communication_N1N2MessageTransfer response to the SMF or other network function (in step 3a, the NF sends a request message to the AMF). Alternatively, the AMF may perform asynchronous type communication and store the UE context based on the received message. When asynchronous type communication is invoked, the AMF may initiate communication with the UE and (R)AN when the UE is reachable (e.g., when the UE enters the CM-CONNECTED state).

[0503] When the AMF determines that the UE is unreachable for the SMF (for example, because the UE is in Mobile Initiated Connection Only (MICO) mode, or the UE is only registered through non-3GPP access and the UE is in CM-IDLE state), the AMF may reject the request from the SMF. When the SMF is not subscribed to UE reachability events, the AMF may include an indication in the rejection message (an indication that the SMF does not need to trigger a Namf_Communication_N1N2MessageTransfer request to the AMF). The AMF may store the indication that the SMF has been notified that the UE is unreachable.

[0504] When the UE is not in MICO mode and the AMF detects that the UE is in a non-allowed area, the AMF may reject the request from the SMF and notify the SMF that the UE is reachable only for regulatory priority services, unless the request from the SMF is for regulatory priority services. The AMF may store an indication that the SMF has been notified that the UE is reachable only for regulatory priority services.

[0505] If the Registration procedure with AMF changes is performed when the previous AMF receives a Namf_Communication_N1N2MessageTransfer, the previous AMF may reject the request with an indication that the Namf_Communication_N1N2MessageTransfer has been temporarily rejected.

[0506] When receiving a Namf_Communication_N1N2MessageTransfer response with an indication that the request has been temporarily rejected, the SMF may start a locally set protection timer and may wait until a random message from the AMF. When receiving a message from the AMF, the SMF may re-invoke Namf_Communication_N1N2MessageTransfer (along with the N2 SM information) to the AMF that sent the message. In other cases, when the protection timer expires, the SMF may perform step 3a. If the SMF determines that control region buffering is applied, the SMF may request the UPF to start sending downlink data PDUs to the SMF.

[0507] 3c) [Conditional Action] The SMF may respond to the UPF. For example, the SMF may send a failure indication to the UPF.

[0508] The SMF may notify the UPF of the user plane establishment failure.

[0509] When the SMF receives an indication from the AMF that the UE is unreachable or that the UE is reachable only for regulatory priority services, the SMF may perform the following operations based on network policy:

[0510] SMF can instruct UPF to stop sending data notifications;

[0511] The SMF can instruct the UPF to stop buffering DL data and discard the buffered data;

[0512] The SMF may instruct the UPF to stop sending data notifications, stop buffering DL data, and discard the buffered data; or

[0513] - When the UE is unreachable, the SMF refrains from sending additional Namf_Communication_N1N2MessageTransfer messages for DL data.

[0514] Based on operator policy, SMF may apply suspension of the billing process.

[0515] When the SMF receives an indication from the AMF that the Namf_Communication_N1N2MessageTransfer requested by the SMF has been temporarily rejected, the SMF may instruct the UPF to apply temporary buffering based on the network policy.

[0516] 4a) [Conditional Action] When the UE is in the CM-CONNECTED state in the access associated with the PDU Session ID received from the SMF in step 3a, the following action may be performed without sending a paging message to the (R)AN node and the UE to activate the user plane connection for the PDU Session (e.g. radio resources and N3 tunnel may be established): Figures 11a to 11c Steps 12 to 22. Figures 11a to 11c In step 12, the AMF may not send the NAS service accept message to the UE. Figures 11a to 11c Except for steps 12 to 22.

[0517] 4b) [Conditional Action] Even when the UE is in CM-IDLE state for 3GPP access, the PDU Session ID received from the SMF in step 3a is related to 3GPP access, and the UE is in CM-CONNECTED state for non-3GPP access, the AMF may send a paging message to the NG-RAN node over 3GPP access if the AMF determines based on local policy to notify the UE over 3GPP access.

[0518] When a UE is simultaneously registered in the same PLMN via 3GPP access and non-3GPP access, and the UE is in CM-IDLE state in both 3GPP access and non-3GPP access mode, and the PDU Session ID of step 3a is related to the non-3GPP access, the AMF may send a paging message related to the access "non-3GPP" to the NG-RAN node via 3GPP access.

[0519] When the UE is in the RM (Registration Management)-REGISTERED state and the CM-IDLE state and the UE is reachable in 3GPP access, the AMF may send a paging message (including the NAS ID for paging, the registration area list, the paging DRX length, the paging priority indication, and the access associated with the PDU session) to the (R)AN node belonging to the registration area in which the UE is registered. Upon receiving the paging message from the AMF, the NG-RAN node may page the UE by including the access associated with the PDU session in the paging message.

[0520] For reference, two RM states, RM-DEREGISTERED state and RM-REGISTERED state, are used in the UE and AMF to reflect the registration status of the UE in the PLMN.

[0521] When paging policy differentiation is supported, paging policies can be set in the AMF for different combinations of DNN, paging policy indication, ARP and 5QI.

[0522] For the RRC inactive state, the paging policy may be set in the (R)AN for other combinations of paging policy indication, ARP and 5QI.

[0523] The paging priority indication may be included only in the following cases:

[0524] When the AMF receives a Namf_Communication_N1N2MessageTransfe message including an ARP value related to a priority service (e.g., MPS, MCS) set by the operator.

[0525] One paging priority can be used for multiple ARP values. The mapping of ARP values used for paging priorities can be set in the AMF and NG-RAN according to operator policy.

[0526] The (R)AN may prioritize the paging of the UE according to the paging priority indication (or paging policy indicator).

[0527] While waiting for a response from the UE to a paging request message sent without a paging priority indication (or paging policy indicator), if the AMF receives a Namf_Communication_N1N2MessageTransfer message indicating an ARP value related to a priority service (e.g., MPS, MCS) set by the operator, the AMF may send another paging message with the appropriate paging priority (or paging policy indicator). For a later received Namf_Communication_N1N2MessageTransfer message with the same or higher priority, the AMF may determine whether to send a paging message with the appropriate paging priority based on local policy.

[0528] Paging policies can include the following:

[0529] Paging retransmission scheme (e.g., how often or at what interval to repeat paging);

[0530] Determining whether to send a paging message to a (R)AN node during a specific AMF high load condition;

[0531] Whether to apply sub-area based paging (e.g. first paging in last known cell id or TA and retransmissions in all registered TAs)

[0532] NOTE 2: Setting the paging priority (or paging policy indicator) in a paging message is independent of any paging policy.

[0533] To reduce the signaling load and network resources used to successfully page the UE, the AMF and (R)AN may support additional paging optimization using at least one or more of the following means:

[0534] Implementing specific paging strategies through the AMF (e.g., the AMF may send an N2 paging message to the (R)AN node that most recently served the UE);

[0535] The AMF considers information about the recommended cell and the NG-RAN node provided by the (R)AN when switching to the CM-IDLE state (Information about the Recommended Cell and the NG-RAN Node). The AMF may determine the (R)AN node to be paged by considering the (R)AN node-related part of the information, include the information about the recommended cell in the N2 paging message, and provide the information to each of the (R)AN nodes;

[0536] The paging attempt count information provided by the AMF in the paging is taken into account by the (R)AN.

[0537] When the UE radio capabilities for paging information are available in the AMF, the AMF may include the UE radio capabilities for paging information in the N2 paging message and send the corresponding N2 paging message to the (R)AN node.

[0538] When information about the recommended cell and NG-RAN node is available in the AMF, the AMF can consider the information to determine the (R)AN node for paging, and when paging the (R)AN node, the AMF can transparently send information about the recommended cell to the (R)AN node.

[0539] The AMF may include paging attempt count information in the N2 paging message. The paging attempt count information may be the same for all (R) ANs selected by the AMF for paging.

[0540] 4c) [Conditional Action] When the UE is registered for both 3GPP access and non-3GPP access in the same PLMN, the UE is in CM-CONNECTED state in the 3GPP access, and the PDU Session ID of step 3a is associated with the non-3GPP access, the AMF may send a NAS Notification message including the non-3GPP access type to the UE via the 3GPP access, and may set a Notification Timer. When step 4c is performed, step 5 may be omitted.

[0541] When a UE is simultaneously registered for 3GPP access and non-3GPP access in the same PLMN, the UE is in the CM-IDL state in the 3GPP access and in the CM-CONNECTED state in the non-3GPP access, the PDU session ID of step 3a is associated with the 3GPP access, and the AMF determines based on local policy that the UE can be notified via the non-3GPP access, the AMF may send a NAS notification message including the 3GPP access type to the UE via the non-3GPP access and set a notification timer.

[0542] 5) [Conditional Action] Signalling from AMF to SMF: AMF may send notifications related to the failure of Namf_Communication_N1N2Transfer to SMF. For example, AMF may send a Namf_Communication_N1N2TransferFailure notification to SMF.

[0543] The AMF uses a timer to supervise the paging process. If the AMF fails to receive a response to the Paging Request message from the UE, the AMF may apply additional paging according to any available paging strategy described in step 4b.

[0544] If the UE does not respond to the paging, the AMF sends a Namf_Communications_N1N2MessageTransfer failure notification to the notification target address provided by the SMF in step 3a to inform the SMF, unless the AMF identifies an ongoing MM procedure that prevents the UE from responding to the SMF. Here, the AMF's identification of an ongoing MM procedure that prevents the UE from responding may be, for example, a case where the AMF receives an N14 Context Request message instructing the UE to perform a registration procedure with another AMF.

[0545] When receiving the Namf_Communication_N1N2TransferFailure notification, the SMF may notify the UPF.

[0546] 6) When the UE is in CM-IDLE state in 3GPP access and receives a paging request for a PDU session related to the 3GPP access, the UE may initiate Figures 11a to 11c The UE-initiated service request process described in Figure 11a In step 4 of the service request message, the AMF may call the Nsmf_PDUSession_UpdateSMContext request associated with the PDU session identified in the service request message to the SMF (except for the Figure 12 (Outside the PDU session with the PDU session ID in Namf_Communication_N1N2MessageTransfer in step 3a). Figure 11a As described in steps 6a, 7a and 8b, in order to support the transmission of buffered data, the SMF can instruct the UPF to establish a data transmission tunnel between the old UPF and the new UPF or PSA.

[0547] When a UE is in CM-IDLE state in both non-3GPP access and 3GPP access and receives a paging request for a PDU session associated with the non-3GPP access, the UE may initiate a paging request. Figures 11a to 11c. Here, the service request procedure initiated by the UE may include a list of allowed PDU sessions that can be reactivated through 3GPP access according to the UE policy, and whether the S-NSSAI of the PDU session is included in the allowed NSSAI for 3GPP access. If there is no PDU session that can be reactivated through 3GPP access, the UE may include an empty allowed PDU session list. When the AMF receives a service request message from the UE through non-3GPP access (for example, because the UE successfully connects to the non-3GPP access), the AMF may stop the paging procedure and process the received service request procedure. When the AMF receives a service request message and the allowed PDU session list provided by the UE does not include the PDU session of the UE that has been paged, the AMF may call the Namf_EventExposure_Notify service to notify the SMF that the UE is reachable but does not accept the reactivation of the PDU session.

[0548] When the UE is in CM-IDLE state in non-3GPP access and in CM-CONNECTED state in 3GPP access, upon receiving a NAS notification message including the non-3GPP access type via 3GPP access, the UE may initiate Figures 11a to 11c The UE initiated service request procedure described in . Here, the UE initiated service request procedure may include a list of allowed PDU sessions that can be reactivated through 3GPP access according to the UE policy, and whether the S-NSSAI of the PDU session is included in the allowed NSSAI for 3GPP access. If there is no PDU session that can be reactivated through 3GPP access, the UE may include an empty allowed PDU session list. When the AMF receives a service request message and the allowed PDU session list provided by the UE does not include the PDU session of the UE that has been notified, the AMF may call the Namf_EventExposure_Notify service to notify the SMF that the UE is reachable but does not accept reactivation of the PDU session. When the AMF receives a service request message from the UE through non-3GPP access, the AMF may stop the notification timer and process the received service request procedure.

[0549] When a UE is in CM-IDLE state in 3GPP access and in CM-CONNECTED state in non-3GPP access, upon receiving a NAS notification identifying the 3GPP access type via the non-3GPP access, the UE may initiate a 3GPP access request if 3GPP access is available. Figures 11a to 11cIf the AMF does not receive the Service Request message before the notification timer expires, the AMF may page the UE via 3GPP access or notify the SMF that the UE cannot reactivate the PDU Session.

[0550] 7) The UPF may send the buffered downlink data to the UE through the (R)AN node that has performed the service request procedure.

[0551] When the network initiated service request procedure is initiated according to the request from another network described in step 3a, the network may send downlink signaling.

[0552] <Multiple Access (MA) PDU Session>

[0553] In the prior art, an MA PDU session is a session that can use one PDU session to simultaneously serve 3GPP access and non-3GPP access.

[0554] Figure 13 An example of generating an MA PDU session is shown.

[0555] exist Figure 13 In [1], a MAPDU session is a PDU session and has separate session tunnels for each access: one is established on a 3GPP access and the other PDU session is established on an untrusted non-3GPP access (e.g., WLAN AN).

[0556] Since a MAPDU session is a session, the MAPDU session has the following characteristics.

[0557] A DNN;

[0558] A UPF anchor point (UPF-A);

[0559] A PDU type (e.g., IPv6);

[0560] A session IP address

[0561] An SSC model

[0562] An HPLMN S-NSSAI.

[0563] The MA PDU session implements a multipath data link between the UE and the UPF-A. This can be implemented below the IP layer.

[0564] A MAPDU session can be established by one of the following procedures.

[0565] It can be established through two separate PDU session establishment processes. This is called a separate establishment.

[0566] It can be established through a MA PDU session establishment procedure. That is, an MA PDU session is established simultaneously in two accesses with a session establishment request. This is called binding establishment.

[0567] After the MA PDU session is established, session management (SM) signaling related to the MA PDU session can be sent and received through random access.

[0568] Separate establishment of MA PDU session

[0569] An MA PDU session can be established through two separate PDU session establishment procedures. For example, a UE can establish an MA PDU session on a 3GPP access and then perform a PDU session establishment procedure on a non-3GPP access to add the non-3GPP access to the MA PDU session created on the 3GPP access. The request type for adding the second access in the setup request message can be set to "MA PDU Request".

[0570] B. Binding establishment

[0571] An MA PDU session can be established for both 3GPP and non-3GPP accesses through a single procedure. Such a procedure may be referred to as a UE-requested MA PDU session establishment procedure. This procedure may be useful when the UE intends to establish an MA PDU session and the UE has registered with the 5GC through two accesses. Instead of performing two separate PDU session establishment procedures, the UE can establish an MA PDU session by performing a single MA PDU session establishment procedure.

[0572] Access Service Steering, Switching, and Splitting (ATSSS)

[0573] The ATSSS function may be an optional feature supported by the UE and the 5GC network.

[0574] The ATSSS function can implement multi-access PDU connection services. For example, the ATSSS function can exchange PDUs between the UE and the data network by using one 3GPP access network and one non-3GPP access network simultaneously and using two independent N3 / N9 tunnels between the PSA and the RAN / AN. The multi-access PDU connection service can be implemented by establishing a multi-access PDU (MA PDU) session. The MA PDU session can be, for example, a PDU session with user plane resources in two access networks.

[0575] The UE may request an MA PDU session if the UE is registered with both 3GPP and non-3GPP accesses, or if the UE is registered with only one access.

[0576] After establishing an MA PDU session, if user plane resources exist in both access networks, the UE applies network-provided policies (e.g., ATSSS rules) and exchanges local conditions (e.g., network interface availability, signal loss conditions, user preferences, etc.) to determine how to distribute uplink traffic over the two access networks. Similarly, the UPF anchor of the MA PDU session applies network-provided policies (e.g., N4 rules) and feedback information received from the UE via the user plane (e.g., access network unavailability or availability) to determine the distribution of downlink traffic to the two N3 / N9 tunnels and the two access networks. If only one access network has user plane resources, the UE may apply ATSSS rules and may consider local conditions in order to trigger the establishment or activation of user plane resources over the other access.

[0577] For example, the MAPDU session type may be one of IPv4, IPv6, IPv4v6, and Ethernet. The current version may not support the unstructured type.

[0578] ATSSS functionality can be supported via any type of access network. Here, all types of access networks can include untrusted non-3GPP access networks and trusted non-3GPP access networks, wired 5G access networks, etc. As long as an MA PDU session can be established via any type of access network, ATSSS functionality can be supported via any type of access network.

[0579] Hereinafter, the function for enabling ATSSS will be described.

[0580] First, the MA PDU session will be described. The MA PDU session can be managed using the session management function with the following additions and modifications.

[0581] If the UE wants to request a new MAPDU session

[0582] When a UE is registered in the same PLMN via 3GPP access and non-3GPP access, the UE may send a PDU Session Establishment Request message including "MA PDU Request" via one of the two accesses. The AMF may notify the SMF that the UE is registered via both accesses. The AMF notifying the SMF may trigger the establishment of user plane resources in both accesses and two N3 / N9 tunnels between the PDU Session Anchor (PSA) and the RAN / AN.

[0583] When a UE is registered with different PLMNs via 3GPP access and non-3GPP access, the UE can send a PDU Session Establishment Request message including "MAPDU Request" via one of the two accesses. After the PDU session is established in one N3 / N9 tunnel between the PSA and (R)AN / AN, the UE can send a PDU Session Establishment Request message including "MAP PDU Request" and the same PDU Session ID via the other access. User plane resources in both N3 / N9 tunnels between the access and the PSA and the RAN / AN can be established.

[0584] If the UE is registered through only one access, the UE may send a PDU Session Establishment Request message including an indication of "MA PDU Request" through the access to which the UE is registered. An N3 / N9 tunnel may be established between the PSA and RAN / AN and user plane resources in that access. After registering the UE through a second access, the UE may establish user plane resources in the second access.

[0585] In the PDU Session Establishment Request message sent to request a new MA PDU session, the UE may provide the UE's ATSSS capability information. The ATSSS capability (capability) information may include information on steering modes and steering functions supported by the UE.

[0586] If the UE indicates that it can support ATSC-LL (lower layer) functionality with any steering mode and the network accepts activation of the functionality, the network may provide UE measurement assistance information to the UE. In addition, the network may provide one or more ATSSS rules to the UE.

[0587] The UE indicates that the UE can support MPTCP functionality in any bootstrap mode and can support ASSSS-LL functionality only in active standby bootstrap mode, and the network can accept activation of these functionality. In this case, the network provides the UE with MPTCP proxy information, and the network can allocate to the UE one IP address / prefix for the MA PDU session and two additional IP addresses / prefixes called "link-specific multipath". In addition, the network can provide the UE with UE measurement assistance information and provide the UE with one or more ASSSS rules (including ASSSS rules for non-MPTCP services). The ASSSS rules for non-MPTCP services can use the ASSSS-LL functionality and active standby bootstrap mode to indicate how non-MPTCP services are sent via 3GPP access and non-3GPP access in the uplink direction.

[0588] If the UE indicates that it can support MPTCP functionality with all steering modes and ASSSS-LL functionality with all steering modes, and the network accepts the activation of these functions, the network may provide the UE with MPTCP proxy information. In addition, the network may allocate one IP address / prefix for the MA PDU session and two additional IP addresses / prefixes called "Link Specific Multipath" to the UE. The network may provide the UE with UE measurement assistance information and one or more ASSSS rules.

[0589] If the UE requests S-NSSAI, then S-NSSAI shall be allowed in both accesses. Otherwise, no MA PDU session may be established.

[0590] The SMF can determine the ASSSS capabilities supported by the MA PDU session based on the ASSSS capabilities provided by the UE and the DNN configuration of the SMF. The SMF can perform the following actions:

[0591] a) If the UE includes in ASSSS capabilities “MPTCP functionality with any bootstrapping mode and ATSSS-LL functionality with active standby bootstrapping mode only”; and

[0592] a-1) If the DNN configuration allows MPTCP and ATSSS-LL for all bootstrapping modes, then for an MA PDU session, (1) MPTCP and ATSSS-LL are possible for all bootstrapping modes in downlink, and (2) uplink MPTCP and ATSSS-LL are possible in Active Standby mode; or

[0593] a-2) If the DNN configuration allows MPTCP for all bootstrapping modes and allows ASSSS-LL for active standby mode, then for an MA PDU session, MPTCP and ASSSS-LL are possible in active standby mode in uplink and downlink.

[0594] b) If the UE includes "ATSSS-LL functionality with any steering mode" in the ATSSS capabilities and the DNN setting allows ATSSS-LL with any steering mode, the MAPDU session shall cover all steering modes in uplink and downlink. ATSSS-LL may be possible.

[0595] c) If the UE includes "MPTCP functionality with any steering mode and ASSSS-LL functionality with any steering mode" in the ASSSS capabilities and the DNN configuration allows MPTCP and ASSSS-LL for all steering modes, then for an MA PDU session, MPTCP and ASSSS-LL are possible for all steering modes in uplink and downlink.

[0596] When the PDU session establishment process is being performed, the SMF may provide the PCF with the ASSSS capability for the MA PDU session.

[0597] The policy and charging control (PCC) rules provided by the PCF may include ASSSS control information. PCC rules and ASSSS control information may be used by the SMF to derive the ASSSS rules for the UE and the N4 rules for the UPF. For MA PDU sessions, if dynamic PCC rules are not used, the SMF may provide ASSSS rules and N4 rules to the UE and UPF, respectively, based on local configuration (e.g., local configuration based on DNN or S-NSSAI).

[0598] The UE may receive ATSSS rules from the SMF. The ATSSS rules may indicate how uplink traffic is routed over 3GPP access and non-3GPP access. Similarly, the UPF may receive N4 rules from the SMF. The N4 rules may indicate how downlink traffic is routed over 3GPP access and non-3GPP access.

[0599] When the SMF receives a PDU session establishment request message including an "MA PDU Request" indication, and if the PDU session requires UP security protection, the SMF may confirm the establishment of the MAPDU session only if UP security protection requiring 3GPP access can be implemented. The SMF does not need to check whether it can implement UP security protection requiring non-3GPP access.

[0600] 2) After the MA PDU Session Establishment Procedure (i.e., after the MA PDU Session is established), the following description may apply:

[0601] At any given time, an MA PDU session may have user plane resources in both 3GPP and non-3GPP accesses, may have user plane resources in only one access, or may have no user plane resources in either access.

[0602] Even if the UE deregisters from one access, the AMF, SMF, PCF and UPF may maintain its MA PDU session context if the UE registers to another access.

[0603] When the UE deregisters from one access and registers for another access, the AMF may notify the SMF that the access type used for the MA PDU session has become unavailable. Thereafter, the SMF may notify the UPF that the access type of the deregistered access has become unavailable and that the N3 / N9 tunnel of the corresponding access type has been released.

[0604] When the UE wants to add user plane resources to an access of an MA PDU session (for example, based on access network performance measurements and / or ATSSS rules), the UE may send a PDU Session Establishment Request message over the access. Here, the PDU Session Establishment Request message may include the PDU Session ID of the MA PDU session and an "MA PDU Request" indication. For this access, if N3 / N9 does not exist, N3 / N9 for this access may be established.

[0605] When the UE wants to reactivate user plane resources in one access of an MA PDU session (e.g., based on access network performance measurements and / or ATSSS rules), the UE may initiate a UE-triggered service request procedure over the access.

[0606] 3) When the network wants to reactivate user plane resources through 3GPP access or non-3GPP access of an MA PDU session, the network may initiate a network-triggered service request procedure.

[0607] An MA PDU session may also be established in one of the following situations.

[0608] When a UE supporting ATSC explicitly requests the establishment of an MA PDU session; or

[0609] If a UE supporting ATSC requests a single access PDU session, but the network decides to establish an MA PDU session, an MA PDU session may be established. This example may correspond to an optional scenario that may occur when a UE requiring single access to a PDU session has requested a single access PDU session, but when there are no policies (e.g., UE Routing Policy (URSP) rules) and local restrictions.

[0610] When a UE moves from EPS to 5GS, an MA PDU session can be established while performing the PDU session modification procedure.

[0611] A UE supporting ATSC may decide to request an MA PDU session based on the provided URSP rules. Specifically, if the URSP rules trigger the UE to establish a new PDU session, and if the access type preference component of the URSP rules indicates "multiple access", then the UE may request an MA PDU session when the URSP rules are applied.

[0612] In the following, the strategy for ATSSS control will be described.

[0613] When establishing an MA PDU session, if dynamic PCC is used for the MA PDU session, the PCF may perform ASS policy determination and create PCC rules including ASS policy control information. Here, the ATSS policy control information may be used to determine how to distribute uplink and downlink traffic for the MA PDU session over 3GPP access and non-3GPP access.

[0614] The SMF may receive PCC rules and ATSSS policy control information from the PCF. Furthermore, the SMF may map these rules to (a) ATSSS rules sent to the UE and (b) N4 rules sent to the UPF. The ATSSS rules may be a prioritized list of rules that the UE applies to enforce the ATSSS policy in the uplink direction. Furthermore, the UPF may apply the N4 rules to enforce the ATSSS policy in the downlink direction.

[0615] When creating an MA PDU session or when the SMF updates an MA PDU session (for example, after the SMF receives updated (or new) PCC rules from the PCF), the ATSSS rules may be sent to the UE along with the NAS message. Similarly, when creating an MA PDU session or when the SMF updates an MA PDU session, the N4 rules may be sent to the UPF.

[0616] For ATSSS, Quality of Service (QoS) can be supported. Hereinafter, QoS support will be described (QoS support).

[0617] The 5G QoS model for single access PDU sessions can also be applied to MA PDU sessions. For example, QoS flows can be the finest granularity of QoS differentiation in MA PDU sessions. One difference compared to single access PDU sessions is that in MA PDU sessions, separate user plane tunnels can exist between AN and PSA, and each user plane tunnel can be associated with a specific access (3GPP access or non-3GPP access). However, QoS flows may not be associated with a specific access. That is, since QoS flows are access agnostic, the same QoS can be supported when services are distributed over 3GPP access and non-3GPP access. SMF can provide the same QoS flow ID (QFI) in 3GPP access and non-3GPP access, so that the same QoS is supported in both accesses.

[0618] In ATSSS, a steering function may be supported. Hereinafter, the steering function will be described.

[0619] The function of the UE supporting ATSC (UE supporting ATSC) to guide (coordinate), switch and split the traffic of the MA PDU session through 3GPP access and non-3GPP access may be referred to as "steering function". The UE supporting ATSC may support one or more of the following types of steering functions:

[0620] The UE may support high-level steering functions operating above the Internet Protocol (IP) layer. For example, the UE may support high-level steering functions ("MPTCP functions") that apply the Multipath Transport Control Protocol (MPTCP) protocol. This steering function ("MPTCP function") may be applied to direct, switch, and split TCP traffic for MPTCP-enabled applications. The UE's MPTCP function may communicate with the associated MPTCP proxy function of the UPF via the 3GPP user plane and / or the non-3GPP user plane.

[0621] Low-layer guidance functions that operate below the IP layer can be supported. For example, a low-layer guidance function called "ATSSS low-layer function" or ATSSS-LL function can be supported. Here, the guidance function ("ATSSS low-layer function" or ATSSS-LL function) can be applied to guide, switch and split any type of service (including TCP service, User Datagram Protocol (UDP) service, Ethernet service, etc.). The ATSSS-LL function must be provided in an Ethernet type MA PDU session. In the network, a UPF that supports ATSSS-LL must exist in the data path of the MA PDU session.

[0622] The UE may indicate to the network the steering functions and steering modes supported by the UE by including one of the following in the UE ATSSS capabilities:

[0623] ATSSS-LL functionality with any steering mode. In this case, the UE may indicate that it may use the ATSSS-LL functionality with all steering modes for steering, switching and splitting of all services of an MA PDU session.

[0624] MPTCP functionality with any bootstrap mode and ATSSS-LL functionality with only active standby bootstrap mode. In this case, ATSSS-LL functionality with only MPTCP functionality and active standby bootstrap mode with all bootstrap modes may be supported. In this case, the UE may indicate:

[0625] 2-a) The UE can use the MPTCP functionality with all steering modes to steer, switch, and split the MPTCP traffic of the MA PDU session.

[0626] 2-b) The UE may use the ATSSS-LL functionality with active standby steering mode to steer, switch, and split all other services (e.g., non-MPTCP services) of the MAPDU session.

[0627] 3) MPTCP functionality with any steering mode and ASSSS-LL functionality with any steering mode. In this case, MPTCP functionality with all steering modes and ASSSS-LL functionality with all steering modes may be supported. In this case, the UE may indicate:

[0628] 3-a) The UE can use the MPTCP functionality with all steering modes to steer, switch, and split the MPTCP services of the MA PDU session.

[0629] 3-b) The UE may use the ATSSS-LL functionality with any steering mode to steer, switch, and split all other services (ie, non-MPTCP services) in the MA PDU session.

[0630] <Packet Switching (PS) Data Off>

[0631] With the significant increase in users' use of data services, data capacity in mobile communication networks is increasing. Therefore, methods have been discussed to allow operators to limit unnecessary background traffic of user equipment (UE) or allow users to limit undesirable use of data (or signaling). As an example of such a solution, a feature called "PS Data Off" can be implemented in some systems (e.g., in EPS and 5GS).

[0632] In some embodiments, if a user activates the 3GPP PS Data Shutdown feature, traffic (e.g., all Internet Protocol (IP) packets, and all traffic of unstructured and Ethernet data) accessed via 3GPP is blocked, except for data related to certain exempt services (e.g., 3GPP PS Data Shutdown exempt services, hereinafter referred to as "exempt services").

[0633] Exempt services or 3GPP PS Data Off exempt services are services that are allowed even if the 3GPP PS Data Off feature is activated by the user. In some implementations, the 3GPP PS Data Off example services are a set of operator services. The 5GC can assist (or support) 3GPP PS Data Off operation in both non-roaming and roaming scenario modes.

[0634] Examples of 3GPP data switching exemption services are listed below.

[0635] Multimedia Telephony (MMTel) voice;

[0636] SMS over IP Multimedia Subsystem (IMS);

[0637] Unstructured Supplementary Service Data (USSD) over IMS (USSD Emulation Service in IMS (USSI));

[0638] MMTel video;

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

[0640] Device management on PS; and

[0641] IMS supplementary service configuration via the Ut interface using the Extensible Markup Language (XML) Configuration Application Protocol (XCAP)

[0642] Thus, when the UE activates the PS data off feature, the UE cannot perform uplink transmission (eg, mobile-initiated data transmission) and downlink data reception (eg, mobile-terminated data reception) except for this exemption service.

[0643] The UE may maintain information about the status of the PS Data Off feature (referred to as the PS Data Off status) (e.g., "activated" or "deactivated"). The UE may include the PS Data Off status in the Protocol Configuration Option (PCO) of the Attach Request, PDN Connection Request (per PDN (APN)), Bearer Resource Modification Request (per PDN (APN)) and PDU Session Establishment Request messages, and may notify the network of this. The network may notify the network of the acceptance (Accept) of PS Data Off assistance (or support) for the corresponding PDN (APN), or may reject this assistance (or support).

[0644] In some implementations, even if PS data off related operations are performed between the UE and the network, transmission of uplink data and downlink data is possible for operator-defined exempt services, even if PS data off is activated. In some scenarios, the list of such exempt services may be pre-configured by the operator's network and may be provided to the UE via a Management Object (MO) (NAS configured MO or new MO configured), for example, via Open Mobile Alliance Device Management (OMA DM) or USIM.

[0645] Thus, in some implementations, if the user activates the PS data off function, the UE cannot perform uplink data transmission to the PDN for all services except those included in the exempted service list. In some implementations, activation or deactivation of the PS data off function is typically configured by the user.

[0646] According to some implementations, up to two lists of 3GPP data shutdown exemption services for a UE may be configured and provided to the UE by the Home PLMN (HPLMN) via device management or UICC provisioning. If two lists are configured for a UE, one list is valid for the UE camped on the HPLMN and the other list is valid in a random VPLMN in which the UE is roaming. In some implementations, if only one list is configured for the UE, without any indication of which PLMN this applies to, then that list may be valid for both the Home PLMN and the random PLMN in which the UE intends to roam.

[0647] In some implementations, the operator will ensure that the list of GPP Data Off example services is provided to the UE and configured in the network.

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

[0649] In some implementations, the UE's reporting of the UE's 3GPP PS data off status during the UE-requested PDU session establishment procedure may also be applied to the scenario where a handover to 3GPP access occurs after the user activates / deactivates 3GPP PS data off, while the UE is connected only via non-3GPP access.

[0650] In case the 3GPP PS Data Shutdown feature is activated, the UE blocks uplink transmission of uplink IP packets and unstructured and Ethernet data based on a preconfigured list of 3GPP Data Shutdown example services, depending on the implementation.

[0651] The UE can include a modification (or shift) of the UE's 3GPP PS Data Off state in the PCO by using the UE-triggered PDU Session Modification procedure, and the UE will report this immediately. This can also be applied to NG-RAN inter-RAT mobility scenarios and scenarios where the 3GPP PS Data Off state changes (or shifts) while operating the Session Management Back-off Timer. In the event that the UE moves outside the LADN area and the PDU Session is still maintained in the UE, the UE will immediately report any change (or shift) in the 3GPP PS Data Off state of the PDU Session.

[0652] Additional operations of the SMF for 3GPP data off may be controlled by positioning configuration or policy of the PCF.

[0653] In case of using PDU sessions in IMS services, 3GPP data switching exemption service is implemented in the IMS area. If the UE's 3GPP data switching status is set to "activated", it should be ensured that the policy configured in the (H-)SMF / PCF is such that such service is always allowed.

[0654] As described above, in some implementations, up to two lists of 3GPP data off exemption services can be configured for a UE supporting (or assisting) 3GPP PS data off. The list of exemption services can also be configured by the EF3GPPPSDATAOFFUSIM file. Here, EF represents an elementary file, and EF3GPPPSDATAOFF represents an EF associated with 3GPP data off. An example of two lists of exemplary exemption services is described below.

[0655] A list of 3GPP PS Data Shutdown Exempt Services to be used in the HPLMN or Equivalent HPLMN (EHPLMN); and

[0656] List of 3GPP PS Data Off exemption services to be used in the VPLMN.

[0657] In some implementations, if only the above list is configured, the list may also be used in the VPLMN.

[0658] In case the UE assists (or supports) the 3GPP PS Data Off feature, then during the UE Requested PDU Session Establishment procedure and the UE Requested PDU Session Modification procedure, the UE may, according to some implementations, provide the 3GPP PS Data Off UE status by including the status in the Extended PCO IE.

[0659] The UE may operate in a network that assists with (or supports) the 3GPP PS Data Off feature.

[0660] By using the UE-Requested PDU Session Modification procedure, the UE may indicate a change (or shift) of the 3GPP PS Data Off state of a PDU Session.

[0661] In the case where the 3GPP PS data off state is "activated", according to some implementations, the UE may perform the following example operations.

[0662] The UE does not send uplink IP packets over 3GPP access except for the following exemptions:

[0663] 1-i) specifying a service in a list of 3GPP PS data switch-off exempt services to be used in the HPLMN or EHPLMN when the UE is in the UE's HPLMN or EHPLMN;

[0664] 1-ii) when the UE is in the UE's VPLMN, and only a list of 3GPP PS data switch-off exemption services for use in the HPLMN or EHPLMN is configured for the UE, a service specified in the list of 3GPP PS data switch-off exemption services for use in the HPLMN or EHPLMN;

[0665] 1-iii) if a list of 3GPP PS data switching exemption services to be used in the VPLMN is configured for the UE, services specified in the list of 3GPP PS data switching exemption services to be used in the VPLMN;

[0666] 1-iv) Services specified in the EF3GPP PSDATAOFF USIM profile; and

[0667] 1-vi) Uplink traffic according to procedures associated with the Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for handling supplementary services.

[0668] 2) The UE does not send any uplink Ethernet user data packets via 3GPP access; and

[0669] 3) The UE does not send any uplink unstructured user data packets via 3GPP access.

[0670] In case the 3GPP PS data off state is not "active", the UE can send uplink user data packets without restriction.

[0671] According to some implementations, the 3GPP PS Data Off feature does not restrict the transmission of uplink user data packets via non-3GPP access.

[0672] II. Problems to be Solved by the Disclosure of This Specification

[0673] In addition, in 5G mobile communications, the 3rd Generation Partnership Project (3GPP) Packet Switched (PS) Data Off function can be used. However, conventionally, when 3GPP PS Data Off is used for Packet Data Unit (PDU) sessions associated with non-3GPP access, no method for supporting effective communication has been discussed.

[0674] Hereinafter, examples of problems to be solved in the disclosure of this specification will be described in detail.

[0675] For MA PDU sessions, whether to support PS data shutdown was discussed. The following discussion was conducted:

[0676] For 3GPP access aspects of MA PDU sessions, the 3GPP PS Data Shutdown feature may be applied. For UEs with MA PDU sessions, when 3GPP PS Data Shutdown is activated (Activated), uplink and downlink traffic for MA PDU sessions over non-3GPP access may continue to follow expected ATSSS rules.

[0677] That is, when a MAPDU session supports PS Data Off, it has been discussed that PS Data Off applies to 3GPP access and does not apply to non-3GPP access. However, there has been no discussion of how to enable this. In other words, for MA PDU sessions, there has been no discussion of a method for applying PS Data Off only to 3GPP access and not to non-3GPP access.

[0678] For MAPDU sessions, it is proposed to apply the contents of PS Data Off that are not applied to non-3GPP access to PDU sessions established in non-3GPP access. In the following, PDU sessions established in non-3GPP access or PDU sessions connected only to non-3GPP access will be referred to as non-3GPP PDU sessions.

[0679] PS data off does not apply to non-3GPP PDU sessions. Therefore, the UE does not need to send a PS data off status report for non-3GPP PDU sessions. Here, the PS data off status report can be a report used to notify the network of the PS data off status. For example, the PS data off status report can be sent to notify a change in the PS data off status (e.g., activation or deactivation).

[0680] In addition, according to the service request process (e.g. Figures 11a to 11c and Figure 12 (The service request process described in the example of FIG) can be used to change the non-3GPP access PDU session of the terminal to a 3GPP access PDU session while executing the service request process. That is, the PDU session established in the non-3GPP access can be transferred to the 3GPP access (for example, a handover can be performed). In this case, since the network (for example, the network of the 3GPP access) is unaware of the PS data off state of the PDU session, data for services other than the 3GPP PS data off exemption service can be sent to the terminal.

[0681] For example, if a user activates PS data off after the terminal generates a non-3GPP access PDU session, the terminal does not need to send a PS data off status report. However, when the PDU session is transferred from non-3GPP access to 3GPP access during a subsequent service request, the PS data off status report of the PDU session is not sent to the network (e.g., the network of the 3GPP access). Therefore, even if the user activates PS data off, the network does not know the PS data off status. For this reason, even if the user activates PS data off, the network sends data to the terminal. Even if the user activates PS data off, since the network sends data to the terminal without considering the PS data off, it may affect billing. For this reason, even after PS data off is activated, the user must pay the fee. The disclosure of this specification proposes a method for solving this problem.

[0682] III. Disclosure of this Specification

[0683] The disclosure described below in this specification can be implemented in one or more combinations (for example, a combination including at least one of the contents described below). Each drawing shows an embodiment of each disclosure, but the embodiments of the drawings can be implemented in combination with each other.

[0684] The description of the method proposed in the disclosure of this specification may consist of a combination of one or more operations / configurations / steps described below. The following methods described below may be performed or used in combination or complementarily.

[0685] In this specification, the following methods are proposed to solve the problem. The following methods can be performed or used in combination or complementarily.

[0686] Hereinafter, the disclosure of the present specification will be described in detail with reference to the first to fourth examples of the disclosure of the present specification. For reference, the first to fourth examples of the disclosure of the present specification can be implemented in combination with each other.

[0687] First example of the disclosure of this specification

[0688] In the first example of the disclosure of this specification, the UE may send a PS data off status report even for a non-3GPP access PDU session. For example, the UE may send a PS data off status report during the process of generating (or establishing) a non-3GPP PDU session, and the UE may send a PS data off status report whenever the PS data off status is changed. In this case, the UE may send a PS data off status report to the network during the process of generating (or establishing) a non-3GPP PDU session. In addition, the UE may receive an indication (or information) of PS data off support from the network. In addition, in this case, the terminal may send a PS data off status report to the network. Here, the PS data off support indication (or information) may be an indication (or information) indicating that the network (e.g., SMF, UPF, AMF, PCF, etc.) supports PS data off. In addition, when the UE switches the PDU session from non-3GPP access to 3GPP access, the UE may not need to send a PS data off status report again unless the PS data off status changes. On the contrary, even when the UE switches the PDU session of 3GPP access to non-3GPP access, the UE does not need to send a PS data off status report unless the PS data status changes. To this end, the SMF stores the PS data off status report sent by the UE and can determine whether to apply PS data off when the access changes (for example, when the PDU session is switched from 3GPP access to non-3GPP access, or when the PDU session is switched from non-3GPP access to 3GPP access).

[0689] The SMF may receive a PS data closing status report from the terminal. In this case, the SMF may determine whether to apply PS data closing by considering the access type (e.g., non-3GPP access or 3GPP access) of the current PDU session. For example, even if the terminal reports that the PS data closing status is activated for non-3GPP access, the SMF may prevent PS data closing from being applied to non-3GPP access. If a PCF is used (e.g., if a PCF exists), the PCF generates (or updates) a PCC rule by considering the access type (e.g., non-3GPP access or 3GPP access) of the current PDU session so that PS data closing may be activated only in the case of 3GPP access and PS data closing may not be activated in the case of non-3GPP access. For reference, if there is no PCF, the SMF may operate based on the PCC rule set in the SMF.

[0690] When a non-3GPP access PDU session may be switched to 3GPP access, the UE may send a PS data closing status report for the non-3GPP access PDU session. For example, the UE considers whether the URSP rule or NSSAI of the non-3GPP access is included in the 3GPP access, and the UE may send a PS data closing status report only when a switch from non-3GPP access to 3GPP access is possible in the PDU session PS data closing. If the URSP rule or the allowed NSSAI of the 3GPP access is updated, the UE may determine whether to send a PS data closing status report again for the non-3GPP access PDU session. In this way, the UE does not perform PS data closing status reporting for all non-3GPP access PDU sessions, and performs PS data closing status reporting for non-3GPP access PDU sessions that may be switched to 3GPP access.

[0691] When the UE sends a PS data off status report for a non-3GPP access PDU session to the SMF, the SMF may not notify the PCF of the PS data off status report. This may be due to the local configuration of the SMF, or because the PCF may not request a PS data status report for non-3GPP access. That is, the SMF may not send a PS data off status report to the PCF based on the local configuration of the SMF or based on the fact that the PCF does not request a PS data status report for non-3GPP access. For example, the PCF may request the SMF to report a 3GPP PS off data status change for a 3GPP access PDU session (for example, when the 3GPP PS off data status changes), and the PCF may request the SMF not to report a PS off data status change for a non-3GPP access PDU session. To this end (for example, reporting the PS data off status to the PCF when a PDU non-3GPP PDU session is switched to 3GPP access), the SMF may store the PS data off status report sent by the UE. When a non-3GPP access PDU session is switched to 3GPP access, the SMF may notify (or send) the PCF of the PS data off status. In this case, the SMF can perform reporting only when the status changes from the last reported status. For example, if the SMF previously sent a PS data off status report to the PCF, the SMF can only send a PS data off status report to the PCF when the PS data off status of the last PS data off status report sent by the SMF is different from the current PS data off status. To this end, the SMF can store the PS data off status last reported to the PCF. If the SMF reports only when the last reported PS data off status changes, the PCF always stores the PS data off status previously reported by the SMF. For example, when the terminal reports that the PS data off status is activated in 3GPP access, the PCF can store that the PS data off status is activated. When the SMF notifies the PCF of an event that the access type changes to non-3GPP, the PCF can update the PCC rules based on the PS data off status previously reported by the SMF (e.g., activated). For example, since PS data off is not applied in non-3GPP access, the PCF can update the PCC rules so that data can be sent to the terminal regardless of PS data off.

[0692] According to the first example disclosed in this specification, even if PS data off is not applied to a PDU session in non-3GPP access, the UE must perform a PS data off status report when the PS data off status changes, and signaling may increase.

[0693] In the following, reference will be made to Figure 14a 、 Figure 14b and Figure 15 An example of operations of a terminal and a network according to the first example of the disclosure of this specification is described in detail.

[0694] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented as examples, the technical features of this specification are not limited to the specific names used in the following figures.

[0695] Figure 14a and Figure 14b An example of operations of a terminal and a network according to the first example of the disclosure of this specification is shown.

[0696] Figure 14a and Figure 14b An example is shown in which a PDU session is switched to 3GPP access after the UE generates (or establishes) the PDU session in non-3GPP access. Figure 14a and Figure 14b The example can basically follow the reference above Figure 9a and Figure 9b The example describes the PDU session establishment process. Figure 14a and Figure 14b In the example of FIG, the UE may report the PS data off state as active when generating (or establishing) a PDU session in non-3GPP access. Thereafter, when the UE switches the PDU session to 3GPP access, since the previously reported PS data off state has not changed (for example, when the previously reported PS data off state and the current PS data off state are the same), it is assumed that the UE does not separately report the PS data off state.

[0697] The UE may send a PDU Session Establishment Request message in non-3GPP access to create (or establish) a PDU session. In this case, the terminal may confuse the PS Data Off state with an active state. The PDU Session Establishment Request message may include request type information and a PCO. The request type information may include an initial request indicating the establishment of a new PDU session. The PCO may include information indicating that the PS Data Off state is activated.

[0698] The AMF sends the PDU session establishment request message sent by the UE to the SMF. For example, the AMF may send an Nsmf_PDUSession_CreateSMContext message including the PDU session establishment request message and request type information (e.g., "initial request") to the SMF.

[0699] The SMF may report the PS data off status sent by the terminal to the PCF. In this case, the SMF may notify the PCF of the access type information of the PDU session (i.e., non-3GPP access) in the same manner as in the prior art. Although the UE reports the PS data off status as active, since the PDU session is a non-3GPP access PDU session, the PCF may not generate a PCC rule for activating PS data off.

[0700] The SMF may send a PDU session establishment accept message (e.g., a PDU session establishment request message) for accepting the UE's request and N2 SM information for establishing non-3GPP access resources to the N3IWF. For example, the SMF may send the PDU session establishment accept message and the N2 SM information to the N3IWF via the AMF. As an example, the SMF may send a Namf_Communication_N1N2MessageTransfer message (including an N1 SM container, which includes the PDU session establishment accept message and the N2 SM information) to the AMF.

[0701] AMF can send the N2 SM information and PDU session establishment accept message sent by SMF to N3IWF.

[0702] The N3IWF can send and receive AN signaling for resources to establish a PDU session with the UE. During this process, the N3IWF can send a PDU session establishment accept message to the UE. Even if the UE reports the PS data closing status of the corresponding PDU session as activated, since the PDU session is a non-3GPP access PDU session, data that does not belong to the 3GPP PS data closing exemption service can be sent without blocking the data. That is, when PS data closing is activated, the UE can handle operations related to the PDU session in the same way as when PS data closing is not activated.

[0703] 7-8) N3IWF can notify SMF through AMF that AN resource setting has been successfully executed.

[0704] Hereinafter, operations according to the first example disclosed in this specification will be described in a case where a terminal switches a PDU session from non-3GPP access to 3GPP access.

[0705] 9) The UE can send a PDU Session Establishment Request message to switch a PDU session generated (or established) in a non-3GPP access to a 3GPP access. In this case, in order to notify that the PDU Session Establishment Request message is a message for switching a PDU session, the UE can set the request type to "existing PDU session" and send the PDU session ID to switch together. In addition, since Figure 14a and Figure 14b It is assumed that the PS data off status reported in step 1 has not changed, so the UE may not include the PS data off status in the PDU session establishment request message. If before performing step 9), when the UE transitions the PS data off status to deactivated, the UE may send a PDU session establishment request message including the PS data off status information.

[0706] 10) AMF sends the PDU session establishment request message sent by the UE to SMF. For example, AMF can send an Nsmf_PDUSession_CreateSMContext message including the PDU session establishment request message and request type information (e.g., "existing PDU session") to SMF.

[0707] 11) The SMF may notify the PCF of information that the PDU session has been changed to 3GPP access (for example, information that the PDU session has been switched from non-3GPP access to 3GPP access) by the UE performing a switchover of the PDU session to 3GPP access. Upon receiving information from the SMF that the PDU session has been changed to 3GPP access, the PCF generates (or updates) a PCC rule for activating PS data off based on the UE reporting that the PS data off state is activated, and the PCF may send the PCC rule to the SMF. Here, the PCC rule for activating PS data off may mean a PCC rule for sending or not sending data to the UE according to whether the data is included in the PS data off exemption service when the PS data off state is activated.

[0708] 12) The SMF may generate an N4 rule based on the updated PCC rule (e.g., the PCC rule received from the PCF in step 11) and send the N4 rule to the UPF (not shown). The SMF may send a PDU Session Establishment Accept message for accepting the UE's request (e.g., a PDU Session Establishment Request message) and N2 SM information for establishing resources for 3GPP access to the RAN. For example, the SMF may send the PDU Session Establishment Accept message and the N2 SM information to the RAN via the AMF. As an example, the SMF may send a Namf_Communication_N1N2MessageTransfer message (including an N1SM container, which includes the PDU Session Establishment Accept message and the N2 SM information) to the AMF.

[0709] 13)AMF may send the N2 SM information and PDU session establishment accept message sent by SMF to RAN.

[0710] 14) The RAN may send and receive AN signaling for resources used to establish a PDU session with the UE. During this process, the RAN may send a PDU Session Establishment Accept message to the UE. Since the PDU session has changed from a non-3GPP access PDU session to a 3GPP access PDU session, the UE may not send data that does not fall under the 3GPP PS Data Shutdown Exemption Service to the network and may only send data that falls under the 3GPP PS Data Shutdown Exemption Service to the network.

[0711] 15-16) RAN can notify SMF through AMF that AN resource setting has been successfully executed.

[0712] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented as examples, the technical features of this specification are not limited to the specific names used in the following figures.

[0713] Figure 15 An example of the operation of the terminal according to the first example disclosed in this specification is shown.

[0714] Figure 15 The examples are only examples of operations performed by the terminal, and except Figure 15 In addition to the operations shown in , the terminal may also perform the operations of the terminal (eg, UE) described in the first example disclosed in this specification. In addition, the terminal may perform the operations of the terminal in the following description with reference to the second to fourth examples disclosed in this specification.

[0715] In step S1601, the terminal may send a PDU session establishment request message. The UE may send the PDU session establishment request message to establish a PDU session associated with 3GPP access and / or non-3GPP access. The UE may send the PDU session establishment request message by including the UE's PS data off status information in the PDU session establishment request message. The UE's PS data off status information may be sent by including the PCO in the PDU session establishment request message.

[0716] In step S1602, for handover between 3GPP access and non-3GPP access, the UE may send a PDU session establishment request message. The UE may send the PDU session establishment request message by including the UE's PS data off status information in the PDU session establishment request message. At this time, if the PS data off status has not changed since the last report (i.e., if the last reported PS data off status is the same as the current PS data off status), the UE may not send the PS data off status information.

[0717] For reference, step S1602 may be selectively performed. For example, step S1602 may be performed only when handover between 3GPP access and non-3GPP access is required.

[0718] For reference, the PS Data Off state of a PDU Session does not affect data transmission via non-3GPP access. For example, even if the PS Data Off state is active, since PS Data Off does not apply to communications via non-3GPP access, the network and the terminal can communicate via non-3GPP access regardless of the PS Data Off state.

[0719] When receiving a PDU session establishment request message from the terminal, the SMF can determine whether to apply PS data closing based on the access type and PS data closing status of the PDU session.

[0720] Second Example of the Disclosure of This Specification

[0721] In a second example disclosed in this specification, when a terminal receives paging or NAS notification related to non-3GPP access through 3GPP access, an operation of transmitting a PS data off status report while performing a service request procedure will be explained.

[0722] Hereinafter, the second example disclosed in the present specification will be described in detail with reference to the first example and the second example of the second example disclosed in the present specification.

[0723] 2-1. First Example of the Second Example Disclosed in This Specification

[0724] According to the first example of the second example disclosed in this specification, the terminal may send a service request message including a PS data off status report.

[0725] Specifically, the terminal may receive paging or NAS notification for non-3GPP access. In this case, the terminal may send a service request message by including a PS data off status report in the service request message at the same time as sending the service request message.

[0726] Upon receiving a service request message including a PS data closing status report, the AMF may send a PS data closing status report for all PDU sessions. For example, the AMF may send a PS data closing status report related to all PDU sessions that the UE has to the SMF. Alternatively, the AMF may send a PS data closing status report only for non-3GPP access PDU sessions instead of all PDU sessions. For example, the AMF may send a PS data closing status report related to non-3GPP access PDU sessions owned by the UE to the SMF. Alternatively, the AMF may send a PS data closing status report only for non-3GPP access PDU sessions for which mobile terminal (MT) data arrives and triggers a network-initiated service request process. For example, the AMF may send a PS data closing status report related to a non-3GPP access PDU session related to the received MT data to the SMF.

[0727] Upon receiving the PS data closing status report from the AMF, the SMF may notify the UE whether PS data closing is supported for the PDU session. For example, if PS data closing is supported for the PDU session, the SMF may send a PS data closing support indication to the terminal through the PCO by performing the PDU session modification process initiated by the SMF. Alternatively, when the PDU session supports PS closing data, the SMF may notify the AMF by including a PS closing data status support indication in the Nsmf_PDUSession_UpdateSMContext response message. For reference, the indication of supporting the PS data closing status here may be information indicating that the PDU session supports PS data closing. For example, the SMF may send an Nsmf_PDUSession_UpdateSMContext response message including an indication of PS data closing status support to the AMF. The AMF may notify (i.e., send) the terminal of the PS data closing support indication received from each SMF.

[0728] 2-2. Second Example of the Second Example Disclosed in This Specification

[0729] According to the second example of the second example disclosed in this specification, the UE may send a service request message including an SM container. Here, the SM container may include a PDU session modification request message including a PS data off status report.

[0730] Specifically, the terminal may send a service request message including an SM container. Here, the SM container may include a PDU session modification request message including a PS data off status report. The UE may send a PS data off status report for each PDU session by sending a PDU session modification request message including a PS data off status report via the service request message.

[0731] Upon receiving the service request message, the AMF may send an SM message (e.g., a PDU session modification request message) included in the SM container of the service request message to the SMF responsible for each PDU session. The SMF may send a PDU session modification command message including a PS data shutdown support indication to the UE. For reference, the indication of supporting the PS data shutdown status here may be information indicating that the PDU session supports PS data shutdown. In addition, when the SMF receiving the SM message needs to move the PDU session from non-3GPP access to 3GPP access (e.g., when the SMF receives an "indication that the access type can be changed" from the AMF), the SMF may determine whether to send data to the terminal based on the PS data shutdown status. For example, if the terminal sends a PS data shutdown status of "activated," the SMF only sends data related to services included in the 3GPP PS data shutdown exemption service to the terminal, and the SMF blocks data for services other than those included in the 3GPP PS data shutdown exemption service. In this case, the SMF may determine whether to move the corresponding non-3GPP access PDU session to 3GPP access. For reference, the "indication that the access type may be changed" may be information indicating that a PDU session associated with non-3GPP access may be moved to 3GPP access. After the "indication that the access type may be changed" is sent to the network (e.g., SMF), the SMF and / or PCF may determine whether to transfer the non-3GPP access PDU session to 3GPP access based on the "indication that the access type may be changed."

[0732] In the following, reference will be made to Figure 16 An example of operations of a specific terminal and a network according to the second example of the disclosure of this specification is described.

[0733] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented as examples, the technical features of this specification are not limited to the specific names used in the following figures.

[0734] Figure 16 An example of operations of a terminal and a network according to the second example of the disclosure of this specification is shown.

[0735] Figure 16 An example is described in which a terminal reports a PS data off state while performing a service request procedure. Figure 16 The example can basically follow the reference above Figure 12 The service request process is described in the example.

[0736] Downlink data for a non-3GPP access PDU session may arrive at the UPF. For example, the UPF may receive downlink data related to a non-3GPP access PDU session of a terminal.

[0737] The UPF may notify the SMF that downlink data has arrived. For example, the UPF may send a data notification message, and the SMF may send a confirmation message to the UPF.

[0738] The SMF may send an N2 message (e.g., Namf_CommunicationN1N2MessageTransfer message) to the AMF to establish user plane resources for the non-3GPP access PDU session.

[0739] exist Figure 16 In the example shown in FIG1 , it is assumed that the terminal is in the CM (Connection Management)-IDLE state in non-3GPP access. The AMF may know that the terminal is in the CM-IDLE state in non-3GPP access and may send a Paging Request message to the RAN via 3GPP access to page the terminal. In this case, the AMF may set the access type information to non-3GPP access to notify that the paging is for non-3GPP access. The access type information may be included in the Paging Request message and sent.

[0740] The RAN may perform paging for the UE. In this case, the RAN may include information indicating that it is paging a non-3GPP access in a paging message sent to the terminal based on information sent by the AMF (e.g., access type information notifying it that it is paging a non-3GPP access). For example, the RAN may send a paging message to the terminal including information indicating that the paging is for a non-3GPP access.

[0741] The UE may receive a paging message for non-3GPP access. And, the terminal may perform a service request process in response to the paging message. For example, the terminal may send a service request message to the AMF. At this time, since the UE knows that the PDU session can be switched to 3GPP access, the UE may set the PS data closed status report to be activated and send the PS data closed status report together with the service request message. For example, when the user activates the PS data closed state, the terminal receives a paging message for non-3GPP access through 3GPP access, and then sends a service request message including information for activating the PS data closed status report to the AMF. For example, the UE may send a service request message to the AMF including a list of PDU sessions that may be switched to 3GPP access (e.g., an allowed PDU session list). The AMF may then send an "indication that the access type may be changed" to the SMF based on the PDU session list (e.g., the allowed PDU session list).

[0742] Here, as described above in item 2-1 (the first example of the second example disclosed in this specification), the terminal may send a service request message including a PS data off status report. Alternatively, as described in item 2-2 (the second example of the second example disclosed in this specification), the terminal may also send a service request message including a PDU session modification request message by including the PS data off status in the PCO of the PDU session modification request message.

[0743] 7) The AMF may notify the SMF that the UE may move the non-3GPP PDU session to 3GPP access. For reference, since the AMF has received a service request message including a list of PDU sessions that may be switched to 3GPP access (allowed PDU session list), the AMF may know that the terminal may move the non-3GPP PDU session to 3GPP access. For example, the AMF may send an Nsmf_PDUSession_UpdateSMContext request message including information indicating that the UE may move the non-3GPP PDU session to 3GPP access. In this case, when performing the operation according to item 2-1 above (the first example of the second example disclosed in this specification), the AMF may send the PS data off status sent by the terminal to the SMF together. When performing the operation as described in item 2-2 above (the second example of the second example disclosed in this specification), the AMF may send the PDU session modification request message sent by the terminal to the SMF together.

[0744] 8) The SMF may notify the PCF that the terminal's PS data off state is active. The PCF may generate (or update) PCC rules for applying PS data off. The PCF may send the generated (or updated) PCC rules to the SMF.

[0745] 9) The SMF may generate N4 rules based on the PCC rules received from the PCF. For example, the SMF may generate N4 rules so that services that do not belong to the 3GPP PS Data Shutdown Exemption Service are not sent to the UE.

[0746] 10) The SMF may send an N2 message to the AMF for establishing user plane resources for the PDU session in order to move the PDU session to 3GPP access.

[0747] 11)AMF may send the N2 message sent by SMF to RAN. In addition, in order to notify the terminal that the service request has been successful, AMF may also send a service acceptance message to the terminal.

[0748] 12) RAN may perform AN signaling to establish user plane resources. In this case, RAN may send a service acceptance message to the terminal.

[0749] 13-14) RAN may notify SMF through AMF that the establishment of user plane resources has been successfully performed.

[0750] Third Example of the Disclosure of This Specification

[0751] In a second example disclosed in this specification, when a terminal receives paging or NAS notification related to non-3GPP access, when sending an allowed PDU session list, an operation for configuring an allowed PDU session list considering the PS data off state will be described.

[0752] According to the prior art, when a terminal receives a paging or NAS notification related to non-3GPP access via 3GPP access, the terminal can check whether the UE policy and S-NSSAI of the PDU session are allowed in 3GPP access. As a result of the check, if the PDU session can be used for 3GPP access, the UE sends a service request message by including the non-3GPP access PDU session information in the allowed PDU session list.

[0753] The third example disclosed in this specification includes an operation in which the terminal also considers the PS data off state at this time.

[0754] For example, when the user activates the PS data off state, all services used in a specific non-3GPP access PDU session may not be included in the 3GPP PS data off exemption service. In this case, even if the PDU session is moved to 3GPP access, since the UE cannot receive services for the PDU session, the UE may not include the non-3GPP PDU session in the allowed PDU session list. For example, all services used in a specific non-3GPP access PDU session may be included in the 3GPP PS data off exemption service. In this case, the UE can transmit the non-3GPP PDU session by including the non-3GPP PDU session in the allowed PDU session list.

[0755] If a specific non-3GPP PDU session uses services included in the 3GPP PS Data Shutdown Exemption Service and services not included in the 3GPP PS Data Shutdown Exemption Service, the operation of the terminal may vary depending on whether the first example or the second example disclosed in this specification is performed. If the first example or the second example disclosed in this specification is performed, if even one service used by the specific non-3GPP PDU session is included in the 3GPP PS Data Shutdown Exemption Service, the UE may transmit an allowed PDU session list by including the corresponding non-3GPP PDU session. If neither the first example nor the second example disclosed in this specification is performed, the terminal may not include the corresponding non-3GPP PDU session in the allowed PDU session list.

[0756] Alternatively, when neither the first example nor the second example of the disclosure of this specification is performed, when the user activates the PS data off state so that the terminal can perform simple operations, the UE may not include any PDU session information in the allowed PDU session list. In other words, the UE may send an empty allowed PDU session list.

[0757] In the following, reference will be made to Figure 17 An example of operations of a specific terminal and a network according to the third example of the disclosure of this specification is described.

[0758] The following figures are created to explain specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented as examples, the technical features of this specification are not limited to the specific names used in the following figures.

[0759] Figure 17 An example of operations of a terminal and a network according to the third example of the disclosure of this specification is shown.

[0760] Figure 17 An example of operation that considers the PS Data Off state when the UE establishes an allowed PDU session list while performing a service request procedure is described. Figure 17 The examples can basically follow the reference Figure 12 The service request process is described in the example.

[0761] Downlink data for a non-3GPP access PDU session may arrive at the UPF. For example, the UPF may receive downlink data related to a non-3GPP access PDU session of a terminal.

[0762] The UPF may notify the SMF that downlink data has arrived. For example, the UPF may send a data notification message, and the SMF may send an Ack message to the UPF.

[0763] The SMF may send an N2 message (e.g., Namf_CommunicationN1N2MessageTransfer message) to the AMF to establish user plane resources for the non-3GPP access PDU session.

[0764] exist Figure 16In the example shown in FIG1 , it is assumed that the terminal is in the CM (Connection Management)-IDLE state in non-3GPP access. The AMF may know that the terminal is in the CM-IDLE state in non-3GPP access and may send a Paging Request message to the RAN via 3GPP access to page the terminal. In this case, the AMF may set the access type information to non-3GPP access to notify that the paging is for non-3GPP access. This access type information may be included in the Paging Request message and sent.

[0765] The RAN may perform paging for the UE. In this case, the RAN may include information indicating that it is paging a non-3GPP access (e.g., access type information used to notify that it is paging a non-3GPP access) in the paging message sent to the terminal based on the information sent by the AMF. For example, the RAN may send a paging message to the terminal including information indicating that the paging is for a non-3GPP access.

[0766] The UE may receive a paging message for non-3GPP access. And, the UE may perform a service request process in response to the paging message. In this case, according to the prior art, the UE may send an allowed PDU session list to the AMF, which includes PDU session information that can be switched to 3GPP access among non-3GPP PDU sessions. According to the third example of the present disclosure, unlike the prior art, when the PS data off state is activated, the UE may send an allowed PDU session list by including the corresponding non-3GPP PDU session only when all services used by the non-3GPP access PDU session are included in the 3GPP PS data off exemption service. If the service used by a non-3GPP PDU session is not included in the 3GPP PS data off exemption service, the UE may not include the non-3GPP PDU session information in the allowed PDU session list even if the corresponding PDU session can be switched to 3GPP.

[0767] The AMF may notify the SMF that the UE is unreachable based on the allowed PDU session information list sent by the terminal. When all services used by the non-3GPP access PDU session are included in the 3GPP PS shutdown exemption service and the UE sends the non-3GPP PDU session by including the corresponding non-3GPPP DU session in the allowed PDU session list, the AMF sends an "Indication that the access type can be changed" to the SMF to notify that the PDU session can be moved to 3GPP access.

[0768] The SMF may instruct the UPF to discard downlink traffic.

[0769] The SMF may send a response to step 7 to the AMF.

[0770] 10-12)AMF may send a service accept message to the terminal to notify that the service request has been successful.

[0771] The fourth example disclosed in this specification, described below, is an example in which the contents described in the disclosure of this specification are applied to a description related to 3GPP PS data shutdown. The contents described in the first to third examples disclosed in this specification can be applied to the fourth example disclosed in this specification. Furthermore, the contents described in the fourth example disclosed in this specification can also be applied to the disclosure of this specification (e.g., including the first to third examples disclosed in this specification).

[0772] Fourth Example of the Disclosure of This Specification

[0773] The fourth example of this specification describes the contents of PS data close for non-3GPP access PDU session.

[0774] For MA PDU sessions, the PS Data Off state does not affect data transmission via non-3GPP access.

[0775] Traditionally, it is unclear whether the UE sends the PS Data Off status for a PDU Session associated with a non-3GPP access. Typically, in order for the UE to handover a PDU Session from a non-3GPP access to a 3GPP access, the UE sends a PDU Session Setup Request message. In this case, the UE can report the PS Data Off status during the handover process by indicating the PS Data Off status in the PDU Session Setup Request message.

[0776] However, if the UE indicates the "Allowed PDU Session List" when performing the service request procedure, the PDU session associated with the non-3GPP access can be moved to the 3GPP access. In this case, the network does not know whether the UE has activated the PS Data Off state. Therefore, even if the user has activated PS Data Off and the buffered DL traffic does not belong to the 3GPP PS Data Off exemption service, there may be a situation where the network sends buffered DL traffic to the UE.

[0777] To prevent this, the UE should report the PS Data Off status even for non-3GPP access PDU sessions.

[0778] The PS Data Off state does not affect data delivery over non-3GPP access. Reporting of the PS Data Off state does not affect data delivery over non-3GPP access when the PDU Session is associated with a non-3GPP access. Reporting of the PS Data Off state is used to address the aforementioned scenario when the PDU Session is associated with a non-3GPP access (e.g., when a PDU Session is transferred from a non-3GPP access to a 3GPP access while a service request is in progress).

[0779] The UE may report the PS Data Off status even for non-3GPP access PDU sessions. If the UE fails to report the PS Data Off status even for non-3GPP access PDU sessions, the following results may occur. If a non-3GPP access PDU session is moved to 3GPP access while the service request procedure is being performed, DL traffic may be sent to the UE even if the user has enabled PS Data Off and the DL traffic does not belong to the 3GPP PS Data Off exemption service.

[0780] When a user enables 3GPP PS Data Shutdown, 3GPP PS Data Shutdown blocks traffic (all Internet Protocol (IP) packet traffic, unstructured and Ethernet data) over 3GPP access except data related to 3GPP PS Data Shutdown exempt services.

[0781] 3GPP Data Off Exemption Services are services that are allowed even when the user activates 3GPP PS Data Off. 3GPP PS Data Off Exemption Services are a set of operator services. 5GC supports 3GPP PS Data Off operation in both non-roaming and roaming scenarios.

[0782] Up to two 3GPP PS Data Shutdown Exemption Service Lists can be configured for a UE, and these lists can be provided to the UE through device management or UICC provisioning in the HPLMN (Home PLMN). If two lists are configured for a UE, one list is valid for UEs residing in the HPLMN, and the other list is valid for any VPLMN to which the UE roams. If only one list is configured for a UE without indicating which PLMN it applies to, the list can be valid for both the Home PLMN and any PLMN to which the UE intends to roam.

[0783] Note 1: The operator must ensure that the 3GPP PS Data Off Exemption Service configured in the network matches the UE.

[0784] During the UE's request for a PDU session establishment procedure, the UE may include its 3GPP PS data off status in the PCO and report it to the (H-)SMF. Here, the PDU session establishment procedure may be a PDU session establishment procedure for a PDU session associated with 3GPP access and a PDU session establishment procedure for a PDU session associated with non-3GPP access.

[0785] NOTE 2: The UE may not report the PS Data Off status during the PDU Session Establishment procedure for PDU Session Handover if the 3GPP PS Data Off status has not changed since the last report. Here, the last report means that the UE last reported the 3GPP PS Data Off status. Reporting of the PS Data Off status for a PDU Session associated with a non-3GPP access does not affect data delivery over the non-3GPP access. When 3GPP PS Data Off is activated, the UE blocks uplink transmission of uplink IP packets, unstructured, and Ethernet data based on a preconfigured list of Data Off Exempt Services (Preconfigured List of Data Off Exempt Services), except for data associated with 3GPP PS Data Off Exempt Services.

[0786] The UE may include the change of 3GPP data off state in the PCO using the UE-requested PDU session modification procedure layer and report it immediately. This may also apply to scenarios of inter-RAT mobility to NG-RAN and scenarios where the 3GPP data off state is changed while the session management fallback timer is running. If the UE is in a non-allowed area (non-allowed area) or in an area that is not an allowed area, the UE must also report the change of 3GPP PS data off state of the PDU session immediately. When the UE leaves the LADN area and the UE's PDU session is maintained, the UE shall also report the change of 3GPP PS data off state of the PDU session immediately.

[0787] Additional operations of the SMF for 3GPP PS data off may be controlled according to local settings or policies provided from the PCF.

[0788] Note 3: For PDU sessions used for IMS (IP Multimedia Subsystem) services, the 3GPP Data Shutdown Exemption Service may be applied in the IMS domain. When the UE's 3GPP Data Shutdown status is set to "Active", the policy set in the (H-)SMF / PCF may allow IMS services to be always allowed.

[0789] According to the disclosure of this specification, by applying PS data off only to 3GPP access, even if the terminal activates PS data off, data transmission can be performed through non-3GPP access, thereby ensuring service continuity.

[0790] As described in the first example disclosed in this specification, the UE can send a PS data off status report even for a non-3GPP access PDU session. For example, the UE can perform a PS data off status report even for a non-3GPP access PDU session. When the UE reports the PS data off status report as active by considering the access type of the PDU session, the SMF and / or PCF applies the PS data off policy only when the access type is 3GPP access, and when the access type is non-3GPP access, the SMF and / or PCF can provide services regardless of the PS data off status report.

[0791] As described in the second example disclosed in this specification, the terminal can send a PS data closing status report while performing a service request. For example, when the terminal receives a paging or NAS notification related to non-3GPP access, the terminal can send a service request message by including the PS data status report in the service request message. When the terminal receives a paging or NAS notification related to non-3GPP access, the terminal can send a service request message including an SM container in the service request message. Here, the SM container may include a PDU session modification request message for each non-3GPP access PDU session, and the PDU session modification request message may include a PCO (including a PS data closing status report). When the SMF and / or PCF receives "Access type can be changed" from the AMF and receives the PS data closing status report, when PS data closing is activated, the SMF and / or PCF can send downlink data to the terminal only when the downlink data is a 3GPP PS data closing exemption service.

[0792] As described in the third example disclosed in this specification, the UE may send an allowed PDU session list while taking into account the PS data off state. For example, when the terminal receives paging or NAS notification related to non-3GPP access, the terminal may send a service request message including an allowed PDU session list taking into account the PS data off state. For example, when the PS data off state is activated, the UE may send an empty allowed PDU session list. The terminal may send a PS data off state report to the SMF by executing the first example or the second example disclosed in this specification. In this case, when the terminal receives paging or NAS notification related to non-3GPP access, the terminal may send an allowed PDU session list in a service request message. In this case, when the PS data off state is activated, the UE may send an allowed PDU session list by including only services belonging to the 3GPP PS data off exemption service in the allowed PDU session list.

[0793] For reference, the operation of the terminal (eg, UE) described in this specification may be performed by the above Figures 1 to 3For example, a terminal (eg, UE) may be Figure 1 The first wireless device 100 or the second wireless device 200 in the embodiment of the present invention may be a first wireless device 100 or a second wireless device 200. For example, the operations of the terminal (e.g., UE) described herein may be processed by one or more processors 102 or 202. The operations of the terminal described herein may be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., instructions, executable codes) that can be executed by one or more processors 102 or 202. The one or more processors 102 or 202 control the one or more memories 104 or 204 and the one or more transceivers 106 or 206, and may perform the operations of the terminal (e.g., UE) described herein by executing the instructions / programs stored in the one or more memories 104 or 204.

[0794] In addition, instructions for performing the operations of a terminal (e.g., UE) described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium that records the instructions. The storage medium may be included in one or more memories 104 or 204. Furthermore, the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform the operations of the terminal (e.g., UE) described in the disclosure of this specification.

[0795] For reference, the operations of the network nodes (e.g., AMF, SMF, UPF, PCF, N3IWF, etc.) or base stations (e.g., NG-RAN, gNB, gNB (NB-Io T), gNB (NR) eNB, RAN, etc.) described herein may be performed by the following methods. Figures 1 to 3For example, a network node (e.g., AMF, SMF, UPF, PCF, N3IWF, etc.) or a base station (e.g., NG-RAN, gNB, gNB (NB-Io T), gNB (NR) eNB, RAN, etc.) may be the first device 100a or the second device 100b. For example, the operations of the network node (e.g., AMF, SMF, UPF, PCF, N3IWF, etc.) or the base station (e.g., NG-RAN, gNB, gNB (NB-Io T), gNB (NR) eNB, RAN, etc.) described herein may be processed by one or more processors 102 or 202. The operations of the terminal described herein may be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., instructions, executable codes) that can be executed by one or more processors 102 or 202. One or more processors 102 or 202 can perform the operations of the network node (e.g., AMF, SMF, UPF, PCF, N3IWF, etc.) or base station (e.g., NG-RAN, gNB, gNB (NB-Io T), gNB (NR) eNB, RAN, etc.) described herein by controlling one or more memories 104 or 204 and one or more transceivers 106 or 206 and executing instructions / programs stored in one or more memories 104 or 204.

[0796] In addition, instructions for performing operations of a network node (e.g., AMF, SMF, UPF, PCF, N3IWF, etc.) or a base station (e.g., NG-RAN, gNB, gNB (NB-IoT), gNB (NR) eNB, RAN, etc.) described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium. The storage medium may be included in one or more memories 104 or 204. The instructions recorded in the storage medium are executed by one or more processors 102 or 202, causing operations of the network node (e.g., AMF, SMF, UPF, PCF, N3IWF, etc.) or a base station (e.g., NG-RAN, gNB, gNB (NB-IoT), gNB (NR) eNB, RAN, etc.) to be performed.

[0797] Hereinabove, the preferred embodiment has been exemplarily described, but the disclosure of the present specification is not limited to such specific embodiment, and thus, improvements, modifications, or changes may be made.

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

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

Claims

1. A method for performing communications related to packet switched (PS) data shutdown, the method being performed by a user equipment (UE) and comprising the following steps: sending a first PDU session establishment request message for establishment of a PDU session associated with a non-3rd Generation Partnership Project 3GPP access or a 3GPP access, The first PDU session establishment request message includes first report information related to the 3GPP PS data closed state of the UE, Regardless of whether the PDU session is associated with the 3GPP access or the non-3GPP access, the first report information is included in the first PDU session establishment request. wherein the 3GPP PS data off state for the PDU session does not affect data delivery via the non-3GPP access, and wherein, when the 3GPP PS data shutoff is activated, the 3GPP PS data shutoff blocks services accessed via the 3GPP except for services related to a 3GPP PS data shutoff exemption service; and sending a second PDU session establishment request message for handover of the PDU session between the 3GPP access and the non-3GPP access, Wherein, based on the fact that the 3GPP PS data off status of the UE has not changed since the last report information, the second PDU session establishment request message does not need to include second report information related to the 3GPP PS data off status.

2. The method according to claim 1, in, Based on the 3GPP PS data off state of the UE being changed from the 3GPP PS data off state included in the last report information, the second PDU session establishment request message includes the second report information related to the 3GPP PS data off state of the UE.

3. The method according to claim 1, in, Based on the 3GPP PS data off status of the UE not changing since last reporting information, the second PDU session establishment request message does not include the second reporting information related to the 3GPP PS data off status of the UE.

4. The method according to claim 1, further comprising the steps of: Based on the 3GPP PS data off status of the UE and the 3GPP PS data off status included in the last report information, it is determined whether to include the second report information related to the 3GPP PS data off status of the UE in the second PDU session establishment request message.

5. The method according to claim 1, in, When the report information related to the 3GPP PS data off state of the UE is not sent after the first report information is sent, the last report information is the first report information, When one or more report information related to the 3GPP PS data off state of the UE is sent after the first report information is sent, the last report information is the last sent report information among the one or more report information.

6. The method according to claim 1, Although the first report information includes information indicating that the 3GPP PS data off state of the UE is activated, when the PDU session is associated with the non-3GPP access, the 3GPP PS data off does not affect the PDU session.

7. The method according to claim 1, in, The first report information is included in a protocol configuration option PCO of the first PDU session establishment request message.

8. The method according to claim 1, in, The first PDU session establishment request message is sent together with request type information configured as “initial request”.

9. The method according to claim 1, in, The second PDU session establishment request message is sent together with request type information configured as “existing PDU session”.

10. A method for performing communications related to Packet Switched (PS) Data Close, the method being performed by a network node and comprising the steps of: receiving, from a user equipment UE, a first PDU session establishment request message for establishment of a PDU session associated with a non-3rd Generation Partnership Project 3GPP access or a 3GPP access, The first PDU session establishment request message includes first report information related to the 3GPP packet switched PS data closed state of the UE, Regardless of whether the PDU session is associated with the 3GPP access or the non-3GPP access, the first report information is included in the first PDU session establishment request. wherein the 3GPP PS data off state for the PDU session does not affect data delivery via the non-3GPP access, and wherein, when the 3GPP PS data shutoff is activated, the 3GPP PS data shutoff blocks services accessed via the 3GPP except for services related to a 3GPP PS data shutoff exemption service; and receiving, from the UE, a second PDU session establishment request message for handover of the PDU session between the 3GPP access and the non-3GPP access, Wherein, based on the fact that the 3GPP PS data off status of the UE has not changed since the last report information, the second PDU session establishment request message does not need to include second report information related to the 3GPP PS data off status.

11. The method according to claim 10, in, When no report information related to the 3GPP PS data off state of the UE is sent from the UE after the first report information is sent, the last report information is the first report information, When one or more report information related to the 3GPP PS data off state of the UE is sent from the UE after the first report information is sent, the last report information is the last sent report information among the one or more report information.

12. A user equipment (UE) for performing communications related to packet switched (PS) data shut down, the UE comprising: at least one processor; as well as at least one memory for storing instructions and operatively connected to the at least one processor, The operations performed based on the execution of the instruction by the at least one processor include: sending a first PDU session establishment request message for establishment of a PDU session associated with a non-3rd Generation Partnership Project 3GPP access or a 3GPP access, The first PDU session establishment request message includes first report information related to the 3GPP PS data closed state of the UE, Regardless of whether the PDU session is associated with the 3GPP access or the non-3GPP access, the first report information is included in the first PDU session establishment request. wherein the 3GPP PS data off state for the PDU session does not affect data delivery via the non-3GPP access, and wherein, when the 3GPP PS data shutoff is activated, the 3GPP PS data shutoff blocks services accessed via the 3GPP except for services related to a 3GPP PS data shutoff exemption service; and sending a second PDU session establishment request message for handover of the PDU session between the 3GPP access and the non-3GPP access, Wherein, based on the fact that the 3GPP PS data off status of the UE has not changed since the last report information, the second PDU session establishment request message does not need to include second report information related to the 3GPP PS data off status.

13. A network node for performing communications related to packet switched (PS) data close, the network node comprising: at least one processor; as well as at least one memory for storing instructions and operatively connected to the at least one processor, The operations performed based on the execution of the instruction by the at least one processor include: receiving, from a user equipment UE, a first PDU session establishment request message for establishment of a PDU session associated with a non-3rd Generation Partnership Project 3GPP access or a 3GPP access, The first PDU session establishment request message includes first report information related to the 3GPP packet switched PS data closed state of the UE, Regardless of whether the PDU session is associated with the 3GPP access or the non-3GPP access, the first report information is included in the first PDU session establishment request. wherein the 3GPP PS data off state for the PDU session does not affect data delivery via the non-3GPP access, and wherein, when the 3GPP PS data shutoff is activated, the 3GPP PS data shutoff blocks services accessed via the 3GPP except for services related to the 3GPP PS data shutoff exemption service; and receiving, from the UE, a second PDU session establishment request message for handover of the PDU session between the 3GPP access and the non-3GPP access, Wherein, based on the fact that the 3GPP PS data off status of the UE has not changed since the last report information, the second PDU session establishment request message does not need to include second report information related to the 3GPP PS data off status.

Images