[go: up one dir, main page]

WO2020071681A1 - Procédé et appareil de prise en charge de transfert de l'informatique en périphérie mobile dans un système de communication sans fil - Google Patents

Procédé et appareil de prise en charge de transfert de l'informatique en périphérie mobile dans un système de communication sans fil

Info

Publication number
WO2020071681A1
WO2020071681A1 PCT/KR2019/012458 KR2019012458W WO2020071681A1 WO 2020071681 A1 WO2020071681 A1 WO 2020071681A1 KR 2019012458 W KR2019012458 W KR 2019012458W WO 2020071681 A1 WO2020071681 A1 WO 2020071681A1
Authority
WO
WIPO (PCT)
Prior art keywords
upf
smf
change
terminal
notification
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2019/012458
Other languages
English (en)
Korean (ko)
Inventor
한윤선
김성훈
이호연
권기석
박중신
손중제
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020190017967A external-priority patent/KR102814699B1/ko
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to CN201980065929.3A priority Critical patent/CN112806056B/zh
Priority to EP19869392.1A priority patent/EP3855801A4/fr
Priority to JP2021518577A priority patent/JP7334243B2/ja
Priority to US17/282,874 priority patent/US11825400B2/en
Publication of WO2020071681A1 publication Critical patent/WO2020071681A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • 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.
  • 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.
  • NR New Radio
  • 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, 60 gigahertz (60 GHz) band).
  • mmWave ultra-high frequency
  • FD-MIMO full dimensional multiple input / output
  • Array antenna analog beam-forming, and large scale antenna techniques have been discussed and applied to NR systems.
  • 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.
  • ACM Advanced Coding Modulation
  • FQAM Hybrid FSK and QAM Modulation
  • SSC Extended Window Superposition Coding
  • FBMC Fan Bank Multi Carrier
  • NOMA non-orthogonal multiple access
  • SCMA parse code multiple access
  • IoT Internet of Things
  • IoE Internet of Everything
  • sensing technology wired / wireless communication and network infrastructure, service interface technology, and security technology
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • 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.
  • 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.
  • M2M machine to machine
  • MTC machine type communication
  • cloud RAN cloud radio access network
  • V2X Vehicle to Everything
  • WAVE Wireless Access in Vehicular Environments
  • DSRC Dedicated Short Range Communication
  • 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.
  • FIG. 1 is a diagram illustrating a network structure and an interface of a wireless communication system according to an embodiment.
  • FIG. 2 is a diagram for describing a handover situation without change of a PDU session according to an embodiment.
  • FIG. 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 13 is a diagram illustrating a PDU session transfer procedure for connection with another MEC using SSC MODE2 according to an embodiment.
  • FIG. 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.
  • FIG. 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 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.
  • UPF user plane function
  • AF Application Function
  • 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.
  • UPF user plane function
  • 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.
  • 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.
  • 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.
  • the predetermined time is a maximum waiting time for waiting to receive a response message from the AF
  • the notification may include information about the predetermined time
  • 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.
  • NEF Network Exposure Function
  • PCF Policy Control Function
  • 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.
  • the notification is an early notification
  • 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.
  • the notification is a rate notification
  • 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.
  • 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.
  • UPF User Plane Function
  • 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).
  • 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.
  • 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.
  • ' ⁇ 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.
  • ' ⁇ 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.
  • components and ' ⁇ units' may be combined into a smaller number of components and ' ⁇ units', or further separated into additional components and ' ⁇ units'.
  • the components and ' ⁇ unit' may be implemented to play one or more CPUs in the device or secure multimedia card.
  • ' ⁇ unit' may include one or more processors.
  • the wireless access network New RAN 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.
  • 3GPP 3rd Generation Partnership Project Long Term Evolution
  • 5G, NR, LTE or similar system standard 5G, NR, LTE or similar system standard
  • present disclosure is not limited by the terms and names, and may be equally applied to systems conforming to other standards.
  • connection node 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.
  • 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.
  • a terminal 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).
  • RAN Radio Access Network
  • UPF user plane function
  • DN data network
  • 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.
  • AMF Access and Mobility Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • SMF Session Management Function
  • UDR / UDM User Data Repository / User Data Management
  • NEF Network exposure function
  • a base station hereinafter referred to as a RAN
  • 5GC 5G core network
  • PDU protocol data unit
  • FIG. 1 is a diagram illustrating a network structure and an interface of a wireless communication system according to an embodiment.
  • 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.
  • a network structure and interface connected to a user equipment may include RAN, UPF, DN, AMF, SMF, PCF, UDM / UDR, NEF and AF.
  • FIGS. 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.
  • 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.
  • FIG. 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.
  • 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.
  • FIG. 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.
  • FIG. 4 is a diagram illustrating a handover situation according to an embodiment.
  • 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.
  • the terminal may receive the service from the MEC 1 node from the MEC 1 node after the handover occurs.
  • RAN2 may be able to connect to UPF1, which was previously transmitting data.
  • connection of the service may be continued due to the internal operation of 5GC.
  • 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.
  • 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.
  • an additional procedure for transferring traffic to / from the UE from MEC1 to MEC2 in 5GC may be required.
  • L2 Layer 2
  • L3 Layer 3
  • 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.
  • 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.
  • AF can request a traffic path to send traffic generated from a terminal using its own service to a specific DNN.
  • conditions and additional information related to time and place can be delivered to 5GC.
  • 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.
  • 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.
  • Table 1 is a table showing AF transfer factors used in the AF Influence on Traffic Routing procedure.
  • 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.
  • 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.
  • 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).
  • 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.
  • AF 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.
  • 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.
  • FIG. 8 is a diagram illustrating a procedure for transferring UPF according to the present embodiment.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • the AF may add and send a newly added reset time to the request factor.
  • the UE can use the service located in MEC 1 through RAN 1 and UPF 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • step 3 the handover procedure between RANs can be completed.
  • the RAN connected to the terminal may be transferred from RAN1 to RAN2.
  • I-UPF insertion may occur.
  • 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.
  • communication between the UE and the MEC may be performed through RAN 2, I-UPF, and UPF 1.
  • the SMF may decide to insert the UPF2 to optimize the data transmission path and select the destination UPF.
  • 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.
  • 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.
  • the AF received the notification from the SMF may inform the MEC node that the address of the UE can be changed.
  • 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.
  • 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.
  • step 8 the QoS flow corresponding to the UE receiving the service in UPF 1 may be transferred to UPF 2.
  • the SMF can update the I-UPF so that data generated at the terminal is delivered to the MEC through UPF 2.
  • the SMF may disconnect the I-UPF and UPF 1, and reset UPF 2 and RAN 2 to enable direct data transfer.
  • FIG. 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.
  • the UPF change is not known (eg, Xn-based handover) in the preparation of the RAN handover in the first embodiment described above.
  • 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.
  • step 2 when the handover procedure between the RANs is completed, the RAN connected to the terminal may be transferred from RAN1 to RAN2.
  • I-UPF insertion may occur.
  • 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.
  • communication between the UE and the MEC may be performed through RAN 2, I-UPF, and UPF 1.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may transmit the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the SMF can determine the insertion of UPF2 to optimize the data delivery path and select the destination UPF.
  • 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.
  • 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.
  • the AF received the notification from the SMF may inform the MEC node that the address of the UE can be changed.
  • 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.
  • 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.
  • step 8 the QoS flow corresponding to the UE receiving the service in UPF 1 may be transferred to UPF 2.
  • the SMF can update the I-UPF so that data generated at the terminal is delivered to the MEC through UPF 2.
  • 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.
  • 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.
  • FIG. 11 is a diagram showing a transfer procedure of UPF according to the present embodiment.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • the AF may add and send a newly added reset time to the request factor.
  • the UE can use the service located in MEC 1 through RAN 1 and UPF 1.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • step 3 the handover procedure between RANs can be completed.
  • the RAN connected to the terminal may be transferred from RAN1 to RAN2.
  • I-UPF insertion may occur.
  • 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.
  • communication between the UE and the MEC may be performed through RAN 2, I-UPF, and UPF 1.
  • the SMF may decide to insert the UPF2 to optimize the data transmission path and select the destination UPF.
  • 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.
  • 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.
  • the AF received the notification from the SMF may inform the MEC node that the address of the UE can be changed.
  • 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.
  • 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.
  • 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.
  • data eg, virtual machine image, service related context
  • step 8-1 if the previous time is obtained through step 8, the SMF may wait for the previous time.
  • step 9 QoS flow corresponding to the UE receiving service in UPF 1 may be transferred to UPF 2.
  • the SMF can update the I-UPF so that data generated at the terminal is delivered to the MEC through UPF 2.
  • the SMF can disconnect the I-UPF and UPF 1 and reset the UPF 2 and RAN 2 to enable direct data transfer.
  • FIG. 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.
  • the UPF change is not known (eg, Xn-based handover) in the handover preparation process of the RAN in the third embodiment described above.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • the AF may add and send a newly added reset time to the request factor.
  • the UE can use the service located in MEC 1 through RAN 1 and UPF 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.
  • step 2 when the handover procedure between the RANs is completed, the RAN connected to the terminal may be transferred from RAN1 to RAN2.
  • I-UPF insertion may occur.
  • 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.
  • communication between the UE and the MEC may be performed through RAN 2, I-UPF, and UPF 1.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may transmit the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the SMF can determine the insertion of UPF2 to optimize the data delivery path and select the destination UPF.
  • 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.
  • 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.
  • the AF received the notification from the SMF may inform the MEC node that the address of the UE can be changed.
  • 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.
  • 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.
  • 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.
  • data eg, virtual machine image, service related context
  • step 8-1 the SMF can wait for the previous time.
  • step 9 QoS flow corresponding to the UE receiving service in UPF 1 may be transferred to UPF 2.
  • the SMF can update the I-UPF so that data generated at the terminal is delivered to the MEC through UPF 2.
  • the SMF may disconnect the I-UPF and UPF 1, and reset UPF 2 and RAN 2 to enable direct data transfer.
  • 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.
  • SSC Session and Service Continuity
  • 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.
  • SSC mode 2 method 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.
  • the 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.
  • 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.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • the AF may add and send a newly added reset time to the request factor.
  • the UE can use the service located in MEC 1 through RAN 1 and UPF 1.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • data eg, virtual machine image, service related context
  • step 3 the SMF can wait for the AF influence on traffic routing request MEC reset time (Table 3).
  • 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.
  • 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.
  • step 5 the existing PDU session may be released according to the SSC Mode 2 procedure.
  • a new PDU session may be created according to the SSC Mode 2 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • FIG. 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.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • the AF may add and send a newly added reset time to the request factor.
  • the UE can use the service located in MEC 1 through RAN 1 and UPF 1.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • data eg, virtual machine image, service related context
  • step 3 the SMF may wait for the AF influence on traffic routing request MEC reset time (Table 3).
  • 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.
  • 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.
  • a new PDU session may be created according to the SSC Mode 3 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • step 7 the PDU session may be changed according to the SSC Mode 3 procedure and the existing PDU session may be released.
  • 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.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • the AF may add and send a newly added reset time to the request factor.
  • the UE can use the service located in MEC 1 through RAN 1 and UPF 1.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • data eg, virtual machine image, service related context
  • step 3 the SMF can wait for the AF influence on traffic routing request MEC reset time (Table 3).
  • 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.
  • step 5 a new PDU session is created according to the SSC Mode 3 procedure.
  • the UE may be informed of the required time before the MEC, and may wait for the required time in step 7.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • 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.
  • step 8 it is possible to change the PDU session according to the SSC Mode 3 procedure and release the existing PDU session.
  • 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.
  • 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.
  • 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.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • data eg, virtual machine image, service related context
  • 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.
  • step 4 the SMF may wait for the AF influence on traffic routing request MEC reset time (Table 3).
  • step 5 the existing PDU session may be released according to the SSC Mode 2 procedure.
  • a new PDU session may be created according to the SSC Mode 2 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • FIG. 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.
  • 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.
  • 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.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • data eg, virtual machine image, service related context
  • 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.
  • a new PDU session may be created according to the SSC Mode 3 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • step 7 during the previous time received in step 3, entities included in the network may wait.
  • the waiting entity may be a terminal (step 7a) or a 5GC (step 7b).
  • step 8 the PDU session may be changed according to the SSC Mode 3 procedure and the existing PDU session may be released.
  • the tenth embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4.
  • a procedure for supporting Session and Service Continuity (SSC) which is a method for supporting continuity of session and service in 5GC, is applied.
  • 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.
  • “change of the UPF” may include configuring a new UPF or activating a connection to the new UPF.
  • “change of UPF” may include setting a new UPF after the SMF sends an early notification to AF.
  • "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.
  • 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.
  • 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.
  • 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.
  • FIG. 18 is a diagram illustrating a method of changing a PDU session transfer procedure according to the tenth embodiment according to an AF request.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • 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.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • 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.
  • data eg, virtual machine image, service related context
  • 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.
  • AF may use a specific UE identifier (Target UE Identifier) to limit the target.
  • UE Identifier UE identifier
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • 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.
  • step 5 the existing PDU session may be released according to the SSC Mode 2 procedure.
  • a new PDU session may be created according to the SSC Mode 2 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • 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.
  • 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.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • 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.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • 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.
  • data eg, virtual machine image, service related context
  • 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.
  • the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals.
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • 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.
  • a new PDU session may be created according to the SSC Mode 3 procedure.
  • the SMF may inform the UE of the time required before the MEC, and may wait for the required time in step 7.
  • the SMF may inform the AF of the new UE's address.
  • 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 the existing UE address.
  • the AF may change the service connection by using the new address of the received UE.
  • step 7 the PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.
  • 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.
  • 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.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • 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.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • 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.
  • data eg, virtual machine image, service related context
  • 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.
  • the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals.
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • a new PDU session may be created according to the SSC Mode 3 procedure.
  • the SMF may inform the UE of the time required before the MEC, and may wait for the required time in step 7.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • step 6 the terminal may wait for the previous time received from the SMF in step 4.
  • step 7 the PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.
  • the thirteenth embodiment of the present disclosure is to describe a method and procedure for supporting transfer corresponding to FIG. 4.
  • 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.
  • SSC Session and Service Continuity
  • 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.
  • whether to change the 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.
  • 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.
  • 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.
  • 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.
  • 21 is a diagram illustrating a method of changing a PDU session transfer procedure according to the tenth embodiment according to an AF request.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • 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.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • 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.
  • data for example, a virtual machine image or a service related context
  • AF may send a new AF influence on traffic routing or update an existing request.
  • the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals.
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • step 4 the existing PDU session may be released according to the SSC Mode 2 procedure.
  • a new PDU session may be created according to the SSC Mode 2 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • 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.
  • 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.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • 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.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • 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.
  • data eg, virtual machine image, service related context
  • AF may send a new AF influence on traffic routing or update an existing request.
  • the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals.
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • the SMF may receive a new AF influence traffic routing request from AF.
  • a new PDU session may be created according to the SSC Mode 3 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • step 6 the PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.
  • 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.
  • 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.
  • the factor used for the AF influence on traffic routing request of the fifteenth embodiment may be the same as the thirteenth embodiment.
  • FIG. 23 is a diagram illustrating a method of changing a PDU session transfer procedure according to the fifteenth embodiment by an AF request.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • the AF may explicitly send an UPF change (Allow reallocation of UPF).
  • UPF change may include configuring a new UPF or activating a connection to the new UPF.
  • change of UPF may include setting a new UPF after the SMF sends an early notification to AF.
  • 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.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • 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.
  • data eg, virtual machine image, service related context
  • AF may send a new AF influence on traffic routing or update an existing request.
  • the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals.
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • 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.
  • NACK negative response
  • Steps 3a and 3b may be selectively performed according to the determination of AF.
  • the SMF may receive a new AF influence traffic routing request or response (ACK) from AF.
  • ACK traffic routing request or response
  • a new PDU session may be created according to the SSC Mode 3 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • 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.
  • the SMF can spend time waiting for the response from AF according to the internal policy.
  • the AF may change the service connection by using the new address of the received UE.
  • AF may send a new AF influence on traffic routing or update an existing request.
  • the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals.
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • 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.
  • NACK negative response
  • Steps 6a and 6b may be selectively performed according to the determination of AF.
  • step 7 the used PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.
  • SSC mode 2 may be used in the fifteenth embodiment.
  • step 7 may be performed continuously with step 4.
  • 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.
  • 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.
  • the AF may send an AF influence on traffic routing request to the SMF through the NEF targeting a specific terminal or service flow.
  • 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.
  • 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.
  • 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.
  • the SMF can send an early notification related to the UPF change to the AF.
  • the SMF may send the Generic Public Subscription Identifier (GPSI) of the relevant UE and the address of the current UE.
  • GPSI Generic Public Subscription Identifier
  • 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.
  • the path between the terminal and the MEC in the MEC node or the intermediate delivery network can be optimized.
  • 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.
  • 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.
  • data eg, virtual machine image, service related context
  • AF may send a new AF influence on traffic routing or update an existing request.
  • the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals.
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • 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.
  • NACK negative response
  • Steps 3a and 3b may be selectively performed according to the determination of AF.
  • the SMF may receive a new AF influence traffic routing request or response (ACK) from AF.
  • ACK traffic routing request or response
  • a new PDU session may be created according to the SSC Mode 3 procedure.
  • the SMF may inform the AF of the new UE's address.
  • 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.
  • 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.
  • the AF may change the service connection by using the new address of the received UE.
  • AF may send a new AF influence on traffic routing or update an existing request.
  • the AF may limit the target by using a specific UE identifier (Target UE Identifier), so as not to affect other terminals.
  • AF can specify the previous AF request to update using the AF transaction identifier.
  • 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.
  • NACK negative response
  • Steps 6a and 6b may be selectively performed according to the determination of AF.
  • step 7 the PDU session is changed according to the SSC Mode 3 procedure, and the existing PDU session may be released.
  • SSC mode 2 may be used in the sixteenth embodiment.
  • step 7 may be performed continuously with step 4.
  • the service connection may not be interrupted.
  • 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.
  • 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.
  • 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.
  • an entity may include a transceiver 2310, a processor 2320, and a memory 2330.
  • the processor 2320 may be defined as a circuit or application specific integrated circuit or at least one processor.
  • the components of the entity are not limited to the above-described examples.
  • an entity may include more components or fewer components than the components described above.
  • 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.
  • 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.
  • 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 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
  • CD-ROM Compact Disc-ROM
  • DVDs digital versatile discs
  • 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.
  • 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.
  • 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.
  • a separate storage device on the communication network may access a device that performs embodiments of the present disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé et un appareil de prise en charge de transfert de l'informatique en périphérie mobile dans un système de communication sans fil. Un mode de réalisation de l'invention concerne un procédé de contrôle d'un trajet entre une fonction d'application (AF) et un terminal par une fonction de gestion de session (SMF) dans un système de communication sans fil qui peut comprendre les étapes consistant à : recevoir, en provenance de l'AF, un message de requête AF comprenant des informations concernant l'autorisation ou non d'un changement dans une fonction de plan utilisateur (UPF) ; déterminer si oui ou non il est nécessaire de changer l'UPF inclus dans le trajet entre l'AF et le terminal ; transmettre une notification comprenant des informations concernant un changement de l'UPF à l'AF sur la base du résultat de la détermination ; confirmer s'il faut ou non attendre la réception d'un message de réponse de l'AF pendant un laps de temps prédéfini sur la base des informations concernant l'autorisation ou non d'un changement dans l'UPF ; et à contrôler le changement dans le trajet entre le terminal et l'AF, y compris l'UPF sur la base du résultat de confirmation.
PCT/KR2019/012458 2018-10-05 2019-09-25 Procédé et appareil de prise en charge de transfert de l'informatique en périphérie mobile dans un système de communication sans fil Ceased WO2020071681A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201980065929.3A CN112806056B (zh) 2018-10-05 2019-09-25 支持无线通信系统中的移动边缘计算转移的方法和装置
EP19869392.1A EP3855801A4 (fr) 2018-10-05 2019-09-25 Procédé et appareil de prise en charge de transfert de l'informatique en périphérie mobile dans un système de communication sans fil
JP2021518577A JP7334243B2 (ja) 2018-10-05 2019-09-25 無線通信システムにおいて、モバイルエッジコンピューティングの移転を支援する方法及びその装置
US17/282,874 US11825400B2 (en) 2018-10-05 2019-09-25 Method and apparatus for supporting transfer of mobile edge computing in wireless communication system

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR10-2018-0119321 2018-10-05
KR20180119321 2018-10-05
KR20180134449 2018-11-05
KR10-2018-0134449 2018-11-05
KR10-2019-0017967 2019-02-15
KR1020190017967A KR102814699B1 (ko) 2018-10-05 2019-02-15 무선 통신 시스템에서 모바일 엣지 컴퓨팅의 이전을 지원하는 방법 및 장치

Publications (1)

Publication Number Publication Date
WO2020071681A1 true WO2020071681A1 (fr) 2020-04-09

Family

ID=70055530

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/012458 Ceased WO2020071681A1 (fr) 2018-10-05 2019-09-25 Procédé et appareil de prise en charge de transfert de l'informatique en périphérie mobile dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2020071681A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023007611A1 (fr) * 2021-07-28 2023-02-02 株式会社Ｎｔｔドコモ Nœud de réseau et procédé de communication
JP2024532684A (ja) * 2021-08-27 2024-09-10 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 第１のノード、第２のノード、および第３のノード、通信システム、ならびにそれによって実行される、デバイスのための１つ以上の進行中の通信セッションのモビリティを処理するための方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20130076870A (ko) * 2010-08-31 2013-07-08 퀄컴 인코포레이티드 Ｌｔｅ 터널을 통한 ｅｈｒｐｄ 네트워크에서의 ｐｄｎ 컨텍스트의 생성
KR20180106998A (ko) * 2017-03-21 2018-10-01 한국전자통신연구원 등록 지역을 최적화하는 통신 시스템 및 상기 통신 시스템에서의 등록 방법
KR20180107000A (ko) * 2017-03-21 2018-10-01 한국전자통신연구원 리플렉티브 QoS를 지원하는 통신 시스템

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20130076870A (ko) * 2010-08-31 2013-07-08 퀄컴 인코포레이티드 Ｌｔｅ 터널을 통한 ｅｈｒｐｄ 네트워크에서의 ｐｄｎ 컨텍스트의 생성
KR20180106998A (ko) * 2017-03-21 2018-10-01 한국전자통신연구원 등록 지역을 최적화하는 통신 시스템 및 상기 통신 시스템에서의 등록 방법
KR20180107000A (ko) * 2017-03-21 2018-10-01 한국전자통신연구원 리플렉티브 QoS를 지원하는 통신 시스템

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 3GPP TS 23.501 V15.2.0, 19 June 2018 (2018-06-19), XP055686668 *
ANONYMOUS: "5G; Procedures for the 5G System ", 3GPP IS 23.502 VERSION 15.2.0 RELEASE 15, vol. ETSI TS 123 502 V15.2.0 (2018-06), 19 June 2018 (2018-06-19), XP009527189 *
See also references of EP3855801A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023007611A1 (fr) * 2021-07-28 2023-02-02 株式会社Ｎｔｔドコモ Nœud de réseau et procédé de communication
JP2024532684A (ja) * 2021-08-27 2024-09-10 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 第１のノード、第２のノード、および第３のノード、通信システム、ならびにそれによって実行される、デバイスのための１つ以上の進行中の通信セッションのモビリティを処理するための方法

Similar Documents

Publication Publication Date Title
WO2021187893A1 (fr) Appareil et procédé pour fournir un service d'information d'emplacement à faible latence dans un système de communication sans fil
WO2019194592A1 (fr) Procédé de prise en charge de transfert intercellulaire et station de base et noeud de réseau correspondants
WO2020218857A1 (fr) Appareil et procédé de fourniture de services de communication directe dans un système de communication sans fil
WO2021137579A1 (fr) Procédé et appareil pour régler une relocalisation de contexte d'application dans un système informatique en périphérie de réseau
WO2021054770A1 (fr) Procédé et dispositif de commande de débit de données dans un système de communication sans fil
WO2017126892A1 (fr) Procédé et appareil pour la communication d'un terminal dans un système de communication mobile
WO2017119723A1 (fr) Procédé de contexte d'ue et de reprise de connexion d'ue
WO2017213438A1 (fr) Appareil et procédé de réalisation de communication de relais dans un système de communication sans fil
WO2021054747A1 (fr) Appareil et procédé de relocalisation d'upf psa dans un système de communication sans fil
WO2021133092A1 (fr) Procédé et appareil permettant de gérer une procédure de transfert intercellulaire dans un système de communication sans fil
EP3443805A1 (fr) Procédé et appareil de commande de connexion légère
WO2021235880A1 (fr) Procédé et dispositif de fourniture d'informations d'un réseau de données local à un terminal dans un système de communication sans fil
WO2021206519A1 (fr) Appareil et procédé de transmission d'informations de gestion de pont dans un système de communication sans fil
WO2021201530A1 (fr) Authentification et autorisation spécifiques à une tranche de réseau
WO2021194163A1 (fr) Procédé et dispositif de service d'exposition d'événement d'état de retard de paquet basé sur un service upf
WO2021235878A1 (fr) Procédé et appareil pour améliorer les optimisations de l'internet des objets cellulaire dans un réseau de télécommunication
WO2022098114A1 (fr) Procédé et appareil de réalisation de communications pour utiliser une tranche de réseau dans un système de communication sans fil
WO2017196161A1 (fr) Procédé et appareil de commande de connexion légère
WO2023059164A1 (fr) Procédé et appareil pour gérer l'enregistrement d'une tranche de réseau dans un système de communication sans fil
WO2021091298A1 (fr) Procédé et appareil de prise en charge de l'auto-optimisation dans un système de communication sans fil
WO2021162477A1 (fr) Procédé et appareil pour la confidentialité d'utilisateur dans un système de communication sans fil
WO2020159168A1 (fr) Procédé de réplication de données, procédé de comptage de données, entités et supports correspondants
WO2022231385A1 (fr) Procédé de configuration de positionnement et dispositif électronique
WO2021194311A1 (fr) Procédé et dispositif de commande d'état de connexion de terminal pour fournir un service d'informations d'emplacement à latence ultra-faible dans un système de communication sans fil
WO2021060904A1 (fr) Procédé et dispositif pour effectuer une communication dans un système de communication sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19869392

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021518577

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019869392

Country of ref document: EP

Effective date: 20210419