Method and apparatus for sending notification to target af in wireless communication system

Abstract

A method performed by an application function (AF) in a wireless communication system is provided. The method includes receiving, from a session management function (SMF), a late notification message indicating a change of a data network access identifier (DNAI), identifying whether the AF change is required based on the late notification message, and transmitting, to the SMF, a response message including information for changing to a target AF for a target DNAI based on a result of the identifying that the AF change is required.

Description

Technical Field

[0001] This disclosure relates to communication systems. More specifically, this disclosure relates to a method for enhancing session continuity of a UE by sending a notification to the target application function (AF) when the local data network (DN) changes due to the movement of a user equipment (UE). Background Technology

[0002] To meet the increased demand for wireless data traffic resulting from the commercialization of fourth-generation (4G) communication systems, improved fifth-generation (5G) or near-5G communication systems have been developed. Therefore, 5G or near-5G communication systems are referred to as super-4G network communication systems or post-Long Term Evolution (LTE) systems.

[0003] To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency millimeter-wave (mmWave) bands (e.g., the 60 GHz band). To mitigate path loss and increase transmission distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are being discussed for 5G communication systems.

[0004] In addition, to improve the system network, technologies such as advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receive interference cancellation have been developed in 5G communication systems.

[0005] In addition, hybrid frequency shift keying (FSK), quadrature amplitude modulation (QAM) (FQAM), and sliding window superposition coding (SWSC) are being developed as advanced coding and modulation (ACM) methods, as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies.

[0006] In 5G systems, there are considerations to support a wider range of services compared to existing 4G systems. For example, the most representative services include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), and evolved multimedia broadcast / multicast service (eMBMS). Furthermore, a system providing URLLC services can be called an URLLC system, and a system providing eMBB services can be called an eMBB system. Additionally, the terms "service" and "system" are used interchangeably.

[0007] Among the services mentioned above, URLLC is a new service considered for 5G systems, unlike existing 4G systems. Compared to other services, it meets requirements such as ultra-high reliability (e.g., approximately 10). -5 The conditions include low packet error rate and low latency (e.g., approximately 0.5 milliseconds). To meet these stringent conditions, URLLC services may require applications with shorter Transmission Time Intervals (TTIs) than eMBB services, and various operational methods for using such applications are being considered.

[0008] The Internet is evolving from a human-centric network of connections where information is generated and consumed to an Internet of Things (IoT) network where information is exchanged and processed between distributed components such as things. The Internet of Everything (IoE) technology, which combines big data processing technologies with IoT technologies through connections to cloud servers and other technologies, is also emerging. To realize the IoT, technological components such as detection technologies, wired / wireless communication and network infrastructure, service interface technologies, and security technologies are required. Recently, research has been conducted on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) for connecting things.

[0009] In the IoT environment, intelligent Internet of Things (IoT) services can be provided to create new value in human life by collecting and analyzing data generated from connected things. Through the convergence and integration of existing information technology (IT) with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0010] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, M2M communication, and MTC are being implemented using 5G communication technologies such as beamforming, MIMO, and array antennas. Using cloud RAN as the big data processing technology mentioned above can be an example of the integration of 5G and IoT technologies.

[0011] Since various services can be provided based on the above description and the development of mobile communication systems, there is a particular need for methods to enhance the session continuity of UEs.

[0012] The above information is presented as background information only to aid in understanding this disclosure. No determination is made, and no assertion is made, regarding whether any of the above content is applicable to prior art relating to this disclosure. Summary of the Invention

[0013] A method is provided that is performed by an application function (AF) in a wireless communication system. The method includes: receiving a delayed notification message from a session management function (SMF) indicating a change in a data network access identifier (DNAI); identifying, based on the delayed notification message, whether an AF change is required; and, based on the result of identifying that an AF change is required, sending a response message to the SMF including information for changing to a target AF targeting the target DNAI. Attached Figure Description

[0014] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings.

[0015] Figure 1 This is a diagram illustrating the structure of a fifth-generation (5G) network according to an embodiment of the present disclosure.

[0016] Figure 2 This is a diagram illustrating the configuration of sending an early / late notification from the Session Management Function (SMF) to the Target Application Function (AF) when a User Plane Management event occurs, according to an embodiment of this disclosure.

[0017] Figure 3 This is a diagram illustrating the configuration by which the SMF sends a delayed notification to the AF when a user plane management event occurs, according to an embodiment of this disclosure.

[0018] Figure 4 This is a diagram illustrating the configuration by which the SMF sends an advance notification to the target AF when a user plane management event occurs, according to an embodiment of this disclosure.

[0019] Figure 5 This is a diagram illustrating the configuration of joining or subscribing to a service to request AF notification when a traffic routing change or a user plane management event related to a Protocol Data Unit (PDU) session occurs, according to an embodiment of this disclosure.

[0020] Figure 6 This is a diagram illustrating the configuration of the SMF sending an early / late notification to the target AF when a user plane management event occurs, according to an embodiment of this disclosure.

[0021] Figure 7 This is a flowchart of a method for sending a notification from an SMF to a target AF according to an embodiment of the present disclosure.

[0022] Figure 8 This is a block diagram of the structure of a network function (NF) according to an embodiment of the present disclosure.

[0023] Figure 9 This is a block diagram of the structure of a user equipment (UE) according to an embodiment of the present disclosure.

[0024] In all the accompanying drawings, the same reference numerals will be understood to refer to the same parts, components and structures. Detailed Implementation

[0025] The preferred embodiment of the invention

[0026] This disclosure aims to at least address the aforementioned problems and / or disadvantages, and to at least provide the advantages described below. Therefore, one aspect of the invention aims to provide a method and apparatus for efficiently providing services in a wireless communication system.

[0027] Additional aspects will be set forth in part in the description which follows, and will be apparent in part from the description, or may be learned by practice of the presented embodiments.

[0028] According to one aspect of this disclosure, a method is provided performed by an application function (AF) in a wireless communication system. The method includes: receiving a delayed notification message from a session management function (SMF) indicating a change in a data network access identifier (DNAI); identifying, based on the delayed notification message, whether an AF change is required; and, based on the result of identifying that an AF change is required, sending a response message to the SMF including information for changing to a target AF targeting the target DNAI.

[0029] The response message includes at least one of the following: indication of AF change, target AF ID, or target AF notification target address.

[0030] Sending a response message to the SMF that includes information about the change to the target AF includes: in the case where the AF requests a delayed notification message via the Network Open Function (NEF), sending a response message to the NEF that includes at least one of an indication of AF change, the target AF ID, or the notification target address of the target AF, and the response message is sent to the SMF via the NEF.

[0031] Sending a response message to the SMF that includes information about the change to the target AF includes: identifying whether the application relocation was completed successfully on time, and if the application relocation was not completed successfully on time, the response message includes a negative reason code.

[0032] Identifying whether an AF change is needed based on delayed notification messages includes: confirming whether the target DNAI is served by an AF based on delayed notification messages, and identifying the target AF for the target DNAI if the target DNAI is not served by an AF.

[0033] When the SMF receives a response message indicating a change to the target AF, the SMF sends a delayed notification message to the target AF based on the response message.

[0034] The delayed notification message includes the target DNAI of the Protocol Data Unit (PDU) session.

[0035] According to another aspect of this disclosure, a method performed by an SMF in a wireless communication system is provided. The method includes: sending a delayed notification message to an AF indicating a change in DNAI; and, if an AF change is required based on the delayed notification message, receiving from the AF a response message including information for changing to a target AF targeting the target DNAI.

[0036] The response message includes at least one of the following: indication of AF change, target AF ID, or target AF notification target address.

[0037] Receiving a response message from the AF that includes information about the change to the target AF includes: in the case where the AF requests a delayed notification message via the NEF, receiving from the NEF a response message that includes at least one of an indication of AF change, the target AF ID, or the notification target address of the target AF, and the response message being sent to the NEF via the AF.

[0038] If the application relocation fails to complete successfully on time, the response message includes a negative reason code.

[0039] The AF identifies whether it is serving the target DNAI based on delayed notification messages, and if the AF is not serving the target DNAI, the AF identifies the target AF for the target DNAI.

[0040] The method further includes: when the SMF receives a response message indicating a change to the target AF, sending a delayed notification message to the target AF based on the response message.

[0041] The delayed notification message includes the target DNAI of the PDU session.

[0042] According to another aspect of this disclosure, an AF (Automatic AF) in a wireless communication system is provided. The AF includes: a transceiver; and at least one processor coupled to the transceiver and configured to: receive a delayed notification message from an SMF (Supervisory Element) indicating a change in DNAI (Dual DNAI); identify, based on the delayed notification message, whether an AF change is required; and, based on the identification that an AF change is required, send a response message to the SMF including information for changing to a target AF for the target DNAI.

[0043] The response message includes at least one of the following: indication of AF change, target AF ID, or target AF notification target address.

[0044] At least one processor is configured to: in the event that an AF requests a delayed notification message via NEF, send a response message to NEF including at least one of an indication of AF change, a target AF ID, or a notification target address of the target AF, and the response message is sent to SMF via NEF.

[0045] At least one processor is configured to: confirm whether the application relocation was successfully completed on time, and, if the application relocation was not successfully completed on time, respond with a negative reason code.

[0046] At least one processor is configured to: identify whether a target DNAI is served by an AF based on a delayed notification message, and identify the target AF for the target DNAI if the target DNAI is not served by an AF.

[0047] When the SMF receives a response message indicating a change to the target AF, the SMF sends a delayed notification message to the target AF based on the response message.

[0048] Other aspects, advantages, and salient features of this disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments disclosed in conjunction with the accompanying drawings.

[0049] Embodiments of the present invention

[0050] The following description, provided with reference to the accompanying drawings, is intended to aid in a full understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. It includes various specific details to aid understanding, but these should be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.

[0051] The terms and words used in the following description and claims are not limited to their literal meaning, but are used solely by the inventors to enable a clear and consistent understanding of this disclosure. Therefore, it will be clear to those skilled in the art that the following description providing various embodiments of this disclosure is for illustrative purposes only and is not intended to limit the disclosure as defined by the appended claims and their equivalents.

[0052] It should be understood that, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” include plural referents. Thus, for example, referring to “the surface of a component” includes referring to one or more such surfaces.

[0053] For the same reason, each element shown in the figures may be exaggerated, omitted, or shown schematically. Furthermore, the dimensions of each element shown do not substantially reflect its actual dimensions. In each figure, the same or corresponding constituent elements are indicated by the same reference numerals.

[0054] Referring to the accompanying drawings, which illustrate preferred embodiments of the present disclosure, a full understanding of the disclosure, its advantages, and the objectives to be achieved by practicing the disclosure is obtained. However, the disclosure may be implemented in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that the disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Throughout the specification, the same reference numerals denote the same constituent elements.

[0055] Throughout this disclosure, the expression "at least one of a, b or c" indicates only a, only b, only c, both a and b, both a and c, both b and c, all a, b and c, or variations thereof.

[0056] Examples of terminals may include user equipment (UE), mobile base station (MS), cellular phone, smartphone, computer, multimedia system capable of performing communication functions, etc.

[0057] In this disclosure, the controller may also be referred to as a processor.

[0058] Throughout the specification, a layer (or layer device) may also be referred to as an entity.

[0059] It will be understood that the flowchart blocks and combinations thereof can be executed by computer program instructions. Because these computer program instructions can be loaded into 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 create units for performing the functions described in the flowchart blocks. The computer program instructions can be stored in a computer-usable or computer-readable storage medium capable of directing the computer or other programmable data processing device to perform its functions in a particular manner, and therefore the instructions stored in the computer-usable or computer-readable storage medium can also produce a manufacturing item containing instruction units for performing the functions described in the flowchart blocks. The computer program instructions can also be loaded into a computer or other programmable data processing device, and therefore, when a series of operations are performed in the computer or other programmable data processing device, the instructions for operating the computer or other programmable data processing device by generating a computer-executable process can provide operations for performing the functions described in the flowchart blocks.

[0060] Furthermore, each box may represent a module, segment, or portion of code that includes 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 out of sequence. For example, depending on the corresponding function, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order.

[0061] As used herein, the term "unit" refers to a software component or a hardware component such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC) that performs a specific function. However, the term "unit" is not limited to software or hardware. A "unit" can be configured to reside in an addressable memory medium or to operate one or more processors. Thus, for example, the term "unit" can refer to components such as software components, object-oriented software components, class components, and task components, and can include processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The functionality provided by components and "units" can be associated with a small number of components and "units," or can be divided into additional components and "units." Furthermore, components and "units" can be implemented to reproduce one or more central processing units (CPUs) in a device or secure multimedia card.

[0062] As used herein, a base station is an entity used to allocate resources to a UE, and examples of a base station may include at least one of an eNode B, Node B, base station (BS), radio access unit, base station controller, or network node. Examples of terminals may include a UE, MS, cellular phone, smartphone, computer, multimedia system capable of performing communication functions, etc. Furthermore, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Moreover, based on the judgment of those skilled in the art, embodiments of this disclosure may also be applied to other communication systems with partial modifications without significantly departing from the scope of this disclosure.

[0063] In the following description, for ease of illustration, terms for identifying access nodes, terms for indicating network entities or network functions (NFs), terms for indicating messages, terms for indicating interfaces between network entities, and terms for indicating various identification information are illustrated. Therefore, this disclosure is not limited to the terms described below, and other terms relating to objects with equivalent technical meanings may be used.

[0064] In the following text, for ease of explanation, terms and names defined in the 3GPP Long Term Evolution (LTE) standard and / or the 3GPP New Radio (NR) standard may be used in part. However, this disclosure is not limited to these terms and names and may be applied to systems conforming to other standards.

[0065] Embodiments of this disclosure disclose a method for enhancing session continuity of a UE when a User Plane Function (UPF) relocation occurs due to UE movement, resulting in a change of the Data Network Access Identifier (DNAI) and a change of the Local DN due to the DNAI change, by providing notification to the Target Application Function (AF) (i.e., the new AF responsible for the changed Local DN). This disclosure will now be described more fully with reference to the accompanying drawings, in which embodiments of this disclosure are illustrated.

[0066] Figure 1 This is a diagram illustrating the structure of a fifth-generation (5G) network according to embodiments of the present disclosure. The network entities or network nodes that form the 5G network are described below.

[0067] refer to Figure 1 The (Radio) Access Network ((R)AN) is the entity that performs the allocation of radio resources for the UE and can be at least one of an eNode B, gNode B, Node B, base station (BS), next-generation radio access network (NG-RAN), 5G-AN, radio access unit, base station controller, or a node on the network. The terminal can be at least one of a UE, next-generation (NG)UE, MS, cellular phone, smartphone, or computer. Furthermore, the terminal may include a multimedia system capable of performing communication functions. Although embodiments of this disclosure have been described using examples of 5G systems, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds. Moreover, based on the judgment of those skilled in the art, embodiments of this disclosure can also be applied to other communication systems with partial modifications without significantly departing from the scope of this disclosure.

[0068] In the transition from fourth-generation (4G) systems to 5G systems, wireless communication systems have defined new core networks, namely next-generation (NG) cores or 5G cores (5GC) networks. In the new core network, all traditional network entities (NEs) are virtualized into network functions (NFs). According to embodiments of this disclosure, a network function can mean a network entity, a network component, or a network resource.

[0069] According to embodiments of this disclosure, 5GC may include Figure 1 The NF shown is not limited to this disclosure. Figure 1 As shown, and 5GC can include more than Figure 1The NF shown can be more than NF, or can include more than Figure 1 The NF shown is less than the NF.

[0070] According to embodiments of this disclosure, the Access and Mobility Management Function (AMF) can be a network function that manages the mobility of a UE.

[0071] According to embodiments of this disclosure, the Session Management Function (SMF) can be a network function for managing Packet Data Network (PDN) connections provided to the UE. PDN connections can be stored in the name of Protocol Data Unit (PDU) sessions.

[0072] According to embodiments of this disclosure, the policy control function (PCF) may be a network function that applies the mobile communication provider's service policy, charging policy, and PDU session policy to the UE.

[0073] According to embodiments of this disclosure, unified data management (UDM) can be a network function that stores information about subscribers.

[0074] According to embodiments of this disclosure, the Network Open Function (NEF) can be a function that provides information about the UE to a server outside the 5G network. Furthermore, the NEF can provide information required to provide services to the 5G network and store that information in a Unified Data Repository (UDR).

[0075] According to embodiments of this disclosure, the UPF can be a function that performs gateway functions to send user data (PDU) to a data network (DN).

[0076] According to embodiments of this disclosure, a network repository function (NRF) can perform the function of discovering NFs.

[0077] According to embodiments of this disclosure, the Authentication Server Function (AUSF) can perform UE authentication in both 3GPP and non-3GPP access networks.

[0078] According to embodiments of this disclosure, the Network Slice Selection Function (NSSF) can perform the function of selecting a network slice instance provided to the UE.

[0079] According to embodiments of this disclosure, a DN can be a data network in which a UE sends and receives data to use services provided by a network service provider or a third-party service.

[0080] Figure 2 This is a diagram illustrating the configuration of the SMF sending early / late notifications to the AF when a user plane management event occurs, according to an embodiment of this disclosure. More specifically, in Figure 2The method provided is such that when an AF requests both early notification and late notification, the source AF informs the SMF of the changes in the DNAI based on the AF (which is responsible for the local DN) by using two notifications, and the SMF sends a notification to the target AF.

[0081] refer to Figure 2 In Phase 1, SMF can detect the occurrence of a user plane management event that generates an AF notification (i.e., the conditions for triggering an AF notification are met). An example of a user plane management event is shown below.

[0082] - Generation and removal of PDU session anchors (PSA)

[0083] -DNAI alteration

[0084] - Ethernet PSA relocation

[0085] -AF requests other events via notification subscription requests.

[0086] Phases 2a and 2b illustrate the configuration for the SMF to send an advance notification to the AF via the NEF when the AF requests an AF notification via the NEF (e.g., a request made via an AF request (notification subscription) prior to Phase 1). In Phase 2a, when the SMF detects a user plane management event in Phase 1, the SMF can send an advance notification to the NEF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message may include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance or late notification), the identity of the source DNAI and / or the identity of the target DNAI, the UE's IP address / prefix or Media Access Control (MAC) address, or the General Public Subscription Identifier (GPSI) or N6 traffic routing information.

[0087] In phase 2b, when an Nsmf_EventExposure_Notify message is received, the NEF can configure the information mapping (e.g., mapping between AF transaction internal IDs and AF transaction IDs, mapping between SUPI and GPSI, etc.) and send an Nnef_TrafficInfluence_Notify message to the appropriate AF that includes the information received from the SMF.

[0088] Phase 2c illustrates the configuration for the SMF to send advance notifications to the AF when the AF does not request AF notifications via the NEF (e.g., prior to Phase 1, via an AF request (notification subscription)). In Phase 2c, when the SMF detects a user plane management event in Phase 1, the SMF can send an advance notification to the AF of the target DNAI of the PDU session via the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message may include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance or late notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information.

[0089] According to embodiments of this disclosure, phases 2a and 2b may be executed selectively with phase 2c. For example, phase 2c may be executed when the AF requests an AF notification not via the NEF (e.g., via an AF request (notification subscription)); otherwise, phases 2a and 2b may be executed. In the following description of this disclosure, the configuration of "the AF requests an AF notification (e.g., via an AF request (notification subscription))" and the configuration of "the AF requests an AF notification (e.g., without a NEF request (notification subscription))" may be executed selectively as described with respect to phases 2a and 2b, and as described with respect to phase 2c, respectively.

[0090] In phase 2d, the AF that has received advance notification can confirm the target DNAI's ID and determine whether the target DNAI is within the coverage area of ​​the local DN it is responsible for. When the target DNAI is outside the coverage area of ​​the local DN it is responsible for, the AF can identify a new AF (i.e., the target AF) responsible for the new local DN and perform AF migration configuration as the target AF. Through the above configuration, the AF can perform application relocation to the target AF and send AF notification subscription information, user information, and UE information (i.e., application information, account information, etc.) to the target AF.

[0091] Phases 2e and 2f illustrate the configuration for the AF to send a response to advance notification to the SMF via the NEF when the AF requests notification from the NEF. In phase 2e, the AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. When, in phase 2d, the target DNAI is within the coverage area of ​​the local DN covered by the AF, the AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required for the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the AF can send a positive or negative response. If the AF cannot perform application relocation in a timely manner, the AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message. When a target DNAI falls outside the coverage area of ​​the local DN that the AF is responsible for during phase 2d, the AF can notify the SMF of the instruction requiring AF modification, the ID of the target AF responsible for the target local DN to which the target DNAI belongs, and the address of the target AF that sent the message. To do this, the AF can send an Nnef_TrafficInfluence_AppRelocationInfo message to the NEF containing at least one of the following: the instruction for AF modification, the target AF ID, or the notification target address of the target AF.

[0092] In phase 2f, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes the information received from the AF, to the appropriate SMF.

[0093] Phase 2g illustrates the configuration for the AF to send a response to advance notification to the SMF when the AF does not request AF notification via the NEF. The AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. When, in Phase 2d, the target DNAI is within the coverage area of ​​the local DN covered by the AF, the AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required for the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the AF can send a positive or negative response. If the AF cannot perform application relocation in a timely manner, the AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message. When a target DNAI falls outside the coverage area of ​​the local DN that the AF is responsible for during phase 2d, the AF can notify the SMF of the instruction that the AF needs to be changed, the ID of the target AF responsible for the target local DN to which the target DNAI belongs, and the address of the target AF that sent the message. To do this, the AF can send the SMF an Nsmf_EventExposure_AppRelocationInfo message containing at least one of the following: the instruction for AF change, the target AF ID, or the notification target address of the target AF.

[0094] In Phase 3, the SMF can perform UPF removal, modification, and addition, or DNAI modification. When runtime coordination is set between 5GC and AF, the SMF can wait for a response to the advance notification from AF before executing Phase 3, based on the "Expected AF Confirmation" indication included in the AF request message, and can also skip Phase 3 until a positive response is received from AF.

[0095] Phases 4a through 4f illustrate the configuration for the SMF to send delayed notifications when the target DNAI is within the coverage of the local DN covered by the AF that has joined or subscribed to the notification service in Phase 2d (i.e., when no AF change occurs). Once at least one of Phases 4a through 4f has been executed, the configuration after Phase 5 can be omitted. When an AF change occurs, the configuration of Phases 4a through 4f can be omitted, and the configuration after Phase 5 can be executed.

[0096] Phases 4a and 4b illustrate the configuration for the SMF to send a delayed notification to the AF via the NEF when the AF requests an AF notification via the NEF. In phase 4a, when the SMF detects a user plane management event in phase 1 and performs a UPF removal, change, or addition, or DNAI change, in phase 3, the SMF can send a delayed notification to the NEF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message may include at least one of the following: the AF transaction internal ID, the type of notification (i.e., early notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information. When runtime coordination is established between the 5GC and the AF, the SMF can wait for a response to the delayed notification from the AF, and may not send data via a new UP path, until a positive response is received from the AF, according to the "Expected AF Confirmation" indication included in the AF request message.

[0097] In phase 4b, when an Nsmf_EventExposure_Notify message is received, the NEF performs configuration of information mappings (e.g., mappings between AF transaction internal IDs and AF transaction IDs, mappings between SUPI and GPSI, etc.) and sends an Nnef_TrafficInfluence_Notify message to the appropriate AF that includes the information received from the SMF.

[0098] Phase 4c illustrates the configuration for the SMF to send a delayed notification to the AF when the AF does not request the AF notification via the NEF. When the SMF detects a user plane management event in Phase 1 and performs a UPF removal, change, or addition, or a DNAI change in Phase 3, in Phase 4c, the SMF can send a delayed notification to the AF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message may include at least one of the following: the AF transaction internal ID, the type of notification (i.e., early notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information.

[0099] Phases 4d and 4e illustrate the configuration for the AF to send a response to a delayed notification to the SMF via the NEF when the AF requests an AF notification via the NEF. In phase 4d, the AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. When, in phase 2d, the target DNAI is within the coverage area of ​​the local DN covered by the AF, the AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required for the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the AF can send a positive or negative response. When the AF cannot perform the application relocation in a timely manner, the AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message.

[0100] In phase 4e, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes information received from the AF, to the appropriate SMF.

[0101] Phase 4f shows the configuration for the AF to send a response to a delayed notification to the SMF when the AF does not request the AF notification via the NEF. The AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. When the target DNAI is within the coverage area of ​​the local DN covered by the AF in Phase 2d, the AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required for the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the AF can send a positive or negative response. When the AF cannot perform the application relocation in a timely manner, the AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message.

[0102] Phase 5 illustrates the configuration for the SMF to send a delayed notification when it receives a response (e.g., a response message) in response to an advance notification, including information indicating that the target DNAI is outside the coverage of the local DN covered by the AF that has joined or subscribed to the notification service (i.e., an AF change is required). The previous phases 4a through 4f may not need to be performed when the configuration of Phase 5 is executed.

[0103] Phases 6a and 6b illustrate the configuration where the SMF sends a delayed notification to the target AF via the NEF when the target AF requests an AF notification via the NEF. During the advance notification process, when the SMF receives an indication requiring an AF change through a response message to the advance notification, in phase 6a, the SMF can send a delayed notification to the NEF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, and also information about the target AF (indication of AF change, target AF ID, or target AF notification target address) contained in the received advance notification response message. When runtime coordination is set up between 5GC and AF, based on the “Expected AF acknowledgment” indication included in the AF request message, SMF can wait for a response to the delayed notification from AF and can send data without sending it through a new UP path until a positive response is received from AF.

[0104] In phase 6b, when an Nsmf_EventExposure_Notify message is received, the NEF can configure information mappings (e.g., mappings between AF transaction internal IDs and AF transaction IDs, mappings between SUPI and GPSI, etc.) and configure information about the target AF within the NEF. It can also send an Nnef_TrafficInfluence_Notify message to the target AF that includes information received from the SMF.

[0105] Phase 6c illustrates the configuration for the SMF to send a delayed notification to the AF when the AF does not request AF notification via the NEF. During the transmission and reception of advance notifications, when the SMF receives an indication requiring an AF change via a response message to the advance notification, in Phase 6c, the SMF can send a delayed notification to the target AF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation, based on information about the target AF received from the advance notification response message (indication of AF change, target AF ID, or target AF notification target address). The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, and also the information about the target AF (indication of AF change, target AF ID, or target AF notification target address) contained in the received advance notification response message.

[0106] Phases 6d and 6e illustrate the configuration for an AF to send a response to a delayed notification to an SMF via the NEF when the AF requests an AF notification via the NEF. In phase 6d, the AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. The target AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required as the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform the application relocation in a timely manner, the target AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message.

[0107] In phase 6e, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes information received from the target AF, to the appropriate SMF.

[0108] Phase 6f illustrates the configuration for the target AF to send a response to a delayed notification to the SMF when the target AF does not request the AF notification via the NEF, or when the target AF does not receive the AF notification via the NEF. The target AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. The target AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required as the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform the application relocation in a timely manner, the target AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message.

[0109] The configuration of phases 7 through 8b involves changing the existing user plane management event subscription information of the source AF to the changed subscription information of the target AF when the local DN changes according to the DNAI, resulting in an AF change. The subscription information change method can include two approaches: as in phase 7, where the target AF updates the existing subscription information; and as in phases 8a and 8b, where the source AF erases the existing subscription information and the target AF executes a new subscription. In phases 7 through 8b, only phase 7 can be executed, or only phases 8a and 8b can be executed. Furthermore, the configuration of phases 7 through 8b can be omitted depending on the circumstances.

[0110] Figure 3 This is a diagram illustrating the configuration of the SMF sending a delayed notification to the AF when a user plane management event occurs, according to an embodiment of this disclosure. More specifically, in Figure 3 The document provides a method in which, when an AF requests a delayed notification, the source AF informs the SMF of the changes made by the AF (which is responsible for the local DN) based on the DNAI change by using a delayed notification, and the SMF sends a notification to the target AF.

[0111] refer to Figure 3 In Phase 1, when an AF notification is generated (i.e., the conditions for triggering an AF notification are met), the SMF can detect the generation of a user plane management event. An example of a user plane management event is shown below.

[0112] - Generation and removal of PDU session anchors (PSA)

[0113] -DNAI alteration

[0114] - Ethernet PSA relocation

[0115] -AF requests other events via notification subscription requests.

[0116] Phase 2 is executed when the SMF detects a user plane management event and the AF requests advance notification during Phase 1. However, in Figure 3 The text describes the case where the AF only requests delayed notification. In other words, in... Figure 3 In this context, stage 2 can be omitted.

[0117] In Phase 3, when a user plane management event is detected in Phase 1, the SMF can perform UPF removal, modification, and addition, or DNAI modification. When runtime coordination is established between 5GC and AF and AF requests advance notification, the SMF can wait for a response to the advance notification from AF before executing Phase 3, based on the "Expected AF Confirmation" indication included in the AF request message, and can choose not to execute Phase 3 until a positive response is received from AF.

[0118] exist Figure 3 This section only describes the configuration for sending delayed notifications when the target DNAI is outside the coverage area of ​​the local DNs managed by the AF of the subscription notification service (see Phase 4d), i.e., when an AF change occurs. See also... Figure 2 Phases 4a to 4f describe the configuration for sending a delayed notification when no AF change occurs.

[0119] Phases 4a and 4b illustrate the configuration for the SMF to send a delayed notification to the AF via the NEF when the AF requests an AF notification via the NEF. In phase 4a, when the SMF detects a user plane management event in phase 1 and performs a UPF removal, change, or addition, or DNAI change, in phase 3, the SMF can send a delayed notification to the NEF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message may include at least one of the following: the AF transaction internal ID, the type of notification (i.e., early notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information. When runtime coordination is established between the 5GC and the AF, the SMF can wait for a response to the delayed notification from the AF, and may not send data via a new UP path, until a positive response is received from the AF, according to the "Expected AF Confirmation" indication included in the AF request message.

[0120] In phase 4b, when an Nsmf_EventExposure_Notify message is received, the NEF performs configuration of information mappings (e.g., mappings between AF transaction internal IDs and AF transaction IDs, mappings between SUPI and GPSI, etc.) and sends an Nnef_TrafficInfluence_Notify message to the appropriate AF that includes the information received from the SMF.

[0121] Phase 4c illustrates the configuration for the SMF to send a delayed notification to the AF when the AF does not request the AF notification via the NEF. When the SMF detects a user plane management event in Phase 1 and performs a UPF removal, change, or addition, or a DNAI change in Phase 3, in Phase 4c, the SMF can send a delayed notification to the AF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message may include at least one of the following: the AF transaction internal ID, the type of notification (i.e., early notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information.

[0122] In phase 4d, the AF that has received the delayed notification can check the target DNAI's ID and determine if the target DNAI is within the coverage area of ​​the local DN it is responsible for. When the target DNAI is outside the coverage area of ​​the local DN it is responsible for, the AF can identify a new AF (i.e., the target AF) responsible for the new local DN and perform AF migration configuration as the target AF. Through the above configuration, the AF can perform application relocation to the target AF and send AF notification subscription information, user information, and UE information (application information, account information, etc.) to the target AF.

[0123] Phases 4e and 4f illustrate the configuration for the AF to send a response to a delayed notification to the SMF via the NEF when the AF requests an AF notification via the NEF. In phase 4e, the AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. When the target DNAI is within the coverage area of ​​the local DN covered by the AF in phase 4d, the AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required for the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the AF can send a positive or negative response. When the AF cannot perform the application relocation in a timely manner, the AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message. When a target DNAI falls outside the coverage area of ​​the local DN that the AF is responsible for during phase 4d, the AF can inform the SMF of the instruction requiring AF modification, the ID of the target AF responsible for the target local DN to which the target DNAI belongs, and the address of the target AF that sent the message. To do this, the AF can send an Nnef_TrafficInfluence_AppRelocationInfo message to the NEF containing at least one of the following: the instruction for AF modification, the target AF ID, or the notification target address of the target AF.

[0124] In phase 4f, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes the information received from the AF, to the appropriate SMF.

[0125] Phase 4g illustrates the configuration for the AF to send a response to a delayed notification to the SMF when the AF does not request the AF notification via the NEF. The AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. When the target DNAI is within the coverage area of ​​the local DN covered by the AF in Phase 4d, the AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required for the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the AF can send a positive or negative response. When the AF cannot perform the application relocation in a timely manner, the AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message. When a target DNAI falls outside the coverage area of ​​the local DN that the AF is responsible for during phase 4d, the AF can inform the SMF of the instruction that the AF needs to be changed, the ID of the target AF responsible for the target local DN to which the target DNAI belongs, and the address of the target AF that sent the message. To do this, the AF can send the SMF an Nsmf_EventExposure_AppRelocationInfo message that includes at least one of the following: the instruction for AF change, the target AF ID, or the notification target address of the target AF.

[0126] Phases 4h and 4i illustrate the configuration where the SMF sends a delayed notification to the target AF via the NEF when the AF requests an AF notification via the NEF. In phase 4h, when the SMF receives an indication requiring an AF change during a previous phase of sending and receiving delayed notifications, the SMF can send a delayed notification to the NEF of the target DNAI of the PDU session via the Nsmf_EventExposure_Notify service operation through a delayed notification response message. The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., early notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, as well as information about the target AF (indication of AF change, target AF ID, or target AF notification target address) contained in the received delayed notification response message. When runtime coordination is set up between 5GC and AF, based on the “Expected AF acknowledgment” indication included in the AF request message, SMF can wait for a response to the delayed notification from AF and can send data without sending it through a new UP path until a positive response is received from AF.

[0127] In phase 4i, when an Nsmf_EventExposure_Notify message is received, the NEF can configure information mappings (e.g., mappings between AF transaction internal IDs and AF transaction IDs, mappings between SUPI and GPSI, etc.) and configure information about the target AF within the NEF. It can also send an Nnef_TrafficInfluence_Notify message to the target AF that includes information received from the SMF.

[0128] Phase 4j illustrates the configuration for the SMF to send a delayed notification to the target AF when the AF does not request AF notification via the NEF. When the SMF receives an indication requiring an AF change during a previous phase of sending and receiving delayed notifications, in Phase 4j, the SMF can send a delayed notification to the target AF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation, based on information about the target AF received from the delayed notification response message (indication of AF change, target AF ID, or target AF notification target address). The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., early notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, and also the information about the target AF (indication of AF change, target AF ID, or target AF notification target address) contained in the received delayed notification response message.

[0129] Phases 4k and 4l illustrate the configuration for the target AF to send a response to a delayed notification to the SMF via the NEF when the AF requests AF notification via the NEF. In phase 4k, the target AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. The target AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required as the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform application relocation in a timely manner, the target AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message.

[0130] In phase 4l, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes information received from the target AF, to the appropriate SMF.

[0131] Phase 4m illustrates the configuration for the target AF to send a response to a delayed notification to the SMF when the target AF does not request the AF notification via the NEF, or when the target AF does not receive the AF notification via the NEF. The target AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. The target AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required as the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform the application relocation in a timely manner, the target AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message.

[0132] The configuration of phases 5 through 6b involves changing the existing user plane management event subscription information of the source AF to the changed subscription information of the target AF when the local DN changes according to the DNAI, resulting in an AF change. The subscription information change method can include two approaches: as in phase 5, where the target AF updates the existing subscription information; and as in phases 6a and 6b, where the source AF erases the existing subscription information and the target AF executes a new subscription. In phases 5 through 6b, only phase 5 can be executed, or only phases 6a and 6b can be executed. Furthermore, the configuration of phases 5 through 6b can be omitted.

[0133] Figure 4 This is a diagram illustrating a configuration whereby the SMF sends an advance notification to the target AF when a user plane management event occurs, according to an embodiment of this disclosure. More specifically, in Figure 4 The document provides a method in which, when an AF requests advance notification, the source AF informs the SMF of the changes in the DNAI based on the AF (which is responsible for the local DN) by using the advance notification configuration, and the SMF sends the notification to the target AF.

[0134] refer to Figure 4 In Phase 1, when an AF notification is generated (i.e., the conditions for triggering an AF notification are met), the SMF can detect the generation of a user plane management event. An example of a user plane management event is shown below.

[0135] - Generation and removal of PDU session anchors (PSA)

[0136] -DNAI alteration

[0137] - Ethernet PSA relocation

[0138] -AF requests other events via notification subscription requests.

[0139] exist Figure 4 This section only describes the configuration for sending advance notifications when the target DNAI is outside the coverage of the local DNs covered by the AF (AF) of the subscription notification service (see Phase 2d), i.e., when an AF change occurs. When no AF change occurs, please refer to [the relevant documentation / reference]. Figure 2 a to Figure 2 The g phase describes the configuration for sending advance notice.

[0140] Phases 2a and 2b illustrate the configuration for the SMF to send an advance notification to the AF via the NEF when the AF requests an AF notification via the NEF. When the SMF detects a user plane management event in Phase 1, in Phase 2a, the SMF can send an advance notification to the NEF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message may include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information.

[0141] In phase 2b, when an Nsmf_EventExposure_Notify message is received, the NEF performs configuration of information mappings (e.g., mapping between AF transaction internal IDs and AF transaction IDs, mapping between SUPI and GPSI, etc.) and sends an Nnef_TrafficInfluence_Notify message to the appropriate AF that includes the information received from the SMF.

[0142] Phase 2c illustrates the configuration for the SMF to send advance notifications to the AF when the AF does not request AF notifications via the NEF. When the SMF detects a user plane management event in Phase 1, in Phase 2c, the SMF can send an advance notification to the AF of the target DNAI of the PDU session via the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message may include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information.

[0143] In phase 2d, the AF that has received advance notification can check the target DNAI's ID and determine if the target DNAI is within the coverage area of ​​the local DN it is responsible for. When the target DNAI is outside the coverage area of ​​the local DN it is responsible for, the AF can identify a new AF (i.e., the target AF) responsible for the new local DN and perform AF migration configuration as the target AF. Through the above configuration, the AF can perform application relocation to the target AF and send AF notification subscription information, user information, and UE information (application information, account information, etc.) to the target AF.

[0144] Phases 2e and 2f illustrate the configuration for the AF to send a response to advance notification to the SMF via the NEF when the AF requests notification from the NEF. In phase 2e, the AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. When, in phase 2d, the target DNAI is within the coverage area of ​​the local DN covered by the AF, the AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required for the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the AF can send a positive or negative response. If the AF cannot perform application relocation in a timely manner, the AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message. When a target DNAI falls outside the coverage area of ​​the local DN that the AF is responsible for during Phase 2d, the AF can inform the SMF of the instruction requiring AF modification, the ID of the target AF responsible for the target local DN to which the target DNAI belongs, and the address of the target AF that sent the message. To do this, the AF can send an Nnef_TrafficInfluence_AppRelocationInfo message to the NEF containing at least one of the following: the instruction for AF modification, the target AF ID, or the notification target address of the target AF.

[0145] In phase 2f, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes the information received from the AF, to the appropriate SMF.

[0146] Phase 2g illustrates the configuration for the AF to send a response to advance notification to the SMF when the AF does not request AF notification via the NEF. The AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. When, in Phase 2d, the target DNAI is within the coverage area of ​​the local DN covered by the AF, the AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required for the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the AF can send a positive or negative response. If the AF cannot perform application relocation in a timely manner, the AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message. When a target DNAI falls outside the coverage area of ​​the local DN that the AF is responsible for during phase 2d, the AF can inform the SMF of the instruction that the AF needs to be changed, the ID of the target AF responsible for the target local DN to which the target DNAI belongs, and the address of the target AF that sent the message. To do this, the AF can send the SMF an Nsmf_EventExposure_AppRelocationInfo message containing at least one of the following: the instruction for AF change, the target AF ID, or the notification target address of the target AF.

[0147] Phases 2h and 2i illustrate the configuration where the SMF sends an advance notification to the target AF via the NEF when the AF requests an AF notification via the NEF. In the preceding advance notification transmission and reception process, when the SMF receives an indication requiring an AF change via a response message to the advance notification, in phase 2h, the SMF can send an advance notification to the NEF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, and also information about the target AF (indication of AF change, target AF ID, or target AF notification target address) contained in the received advance notification response message.

[0148] In phase 2i, when an Nsmf_EventExposure_Notify message is received, the NEF can configure information mappings (e.g., mappings between AF transaction internal IDs and AF transaction IDs, mappings between SUPI and GPSI, etc.) and configure information about the target AF within the NEF. It can also send an Nnef_TrafficInfluence_Notify message to the target AF that includes information received from the SMF.

[0149] Phase 2j illustrates the configuration for the SMF to send advance notification to the AF when the AF does not request AF notification via the NEF. During the prior transmission and reception of the advance notification, when the SMF receives an indication requiring an AF change via a message response to the advance notification, in Phase 2j, the SMF can send an advance notification to the target AF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation, based on information about the target AF received from the advance notification response message (indication of AF change, target AF ID, or target AF notification target address). The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, and also the information about the target AF (indication of AF change, target AF ID, or target AF notification target address) contained in the received advance notification response message.

[0150] Phases 2k and 2l illustrate the configuration for the target AF to send a response to advance notification to the SMF via the NEF when the AF requests AF notification via the NEF. In phase 2k, the target AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. The target AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required as the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform application relocation in a timely manner, the target AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message.

[0151] In phase 2l, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes information received from the target AF, to the appropriate SMF.

[0152] Phase 2m illustrates the configuration for the target AF to send a response to advance notification to the SMF when the target AF does not request AF notification via the NEF, or when the target AF does not receive AF notification via the NEF. The target AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. The target AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required as the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform application relocation in a timely manner, the AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message.

[0153] The configuration of phases 3 through 4b involves changing the existing user plane management event subscription information of the source AF to the changed subscription information of the target AF when the local DN changes according to the DNAI, resulting in an AF change. The subscription information change method can include two approaches: as in phase 3, where the target AF updates the existing subscription information; and as in phases 4a and 4b, where the source AF erases the existing subscription information and the target AF executes a new subscription. In phases 3 through 4b, only phase 3 can be executed, or only phases 4a and 4b can be executed. Furthermore, the configuration of phases 3 through 4b can be omitted depending on the circumstances.

[0154] In Phase 5, when a User Plane Management event is detected in Phase 1, the SMF can perform UPF removal, modification, and addition, or DNAI modification. When runtime coordination is established between 5GC and AF and AF requests advance notification, the SMF can wait for a response to the advance notification from AF before executing Phase 5, based on the "Expected AF Confirmation" indication included in the AF request message, and can choose not to execute Phase 5 until a positive response is received from AF.

[0155] Phase 6 can be executed when the SMF detects a user plane management event and the AF requests a delayed notification during Phase 1. Figure 4 The text only describes the scenario where AF requests advance notice. Please refer to [reference needed]. Figure 2 or Figure 3 This describes the configuration for delayed notifications.

[0156] Figure 5 This is a diagram illustrating the configuration of joining or subscribing to a service to request AF notification when a traffic routing change or a user plane management event related to a Protocol Data Unit (PDU) session occurs, according to an embodiment of this disclosure.

[0157] refer to Figure 5In Phase 1, the AF can generate an AF request. The AF request may include the AF transaction ID, the UE's address (IP or Ethernet) (if available), GPSI (if available), DNN (if available), S-NSSAI (if available), external group identifier (if available), application identifier or traffic filtering information, AF service identifier, DNAI list and corresponding routing profile ID or N6 traffic routing information, indication of traffic relevance, indication of application relocation probability, indication of UE IP address storage, early and / or late notification of UP path management events, or at least one of the following: time validity conditions and spatial validity conditions. Furthermore, the SMF can check the target DNAI's ID and determine if the target DNAI is within the coverage area of ​​the local DN managed by the AF that has subscribed to the notification service. When the target DNAI is outside the coverage area of ​​the local DN managed by the AF that has subscribed to the notification service, the AF can add adjacent AF information to the AF request to identify the AF responsible for the new local DN, i.e., the target AF. Neighboring AF information may include at least one piece of information from the AF that sent the AF request, the AF ID of the neighboring AF, the list of DNAIs in the coverage area of ​​the local DN that each of the neighboring AFs is responsible for, or the notification target address that can send notifications to each of the neighboring AFs. For example, as shown below, an AF may add information about neighboring AFs (AF#1, AF#2, and AF#3) to the AF request.

[0158] - Adjacent AF information

[0159] *(AF#1ID, DNAI#1, Notification Target Address)

[0160] *(AF#2ID, DNAI#2, Notification Target Address)

[0161] *(AF#3ID, DNAI#3, Notification Target Address)

[0162] The method of sharing information such as AF ID, DNAI list, and notification target address between adjacent AFs can correspond to operations outside the 3GPP standard scope and can be implemented through signaling or pre-configuration between AFs. Furthermore, the AF sending the AF request can send information such as the AF ID, AF transaction identifier, or notification target address to adjacent AFs (AF#1, AF#2, and AF#3), and the adjacent AFs can store the received information. Moreover, the above method can correspond to operations between AFs outside the 3GPP standard scope.

[0163] In Phase 2, the AF can send AF requests to the NEF using the Nnef_TrafficInfluence_Create service operation. To update or erase an existing request, the AF can use the Nnef_TrafficInfluence_Update or Nnef_TrafficInfluence_Delete service operations with the AF transaction ID of the existing request to be updated or erased. When the AF can send AF requests directly to the PCF instead of via the NEF, the AF can search for the appropriate PCF using the Nbsf_management_Discovery service. The NEF can perform the necessary authorization controls and perform the mapping between the information sent by the AF and the information required within 5GC.

[0164] In phase 3a, when the AF performs the Nnef_TrafficInfluence_Create or Nnef_TrafficInfluence_Update operation, the NEF can store the AF request information in the UDR, as follows.

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

[0166] When AF performs the Nnef_TrafficInfluence_Delete operation, NEF can erase the AF request information in the UDR.

[0167] (Data Set = Application Data; Data Subset = AF traffic influence request information; Data Key = AF transaction internal ID)

[0168] In phase 3b, NEF can notify AF of the results of the requested create / update / delete by sending a response message to AF.

[0169] In phase 4, the UDR can send notifications about changes to the stored data by sending a Nudr_DM_Notify message to the PCF, which has subscribed to a notification service for changes to AF requests.

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

[0171] In Phase 5, the PCF involved in an AF request can update the PCC rules of the PDU session associated with the AF request using the Npcf_SMPolicyControl_UpdateNotify service operation. When the AF request includes a notification request related to an UP path change, the Npcf_SMPolicyControl_UpdateNotify message can include a notification-related ID containing the AF transaction's internal ID and a notification target address toward the NEF or AF.

[0172] In phase 6, when a PCC rule is received, the SMF can perform a reconfiguration of the user plane of the PDU session through the following actions.

[0173] - Add / replace / remove UPF in the data path (e.g., UL CL or branch point).

[0174] - New prefix UE configuration (when applying multihoming)

[0175] -UPF update for target DNAI

[0176] -Subscribe to AMF notifications

[0177] Figure 6 This is a diagram illustrating the configuration of the SMF sending an early / late notification to the target AF when a user plane management event occurs, according to an embodiment of this disclosure.

[0178] More specifically, in Figure 6The document provides a method by which the SMF sends a notification to the target AF (which is responsible for the local DN) based on the DNAI change when the AF adds neighboring AF information to the AF request, using either advance notification or delayed notification.

[0179] refer to Figure 6 In Phase 1, when an AF notification is generated (i.e., the conditions for triggering an AF notification are met), the SMF can detect the generation of a user plane management event. An example of a user plane management event is shown below.

[0180] - Generation and removal of PDU session anchors (PSA)

[0181] -DNAI alteration

[0182] - Ethernet PSA relocation

[0183] -AF requests other events via notification subscription requests.

[0184] In Phase 2, the SMF can examine the ID of the changed target DNAI and determine whether the changed target DNAI is within the coverage area of ​​the local DN responsible for by the current AF (i.e., the source AF) based on neighboring AF information received from the current AF (i.e., the source AF). When the target DNAI is outside the coverage area of ​​the local DN responsible for by the current AF, the SMF can identify the new AF (i.e., the target AF) responsible for the new local DN and send an early / late notification to the target AF. The target AF that has received the notification from the SMF can perform application relocation using the source AF and receive AF notification subscription information, user information, and UE information (application information, account information, etc.) from the source AF.

[0185] Phases 3a and 3b illustrate the configuration where the SMF sends an advance notification to the target AF via the NEF when the AF requests advance notification via the NEF. In Phase 2, when the SMF determines that an AF change is required, in Phase 3a, the SMF can send an advance notification to the NEF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, and can also include an indication that an AF change is required, as well as information about the target AF included in the neighboring AF information (the indication of the AF change, the target AF ID, or the target AF's notification target address).

[0186] In phase 3b, upon receiving the Nsmf_EventExposure_Notify message, the NEF can configure information mappings (e.g., mapping between AF transaction internal IDs and AF transaction IDs, mapping between SUPI and GPSI, etc.) and configure information about the target AF within the NEF. It can also send an Nnef_TrafficInfluence_Notify message to the target AF, including information received from the SMF. The target AF, having received advance notification, can identify that it has become the new responsible AF as the AF has changed according to the DNAI by checking the AF change indication, AF transaction ID, and source AF ID. Furthermore, the target AF can check the target DNAI ID and confirm whether the target DNAI is within the coverage area of ​​the local DN it is responsible for. The target AF can identify the source AF and perform AF migration using the source AF. With the above configuration, the target AF can perform application relocation and receive AF notification subscription information, user information, and UE information (application information, account information, etc.).

[0187] Phase 3c illustrates the configuration where the SMF sends an advance notification to the target AF when the AF does not request advance notification from the NEF. In Phase 2, when the SMF determines that an AF change is necessary, in Phase 3c, the SMF can send an advance notification to the target AF of the target DNAI in the PDU session using the Nsmf_EventExposure_Notify service operation, based on information about the target AF (an indication of AF change, the target AF ID, or the target AF's notification target address). The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., advance or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, as well as an indication of the AF change and information about the target AF (an indication of AF change, the target AF ID, or the target AF's notification target address). The target AF that has received the advance notification can identify that it has become the new responsible AF as the AF has changed according to the DNAI by checking the AF change indication, the AF transaction ID, and the source AF ID. Furthermore, the target AF can check the target DNAI's ID and confirm whether the target DNAI is within the coverage area of ​​the local DN it is responsible for. The target AF can also identify the source AF and utilize it to perform AF migration. With the above configuration, the target AF can perform application relocation and receive AF notifications, subscription information, user information, and UE information (application information, account information, etc.).

[0188] Phases 3d and 3e illustrate the configuration for the target AF to send a response to the advance notification to the SMF via the NEF when the AF requests advance notification from the NEF. In Phase 3d, the target AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. The target AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required as the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform the application relocation in a timely manner, the target AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message.

[0189] In phase 3e, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes information received from the target AF, to the appropriate SMF.

[0190] Phase 3f illustrates the configuration for the target AF to send a response to the advance notification to the SMF when the target AF does not request advance notification from the NEF (or when the target AF does not receive the AF notification from the NEF). The target AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. The target AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required as the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform the application relocation in a timely manner, the AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message.

[0191] In Phase 4, the SMF can perform UPF removal, modification, and addition, or DNAI modification. When runtime coordination is set up between 5GC and AF, the SMF can wait for a response to the advance notification from AF before executing Phase 4, based on the "Expected AF Confirmation" indication included in the AF request message, and can also skip Phase 4 until a positive response is received from AF.

[0192] Phases 5a and 5b illustrate the configuration where the SMF sends a delayed notification to the target AF via the NEF when the AF requests a delayed notification via the NEF. In Phase 2, when the SMF determines that an AF change is required, in Phase 5a, the SMF can send a delayed notification to the NEF of the target DNAI of the PDU session using the Nsmf_EventExposure_Notify service operation. The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., early notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, and can also include an indication that an AF change is required, as well as information about the target AF included in the neighboring AF information (the indication of the AF change, the target AF ID, or the target AF's notification target address). When runtime coordination is set up between 5GC and AF, based on the “Expected AF acknowledgment” indication included in the AF request message, SMF can wait for a response to the delayed notification from AF and can send data without sending it through a new UP path until a positive response is received from AF.

[0193] In phase 5b, upon receiving the Nsmf_EventExposure_Notify message, the NEF configures information mappings (e.g., mapping between AF transaction internal IDs and AF transaction IDs, mapping between SUPI and GPSI, etc.) and sets information about the target AF in the NEF. It can also send an Nnef_TrafficInfluence_Notify message to the target AF, including information received from the SMF. By examining the AF change indication, AF transaction ID, and source AF ID, the target AF that has received the delayed notification can recognize that it has become the new responsible AF as the AF changes according to the DNAI. Furthermore, the target AF can check the target DNAI ID and confirm whether the target DNAI is within the coverage area of ​​the local DN it is responsible for. The target AF can identify the source AF and perform AF migration using the source AF. With the above configuration, the target AF can perform application relocation and receive AF notification subscription information, user information, and UE information (application information, account information, etc.).

[0194] Phase 5c illustrates the configuration where the SMF sends a delayed notification to the target AF when the AF does not request a delayed notification via the NEF. In Phase 2, when the SMF determines that an AF change is necessary, in Phase 5c, the SMF can send a delayed notification to the target AF of the target DNAI in the PDU session using the Nsmf_EventExposure_Notify service operation, based on information about the target AF (an indication of AF change, the target AF ID, or the target AF's notification target address). The Nsmf_EventExposure_Notify message can include at least one of the following: the AF transaction internal ID, the type of notification (i.e., early notification or delayed notification), the identifier of the source DNAI and / or the identifier of the target DNAI, the UE's IP address / prefix or MAC address, or GPSI or N6 traffic routing information, and can also include an indication of the AF change and information about the target AF (an indication of AF change, the target AF ID, or the target AF's notification target address). By examining the AF change indication, the AF transaction ID, and the source AF ID, the target AF that has received the delayed notification can recognize that, as the AF changes according to the DNAI change, the target AF becomes the new responsible AF. Furthermore, the target AF can check the target DNAI's ID and confirm whether the target DNAI is within the coverage area of ​​the local DN it is responsible for. The target AF can also identify the source AF and utilize it to perform AF migration. With the above configuration, the target AF can perform application relocation and receive AF notifications, subscription information, user information, and UE information (application information, account information, etc.).

[0195] Phases 5d and 5e illustrate the configuration for the target AF to send a response to the delayed notification to the SMF via the NEF when the AF requests a delayed notification from the NEF. In phase 5d, the target AF can send a response to the Nnef_TrafficInfluence_Notify message to the NEF using the Nnef_TrafficInfluence_AppRelocationInfo service operation. The target AF can send the Nnef_TrafficInfluence_AppRelocationInfo message to the NEF immediately or after performing the application relocation required as the target DNAI. The Nnef_TrafficInfluence_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform the application relocation in a timely manner, the target AF can include a negative reason code in the Nnef_TrafficInfluence_AppRelocationInfo message.

[0196] In phase 5e, when the Nnef_TrafficInfluence_AppRelocationInfo message is received, the NEF can send the Nsmf_EventExposure_AppRelocationInfo message, which includes information received from the target AF, to the appropriate SMF.

[0197] Phase 5f illustrates the configuration for the target AF to send a response to a delayed notification to the SMF when the target AF does not request the delayed notification via the NEF (or when the target AF does not receive the AF notification via the NEF). The target AF can send a response to the Nsmf_EventExposure_Notify message to the SMF using the Nsmf_EventExposure_AppRelocationInfo service operation. The target AF can send the Nsmf_EventExposure_AppRelocationInfo message to the SMF immediately or after performing the application relocation required as the target DNAI. The Nsmf_EventExposure_AppRelocationInfo message can include N6 traffic routing information toward the target DNAI. Furthermore, the target AF can send a positive or negative response. When the target AF cannot perform the application relocation in a timely manner, the AF can include a negative reason code in the Nsmf_EventExposure_AppRelocationInfo message.

[0198] The configuration of phases 6 through 7b involves changing the existing user plane management event subscription information already subscribed to by the source AF to the changed target AF subscription information when the local DN changes according to the DNAI, resulting in an AF change. The subscription information change method can include two approaches: as in phase 6, the target AF updates the existing subscription information; and as in phases 7a and 7b, the source AF erases the existing subscription information and the target AF executes a new subscription. In phases 6 through 7b, only phase 6 can be executed, or only phases 7a and 7b can be executed. Furthermore, the configuration of phases 6 through 7b can be omitted depending on the circumstances.

[0199] Figure 7 This is a flowchart of a method for sending a notification from an SMF to a target AF according to an embodiment of the present disclosure.

[0200] refer to Figure 7 In operation 710, SMF can detect the occurrence of AF notification trigger events.

[0201] In operation 720, the SMF can send either a first advance notice or a first delayed notice regarding the triggering event to the source AF. Whether the SMF sends either the first advance notice or the first delayed notice, or both, depends on whether the AF requested the advance notice, the delayed notice, or both. Furthermore, the configuration for sending and receiving advance notices and responses, as well as the configuration for sending and receiving delayed notices and responses, can be executed separately, and can be referenced... Figures 2 to 6 Describe it.

[0202] In operation 730, the SMF can receive a response message from the source AF, including information about the target AF, as a response to the first early notification or the first late notification. The source AF can determine whether the target DNAI included in the notification received from the SMF in operation 720 is within the coverage of the local DN responsible for by the source AF. When the target DNAI is not within the coverage of the local DN responsible for by the source AF, the source AF can send a response message to the SMF, which includes an indication that an AF change is required, the ID of the target AF responsible for the target local DN to which the target DNAI belongs, and the address of the target AF to which the SMF sent the message.

[0203] In operation 740, the SMF can send a second advance notification or a second delayed notification to the target AF based on information about the target AF. The SMF can identify the target AF and its address using the response message received in operation 730 and send the notification to the target AF.

[0204] Figure 8 This is a block diagram of the structure of a network function (NF) according to an embodiment of the present disclosure.

[0205] refer to Figures 1 to 7 Each of the network entities or NFs described can correspond to Figure 8 The NF. For example, the structures of SMF, NEF, AF, etc. can correspond to Figure 8 The structure of NF as described in [the document].

[0206] refer to Figure 8 The NF may include a transceiver 810, a memory 820, and a processor 830. The transceiver 810, processor 830, and memory 820 of the NF can operate according to the communication method of the NF described above. However, the constituent elements of the NF are not limited to the examples described above. For example, the NF may include more or fewer constituent elements than those described above. Furthermore, the transceiver 810, processor 830, and memory 820 may be implemented as a single chip. Additionally, the processor 830 may include one or more processors.

[0207] Transceiver 810 (which is a collective term for receiver and transmitter of an NF) can transmit and receive signals with a base station, UE, or another NF. The signals to be transmitted and received with the base station, UE, or another NF may include control information and data. For this purpose, transceiver 810 may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification of the received signal and down-converting the frequency of the signal. However, this is merely one embodiment of transceiver 810, and the components of transceiver 810 are not limited to RF transmitters and RF receivers.

[0208] In addition, transceiver 810 can receive signals via a wireless channel, output the received signals to processor 830, and transmit signals output from processor 830 via a wireless channel.

[0209] The memory 820 can store the programs and data required for the operation of the NF. Furthermore, the memory 820 can store control information or data included in signals received from the NF. The memory 820 can include storage media or combinations of storage media such as read-only memory (ROM), random access memory (RAM), hard disk, optical disc ROM (CD-ROM), and digital versatile disc (DVD). Alternatively, the memory 820 may not be provided separately, but can be provided by being included in the processor 830.

[0210] Processor 830 can control a series of processes that cause the NF to operate according to the embodiments of the present disclosure described above. For example, processor 830 can receive and process control signals and data signals via transceiver 810. Furthermore, processor 830 can transmit processed control signals and data signals via transceiver 810. Processor 830 may include multiple processors, and processor 830 can perform component control operations of the NF by executing programs stored in memory 820.

[0211] According to embodiments of this disclosure, processor 830 can detect the occurrence of an AF notification triggering event, send a first advance notification or a first late notification about the triggering event to a source AF, receive a response message from the source AF including information about a target AF as a response to the first advance notification or the first late notification, and send a second advance notification or a second late notification about the triggering event to the target AF based on the information about the target AF.

[0212] According to embodiments of this disclosure, processor 830 can receive information about neighboring AFs of the source AF, detect the occurrence of an AF notification triggering event, determine whether the AF corresponding to the target DNAI has changed to the target AF based on the information about neighboring AFs of the source AF, and send a first advance notification or a first delayed notification about the triggering event to the target AF.

[0213] Figure 9 This is a block diagram of the structure of a UE according to an embodiment of the present disclosure.

[0214] refer to Figures 1 to 7 The described UE can correspond to Figure 9 UE.

[0215] refer to Figure 9 The UE may include a transceiver 910, a memory 920, and a processor 930. The transceiver 910, processor 930, and memory 920 of the UE can operate according to the communication method of the UE described above. However, the constituent elements of the UE are not limited to the examples described above. For example, the UE may include more or fewer constituent elements than those described above. Furthermore, the transceiver 910, processor 930, and memory 920 may be implemented as a single chip. Additionally, the processor 930 may include one or more processors.

[0216] Transceiver 910 (which is a collective term for the receiver and transmitter of the UE) can transmit and receive signals with a base station, NF, or another UE. The signals to be transmitted and received with the base station, NF, or another UE may include control information and data. For this purpose, transceiver 910 may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification of the received signal and down-converting the frequency of the signal. However, this is merely one embodiment of transceiver 910, and the components of transceiver 910 are not limited to RF transmitters and RF receivers.

[0217] In addition, transceiver 910 can receive signals via a wireless channel, output the received signals to processor 930, and transmit signals output from processor 930 via a wireless channel.

[0218] The memory 920 can store programs and data required for the operation of the UE. Furthermore, the memory 920 can store control information or data included in signals received from the UE. The memory 920 can include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Moreover, the memory 920 may not be provided separately, but can be provided by being included in the processor 930.

[0219] The processor 930 can control a series of processes that enable the UE to operate according to the embodiments of the present disclosure described above. For example, the processor 930 can receive and process control signals and data signals via transceiver 910. Furthermore, the processor 930 can transmit the processed control signals and data signals via transceiver 910. The processor 930 may include multiple processors, and the processor 930 can perform component control operations of the UE by executing programs stored in memory 920.

[0220] The methods described in the claims and specification of this disclosure can be implemented by hardware, software, or a combination of hardware and software.

[0221] When the method is implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. One or more programs may include instructions to cause the electronic device to perform the method according to the embodiments described in the claims or specification of this disclosure.

[0222] Such a program (software module or software) can be stored in non-volatile memory including RAM and flash memory, ROM, electrically erasable programmable ROM (EEPROM), disk storage devices, CD-ROM, DVD or other types of optical storage devices, or magnetic tape cassettes. Alternatively, the program can be stored in some or all of the above-mentioned memories. Furthermore, each constituting memory may include multiple memories.

[0223] Furthermore, the program can be stored in an attachable storage device accessible via a communication network, including the Internet, intranet, local area network (LAN), wide area network (WLAN), or storage area network (SAN), or a combination thereof. Such a storage device can be accessed by an external port to a device executing embodiments of this disclosure. Additionally, a separate storage device on the communication network can access the device executing embodiments of this disclosure.

[0224] The disclosed embodiments provide apparatus and methods for effectively providing services in a wireless communication system.

[0225] The embodiments of this disclosure disclosed in the specification and accompanying drawings are intended to provide specific examples that facilitate the description of the technical content of this disclosure and aid in understanding it, and are not intended to limit the scope of this disclosure. In other words, it will be apparent to those skilled in the art to which this disclosure pertains that other variations can be implemented based on the technical concepts of this disclosure. Furthermore, the various embodiments can be used by combining them with each other as needed. For example, a base station and a UE can operate by combining parts of embodiments of this disclosure with parts of another embodiment. Moreover, the embodiments of this disclosure can be applied to other communication systems, and other variations based on the technical concepts of this disclosure can be implemented.

[0226] Although this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by an application function (AF) entity in a wireless communication system, the method comprising: Receive a delayed notification message, including the Target Data Network Access Identifier (DNAI), from the Session Management Function (SMF) entity; Identify whether the target DNAI can be served by the AF entity; If the target DNAI cannot be served by the AF entity, identify the target AF entity for the target DNAI and perform AF migration to the target AF entity; as well as A response message including N6 traffic routing information related to the target DNAI is sent to the SMF entity as a response to the delayed notification message.

2. The method according to claim 1, wherein, The response message includes at least one of the following: an indication of AF change, a target AF identifier ID, or a notification target address of the target AF entity.

3. The method according to claim 1, in, The response message includes a reason code, and In cases where the application relocation in the target DNAI is not successfully completed on time, the reason code corresponds to a negative response.

4. The method according to claim 1, further comprising: Based on the result of identifying whether the target DNAI can be served by the AF entity, it is determined whether the AF needs to be changed.

5. The method according to claim 1, wherein, If the AF entity requests a delayed direct notification, the delayed notification message is received from the SMF entity.

6. The method according to claim 1, wherein, The delayed notification message includes the target DNAI of the Protocol Data Unit (PDU) session.

7. The method according to claim 1, wherein, The response message is sent immediately, or after the required application relocation in the target DNAI is completed.

8. A method performed by a Session Management Function (SMF) entity in a wireless communication system, the method comprising: Send a delayed notification message, including the target data network access identifier (DNAI), to the application function (AF) entity; as well as The AF entity receives a response message including N6 traffic routing information related to the target DNAI as a response to the delayed notification message. Wherein, whether the target DNAI can be identified by the AF entity service; In cases where the target DNAI cannot be served by the AF entity, the AF entity identifies the target AF entity for the target DNAI and performs AF migration to the target AF entity.

9. The method according to claim 8, wherein, The response message includes at least one of the following: an indication of AF change, a target AF identifier ID, or a notification target address of the target AF entity.

10. The method according to claim 8, wherein, The response message includes a reason code, and wherein, in the event that the application relocation in the target DNAI is not completed successfully on time, the reason code corresponds to a negative response.

11. The method according to claim 8, wherein, If the AF entity requests a delayed direct notification, the delayed notification message is sent to the AF entity.

12. The method according to claim 8, wherein, The delayed notification message includes the target DNAI of the Protocol Data Unit (PDU) session.

13. The method according to claim 8, wherein, The response message is received immediately, or after the required application relocation in the target DNAI is completed.

14. An application function (AF) entity in a wireless communication system, the AF entity comprising: transceiver; as well as At least one processor, coupled to the transceiver and configured to: Receive a delayed notification message, including the target data network access identifier (DNAI), from the Session Management Function (SMF) entity. Identify whether the target DNAI can be served by the AF entity. In the case where the target DNAI cannot be served by the AF entity, the target AF entity for the target DNAI is identified, and an AF migration to the target AF entity is performed. A response message including N6 traffic routing information related to the target DNAI is sent to the SMF entity as a response to the delayed notification message.

Images