WO2020071681A1 - Method and apparatus for supporting transfer of mobile edge computing in wireless communication system - Google Patents

Abstract

The present disclosure relates to a method and an apparatus for supporting transfer of mobile edge computing in a wireless communication system. A method for controlling a path between an application function (AF) and a terminal by a session management function (SMF) in a wireless communication system according to an embodiment of the present disclosure may include the steps of: receiving, from the AF, an AF request message including information regarding whether or not a change in a user plane function (UPF) is allowed; determining whether or not it is necessary to change the UPF included in the path between the AF and the terminal; transmitting a notification including information regarding a change in the UPF to the AF on the basis of the result of determination; confirming whether or not to await reception of a response message from the AF for a predetermined period of time on the basis of the information regarding whether or not to allow a change in the UPF; and controlling the change in the path between the terminal and the AF, including the UPF on the basis of the result of confirmation.

Description

Method and apparatus for supporting the transfer of mobile edge computing in a wireless communication system

The present disclosure relates to a method for supporting mobile edge computing in a wireless communication system. More specifically, it relates to an apparatus and method for supporting seamlessly the transfer of resources of mobile edge computing in a 5G mobile network in a 5G mobile network.

Efforts have been made to develop an improved 5G communication system or a pre-5G communication system to meet the increasing demand for wireless data traffic after commercialization of the 4G communication system. For this reason, the 5G communication system or the pre-5G communication system is called a 4G network (Beyond 4G Network) communication system or an LTE system (Post LTE) or later system. The 5G communication system established by 3GPP is called a New Radio (NR) system.

To achieve high data rates, 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, 60 gigahertz (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, in 5G communication systems, beamforming, massive array multiple input / output (massive MIMO), full dimensional multiple input / output (FD-MIMO) ), Array antenna, analog beam-forming, and large scale antenna techniques have been discussed and applied to NR systems.

In addition, in order to improve the network of the system, in the 5G communication system, the evolved small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network , Device to Device communication (D2D), wireless backhaul, mobile network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation Technology development is being conducted.

In addition, in the 5G system, advanced coding modulation (Advanced Coding Modulation (ACM)), Hybrid FSK and QAM Modulation (FQAM) and SSC (Sliding Window Superposition Coding), and advanced access technologies, FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed.

Meanwhile, the Internet is evolving from a human-centered connection network where humans generate and consume information, to an Internet of Things (IoT) network that exchanges information between distributed components such as objects. Internet of Everything (IoE) technology, in which big data processing technology, etc. through connection to a cloud server, is combined with IoT technology is also emerging. In order to implement IoT, technical elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between objects, a machine to machine (Machine to Machine) , M2M), and MTC (Machine Type Communication). In an IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects to create new values in human life may be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, high-tech medical service through convergence and combination between existing IT (iInformation Technology) technology and various industries. It can be applied to.

Accordingly, various attempts have been made to apply a 5G communication system to an IoT network. For example, 5G communication such as a sensor network, a machine to machine (M2M), and a machine type communication (MTC) are implemented by techniques such as beamforming, MIMO, and array antenna. It may be said that the application of cloud radio access network (cloud RAN) as the big data processing technology described above is an example of 5G technology and IoT technology convergence.

In addition, technologies related to mobile edge computing or fog computing, which have evolved from existing cloud computing, are emerging, and these technologies provide distributed cloud computing nodes located near users in providing services in a centralized data center. The core thing. The cloud computing nodes installed near the user can process and return the request immediately upon request of the user terminal, so there is an advantage of low latency and large-capacity transmission than the existing centralized cloud computing environment. As a service using such mobile edge computing, it can be applied to services such as connected car, virtual reality, augmented reality, and big data analysis.

In addition, V2X (Vehicle to Everything) is a general term that refers to all types of communication methods applicable to road vehicles, and in combination with the development of wireless communication technology, various additional services are available in addition to the initial safety use case. The IEEE 802.11p and IEEE P1609-based Wireless Access in Vehicular Environments (WAVE) standards have been standardized as a V2X service providing technology. However, WAVE, which is a type of Dedicated Short Range Communication (DSRC) technology, has a limitation in that a message communication distance between a vehicle and a vehicle is limited. To overcome these limitations, cellular-based V2X technology standards are being conducted in 3GPP. In Release 14, the LTE-based 4G V2X standard was completed, and in Release 16, the NR-based 5G V2X standard is in progress.

As it is possible to provide various services according to the above-mentioned and development of a mobile communication system, a method for effectively providing these services is required.

The disclosed embodiment provides an apparatus and method capable of effectively providing a service in a wireless communication system. More specifically, it provides an apparatus and method capable of supporting the transfer of mobile edge computing in a wireless communication system.

1 is a diagram illustrating a network structure and an interface of a wireless communication system according to an embodiment.

2 is a diagram for describing a handover situation without change of a PDU session according to an embodiment.

3 is a diagram illustrating a handover situation in which a PDU session is changed according to an embodiment but connected to the same MEC node.

FIG. 4 is a diagram illustrating a handover situation for accessing another MEC node while changing a PDU session according to an embodiment.

5 is a diagram illustrating a procedure of AF influence on traffic routing defined in 5GC according to an embodiment.

FIG. 6 is a diagram illustrating an AF notification procedure in AF influence on traffic routing defined in 5GC according to an embodiment.

7 is a diagram for explaining a method of transferring a PDU session for connection to the same MEC through I-UPF insertion according to an embodiment.

8 is a diagram illustrating a PDU session transfer procedure for connection to the same MEC through network-based I-UPF insertion according to an embodiment.

9 is a diagram illustrating a PDU session transfer procedure for connection with the same MEC through RAN-based I-UPF insertion according to an embodiment.

FIG. 10 is a diagram illustrating a method of transferring a PDU session for connection with another MEC through I-UPF insertion according to an embodiment.

11 is a diagram illustrating a PDU session transfer procedure for connection with another MEC through network-based I-UPF insertion according to an embodiment.

12 is a diagram illustrating a PDU session transfer procedure for connection with another MEC through RAN-based I-UPF insertion according to an embodiment.

13 is a diagram illustrating a PDU session transfer procedure for connection with another MEC using SSC MODE2 according to an embodiment.

14 is a diagram illustrating a PDU session transfer procedure for connection with another MEC using SSC MODE3 according to an embodiment.

15 is a diagram showing a procedure for transferring a PDU session for connection with another MEC based on a terminal using SSC MODE3 according to an embodiment.

16 is a diagram illustrating a method of changing a PDU session transfer procedure for connection with MEC according to an AF request by using SSC MODE2 according to an embodiment.

FIG. 17 is a diagram illustrating a method of changing a PDU session transfer procedure for connection with MEC according to an AF request by using SSC MODE3 according to an embodiment.

FIG. 18 is a diagram illustrating a method of changing a PDU session transfer procedure using whether to allow UPF transfer according to an AF request by using SSC MODE2 according to an embodiment.

FIG. 19 is a diagram illustrating a method of changing a PDU session transfer procedure according to an AF request using SSC MODE3 according to an embodiment and using UPF transfer permission.

FIG. 20 is a diagram illustrating a method of changing a PDU session transfer procedure according to an AF request using SSC MODE3 according to an embodiment and whether to allow UPF transfer based on a terminal. FIG. 21 is a diagram illustrating a method according to an embodiment. It is a diagram showing how to change the PDU session at the request of AF when completing the AF transfer using the UPF permission factor and SSC MODE2.

FIG. 22 is a diagram illustrating a method of changing a PDU session by request of AF when AF transfer is completed using UPF permission factor and SSC MODE3 according to an embodiment.

23 is a diagram illustrating a method of changing an SSC MODE3 based PDU session transfer procedure according to an embodiment using an AF response.

24 is a diagram illustrating a method of changing an SSC MODE3 based PDU session transfer procedure according to an embodiment using an AF response.

25 is a block diagram showing the structure of an entity according to an embodiment.

A method for supporting the transfer of mobile edge computing in a wireless communication system according to an embodiment includes the step of transmitting a pre-notification information regarding a user plane function (UPF) change by a Session Management Function (SMF) to an Application Function (AF), SMF controlling the operation related to the UPF according to the request of the AF, transmitting the post notification information about the UPF change to the AF by the SMF and updating the control information regarding the UPF by the AF It may include.

In a wireless communication system according to an embodiment of the present disclosure, a method for controlling a path between an application function (AF) and a terminal by a session management function (SMF) is related to whether or not a user plane function (UPF) change is allowed from AF. Receiving an AF request message including information; Determining whether it is necessary to change the UPF included in the path between the AF and the terminal; Based on the determination result, transmitting a notification including information regarding a change of the UPF to the AF; Determining whether to wait to receive a response message from the AF for a predetermined time based on the information on whether the UPF change is allowed; And controlling a change of a path between the AF including the UPF and the terminal based on the determination result.

According to an embodiment of the present disclosure, if the response message is not received from the AF for the predetermined time based on the information on whether the UPF change is allowed, the response of the AF is NACK. And identifying.

According to an embodiment of the present disclosure, the method further includes receiving the response message for the notification from the AF, wherein receiving the response message completes MEC transfer within the predetermined time. In this case, an ACK message may be received from the AF, and if MEC transfer is not completed within the predetermined time, a NACK message may be received from the AF.

According to an embodiment of the present disclosure, the predetermined time is a maximum waiting time for waiting to receive a response message from the AF, and the notification may include information about the predetermined time.

According to an embodiment of the present disclosure, the response message of the AF is transmitted directly from the AF to the SMF or is transmitted to the SMF through a Network Exposure Function (NEF), and does not go through a Policy Control Function (PCF). It may be transmitted without.

According to an embodiment of the present disclosure, the notification is at least one of an early notification or a late notification, and the early notification is performed before a new path between the AF and the terminal is established. The AF is transmitted through the AF, and the rate notification may be transmitted through the AF after a new path between the AF and the terminal is established.

According to an embodiment of the present disclosure, the notification is an early notification, and the step of controlling the change of the path between the AF and the terminal is based on the information on whether or not the change of the UPF is allowed, based on the predetermined It may include the step of not changing the UPF for a period of time.

According to an embodiment of the present disclosure, the notification is a rate notification, and the step of controlling the change of the path between the AF and the terminal is based on the information on whether or not the change of the UPF is allowed, based on the predetermined It may include the step of not activating the PDU session through the UPF changed over time.

According to an embodiment of the present disclosure, a session management function (SMF) for controlling a path between an application function (AF) and a terminal in a wireless communication system includes: a transceiver; Memory; And from AF, controlling the transceiver to receive an AF request message including information on whether to allow a UPF (User Plane Function) change, and determining whether a change in the UPF included in the path between the AF and the terminal is necessary. And, based on the determination result, controls the transceiver to transmit a notification including information on the UPF change to the AF, and for a predetermined time based on the information on whether the UPF change is allowed or not. It may include at least one processor that determines whether to wait to receive a response message from the AF, and controls a change in a path between the AF and the terminal including the UPF based on the determination result.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

In describing the embodiments, descriptions of technical contents well known in the technical field to which the present disclosure pertains and which are not directly related to the present disclosure will be omitted. This is to more clearly and without obscuring the subject matter of the present disclosure by omitting unnecessary description.

For the same reason, some components in the accompanying drawings are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. The same reference numbers are assigned to the same or corresponding elements in each drawing.

Advantages and features of the present disclosure, and a method of achieving them will be apparent with reference to embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the present embodiments allow the present disclosure to be complete, and those skilled in the art to which the present disclosure pertains. It is provided to fully inform a person of the scope of the present disclosure, and the present disclosure is only defined by the scope of the claims. The same reference numerals refer to the same components throughout the specification.

At this time, it will be understood that each block of the process flow chart drawings and combinations of the flow chart drawings can be performed by computer program instructions. These computer program instructions may be mounted on a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, so that instructions performed through a processor of a computer or other programmable data processing equipment are described in flowchart block (s). It creates a means to perform functions. These computer program instructions can also be stored in computer readable or computer readable memory that can be oriented to a computer or other programmable data processing equipment to implement a function in a particular way, so that computer readable or computer readable memory It is also possible for the instructions stored in to produce an article of manufacture containing instructions means for performing the functions described in the flowchart block (s). Since computer program instructions may be mounted on a computer or other programmable data processing equipment, a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer to generate a computer or other programmable data. It is also possible for instructions to perform processing equipment to provide steps for executing the functions described in the flowchart block (s).

Also, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing the specified logical function (s). It should also be noted that in some alternative implementations, it is also possible that the functions mentioned in the blocks occur out of sequence. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or it is also possible that the blocks are sometimes executed in reverse order according to a corresponding function.

At this time, the term '~ unit' used in this embodiment means a hardware component such as software or an FPGA or an ASIC, and '~ unit' performs certain roles. However, '~ wealth' is not limited to software or hardware. The '~ unit' may be configured to be in an addressable storage medium or may be configured to reproduce one or more processors. Thus, as an example, '~ unit' refers to components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, and procedures. , Subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, database, data structures, tables, arrays, and variables. The functions provided within components and '~ units' may be combined into a smaller number of components and '~ units', or further separated into additional components and '~ units'. In addition, the components and '~ unit' may be implemented to play one or more CPUs in the device or secure multimedia card. Also, in the embodiment, '~ unit' may include one or more processors.

In describing the embodiments of the present disclosure in detail, the wireless access network New RAN (NR) on the 5G mobile communication standard specified by 3GPP, a standardization organization for mobile communication standards, and the packet core (5G System, or 5G Core Network, or core network), or NG Core: Next Generation Core) is the main target, but the main subject matter of the present disclosure can be applied to other communication systems having similar technical backgrounds with a slight modification within a range not significantly outside the scope of the present disclosure. It will be possible at the discretion of those skilled in the technical field of the present disclosure.

For convenience of description below, some terms and names defined in 3GPP (3rd Generation Partnership Project Long Term Evolution) standard (5G, NR, LTE or similar system standard) may be partially used. However, the present disclosure is not limited by the terms and names, and may be equally applied to systems conforming to other standards.

In addition, terms used to identify a connection node (node) used in the following description, a term referring to a network object (network entity), a term referring to a message, a term referring to an interface between network entities, various identification information Terms referring to them are exemplified for convenience of explanation. Therefore, it is not limited to the terms used in the present disclosure, and other terms indicating objects having equivalent technical meanings may be used.

In the following description of the present disclosure, when it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the subject matter of the present disclosure, the detailed description will be omitted. Hereinafter, an embodiment of the present disclosure will be described with reference to the accompanying drawings.

One embodiment of the present disclosure relates to a situation in which a terminal is provided with a service from a MEC when a 5G or New Radio (NR) mobile communication network system and a mobile edge computing (MEC) are connected. When a terminal is provided with a service through a MEC, data transmission and reception between the terminal and the MEC may be performed through a 5G mobile communication network and some external transmission networks. The terminal transmits and receives data through radio communication with a base station (Radio Access Network, RAN), and the RAN is data externally located through a user plane function (UPF) which is a component of the 5G Core Network (5GC). It may have a path for transmitting and receiving data through a data network (hereinafter referred to as DN). At this time, the 5GC that manages these connections are AMF (Access and Mobility Function), UPF, PCF (Policy Control Function), SMF (Session Management Function), UDR / UDM (User Data Repository / User Data Management), Network exposure function (NEF) may be included. These components can be involved to control the communication procedure for control.

In a mobile communication system, a base station (hereinafter referred to as a RAN), some components of a 5G core network (hereinafter, 5GC) connected according to the movement of a terminal, or a change in a protocol data unit (PDU) session may occur according to a handover procedure defined in 3GPP. .

1 is a diagram illustrating a network structure and an interface of a wireless communication system according to an embodiment.

More specifically, FIG. 1 is a diagram illustrating a relationship between a terminal for receiving a service through a MEC, a 5G mobile communication system, an MEC node and an AF (Application Function, MEC Orchestrator) for control. Referring to FIG. 1, a network structure and interface connected to a user equipment (hereinafter referred to as UE) may include RAN, UPF, DN, AMF, SMF, PCF, UDM / UDR, NEF and AF.

2 to 4 are diagrams for explaining each situation of handover that may occur according to the movement of the terminal according to the embodiment. At this time, management and control of the PDU session for determining the change of the UPF or transferring data may be performed through procedures related to AMF, PCF, and UDM / UDR that can help the operation of 5GC SMF and SMF.

2 is a diagram illustrating a handover situation according to an embodiment. More specifically, FIG. 2 shows a handover situation without changing the PDU session. Referring to FIG. 2, when a handover occurs according to the movement of the terminal, a change occurs in RAN 1 to RAN 2 for a RAN in charge of a radio section, but a UPF that transmits data in 5GC does not change the scenario. Is shown.

3 is a diagram illustrating a handover situation according to an embodiment. More specifically, FIG. 3 shows a scenario in which the PDU session is changed but connected to the same MEC node. Referring to FIG. 3, when a change of a RAN and a change of a UPF occur together according to the movement of a terminal, a scenario in which the existing UPF1 and UPF2 can communicate with a MEC 1 node providing a service is illustrated.

4 is a diagram illustrating a handover situation according to an embodiment. Referring to FIG. 4, a scenario is illustrated in which a change in the RAN and UPF is accompanied with a change in a MEC node providing a service as the terminal moves. At this time, the terminal may receive the service from the MEC 1 node from the MEC 1 node after the handover occurs. At this time, RAN2 may be able to connect to UPF1, which was previously transmitting data.

In the present disclosure, in the case of the scenario of FIG. 2, there may be no change in the PDU session and the PDU session anchor that distinguishes the connection between the UE and the DN in 5GC. In this case, when a handover occurs, connection of the service may be continued due to the internal operation of 5GC.

Meanwhile, in the situations corresponding to the scenarios of FIGS. 3 and 4, the transfer to the new UPF is all necessary, and at this time, the address of the externally visible terminal, that is, the address of the PDU session anchor may be changed. In this situation, the MEC node located outside may change the address of the terminal and newly establish a connection to the service, so that the service may be disconnected. In addition, in the scenario of FIG. 4, since the MEC providing the service is changed, an additional procedure for transferring traffic to / from the UE from MEC1 to MEC2 in 5GC may be required. At this time, as a method to assist the support for the MEC transfer, L2 (Layer 2) or L3 (Layer 3) based tunneling protocols VXLAN (Virtual Extensible Local Area Network), NVGRE (Network Virtualization using Generic Routing Encapsulation), Protocols such as LISP (Locator Identifier Separation Protocol) may be supported through a terminal and a MEC node or proxy servers located between them.

Meanwhile, in 3GPP, in order to support MEC and other vertical services, AF influence on traffic routing functions are defined in TS 23.501 and TS 23.502, which request to control specific network traffic from an application function (AF) located outside 5GS.

One embodiment of the related procedure is described with reference to FIG. 5, wherein the factors that AF delivers through NEF are described with reference to Table 1. Through this function, AF can request a traffic path to send traffic generated from a terminal using its own service to a specific DNN. At this time, conditions and additional information related to time and place can be delivered to 5GC. In an embodiment, AF is an event generated when a PDU session requesting to subscribe to an event is additionally created / deleted, a DNA Access Identifier (DNAI) change, an SMF receives an AF notification, and a PDU session satisfies a specific condition. You can get a notice about. At this time, the notification may be divided into an early notification sent before the SMF performs a specific operation and a late notification sent after performing a specific operation. The procedure for sending the above-described notification is described with reference to FIG. 6.

As described above, Table 1 is a table showing AF transfer factors used in the AF Influence on Traffic Routing procedure.

[Table 1]

Hereinafter, in the present disclosure, in each of the above-described situations, a specific embodiment of a method of preventing a service provided by a terminal from being disconnected when a MEC node is transferred is described.

[First Example]

The first embodiment of the present disclosure relates to a method for solving a service disconnection due to a change in the address of a terminal on a group MEC node due to a change in UPF in the scenario of FIG. 3. According to the scenario of FIG. 3, the RAN that communicates with the terminal may be moved according to the movement of the terminal, and the UPF may be transferred together with the transfer of the RAN. At this time, the UPF transfer condition is made in accordance with the internal management policy when the transfer between RAN 2 and UPF 1 is not allowed due to other reasons when the transfer to RAN 2 does not belong to the service area of the existing UPF 1 It may include cases. The present exemplary embodiment is targeted to a case where it is possible to know a case in which UPF needs to be changed in the handover preparation process of the RAN (eg, N2 based handover).

According to this embodiment, in the process of moving the PDU session from UPF 1 to UPF 2 by RAN handover, the UE is simultaneously used for UPF 1 and UPF 2 using I-UPF using UL CL (Uplink Classifier). The process of migrating UPF through a method of maintaining this connection may be proposed. In addition, the MEC is an entity located outside the 5GC and cannot be controlled by the 5GC, and re-configuration may occur due to the change of the UPF and the address change of the UE. Therefore, if data is sent through UPF 2 before the resetting is completed, data loss may occur. In this embodiment, a method of utilizing a certain waiting time to prevent this is proposed. FIG. 7 is a diagram illustrating a 5GC data transmission path for communication between a UE and MEC to which the present disclosure is applied.

In one embodiment, when sending an AF influence on traffic routing request, AF may send a reconfiguration time in addition to the factors defined in Table 1. This reset time is the time it takes to change the MEC internal settings for continuous service provision within the MEC when the UPF is changed. It can be used by setting the value based on empirical knowledge or expectations. In addition, the reset time can be calculated by including the setting of an intermediate entity, such as a gateway or proxy, that may be located in a path through which data is transmitted from UPF to MEC as well as the MEC. That is, the reset time may refer to a time required for the MEC 'according to the UPF change and the reset of the affected entity. Table 2 shows an embodiment of the AF influence on traffic routing factor including the reset time added to the factor in Table 1.

[Table 2]

8 is a diagram illustrating a procedure for transferring UPF according to the present embodiment.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may add and send a newly added reset time to the request factor. Thereafter, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, RAN 1 and 2 can detect that a handover occurs from RAN 1 to RAN 2 by the movement of the terminal. Accordingly, a handover preparation procedure may be performed.

In step 2, if the change of the UPF can be detected at 5GC (eg, N2 based handover), the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be transmitted for use in AF for identification of the UE, and GPSI, external ID External ID, or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Based on this, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 3, the handover procedure between RANs can be completed. At this time, the RAN connected to the terminal may be transferred from RAN1 to RAN2. In addition, I-UPF insertion may occur. At this time, the I-UPF may be able to connect to RAN 1 and RAN 2 simultaneously. Generation of the I-UPF and connection with RAN 1 are also possible in step 1, but connection with RAN 2 can be performed in step 3. Thereafter, communication between the UE and the MEC may be performed through RAN 2, I-UPF, and UPF 1.

In step 4, the SMF may decide to insert the UPF2 to optimize the data transmission path and select the destination UPF.

In step 5, the SMF can establish a connection with UPF 2 and set UPF 2 so that data can be transferred to the I-UPF.

In step 6, after the SMF is connected to the UPF 2, the AFI can transmit the address of the GPSI, the UE UPF2 for the identification of the terminal to the AF. At this time, the address of UPF 1 can also be passed to AF.

In step 6-1, the AF received the notification from the SMF may inform the MEC node that the address of the UE can be changed. In addition, the AF may reset an existing connection using a new address, that is, a terminal address assigned in UPF 2, for a connection with a UE corresponding to GPSI.

When data generated in the terminal is transmitted through the UPF 2 roll while step 6-1 is performed, a loss may occur. Therefore, in order to prevent this phenomenon, in step 7, data generated in the terminal may be transmitted through the existing UPF 1. The SMF may wait for the time required for the reset received from AF in step 0.

In step 8, the QoS flow corresponding to the UE receiving the service in UPF 1 may be transferred to UPF 2. In addition, the SMF can update the I-UPF so that data generated at the terminal is delivered to the MEC through UPF 2.

In step 9, the SMF may disconnect the I-UPF and UPF 1, and reset UPF 2 and RAN 2 to enable direct data transfer.

[Second Example]

9 is a view for explaining a procedure for responding to a case in which the UPF change is not known (eg, Xn-based handover) in the preparation of the RAN handover in the first embodiment described above.

In step 1, RAN 1 and 2 detect that handover is generated from RAN 1 to RAN 2 by the movement of the terminal, and may perform a handover preparation procedure.

In step 2, when the handover procedure between the RANs is completed, the RAN connected to the terminal may be transferred from RAN1 to RAN2. In addition, I-UPF insertion may occur. At this time, the I-UPF may need to be able to connect simultaneously with RAN 1 and RAN 2. Generation of the I-UPF and connection to RAN 1 are also possible in step 1, but connection to RAN 2 can be performed in this step. Thereafter, communication between the UE and the MEC may be performed through RAN 2, I-UPF, and UPF 1.

In step 3, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may transmit the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally transmit the location of the current UE. GPSI may be used to identify the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE is a factor that is selectively transmitted to AF to optimize the path between DNAI and DN. Based on this, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 4, the SMF can determine the insertion of UPF2 to optimize the data delivery path and select the destination UPF.

In step 5, the SMF can establish a connection with UPF 2 and set UPF 2 so that data can be transferred to the I-UPF.

In step 6, after the SMF is connected to the UPF 2, the AFI can transmit the address of the GPSI, the UE UPF2 for the identification of the terminal to the AF. At this time, the address of UPF 1 can also be passed to AF.

In step 6-1, the AF received the notification from the SMF may inform the MEC node that the address of the UE can be changed. In addition, AF enables a connection with a UE corresponding to GPSI to re-establish an existing connection using a new address, that is, a terminal address assigned in UPF 2.

Loss may occur when data generated at the terminal is transmitted through UPF 2 while step 6-1 is being performed. Therefore, in order to prevent this phenomenon, in step 7, data generated in the terminal may be transmitted through the existing UPF 1. The SMF may wait for the time required for the reset received from AF in step 0.

In step 8, the QoS flow corresponding to the UE receiving the service in UPF 1 may be transferred to UPF 2. In addition, the SMF can update the I-UPF so that data generated at the terminal is delivered to the MEC through UPF 2.

In step 9, the SMF may disconnect the I-UPF and UPF 1 and reset the UPF 2 and RAN 2 so that direct data transfer is possible.

[Third Example]

10 is a view for explaining a method and procedure for supporting the transfer corresponding to FIG. 4. In an embodiment, this procedure may be a scenario in which a change in the RAN, a change in the UPF, and a change in the MEC occur simultaneously when the destination is moved from MEC1 to MEC2 by the movement of the terminal in the first embodiment described above. have.

At this time, for a time required before MEC, communication with MEC 2 through UPF 2 may not be activated. When UPF 2 is prepared and the data of the terminal is transmitted, data loss may occur because MEC 2 is not prepared. Therefore, it is necessary for the MEC to notify the SMF of the previous time, and it can be performed by updating the existing AF influence on traffic routing (or updating the existing AF influence on traffic routing) or re-sending the AF influence on traffic routing for the specific terminal. Can. At this time, AF can send the migration time in addition to the request. Table 3 is a table showing the factors that can be used in the request.

[Table 3]

FIG. 11 is a diagram showing a transfer procedure of UPF according to the present embodiment.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may add and send a newly added reset time to the request factor. Thereafter, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, RAN 1 and 2 detect that a handover is generated from RAN 1 to RAN 2 by the movement of the terminal, and thus a handover preparation procedure may be performed.

In step 2, if it is possible to detect a change in the UPF at 5GC (eg, N2 based handover), the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Based on this, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 3, the handover procedure between RANs can be completed. At this time, the RAN connected to the terminal may be transferred from RAN1 to RAN2. In addition, I-UPF insertion may occur. At this time, the I-UPF may be able to connect to RAN 1 and RAN 2 simultaneously. Generation of the I-UPF and connection with RAN 1 are also possible in step 1, but connection with RAN 2 can be performed in step 3. Thereafter, communication between the UE and the MEC may be performed through RAN 2, I-UPF, and UPF 1.

In step 4, the SMF may decide to insert the UPF2 to optimize the data transmission path and select the destination UPF.

In step 5, the SMF can establish a connection with UPF 2 and set UPF 2 so that data can be transferred to the I-UPF.

In step 6, after the SMF is connected to the UPF 2, the AFI can transmit the address of the GPSI, the UE UPF2 for the identification of the terminal to the AF. At this time, the address of UPF 1 can also be passed to AF.

In step 6-1, the AF received the notification from the SMF may inform the MEC node that the address of the UE can be changed. In addition, the AF may reset an existing connection using a new address, that is, a terminal address assigned in UPF 2, for a connection with a UE corresponding to GPSI.

Loss may occur when data generated at the terminal is transmitted through UPF 2 while step 6-1 is being performed. Therefore, in order to prevent this phenomenon, in step 7, data generated in the terminal may be transmitted through the existing UPF 1. The SMF may wait for the time required for the reset received from AF in step 0.

In step 8, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE's service provision from MEC 1 to MEC 2, and calculate the time required for the necessary transfer. AF can then send new AF influence on traffic routing or update existing requests (see Table 3). At this time, the AF can transmit the time previously required together. Step 8 may optionally be provided.

In step 8-1, if the previous time is obtained through step 8, the SMF may wait for the previous time.

In step 9, QoS flow corresponding to the UE receiving service in UPF 1 may be transferred to UPF 2. In addition, the SMF can update the I-UPF so that data generated at the terminal is delivered to the MEC through UPF 2.

In step 10, the SMF can disconnect the I-UPF and UPF 1 and reset the UPF 2 and RAN 2 to enable direct data transfer.

[Example 4]

12 is a view for explaining a procedure for responding to a case in which the UPF change is not known (eg, Xn-based handover) in the handover preparation process of the RAN in the third embodiment described above.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may add and send a newly added reset time to the request factor. Thereafter, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, RAN 1 and 2 detect that handover is generated from RAN 1 to RAN 2 by the movement of the terminal, and may perform a handover preparation procedure.

In step 2, when the handover procedure between the RANs is completed, the RAN connected to the terminal may be transferred from RAN1 to RAN2. In addition, I-UPF insertion may occur. At this time, the I-UPF may need to be able to connect simultaneously with RAN 1 and RAN 2. Generation of the I-UPF and connection to RAN 1 are also possible in step 1, but connection to RAN 2 can be performed in this step. Thereafter, communication between the UE and the MEC may be performed through RAN 2, I-UPF, and UPF 1.

In step 3, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may transmit the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally transmit the location of the current UE. GPSI may be used to identify the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE is a factor that is selectively transmitted to AF to optimize the path between DNAI and DN. Based on this, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 4, the SMF can determine the insertion of UPF2 to optimize the data delivery path and select the destination UPF.

In step 5, the SMF can establish a connection with UPF 2 and set UPF 2 so that data can be transferred to the I-UPF.

In step 6, after the SMF is connected to the UPF 2, the AFI can transmit the address of the GPSI, the UE UPF2 for the identification of the terminal to the AF. At this time, the address of UPF 1 can also be passed to AF.

In step 6-1, the AF received the notification from the SMF may inform the MEC node that the address of the UE can be changed. In addition, AF enables a connection with a UE corresponding to GPSI to re-establish an existing connection using a new address, that is, a terminal address assigned in UPF 2.

Loss may occur when data generated at the terminal is transmitted through UPF 2 while step 6-1 is being performed. Therefore, in order to prevent this phenomenon, in step 7, data generated in the terminal may be transmitted through the existing UPF 1. The SMF may wait for the time required for the reset received from AF in step 0.

In step 8, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE's service provision from MEC 1 to MEC 2, and calculate the time required for the necessary transfer. AF can then send new AF influence on traffic routing or update existing requests (see Table 3). At this time, the AF can transmit the time previously required together. Step 8 may optionally be provided.

In step 8-1, the SMF can wait for the previous time.

In step 9, QoS flow corresponding to the UE receiving service in UPF 1 may be transferred to UPF 2. In addition, the SMF can update the I-UPF so that data generated at the terminal is delivered to the MEC through UPF 2.

In step 10, the SMF may disconnect the I-UPF and UPF 1, and reset UPF 2 and RAN 2 to enable direct data transfer.

[Example 5]

13 is a view for explaining a method and procedure for supporting the transfer corresponding to FIG. 4. The fifth embodiment of the present disclosure is applied to a procedure for supporting Session and Service Continuity (SSC), which is a method for supporting continuity of session and service in 5GC. In particular, this embodiment may be in accordance with the SSC mode 2 method, a process in which the session is terminated and a new order is established. Based on the existing 5GC SSC mode 2 procedure, if the session is disconnected and newly established according to whether the UPF is prepared considering only the situation of the 5GC, a disconnection of the service may occur because the MEC has not been transferred yet. In addition, in the case of MEC, since the address of the changed UE terminal is not known, it may be necessary to start a new service by recognizing it as a new terminal if the application does not support continuity of service. In order to solve this problem, according to the present embodiment, information related to a change of the terminal is transmitted to the MEC, and the MEC can transmit the time required before the MEC when the transfer is required.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may add and send a newly added reset time to the request factor. Thereafter, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF may recognize that the UPF needs to be changed according to the movement of the terminal through internal policy and AF request.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 2-1, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2, and calculate the time required for the necessary transfer. AF can then send new AF influence on traffic routing or update existing requests (see Table 3). At this time, the AF can transmit the time previously required together. Step 2-1 may optionally be provided.

In step 3, the SMF can wait for the AF influence on traffic routing request MEC reset time (Table 3).

In step 4, the SMF can wait for the MEC reset time and receive an AF influence on traffic routing request from AF through step 2-1. If not, you can proceed to the next step. Step 4 may optionally be provided.

In step 4-1, if an AF influence on traffic routing request is received, the SMF can recognize that there is a time required for the MEC to prepare and wait for that time.

In step 5, the existing PDU session may be released according to the SSC Mode 2 procedure.

In step 6, a new PDU session may be created according to the SSC Mode 2 procedure.

In step 7, the SMF may inform the AF of the new UE's address. At this time, the SMF may enable the connection with the UE corresponding to the GPSI to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2. Additionally, an existing UE address may be delivered together.

In step 7-1, the AF may change the service connection by using the new address of the received UE.

[Example 6]

14 is a view for explaining a method and procedure for supporting the transfer corresponding to FIG. 4. More specifically, FIG. 14 is a diagram for explaining a method of using SSC Mode 3 in the above-described fifth embodiment. SSC Mode 3 follows the sequence of creating a new connection first and then releasing the existing connection to transfer the PDU session.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may add and send a newly added reset time to the request factor. Thereafter, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF can recognize through the policy and AF request that the UPF needs to be changed according to the movement of the terminal.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 2-1, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2, and calculate the time required for the necessary transfer. AF can then send new AF influence on traffic routing or update existing requests (see Table 3). At this time, the AF can transmit the time previously required together. Step 2-1 may optionally be provided.

In step 3, the SMF may wait for the AF influence on traffic routing request MEC reset time (Table 3).

In step 4, the SMF can wait for the MEC reset time and receive an AF influence on traffic routing request from AF through step 2-1. If not, you can proceed to the next step. Step 4 can optionally be provided.

In step 4-1, if an AF influence on traffic routing request is received, the SMF can recognize that there is a time required for the MEC to prepare and wait for that time.

In step 5, a new PDU session may be created according to the SSC Mode 3 procedure.

In step 6, the SMF may inform the AF of the new UE's address. At this time, the SMF may enable the connection with the UE corresponding to the GPSI to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2. Additionally, an existing UE address may be delivered together.

In step 6-1, the AF may change the service connection by using the new address of the received UE.

In step 7, the PDU session may be changed according to the SSC Mode 3 procedure and the existing PDU session may be released.

[Example 7]

15 is a view for explaining a method and procedure for supporting the transfer corresponding to FIG. 4. In the seventh embodiment of the present disclosure, in using the SSC Mode 3 in the above-described fifth embodiment, the UE uses the new PDU session by notifying the UE of the time for the SMF to change the PDU session for the previous time. It is related to the case of adjusting the viewpoint.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may add and send a newly added reset time to the request factor. Thereafter, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF can recognize through the policy and AF request that the UPF needs to be changed according to the movement of the terminal.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 2-1, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2, and calculate the time required for the necessary transfer. AF can then send new AF influence on traffic routing or update existing requests (see Table 3). At this time, the AF can transmit the time previously required together. Step 2-1 may optionally be provided.

In step 3, the SMF can wait for the AF influence on traffic routing request MEC reset time (Table 3).

In step 4, the SMF can wait for the MEC reset time and receive an AF influence on traffic routing request from AF through step 2-1. If not, you can proceed to the next step. Step 4 can optionally be provided.

In step 5, a new PDU session is created according to the SSC Mode 3 procedure. At this time, the UE may be informed of the required time before the MEC, and may wait for the required time in step 7.

In step 6, the SMF may inform the AF of the new UE's address. At this time, the SMF may enable the connection with the UE corresponding to the GPSI to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2. Additionally, an existing UE address may be delivered together.

In step 6-1, the AF may change the service connection by using the new address of the received UE.

In step 7, if an AF influence on traffic routing request is received, the UE may recognize that there is a time required for the MEC to prepare and wait for that time.

In step 8, it is possible to change the PDU session according to the SSC Mode 3 procedure and release the existing PDU session.

[Example 8]

16 is a view for explaining a method and procedure for supporting the transfer corresponding to 4. The eighth embodiment of the present disclosure relates to a procedure for dynamically changing network traffic of a terminal to a specific MEC in a situation where AF receives and reports location information of the terminal through SMF or PCF. At this time, the AF receiving and reporting the location of the terminal in real time can dynamically perform AF influence on traffic routing request and the time it takes for the MEC of a specific location to be transferred or prepared to perform a procedure for maintaining continuity of service. This embodiment illustratively relates to a case of using SSC Mode2 when using MEC2 in the existing MEC1.

In step 0, the AF may request an event subscription to the PCF or SMF through the NEF to view and receive the location of a specific terminal. The UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF can report the location of the terminal to the AF through the NEF according to the movement of the terminal. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. The location of the UE may be obtained by receiving an AMF event by the SMF or PCF. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 2, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE's service provision from MEC 1 to MEC 2, and calculate the time required for the necessary transfer.

In step 3, AF can then send a new AF influence on traffic routing (see Table 3). At this time, the AF can transmit the time previously required together.

In step 4, the SMF may wait for the AF influence on traffic routing request MEC reset time (Table 3).

In step 5, the existing PDU session may be released according to the SSC Mode 2 procedure.

In step 6, a new PDU session may be created according to the SSC Mode 2 procedure.

In step 7, the SMF may inform the AF of the new UE's address. At this time, the SMF may enable the connection with the UE corresponding to the GPSI to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2. Additionally, an existing UE address may be delivered together.

In step 7-1, the AF may change the service connection by using the new address of the received UE.

[Example 9]

17 is a view for explaining a method and procedure for supporting the transfer corresponding to FIG. 4. The ninth embodiment of the present disclosure relates to the case where SSC Mode3 is used in the eighth embodiment.

In step 0, the AF may request the PCF or SMF to subscribe to the event through the NEF so that the location of a specific terminal can be reported and received. The UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF can report the location of the terminal to the AF through the NEF according to the movement of the terminal. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. The location of the UE may be obtained by receiving an AMF event by the SMF or PCF. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In step 2, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE's service provision from MEC 1 to MEC 2, and calculate the time required for the necessary transfer.

In step 3, AF can then send a new AF influence on traffic routing (see Table 3). At this time, the AF can transmit the time previously required together.

In step 4, a new PDU session may be created according to the SSC Mode 3 procedure.

In step 5, the SMF may inform the AF of the new UE's address. At this time, the SMF may enable the connection with the UE corresponding to the GPSI to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2. Additionally, an existing UE address may be delivered together.

In step 6, the AF may change the service connection by using the new address of the received UE.

In step 7, during the previous time received in step 3, entities included in the network may wait. At this time, the waiting entity may be a terminal (step 7a) or a 5GC (step 7b).

In step 8, the PDU session may be changed according to the SSC Mode 3 procedure and the existing PDU session may be released.

[Example 10]

The tenth embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4. In the tenth embodiment, a procedure for supporting Session and Service Continuity (SSC), which is a method for supporting continuity of session and service in 5GC, is applied.

In an embodiment of the present disclosure, AF may prevent the UPF from being changed when the AF is not prepared by explicitly transmitting whether or not the UPF change is allowed when the initial influence on traffic routing request is delivered. Thereafter, the AF can control the UPF change by dynamically sending an AF influence on traffic routing request to a specific terminal while the UPF change is ready. In the present disclosure, "change of the UPF" may include configuring a new UPF or activating a connection to the new UPF. For example, "change of UPF" may include setting a new UPF after the SMF sends an early notification to AF. Or, "change of UPF" may include activating the connection to the new UPF after the SMF sets a new UPF and sends a late notification to AF. Accordingly, the operation of determining whether the SMF waits for the response of the AF in accordance with the "allow or not change of the UPF" can be applied to both the procedure for fast notification and the procedure for late notification.

Table 4 is a table explaining the factors used in this example. In an embodiment, whether to change the UPF (Allow reallocation of UPF) and the migration time (Migration Time) may be newly added to the AF influence on traffic routing request defined in the existing TS 23.501. In an embodiment, each factor can be used separately. Whether the UPF is changed may indicate whether the PCF or the SMF is allowed to transfer the PDU session when the UPF needs to be changed by the 5GC internal policy. If this parameter is set to not allow, the SMF may not change the UPF even if the UPF change is required by the internal policy. However, even in such a case, the SMF may continuously perform an operation of notifying the AF that a UPF change is necessary.

In an embodiment, the previous time is a factor used when the AF responds to the SMF through the PCF after receiving the notification related to the UPF change, and may indicate a time taken to prepare for the transfer of a specific UE. Therefore, the SMF can perform the transfer of the PDU session in consideration of the previous time of the specific UE newly received from the AF. This embodiment illustratively relates to a case of using SSC Mode2 when using MEC2 in the existing MEC1.

[Table 4]

18 is a diagram illustrating a method of changing a PDU session transfer procedure according to the tenth embodiment according to an AF request.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may explicitly send an UPF change (Allow reallocation of UPF). If the AF request is successfully reflected, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF may recognize that the UPF needs to be changed according to the movement of the terminal through internal policy and AF request.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

At this time, if the UPF change is allowed in the initially received AF request, the SMF can immediately execute step 5. If not allowed, the SMF can wait until it receives a new AF request from AF. At this time, the maximum value of the waiting time may be determined by an internal policy.

In step 2-1, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2, and calculate the time required for the necessary transfer.

In step 3, AF can send a new AF influence on traffic routing or update an existing request (Table 4). At this time, the AF can transmit the time previously required together. When a new AF request is sent so that other UEs are not affected, AF may use a specific UE identifier (Target UE Identifier) to limit the target. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 4, the SMF can wait for the time before the MEC. At this time, considering the time it takes to operate the SSC Mode later, the SMF may wait a shorter time than the previous time included in the AF request.

In step 5, the existing PDU session may be released according to the SSC Mode 2 procedure.

In step 6, a new PDU session may be created according to the SSC Mode 2 procedure.

In step 7, the SMF may inform the AF of the new UE's address. At this time, the SMF may be able to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2, in connection with a UE corresponding to GPSI. The SMF may additionally carry an existing UE address.

In step 7-1, the AF may change the service connection by using the new address of the received UE.

[Example 11]

The eleventh embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4. The eleventh embodiment relates to a method of utilizing the SSC Mode 3 procedure in the tenth embodiment described above. In an embodiment, the factor used for the AF influence on traffic routing request of the eleventh embodiment may be the same as the tenth embodiment.

19 is a diagram illustrating a method of changing a PDU session transfer procedure according to an eleventh embodiment by an AF request.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may explicitly send an UPF change (Allow reallocation of UPF). If the AF request is successfully reflected, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF may recognize that the UPF needs to be changed according to the movement of the terminal through internal policy and AF request.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

At this time, if the UPF change is allowed in the initially received AF request, the SMF may immediately execute step 5. If not allowed, the SMF can wait until it receives a new AF request from AF. At this time, the maximum value of the waiting time may be determined by an internal policy.

In step 2-1, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2, and calculate the time required for the necessary transfer.

In step 3, AF can send a new AF influence on traffic routing or update an existing request (Table 4). At this time, the AF can transmit the time previously required together. When sending a new AF request, the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 4, the SMF can wait for the time before the MEC. At this time, considering the time it takes to operate the SSC Mode later, the SMF may wait a shorter time than the previous time included in the AF request.

In step 5, a new PDU session may be created according to the SSC Mode 3 procedure. At this time, the SMF may inform the UE of the time required before the MEC, and may wait for the required time in step 7.

In step 6, the SMF may inform the AF of the new UE's address. At this time, the SMF may be able to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2, in connection with a UE corresponding to GPSI. In addition, the SMF may additionally carry the existing UE address.

In step 6-1, the AF may change the service connection by using the new address of the received UE.

In step 7, the PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.

[Example 12]

The twelfth embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4. The twelfth embodiment utilizes the SSC Mode 3 procedure in the eleventh embodiment described above, but in a waiting time of the MEC, in the method of using the Release Timer to determine when the UE creates and transfers a new PDU session. It is about. In an embodiment, the factor used for the AF influence on traffic routing request of the twelfth embodiment may be the same as the tenth embodiment.

20 is a diagram illustrating a method of changing a PDU session transfer procedure according to a twelfth embodiment according to an AF request.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may explicitly send an UPF change (Allow reallocation of UPF). If the AF request is successfully reflected, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF may recognize that the UPF needs to be changed according to the movement of the terminal through internal policy and AF request.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

At this time, if the UPF change is allowed in the initially received AF request, the SMF may immediately execute step 5. If not allowed, the SMF can wait until it receives a new AF request from AF. At this time, the maximum value of the waiting time may be determined by an internal policy.

In step 2-1, the AF may initiate the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2, and calculate the time required for the necessary transfer.

In step 3, AF can send a new AF influence on traffic routing or update an existing request (Table 4). At this time, the AF can transmit the time previously required together. When sending a new AF request, the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 4, a new PDU session may be created according to the SSC Mode 3 procedure. At this time, the SMF may inform the UE of the time required before the MEC, and may wait for the required time in step 7.

In step 5, the SMF may inform the AF of the new UE's address. At this time, the SMF may be able to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2, in connection with a UE corresponding to GPSI. The SMF may additionally carry an existing UE address.

In step 5-1, the AF may change the service connection by using the new address of the received UE.

In step 6, the terminal may wait for the previous time received from the SMF in step 4.

In step 7, the PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.

[Example 13]

The thirteenth embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4. In the thirteenth embodiment, the present disclosure applies a procedure for supporting Session and Service Continuity (SSC), which is a method for supporting continuity of session and service in 5GC.

In an embodiment of the present disclosure, AF may prevent an UPF change in a state in which AF is not prepared by explicitly transmitting whether or not an UPF change is allowed when an initial influence on traffic routing request is delivered. Thereafter, the AF can control the UPF change by dynamically sending an AF influence on traffic routing request to a specific terminal while the UPF change is ready.

Table 5 is a table explaining the factors used in this example. In an embodiment, whether to change the UPF (Allow reallocation of UPF) may be newly added to the AF influence on traffic routing request defined in the existing TS 23.501. Whether UPF is changed may indicate whether PCF or SMF is allowed to transfer such a PDU session when UPF needs to be changed according to the 5GC internal policy. If this parameter is set to not allow, the SMF may not change the UPF even if the UPF change is required by the internal policy. However, even in such a case, the SMF may continuously perform an operation of notifying the AF that a UPF change is necessary.

In the present embodiment, AF may send an AF request for a specific terminal in a state in which the transfer of resources and information necessary to continuously support the service of the specific terminal is completed. Unlike in the above-described 10th, 11th, and 12th embodiments, AF explicitly transmits the previous time to the AF influence on traffic routing request, the AF according to this embodiment sends the AF influence on traffic routing request after the transfer is completed. You can. Upon receiving this, the SMF can immediately perform the next operation for PDU session transfer. This embodiment illustratively relates to a case of using SSC Mode2 when using MEC2 in the existing MEC1.

[Table 5]

21 is a diagram illustrating a method of changing a PDU session transfer procedure according to the tenth embodiment according to an AF request.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may explicitly send an UPF change (Allow reallocation of UPF). If the AF request is successfully reflected, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF may recognize that the UPF needs to be changed according to the movement of the terminal through internal policy and AF request.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

At this time, if the UPF change is allowed in the initially received AF request, the SMF can immediately execute step 5. If not allowed, the SMF can wait until it receives a new AF request from AF. At this time, the maximum value of the waiting time may be determined by an internal policy.

In step 2-1, the AF may perform the transfer of data (for example, a virtual machine image or a service related context) necessary for the UE to provide service from MEC 1 to MEC 2.

In step 3, when the service transfer is completed, AF may send a new AF influence on traffic routing or update an existing request. When sending a new AF request, the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 4, the existing PDU session may be released according to the SSC Mode 2 procedure.

In step 5, a new PDU session may be created according to the SSC Mode 2 procedure.

In step 6, the SMF may inform the AF of the new UE's address. At this time, the SMF may be able to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2, in connection with a UE corresponding to GPSI. The SMF may additionally carry an existing UE address.

In step 6-1, the AF may change the service connection by using the new address of the received UE.

[Example 14]

The fourteenth embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4. The fourteenth embodiment relates to a method of utilizing the SSC Mode 3 procedure in the thirteenth embodiment described above. In an embodiment, the factor used for the AF influence on traffic routing request of the 14th embodiment may be the same as the 13th embodiment.

22 is a view showing a method of changing a PDU session transfer procedure according to the 14th embodiment according to an AF request.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may explicitly send an UPF change (Allow reallocation of UPF). If the AF request is successfully reflected, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 1, the PCF and the SMF may recognize that the UPF needs to be changed according to the movement of the terminal through internal policy and AF request.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and GPSI or an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

At this time, if the UPF change is allowed in the initially received AF request, the SMF can immediately execute step 5. If not allowed, the SMF can wait until it receives a new AF request from AF. At this time, the maximum value of the waiting time may be determined by an internal policy.

In step 2-1, the AF may perform the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2.

In step 3, when the service transfer is completed, AF may send a new AF influence on traffic routing or update an existing request. When sending a new AF request, the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 4, the SMF may receive a new AF influence traffic routing request from AF. At this time, a new PDU session may be created according to the SSC Mode 3 procedure.

In step 5, the SMF may inform the AF of the new UE's address. At this time, the SMF may be able to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2, in connection with a UE corresponding to GPSI. The SMF may additionally carry an existing UE address.

In step 5-1, the AF may change the service connection by using the new address of the received UE.

In step 6, the PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.

[Example 15]

The fifteenth embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4. The fifteenth embodiment additionally relates to a method of explicitly transmitting a time to wait for a PDU session change when the SMF sends a notification to the AF in the fourteenth embodiment described above. In an embodiment, the AF receiving notification related to the route change may send a response to the 5GS in two ways. The first possible response method may be a method of sending a new request or updating an existing request when the content of the existing AF influence on traffic routing is changed according to a path change of the terminal. The second possible response method may be a method of sending a response acknowledgment (Ack) when a change of an existing AF influence on traffic routing request is not required. In an embodiment, the factor used for the AF influence on traffic routing request of the fifteenth embodiment may be the same as the thirteenth embodiment.

23 is a diagram illustrating a method of changing a PDU session transfer procedure according to the fifteenth embodiment by an AF request.

In step 0, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may explicitly send an UPF change (Allow reallocation of UPF). If the AF request is successfully reflected, the UE can use the service located in MEC 1 through RAN 1 and UPF 1. In the present disclosure, "change of the UPF" may include configuring a new UPF or activating a connection to the new UPF. For example, "change of UPF" may include setting a new UPF after the SMF sends an early notification to AF. Or, "change of UPF" may include activating the connection to the new UPF after the SMF sets a new UPF and sends a late notification to AF. Accordingly, the operation of determining whether the SMF waits for the response of the AF in accordance with the "allow or not change of the UPF" can be applied to both the procedure for fast notification and the procedure for late notification.

In step 1, the PCF and the SMF may recognize that the UPF needs to be changed according to the movement of the terminal through internal policy and AF request.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

At this time, the SMF may determine whether to allow the UPF change by considering whether the UPF received in the AF request is allowed, the AF characteristics, and internal policies. If the UPF change is permitted at the SMF's discretion, the SMF can immediately implement step 5. If not allowed, the SMF can wait until it receives a new AF request from AF. At this time, the maximum value of the waiting time may be determined by an internal policy. The notification may include the time for the SMF to wait for AF's response in accordance with its internal policy.

In step 2-1, the AF may perform the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2.

In step 3a, when the service transfer is completed, AF may send a new AF influence on traffic routing or update an existing request. When sending a new AF request, the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 3b, there is no need to change the existing AF influence on traffic routing (for example, if "Allow or disallow UPF change" is "disallow", and change to "allow" is not required), NEF If and SMF supports response to a notification (ACK) according to the UPF change, AF may transmit to the SMF via ACK that it is ready for UPF 'change. In an embodiment, if it is not possible to complete step 2-1 within the waiting time of the SMF received in step 2, a negative response (NACK) may be transmitted.

Steps 3a and 3b may be selectively performed according to the determination of AF.

In step 4, the SMF may receive a new AF influence traffic routing request or response (ACK) from AF. At this time, a new PDU session may be created according to the SSC Mode 3 procedure.

In step 5, the SMF may inform the AF of the new UE's address. At this time, the SMF may be able to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2 in connection with a UE corresponding to GPSI. The SMF may additionally carry an existing UE address. Of course, as described above in step 2, the SMF, based on whether the UPF received in the AF request is allowed, immediately executes step 7 if the UPF change is allowed, or receives a response from the AF if the UPF change is not allowed. You can wait until. In addition, the SMF can spend time waiting for the response from AF according to the internal policy.

In step 5-1, the AF may change the service connection by using the new address of the received UE.

In step 6a, when the service transfer is completed, AF may send a new AF influence on traffic routing or update an existing request. When sending a new AF request, the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 6b, there is no need to change the existing AF influence on traffic routing (e.g., if "allow or not allow UPF change" is "disallow", and change to "allow" is not required), NEF If and SMF supports response to a notification (ACK) according to the UPF change, AF may transmit to the SMF via ACK that it is ready for UPF 'change. In an embodiment, if it is not possible to complete step 5-1 within the waiting time of the SMF received in step 5, a negative response (NACK) may be transmitted.

Steps 6a and 6b may be selectively performed according to the determination of AF.

In step 7, the used PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.

According to an embodiment of the present disclosure, SSC mode 2 may be used in the fifteenth embodiment. For example, in the fifteenth embodiment, step 7 may be performed continuously with step 4.

[Example 16]

The sixteenth embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4. The sixteenth embodiment includes a process in which the AF can acquire a time for the SMF to wait for an AF response in the above-described fifteenth embodiment, in the process of requesting and receiving an AF influence on traffic routing. In the embodiment, the factor used for the AF influence on traffic routing request of the sixteenth embodiment may be the same as the thirteenth embodiment.

24 is a diagram showing a method of changing a PDU session transfer procedure according to the sixteenth embodiment according to an AF request.

In step 0a, the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow. At this time, the AF may explicitly send an UPF change (Allow reallocation of UPF). If the AF request is successfully reflected, the UE can use the service located in MEC 1 through RAN 1 and UPF 1.

In step 0b, the SMF may transmit the maximum time in which the SMF waits for the response of the AF when the UPF change occurs in the response message for the AF.

In step 1, the PCF and the SMF may recognize that the UPF needs to be changed according to the movement of the terminal through internal policy and AF request.

In step 2, the SMF can send an early notification related to the UPF change to the AF. In this case, the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE. In addition, the SMF may additionally send the location of the current UE. GPSI may be used for identification of the UE in AF, and an external ID or MSISDN may be transmitted. The location of the UE may be an additional factor that is selectively sent to AF to optimize the path between DNAI and DN. Using this, AF can know whether the MEC transfer is necessary. In addition, the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.

In this case, the SMF may determine whether to allow the UPF by considering whether the UPF received in the initial AF request is allowed, the AF characteristics, and internal policies. If the UPF change is permitted at the SMF's discretion, the SMF can immediately implement step 5. If not allowed, the SMF can wait until it receives a new AF request from AF. At this time, the maximum value of the waiting time may be determined by an internal policy. If the maximum waiting time transmitted in step 0b is different, a new maximum waiting time may be included in the notification.

In step 2-1, the AF may perform the transfer of data (eg, virtual machine image, service related context) necessary for the UE to provide service from MEC 1 to MEC 2.

In step 3a, when the service transfer is completed, AF may send a new AF influence on traffic routing or update an existing request. When sending a new AF request, the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 3b, there is no need to change the existing AF influence on traffic routing (for example, if "Allow or disallow UPF change" is "disallow", and change to "allow" is not required), NEF If and SMF supports response to a notification (ACK) according to the UPF change, AF may transmit to the SMF via ACK that it is ready for UPF 'change. In an embodiment, if it is not possible to complete step 2-1 within the waiting time of the SMF received in step 2, a negative response (NACK) may be transmitted.

Steps 3a and 3b may be selectively performed according to the determination of AF.

In step 4, the SMF may receive a new AF influence traffic routing request or response (ACK) from AF. At this time, a new PDU session may be created according to the SSC Mode 3 procedure.

In step 5, the SMF may inform the AF of the new UE's address. At this time, the SMF may be able to re-establish an existing connection using a new address, for example, a terminal address assigned in UPF 2, in connection with a UE corresponding to GPSI. The SMF may additionally carry an existing UE address. Of course, as described above in step 2, the SMF, based on whether the UPF received in the AF request is allowed, immediately executes step 7 if the UPF change is allowed, or receives a response from the AF if the UPF change is not allowed. You can wait until.

In step 5-1, the AF may change the service connection by using the new address of the received UE.

In step 6a, when the service transfer is completed, AF may send a new AF influence on traffic routing or update an existing request. When sending a new AF request, the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals. In the case of an update, AF can specify the previous AF request to update using the AF transaction identifier.

In step 6b, there is no need to change the existing AF influence on traffic routing (e.g., if "allow or not allow UPF change" is "disallow", and change to "allow" is not required), NEF If and SMF supports response to a notification (ACK) according to the UPF change, AF may transmit to the SMF via ACK that it is ready for UPF 'change. In an embodiment, if it is not possible to complete step 5-1 within the waiting time of the SMF received in step 2, a negative response (NACK) may be transmitted.

Steps 6a and 6b may be selectively performed according to the determination of AF.

In step 7, the PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.

According to an embodiment of the present disclosure, SSC mode 2 may be used in the sixteenth embodiment. For example, in the sixteenth embodiment, step 7 may be performed continuously with step 4.

According to an apparatus and method according to various embodiments of the present disclosure, when a terminal using a 5G mobile communication system changes a node in a situation where a service is provided through a distributed mobile edge computing node, the service connection may not be interrupted.

In addition, through the present disclosure, vehicle terminals can seamlessly change the distributed V2X servers according to the location and network conditions of the vehicle and receive a high level of service through optimal service nodes. At this time, the vehicle terminal may be a device embedded in the vehicle, or may be a terminal attached to the vehicle, such as a smartphone or a black box. In addition, it will be readily understood by those skilled in the art that the method of moving the mobile edge cloud according to an embodiment of the present invention is applicable to vertical services other than V2X. V2X service provider (SP) according to an embodiment of the present invention may provide a service specialized in 5G.

25 is a diagram showing the structure of an entity according to an embodiment.

Referring to FIG. 25, an entity may include a transceiver 2310, a processor 2320, and a memory 2330. In the present invention, the processor 2320 may be defined as a circuit or application specific integrated circuit or at least one processor. However, the components of the entity are not limited to the above-described examples. For example, an entity may include more components or fewer components than the components described above. In addition, the transceiver 2310, the processor 2320, and the memory 2330 may be implemented as a single chip.

The transceiver 2310 may transmit and receive signals with other network entities. The transceiver 2310 may transmit system information to the terminal, for example, and may transmit a synchronization signal or a reference signal.

The processor 2320 may control the overall operation of the entity according to the embodiment proposed in the present invention. For example, the processor 2320 may control signal flow between blocks to perform the operation described with reference to the above-described drawings.

The memory 2330 may store at least one of information transmitted and received through the transceiver 2310 and information generated through the processor 2320. In addition, the memory 2330 may store control information or data included in a signal obtained from a base station. The memory 2330 may be composed of a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. Also, the memory 2330 may be configured with a plurality of memories. In one embodiment, memory 2330 may store a program to support beam-based cooperative communication.

Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

Such programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device (CD-ROM: Compact Disc-ROM), digital versatile discs (DVDs) or other forms It can be stored in an optical storage device, a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all of them. Also, a plurality of configuration memories may be included.

In addition, the program may be accessed through a communication network composed of a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), or a storage area network (SAN), or a combination thereof. It may be stored in an attachable (storage) storage device (access). Such a storage device may connect to a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may access a device that performs embodiments of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the present disclosure are expressed in singular or plural according to the specific embodiments presented. However, the singular or plural expressions are appropriately selected for the situation presented for convenience of explanation, and the present disclosure is not limited to the singular or plural components, and even the components expressed in plural are composed of singular or Even the expressed components can be composed of a plurality.

On the other hand, the embodiments of the present disclosure disclosed in the specification and drawings are merely to provide a specific example to easily describe the technical content of the present disclosure and to understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art to which other modifications based on the technical spirit of the present disclosure can be practiced. In addition, each of the above-described embodiments can be operated in combination with each other as necessary. Also, the embodiments may be applied to other systems, for example, an LTE system, a 5G or NR system, and the like.

Claims (15)

In the method for controlling the path between the application function (AF) and the terminal by the Session Management Function (SMF) in the wireless communication system, Receiving, from AF, an AF request message including information on whether to allow a UPF (User Plane Function) change; Determining whether it is necessary to change the UPF included in the path between the AF and the terminal; Based on the determination result, transmitting a notification including information regarding a change of the UPF to the AF; Determining whether to wait to receive a response message from the AF for a predetermined time based on the information on whether the UPF change is allowed; And And controlling a change of a path between the AF including the UPF and the terminal based on the determination result. According to claim 1, The above method, And if the response message is not received from the AF for the predetermined time based on the information on whether the UPF change is allowed, identifying the response of the AF as a NACK. According to claim 1, The above method, And receiving the response message to the notification from the AF, The step of receiving the response message, When MEC transfer is completed within the predetermined time, an ACK message is received from the AF, If MEC transfer is not completed within the predetermined time, a NACK message is received from the AF. According to claim 1, The predetermined time, It is the maximum waiting time to wait for the reception of the response message from the AF, The above notification, The method includes information about the predetermined time. According to claim 1, The AF response message, From the AF, it is transmitted directly to the SMF or is transmitted to the SMF through a Network Exposure Function (NEF), Method that is transmitted without going through a PCF (Policy Control Function). According to claim 1, The above notification, It is at least one of an early notification or a late notification, The early notice, It is to transmit to the AF before a new path between the AF and the terminal is established, The rate notification, And a new path between the AF and the terminal is established and then transmitted to the AF. The method of claim 6, The notification is an early notification, Controlling the change of the path between the AF and the terminal, And not changing the UPF for the predetermined time based on the information on whether the UPF is allowed to be changed. The method of claim 6, The notification is a rate notification, Controlling the change of the path between the AF and the terminal, And not activating a PDU session through the UPF changed for the predetermined time based on the information on whether the UPF is allowed to be changed. In the SMF (Session Management Function) for controlling the path between the application function (AF) and the terminal in the wireless communication system, Transceiver; Memory; And Controls the transceiver to receive an AF request message including information on whether to allow UPF (User Plane Function) change from AF, Determine whether it is necessary to change the UPF included in the path between the AF and the terminal, Based on the result of the determination, the transceiver controls the transmitting and receiving unit to transmit a notification including information on the change of the UPF to the AF, It is determined whether to wait to receive a response message from the AF for a predetermined time based on the information on whether the UPF change is allowed, And at least one processor for controlling a change of a path between the AF including the UPF and the terminal based on the determination result. The method of claim 9, The at least one processor, Control the transceiver to receive the response message to the notification from the AF, When the MEC transfer is completed within the predetermined time, the transmitter and receiver are controlled to receive an ACK message from the AF, When the MEC transfer is not completed within the predetermined time, the SMF controls the transceiver to receive a NACK message from the AF. The method of claim 9, The predetermined time, It is the maximum waiting time to wait for the reception of the response message from the AF, The above notification, SMF that includes information about the predetermined time. The method of claim 9, The AF response message, From the AF, it is transmitted directly to the SMF or is transmitted to the SMF through a Network Exposure Function (NEF), SMF that is transmitted without going through a PCF (Policy Control Function). The method of claim 9, The above notification, It is at least one of an early notification or a late notification, The early notice, It is to transmit to the AF before a new path between the AF and the terminal is established, The rate notification, SMF is to transmit to the AF after a new path between the AF and the terminal is established. The method of claim 13, The notification is an early notification, The at least one processor, Based on information on whether or not the UPF is allowed to be changed, SMF is controlled to not change the UPF for the predetermined time. The method of claim 13, The notification is a rate notification, The at least one processor, SMF that controls not to activate a PDU session through the UPF changed for the predetermined time based on information on whether the UPF is allowed to be changed.

Images