Method and apparatus for operating terminal in wireless communication system
By using AMF and SMF to jointly manage PDU sessions in wireless communication systems, the problem of low session deactivation and resource release efficiency of terminals during 3GPP and non-3GPP access switching is solved, and efficient communication of terminals in MA PDU sessions is achieved. and service stability.
Patent Information
- Application Number
- CN202380037908.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-05-04
- Filing Date
- 2023-04-28
- Publication Date
- 2024-12-03
AI Technical Summary
In wireless communication systems, when the terminal executes a multi-access (MA) PDU session, it is difficult for the terminal to effectively handle 3GPP and non-3GPP access handover, resulting in session deactivation and resource release efficiency, affecting communication quality and service continuity.
Through the coordinated work of the access management function (AMF) and the session management function (SMF), the activation and release process of the PDU session is managed based on the access handover to ensure that PDU sessions that are not accessed by 3GPP avoid unnecessary deactivation during handover. AN release process to maintain service continuity.
In the wireless communication system, the terminal performs communication through 3GPP and non-3GPP access based on the MA PDU is realized, and the resource management efficiency during the access handover process is improved, and the stability and continuity of services are ensured.
Smart Images

Figure CN119073004A_ABST
Abstract
Description
Technical Field
[0001] The following description relates to a wireless communication system and a method of operating a terminal. Specifically, it relates to a method of maintaining a service even if access switching is performed when a terminal transmits data based on a multiple access (MA) PDU (Protocol Data Unit). Background Art
[0002] Wireless communication systems have been widely deployed to provide various types of communication services, such as voice or data. Generally speaking, wireless communication systems are multiple access systems that support communication for multiple users by sharing available system resources (bandwidth, transmit power, etc.). 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, and single carrier frequency division multiple access (SC-FDMA) systems.
[0003] Specifically, because a large number of communication devices require a large communication capacity, enhanced mobile broadband (eMBB) communication technology is being proposed compared to conventional radio access technology (RAT). In addition, not only large-scale machine type communication (massive MTC) that provides various services anytime and anywhere by connecting multiple devices and objects is being proposed, but also communication systems that take into account services / user terminal equipment (UE) that are sensitive to reliability and latency are being proposed. Various technical configurations are proposed for this purpose. Summary of the invention
[0004] Technical issues
[0005] The present disclosure relates to a method and apparatus for enabling a terminal to perform communication through 3GPP access and non-3GPP access based on MA PDU in a wireless communication system.
[0006] The present disclosure relates to an operation method and device when a terminal performs access switching for non-3GPP access in a situation where the terminal performs communication based on MA PDU in a wireless communication system.
[0007] The present disclosure relates to a method and apparatus for enabling an Access Management Function (AMF) to maintain a PDU session for a new non-3GPP access based on access switching in a wireless communication system.
[0008] The present disclosure relates to a method and apparatus for causing a session management function (SMF) to determine whether to perform session deactivation based on information received from an AMF.
[0009] The technical objectives to be achieved by the present disclosure are not limited to the contents mentioned above, and those skilled in the art who apply the technical configuration of the present disclosure can consider other technical objectives not mentioned herein from the embodiments of the present disclosure to be described below.
[0010] Technical Solution
[0011] As an example of the present disclosure, a method of operating an access management function (AMF) in a wireless communication system may include: performing registration on a first access having a first access and a second access having a second type and establishing a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type; receiving a registration request message from a terminal based on access switching, the registration request message including information about a list of PDU sessions to be activated; and performing registration on a third access having the second type based on the access switching and after performing activation of the PDU session to be switched to the third access having the second type, performing an access network (AN) release procedure on the second access having the second type. The AMF may perform deactivation of the at least one second PDU session through the AN release procedure based on the information about the list of PDU sessions to be activated.
[0012] In addition, as an example of the present disclosure, an access management function (AMF) operating in a wireless communication system may include at least one transceiver, at least one processor, and at least one memory, the at least one memory being operably connected to the at least one processor and configured to store instructions, which when executed, cause the at least one processor to perform specific operations. The specific operation may perform registration on a first access having a first access and a second access of a second type, establish a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type, control at least one transceiver to receive a registration request message from a terminal based on access switching, the registration request message including information about a list of PDU sessions to be activated, and perform registration on a third access having a second type based on access switching and perform an access network (AN) release procedure on the second access having the second type. The AMF may perform deactivation of at least one second PDU session through an AN release procedure based on the information about the list of PDU sessions to be activated.
[0013] In addition, as an example of the present disclosure, a method of operating a terminal in a wireless communication system may include: performing registration for a first access having a first type and a second access having a second type and establishing a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type, sending a registration request message to an access management function (AMF) based on access switching, the registration request message including information about a list of PDU sessions to be activated, and performing registration for a third access having the second type based on the access switching and performing an access network (AN) release procedure for the second access having the second type after performing activation of the PDU session to be switched to the third access having the second type. The AMF performs deactivation of the at least one second PDU session through the AN release procedure based on the information about the list of PDU sessions to be activated.
[0014] In addition, as an example of the present disclosure, a terminal operating in a wireless communication system may include at least one transceiver, at least one processor, and at least one memory, the at least one memory being operably connected to the at least one processor and configured to store instructions, which, when executed, cause the at least one processor to perform specific operations. The specific operation may perform registration for a first access of a first type and a second access of a second type, establish a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access of the first type and at least one second PDU session for the second access of the second type, control at least one transceiver to send a registration request message to an access management function (AMF) based on access switching, the registration request message including information about a list of PDU sessions to be activated, and perform registration for a third access of the second type based on access switching and perform an access network (AN) release procedure for the second access of the second type after performing activation of the PDU session to be switched to the third access of the second type. The AMF performs deactivation of at least one second PDU session through the AN release procedure based on the information about the list of PDU sessions to be activated.
[0015] In addition, as an example of the present disclosure, a device may include at least one memory and at least one processor, the at least one processor being functionally connected to the at least one memory, wherein the at least one processor controls the device to perform registration for a first access having a first type and a second access having a second type, establish a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type, receive a registration request message from a terminal based on access switching, the registration request message including information about a list of PDU sessions to be activated, and perform registration for a third access having the second type based on the access switching, perform activation of the PDU session switched to the third access having the second type, and perform an access network (AN) release procedure for the second access having the second type. The AMF performs deactivation of the at least one second PDU session through the AN release procedure based on the information about the list of PDU sessions to be activated.
[0016] In addition, as an example of the present disclosure, a non-transitory computer-readable medium storing at least one instruction may include at least one instruction executable by a processor. The at least one instruction may control a device to perform registration for a first access of a first type and a second access of a second type, establish a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access of the first type and at least one second PDU session for the second access of the second type, receive a registration request message from a terminal based on access switching, the registration request message including information about a list of PDU sessions to be activated, and perform registration for a third access of the second type based on access switching, perform activation of a PDU session switched to the third access of the second type, and perform an access network (AN) release procedure for the second access of the second type. The AMF performs deactivation of at least one second PDU session through the AN release procedure based on the information about the list of PDU sessions to be activated.
[0017] Additionally, the following may be commonly applied:
[0018] As an example of the present disclosure, a list of PDU sessions to be activated may include PDU sessions to be activated in a third access of a second type of switching, and the AMF may perform deactivation of remaining second PDU sessions among at least one second PDU session except for the second PDU sessions included in the list of PDU sessions to be activated.
[0019] In addition, as an example of the present disclosure, the AMF may determine a second PDU session requiring session switching among at least one second PDU session, and the second PDU session requiring session switching may be maintained in an activated state.
[0020] In addition, as an example of the present disclosure, the registration request message may include an indicator indicating access switching.
[0021] In addition, as an example of the present disclosure, the first type may be a 3GPP access type, and the second type may be a non-3GPP access type.
[0022] In addition, as an example of the present disclosure, when performing an AN release process for a second access having a second type, the AMF may receive a terminal context release completion message including at least one second PDU session information for a second access having a second type, and may send a session management (SM) context update request for the PDU session to a session management function (SMF) based on the terminal context release completion message.
[0023] In addition, as an example of the present disclosure, an SM context update request for a PDU session may include a PDU session ID and PDU session deactivation information corresponding to at least one second PDU session associated with a second access of a second type, and the SMF may perform PDU session deactivation based on the PDU session ID.
[0024] In addition, as an example of the present disclosure, when access switching is performed, the SMF can store the user location information of the terminal based on the switched second type of third access.
[0025] In addition, as an example of the present disclosure, when the SM context update request for the PDU session includes user location information of the terminal based on the second access before the second type of handover, the SMF may not perform PDU session deactivation.
[0026] In addition, as an example of the present disclosure, the SM context update request for the PDU session may include an indicator indicating whether to perform access switching, and the SMF may not perform PDU session deactivation based on the indicator of whether to perform access switching.
[0027] Beneficial Effects
[0028] The present disclosure can provide a method for enabling a terminal to perform communication through 3GPP access and non-3GPP access based on an MA PDU in a wireless communication system.
[0029] The present disclosure can provide an operation method when performing access switching for non-3GPP access in a situation where a terminal performs communication based on an MA PDU in a wireless communication system.
[0030] The present disclosure can provide a method for enabling the AMF to maintain a PDU session for a new non-3GPP access based on access switching in a wireless communication system.
[0031] The present disclosure relates to a method that enables an SMF to determine whether to perform session deactivation based on information received from an AMF.
[0032] The effects obtained in the present disclosure are not limited to the effects mentioned above, and from the following description of the embodiments of the present disclosure, those skilled in the art who apply the technical configuration of the present disclosure can clearly derive and understand other effects not mentioned above. That is, those skilled in the art can also derive from the embodiments of the present disclosure the effects that were not expected when implementing the configuration described in the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] The accompanying drawings are provided to help understand the present disclosure, and embodiments of the present disclosure may be provided together with the detailed description. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. The reference numerals in each drawing may refer to structural elements.
[0034] Figure 1 is a diagram showing an example of a communication system applicable to the present disclosure.
[0035] Figure 2 is a view showing an example of a UE to which an embodiment of the present disclosure is applied.
[0036] Figure 3 is a view showing an example of functional separation of a general NG-RAN and a fifth generation core (5GC).
[0037] Figure 4 is a view showing an example of a general architecture of a fifth generation (5G) system.
[0038] Figure 5 is a view showing a terminal logout process applicable to the present disclosure.
[0039] Figure 6 is a view showing a method of performing an AN release process applicable to the present disclosure.
[0040] Figure 7 is a view showing a method of receiving a list of PDU sessions to be activated applicable to the present disclosure.
[0041] Figure 8 is a flow chart illustrating an AMF operation method applicable to the present disclosure.
[0042] Fig. 9 is a flow chart illustrating a terminal operation method applicable to the present disclosure.
[0043] Fig.10 is a flow chart illustrating a method of operating an SMF applicable to the present disclosure. DETAILED DESCRIPTION
[0044] The following embodiments are achieved by combining the structural elements and features of the present disclosure in a predetermined manner. Unless specified separately, each structural element or feature should be selectively considered. Each structural element or feature can be performed without being combined with other structural elements or features. In addition, some structural elements and / or features can be combined with each other to form embodiments of the present disclosure. The order of the operations described in the embodiments of the present disclosure can be changed. Some structural elements or features of an embodiment may be included in another embodiment, or may be replaced by corresponding structural elements or features of another embodiment.
[0045] In the description of the drawings, processes or steps that render the scope of the present disclosure unnecessarily ambiguous will be omitted, and processes or steps that can be understood by those skilled in the art will be omitted.
[0046] Throughout the specification, when a part "comprises" or "includes" a component, this indicates that other components are not excluded, but may be further included, unless otherwise specified. The terms "unit", "-or / er" and "module" described in this specification indicate a unit for processing at least one function or operation, which can be implemented by hardware, software and a combination thereof. In addition, "a" or "an", "one", "the" and similar related words can be used to include both singular and plural expressions, unless the context of describing this specification (especially in the context of the following claims) indicates a difference from this specification or is obviously contradictory to the context.
[0047] In this specification, the embodiments of the present disclosure are described focusing on the relationship between data reception and transmission between a base station and a mobile station. Here, a base station means a terminal node of a network that performs direct communication with a mobile station. In this document, a specific operation described as being performed by a base station may be performed by an upper node of the base station in some cases.
[0048] That is, in a network composed of a plurality of network nodes including a base station, various operations for communicating with a mobile station may be performed by a base station or a network node other than a base station. Here, "base station" may be replaced by terms such as "fixed station", "Node (Node) B", "eNode B (eNB)", "gNode B (gNB)", "ng-eNB", "advanced base station (ABS)" or "access point".
[0049] In addition, in an embodiment of the present disclosure, “terminal” may be replaced with terms such as “user terminal equipment (UE)”, “mobile station (MS)”, “subscriber station (SS)”, “mobile subscriber station (MSS)”, “mobile terminal” or “advanced mobile station (AMS)”.
[0050] In addition, the transmitting end refers to a fixed and / or mobile node that provides data services or voice services, and the receiving end means a fixed and / or mobile node that receives data services or voice services. Therefore, in the case of an uplink, the mobile station can be the transmitting end, and the base station can be the receiving end. Similarly, in the case of a downlink, the mobile station can be the receiving end, and the base station can be the transmitting end.
[0051] The embodiments of the present disclosure may be supported by standard documents disclosed in at least one of the following radio access systems: IEEE 802xx system, 3rd Generation Partnership Project (3GPP) system, 3GPP Long Term Evolution (LTE) system, 3GPP Fifth Generation (5G) New Radio (NR) system, and 3GPP2 system, and specifically, the embodiments of the present disclosure may be supported by the following documents: 3GPP TS (Technical Specification) 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.321, and 3GPP TS 38.331.
[0052] In addition, the embodiments of the present disclosure are applicable to other radio access systems, but are not limited to the above-mentioned systems. As an example, they are applicable to systems applied after the 3GPP 5G NR system, and are not limited to a specific system.
[0053] That is to say, obvious steps and parts not described in the embodiments of the present disclosure can be described with reference to the above documents. In addition, all terms disclosed in this document can be interpreted by standard documents.
[0054] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Figure 1 The detailed description disclosed above is intended to describe example embodiments of the present disclosure, and is not intended to illustrate any only embodiment of the technical configuration capable of implementing the present disclosure.
[0055] In addition, specific terms used in the embodiments of the present disclosure are provided to help understanding of the present disclosure, and these specific terms can be used in any other modified forms without departing from the technical idea of the present disclosure.
[0056] The following technology can be applied to various radio access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc.
[0057] For the purpose of explanation, the following description is based on a 3GPP communication system (e.g., LTE, NR, etc.), but the technical idea of the present disclosure is not limited thereto. LTE may refer to technology after 3GPP TS 36.xxx version 8. Specifically, LTE technology after 3GPP TS 36.xxx version 10 may be referred to as LTE-A, and technology after 3GPP TS 36.xxx version 13 may be referred to as pre-LTE-A. 3GPP NR may refer to technology after TS 38.xxx version 15. 3GPP 6G may refer to technology after TS version 17 and / or version 18. "xxx" means the specific number of a standard document. LTE / NR / 6G may be collectively referred to as a 3GPP system.
[0058] Contents described in standard documents issued earlier than the present disclosure may be referenced for background technology, terminology and abbreviations used in the present disclosure. As an example, 36.xxx and 38.xxx standard documents may be referenced.
[0059] For terms, abbreviations, and other backgrounds that may be used in this document, reference may be made to the following standard document descriptions published prior to this document. Specifically, terms, abbreviations, and other background technologies related to LTE / EPS (Evolved Packet System) may refer to the 36.xxx series, 23.xxx series, and 24.xxx series, and NR (New Radio) / 5GS related terms and abbreviations and other backgrounds may refer to the 38.xxx series, 23.xxx series, and 24.xxx series.
[0060] Hereinafter, the present disclosure is described based on the terms defined above.
[0061] The three main demand areas of 5G include (1) enhanced mobile broadband (eMBB), (2) massive machine type communications (mMTC), and (3) ultra-reliable low latency communications (URLLC).
[0062] Some use cases may require multiple areas to be optimized, and others may focus on just one key performance indicator (KPI). 5G supports these different use cases in a flexible and reliable way.
[0063] Communication system applicable to the present disclosure
[0064] Although not limited thereto, the various descriptions, functions, processes, proposals, methods and / or operational flowcharts of the present disclosure disclosed herein may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.
[0065] In the following, a more detailed description will be given with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise mentioned, the same reference numerals may illustrate the same or corresponding hardware blocks, software blocks or functional blocks.
[0066] Figure 1 An example communication system suitable for use with the present disclosure is illustrated.
[0067] refer to Figure 1 , the communication system applied to the present disclosure includes a wireless device, a base station, and a network. Here, the wireless device refers to a device for performing communication using a wireless connection technology (e.g., 5G NR, LTE), and may be referred to as a communication / wireless / 5G device. Without being limited thereto, the wireless device may include a robot 100a, a vehicle 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 100g. For example, a vehicle may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, a vehicle capable of performing vehicle-to-vehicle communication, and the like. Here, the vehicles 100b-1 and 100b-2 may include an unmanned aerial vehicle (UAV)) (e.g., a drone). The XR device 100c may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head-up display (HUD) installed in a vehicle, a TV, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like. The handheld device 100d may include a smart phone, a smart tablet, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance 100e may include a TV, a refrigerator, a washing machine, etc. The IoT device 100f may include a sensor, a smart meter, etc. For example, the base station 120 and the network 130 may be implemented as wireless devices, and a specific wireless device 120a may operate as a base station / network node for another wireless device.
[0068] The wireless devices 100a to 100f may be connected to the network 130 through the base station 120. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 100g through the network 130. The network 130 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f may communicate with each other through the base station 120 / network 130, but perform direct communication (e.g., sidelink communication) that does not pass through the base station 120 / network 130. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). In addition, the IoT device 100f (e.g., a sensor) may perform direct communication with another IoT device (e.g., a sensor) or other wireless devices 100a to 100f.
[0069] Wireless communication / connection 150a, 150b, and 150c may be established between wireless devices 100a to 100f / base station 120 and base station 120 / base station 120. Here, wireless communication / connection, such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), and base station to base station communication 150c (e.g., relay, integrated access backhaul (IAB)), may be established through various wireless connection technologies (e.g., 5G NR). The wireless device and the base station / wireless device, and the base station and the wireless device may send / receive radio signals through wireless communication / connection 150a, 150b, and 150c. For example, wireless communication / connection 150a, 150b, and 150c may send / receive signals through various physical channels. To this end, based on various proposals of the present disclosure, various configuration information setting processes for transmission / reception of radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and at least a portion of the resource allocation process may be performed.
[0070] Figure 2 is a view showing an example of a UE to which an embodiment of the present disclosure is applied.
[0071] refer to Figure 2 UE 200 may include a processor 202 , a memory 204 , a transceiver 206 , one or more antennas 208 , a power management module 241 , a battery 242 , a display 243 , a keyboard 244 , a subscriber identity module (SIM) card 245 , a speaker 246 , and a microphone 247 .
[0072] The processor 202 may be configured to implement the description, functions, processes, proposals, methods and / or operational flow charts disclosed in this specification. The processor 202 may be configured to control one or more different components of the UE 200 to implement the description, functions, processes, proposals, methods and / or operational flow charts disclosed in this specification. The layers of the wireless interface protocol may be embodied in the processor 202. The processor 202 may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor 202 may be an application processor. The processor 202 may include at least one of a DSP, a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator).
[0073] The memory 204 may be operably coupled to the processor 202 and store various information for operating the processor 202. The memory 204 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage devices. In the case of software implementation, the technology described herein may be implemented using a module (e.g., process, function, etc.) that executes the description, function, process, proposal, method and / or operation flow chart disclosed in this specification. The module may be stored in the memory 204 and executed by the processor 202. The memory 204 may be implemented in the processor 202 or outside the processor 202, in which case the memory 204 may be communicatively coupled to the processor 202 by various methods known in the art.
[0074] The transceiver 206 can be operably coupled to the processor 202 and send and / or receive radio signals. The transceiver 206 can include a transmitter and a receiver. The transceiver 206 can include a baseband circuit for processing radio frequency signals. The transceiver 206 can send and / or receive radio signals by controlling one or more antennas 208.
[0075] The power management module 241 may manage the power of the processor 202 and / or the transceiver 206. The battery 242 may supply power to the power management module 241.
[0076] The display 243 may output a result processed by the processor 202. The keyboard 244 may receive an input to be used in the processor 202. The keyboard 244 may be displayed on the display 243.
[0077] SIM card 245 is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and related keys, and can be used to identify and authenticate a user in a handheld telephone device such as a mobile phone or computer. In addition, contact information can be stored in many SIM cards.
[0078] The speaker 246 may output sound-related results processed in the processor 202. The microphone 247 may receive sound-related input to be used in the processor 202.
[0079] In an embodiment of the present specification, a UE may operate as a transmitting device in an uplink and as a receiving device in a downlink. In an embodiment of the present specification, a base station may operate as a receiving device in an UL and as a transmitting device in a DL. In the present specification, a base station may be referred to as a Node B (Node B), an eNode B (eNB), and a gNB, and may not be limited to a specific form.
[0080] In addition, as an example, the UE may be embodied in various forms according to the usage examples / services. The UE may be configured by various components, devices / components and / or modules. For example, each UE may include a communication device, a control device, a storage device and additional components. The communication device may be a communication circuit and a transceiver. For example, the communication circuit may include one or more processors and / or one or more memories. For example, the transceiver may include one or more transceivers and / or one or more antennas. The control device may be electrically coupled to the communication device, the storage device and the additional components, and control the overall operation of each UE. For example, the control device may control the electrical / mechanical operation of each UE based on the program / code / instruction / information stored in the storage device. The control device may send the information stored in the storage device to the outside (e.g., another communication device) via the communication device through a wireless / wired interface, or store the information received from the outside (e.g., another communication device) through the wireless / wired interface in the storage device.
[0081] The additional components may be configured in various ways depending on the type of UE. For example, the additional components may include at least one of a power supply device / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a drive device, and a computing device. In addition, without limitation, the UE may be configured in a variety of ways. Figure 1 The robot 100a, Figure 1 The vehicles 100b-1 and 100b-2, Figure 1 XR device 100c, Figure 1 Handheld device 100d, Figure 1 Home appliances 100e, Figure 1 IoT devices 100f, digital broadcast terminals, hologram devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environmental devices, Figure 1 AI server / device 100g, Figure 1 The UE may be used in a mobile or fixed location depending on the use case / service.
[0082] The various components, devices / components and / or all modules of the UE may be interconnected via a wired interface, or at least a portion thereof may be wirelessly connected via a communication device. In addition, each component, device / component and / or module of the UE may further include one or more components. For example, the control device may be configured by a collection of one or more processors. As an example, the control device may be configured by a collection of a communication control processor, an application processor (AP), an electronic control unit (ECU), a GPU, and a memory control processor. As another example, the storage device may be configured by RAM, dynamic RAM (DRAM), ROM, flash memory, volatile memory, non-volatile memory, and / or a combination thereof.
[0083] 5G system architecture to which the present disclosure is applicable
[0084] The 5G system is an advanced technology derived from the 4G LTE mobile communication technology, and supports new radio access technologies (RATs), extended long term evolution (eLTE) as an extension technology of LTE, non-3GPP access (e.g., wireless local area network (WLAN) access), etc. through the evolution of the existing mobile communication network structure or net state structure.
[0085] The 5G system is defined based on services, and the interactions between network functions (NFs) in the 5G system architecture can be represented in the following two ways.
[0086] Reference point representation: Indicates the interaction between NF services in NFs described by a point-to-point reference point (e.g., N11) between two NFs (e.g., AMF and SMF).
[0087] Service-based representation: A network function (e.g. AMF) within the control plane (CP) allows other authenticated network functions to access its services. This representation also includes point-to-point reference points if necessary.
[0088] 5GC (5G Core) can include various components, Figure 6 Some of the various components are shown, including Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Prose User Plane Function (UPF), Application Function (AF), Unified Data Management (UDM) and Non-3GPP Interworking Function (N3IWF).
[0089] The UE is connected to the data network via the UPF via the Next Generation Radio Access Network (NG-RAN) including the gNB. The UE can even be provided with data services through untrusted non-3GPP access, such as a wireless local area network (WLAN). In order to connect the non-3GPP access to the core network, the N3IWF can be deployed.
[0090] N3IWF performs the function of managing the interworking between non-3GPP access and 5G system. When the UE is connected to non-3GPP access (e.g., WiFi called IEEE 801.11), the UE can connect to the 5G system through N3IWF. N3IWF performs control signaling with AMF and connects to UPF through N3 interface for data transmission.
[0091] AMF can manage access and mobility in the 5G system. AMF can perform the function of managing (non-access layer) NAS security. AMF can perform the function of handling mobility in idle state.
[0092] The UPF performs the function of sending and receiving user data by the gateway. The UPF node 440 may perform all or part of the user plane functions of the serving gateway (S-GW) and the packet data network gateway (P-GW) of 4G mobile communication.
[0093] The UPF is a component that operates as a boundary point between the Next Generation Radio Access Network (NG-RAN) and the core network and maintains the data path between the gNB and the SMF. In addition, the UPF acts as a mobility anchor when the UE moves over the area served by the gNB. The UPF can perform the function of processing PDUs. For mobility within the NG-RAN (which is defined after 3GPP Release 15), the UPF can route packets. In addition, the UPF can also utilize 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) as a mobility anchor. The UPF may correspond to the termination point of the data interface toward the data network.
[0094] PCF is a node that controls the operator's policies. AF is a server for providing various services to UE. UDM is a server that manages subscriber information, such as the Home Subscriber Server (HSS) of 4G mobile communication. UDM stores subscriber information in a unified data repository (UDR) and manages the subscriber information.
[0095] The SMF can perform the function of allocating the Internet Protocol (IP) address of the UE. In addition, the SMF can control the packet data unit (PDU) session.
[0096] For ease of explanation, in the following, the figure marks may be omitted for AMF, SMF, PCF, UPF, AF, UDM, N3IWF, gNB or UE, which may operate with reference to the contents described in the standard documents released earlier than this document.
[0097] Figure 3 : is a diagram showing an example of expressing a structure of a wireless communication system applied to the present disclosure from a node perspective.
[0098] refer to Figure 3 , UE is connected to the data network (DN) through the next generation RAN. The control plane function (CPF) node performs all or part of the functions of the mobility management entity (MME) of 4G mobile communication and all or part of the serving gateway (S-GW) and PDN gateway (P-GW) functions. CPF nodes include AMF and SMF.
[0099] The UPF node performs the function of a gateway for sending and receiving user data.
[0100] The Authentication Server Function (AUSF) authenticates and manages the UE. The Network Slice Selection Function NSSF is the node of the network slice described below.
[0101] The Network Open Function (NEF) provides a mechanism to securely open services and functions of the 5G core.
[0102] Figure 3 The reference points in are described as follows. N1 represents the reference point between UE and AMF. N2 represents the reference point between (R)AN and AMF. N3 represents the reference point between (R)AN and UPF. N4 represents the reference point between SMF and UPF. N5 represents the reference point between PCF and AF. N6 represents the reference point between UPF and DN. N7 represents the reference point between SMF and PCF. N8 represents the reference point between UDM and AMF. N9 represents the reference point between UPFs. N10 represents the reference point between UDM and SMF. N11 represents the reference point between AMF and SMF. N12 represents the reference point between AMF and AUSF. N13 represents the reference point between UDM and AUSF. N14 represents the reference point between AMFs. N15 represents the reference point between PCF and AMF in non-roaming scenario and between AMF and PCF of visited network in roaming scenario. N16 represents the reference point between SMFs. N22 represents the reference point between AMF and NSSF. N30 represents the reference point between PCF and NEF. N33 may denote a reference point between AF and NEF, and the above-mentioned entities and interfaces may be configured with reference to contents described in a standard document released earlier than this document.
[0103] The radio interface protocol is based on the 3GPP radio access network standard. The radio interface protocol is horizontally divided into a physical layer, a data link layer, and a network layer, and vertically divided into a user plane for transmission of data information and a control plane (signaling) for transmission of control signals.
[0104] The protocol layer may be divided into L1 (layer 1), L2 (layer 2), and L3 (layer 3) based on three lower layers of an open system interconnection (OSI) reference model widely known in communication systems.
[0105] Hereinafter, the present disclosure describes each layer of the radio protocol. Figure 4 is a view showing an example of the structure of a radio interface protocol between a UE and a gBN.
[0106] refer to Figure 4 , the access stratum (AS) layer may include a physical (PHY) layer, a medium access control layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a radio resource control (RRC) layer, and may refer to the contents described in a standard document released earlier than the current document to perform operations based on each layer.
[0107] For example, the terminal can perform communication through a 3GPP access path and a non-3GPP access path based on the ATSS (Access Service Steering, Switching and Splitting) function. If the terminal supports a non-3GPP access path, the terminal can perform communication by establishing a PDU session based on the 3GPP access path and the non-3GPP access path. Here, the ATSS function can support a MA PDU (Multiple Access PDU) session consisting of one 3GPP access path and one non-3GPP access path. That is, the terminal can perform communication through a PDU session configured based on a 3GPP access path and a PDU session configured based on a non-3GPP access path. Specifically, the terminal can send some data through a PDU session configured based on a 3GPP access path, and send some other data through a PDU session configured based on a non-3GPP access path. As another example, if a problem occurs in the PDU session while the terminal sends data through a PDU session configured based on a 3GPP access path, data transmission can be performed through a PDU session configured based on a non-3GPP access path, and is not limited to a specific form. That is, the terminal can perform communication through the MAPDU sessions established via multiple paths, and through this, policy-based multi-access traffic distribution and new high-speed data services can be realized.
[0108] Here, QUIC (Quick UDP Internet Connection)-based steering can be considered for the ATSS function. QUIC can implement a steering function to distribute non-TCP services to multiple paths. Through this, the efficiency of services sent through multiple paths can be increased, and the quality of service (QoS) can be improved. In addition, as an example, a redundant steering mode can be considered based on ATSS. The redundant steering mode can be a mode for enabling or disabling packet transmission redundancy based on performance measurements and thresholds at the transmitter (UE or UPF). That is, the terminal can determine whether to redundantly send the same packet through different paths based on the redundant steering mode.
[0109] As another example, when the terminal is in an idle state and outside the local area network (LADN) service area, the terminal needs to maintain data exchange via non-3GPP access. With respect to the above description, ATSS support may be required when the terminal receives services from the LADN. Here, as an example, ATSS may only support service distribution between a 3GPP access path and one non-3GPP access path, but situations where service distribution support for other access paths is required may be considered. As an example, when two non-3GPP accesses are provided, service distribution support for different access paths based on different PLMNs (such as an NTN access path and a TN access path) and for different paths (such as a path using LTE / EPC and a path using NR / 5GC) may be required.
[0110] Based on the above description, a method for improving ATSS functionality may be needed. For example, steering, switching, and segmentation operations for non-TCP service flows (e.g., UDP service flows and IP service flows) may be performed based on a new steering function. In addition, segmentation of packets may be supported, or new steering functions may be supported through a Datagram Congestion Control Protocol (DCCP) protocol and multipath extensions based thereon, but are not limited to a specific form. As another example, more types of access paths may be supported in an MA PDU session. As a specific example, MA PDU session service switching may be enabled between two non-3GPP access paths within the same PLMN.
[0111] For example, the terminal can perform MA PDU session data service switching between a non-3GPP access path to N3IWF within the PLMN and another non-3GPP access path from TNGF (TNF Gateway Function). TNGF can provide functions for handling connections to 3GPP external networks as an entity in the 5G network that performs gateway functions for connecting to external networks. Here, TNGF can perform functions similar to N3IWF, but N3IWF can be an interface for transmitting non-3GPP data from outside the 5G network to 5GC, and TNGF can be an interface for controlling data flows between 5GC and external networks, but is not limited to a specific form.
[0112] For example, a method may be needed to switch data services to another non-3GPP access path after the terminal registers with the 5G core network. As another example, a method may be needed to enable a terminal to switch data services of an MA PDU session between a non-3GPP access path based on N3IWF and a non-3GPP access path based on TNGF within a PLMN.
[0113] For example, multiple non-3GPP access paths may pass through the same PLMN. Here, one non-3GPP access path may be based on N3IWF, and another non-3GPP access path may be based on TNGF as described above. The terminal may perform a service path switch from a source non-3GPP access path to a target non-3GPP access path within the same PLMN.
[0114] As described above, non-3GPP access switching can be performed based on the ATSS function. For example, based on non-3GPP access switching, the old non-3GPP access can be switched to the new non-3GPP access. Based on the above description, the PDU session based on the old non-3GPP access path can be switched to the new non-3GPP access PDU session.
[0115] Here, if the old non-3GPP access is switched to the new non-3GPP access based on the non-3GPP access switching, the AMF may trigger the AN (Access Network) release process through the old non-3GPP access to deactivate the existing connection. However, if the AMF performs a deactivation process on the non-3GPP access based on the old AN release process, the PDU session established in the old non-3GPP access and switched to the new non-3GPP access may be deactivated. More specifically, if the AMF performs the AN release process, the AMF may transmit an AN release command to the base station. The base station may send the PDU session list information included in the base station to the AMF while sending the AN release completion message. Here, although the PDU session established in the old non-3GPP access is switched to the new non-3GPP access, the base station may transmit the PDU session list information including information about the PDU session established in the old non-3GPP access to the AMF while sending the AN release completion message. The AMF may transmit the PDU session list information to the SMF based on the AN release received from the base station, and the PDU session included in the PDU session list may be released by the SMF. That is, the session switched to the new non-3GPP access can be deactivated through the AN release process. In the above situation, because the new PDU session establishment process for the new non-3GPP access is performed again, it may be inefficient, and a method of preventing the PDU session established in the old non-3GPP access from being released may be required. This will be described below.
[0116] For example, when the terminal establishes an MA PDU session, the terminal may create a PDU session based on a 3GPP access path and a PDU session based on a non-3GPP access path, and thereafter, the terminal may perform a switch to a non-3GPP access. Here, as an example, even if the terminal only creates a PDU session for a non-3GPP access path, the same may apply, and is not limited to a specific embodiment.
[0117] As a specific example, after establishing a PDU session for an untrusted non-3GPP access, an access handover from the untrusted non-3GPP access to the trusted non-3GPP access may be performed. Here, when performing the access handover for the non-3GPP access, a release operation (e.g., logout or AN release) for resources used in the old non-3GPP access may be performed. However, if the above process is performed without change, a problem may arise in which the PDU session switched from the old non-3GPP access to the new non-3GPP access is released together with the above resource release process.
[0118] For example, when performing a deregistration procedure as an operation to release resources in an old non-3GPP access, the AMF may perform a release operation on all PDU sessions associated with the access type while performing the deregistration procedure. Here, the AMF may also release a PDU session that has been switched from an old non-3GPP access to a new non-3GPP access, and a method to prevent this from happening may be required, which will be described below.
[0119] Figure 5 2 is a diagram illustrating a terminal logout process applicable to the present disclosure. Figure 5 , the AMF 530 may receive a deregistration request message. The AMF 530 may obtain information about a list of PDU sessions to be released based on the deregistration request message, and the AMF 530 may send a request message for releasing the SM context of the PDU session to the SMF 550 based on the information about the list of PDU sessions. The SMF 550 may send an N4 session release request message for the corresponding PDU session to the UPF 560, receive a response, and then transmit an SM context release response message to the AMF 530. When the AMF 530 sends an SM context release request message for the PDU session to the SMF 550 based on the list of PDU sessions, all PDU sessions for the target access set in the terminal may be released. When the above-mentioned non-3GPP access handover is performed, the AMF 530 may release all PDU sessions for the old non-3GPP access as the target access. Here, the following problem may occur: even the PDU session switched to the PDU session for the new non-3GPP access among the PDU sessions for the old non-3GPP access is released.
[0120] As another example, Figure 6 2 is a diagram showing a method for performing an AN release process applicable to the present disclosure. Figure 6 , (R)AN 620 may send an N2 UE context release request to AMF 630, and AMF 630 may release the PDU session for the corresponding terminal. Here, AMF 630 may send an N2 UE context release command to (R)AN 620, and (R)AN 620 may release radio resources and terminate the connection with the terminal 610. Thereafter, AMF 630 may receive an N2 UE context release complete from (R)AN 620. Here, the N2 UE context release complete may include information about a list of PDU sessions to be released. Based on the above description, AMF 630 may release radio resources related to the terminal 610 and release the related terminal context. Thereafter, AMF 630 may send an SM context update request (e.g., Nsmf_PDUSession_UpdateSMContext request) for the PDU session to SMF 550 for session update. Here, the request may include at least one of a PDU session ID, a PDU session deactivation, a reason, an operation type, a user location information, an age of the location information, or N2 SM information (secondary RAT usage). For example, if the N2 UE context release request sent by the (R)AN 620 to the AMF 630 includes a PDU session list and an active N3 user plane, then the N2 UE context release request may be sent to the AMF 630 in the execution Figure 6 Step 2 is performed after steps 5 to 7 in the above. In addition, as an example, the operation type may be set to "UP deactivation", which indicates that the user plane resources of the PDU session are deactivated.
[0121] Based on the above description, SMF 650 may perform deactivation of the PDU session for the old non-3GPP access, which may cause service interruption. Therefore, the PDU session switched from the old non-3GPP access to the new non-3GPP access may also be released, and unnecessary additional procedures may be required as a process for reactivating the corresponding PDU session. In the following, taking the above points into consideration, a method for preventing the PDU session of the new non-3GPP access from being deactivated during the access switching process will be described.
[0122] As described above, a method may be needed to prevent a newly accessed session from being deactivated during an access switching process. As an example, the following description is based on non-3GPP access, but may not be limited to this. As an example, a similar method may be applied when access switching is performed for 3GPP access. In addition, the following description is based on a case where access switching is performed according to an MA PDU session. More specifically, there may be a case where an MA PDU session exists as a PDU session based on 3GPP access and a PDU session based on non-3GPP access. However, the present disclosure may not be limited to this, and may be equally applicable to access switching of a general PDU session, and is not limited to a specific embodiment.
[0123] As a specific example, the case where the old non-3GPP access is deregistered based on the deregistration process can be considered. Here, according to the above deregistration process, the PDU session that has been switched to the new non-3GPP access can also be released. In order to prevent the release of the PDU session that has been switched to the new non-3GPP access, the AMF can store the associated RAT type for each PDU session.
[0124] For example, the associated RAT type may be stored for all PDU sessions. In other words, the associated RAT type may be stored for each PDU session.
[0125] As another example, the associated RAT type may be stored only when the PDU session is a non-3GPP access or user plane resources are established for an MA PDU session via a non-3GPP access. That is, the associated RAT type may not be stored in a PDU session for a 3GPP access, while the associated RAT type may be stored in a PDU session for a non-3GPP access. As an example, the AMF may identify whether the PDU session is a PDU session for a new non-3GPP access based on the associated RAT type.
[0126] As a specific example, the AMF may perform a PDU session release only for the PDU session for the old non-3GPP access by checking the associated RAT type of the PDU session, and not release the PDU session for the new non-3GPP access. Here, when switching from the old non-3GPP access to the new non-3GPP access, the associated RAT type information of the PDU session switched to the new non-3GPP access may be updated. For example, when the AMF receives a message requesting an MA PDU session from the terminal via an uplink NAS message (e.g., UL NAS transmission), the AMF may update the associated RAT type information via the user location information delivered by the (R)AN that sent the message. As described above, the associated RAT type information of each PDU session may be updated, and the AMF may not release the PDU session for the new non-3GPP access based on the associated RAT type information of the PDU session.
[0127] As another example, the case where the old non-3GPP access is released based on the AN release procedure can be considered. For example, when access handover is performed, the AN release procedure for the old non-3GPP access can be performed. Here, according to the above AN procedure, the PDU session for which access handover to the new non-3GPP access has been performed can also be deactivated. Therefore, the AMF needs to prevent user plane deactivation from occurring for the PDU session for the new non-3GPP access for which access handover has been performed.
[0128] For example, the AMF may not perform user plane deactivation for all PDU sessions delivered by the (R)AN, but may request the SMF to deactivate the user plane for other PDU sessions except for the PDU session for which access switching has occurred. Specifically, even for old PDU sessions, if access switching has occurred, the AMF may not perform user plane deactivation for all PDU sessions delivered by the (R)AN. In other words, the AMF may request the SMF to deactivate the user plane except for the PDU session for which access switching has occurred.
[0129] Here, the AMF can obtain a list of PDU sessions to be activated in advance and use the list to store the PDU sessions for which access switching has been requested.
[0130] Figure 7 is a view showing a method of receiving a list of PDU sessions to be activated applicable to the present disclosure. Figure 7 , the terminal 710 can establish an MA PDU session based on the 3GPP access and non-3GPP access as described above. In the process of establishing the MA PDU session, information on whether non-3GPP access switching is supported can be included in the PDU session establishment request message. In addition, the AMF 750 can also notify the SMF 760 of information on whether non-3GPP access switching is supported. Based on the information on whether each of the terminal 710, the AMF 750 and the SMF 760 supports non-3GPP access switching, the SMF 760 can indicate whether non-3GPP access switching is supported by including it in the PDU session establishment permission message.
[0131] For example, when the terminal 710 switches from an untrusted non-3GPP access to a trusted non-3GPP access and sends a registration request to the trusted non-3GPP access, the registration request message may include registration type information indicating access switching. In addition, the registration request message may include a list of PDU sessions to be activated. Here, the list of PDU sessions may be information indicating a PDU session to be activated among the PDU sessions established in the old non-3GPP access.
[0132] Thereafter, the AMF 750 may perform a registration procedure for the new non-3GPP access, and during this procedure, may perform an AN release procedure for the old non-3GPP access. Here, as an example, the AMF 750 may store a list of PDU sessions to be activated, which list is obtained based on the above description. As an example, based on the above Figure 6 , AMF 750 may obtain the PDU session information of the old non-3GPP access from the (R)AN during the AN release process. That is, AMF 750 may obtain the PDU session ID information of the old non-3GPP access. Here, AMF 750 may perform user plane deactivation only on PDU sessions other than the PDU sessions in the list of PDU sessions to be activated among the transmitted PDU session IDs.
[0133] As another example, if the AMF determines that a PDU session requires PDU session switching, the AMF may request deactivation of the user plane except for that PDU session, thereby deactivating the remaining PDU sessions.
[0134] That is, after completing the UP connection in the new non-3GPP access, the AMF can trigger the AN release process for the old non-3GPP access (ie, the old N3IWF or TNGF). Here, for the PDU session not included in the list of PDU sessions to be activated transmitted by the terminal and indicated by the list of PDU session IDs with active N3 user planes, the AMF can request the SMF to deactivate the PDU session. For other PDU sessions, the AMF may not request to deactivate the PDU session.
[0135] As another example, after performing access switching, the session of the old non-3GPP access may be released based on the AN release process. Here, the AMF may not manage information about the PDU session for which user plane deactivation is to be performed. That is, the AMF may send a user plane deactivation request to the SMF to perform user plane deactivation on all PDU sessions transmitted by the (R)AN. However, even if the SMF receives a user plane deactivation request from the AMF, the SMF may not perform the corresponding operation.
[0136] As a specific example, AMF may transmit the old non-3GPP access information together with the user location information to SMF while performing the AN release process. SMF may determine whether AMF requests user plane deactivation for the old non-3GPP access based on the received information. That is, SMF may determine whether AMF requests user plane deactivation for the old non-3GPP access or requests user plane deactivation for the new non-3GPP access. As an example, after performing access switching, SMF may receive a user plane resource deactivation request and user location information for the old non-3GPP access. Here, SMF may store the user location information of the terminal together with the new non-3GPP access, and compare the received information with the corresponding information. That is, when SMF receives the user plane resource deactivation request and the user location information for the old non-3GPP access, SMF may send a response based on the AMF request, but may not perform the actual user plane resource deactivation. Therefore, in the AN release process, SMF may receive an AMF request, but may not perform a session change operation because the request is based on the old non-3PP access. In addition, because the user location information received by the SMF is the old non-3GPP access user location information, the SMF may not update the user location information.
[0137] As another example, when the AMF performs an AN release procedure after performing access switching, the AMF may send an SM context request (e.g., Nsmf_PDUSession_UpdateSMContext request) to the SMF based on a PDU session update. Here, the AMF may send an indication added to the request. As a specific example, in addition to the information included in the AN release procedure, the AMF may further include an indicator indicating that an AN release procedure is performed based on access switching. Here, an SMF that supports access switching may identify the indicator and may not perform PDU session deactivation during the AN release procedure. That is, the SMF may not perform the above-mentioned session change procedure. On the other hand, an SMF that does not support the indicator may perform PDU session deactivation. Based on the above description, when a terminal performs access switching based on an MA PDU session between different non-3GPP accesses, PDU session resources may be released or the session may be prevented from being released.
[0138] Figure 8 is a flow chart illustrating an AMF operation method applicable to the present disclosure.
[0139] refer to Figure 8, the AMF may perform registration for a first access having a first type and a second access having a second type (S810). For example, the first type may be a 3GPP access type, and the second type may be a non-3GPP access type. Then, the AMF may establish an MA PDU session based on at least one first PDU session for the first access having the first access and at least one second PDU session for the second access having the second type (S820). That is, a PDU session based on 3GPP access and a PDU session based on non-3GPP access may be established. Then, access switching may be performed in non-3GPP access. The AMF may receive a registration request message from the terminal based on access switching (S830). Here, the registration request message may include information about a list of PDU sessions to be activated. In addition, the registration request message may indicate access switching based on the type used for the registration request message. Alternatively, the registration request message may include a separate indicator requesting access switching. Thereafter, registration of a third access having a second type through non-3GPP access and an AN release process of a second access having a second type may be performed (S840). In which, the AMF can perform deactivation of at least one second PDU session through the AN release process based on the information about the list of PDU sessions to be activated.
[0140] Specifically, the list of PDU sessions to be activated may include the PDU sessions to be activated in the switched third access having the second type. That is, the list of PDU sessions to be activated may be information about the PDU sessions to be activated in the new non-3GPP access. The AMF may store information about the list of PDU sessions to be activated, and deactivate the remaining second PDU sessions except the second PDU session included in the information about the PDU session to be activated during the AN release process. As another example, the AMF may directly determine the second PDU session that requires session switching among at least one second PDU session, and keep the second PDU session that requires session switching in an activated state.
[0141] Fig. 9 is a flow chart illustrating a terminal operation method applicable to the present disclosure.
[0142] refer to Fig. 9, the terminal may perform registration for a first access of a first type and a second access of a second type (S910). For example, the first type may be a 3GPP access type, and the second type may be a non-3GPP access type. Then, an MA PDU session may be established based on at least one first PDU session for the first access of the first type and at least one second PDU session for the second access of the second type (S930). That is, a PDU session based on 3GPP access and a PDU session based on non-3GPP access may be established. Then, access switching may be performed in non-3GPP access. The terminal may send a registration request message to the AMF based on access switching (S930). Here, the registration request message may include information about a list of PDU sessions to be activated. In addition, the registration request message may indicate access switching using a type for the registration request message. Alternatively, the registration request message may include a separate indicator requesting access switching. Thereafter, registration for a third access of the second type through non-3GPP access and an AN release procedure for a second access of the second type may be performed (S940). Here, the AMF may perform deactivation of at least one second PDU session through the AN release process based on the information of the list of PDU sessions to be activated. Specifically, the list of PDU sessions to be activated may include PDU sessions to be activated in the switched third access of the second type. That is, the list of PDU sessions to be activated may be information about the PDU sessions to be activated in the new non-3GPP access. The AMF may store information about the list of PDU sessions to be activated, and perform deactivation of the remaining second PDU sessions except the second PDU session included in the information about the list of PDU sessions to be activated during the AN release process. As another example, the AMF may directly determine the second PDU session that requires session switching among at least one second PDU session, and may keep the second PDU session that requires session switching in an activated state.
[0143] Fig.10 is a flow chart illustrating an SMF operation method applicable to the present disclosure. Fig.10, the SMF may receive an SM context update request for the PDU session from the AMF (S1010). Here, the AMF may receive a terminal context release completion message including PDU session list information from the base station, and send an SM context update request for the PDU session to the SMF based on the terminal context release completion message. For example, the SM context update request for the PDU session may include at least one of the PDU session ID, PDU session deactivation, cause, operation type, user location information, age of location information, or N2 SM information (secondary RAT usage). In addition, when switching to a new non-3GPP access based on access switching, the SMF may store user location information for the new non-3GPP access. For example, if the SMF receives user location information after access switching, and the user location information is user location information for access after access switching (S1020), the SMF may deactivate the PDU session based on the PDU session deactivation request received from the AMF (S1030). On the other hand, if the SMF receives the user location information after the access switching, and the user location information is the user location information used for access before the access switching, the SMF may ignore the request from the AMF and maintain the PDU session (S1040). In addition, as described above, the SMF may not update the user location information as described above.
[0144] Since the examples of the above-mentioned proposed methods can also be included in one of the implementation methods of the present disclosure, it is an obvious fact that they can be regarded as a proposed method. In addition, the above-mentioned proposed methods can be implemented individually or in combination (or merge) of some of them. A rule can be defined so that information about whether to apply the proposed method (or information about the rule of the proposed method) is notified from the base station to the terminal through a predefined signal (e.g., a physical layer signal or an upper layer signal).
[0145] Without departing from the technical ideas and basic features described in the present disclosure, the present disclosure can be embodied in other specific forms. Therefore, the above detailed description should not be interpreted as limiting in all aspects, but should be regarded as exemplary. The scope of the present disclosure should be determined by a reasonable interpretation of the attached claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure. In addition, claims that do not have a clear reference relationship in the claims may be combined to form an embodiment, or may be included as a new claim through modification after submission.
[0146] Industrial availability
[0147] Embodiments of the present disclosure are applicable to various radio access systems. Examples of various radio access systems include the 3rd Generation Partnership Project (3GPP) or 3GPP2 system.
[0148] The embodiments of the present disclosure are applicable not only to various radio access systems but also to all technical fields to which various radio access systems are applied. In addition, the proposed method is applicable to millimeter wave and terahertz wave communication systems using ultra-high frequency bands.
[0149] Additionally, embodiments of the present disclosure are applicable to a variety of applications, such as autonomous vehicles, drones, and the like.
Claims
1. A method of operating an access management function (AMF) in a wireless communication system, the method comprising: performing registration for a first access having a first type and a second access having a second type, and establishing a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type; receiving a registration request message from the terminal based on the access handover, the registration request message including information about a list of PDU sessions to be activated; as well as performing registration on a third access of the second type based on the access switching, and performing an access network (AN) release procedure on the second access of the second type after performing the switching to activation of the PDU session of the third access of the second type, Wherein, the AMF performs deactivation of the at least one second PDU session through the AN release process based on the information about the list of PDU sessions to be activated.
2. The method according to claim 1, in, The list of PDU sessions to be activated includes PDU sessions to be activated in the switched third access of the second type, and The AMF performs deactivation of the remaining second PDU sessions among the at least one second PDU session except the second PDU session included in the list of PDU sessions to be activated.
3. The method according to claim 2, wherein: The AMF determines a second PDU session requiring session switching among the at least one second PDU session, and keeps the second PDU session requiring the session switching in an activated state.
4. The method according to claim 1, wherein: The registration request message includes an indicator indicating the access switching.
5. The method according to claim 1, wherein: The first type is a 3GPP access type, and the second type is a non-3GPP access type.
6. The method according to claim 1, in, based on performing the AN release procedure for the second access of the second type, the AMF receiving a terminal context release complete message, the terminal context release complete message including information related to the at least one second PDU session for the second access of the second type, and Wherein, a session management (SM) context update request for the PDU session is sent to a session management function (SMF) based on the terminal context release completion message.
7. The method according to claim 6, in, the SM context update request for the PDU session comprises a PDU session ID and PDU session deactivation information corresponding to the at least one second PDU session associated with the second access of the second type, and The SMF performs PDU session deactivation based on the PDU session ID.
8. The method according to claim 7, wherein: When performing the access switching, the SMF stores the user location information of the terminal based on the switched third access having the second type.
9. The method according to claim 8, wherein: When the SM context update request for the PDU session includes the user location information of the terminal based on the second access of the second type before the access switching, the SMF does not perform the PDU session deactivation.
10. The method according to claim 7, in, The SM context update request for the PDU session includes an indicator indicating whether to perform access switching, and The SMF does not perform the PDU session deactivation based on an indicator indicating whether to perform the access switching.
11. An access management function (AMF) operating in a wireless communication system, the AMF comprising: at least one transceiver; at least one processor; as well as at least one memory operably connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform specific operations, Among them, the specific operation: performing registration for a first access having a first type and a second access having a second type; establishing a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type; controlling the at least one transceiver to receive a registration request message from a terminal based on access switching, the registration request message including information on a list of PDU sessions to be activated; and performing registration of a third access of the second type based on the access switching, and performing an access network (AN) release procedure for the second access of the second type, Wherein, the AMF performs deactivation of the at least one second PDU session through the AN release process based on the information about the list of PDU sessions to be activated.
12. A method for operating a terminal in a wireless communication system, the method comprising: performing registration for a first access having a first type and a second access having a second type, and establishing a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type; Sending a registration request message to an access management function (AMF) based on access switching, the registration request message including information about a list of PDU sessions to be activated; as well as performing registration on a third access of the second type based on the access switching, and performing an access network (AN) release procedure on the second access of the second type after performing activation of a PDU session to be switched to the third access of the second type, Wherein, the AMF performs deactivation of the at least one second PDU session through the AN release process based on the information about the list of PDU sessions to be activated.
13. A terminal operating in a wireless communication system, the terminal comprising: at least one transceiver; at least one processor; as well as at least one memory operably connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform specific operations, Among them, the specific operation: performing registration for a first access having a first type and a second access having a second type; establishing a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type; controlling the at least one transceiver to send a registration request message to an access management function (AMF) based on access switching, the registration request message including information on a list of PDU sessions to be activated; and performing registration on a third access of the second type based on the access switching, and performing an access network (AN) release procedure on the second access of the second type after performing activation of a PDU session to be switched to the third access of the second type, Wherein, the AMF performs deactivation of the at least one second PDU session through the AN release process based on the information about the list of PDU sessions to be activated.
14. A device comprising at least one memory and at least one processor, the at least one processor being functionally connected to the at least one memory, wherein: The at least one processor controls the device: performing registration for a first access having a first type and a second access having a second type; establishing a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type; receiving a registration request message from the terminal based on the access handover, the registration request message including information about a list of PDU sessions to be activated; as well as performing registration on a third access of the second type based on the access switching, performing activation of a PDU session switched to the third access of the second type, and performing an access network (AN) release procedure on the second access of the second type, Wherein, the AMF performs deactivation of the at least one second PDU session through the AN release process based on the information about the list of PDU sessions to be activated.
15. A non-transitory computer-readable medium storing at least one instruction, the non-transitory computer-readable recording medium including the at least one instruction executable by a processor, in, The at least one instruction controls the device to: performing registration for a first access having a first type and a second access having a second type; establishing a multi-access (MA) PDU session based on at least one first protocol data unit (PDU) session for the first access having the first type and at least one second PDU session for the second access having the second type; receiving a registration request message from the terminal based on the access handover, the registration request message including information about a list of PDU sessions to be activated; as well as performing registration on a third access of the second type based on the access switching, performing activation of a PDU session switched to the third access of the second type, and performing an access network (AN) release procedure on the second access of the second type, Wherein, the AMF performs deactivation of the at least one second PDU session through the AN release process based on the information about the list of PDU sessions to be activated.
