WO2022032728A1 - 一种应用迁移的方法和装置 - Google Patents

一种应用迁移的方法和装置 Download PDF

Info

Publication number
WO2022032728A1
WO2022032728A1 PCT/CN2020/111536 CN2020111536W WO2022032728A1 WO 2022032728 A1 WO2022032728 A1 WO 2022032728A1 CN 2020111536 W CN2020111536 W CN 2020111536W WO 2022032728 A1 WO2022032728 A1 WO 2022032728A1
Authority
WO
WIPO (PCT)
Prior art keywords
source
information
target
pdu session
user plane
Prior art date
Application number
PCT/CN2020/111536
Other languages
English (en)
French (fr)
Inventor
姚琦
宗在峰
Original Assignee
华为技术有限公司
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
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202080103975.0A priority Critical patent/CN116097680A/zh
Priority to CA3189164A priority patent/CA3189164A1/en
Priority to EP20949225.5A priority patent/EP4187947A4/en
Priority to AU2020463541A priority patent/AU2020463541A1/en
Priority to JP2023509819A priority patent/JP2023537135A/ja
Publication of WO2022032728A1 publication Critical patent/WO2022032728A1/zh
Priority to US18/167,476 priority patent/US20230188965A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a method and apparatus for application migration.
  • 5G fifth generation
  • AS application servers
  • UPF user plane function
  • the prior art proposes an application migration method based on session and service continuity (session and service continuity, SSC) mode3.
  • SSC mode3 session and service continuity
  • UE user equipment
  • PDU protocol data unit
  • PDU protocol data unit
  • the OS needs to notify the application client (app client, AC), and the AC receives the notification.
  • DNS domain name system
  • the AC sends the address of the New AS to the Old AS to instruct the Old AS to perform application migration.
  • the UE After the state is synchronized between the Old AS and the New AS, the UE starts to AS sends packets.
  • the method determines the New AS based on the DNS query, since the DNS query result is not accurate enough, the New AS determined based on the DNS query result is not the most suitable application server. The problem of large delay in accessing the New AS is caused.
  • the embodiments of the present application provide a method and an apparatus for application migration, which are used to more accurately determine a target AS and reduce the delay for a UE to access an application server.
  • a first aspect of the embodiments of the present application provides a method for application migration.
  • the method includes: the source application function AF acquires first information, where the first information is after the user plane path of the protocol data unit PDU session of the user equipment UE is changed The location information of the UE; the source AF determines the target application server AS based on the first information; the source AF sends the connection information of the target AS to the UE. Based on this solution, the source AF determines the target AS based on the location information of the UE after the user plane path of the UE's PDU session is changed. Therefore, the determined target AS is more accurate, and the delay when the UE accesses the target AS is small, that is, this solution can Reduce the delay of UE accessing the application server.
  • the network side device triggers target AS reselection and application migration, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the AC design.
  • the source AF in this solution may be the source AS or the source ES, that is to say, in this application, the source AS may determine the target AS, or the source ES may determine the target AS.
  • the target AS and the source AS serve the same application
  • the source AS may be the AS visited by the UE before the user plane path of the PDU session of the UE is changed.
  • the target AS determined by the source AF is an AS serving the same application as the source AS, so during the UE movement process, the continuity of the services accessed by the UE can be ensured.
  • the user plane path change of the PDU session of the UE may be understood as a UPF change.
  • the location information of the UE is the IP address of the UE, and the data network access identifier DNAI corresponding to the user plane path of the PDU session of the UE. , at least one of the tracking area identifier TAI of the UE, the cell identifier cell ID of the UE, the radio access network identifier RAN ID of the UE, or the geographic location information of the UE.
  • the source AF can determine the target AS based on the UE's IP address, DNAI, TAI, cell ID, RAN ID, or the UE's geographic location information, so the determined target AS is more accurate.
  • the DNAI corresponding to the user plane path of the PDU session of the UE in this application is the DNAI corresponding to the data network accessible to the UE.
  • the source AF determines the target AS based on the first information, including: the source AF acquires the PDU of the UE based on the first information Information of the user plane function UPF entity after the user plane path of the session is changed; the source AF determines the target AS based on the information of the UPF entity.
  • the source AF can determine the target AS according to the information of the user plane UPF, so the determined target AS is more accurate, and thus the delay when the UE accesses the target AS is small.
  • the information of the UPF can be, for example, DNAI or other information that can identify the UPF.
  • the source AF can obtain the UPF information by sending a query request to the 5GC.
  • the foregoing source AF is the foregoing source AS.
  • the source AS can determine the target AS and send the connection information of the target AS to the UE, which can reduce the delay for the UE to access the application server.
  • the above-mentioned source AF acquiring the above-mentioned first information includes: the above-mentioned source AS receives the first information from the policy control function PCF entity or the session management function SMF entity. A notification message, where the first notification message is used to notify the source AS that the user plane path of the PDU session of the UE is changed, and the first notification message includes the first information. Based on this solution, the source AS can learn that the user plane path of the UE's PDU session has changed by receiving the first notification message sent by the PCF or SMF, so that the source AS can determine the target AS based on the notification message.
  • the first notification message may not include the first information, and when the first notification message does not include the first information, after receiving the first notification message, the source AS may notify the core network element (for example, PCF or SMF) requests to acquire the first information, and then determines the target AS based on the first information.
  • the core network element for example, PCF or SMF
  • the above method further includes: the above-mentioned source AS subscribes to the above-mentioned PCF entity or the above-mentioned SMF entity for a user plane management event notification, and the user plane management event notification It is used to notify the above-mentioned source AS when the user plane path of the above-mentioned UE's PDU session is changed.
  • the source AS subscribes to the PCF or SMF for notification of user plane management events, so that the PCF or SMF can notify the source AS when the PCF or SMF determines that the user plane path of the UE's PDU session changes.
  • the obtaining of the first information by the source AF includes: the source AS receiving the second notification message from the source enabling server ES, the The second notification message is used to notify the source AS of the change of the user plane path of the PDU session of the UE, and the second notification message includes the first information.
  • the source AS can learn that the user plane path of the UE's PDU session has changed by receiving the second notification message sent by the source ES, so that the source AS can determine the target AS and perform application migration based on the notification message.
  • the above-mentioned method further includes: the above-mentioned source AS subscribes a user plane management event notification to the above-mentioned source ES, and the user plane management event notification is used when the above-mentioned The source AS is notified when the user plane path of the PDU session of the UE changes.
  • the source AS subscribes the user plane management event notification to the source ES, so that the source AS can be notified when the source ES determines that the user plane path of the UE's PDU session changes.
  • the source ES can learn the user plane path change of the UE's PDU session by subscribing to the user plane management event notification from the core network element; the source ES can also learn the user of the UE's PDU session by receiving a notification message sent by the UE.
  • the foregoing method further includes: the foregoing source AS sends the connection information of the foregoing target AS to the foregoing UE. Based on this solution, the source AS sends the connection information of the target AS to the UE, so that the UE can establish a connection with the target AS, thereby reducing the time delay of the UE accessing the application server.
  • the foregoing source AF is the source ES.
  • the source ES can determine the target AS and send the connection information of the target AS to the UE, which can reduce the delay for the UE to access the application server.
  • the above-mentioned source AF acquiring the above-mentioned first information includes: the above-mentioned source ES receives a third notification message from the PCF entity or the SMF entity, the first The third notification message is used to notify the source ES of the change of the user plane path of the PDU session of the UE, and the third notification message includes the first information. Based on this solution, the source ES can learn that the user plane path of the UE's PDU session has changed by receiving the third notification message sent by the PCF or SMF, so that the source ES can determine the target AS based on the notification message.
  • the above method further includes: the above-mentioned source ES subscribes to the above-mentioned PCF entity or the above-mentioned SMF entity for user plane management event notification, and the user plane management event notification It is used to notify the above-mentioned source ES when the user plane path of the above-mentioned UE's PDU session is changed.
  • the source ES subscribes to the PCF or SMF for notification of user plane management events, so that the PCF or SMF can notify the source ES when the PCF or SMF determines that the user plane path of the UE's PDU session changes.
  • the above-mentioned source AF acquiring the above-mentioned first information includes: the above-mentioned source ES receives the fourth information sent by the edge-enabled client EEC from the above-mentioned UE.
  • a notification message where the fourth notification message is used to notify the source ES of the re-establishment of the PDU session of the UE, and the fourth notification message includes the first information.
  • the source ES can know the re-establishment of the PDU session of the UE by receiving the fourth notification message sent by the EEC of the UE, so that the source ES can determine the target AS based on the notification message. Therefore, the determined target AS is more accurate, reducing the UE's The latency of accessing the application server.
  • the foregoing method further includes: the foregoing source ES sends the connection information of the foregoing target AS to the foregoing UE. Based on this solution, the source ES sends the connection information of the target AS to the UE, so that the UE can establish a connection with the target AS, thereby reducing the time delay of the UE accessing the application server.
  • the source AF is a configuration server CS
  • the above method further includes: the CS receives the first indication information of the UE, the first indication The information is used to instruct the CS to send the information of the target data network DN to the above-mentioned UE when the user plane path of the PDU session of the above-mentioned UE changes; the CS determines the target DN based on the above-mentioned first information; the CS sends the above-mentioned UE the information of the target DN. information.
  • the CS determines the target DN based on the UE's location information after the user plane path of the UE's PDU session is changed. Therefore, the determined target AS is more accurate. Therefore, after the UE accesses the target DN, the time for the UE to access the data network can be reduced. extension. For example, when the UE moves, the SMF decides to reestablish the PDU session, and the CS can determine the target DN according to the location information of the UE after the reestablishment of the PDU session, and send the information of the target DN to the UE, so that the UE can access the target DN.
  • the acquisition of the first information by the CS includes: the CS receives second indication information from the UE, where the second indication information is used to indicate the above The PDU session of the UE is re-established, and the second indication information includes the above-mentioned first information.
  • the CS can know that the PDU session of the UE is re-established by receiving the indication information of the UE, so that the CS can determine the target DN based on the indication information, so the determined target AS is more accurate, so the UE can reduce the size of the target DN after accessing the target DN. The delay for the UE to access the data network.
  • the obtaining of the first information by the CS includes: the CS receiving the fifth notification message from the policy control function PCF entity or the session management function SMF entity, The fifth notification message is used to notify the CS and the UE of the user plane path change of the PDU session, and the fifth notification message includes the first information.
  • the CS can know that the PDU session of the UE is re-established by receiving the notification message of the PCF or SMF, so that the CS can determine the target DN based on the notification message, so the determined target AS is more accurate.
  • the method further includes: the CS subscribes the user plane management event notification to the PCF entity or the SMF entity, and the user plane management event notification uses The CS is notified when the user plane path of the PDU session of the UE is changed.
  • the CS subscribes to the PCF or SMF for notification of user plane management events, so that when the PCF or SMF determines that the user plane path of the UE's PDU session changes, the CS can be notified.
  • the user plane path change of the PDU session of the UE includes the change of the anchor point of the PDU session of the UE, the session of the PDU session of the UE and the service continuous SSC.
  • Mode is Mode 3.
  • the source AF can determine the target AS when the UE's PDU session anchor changes.
  • the anchor point of the PDU session of the UE does not change, the data network accessed by the UE may not change, so it may not be necessary to perform application migration. Therefore, the change of the user plane path of the PDU session of the UE in this application can be understood.
  • the session anchor for the UE's PDU is changed.
  • a second aspect of the embodiments of the present application provides a method for application migration, the method includes: the source enabling server ES obtains first information, where the first information is a user plane path change of a protocol data unit PDU session of a user equipment UE The location information of the back UE; the source ES sends a second notification message to the source application server AS; the second notification message is used to notify the source AS that the user plane path of the PDU session of the above-mentioned UE is changed, and the source AS is the PDU session of the above-mentioned UE.
  • the AS visited by the above UE before the user plane path is changed.
  • the source AS notifies the source AS of the change of the user plane path of the UE's PDU session, so that the source AS can determine the target AS. It can be understood that the source AS can determine the target AS based on the first information, so the determined target AS is more accurate, and the delay when the UE accesses the target AS is small, that is, the solution can reduce the delay of the UE accessing the application server. It can be understood that in this solution, the source AS can trigger the reselection and application migration of the target AS, and there is no change to the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • the location information of the UE is the network protocol IP address of the UE, the data network access identifier DNAI corresponding to the user plane path of the PDU session of the UE, and the tracking area of the UE. At least one of the identification TAI, the cell identification cell ID of the UE, the radio access network identification RAN ID of the UE, or the geographic location information of the UE. Based on this solution, the source ES can determine the target AS based on the UE's IP address, DNAI, TAI, cell ID, RAN ID, or the UE's geographic location information, so the determined target AS is more accurate.
  • the above method further includes: the above-mentioned source ES receives a user plane management event notification subscribed from the above-mentioned source AS, and the user plane management event notification is used for The above-mentioned source AS is notified when the user plane path of the above-mentioned UE's PDU session is changed.
  • the source AS subscribes the user plane management event notification to the source ES, so that the source AS can be notified when the source ES determines that the user plane path of the UE's PDU session changes.
  • the obtaining of the first information by the source ES includes: the source ES receiving a fourth notification message sent by the edge-enabled client EEC from the UE. , the fourth notification message is used to notify the source ES of the re-establishment of the PDU session of the UE, and the fourth notification message includes the first information.
  • the source ES can know the re-establishment of the PDU session of the UE by receiving the fourth notification message sent by the EEC of the UE, so that the source ES can notify the source AS that the user plane path of the PDU session of the UE has changed.
  • the user plane path change of the PDU session of the UE includes a change of the anchor point of the PDU session of the UE, the session of the PDU session of the UE and service continuous SSC mode as mode 3.
  • the source ES can notify the source AS, so that the source AS can determine the target AS and trigger application migration. It is more accurate and reduces the time delay of the UE accessing the application server.
  • the source AS can trigger the reselection and application migration of the target AS without changing the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • a third aspect of the embodiments of the present application provides a method for application migration, the method comprising: an edge-enabled client EEC of a user equipment UE subscribes to an operating system OS of the UE for a session re-establishment event notification, where the session re-establishment event notification is used for Notify the EEC when the PDU session of the UE is re-established; the EEC receives the sixth notification message from the OS, the sixth notification message is used to notify the EEC of the re-establishment of the PDU session of the UE, and the sixth notification message includes the first information , where the first information is the location information of the UE after the PDU session is reestablished.
  • the EEC in the UE subscribes the session re-establishment event notification to the OS in the UE, so that when the PDU session of the UE is re-established, the OS in the UE notifies the EEC in the UE, so that the EEC can learn the relevant information of the user plane.
  • the EEC in the UE can determine the target AS based on the first information (the location information of the UE), so the determined target AS is more accurate, and the time delay when the UE accesses the target AS is small, that is, this solution can reduce the time delay of the UE.
  • the method does not require the AC in the UE to understand the network logic, which can simplify the design of the AC.
  • the location information of the UE is the IP address of the UE, the data network access identifier DNAI corresponding to the user plane path of the PDU session of the UE, and the tracking area identifier TAI of the UE. , at least one of the cell ID of the UE, the radio access network ID of the UE, or the geographic location information of the UE.
  • the EEC can determine the target AS based on the UE's IP address, DNAI, TAI, cell ID, RAN ID, or the UE's geographic location information, so the determined target AS is more accurate.
  • the above method further includes: the above EEC sends a fourth notification message to the source enabling server ES, where the fourth notification message is used to notify the above source ES reestablishes the PDU session of the UE, and the fourth notification message includes the first information.
  • the EEC in the UE notifies the source ES of the UE's PDU session re-establishment, so that the source ES can determine the target AS and perform application migration based on the notification message sent by the EEC.
  • the target AS determined by this method is more accurate, so the UE accesses the target AS.
  • the delay of AS is small.
  • the method does not require the AC in the UE to understand the network logic, which can simplify the design of the AC.
  • the above method further includes: the above-mentioned EEC determines the target application server AS based on the above-mentioned first information; the target AS and the source AS serve the same application , the source AS is the AS visited by the UE before the PDU session of the UE is reestablished. Based on this solution, when the EEC in the UE learns that the user plane path of the UE's PDU session changes, it can determine the target AS by itself. Not only the determined target AS is more accurate, but also the AC in the UE does not need to understand the network logic, which can simplify the design of the AC .
  • the above-mentioned EEC determines the target application server AS based on the above-mentioned first information, including: the above-mentioned EEC determines the target ES based on the above-mentioned first information; the above-mentioned The EEC sends a discovery request to the above-mentioned target ES; the above-mentioned EEC receives a first message from the above-mentioned target ES, and the first message includes the connection information of one or more ASs managed by the above-mentioned target ES, and the one or more ASs managed by the target ES
  • the AS serves the same application as the source AS; the EEC determines the target AS from one or more ASs managed by the target ES.
  • the EEC in the UE can determine the target AS in one or more ASs managed by the target ES, so that the target AS can be accessed. Therefore, the determined target AS is more accurate, and the time delay for the UE to access the target AS is small. Moreover, this solution does not need to change the AC in the UE, which simplifies the design of the AC.
  • the above-mentioned method further includes: the above-mentioned EEC sends the connection information of the above-mentioned target AS to the above-mentioned source AS or source ES, so that the above-mentioned source AS or source
  • the ES migrates the context of the aforementioned UE from the aforementioned source AS to the aforementioned target AS.
  • the source AS or the source ES can migrate the context of the UE from the source AS to the target AS, so that the logic of the AC in the UE does not need to be strengthened, which simplifies the design of the AC.
  • the user plane path change of the PDU session of the UE includes the re-establishment of the PDU session of the UE.
  • the OS in the UE can notify the EEC in the UE when the PDU session of the UE is reestablished. This method does not require the AC in the UE to understand the network logic, which can simplify the design of the AC.
  • the change of the user plane path of the PDU session of the UE includes the change of the anchor point of the PDU session of the UE, the session of the PDU session of the UE and the service continuous SSC.
  • Mode is Mode 3. Based on this solution, since the SSC mode of the UE's PDU session is mode 3, after the UE's PDU session anchor is changed, the target AS can be determined and the application can be migrated, reducing the delay for the UE to access the application server.
  • a method for application migration includes: a source application server AS sends a subscription request to a source enabling server ES, where the subscription request is used to notify the source when the source ES determines that the target AS exists AS; the source AS receives the seventh notification message from the source ES, where the seventh notification message includes connection information of the target AS; the source AS determines to migrate the context of the user equipment UE from the source AS to the target AS.
  • the target AS and the source AS serve the same application.
  • the source AS sends a subscription request to the source ES, so that when the source ES determines that the target AS exists in the DN that the UE can access, it can send a notification message including the connection information of the target AS to the source AS, and then the source ES can send a notification message including the connection information of the target AS to the source AS.
  • AS triggers application migration. After the user plane path of the UE's PDU session is changed, the data network accessible to the UE may not necessarily deploy an AS serving the same application as the source AS. Therefore, by sending a subscription request, the source ES can determine the data that the UE can access. When there is an AS serving the same application as the source AS in the network, the source AS is notified again, and then application migration is initiated. Therefore, invalid notifications during the application migration process can be reduced and delays can be reduced.
  • the above method further includes: the source AS sends fourth indication information to the source ES, where the fourth indication information is used to instruct the source ES to migrate the context of the UE from the source AS to the target AS.
  • the source AS sends the source ES instruction information indicating that the source ES migrates the context of the UE from the source AS to the target AS, so that the source ES can migrate the context of the UE from the source AS to the target AS, thereby reducing the size of the UE.
  • the latency of accessing the application server is accessed.
  • the above method further includes: the source AS sends an application switching request message to the target AS, where the application switching request message is used to migrate the context on the source AS to the target AS.
  • the source AS sends an application switching request message to the target AS, so that the target AS can migrate the context on the source AS to the target AS, thereby reducing the delay of the UE accessing the application server.
  • the method further includes: the source AS receives an application switching response message from the target AS, the application switching response message includes third indication information, and the third indication information It is used to indicate whether the above-mentioned target AS agrees to the application handover; correspondingly, the above-mentioned source AS determines to migrate the context of the above-mentioned UE from the above-mentioned source AS to the above-mentioned target AS, including: if the above-mentioned third indication information indicates that the above-mentioned target AS agrees to the application handover, the above-mentioned The source AS determines to migrate the context of the UE from the source AS to the target AS. Based on this solution, the target AS can send an application switching response message to the source AS, so that the target AS can determine to trigger the application migration when the target AS agrees to the application switching, thereby avoiding the migration failure.
  • the above method further includes: the source AS sends fifth indication information to the source ES, where the fifth indication information is used to indicate whether the source AS supports Application switching. Based on this solution, the source ES can know whether the source AS supports application handover. If the source ES determines that the source AS supports application handover, the source ES can perform application migration after the source ES determines that the target AS exists in the data network accessible to the UE.
  • the above method further includes: the source AS sends seventh indication information to the source ES, where the seventh indication information is used to indicate that the application needs to be maintained during switching business continuity. Based on this solution, by sending the seventh indication information from the source AS to the source ES, when the DNAI changes, a forwarding tunnel between UPFs can be established for service continuity, so that the UE can send application data to the source AS.
  • a fifth aspect of the embodiments of the present application provides an application migration method, the method includes: a source enabling server ES receives a subscription request from a source application server AS, where the subscription request is used to notify when the source ES determines that a target AS exists The source AS; the source ES obtains first information, where the first information is the location information of the UE after the user plane path of the UE's protocol data unit PDU session is changed; the source ES determines the target AS based on the first information.
  • the target AS and the source AS serve the same application.
  • the source AS sends a subscription request to the source ES, so that when the source ES determines that the target AS exists in the DNs accessible to the UE, the source ES can send a notification message including the connection information of the target AS to the source AS.
  • the data network accessible to the UE may not necessarily deploy an AS serving the same application as the source AS. Therefore, by sending a subscription request, the source ES can determine the data that the UE can access.
  • the source AS is notified again, and then application migration is initiated. Therefore, invalid notifications during the application migration process can be reduced and delays can be reduced.
  • the source ES sends a seventh notification message to the source AS, where the seventh notification message includes connection information of the target AS.
  • the source AS sends a subscription request to the source ES, so that when the source ES determines that the target AS exists in the DNs accessible to the UE, the source ES can send a notification message including the connection information of the target AS to the source AS. It can be understood that when the source ES determines that the target AS exists, the source ES sends a seventh notification message to the source AS.
  • the location information of the UE is the IP address of the UE, and the data network access identifier DNAI corresponding to the user plane path of the PDU session of the UE. , at least one of the tracking area identifier TAI of the UE, the cell identifier cell ID of the UE, the radio access network identifier RAN ID of the UE, or the geographic location information of the UE.
  • the source ES can determine, based on the IP address, DNAI, TAI, cell ID, RAN ID, or geographic location information of the UE, that the target AS exists in the DN that the UE can access, so the determination result is more accurate.
  • the obtaining of the first information by the source ES includes: the source ES receiving the third information from the policy control function PCF entity or the session management function SMF entity.
  • a notification message where the third notification message is used to notify the source ES of the change of the user plane path of the PDU session of the UE, and the third notification message includes the first information.
  • the source ES can learn that the user plane path of the UE's PDU session has changed by receiving the third notification message sent by the PCF or SMF, so that the source ES can determine, based on the notification message, that the target AS exists in the DNs accessible to the UE. .
  • the above method further includes: the above-mentioned source ES subscribes to the above-mentioned PCF entity or the above-mentioned SMF entity for user plane management event notification, the user plane management event notification It is used to notify the above-mentioned source ES when the user plane path of the above-mentioned UE's PDU session is changed.
  • the source ES subscribes to the PCF or SMF for notification of user plane management events, so that the PCF or SMF can notify the source ES when the PCF or SMF determines that the user plane path of the UE's PDU session changes.
  • the above subscription request includes the information of the PDU session of the UE; the information of the PDU session of the UE includes the network protocol IP address, data network name of the UE. At least one of DNN, or single network slice selection auxiliary information S-NSSAI.
  • the source ES can identify the 5GC network element accessed by the UE based on the information of the PDU session of the UE.
  • the above method further includes: the source ES determines the policy control function PCF entity or the session management function SMF entity according to the information of the PDU session of the UE. Based on this solution, the source ES can determine the PCF entity or SMF entity accessed by the UE based on the information of the PDU session of the UE.
  • the above-mentioned subscription request includes the application identification information
  • the above-mentioned source ES determines the target AS based on the above-mentioned first information, including: the source ES is based on the first information.
  • the source ES can determine the target AS based on the first information and the application identification information, so the determined target AS is more accurate, which can reduce the delay of the UE accessing the application server.
  • the above method further includes: the source ES sends sixth indication information to the SMF, where the sixth indication information is used to indicate whether the source AS supports application switching .
  • the source ES sends sixth indication information to the SMF, where the sixth indication information is used to indicate whether the source AS supports application switching .
  • the above method further includes: the source ES receives seventh indication information from the source AS, where the seventh indication information is used to indicate that the application switching needs to be Maintain business continuity. Based on this solution, when the DNAI changes, a forwarding tunnel between UPFs can be established for service continuity, so that the UE can send application data to the source AS.
  • the above method further includes: the source ES sends eighth indication information to the SMF or the PCF, where the eighth indication information is used to indicate when the application is switched Business continuity needs to be maintained. Based on this solution, the source ES sends the eighth indication information to the SMF or the PCF, so that the 5GC network element can release the forwarding tunnel after the application handover is completed.
  • the foregoing method further includes: the foregoing source ES sends the connection information of the target AS to the SMF or the PCF. Based on this solution, the source ES sends the connection information of the target AS to the SMF or the PCF, so that the SMF or the PCF can send the connection information of the target AS to the UE, so that the UE can establish a connection with the target AS, reducing the time required for the UE to access the application server. time delay.
  • a method for application migration includes: a configuration server CS receives first indication information from a user equipment UE, where the first indication information is used to indicate that the CS is a protocol data unit of the UE
  • the first indication information is used to indicate that the CS is a protocol data unit of the UE
  • the CS obtains the first information, which is the location information of the UE after the user plane path of the PDU session of the UE is changed; the CS is based on the first information. information to determine the target DN; the CS sends the information of the target DN to the UE.
  • the CS determines the target DN based on the UE's location information after the user plane path of the UE's PDU session is changed. Therefore, the determined target AS is more accurate. Therefore, after the UE accesses the target DN, the time for the UE to access the data network can be reduced. extension.
  • the SSC mode of the PDU session of the UE may be mode 3.
  • the above-mentioned change of the user plane path of the PDU session of the UE includes the re-establishment of the PDU session of the UE.
  • the location information of the UE is the IP address of the UE, the data network access identifier DNAI corresponding to the user plane path of the PDU session of the UE, and the tracking area identifier TAI of the UE. , at least one of the cell ID of the UE, the radio access network ID of the UE, or the geographic location information of the UE.
  • the CS can determine the target DN based on the UE's IP address, DNAI, TAI, cell ID, RAN ID, or the UE's geographic location information, so the determined result is more accurate.
  • the obtaining of the first information by the CS includes: the CS receiving second indication information from the UE, where the second indication information is used to indicate the above The PDU session of the UE is re-established, and the second indication information includes the above-mentioned first information.
  • the CS can know that the PDU session of the UE is re-established by receiving the indication information of the UE, so that the CS can determine the target DN based on the indication information, so the determined target AS is more accurate, so the UE can reduce the size of the target DN after accessing the target DN. The delay for the UE to access the data network.
  • the obtaining of the first information by the CS includes: the CS receiving the fifth notification message from the policy control function PCF entity or the session management function SMF entity,
  • the fifth notification message is used to notify the CS and the UE of the user plane path change of the PDU session, and the fifth notification message includes the first information.
  • the CS can know that the PDU session of the UE is re-established by receiving the notification message of the PCF or SMF, so that the CS can determine the target DN based on the notification message, so the determined target AS is more accurate.
  • the method further includes: the CS subscribes the user plane management event notification to the PCF entity or the SMF entity, and the user plane management event notification uses The CS is notified when the user plane path of the PDU session of the UE is changed.
  • the CS subscribes to the PCF or SMF for notification of user plane management events, so that when the PCF or SMF determines that the user plane path of the UE's PDU session changes, the CS can be notified.
  • the user plane path change of the PDU session of the UE includes the re-establishment of the PDU session of the UE.
  • the CS can determine the target DN when the UE's PDU session is reestablished.
  • the data network accessed by the UE may not change, so it may not be necessary to perform application migration. Therefore, in this application, the user plane path change of the PDU session of the UE can be considered as the UE. The PDU session is reestablished.
  • the user plane path change of the PDU session of the UE includes the change of the anchor point of the PDU session of the UE, the session of the PDU session of the UE and the service continuous SSC Mode is Mode 3. Based on this solution, since the SSC mode of the PDU session of the UE is mode 3, the target DN can be determined after the PDU session of the UE is reestablished.
  • a seventh aspect of the embodiments of the present application provides a method for application migration.
  • the method includes: the configuration server CS obtains first information, where the first information is after the user plane path of the protocol data unit PDU session of the user equipment UE is changed location information of the UE; the CS determines a target enabling server ES based on the first information. Based on this solution, the CS determines the target ES based on the UE's location information after the user plane path of the UE's PDU session is changed. Therefore, the determined target ES is more accurate, so that the target AS determined based on the target ES is more accurate, and the UE accesses the target AS.
  • the time delay is small, that is, the solution can reduce the time delay of the UE accessing the application server.
  • the location information of the UE includes the network protocol IP address of the UE, the data network access identifier DNAI corresponding to the user plane path of the PDU session of the UE, and the tracking area identifier TAI of the UE. , at least one of the cell identity of the UE, the radio access network identity of the UE, or the geographic location information of the UE.
  • the CS can determine the target ES based on the UE's IP address, DNAI, TAI, cell ID, RAN ID, or the UE's geographic location information, so the determined target ES is more accurate.
  • the above-mentioned CS acquiring the above-mentioned first information includes: the CS receiving the above-mentioned first information from the above-mentioned UE. Based on this solution, the CS can receive the UE's location information from the UE after the user plane path of the UE's PDU session is changed, so that the target ES determined by the CS based on the UE's location information is more accurate, and the delay for the UE to access the application server is reduced. .
  • the foregoing method further includes: the foregoing CS sending the connection information of the foregoing target ES to the foregoing UE.
  • the CS sends the connection information of the target ES to the UE, so that the UE can request the target AS based on the connection information of the target ES, thereby reducing the delay of the UE accessing the application server.
  • the above-mentioned CS acquiring the above-mentioned first information includes: the above-mentioned CS receiving the first information from the source ES. Based on this solution, the CS can receive the location information of the UE after the user plane path of the UE's PDU session is changed from the source ES, so that the target ES determined by the CS based on the location information of the UE is more accurate, and the time for the UE to access the application server is reduced. extension.
  • the foregoing method further includes: the foregoing CS sending the connection information of the foregoing target ES to the foregoing source ES.
  • the CS sends the connection information of the target ES to the source ES, so that the UE can request the target AS based on the connection information of the target ES, thereby reducing the delay of the UE accessing the application server.
  • the above-mentioned first information is the IP address of the UE after the user plane path of the PDU session of the above-mentioned UE is changed, and the above-mentioned CS is based on the above-mentioned first information
  • Determining the above target ES includes: the CS determines, based on the IP address of the UE after the user plane path of the UE's PDU session is changed, the DNAI of the UE's PDU session after the user plane path is changed; and the CS determines the target ES based on the DNAI. Based on this solution, the CS can determine the DNAI based on the IP address of the UE, so that the target ES can be determined based on the DNAI, so the determined target ES is more accurate.
  • the user plane path change of the PDU session of the UE includes the change of the PDU session anchor point of the UE, and the session and service continuous SSC mode of the UE is the mode 3.
  • the SSC mode of the PDU session of the UE is mode3
  • the change of the user plane path of the PDU session of the UE includes the change of the anchor point of the PDU session of the UE. That is to say, in this solution, when the PDU session anchor point of the UE changes, the target ES is determined based on the position information of the UE after the session anchor point is changed, so the determined target ES is more accurate.
  • An eighth aspect of the embodiments of the present application provides a method for application migration.
  • the method includes: the source enabling server ES obtains first information, where the first information is a user plane path change of a protocol data unit PDU session of a user equipment UE After the location information of the UE; the source ES sends the first information to the configuration server CS; the source ES receives the connection information of the target ES from the CS. Based on this solution, the source ES sends the first information to the CS, so that the CS can determine the target ES based on the first information. Therefore, the determined target ES is more accurate, which can reduce the delay of the UE accessing the application server.
  • the location information of the UE includes the network protocol IP address of the UE, the data network access identifier DNAI corresponding to the user plane path of the PDU session of the UE, and the tracking area identifier TAI of the UE. , at least one of the cell identity of the UE, the radio access network identity of the UE, or the geographic location information of the UE.
  • the CS can determine the target ES based on the UE's IP address, DNAI, TAI, cell ID, RAN ID, or the UE's geographic location information, so the determined target ES is more accurate.
  • the foregoing source ES acquiring the first information includes: the source ES receiving the first information from the UE. Based on this solution, the source ES receives the first information from the UE, and sends the first information to the CS, so that the CS can more accurately determine the target ES based on the first information.
  • the source ES acquiring the above-mentioned first information includes: the above-mentioned source ES receiving the third information from the policy control function PCF entity or the session management function SMF entity.
  • a notification message where the third notification message is used to notify the source ES of the change of the user plane path of the PDU session of the UE, and the third notification message includes the first information.
  • the source ES can also obtain the first information from the 5GC network element, and send the first information to the CS, so that the CS can more accurately determine the target ES based on the first information.
  • the source ES subscribes the user plane management event notification to the above PCF entity or the above SMF entity, and the user plane management event notification is used when the above UE's
  • the above-mentioned source ES is notified when the user plane path of the PDU session is changed.
  • the source ES can know the user plane path change of the UE's PDU session by subscribing the user plane management event notification to the 5GC network element, and obtain the location information of the UE after the user plane path change.
  • the above method further includes: the above-mentioned source ES sends a first application discovery request to the above-mentioned target ES, and the first application discovery request is used for requesting to obtain Target AS; the above-mentioned source ES receives the connection information of the target AS from the above-mentioned target ES. Based on this solution, the source ES can send a first application discovery request to the target ES, so as to obtain the information of the target AS from the target ES.
  • the above-mentioned target AS serves the same application as the source AS
  • the source AS is the above-mentioned UE access before the user plane path of the PDU session of the above-mentioned UE is changed.
  • the target AS determined by the target ES is an AS serving the same application as the source AS, so during the UE movement process, the continuity of the services accessed by the UE can be ensured.
  • the foregoing method further includes: the foregoing source ES sends the connection information of the foregoing target AS to the foregoing UE. Based on this solution, the source ES sends the connection information of the target AS to the UE, so that the UE can establish a connection with the target AS, so that the context of the UE is switched from the source AS to the target AS, and the delay of the UE accessing the application server is reduced.
  • a ninth aspect of the embodiments of the present application provides a method for application migration, the method includes: user equipment UE receiving first information from a session management function SMF entity or a user plane function UPF entity, where the first information is the UE's The location information of the UE after the user plane path of the protocol data unit PDU session is changed; the UE sends the first information to the application function AF.
  • the AF can be the CS or the source ES.
  • the UE sends the location information of the UE to the CS or the source ES after the user plane path of the UE's PDU session is changed, so that the CS can determine the target ES based on the location information of the UE, so the determined target ES is more accurate, and then based on The target AS determined by the target ES is relatively accurate, and the time delay when the UE accesses the target AS is relatively small, that is, the present solution can reduce the time delay of the UE accessing the application server.
  • the location information of the UE includes the network protocol IP address of the UE, the data network access identifier DNAI corresponding to the user plane path of the PDU session of the UE, and the tracking area of the UE. At least one of the identifier TAI, the cell identifier of the UE, the radio access network identifier of the UE, or the geographic location information of the UE. Based on this solution, the UE can send the IP address, DNAI, TAI, cell ID, RAN ID, or geographic location information of the UE to the AF, so that the CS can determine the target ES based on the above information, so the determined target ES is more accurate.
  • the AF is a configuration server CS
  • the method further includes: the UE receives connection information from the target enabling server ES of the CS.
  • the CS can determine the target ES based on the location information of the UE after the user plane path of the PDU session is changed, and send the target ES to the UE, so that the UE can request the target AS from the target ES and establish a connection with the target AS, The delay of UE accessing the application server is reduced.
  • the above method further includes: the above-mentioned UE sends a second application discovery request to the above-mentioned target ES, and the second application discovery request is used for requesting to obtain the target.
  • AS the above-mentioned UE receives the connection information of the target AS from the above-mentioned target ES.
  • the UE can request the target ES to acquire the target AS, so that the UE can establish a connection with the target AS, which can reduce the time delay of the UE accessing the application server.
  • the foregoing AF is the source ES.
  • the UE sends the location information of the UE to the source ES after the user plane path of the PDU session of the UE is changed, so that the source ES can send the location information to the CS, and the CS can determine the target ES based on the location information of the UE.
  • the target ES is more accurate, and the target AS determined based on the target ES is more accurate, and the delay when the UE accesses the target AS is small, that is, the solution can reduce the delay of the UE accessing the application server.
  • the above method further includes: the above UE receives connection information of the target AS from the above source ES. Based on this solution, the UE can obtain the connection information of the target AS from the source ES, so that the UE can establish a connection with the target AS, which can reduce the time delay of the UE accessing the application server.
  • a tenth aspect of the embodiments of the present application provides a method for application migration.
  • the method includes: a source application server AS subscribes an available AS notification to a source enabling server ES, and the available AS notification is used when the source ES determines that the user equipment UE is available. Notify the source AS when the target AS exists in the accessed data network DN; the source AS receives the seventh notification message from the above-mentioned source ES, and the seventh notification message includes the address information of the target AS; the source AS determines the AS to be visited by the UE Migrate from the source AS to the target AS.
  • the target AS and the source AS serve the same application.
  • the source AS subscribes to the source ES for notification of available ASes, so that when the source ES determines that the target AS exists in the DNs accessible to the UE, it can send a notification message including the address information of the target AS to the source AS, and then send the notification message to the source AS.
  • the source AS triggers application migration. After the user plane path of the UE's PDU session is changed, an AS serving the same application as the source AS may not necessarily be deployed in the data network accessible to the UE.
  • the source ES can determine that the UE can access
  • the source AS will be notified to initiate application migration, thus reducing invalid notifications and delays in the application migration process.
  • the above method further includes: the above-mentioned source AS sends an application switching request message to the above-mentioned target AS; the above-mentioned source AS receives an application switching response message from the above-mentioned target AS, the application switching response message
  • the message includes third indication information, where the third indication information is used to indicate whether the target AS agrees to the application switching.
  • the source AS can send an application switching request message to the target AS, and then determine to trigger the application migration when the target AS agrees to the application switching, thereby avoiding the migration failure.
  • the source AS determines to migrate the AS visited by the UE from the source AS to the target AS, including: if the third indication information indicates that The above-mentioned target AS agrees to apply the handover, and the above-mentioned source AS determines to migrate the AS visited by the above-mentioned UE from the above-mentioned source AS to the above-mentioned target AS. Based on this solution, the source AS can determine to trigger the application migration when the target AS agrees to the application switching, thereby avoiding the migration failure.
  • an application migration method includes: the source enabling server ES receives an available AS notification subscribed from the source application server AS, and the available AS notification is used when the source ES determines a user Notify the source AS when the target AS exists in the data network DN accessible by the equipment UE; the source ES obtains the first information, the first information is the location information of the UE after the user plane path of the UE's protocol data unit PDU session is changed; the source ES; Based on the first information, it is determined that a target AS exists in a DN accessible to the UE; the source ES sends a seventh notification message to the source AS, where the seventh notification message includes address information of the target AS.
  • the target AS and the source AS serve the same application.
  • the source AS subscribes to the source ES for notification of available ASes, so that when the source ES determines that the target AS exists in the DNs accessible to the UE, the source ES can send a notification message including the address information of the target AS to the source AS.
  • the data network accessible to the UE may not necessarily deploy an AS serving the same application as the source AS. Therefore, by subscribing to the available AS notification, the source ES can determine that the UE can access
  • the source AS will be notified to initiate application migration. Therefore, invalid notifications during the application migration process can be reduced and delays can be reduced. It can be understood that when the source ES determines that the target AS exists in the DN accessible to the UE, the source ES sends the seventh notification message to the source AS.
  • the location information of the UE is the IP address of the UE, the data network access identifier DNAI corresponding to the data network that the UE can access, and the tracking area identifier TAI of the UE. , at least one of the cell ID of the UE, the radio access network ID of the UE, or the geographic location information of the UE.
  • the source ES can determine, based on the IP address, DNAI, TAI, cell ID, RAN ID, or geographic location information of the UE, that the target AS exists in the DN that the UE can access, so the determination result is more accurate.
  • the obtaining of the first information by the source ES includes: the source ES receiving the first information from the policy control function PCF entity or the session management function SMF entity.
  • the third notification message is used to notify the source ES of the change of the user plane path of the PDU session of the UE, and the third notification message includes the first information.
  • the source ES can learn that the user plane path of the UE's PDU session has changed by receiving the third notification message sent by the PCF or SMF, so that the source ES can determine, based on the notification message, that the target AS exists in the DNs accessible to the UE. .
  • the above method further includes: the above-mentioned source ES subscribes to the above-mentioned PCF entity or the above-mentioned SMF entity to notify the user plane management event, the user plane management event The notification is used to notify the above-mentioned source ES when the user plane path of the above-mentioned UE's PDU session is changed.
  • the source ES subscribes to the PCF or SMF for notification of user plane management events, so that the PCF or SMF can notify the source ES when the PCF or SMF determines that the user plane path of the UE's PDU session changes.
  • a twelfth aspect of the embodiments of the present application provides a communication system, the communication system includes a source application server AS and a source enabling server ES, wherein the source AS subscribes to the source ES for user plane management event notifications, and the user plane management event notifications Used to notify the source AS when the user plane path of the PDU session of the UE's protocol data unit changes; the source AS is the AS that the UE accesses before the user plane path of the PDU session is changed; the source ES obtains the first information, and the first information is the PDU of the UE The location information of the UE after the user plane path of the session is changed; the source ES sends a second notification message to the source AS, and the second notification message is used to notify the source AS that the user plane path of the UE's PDU session is changed, and the second notification message includes information; the source AS determines the target AS based on the first information, and sends the connection information of the target AS to the UE.
  • the source AS determines the target AS
  • the above-mentioned communication system further includes the above-mentioned UE, and the UE receives the connection information of the target AS from the source AS; the UE is based on the target AS's connection information; The connection information establishes a connection with the target AS.
  • a thirteenth aspect of the embodiments of the present application provides an apparatus for application migration, where the apparatus for application migration has a function of implementing the method for application migration described in any one of the first to ninth aspects above.
  • This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a fourteenth aspect of the embodiments of the present application provides an apparatus for application migration, including: a processor, a memory, a bus, and a communication interface; the memory is used to store computer execution instructions, and the processor and the memory are connected through the bus, When the device for application migration is running, the processor executes the computer-executed instructions stored in the memory, so that the device for application migration executes the method for application migration according to any one of the first to ninth aspects.
  • the embodiments of the present application provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, so that when the computer-readable storage medium runs on a computer, the computer can execute the above-mentioned first
  • the method for application migration according to any one of the aspects to the ninth aspect.
  • the embodiments of the present application provide a computer program product including instructions, which, when run on a computer, enables the computer to execute any one of the above-mentioned first to ninth aspects. method of application migration.
  • a seventeenth aspect of the embodiments of the present application provides a chip system, the chip system includes a processor and a memory, and instructions are stored in the memory; when the instructions are executed by the processor, any one of the first to ninth aspects above is implemented The described application migration method.
  • FIG. 1 is a schematic diagram of the architecture of a 5G network provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an SA6 workgroup edge service enabling architecture provided by an embodiment of the present application
  • FIG. 3 is a schematic structural diagram of a network deployment provided by an embodiment of the present application.
  • FIG. 4a is a schematic flow chart of a PDU session switching process of SSC mode3 provided by an embodiment of the present application
  • FIG. 4b is a schematic flowchart of a PDU session switching process of a multi-homed session mechanism provided by an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method for application migration provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • FIG. 13 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • 15 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • 16 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • 17 is a schematic flowchart of another method for application migration provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of the composition of a communication device provided by an embodiment of the present application.
  • FIG. 19 is a schematic diagram of the composition of another communication device provided by an embodiment of the present application.
  • FIG. 20 is a schematic diagram of the composition of another communication device provided by an embodiment of the present application.
  • FIG. 21 is a schematic diagram of the composition of another communication device provided by an embodiment of the present application.
  • At least one (a) of a, b or c may represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b and c can be single or multiple.
  • words such as “first” and “second” are used to distinguish the same or similar items that have basically the same function and effect, Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order.
  • first notification message and second notification message in the embodiment of the present application are only used to distinguish different notification messages.
  • the descriptions of the first, second, etc. appearing in the embodiments of the present application are only used for illustration and distinguishing the description objects, and have no order. any limitations of the examples.
  • connection in the embodiments of the present application refers to various connection modes such as direct connection or indirect connection, so as to realize communication between devices, which is not limited in the embodiments of the present application.
  • Network and "system” appearing in the embodiments of this application express the same concept, and a communication system is a communication network.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • FIG. 1 is a schematic diagram of a 5G network architecture according to an embodiment of the present application.
  • the 5G network includes user equipment UE, access network (AN) equipment/radio access network (RAN) equipment, user plane function (UPF) entity and data network (data network) , DN), access and mobility management function (AMF) entity, session management function (session management function, SMF) entity, policy control function (policy control function, PCF) entity and application function (application function) , AF), network slice selection function (NSSF) entity, authentication server function (authentication server function, AUSF) entity and unified data management (unified data management, UDM) entity.
  • AN access network
  • RAN radio access network
  • UPF user plane function
  • AMF access and mobility management function
  • SMF session management function
  • policy control function policy control function
  • PCF policy control function
  • application function application function
  • AF network slice selection function
  • NSF network slice selection function
  • authentication server function authentication server function
  • AUSF unified data management
  • UDM
  • the access network device refers to a device that accesses the core network, and may be, for example, a base station, a broadband network gateway (BNG), an aggregation switch, or a non-3GPP access device.
  • the base station may include various forms of base stations, such as: a macro base station, a micro base station (also called a small station), a relay station, an access point, and the like.
  • the UPF entity is mainly responsible for the routing, forwarding of PDUs, and policy enforcement for packet data.
  • the UPF entity may implement the user plane functions of a serving gateway (SGW) and a packet data network gateway (PGW).
  • SGW serving gateway
  • PGW packet data network gateway
  • the UPF entity may also be a software defined network (software defined network, SDN) switch (Switch), which is not specifically limited in this embodiment of the present application.
  • SDN software defined network
  • the AMF entity mainly accesses the UE's non-access stratum (NAS) signaling (including session management SM signaling) through the N1 interface, and accesses the wireless access network signaling through the N2 interface, and is mainly responsible for access Authentication, authorization, and mobility management.
  • NAS non-access stratum
  • the SMF entity communicates with the UPF entity through the N4 interface.
  • the SMF entity is mainly responsible for the establishment, release, update and other processes related to the session, as well as the allocation and management of the Internet protocol (IP) address, the selection and control of the UPF entity, and legal interception, etc. Session-related control functions.
  • IP Internet protocol
  • the PCF entity is mainly responsible for user policy management, including both mobility-related policies and protocol data unit (PDU) session-related policies, such as quality of service (QoS) policies, charging policies, and so on.
  • PDU protocol data unit
  • QoS quality of service
  • the AF is mainly responsible for providing the PCF with service information of the user's access service, which is used for the PCF's policy decision.
  • NSSF is primarily responsible for managing network slices.
  • UDM is mainly responsible for saving the user's subscription data.
  • the AUSF is mainly responsible for authenticating and authorizing the access of the UE.
  • the name of the interface between each network element in FIG. 1 is just an example, and the name of the interface may be called other names in a specific implementation, which is not specifically limited in this embodiment of the present application.
  • the 5G network may also include other network devices other than the device shown in FIG. 1 , and FIG. 1 is only an exemplary illustration.
  • the application migration method provided in the embodiments of the present application can be adapted to the 5G network shown in generation, NG) communication network, etc., which are not limited in this embodiment of the present application.
  • the following embodiments only take a 5G network as an example for description.
  • FIG. 2 provides an SA (System and Architecture) 6 working group edge service enabling architecture provided in an embodiment of the present application.
  • a UE can access an edge data network (EDN) through a 5G network, wherein The edge data network can also be called the local data network (LDN).
  • the EDN may include an edge enabler server (EES) and an edge application server (EAS).
  • EES can be a control network element or a management network element in a mobile edge computing (mobile edge computing, MEC) node, and the EES is responsible for managing the EAS deployed in the EDN, such as registration, domain name system (domain name system, DNS) resolution Etc.
  • EAS has configuration information (profile) of EAS stored on EES.
  • each EDN has a specific service scope, and one or more EASs may be deployed in one EDN.
  • FIG. 2 only one EAS deployed in the EDN is taken as an example for illustration.
  • the multiple EASs can serve multiple different applications.
  • three EASs are deployed in the EDN, namely EAS1, EAS2 and EAS3.
  • EAS1 is the EAS corresponding to the Baidu application
  • EAS2 is the EAS corresponding to the iQiyi application
  • EAS3 is the EAS corresponding to the Tencent video application.
  • EASs when multiple EASs are deployed in the EDN, some or all of the EASs in the multiple EASs can serve the same application for disaster recovery or load balancing.
  • EAS1, EAS2 and EAS3 three EASs are deployed in the EDN, namely EAS1, EAS2 and EAS3.
  • EAS1 and EAS2 are the EASs of Baidu's application
  • EAS3 is the EAS of Tencent's video application.
  • the edge configuration server can be a global management network element, responsible for maintaining the information of each EDN, including service scope and EES address. It should be noted that, in some standard protocols (for example, technical specification (TS) 23.501, TS23.502 and other protocols), the above EES, EAS, and ECS can all be called AF.
  • TS technical specification
  • the UE may include an edge enabler client (EEC) and an application client (AC), wherein the EEC provides necessary support for the AC on the UE, and the functions of the EEC include retrieval through the EDGE-4 interface EDN information, retrieval of available EAS, EAS availability change, EAS migration notification to EEC, UE registration to EES, etc.
  • EEC edge enabler client
  • AC application client
  • the EEC in the UE can communicate with the EES through the EDGE-1 interface (edge interface-1), and the EEC in the UE can communicate with the AC in the UE through the EDGE-5 (edge interface-5) interface.
  • the NEs in the network can communicate with the EES through the EDGE-2 (edge interface-2) interface
  • the NEs in the 5G network can communicate with the ECS through the EDGE-8 interface (edge interface-8)
  • the EES deployed in the DN can communicate with the ECS through the EDGE-8 interface (edge interface-8).
  • the EDGE-3 interface (edge interface-3) communicates with the EAS
  • the ESC can communicate with the EES through the EDGE-6 (edge interface-6) interface.
  • the source AS or the target AS in the following embodiments of the present application may be the EAS in FIG. 2
  • the source enabler server (ES) or the target ES may be the EES in FIG. 2
  • the CS may be ECS in Figure 2. That is, in SA6, AS can be called EAS, ES can be called EES, and CS can be called ECS.
  • FIG. 3 is a schematic structural diagram of a network deployment according to an embodiment of the present application.
  • EAS1, EAS2, and EAS3 are deployed in MEC1 node or EDN1, EAS2, EAS3, and EAS4 are deployed in MEC2 node, and EAS1, EAS2, EAS3, and EAS4 are deployed in MEC3.
  • the PDU session anchor (PSA) 1 in FIG. 3 is connected to MEC1/EDN1 (or referred to as PSA1 serving MEC1/EDN1), PSA2 is connected to MEC2, and PSA3 is connected to MEC3.
  • PSA1 serving MEC1/EDN1 PSA2 is connected to MEC2
  • PSA3 is connected to MEC3.
  • Each MEC has a corresponding service area, and the service areas of different MECs may overlap.
  • EAS1, EAS2, EAS3, and EAS4 deployed in Figure 3 serve different applications respectively.
  • EAS2 deployed in MEC1 and EAS2 in MEC2 serve the same application, that is, EAS2 deployed in MEC1 and EAS2 deployed in MEC2 serve the same application.
  • Different servers for an application It should be noted that, in actual deployment, more EASs may be deployed in one MEC or EDN, and FIG. 3 only illustrates the deployment of three or four EASs in one MEC as an example.
  • SSC session and service continuity
  • SSC mode1 the network will always maintain the UPF that acts as the anchor of the PDU session when the PDU session is established, and the IP address of the UE remains unchanged.
  • SSC mode2 if the network wants to migrate the anchor UPF, the old PDU session is released first, and then a new PDU session establishment process is initiated.
  • PDU session of SSC mode3 the network allows to establish a PDU session connection passing through the new anchor point first, and then release the old anchor point PDU session connection, so as to ensure the continuity of the service.
  • FIG. 4a is a schematic flowchart of a PDU session handover in SSC mode3 provided by an embodiment of the present application.
  • the SMF informs the UE to establish a new PDU session with UPF2 first. , and then disconnect the source PDU session when the timer expires.
  • the UE's anchor UPF is switched from UPF1 to UPF2, the two sessions can transmit data at the same time.
  • the old IP address of the UE corresponds to UPF1, and the new address of the UE corresponds to UPF2.
  • the EDN accessed by the UE after the move may be the same as the EDN accessed by the UE before the move, or may be different. That is, the data network accessed by the UE after moving may or may not change.
  • FIG. 4 only takes an example in which the EDN accessed by the UE remains unchanged after moving.
  • FIG. 4b is a schematic flowchart of a PDU session switching process of a multi-homed session mechanism provided by an embodiment of the present application.
  • the multi-homed session mechanism when used to implement SSC mode 3, before the UE moves, it accesses the AS in the DN through UPF1.
  • the anchor UPF When the UE moves and the anchor UPF is switched, a branching point is created.
  • UPF and UPF2 the branch point UPF is connected to UPF1 and UPF2 during the handover process, and after the handover is completed, the connection between UPF1 and the branch points UPF and UPF1 is released.
  • AMF, SMF, PCF, UPF, EDN, EAS, EES, etc. in the above-mentioned FIG. 1 to FIG. 4 are only a name, and the name does not constitute a limitation on the device itself.
  • AMF, SMF, PCF, UPF, EDN, EAS, and EES may also be other names, which are not specifically limited in this embodiment of the present application.
  • an application migration method based on SSC mode3 is that after the OS on the UE finds that a new PDU session is established, the OS notifies the AC, and the AC receives the notification. Trigger a DNS query to obtain the New EAS address, and the AC sends the New EAS address to the Old EAS to instruct the Old EAS to perform application migration. After the state is synchronized between the Old EAS and the New EAS, the UE starts to send data packets to the New EAS.
  • the method determines the New AS based on the DNS query, since the DNS query result is not accurate enough, the New AS determined based on the DNS query result is not the most suitable application server.
  • the embodiments of the present application provide a method for application migration, which can determine the target AS more accurately, reduce The delay of UE accessing the application server is reduced.
  • the source AS, source ES, target AS, target ES, CS, and UE may all adopt the composition shown in FIG. 5 , or include the composition shown in FIG. part.
  • FIG. 5 is a schematic diagram of the composition of a communication apparatus 500 according to an embodiment of the present application.
  • the communication apparatus 500 may include at least one processor 501 , a memory 502 , a transceiver 503 and a communication bus 504 .
  • Each component of the communication device 500 will be specifically introduced below with reference to FIG. 5 :
  • the processor 501 is the control center of the communication device 500, and may be a processor or a general term for multiple processing elements.
  • the processor 501 is a central processing unit (central processing unit, CPU), may also be a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or is configured to implement one or more integrated circuits of the embodiments of the present application , for example: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA).
  • the processor 501 can execute various functions of the communication device by running or executing software programs stored in the memory 502 and calling data stored in the memory 502 .
  • the processor 501 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 5 .
  • the communication apparatus 500 may include multiple processors, such as the processor 501 and the processor 505 shown in FIG. 5 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more communication devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the memory 502 may be read-only memory (ROM) or other type of static storage communication device that can store static information and instructions, random access memory (RAM) or other type of static storage communication device that can store information and instructions.
  • Type of dynamic storage communication device it can also be Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage, Optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage communication devices, or capable of containing or storing desired program code in the form of instructions or data structures and Any other medium that can be accessed by a computer, but is not limited to this.
  • the memory 502 may exist independently and be connected to the processor 501 through the communication bus 504 .
  • the memory 502 may also be integrated with the processor 501 .
  • the memory 502 is used for storing the software program for executing the solution of the present application, and the execution is controlled by the processor 501 .
  • the processor 501 is configured to execute the application program code stored in the memory 502, thereby implementing the application migration method provided by the following embodiments of the present application.
  • the transceiver 503 is used for communication with the access point.
  • the transceiver 503 can also be used to communicate with a communication network, such as an Ethernet network, a radio access network (RAN), a wireless local area network (Wireless Local Area Networks, WLAN) and the like.
  • the transceiver 503 may include a receiving unit to implement a receiving function, and a transmitting unit to implement a transmitting function.
  • the communication bus 504 can be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external communication device interconnect (Peripheral Component, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus and the like.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 5, but it does not mean that there is only one bus or one type of bus.
  • the communication apparatus 500 may be a general communication device or a dedicated communication device.
  • the communication apparatus 500 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device with a similar structure in FIG. 5 .
  • This embodiment of the present application does not limit the type of the communication apparatus 500 .
  • the composition shown in FIG. 5 does not constitute a limitation on the communication device, and in addition to the components shown in FIG. 5 , the communication device may include more or less components than those shown in the figure, or combine some components , or a different component arrangement.
  • the UE in this embodiment of the present application may be various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication functions; it may also include a subscriber unit. ), cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop laptop computer (laptop computer), cordless phone (cordless phone) or wireless local loop (wireless local loop, WLL) station, machine type communication (machine type communication, MTC) terminal, user equipment (user equipment, UE), mobile station (mobile station, MS), terminal device (terminal device), etc.
  • PDA personal digital assistant
  • modem modem
  • handheld device handheld
  • laptop laptop computer laptop computer
  • cordless phone cordless phone
  • WLL wireless local loop
  • machine type communication machine type communication
  • MTC machine type communication
  • UE user equipment
  • MS mobile station
  • terminal device terminal device
  • an application migration method is provided in an embodiment of the present application. As shown in FIG. 6 , the method for application migration includes steps S601-S604.
  • the source AF acquires first information.
  • the first information is the location information of the UE after the user plane path of the PDU session of the UE is changed.
  • the location information of the UE may be the IP address of the UE, the data network access identity (DNAI) corresponding to the user plane path of the PDU session of the UE, or the identification information of the UE in the network (for example, cell ID, RAN ID, tracking area identification (track area ID, TAI), geographic location information, etc.).
  • DNAI data network access identity
  • the DNAI corresponding to the user plane path of the PDU session of the UE is the DNAI corresponding to the data network accessible to the UE.
  • the first information is the IP address of the UE after reestablishing the PDU session or the IP address of the UE corresponding to the newly inserted anchor UPF when the multi-homed session creation mechanism is used to implement SSC mode 3.
  • the first information is the DNAI corresponding to the UPF after the UE reestablishes the PDU session.
  • the first information is information of a base station to which the UE is attached after moving, such as a cell ID. This embodiment of the present application does not limit the specific content of the first information.
  • the DNAI corresponding to the data network that the UE can access can be understood as the DNAI corresponding to the UPF after the UE reconstructs the PDU session, or the multi-homed session creation mechanism is used to achieve SSC mode 3 , the newly inserted anchor UPF corresponds to the DNAI.
  • DNAI can be used to identify the path between the UPF and the data network, i.e. DNAI can be used to determine the UPF or DN.
  • DNAI can be used to determine the UPF or DN.
  • the relationship between DNAI and UPF can be stored on the SMF, then the SMF can determine the UPF based on the DNAI, and conversely, the SMF can also determine the corresponding DNAI based on the UPF. Therefore, after the UE rebuilds the PDU session, if the UPF changes, the DNAI corresponding to the UPF will also change accordingly. Since the UE location information needs to be considered when the SMF selects the UPF, the DNAI can also be regarded as a kind of UE location information.
  • SMF can store the relationship between DNAI and DN
  • other network elements such as SMF or AF can determine DN based on DNAI
  • SMF can also determine corresponding DNAI based on DN.
  • the source AF may acquire the first information when the user plane path of the PDU session of the UE changes.
  • the above-mentioned user plane path of the PDU session of the UE refers to the path from the UE to the base station and then to the UPF entity.
  • the above-mentioned user plane path change of the PDU session of the UE may include the following situations: In the first situation, the UPF is changed.
  • the UPF change includes the anchor point UPF change, which can be understood as the UE's PDU session anchor point change.
  • the UPF changes the IP address of the UE also changes, or the data network that the UE can access changes, that is, the DNAI that the UE can access changes.
  • the UPF does not change but the base station changes.
  • both the UPF and the base station are changed.
  • the user plane path change of the PDU session of the UE may be any of the foregoing, which is not limited in the embodiment of the present application.
  • the following embodiments are only described by taking an example that the user plane path of the PDU session of the UE is changed to the re-establishment of the PDU session of the UE. That is, if the PDU session of the UE is reestablished, the user plane path of the PDU session of the UE is changed, and the source AF acquires the first information.
  • the above-mentioned source AF may be the source AS or the source ES.
  • the source AS or source ES is the AS or ES accessed by the UE before the user plane path of the PDU session is changed. For example, before the PDU session of the UE is reestablished, the UE accesses the AS of Tencent Video, and the AS of the Tencent Video is the source AS.
  • the source AS may be the EAS in FIG. 2
  • the source ES may be the EES in FIG. 2 .
  • the first information obtained by the source AF in the above step S601 is the first information obtained by the source AS
  • the first information obtained by the source AS may come from the core network element ( For example, AMF entity, UPF entity, PCF entity or SMF entity), alternatively, can also come from the source ES.
  • the source AS can subscribe the user plane management event (User plane management event) notification to the PCF entity or the SMF entity,
  • the user plane management event notification is used to notify the source AS when the user plane path of the UE's PDU session changes.
  • the PCF entity or the SMF entity sends to the source AS a first notification message for indicating the change of the user plane path of the PDU session of the UE, where the first notification message may include the first notification message. information.
  • the source AS can subscribe to the source ES for a user plane management event notification, and the user plane management event notification is used for the PDU of the UE.
  • the source AS is notified when the user plane path of the session changes.
  • the source ES sends to the source AS a second notification message for indicating the change of the user plane path of the PDU session of the UE, where the second notification message may include the first information.
  • the source ES may learn, through the PCF entity or the SMF entity or the UE, that the user plane path of the PDU session of the UE changes.
  • the source AS may subscribe to the source ES for a user plane management event notification, and the user plane management event notification is used when the UE
  • the source AS is notified when the user plane path of the PDU session changes.
  • the source ES sends to the source AS a second notification message for indicating the change of the user plane path of the PDU session of the UE.
  • the second notification message may include the first information; if the second notification message does not include the first information, after receiving the second notification message, the source AS may report to the core network element (for example, the AMF entity, the SMF entity or the UPF entity) ) to send a request message to obtain the above-mentioned first information. That is, in this implementation manner, the first information is not included in the second notification message sent by the source ES, but is obtained by sending a request message to the core network element after the source AS receives the second notification message sent by the source ES. .
  • the core network element for example, the AMF entity, the SMF entity or the UPF entity
  • the first information obtained by the source AF in the above step S601 is the first information obtained by the source ES
  • the first information obtained by the source ES may come from the PCF entity or the SMF entity. , or, alternatively, from the UE.
  • the source ES can subscribe the PCF entity or the SMF entity for user plane management event notification, and the user plane management event notification Used to notify the source ES when the user plane path of the UE's PDU session changes.
  • the PCF entity or the SMF entity sends a third notification message to the source ES for indicating the change of the user plane path of the PDU session of the UE, where the third notification message may include the above-mentioned first notification message. a message.
  • step S601 when the first information obtained by the source ES comes from the UE, step S601 includes: the source ES receives a fourth notification message sent by the EEC from the UE and used to indicate the re-establishment of the PDU session of the UE, the fourth notification message
  • the message includes the above-mentioned first information.
  • the first information obtained by the source ES may also be obtained by the source ES requesting the 5GC after receiving the fourth notification message sent by the EEC of the UE.
  • the source ES may also send a request to a core network element (for example, an AMF entity, an SMF entity, or a UPF entity) to obtain the first information. a message.
  • a core network element for example, an AMF entity, an SMF entity, or a UPF entity
  • this embodiment of the present application does not limit which of the foregoing implementation manners the source AF acquires the first information specifically adopts.
  • the source AF determines the target AS based on the first information.
  • the target AS serves the same application as the source AS.
  • the target AS is also the AS of the Tencent Video App, that is, both the source AS and the target AS can serve the application of the Tencent Video App.
  • the target AS can continue to provide services for the UE. That is, the source AS and the target AS are two application servers that can serve the same application.
  • the application identifiers (edge application server ID, EAS ID) of the target AS and the source AS are the same.
  • the target AS and the source AS serve the same application, indicating that the two application servers can provide the same services, and both the source AS and the target AS can only provide Tencent Video services.
  • the target AS and the source AS serve the same application, but the services provided by the two application servers are inconsistent.
  • the source AS can provide Tencent video services
  • the target AS can provide Tencent video services and Tencent video services. map service. For example, before the UE moves, the UE connects to the source AS to access the Tencent Video service. After the application is migrated, the target AS can continue to provide the Tencent Video service.
  • the source AS and the target AS may be deployed in the same data network, or may be deployed in different data networks.
  • the source AS is the application server deployed in the source data network (the data network before the switch)
  • the target AS is the target data network (the data network after the switch). ) deployed in the application server.
  • the source AS and the target AS are two servers deployed in the data network and serving the same application.
  • the embodiments of the present application only take that the source AS and the target AS are deployed in different data networks as an example for description.
  • the source AS and the target AS are the source EAS and the target EAS respectively, the source AS and the target AS are deployed in different edge data network EDNs and serve the same application.
  • the source AF determines the target AS based on the first information, which may include: the source AF obtains, based on the first information, the information of the UPF entity after the user plane path of the PDU session of the UE is changed; the source AF is based on the UPF entity information to determine the target AS.
  • the source AF can send a request to the 5GC based on the IP address of the UE to obtain the DNAI of the UE, and based on the IP address of the UE, the source AF can send a request to the 5GC to obtain the DNAI of the UE.
  • DNAI identifies target AS.
  • the source AF determining the target AS based on the DNAI includes: the source AF determines a new PSA according to the DNAI, and then determines the MEC to which the new PSA is connected, so as to select the EAS deployed in the MEC as the target AS.
  • the source AF stores the relationship between the first information and the target AS, and the source AF queries the mapping relationship according to the acquired first information to determine the target AS.
  • the storage form of the mapping relationship may be in the form of a relation table, context, key-value pair, etc., which is not limited in this embodiment of the present application.
  • the source AF saves the relationship between the target AS and the service range information corresponding to the target AS. After obtaining the UE's location information, the source AF can determine which AS's service range protects the UE's location, that is, determine the AS's location. for the target AS.
  • the source AF stores the corresponding relationship between the target AS and the DNAI, and the source AF obtains the DNAI corresponding to the UPF entity whose user plane path is changed, thereby determining the target AS.
  • the source AF stores the correspondence between the target AS and the IP address or IP address segment, the source AF obtains the new IP address of the UE after the user plane path is changed, so as to determine the target AS.
  • This embodiment of the present application does not limit the implementation manner of how the source AF determines the target AS based on the first information, which is only an exemplary description here.
  • (Optional) S603 The source AF sends the connection information of the target AS to the UE.
  • connection information of the target AS includes address information of the AS, and the connection information of the target AS may be the IP address of the target AS, the Uniform Resource Identifier (URI) of the target AS, or the Uniform Resource Locator (Uniform Resource Locator). , URL), the endpoint of the target AS, etc.
  • URI Uniform Resource Identifier
  • Uniform Resource Locator Uniform Resource Locator
  • the source AS may send the connection information of the target AS to the AC of the UE.
  • the source AS may send the connection information of the target AS to the UE; it may also be that the source ES sends the connection information of the target AS to the UE; or the source AS may send the connection information of the target AS to the source ES. information, and then the source ES sends the connection information of the target AS to the UE; or another network device may send the connection information of the target AS to the UE, which is not limited in this embodiment of the present application.
  • connection information of the target AS sent by the source AF to the UE in the above step S603 may be included in the application layer message, or may be included in the non-access stratum (non-access stratum) NAS signaling.
  • the source AF sending the connection information of the target AS to the UE in the above step S603 may include: the source AF sends the connection of the target AS to the 5GC (eg, AMF, SMF, PCF) information, the 5GC sends the connection information of the target AS to the UE through NAS signaling.
  • the UE receives the connection information of the target AS, and establishes a connection with the target AS.
  • the AC in the UE receives the connection information of the target AS
  • the AC establishes a Socket
  • the OS in the UE selects the target AS according to the connection information of the target AS, and establishes a connection.
  • the connection information of the target AS received by the UE in step S604 may come from the source ES.
  • the UE may request information of the target AS from the source ES, and after receiving the request from the UE, the source ES sends the connection information of the target AS to the UE.
  • the UE sends the above request to the source ES after learning that the user plane path of the PDU session of the UE has changed.
  • the source AF may further include triggering application migration.
  • This application migration is also known as application switching or state migration.
  • the application migration refers to migrating the context of the UE from the source AS to the target AS.
  • the application migration can be understood as state synchronization (context synchronization) between the source AS and the target AS. For example, before the user plane path of the UE's PDU session is changed, the UE accesses the source AS corresponding to the Tencent Video APP to watch the video, and the user watches the video at the 30th minute.
  • the source AS and the target AS perform context synchronization. , if the migration is successful, the UE starts to access the target AS and continues to watch the video at the 30th minute.
  • the ES accessed by the UE after the move may be the same as the ES accessed before the move, or may be different. If the ES accessed by the UE changes after the UE moves, the ES accessed before the UE moves is the source ES, and the ES accessed after the UE moves is the target ES.
  • the source AF when the user plane path of the PDU session of the UE changes, obtains the location information of the UE after the user plane path of the PDU session of the UE changes, and can determine the location information according to the location information of the UE. target AS and trigger application migration.
  • the target AS determined by the UE's location information after the user plane path of the UE's PDU session is changed is more accurate, so the delay when the UE accesses the target AS is small.
  • this solution does not require the AC in the UE to receive a notification from the OS instructing the UE to reestablish a session, initiate a DNS query, and obtain the address of the target AS, that is, the network side device triggers the target AS reselection and application migration in this solution.
  • the AC in the network is not changed, therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • FIG. 7 The schematic flowchart of the method for application migration provided by the embodiment of the present application is shown in FIG. 7 , which involves the interaction between the source AS, the PCF entity/SMF entity and the UE, and includes the following steps:
  • the source AS subscribes the user plane management event notification to the PCF entity or the SMF entity.
  • the user plane management event notification is used to notify the source AS when the user plane path of the UE's PDU session changes.
  • the source AS may directly subscribe to the PCF entity for notification of user plane management events, or may directly subscribe to the SMF entity for notification of user plane management events.
  • the PCF can subscribe the user plane management event to the SMF, so that the SMF determines the change.
  • the SMF can notify the PCF, and the PCF then notifies the source AS.
  • the SMF may also directly notify the source AS.
  • step S701 it may also include that the source AS requests to establish an association (policy association) with the PCF entity or the SMF entity, and the PCF entity or the SMF entity sends the session mode to the source AS, and the session mode can be SSC mode 3.
  • policy association an association
  • the PCF entity or the SMF entity sends the session mode to the source AS, and the session mode can be SSC mode 3.
  • the PCF entity or the SMF entity sends a first notification message to the source AS.
  • the first notification message is used to notify the source AS that the user plane path of the PDU session of the UE is changed. That is, when the PCF entity or the SMF entity determines that the user plane path of the UE's PDU session is changed, the PCF entity or the SMF entity sends the first notification message to the source AS.
  • the first notification message may include first information.
  • first information For the description of the first information, reference may be made to the foregoing embodiments, and details are not repeated here.
  • the above-mentioned user plane path change of the PDU session of the UE includes the re-establishment of the PDU session of the UE.
  • the user plane path change of the PDU session of the UE may be triggered based on UE movement or load balancing. For example, as shown in FIG. 3 , taking the first information as the IP address of the UE as an example, when the UE accesses EAS2 in the MEC1, the anchor UPF of the session is PSA1, and the IP address of the UE is IP@1. If the UE moves into the service range of MEC2, the SMF decides to re-establish the PDU session, and the SMF sends the UE an instruction to create a new session.
  • the indication may include a timer, and when the timer expires, the old PDU session is released.
  • the UE initiates a request to create a session.
  • the SMF selects a new session anchor UPF, namely PSA2, for the current session, and assigns a new IP address IP@2 to the UE.
  • IP@2 is sent to the PCF, and the PCF sends the new IP address IP@2 to the source AS.
  • the SMF of the PDU session before the re-establishment (the old PDU session) and the SMF of the re-established PDU session (the new PDU session) may be the same or different. That is, the SMF may or may not be changed when the PDU session is reestablished.
  • the SMF can associate the old PDU session (the PDU session before the re-establishment) with the new PDU session (the re-established PDU session), and the SMF can send the new PDU session to the source AS.
  • the old SMF that is, the SMF before the re-establishment of the PDU session
  • the AMF sends the PCF information to the new SMF (the SMF after the PDU session is re-established).
  • the new SMF selects the same PCF according to the information of the PCF. That is, although the SMF is changed when the PDU session is rebuilt, the PCF does not change, so the PCF can associate the new PDU session with the old PDU session, and send the new IP address or new DNAI or UE to the source AS. location information.
  • the first notification message in step S702 is in response to the notification of the user plane management event subscribed by the source AS to the PCF entity or the SMF entity in step S701.
  • the source AS receives the first notification message.
  • the source AS determines the target AS based on the first information.
  • the source AS may determine the target AS based on the first information included in the first notification message.
  • the source AS may send a request to the 5GC network element to obtain the first information, and based on the information from the 5GC network
  • the first information obtained by the meta determines the target AS.
  • the source AS may obtain the UE location information from the AMF entity, or obtain the DNAI corresponding to the UPF currently serving the UE from the SMF entity, or obtain the current UE's IP address from the SMF entity or the UPF entity.
  • the source AS determines the specific implementation manner of the target AS based on the first information. Reference may be made to the implementation manner of the source AF determining the target AS based on the first information in step S602, which will not be repeated here.
  • the application migration refers to migrating the application server accessed by the UE from the source AS to the target AS.
  • the source ES may also trigger the application migration.
  • the source AS may send the connection information of the target AS to the source ES, so that The source ES migrates the context of the UE from the source AS to the target AS based on the connection information of the target AS. That is, in this embodiment of the present application, the device that determines the target AS and the device that triggers application migration may be the same device, or may be different devices.
  • step S705 in FIG. 7 is an optional step.
  • the source AS sends the connection information of the target AS to the UE.
  • connection information of the target AS reference may be made to step S603, and details are not repeated here.
  • the UE receives the connection information of the target AS, and establishes a connection with the target AS.
  • the AC in the UE receives the connection information of the target AS
  • the AC establishes a Socket
  • the OS in the UE selects the target AS according to the connection information of the target AS, and establishes a connection.
  • the source AS may forward the received data packet to the target AS.
  • FIG. 7 is only an exemplary illustration.
  • the application migration method subscribes the user plane event management notification to the core network element through the source AS, so that when the user plane path of the UE's PDU session changes, the core network element can receive the notification sent by the core network element.
  • the first notification message, and the target AS is determined based on the first information included in the first notification message, and application migration is triggered.
  • the target AS determined by the method based on the location information of the UE after the user plane path of the PDU session of the UE is changed is relatively accurate, so the delay when the UE accesses the target AS is small.
  • the source AS triggers the reselection and application migration of the target AS, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • FIG. 8 The schematic flowchart of the method for application migration provided by the embodiment of the present application is shown in FIG. 8 , which involves the interaction between the source ES, the PCF entity/SMF entity and the UE, and includes the following steps:
  • the source ES subscribes the user plane management event notification to the PCF entity or the SMF entity.
  • the user plane management event notification is used to notify the source ES when the user plane path of the UE's PDU session changes.
  • the source ES may directly subscribe the PCF entity for notification of user plane management events, or may directly subscribe to the SMF entity for notification of user plane management events. It should be noted that, since the change of the user plane path of the PDU session of the UE is managed by the SMF, when the source ES subscribes the user plane management event to the PCF, the PCF can subscribe the user plane management event to the SMF, so that the SMF determines the change. When the UE's PDU session is on the user plane path, the SMF can notify the PCF, and the PCF then notifies the source ES. Optionally, when the SMF determines to change the user plane path of the PDU session of the UE, the SMF may also directly notify the source ES.
  • the source ES may request to establish an association (policy association) with the PCF entity or the SMF entity, and the PCF entity or the SMF entity sends the session mode to the source ES, and the session mode may be SSC mode 3.
  • policy association an association with the PCF entity or the SMF entity
  • the PCF entity or the SMF entity sends the session mode to the source ES
  • the session mode may be SSC mode 3.
  • the PCF entity or the SMF entity sends a third notification message to the source ES.
  • the third notification message is used to notify the source ES that the user plane path of the PDU session of the UE is changed. That is, when the PCF entity or the SMF entity determines that the user plane path of the PDU session of the UE is changed, the PCF entity or the SMF entity sends the third notification message to the source ES.
  • the third notification message may include the first information.
  • the first information reference may be made to the foregoing embodiments, and details are not repeated here.
  • step S802 is in response to the notification of the user plane management event subscribed by the source ES to the PCF entity or the SMF entity in step S801.
  • the source ES receives the third notification message.
  • the source ES determines the target AS based on the first information.
  • the source AS may determine the target AS based on the first information included in the third notification message.
  • the source AS may send a request to the 5GC network element to obtain the first information, and based on the first information obtained from the 5GC network element Determine the target AS.
  • the source ES may obtain UE location information from the AMF entity, or obtain the DNAI corresponding to the UPF currently serving the UE from the SMF entity, or obtain the IP address of the current UE from the SMF entity or the UPF entity.
  • the source ES determines the specific implementation manner of the target AS based on the first information, and can refer to the implementation manner of the source AF determining the target AS based on the first information in step S602, which will not be repeated here.
  • the source ES triggers application migration.
  • the application migration refers to migrating the application server accessed by the UE from the source AS to the target AS.
  • the source AS may also trigger the application migration.
  • the source ES may also send the connection information of the target AS to the source AS, so that The source AS migrates the context of the UE from the source AS to the target AS based on the connection information of the target AS.
  • step S805 in FIG. 8 is an optional step.
  • the source ES sends the connection information of the target AS to the UE.
  • the connection information of the target AS includes address information of the target AS.
  • the connection information of the target AS may be information such as the IP address of the target AS, the URI of the target AS, the URL of the target AS, or the endpoint (end point) of the target AS.
  • the source ES may send the connection information of the target AS to the AC in the UE.
  • the UE receives the connection information of the target AS, and establishes a connection with the target AS.
  • FIG. 8 is only an exemplary illustration.
  • the method for application migration subscribes the user plane event management notification to the core network element through the source ES, so that when the user plane path of the PDU session of the UE changes, it can receive the information sent by the core network element.
  • the third notification message, and the target AS is determined based on the first information included in the third notification message, and the application migration is triggered.
  • the target AS determined by the method based on the location information of the UE after the user plane path of the PDU session of the UE is changed is relatively accurate, so the delay when the UE accesses the target AS is small.
  • the source ES triggers the reselection and application migration of the target AS, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • FIG. 9 The schematic flowchart of the method for application migration provided by the embodiment of the present application is shown in FIG. 9 , which involves the interaction between the source AS, the source ES, the PCF entity/SMF entity and the UE, and includes the following steps:
  • the source AS subscribes the user plane management event notification to the source ES.
  • the user plane management event notification is used to notify the source AS when the user plane path of the UE's PDU session changes.
  • the source ES subscribes the user plane management event notification to the PCF entity or the SMF entity.
  • the user plane management event notification is used to notify the source ES when the user plane path of the UE's PDU session changes.
  • the PCF entity or the SMF entity sends a third notification message to the source ES.
  • the third notification message is used to notify the source ES that the user plane path of the PDU session of the UE is changed. That is, when the PCF entity or the SMF entity determines that the user plane path of the PDU session of the UE is changed, the PCF entity or the SMF entity sends the third notification message to the source ES.
  • the third notification message may include the first information.
  • the first information reference may be made to the foregoing embodiments, and details are not repeated here.
  • step S903 is in response to the notification of the user plane management event subscribed by the source ES to the PCF entity or the SMF entity in step S902.
  • the source ES receives the third notification message.
  • the source ES sends a second notification message to the source AS.
  • the second notification message is used to notify the source AS that the user plane path of the PDU session of the UE is changed. That is, when the source ES determines that the user plane path of the PDU session of the UE is changed, the source ES sends the second notification message to the source AS.
  • the second notification message may include the first information.
  • the first information may be the DNAI of the UE after the user plane path of the PDU session of the UE is changed.
  • step S905 is in response to the notification of the user plane management event subscribed by the source AS to the source ES in step S901.
  • the source AS receives the second notification message.
  • the source AS determines the target AS based on the first information.
  • the source AS may determine the target AS based on the first information included in the second notification message.
  • the source AS can send a request to the 5GC network element to obtain the first information, and based on the first information obtained from the 5GC network element Determine the target AS.
  • the source AS determines the specific implementation of the target AS based on the first information, and can refer to the implementation of the source AF to determine the target AS based on the first information in step S602, which will not be repeated here.
  • the application migration refers to migrating the application server accessed by the UE from the source AS to the target AS.
  • the source ES may also trigger the application migration.
  • the source AS may send the connection information of the target AS to the source ES, so that The source ES migrates the context of the UE from the source AS to the target AS based on the connection information of the target AS.
  • step S908 in FIG. 9 is an optional step.
  • the source AS sends the connection information of the target AS to the UE.
  • S910 The UE receives the connection information of the target AS, and establishes a connection with the target AS.
  • the application migration method uses the source AS to subscribe the user plane event management notification to the source ES, and the source ES subscribes the user plane event management notification to the core network element, so that the user plane event management notification in the PDU session of the UE can be subscribed.
  • the source ES receives the notification message sent by the core network element and sends a notification to the source AS.
  • the source AS can determine the target AS based on the first information included in the notification sent by the source ES, and trigger application migration.
  • the target AS determined by the method based on the location information of the UE after the user plane path of the PDU session of the UE is changed is relatively accurate, so the delay when the UE accesses the target AS is small.
  • the source AS triggers the reselection and application migration of the target AS, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • FIG. 10 The schematic flowchart of the method for application migration provided by the embodiment of the present application is shown in FIG. 10 , which involves the interaction between the source AS, the source ES, the EEC in the UE, the OS in the UE, and the AC in the UE, including the following steps:
  • the source AS subscribes the user plane management event notification to the source ES.
  • the user plane management event notification is used to notify the source AS when the user plane path of the UE's PDU session changes. It can be understood that the user plane path change of the PDU session of the UE includes the re-establishment of the PDU session of the UE.
  • the EEC in the UE subscribes to the OS in the UE for a session re-establishment event notification.
  • the session re-establishment event notification is used to notify the EEC in the UE when the UE's PDU session is re-established.
  • the OS in the UE sends a sixth notification message to the EEC in the UE.
  • the sixth notification message is used to notify the EEC in the UE that the PDU session of the UE is re-established. That is, when the OS in the UE determines that the PDU session of the UE is reestablished, the OS in the UE sends the sixth notification message to the EEC in the UE.
  • the sixth notification message includes the first information.
  • the sixth notification message in step S1003 is in response to the notification of the session re-establishment event subscribed by the EEC in the UE to the OS in the UE in step 1002 .
  • the EEC in the UE receives the sixth notification message.
  • the EEC in the UE sends a fourth notification message to the source ES.
  • the fourth notification message is used to notify the source ES that the PDU session of the UE is reestablished. That is, when the EEC in the UE determines that the PDU session of the UE is reestablished, the EEC in the UE sends the fourth notification message to the source ES.
  • the fourth notification message includes the first information.
  • the fourth notification message sent by the EEC in the UE to the source ES in step S1005 may include the new DNAI, and/or the new IP address, and/or the location identification information of the UE in the network.
  • the source ES receives the fourth notification message.
  • the source ES can send a request to the 5GC network element (such as the AMF entity or the SMF entity, etc.) to obtain the first information, such as obtaining the UE in the network from the AMF entity. location identification information, or obtain the DNAI corresponding to the UPF currently serving the UE from the SMF entity, or obtain the IP address of the current UE from the SMF entity or the UPF entity, etc.
  • the 5GC network element such as the AMF entity or the SMF entity, etc.
  • the source ES sends a second notification message to the source AS.
  • the second notification message is used to notify the source AS that the user plane path of the PDU session of the UE is changed. That is, when the source ES determines that the user plane path of the PDU session of the UE changes, the source ES sends the second notification message to the source AS.
  • the second notification message may include the first information.
  • step S1007 is in response to the notification of the user plane management event subscribed by the source AS to the source ES in step S1001.
  • the source AS receives the second notification message.
  • the source AS determines the target AS based on the first information.
  • the source AS may determine the target AS based on the first information included in the second notification message.
  • the source AS can send a request to the 5GC network element to obtain the first information, and based on the first information obtained from the 5GC network element Determine the target AS.
  • the source AS can query the 5GC network element for the path information of the IP address of the UE, and based on The path information determines the target AS.
  • the source AS can establish an AF policy association according to the IP address, and query the path information of the session (for example, the DNAI corresponding to the session) or the location information of the UE through the AF policy association, and determine the target based on the DNAI or the location information of the UE AS.
  • the source AS determines the specific implementation manner of the target AS based on the first information, and can refer to the implementation manner of the source AF determining the target AS based on the first information in step S602, which will not be repeated here.
  • the source AS triggers application migration.
  • the source ES may also trigger the application migration.
  • the source AS may send the connection information of the target AS to the source ES, so that The source ES migrates the context of the UE from the source AS to the target AS based on the connection information of the target AS.
  • step S1010 in FIG. 10 is an optional step.
  • the source AS sends the connection information of the target AS to the UE.
  • the connection information of the target AS includes address information of the target AS.
  • the connection information of the target AS may be information such as the IP address of the target AS, the URI of the target AS, the URL of the target AS, or the endpoint (end point) of the target AS.
  • the source AS may send the above-mentioned connection information of the target AS to the AC in the UE.
  • the UE receives the connection information of the target AS, and establishes a connection with the target AS.
  • FIG. 10 is only an exemplary illustration.
  • the method for application migration subscribes the session re-establishment event notification to the OS in the UE through the EEC in the UE, so that when the PDU session of the UE is re-established, the OS in the UE can notify the EEC in the UE.
  • the EEC in the UE notifies the source ES, the source ES sends a notification to the source AS, and the source AS can determine the target AS based on the information included in the notification sent by the source ES, and trigger application migration.
  • the target AS determined by the method based on the location information of the UE after the user plane path of the PDU session of the UE is changed is relatively accurate, so the delay when the UE accesses the target AS is small.
  • the source AS triggers the reselection and application migration of the target AS, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • FIG. 11 is a schematic flowchart of the method for application migration provided by the embodiment of the present application, which involves the interaction between the source ES, the EEC in the UE, the OS in the UE, and the AC in the UE, including the following steps:
  • the EEC in the UE subscribes to the OS in the UE for a notification of a session re-establishment event.
  • the OS in the UE sends a sixth notification message to the EEC in the UE.
  • the EEC in the UE receives the sixth notification message.
  • the EEC in the UE sends a fourth notification message to the source ES.
  • the source ES receives the fourth notification message.
  • the source ES determines the target AS based on the first information.
  • the source ES may determine the target AS based on the first information included in the fourth notification message.
  • the source ES can send a request to the 5GC network element to obtain the first information, and based on the first information obtained from the 5GC network element Determine the target AS.
  • the source ES determines the specific implementation manner of the target AS based on the first information, and can refer to the implementation manner of the source AF determining the target AS based on the first information in step S602, which is not repeated here.
  • the source ES triggers application migration.
  • the source AS may also trigger the application migration.
  • the source AS may send the connection information of the target AS to the source AS, so that the connection information of the target AS is sent to the source AS.
  • the source AS migrates the context of the UE from the source AS to the target AS based on the connection information of the target AS.
  • step S1107 in FIG. 11 is an optional step.
  • the source ES sends the connection information of the target AS to the UE.
  • the source ES may send the connection information of the target AS to the AC in the UE.
  • the UE receives the connection information of the target AS, and establishes a connection with the target AS.
  • FIG. 11 is only an exemplary illustration.
  • the method for application migration subscribes the session reestablishment event notification to the OS in the UE through the EEC in the UE, so that when the PDU session of the UE is reestablished, the OS in the UE notifies the EEC in the UE, and the EEC in the UE can Notify the source ES, the source ES determines the target AS, and triggers application migration.
  • the target AS determined by the method based on the location information of the UE after the user plane path of the PDU session of the UE is changed is relatively accurate, so the delay when the UE accesses the target AS is small.
  • the source ES triggers the reselection and application migration of the target AS, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • FIG. 12 The schematic flowchart of the method for application migration provided by the embodiment of the present application is shown in FIG. 12 , which involves the interaction between the source AS, the target ES, the EEC in the UE, the OS in the UE, and the AC in the UE, including the following steps:
  • the EEC in the UE subscribes to the OS in the UE for a session re-establishment event notification.
  • the OS in the UE sends a sixth notification message to the EEC in the UE.
  • the EEC in the UE receives the sixth notification message.
  • the EEC in the UE learns that the PDU session of the UE is re-established based on the sixth notification message, and determines that application switching is required.
  • the EEC in the UE determines the target ES based on the first information.
  • the EEC in the UE may determine the target ES based on the first information in the sixth notification message.
  • the target ES and the source ES are the same ES. In another implementation, the target ES is a different ES from the source ES.
  • the target ES may be an ES deployed in a DN accessible to the UE.
  • the EEC in the UE sends a discovery request to the target ES.
  • the discovery request is used to request the list of ASs managed by the target ES.
  • the AS list may be an AS list of an application serving the same as the source AS.
  • the discovery request is used to request the list of ASs of Tencent Video managed by the target ES.
  • the discovery request may include identification information of the source AS.
  • the target ES receives the discovery request.
  • the target ES sends the first message to the EEC in the UE.
  • the first message includes connection information of one or more ASs managed by the target ES.
  • the one or more ASs may serve the same application as the source AS.
  • the target ES sends the connection information of all Tencent Video ASs managed by it to the UE.
  • the EEC in the UE receives the first message, and determines the target AS from one or more ASs managed by the target ES based on the first message.
  • the EEC in the UE may select one AS as the target AS from one or more ASs managed by the target ES.
  • the first message includes the priorities of one or more ASs, and the EEC selects the AS with the highest priority as the target AS.
  • the EEC in the UE sends the connection information of the target AS to the AC in the UE.
  • the AC in the UE receives the connection information of the target AS, and establishes a connection with the target AS.
  • the AC in the UE sends the connection information of the target AS to the source AS.
  • the AC in the UE may also send the connection information of the target AS to the source ES, so that the source ES receives the connection information of the target AS and migrates the context of the UE from the source AS to the target AS.
  • the source AS receives the connection information of the target AS, and triggers application migration.
  • the source AS may perform state transition between the source AS and the target AS, or referred to as application context transition.
  • the application migration refers to migrating the context of the UE from the source AS to the target AS.
  • the source ES may receive the connection information of the target AS in step S1212 and trigger application migration. That is, in this embodiment, the source AS may trigger the application migration, or the source ES may trigger the application migration.
  • the source AS or the source ES may perform context synchronization between the source AS and the target AS.
  • FIG. 12 is only an exemplary illustration.
  • the method for application migration subscribes the session re-establishment event notification to the OS in the UE through the EEC in the UE, so that when the PDU session of the UE is re-established, the OS in the UE can notify the EEC in the UE.
  • the EEC in the UE determines the target AS, and sends the connection information of the target AS to the source ES or the source AS, and the source ES or the source AS triggers the application migration.
  • the target AS determined by the method based on the location information of the UE after the user plane path of the PDU session of the UE is changed is relatively accurate, so the delay when the UE accesses the target AS is small.
  • the source ES or the source AS triggers the reselection and application migration of the target AS, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • the source ES can obtain the information of the PDU session of the UE from the PCF entity/SMF entity.
  • the user plane path changes, but since the source ES does not know which AS in the source DN the UE is currently visiting, the source ES will send to all the ASs deployed in the source DN to indicate that the user plane path of the UE's PDU session has changed
  • the UE may only access the AS of Tencent Video in the source DN. Therefore, the notification message sent by the source ES to other ASs (ASs that are not visited by the UE deployed in the source DN) is invalid.
  • the notification message sent by the source ES to the source AS is invalid.
  • the embodiment of the present application further provides a method for application migration.
  • the method sends a subscription request to the source ES through the source AS, so that when the source ES determines that the target AS exists, the The source AS sends a notification message including the connection information of the target AS, so invalid notifications in the application migration process can be reduced.
  • FIG. 13 The schematic flowchart of the method for application migration provided by the embodiment of the present application is shown in FIG. 13 , which involves the interaction between the source AS, the source ES, the PCF entity/SMF entity, the target AS, and the UE, including the following steps:
  • the source AS sends a subscription request to the source ES.
  • the subscription request is used to notify the source AS when the source ES determines that the target AS exists.
  • the subscription request may also be used to notify the source AS when the source ES determines that the target AS exists in the DN accessible to the UE.
  • the subscription request may be an application switching event notification, and the name of the subscription request is not limited.
  • the subscription request may include application identification information.
  • the application identification information is identification information corresponding to the application, such as application ID, or the application identification information is identification information of the server corresponding to the application, such as EAS ID (edge application server ID).
  • the target AS and the source AS serve the same application. That is, the application identifier (edge application server ID, EAS ID) of the target AS and the source AS are the same.
  • the source ES obtains an available AS or an accessible AS from the target ES or CS, and determines that the target AS exists in the DN accessible to the UE, which can be used to switch the application server accessed by the UE from the source AS to the target AS, thereby Improve user experience, such as lower latency, higher bandwidth, etc.
  • the source AS may send a subscription request to the source ES.
  • the DN accessible to the UE may be one or more data networks that the UE can access from the moved location. It can be understood that after the UE moves, the AS that serves the same application as the source AS may not necessarily be deployed in the data network that the UE can access. Therefore, by sending a subscription request, the source ES can determine that the data network that the UE can access exists in the data network that the UE can access. When the source AS serves the AS of the same application, it notifies the source AS, and then initiates application migration.
  • the DN has a specific service range or service area, and when the UE enters the specific service range or service area, the DN can be regarded as a DN accessible to the UE, otherwise, the DN can be regarded as a DN accessible to the UE.
  • the DN is not a DN accessible by the UE in the current location. It should be understood that under the current location of the UE, there may be 0, 1 or more DNs that can be accessed. That is, the above subscription request can be used to notify the source AS when the source ES determines that there is a UE at the current location that the target AS can serve, and the target AS and the source AS serve the same application.
  • an AS has a specific service range or service area.
  • the AS can serve the UE in the current location. Otherwise, it can be considered that the AS cannot serve the UE in the current location.
  • UE It should be understood that the source ES determines that the target AS exists in the DNs accessible to the UE and the source ES determines that the target AS can serve the current location of the UE has the same meaning. In the following, only the source ES determines that the target AS exists in the accessible DNs of the UE. Take an example to illustrate.
  • step S1301 may also be that the source AS sends to the source ES indication information for indicating whether the source AS supports application handover, or whether the application corresponding to the source AS supports handover.
  • the source AS sends the indication information for indicating that the source AS supports application handover to the source ES, so that when the source ES determines that the target AS exists in the DN accessible to the UE, the source ES can directly determine to perform application migration or the source ES. Be sure to perform an app migration.
  • the application migration in the embodiments of the present application may also be called application switching, that is, switching the context of the UE from the source AS to the target AS.
  • the subscription request may further include information about the PDU session of the UE.
  • the information of the PDU session of the UE includes at least one of the UE's network protocol IP address, data network name (data netword name, DNN), or single network slice selection assistance information (S-NSSAI) .
  • the source ES may determine the policy control function PCF entity or the session management function SMF entity according to the information of the PDU session of the UE included in the subscription request.
  • the subscription request includes application identification information
  • the source ES may determine the target AS based on the application identification information, and notify the source AS when the source ES determines that there is a UE at the current location that the target AS can serve.
  • the source ES may determine the application identification information corresponding to the source AS according to the received subscription request of the source AS
  • the source ES subscribes to the PCF entity or the SMF entity for a notification of user plane management events, where the notification of the user plane management event is used to notify the source ES when the user plane path of the PDU session of the UE changes.
  • the user plane path change of the PDU session of the UE includes re-establishment of the PDU session of the UE.
  • the source ES subscribes to the AMF entity for notification of mobility events or location change events of the UE, where the mobility event or location change event notification is used to notify the source ES when the location of the UE changes.
  • the granularity of the location change may include cell change, RAN change, TA change, RA change, etc. of the UE, which is not limited in this application.
  • the source ES subscribes to the PCF entity, the SMF entity or the AMF entity for the notification.
  • the source ES can directly subscribe to the PCF entity, the SMF entity or the AMF entity, or it can be subscribed through other entities, such as NEF. This application does not do this. limited.
  • the SSC mode of the PDU session of the UE may be SSC mode1, SSC mode2 or SSC mode3.
  • the PCF entity or the SMF entity sends a third notification message to the source ES.
  • the third notification message in step S1303 is in response to the user plane management event notification subscribed by the source ES to the PCF entity or the SMF entity in step S1302, or it can also be in response to the source ES subscribed to the AMF entity in step S1302 for location change.
  • Event notification may include the first information.
  • the first information For the relevant description of the first information, reference may be made to the foregoing embodiments, and details are not repeated here.
  • the AMF entity may also send a third notification message to the source ES.
  • the third notification message may be an ealier notification sent by the SMF or the PCF, which is used to indicate that the source ES 5GC will or wants to switch the user plane path of the UE session.
  • the source ES receives the third notification message.
  • the source ES determines whether there is a target AS.
  • the source ES determines whether the target AS exists in the DN accessible to the UE according to the first information, including: the source ES may request the CS or the target ES to determine whether the target AS exists in the DN accessible to the UE.
  • the source ES sends the first information and the application identification information to the CS
  • the CS determines the target ES based on the first information and the application identification information
  • the CS sends the target ES to the source ES
  • the source ES obtains the UE from the target ES
  • There are one or more ASs in the accessible DNs where the target ES is located in the DNs accessible by the UE.
  • the target ES sends the information of one or more ASs to the source ES.
  • the target ES can determine one and send it to the source ES, or it can send the information of multiple ASs to the source ES.
  • the ES determines the target AS.
  • the source ES sends the first information and the application identification information to the CS, and the CS determines, based on the first information and the application identification information, that there are one or more ASs in the DNs accessible to the UE, and the CS sends one or more ASs to the DNs accessible to the UE.
  • the information of multiple ASs is sent to the source ES, and the source ES determines the target AS.
  • the source ES sends the first information and the application identification information to the target ES, and the target ES determines, based on the first information and the application identification information, that one or more ASs exist in the DN corresponding to the target ES, and the target ES sends The information of one or more ASs is sent to the source ES, which determines the target AS. If the source ES obtains the target AS from the target ES or CS, the source ES determines that there is an accessible target AS; otherwise, the source ES determines that there is no accessible target AS.
  • the above-mentioned source ES and the target ES may be the same ES, and the interaction between the source ES and the target ES can be skipped.
  • the above-mentioned information of the AS may be the connection information of the AS.
  • the source ES determining whether the target AS exists may include: the source ES determines whether the target AS exists according to the first information and the application identification information.
  • the first information included in the third notification message is the DNAI corresponding to the user plane path of the PDU session of the UE. If the source ES determines that there is an AS corresponding to the application identification information in the DN corresponding to the DNAI, the source ES The ES determines that the target AS exists.
  • the source ES determines that there is no AS corresponding to the application identification information in the DN corresponding to the DNAI, then the source ES can send the first information and the application identification information to the CS or the target ES to determine the target AS, and the method is the same as described above, No longer.
  • the source ES determines that the target AS does not exist in the DN accessible to the UE, that is, the DN accessible to the UE does not deploy an AS serving the same application as the source AS, then the source ES will not send a notification message to the source AS. Or send a notification message that the target AS does not exist, the source AS will not trigger application migration, and the UE will continue to visit the source AS.
  • the source ES after receiving the third notification message, performs the step of determining whether the target AS exists in the DN accessible to the UE.
  • the source ES after detecting that the source AS is overloaded, performs the step of determining whether the target AS exists in the DNs accessible to the UE. In other cases, this step is not performed to save computing resources.
  • steps S1305-S1314 are continued.
  • the source ES sends a seventh notification message to the source AS.
  • the source ES when the source ES determines that the target AS exists in the DN accessible to the UE, the source ES sends a seventh notification message to the source AS.
  • the seventh notification message includes connection information of the target AS.
  • the source ES may send a notification message indicating that the target AS does not exist in the DN accessible to the UE to the source AS.
  • the source ES may send a notification message to the source AS indicating that there is no UE that the target AS can serve the current location.
  • the source AS sends indication information to the source ES, the indication information is used to indicate that the source AS supports application switching, and if the source ES determines that there is an accessible target AS, the source ES can directly determine that application migration needs to be performed. , or the source ES determines to perform application migration. Subsequent steps that the source AS determines that application migration needs to be done can be skipped.
  • the source ES directly determines that application migration is required, the source ES sends a seventh notification message to the source AS, and the seventh notification message instructs the source AS to send the context of the UE to the source AS.
  • the seventh notification message in step S1305 is in response to the subscription request sent by the source AS to the source ES in step S1301.
  • the source ES determines that the target AS exists in the DN accessible to the UE, the source ES sends a seventh notification message to the source AS.
  • the source AS receives the seventh notification message.
  • the source AS determines to migrate the context of the user equipment UE from the source AS to the target AS.
  • Step S1307 may also be that the source AS determines that application migration needs to be performed, or the source AS determines to perform application migration.
  • the application migration refers to migrating the context of the UE from the source AS to the target AS.
  • the application migration refers to application context migration, that is, the context on the source AS is migrated to the target AS.
  • the context of the UE may also be called the application context, and the name of the context is not limited.
  • the source AS sends the UE's context to the target AS.
  • the source AS sends the context of the UE to the source ES, and then the source ES sends the context to the target AS, wherein the source ES may need to send the context to the target AS through the target ES.
  • the source AS may also send fourth indication information to the source ES, where the fourth indication information is used to instruct the source ES to migrate the context of the UE from the source AS to the target AS.
  • the source AS receives a seventh notification message, where the seventh notification message includes connection information of the target AS, and the source AS determines that application migration needs to be performed.
  • the source AS may determine whether application migration needs to be performed according to different scenarios, that is, the source AS may determine that application migration needs to be performed, or may determine that application migration is not required. For example, the source AS may determine that it is currently not suitable for application migration according to factors such as load and service urgency, which is not limited in this application.
  • the source AS performs application migration after receiving it.
  • the source AS may directly determine to trigger application migration. That is, when the target AS exists in the DN accessible to the UE, the source AS directly determines to trigger the application migration.
  • steps S1308-S1311 may also be included before the above step S1307.
  • the source AS may negotiate with the target AS to determine whether application migration can be performed currently.
  • the source AS sends an application switching request message to the target AS.
  • the application switching request message is used to migrate the context on the source AS to the target AS.
  • the first request message may also be used to request the target AS to allocate resources required for application switching.
  • the target AS receives the application switching request message.
  • the target AS sends an application switching response message to the source AS.
  • the application switching response message includes third indication information, where the third indication information is used to indicate whether the target AS agrees or accepts the application switching.
  • the target AS may determine whether to approve or accept the application switching request according to its resource usage. If the remaining resources of the target AS are relatively large, the target AS determines to agree to accept the application switching.
  • the third indication information may indicate that the target AS agrees to the application switching.
  • the source AS receives an application switching response message.
  • the determination by the source AS to migrate the context of the user equipment UE from the source AS to the target AS in the above step S1307 may include: the source AS determines to migrate the context of the user equipment UE from the source AS to the target AS based on the third indication information. If the third indication information in the application switching response message indicates that the target AS agrees to the application switching, the source AS determines to trigger the application migration.
  • the source AS sends fifth indication information to the source ES, where the fifth indication information is used to indicate whether the source AS supports application switching or whether the source AS agrees to the application switching or whether the source AS performs application switching. It can be understood that the fifth indication information is in response to the seventh notification message. That is, after the source ES sends the seventh notification message indicating that the target AS exists in the DNs accessible to the UE to the source AS, the source AS sends fifth indication information indicating whether the source AS supports application handover to the source ES.
  • the source ES sends sixth indication information to the 5GC (such as SMF, PCF or AMF), where the sixth indication information is used to indicate whether the source AS supports application switching, which is understandable , the sixth indication information is in response to the third notification message.
  • the 5GC may determine whether to terminate the user plane path of the handover session based on the sixth indication information. For example, if the sixth indication information indicates that the source AS does not support application switching, the SMF terminates switching the user plane path of the PDU session of the UE after receiving the sixth indication information sent by the source ES.
  • the source AS may also send seventh indication information to the source ES, where the seventh indication information is used to indicate that service continuity needs to be maintained during application switching.
  • the seventh indication information is used to establish a forwarding tunnel between UPFs when the DNAI changes, for service continuity, so that the UE can send application data to the source AS.
  • the source ES sends eighth indication information to the SMF or PCF, where the eighth indication information is used to indicate that service continuity needs to be maintained during application switching. Therefore, after the source ES completes the handover, the 5GC network element can release the forwarding tunnel by sending the eighth indication information to the 5GC network element.
  • the source AS triggers application migration.
  • step S1312 in FIG. 13 is an optional step.
  • the source AS when the source AS receives the connection information of the target AS, the source AS triggers application migration.
  • the source AS sends the application context directly to the target AS.
  • the source AS sends the application context to the source ES
  • the source ES sends the context to the target ES
  • the target ES sends the context to the target AS.
  • the source AS sends the connection information of the target AS to the UE.
  • the source ES may also send the connection information of the target AS to the UE, or, the source ES may also send the connection information of the target AS to the 5GC network element (for example, SMF or PCF), and then the 5GC may send the connection information of the target AS to the UE.
  • the network element sends the connection information of the target AS to the UE.
  • the UE receives the connection information of the target AS, and establishes a connection with the target AS.
  • connection information of the target AS that can be received by the UE may come from a source AS, a source ES, a 5GC network element, or other devices, which is not limited in this embodiment of the present application.
  • FIG. 13 is only an exemplary illustration.
  • the application migration method provided in this embodiment sends a subscription request to the source ES through the source AS, so that when the source ES determines that the target AS exists, it can send a notification message including the connection information of the target AS to the source AS, and then send the notification message to the source AS.
  • Application migration is triggered by the source AS. After the user plane path of the UE's PDU session is changed, the data network accessible to the UE may not necessarily deploy an AS serving the same application as the source AS. Therefore, by sending a subscription request, the source ES can determine the data that the UE can access. When there is an AS serving the same application as the source AS in the network, the source AS is notified again, and then application migration is initiated. Therefore, invalid notifications during the application migration process can be reduced and delays can be reduced.
  • this embodiment of the present application further provides a method for application migration, the method may include: the source AS sends indication information for indicating whether the source AS supports application switching to the source ES, and the source ES receives the indication information.
  • the source ES subscribes the user plane management event notification or mobility event notification to the 5GC network element, and when the user plane path of the UE's PDU session changes or the UE's location changes, the 5GC network element sends a third notification message to the source ES.
  • the source ES receives the third notification message, and determines whether the target AS exists in the DN accessible to the UE based on the first information.
  • the source ES determines that the target AS exists in the DN accessible to the UE, the source ES determines to perform application migration, the source ES can request the source AS for the context on the source AS, and the source AS can The context is migrated to the target AS.
  • this embodiment of the present application also provides a method for application migration, which involves How to update network information in the process of application migration
  • the UE sends first indication information to the CS.
  • the first indication information is used to instruct the CS to send the information of the target DN to the UE when the user plane path of the PDU session of the UE changes.
  • the user plane path change of the PDU session of the UE includes the re-establishment of the PDU session of the UE.
  • the SSC mode of the PDU session of the UE may be SSC mode3, and when the session of the PDU of the UE is reestablished, the data network accessed by the UE may be switched accordingly.
  • the CS may be the ECS in FIG. 2
  • the DN may be the EDN in FIG. 2 .
  • the CS receives the first indication information.
  • the CS subscribes the user plane management event notification to the PCF entity or the SMF entity.
  • the user plane management event notification is used to notify the CS when the user plane path of the UE's PDU session is changed.
  • the PCF entity or the SMF entity sends a fifth notification message to the CS.
  • the fifth notification message is used to notify the CS that the user plane path of the PDU session of the UE is changed. That is, when the PCF entity or the SMF entity determines that the user plane path of the PDU session of the UE is changed, the PCF entity or the SMF entity sends the fifth notification message to the CS.
  • the fifth notification message may include the first information.
  • the first information reference may be made to the foregoing embodiments, and details are not repeated here.
  • the fifth notification message in step S1404 is in response to the notification of the user plane management event subscribed by the CS to the PCF entity or the SMF entity in step S1403.
  • the CS receives the fifth notification message.
  • the CS determines the target DN based on the first information.
  • the CS may determine the target DN based on the first information included in the fifth notification message.
  • the first information is the DNAI of the UE.
  • the CS may also query the PCF entity or the SMF entity for the information of the UPF based on the first information included in the fifth notification message, and determine the target DN based on the information of the UPF.
  • the CS may query the PCF entity or the SMF entity for the DNAI based on the IP address of the UE included in the fifth notification message, and determine the target DN based on the DNAI.
  • the CS sends the information of the target DN to the UE.
  • the UE receives the information of the target DN, and establishes a connection with the target DN.
  • the UE instructs the CS to send the information of the target DN to the UE when the PDU session of the UE is re-established, so that when the PDU session of the UE is re-established, the CS can send the information of the target DN to the UE, so that the UE can access the information of the target DN to the UE.
  • Target DN the information of the target DN to the UE when the PDU session of the UE is re-established.
  • an embodiment of the present application further provides a method for application migration, which involves how to update network information during the process of application migration. Interaction, including the following steps:
  • the UE sends first indication information to the CS.
  • the first indication information is used to instruct the CS to send the information of the target DN to the UE when the user plane path of the PDU session of the UE changes.
  • the user plane path change of the PDU session of the UE includes the re-establishment of the PDU session of the UE.
  • the data network accessed by the UE can be switched accordingly.
  • the CS may be the ECS in FIG. 2
  • the DN may be the EDN in FIG. 2 .
  • the SSC mode of the PDU session of the UE may be SSC mode3.
  • the CS receives the first indication information.
  • S1503 The UE sends the second indication information to the CS.
  • the second indication information is used to indicate that the PDU session of the UE is re-established.
  • the second indication information includes the first information.
  • the CS receives the second indication information.
  • the CS determines the target DN based on the first information.
  • the CS may determine the target DN based on the first information included in the second indication information.
  • the first information is the DNAI of the UE.
  • the CS may query the PCF entity or the SMF entity for the DNAI, and The target DN is determined based on the DNAI.
  • the CS sends the information of the target DN to the UE.
  • the UE receives the information of the target DN, and establishes a connection with the target DN.
  • FIG. 15 is only an exemplary illustration.
  • the difference between the embodiment shown in FIG. 14 and the embodiment shown in FIG. 15 is that the embodiment shown in FIG. 14 is to subscribe the user plane management event notification to the PCF entity or the SMF entity through the CS to learn the PDU session of the UE.
  • the UE sends indication information to the CS to inform the CS that the PDU session of the UE is re-sent after the session is re-established. That is to say, the difference between the embodiment shown in Fig. 14 and the embodiment shown in Fig. 15 is that the CS learns that the UE's PDU session transmission re-establishment is different.
  • the UE instructs the CS to send the information of the target DN to the UE when the PDU session of the UE is reestablished, and notify the CS when the PDU session of the UE is reestablished, so that the CS can determine the target DN and send the information of the target DN to the UE, so that the UE can access the target DN.
  • FIG. 16 The schematic flowchart of the method for application migration provided by the embodiment of the present application is shown in FIG. 16 , which involves the target ES, CS, 5GC network element (such as SMF, UPF, or other entities that allocate IP) and UE (which may include AC, EEC, etc.). , OS, etc.), including the following steps:
  • the 5GC network element sends the first information to the UE.
  • the 5GC network element may be an SMF entity, a UPF entity or other network elements that allocate IP.
  • the SSC mode of the session established by the UE is mode 3.
  • the UE obtains a new IP address from the 5GC network element, and the new IP address can be The IP address of the UE corresponding to the newly inserted anchor UPF when the IP address of the UE after re-establishing the PDU session or using the multi-homed session creation mechanism to implement SSC mode 3.
  • the new IP address may be allocated by the SMF entity, may also be allocated by the UPF entity, may also be allocated by the DN-AAA, or may be allocated by other entities, which are not limited in this application.
  • the 5GC network element (such as the SMF network element) may also send the anchor UPF of the new session or the DNAI corresponding to the anchor UPF newly inserted in the multi-homed session to the UE.
  • the UE receives the first information.
  • the first information may be received by the EEC module in the UE, the AC module in the UE, or the OS in the UE, which is not limited in this application.
  • the UE sends the first information to the CS.
  • the first information may be included in the Service provisioning Request.
  • the EEC module in the UE may send the first information to the CS.
  • the CS receives the first information.
  • the CS determines the target ES based on the first information.
  • the UE sends a new IP address to the CS. If the CS is configured with a mapping relationship between the IP address (segment) and the target ES or DN, the CS can determine the target ES, where the target ES serves the target DN.
  • the UE sends a new IP address to the CS
  • the CS can send a request to the 5GC network element, where the request includes the new IP address, and the request is used to obtain the anchor of the new session of the UE based on the IP address of the UE Click the DNAI corresponding to the newly inserted anchor UPF in the UPF or multi-homed session.
  • the CS is configured with a mapping relationship between the DNAI and the target ES or DN, the CS can determine the target ES.
  • the UE sends a DNAI corresponding to the anchor UPF of the new session or the newly inserted anchor UPF of the multi-homed session to the CS. If the CS is configured with a mapping relationship between the DNAI and the target ES or DN, the CS can determine the target ES. Compared with the second implementation manner, the process of querying the 5GC network element for the DNAI can be omitted.
  • the CS sends the connection information of the target ES to the UE.
  • the CS may also send the connection information of the target ES to the UE.
  • the connection information of the target ES includes address information of the target ES, and the connection information of the target ES may be information such as the IP address of the target ES, the URI of the target ES, the URL of the target ES, and the endpoint (end point) of the target ES.
  • S1607 The UE receives the connection information of the target ES.
  • the EEC module in the UE may receive the connection information of the target ES.
  • S1608 The UE sends a second application discovery request to the target ES.
  • the second application discovery request is used for requesting to acquire the target AS.
  • the EEC module of the UE sends the second application discovery request to the target ES.
  • the second application discovery request includes a new IP address.
  • the second application discovery request includes the application identifier of the source AS.
  • the second application discovery request includes the first information.
  • the target ES receives the second application discovery request.
  • the target ES determines the target AS.
  • the target ES may determine the target AS based on the first information.
  • the target ES may determine the target AS based on the first information.
  • reference may be made to the process of determining the target AS in S602, which will not be repeated here. It can be understood that the target AS determined by the target ES based on the first information has the same application identifier as the source AS.
  • the target ES determines to trigger application migration.
  • the target ES determines that application migration needs to be performed based on receiving the new IP address and the second application discovery request, and the target ES may send the connection information of the target AS to the source ES or the source AS.
  • the target ES may send the connection information of the target AS to the UE.
  • the target ES sends the connection information of the target AS to the UE.
  • the target ES may also send the connection information of the target AS to the UE.
  • the connection information of the target AS includes address information of the target AS, and the connection information of the target AS may be IP address, URI, URL, endpoint (end point) and other information.
  • S1613 The UE receives the connection information of the target AS.
  • the EEC module of the UE receives the connection information of the target AS.
  • the UE determines to trigger application migration.
  • the EEC module of the UE determines that application migration needs to be performed after receiving the connection information of the target AS.
  • the source AS sends the application context directly to the target AS.
  • the source AS sends the application context to the source ES
  • the source ES sends the context to the target ES
  • the target ES sends the context to the target AS.
  • the target ES may determine to trigger application migration
  • the UE may also determine to trigger application migration
  • other network devices may also determine to trigger application migration, which is not limited in this embodiment of the present application.
  • FIG. 16 is only an exemplary illustration.
  • the UE when the PDU session of the UE is reestablished, the UE receives the first information from the 5GC network element, and the UE sends the first information to the CS, and the CS
  • the acquisition target ES is determined based on the first information, and then the UE may acquire the target AS connection information from the target ES.
  • the target ES determined based on the UE's location information after the user plane path of the UE's PDU session is changed is more accurate, and the target AS determined based on the target ES is more accurate, so the delay when the UE accesses the target AS is small.
  • the target ES or EEC triggers the reselection and application migration of the target AS, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • FIG. 17 The schematic flowchart of the method for application migration provided by this embodiment of the present application is shown in FIG. 17 , which involves source ES, target ES, CS, 5GC network element (such as SMF, UPF, or other entity that allocates IP) and UE (which may include The interaction between AC, EEC, OS, etc.) includes the following steps:
  • the 5GC network element sends the first information to the UE.
  • the UE receives the first information.
  • the first information may be received by the EEC module in the UE, the AC module in the UE, or the OS in the UE, which is not limited in this application.
  • the UE sends the first information to the source ES.
  • the EEC module in the UE may send the first information to the source ES.
  • the first information may be included in a request message, and the request message may be an application server discovery request message.
  • the source ES receives the first information.
  • the source ES sends the first information to the CS.
  • the first information sent by the source ES to the CS may be included in a request message, where the request message is used to acquire the target ES from the CS.
  • the CS receives the first information.
  • the CS determines the target ES based on the first information.
  • the CS sends the connection information of the target ES to the source ES.
  • the source ES receives the connection information of the target ES.
  • the source ES sends a first application discovery request to the target ES.
  • the first application discovery request is used to request to acquire the target AS.
  • the first application discovery request includes first information.
  • the first application discovery request is used to acquire the target AS from the target ES.
  • the first application discovery request includes the application identifier of the source AS.
  • the target ES receives the first application discovery request.
  • the target ES determines the target AS.
  • the target ES may determine the target AS based on the first information.
  • the target ES may determine the target ES based on the first information and the application identification information.
  • the target ES to determine the target AS based on the first information reference may be made to the process of determining the target AS in S602, which will not be repeated here.
  • the target ES may also be determined based only on the application identification information.
  • the application identification information is the identification information of the application corresponding to the source AS.
  • the target ES sends the connection information of the target AS to the source ES.
  • the target ES can also directly send the connection information of the target AS to the UE, or the target ES can also send the connection information of the target AS to the CS, and the CS sends the connection information of the target AS to the UE.
  • the source ES receives the connection information of the target AS.
  • the source ES sends the connection information of the target AS to the UE.
  • S1716 The UE receives the connection information of the target AS.
  • the EEC module of the UE receives the connection information of the target AS.
  • the target ES determines that application migration needs to be performed based on receiving the new IP address and the first application discovery request, and then the target ES sends the connection information of the target AS to the source ES or the source AS.
  • the UE determines that application migration needs to be performed.
  • the EEC module of the UE determines that application migration needs to be performed after receiving the connection information of the target AS.
  • the source AS sends the application context directly to the target AS.
  • the source AS sends the application context to the source ES
  • the source ES sends the context to the target ES
  • the target ES sends the context to the target AS.
  • FIG. 17 is only an exemplary illustration.
  • the UE when the PDU session of the UE is reestablished, the UE receives the first information from the 5GC network element, and the UE sends the first information to the source ES, The source ES sends the first information to the CS, and the CS determines the target ES based on the first information, and then the source ES can obtain the connection information of the target AS from the target ES, and send the connection information of the target AS to the UE.
  • the target ES determined based on the UE's location information after the user plane path of the UE's PDU session is changed is more accurate, and the target AS determined based on the target ES is more accurate, so the delay when the UE accesses the target AS is small.
  • the target ES or EEC triggers the reselection and application migration of the target AS, and does not change the AC in the UE. Therefore, the AC is not required to understand the network logic, which can simplify the design of the AC.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • FIG. 18 shows a schematic structural diagram of a communication device 1800.
  • the communication device can be the above-mentioned source AS or a chip in the above-mentioned source AS.
  • the communication device 1800 can be used to implement the method involving the source AS in any of the above-mentioned embodiments. and function.
  • the communication device 1800 includes: a processing unit 1801 and a transceiver unit 1802 .
  • the transceiver unit 1802 may be used to support communication between the source AS and the source ES, PCF entity/SMF entity or UE in the above-mentioned embodiments.
  • the processing unit 1801 is used to control and manage the actions of the above-mentioned source AS, and is used to execute the processing performed by the source AS in the above-mentioned embodiment. Programs or instructions in the memory to enable the communication device 1800 to implement the methods and functions involved in any of the above embodiments.
  • the above-mentioned processing unit 1801 may be configured to perform, for example, steps S602-S603 in FIG. 6 , or steps S704 and S705 in FIG. 7 , or steps S907 and S908 in FIG. 9 , or, steps S907 and S908 in FIG. Steps S1009 and S1010, or, step S1212 in FIG. 12 triggers application migration, or, steps S1307 and S1312 in FIG. 13, and/or other processes for the techniques described herein.
  • the transceiver unit 1802 may be configured to perform, for example, step S601 in FIG. 6 , or steps S701 , S703 and S706 in FIG.
  • steps S1301, S1306, S1308, S1311 and S1313 in FIG. 13, and/or other processes for the techniques described herein are relevant contents of the steps involved in the above method embodiments.
  • the communication device 1800 may be the communication apparatus shown in FIG. 5
  • the processing unit 1801 may be the processor 501 in FIG. 5
  • the transceiver unit 1802 may be the transceiver 503 in FIG. 5
  • the communication device 1800 may further include a memory, where the memory is configured to store program codes and data corresponding to the communication device 1800 executing any of the methods for migrating applications provided above.
  • the descriptions of all the relevant contents of the components involved in the above FIG. 5 can be referred to the functional descriptions of the corresponding components of the communication device 1800 , which are not repeated here.
  • FIG. 19 shows a schematic structural diagram of a communication device 1900.
  • the communication device may be the above-mentioned source ES, or may be a chip in the above-mentioned source ES, and the communication device 1900 may be used to implement the method involving the source ES in any of the above-mentioned embodiments. and function.
  • the communication device 1900 includes: a processing unit 1901 and a transceiver unit 1902 .
  • the transceiver unit 1902 may be configured to support communication between the source ES and the source AS, PCF entity/SMF entity or UE in the above-mentioned embodiments.
  • the processing unit 1901 is used to control and manage the actions of the above-mentioned source ES, and is used to execute the processing performed by the source ES in the above-mentioned embodiment. Programs or instructions in the memory to enable the communication device 1900 to implement the methods and functions involved in any of the above embodiments.
  • the above-mentioned processing unit 1901 can be used to perform, for example, step S602 in FIG. 6 , or steps S804 and S805 in FIG. 8 , or steps S1106 and S1107 in FIG. 11 , and/or for the descriptions described herein. other processes of the technology.
  • the transceiver unit 1902 may be configured to perform, for example, steps S601 and S603 in FIG. 6 , or steps S801 , S803 and S806 in FIG. 8 , or steps S902 , S904 and S905 in FIG. 9 , or steps in FIG. 10 S1006 and S1007, or, steps S1105 and S1108 in FIG.
  • all relevant contents of the steps involved in the above method embodiments can be cited in the functional descriptions of the corresponding functional modules, which will not be repeated here.
  • the communication device 1900 may be the communication apparatus shown in FIG. 5
  • the processing unit 1901 may be the processor 501 in FIG. 5
  • the transceiver unit 1902 may be the transceiver 503 in FIG. 5
  • the communication device 1900 may further include a memory, where the memory is used for storing program codes and data corresponding to the communication device 1900 executing any of the methods for migrating applications provided above.
  • the descriptions of all the relevant contents of the components involved in the above-mentioned FIG. 5 can be referred to the functional descriptions of the corresponding components of the communication device 1900 , which are not repeated here.
  • FIG. 20 shows a schematic structural diagram of a communication device 2000.
  • the communication device may be the above-mentioned UE or a chip in the above-mentioned UE.
  • the communication device 2000 may be used to implement the methods and functions of any of the above-mentioned embodiments related to the UE.
  • the communication device 2000 includes: a processing unit 2001 and a transceiver unit 2002 .
  • the transceiver unit 2002 may be configured to support communication between the UE and the source ES, the source AS, and the target ES in the above embodiments.
  • the processing unit 2001 is used to control and manage the actions of the above-mentioned UE, and is used to perform the processing performed by the UE in the above-mentioned embodiment.
  • the above-mentioned processing unit 2001 may be configured to perform, for example, establishing a connection with the target AS in FIG. 6 to FIG. 13 , or performing the establishing a connection with the target DN in FIG. 14 or FIG. 15 , or performing step S1204 in FIG. 12 . , determining the target AS from one or more ASs managed by the target ES based on the first message in S1208, or, step S1614 in FIG. 16, or, step S1708 in FIG. 17, and/or for use in the process described herein other processes of technology.
  • the transceiver unit 2002 may be configured to perform, for example, receiving connection information of the target AS, or, step S1005 in FIG. 10 , or step S1104 in FIG.
  • the communication device 2000 may be the communication apparatus shown in FIG. 5
  • the processing unit 2001 may be the processor 501 in FIG. 5
  • the transceiver unit 2002 may be the transceiver 503 in FIG. 5
  • the communication device 2000 may further include a memory, where the memory is configured to store program codes and data corresponding to the communication device 2000 executing any of the above-provided application migration methods.
  • the descriptions of all the relevant contents of the components involved in the above FIG. 5 can be referred to the functional descriptions of the corresponding components of the communication device 2000 , which will not be repeated here.
  • FIG. 21 shows a schematic structural diagram of a communication device 2100.
  • the communication device may be the above CS or a chip in the above CS, and the communication device 2100 may be used to implement the methods and functions related to the CS in any of the above embodiments.
  • the communication device 2100 includes: a processing unit 2101 and a transceiver unit 2102 .
  • the transceiver unit 2102 may be configured to support communication between the CS and the PCF entity, the SMF entity or the UE in the above embodiments.
  • the processing unit 2101 is used to control and manage the actions of the above CS, and is used to execute the processing performed by the CS in the above embodiment.
  • the above-mentioned processing unit 2101 may be configured to perform, for example, step S1406 in FIG. 14 , or step S1505 in FIG. 15 , or step S1605 in FIG. 16 , or step S1707 in FIG. 17 , and/or for Other procedures for the techniques described herein.
  • the transceiver unit 2102 may be configured to perform, for example, steps S1402, S1403, S1405, and S1407 in FIG. 14, or steps S1502, S1504, and S1506 in FIG. 15, or steps S1604 and S1606 in FIG. 16, or, in FIG. 17 of steps S1706 and S1708, and/or other processes for the techniques described herein.
  • the communication device 2100 may be the communication apparatus shown in FIG. 5
  • the processing unit 2101 may be the processor 501 in FIG. 5
  • the transceiver unit 2102 may be the transceiver 503 in FIG. 5
  • the communication device 2100 may further include a memory, where the memory is configured to store program codes and data corresponding to the communication device 2100 executing any of the above-provided application migration methods.
  • the descriptions of all the relevant contents of the components involved in the above FIG. 5 can be cited from the functional descriptions of the corresponding components of the communication device 2100 , which will not be repeated here.
  • an embodiment of the present application further provides an apparatus for application migration, where the apparatus for application migration includes a processor, and the processor is configured to execute computer-executed instructions, so as to support the apparatus for application migration to implement any of FIG. 6 to FIG. 17 .
  • the device for application migration may further include a transceiver and a memory, where the transceiver is used to send and receive information, or used to communicate with other network elements; the memory is used to store computer execution instructions.
  • An embodiment of the present application further provides a computer storage medium, where computer program code is stored in the computer storage medium, and when the above-mentioned processor executes the computer program code, the electronic device executes the application in any of the embodiments in FIG. 6 to FIG. 17 . method of migration.
  • Embodiments of the present application further provide a computer program product, which, when the computer program product runs on a computer, enables the computer to execute the application migration method in any of the embodiments in FIG. 6 to FIG. 17 .
  • An embodiment of the present application further provides a communication system, where the communication system includes a source application server AS, a source enabling server ES, and a user equipment UE, wherein the source AS subscribes to the source ES for notification of user plane management events, the The user plane management event notification is used to notify the source AS when the user plane path of the protocol data unit PDU session of the UE changes; the source AS is the AS visited by the UE before the user plane path of the PDU session is changed The source ES obtains first information, and the first information is the location information of the UE after the user plane path of the PDU session of the UE is changed; the source ES sends a second notification message to the source AS, The second notification message is used to notify the source AS that the user plane path of the UE's PDU session is changed, and the second notification message includes first information; the source AS determines the target based on the first information AS, and trigger application migration, the application migration refers to migrating the UE from the source AS to the target AS; the source AS send
  • An embodiment of the present application further provides a chip system, the chip system includes a processor and a memory, and instructions are stored in the memory; when the instructions are executed by the processor, the application migration in any of the foregoing embodiments in FIG. 6 to FIG. 17 is implemented. method.
  • the steps of the methods or algorithms described in conjunction with the disclosure of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory (RAM), flash memory, erasable programmable read-only memory (erasable programmable read-only memory, EPROM), electrically erasable programmable Programmable read only memory (electrically EPROM, EEPROM), registers, hard disk, removable hard disk, compact disk read only memory (CD-ROM), or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist in the core network interface device as discrete components.
  • the functions described in this application may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请实施例公开了一种应用迁移的方法和装置，涉及通信技术领域，解决了现有技术中确定的目标AS不准确，导致UE访问应用服务器的时延较大的问题。具体方案为：源应用功能AF获取第一信息，第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后UE的位置信息；源AF基于第一信息，确定目标应用服务器AS。

Description

一种应用迁移的方法和装置
本申请要求于2020年08月12日提交国家知识产权局、申请号为PCT/CN2020/108751、申请名称为“一种应用迁移的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种应用迁移的方法和装置。
背景技术
在第五代(5rd generation，5G)移动通信网络中，为了提升用户体验，缩短用户访问应用服务器(application server，AS)的时延，运营商或服务提供商可以在本地部署应用服务器。当终端处于移动状态时，可能会存在用户面功能(user plane function，UPF)实体和AS切换的场景。
现有技术提出了一种基于会话和服务连续(session and service continuity，SSC)mode3的应用迁移方法，SSC mode3的特点是在用户设备(user equipment，UE)与先前的协议数据单元(protocol data unit，PDU)会话锚点之间的连接被释放之前，先建立一条经过新PDU会话锚点的连接，从而保证服务的连续性。现有的迁移方法在切换过程中，当UE上的操作系统(operation system，OS)发现建立了新的PDU会话后，OS需要通知应用客户端(app client，AC)，AC收到该通知后触发域名系统(domain name system，DNS)查询，获取New AS地址，AC将New AS的地址发送给Old AS指示Old AS做应用迁移，Old AS与New AS之间进行状态同步之后，UE开始向New AS发送数据包。该方法基于DNS查询确定New AS时，由于DNS的查询结果不够准确，基于该DNS查询结果确定的New AS不是最合适的应用服务器，因此将UE访问的AS迁移至该New AS后，会造成UE访问该New AS的时延较大的问题。
发明内容
本申请实施例提供一种应用迁移的方法和装置，用于更加准确的确定目标AS，减小UE访问应用服务器的时延。
为达到上述目的，本申请实施例采用如下技术方案：
本申请实施例的第一方面，提供一种应用迁移的方法，该方法包括：源应用功能AF获取第一信息，该第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后UE的位置信息；源AF基于该第一信息，确定目标应用服务器AS；源AF向UE发送目标AS的连接信息。基于本方案，通过源AF基于UE的PDU会话的用户面路径改变后UE的位置信息确定目标AS，因此确定的目标AS较准确，UE访问该目标AS时的时延较小，即本方案能够减小UE访问应用服务器的时延。可以理解的，本方案是由网络侧设备(源AF)触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。示例性的，该方案 中的源AF可以为源AS，也可以为源ES，也就是说本申请可以由源AS确定目标AS，也可以由源ES确定目标AS。
结合第一方面，在一种可能的实现方式中，上述目标AS与源AS服务相同的应用，该源AS可以为上述UE的PDU会话的用户面路径改变前上述UE访问的AS。基于本方案，源AF确定的目标AS是与源AS服务相同应用的AS，因此在UE移动过程中，能够确保UE访问的业务的连续性。可选的，UE的PDU会话的用户面路径改变可以理解为UPF改变。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的位置信息为上述UE的IP地址、上述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、UE的跟踪区域标识TAI、UE的小区标识cell ID、UE的无线接入网标识RAN ID或者UE的地理位置信息中的至少一种。基于本方案，源AF可以基于UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息确定目标AS，因此确定的目标AS较为准确。可以理解的，本申请中UE的PDU会话的用户面路径对应的DNAI为UE可接入的数据网络对应的DNAI。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AF基于上述第一信息，确定目标AS，包括：上述源AF基于该第一信息，获取上述UE的PDU会话的用户面路径改变后的用户面功能UPF实体的信息；上述源AF基于该UPF实体的信息，确定上述目标AS。基于本方案，源AF可以根据用户面UPF的信息确定目标AS，因此确定的目标AS较为准确，从而UE访问该目标AS时的时延较小。示例性的，该UPF的信息例如可以为DNAI或其他可以识别UPF的信息。可选的，源AF可以通过向5GC发送查询请求获取UPF的信息。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AF为上述源AS。基于本方案，源AS可以确定目标AS并向UE发送目标AS的连接信息，能够降低UE访问应用服务器的时延。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AF获取上述第一信息，包括：上述源AS接收来自策略控制功能PCF实体或会话管理功能SMF实体的第一通知消息，该第一通知消息用于通知上述源AS上述UE的PDU会话的用户面路径改变，该第一通知消息中包括上述第一信息。基于本方案，源AS通过接收PCF或SMF发送的第一通知消息，可以获知UE的PDU会话的用户面路径发生改变，从而源AS可以基于该通知消息确定目标AS。可选的，该第一通知消息中也可以不包括第一信息，当第一通知消息中不包括该第一信息时，源AS接收第一通知消息后，可以向核心网网元(例如，PCF或SMF)请求获取该第一信息，再基于该第一信息确定目标AS。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源AS向上述PCF实体或上述SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述源AS。基于本方案，通过源AS向PCF或SMF订阅用户面管理事件通知，从而能够在PCF或SMF确定UE的PDU会话的用户面路径改变时通知源AS。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AF 获取上述第一信息，包括：上述源AS接收来自源使能服务器ES的第二通知消息，该第二通知消息用于通知上述源AS上述UE的PDU会话的用户面路径改变，该第二通知消息中包括上述第一信息。基于本方案，源AS通过接收源ES发送的第二通知消息，可以获知UE的PDU会话的用户面路径发生改变，从而源AS可以基于该通知消息确定目标AS并确定进行应用迁移。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源AS向上述源ES订阅用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述源AS。基于本方案，通过源AS向源ES订阅用户面管理事件通知，从而能够在源ES确定UE的PDU会话的用户面路径改变时通知源AS。可选的，源ES可以通过向核心网网元订阅用户面管理事件通知，获知UE的PDU会话的用户面路径改变；源ES也可以通过接收UE发送的通知消息，获知UE的PDU会话的用户面路径改变。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源AS向上述UE发送上述目标AS的连接信息。基于本方案，通过源AS向UE发送目标AS的连接信息，使得UE可以与该目标AS建立连接，从而减小UE访问应用服务器的时延。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AF为源ES。基于本方案，源ES可以确定目标AS并向UE发送目标AS的连接信息，能够降低UE访问应用服务器的时延。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AF获取上述第一信息，包括：上述源ES接收来自PCF实体或SMF实体的第三通知消息，该第三通知消息用于通知上述源ES上述UE的PDU会话的用户面路径改变，该第三通知消息中包括上述第一信息。基于本方案，源ES通过接收PCF或SMF发送的第三通知消息，可以获知UE的PDU会话的用户面路径发生改变，从而源ES可以基于该通知消息确定目标AS。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES向上述PCF实体或上述SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述源ES。基于本方案，通过源ES向PCF或SMF订阅用户面管理事件通知，从而能够在PCF或SMF确定UE的PDU会话的用户面路径改变时通知源ES。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AF获取上述第一信息，包括：上述源ES接收来自上述UE的边缘使能客户端EEC发送的第四通知消息，该第四通知消息用于通知上述源ES上述UE的PDU会话重建，该第四通知消息中包括上述第一信息。基于本方案，源ES通过接收UE的EEC发送的第四通知消息，可以获知UE的PDU会话重建，从而源ES可以基于该通知消息确定目标AS，因此确定的目标AS较为准确，减小了UE访问应用服务器的时延。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES向上述UE发送上述目标AS的连接信息。基于本方案，通过源ES向UE发送目标AS的连接信息，使得UE可以与该目标AS建立连接，从而减小UE 访问应用服务器的时延。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AF为配置服务器CS，上述方法还包括：该CS接收来上述UE的第一指示信息，该第一指示信息用于指示该CS当上述UE的PDU会话的用户面路径改变时，向上述UE发送目标数据网络DN的信息；CS基于上述第一信息，确定目标DN；CS向上述UE发送该目标DN的信息。基于本方案，通过CS基于UE的PDU会话的用户面路径改变后UE的位置信息确定目标DN，因此确定的目标AS较准确，故UE接入该目标DN后能够减小UE访问数据网络的时延。例如，当UE移动时，SMF决定重建PDU会话，CS可以根据重建PDU会话后UE的位置信息确定目标DN，并向UE发送该目标DN的信息，从而UE可以接入该目标DN。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述CS获取第一信息包括：上述CS接收来自上述UE的第二指示信息，该第二指示信息用于指示上述UE的PDU会话发生重建，该第二指示信息中包括上述第一信息。基于本方案，CS可以通过接收UE的指示信息获知UE的PDU会话发生重建，从而CS可以基于该指示信息确定目标DN，因此确定的目标AS较准确，故UE接入该目标DN后能够减小UE访问数据网络的时延。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述CS获取第一信息包括：上述CS接收来自策略控制功能PCF实体或会话管理功能SMF实体的第五通知消息，该第五通知消息用于通知上述CS上述UE的PDU会话的用户面路径改变，该第五通知消息中包括上述第一信息。基于本方案，CS可以通过接收PCF或SMF的通知消息获知UE的PDU会话发生重建，从而CS可以基于该通知消息确定目标DN，因此确定的目标AS较准确。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述CS向上述PCF实体或上述SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述CS。基于本方案，通过CS向PCF或SMF订阅用户面管理事件通知，从而能够在PCF或SMF确定UE的PDU会话的用户面路径改变时通知CS。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的PDU会话的用户面路径改变包括UE的PDU会话锚点改变，UE的PDU会话的会话和服务连续SSC模式为模式3。基于本方案，源AF可以在UE的PDU会话锚点改变时，确定目标AS。可选的，若UE的PDU会话锚点未发生改变，那么UE接入的数据网络可能不会发生变化，因此可能无需进行应用迁移，故本申请中UE的PDU会话的用户面路径改变可以理解为UE的PDU会话锚点改变。
本申请实施例的第二方面，提供一种应用迁移的方法，该方法包括：源使能服务器ES获取第一信息，该第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后UE的位置信息；该源ES向源应用服务器AS发送第二通知消息；该第二通知消息用于通知源AS上述UE的PDU会话的用户面路径改变，该源AS为上述UE的PDU会话的用户面路径改变前上述UE访问的AS。基于本方案，通过源ES通知源AS UE的PDU会话的用户面路径改变，从而使得源AS可以确定目标AS。可以理解 的，源AS可以基于第一信息确定目标AS，因此确定的目标AS较准确，UE访问该目标AS时的时延较小，即本方案能够减小UE访问应用服务器的时延。可以理解的，本方案可以由源AS触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
结合第二方面，在一种可能的实现方式中，上述UE的位置信息为上述UE的网络协议IP地址、上述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、UE的跟踪区域标识TAI、UE的小区标识cell ID、UE的无线接入网标识RAN ID或者UE的地理位置信息中的至少一种。基于本方案，源ES可以基于UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息确定目标AS，因此确定的目标AS较为准确。
结合第二方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES接收来自上述源AS订阅的用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述源AS。基于本方案，通过源AS向源ES订阅用户面管理事件通知，从而能够在源ES确定UE的PDU会话的用户面路径改变时通知源AS。
结合第二方面和上述可能的实现方式，在另一种可能的实现方式中，上述源ES获取第一信息包括：上述源ES接收来自上述UE的边缘使能客户端EEC发送的第四通知消息，该第四通知消息用于通知上述源ES上述UE的PDU会话重建，该第四通知消息中包括上述第一信息。基于本方案，源ES通过接收UE的EEC发送的第四通知消息，可以获知UE的PDU会话重建，从而源ES可以通知源AS UE的PDU会话的用户面路径发生改变。
结合第二方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的PDU会话的用户面路径改变包括所述UE的PDU会话锚点改变，所述UE的PDU会话的会话和服务连续SSC模式为模式3。基于本方案，由于UE的PDU会话的SSC模式为模式3，从而能够在UE的PDU会话锚点改变后，源ES通知源AS，从而使得源AS可以确定目标AS并触发应用迁移，确定的目标较准确，减小了UE访问应用服务器的时延。而且该方案可以由源AS触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
本申请实施例的第三方面，提供一种应用迁移的方法，该方法包括:用户设备UE的边缘使能客户端EEC向UE的操作系统OS订阅会话重建事件通知，该会话重建事件通知用于当UE的协议数据单元PDU会话重建时通知EEC；该EEC接收来自OS的第六通知消息，该第六通知消息用于通知EEC该UE的PDU会话重建，该第六通知消息中包括第一信息，该第一信息为上述PDU会话重建后上述UE的位置信息。基于本方案，通过UE中的EEC向UE中的OS订阅会话重建事件通知，从而能够在UE的PDU会话重建时，UE中的OS通知UE中的EEC，使得EEC获知用户面的相关信息。可选的，UE中的EEC可以基于第一信息(UE的位置信息)确定目标AS，因此确定的目标AS较准确，UE访问该目标AS时的时延较小，即本方案能够减小UE访问应用服务器的时延。而且该方法不需要UE中的AC理解网络逻辑，能够简化AC的设计。
结合第三方面，在一种可能的实现方式中，上述UE的位置信息为上述UE的IP地址、上述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、UE的跟踪区域标识TAI、UE的小区标识cell ID、UE的无线接入网标识RAN ID或者UE的地理位置信息中的至少一种。基于本方案，EEC可以基于UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息确定目标AS，因此确定的目标AS较为准确。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述EEC向源使能服务器ES发送第四通知消息，该第四通知消息用于通知上述源ES上述UE的PDU会话重建，该第四通知消息中包括上述第一信息。基于本方案，通过UE中的EEC通知源ES UE的PDU会话重建，从而使得源ES可以基于EEC发送的通知消息确定目标AS并进行应用迁移，该方法确定的目标AS较准确，因此UE访问目标AS的时延较小。而且该方法不需要UE中的AC理解网络逻辑，能够简化AC的设计。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述EEC基于上述第一信息，确定目标应用服务器AS；该目标AS与源AS服务相同的应用，该源AS为UE的PDU会话重建前UE访问的AS。基于本方案，UE中的EEC获知UE的PDU会话的用户面路径改变时，可以自己确定目标AS，不仅确定的目标AS较准确，而且不需要UE中的AC理解网络逻辑，能够简化AC的设计。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，上述EEC基于上述第一信息，确定目标应用服务器AS，包括：上述EEC基于上述第一信息，确定目标ES；上述EEC向上述目标ES发送发现请求；上述EEC接收来自上述目标ES的第一消息，该第一消息中包括上述目标ES管理的一个或多个AS的连接信息，该目标ES管理的一个或多个AS与源AS服务相同的应用；所述EEC从目标ES管理的一个或多个AS中确定目标AS。基于本方案，UE中的EEC可以在目标ES管理的一个或多个AS中确定目标AS，从而可以访问该目标AS，因此确定的目标AS较准确，UE访问该目标AS的时延较小。而且该方案不需要对UE中的AC进行改动，简化了AC的设计。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述EEC向上述源AS或源ES发送上述目标AS的连接信息，以使得上述源AS或源ES将上述UE的上下文从上述源AS迁移至上述目标AS。基于本方案，源AS或源ES可以将UE的上下文从源AS迁移至目标AS，从而不需要加强UE中的AC的逻辑，简化了AC的设计。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的PDU会话的用户面路径改变包括上述UE的PDU会话重建。基于本方案，能够在UE的PDU会话重建时，UE中的OS通知UE中的EEC，该方法不需要UE中的AC理解网络逻辑，能够简化AC的设计。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的PDU会话的用户面路径改变包括UE的PDU会话锚点改变，UE的PDU会话的会话和服务连续SSC模式为模式3。基于本方案，由于UE的PDU会话的SSC模式为模式3，从而能够在UE的PDU会话锚点改变后，确定目标AS并进行应用迁移，降低UE 访问应用服务器的时延。
本申请实施例的第四方面，提供一种应用迁移的方法，该方法包括：源应用服务器AS向源使能服务器ES发送订阅请求，该订阅请求用于当源ES确定存在目标AS时通知源AS；该源AS接收来自上述源ES的第七通知消息，该第七通知消息包括目标AS的连接信息；源AS确定将用户设备UE的上下文从源AS迁移至目标AS。示例性的，该目标AS和源AS服务相同的应用。基于本方案，通过源AS向源ES发送订阅请求，从而能够在源ES确定UE可接入的DN中存在目标AS时，再向源AS发送包括目标AS的连接信息的通知消息，再由源AS触发应用迁移。由于UE的PDU会话的用户面路径改变后，UE可接入的数据网络中不一定部署了与源AS服务相同应用的AS，因此通过发送订阅请求，能够在源ES确定UE可接入的数据网络中存在与源AS服务相同应用的AS时，再通知源AS，进而发起应用迁移，因此能够减少应用迁移过程中的无效通知，降低时延。
结合第四方面，在一种可能的实现方式中，上述方法还包括：源AS向源ES发送第四指示信息，该第四指示信息用于指示源ES将UE的上下文从源AS迁移至目标AS。基于本方案，通过源AS向源ES发送指示源ES将UE的上下文从源AS迁移至目标AS的指示信息，使得源ES可以将UE的上下文从源AS迁移至目标AS，从而能够减小UE访问应用服务器的时延。
结合第四方面，在一种可能的实现方式中，上述方法还包括：上述源AS向上述目标AS发送应用切换请求消息，该应用切换请求消息用于将源AS上的上下文迁移至目标AS。基于本方案，通过源AS向目标AS发送应用切换请求消息，使得目标AS可以将源AS上的上下文迁移至目标AS，从而能够减小UE访问应用服务器的时延。
结合第四方面，在一种可能的实现方式中，上述方法还包括：上述源AS接收来自上述目标AS的应用切换响应消息，该应用切换响应消息中包括第三指示信息，该第三指示信息用于指示上述目标AS是否同意应用切换；相应的，上述源AS确定将上述UE的上下文从上述源AS迁移至上述目标AS，包括：若上述第三指示信息指示上述目标AS同意应用切换，上述源AS确定将上述UE的上下文从上述源AS迁移至上述目标AS。基于本方案，目标AS可以通过向源AS发送应用切换响应消息，从而能够在目标AS同意应用切换的情况下再确定触发应用迁移，从而能够避免迁移失败。
结合第四方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源AS向源ES发送第五指示信息，该第五指示信息用于指示源AS是否支持应用切换。基于本方案，源ES能够获知源AS是否支持应用切换，若源ES确定源AS支持应用切换，那么源ES确定UE可接入的数据网络中存在目标AS后，源ES可以执行应用迁移。
结合第四方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：源AS向源ES发送第七指示信息，该第七指示信息用于指示应用切换时需要保持业务连续性。基于本方案，通过源AS向源ES发送第七指示信息，能够在DNAI改变的时候，建立UPF之间的转发隧道，用于做业务连续性，以便UE可将应用数据发送给源AS。
本申请实施例的第五方面，提供一种应用迁移的方法，该方法包括：源使能服务 器ES接收来自源应用服务器AS的订阅请求，该订阅请求用于当源ES确定存在目标AS时通知源AS；源ES获取第一信息，该第一信息为UE的协议数据单元PDU会话的用户面路径改变后UE的位置信息；源ES基于所述第一信息，确定目标AS。示例性的，该目标AS和源AS服务相同的应用。基于本方案，通过源AS向源ES发送订阅请求，从而能够在源ES确定UE可接入的DN中存在目标AS时，源ES向源AS发送包括目标AS的连接信息的通知消息。由于UE的PDU会话的用户面路径改变后，UE可接入的数据网络中不一定部署了与源AS服务相同应用的AS，因此通过发送订阅请求，能够在源ES确定UE可接入的数据网络中存在与源AS服务相同应用的AS时，再通知源AS，进而发起应用迁移，因此能够减少应用迁移过程中的无效通知，降低时延。
结合第五方面，在一种可能的实现方式中，源ES向源AS发送第七通知消息，该第七通知消息中包括目标AS的连接信息。基于本方案，通过源AS向源ES发送订阅请求，从而能够在源ES确定UE可接入的DN中存在目标AS时，源ES向源AS发送包括目标AS的连接信息的通知消息。可以理解的，当源ES确定存在目标AS时，源ES向源AS发送第七通知消息。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的位置信息为上述UE的IP地址、上述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、UE的跟踪区域标识TAI、UE的小区标识cell ID、UE的无线接入网标识RAN ID或者UE的地理位置信息中的至少一种。基于本方案，源ES可以基于UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息确定UE可接入的DN中存在目标AS，因此确定结果较为准确。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述源ES获取第一信息，包括：上述源ES接收来自策略控制功能PCF实体或会话管理功能SMF实体的第三通知消息，该第三通知消息用于通知上述源ES上述UE的PDU会话的用户面路径改变，该第三通知消息中包括上述第一信息。基于本方案，源ES通过接收PCF或SMF发送的第三通知消息，可以获知UE的PDU会话的用户面路径发生改变，从而源ES可以基于该通知消息确定UE可接入的DN中存在目标AS。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES向上述PCF实体或上述SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述源ES。基于本方案，通过源ES向PCF或SMF订阅用户面管理事件通知，从而能够在PCF或SMF确定UE的PDU会话的用户面路径改变时通知源ES。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述订阅请求中包括UE的PDU会话的信息；UE的PDU会话的信息包括UE的网络协议IP地址、数据网络名称DNN、或单网络切片选择辅助信息S-NSSAI中的至少一种。基于本方案，通过在订阅请求中携带UE的PDU会话的信息，从而能够源ES能够基于该UE的PDU会话的信息识别UE访问的5GC网元。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：源ES根据UE的PDU会话的信息，确定策略控制功能PCF实体或会话管理功 能SMF实体。基于本方案，源ES能够基于该UE的PDU会话的信息确定UE访问的PCF实体或SMF实体。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述订阅请求中包括该应用标识信息，上述源ES基于上述第一信息，确定目标AS，包括：源ES基于第一信息和应用标识信息，确定目标AS。基于本方案，源ES可以基于第一信息和应用标识信息确定目标AS，因此确定的目标AS较准确，能够减小UE访问应用服务器的时延。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：源ES向SMF发送第六指示信息，该第六指示信息用于指示源AS是否支持应用切换。基于本方案，通过源ES向5GC发送用于指示源AS是否支持应用切换的指示信息，可以在源AS不支持应用切换的场景下，5GC能够终止切换UE的PDU会话的用户面路径。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：源ES接收来自源AS的第七指示信息，该第七指示信息用于指示应用切换时需要保持业务连续性。基于本方案，能够在DNAI改变的时候，建立UPF之间的转发隧道，用于做业务连续性，以便UE可将应用数据发送给源AS。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES向SMF或PCF发送第八指示信息，该第八指示信息用于指示应用切换时需要保持业务连续性。基于本方案，通过源ES向SMF或PCF发送第八指示信息，使得5GC网元在应用切换完成后可以释放转发隧道。
结合第五方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES向SMF或PCF发送所述目标AS的连接信息。基于本方案，通过源ES向SMF或PCF发送目标AS的连接信息，使得SMF或PCF可以向UE发送目标AS的连接信息，从而UE可以与该目标AS建立连接，减小了UE访问应用服务器的时延。
本申请实施例的第六方面，提供一种应用迁移的方法，上述方法包括：配置服务器CS接收来自用户设备UE的第一指示信息，该第一指示信息用于指示CS当UE的协议数据单元PDU会话的用户面路径改变时，向UE发送目标数据网络DN的信息；CS获取第一信息，该第一信息为UE的PDU会话的用户面路径改变后UE的位置信息；CS基于该第一信息，确定目标DN；CS向UE发送该目标DN的信息。基于本方案，通过CS基于UE的PDU会话的用户面路径改变后UE的位置信息确定目标DN，因此确定的目标AS较准确，故UE接入该目标DN后能够减小UE访问数据网络的时延。可选的，UE的PDU会话的SSC模式可以为模式3。当UE的PDU会话的SSC模式可以为模式3时，上述UE的PDU会话的用户面路径改变包括UE的PDU会话发生重建。
结合第六方面，在一种可能的实现方式中，上述UE的位置信息为上述UE的IP地址、上述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、UE的跟踪区域标识TAI、UE的小区标识cell ID、UE的无线接入网标识RAN ID或者UE的地理位置信息中的至少一种。基于本方案，CS可以基于UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息确定目标DN，因此确定的结果较为准确。
结合第六方面和上述可能的实现方式，在另一种可能的实现方式中，上述CS获取第一信息包括：上述CS接收来自上述UE的第二指示信息，该第二指示信息用于指示上述UE的PDU会话发生重建，该第二指示信息中包括上述第一信息。基于本方案，CS可以通过接收UE的指示信息获知UE的PDU会话发生重建，从而CS可以基于该指示信息确定目标DN，因此确定的目标AS较准确，故UE接入该目标DN后能够减小UE访问数据网络的时延。
结合第六方面和上述可能的实现方式，在另一种可能的实现方式中，上述CS获取第一信息包括：上述CS接收来自策略控制功能PCF实体或会话管理功能SMF实体的第五通知消息，该第五通知消息用于通知上述CS上述UE的PDU会话的用户面路径改变，该第五通知消息中包括上述第一信息。基于本方案，CS可以通过接收PCF或SMF的通知消息获知UE的PDU会话发生重建，从而CS可以基于该通知消息确定目标DN，因此确定的目标AS较准确。
结合第六方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述CS向上述PCF实体或上述SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述CS。基于本方案，通过CS向PCF或SMF订阅用户面管理事件通知，从而能够在PCF或SMF确定UE的PDU会话的用户面路径改变时通知CS。
结合第六方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的PDU会话的用户面路径改变包括上述UE的PDU会话重建。基于本方案，CS可以在UE的PDU会话重建时，确定目标DN。可选的，若UE的PDU会话未发生重建，那么UE接入的数据网络可能不会发生变化，因此可能无需进行应用迁移，故本申请中UE的PDU会话的用户面路径改变可以认为是UE的PDU会话发生重建。
结合第六方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的PDU会话的用户面路径改变包括UE的PDU会话锚点改变，UE的PDU会话的会话和服务连续SSC模式为模式3。基于本方案，由于UE的PDU会话的SSC模式为模式3，从而能够在UE的PDU会话重建后，确定目标DN。
本申请实施例的第七方面，提供一种应用迁移的方法，该方法包括：配置服务器CS获取第一信息，所述第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后所述UE的位置信息；所述CS基于所述第一信息，确定目标使能服务器ES。基于本方案，通过CS基于UE的PDU会话的用户面路径改变后UE的位置信息确定目标ES，因此确定的目标ES较准确，使得基于该目标ES确定的目标AS较准确，UE访问该目标AS时的时延较小，即本方案能够减小UE访问应用服务器的时延。
结合第七方面，在一种可能的实现方式中，上述UE的位置信息包括UE的网络协议IP地址、UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、UE的跟踪区域标识TAI、UE的小区标识、UE的无线接入网标识或者UE的地理位置信息中的至少一种。基于本方案，CS可以基于UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息确定目标ES，因此确定的目标ES较为准确。
结合第七方面和上述可能的实现方式，在另一种可能的实现方式中，上述CS获取上述第一信息，包括：CS接收来自上述UE的第一信息。基于本方案，CS可以从 UE接收UE的PDU会话的用户面路径改变后UE的位置信息，从而使得CS基于该UE的位置信息确定的目标ES较准确，减小了UE访问应用服务器的时延。
结合第七方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述CS向上述UE发送上述目标ES的连接信息。基于本方案，通过CS向UE发送目标ES的连接信息，使得UE可以基于该目标ES的连接信息请求目标AS，从而能够减小UE访问应用服务器的时延。
结合第七方面和上述可能的实现方式，在另一种可能的实现方式中，上述CS获取上述第一信息，包括：上述CS接收来自源ES的第一信息。基于本方案，CS可以从源ES接收UE的PDU会话的用户面路径改变后UE的位置信息，从而使得CS基于该UE的位置信息确定的目标ES较准确，减小了UE访问应用服务器的时延。
结合第七方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述CS向上述源ES发送上述目标ES的连接信息。基于本方案，通过CS向源ES发送目标ES的连接信息，使得UE可以基于该目标ES的连接信息请求目标AS，从而能够减小UE访问应用服务器的时延。
结合第七方面和上述可能的实现方式，在另一种可能的实现方式中，上述第一信息为上述UE的PDU会话的用户面路径改变后UE的IP地址，上述CS基于上述第一信息，确定上述目标ES，包括：CS基于UE的PDU会话的用户面路径改变后UE的IP地址，确定UE的PDU会话的用户面路径改变后的DNAI；CS基于该DNAI，确定目标ES。基于本方案，CS可以基于UE的IP地址，确定DNAI，从而可以基于DNAI确定目标ES，因此确定的目标ES较准确。
结合第七方面和上述可能的实现方式，在另一种可能的实现方式中，上述UE的PDU会话的用户面路径改变包括UE的PDU会话锚点改变，UE的会话和服务连续SSC模式为模式3。基于本方案，UE的PDU会话的SSC模式为mode3，UE的PDU会话的用户面路径改变包括UE的PDU会话锚点改变。也就是说，本方案是在UE的PDU会话锚点改变时，基于会话锚点改变后UE的位置信息确定目标ES，因此确定的目标ES较准确。
本申请实施例的第八方面，提供一种应用迁移的方法，该方法包括：源使能服务器ES获取第一信息，该第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后UE的位置信息；源ES向配置服务器CS发送第一信息；源ES接收来自CS的目标ES的连接信息。基于本方案，通过源ES向CS发送第一信息，从而使得CS可以基于该第一信息确定目标ES，因此确定的目标ES较为准确，能够减小UE访问应用服务器的时延。
结合第八方面，在一种可能的实现方式中，上述UE的位置信息包括UE的网络协议IP地址、UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、UE的跟踪区域标识TAI、UE的小区标识、UE的无线接入网标识或者UE的地理位置信息中的至少一种。基于本方案，CS可以基于UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息确定目标ES，因此确定的目标ES较为准确。
结合第八方面和上述可能的实现方式，在另一种可能的实现方式中，上述源ES获取第一信息，包括：源ES接收来自UE的第一信息。基于本方案，源ES接收来自 UE的第一信息，并向CS发送该第一信息，从而使得CS可以基于该第一信息较为准确的确定目标ES。
结合第八方面和上述可能的实现方式，在另一种可能的实现方式中，源ES获取上述第一信息，包括：上述源ES接收来自策略控制功能PCF实体或会话管理功能SMF实体的第三通知消息，该第三通知消息用于通知上述源ES上述UE的PDU会话的用户面路径改变，该第三通知消息中包括上述第一信息。基于本方案，源ES也可以从5GC网元获取第一信息，并向CS发送该第一信息，从而使得CS可以基于该第一信息较为准确的确定目标ES。
结合第八方面和上述可能的实现方式，在另一种可能的实现方式中，源ES向上述PCF实体或上述SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述源ES。基于本方案，源ES可以通过向5GC网元订阅用户面管理事件通知，从而能够获知UE的PDU会话的用户面路径改变，并获取用户面路径改变后UE的位置信息。
结合第八方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES向上述目标ES发送第一应用发现请求，该第一应用发现请求用于请求获取目标AS；上述源ES接收来自上述目标ES的目标AS的连接信息。基于本方案，源ES可以向目标ES发送第一应用发现请求，以从目标ES获取目标AS的信息。
结合第八方面和上述可能的实现方式，在另一种可能的实现方式中，上述目标AS与源AS服务相同的应用，该源AS为上述UE的PDU会话的用户面路径改变前上述UE访问的AS。基于本方案，目标ES确定的目标AS是与源AS服务相同应用的AS，因此在UE移动过程中，能够确保UE访问的业务的连续性。
结合第八方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES向上述UE发送上述目标AS的连接信息。基于本方案，通过源ES向UE发送目标AS的连接信息，从而UE可以与该目标AS建立连接，以使得UE的上下文从源AS切换为目标AS，减小UE访问应用服务器的时延。
本申请实施例的第九方面，提供一种应用迁移的方法，该方法包括：用户设备UE接收来自会话管理功能SMF实体或用户面功能UPF实体的第一信息，该第一信息为上述UE的协议数据单元PDU会话的用户面路径改变后上述UE的位置信息；上述UE向应用功能AF发送上述第一信息。该AF可以为CS或源ES。基于本方案，通过UE向CS或源ES发送UE的PDU会话的用户面路径改变后UE的位置信息，使得CS可以基于该UE的位置信息确定目标ES，因此确定的目标ES较准确，进而基于该目标ES确定的目标AS较准确，UE访问该目标AS时的时延较小，即本方案能够减小UE访问应用服务器的时延。
结合第九方面，在一种可能的实现方式中，UE的位置信息包括上述UE的网络协议IP地址、上述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、上述UE的跟踪区域标识TAI、上述UE的小区标识、上述UE的无线接入网标识或者上述UE的地理位置信息中的至少一种。基于本方案，UE可以向AF发送UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息，使得CS可以基于上述信息确定目标ES，因此确定的目标ES较为准确。
结合第九方面和上述可能的实现方式，在另一种可能的实现方式中，上述AF为配置服务器CS，上述方法还包括：上述UE接收来自上述CS的目标使能服务器ES的连接信息。基于本方案，CS可以基于PDU会话的用户面路径改变后UE的位置信息确定目标ES，并向UE发送该目标ES，从而使得UE可以向目标ES请求目标AS，并与该目标AS建立连接，减小了UE访问应用服务器的时延。
结合第九方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述UE向上述目标ES发送第二应用发现请求，该第二应用发现请求用于请求获取目标AS；上述UE接收来自上述目标ES的目标AS的连接信息。基于本方案，UE可以向目标ES请求获取目标AS，从而UE可以与该目标AS建立连接，能够减小UE访问应用服务器的时延。
结合第九方面和上述可能的实现方式，在另一种可能的实现方式中，上述AF为源ES。基于本方案，通过UE向源ES发送UE的PDU会话的用户面路径改变后UE的位置信息，使得源ES可以向CS发送该位置信息，CS可以基于该UE的位置信息确定目标ES，因此确定的目标ES较准确，进而基于该目标ES确定的目标AS较准确，UE访问该目标AS时的时延较小，即本方案能够减小UE访问应用服务器的时延。
结合第九方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述UE接收来自上述源ES的目标AS的连接信息。基于本方案，UE可以从源ES获取目标AS的连接信息，从而UE可以与该目标AS之间建立连接，能够减小UE访问应用服务器的时延。
本申请实施例的第十方面，提供一种应用迁移的方法，该方法包括：源应用服务器AS向源使能服务器ES订阅可用AS通知，该可用AS通知用于当源ES确定用户设备UE可接入的数据网络DN中存在目标AS时通知源AS；该源AS接收来自上述源ES的第七通知消息，该第七通知消息中包括目标AS的地址信息；源AS确定将UE访问的AS从源AS迁移至目标AS。示例性的，该目标AS和源AS服务相同的应用。基于本方案，通过源AS向源ES订阅可用AS通知，从而能够在源ES确定UE可接入的DN中存在目标AS时，再向源AS发送包括目标AS的地址信息的通知消息，再由源AS触发应用迁移。由于UE的PDU会话的用户面路径改变后，UE可接入的数据网络中不一定部署了与源AS服务相同应用的AS，因此通过订阅该可用AS通知，能够在源ES确定UE可接入的数据网络中存在与源AS服务相同应用的AS时，再通知源AS，进而发起应用迁移，因此能够减少应用迁移过程中的无效通知，降低时延。
结合第十方面，在一种可能的实现方式中，上述方法还包括：上述源AS向上述目标AS发送应用切换请求消息；上述源AS接收来自上述目标AS的应用切换响应消息，该应用切换响应消息中包括第三指示信息，该第三指示信息用于指示上述目标AS是否同意应用切换。基于本方案，源AS可以通过向目标AS发送应用切换请求消息，并在目标AS同意应用切换的情况下再确定触发应用迁移，从而能够避免迁移失败。
结合第十方面和上述可能的实现方式，在另一种可能的实现方式中，上述源AS确定将上述UE访问的AS从上述源AS迁移至上述目标AS，包括：若上述第三指示信息指示上述目标AS同意应用切换，上述源AS确定将上述UE访问的AS从上述源AS迁移至上述目标AS。基于本方案，源AS可以在目标AS同意应用切换的情况下再 确定触发应用迁移，从而能够避免迁移失败。
本申请实施例的第十一方面，提供一种应用迁移的方法，该方法包括：源使能服务器ES接收来自源应用服务器AS订阅的可用AS通知，该可用AS通知用于当源ES确定用户设备UE可接入的数据网络DN中存在目标AS时通知源AS；源ES获取第一信息，该第一信息为UE的协议数据单元PDU会话的用户面路径改变后UE的位置信息；源ES基于所述第一信息，确定UE可接入的DN中存在目标AS；源ES向源AS发送第七通知消息，该第七通知消息中包括目标AS的地址信息。示例性的，该目标AS和源AS服务相同的应用。基于本方案，通过源AS向源ES订阅可用AS通知，从而能够在源ES确定UE可接入的DN中存在目标AS时，源ES向源AS发送包括目标AS的地址信息的通知消息。由于UE的PDU会话的用户面路径改变后，UE可接入的数据网络中不一定部署了与源AS服务相同应用的AS，因此通过订阅该可用AS通知，能够在源ES确定UE可接入的数据网络中存在与源AS服务相同应用的AS时，再通知源AS，进而发起应用迁移，因此能够减少应用迁移过程中的无效通知，降低时延。可以理解的，当源ES确定UE可接入的DN中存在目标AS时，源ES向源AS发送第七通知消息。
结合第十一方面，在一种可能的实现方式中，上述UE的位置信息为上述UE的IP地址、上述UE可接入的数据网络对应的数据网络接入标识DNAI、UE的跟踪区域标识TAI、UE的小区标识cell ID、UE的无线接入网标识RAN ID或者UE的地理位置信息中的至少一种。基于本方案，源ES可以基于UE的IP地址、DNAI、TAI、cell ID、RAN ID或者UE的地理位置信息确定UE可接入的DN中存在目标AS，因此确定结果较为准确。
结合第十一方面和上述可能的实现方式，在另一种可能的实现方式中，上述源ES获取第一信息，包括：上述源ES接收来自策略控制功能PCF实体或会话管理功能SMF实体的第三通知消息，该第三通知消息用于通知上述源ES上述UE的PDU会话的用户面路径改变，该第三通知消息中包括上述第一信息。基于本方案，源ES通过接收PCF或SMF发送的第三通知消息，可以获知UE的PDU会话的用户面路径发生改变，从而源ES可以基于该通知消息确定UE可接入的DN中存在目标AS。
结合第十一方面和上述可能的实现方式，在另一种可能的实现方式中，上述方法还包括：上述源ES向上述PCF实体或上述SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当上述UE的PDU会话的用户面路径改变时通知上述源ES。基于本方案，通过源ES向PCF或SMF订阅用户面管理事件通知，从而能够在PCF或SMF确定UE的PDU会话的用户面路径改变时通知源ES。
本申请实施例的第十二方面，提供一种通信系统，该通信系统包括源应用服务器AS和源使能服务器ES，其中，源AS向源ES订阅用户面管理事件通知，用户面管理事件通知用于当UE的协议数据单元PDU会话的用户面路径改变时通知源AS；源AS为PDU会话的用户面路径改变前UE访问的AS；源ES获取第一信息，第一信息为UE的PDU会话的用户面路径改变后UE的位置信息；源ES向源AS发送第二通知消息，第二通知消息用于通知源AS上述UE的PDU会话的用户面路径改变，第二通知消息中包括第一信息；源AS基于第一信息，确定目标AS，并向UE发送该目标AS 的连接信息。
结合第十二方面，在一种可能的实现方式中，上述通信系统还包括上述UE，所述UE接收来自所述源AS的所述目标AS的连接信息；所述UE基于所述目标AS的连接信息与所述目标AS建立连接。
本申请实施例的第十三方面，提供一种应用迁移的装置，该应用迁移的装置具有实现上述第一方面至第九方面中任一所述的应用迁移的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例的第十四方面，提供一种应用迁移的装置，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该应用迁移的装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该应用迁移的装置执行如上述第一方面至第九方面中任一所述的应用迁移的方法。
本申请实施例的第十五方面，本申请实施例提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面至第九方面中任一所述的应用迁移的方法。
本申请实施例的第十六方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面至第九方面中任一所述的应用迁移的方法。
本申请实施例的第十七方面，提供一种芯片系统，该芯片系统包括处理器和存储器，存储器中存储有指令；指令被处理器执行时，实现上述第一方面至第九方面中任一所述的应用迁移的方法。
附图说明
图1为本申请实施例提供的一种5G网络的架构示意图；
图2为本申请实施例提供的一种SA6工作组边缘业务使能架构示意图；
图3为本申请实施例提供的一种网络部署的架构示意图；
图4a为本申请实施例提供的一种SSC mode3的PDU会话切换流程示意图；
图4b为本申请实施例提供的一种multi-homed会话机制的PDU会话切换流程示意图；
图5为本申请实施例提供的一种通信装置的结构示意图；
图6为本申请实施例提供的一种应用迁移的方法的流程示意图；
图7为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图8为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图9为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图10为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图11为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图12为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图13为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图14为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图15为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图16为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图17为本申请实施例提供的另一种应用迁移的方法的流程示意图；
图18为本申请实施例提供的一种通信设备的组成示意图；
图19为本申请实施例提供的另一种通信设备的组成示意图；
图20为本申请实施例提供的另一种通信设备的组成示意图；
图21为本申请实施例提供的另一种通信设备的组成示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。在本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b或c中的至少一项(个)，可以表示：a，b，c，a和b，a和c，b和c，或，a和b和c，其中a、b和c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分，本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定。比如，本申请实施例中的第一通知消息中的“第一”和第二通知消息中的“第二”仅用于区分不同的通知消息。本申请实施例中出现的第一、第二等描述，仅作示意与区分描述对象之用，没有次序之分，也不表示本申请实施例中对设备个数的特别限定，不能构成对本申请实施例的任何限制。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例中出现的“多个”是指两个或两个以上。
本申请实施例中出现的第一、第二等描述，仅作示意与区分描述对象之用，没有次序之分，也不表示本申请实施例中对设备个数的特别限定，不能构成对本申请实施例的任何限制。
本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式，以实现设备间的通信，本申请实施例对此不做任何限定。
本申请实施例中出现的“网络”与“系统”表达的是同一概念，通信系统即为通信网络。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
图1为本申请实施例提供的一种5G网络架构的示意图。如图1所示，该5G网络 中的用户面网元和控制面网元分离部署。该5G网络中包括用户设备UE、接入网(access network，AN)设备/无线接入网(radio access network，RAN)设备、用户面功能(user plane function，UPF)实体和数据网络(data network，DN)、接入与移动管理功能(access and mobility management function，AMF)实体、会话管理功能(session management function，SMF)实体、策略控制功能(policy control function，PCF)实体和应用功能(application function，AF)、网络切片选择功能(network slice selection function，NSSF)实体、鉴权服务器功能(authentication server function，AUSF)实体和统一数据管理(unified data management，UDM)实体。
其中，接入网设备指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非3GPP接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
UPF实体主要负责PDU的路由、转发以及对分组数据的策略执行。例如，UPF实体可实现服务网关(serving gateway，SGW)和分组数据网络网关(packet data network gateway，PGW)的用户面功能。UPF实体还可以是软件定义网络(software defined network，SDN)交换机(Switch)，本申请实施例对此不作具体限定。UPF实体通过N6接口与DN通信，DN是用户的PDU会话访问的目的地。
AMF实体主要通过N1接口接入UE的非接入层(non-access stratum，NAS)信令(包括会话管理SM信令)，通过N2接口接入无线接入网的信令，主要负责接入认证、授权以及移动性管理。
SMF实体通过N4接口与UPF实体通信，SMF实体主要负责完成会话相关的建立、释放、更新等流程，以及网络协议(internet protocol，IP)地址分配和管理，UPF实体的选择和控制，合法监听等与会话相关的控制功能。
PCF实体主要负责用户策略管理，既包括移动性相关策略，也包括协议数据单元(protocol data unit，PDU)会话相关策略，例如，服务质量(quality of service，QoS)策略、计费策略等。
AF主要负责向PCF提供用户访问业务的业务信息，用于PCF的策略决策。NSSF主要负责管理网络切片。UDM主要负责保存用户的签约数据。AUSF主要负责对UE的接入进行认证和授权。
需要说明的是，图1中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能称为其他名字，本申请实施例对此不作具体限定。可选的，5G网络中还可以包括除图1所示的设备以外的其它网络设备，图1仅是示例性的示意。
可以理解的，本申请实施例提供的应用迁移的方法可以适应于图1所示的5G网络中，也可以适用于长期演进(long term evolution，LTE)无线通信网络，或者是其他下一代(next generation，NG)通信网络等，本申请实施例对此不做限定。下述实施例仅以5G网络为例进行说明。
图2为本申请实施例提供的一种SA(System and architecture)6工作组边缘业务使能架构，如图2所示，UE可以通过5G网络访问边缘数据网络(edge data network，EDN)，其中边缘数据网络也可以称为本地数据网络(Local data network，LDN)。该EDN可以包括边缘使能服务器(edge enabler server，EES)和边缘应用服务器(edge  application server，EAS)。其中，EES可以是移动边缘计算(mobile edge computing，MEC)节点中的控制网元或者管理网元，EES负责管理部署在该EDN里的EAS，比如注册，域名系统(domain name system，DNS)解析等，EES上存有EAS的配置信息(profile)。
示例性的，每个EDN有特定的服务范围，一个EDN中可以部署一个或多个EAS，图2中仅以EDN中部署一个EAS为例进行示意。当EDN中部署多个EAS时，该多个EAS可以服务多个不同的应用。例如，EDN中部署了三个EAS，分别为EAS1、EAS2和EAS3，其中，EAS1是百度应用(application)对应的EAS，EAS2是爱奇艺应用对应的EAS，EAS3是腾讯视频应用对应的EAS。可选的，当EDN中部署多个EAS时，该多个EAS中的部分EAS或全部EAS可以服务同一个应用，用于做容灾或负载均衡等。再例如，EDN中部署了三个EAS，分别为EAS1、EAS2和EAS3，其中，EAS1和EAS2是百度应用的EAS，EAS3是腾讯视频应用的EAS。
边缘配置服务器(edge configuration server，ECS)可以是全局管理网元，负责维护各个EDN的信息，包括服务范围和EES地址等。需要说明的是，在一些标准协议中(例如，技术规范(technical specification，TS)23.501、TS23.502等协议)，上述EES，EAS，ECS都可以称之为AF。
UE中可以包括边缘使能客户端(edge enabler client，EEC)和应用客户端(application client，AC)，其中，EEC为UE上的AC提供必要的支持，EEC的功能包括通过EDGE-4接口检索EDN信息、检索可用的EAS、EAS可用性变化、EAS迁移通知给EEC、UE注册到EES等。
如图2所示，UE中的EEC可以通过EDGE-1接口(边缘接口-1)与EES通信，UE中的EEC可以通过EDGE-5(边缘接口-5)接口与UE中的AC通信，5G网络中的网元可以通过EDGE-2(边缘接口-2)接口与EES通信，5G网络中的网元可以通过EDGE-8接口(边缘接口-8)与ECS通信，DN中部署的EES可以通过EDGE-3接口(边缘接口-3)与EAS通信，ESC可以通过EDGE-6(边缘接口-6)接口与EES通信。
需要说明的是，本申请下述实施例中的源AS或目标AS可以为图2中的EAS，源使能服务器(enabler server，ES)或目标ES可以为图2中的EES，CS可以为图2中的ECS。即在SA6中AS可以称为EAS，ES可以称为EES，CS可以称为ECS。
为了提升用户体验，缩短用户访问应用服务器的时延，运营商或服务提供商会将应用服务器的部署下沉到地市级或热点区域等。图3为本申请实施例提供的一种网络部署的架构示意图。
如图3所示，MEC1节点或EDN1中部署了EAS1、EAS2和EAS3，MEC2节点中部署了EAS2、EAS3和EAS4，MEC3中部署了EAS1、EAS2、EAS3和EAS4。图3中的PDU会话锚点(PDU session anchor，PSA)1连接MEC1/EDN1(或者称为PSA1服务MEC1/EDN1)，PSA2连接MEC2，PSA3连接MEC3。每个MEC有对应的服务区域，不同MEC的服务区域之间可以有重叠。
图3中标识相同的EAS服务相同的应用，标识不同的EAS服务不同的应用。例如，图3中部署的EAS1、EAS2、EAS3和EAS4分别服务不同的应用，MEC1中部署的EAS2和MEC2中的EAS2服务相同的应用，即MEC1中部署的EAS2和MEC2中 部署的EAS2为服务同一个应用的不同服务器。需要说明的是，在实际部署中，一个MEC或EDN中可以部署更多个EAS，图3仅是以一个MEC中部署三个或四个EAS为例进行示意。
示例性的，5G中引入了三种会话和服务连续(session and service continuity，SSC)模式，分别为SSC mode1，SSC mode2和SSC mode3。其中，对于SSC mode1的PDU会话，网络会一直维持在PDU会话建立时充当PDU会话锚点的UPF，UE的IP地址不变。对于SSC mode2的PDU会话，网络如果要迁移锚点UPF，先释放旧的PDU会话，再发起新的PDU会话建立流程。对于SSC mode3的PDU会话，网络允许先建立一条经过新锚点的PDU会话连接，然后再释放旧锚点PDU会话连接，从而保证业务的连续性。
图4a为本申请实施例提供的一种SSC mode3的PDU会话切换流程示意图。如图4a所示，对于SSC mode3的PDU会话，UE移动前，通过UPF1访问EDN中的EAS，当UE发生移动时，发生锚点UPF的切换时，SMF通知UE先与UPF2建立新的PDU会话，再在定时器到时断开源PDU会话。UE的锚点UPF从UPF1切换到UPF2的过程中，两路会话可同时传输数据。其中，UE的旧IP地址与UPF1对应，UE的新地址与UPF2对应。需要说明的是，UE移动后接入的EDN与UE移动前接入的EDN可以相同，也可以不同。即UE移动后接入的数据网络可能发生变化，也可能不变。图4仅以UE移动后接入的EDN不变为例进行示意。
图4b为本申请实施例提供的一种multi-homed会话机制的PDU会话切换流程示意图。如图4b所示，使用创建multi-homed会话机制实现SSC mode 3时，UE移动前，通过UPF1访问DN中的AS，当UE发生移动，发生锚点UPF的切换时，创建分支点(branching point)UPF以及UPF2，在切换过程中分支点UPF与UPF1以及UPF2连接，在切换完成后，释放UPF1以及分支点UPF和UPF1之间的连接。
需要说明的是，上述图1至图4中的AMF、SMF、PCF、UPF、EDN、EAS、EES等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，AMF、SMF、PCF、UPF、EDN、EAS、EES也可以是其他的名字，本申请实施例对此不作具体限定。
结合图3和图4，当UE的PDU会话的SSC模式为SSC mode3时，如果UE移动过程中需要切换UPF，为了降低访问应用的时延，可以将对应的应用服务器也随之切换。
在UE移动过程中，为了降低UE访问应用服务器的时延，一种基于SSC mode3的应用迁移方法是在UE上的OS发现建立了新的PDU会话后，OS通知AC，AC收到该通知后触发DNS查询，获取New EAS地址，AC将New EAS的地址发送给Old EAS指示Old EAS做应用迁移，Old EAS与New EAS之间进行状态同步之后，UE开始向New EAS发送数据包。该方法基于DNS查询确定New AS时，由于DNS的查询结果不够准确，基于该DNS查询结果确定的New AS不是最合适的应用服务器，因此将UE访问的AS迁移至该New AS后，会造成UE访问该New AS的时延较大的问题。而且该应用迁移方法需要增加OS与AC之间的接口，而且需要AC理解SSC mode3，从而AC才能在收到OS发送的通知后，发起DNS查询确定New EAS并将New EAS 的地址发送给Old EAS触发应用切换。因此该方案需要增强AC的逻辑，导致AC的设计难度较大。
为了解决该应用迁移方法中确定的目标AS不准确，导致UE访问应用服务器的时延较大的问题，本申请实施例提供一种应用迁移的方法，该方法能够较为准确的确定目标AS，减小了UE访问应用服务器的时延。
在具体实现时，本申请实施提供的应用迁移的方法中，源AS、源ES、目标AS、目标ES、CS和UE等均可以采用图5所示的组成结构，或者包括图5所示的部件。
示例性的，图5为本申请实施例提供的一种通信装置500的组成示意图。如图5所示，该通信装置500可以包括至少一个处理器501，存储器502、收发器503以及通信总线504。
下面结合图5对该通信装置500的各个构成部件进行具体的介绍：
处理器501是通信装置500的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器501是一个中央处理器(central processing unit，CPU)，也可以是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)。
其中，处理器501可以通过运行或执行存储在存储器502内的软件程序，以及调用存储在存储器502内的数据，执行通信装置的各种功能。
在具体的实现中，作为一种实施例，处理器501可以包括一个或多个CPU，例如图5中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置500可以包括多个处理器，例如图5中所示的处理器501和处理器505。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个通信设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器502可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储通信设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储通信设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储通信设备、或者能够用于包括或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器502可以是独立存在，通过通信总线504与处理器501相连接。存储器502也可以和处理器501集成在一起。
其中，所述存储器502用于存储执行本申请方案的软件程序，并由处理器501来控制执行。处理器501用于执行存储器502中存储的应用程序代码，从而实现本申请下述实施例提供的应用迁移的方法。
收发器503，用于与接入点之间的通信。当然，收发器503还可以用于与通信网络通信，通信网络例如为以太网，无线接入网(radio access network，RAN)，无线局 域网(Wireless Local Area Networks，WLAN)等。收发器503可以包括接收单元实现接收功能，以及发送单元实现发送功能。
通信总线504，可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外部通信设备互连(Peripheral Component，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图5中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
需要说明的是，通信装置500可以是一个通用通信设备或者是一个专用通信设备。在具体实现中，通信装置500可以是台式机、便携式电脑、网络服务器、移动手机、平板电脑、无线终端、嵌入式设备、芯片系统或有图5中类似结构的设备。本申请实施例不限定通信装置500的类型。此外，图5中示出的组成结构并不构成对该通信装置的限定，除图5所示部件之外，该通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
示例性的，本申请实施例中的UE可以为各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)等。为方便描述，本申请中，上面提到的设备统称为UE。
下面将结合图1至图5对本申请实施例提供的应用迁移的方法进行具体阐述。
结合图1-图5，如图6所示，为本申请实施例提供的一种应用迁移的方法。如图6所示，该应用迁移的方法包括步骤S601-S604。
S601、源AF获取第一信息。
该第一信息为UE的PDU会话的用户面路径改变后UE的位置信息。该UE的位置信息可以为UE的IP地址、UE的PDU会话的用户面路径对应的数据网络接入标识(data network access identity，DNAI)、或者UE在网络中的标识信息(例如，cell ID，RAN ID，跟踪区域标识(track area ID，TAI)，地理位置信息等)。可以理解的，UE的PDU会话的用户面路径对应的DNAI为UE可接入的数据网络对应的DNAI。例如，第一信息为UE重建PDU会话后的IP地址或使用创建multi-homed会话机制实现SSC mode 3时，新插入的锚点UPF对应的UE的IP地址。再例如，第一信息为UE重建PDU会话后UPF对应的DNAI。再例如，第一信息为UE移动后附着的基站的信息，如cell ID。本申请实施例对于第一信息的具体内容并不进行限定。应注意，在SSC mode 3会话重建的场景下，UE可接入的数据网络对应的DNAI，可以理解为UE重建PDU会话后的UPF对应的DNAI，或使用创建multi-homed会话机制实现SSC mode 3时，新插入的锚点UPF对应的DNAI。
示例性的，DNAI可以用来标识UPF与数据网络之间的路径，即DNAI可用于确 定UPF或DN。例如，SMF上可以保存DNAI与UPF的关系，则SMF可以基于DNAI来确定UPF，反过来，SMF也可以基于UPF确定对应的DNAI。因此当UE重建PDU会话后，若UPF发生变化，则UPF对应的DNAI也会随之变化，由于SMF选择UPF时需要考虑UE位置信息，因此DNAI也可以视为一种UE的位置信息。或者，SMF或AF等其它网元上可以保存DNAI与DN的关系，则SMF或AF等其它网元可以基于DNAI来确定DN，反过来，SMF也可以基于DN确定对应的DNAI。
示例性的，上述步骤S601中源AF可以在UE的PDU会话的用户面路径改变的情况下，获取第一信息。
上述UE的PDU会话的用户面路径是指从UE到基站再到UPF实体的路径。上述UE的PDU会话的用户面路径改变可以包括以下几种情况：第一种情况，UPF改变。UPF改变包括锚点UPF改变，可以理解为UE的PDU会话锚点改变。当UPF改变时，UE的IP地址也会发生变化，或者，UE可接入的数据网络发生改变，也即UE可接入的DNAI改变。第二种情况，UPF不变但基站改变。第三种情况，UPF和基站均改变。本申请实施例中UE的PDU会话的用户面路径改变的情况可以是上述任一种，本申请实施例对此并不进行限定。下述实施例仅以UE的PDU会话的用户面路径改变为UE的PDU会话发生重建为例进行说明。即，如果UE的PDU会话发生重建，UE的PDU会话的用户面路径改变，源AF获取第一信息。
示例性的，上述源AF可以为源AS或者源ES。该源AS或者源ES为PDU会话的用户面路径改变前，UE访问的AS或ES。例如，UE的PDU会话重建前，UE访问腾讯视频的AS，该腾讯视频的AS为源AS。可选的，该源AS可以为图2中的EAS，该源ES可以为图2中的EES。
示例性的，当步骤S601中的源AF为源AS时，上述步骤S601中源AF获取第一信息即为源AS获取第一信息，该源AS获取的第一信息可以来自核心网网元(例如，AMF实体、UPF实体、PCF实体或SMF实体)，或者，也可以来自源ES。
第一种实现方式中，当源AS获取的第一信息来自PCF实体或SMF实体时，在步骤S601之前，源AS可以向PCF实体或SMF实体订阅用户面管理事件(User plane management event)通知，该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源AS。当UE的PDU会话的用户面路径发生变化时，PCF实体或SMF实体向源AS发送用于指示UE的PDU会话的用户面路径改变的第一通知消息，该第一通知消息中可以包括第一信息。
第二种实现方式中，当源AS获取的第一信息来自源ES时，在步骤S601之前，源AS可以向源ES订阅用户面管理事件通知，该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源AS。当UE的PDU会话的用户面路径发生变化时，源ES向源AS发送用于指示UE的PDU会话的用户面路径改变的第二通知消息，该第二通知消息中可以包括第一信息。可选的，源ES可以通过PCF实体或SMF实体或UE获知UE的PDU会话的用户面路径发生变化。
第三种实现方式中，当源AS获取的第一信息来自核心网网元时，在步骤S601之前，源AS可以向源ES订阅用户面管理事件通知，该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源AS。当UE的PDU会话的用户面路径发生变 化时，源ES向源AS发送用于指示UE的PDU会话的用户面路径改变的第二通知消息。该第二通知消息中可以包括第一信息；若第二通知消息中不包括第一信息，源AS接收该第二通知消息后可以向核心网网元(例如，AMF实体、SMF实体或UPF实体)发送请求消息，以获取上述第一信息。即该实现方式中第一信息并没有包括在源ES发送的第二通知消息中，而是在源AS收到源ES发送的第二通知消息后，通过向核心网网元发送请求消息获取的。
示例性的，当步骤S601中的源AF为源ES时，上述步骤S601中源AF获取第一信息即为源ES获取第一信息，该源ES获取的第一信息可以来自PCF实体或SMF实体，或者，也可以来自UE。
第一种实现方式中，当源ES获取的第一信息来自PCF实体或SMF实体时，在步骤S601之前，源ES可以向PCF实体或SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源ES。当UE的PDU会话的用户面路径发生变化时，PCF实体或SMF实体向源ES发送用于指示UE的PDU会话的用户面路径改变的第三通知消息，该第三通知消息中可以包括上述第一信息。
第二种实现方式中，当源ES获取的第一信息来自UE时，步骤S601包括：源ES接收来自UE的EEC发送的用于指示UE的PDU会话重建的第四通知消息，该第四通知消息中包括上述第一信息。可选的，源ES获取的第一信息，也可以是源ES接收UE的EEC发送的第四通知消息后，向5GC请求得到的。
可选的，当上述第三通知消息或第四通知消息中不包括第一信息时，源ES还可以向核心网网元(例如，AMF实体、SMF实体或UPF实体)发送请求以获取该第一信息。
需要说明的是，本申请实施例对于源AF获取第一信息的具体采用上述哪种实现方式并不进行限定。
S602、源AF基于第一信息，确定目标AS。
该目标AS与源AS服务相同的应用。例如，若源AS是腾讯视频App的AS，那么目标AS也是腾讯视频App的AS，即源AS和目标AS都能为腾讯视频App这个应用服务。在将UE的上下文从源AS迁移至目标AS后，目标AS能继续为UE提供服务。也就是说，源AS和目标AS是能为同一个应用服务的两个应用服务器。
可选的，目标AS和源AS的应用标识(edge application server ID，EAS ID)相同。
在一种实现方式中，该目标AS与源AS服务相同的应用表示两个应用服务器能提供的服务是一致的，源AS和目标AS均仅能提供腾讯视频服务。在另一种实现方式中，该目标AS与源AS服务相同的应用，但两种应用服务器能提供的服务是不一致的，比如源AS能提供腾讯视频服务，目标AS能提供腾讯视频服务和腾讯地图服务。例如，UE移动前，UE连接源AS访问腾讯视频服务，应用迁移后，可由目标AS继续提供腾讯视频服务。
可选的，源AS和目标AS可以部署在同一个数据网络，也可以部署在不同的数据网络中。例如，若UE的PDU会话的用户面路径改变时切换了数据网络，那么源AS为源数据网络(切换前的数据网络)中部署的应用服务器，目标AS为目标数据网络(切换后的数据网络)中部署的应用服务器。再例如，若UE的PDU会话的用户面路 径改变前后访问同一个数据网络，那么，源AS和目标AS为部署在该数据网络中，且服务于同一个应用的两个服务器。本申请实施例仅以源AS和目标AS部署在不同的数据网络中为例进行说明。当源AS和目标AS分别为源EAS和目标EAS时，源AS和目标AS部署在不同的边缘数据网络EDN中，且为同一个应用服务。
示例性的，上述步骤S602中源AF基于第一信息确定目标AS，可以包括：源AF基于第一信息，获取UE的PDU会话的用户面路径改变后的UPF实体的信息；源AF基于UPF实体的信息，确定目标AS。例如，以第一信息为UE的IP地址，UPF实体的信息为DNAI为例，源AF获取到UE的IP地址后，可以基于UE的IP地址，向5GC发送请求以获取UE的DNAI，并基于DNAI确定目标AS。
示例性的，源AF基于DNAI确定目标AS包括：源AF根据DNAI确定新的PSA，进而确定该新的PSA连接的MEC，从而选择该MEC中部署的EAS作为目标AS。
示例性的，源AF上保存有第一信息与目标AS的关系，源AF根据获取到的第一信息查询该映射关系，确定目标AS。其中，该映射关系的存储形式可以是关系表、上下文、键值对等形式，本申请实施例对此不做限定。例如，源AF上保存有目标AS与目标AS对应的服务范围信息这一关系，则源AF获取到UE的位置信息后，可确定哪个AS的服务范围保护了该UE的位置，即确定该AS为目标AS。或者，源AF上保存有目标AS与DNAI的对应关系，则源AF获取到用户面路径改变后的UPF实体对应的DNAI，从而确定目标AS。又或者，源AF上保存有目标AS与IP地址或IP地址段的对应关系，则源AF获取到用户面路径改变后UE新的IP地址，从而确定目标AS。本申请实施例对于源AF基于第一信息，具体如何确定目标AS的实现方式并不进行限定，在此仅是示例性说明。
(可选的)S603、源AF向UE发送目标AS的连接信息。
该目标AS的连接信息包括AS的地址信息，该目标AS的连接信息可以是目标AS的IP地址、目标AS的统一资源标志符(Uniform Resource Identifier，URI)、或统一资源定位符(Uniform Resource Locator，URL)、目标AS的端点(end point)等。
示例性的，源AS可以向UE的AC发送上述目标AS的连接信息。
示例性的，上述步骤S603中可以是由源AS向UE发送目标AS的连接信息；也可以是由源ES向UE发送目标AS的连接信息；或者可以是源AS向源ES发送目标AS的连接信息，然后源ES向UE发送目标AS的连接信息；或者还可以是由其他网络设备向UE发送目标AS的连接信息，本申请实施例对此并不限定。
可选的，上述步骤S603中源AF向UE发送的目标AS的连接信息可以包括在应用层消息中，也可以包括在非接入层(non-access stratum)NAS信令中，本申请实施例对此并不限定。例如，目标AS的连接信息包括在NAS信令中时，上述步骤S603中源AF向UE发送目标AS的连接信息可以包括：源AF向5GC(例如，AMF、SMF、PCF)发送目标AS的连接信息，5GC通过NAS信令向UE发送目标AS的连接信息。
(可选的)S604、UE接收目标AS的连接信息，并与目标AS建立连接。
示例性的，UE中的AC接收目标AS的连接信息后，AC建立Socket，UE中的OS根据目标AS的连接信息选择目标AS，并建立连接。
可选的，步骤S604中UE接收的目标AS的连接信息可以来自源ES。例如，步骤 S604之前UE可以向源ES请求目标AS的信息，源ES接收UE的请求后，向UE发送目标AS的连接信息。可选的，UE在获知该UE的PDU会话的用户面路径改变后，向源ES发送上述请求。
可选的，上述步骤S603之前还可以包括源AF触发应用迁移。该应用迁移也称为应用切换或状态迁移。该应用迁移是指将UE的上下文从源AS迁移至目标AS。该应用迁移可以理解为源AS和目标AS之间进行状态同步(上下文同步)。例如，UE的PDU会话的用户面路径改变之前，UE访问腾讯视频APP对应的源AS观看视频，用户观看的视频在第30分钟，当源AF触发应用迁移后，源AS和目标AS进行上下文同步，若迁移成功UE开始访问目标AS，并在第30分钟继续观看视频。
可选的，UE移动后访问的ES与移动前访问的ES可以相同，也可以不同。如果UE移动后访问的ES发生变化，那么UE移动前访问的ES为源ES，UE移动后访问的ES为目标ES。
可以理解的，本申请实施例在UE的PDU会话的用户面路径发生变化时，通过源AF获取UE的PDU会话的用户面路径改变后UE的位置信息，并根据该UE的位置信息可以确定出目标AS并触发应用迁移。该方案基于UE的PDU会话的用户面路径改变后UE的位置信息确定的目标AS较为准确，因此UE访问该目标AS时的时延较小。而且本方案不需要UE中的AC接收来自OS的指示UE重建会话的通知、发起DNS查询并获取目标AS的地址，即本方案是由网络侧设备触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
下面对本申请实施例提供的应用迁移的方法的各种实施方式进行具体阐述。
本申请实施例提供的应用迁移的方法的流程示意图如图7所示，涉及到源AS、PCF实体/SMF实体和UE之间的交互，包括如下步骤：
S701、源AS向PCF实体或SMF实体订阅用户面管理事件通知。
该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源AS。
示例性的，源AS可以直接向PCF实体订阅用户面管理事件通知，也可以直接向SMF实体订阅用户面管理事件通知。需要说明的是，由于UE的PDU会话的用户面路径是否改变是由SMF管理的，所以源AS在向PCF订阅用户面管理事件时，PCF可以向SMF订阅用户面管理事件，从而在SMF确定改变UE的PDU会话的用户面路径时，SMF可以通知PCF，PCF再通知源AS。可选的，在SMF确定改变UE的PDU会话的用户面路径时，也可以直接由SMF通知源AS。
可选的，在上述步骤S701之前还可以包括源AS请求与PCF实体或SMF实体建立关联(policy association)，PCF实体或SMF实体将会话模式发送给源AS，该会话模式可以为SSC mode 3。
S702、PCF实体或SMF实体向源AS发送第一通知消息。
该第一通知消息用于通知源AS，UE的PDU会话的用户面路径改变。即当PCF实体或SMF实体确定UE的PDU会话的用户面路径改变时，PCF实体或SMF实体向源AS发送该第一通知消息。可选的，该第一通知消息中可以包括第一信息。关于第一信息的描述可以参考前述实施例，在此不再赘述。
当UE的PDU会话的SSC mode为SSC mode3时，上述UE的PDU会话的用户面 路径改变包括UE的PDU会话重建。
示例性的，UE的PDU会话的用户面路径改变可以是基于UE移动或负载均衡等触发的。例如，如图3所示，以第一信息为UE的IP地址为例，当UE在访问MEC1中的EAS2时，会话的锚点UPF为PSA1，UE的IP地址为IP@1。若UE移动到MEC2的服务范围内，SMF决定重建PDU会话，SMF向UE发送新建一个会话的指示。可选地，该指示中可以包括一个定时器，当定时器超时，释放旧的PDU会话。对应的，UE发起创建一个会话的请求，SMF收到会话请求后，为当前会话选择新的会话锚点UPF，即PSA2，并为UE分配新的IP地址IP@2，SMF将新的IP地址IP@2发送给PCF，PCF将该新的IP地址IP@2发送给源AS。
需要说明的是，重建前的PDU会话(旧的PDU会话)和重建的PDU会话(新的PDU会话)的SMF可以相同，也可以不同。也就是说，重建PDU会话时可以改变SMF，也可以不改变SMF。
示例性的，当重建PDU会话不改变SMF时，可以由该SMF关联旧的PDU会话(重建前的PDU会话)和新的PDU会话(重建的PDU会话)，该SMF可向源AS发送新的IP地址或者新PDU会话的锚点PSA2对应的DNAI或者UE的位置信息。
示例性的，当重建PDU会话时改变SMF时，旧的SMF(即重建PDU会话前的SMF)向AMF发送PCF的信息，AMF向新的SMF(重建PDU会话后的SMF)发送该PCF的信息，新的SMF根据该PCF的信息选择相同的PCF。即虽然重建PDU会话时改变了SMF，但是PCF并未改变，所以可以由该PCF关联新的PDU会话和旧的PDU会话，并由该PCF向源AS发送新的IP地址或者新的DNAI或者UE位置信息。
可以理解的，步骤S702中的第一通知消息是响应步骤S701中源AS向PCF实体或SMF实体订阅的用户面管理事件通知的。
S703、源AS接收第一通知消息。
S704、源AS基于第一信息，确定目标AS。
示例性的，当第一通知消息中包括第一信息时，源AS可以基于第一通知消息中包括的第一信息，确定目标AS。可选的，当第一通知消息中不包括第一信息时，在步骤S704之前，当源AS接收第一通知消息后，可以向5GC网元发送请求以获取第一信息，并基于从5GC网元获取的第一信息确定目标AS。例如，源AS可以向AMF实体获取UE位置信息，或者向SMF实体获取当前服务UE的UPF对应的DNAI，或者向SMF实体或UPF实体获取当前UE的IP地址等。
可以理解的，上述步骤S704中源AS基于第一信息，确定目标AS的具体实现方式，可以参考步骤S602中源AF基于第一信息，确定目标AS的实现方式，在此不再赘述。
S705、源AS触发应用迁移。
该应用迁移是指将UE访问的应用服务器从源AS迁移至目标AS。
可选的，步骤S705中也可以是由源ES触发应用迁移，当步骤S705是由源ES触发应用迁移时，在步骤S705之前还可以包括源AS向源ES发送目标AS的连接信息，以使得源ES基于目标AS的连接信息将UE的上下文从源AS迁移至目标AS。即在本申请实施例中，确定目标AS的设备和触发应用迁移的设备可以为同一个设备，也可 以为不同的设备。
可以理解的，图7中的步骤S705为可选的步骤。
S706、源AS向UE发送目标AS的连接信息。
可以理解的，目标AS的连接信息的相关描述可以参考步骤S603，在此不再赘述。
S707、UE接收目标AS的连接信息，并与目标AS建立连接。
示例性的，UE中的AC接收目标AS的连接信息后，AC建立Socket，UE中的OS根据目标AS的连接信息选择目标AS，并建立连接。
可选的，如果在应用迁移完成之后，源AS还收到UE发送的数据包，源AS可以将其收到的数据包转发给目标AS。
需要说明的是，本申请对于上述步骤S701-S707的先后执行顺序并不进行限定，图7仅是示例性说明。
可以理解的，本申请实施例提供的应用迁移的方法通过源AS向核心网网元订阅用户面事件管理通知，从而能够在UE的PDU会话的用户面路径发生变化时，接收核心网网元发送的第一通知消息，并基于该第一通知消息中包括的第一信息确定目标AS，并触发应用迁移。该方法基于UE的PDU会话的用户面路径改变后UE的位置信息确定的目标AS较为准确，因此UE访问该目标AS时的时延较小。而且该方法是由源AS触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
本申请实施例提供的应用迁移的方法的流程示意图如图8所示，涉及到源ES、PCF实体/SMF实体和UE之间的交互，包括如下步骤：
S801、源ES向PCF实体或SMF实体订阅用户面管理事件通知。
该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源ES。
示例性的，源ES可以直接向PCF实体订阅用户面管理事件通知，也可以直接向SMF实体订阅用户面管理事件通知。需要说明的是，由于UE的PDU会话的用户面路径是否改变是由SMF管理的，所以源ES在向PCF订阅用户面管理事件时，PCF可以向SMF订阅用户面管理事件，从而在SMF确定改变UE的PDU会话的用户面路径时，SMF可以通知PCF，PCF再通知源ES。可选的，在SMF确定改变UE的PDU会话的用户面路径时，也可以由SMF直接通知源ES。
可选的，在上述步骤S801之前还可以包括源ES请求与PCF实体或SMF实体建立关联(policy association)，PCF实体或SMF实体将会话模式发送给源ES，该会话模式可以为SSC mode 3。
S802、PCF实体或SMF实体向源ES发送第三通知消息。
该第三通知消息用于通知源ES，UE的PDU会话的用户面路径改变。即当PCF实体或SMF实体确定UE的PDU会话的用户面路径改变时，PCF实体或SMF实体向源ES发送该第三通知消息。可选的，该第三通知消息中可以包括第一信息。关于第一信息的描述可以参考前述实施例，在此不再赘述。
可以理解的，步骤S802中的第三通知消息是响应步骤S801中源ES向PCF实体或SMF实体订阅的用户面管理事件通知的。
S803、源ES接收第三通知消息。
S804、源ES基于第一信息，确定目标AS。
示例性的，当第三通知消息中包括第一信息时，源AS可以基于第三通知消息中包括的第一信息，确定目标AS。可选的，当第三通知消息中不包括第一信息时，源AS接收第三通知消息后，可以向5GC网元发送请求以获取第一信息，并基于从5GC网元获取的第一信息确定目标AS。例如，源ES可以向AMF实体获取UE位置信息，或者向SMF实体获取当前服务UE的UPF对应的DNAI，或者向SMF实体或UPF实体获取当前UE的IP地址等。
可以理解的，上述步骤S804中源ES基于第一信息，确定目标AS的具体实现方式，可以参考步骤S602中源AF基于第一信息，确定目标AS的实现方式，在此不再赘述。
S805、源ES触发应用迁移。
该应用迁移是指将UE访问的应用服务器从源AS迁移至目标AS。
可选的，步骤S805中也可以是由源AS触发应用迁移，当步骤S805是由源AS触发应用迁移时，在步骤S805之前还可以包括源ES向源AS发送目标AS的连接信息，以使得源AS基于目标AS的连接信息将UE的上下文从源AS迁移至目标AS。
可以理解的，图8中的步骤S805为可选的步骤。
S806、源ES向UE发送目标AS的连接信息。
该目标AS的连接信息包括目标AS的地址信息。该目标AS的连接信息可以是目标AS的IP地址、目标AS的URI、目标AS的URL、或目标AS的端点(end point)等信息。
示例性的，源ES可以向UE中的AC发送上述目标AS的连接信息。
S807、UE接收目标AS的连接信息，并与目标AS建立连接。
可以理解的，上述步骤S806-S807的具体实现方式可以参考步骤S706-S707，在此不再赘述。
需要说明的是，本申请对于上述步骤S801-S807的先后执行顺序并不进行限定，图8仅是示例性说明。
可以理解的，本申请实施例提供的应用迁移的方法通过源ES向核心网网元订阅用户面事件管理通知，从而能够在UE的PDU会话的用户面路径发生变化时，接收核心网网元发送的第三通知消息，并基于该第三通知消息中包括的第一信息确定目标AS，并触发应用迁移。该方法基于UE的PDU会话的用户面路径改变后UE的位置信息确定的目标AS较为准确，因此UE访问该目标AS时的时延较小。而且该方法是由源ES触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
本申请实施例提供的应用迁移的方法的流程示意图如图9所示，涉及到源AS、源ES、PCF实体/SMF实体和UE之间的交互，包括如下步骤：
S901、源AS向源ES订阅用户面管理事件通知。
该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源AS。
S902、源ES向PCF实体或SMF实体订阅用户面管理事件通知。
该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源ES。
S903、PCF实体或SMF实体向源ES发送第三通知消息。
该第三通知消息用于通知源ES，UE的PDU会话的用户面路径改变。即当PCF实体或SMF实体确定UE的PDU会话的用户面路径改变时，PCF实体或SMF实体向源ES发送该第三通知消息。可选的，该第三通知消息中可以包括第一信息。关于第一信息的描述可以参考前述实施例，在此不再赘述。
可以理解的，步骤S903中的第三通知消息是响应步骤S902中源ES向PCF实体或SMF实体订阅的用户面管理事件通知的。
S904、源ES接收第三通知消息。
S905、源ES向源AS发送第二通知消息。
该第二通知消息用于通知源AS，UE的PDU会话的用户面路径改变。即当源ES确定UE的PDU会话的用户面路径改变时，源ES向源AS发送该第二通知消息。可选的，该第二通知消息中可以包括第一信息。该第一信息可以为UE的PDU会话的用户面路径改变后UE的DNAI。
可以理解的，步骤S905中的第二通知消息是响应步骤S901中源AS向源ES订阅的用户面管理事件通知的。
S906、源AS接收第二通知消息。
S907、源AS基于第一信息，确定目标AS。
示例性的，当第二通知消息中包括第一信息时，源AS可以基于第二通知消息中包括的第一信息确定目标AS。可选的，当第二通知消息中不包括第一信息时，源AS接收第二通知消息后，可以向5GC网元发送请求以获取第一信息，并基于从5GC网元获取的第一信息确定目标AS。
可以理解的，上述步骤S907中源AS基于第一信息，确定目标AS的具体实现方式，可以参考步骤S602中源AF基于第一信息，确定目标AS的实现方式，在此不再赘述。
S908、源AS触发应用迁移。
该应用迁移是指将UE访问的应用服务器从源AS迁移至目标AS。
可选的，步骤S908中也可以是由源ES触发应用迁移，当步骤S908是由源ES触发应用迁移时，在步骤S908之前还可以包括源AS向源ES发送目标AS的连接信息，以使得源ES基于目标AS的连接信息将UE的上下文从源AS迁移至目标AS。
可以理解的，图9中的步骤S908为可选的步骤。
S909、源AS向UE发送目标AS的连接信息。
S910、UE接收目标AS的连接信息，并与目标AS建立连接。
可以理解的，上述步骤S909-S910的具体实现方式可以参考步骤S706-S707，在此不再赘述。
需要说明的是，本申请对于上述步骤S901-S910的先后执行顺序并不进行限定，图9仅是示例性说明。
可以理解的，本申请实施例提供的应用迁移的方法通过源AS向源ES订阅用户面事件管理通知，源ES向核心网网元订阅用户面事件管理通知，从而能够在UE的PDU会话的用户面路径发生变化时，源ES接收核心网网元发送的通知消息，并向源AS发 送通知，源AS可以基于源ES发送的通知中包括的第一信息确定目标AS，并触发应用迁移。该方法基于UE的PDU会话的用户面路径改变后UE的位置信息确定的目标AS较为准确，因此UE访问该目标AS时的时延较小。而且该方法是由源AS触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
本申请实施例提供的应用迁移的方法的流程示意图如图10所示，涉及到源AS、源ES、UE中的EEC、UE中的OS和UE中的AC之间的交互，包括如下步骤：
S1001、源AS向源ES订阅用户面管理事件通知。
该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源AS。可以理解的，UE的PDU会话的用户面路径改变包括UE的PDU会话重建。
S1002、UE中的EEC向UE中的OS订阅会话重建事件通知。
该会话重建事件通知用于当UE的PDU会话发生重建时通知UE中的EEC。
S1003、UE中的OS向UE中的EEC发送第六通知消息。
该第六通知消息用于通知UE中的EEC，UE的PDU会话发生重建。即当UE中的OS确定UE的PDU会话重建时，UE中的OS向UE中的EEC发送该第六通知消息。可选的，该第六通知消息中包括第一信息。
可以理解的，步骤S1003中的第六通知消息是响应步骤1002中UE中的EEC向UE中的OS订阅的会话重建事件通知的。
S1004、UE中的EEC接收第六通知消息。
S1005、UE中的EEC向源ES发送第四通知消息。
该第四通知消息用于通知源ES，UE的PDU会话重建。即当UE中的EEC确定UE的PDU会话重建时，UE中的EEC向源ES发送该第四通知消息。可选的，该第四通知消息中包括第一信息。
可选的，步骤S1005中UE中的EEC向源ES发送的第四通知消息中可以包括新的DNAI，和/或新的IP地址，和/或UE在网络中的位置标识信息。
S1006、源ES接收第四通知消息。
可选的，当第四通知消息中不包括第一信息时，源ES可以向5GC网元(比如AMF实体或SMF实体等)发送请求以获取第一信息，比如向AMF实体获取UE在网络中的位置标识信息，或者向SMF实体获取当前服务UE的UPF对应的DNAI，或者向SMF实体或UPF实体获取当前UE的IP地址等。
S1007、源ES向源AS发送第二通知消息。
该第二通知消息用于通知源AS，UE的PDU会话的用户面路径改变。即源ES确定UE的PDU会话的用户面路径改变时，源ES向源AS发送该第二通知消息。可选的，该第二通知消息中可以包括第一信息。
可以理解的，步骤S1007中的第二通知消息是响应步骤S1001中源AS向源ES订阅的用户面管理事件通知的。
S1008、源AS接收第二通知消息。
S1009、源AS基于第一信息，确定目标AS。
示例性的，当第二通知消息中包括第一信息时，源AS可以基于第二通知消息中 包括的第一信息确定目标AS。可选的，当第二通知消息中不包括第一信息时，源AS接收第二通知消息后，可以向5GC网元发送请求以获取第一信息，并基于从5GC网元获取的第一信息确定目标AS。
可选的，当第二通知消息中包括的第一信息为UE的IP地址时，源AS在接收第二通知消息中后，可以向5GC网元查询该UE的IP地址的路径信息，并基于该路径信息确定目标AS。例如，源AS可根据该IP地址建立AF policy association，并通过该AF policy association查询该会话的路径信息(例如，会话对应的DNAI)或UE的位置信息，并基于DNAI或UE的位置信息确定目标AS。
可以理解的，上述步骤S1009中源AS基于第一信息，确定目标AS的具体实现方式，可以参考步骤S602中源AF基于第一信息，确定目标AS的实现方式，在此不再赘述。
S1010、源AS触发应用迁移。
可选的，步骤S1010中也可以是由源ES触发应用迁移，当步骤S1010是由源ES触发应用迁移时，在步骤S1010之前还可以包括源AS向源ES发送目标AS的连接信息，以使得源ES基于目标AS的连接信息将UE的上下文从源AS迁移至目标AS。
可以理解的，图10中的步骤S1010为可选的步骤。
S1011、源AS向UE发送目标AS的连接信息。
该目标AS的连接信息包括目标AS的地址信息。该目标AS的连接信息可以是目标AS的IP地址、目标AS的URI、目标AS的URL、或目标AS的端点(end point)等信息。
示例性的，源AS可以向UE中的AC发送上述目标AS的连接信息。
S1012、UE接收目标AS的连接信息，并与目标AS建立连接。
可以理解的，上述步骤S1011-S1012的具体实现方式可以参考步骤S706-S707，在此不再赘述。
需要说明的是，本申请对于上述步骤S1001-S1012的先后执行顺序并不进行限定，图10仅是示例性说明。
可以理解的，本申请实施例提供的应用迁移的方法通过UE中的EEC向UE中的OS订阅会话重建事件通知，从而能够在UE的PDU会话重建时，UE中的OS通知UE中的EEC，UE中的EEC通知源ES，源ES向源AS发送通知，源AS可以基于源ES发送的通知中包括的信息确定目标AS，并触发应用迁移。该方法基于UE的PDU会话的用户面路径改变后UE的位置信息确定的目标AS较为准确，因此UE访问该目标AS时的时延较小。而且该方法是由源AS触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
本申请实施例提供的应用迁移的方法的流程示意图如图11所示，涉及到源ES、UE中的EEC、UE中的OS和UE中的AC之间的交互，包括如下步骤：
S1101、UE中的EEC向UE中的OS订阅会话重建事件通知。
S1102、UE中的OS向UE中的EEC发送第六通知消息。
S1103、UE中的EEC接收第六通知消息。
S1104、UE中的EEC向源ES发送第四通知消息。
S1105、源ES接收第四通知消息。
可以理解的，上述步骤S1101-S1105的具体实现方式可以参考步骤S1002-S1006的实现方式，在此不再赘述。
S1106、源ES基于第一信息，确定目标AS。
示例性的，当第四通知消息中包括第一信息时，源ES可以基于第四通知消息中包括的第一信息确定目标AS。可选的，当第四通知消息中不包括第一信息时，源ES接收第四通知消息后，可以向5GC网元发送请求以获取第一信息，并基于从5GC网元获取的第一信息确定目标AS。
可以理解的，上述步骤S1106中源ES基于第一信息，确定目标AS的具体实现方式，可以参考步骤S602中源AF基于第一信息，确定目标AS的实现方式，在此不再赘述。
S1107、源ES触发应用迁移。
可选的，步骤S1107中也可以是由源AS触发应用迁移，当步骤S1107是由源AS触发应用迁移时，在步骤S1107之前还可以包括源ES向源AS发送目标AS的连接信息，以使得源AS基于目标AS的连接信息将UE的上下文从源AS迁移至目标AS。
可以理解的，图11中的步骤S1107为可选的步骤。
S1108、源ES向UE发送目标AS的连接信息。
示例性的，源ES可以向UE中的AC发送上述目标AS的连接信息。
S1109、UE接收目标AS的连接信息，并与目标AS建立连接。
需要说明的是，本申请对于上述步骤S1101-S1109的先后执行顺序并不进行限定，图11仅是示例性说明。
本申请实施例提供的应用迁移的方法通过UE中的EEC向UE中的OS订阅会话重建事件通知，从而能够在UE的PDU会话重建时，UE中的OS通知UE中的EEC，UE中的EEC通知源ES，由源ES确定目标AS，并触发应用迁移。该方法基于UE的PDU会话的用户面路径改变后UE的位置信息确定的目标AS较为准确，因此UE访问该目标AS时的时延较小。而且该方法是由源ES触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
本申请实施例提供的应用迁移的方法的流程示意图如图12所示，涉及到源AS、目标ES、UE中的EEC、UE中的OS和UE中的AC之间的交互，包括如下步骤：
S1201、UE中的EEC向UE中的OS订阅会话重建事件通知。
S1202、UE中的OS向UE中的EEC发送第六通知消息。
S1203、UE中的EEC接收第六通知消息。
示例性的，UE中的EEC接收第六通知消息后，基于该第六通知消息获知UE的PDU会话发生重建，确定需要进行应用切换。
可以理解的，上述步骤S1201-S1203的具体实现方式可以参考步骤S1002-S1004的实现方式，在此不再赘述。
S1204、UE中的EEC基于第一信息，确定目标ES。
示例性的，当第六通知消息中包括第一信息时，UE中的EEC可以基于第六通知消息中的第一信息确定目标ES。
在一种实现方式中，目标ES与源ES是同一个ES。在另一种实现方式中，目标ES与源ES不同的ES。
该目标ES可以为UE可接入的DN中部署的ES。可选的，UE可接入的DN可以有一个或多个。
S1205、UE中的EEC向目标ES发送发现请求。
发现请求用于请求目标ES管理的AS列表。可选的，该AS列表可以是与源AS服务相同的应用的AS列表。例如，源AS为腾讯视频的AS，该发现请求用于请求目标ES管理的腾讯视频的AS的列表。
可选的，该发现请求中可以包括源AS的标识信息。
S1206、目标ES接收发现请求。
S1207、目标ES向UE中的EEC发送第一消息。
该第一消息中包括目标ES管理的一个或多个AS的连接信息。可选的，该一个或多个AS可以与源AS服务相同的应用。例如，目标ES向UE发送其管理的所有腾讯视频的AS的连接信息。
S1208、UE中的EEC接收第一消息，并基于第一消息从目标ES管理的一个或多个AS中确定目标AS。
示例性的，UE中的EEC可以从目标ES管理的一个或多个AS中选择一个AS为目标AS。在一种实现方式中，第一消息中包含了一个或多个AS的优先级，EEC选择优先级最高的AS作为目标AS。
S1209、UE中的EEC向UE中的AC发送目标AS的连接信息。
S1210、UE中的AC接收目标AS的连接信息，并与目标AS建立连接。
S1211、UE中的AC向源AS发送目标AS的连接信息。
可选的，步骤S1211中UE中的AC也可以向源ES发送目标AS的连接信息，以使得源ES接收目标AS的连接信息，并将UE的上下文从源AS迁移至目标AS。
S1212、源AS接收目标AS的连接信息，并触发应用迁移。
示例性的，源AS接收目标AS的连接信息后，可以执行源AS与目标AS之间的状态迁移，或者称为应用上下文迁移。
该应用迁移是指将UE的上下文从源AS迁移至目标AS。
可选的，当步骤S1211中UE中的AC向源ES发送目标AS的连接信息时，步骤S1212中源ES可以接收目标AS的连接信息，并触发应用迁移。即在本实施例中可以是源AS触发应用迁移，也可以是源ES触发应用迁移。
可以理解的，上述步骤S1011-S1212是可选的步骤。为了提高UE访问应用的时延，源AS或源ES可以执行源AS与目标AS之间的上下文同步。
需要说明的是，本申请对于上述步骤S1201-S1212的先后执行顺序并不进行限定，图12仅是示例性说明。
可以理解的，本申请实施例提供的应用迁移的方法通过UE中的EEC向UE中的OS订阅会话重建事件通知，从而能够在UE的PDU会话重建时，UE中的OS通知UE中的EEC，UE中的EEC确定目标AS，并向源ES或源AS发送该目标AS的连接信息，源ES或源AS触发应用迁移。该方法基于UE的PDU会话的用户面路径改变后 UE的位置信息确定的目标AS较为准确，因此UE访问该目标AS时的时延较小。而且该方法是由源ES或源AS触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
示例性的，以源ES向PCF实体/SMF实体订阅用户面管理事件通知为例。当UE访问源DN中部署的源AS(例如，源AS为腾讯视频的AS)时，若UE发生移动且UE的PDU会话发生重建，源ES可以从PCF实体/SMF实体获知UE的PDU会话的用户面路径改变，但是由于源ES并不知道该UE当前在访问源DN中的哪个AS，所以源ES将向源DN中部署的所有AS发送用于指示UE的PDU会话的用户面路径发生变化的通知消息，但是UE可能仅访问源DN中腾讯视频的AS，因此，源ES发送给其他AS(源DN中部署的UE未访问的AS)的通知消息是无效的。而且如果UE移动后可接入的DN中并未部署腾讯视频的AS，那么源ES向源AS发送的通知消息是无效的。因此，为了减少应用迁移过程中的无效通知，本申请实施例还提供一种应用迁移的方法，该方法通过源AS向源ES发送订阅请求，从而能够在源ES确定存在目标AS时，再向源AS发送包括目标AS的连接信息的通知消息，因此能够减少应用迁移过程中的无效通知。
本申请实施例提供的应用迁移的方法的流程示意图如图13所示，涉及到源AS、源ES、PCF实体/SMF实体、目标AS和UE之间的交互，包括如下步骤：
S1301、源AS向源ES发送订阅请求。
该订阅请求用于当源ES确定存在目标AS时通知源AS。可选的，订阅请求还可以用于当源ES确定UE可接入的DN中存在目标AS时通知源AS。在一种实现方式中，该订阅请求可以为应用切换事件通知，对订阅请求的名称不做限定。
可选的，订阅请求中可以包括应用标识信息。该应用标识信息为应用对应的标识信息，比如appliation ID，或者应用标识信息为应用对应的服务器的标识信息，比如EAS ID(edge application server ID)。
示例性的，目标AS和源AS服务相同的应用。即该目标AS和源AS的应用标识(edge application server ID，EAS ID)相同。
可选的，源ES从目标ES或CS获取可用AS或可接入的AS，确定UE可接入的DN中存在目标AS，可用于将UE访问的应用服务器从源AS切换到目标AS，从而提升用户体验，比如更低的时延，更高的带宽等。
可选的，在UE建立了与源AS的连接时或建立了与源AS的连接后，源AS可以向源ES发送订阅请求。
示例性的，UE可接入的DN可以是UE移动后的位置可以接入的一个或多个数据网络。可以理解的，UE移动后，其可接入的数据网络中不一定部署了与源AS服务相同应用的AS，因此通过发送订阅请求，能够在源ES确定UE可接入的数据网络中存在与源AS服务相同应用的AS时，再通知源AS，进而发起应用迁移。
在一种实现方式中，DN具有特定的服务范围或服务区域，当UE进入该特定的服务范围或服务区域内时，可以视为该DN为UE可接入的DN，反之，则可以认为该DN不是UE在当前位置下可接入的DN。应理解，UE在当前位置下，可接入的DN可以有0个、1个或多个。也就是说，上述订阅请求可以用于当源ES确定存在目标 AS能服务当前位置的UE时通知源AS，该目标AS和源AS服务相同的应用。例如，AS具有特定的服务范围或服务区域，当UE处于该特定的服务范围或服务区域内时，可以视为该AS能服务当前位置的UE，反之，则可以认为该AS不能服务当前位置的UE。应理解，源ES确定UE可接入的DN中存在目标AS和源ES确定存在目标AS能服务当前位置的UE具有相同的含义，以下仅以源ES确定UE可接入的DN中存在目标AS为例进行说明。
可选的，步骤S1301也可以是源AS向源ES发送用于指示源AS是否支持应用切换，或者，用于指示源AS对应的应用是否支持切换的指示信息。可以理解的，源AS向源ES发送用于指示源AS支持应用切换的指示信息，从而使得源ES确定UE可接入的DN中存在目标AS时，源ES可以直接确定做应用迁移或者源ES确定执行应用迁移。需要说明的是，本申请实施例中的应用迁移，也可以称为应用切换，即将UE的上下文从源AS切换为目标AS。
可选的，订阅请求中还可以包括UE的PDU会话的信息。该UE的PDU会话的信息包括UE的网络协议IP地址、数据网络名称(data netword name，DNN)、或单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)中的至少一种。可选的，源ES可以根据订阅请求中包括的UE的PDU会话的信息，确定策略控制功能PCF实体或会话管理功能SMF实体。
可选的，订阅请求中包括应用标识信息，源ES可以基于应用标识信息确定目标AS，当源ES确定存在目标AS能服务当前位置的UE时通知源AS。在另一种实现方式中，源ES可以根据收到的源AS的订阅请求确定出源AS对应的应用标识信息
S1302、源ES向PCF实体或SMF实体订阅用户面管理事件通知，该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知源ES。可选的，该UE的PDU会话的用户面路径改变包括UE的PDU会话发生重建。或者，源ES向AMF实体订阅UE的移动性事件或者位置变更事件通知，该移动性事件或者位置变更事件通知用于当UE的位置发生改变时通知源ES。可选的，位置变更的粒度可以包括UE的cell改变、RAN改变、TA改变，RA改变等，本申请对此不做限定。
可以理解的，源ES向PCF实体或SMF实体或AMF实体订阅通知可以是源ES直接向PCF实体或SMF实体或AMF实体订阅，也可以是通过其它实体订阅，比如NEF，本申请对此不做限定。
可选的，在本实施例中UE的PDU会话的SSC模式可以为SSC mode1、SSC mode2或SSC mode3。
S1303、PCF实体或SMF实体向源ES发送第三通知消息。
可以理解的，步骤S1303中的第三通知消息是响应步骤S1302中源ES向PCF实体或SMF实体订阅的用户面管理事件通知，或者，也可以是响应步骤S1302中源ES向AMF实体订阅位置变更事件通知。可选的，第三通知消息中可以包含第一信息。关于第一信息的相关描述可以参考前述实施例，在此不再赘述。
可选的，步骤S1303也可以是AMF实体向源ES发送第三通知消息。
可选的，第三通知消息可以为SMF或PCF发送的ealier notification，用于指示源ES 5GC将要或想要切换UE会话的用户面路径。
S1304、源ES接收第三通知消息。
S1304a、源ES确定是否存在目标AS。
可选的，源ES根据第一信息确定UE可接入的DN中是否存在目标AS，包括：源ES可以请求CS或目标ES确定UE可接入的DN中是否存在目标AS。在一种实现方式中，源ES将第一信息以及应用标识信息发送给CS，CS基于第一信息和应用标识信息确定目标ES，CS将目标ES发送给源ES，源ES从目标ES获取UE可接入的DN中存在一个或多个AS，其中目标ES位于UE可接入的DN中。目标ES将一个或多个AS的信息发送给源ES，若目标ES管理的AS有多个，可以由目标ES确定一个发送给源ES，也可以发送多个AS的信息给源ES，由源ES确定目标AS。在另一种实现方式中，源ES将第一信息以及应用标识信息发送给CS，CS基于第一信息和应用标识信息确定UE可接入的DN中存在一个或多个AS，CS将一个或多个AS的信息发送给源ES，源ES确定目标AS。在另一种实现方式中，源ES将第一信息以及应用标识信息发送给目标ES，目标ES基于第一信息和应用标识信息确定目标ES对应的DN中存在一个或多个AS，目标ES将一个或多个AS的信息发送给源ES，源ES确定目标AS。若源ES从目标ES或CS获取到目标AS，则源ES确定存在可接入的目标AS，反之，则源ES确定不存在可接入的目标AS。可以理解的是，即若源AS与目标ES均由源ES管理时，上述源ES和目标ES可能为同一个ES，源ES与目标ES之间的交互可以跳过。上述AS的信息可以为AS的连接信息。
可选的，源ES确定是否存在目标AS可以包括：源ES根据第一信息和应用标识信息，确定是否存在目标AS。在一种实现方式中，第三通知消息中包含的第一信息为UE的PDU会话的用户面路径对应的DNAI，若源ES确定该DNAI对应的DN中存在应用标识信息对应的AS，则源ES确定存在目标AS。否则，则源ES确定该DNAI对应的DN中不存在应用标识信息对应的AS，则源ES可将第一信息以及应用标识信息发送给CS或目标ES，确定目标AS，方法同前所述，不再赘述。
可选的，若源ES确定UE可接入的DN中不存在目标AS，即UE可接入的DN中未部署与源AS服务相同应用的AS，那么源ES不会向源AS发送通知消息或者发送一个不存在目标AS的通知消息，源AS不会触发应用迁移，UE将继续访问源AS。
可选的，源ES接收第三通知消息后，执行确定UE可接入的DN中是否存在目标AS这一步骤。或者，源ES检测到源AS过载后执行确定UE可接入的DN中是否存在目标AS这一步骤。其他情况下，不执行该步骤，用于节省计算资源。
可选的，若源ES确定UE可接入的DN中存在目标AS，继续执行步骤S1305-S1314。
S1305、源ES向源AS发送第七通知消息。
在一种实现方式中，当源ES确定UE可接入的DN中存在目标AS，源ES向源AS发送第七通知消息。可选的，该第七通知消息中包括目标AS的连接信息。
可选的，当源ES确定UE可接入的DN中不存在目标AS时，源ES可以向源AS发送指示UE可接入的DN中不存在目标AS的通知消息。或者，当源ES确定不存在目标AS能服务当前位置的UE时，源ES可以向源AS发送指示不存在目标AS能服务当前位置的UE的通知消息。
可选的，若S1301中，源AS向源ES发送指示信息，指示信息用于指示源AS支 持应用切换，若源ES确定存在可接入的目标AS，则源ES可以直接确定需要做应用迁移，或者说源ES确定执行应用迁移。后续源AS确定需要做应用迁移的步骤可以跳过。
在另一种实现方式中，，若源ES直接确定需要做应用迁移，源ES向源AS发送第七通知消息，第七通知消息指示源AS将UE的上下文发送给源AS。
可以理解的，步骤S1305中的第七通知消息是响应步骤S1301中源AS向源ES发送的订阅请求。当源ES确定UE可接入的DN中存在目标AS，源ES向源AS发送第七通知消息。
S1306、源AS接收第七通知消息。
S1307、源AS确定将用户设备UE的上下文从源AS迁移至目标AS。
步骤S1307也可以是源AS确定需要做应用迁移，或者，源AS确定执行应用迁移。该应用迁移是指将UE的上下文从源AS迁移至目标AS。或者，该应用迁移是指应用上下文迁移，即将源AS上的上下文迁移至目标AS。其中，UE的上下文也可以称为应用上下文，上下文的名称不做限定。在一种实现方式中，源AS将UE的上下文发送给目标AS。在另一种实现方式中，源AS将UE的上下文发送给源ES，后续源ES发送给目标AS，其中，源ES可能需要经过目标ES发送给目标AS。
可选的，源AS还可以向源ES发送第四指示信息，该第四指示信息用于指示源ES将UE的上下文从源AS迁移至目标AS。
在一种实现方式中，源AS接收第七通知消息，第七通知消息中包括目标AS的连接信息，源AS确定需要做应用迁移。在另一种实现方式中，源AS可以根据不同的场景确定是否需要做应用迁移，即源AS可以确定需要做应用迁移，也可以确定不需要做应用迁移。比如，源AS可能根据负载、业务的紧急性等因素来确定当前不适宜做应用迁移，本申请对此不做限定。
在一种实现方式中，若源ES确定需要做应用迁移，则源AS收到后执行应用迁移。
示例性的，源AS接收第一通知消息后，可以直接确定触发应用迁移。即在UE可接入的DN中存在目标AS时，源AS直接确定触发应用迁移。
可选的，上述步骤S1307之前还可以包括步骤S1308-S1311，源AS可以与目标AS进行协商，确定当前是否可以做应用迁移。
可选的，S1308、源AS向目标AS发送应用切换请求消息。
该应用切换请求消息用于将源AS上的上下文迁移至目标AS。
可选的，该第一请求消息也可以用于请求目标AS分配应用切换所需的资源。
可选的，S1309、目标AS接收应用切换请求消息。
可选的，S1310、目标AS向源AS发送应用切换响应消息。
该应用切换响应消息中包括第三指示信息，第三指示信息用于指示目标AS是否同意或接受应用切换。
示例性的，目标AS可以结合其资源使用情况，确定是否同意或接受应用切换请求。若目标AS的剩余资源较多，目标AS确定同意接受应用切换。该第三指示信息可以指示目标AS同意应用切换。
可选的，S1311、源AS接收应用切换响应消息。
上述步骤S1307中源AS确定将用户设备UE的上下文从源AS迁移至目标AS可以包括：源AS基于第三指示信息确定将用户设备UE的上下文从源AS迁移至目标AS。若应用切换响应消息中的第三指示信息指示目标AS同意应用切换，源AS确定触发应用迁移。
可选的，源AS向源ES发送第五指示信息，该第五指示信息用于指示源AS是否支持应用切换或者指示源AS是否同意应用切换或者指示源AS是否执行应用切换。可以理解的，该第五指示信息响应于第七通知消息。即源ES向源AS发送指示UE可接入的DN中存在目标AS的第七通知消息后，源AS向源ES发送指示源AS是否支持应用切换的第五指示信息。
可选的，源ES收到第五指示信息后，源ES向5GC(比如SMF或PCF或AMF)发送第六指示信息，该第六指示信息用于指示源AS是否支持应用切换，可以理解的，该第六指示信息响应于第三通知消息。5GC可以基于该第六指示信息确定是否终止切换会话的用户面路径。例如，若第六指示信息指示源AS不支持应用切换，则SMF收到源ES发送的第六指示信息后终止切换UE的PDU会话的用户面路径。
可选的，源AS还可以向源ES发送第七指示信息，该第七指示信息用于指示应用切换时需要保持业务连续性。该第七指示信息用于在DNAI改变的时候，建立UPF之间的转发隧道，用于做业务连续性，以便UE可将应用数据发送给源AS。
可选的，源ES接收第七指示信息后，源ES向SMF或PCF发送第八指示信息，该第八指示信息用于指示应用切换时需要保持业务连续性。从而在源ES完成切换后，通过向5GC网元发送该第八指示信息，使得5GC网元可以释放转发隧道。
S1312、源AS触发应用迁移。
可以理解的，图13中的步骤S1312为可选的步骤。
在一种实现方式中，源AS收到目标AS的连接信息，则源AS触发应用迁移。
在一种实现方式中，源AS将应用上下文直接发送给目标AS。
在另一种实现方式中，源AS将应用上下文发送给源ES，源ES将上下文发送给目标ES，再由目标ES发送给目标AS。
S1313、可选的，源AS向UE发送目标AS的连接信息。
可选的，步骤S1313也可以是由源ES向UE发送目标AS的连接信息，或者，还可以是由源ES向5GC网元(例如，SMF或PCF)发送目标AS的连接信息，再由5GC网元向UE发送目标AS的连接信息。
S1314、可选的，UE接收目标AS的连接信息，并与目标AS建立连接。
可选的，UE可以接收的目标AS的连接信息可以来自源AS、源ES、5GC网元或其他设备，本申请实施例对此不作限定。
需要说明的是，本申请对于上述步骤S1301-S1314的先后执行顺序并不进行限定，图13仅是示例性说明。
可以理解的，本实施例提供的应用迁移的方法通过源AS向源ES发送订阅请求，从而能够在源ES确定存在目标AS时，再向源AS发送包括目标AS的连接信息的通知消息，再由源AS触发应用迁移。由于UE的PDU会话的用户面路径改变后，UE 可接入的数据网络中不一定部署了与源AS服务相同应用的AS，因此通过发送订阅请求，能够在源ES确定UE可接入的数据网络中存在与源AS服务相同应用的AS时，再通知源AS，进而发起应用迁移，因此能够减少应用迁移过程中的无效通知，降低时延。
可选的，本申请实施例还提供一种应用迁移的方法，该方法可以包括：源AS向源ES发送用于指示源AS是否支持应用切换的指示信息，源ES接收该指示信息。源ES向5GC网元订阅用户面管理事件通知或者移动性事件通知，当UE的PDU会话的用户面路径改变或者UE的位置改变时，5GC网元向源ES发送第三通知消息。源ES接收第三通知消息，并基于第一信息确定UE可接入的DN中是否存在目标AS。若指示信息指示源AS支持应用切换，那么源ES确定UE可接入的DN中存在目标AS后，源ES确定执行应用迁移，源ES可以向源AS请求源AS上的上下文，并将源AS上的上下文迁移至目标AS。
示例性的，在UE移动过程中，服务于UE的数据网络可能发生变化，CS可以更新下发给UE的数据网络的信息，因此本申请实施例还提供一种应用迁移的方法，该方法涉及在应用迁移的过程中如何更新网络信息，该方法的流程示意图如图14所示，涉及到CS、UE和PCF实体/SMF实体之间的交互，包括如下步骤：
S1401、UE向CS发送第一指示信息。
该第一指示信息用于指示CS当UE的PDU会话的用户面路径改变时，向UE发送目标DN的信息。
可选的，在本实施例中UE的PDU会话的用户面路径改变包括UE的PDU会话发生重建。在本实施例中UE的PDU会话的SSC模式可以为SSC mode3，当UE的PDU的会话发生重建时，UE接入的数据网络可以相应的进行切换。
可选的，在本实施例中CS可以是图2中的ECS，DN可以是图2中的EDN。
S1402、CS接收第一指示信息。
S1403、CS向PCF实体或SMF实体订阅用户面管理事件通知。
该用户面管理事件通知用于当UE的PDU会话的用户面路径改变时通知CS。
S1404、PCF实体或SMF实体向CS发送第五通知消息。
该第五通知消息用于通知CS，UE的PDU会话的用户面路径改变。即当PCF实体或SMF实体确定UE的PDU会话的用户面路径改变时，PCF实体或SMF实体向CS发送该第五通知消息。可选的，该第五通知消息中可以包括第一信息。关于第一信息的描述可以参考前述实施例，在此不再赘述。
可以理解的，步骤S1404中的第五通知消息是响应步骤S1403中CS向PCF实体或SMF实体订阅的用户面管理事件通知的。
S1405、CS接收第五通知消息。
S1406、CS基于第一信息，确定目标DN。
示例性的，CS可以基于第五通知消息中包括的第一信息，确定目标DN。例如，第一信息为UE的DNAI。
可选的，CS也可以基于第五通知消息中包括的第一信息，向PCF实体或SMF实体查询UPF的信息，并基于该UPF的信息确定目标DN。例如，CS可以基于第五通 知消息中包括的UE的IP地址，向PCF实体或SMF实体查询DNAI，并基于该DNAI确定目标DN。
S1407、CS向UE发送目标DN的信息。
S1408、UE接收目标DN的信息，并与目标DN建立连接。
需要说明的是，本申请对于上述步骤S1401-S1408的先后执行顺序并不进行限定，图14仅是示例性说明。
本实施例通过UE指示CS当UE的PDU会话重建时，向UE发送目标DN的信息，从而能够在UE的PDU会话发生重建时，CS向UE发送目标DN的信息，以使得UE可以接入该目标DN。
示例性的，本申请实施例还提供一种应用迁移的方法，该方法涉及在应用迁移的过程中如何更新网络信息，该方法的流程示意图如图15所示，涉及到CS和UE之间的交互，包括如下步骤：
S1501、UE向CS发送第一指示信息。
该第一指示信息用于指示CS当UE的PDU会话的用户面路径改变时，向UE发送目标DN的信息。
可选的，在本实施例中UE的PDU会话的用户面路径改变包括UE的PDU会话发生重建。当UE的PDU的会话发生重建时，UE接入的数据网络可以相应的进行切换。
可选的，在本实施例中CS可以是图2中的ECS，DN可以是图2中的EDN。
可选的，在本实施例中UE的PDU会话的SSC模式可以为SSC mode3。
S1502、CS接收第一指示信息。
S1503、UE向CS发送第二指示信息。
该第二指示信息用于指示UE的PDU会话发生重建。可选的，第二指示信息中包括第一信息。
S1504、CS接收第二指示信息。
S1505、CS基于第一信息，确定目标DN。
示例性的，CS可以基于第二指示信息中包括的第一信息，确定目标DN。例如，第一信息为UE的DNAI。
可选的，当第二指示信息不包括第一信息或者第二指示信息包括的第一信息为UE的IP地址时，CS接收第二指示信息后，可以向PCF实体或SMF实体查询DNAI，并基于该DNAI确定目标DN。
S1506、CS向UE发送目标DN的信息。
S1507、UE接收目标DN的信息，并与目标DN建立连接。
需要说明的是，本申请对于上述步骤S1501-S1507的先后执行顺序并不进行限定，图15仅是示例性说明。
可以理解的，图14所示的实施例与图15所示的实施例的区别在于，图14所示的实施例是通过CS向PCF实体或SMF实体订阅用户面管理事件通知获知UE的PDU会话发生重建的，而图15所示的实施例是UE重建会话后向CS发送指示信息告知CS该UE的PDU会话发送重建了。也就是说，图14所示的实施例和图15所示的实施例的区别是CS获知UE的PDU会话发送重建的方式不同。
本实施例通过UE指示CS当UE的PDU会话重建时，向UE发送目标DN的信息，并在UE的PDU会话重建时通知CS，从而CS可以确定目标DN并向UE发送该目标DN的信息，以使得UE可以接入该目标DN。
本申请实施例提供的应用迁移的方法的流程示意图如图16所示，涉及到目标ES、CS、5GC网元(例如SMF、UPF或其它能分配IP的实体)和UE(可以包含AC，EEC，OS等)之间的交互，包括如下步骤：
S1601、5GC网元向UE发送第一信息。
示例性的，该5GC网元可以为SMF实体、UPF实体或其它能分配IP的网元。
在一种实现方式中，UE建立的会话的SSC mode为mode 3，当UE重建一个新会话或创建multi-homed会话时，UE从5GC网元获取一个新的IP地址，该新的IP地址可以为UE重建PDU会话后的IP地址或使用创建multi-homed会话机制实现SSC mode 3时，新插入的锚点UPF对应的UE的IP地址。该新的IP地址可能是SMF实体分配的，也可能是UPF实体分配，还可以是DN-AAA分配的，也可以是其它实体分配的，本申请对此不做限定。可选的，5GC网元(比如SMF网元)还可以向UE发送新会话的锚点UPF或multi-homed会话新插入的锚点UPF对应的DNAI。
可以理解的，关于第一信息的具体描述可以参考前述实施例，在此不再赘述。
S1602、UE接收第一信息。
示例性的，步骤S1602可能由UE中的EEC模块、UE中的AC模块或UE中的OS接收第一信息，本申请对此不做限定。
S1603、UE向CS发送第一信息。
示例性的，该第一信息可以包含在Service provisioning Request中。
可选的，在一种实现方式中，UE中的EEC模块可以向CS发送第一信息。
S1604、CS接收第一信息。
S1605、CS基于第一信息确定目标ES。
在第一种实现方式中，UE向CS发送新的IP地址。CS若配置了IP地址(段)与目标ES或DN的映射关系，CS可以确定目标ES，其中目标ES服务目标DN。
在第二种实现方式中，UE向CS发送新的IP地址，CS可以向5GC网元发送请求，请求中包含新的IP地址，该请求用于基于UE的IP地址获取UE的新会话的锚点UPF或multi-homed会话新插入的锚点UPF对应的DNAI。CS若配置了DNAI与目标ES或DN的映射关系，CS可以确定目标ES。
在第三种实现方式中，UE向CS发送新会话的锚点UPF或multi-homed会话新插入的锚点UPF对应的DNAI。CS若配置了DNAI与目标ES或DN的映射关系，CS可以确定目标ES，与第二种实现方式相比，可以省去向5GC网元查询DNAI的过程。
S1606、CS向UE发送目标ES的连接信息。
可选的，步骤S1605中CS也可以向UE发送目标ES的连接信息。该目标ES的连接信息包括目标ES的地址信息，该目标ES的连接信息可以为目标ES的IP地址、目标ES的URI、目标ES的URL、目标ES的端点(end point)等信息。
S1607、UE接收目标ES的连接信息。
可选的，步骤S1606中可以由UE中的EEC模块接收该目标ES的连接信息。
S1608、UE向目标ES发送第二应用发现请求。
该第二应用发现请求用于请求获取目标AS。
在一种实现方式中，UE的EEC模块向目标ES发送第二应用发现请求。可选的，第二应用发现请求中包含新的IP地址。
可选的，第二应用发现请求中包括源AS的应用标识。
可选的，第二应用发现请求中包括第一信息。
S1609、目标ES接收第二应用发现请求。
S1610、目标ES确定目标AS。
可选的，目标ES可以基于第一信息确定目标AS。目标ES基于第一信息确定目标AS具体可参考S602中确定目标AS的过程，此处不作赘述。可以理解的，目标ES基于第一信息确定的目标AS与源AS的应用标识相同。
S1611、可选的，目标ES确定触发应用迁移。
在一种实现方式中，目标ES基于收到新的IP地址和第二应用发现请求确定需要做应用迁移，目标ES可以将目标AS的连接信息发送给源ES或源AS。
可选的，若目标ES确定触发应用迁移，目标ES可以向UE发送目标AS的连接信息。
S1612、目标ES向UE发送目标AS的连接信息。
可选的，目标ES也可以向UE发送目标AS的连接信息。该目标AS的连接信息包括目标AS的地址信息，该目标AS的连接信息可以为IP地址、URI、URL、端点(end point)等信息。
S1613、UE接收目标AS的连接信息。
在一种实现方式中，UE的EEC模块接收目标AS的连接信息。
S1614、可选的，UE确定触发应用迁移。
在一种实现方式中，UE的EEC模块在接收到目标AS的连接信息后确定需要做应用迁移。
在一种实现方式中，源AS将应用上下文直接发送给目标AS。
在另一种实现方式中，源AS将应用上下文发送给源ES，源ES将上下文发送给目标ES，再由目标ES发送给目标AS。
可以理解的，本申请实施例可以由目标ES确定触发应用迁移，也可以由UE确定触发应用迁移，还可以由其他网络设备确定触发应用迁移，本申请实施例对此不作限定。
需要说明的是，本申请对于上述步骤S1601-S1614的先后执行顺序并不进行限定，图16仅是示例性说明。
可以理解的，本申请实施例提供的应用迁移的方法，对于SSC mode 3会话，在UE的PDU会话重建时，UE接收来自5GC网元的第一信息，UE将第一信息发送给CS，CS基于第一信息确定获取目标ES，进而UE可以从目标ES获取目标AS连接信息。该方法基于UE的PDU会话的用户面路径改变后UE的位置信息确定的目标ES较为准确，基于该目标ES确定的目标AS较准确，因此UE访问该目标AS时的时延较小。而且该方法是由目标ES或EEC触发目标AS的重选和应用迁移，对UE中的 AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
本申请实施例提供的应用迁移的方法的流程示意图如图17所示，涉及到源ES、目标ES、CS、5GC网元(例如SMF、UPF或其它能分配IP的实体)和UE(可以包含AC，EEC，OS等)之间的交互，包括如下步骤：
S1701、5GC网元向UE发送第一信息。
可以理解的，关于第一信息的具体描述可以参考前述实施例，在此不再赘述。
S1702、UE接收第一信息。
示例性的，步骤S1702可能由UE中的EEC模块、UE中的AC模块或UE中的OS接收第一信息，本申请对此不做限定。
可以理解的，上述步骤S1701-S1702的具体实现方式可以参考步骤S1601-S1602的实现方式，在此不再赘述。
S1703、UE向源ES发送第一信息。
可选的，在一种实现方式中，UE中的EEC模块可以向源ES发送第一信息。
可选的，该第一信息可以包括在请求消息中，该请求消息可以为应用服务器发现请求消息。
S1704、源ES接收第一信息。
S1705、源ES向CS发送第一信息。
可选的，源ES向CS发送的第一信息可以包括在请求消息中，该请求消息用于从CS获取目标ES。
S1706、CS接收第一信息。
S1707、CS基于第一信息确定目标ES。
可以理解的，步骤S1707中CS基于第一信息确定目标ES的具体实现方式可以参考步骤S1605的实现方式，在此不再赘述。
S1708、CS向源ES发送目标ES的连接信息。
S1709、源ES接收目标ES的连接信息。
S1710、源ES向目标ES发送第一应用发现请求。
该第一应用发现请求用于请求获取目标AS。
可选的，第一应用发现请求中包括第一信息。该第一应用发现请求用于从目标ES获取目标AS。
可选的，第一应用发现请求中包括源AS的应用标识。
S1711、目标ES接收第一应用发现请求。
S1712、目标ES确定目标AS。
可选的，目标ES可以基于第一信息确定目标AS。例如，目标ES可以基于第一信息与应用标识信息，确定目标ES。目标ES基于第一信息确定目标AS具体可参考S602中确定目标AS的过程，此处不作赘述。
可选的，目标ES也可以仅基于应用标识信息，确定目标ES。该应用标识信息为源AS对应的应用的标识信息。
S1713、目标ES向源ES发送目标AS的连接信息。
可选的，目标ES也可以直接向UE发送目标AS的连接信息，或者，目标ES也 可以向CS发送目标AS的连接信息，由CS向UE发送目标AS的连接信息。
S1714、源ES接收目标AS的连接信息。
S1715、源ES向UE发送目标AS的连接信息。
S1716、UE接收目标AS的连接信息。
在一种实现方式中，UE的EEC模块接收目标AS的连接信息。
S1717、可选的，目标ES确定需要做应用迁移。
在一种实现方式中，目标ES基于收到新的IP地址和第一应用发现请求确定需要做应用迁移，然后目标ES将目标AS的连接信息发送给源ES或源AS。
S1718、可选的，UE确定需要做应用迁移。
在一种实现方式中，UE的EEC模块在接收到目标AS的连接信息后确定需要做应用迁移。
在一种实现方式中，源AS将应用上下文直接发送给目标AS。
在另一种实现方式中，源AS将应用上下文发送给源ES，源ES将上下文发送给目标ES，再由目标ES发送给目标AS。
需要说明的是，本申请对于上述步骤S1701-S1718的先后执行顺序并不进行限定，图17仅是示例性说明。
可以理解的，本申请实施例提供的应用迁移的方法，对于SSC mode 3会话，在UE的PDU会话重建时，UE接收来自5GC网元的第一信息，UE将第一信息发送给源ES，源ES将第一信息发送给CS，CS基于第一信息确定目标ES，进而源ES可以从目标ES获取目标AS的连接信息，并向UE发送该目标AS的连接信息。该方法基于UE的PDU会话的用户面路径改变后UE的位置信息确定的目标ES较为准确，基于该目标ES确定的目标AS较准确，因此UE访问该目标AS时的时延较小。而且该方法是由目标ES或EEC触发目标AS的重选和应用迁移，对UE中的AC并无改动，因此，不要求AC理解网络逻辑，能够简化AC的设计。
上述主要从方法步骤的角度对本申请实施例提供的方案进行了介绍。可以理解的是，计算机为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件和计算机软件的结合形式来实现。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对计算机进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图18示出了一种通信设备1800的结构示意图，该通信设备可以为上述源AS，还可以为上述源AS内的芯片，通信设备1800可以用于实现上述任一实施例涉及源AS的方法和功能。
该通信设备1800包括：处理单元1801和收发单元1802。示例性的，收发单元1802 可用于支持源AS与上述实施例中的源ES、PCF实体/SMF实体或UE之间进行通信。处理单元1801用于对上述源AS的动作进行控制管理，用于执行上述实施例中由源AS进行的处理，可选的，若通信设备1800包括存储单元，则处理单元1801还可以执行存储在存储器中的程序或指令，以使得通信设备1800实现上述任一实施例所涉及的方法和功能。
示例性的，上述处理单元1801可以用于执行例如图6中的步骤S602-S603，或，图7中的步骤S704和S705，或，图9中的步骤S907和S908，或，图10中的步骤S1009和S1010，或，图12中的步骤S1212中触发应用迁移，或，图13中的步骤S1307和S1312，和/或用于本文所描述的技术的其它过程。收发单元1802可以用于执行例如图6中的步骤S601，或，图7中的步骤S701、S703和S706，或，图9中的步骤S901、S906和S909，或，图10中的步骤S1001、S1008和S1011，或，图12中的步骤S1212中接收目标AS的连接信息，或，图13中的步骤S1301、S1306、S1308、S1311和S1313，和/或用于本文所描述的技术的其它过程。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
示例性的，该通信设备1800可以为图5所示的通信装置，处理单元1801可以为图5中的处理器501、收发单元1802可以为图5中的收发器503。可选的，该通信设备1800还可以包括存储器，该存储器用于存储通信设备1800执行上文所提供的任一应用迁移的方法所对应的程序代码和数据。上述图5涉及的各部件的所有相关内容的描述均可以援引到该通信设备1800对应部件的功能描述，在此不再赘述。
图19示出了一种通信设备1900的结构示意图，该通信设备可以为上述源ES，还可以为上述源ES内的芯片，通信设备1900可以用于实现上述任一实施例涉及源ES的方法和功能。
该通信设备1900包括：处理单元1901和收发单元1902。示例性的，收发单元1902可用于支持源ES与上述实施例中的源AS、PCF实体/SMF实体或UE之间进行通信。处理单元1901用于对上述源ES的动作进行控制管理，用于执行上述实施例中由源ES进行的处理，可选的，若通信设备1900包括存储单元，则处理单元1901还可以执行存储在存储器中的程序或指令，以使得通信设备1900实现上述任一实施例所涉及的方法和功能。
示例性的，上述处理单元1901可以用于执行例如图6中的步骤S602，或，图8中的步骤S804和S805，或，图11中的步骤S1106和S1107，和/或用于本文所描述的技术的其它过程。收发单元1902可以用于执行例如图6中的步骤S601和S603，或，图8中的步骤S801、S803和S806，或，图9中的步骤S902、S904和S905，或，图10中的步骤S1006和S1007，或，图11中的步骤S1105和S1108，或，图13中的步骤S1302、S1304和S1305，或，图17中的步骤S1704、S1705、S1709、S1710、S1714和S1715，和/或用于本文所描述的技术的其它过程。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
示例性的，该通信设备1900可以为图5所示的通信装置，处理单元1901可以为图5中的处理器501、收发单元1902可以为图5中的收发器503。可选的，该通信设备1900还可以包括存储器，该存储器用于存储通信设备1900执行上文所提供的任一 应用迁移的方法所对应的程序代码和数据。上述图5涉及的各部件的所有相关内容的描述均可以援引到该通信设备1900对应部件的功能描述，在此不再赘述。
图20示出了一种通信设备2000的结构示意图，该通信设备可以为上述UE，还可以为上述UE内的芯片，通信设备2000可以用于实现上述任一实施例涉及UE的方法和功能。
该通信设备2000包括：处理单元2001和收发单元2002。示例性的，收发单元2002可用于支持UE与上述实施例中的源ES、源AS、目标ES之间进行通信。处理单元2001用于对上述UE的动作进行控制管理，用于执行上述实施例中由UE进行的处理，可选的，若通信设备2000包括存储单元，则处理单元2001还可以执行存储在存储器中的程序或指令，以使得通信设备2000实现上述任一实施例所涉及的方法和功能。
示例性的，上述处理单元2001可以用于执行例如图6至图13中的与目标AS建立连接，或，执行图14或图15中的与目标DN建立连接，或，执行图12中步骤S1204、S1208中的基于第一消息从目标ES管理的一个或多个AS中确定目标AS，或，图16中的步骤S1614，或，图17中的步骤S1708，和/或用于本文所描述的技术的其它过程。收发单元2002可以用于执行例如接收目标AS的连接信息，或，图10中的步骤S1005，或，图11中的步骤S1104，或，图12中的S1201-S1203、步骤S1205、S1208中的接收第一消息、S1209和S1211，或，图14中的步骤S1401、S1408中的接收目标DN的信息，或，图15中的步骤S1501、S1503、S1507中的接收目标DN的信息，或，图16中的步骤S1602、S1603、S1607、S1608和S1612，或，图17中的步骤S1702、S1703和S1716，和/或用于本文所描述的技术的其它过程。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
示例性的，该通信设备2000可以为图5所示的通信装置，处理单元2001可以为图5中的处理器501、收发单元2002可以为图5中的收发器503。可选的，该通信设备2000还可以包括存储器，该存储器用于存储通信设备2000执行上文所提供的任一应用迁移的方法所对应的程序代码和数据。上述图5涉及的各部件的所有相关内容的描述均可以援引到该通信设备2000对应部件的功能描述，在此不再赘述。
图21示出了一种通信设备2100的结构示意图，该通信设备可以为上述CS，还可以为上述CS内的芯片，通信设备2100可以用于实现上述任一实施例涉及CS的方法和功能。
该通信设备2100包括：处理单元2101和收发单元2102。示例性的，收发单元2102可用于支持CS与上述实施例中的PCF实体、SMF实体或UE之间进行通信。处理单元2101用于对上述CS的动作进行控制管理，用于执行上述实施例中由CS进行的处理，可选的，若通信设备2100包括存储单元，则处理单元2101还可以执行存储在存储器中的程序或指令，以使得通信设备2100实现上述任一实施例所涉及的方法和功能。
示例性的，上述处理单元2101可以用于执行例如图14中步骤S1406，或，图15中步骤S1505，或，图16中的步骤S1605，或，图17中的步骤S1707，和/或用于本文所描述的技术的其它过程。收发单元2102可以用于执行例如图14中的步骤S1402、S1403、S1405和S1407，或，图15中的步骤S1502、S1504和S1506，或，图16中的 步骤S1604和S1606，或，图17中的步骤S1706和S1708，和/或用于本文所描述的技术的其它过程。其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
示例性的，该通信设备2100可以为图5所示的通信装置，处理单元2101可以为图5中的处理器501、收发单元2102可以为图5中的收发器503。可选的，该通信设备2100还可以包括存储器，该存储器用于存储通信设备2100执行上文所提供的任一应用迁移的方法所对应的程序代码和数据。上述图5涉及的各部件的所有相关内容的描述均可以援引到该通信设备2100对应部件的功能描述，在此不再赘述。
示例性的，本申请实施例还提供一种应用迁移的装置，该应用迁移的装置包括处理器，该处理器用于执行计算机执行指令，以支持该应用迁移的装置实现图6至图17中任一实施例中的应用迁移的方法。可选的，该应用迁移的装置还可以包括收发器以及存储器，收发器，用于收发信息，或者用于与其他网元通信；存储器，用于存储计算机执行指令。
本申请实施例还提供一种计算机存储介质，该计算机存储介质中存储有计算机程序代码，当上述处理器执行该计算机程序代码时，电子设备执行图6至图17中任一实施例中的应用迁移的方法。
本申请实施例还提供一种计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行图6至图17中任一实施例中的应用迁移的方法。
本申请实施例还提供一种通信系统，该通信系统包括源应用服务器AS和源使能服务器ES和用户设备UE，其中，所述源AS向所述源ES订阅用户面管理事件通知，所述用户面管理事件通知用于当所述UE的协议数据单元PDU会话的用户面路径改变时通知所述源AS；所述源AS为所述PDU会话的用户面路径改变前所述UE访问的AS；所述源ES获取第一信息，所述第一信息为所述UE的PDU会话的用户面路径改变后所述UE的位置信息；所述源ES向所述源AS发送第二通知消息，所述第二通知消息用于通知所述源AS所述UE的PDU会话的用户面路径改变，所述第二通知消息中包括第一信息；所述源AS基于所述第一信息，确定目标AS，并触发应用迁移，所述应用迁移是指将所述UE从所述源AS迁移至所述目标AS；所述源AS向所述UE发送目标AS的连接信息；所述UE接收所述目标AS的连接信息，并与所述目标AS建立连接。
本申请实施例还提供一种芯片系统，该芯片系统包括处理器和存储器，存储器中存储有指令；指令被处理器执行时，实现上述图6至图17中任一实施例中的应用迁移的方法。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、可擦除可编程只读存储器(erasable programmable ROM，EPROM)、电可擦可编程只读存储器(electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储 介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (88)

  1. 一种应用迁移的方法，其特征在于，所述方法包括：
    源应用功能AF获取第一信息，所述第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后所述UE的位置信息；
    所述源AF基于所述第一信息，确定目标应用服务器AS。
  2. 根据权利要求1所述的方法，其特征在于，所述目标AS与源AS服务相同的应用，所述源AS为所述UE的PDU会话的用户面路径改变前所述UE访问的AS。
  3. 根据权利要求1或2所述的方法，其特征在于，所述UE的位置信息包括所述UE的网络协议IP地址、所述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、所述UE的跟踪区域标识TAI、所述UE的小区标识、所述UE的无线接入网标识或者所述UE的地理位置信息中的至少一种。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述源AF基于所述第一信息，确定目标AS，包括：
    所述源AF基于所述第一信息，确定所述UE的PDU会话的用户面路径改变后的用户面功能UPF实体的信息或数据网络的信息；
    所述源AF基于所述UPF实体的信息或数据网络的信息，确定所述目标AS。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述源AF为所述源AS。
  6. 根据权利要求5所述的方法，其特征在于，所述源AF获取所述第一信息，包括：
    所述源AS接收来自策略控制功能PCF实体或会话管理功能SMF实体的第一通知消息，所述第一通知消息用于通知所述源AS所述UE的PDU会话的用户面路径改变，所述第一通知消息中包括所述第一信息。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述源AS向所述PCF实体或所述SMF实体订阅用户面管理事件通知，所述用户面管理事件通知用于当所述UE的PDU会话的用户面路径改变时通知所述源AS。
  8. 根据权利要求5所述的方法，其特征在于，所述源AF获取所述第一信息，包括：
    所述源AS接收来自源使能服务器ES的第二通知消息，所述第二通知消息用于通知所述源AS所述UE的PDU会话的用户面路径改变，所述第二通知消息中包括所述第一信息。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述源AS向所述源ES订阅用户面管理事件通知，所述用户面管理事件通知用于当所述UE的PDU会话的用户面路径改变时通知所述源AS。
  10. 根据权利要求5-9中任一项所述的方法，其特征在于，所述方法还包括：
    所述源AS向所述UE发送所述目标AS的连接信息。
  11. 根据权利要求1-4中任一项所述的方法，其特征在于，所述源AF为源ES。
  12. 根据权利要求11所述的方法，其特征在于，所述源AF获取所述第一信息，包括：
    所述源ES接收来自PCF实体或SMF实体的第三通知消息，所述第三通知消息用 于通知所述源ES所述UE的PDU会话的用户面路径改变，所述第三通知消息中包括所述第一信息。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述源ES向所述PCF实体或所述SMF实体订阅用户面管理事件通知，所述用户面管理事件通知用于当所述UE的PDU会话的用户面路径改变时通知所述源ES。
  14. 根据权利要求11所述的方法，其特征在于，所述源AF获取所述第一信息，包括：
    所述源ES接收来自所述UE的边缘使能客户端EEC发送的第四通知消息，所述第四通知消息用于通知所述源ES所述UE的PDU会话重建，所述第四通知消息中包括所述第一信息。
  15. 根据权利要求11-14中任一项所述的方法，其特征在于，所述方法还包括：
    所述源ES向所述UE发送所述目标AS的连接信息。
  16. 根据权利要求1-4中任一项所述的方法，其特征在于，所述源AF为配置服务器CS，所述方法还包括：
    所述CS接收来所述UE的第一指示信息，所述第一指示信息用于指示所述CS当所述UE的PDU会话的用户面路径改变时，向所述UE发送目标数据网络DN的信息；
    所述CS基于所述第一信息，确定所述目标DN；
    所述CS向所述UE发送所述目标DN的信息。
  17. 根据权利要求16所述的方法，其特征在于，所述CS获取第一信息包括：
    所述CS接收来自所述UE的第二指示信息，所述第二指示信息用于指示所述UE的PDU会话发生重建，所述第二指示信息中包括所述第一信息。
  18. 根据权利要求16所述的方法，其特征在于，所述CS获取第一信息包括：
    所述CS接收来自策略控制功能PCF实体或会话管理功能SMF实体的第五通知消息，所述第五通知消息用于通知所述CS所述UE的PDU会话的用户面路径改变，所述第五通知消息中包括所述第一信息。
  19. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述CS向所述PCF实体或所述SMF实体订阅用户面管理事件通知，所述用户面管理事件通知用于当所述UE的PDU会话的用户面路径改变时通知所述CS。
  20. 根据权利要求1-19中任一项所述的方法，其特征在于，所述UE的PDU会话的用户面路径改变包括所述UE的PDU会话锚点改变，所述UE的PDU会话的会话和服务连续SSC模式为模式3。
  21. 一种应用迁移的方法，其特征在于，所述方法包括：
    源使能服务器ES获取第一信息，所述第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后所述UE的位置信息；
    所述源ES向源应用服务器AS发送第二通知消息，所述第二通知消息用于通知所述源AS所述UE的PDU会话的用户面路径改变，所述源AS为所述UE的PDU会话的用户面路径改变前所述UE访问的AS。
  22. 根据权利要求21所述的方法，其特征在于，所述UE的位置信息包括所述UE的网络协议IP地址、所述UE的PDU会话的用户面路径对应的数据网络接入标识 DNAI、所述UE的跟踪区域标识TAI、所述UE的小区标识、所述UE的无线接入网标识或者所述UE的地理位置信息中的至少一种。
  23. 根据权利要求21或22所述的方法，其特征在于，所述方法还包括：
    所述源ES接收来自所述源AS订阅的用户面管理事件通知，所述用户面管理事件通知用于当所述UE的PDU会话的用户面路径改变时通知所述源AS。
  24. 根据权利要求21-23中任一项所述的方法，其特征在于，所述源ES获取第一信息包括：
    所述源ES接收来自所述UE的边缘使能客户端EEC发送的第四通知消息，所述第四通知消息用于通知所述源ES所述UE的PDU会话重建，所述第四通知消息中包括所述第一信息。
  25. 根据权利要求20-23中任一项所述的方法，其特征在于，所述UE的PDU会话的用户面路径改变包括所述UE的PDU会话锚点改变，所述UE的PDU会话的会话和服务连续SSC模式为模式3。
  26. 一种应用迁移的方法，其特征在于，所述方法包括:
    用户设备UE的边缘使能客户端EEC向所述UE的操作系统OS订阅会话重建事件通知，所述会话重建事件通知用于当所述UE的协议数据单元PDU会话重建时通知所述EEC；
    所述EEC接收来自所述OS的第六通知消息，所述第六通知消息用于通知所述EEC所述UE的PDU会话重建，所述第六通知消息中包括第一信息，所述第一信息为所述PDU会话重建后所述UE的位置信息。
  27. 根据权利要求26所述的方法，其特征在于，所述UE的位置信息包括所述UE的网络协议IP地址、所述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、所述UE的跟踪区域标识TAI、所述UE的小区标识、所述UE的无线接入网标识或者所述UE的地理位置信息中的至少一种。
  28. 根据权利要求26或27所述的方法，其特征在于，所述方法还包括：
    所述EEC向源使能服务器ES发送第四通知消息，所述第四通知消息用于通知所述源ES所述UE的PDU会话重建，所述第四通知消息中包括所述第一信息。
  29. 根据权利要求26或27所述的方法，其特征在于，所述方法还包括：
    所述EEC基于所述第一信息，确定目标应用服务器AS；所述目标AS与源AS服务相同的应用，所述源AS为所述UE的PDU会话重建前所述UE访问的AS。
  30. 根据权利要求29所述的方法，其特征在于，所述EEC基于所述第一信息，确定目标应用服务器AS，包括：
    所述EEC基于所述第一信息，确定目标ES；
    所述EEC向所述目标ES发送发现请求；
    所述EEC接收来自所述目标ES的第一消息，所述第一消息中包括所述目标ES管理的一个或多个AS的连接信息，所述目标ES管理的一个或多个AS与所述源AS服务相同的应用；
    所述EEC从所述目标ES管理的一个或多个AS中确定所述目标AS。
  31. 根据权利要求29或30所述的方法，其特征在于，所述方法还包括：
    所述EEC向所述源AS或源ES发送所述目标AS的连接信息，以使得所述源AS或源ES将所述UE的上下文从所述源AS迁移至所述目标AS。
  32. 根据权利要求25-30中任一项所述的方法，其特征在于，所述UE的PDU会话的用户面路径改变包括所述UE的PDU会话锚点改变，所述UE的PDU会话的会话和服务连续SSC模式为模式3。
  33. 一种应用迁移的方法，其特征在于，所述方法包括：
    源应用服务器AS向源使能服务器ES发送订阅请求，所述订阅请求用于当所述源ES确定存在目标AS时通知所述源AS；
    所述源AS接收来自所述源ES的第七通知消息，所述第七通知消息中包括所述目标AS的连接信息；
    所述源AS确定将用户设备UE的上下文从所述源AS迁移至所述目标AS。
  34. 根据权利要求33所述的方法，其特征在于，所述方法还包括：
    所述源AS向所述源ES发送第四指示信息，所述第四指示信息用于指示所述源ES将所述UE的上下文从所述源AS迁移至所述目标AS。
  35. 根据权利要求33或34所述的方法，其特征在于，所述目标AS和所述源AS服务相同的应用。
  36. 根据权利要求33-35中任一项所述的方法，其特征在于，所述方法还包括：
    所述源AS向所述目标AS发送应用切换请求消息，所述应用切换请求消息用于将所述源AS上的上下文迁移至所述目标AS。
  37. 根据权利要求36所述的方法，其特征在于，所述方法还包括：
    所述源AS接收来自所述目标AS的应用切换响应消息，所述应用切换响应消息中包括第三指示信息，所述第三指示信息用于指示所述目标AS是否同意应用切换；
    相应的，所述源AS确定将所述UE的上下文从所述源AS迁移至所述目标AS，包括：若所述第三指示信息指示所述目标AS同意应用切换，所述源AS确定将所述UE的上下文从所述源AS迁移至所述目标AS。
  38. 根据权利要求37所述的方法，其特征在于，所述源AS确定将所述UE的上下文从所述源AS迁移至所述目标AS，包括：
    若所述第三指示信息指示所述目标AS同意应用切换，所述源AS确定将所述UE的上下文从所述源AS迁移至所述目标AS。
  39. 根据权利要求33-38中任一项所述的方法，其特征在于，所述方法还包括：
    所述源AS向源ES发送第五指示信息，所述第五指示信息用于指示源AS是否支持应用切换。
  40. 根据权利要求32-39中任一项所述的方法，其特征在于，所述方法还包括：
    所述源AS向源ES发送第七指示信息，所述第七指示信息用于指示应用切换时需要保持业务连续性。
  41. 一种应用迁移的方法，其特征在于，所述方法包括：
    源使能服务器ES接收来自源应用服务器AS的订阅请求，所述订阅请求用于当所述源ES确定存在目标AS时通知所述源AS；
    所述源ES获取第一信息，所述第一信息为所述UE的协议数据单元PDU会话的 用户面路径改变后所述UE的位置信息；
    所述源ES基于所述第一信息，确定所述目标AS。
  42. 根据权利要求41所述的方法，其特征在于，所述方法还包括：
    所述源ES向所述源AS发送第七通知消息，所述第七通知消息用于指示存在目标AS，所述第七通知消息中包括所述目标AS的连接信息。
  43. 根据权利要求41或42所述的方法，其特征在于，所述UE的位置信息包括所述UE的IP地址、所述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、所述UE的跟踪区域标识TAI、所述UE的小区标识、所述UE的无线接入网标识或者所述UE的地理位置信息中的至少一种。
  44. 根据权利要求41-43中任一项所述的方法，其特征在于，所述目标AS和所述源AS服务相同的应用。
  45. 根据权利要求40-44中任一项所述的方法，其特征在于，所述源ES获取第一信息，包括：
    所述源ES接收来自策略控制功能PCF实体或会话管理功能SMF实体的第三通知消息，所述第三通知消息用于通知所述源ES所述UE的PDU会话的用户面路径改变，所述第三通知消息中包括所述第一信息。
  46. 根据权利要求45所述的方法，其特征在于，所述方法还包括：
    所述源ES向所述PCF实体或所述SMF实体订阅用户面管理事件通知，所述用户面管理事件通知用于当所述UE的PDU会话的用户面路径改变时通知所述源ES。
  47. 根据权利要求40-46中任一项所述的方法，其特征在于，所述订阅请求中包括所述UE的PDU会话的信息；所述UE的PDU会话的信息包括所述UE的网络协议IP地址、数据网络名称DNN、或单网络切片选择辅助信息S-NSSAI中的至少一种。
  48. 根据权利要求47所述的方法，其特征在于，所述方法还包括：
    所述源ES根据所述UE的PDU会话的信息，确定策略控制功能PCF实体或会话管理功能SMF实体。
  49. 根据权利要求40-48中任一项所述的方法，其特征在于，所述订阅请求中包括应用标识信息，所述源ES基于所述第一信息，确定所述目标AS，包括：
    所述源ES基于所述第一信息和所述应用标识信息，确定所述目标AS。
  50. 根据权利要求40-49中任一项所述的方法，其特征在于，所述方法还包括：
    所述源ES向SMF发送第六指示信息，所述第六指示信息用于指示所述源AS是否支持应用切换。
  51. 根据权利要求40-50中任一项所述的方法，其特征在于，所述方法还包括：
    所述源ES接收来自源AS的第七指示信息，所述第七指示信息用于指示应用切换时需要保持业务连续性。
  52. 根据权利要求51所述的方法，其特征在于，所述方法还包括：
    所述源ES向SMF或PCF发送第八指示信息，所述第八指示信息用于指示应用切换时需要保持业务连续性。
  53. 根据权利要求40-52中任一项所述的方法，其特征在于，所述方法还包括：
    所述源ES向SMF或PCF发送所述目标AS的连接信息。
  54. 一种应用迁移的方法，其特征在于，所述方法包括：
    配置服务器CS获取第一信息，所述第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后所述UE的位置信息；
    所述CS基于所述第一信息，确定目标使能服务器ES。
  55. 根据权利要求54所述的方法，其特征在于，所述UE的位置信息包括所述UE的网络协议IP地址、所述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、所述UE的跟踪区域标识TAI、所述UE的小区标识、所述UE的无线接入网标识或者所述UE的地理位置信息中的至少一种。
  56. 根据权利要求54或55所述的方法，其特征在于，所述CS获取所述第一信息，包括：
    所述CS接收来自所述UE的所述第一信息。
  57. 根据权利要求56所述的方法，其特征在于，所述方法还包括：
    所述CS向所述UE发送所述目标ES的连接信息。
  58. 根据权利要求54或55所述的方法，其特征在于，所述CS获取所述第一信息，包括：
    所述CS接收来自源ES的所述第一信息。
  59. 根据权利要求58所述的方法，其特征在于，所述方法还包括：
    所述CS向所述源ES发送所述目标ES的连接信息。
  60. 根据权利要求54-59中任一项所述的方法，其特征在于，所述第一信息为所述UE的PDU会话的用户面路径改变后所述UE的IP地址，所述CS基于所述第一信息，确定所述目标ES，包括：
    所述CS基于所述UE的PDU会话的用户面路径改变后所述UE的IP地址，确定所述UE的PDU会话的用户面路径改变后的DNAI；
    所述CS基于所述DNAI，确定所述目标ES。
  61. 根据权利要求54-60中任一项所述的方法，其特征在于，所述UE的PDU会话的用户面路径改变包括所述UE的PDU会话锚点改变，所述UE的PDU会话的会话和服务连续SSC模式为模式3。
  62. 一种应用迁移的方法，其特征在于，所述方法包括：
    源使能服务器ES获取第一信息，所述第一信息为用户设备UE的协议数据单元PDU会话的用户面路径改变后所述UE的位置信息；
    所述源ES向配置服务器CS发送所述第一信息；
    所述源ES接收来自所述CS的目标ES的连接信息。
  63. 根据权利要求62所述的方法，其特征在于，所述UE的位置信息包括所述UE的网络协议IP地址、所述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、所述UE的跟踪区域标识TAI、所述UE的小区标识、所述UE的无线接入网标识或者所述UE的地理位置信息中的至少一种。
  64. 根据权利要求62或63所述的方法，其特征在于，所述源ES获取所述第一信息，包括：
    所述源ES接收来自所述UE的所述第一信息。
  65. 根据权利要求62或63所述的方法，其特征在于，所述源ES获取所述第一信息，包括：
    所述源ES接收来自策略控制功能PCF实体或会话管理功能SMF实体的第三通知消息，所述第三通知消息用于通知所述源ES所述UE的PDU会话的用户面路径改变，所述第三通知消息中包括所述第一信息。
  66. 根据权利要求65所述的方法，其特征在于，所述方法还包括：
    所述源ES向所述PCF实体或所述SMF实体订阅用户面管理事件通知，所述用户面管理事件通知用于当所述UE的PDU会话的用户面路径改变时通知所述源ES。
  67. 根据权利要求62-66中任一项所述的方法，其特征在于，所述方法还包括：
    所述源ES向所述目标ES发送第一应用发现请求，所述第一应用发现请求用于请求获取目标应用服务器AS；
    所述源ES接收来自所述目标ES的目标AS的连接信息。
  68. 根据权利要求67所述的方法，其特征在于，所述目标AS与源AS服务相同的应用，所述源AS为所述UE的PDU会话的用户面路径改变前所述UE访问的AS。
  69. 根据权利要求67或68所述的方法，其特征在于，所述方法还包括：
    所述源ES向所述UE发送所述目标AS的连接信息。
  70. 一种应用迁移的方法，其特征在于，所述方法包括：
    用户设备UE接收来自会话管理功能SMF实体或用户面功能UPF实体的第一信息，所述第一信息为所述UE的协议数据单元PDU会话的用户面路径改变后所述UE的位置信息；
    所述UE向应用功能AF发送所述第一信息。
  71. 根据权利要求70所述的方法，其特征在于，所述UE的位置信息包括所述UE的网络协议IP地址、所述UE的PDU会话的用户面路径对应的数据网络接入标识DNAI、所述UE的跟踪区域标识TAI、所述UE的小区标识、所述UE的无线接入网标识或者所述UE的地理位置信息中的至少一种。
  72. 根据权利要求70或71所述的方法，其特征在于，所述AF为配置服务器CS，所述方法还包括：
    所述UE接收来自所述CS的目标使能服务器ES的连接信息。
  73. 根据权利要求72所述的方法，其特征在于，所述方法还包括：
    所述UE向所述目标ES发送第二应用发现请求，所述第二应用发现请求用于请求获取目标AS；
    所述UE接收来自所述目标ES的目标AS的连接信息。
  74. 根据权利要求70或71所述的方法，其特征在于，所述AF为源ES。
  75. 根据权利要求74所述的方法，其特征在于，所述方法还包括：
    所述UE接收来自所述源ES的目标AS的连接信息。
  76. 一种应用迁移的装置，其特征在于，所述装置包括用于执行如权利要求1-20中任一项所述的应用迁移的方法的单元或手段。
  77. 一种应用迁移的装置，其特征在于，所述装置包括用于执行如权利要求21-25中任一项所述的应用迁移的方法的单元或手段。
  78. 一种应用迁移的装置，其特征在于，所述装置包括用于执行如权利要求26-32中任一项所述的应用迁移的方法的单元或手段。
  79. 一种应用迁移的装置，其特征在于，所述装置包括用于执行如权利要求33-39中任一项所述的应用迁移的方法的单元或手段。
  80. 一种应用迁移的装置，其特征在于，所述装置包括用于执行如权利要求40-53中任一项所述的应用迁移的方法的单元或手段。
  81. 一种应用迁移的装置，其特征在于，所述装置包括用于执行如权利要求54-61中任一项所述的应用迁移的方法的单元或手段。
  82. 一种应用迁移的装置，其特征在于，所述装置包括用于执行如权利要求62-69中任一项所述的应用迁移的方法的单元或手段。
  83. 一种应用迁移的装置，其特征在于，所述装置包括用于执行如权利要求70-75中任一项所述的应用迁移的方法的单元或手段。
  84. 一种应用迁移的装置，其特征在于，所述装置包括：
    收发器，用于收发信息，或者用于与其他网元通信；
    处理器，用于执行计算机程序指令，以实现如权利要求1-75中任一项所述的应用迁移的方法。
  85. 一种通信系统，其特征在于，所述通信系统包括源应用服务器AS和源使能服务器ES，其中，
    所述源AS向所述源ES订阅用户面管理事件通知，所述用户面管理事件通知用于当用户设备UE的协议数据单元PDU会话的用户面路径改变时通知所述源AS；所述源AS为所述UE的PDU会话的用户面路径改变前所述UE访问的AS；
    所述源ES获取第一信息，所述第一信息为所述UE的PDU会话的用户面路径改变后所述UE的位置信息；
    所述源ES向所述源AS发送第二通知消息，所述第二通知消息用于通知所述源AS所述UE的PDU会话的用户面路径改变，所述第二通知消息中包括第一信息；
    所述源AS基于所述第一信息，确定目标AS，并向所述UE发送所述目标AS的连接信息。
  86. 根据权利要求85所述的通信系统，其特征在于，所述通信系统还包括所述UE；
    所述UE接收来自所述源AS的所述目标AS的连接信息；
    所述UE基于所述目标AS的连接信息与所述目标AS建立连接。
  87. 一种芯片系统，其特征在于，所述芯片系统包括处理器和存储器，所述存储器中存储有指令；所述指令被所述处理器执行时，实现如权利要求1-75中任一项所述的应用迁移的方法。
  88. 一种计算机存储介质，所述计算机存储介质中具有计算机程序代码，其特征在于，当所述计算机程序代码在处理器上运行时，使得所述处理器执行如权利要求1-75中任一项所述的应用迁移的方法。
PCT/CN2020/111536 2020-08-12 2020-08-26 一种应用迁移的方法和装置 WO2022032728A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN202080103975.0A CN116097680A (zh) 2020-08-12 2020-08-26 一种应用迁移的方法和装置
CA3189164A CA3189164A1 (en) 2020-08-12 2020-08-26 Application relocation method and apparatus
EP20949225.5A EP4187947A4 (en) 2020-08-12 2020-08-26 APPLICATION MIGRATION METHOD AND APPARATUS
AU2020463541A AU2020463541A1 (en) 2020-08-12 2020-08-26 Application migration method and apparatus
JP2023509819A JP2023537135A (ja) 2020-08-12 2020-08-26 アプリケーション移転方法および装置
US18/167,476 US20230188965A1 (en) 2020-08-12 2023-02-10 Application Relocation Method and Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2020/108751 2020-08-12
PCT/CN2020/108751 WO2022032547A1 (zh) 2020-08-12 2020-08-12 一种应用迁移的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/167,476 Continuation US20230188965A1 (en) 2020-08-12 2023-02-10 Application Relocation Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2022032728A1 true WO2022032728A1 (zh) 2022-02-17

Family

ID=80246711

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2020/108751 WO2022032547A1 (zh) 2020-08-12 2020-08-12 一种应用迁移的方法和装置
PCT/CN2020/111536 WO2022032728A1 (zh) 2020-08-12 2020-08-26 一种应用迁移的方法和装置

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/108751 WO2022032547A1 (zh) 2020-08-12 2020-08-12 一种应用迁移的方法和装置

Country Status (7)

Country Link
US (1) US20230188965A1 (zh)
EP (1) EP4187947A4 (zh)
JP (1) JP2023537135A (zh)
CN (1) CN116097680A (zh)
AU (1) AU2020463541A1 (zh)
CA (1) CA3189164A1 (zh)
WO (2) WO2022032547A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023213322A1 (zh) * 2022-05-06 2023-11-09 大唐移动通信设备有限公司 迁移边缘应用服务器的方法、装置、网元及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220312256A1 (en) * 2020-08-27 2022-09-29 Samsung Electronics Co., Ltd. Method and apparatus of supervised learning approach for reducing latency during context switchover in 5g mec
BR112023020505A2 (pt) * 2021-04-07 2023-11-21 Ericsson Telefon Ab L M Métodos em um servidor de aplicação de borda de origem, em um servidor habilitador de borda de origem e em um servidor habilitador de borda alvo, nó de rede, e, mídia de armazenamento legível por computador

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140115161A1 (en) * 2012-10-18 2014-04-24 Prashant Agarwal Method and system for migration of multi-tier virtual application across different clouds hypervisor platforms
CN108307454A (zh) * 2016-08-30 2018-07-20 中兴通讯股份有限公司 网络切换方法及装置
CN110650513A (zh) * 2018-06-26 2020-01-03 电信科学技术研究院有限公司 一种用户面路径更新的方法、装置及计算机存储介质
CN108886679B (zh) * 2016-04-05 2020-07-07 华为技术有限公司 移动协同通信方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10531420B2 (en) * 2017-01-05 2020-01-07 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
KR102387532B1 (ko) * 2017-04-27 2022-04-19 삼성전자 주식회사 5g 서비스 협상을 위한 등록 타입 추가 방법 및 장치
CN108934007B (zh) * 2017-05-25 2022-03-25 中兴通讯股份有限公司 一种upf重选的策略控制方法、pcf及smf
US20190007500A1 (en) * 2017-07-03 2019-01-03 Electronics And Telecommunications Research Institute Method for protocol data unit (pdu) session anchor relocation and 5g network registration

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140115161A1 (en) * 2012-10-18 2014-04-24 Prashant Agarwal Method and system for migration of multi-tier virtual application across different clouds hypervisor platforms
CN108886679B (zh) * 2016-04-05 2020-07-07 华为技术有限公司 移动协同通信方法及装置
CN108307454A (zh) * 2016-08-30 2018-07-20 中兴通讯股份有限公司 网络切换方法及装置
CN110650513A (zh) * 2018-06-26 2020-01-03 电信科学技术研究院有限公司 一种用户面路径更新的方法、装置及计算机存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4187947A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023213322A1 (zh) * 2022-05-06 2023-11-09 大唐移动通信设备有限公司 迁移边缘应用服务器的方法、装置、网元及存储介质

Also Published As

Publication number Publication date
CN116097680A (zh) 2023-05-09
JP2023537135A (ja) 2023-08-30
CN116097680A8 (zh) 2023-06-27
WO2022032547A1 (zh) 2022-02-17
EP4187947A1 (en) 2023-05-31
US20230188965A1 (en) 2023-06-15
EP4187947A4 (en) 2024-01-17
AU2020463541A1 (en) 2023-03-23
CA3189164A1 (en) 2022-02-17

Similar Documents

Publication Publication Date Title
WO2022032728A1 (zh) 一种应用迁移的方法和装置
AU2018366776B2 (en) Session establishing method and device
WO2019196846A1 (zh) 通信方法及装置
JP7047113B2 (ja) アプリケーションのサービスレベル合意を保証するための方法、デバイスおよびシステム
EP3796617B1 (en) Session management function entity selection method, apparatus, and system
WO2021190180A1 (zh) 时间同步方法、装置、计算机可读介质及电子设备
US9554406B2 (en) Method for device to device communication and control node using the same
US9450667B2 (en) Method for device to device communication and base station and user equipment using the same
EP4383779A1 (en) Method and apparatus for obtaining edge service
AU2019321895B2 (en) Communication method and communication device
WO2017193789A1 (zh) 一种按需为终端选择移动性管理机制的方法及装置
WO2019137125A1 (zh) 会话管理方法、设备及系统
WO2019196602A1 (zh) 通信方法、装置及系统
EP4192106A1 (en) Communication method and apparatus
WO2018233445A1 (zh) 网络系统的切换处理方法、装置及系统、存储介质
WO2018205114A1 (zh) 一种状态切换方法及装置
JP2021503857A (ja) ベアラ識別子を決定する方法及び装置、並びに記憶媒体
WO2022016558A1 (zh) 一种业务连续性事件的通知方法及装置
KR20220158018A (ko) 접속 수립 방법, 통신 장치, 및 시스템
KR20190136948A (ko) 네트워크에서 atsss 방법 및 이를 수행 네트워크 엔터티
WO2022213824A1 (zh) 一种用于传输上下文的方法和通信装置
WO2018082098A1 (zh) 一种网络状态管理方法及相关设备
WO2023174154A1 (zh) 通信方法、装置和系统
WO2022242648A1 (en) Method and apparatus for service continuity
JP7065905B2 (ja) サービスネットワークを選択するための方法およびネットワークデバイスならびに管理デバイス

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: 20949225

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023509819

Country of ref document: JP

Kind code of ref document: A

Ref document number: 3189164

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2020949225

Country of ref document: EP

Effective date: 20230223

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020463541

Country of ref document: AU

Date of ref document: 20200826

Kind code of ref document: A