Method and apparatus for processing application function request

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method for a session management function (SMF) supporting edge relocation in a wireless communication system is disclosed. The method can include the steps of: the SMF receiving, from a policy control function (PCF), an SM policy including a simultaneous connection request to a source protocol data unit (PDU) session anchor (PSA) and a target PSA during edge relocation; the SMF determining whether simultaneous connection to the source PSA and the target PSA during edge relocation is impossible; and based on the determination, the SMF transmitting, to an application function (AF), a notification that the SM policy cannot be applied.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for processing external application function requests in mobile communication systems. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, thus enabling high transmission rates and new services. It can be implemented not only in the "sub-6GHz" band, such as 3.5GHz, but also in the "above 6GHz" band, including 28GHz and 39GHz, known as millimeter waves. Furthermore, the implementation of 6G mobile communication technology (referred to as "super 5G systems") in terahertz (THz) bands (e.g., the 95GHz to 3THz band) is being considered to achieve transmission rates 50 times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] In the early stages of 5G mobile communication technology development, standardization work is underway to support and meet performance requirements for services associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). This includes: beamforming and massive MIMO for reducing radio-wave path loss and increasing radio-wave transmission distance in millimeter waves; parameter sets supporting efficient use of millimeter wave resources and dynamic operation of time slot formats (e.g., operating multi-subcarrier spacing); initial access technologies to support multi-beam transmission and broadband; defining and operating the BWP (broadband portion); new channel coding methods such as LDPC (low-density parity-check) codes for large data transmissions and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing for providing dedicated networks specifically for particular services.

[0004] Currently, considering the services that 5G mobile communication technology needs to support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standards for related technologies have been defined, such as: V2X (vehicle-to-everything) for autonomous vehicles to assist driving decisions based on vehicle location and status information transmitted by the vehicle and for improving user convenience; NR-U (New Radio Unlicensed) designed to ensure that the system operates in unlicensed frequency bands in compliance with various regulatory requirements; NR UE power saving; non-terrestrial networks (NTN) for UE-satellite direct communication to provide coverage in areas where terrestrial network communication is unavailable; and positioning.

[0005] Furthermore, standardization of air interface architecture / protocols is underway, with related technologies including: the Industrial Internet of Things (IIoT) supporting new services through interconnection and integration with other industries; IAB (Integrated Access and Backhaul) providing nodes for network service area expansion by supporting wireless backhaul links and access connections in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover; and two-step random access (2-step RACH for NR) to simplify random access procedures. Standardization of system architecture / services is also progressing, concerning: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for joint Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] With 5G mobile communication systems already commercially available, the number of devices connecting to communication networks is increasing exponentially. Therefore, it is foreseeable that enhanced functionality and performance of 5G mobile communication systems, as well as centralized operation of connected devices, will be necessary. To this end, new research is planned on: Extended Reality (XR) for effectively supporting technologies such as AR (Augmented Reality), VR (Virtual Reality), and MR (Mixed Reality); enhancing 5G performance and reducing complexity through the utilization of Artificial Intelligence (AI) and Machine Learning (ML); AI service support; metaverse service support; and drone communication.

[0007] Furthermore, the aforementioned evolution of 5G mobile communication systems will serve as the foundation for developing the following technologies: not only new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, such as multi-antenna transmission technologies for full-dimensional MIMO (FD-MIMO) / array antennas and massive MIMO antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies utilizing OAM (orbital angular momentum), and RIS (reconfigurable smart surfaces), but also full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technologies for providing services with complexity levels exceeding the UE's operational capabilities by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] [Technical Issues]

[0009] In wireless communication systems, Application Functions (AFs) can determine whether an AF request operation has been successfully executed based on whether the request information in the core network has been successfully stored in the Unified Data Store (UDR). AF requests are generated as policies and submitted to network functions, but information about whether the network functions have performed operations based on the AF request is not provided to the AF. For example, information included in an AF traffic impact request is submitted to the Session Management Function (SMF) as a session management policy, but information about whether session management was performed based on this request information is not provided to the AF. Furthermore, AF request information not approved by the Policy Control Function (PCF) or determined by the SMF not to be applied may be unnecessarily stored in the UDR.

[0010] This disclosure provides a method and apparatus for processing requests for AF (Automatic Request), which affect strategies related to a terminal receiving services through a wireless communication system.

[0011] This disclosure proposes a method and apparatus for providing information to the AF (Automatic AF) regarding whether an AF request related to a terminal service has been set as policy information affecting network functions and applied to enable the network to operate as intended.

[0012] This disclosure provides a method and apparatus for managing application data generated in a UDR due to an AF request.

[0013] [Technical Solution]

[0014] In a method for a Session Management Function (SMF) supporting edge relocation in a wireless communication system according to an embodiment of the present disclosure, the method includes: receiving an SM policy from a Policy Control Function (PCF) by the SMF, the SM policy including a request for simultaneously connecting to a source Protocol Data Unit (PDU) Session Anchor Point (PSA) and a target PSA during edge relocation; determining by the SMF whether simultaneous connection to the source PSA and the target PSA is unavailable during edge relocation; and based on the determination, sending a notification to an Application Function (AF) that the SM policy is inapplicable.

[0015] According to one embodiment of this disclosure, a Session Management Function (SMF) apparatus for supporting edge relocation in a wireless communication system includes: a transceiver; and a processor that controls the transceiver, wherein the processor is configured to: receive an SM policy from a Policy Control Function (PCF), the SM policy including a request for simultaneous connection to a source Protocol Data Unit (PDU) Session Anchor (PSA) and a target PSA during edge relocation, determine whether simultaneous connection to the source PSA and the target PSA is unavailable during edge relocation, and based on the determination, send a notification to an Application Function (AF) that the SM policy is inapplicable.

[0016] According to one embodiment of this disclosure, a method performed by a network entity in a wireless communication system may include: receiving a request message for traffic impact from a second network entity; storing information included in the request message in a third network entity and sending a response message to the request message to the second network entity; and receiving a result notification message for the request message from a fourth network entity and sending the result notification message to the second network entity.

[0017] According to one embodiment of this disclosure, a network entity of a wireless communication system may include a transceiver and a processor for controlling the transceiver. The processor may be configured to: receive a request message for traffic impact from a second network entity; store information included in the request message in a third network entity and send a response message to the request message to the second network entity; and receive a result notification message for the request message from a fourth network entity and send the result notification message to the second network entity. Attached Figure Description

[0018] Figure 1 This is a block diagram illustrating an example configuration of a wireless communication system according to an embodiment of the present disclosure.

[0019] Figure 2 This is a view illustrating a method for providing an AF request to the AF, according to one embodiment of the present disclosure, to determine whether the AF request has been applied.

[0020] Figure 3 This is a view illustrating a method for removing AF request-related information from a UDR according to an embodiment of this disclosure.

[0021] Figure 4 This is a block diagram illustrating the configuration of a UE according to an embodiment of the present disclosure.

[0022] Figure 5 This is a block diagram illustrating the configuration of a network entity according to an embodiment of the present disclosure. Detailed Implementation

[0023] The working principle of this disclosure is described below with reference to the accompanying drawings.

[0024] In describing the working principle of this disclosure, descriptions of techniques known in the art and not directly related to the invention are omitted. This is done to further clarify the spirit of the disclosure without creating ambiguity.

[0025] For the same reason, some components may be exaggerated or shown schematically. The dimensions of each component may not reflect its true dimensions. All figures use the same reference numerals to refer to the same components throughout.

[0026] The advantages and features of this disclosure, as well as the methods for implementing it, will be understood through the embodiments described below in conjunction with the accompanying drawings. However, this disclosure is not limited to the embodiments disclosed herein, and various modifications can be made thereto. The embodiments disclosed herein are only intended to inform those skilled in the art of the scope of protection of this disclosure. This disclosure is defined solely by the appended claims.

[0027] It should be understood that the blocks in each flowchart, and combinations of blocks in the flowcharts, can be executed by computer program instructions. Since these computer program instructions can be located in the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, the instructions, executed by the processor of the computer or other programmable data processing device, generate means for performing the functions described in conjunction with the blocks of each flowchart. Since these computer program instructions can be stored in a computer-usable or computer-readable storage medium capable of implementing functions in a specified manner for a computer or other programmable data processing device, the instructions stored in such a computer-usable or computer-readable storage medium can generate an product comprising instruction means for performing the functions described in conjunction with the blocks of each flowchart.

[0028] Furthermore, each box may represent a module, segment, or a code portion containing one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in the boxes may occur in different orders. For example, two consecutively shown boxes may be executed simultaneously or in reverse order depending on the nature of their corresponding functions.

[0029] As used herein, the term "unit" refers to a software element or a hardware element such as a field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), etc. A unit performs a specific function. However, a "unit" is not limited to software or hardware. A "unit" may be configured in an addressable storage medium or configured to execute one or more processors. Thus, according to this disclosure, a "unit" may include elements such as software elements, object-oriented software elements, class elements, task elements, processes, functions, attributes, programs, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data schemas, tables, arrays, and variables. The functionality provided within a component and a "unit" may be combined into a smaller number of components and units, or further split into additional components and "units." Furthermore, the components and "units" may be implemented to run one or more CPUs in a device or secure multimedia card. According to embodiments of this disclosure, a "...unit" may include one or more processors.

[0030] The terms described below are defined in consideration of the functions described in this disclosure. Since such terms may vary according to the intentions or habits of users or operators, their definitions should be determined based on the full text of this disclosure.

[0031] The terms used in this disclosure to refer to network entities, messages, and identification information are merely illustrative examples for ease of description. Therefore, this disclosure is not limited to the above terms, and the above terms can be replaced with other terms that refer to objects with equivalent technical meanings.

[0032] In the following text, for convenience, this disclosure uses the terms and names defined in the 3GPP 5G System Specification, but is not limited by such terms and names and can be equally applied to systems that conform to other specifications.

[0033] The terms "terminal" or "device" as used in this disclosure may refer to a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, user unit, user station (SS), wireless device, wireless communication device, wireless transceiver unit (WTRU), mobile node, mobile, or other terms. Various embodiments of a terminal include cellular phones and smartphones with wireless communication capabilities, personal digital assistants (PDAs) and wireless modems with wireless communication capabilities, portable computers with wireless communication capabilities, capture / record / photograph / videography devices with wireless communication capabilities, such as digital cameras, game players with wireless communication capabilities, home devices for music storage and playback with wireless communication capabilities, internet-connected home devices capable of wireless internet access and browsing, or portable units or terminals combining these capabilities. Furthermore, a terminal may include, but is not limited to, machine-to-machine (M2M) terminals and machine-type communication (MTC) terminals / devices. In this disclosure, a terminal may be referred to as an electronic device or simply a device.

[0034] Figure 1 This is a block diagram illustrating an exemplary configuration of a wireless communication system according to one embodiment of the present disclosure. In the illustrated embodiment, the wireless communication system may include a 5G mobile communication network.

[0035] Reference Figure 1The 5G mobile communication network can be configured with a 5G UE 110, a radio access network (RAN) 120 (e.g., at least one of a base station, gNB (5G Node B), and eNB (Evolved Node B),) and a 5G core network. The 5G core network may include various network functions (NFs). For example, the 5G core network may include at least one of the following functions: Access and Mobility Management Function (AMF) 150, Session Management Function (SMF) 160, Policy Control Function (PCF) 180, Application Function (AF) 130, Unified Data Management (UDM) 191, User Plane Function (UPF) 170 responsible for delivering data to the Data Network (DN) 171, Network Openness Function (NEF) 193, Unified Data Storage (UDR) 192, and Edge Application Server Discovery Function (EASDF).

[0036] Each NF supports the following functions.

[0037] -AMF 150 provides access and mobility management functions on a per-UE basis, and in principle, one UE can connect to one AMF.

[0038] -DN 171 refers to, for example, operator services, internet access, or third-party services. DN 171 can send downlink protocol data units (PDUs) to UPF 170, or receive PDUs sent by UE 110 from UPF 170.

[0039] PCF 180 provides the functionality to receive packet flow information from the application server and to determine policies for mobility management, session management, etc. Specifically, PCF 180 supports the following functions: support for a unified policy framework for managing network operations; provision of policy rules that enable control plane functions (such as AMF 150, SMF 160, etc.) to execute the policy rules; and a front-end implementation for accessing relevant subscription information for policy determination in the Unified Data Store (UDR) 192.

[0040] -SMF 160 provides session management functionality, and when UE 110 has multiple sessions, each session can be managed by a different SMF.

[0041] -UDM 191 can store user subscription data, policy data, etc.

[0042] -UPF 170 can deliver downlink PDUs received from DN 171 to UE 110 via (R)AN 120, and can deliver uplink PDUs received from UE 110 via (R)AN 120 to DN 171.

[0043] -AF 130 can interact with the 3GPP core network for service provisioning (e.g., supporting functions such as application impact on traffic routing, network open function access, and interaction with policy frameworks for policy control).

[0044] - NEF 193 can provide AF 130 or other network functions with access to and use of services provided by the core network. For example, AF 130 can send policy control requests to PCF 180 or UDR 192 through NEF 193.

[0045] Figure 2 This is a view illustrating a method for providing an AF request to the AF regarding whether it has been applied, according to one embodiment of this disclosure.

[0046] Reference Figure 2 In operation 201, AF 130 can generate an AF request message. PCF 180 can subscribe in advance to UDR 192 to receive notification messages when new AF request-related information is created or changed. For example, PCF 180 can subscribe to the following information.

[0047] (Dataset = Application data; Data subset = AF traffic impact request information; Data key = S-NSSAI and / or DNN and / or internal group identifier or SUPI)

[0048] In operation 202, AF 130 may send a traffic impact request message (Nnef_Trafficinfluence_Create / Update / Delete) to NEF 193. This traffic impact request message may include at least one of the following information.

[0049] - Internet Protocol (IP) address of UE 110

[0050] - Identifier for UE 110

[0051] - Traffic description (a combination of deep neural network (DNN) and optional single network slice selection auxiliary information (S-NSSAI), application identifier, or traffic filtering information)

[0052] - AF Service Identifier

[0053] - List of Data Network Application Identifiers (DNAIs)

[0054] - AF transaction identifier

[0055] - UE IP address reservation indication

[0056] - AF subscription corresponds to SMF event-related information.

[0057] - Information for Edge Application Server (EAS) IP replacement in 5GC

[0058] - User plane latency requirements

[0059] - Indication of simultaneous connection via source and destination PDU session anchors (PSA) during edge relocation

[0060] Furthermore, in operation 202, AF 130 may send an indicator to NEF 193 regarding the AF request and / or the required impact result notification, along with the notification target address. This indicator can be used to request notification regarding whether the AF request has been actually applied to network functions. AF 130 may also, for the same purpose, send the event ID for the AF request / impact result notification to NEF 193 in the AF subscription to the corresponding SMF event by including the event ID in the AF request message. Furthermore, AF 130 may utilize various parameters to request core network functions to notify whether each request has been applied.

[0061] In operations 203 and 204, NEF 193 may store the information received from AF 130 in operation 202 in UDR 192 and send a response message to AF 130. NEF 193 may also store the information received from AF 130 as application data in UDR 192. NEF 193 may also store in UDR 192 an indication of the impact result notification requested / required by AF, the notification target address, or the event ID used for the AF request / impact result notification, along with the information received from AF 130.

[0062] In operation 205, PCF 180 may be notified of AF request-related information by UDR 192. When the indication, notification target address, or event ID used for AF request / required impact result notification is stored as application data, UDR 192 may provide PCF 180 with an implicit subscription to SM policy creation / authorization result information, including the indication, notification target address, or event ID used for AF request / required impact result notification and notification target address.

[0063] In operation 206, PCF 180 can generate and authorize SM policies using information received from UDR 192. PCF 180 can send the generated SM policies to SMF 160, the SM policies including implicit subscriptions to the SM policy establishment results and notification target addresses. This can be used to notify AF 130 of whether the SM policies generated and submitted by PCF 180 have been successfully applied to the user plane by SMF 160.

[0064] When PCF 180 fails to generate an SM policy based on the information received from UDR 192 in operation 205, if the information received from UDR 192 includes an indication of an impact result notification for the AF request / required, and PCF 180 has received an implicit subscription to the SM policy creation / authorization result, then in operation 207, PCF 180 can notify AF 130 of the result regarding whether the SM policy was applied via NEF 193. For example, when generating an SM policy based on an AF request including an indication of simultaneous connection via the source PSA and target PSA during edge relocation, if it is determined based on subscription data, etc., that the UE's Session and Service Continuity Mode (SSC Mode) 3 is not supported, or that operations related to session offloading are impossible to perform, then the SM policy used to support simultaneous connection via the source PSA and target PSA during edge relocation may not be generated. In this case, PCF 180 can send an AF impact result notification to AF 130, which includes information indicating that the SM policy is inapplicable or its application failed.

[0065] In operation 208, SMF 160 may receive an SM policy generated according to an AF request from PCF 180 and perform user plane path configuration, such as traffic route reconfiguration, based on the SM policy.

[0066] When SMF 160 identifies that the SM policy is inapplicable in operation 208, in operation 209, SMF 160 may notify PCF 180 and AF 130 of this situation. SMF 130 may send an AF impact result notification to AF 130, which includes information indicating that the SM policy is inapplicable or its application has failed. For example, when SMF 160 receives an SM policy from PCF 180 including a request to support simultaneous connection via source and target PSA during edge relocation and performs UP path configuration, but a new UPF is selected due to reasons such as UE location movement, supporting simultaneous connection via source and target PSA during edge relocation may not be possible. In this case, SMF 160 may notify PCF 180 and AF 130 of the inapplicability information related to the SM policy.

[0067] Figure 3 This is a schematic diagram illustrating a method for removing AF request-related information from a UDR according to one embodiment of the present disclosure.

[0068] Reference Figure 3 In operation 301, AF 130 can generate an AF request message. PCF 180 can subscribe in advance to the UDR to receive notification messages when new AF request-related information is created or changed. For example, PCF 180 can subscribe to the following information.

[0069] (Dataset = Application data; Data subset = AF traffic impact request information; Data key = S-NSSAI and / or DNN and / or internal group identifier or SUPI)

[0070] In operation 302, AF 130 may send a traffic impact request message to NEF 193. The traffic impact request message may include at least one of the following information.

[0071] - Internet Protocol (IP) address of UE 110

[0072] - Identifier for UE 110

[0073] - Traffic description (a combination of deep neural network (DNN) and optional single network slice selection auxiliary information (S-NSSAI), application identifier, or traffic filtering information)

[0074] - AF Service Identifier

[0075] - List of Data Network Application Identifiers (DNAIs)

[0076] - AF transaction identifier

[0077] - UE IP address reservation indication

[0078] - AF subscription corresponds to SMF event-related information.

[0079] - Information for Edge Application Server (EAS) IP replacement in 5GC

[0080] - User plane latency requirements

[0081] - Indication of simultaneous connection via source and destination PDU session anchors (PSA) during edge relocation

[0082] Furthermore, in operation 302, AF 130 can send an indicator to NEF 193 for a notification of AF request obsolescence. This indicator can be used to receive a notification when generated application data or SM policy-related information generated due to an AF request becomes invalid (obsolescent application data) because it was not applied to network functions. AF 130 can also send an event ID for AF request / application data obsolescence to NEF 193 in the AF subscription to the corresponding SMF event by including the event ID in the AF request message for the same purpose. Furthermore, AF 130 can utilize various parameters to request the core network function to notify the result of whether each request was applied.

[0083] In operations 303 and 304, NEF 193 may store the information received from AF 130 in operation 302 in UDR 192 and send a response message to AF 130. NEF 193 may also store the information received from AF 130 as application data in UDR 192. NEF 193 may also store in UDR 192 an indication of the impact result notification requested / required by AF, the notification target address, or the event ID used for the AF request / impact result notification, along with the information received from AF 130.

[0084] In operation 305, PCF 180 may be notified of AF request-related information by UDR 192. When the indication, notification target address, or event ID used for AF request / required impact result notification is stored as application data, UDR 192 may provide PCF 180 with an implicit subscription to SM policy creation / authorization result information, including the indication, notification target address, or event ID used for AF request / required impact result notification and notification target address.

[0085] In operation 306, PCF 180 can generate and authorize SM policies using information received from UDR 192. PCF 180 can send the generated SM policy to SMF 160. The generated SM policy includes an implicit subscription to the SM policy establishment result and a notification target address. This can be used to notify UDR 192 or NEF 193 when an SM policy generated and submitted by PCF 180 has been successfully applied to the user plane by SMF 160, but the SM policy is no longer applicable and it is determined that the SM policy will not be applied in the future.

[0086] When the SM policy generated by PCF 180 based on the information received from UDR 192 in operation 305 is no longer valid, in operation 307, PCF 180 may send an application data discard request or application data discard notification message to UDR 192.

[0087] When UDR 192 receives an application data obsolescence request or application data obsolescence notification message from PCF 180, in operation 308, UDR 192 may delete or obsolescence the application data information and send notification messages to network function entities (e.g., PCF 180, SMF 160, etc.) that have subscribed to services that are notified when application data changes.

[0088] In operation 309, PCF 180 can send an application data obsolescence notification to AF 130 via NEF 193.

[0089] In operation 310a, when AF 130 receives a notification, such as an application data obsolescence notification, from PCF 180 via NEF 193 regarding a previously sent AF request, AF 130 may send a message to NEF 193 requesting the deletion of the AF request-related information requested by AF 130; and in operation 310b, NEF 193 may send a deletion request message for the information requested by AF 130 to UDR 192 based on the request from AF 130.

[0090] Independent of operations 307 to 309, in operation 311, SMF 160 may send a scrapping request or scrapping notification message to PCF 180. For example, when traffic routing has been configured by applying the SM policy received from PCF 180 in operations 307 to 309, but the SM policy becomes invalid due to changes in the UE's subscription data or UE movement causing the UE to enter a traffic routing unavailable area, SMF 160 may send a scrapping request or scrapping notification message for the received SM policy to PCF 180.

[0091] When PCF 180 receives a scrapping request or scrapping notification message for an SM policy from SMF 160, in operation 312, PCF 180 may specify the application data used to generate the SM policy and send a scrapping request or scrapping notification message to UDR 192. After UDR 192 removes or scraps the application data, in operation 313, UDR 192 may send an AF request scrapping notification message to AF 130 for the occurrence of the event. The AF request scrapping notification message sent to AF 130 in operation 313 can be sent via NEF 193.

[0092] Figure 4 A block diagram illustrating the configuration of a UE according to an embodiment of the present disclosure.

[0093] Reference Figure 4 The UE (e.g.) Figure 1 The UE (110) may include at least one of the processor 401, transceiver 403, and memory 405. The UE is not limited to the form of including only the components shown; the UE may include more or fewer components than the components shown.

[0094] According to one embodiment of this disclosure, transceiver 403 can send / receive signals to / from at least one network entity (e.g., RAN 120, AMF 150, and / or at least one other UE). Signals sent and received between the network entity and the UE may include at least one of control information or data. Transceiver 403 can receive signals via a wireless channel and deliver the signals to processor 601, and can also transmit signals received from processor 401 via a wireless channel.

[0095] According to one embodiment of this disclosure, the processor 401 can control the operation of the UE to perform tasks related to... Figure 2 and Figure 3 The implementation method includes at least one corresponding operation.

[0096] Of course, the processor 401, transceiver 403, and memory 405 do not necessarily have to be implemented as separate modules, and can be implemented as a single module, for example, on a single chip. The processor 401 and transceiver 403 may be electrically connected. The processor 401 may include an application processor (AP) and / or a communication processor (CP).

[0097] According to one embodiment of this disclosure, memory 405 may store data such as basic programs, application programs, and setting information for UE operation. Memory 405 may provide the stored data upon request from processor 401. Memory 405 may be configured with storage media or combinations of storage media, such as read-only memory (ROM), random access memory (RAM), hard disk, read-only optical disc memory (CD-ROM), and digital multifunction optical disc (DVD). Memory 405 may include multiple memories. Processor 401 may execute at least one operation corresponding to an embodiment of this disclosure based on a program stored in memory 405 for performing at least one operation corresponding to an embodiment of this disclosure.

[0098] Figure 5 A block diagram illustrating the configuration of a network entity according to an embodiment of the present disclosure.

[0099] Reference Figure 5 The network entity (e.g., at least one of UPF / EASDF 170, SMF 160, PCF 180, RAN 120, AMF 150, UDR 192, NRF 193, or AF 130) may include at least one of processor 501, transceiver 503 including a transmitter and / or receiver, and memory 505. The network entity is not limited to including only the components shown; it may include a greater number of components than those shown, or a smaller number of components.

[0100] According to one embodiment of this disclosure, transceiver 503 can transmit / receive signals to / from at least one other network entity (e.g., at least one of UPF / EASDF 170, SMF 160, PCF 180, RAN 120, AMF 150, UDR 192, NRF 193, AF 130) and / or at least one UE (e.g., UE 110). Signals transmitted and received between the at least one other network entity and / or the at least one UE may include at least one of control information or data. When the network entity is a base station (e.g., RAN 120), transceiver 503 may include a transceiver for transmitting / receiving radio signals to / from the UE (e.g., UE 110), and a transceiver or communication interface for transmitting / receiving signals to / from another network entity in the core network.

[0101] According to one embodiment of this disclosure, the processor 501 can control the network entity to perform operations related to... Figures 2 to 3 At least one operation corresponding to the implementation method. Of course, the processor 501, transceiver 503, and memory 505 do not necessarily have to be implemented as separate modules, and can be implemented as a single module, for example, on a single chip. The processor 501 and transceiver 503 may be electrically connected. The processor 501 may include an access point (AP) and / or a contention point (CP).

[0102] According to one embodiment of this disclosure, memory 505 may store data such as basic programs, application programs, and setting information for the operation of network entities. Memory 505 may provide the stored data upon request from processor 501. Memory 505 may be configured with storage media or combinations of storage media, such as ROM, RAM, hard disk, CD-ROM, and DVD. Memory 505 may include multiple memories. Processor 501 may execute at least one operation corresponding to an embodiment of this disclosure based on a program stored in memory 505 for performing at least one operation corresponding to an embodiment of this disclosure.

[0103] It should be noted that, Figures 1 to 5 The system configuration diagrams, method example diagrams, and device configuration diagrams shown are not intended to limit the scope of this disclosure. In other words, Figures 1 to 5 All configurations or operations shown should not be construed as essential components for implementing the present invention, and the present invention can be implemented using only some components without departing from the spirit of the invention.

[0104] The methods corresponding to the embodiments described in this disclosure or claims can be implemented in hardware, software, or a combination of hardware and software.

[0105] When implemented in software, a computer-readable storage medium may be provided storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors within an electronic device. The one or more programs include instructions that enable the electronic device to perform methods corresponding to the embodiments described in this disclosure or the claims.

[0106] The program (software module or software) may be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc ROM, digital versatile optical disc (DVD), or other types of optical storage devices, or magnetic tape. Alternatively, the program may be stored in a memory composed of all or some of the above storage media. Multiple copies of each of the above storage media may be configured.

[0107] The program can be stored in an attachable storage device accessible via a communication network, such as the Internet, intranet, local area network (LAN), wide area network (WLAN), storage area network (SAN), or a combination thereof. The storage device can be connected to a device executing embodiments of this disclosure via an external port. A separate storage device on the communication network can be connected to the device executing embodiments of this disclosure.

[0108] In the above specific embodiments, the components included in this disclosure are described in a singular or plural form according to the proposed specific embodiments. However, the singular or plural form is chosen according to the described context for ease of description, and this disclosure is not limited to a single or multiple components. Unless the context clearly indicates otherwise, as used herein, the singular forms “a,” “an,” and “the” are also intended to include their plural forms.

[0109] Although specific embodiments of this disclosure have been described above, various modifications can be made thereto without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the above embodiments, but should be defined by the following claims and their equivalents.

Claims

1. A method for supporting Session Management Function (SMF) edge relocation in a wireless communication system, the method comprising: The SMF receives an SM policy from the Policy Control Function (PCF), the SM policy including a request to simultaneously connect to the source Protocol Data Unit (PDU) session anchor point (PSA) and the target PSA during edge relocation. The SMF determines whether simultaneous connection to both the source PSA and the target PSA is unavailable during edge relocation; as well as Based on the determination, the SMF sends a notification to the application function AF that the SM policy is not applicable.

2. The method according to claim 1, further comprising: The SMF performs user plane path configuration on the user plane function UPF based on the SM strategy.

3. The method according to claim 2, wherein the user plane path configuration includes traffic routing reconfiguration.

4. A Session Management Function (SMF) device supporting edge relocation in a wireless communication system, the device comprising: transceiver; as well as A processor that controls the transceiver, wherein the processor is configured to: The policy control function (PCF) receives an SM policy, which includes a request to simultaneously connect to both the source Protocol Data Unit (PDU) session anchor point (PSA) and the target PSA during edge relocation. Determine whether simultaneous connection to both the source PSA and the target PSA is unavailable during edge relocation, and Based on the determination, a notification is sent to the application function AF that the SM policy is not applicable.

5. The apparatus of claim 4, wherein the processor is further configured to: perform user plane path configuration for the user plane function UPF based on the SM policy.

6. The apparatus of claim 5, wherein the user plane path configuration includes traffic routing reconfiguration.

7. A method for operating a first network entity in a wireless communication system, the method comprising: Receive a request message from the second network entity for traffic impact; The information included in the request message is stored in a third network entity, and a response message for the request message is sent to the second network entity. as well as The system receives a result notification message for the request message from the fourth network entity and sends the result notification message to the second network entity.

8. The method of claim 7, wherein the information included in the request message includes an indicator requesting notification of the results of the traffic impact, and wherein, The result notification message includes information regarding whether the policy generated based on information stored in the third network entity has been applied.

9. The method of claim 8, wherein the information included in the request message further includes target address information for the result notification of the traffic impact.

10. The method of claim 7, wherein the information included in the request message includes an indicator requesting notification of the abandonment of the traffic impact, and wherein, The result notification message includes information related to the obsolescence of information stored in the third network entity.

11. The method according to claim 7, wherein the first network entity is a Network Open Function (NEF), the second network entity is an Application Function (AF), the third network entity is a Unified Data Storage (UDR), and the fourth network entity is a Policy Control Function (PCF).

12. A first network entity in a wireless communication system, the first network entity comprising: transceiver; as well as A processor that controls the transceiver, wherein the processor is configured to: Receive a request message from the second network entity for traffic impact; The information included in the request message is stored in a third network entity, and a response message for the request message is sent to the second network entity. as well as The system receives a result notification message for the request message from the fourth network entity and sends the result notification message to the second network entity.

13. The first network entity of claim 12, wherein the information included in the request message includes an indicator requesting notification of the results of the traffic impact, and wherein, The result notification message includes information regarding whether the policy generated based on information stored in the third network entity has been applied.

14. The first network entity of claim 13, wherein the information included in the request message further includes target address information for the result notification of the traffic impact.

15. The first network entity of claim 12, wherein the information included in the request message includes an indicator requesting notification of the abandonment of the traffic impact, and wherein, The result notification message includes information related to the obsolescence of information stored in the third network entity.

Images