Method and apparatus for processing application function request

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Disclosed is a method for a session management function (SMF) supporting edge relocation in a wireless communication system. The method may comprise the steps in which: the SMF receives, 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 the edge relocation; the SMF determines whether simultaneous connection to the source PSA and the target PSA is impossible during the edge relocation; and the SMF transmits a notification that the SM policy cannot be applied to an application function (AF) on the basis of the determination.

Description

Method and device for processing application function requests

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for processing a request for an external application function in a mobile communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] In a wireless communication system, the application function (AF) can determine whether the AF request operation was successfully performed based on whether the request information within the core network was successfully stored in the unified data repository (UDR). The AF request is generated as a policy and delivered to the network function, but information on whether the network function's operation is performed according to the AF request is not provided to the AF. For example, information contained in the AF traffic influence request is delivered to the session management function (SMF) as an SM policy, but information on whether session management was performed based on the request information is not provided to the AF. In addition, information related to AF requests that were not approved by the policy control function (PCF) or that the SMF determined not to apply may be unnecessarily stored in the UDR.

[0009] The present disclosure proposes a method and device for processing an AF request that affects a policy related to a terminal receiving a service through a wireless communication system.

[0010] The present disclosure proposes a method and device for providing information to the AF on whether an AF request related to a terminal service is set with policy information that affects the operation of a network function and applied so that the network operates as intended.

[0011] The present disclosure proposes a method and device for managing application data generated within a UDR due to an AF request.

[0012] In a method of a session management function (SMF) supporting edge relocation in a wireless communication system according to one embodiment of the present disclosure, the method may include: receiving, by the SMF, from a policy control function (PCF) an SM policy including a simultaneous connection request to a source PSA (protocol data unit (PDU) session anchor) and a target PSA during edge relocation; determining, by the SMF, whether simultaneous connection to the source PSA and the target PSA is not possible during edge relocation; and transmitting, by the SMF, a notification of inapplicability of the SM policy to an application function (AF) based on the determination.

[0013] In a wireless communication system according to one embodiment of the present disclosure, a session management function (SMF) device supporting edge relocation includes a transceiver; and a processor controlling the transceiver. The processor may be configured to receive an SM policy including a simultaneous connection request to a source PSA (protocol data unit (PDU) session anchor) and a target PSA during edge relocation from a policy control function (PCF), determine whether simultaneous connection to the source PSA and the target PSA is not possible during edge relocation, and transmit a notification of inapplicability of the SM policy to an application function (AF) based on the determination.

[0014] A method by a network entity of a wireless communication system according to one embodiment of the present disclosure may include receiving a request message for traffic influence from a second network entity, storing information included in the request message in a third network entity, transmitting a response message for the request message to the second network entity, and receiving a result notification message for the request message from a fourth network entity, and transmitting the result notification message to the second network entity.

[0015] A network entity of a wireless communication system according to one embodiment of the present disclosure may include a transceiver and a processor controlling the transceiver. The processor may be configured to perform the following operations: receiving a request message regarding traffic influence from a second network entity, storing information included in the request message in a third network entity, transmitting a response message for the request message to the second network entity, and receiving a result notification message for the request message from a fourth network entity and transmitting the result notification message to the second network entity.

[0016] FIG. 1 is a block diagram showing an example configuration of a wireless communication system according to an embodiment of the present disclosure.

[0017] FIG. 2 is a diagram illustrating a method for providing an AF with information on whether an AF request is applicable according to one embodiment of the present disclosure.

[0018] FIG. 3 is a diagram illustrating a method for removing AF request related information from a UDR according to one embodiment of the present disclosure.

[0019] FIG. 4 is a block diagram illustrating a configuration of a UE according to one embodiment of the present disclosure.

[0020] FIG. 5 is a block diagram illustrating a configuration of a network entity according to one embodiment of the present disclosure.

[0021] The operating principle of the present disclosure is described in detail with reference to the attached drawings below.

[0022] In explaining the operating principles of the present disclosure, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0023] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0024] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The embodiments of the present disclosure are provided solely to ensure the completeness of the present disclosure and to fully inform those skilled in the art of the present disclosure of the scope of the disclosure.

[0025] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s).

[0026] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0027] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, according to the embodiment, the '~ unit' may include components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. Furthermore, according to an embodiment, the '~parts' may include one or more processors.

[0028] The terms described below are defined based on their functions in this disclosure. These terms may vary depending on the intent or custom of the user or operator, and therefore their definitions should be determined based on the overall content of this specification.

[0029] The terms used in this disclosure to refer to network entities, terms used to refer to messages, terms used to refer to identification information, and the like are provided for convenience of explanation. Therefore, the disclosure is not limited to the terms described below, and other terms that refer to objects with equivalent technical meanings may be used.

[0030] For convenience, the present disclosure uses terms and names defined in the 3GPP (3rd generation partnership project long term evolution) 5G system specifications, but is not limited by the terms and names and can be equally applied to systems conforming to other specifications.

[0031] The term 'terminal' or 'device' used in the present disclosure may be referred to as a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit, subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile, or other terms. Various embodiments of the terminal may include a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, a photographing device such as a digital camera having a wireless communication function, a gaming device having a wireless communication function, a music storage and playback home appliance having a wireless communication function, an Internet home appliance capable of wireless Internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. Additionally, the terminal may include, but is not limited to, an M2M (machine-to-machine) terminal or an MTC (machine type communication) terminal / device. In this specification, the terminal may also be referred to as an electronic device or simply a device.

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

[0033] Referring to FIG. 1, a 5G mobile communication network may be composed of a 5G user equipment (UE) (110), a radio access network (RAN) (120) (e.g., at least one of a base station, a 5G nodeB (gNB), or an evolved nodeB (eNB)), and a 5G core network. The 5G core network may include various network functions (NF). For example, the 5G core network may include at least one of network functions such as an access and mobility management function (AMF) (150), a session management function (SMF) (160), a policy control function (PCF) (180), an application function (AF) (130), a unified data management (UDM) (191), a user plane function (UPF) (170) responsible for forwarding data to a data network (DN) (171), a network exposure function (NEF) (193), a unified data repository (UDR) (192), and an edge application server discovery function (EASDF).

[0034] Each NF supports the following functions:

[0035] - AMF (150) provides functions for access and mobility management per UE, and one UE can be connected to one AMF by default.

[0036] - DN (171) refers to, for example, operator service, Internet access, or third-party service. DN (171) can transmit a downlink protocol data unit (PDU) to UPF (170) or receive a PDU transmitted from UE (110) from UPF (170).

[0037] - PCF (180) provides a function to determine policies such as mobility management and session management by receiving information about packet flow from an application server. Specifically, PCF (180) may support functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane function(s) (e.g., AMF (150), SMF (160), etc.) can enforce the policy rules, and implementing a front end for accessing related subscription information for policy determination within a user data repository (UDR) (192).

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

[0039] - UDM (191) can store user subscription data, policy data, etc.

[0040] - UPF (170) can transmit a downlink PDU received from DN (171) to UE (110) via (R)AN (120), and can transmit an uplink PDU received from UE (110) via (R)AN (120) to DN (171).

[0041] - AF (130) can interact with the 3GPP core network to provide services (e.g., support functions such as application influence on traffic routing, access to network exposure functions, and interaction with policy frameworks for policy control).

[0042] - NEF (193) can provide access to and use of services provided by the core network to AF (130) or other network functions. For example, AF (130) can transmit a policy control request to PCF (180) or UDR (192) through NEF (193).

[0043] FIG. 2 is a diagram illustrating a method for providing an AF with information on whether an AF request is applicable according to one embodiment of the present disclosure.

[0044] Referring to FIG. 2, in operation 201, the AF (130) may generate an AF request message. The PCF (180) may subscribe to receive a notification message in advance when new information about the AF request is created or changed in the UDR (192). For example, the PCF (180) may subscribe to the following information.

[0045] (Data Set = Application Data; Data Subset = AF traffic influence request information, Data Key = S-NSSAI and / or DNN and / or Internal Group Identifier or SUPI)

[0046] In operation 202, AF (130) may transmit a traffic influence request message (Nnef_Trafficinfluence_Create / Update / Delete) to NEF (193). The traffic influence request message may include at least one of the following information:

[0047] - IP (internet protocol) address of UE (110)

[0048] - Identifier of UE (110)

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

[0050] - AF service identifier

[0051] - DNAI (data network application identifier) ​​list

[0052] - AF transaction identifier

[0053] - UE IP address preservation indication

[0054] - Information on AF subscription to corresponding SMF events

[0055] - Information for EAS IP Replacement in 5GC

[0056] - User plane latency requirement)

[0057] - Indication for Simultaneous Connectivity over the source and target PSA (PDU session anchor) at Edge Relocation

[0058] In addition, in operation 202, the AF (130) may transmit an indicator for an AF request and / or an influence result notification required, and a notification target address to the NEF (193). The indicator may be used for the purpose of requesting notification of the result of whether the AF request has actually been applied to a network function. For the same purpose, the AF (130) may include an event ID for AF request / influence result notification in the AF subscription to corresponding SMF events and transmit the information to the NEF (193) in the AF request message. In addition, the AF (130) may use various parameters to request the core network function to notify the result of whether each request has been applied.

[0059] In operations 203 and 204, the NEF (193) may store the information received from the AF (130) in operation 202 in the UDR (192) and transmit a response message to the AF (130). The NEF (193) may store the information received from the AF (130) as application data in the UDR (192). The NEF (193) may store an indication for AF request / influence result notification required, a notification target address, or an event ID for AF request / influence result notification in the UDR (192) together with the information received from the AF (130).

[0060] In operation 205, the PCF (180) may be notified of AF request related information from the UDR (192). If the indication for AF request / influence result notification required, notification target address, or event ID for AF request / influence result notification is stored as application data, the UDR (192) may provide the PCF (180) with implicit subscribe to SM policy creation / authorization result information and notification target address including the indication for AF request / influence result notification required, notification target address, or event ID for AF request / influence result notification.

[0061] At operation 206, the PCF (180) may generate and approve an SM policy using the information received from the UDR (192). The PCF (180) may transmit the generated SM policy to the SMF (160) including an implicit subscription to the SM policy setup result and a notification target address. This may be to notify the AF (130) of the result of whether the SM policy generated and transmitted by the PCF (180) was successfully applied to the user plane by the SMF (160).

[0062] If the PCF (180) fails to create an SM policy based on the information received from the UDR (192) in operation 205, and if the information received from the UDR (192) includes an indication for AF request / influence result notification required and the PCF (180) receives an implicit subscribe to SM Policy creation / authorization result, the PCF (180) may notify the AF (130) of the result on whether to apply the SM policy through the NEF (193) in operation 207. For example, if the SM policy is created based on an AF request including an Indication for Simultaneous Connectivity over the source and target PSA at Edge Relocation, if it is determined that the SSC mode (session and service continuity mode) 3 of the UE is not supported or session breakout-related operations are not possible based on subscription data, etc., the SM policy to support the Simultaneous Connectivity over the source and target PSA at Edge Relocation may not be created. In this case, PCF (180) may transmit a notification of AF influence result including information indicating that SM policy cannot be applied or application has failed to AF (130).

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

[0064] In operation 209, if the SMF (160) recognizes that the SM policy cannot be applied in operation 208, it can notify the PCF (180) and the AF (130) of this. The SMF (130) can transmit a notification of AF influence result including information indicating that the SM policy cannot be applied or that the application has failed to be applied to the AF (130). For example, when an SM policy including a request for support of Simultaneous Connectivity over the source and target PSA at Edge Relocation is received from the PCF (180) and UP path configuration is performed, if a new UPF is selected due to a movement of the UE's location, etc., Simultaneous Connectivity over the source and target PSA at Edge Relocation support may not be supported. In this case, the SMF (160) can notify the PCF (180) and the AF (130) of information that the corresponding SM policy cannot be applied.

[0065] FIG. 3 is a diagram illustrating a method for removing AF request related information from a UDR according to one embodiment of the present disclosure.

[0066] Referring to FIG. 3, in operation 301, the AF (130) may generate an AF request message. The PCF (180) may subscribe to a service to receive a notification message in advance when new information about the AF request is created or changed in the UDR (192). For example, the PCF (180) may subscribe to the following information.

[0067] (Data Set = Application Data; Data Subset = AF traffic influence request information, Data Key = S-NSSAI and / or DNN and / or Internal Group Identifier or SUPI)

[0068] In operation 302, AF (130) may transmit a traffic influence request message to NEF (193). The traffic influence request message may include at least one of the following information:

[0069] - IP (internet protocol) address of UE (110)

[0070] - Identifier of UE (110)

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

[0072] - AF service identifier

[0073] - DNAI (data network application identifier) ​​list

[0074] - AF transaction identifier

[0075] - UE IP address preservation indication

[0076] - Information on AF subscription to corresponding SMF events

[0077] - Information for EAS IP Replacement in 5GC

[0078] - User plane latency requirement)

[0079] - Indication for Simultaneous Connectivity over the source and target PSA (PDU session anchor) at Edge Relocation

[0080] In addition, in operation 302, the AF (130) may transmit an indication for notification of AF request deprecation to the NEF (193). This indication may be used to receive a notification when information about generated application data or SM policies generated due to the AF request is no longer applicable to the network function and becomes invalid (deprecated application data). For the same purpose, the AF (130) may include an event ID for AF request / Application data deprecation (event ID for af request / influence result notification) in the AF subscription to corresponding SMF events in the AF request message and transmit it to the NEF (193). In addition, the AF (130) may use various parameters to request the core network function to notify the result of application for each request.

[0081] In operations 303 and 304, the NEF (193) may store the information received from the AF (130) in operation 302 in the UDR (192) and transmit a response message to the AF (130). The NEF (193) may store the information received from the AF (130) as application data in the UDR (192). The NEF (193) may store an indication for AF request / influence result notification required, a notification target address, or an event ID for AF request / influence result notification in the UDR (192) together with the information received from the AF (130).

[0082] In operation 305, the PCF (180) may be notified of AF request related information from the UDR (192). If the indication for AF request / influence result notification required, notification target address, or event ID for AF request / influence result notification is stored as application data, the UDR (192) may provide the PCF (180) with implicit subscribe to SM policy creation / authorization result information and notification target address including the indication for AF request / influence result notification required, notification target address, or event ID for AF request / influence result notification.

[0083] At operation 306, the PCF (180) may generate and approve an SM policy using the information received from the UDR (192). The PCF (180) may transmit the generated SM policy to the SMF (160) including an implicit subscribe to the SM policy setup result and a notification target address. This may be to notify the UDR (192) or the NEF (193) when the SM policy generated and transmitted by the PCF (180) has been successfully applied to the user plane by the SMF (160), but the SM policy is no longer applicable and will not be applied in the future.

[0084] If the SM policy generated by PCF (180) based on the information received from UDR (192) in operation 305 is no longer valid, PCF (180) may transmit an Application Data Deprecation request or Application Data Deprecation notification message to UDR (192) to notify this in operation 307.

[0085] The UDR (192) that receives the Application Data Deprecation request or Application Data Deprecation notification message from the PCF (180) can delete or depreciate the corresponding application data information in operation 308 and send a notification message to a network function entity (e.g., PCF (180), SMF (160), etc.) that has subscribed to a service that is notified when a change to the corresponding application data occurs.

[0086] In operation 309, PCF (180) may transmit Application Data Deprecation notification to AF (130) via NEF (193).

[0087] In operation 310a, when AF (130) receives a notification such as Application Data Deprecation notification from PCF (180) through NEF (193) regarding a previously transmitted AF request, it can transmit a message requesting deletion of AF request-related information requested by AF (130) to NEF (193), and in operation 310b, NEF (193) can transmit a deletion request message for information requested by AF (130) to UDR (192) according to a request by AF (130).

[0088] Independently of operations 307 to 309, the SMF (160) may transmit a Deprecation request or Deprecation notification message to the PCF (180) in operation 311. For example, if traffic routing is established by applying the SM policy received from the PCF (180) in operations 307 to 309, but the SM policy application is no longer valid due to reasons such as a change in the subscription data of the UE or the UE entering an area where traffic routing is not possible due to movement of the UE, the SMF (160) may transmit a Deprecation request or Deprecation notification message for the received SM policy to the PCF (180).

[0089] When PCF (180) receives a Deprecation request or Deprecation notification message for an SM policy from SMF (160), it can transmit a Deprecation request or Deprecation notification message to UDR (192) by specifying the application data used to create the corresponding SM policy in operation 312. After removing or depreciating the corresponding application data, UDR (192) can transmit a notification message (Notification of AF request deprecation) regarding the occurrence of the corresponding event to AF (130) in operation 313. The notification message (Notification of AF request deprecation) transmitted to AF (130) in operation 313 can be transmitted through NEF (193).

[0090] FIG. 4 is a block diagram illustrating a configuration of a UE according to one embodiment of the present disclosure.

[0091] Referring to FIG. 4, a UE (e.g., UE (110) of FIG. 1) may include at least one of a processor (401), a transceiver (403), or a memory (405). The UE is not limited to including only the illustrated components, and the UE may include more or fewer components than the illustrated components.

[0092] According to one embodiment of the present disclosure, the transceiver (403) can transmit and receive signals with at least one network entity (e.g., RAN (120), AMF (150), and / or at least one other UE). The signals transmitted and received between the network entity and the UE can include at least one of control information or data. The transceiver (403) can receive signals through a wireless channel and transmit them to the processor (601), and transmit the signals received from the processor (401) through the wireless channel.

[0093] According to one embodiment of the present disclosure, the processor (401) can control the operation of the UE to perform an operation corresponding to at least one of the embodiments of FIGS. 2 and 3.

[0094] The processor (401), the transceiver (403), and the memory (405) do not necessarily need to be implemented as separate modules, and may of course be implemented as a single module in the form of a single chip. The processor (401) and the transceiver (403) may be electrically connected. The processor (401) may include an application processor (AP) and / or a communication processor (CP).

[0095] According to one embodiment of the present disclosure, the memory (405) can store data such as basic programs, application programs, setting information, etc. for the operation of the UE. The memory (405) can provide the stored data according to a request of the processor (401). The memory (405) can be configured as a storage medium or a combination of storage media such as a read only memory (ROM), a random access memory (RAM), a hard disk, a compact disc read only memory (CD-ROM), and a digital versatile disc (DVD). The memory (405) can include a plurality of memories. The processor (401) can perform at least one of the operations corresponding to the embodiments of the present disclosure based on a program for performing at least one of the operations corresponding to the embodiments of the present disclosure stored in the memory (405).

[0096] FIG. 5 is a block diagram illustrating a configuration of a network entity according to one embodiment of the present disclosure.

[0097] Referring to FIG. 5, a 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 a processor (501), a transceiver (503) including a transmitter and / or a receiver, or a memory (505). The network entity is not limited to including only the components illustrated, and the network entity may include more or fewer components than the components illustrated.

[0098] According to one embodiment of the present disclosure, the transceiver (503) can transmit and receive signals with 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), or AF (130)) and / or at least one UE (e.g., UE (110)). The signals transmitted and received between the at least one other network entity and / or the at least one UE can include at least one of control information or data. When the network entity illustrated in FIG. 5 is a base station (e.g., RAN (120)), the transceiver (503) can include a transceiver for transmitting and receiving wireless signals with the UE (e.g., UE (110)), and a transceiver or communication interface for transmitting and receiving signals with other network entities of the core network.

[0099] According to one embodiment of the present disclosure, the processor (501) can control a network entity to perform at least one of the operations corresponding to the embodiments of FIGS. 2 and 3. The processor (501), the transceiver (503), and the memory (505) need not necessarily be implemented as separate modules, and may of course be implemented as a single module in the form of a single chip. The processor (501) and the transceiver (503) may be electrically connected. The processor (501) may include an AP and / or a CP.

[0100] According to one embodiment of the present disclosure, the memory (505) can store data such as basic programs, application programs, setting information, etc. for the operation of the network entity. The memory (505) can provide the stored data according to a request of the processor (501). The memory (505) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. The memory (505) can include a plurality of memories. The processor (501) can perform at least one of the operations corresponding to the embodiments of the present disclosure based on a program for performing at least one of the operations corresponding to the embodiments of the present disclosure stored in the memory (505).

[0101] It should be noted that the system configuration diagrams, method example diagrams, device configuration diagrams, etc. exemplified in FIGS. 1 to 5 above are not intended to limit the scope of the present disclosure. That is, not all configurations or operations described in FIGS. 1 to 5 above should be construed as essential components for implementing the present disclosure, and the present disclosure may be implemented without detriment to the essence of the present disclosure even if only some components are included.

[0102] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0103] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs may include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0104] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0105] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0106] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0107] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. A method of SMF (session management function) supporting edge relocation in a wireless communication system, The above SMF receives an SM policy from a policy control function (PCF) including simultaneous connection requests to a source PSA (protocol data unit (PDU) session anchor) and a target PSA during edge relocation; The above SMF determines whether simultaneous connection to the source PSA and the target PSA is not possible during edge relocation; and A method including an action of the SMF sending a notification of non-applicability of the SM policy to the AF (application function) based on the decision.

2. In paragraph 1, A method further comprising the SMF performing a user plane function (UPF) and user plane path configuration based on the SM policy.

3. A method in the second paragraph, wherein the user plane path setting includes resetting traffic routing.

4. In a session management function (SMF) device supporting edge relocation in a wireless communication system, Transmitter and receiver; and comprising a processor controlling the transceiver; A device characterized in that the processor is configured to receive an SM policy including a simultaneous connection request to a source PSA (protocol data unit (PDU) session anchor) and a target PSA during edge relocation from a policy control function (PCF), determine whether simultaneous connection to the source PSA and the target PSA is not possible during edge relocation, and transmit a notification of inapplicability of the SM policy to an application function (AF) based on the determination.

5. A device according to claim 4, characterized in that the processor is further configured to perform a user plane function (UPF) and user plane path configuration based on the SM policy.

6. A device according to claim 5, wherein the user plane path setting includes traffic routing re-establishment.

7. In a method of operating a first network entity in a wireless communication system, The act of receiving a request message for traffic influence from a second network entity; An operation of storing information included in the request message in a third network entity and transmitting a response message for the request message to the second network entity; and Receive a result notification message for the above request message from the fourth network entity, and A method comprising the action of transmitting a notification message to said second network entity.

8. In paragraph 7, The information contained in the above request message includes an instruction requesting notification of the results of the traffic impact, A method in which the above result notification message includes information on whether a policy generated based on information stored in the third network entity is applied.

9. In paragraph 8, A method wherein the information included in the above request message further includes target address information for notification of the results regarding the traffic impact.

10. In paragraph 7, The information contained in the above request message includes an instruction requesting notification of deprecation of the above traffic impact, A method wherein the above result notification message includes information about depreciation of information stored in the third network entity.

11. In paragraph 7, The above first network entity is a network exposure function (NEF), The above second network entity is an application function (AF), The above third network entity is a unified data repository (UDR), A method characterized in that the fourth network entity is a policy control function (PCF).

12. In a first network entity in a wireless communication system, Transmitter and receiver; and comprising a processor controlling the transceiver; The above processor, The act of receiving a request message for traffic influence from a second network entity; An operation of storing information included in the above request message in a third network entity and transmitting a response message for the above request message to the second network entity, and A first network entity configured to perform an operation of receiving a result notification message for the request message from a fourth network entity and transmitting the result notification message to the second network entity.

13. In paragraph 12, The information contained in the above request message includes an instruction requesting notification of the results of the traffic impact, The above result notification message is a first network entity that includes information on whether a policy generated based on information stored in the third network entity is applied.

14. In paragraph 13, The information contained in the above request message further includes target address information for notification of the result regarding the traffic impact to the first network entity.

15. In paragraph 12, The information contained in the above request message includes an instruction requesting notification of deprecation of the above traffic impact, The above result notification message is a first network entity that includes information about depreciation of information stored in the third network entity.

Images