WO2021190513A1 - 一种数据传输方法、装置及系统 - Google Patents

一种数据传输方法、装置及系统 Download PDF

Info

Publication number
WO2021190513A1
WO2021190513A1 PCT/CN2021/082455 CN2021082455W WO2021190513A1 WO 2021190513 A1 WO2021190513 A1 WO 2021190513A1 CN 2021082455 W CN2021082455 W CN 2021082455W WO 2021190513 A1 WO2021190513 A1 WO 2021190513A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
application
information
network device
indication information
Prior art date
Application number
PCT/CN2021/082455
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 华为技术有限公司
Publication of WO2021190513A1 publication Critical patent/WO2021190513A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • This application relates to the field of communication technology, and in particular to a data transmission method, device and system.
  • UPF User Plane Function
  • the 5G system can support the insertion of multiple session anchor points UPF on the user plane path of a Protocol Data Unit (PDU) session to support the connection to the local data network (DN), thereby This allows the terminal device to access the application in the local DN nearby.
  • UPF1 can be used as an uplink classifier (ULCL) or branching point (BP);
  • UPF2 and UPF3 can be used as PDU session anchor points ( PDU session anchor, PSA).
  • ULCL/BP uplink classifier
  • PSA1 PDU session anchor points
  • PSA2 PDU session anchor
  • ULCL/BP can distribute the uplink data packets received from the terminal equipment to PSA1 or PSA2 according to the distribution rules, and send the data packets received from PSA1 or PSA2 to the terminal equipment; PSA1 and PSA2 are respectively with different DNs Connection, DN can be located in Multi-access Edge Computing (MEC).
  • the MEC may include multiple application servers (Application Server, AS).
  • the embodiments of the present application provide a data transmission method, device, and system to solve the problem of how to ensure that data packets are not lost in the process of switching application servers.
  • the present application provides a data transmission method, the method includes: a first network device determines update information of a user plane path of a terminal device; when the first network device determines that it is the terminal device according to the update information The application server of the application service of is changed from the first application server AS to the second AS, instructing the terminal device to stop sending the uplink data of the application.
  • the method does not need to migrate the corresponding link layer state of the application, supports the change of the IP address of the terminal device, and does not require the IP address of the AS to be consistent in different MECs.
  • the method further includes: the first network device sends an application identifier of the application to the terminal device, where the application identifier is used to indicate the application that needs to switch the application server.
  • the instructing the terminal device by the first network device to stop sending the uplink data of the application includes: the first network device sends a first message to the second network device; A message includes first indication information, the first indication information is used to instruct the second network device to send second indication information to the terminal device, and the second indication information is used to instruct the terminal device to stop sending The uplink data of the application; or, the first network device sends the first message to the terminal device through the second network device; the first message includes the second indication information; or, the The first network device sends a first message to the terminal device; the first message includes the second indication information.
  • the first message further includes address information of the second AS.
  • the method further includes: the first network device instructs the terminal device to resume sending the uplink data of the application.
  • the first network device instructing the terminal device to resume sending the uplink data of the application includes: when the first network device determines that the second AS has acquired the terminal device The application layer status information of the instructs the terminal device to resume sending the uplink data of the application; the application layer status information is used to process the application information of the terminal device.
  • the instructing the terminal device to resume sending the uplink data of the application by the first network device includes: the first network device sends the second message to the second network device;
  • the second message includes third indication information, the third indication information is used for the second network device to send fourth indication information to the terminal device, and the fourth indication information is used for instructing the terminal device to resume sending The uplink data of the application; or, the first network device sends the second message to the terminal device through the second network device; the second message includes the fourth indication information or the first
  • the second message is used to instruct the terminal device to resume sending the uplink data of the application; or, the first network device sends the second message to the terminal device; the second message includes fourth instruction information; or,
  • the first network device sends a second message to the terminal device; the second message is used to instruct the terminal device to resume sending the uplink data of the application.
  • the first network device determining update information of the user plane path of the terminal device includes: the first network device is a network element that manages the first AS and the second AS When, or when the first network device is the first AS, the first network device receives the update information from the second network device; or, the first network device is the session management function SMF At this time, the first network device updates the user plane path of the terminal device and obtains the update information.
  • the method further includes: the first network device sending a fifth indication message, where the fifth indication message is used to indicate that the application cannot be migrated.
  • the first network device is an SMF
  • the method further includes: the first network device receives the first instruction information or the second instruction information, and the first network device sends The terminal device sends the second instruction information; the first network device receives the third instruction information or the fourth instruction information, and the first network device sends the fourth instruction information to the terminal device.
  • the present application also provides a communication device that has any method provided in the first aspect.
  • the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or units corresponding to the above-mentioned functions.
  • the communication device includes a processor configured to support the communication device to perform the corresponding function of the first network device in the method shown above.
  • the communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device.
  • the communication device further includes a communication interface, and the communication interface is used to support communication between the communication device and other devices.
  • the communication device includes corresponding functional modules, which are respectively used to implement the steps in the above method.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processing module and a communication module, and these functional modules can perform the corresponding functions in the above method examples.
  • these functional modules can perform the corresponding functions in the above method examples.
  • the present application provides a data transmission method, including: a terminal device receives second instruction information; the second instruction information instructs the terminal device to stop sending the uplink data of the application; the terminal device according to the The second instruction information stops sending the uplink data of the application.
  • the method does not need to migrate the corresponding link layer state of the application, supports the change of the IP address of the terminal device, and does not require the IP address of the AS to be consistent in different MECs.
  • the method further includes: the terminal device receives an application identifier of the application, where the application identifier is used to indicate the application that needs to switch the application server.
  • the method further includes: the terminal device storing the uplink data of the application.
  • the method further includes: the terminal device receives fourth indication information, where the fourth indication information is used to instruct the terminal device to resume sending the uplink data of the application; the terminal The device resumes sending the uplink data of the application according to the fourth instruction information.
  • the method further includes: the terminal device receives address information of a second application server AS; the second AS is a new AS that provides services for the application; the terminal device Establishing a connection with the second AS according to the address information of the second AS.
  • the method further includes: the terminal device sends uplink data to the second AS through the connection.
  • the present application also provides a communication device having any method provided in the third aspect.
  • the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or units corresponding to the above-mentioned functions.
  • the communication device includes: a processor configured to support the communication device to perform corresponding functions of the terminal device in the method shown above.
  • the communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device.
  • the communication device further includes a communication interface, and the communication interface is used to support communication between the communication device and other devices.
  • the communication device includes corresponding functional modules, which are respectively used to implement the steps in the above method.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processing module and a communication module, and these functional modules can perform the corresponding functions in the above method examples.
  • these functional modules can perform the corresponding functions in the above method examples.
  • the present application provides a data transmission method, including: a second network device receives first instruction information or second instruction information, where the first instruction information is used to instruct the second network device to send the terminal to the terminal.
  • the device sends second instruction information, where the second instruction information is used to instruct the terminal device to stop sending the uplink data of the application; the second network device sends the second instruction information to the terminal device.
  • the method further includes: the first network device receives address information of a second application server AS; the second AS is a new AS that provides services for the application; The second network device sends the address information of the second AS to the terminal device.
  • the method further includes: the second network device receives third instruction information or fourth instruction information; and the third instruction information is used by the second network device to report to the terminal The device sends fourth instruction information; the fourth instruction information is used to instruct the terminal device to resume sending the uplink data of the application; the second network device sends the fourth instruction information to the terminal device.
  • the method further includes: the second network device updates the user plane path of the terminal device and obtains update information; the update information is used to determine the second AS ; The second network device sends the update information to the first network device.
  • the method further includes: the second network device sends the application identifier of the application to the terminal device.
  • the method further includes: the second network device receives the application identifier of the application.
  • the present application also provides a communication device that has any method provided in the fifth aspect.
  • the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or units corresponding to the above-mentioned functions.
  • the communication device includes a processor configured to support the communication device to perform the corresponding function of the second network device in the above-mentioned method.
  • the communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device.
  • the communication device further includes a communication interface, and the communication interface is used to support communication between the communication device and other devices.
  • the communication device includes corresponding functional modules, which are respectively used to implement the steps in the above method.
  • the function can be realized by hardware, or the corresponding software can be executed by hardware.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processing module and a communication module.
  • These functional modules can perform the corresponding functions in the above method examples. For details, please refer to the description of the method provided in the fifth aspect, which will not be repeated here. .
  • the present application provides a system, including: a first network device for determining update information of a user plane path of a terminal device; an application server determined to be an application service of the terminal device according to the update information is determined by When the first application server AS is changed to the second AS, the first indication information or the second indication information is sent to the second network device; the first indication information is used by the second network device to send the second indication information to the terminal device.
  • the second indication information is used to instruct the terminal equipment to stop sending the uplink data of the application; the second network equipment is used to receive the first indication information or the second indication information; The terminal device sends the second indication information; the terminal device is configured to receive the second indication information; and stop sending the uplink data of the application according to the second indication information.
  • the present application provides a communication device that includes a processor, and when the processor executes a computer program or instruction in a memory, as provided in the first or third or fifth aspects The method is executed.
  • the present application provides a communication device, the communication device includes a processor and a memory, the memory is used to store computer programs or instructions; the processor is used to execute the computer programs or instructions stored in the memory, The method provided by the first aspect or the third aspect or the fifth aspect is executed by the communication device.
  • the present application provides a communication device, the communication device includes a processor, a memory, and a transceiver, the transceiver is used to receive signals or send signals; the memory is used to store computer programs or instructions; The processor is configured to call the computer program or instruction from the memory to execute the method provided in the first aspect or the third aspect or the fifth aspect.
  • the present application provides a communication device.
  • the communication device includes a processor and a communication interface.
  • the communication interface is configured to receive code instructions and transmit them to the processor; the processor runs the code The instructions are executed by executing the method provided in the first aspect or the third aspect or the fifth aspect.
  • this application provides a computer-readable storage medium for storing a computer program or instruction.
  • the computer reads and executes the computer program or instruction, the first aspect or The method provided by the third or fifth aspect is implemented.
  • the present application provides a computer program product including instructions.
  • the computer reads and executes the computer program product, the method provided in the first aspect, the third aspect, or the fifth aspect is realized.
  • the present application provides a chip including a processor coupled to a memory and configured to execute a computer program or instruction stored in the memory.
  • the processor executes the computer program or instruction At this time, the method provided by the first aspect or the third aspect or the fifth aspect is realized.
  • Figure 1 is a schematic diagram of a 5G network architecture in the prior art
  • FIG. 2 is a schematic diagram of a 5G network architecture applicable to an embodiment of the present application
  • FIG. 3 is a schematic diagram of another system architecture applicable to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a data transmission process provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram of a data transmission process provided by an embodiment of this application.
  • FIG. 6 is a schematic diagram of a data transmission process provided by an embodiment of this application.
  • FIG. 7 is a schematic diagram of a data transmission process provided by an embodiment of this application.
  • FIG. 8 is a schematic diagram of a data transmission process provided by an embodiment of this application.
  • FIG. 9 is a schematic diagram of a data transmission process provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 12 is a schematic diagram of a communication system provided by an embodiment of this application.
  • FIG. 2 exemplarily shows a schematic diagram of a 5G network architecture applicable to the embodiments of the present application.
  • the terminal device 201 can be connected to the core via an access network (AN) 202 Network for communication
  • terminal equipment can refer to user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication equipment , User agent or user device.
  • UE user equipment
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in the future 5G network, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • FIG. 2 only illustrates one terminal. In an actual network, there may be multiple terminals coexisting, which will not be repeated here.
  • AN may also be referred to as a radio access network (Radio Access Network, RAN), which is collectively referred to as AN below, and is mainly responsible for providing a wireless connection for the terminal device 201, ensuring reliable transmission of uplink and downlink data of the terminal device 201, and so on.
  • the access network entity 202 may be a gNB (generation Node B) in a 5G system, or an evolved base station (Evolutional Node B, eNB or eNodeB) in a Long Term Evolution (LTE) system, etc.
  • the Session Management Function (SMF) 203 is mainly responsible for establishing and managing sessions for the terminal device 201.
  • An appropriate UPF can be selected for the terminal device 201 according to the location information of the terminal device 201.
  • UPF 204 is a functional network element of the user plane of the terminal device 201. Its main functions include packet routing and forwarding, and quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • Access and Mobility Management Function (AMF) 205 the main functions include the termination point of the wireless access network control plane, the termination point of non-access signaling, mobility management, lawful monitoring, access authorization or Authentication, etc.
  • PCF Policy Control Funtion
  • the authentication server function (Authentication Server Function, AUSF) 207, whose main functions include user authentication and so on.
  • UDM User Data Management
  • the data network (DN) 209 may refer to a network that provides services for the terminal device 201.
  • An application server (application server, AS) 210 can provide data services for applications (applications) in terminal devices.
  • Figure 2 also shows possible implementations of the interfaces in each entity, such as the N2 interface between AN202 and AMF209, the N9 interface between AN202 and UPF204, etc., which will not be repeated here.
  • 5G also supports the insertion of multiple session anchors UPF on the user plane path of a PDU session to support the connection to the local DN, so that the terminal device can access the local DN nearby.
  • the application can be specifically shown in Figure 3.
  • multiple UPFs may be included between the terminal equipment and the DN.
  • the transmission path from the terminal device to the DN may include ULCL/BP, PSA1; the transmission path from the terminal device to the DN may also include ULCL/BP, PSA2, where ULCL/BP, PSA1, and PSA2 is implemented by UPF.
  • only one PDU session anchor is included in a transmission path as an example.
  • a transmission path between the terminal device and the DN may also include multiple PDU session anchors. , I won’t repeat it here.
  • ULCL/BP can distribute the uplink data packet received from the terminal device to PSA1 or PSA2 according to the distribution rules, and send the data packet received from PSA1 or PSA2 to the terminal device; PSA1 and PSA2 are respectively connected to the DN DN can be located in Multi-access Edge Computing (MEC).
  • MEC Multi-access Edge Computing
  • the MEC can include multiple application servers (Application Server, AS).
  • FIG. 4 is a schematic flowchart of a data transmission method provided by an embodiment of this application.
  • the method includes:
  • Step 401 The first network device determines the updated information of the user plane path of the terminal device
  • the above-mentioned updated information of the user plane path of the terminal device includes the information of the new path of the terminal device.
  • the information of the new path may be a data network access identifier (DNAI) corresponding to the new path.
  • DNAI data network access identifier
  • the first network device may receive a notification message, where the notification message is used to notify the user plane path change of the terminal device.
  • the notification message is an early notification message (Early Notification) or a late notification message (Late Notification).
  • the notification message includes the DNAI of the new route.
  • the update information may include information of multiple new paths, and correspondingly, the notification message also includes DNAI of the multiple new paths.
  • Step 402 The first network device determines that the application server of the application service of the terminal device according to the update information is changed from the first AS to the second AS, and then instructs the terminal device to stop sending the uplink data of the application;
  • the first network device determines whether the second AS of the application is deployed at the location corresponding to the new path according to the DNAI of one or more new paths. Further, the first network device determines whether the second AS deployed at the location corresponding to the new path can better serve the terminal device. For example, the first network device can serve the path between the terminal device according to the application service (for example, Path is shorter), time delay, load and other information determine whether to change the first AS of the application service of the terminal to the second AS.
  • the application service for example, Path is shorter
  • the first network device may instruct the terminal device to stop sending the uplink data of the application in various ways.
  • the first network device may send the first indication information, and perform an indication through the first indication information. For details, refer to step 403 and step 404.
  • step 403 the first network device sends the first indication information to the second network device;
  • the first indication information is used to instruct the second network device to instruct the terminal device to stop sending the uplink data of the application, or the first indication information is used to instruct the second network device to send the second indication information; second The indication information instructs the terminal device to stop sending the uplink data of the application.
  • step 404 the second network device receives the first indication information, and sends second indication information to the terminal device according to the first indication information.
  • the first network device may send the second indication information through the second network device. For details, refer to step 405 and step 406.
  • step 405 the first network device sends second indication information to the second network device;
  • the second indication information instructs the terminal device to stop sending the uplink data of the application.
  • the second indication information is transparently transmitted by the second network device, and the second network device may not parse the content of the first indication information.
  • step 406 the second network device receives the second indication information, and sends the second indication information to the terminal device.
  • the second network device may be a core network device, such as an SMF, or other network devices, such as a PCF or NEF.
  • the second network device may also be another core network device.
  • the second network device may be an AMF device, which is not limited in this embodiment of the application.
  • the first network device may directly send the second indication information to the terminal device. For details, refer to step 407.
  • step 407 the first network device sends second indication information to the terminal device.
  • the first network device may also send the address information of the second AS to the second network device, and the second network device sends the address information of the second AS to the terminal device; or, the first network device directly sends the address information of the second AS to the terminal device. Send the address information of the second AS.
  • the first network device may also send the application identification of the application to the second network device, and the second network device sends the application identification to the terminal device; or, the first network device directly sends the application of the application to the terminal device Logo.
  • the terminal device may determine the application corresponding to the second AS according to the identifier of the application.
  • the application identifier may be the address information of the first AS, for example, a fully qualified domain name (FQDN) or an Internet Protocol (IP) address, and the application identifier may also only be used to indicate The ID of the application.
  • FQDN fully qualified domain name
  • IP Internet Protocol
  • Step 408 The terminal device receives the second indication information.
  • the second indication information instructs the terminal device to stop sending the uplink data of the application.
  • Step 409 The terminal device stops sending the uplink data of the application according to the second instruction information
  • the terminal device may also obtain address information of the second AS, and the terminal device may establish a connection with the second AS.
  • the terminal device can establish a connection with the second AS according to the address information of the second AS.
  • the connection may include a link layer connection, or the connection may also include an application layer connection.
  • the terminal device buffers the uplink data of the application received from the application on the terminal device.
  • the terminal device may include an agent module (or an intermediate layer).
  • the agent module on the terminal device performs processing, that is, the agent module receives the second instruction information, and the agent module stops Sending the uplink data of the application, the proxy module establishes a connection with the second AS, the proxy module stops sending the uplink data of the application, and buffers the uplink data received from the application.
  • the application on the terminal device sends all uplink data to the proxy module, and the proxy module sends it to the application server, and the proxy module receives the downlink data from the application server and sends it to the application on the terminal device .
  • the proxy module can shield the application server from changing from the first AS to the second AS, so that the application does not perceive the change of the application server, and the application server can still be reselected after the terminal device moves and the connection is established with the application server, and reduces the number of problems. Application impact.
  • the first network device and the second network device may have different implementations.
  • the first network device may be an AF that manages the first AS and the second AS, or it may be the first AS. , Can also be SMF, etc.
  • the second network device is a core network device.
  • the process in FIG. 4 may have multiple implementation manners. The following describes the process in FIG. 4 in detail according to different situations.
  • the first network device is the AF that manages the first AS and the second AS
  • the second network device is the core network device, where the core network device can be an SMF or, It is PCF, NEF, AMF, etc.
  • the second network device determines the update information
  • the first network device determines the second AS according to the update information
  • an application function (AF) is used as an example for the terminal device to select the switched AS.
  • AF can manage multiple ASs, such as the first AS and the second AS.
  • the ULCL in 5 can also be implemented by BP, which will not be repeated here.
  • the terminal device Before step 500, the terminal device establishes a connection with the first AS in the first MEC, and the terminal device provides services to the first AS in the first MEC, and the terminal device sends data to The first AS.
  • a second AS that provides services for the terminal device needs to be determined from the second MEC, which will be described in detail below.
  • Step 500 The SMF receives a data network access identifier (Data Network Access Identifier, DNAI) unchanged indication.
  • a data network access identifier Data Network Access Identifier, DNAI
  • the AF can send to the PCF or the Network Exposure Function (NEF) an indication of whether the application that provides services for the terminal device supports handover. If the AF indicates that the application does not support handover, the PCF/NEF can send a DNAI to the SMF Unchanged indication, DNAI unchanging indication is used to indicate that the application needs to keep DNAI unchanged.
  • NEF Network Exposure Function
  • the AF can subscribe to early notification and late notification.
  • the SMF can send a corresponding notification to the AF.
  • Figure 5 shows the direct connection between AF and SMF.
  • AF can be connected to SMF through PCF or Network Exposure Function (NEF), that is, AF sends messages to PCF/NEF .
  • PCF/NEF converts the AF message and then sends the message to the SMF.
  • Figure 5 is just an example, and the message sent by the PCF/NEF to the SMF is not shown in Figure 5.
  • the AF may be a network element that centrally manages all ASs, the AF may also be the first AS, or the AF is the platform of the first MEC where the first AS is located, etc., which is not specifically limited.
  • Step 501 SMF selects the second ULCL and the second PSA.
  • the SMF determines to select the second ULCL and the second PSA in the second MEC. If the AF subscribes to the early notification from the SMF, after the SMF selects the second ULCL and the second PSA, the second ULCL and the second PSA may not be inserted immediately. At this time, that is, the user plane path of the terminal device remains unchanged, and the terminal device still communicates with the first AS after passing the first ULCL and the first PSA.
  • Step 502 The SMF sends an early notification to the AF.
  • the SMF sends update information of the user plane path between the terminal device and the first AS to the AF, and the update information may be at least one DNAI corresponding to the second MEC connected to the second PSA.
  • the SMF can select multiple local PSAs, and these local PSAs respectively correspond to different MECs, and the local PSA includes the second PSA.
  • the update information includes the DNAI corresponding to the MEC connected to each PSA in the local PSA, which is not limited in the embodiment of the present application.
  • the AF can be used to determine the AS in the terminal device after the application is switched. For details, refer to the description of step 503.
  • Step 503 AF selects the second AS.
  • the AF determines whether to select the second AS according to the updated information. If the AF determines to select the second AS, the AF selects the second AS according to the updated information. For example, the AF can determine the location of the second AS based on the update information. For example, when the update information is at least one DNAI corresponding to the second MEC, the AF selects an available AS from the second MEC corresponding to the at least one DNAI. The second AS.
  • the AS can be registered in the AF when it goes online, so that the AF can save all online ASs and the information of the DNAI corresponding to the AS, or when the AF can query the DNS server in the second MEC corresponding to the at least one DNAI, In this way, the addresses of all available ASs in the second MEC can be obtained, and the AF can thus select an AS as the second AS.
  • the specific selection process is not limited, and will not be repeated here.
  • the AF can indicate the second AS to the terminal device through the core network device, and instruct the terminal device to stop sending the uplink data of the application. For details, refer to the description in steps 504 to 506 .
  • Step 504 The AF sends the first message to the core network device.
  • the AF may send a first message to the core network device, and the first message may include the address information of the second AS.
  • the AF may also send the application identifier of the application to the core network device, so as to determine the application corresponding to the second AS according to the application identifier.
  • the AF may send the first indication information to the core network device.
  • the first indication information is used to instruct the core network device to send second indication information to the terminal device, and the second indication information is used to instruct the terminal device to suspend sending uplink data to the first AS.
  • the first message further includes second indication information.
  • the SMF does not parse the first message, and the core network device directly transparently transmits the first message to the terminal device. If the first message passes through the PCF/NEF, the PCF/NEF does not parse the first message.
  • the first message may further include an association identifier, which is used by the second AS to associate the link established between the terminal device and the second AS with the application layer status information received from the first AS.
  • an association identifier which is used by the second AS to associate the link established between the terminal device and the second AS with the application layer status information received from the first AS.
  • the application layer state information may be used to process the application information of the terminal device.
  • the application layer state information may include, but is not limited to, the context information of the terminal device, the current state information of the application, and so on.
  • the application status information may include payment status, order information, and so on.
  • the new application server can determine whether the user has paid according to the application status information, and if not, it can push the payment interface to the user.
  • the first indication information, the address information of the second AS, etc. can all be encapsulated in a transparent container, so that the core network device (such as SMF or PCF, etc.) does not parse, and the AF instructs the core network device to send the transparent container to the terminal device . Based on this, the core network device can send the transparent container to the terminal device.
  • the core network device such as SMF or PCF, etc.
  • the SMF sends the transparent container to the terminal device.
  • AF is used to send the above-mentioned information to the terminal device through SMF.
  • the AF can also send the above information to the terminal device through AMF.
  • the SMF in step 504 and step 506 of this embodiment is replaced with AMF.
  • the non-received information sent to the UE through AMF Non-access stratum (NAS) messages are not session modification messages, but other types of NAS messages.
  • AF can send the above information to SMF through NEF/PCF.
  • the AF may also send the above information to the core network device through the NEF, which is not limited in the present invention.
  • the core network device may also instruct the SMF to insert the second ULCL in the PDU session path.
  • the core network device may also instruct the SMF to insert the second ULCL in the PDU session path.
  • Step 505 The SMF inserts the second ULCL in the PDU session path.
  • the SMF receives an indication that the application needs to keep the DNAI unchanged. For this reason, the SMF can instruct the establishment of a forwarding tunnel between the first ULCL and the second ULCL, or the SMF can instruct the establishment of the establishment between the second ULCL and the first PSA. Forwarding tunnel.
  • the data path between the terminal device and the first AS includes the following devices in sequence: the terminal device, the second ULCL, the first ULCL, and the first PSA; or, the second ULCL
  • the data path between the terminal device and the first AS sequentially includes devices: the terminal device, the second ULCL, and the first PSA.
  • the forwarding tunnel can enable the terminal device to send the application data to the first AS through the forwarding tunnel before the application switching server, so as to minimize the switching delay.
  • Step 506 The core network device sends a notification message to the terminal device.
  • the core network device sends the address information of the second AS to the terminal device through the notification message.
  • the notification message also includes an application identifier, which is used to indicate the application corresponding to the second AS of the terminal device.
  • the terminal device determines which application needs to switch the application server according to the application identifier.
  • the "application” in the terminal device may be a program installed in the terminal device in the form of a client.
  • the following embodiments are collectively referred to as applications.
  • the core network device If the core network device receives the first instruction information or the second instruction information, the core network device sends the first instruction information to the terminal device. If the core network device receives the association identifier, the core network device also sends the association identifier to the terminal device.
  • the core network device may send a session modification message to the terminal device, and the above information is sent to the terminal device in the session modification message.
  • Step 507 The terminal device suspends sending uplink data.
  • an intermediate function that is, a proxy function
  • the application of the terminal device sends all messages sent to the AS to the proxy function, and the proxy function sends it to the AS.
  • the proxy may be an HTTP proxy.
  • HTTP hypertext transfer protocol
  • the message sent by the SMF to the terminal device in step 505 is sent to the proxy function.
  • the proxy function can enable the uplink buffer function, so as to buffer the uplink message sent by the application corresponding to the first AS in the terminal device.
  • Step 508 The terminal device establishes a connection with the second AS according to the address information of the second AS.
  • the terminal device can initiate connection establishment with the second AS. This process establishes a link between the terminal device and the second AS, for example, establishes a Transmission Control Protocol (TCP) connection.
  • TCP Transmission Control Protocol
  • the Proxy function establishes a connection with the second AS.
  • step 508 and step 507 are not limited, and step 508 can also be performed before step 507.
  • Step 509 The terminal device sends a response message to the core network device.
  • the terminal device may send the link information of the link between the terminal device and the second AS to the core network device in a response message.
  • the link information of the link may include the source IP address and source port of the TCP connection Number, protocol number and other information.
  • the response message may also include the application identifier corresponding to the application or the previously received association identifier.
  • the application layer status information received by the second AS from the first AS includes link information, or application identification or association identification, and the second AS associates the application layer status information with the link according to the link information in the application layer status information. If the link information is not sent, that is, the application identification or association identification is used to associate the link with the application layer status information, the terminal device also needs to send the application identification or association identification on the link established by the terminal device and the second AS, So that the second AS can associate.
  • the terminal device may also encapsulate the link information, application identifier or association identifier of the link between the terminal device and the second AS in a transparent container and send it to the core network device, and the core network device may not parse the transparent container. , Transparently transmitted to AF.
  • the terminal device can also directly send the application identifier or the association identifier to the second AS through the link between the terminal device and the second AS, so that the second AS can use the application identifier or association identifier corresponding to the link.
  • the link is associated with the application layer state information (including application identification or association identification) received from the first AS.
  • the terminal device may also send the link information of the link between the terminal device and the second AS to the first AS, and then the first AS sends it to the second AS in the application layer status information.
  • the second AS may associate the application layer state information with the link according to the link information in the application layer state information.
  • Step 510 The core network device sends a late notification to the AF.
  • the SMF may send the link information, application identification or association identification to the AF through the late notification.
  • the AF receives the link information, application identification or association identification of the terminal device, the AF sends the link information, application identification or association identification to the second AS.
  • the core network device may also use other messages to send the above information to the AF, which is not limited in this embodiment.
  • Step 511 Perform state transition between the first AS and the second AS.
  • the AF before the state transition between the first AS and the second AS, the AF can indicate the address information of the second AS to the first AS, and the first AS can thus determine the second AS according to the address information of the second AS;
  • the AF may indicate the address information, application identification or association identification of the first AS to the second AS, and the second AS may thus obtain application layer state information from the first AS according to the address information, application identification or association identification of the first AS.
  • the application layer state information related to the terminal device needs to be migrated between the first AS and the second AS, and there is no need to migrate the state of other terminal devices, and there is no need to migrate the state of the link layer.
  • the content included in the application layer status information is information such as the context of the terminal device, application identification or association identification, and link layer information between the terminal device and the second AS.
  • the first AS may send the application layer status information of the terminal device to the second AS.
  • the sending of the application layer status information may be forwarded by AF, or sent directly between the first AS and the second AS, or sent through other channels, which is not limited in this embodiment of the application.
  • the second AS can associate the link between the terminal device and the second AS with the application sent from the first AS according to the application identification or association identification.
  • the layer status information is associated.
  • the first AS and/or the second AS may send an indication message to the AF to indicate the completion of the state transition.
  • the AF can also instruct the terminal device to resume sending the uplink data of the application through the core network device. For details, refer to the description of step 512 to step 513.
  • Step 512 AF sends a second message.
  • the second message may be used to instruct the terminal device to resume sending the uplink data of the application.
  • the AF sends a second message to the core network device.
  • the core network device may be SMF, or PCF/NEF, or AMF, or AF may also send a second message to SMF or AMF through PCF/NEF, which is not limited in this embodiment of the application.
  • the second message includes third indication information, which is used by the core network device to send fourth indication information to the terminal device, and the fourth indication information is used to instruct the terminal device to resume uplink transmission.
  • the device has established a connection with the second AS, and the fourth indication information may also be used to instruct the terminal device to send uplink data to the second AS.
  • the second message includes fourth indication information.
  • the core network device does not parse the fourth instruction information, and directly sends the fourth instruction information to the terminal device.
  • Step 513 The core network device sends fourth indication information to the terminal device.
  • the AF may also directly send the fourth indication information to the terminal device, or the first AS or the second AS may also send the fourth indication information to the terminal device, which is not limited in this embodiment of the application.
  • the proxy in the terminal device When there is a proxy in the terminal device, the proxy in the terminal device sends the buffered uplink data to the second AS through the link established in step 509 after receiving the fourth indication information.
  • the proxy in the terminal device sends the uplink data sent by the application in the terminal device to the second AS.
  • the second AS After the second AS obtains the application layer status information associated with the application identifier or the association identifier, the second AS can process the uplink data from the terminal device through the application layer status information.
  • the data path between the terminal device and the second AS is: the terminal device, the second ULCL, and the second PSA, that is, the uplink data sent by the terminal device is forwarded to the second AS through the second ULCL and the second PSA;
  • the downlink data sent by the second AS to the terminal device is forwarded to the terminal device through the second PSA and the second ULCL.
  • the AF determines the handover second AS for the terminal device in the second MEC, which can ensure that the terminal device accesses the second AS nearby.
  • the terminal device Before the terminal device communicates with the second AS, it establishes a link layer connection with the second AS. Therefore, only the application layer state information needs to be migrated between the first AS and the second AS, and there is no need to migrate the link layer state corresponding to the application.
  • the IP address of the terminal device can be changed.
  • the IP address of the second AS does not need to be consistent with the IP address of the first AS.
  • step 505 and step 501 can be performed at the same time, that is, after the SMF selects the second ULCL and the second PSA, the selected second ULCL is directly inserted into the PDU session path, which is described below with reference to FIG. 6.
  • the first network device is the AF that manages the first AS and the second AS
  • the second network device is the core network device.
  • the core network device may be an SMF or, It is PCF, NEF, AMF, etc.
  • the second network device determines the update information, the first network device determines the second AS according to the update information, and indicates the second AS to the terminal device through the second network device, which will be described in detail below.
  • the AF is used as the terminal device to select the switched AS as an example for description.
  • the ULCL in FIG. 6 can also be implemented by BP, which will not be repeated here.
  • the terminal equipment Before step 600, the terminal equipment has established a connection with the first AS in the first MEC, and the terminal equipment is provided with services by the first AS in the first MEC.
  • the terminal equipment sends data to The first AS.
  • a second AS that provides services for the terminal device needs to be determined from the second MEC, which will be described in detail below.
  • Step 600 The SMF receives the DNAI unchanged indication.
  • the AF can send an indication to the PCF or NEF whether the application that provides services for the terminal device supports handover. If the AF indicates that the application does not support handover, the PCF/NEF can send the DNAI unchanged indication to the SMF, and the DNAI unchanged indication is used As indicated that the application needs to keep DNAI unchanged.
  • the AF can subscribe to late notifications.
  • the SMF can send a corresponding notification to the AF.
  • Figure 6 shows the direct connection between AF and SMF.
  • AF can be connected to SMF through PCF or Network Exposure Function (NEF), that is, AF sends messages to PCF/NEF .
  • PCF/NEF converts the AF message and then sends the message to the SMF.
  • Figure 6 is just an example, and the message sent by the PCF/NEF to the SMF is not shown in Figure 6.
  • the AF may be a network element that centrally manages all ASs, the AF may also be the first AS, or the AF is the platform of the first MEC where the first AS is located, etc., which is not specifically limited.
  • Step 601 SMF selects the second ULCL and the second PSA, and inserts the second ULCL in the PDU session path.
  • the SMF determines to select the second ULCL and the second PSA in the second MEC. How the SMF specifically selects the second ULCL and the second PSA is not limited in the embodiment of the present application, and will not be repeated here.
  • the SMF receives an indication that the application needs to keep the DNAI unchanged.
  • the SMF can instruct the establishment of a forwarding tunnel between the first ULCL and the second ULCL, or the SMF can instruct the establishment of the establishment between the second ULCL and the first PSA. Forwarding tunnel.
  • the data path between the terminal device and the first AS is: the terminal device, the second ULCL, the first ULCL, the first PSA; or, the second ULCL to the first PSA
  • the data path between the terminal device and the first AS is: the terminal device, the second ULCL, and the first PSA.
  • Step 602 SMF sends a late notification to AF.
  • the SMF sends the update information of the user plane path between the terminal device and the first AS to the AF in the late notification, and the update information may be at least one DNAI corresponding to the second MEC connected to the second PSA.
  • the SMF can select multiple local PSAs, and these local PSAs respectively correspond to different MECs, and the local PSA includes the second PSA.
  • the update information includes the DNAI corresponding to the MEC connected to each PSA in the local PSA, which is not limited in the embodiment of the present application.
  • the AF can determine the AS in the terminal device after the application is switched. For details, refer to the description of step 603.
  • Step 603 AF selects the second AS.
  • the AF determines whether to select the second AS based on the updated information. If the AF determines to select the second AS, the AF selects the second AS based on the updated information. For example, the AF can determine the location of the second AS based on the update information. For example, when the update information is at least one DNAI corresponding to the second MEC, the AF selects an available AS from the second MEC corresponding to the at least one DNAI. The second AS.
  • the AS can be registered in the AF when it goes online, so that the AF can save all online ASs and the information of the DNAI corresponding to the AS, or when the AF can query the DNS server in the second MEC corresponding to the at least one DNAI, In this way, the addresses of all available ASs in the second MEC can be obtained, and the AF can thus select an AS as the second AS.
  • the specific selection process is not limited, and will not be repeated here.
  • the AF can indicate the second AS to the terminal device through SMF and instruct the terminal device to stop sending the uplink data of the application. For details, refer to the description in steps 604 to 606.
  • Step 604 The AF sends the first message to the core network device.
  • the AF sends the address information of the second AS to the core network device through the first message.
  • the first message further includes first indication information.
  • the first indication information is used for the core network device to send second indication information to the terminal device, and the second indication information is used for instructing the terminal device to suspend sending uplink data to the first AS.
  • the first message further includes second indication information.
  • the core network device does not parse the first message, and the core network device transmits the first message directly to the terminal device. If the first message passes through other core network devices, such as PCF/NEF, other core network devices Nor does it parse the first message.
  • the first message may also include an application identifier, and the application identifier is used to indicate the application that needs to switch the application server.
  • the first message may further include an association identifier, which is used by the second AS to associate the link established between the terminal device and the second AS with the application layer status information received from the first AS.
  • an association identifier which is used by the second AS to associate the link established between the terminal device and the second AS with the application layer status information received from the first AS.
  • the first indication information, the address information of the second AS, etc. can all be encapsulated in a transparent container, so that the core network device (such as SMF or PCF) does not parse, and AF instructs the core network device (such as SMF or PCF) to be transparent
  • the container is sent to the terminal device.
  • the core network device can send the transparent container to the terminal device.
  • the core network device is an SMF as an example, and the SMF sends the transparent container to the terminal device.
  • the core network device may also be other network elements, such as AMF, which is not limited in this embodiment.
  • Step 605 The core network device sends the address information of the second AS to the terminal device.
  • the core network device may also send an application identifier to the terminal device, where the application identifier is used to indicate the application corresponding to the second AS of the terminal device.
  • the terminal device determines which application needs to switch the application server according to the application identifier.
  • the core network device If the core network device receives the first indication information, the core network device sends the first indication information or the second indication information to the terminal device. If the core network device receives the association identifier, the core network device also sends the association identifier to the terminal device.
  • the SMF can send a session modification message to the terminal device, and the above information is sent to the terminal device in the session modification message.
  • Step 606 The terminal device suspends sending uplink data.
  • an intermediate function that is, a proxy function
  • the application of the terminal device sends all messages sent to the AS to the proxy function, and the proxy function sends it to the AS.
  • the proxy may be an HTTP proxy.
  • HTTP hypertext transfer protocol
  • the message sent by the SMF to the terminal device in step 605 is sent to the proxy function.
  • the proxy function can enable the uplink buffer function, so as to buffer the uplink messages sent by the application corresponding to the first AS in the terminal device.
  • Step 607 The terminal device establishes a connection with the second AS according to the address information of the second AS.
  • the terminal device can initiate connection establishment with the second AS.
  • This process establishes a connection between the terminal device and the second AS, for example, establishes a TCP connection. It is also possible to establish a connection with the application layer of the second AS.
  • step 607 and step 606 are not limited, and step 607 can also be performed before step 606.
  • Step 608 The terminal device sends a response message to the core network device.
  • the terminal device may send the link information of the link between the terminal device and the second AS to the core network device in a response message.
  • the link information of the link may include the source IP address and source port of the TCP connection Number, protocol number and other information.
  • the response message may also include the application identifier corresponding to the application or the previously received association identifier.
  • the application layer status information received by the second AS from the first AS includes link information, or application identification or association identification, and the second AS associates the application layer status information with the link according to the link information in the application layer status information. If the link information is not sent, that is, the application identification or association identification is used to associate the link with the application layer status information, the terminal device also needs to send the application identification or association identification on the link established by the terminal device and the second AS, So that the second AS can associate.
  • the terminal device may also encapsulate the link information, application identifier or association identifier of the link between the terminal device and the second AS in a transparent container and send it to the core network device, and the core network device may not parse the transparent container. , Transparently transmitted to AF.
  • the terminal device can also directly send the application identifier or the association identifier to the second AS through the link between the terminal device and the second AS, so that the second AS can use the application identifier or association identifier corresponding to the link.
  • the link is associated with the application layer state information (including application identification or association identification) received from the first AS.
  • the terminal device may also send the link information of the link between the terminal device and the second AS to the first AS, and then the first AS sends it to the second AS in the application layer status information.
  • the second AS may associate the application layer state information with the link according to the link information in the application layer state information.
  • Step 609 The core network device sends the first notification to the AF.
  • the core network device may send the link information, application identification or association identification to the AF through the first notification.
  • the AF receives the link information, application identification or association identification of the terminal device, the AF sends the link information, application identification or association identification to the second AS.
  • Step 610 Perform state transition between the first AS and the second AS.
  • the AF before the state transition between the first AS and the second AS, the AF can indicate the address information of the second AS to the first AS, and the first AS can thus determine the second AS according to the address information of the second AS; or , The AF can indicate the address information, application identification or association identification of the first AS to the second AS, and the second AS can thus obtain application layer state information from the first AS according to the address information, application identification or association identification of the first AS.
  • the application layer status information includes, but is not limited to, information such as the context of the terminal device, application identification or association identification, and link layer information between the terminal device and the second AS.
  • the first AS may send the application layer status information of the terminal device to the second AS.
  • the sending of the application layer status information can be forwarded by AF, or sent directly between the first AS and the second AS, or sent through other channels, which is not limited in this embodiment of the application.
  • the second AS can associate the link between the terminal device and the second AS with the application sent from the first AS according to the application identification or association identification.
  • the layer status information is associated.
  • the AF can also instruct the terminal device to resume sending the uplink data of the application through the core network device. For details, refer to the description of step 611 to step 612.
  • Step 611 After the AS state transition is completed, the AF sends a second message to the core network device.
  • the second message may be used to instruct the terminal device to resume sending the uplink data of the application.
  • the second message includes third indication information
  • the third indication information is used to instruct the core network device to send fourth indication information to the terminal device
  • the fourth indication information is used to instruct the terminal device to recover.
  • the fourth indication information may also be used to instruct the terminal device to send uplink data to the second AS.
  • the second message includes fourth indication information.
  • the core network device does not parse the second message, but directly sends the second message to the terminal device.
  • Step 612 The core network device sends fourth indication information to the terminal device.
  • step 512 For details of this step, refer to step 512.
  • the proxy in the terminal device When a proxy exists in the terminal device, the proxy in the terminal device sends the buffered uplink data to the second AS through the link established in step 608 after receiving the fourth indication information.
  • the proxy in the terminal device sends the uplink data sent by the application in the terminal device to the second AS through the link.
  • the data path between the terminal device and the second AS is: the terminal device, the second ULCL, and the second PSA, that is, the uplink data sent by the terminal device is forwarded to the second AS through the second ULCL and the second PSA;
  • the downlink data sent by the second AS to the terminal device is forwarded to the terminal device through the second PSA and the second ULCL.
  • the AF sends the determined address information of the second AS and the first indication information to the terminal device through the core network device, and the AF can also directly send the address information and the first indication information of the second AS To the terminal device, the following is described in detail through the flow of FIG. 7.
  • the first network device is an AF
  • the second network device is a core network device.
  • the core network device may be SMF, or PCF, NEF, AMF, and so on.
  • the second network device determines the update information
  • the first network device determines the second AS according to the update information, and directly indicates the second AS to the terminal device, which will be described in detail below.
  • An exemplary AF may be a network element that manages the first AS and the second AS.
  • the AF is an MEC platform.
  • the AF is used as the terminal device to select the switched AS as an example for description.
  • the ULCL in FIG. 7 can also be implemented by BP, which will not be repeated here.
  • the terminal device Before step 700, the terminal device establishes a connection with the first AS in the first MEC, and the terminal device provides services to the first AS in the first MEC, and the terminal device sends data to The first AS.
  • a second AS that provides services for the terminal device needs to be determined from the second MEC, which will be described in detail below.
  • the AF may be a network element that centrally manages all ASs, the AF may also be the first AS, or the AF may be the platform of the first MEC where the first AS is located, etc., which is not specifically limited.
  • a connection is established between the terminal device and the AF, so that the AF can send a message to the terminal device.
  • the connection is used to support the switching of the application state between the first AS and the second AS.
  • Step 700 The SMF receives the DNAI unchanged indication.
  • step 500 For the specific content of this step, refer to the description of step 500, which will not be repeated here.
  • Step 701 SMF selects the second ULCL and the second PSA, and inserts the second ULCL in the PDU session path.
  • the SMF determines to select the second ULCL and the second PSA in the second MEC. How the SMF specifically selects the second ULCL and the second PSA is not limited in the embodiment of the present application, and will not be repeated here.
  • the SMF receives an indication that the application needs to keep the DNAI unchanged. For this reason, the SMF can instruct the establishment of a forwarding tunnel between the first ULCL and the second ULCL, or the SMF can instruct the establishment of the establishment between the second ULCL and the first PSA. Forwarding tunnel.
  • the data path between the terminal device and the first AS is: the terminal device, the second ULCL, the first ULCL, the first PSA; or, the second ULCL to the first PSA
  • the data path between the terminal device and the first AS is: the terminal device, the second ULCL, and the first PSA.
  • Step 702 SMF sends an early notification to AF.
  • step 502 For the specific content of this step, reference may be made to step 502, which will not be repeated here.
  • the AF can determine the AS in the terminal device after the application is switched. For details, refer to the description of step 703.
  • Step 703 AF selects the second AS.
  • step 503 For the specific content of this step, reference may be made to step 503, which will not be repeated here.
  • step 700 to step 703 can also be replaced by step 600 to step 603, and the details can be referred to as shown in FIG. 6, which will not be repeated here.
  • the AF can directly indicate the second AS to the terminal device and instruct the terminal device to stop sending the uplink data of the application. For details, refer to the description in steps 704 to 705.
  • Step 704 The AF sends the first message to the terminal device.
  • the first message includes the address information of the second AS. If the application is stateful and needs to stop sending the uplink data of the application when the application server is switched, the first message also includes the second indication information.
  • the first message also includes information such as application identification, and the application identification is used by the terminal device to determine the application to be switched to the application server.
  • the AF may also send an association identifier to the terminal device, where the association identifier is used by the second AS to associate the link established between the terminal device and the second AS with the application layer status information received from the first AS.
  • the proxy in the terminal device can receive the first message.
  • Step 705 The terminal device suspends sending uplink data according to the second instruction information.
  • step 507 For the specific content of this step, reference may be made to step 507, which will not be repeated here.
  • Step 706 The terminal device establishes a connection with the second AS according to the address information of the second AS.
  • step 508 For the specific content of this step, reference may be made to step 508, which will not be repeated here.
  • Step 707 The terminal device sends a response message to the AF.
  • the terminal device may send the link information of the link between the terminal device and the second AS to the AF in a response message.
  • the response message may also include the application identifier corresponding to the application or the previously received association identifier.
  • the application layer status information received by the second AS from the first AS includes link information, or application identification or association identification, and the second AS associates the application layer status information with the link according to the link information in the application layer status information. If the link information is not sent, that is, the application identification or association identification is used to associate the link with the application layer status information, the terminal device also needs to send the application identification or association identification on the link established by the terminal device and the second AS, So that the second AS can associate.
  • the terminal device may also directly send the application identifier or the association identifier to the second AS through the link between the terminal device and the second AS, so that the second AS will send the application identifier or association identifier to the second AS according to the application identifier or association identifier received by the link.
  • This link is associated with the application context received from the first AS.
  • Step 708 Perform state transition between the first AS and the second AS.
  • step 511 For the specific content of this step, reference may be made to step 511, which will not be repeated here.
  • the AF can also directly instruct the terminal device to resume sending the uplink data of the application.
  • the terminal device can also directly instruct the terminal device to resume sending the uplink data of the application.
  • Step 709 The AF sends a second message to the terminal device, where the second message includes fourth indication information.
  • the fourth indication information is used to instruct the terminal equipment to resume uplink transmission.
  • the terminal device may send the uplink data to the second AS through the link established with the second AS.
  • the data path between the terminal device and the second AS is: the terminal device, the second ULCL, and the second PSA.
  • the proxy in the terminal device sends the buffered uplink data to the second AS through the link established between the terminal and the second AS after receiving the fourth indication information.
  • the proxy in the terminal device sends the uplink data sent by the application in the terminal device to the second AS through the link.
  • the second AS can process the uplink data from the terminal device through the application layer state information associated with the link.
  • the description is given by taking the AF as a network element that centrally manages all ASs.
  • the AF may also be the first AS, which will be described in detail below through the flow of FIG. 8.
  • the first network device is the first AS
  • the second network device is the core network device.
  • the core network device can be SMF, or PCF, NEF, AMF, etc. , Will be described in detail below.
  • the first AS is used as the terminal device to select the switched AS as an example for description.
  • the ULCL in FIG. 8 can also be implemented by BP, which will not be repeated here.
  • the terminal device establishes a connection with the first AS in the first MEC, and the terminal device provides services to the first AS in the first MEC, and the terminal device sends data to The first AS.
  • a second AS that provides services for the terminal device needs to be determined from the second MEC, which will be described in detail below.
  • Step 800 The SMF receives the DNAI unchanged indication.
  • step 500 For the specific content of this step, refer to the description of step 500, which will not be repeated here.
  • Step 801 SMF selects the second ULCL and the second PSA, and inserts the second ULCL in the PDU session path.
  • step 601 For the specific content of this step, refer to the description in step 601, which will not be repeated here.
  • Step 802 SMF sends a late notification to the first AS.
  • step 502 For the specific content of this step, reference may be made to step 502, which will not be repeated here.
  • the SMF does not insert the second ULCL in step 801, the early notification may be sent in this step.
  • the AF can determine the AS in the terminal device after the application is switched. For details, refer to the description of step 803.
  • the AF may be the first AS or other network elements, such as the orchestrator of the MEC.
  • the following takes the AF as the first AS as an example for description.
  • Step 803 The first AS obtains the second AS.
  • the first AS obtains the second AS refer to the process of AF selecting the second AS in step 503, which will not be repeated here, that is, the second AS is selected by the first AS.
  • the AF may select the second AS and send the selected second AS to the first AS.
  • step 800 to step 803 can also be replaced by step 600 to step 603, and the details can be referred to as shown in FIG. 6, which will not be repeated here.
  • the first AS can indicate the second AS to the terminal device through SMF, and instruct the terminal device to stop sending the uplink data of the application; of course, the first AS can also directly The terminal device indicates the foregoing information.
  • the first AS directly indicates to the terminal device as an example for description.
  • Step 804 The first AS sends a first message to the terminal device, where the first message includes address information of the second AS. If the application has status, the first message also includes second indication information.
  • the first AS may also send an association identifier to the terminal device, where the association identifier is used by the second AS to associate the link established between the terminal device and the second AS with the application layer status information received from the first AS.
  • the terminal device sends the association identifier to the second AS through the link established between the terminal and the second AS, and the first AS includes the association identifier in the application layer status information. Based on this, the second AS can associate the application layer status information with the link Associated.
  • the terminal device may not include the proxy function, and the first AS may directly send the address information of the second AS and the second indication information to the terminal device.
  • the first AS may directly send the first message through application layer messages.
  • Step 805 The terminal device suspends sending uplink data according to the second instruction information.
  • step 507 For the specific content of this step, reference may be made to step 507, which will not be repeated here.
  • Step 806 The terminal device establishes a connection with the second AS according to the address information of the second AS.
  • the terminal device can send the application identifier or the association identifier to the second AS through the connection.
  • Step 807 The terminal device sends a response message to the first AS.
  • the terminal device may send the link information of the link between the terminal device and the second AS to the first AS in a response message.
  • the response message may also include the application identifier corresponding to the application or the previously received association identifier.
  • the terminal device may also directly send the link information, application identifier, or association identifier of the link between the terminal device and the second AS to the second AS through the established link.
  • the second AS associates the application state with the link according to the link information in the application state.
  • Step 808 Perform state transition between the first AS and the second AS.
  • step 511 For the specific content of this step, reference may be made to step 511, which will not be repeated here.
  • the first AS may also instruct the terminal device to resume sending the uplink data of the application through the core network device, or the first AS may also directly instruct the terminal device to resume sending the uplink data of the application, as shown in FIG. 8 Directly instruct the terminal device as an example for description. For details, refer to the description of step 809.
  • Step 809 The first AS sends a second message to the terminal device, where the second message includes fourth indication information.
  • the fourth indication information is used to instruct the terminal equipment to resume uplink transmission.
  • the fourth indication information may also be sent by the second AS to the terminal device.
  • the terminal device may send the uplink data to the second AS through the connection established with the second AS.
  • the data path between the terminal device and the second AS is: the terminal device, the second ULCL, and the second PSA.
  • the AF or the first AS selects the second AS as an example for description.
  • the SMF may also select the second AS, which will be described in detail below through the flow of FIG. 9.
  • the first network device is an SMF
  • the second network device is an AF, which will be described in detail below.
  • Fig. 9 takes the SMF as the terminal device to select the AS after the handover as an example for description.
  • the ULCL in Fig. 8 can also be implemented by BP, which will not be repeated here.
  • the terminal equipment Before step 900, the terminal equipment has established a connection with the first AS in the first MEC, and the terminal equipment is provided with services by the first AS in the first MEC.
  • the terminal equipment sends data to The first AS.
  • a second AS that provides services for the terminal device needs to be determined from the second MEC, which will be described in detail below.
  • Step 900 SMF receiving status indication information.
  • the status indication information is used to indicate that the application includes application layer status information.
  • the SMF may receive the status indication information from the AF or the first AS or the centralized network element that manages the AS.
  • the SMF can also receive the application identifier of the application.
  • Step 901 SMF selects the second ULCL and the second PSA.
  • step 501 For the specific content of this step, reference may be made to step 501, which will not be repeated here.
  • step 901 can also be replaced by step 601, and the details can be referred to as shown in FIG. 6, which will not be repeated here.
  • the SMF can determine the AS in the terminal device after the application is switched. For details, refer to the description of step 902.
  • Step 902 SMF selects the second AS.
  • SMF selects the second AS.
  • the SMF may select the second AS based on the information of the AS deployed in the second MEC.
  • the AF such as the MEC platform
  • the SMF may also query the DNS to obtain the information of the AS deployed in the second MEC.
  • the SMF can also use other methods to select the second AS, which is not limited in this embodiment.
  • Step 903 The SMF sends the address information of the second AS.
  • the SMF can send the address information of the second AS to the first AS, or send the address information of the first AS to the second AS, or send the address information of the second AS to the AF, which is not limited in this embodiment of the application.
  • sending the address information of the second AS to the AF is taken as an example for description, and other situations will not be repeated.
  • the first AS forwards the address information of the second AS to the terminal device.
  • the SMF sends the address information of the first AS to the second AS
  • the first AS is triggered to send the address information of the second AS to the terminal device, and the specific process is not repeated here.
  • the SMF may also send the address information of the first AS to the AF.
  • Step 904 The AF sends the first message to the core network device.
  • the core network equipment may be SMF or AMF and other equipment.
  • the AF may not send the address information of the second AS, which will not be repeated here.
  • the core network device may also instruct the SMF to insert the second ULCL in the PDU session path.
  • the core network device may also instruct the SMF to insert the second ULCL in the PDU session path.
  • Step 905 The SMF inserts the second ULCL in the PDU session path.
  • the SMF can be triggered by the first message to insert the second ULCL, or the AF sends another message, and the message triggers the SMF to insert the second ULCL, which is not limited.
  • step 505 For the specific content of this step, please refer to step 505, which will not be repeated here.
  • Step 906 The core network device sends a notification message to the terminal device.
  • step 506 For the specific content of this step, refer to the description of step 506, which will not be repeated here.
  • Step 904 and step 906 can also be replaced by step 704, which will not be repeated here.
  • step 904 and step 906 can also be replaced by step 804, which will not be repeated here.
  • Step 907 The terminal device suspends sending uplink data.
  • step 507 For the specific content of this step, reference may be made to step 507, which will not be repeated here.
  • Step 908 The terminal device establishes a connection with the second AS according to the address information of the second AS.
  • step 508 For the specific content of this step, reference may be made to step 508, which will not be repeated here.
  • Step 909 The terminal device sends a response message.
  • the terminal device sends a response message to the AF through the SMF as an example for description, and the description in step 509 may be referred to, which will not be repeated here.
  • the terminal device may also directly send a response message to the AF or the first AS.
  • the terminal device may also directly send a response message to the AF or the first AS.
  • the terminal device may also directly send a response message to the AF or the first AS.
  • step 707 or step 807 in the previous embodiment please refer to the description of step 707 or step 807 in the previous embodiment, which will not be repeated here.
  • Step 910 Perform state transition between the first AS and the second AS.
  • step 511 For the specific content of this step, reference may be made to step 511, which will not be repeated here.
  • Step 911 The terminal device receives fourth indication information.
  • the fourth indication information is used to instruct the terminal equipment to resume uplink transmission.
  • the terminal device receives the fourth indication information sent by the core network device as an example for description. For details, reference may be made to the description in step 513 in the previous embodiment.
  • the terminal device may also receive the fourth indication information sent by the AF or the first AS.
  • the terminal device may also receive the fourth indication information sent by the AF or the first AS.
  • the fourth indication information sent by the AF or the first AS please refer to the description of step 709 or step 809 in the previous embodiment, which will not be repeated here.
  • the fourth indication information may also be sent by the second AS to the terminal device.
  • the terminal device may send the uplink data to the second AS through the link established with the second AS.
  • the data path between the terminal device and the second AS is: the terminal device, the second ULCL, and the second PSA.
  • the terminal device and the first network device may include a hardware structure and/or a software module, and the above may be implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • a hardware structure a hardware structure plus a software module.
  • Each function Whether a certain function among the above-mentioned functions is executed by a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the functional modules in the various embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more modules may be integrated in one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software function modules.
  • an embodiment of the present application further provides an apparatus 1000 for implementing the functions of the terminal device or the network device in the above-mentioned method.
  • the device may be a software module or a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the device 1000 may include: a processing module 1001 and a communication module 1002.
  • the communication module 1002 may also be referred to as a transceiver module, and may include a sending module and/or a receiving module, which are respectively used to perform the sending and receiving steps of the terminal device or the first network device in the above method embodiment.
  • the apparatus 1000 can implement the steps or processes corresponding to the terminal device or the network device in the above method embodiment, which will be described separately below.
  • the communication module 1002 is used to determine the updated information of the user plane path of the terminal device
  • the processing module 1001 is configured to, when the application server determined to be the application service of the terminal device according to the update information is changed from the first application server AS to the second AS, and instruct the terminal device to stop sending the terminal device through the communication module 1002.
  • the uplink data of the application is configured to, when the application server determined to be the application service of the terminal device according to the update information is changed from the first application server AS to the second AS, and instruct the terminal device to stop sending the terminal device through the communication module 1002.
  • the uplink data of the application is configured to, when the application server determined to be the application service of the terminal device according to the update information is changed from the first application server AS to the second AS, and instruct the terminal device to stop sending the terminal device through the communication module 1002.
  • the uplink data of the application is configured to, when the application server determined to be the application service of the terminal device according to the update information is changed from the first application server AS to the second AS, and instruct the terminal device to stop sending the terminal device through the communication module 1002.
  • the uplink data of the application is
  • the communication module 1002 is further configured to:
  • the application identifier of the application is sent to the terminal device, where the application identifier is used to indicate the application that needs to switch the application server.
  • the communication module 1002 is specifically configured to:
  • Send a first message to the second network device includes first indication information, and the first indication information is used to instruct the second network device to send second indication information to the terminal device. 2.
  • the indication information is used to instruct the terminal device to stop sending the uplink data of the application;
  • the terminal device sends a first message to the terminal device; the first message includes the second indication information.
  • the first message further includes address information of the second AS.
  • the communication module 1002 is further configured to:
  • the communication module 1002 is further configured to:
  • the second AS When it is determined that the second AS has acquired the application layer status information of the terminal device, it instructs the terminal device to resume sending the uplink data of the application; the application layer status information is used to process all the terminal device status information. Information about the application.
  • the communication module 1002 is specifically configured to:
  • the second message includes third indication information, and the third indication information is used by the second network device to send fourth indication information to the terminal device, the The fourth indication information is used to instruct the terminal device to resume sending the uplink data of the application;
  • the communication module 1002 is specifically configured to:
  • the device is a network element that manages the first AS and the second AS, or when the device is the first AS, receiving the update information from the second network device;
  • the device is a session management function SMF
  • the user plane path of the terminal device is updated, and the update information is obtained.
  • the communication module 1002 is configured to receive second indication information; the second indication information instructs the terminal device to stop sending uplink data of the application;
  • the processing module 1001 is configured to stop sending the uplink data of the application according to the second instruction information.
  • the communication module 1002 is further configured to:
  • the device further includes:
  • the communication module 1002 is further configured to:
  • the communication module 1002 is further configured to:
  • the second AS is a new AS that provides services for the application; establish a connection with the second AS according to the address information of the second AS.
  • the communication module 1002 is further configured to:
  • the communication module 1002 is configured to receive first indication information or second indication information, where the first indication information is used to instruct the second network device to send second indication information to the terminal device, and the second indication information is used for To instruct the terminal device to stop sending the uplink data of the application;
  • the processing module 1001 is configured to generate the second indication information when the communication module 1002 receives the first indication information
  • the communication module 1002 is configured to send the second instruction information to the terminal device.
  • the communication module 1002 is further configured to:
  • the second AS is a new AS that provides services for the application
  • the communication module 1002 is further configured to:
  • the third instruction information is used for the second network device to send fourth instruction information to the terminal device;
  • the fourth instruction information is used for instructing the terminal device to recover Sending uplink data of the application; sending the fourth indication information to the terminal device.
  • the communication module 1002 is further configured to:
  • the communication module 1002 is further configured to:
  • the communication module 1002 is also used to:
  • FIG. 11 shows an apparatus 1100 provided by an embodiment of the application, and the apparatus shown in FIG. 11 may be a hardware circuit implementation of the apparatus shown in FIG. 10.
  • the communication device can perform the functions of the terminal device or the first network device or the second network device in the foregoing method embodiment.
  • FIG. 11 only shows the main components of the communication device.
  • the apparatus 1100 shown in FIG. 11 includes at least one processor 1120, configured to implement any method in FIG. 2 provided in an embodiment of the present application.
  • the device 1100 may further include at least one memory 1130 for storing program instructions and/or data.
  • the memory 1130 and the processor 1120 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1120 may operate in cooperation with the memory 1130.
  • the processor 1120 may execute program instructions stored in the memory 1130. At least one of the at least one memory may be included in the processor.
  • each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the steps of the method disclosed in combination with the embodiments of the present application may be embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments may be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processing circuit (digital signal processor, DSP), a dedicated integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processing circuit
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • Programming logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the apparatus 1100 may further include a communication interface 1110 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 1100 can communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
  • the transceiver when the communication interface is a transceiver, the transceiver may include an independent receiver and an independent transmitter; it may also be a transceiver with integrated transceiver functions, or an interface circuit.
  • the device 1100 may also include a communication line 1140.
  • the communication interface 1110, the processor 1120, and the memory 1130 may be connected to each other through a communication line 1140;
  • the communication line 1140 may be a peripheral component interconnection standard (peripheral component interconnect, PCI for short) bus or an extended industry standard architecture (extended industry standard architecture) , Referred to as EISA) bus and so on.
  • the communication line 1140 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • An embodiment of the present application also provides a system, as shown in FIG. 12, which includes a first network device 1201, a terminal device 1202, and a second network device 1203.
  • the terminal device 1202, and the second network device 1203 For the specific functions of the first network device 1201, the terminal device 1202, and the second network device 1203, reference may be made to the description in the previous embodiment, which will not be repeated here.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

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

Abstract

本申请提供一种数据传输方法、装置及系统，其中方法包括：当第一网络设备根据终端设备的用户面路径的更新信息，确定为所述终端设备的应用服务的应用服务器由第一AS变更为第二AS时，可以指示所述终端设备停止发送所述应用的上行数据。通过这种方法，可以避免应用服务器切换过程中，终端设备的数据出现丢失的问题。

Description

一种数据传输方法、装置及系统
相关申请的交叉引用
本申请要求在2020年03月25日提交中国专利局、申请号为202010218174.0、申请名称为“一种数据传输方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据传输方法、装置及系统。
背景技术
在5G系统中，例如新无线(new radio，NR)系统，引入了用户面功能(User Plane Function，UPF)负责终端设备数据的转发。为此，5G系统中可以支持在一个协议数据单元(Protocol Data Unit，PDU)会话的用户面路径上插入多个会话锚点UPF，以支持到本地数据网络(data network，DN)的连接，从而使得终端设备可以就近访问本地DN中的应用。参考图1所示，终端设备与DN之间包括多个UPF，其中UPF1可以作为上行分流器(uplink classifier，ULCL)或分支点(branching point，BP)；UPF2和UPF3可以作为PDU会话锚点(PDU session anchor，PSA)。为了描述方便，以下将UPF1称为ULCL/BP，将UPF2称为PSA1，将UPF3称为PSA2。
图1中，ULCL/BP可以将从终端设备收到的上行数据包根据分发规则分发给PSA1或PSA2，并将从PSA1或PSA2收到的数据包发送给终端设备；PSA1和PSA2分别与不同DN连接，DN可以位于多址边缘计算(Multi-access Edge Computing，MEC)中。MEC中可以包括多个应用服务器(Application Server，AS)。
在图1中，假设初始时，终端设备可以通过ULCL/BP接入MEC1中的AS1，当终端设备移出MEC1的服务区域，移入MEC2的服务区域时，AS1可能无法为终端设备提供应用层服务。为此，需要将终端设备连接到MEC2中的AS2，以便继续为终端设备提供应用层服务。然而在现有技术中，只有保证切换前的AS1和切换后的AS2的互联网协议(internet protocol，IP)地址相同，且切换后的终端设备的IP地址不变时，才能保证切换过程中数据包不会丢失。显然，上述切换条件在很多情况下是不能满足的。
发明内容
本申请实施例提供一种数据传输方法、装置及系统，用以解决如何保证切换应用服务器过程中数据包不会丢失的问题。
第一方面，本申请提供一种数据传输方法，该方法包括：第一网络设备确定终端设备的用户面路径的更新信息；当所述第一网络设备根据所述更新信息确定为所述终端设备的应用服务的应用服务器由第一应用服务器AS变更为第二AS，指示所述终端设备停止发送所述应用的上行数据。
上述方法中，通过在切换AS时，指示终端设备停止发送上行数据，可以避免切换过 程中出现数据丢失的问题。而且该方法不需要迁移应用对应的链路层状态，支持终端设备的IP地址改变，也不需要AS的IP地址在不同的MEC中保持一致。
在一种可能的实施方式中，所述方法还包括：所述第一网络设备向所述终端设备发送所述应用的应用标识，所述应用标识用于指示需要切换应用服务器的应用。
在一种可能的实施方式中，所述第一网络设备指示所述终端设备停止发送所述应用的上行数据，包括：所述第一网络设备向第二网络设备发送第一消息；所述第一消息包括第一指示信息，所述第一指示信息用于指示所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示所述终端设备停止发送所述应用的上行数据；或者，所述第一网络设备通过所述第二网络设备向所述终端设备发送所述第一消息；所述第一消息包括所述第二指示信息；或者，所述第一网络设备向所述终端设备发送第一消息；所述第一消息包括所述第二指示信息。
在一种可能的实施方式中，所述第一消息还包括所述第二AS的地址信息。
在一种可能的实施方式中，所述方法还包括：所述第一网络设备指示所述终端设备恢复发送所述应用的上行数据。
在一种可能的实施方式中，所述第一网络设备指示所述终端设备恢复发送所述应用的上行数据，包括：当所述第一网络设备确定所述第二AS获取到所述终端设备的应用层状态信息，则指示所述终端设备恢复发送所述应用的上行数据；所述应用层状态信息被用于处理所述终端设备的所述应用的信息。
在一种可能的实施方式中，所述第一网络设备指示所述终端设备恢复发送所述应用的上行数据，包括：所述第一网络设备向第二网络设备发送所述第二消息；所述第二消息包括第三指示信息，所述第三指示信息用于所述第二网络设备向所述终端设备发送第四指示信息，所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；或者，所述第一网络设备通过所述第二网络设备向所述终端设备发送所述第二消息；所述第二消息包括所述第四指示信息或所述第二消息用于指示所述终端设备恢复发送所述应用的上行数据；或者，第一网络设备向所述终端设备发送所述第二消息；所述第二消息包括第四指示信息；或者额，第一网络设备向所述终端设备发送第二消息；所述第二消息用于指示所述终端设备恢复发送所述应用的上行数据。
在一种可能的实施方式中，所述第一网络设备确定终端设备的用户面路径的更新信息，包括：所述第一网络设备为管理所述第一AS以及所述第二AS的网元时，或者所述第一网络设备为所述第一AS时，所述第一网络设备接收来自所述第二网络设备的所述更新信息；或者，所述第一网络设备为会话管理功能SMF时，所述第一网络设备对所述终端设备的用户面路径进行更新，并获得所述更新信息。
在一种可能的实施方式中，所述方法还包括：所述第一网络设备发送第五指示消息，第五指示消息用于指示所述应用不能被迁移。
在一种可能的实施方式中，所述第一网络设备为SMF，所述方法还包括：所述第一网络设备接收所述第一指示信息或第二指示信息，所述第一网络设备向所述终端设备发送所述第二指示信息；所述第一网络设备接收所述第三指示信息或第四指示信息，所述第一网络设备向所述终端设备发送所述第四指示信息。
第二方面，本申请还提供一种通信装置，该通信装置具有实现上述第一方面提供的任 一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或单元。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中第一网络设备的相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括通信接口，该通信接口用于支持该通信装置与其它设备之间的通信。
在一种可能的实现方式中，该通信装置包括相应的功能模块，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
在一种可能的实施方式中，通信装置的结构中包括处理模块和通信模块，这些功能模块可以执行上述方法示例中相应功能，具体参见第一方面提供的方法中的描述，此处不做赘述。
第三方面，本申请提供一种数据传输方法，包括：终端设备接收第二指示信息；所述第二指示信息指示所述终端设备停止发送所述应用的上行数据；所述终端设备根据所述第二指示信息停止发送所述应用的上行数据。
上述方法中，通过在切换AS时，指示终端设备停止发送上行数据，可以避免切换过程中出现数据丢失的问题。而且该方法不需要迁移应用对应的链路层状态，支持终端设备的IP地址改变，也不需要AS的IP地址在不同的MEC中保持一致。
在一种可能的实施方式中，所述方法还包括：所述终端设备接收所述应用的应用标识，所述应用标识用于指示需要切换应用服务器的应用。
在一种可能的实施方式中，所述方法还包括：所述终端设备存储所述应用的上行数据。
在一种可能的实施方式中，所述方法还包括：所述终端设备接收第四指示信息，所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；所述终端设备根据所述第四指示信息恢复发送所述应用的上行数据。
在一种可能的实施方式中，所述方法还包括：所述终端设备接收第二应用服务器AS的地址信息；所述第二AS为新的为所述应用提供服务的AS；所述终端设备根据所述第二AS的地址信息与所述第二AS建立连接。
在一种可能的实施方式中，所述方法还包括：所述终端设备通过所述连接向所述第二AS发送上行数据。
第四方面，本申请还提供一种通信装置，该通信装置具有实现上述第三方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或单元。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中终端设备的相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括通信接口，该通信接口用于支持该通信装置与其它设备之间的通信。
在一种可能的实现方式中，该通信装置包括相应的功能模块，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
在一种可能的实施方式中，通信装置的结构中包括处理模块和通信模块，这些功能模块可以执行上述方法示例中相应功能，具体参见第三方面提供的方法中的描述，此处不做赘述。
第五方面，本申请提供了一种数据传输方法，包括：第二网络设备接收第一指示信息或第二指示信息，所述第一指示信息用于指示所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示终端设备停止发送所述应用的上行数据；所述第二网络设备向所述终端设备发送所述第二指示信息。
在一种可能的实施方式中，所述方法还包括：所述第一网络设备接收第二应用服务器AS的地址信息；所述第二AS为新的为所述应用提供服务的AS；所述第二网络设备向所述终端设备发送所述第二AS的地址信息。
在一种可能的实施方式中，所述方法还包括：所述第二网络设备接收第三指示信息或第四指示信息；所述第三指示信息用于所述第二网络设备向所述终端设备发送第四指示信息；所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；所述第二网络设备向所述终端设备发送所述第四指示信息。
在一种可能的实施方式中，所述方法还包括：所述第二网络设备对所述终端设备的用户面路径进行更新，并获得更新信息；所述更新信息用于确定所述第二AS；所述第二网络设备向所述第一网络设备发送所述更新信息。
在一种可能的实施方式中，所述方法还包括：所述第二网络设备向所述终端设备发送所述应用的应用标识。
在一种可能的实施方式中，所述方法还包括：所述第二网络设备接收所述应用的应用标识。
第六方面，本申请还提供一种通信装置，该通信装置具有实现上述第五方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或单元。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中第二网络设备的相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括通信接口，该通信接口用于支持该通信装置与其它设备之间的通信。
在一种可能的实现方式中，该通信装置包括相应的功能模块，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
在一种可能的实施方式中，通信装置的结构中包括处理模块和通信模块，这些功能模块可以执行上述方法示例中相应功能，具体参见第五方面提供的方法中的描述，此处不做赘述。
第七方面，本申请提供了一种系统，包括：第一网络设备，用于确定终端设备的用户面路径的更新信息；根据所述更新信息确定为所述终端设备的应用服务的应用服务器由第一应用服务器AS变更为第二AS，则向第二网络设备发送第一指示信息或第二指示信息；所述第一指示信息用于所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示终端设备停止发送所述应用的上行数据；所述第二网络设备，用于接收所述第一指示信息或所述第二指示信息；向所述终端设备发送所述第二指示信息；所述终端 设备，用于接收第二指示信息；根据所述第二指示信息停止发送所述应用的上行数据。
第八方面，本申请提供一种通信装置，所述通信装置包括处理器，当所述处理器执行存储器中的计算机程序或指令时，如第一方面或第三方面或第五方面所提供的方法被执行。
第九方面，本申请提供一种通信装置，所述通信装置包括处理器和存储器，所述存储器用于存储计算机程序或指令；所述处理器用于执行所述存储器所存储的计算机程序或指令，以使所述通信装置执行如第一方面或第三方面或第五方面所提供的方法被执行。
第十方面，本申请提供一种通信装置，所述通信装置包括处理器、存储器和收发器，所述收发器，用于接收信号或者发送信号；所述存储器，用于存储计算机程序或指令；所述处理器，用于从所述存储器调用所述计算机程序或指令执行如第一方面或第三方面或第五方面所提供的方法被执行。
第十一方面，本申请提供一种通信装置，所述通信装置包括处理器和通信接口，所述通信接口，用于接收代码指令并传输至所述处理器；所述处理器运行所述代码指令以执行如第一方面或第三方面或第五方面所提供的方法被执行。
第十二方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序或指令，当计算机读取并执行所述计算机程序或指令时，使得第一方面或第三方面或第五方面所提供的方法被实现。
第十三方面，本申请提供一种包括指令的计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得第一方面或第三方面或第五方面所提供的方法被实现。
第十四方面，本申请提供一种芯片，包括处理器，所述处理器与存储器耦合，用于执行所述存储器中存储的计算机程序或指令，当所述处理器执行所述计算机程序或指令时，使得第一方面或第三方面或第五方面所提供的方法被实现。
附图说明
图1为现有技术中的一种5G网络架构示意图；
图2为适用于本申请实施例的一种5G网络架构示意图；
图3为适用于本申请实施例的另一种系统架构示意图；
图4为本申请实施例提供的一种数据传输流程示意图；
图5为本申请实施例提供的一种数据传输流程示意图；
图6为本申请实施例提供的一种数据传输流程示意图；
图7为本申请实施例提供的一种数据传输流程示意图；
图8为本申请实施例提供的一种数据传输流程示意图；
图9为本申请实施例提供的一种数据传输流程示意图；
图10为本申请实施例提供的一种通信装置结构示意图；
图11为本申请实施例提供的一种通信装置结构示意图；
图12为本申请实施例提供的一种通信系统示意图。
具体实施方式
下面结合说明书附图对本申请实施例做详细描述。
图2示例性示出了适用于本申请实施例的一种5G网络架构示意图，如图2所示，在 5G网络架构中，终端设备201可以经接入网(Access Network，AN)202与核心网进行通信，终端设备可以指用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端等。图2中为方便描述，只示例出1个终端，实际网络中，可能存在多个终端共存，在此不再赘述。
AN也可以称之为无线接入网(Radio Access Network，RAN)，以下统称为AN，主要负责为终端设备201提供无线连接，保证终端设备201的上下行数据的可靠传输等。接入网实体202可为5G系统中的gNB(generation Node B)，还可以是长期演进(Long Term Evolution，LTE)系统中的演进型基站(Evolutional Node B，eNB或eNodeB)等。
会话管理功能(Session Management Function，SMF)203，主要负责为终端设备201建立会话、管理会话等。可以根据终端设备201的位置信息为终端设备201选择合适的UPF。
UPF204，是终端设备201用户面的功能网元，主要功能包括分组路由和转发，用户面数据的服务质量(Quality of Service，QoS)处理等。
接入和移动性管理(Access and Mobility Management Function,AMF)205，主要功能包括无线接入网络控制平面的终结点，非接入信令的终结点，移动性管理，合法监听，接入授权或鉴权等。
策略控制功能(Policy Control Funtion，PCF)206，主要负责用户面传输路径的建立、释放和更改等功能。
鉴权服务器功能(Authentication Server Function，AUSF)207，其主要功能包括用户鉴权等。
用户数据管理(User Data Management，UDM)208，主要负责管理用户的签约数据等。
数据网络(Data Network，DN)209可以是指为终端设备201提供服务的网络。
应用服务器(application server，AS)210，可以为终端设备中的应用(application)提供数据服务。
图2中还示出了各个实体中的接口的可能实现方式，比如AN202和AMF209之间的N2接口，AN202与UPF204之间的N9接口等，在此不再一一赘述。
在图2所示的架构的基础上，5G还支持在一个PDU会话的用户面路径上插入多个会话锚点UPF，以支持到本地DN的连接，从而使得终端设备可以就近访问本地DN中的应用，具体可以如图3所示。
图3中，终端设备到DN之间可以包括多个UPF。举例来说，图3中，终端设备到DN之间的传输路径可以包括ULCL/BP、PSA1；终端设备到DN之间的传输路径还可以包括ULCL/BP、PSA2，其中ULCL/BP、PSA1以及PSA2均由UPF实现。需要说明的是，图3中仅以一个传输路径中包括一个PDU会话锚点为例进行说明，在实际应用中，终端设备与DN之间的一个传输路径中还可能包括多个PDU会话锚点，在此不再赘述。
图3中，ULCL/BP可以将从终端设备收到的上行数据包根据分发规则分发给PSA1或PSA2，并将从PSA1或PSA2收到的数据包发送给终端设备；PSA1和PSA2分别与DN连接，DN可以位于多址边缘计算(Multi-access Edge Computing，MEC)中。MEC中可以包 括多个应用服务器(Application Server，AS)。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例中部分场景以无线通信网络中NR网络的场景为例进行说明，应当指出的是，本申请实施例中的方案还可以应用于其他无线通信网络中，相应的名称也可以用其他无线通信网络中的对应功能的名称进行替代。
参见图4，为本申请实施例提供的一种数据传输方法流程示意图。该方法包括：
步骤401：第一网络设备确定终端设备的用户面路径的更新信息；
上述终端设备的用户面路径的更新信息包括终端设备的新路径的信息。示例性的，该新路径的信息可以是该新路径所对应的数据网络接入标识(Data Network Access Identifier，DNAI)。
在一种实现方式中，第一网络设备可以接收通知消息，所述通知消息用于通知所述终端设备的用户面路径改变。示例性的，该通知消息是早通知消息(Early Notification)或者晚通知消息(Late Notification)。
示例性的，该通知消息包括该新路径的DNAI。示例性的，该更新信息可以包括多个新路径的信息，相应地，通知消息也包括该多个新路径的DNAI。
步骤402：第一网络设备根据所述更新信息确定为所述终端设备的应用服务的应用服务器由第一AS变更为第二AS，则指示所述终端设备停止发送所述应用的上行数据；
示例性的，第一网络设备根据一个或多个新路径的DNAI确定新路径所对应的位置是否部署了该应用的第二AS。进一步的，第一网络设备确定该新路径所对应的位置所部署的第二AS是否可以更好地服务该终端设备，例如，第一网络设备可以根据该应用服务与终端间的路径(例如，路径更短)、时延、负荷等信息确定是否将该终端的该应用服务的第一AS变更为第二AS。
本申请实施例中，第一网络设备可以通过多种方式指示终端设备停止发送所述应用的上行数据。
第一种可能的实现方式中，第一网络设备可以发送第一指示信息，通过第一指示信息进行指示，具体可以参考步骤403以及步骤404。
可选的，步骤403：第一网络设备向第二网络设备发送第一指示信息；
其中，第一指示信息用于指示所述第二网络设备指示终端设备停止发送所述应用的上行数据，或者，第一指示信息用于指示所述第二网络设备发送第二指示信息；第二指示信息指示所述终端设备停止发送所述应用的上行数据。
可选的，步骤404：第二网络设备接收第一指示信息，并根据所述第一指示信息向终端设备发送第二指示信息。
第二种可能的实现方式中，第一网络设备可以通过第二网络设备发送第二指示信息，具体可以参考步骤405以及步骤406。
可选的，步骤405：第一网络设备向第二网络设备发送第二指示信息；
其中，第二指示信息指示所述终端设备停止发送所述应用的上行数据。
在这种情况下，第二指示信息由第二网络设备透传，第二网络设备可以不解析第一指 示信息的内容。
可选的，步骤406：第二网络设备接收第二指示信息，并向终端设备发送第二指示信息。
可选的，示例性的，该第二网络设备可以是核心网设备，例如是SMF，也可以是其他网络设备，例如是PCF或NEF。当然，第二网络设备也可以是其他核心网设备，例如，第二网络设备可以是AMF设备，本申请实施例不限定。
第三种可能的实现方式中，第一网络设备可以直接向终端设备发送第二指示信息，具体可以参考步骤407。
可选的，步骤407：第一网络设备向终端设备发送第二指示信息。
示例性的，第一网络设备还可以向第二网络设备发送第二AS的地址信息，并由第二网络设备向终端设备发送第二AS的地址信息；或，第一网络设备直接向终端设备发送第二AS的地址信息。
可选的，第一网络设备还可以向第二网络设备该应用的应用标识，并由第二网络设备向终端设备发送该应用标识；或，第一网络设备直接向终端设备发送该应用的应用标识。终端设备可以根据应用的标识确定该第二AS所对应的所述应用。示例性的，应用标识可以是第一AS的地址信息，例如，全限定域名(Fully Qualified Domain Name，FQDN)或网际互连协议(Internet Protocol，IP)地址，应用标识也可以仅仅是用于指示该应用的标识。
步骤408：终端设备接收第二指示信息。
其中，所述第二指示信息指示所述终端设备停止发送所述应用的上行数据。
步骤409：终端设备根据所述第二指示信息停止发送所述应用的上行数据；
可选的，终端设备还可以获取第二AS的地址信息，终端设备可以与所述第二AS建立连接。
终端设备可以根据第二AS的地址信息与第二AS件建立连接。示例性的，该连接可以包括链路层连接，或者，该连接也可以包括应用层连接。
可选的，终端设备缓存从终端设备上的该应用收到的该应用的上行数据。
需要说明的是，上述步骤408、步骤409间没有必然的先后顺序。
需要说明的是，终端设备可以包括代理模块(或中间层)，在上述步骤408、步骤409中，由终端设备上的代理模块进行处理，即该代理模块接收第二指示信息，该代理模块停止发送应用的上行数据，该代理模块与第二AS建立连接，该代理模块停止发送该应用的上行数据、并缓存从应用接收到的上行数据。示例性的，终端设备上的应用将所有上行数据均发送给该代理模块，并由该代理模块发送给应用服务器，并且，该代理模块从应用服务器接收下行数据并发送给该终端设备上的应用。该代理模块可以向应用屏蔽应用服务器由第一AS变为第二AS，使得应用不感知应用服务器的变化，可以在终端设备移动与应用服务器已经建立连接后仍然可以重选应用服务器，并且减少对应用的影响。
上面的流程中，当确定将为所述终端设备的应用服务的服务器由第一AS变更为第二AS之后，通过指示终端设备停止发送所述应用的上行数据，可以避免在服务器切换过程中出现数据丢包的发生，保证服务质量。
图4所示的流程中，第一网络设备以及第二网络设备可以存在不同实现方式，举例来说，第一网络设备可以为管理第一AS以及第二AS的AF，还可以为第一AS，还可以为 SMF等，第二网络设备为核心网设备。第一网络设备为不同类型的设备时，图4的流程可能存在多种实现方式，下面分不同情况详细描述图4中的流程。
实施例一：
结合图4中的流程，实施例一中，第一网络设备为管理第一AS以及第二AS的AF，第二网络设备为核心网设备，其中，核心网设备可以是SMF，或者，也可以是PCF、NEF以及AMF等。在实施例一中，第二网络设备确定更新信息，第一网络设备根据更新信息确定第二AS，并通过第二网络设备向终端设备指示第二AS，下面将详细描述。
如图5所示，图5中以应用功能(application function，AF)为终端设备选择切换后的AS为例进行说明，AF可以管理多个AS，例如管理第一AS以及第二AS等，图5中的ULCL也可以采用BP实现，在此不再赘述。
在步骤500之前，终端设备与第一MEC中的第一AS建立了连接，为终端设备提供服务的是第一MEC中的第一AS，终端设备通过第一ULCL、第一PSA将数据发送给第一AS。终端设备移动到第二MEC之后，需要从第二MEC中确定为终端设备提供服务的第二AS，下面将详细描述。
步骤500：SMF接收数据网络接入标识(Data Network Access Identifier，DNAI)不变指示。
具体的，AF可以给PCF或者网络开放功能(Network Exposure Function，NEF)发送为终端设备提供服务的应用是否支持切换的指示，若AF指示该应用不支持切换，则PCF/NEF可以向SMF发送DNAI不变指示，DNAI不变指示用于指示该应用需要保持DNAI不变。
此外，AF可以订阅早通知(early notification)和晚通知(late notification)，当终端设备与该应用之间的PDU会话路径改变时，SMF可以向AF发送相应的通知。
需要说明的是，图5中显示了AF与SMF的直接连接，在实际部署时，AF可以通过PCF或者网络开放功能(Network Exposure Function，NEF)与SMF连接，即AF将消息发送给PCF/NEF。PCF/NEF对AF的消息进行相应的转换后再向SMF发送消息。图5只是示例，图5中未体现PCF/NEF向SMF发送的消息。
在本申请实施例中，AF可以是集中管理所有AS的网元，AF也可以是第一AS，或者AF是第一AS所在第一MEC的平台等，具体不做限制。
步骤501：SMF选择第二ULCL和第二PSA。
当终端设备移动到第二MEC的服务区域后，SMF确定在第二MEC中选择第二ULCL和第二PSA。若AF向SMF订阅了early notification，SMF在选择了第二ULCL和第二PSA后，可以不立即插入第二ULCL和第二PSA。此时即，终端设备的用户面路径保持不变，终端设备还是经过第一ULCL和第一PSA之后，与第一AS通信。
步骤502：SMF向AF发送早通知。
SMF在早通知中将终端设备与第一AS之间的用户面路径的更新信息发送给AF，更新信息可以是第二PSA所连接的第二MEC对应的至少一个DNAI。
需要说明的是，SMF可以选择多个本地PSA，这些本地PSA分别与不同的MEC对应，本地PSA包括第二PSA。更新信息包括本地PSA中每个PSA所连接的MEC对应的DNAI，本申请实施例对此不限定。
在该实施例中，可以由AF确定终端设备中的应用切换后的AS，具体可以参考步骤 503的描述。
步骤503：AF选择第二AS。
AF根据更新信息确定是否选择第二AS，若AF确定选择第二AS，则AF根据更新信息选择第二AS。举例来说，AF可以根据更新信息确定第二AS的位置，例如，当更新信息是第二MEC对应的至少一个DNAI时，AF从该至少一个DNAI对应的第二MEC中选择一个可用的AS作为第二AS。具体的，AS在上线时可注册到AF中，这样AF可以保存所有在线AS以及该AS所对应的DNAI的信息，或者，当AF可以查询该至少一个DNAI对应的第二MEC中的DNS服务器，从而可以获得第二MEC中所有可用的AS的地址，AF从而可以选择一个AS作为第二AS，具体选择过程并不限定，在此不再赘述。
在该实施例中，AF确定第二AS之后，AF可以通过核心网设备向终端设备指示第二AS，并指示终端设备停止发送所述应用的上行数据，具体可以参考步骤504至506中的描述。
步骤504：AF向核心网设备发送第一消息。
AF可以向核心网设备发送第一消息，第一消息可以包括第二AS的地址信息。
可选的，AF还可以向核心网设备发送该应用的应用标识，以便根据该应用标识确定第二AS所对应的应用。
若为终端设备提供服务的应用存在对应的应用层状态信息，且在应用服务器切换时需要暂停接收上行数据时，第一种实现方式中，AF可以向核心网设备发送第一指示信息。该第一指示信息用于指示核心网设备向终端设备发送第二指示信息，第二指示信息用于指示终端设备暂停向第一AS发送上行数据。
第二种实现方式中，第一消息还包括第二指示信息。在该实现方式中，SMF不解析该第一消息，核心网设备将该第一消息直接透传给终端设备，若第一消息经过PCF/NEF时，PCF/NEF也不解析第一消息。
可选的，该第一消息还可以包括关联标识，关联标识用于第二AS将终端设备与第二AS间建立的链路与从第一AS收到的应用层状态信息关联。
需要说明的是，应用层状态信息可以被用于处理所述终端设备的所述应用的信息。应用层状态信息可以包括但不限于终端设备的上下文信息、应用当前的状态信息等。举例来说，应用为购物应用时，应用状态信息可以包括付款状态、订单信息等。终端设备切换到新的应用服务器时，新的应用服务器可根据应用状态信息确定用户是否已付款，若未付款，可给用户推送付款界面。
此外，第一指示信息、第二AS的地址信息等都可以封装在一个透明容器中，使得核心网设备(例如SMF或PCF等)不解析，AF指示核心网设备将该透明容器发送给终端设备。基于此，核心网设备可以将该透明容器发送给终端设备。以核心网设备为SMF为例，由SMF将该透明容器发送给终端设备。
需要说明的是，本实施例中以AF通过SMF向终端设备发送上述信息。在实际部署时，AF也可以通过AMF向终端设备发送上述信息，当AF通过AMF发送时，本实施例的步骤504、步骤506的SMF被替换为AMF，此外，通过AMF给UE发送的非接入层(non-access stratum，NAS)消息不是会话修改消息，而是其他类型的NAS消息。
当核心网网元是SMF时，AF可通过NEF/PCF将上述信息发送给SMF。当核心网设备是其他设备时，AF也可以通过NEF将上述信息发送给核心网设备，本发明不限定。
核心网设备不是SMF时，核心网设备还可以指示SMF在PDU会话路径中插入第二ULCL，具体如何指示，可以参考现有技术中的描述，本申请实施例对此并不限定。
步骤505：SMF在PDU会话路径中插入第二ULCL。
在步骤500中，SMF收到了该应用需要保持DNAI不变的指示，为此SMF可以指示第一ULCL和第二ULCL之间建立转发隧道，或者SMF可以指示第二ULCL到第一PSA之间建立转发隧道。
第一ULCL和第二ULCL之间建立转发隧道之后，终端设备与第一AS间的数据路径依次包括的设备为：终端设备、第二ULCL、第一ULCL、第一PSA；或者，第二ULCL到第一PSA之间建立转发隧道后，终端设备与第一AS间的数据路径依次包括的设备为：终端设备、第二ULCL、第一PSA。
该转发隧道可以使得在应用切换服务器之前，终端设备可以通过该转发隧道将该应用的数据发送给第一AS，最大限度地减少切换的时延。
步骤506：核心网设备向终端设备发送通知消息。
核心网设备通过所述通知消息将第二AS的地址信息发送给终端设备。该通知消息还包括应用标识，用于指示终端设备该第二AS所对应的应用。终端设备根据应用标识确定哪个应用需要切换应用服务器。
需要说明的是，本申请实施例中，终端设备中的“应用”，可以是以客户端形式安装在终端设备中程序，为了描述方便，以下的实施例中均统称为应用。
若核心网设备收到第一指示信息或第二指示信息时，核心网设备向终端设备发送第一指示信息。若核心网设备收到了关联标识，则核心网设备也将该关联标识发送给终端设备。
具体的，核心网设备可以给终端设备发送会话修改消息，在会话修改消息中将上述信息发送给终端设备。
步骤507：终端设备暂停发送上行数据。
为了支持AS迁移不影响终端设备上的应用，可以在终端设备上增加一个中间功能，即，代理(proxy)功能。终端设备的应用将所有发送给AS的消息发送给该proxy功能，由proxy功能再发送给AS。例如，当应用基于超文本传输协议(hyper text transfer protocol，HTTP)时，该proxy可以是HTTP proxy。当存在该proxy时，所有终端设备中的应用与AS间通信的消息均经过该proxy转发。
当终端设备上存在该proxy功能时，步骤505中SMF发送给终端设备的消息被发送给该proxy功能。该proxy功能可开启上行缓存功能，以便缓存终端设备中的与第一AS对应的应用发送的上行消息。
步骤508：终端设备根据第二AS的地址信息与第二AS间建立连接。
终端设备收到核心网设备的通知消息后，终端设备可发起与第二AS之间的连接建立。该过程建立了终端设备与第二AS之间的链路，例如，建立传输控制协议(Transmission Control Protocol，TCP)连接。
当终端设备包括Proxy功能时，Proxy功能与第二AS建立连接。
步骤508与步骤507的顺序并不限定，步骤508也可以在步骤507之前执行。
步骤509：终端设备向核心网设备发送响应消息。
可选的，终端设备可以将终端设备与第二AS之间的链路的链路信息在响应消息中发送给核心网设备。以终端设备与第二AS之间的链路的链路层协议是传输控制协议 (Transmission Control Protocol，TCP)为例，所述链路的链路信息可以包括TCP连接的源IP地址、源端口号、协议号等信息。
可选的，响应消息中还可以包括应用对应的应用标识或前面收到的关联标识。
第二AS从第一AS接收的应用层状态信息中包括链路信息、或应用标识或关联标识，第二AS根据应用层状态信息中的链路信息将应用层状态信息与该链路关联。若不发送链路信息，即，使用应用标识或关联标识关联链路与应用层状态信息，则终端设备还需要在该终端设备与第二AS建立的链路上发送该应用标识或关联标识，以便第二AS进行关联。
可选的，终端设备还可以将终端设备与第二AS之间的链路的链路信息、应用标识或关联标识封装在透明容器中发送至核心网设备，核心网设备可以不解析该透明容器，透传给AF。
可选的，终端设备还可以直接通过终端设备与第二AS之间的链路将应用标识或关联标识发送至第二AS，以便第二AS根据该链路对应的应用标识或关联标识将该链路与从第一AS接收的应用层状态信息(包括应用标识或关联标识)关联。
可选的，终端设备还可以将终端设备与第二AS之间的链路的链路信息发送给第一AS，再由第一AS在应用层状态信息中发送给第二AS。第二AS可根据应用层状态信息中的链路信息将应用层状态信息与该链路关联。
步骤510：核心网设备向AF发送晚通知。
可选的，若步骤509中的响应消息中包括链路信息、应用标识或关联标识，则SMF可以将链路信息、应用标识或关联标识通过所述晚通知发送给AF。
相应的，若AF接收到终端设备的链路信息、应用标识或关联标识，则AF将链路信息、应用标识或关联标识发送给第二AS。
当然，核心网设备也可以采用其他消息将上述信息发送给AF，本实施例不限定。
步骤511：第一AS与第二AS间进行状态迁移。
本申请实施例中，第一AS与第二AS间进行状态迁移之前，AF可以向第一AS指示第二AS的地址信息，第一AS从而可以根据第二AS的地址信息确定第二AS；或者，AF可向第二AS指示第一AS的地址信息、应用标识或关联标识，第二AS从而可以根据第一AS的地址信息、应用标识或关联标识从第一AS获取应用层状态信息。
在本申请实施例中，第一AS与第二AS间只需要迁移与终端设备相关的应用层状态信息，不需要迁移其他终端设备的状态，也不需要迁移链路层的状态。其中应用层状态信息中包括的内容为终端设备的上下文、应用标识或关联标识、终端设备与第二AS之间的链路层信息等信息。
具体的，第一AS可将该终端设备的应用层状态信息发送给第二AS。该应用层状态信息的发送，可以经过AF转发，或者在第一AS与第二AS间直接发送，或者通过其他途径发送，本申请实施例不限定。
若第二AF接收到终端设备的链路信息、应用标识或关联标识，则第二AS可以根据应用标识或关联标识将终端设备与第二AS之间的链路与从第一AS发送的应用层状态信息进行关联。
需要说明的是，第一AS与第二AS间状态迁移完成之后，第一AS和/或第二AS可以向AF发送指示消息，用于指示状态迁移完成。
AF还可以通过核心网设备指示终端设备恢复发送所述应用的上行数据，具体可以参考步骤512至步骤513的描述。
步骤512：AF发送第二消息。
其中，所述第二消息可以用于指示所述终端设备恢复发送所述应用的上行数据。举例来说，当AS状态迁移完成后，AF向核心网设备发送第二消息。其中，核心网设备可以是SMF，或者，也可以是PCF/NEF，或者AMF，或者，AF也可以通过PCF/NEF给SMF或AMF发送第二消息，本申请实施例不限定。
第一种实现方式中，第二消息包括第三指示信息，该第三指示信息用于核心网设备向终端设备发送第四指示信息，第四指示信息用于指示终端设备恢复上行发送，由于终端设备与第二AS建立了连接，第四指示信息也可以用于指示终端设备向第二AS发送上行数据。
第二种实现方式中，第二消息包括第四指示信息。在该实现方式中，核心网设备不解析第四指示信息，直接将第四指示信息发送给终端设备。
步骤513：核心网设备向终端设备发送第四指示信息。
可选的，也可以由AF直接向终端设备发送第四指示信息，或者还可以由第一AS或者第二AS向终端设备发送第四指示信息，本申请实施例并不限定。
当终端设备中存在proxy时，终端设备中的proxy在收到第四指示信息后，将缓存的上行数据通过步骤509建立的链路发送给第二AS。终端设备中的proxy将终端设备中的应用发送的上行数据发送给第二AS。第二AS获取到与应用标识或关联标识关联的应用层状态信息之后，第二AS可以通过该应用层状态信息处理来自终端设备的上行数据。
需要说明的是，终端设备与第二AS间的数据路径为：终端设备、第二ULCL、第二PSA，即终端设备发送的上行数据通过第二ULCL、第二PSA转发至第二AS；第二AS发送至终端设备的下行数据通过第二PSA、第二ULCL转发至终端设备。当然终端设备与第二AS间的数据路径中还可能存在多个PSA，在此不再赘述。
在图5所示的流程中，终端设备移动到第二MEC的服务区域后，由AF在第二MEC中为终端设备确定切换后的第二AS，可以保证终端设备就近接入第二AS。终端设备与第二AS通信之前，与第二AS建立了链路层连接，因此第一AS和第二AS之间仅需迁移应用层状态信息，不需要迁移应用对应的链路层状态，因此终端设备在切换至第二AS后，终端设备的IP地址可以变更，相应的，第二AS的IP地址也不需要和第一AS的IP地址保持一致。通过上述方法，可以实现在各种不同条件下为终端设备切换AS，保证了终端设备在移动过程中，随时切换到新的AS中，从而不会出现服务中断。
实施例一中，步骤505和步骤501可以同时执行，即SMF选择了第二ULCL和第二PSA之后，直接将选择的第二ULCL插入PDU会话路径中，下面结合图6进行描述。
实施例二：
结合图4中的流程，实施例二中，第一网络设备为管理第一AS以及第二AS的AF，第二网络设备为核心网设备，其中，核心网设备可以是SMF，或者，也可以是PCF、NEF以及AMF等。在实施例二中，第二网络设备确定更新信息，第一网络设备根据更新信息 确定第二AS，并通过第二网络设备向终端设备指示第二AS，下面将详细描述。
如图6所示，图6中以AF为终端设备选择切换后的AS为例进行说明，图6中的ULCL也可以采用BP实现，在此不再赘述。
在步骤600之前，终端设备与第一MEC中的第一AS建立了连接，为终端设备提供服务的是第一MEC中的第一AS，终端设备通过第一ULCL、第一PSA将数据发送给第一AS。终端设备移动到第二MEC之后，需要从第二MEC中确定为终端设备提供服务的第二AS，下面将详细描述。
步骤600：SMF接收DNAI不变指示。
具体的，AF可以给PCF或者NEF发送为终端设备提供服务的应用是否支持切换的指示，若AF指示该应用不支持切换，则PCF/NEF可以向SMF发送DNAI不变指示，DNAI不变指示用于指示该应用需要保持DNAI不变。
此外，AF可以订阅晚通知(late notification)，当终端设备与该应用之间的PDU会话路径改变时，SMF可以向AF发送相应的通知。
需要说明的是，图6中显示了AF与SMF的直接连接，在实际部署时，AF可以通过PCF或者网络开放功能(Network Exposure Function，NEF)与SMF连接，即AF将消息发送给PCF/NEF。PCF/NEF对AF的消息进行相应的转换后再向SMF发送消息。图6只是示例，图6中未体现PCF/NEF向SMF发送的消息。
在本申请实施例中，AF可以是集中管理所有AS的网元，AF也可以是第一AS，或者AF是第一AS所在第一MEC的平台等，具体不做限制。
步骤601：SMF选择第二ULCL和第二PSA，并在PDU会话路径中插入第二ULCL。
当终端设备移动到第二MEC的服务区域后，SMF确定在第二MEC中选择第二ULCL和第二PSA。SMF具体如何选择第二ULCL和第二PSA，本申请实施例对此并不限定，在此不再赘述。
在步骤600中，SMF收到了该应用需要保持DNAI不变的指示，为此SMF可以指示第一ULCL和第二ULCL之间建立转发隧道，或者SMF可以指示第二ULCL到第一PSA之间建立转发隧道。
第一ULCL和第二ULCL之间建立转发隧道之后，终端设备与第一AS间的数据路径为：终端设备、第二ULCL、第一ULCL、第一PSA；或者，第二ULCL到第一PSA之间建立转发隧道后，终端设备与第一AS间的数据路径为：终端设备、第二ULCL、第一PSA。
步骤602：SMF向AF发送晚通知。
SMF在晚通知中将终端设备与第一AS之间的用户面路径的更新信息发送给AF，更新信息可以是第二PSA所连接的第二MEC对应的至少一个DNAI。
需要说明的是，SMF可以选择多个本地PSA，这些本地PSA分别与不同的MEC对应，本地PSA包括第二PSA。更新信息包括本地PSA中每个PSA所连接的MEC对应的DNAI，本申请实施例对此不限定。
在该实施例中，可以由AF确定终端设备中的应用切换后的AS，具体可以参考步骤603的描述。
步骤603：AF选择第二AS。
AF根据更新信息确定是否选择第二AS，若AF确定选择第二AS，则AF根据更新信 息选择第二AS。举例来说，AF可以根据更新信息确定第二AS的位置，例如，当更新信息是第二MEC对应的至少一个DNAI时，AF从该至少一个DNAI对应的第二MEC中选择一个可用的AS作为第二AS。具体的，AS在上线时可注册到AF中，这样AF可以保存所有在线AS以及该AS所对应的DNAI的信息，或者，当AF可以查询该至少一个DNAI对应的第二MEC中的DNS服务器，从而可以获得第二MEC中所有可用的AS的地址，AF从而可以选择一个AS作为第二AS，具体选择过程并不限定，在此不再赘述。
在该实施例中，AF确定第二AS之后，AF可以通过SMF向终端设备指示第二AS，并指示终端设备停止发送所述应用的上行数据，具体可以参考步骤604至606中的描述。
步骤604：AF向核心网设备发送第一消息。
AF通过第一消息将第二AS的地址信息发送给核心网设备。
若为终端设备提供服务的应用存在对应的应用层状态信息，第一种实现方式中，第一消息还包括第一指示信息。该第一指示信息用于核心网设备向终端设备发送第二指示信息，第二指示信息用于指示终端设备暂停向第一AS发送上行数据。
第二种实现方式中，第一消息还包括第二指示信息。在该实现方式中，核心网设备不解析该第一消息，核心网设备该第一消息直接透传给终端设备，若第一消息经过其他核心网设备，如PCF/NEF时，其他核心网设备也不解析第一消息。
可选的，第一消息中还可以包括应用标识，应用标识用于指示需要切换应用服务器的应用。
可选的，该第一消息还可以包括关联标识，关联标识用于第二AS将终端设备与第二AS间建立的链路与从第一AS收到的应用层状态信息关联。
此外，第一指示信息、第二AS的地址信息等都可以封装在一个透明容器中，使得核心网设备(例如SMF或PCF)不解析，AF指示核心网设备(如SMF或PCF)将该透明容器发送给终端设备。基于此，核心网设备可以将该透明容器发送给终端设备。在该实施例中，可以以核心网设备为SMF为例，由SMF将该透明容器发送给终端设备。核心网设备也可以是其他网元，例如，AMF，本实施例不限定。
步骤605：核心网设备向终端设备发送第二AS的地址信息。
核心网设备还可以将应用标识发送给终端设备，该应用标识用于指示终端设备该第二AS所对应的应用。终端设备根据应用标识确定哪个应用需要切换应用服务器。
若核心网设备收到第一指示信息，核心网设备向终端设备发送第一指示信息或者第二指示信息。若核心网设备收到了关联标识，则核心网设备也将该关联标识发送给终端设备。
举例来说，若核心网设备是SMF，则SMF可以给终端设备发送会话修改消息，在会话修改消息中将上述信息发送给终端设备。
步骤606：终端设备暂停发送上行数据。
为了支持AS迁移不影响终端设备上的应用，可以在终端设备上增加一个中间功能，即，代理(proxy)功能。终端设备的应用将所有发送给AS的消息发送给该proxy功能，由proxy功能再发送给AS。例如，当应用基于超文本传输协议(hyper text transfer protocol，HTTP)时，该proxy可以是HTTP proxy。当存在该proxy时，所有终端设备中的应用与AS间通信的消息均经过该proxy转发。
当终端设备上存在该proxy功能时，步骤605中SMF发送给终端设备的消息被发送给该proxy功能。该proxy功能可开启上行缓存功能，以便缓存终端设备中与第一AS对应的 应用发送的上行消息。
步骤607：终端设备根据第二AS的地址信息与第二AS间建立连接。
终端设备收到第二AS的信息后，终端设备可发起与第二AS之间的连接建立。该过程建立了终端设备与第二AS之间的连接，例如，建立TCP连接。也可以建立与第二AS的应用层的连接。
步骤607与步骤606的顺序并不限定，步骤607也可以在步骤606之前执行。
步骤608：终端设备向核心网设备发送响应消息。
可选的，终端设备可以将终端设备与第二AS之间的链路的链路信息在响应消息中发送给核心网设备。以终端设备与第二AS之间的链路的链路层协议是传输控制协议(Transmission Control Protocol，TCP)为例，所述链路的链路信息可以包括TCP连接的源IP地址、源端口号、协议号等信息。
可选的，响应消息中还可以包括应用对应的应用标识或前面收到的关联标识。第二AS从第一AS接收的应用层状态信息中包括链路信息、或应用标识或关联标识，第二AS根据应用层状态信息中的链路信息将应用层状态信息与该链路关联。若不发送链路信息，即，使用应用标识或关联标识关联链路与应用层状态信息，则终端设备还需要在该终端设备与第二AS建立的链路上发送该应用标识或关联标识，以便第二AS进行关联。
可选的，终端设备还可以将终端设备与第二AS之间的链路的链路信息、应用标识或关联标识封装在透明容器中发送至核心网设备，核心网设备可以不解析该透明容器，透传给AF。
可选的，终端设备还可以直接通过终端设备与第二AS之间的链路将应用标识或关联标识发送至第二AS，以便第二AS根据该链路对应的应用标识或关联标识将该链路与从第一AS接收的应用层状态信息(包括应用标识或关联标识)关联。
可选的，终端设备还可以将终端设备与第二AS之间的链路的链路信息发送给第一AS，再由第一AS在应用层状态信息中发送给第二AS。第二AS可根据应用层状态信息中的链路信息将应用层状态信息与该链路关联。
步骤609：核心网设备向AF发送第一通知。
可选的，若步骤608中的响应消息中包括链路信息、应用标识或关联标识，则核心网设备可以将链路信息、应用标识或关联标识通过所述第一通知发送给AF。
相应的，若AF接收到终端设备的链路信息、应用标识或关联标识，则AF将链路信息、应用标识或关联标识发送给第二AS。
步骤610：第一AS与第二AS间进行状态迁移。
申请实施例中，第一AS与第二AS间进行状态迁移之前，AF可以向第一AS指示第二AS的地址信息，第一AS从而可以根据第二AS的地址信息确定第二AS；或者，AF可向第二AS指示第一AS的地址信息、应用标识或关联标识，第二AS从而可以根据第一AS的地址信息、应用标识或关联标识从第一AS获取应用层状态信息。
在本申请实施例中，第一AS与第二AS间只需要迁移与终端设备相关的应用层状态信息，不需要迁移其他终端设备的状态，也不需要迁移链路层的状态。其中应用层状态信息包括但不限于终端设备的上下文、应用标识或关联标识、终端设备与第二AS之间的链路层信息等信息。
具体的，第一AS可将该终端设备的应用层状态信息发送给第二AS。该应用层状态信 息的发送，可以经过AF转发，或者在第一AS与第二AS间直接发送，或者通过其他途径发送，本申请实施例不限定。
若第二AF接收到终端设备的链路信息、应用标识或关联标识，则第二AS可以根据应用标识或关联标识将终端设备与第二AS之间的链路与从第一AS发送的应用层状态信息进行关联。
AF还可以通过核心网设备指示终端设备恢复发送所述应用的上行数据，具体可以参考步骤611至步骤612的描述。
步骤611：当AS状态迁移完成后，AF向核心网设备发送第二消息。
其中，所述第二消息可以用于指示所述终端设备恢复发送所述应用的上行数据。举例来说，第一种实现方式中，第二消息包括第三指示信息，该第三指示信息用于指示核心网设备向终端设备发送第四指示信息，第四指示信息用于指示终端设备恢复上行发送，由于终端设备与第二AS建立了链路，第四指示信息也可以用于指示终端设备向第二AS发送上行数据。
第二种实现方式中，第二消息包括第四指示信息。在该实现方式中，核心网设备不解析第二消息，直接将第二消息发送给终端设备。
步骤612：核心网设备向终端设备发送第四指示信息。
该步骤具体可以参考步骤512所述。
当终端设备中存在proxy时，终端设备中的proxy在收到第四指示信息后，将缓存的上行数据通过步骤608建立的链路发送给第二AS。终端设备中的proxy将终端设备中的应用发送的上行数据通过链路发送给第二AS。
需要说明的是，终端设备与第二AS间的数据路径为：终端设备、第二ULCL、第二PSA，即终端设备发送的上行数据通过第二ULCL、第二PSA转发至第二AS；第二AS发送至终端设备的下行数据通过第二PSA、第二ULCL转发至终端设备。当然终端设备与第二AS间的数据路径中还可能存在多个PSA，在此不再赘述。
实施例一至实施例二中，由AF将确定的第二AS的地址信息和第一指示信息通过核心网设备发送至终端设备，AF还可以直接将第二AS的地址信息和第一指示信息发送至终端设备，下面通过图7的流程详细描述。
实施例三：
结合图4中的流程，实施例三中，第一网络设备为AF，第二网络设备为核心网设备，其中，核心网设备可以是SMF，或者，也可以是PCF、NEF以及AMF等。在实施例三中，第二网络设备确定更新信息，第一网络设备根据更新信息确定第二AS，并直接向终端设备指示第二AS，下面将详细描述。示例性的AF可以是管理第一AS和第二AS的网元，在一种实现方式中AF是MEC平台。
如图7所示，图7中以AF为终端设备选择切换后的AS为例进行说明，图7中的ULCL也可以采用BP实现，在此不再赘述。
在步骤700之前，终端设备与第一MEC中的第一AS建立了连接，为终端设备提供服务的是第一MEC中的第一AS，终端设备通过第一ULCL、第一PSA将数据发送给第一AS。终端设备移动到第二MEC之后，需要从第二MEC中确定为终端设备提供服务的第二AS，下面将详细描述。
在本实施例中，AF可以是集中管理所有AS的网元，AF也可以是第一AS，或者AF是第一AS所在第一MEC的平台等，具体不做限制。
在步骤700之前，终端设备与AF间建立了连接，以便AF可向终端设备发送消息。在本实施例中，该连接用来支持第一AS与第二AS间应用状态的切换。
步骤700：SMF接收DNAI不变指示。
该步骤的具体内容可以参考步骤500所述，在此不再赘述。
步骤701：SMF选择第二ULCL和第二PSA，并在PDU会话路径中插入第二ULCL。
当终端设备移动到第二MEC的服务区域后，SMF确定在第二MEC中选择第二ULCL和第二PSA。SMF具体如何选择第二ULCL和第二PSA，本申请实施例对此并不限定，在此不再赘述。
在步骤700中，SMF收到了该应用需要保持DNAI不变的指示，为此SMF可以指示第一ULCL和第二ULCL之间建立转发隧道，或者SMF可以指示第二ULCL到第一PSA之间建立转发隧道。
第一ULCL和第二ULCL之间建立转发隧道之后，终端设备与第一AS间的数据路径为：终端设备、第二ULCL、第一ULCL、第一PSA；或者，第二ULCL到第一PSA之间建立转发隧道后，终端设备与第一AS间的数据路径为：终端设备、第二ULCL、第一PSA。
步骤702：SMF向AF发送早通知。
该步骤的具体内容可以参考步骤502所述，在此不再赘述。
在该实施例中，可以由AF确定终端设备中的应用切换后的AS，具体可以参考步骤703的描述。
步骤703：AF选择第二AS。
该步骤的具体内容可以参考步骤503所述，在此不再赘述。
需要说明的是，步骤700至步骤703还可以采用步骤600至步骤603替换，具体可以参考图6所示，在此不再赘述。
在该实施例中，AF确定第二AS之后，AF可以直接向终端设备指示第二AS，并指示终端设备停止发送所述应用的上行数据，具体可以参考步骤704至705中的描述。
步骤704：AF向终端设备发送第一消息。
第一消息包括第二AS的地址信息。若应用有状态且在应用服务器切换时需要停止发送应用的上行数据，第一消息还包括第二指示信息。
若终端设备与AF间的连接可以用于支持多个不同应用的状态切换，则第一消息还包括应用标识等信息，应用标识用于终端设备确定所要切换应用服务器的应用。
可选的，AF还可以向终端设备发送关联标识，关联标识用于第二AS将终端设备与第二AS间建立的链路与从第一AS收到的应用层状态信息关联。
需要说明的是，终端设备包括proxy时，终端设备中的proxy可以接收第一消息。
步骤705：终端设备根据第二指示信息暂停发送上行数据。
该步骤的具体内容可以参考步骤507所述，在此不再赘述。
步骤706：终端设备根据第二AS的地址信息与第二AS间建立连接。
该步骤的具体内容可以参考步骤508所述，在此不再赘述。
步骤707：终端设备向AF发送响应消息。
可选的，终端设备可以将终端设备与第二AS之间的链路的链路信息在响应消息中发 送给AF。可选的，响应消息中还可以包括应用对应的应用标识或前面收到的关联标识。第二AS从第一AS接收的应用层状态信息中包括链路信息、或应用标识或关联标识，第二AS根据应用层状态信息中的链路信息将应用层状态信息与该链路关联。若不发送链路信息，即，使用应用标识或关联标识关联链路与应用层状态信息，则终端设备还需要在该终端设备与第二AS建立的链路上发送该应用标识或关联标识，以便第二AS进行关联。
可选的，终端设备还可以通过终端设备与第二AS之间的链路将应用标识或关联标识直接发送至第二AS，以便第二AS根据该链路收到的应用标识或关联标识将该链路与从第一AS收到的应用上下文关联。
步骤708：第一AS与第二AS间进行状态迁移。
该步骤的具体内容可以参考步骤511所述，在此不再赘述。
该实施例中，AF还可以直接指示终端设备恢复发送所述应用的上行数据，具体可以参考步骤709的描述。
步骤709：AF向终端设备发送第二消息，第二消息包括第四指示信息。
其中，第四指示信息用于指示终端设备恢复上行发送。
终端设备收到第四指示信息后，可以将上行数据通过与第二AS之间建立的链路发送给第二AS。需要说明的是，终端设备与第二AS间的数据路径为：终端设备、第二ULCL、第二PSA。当然终端设备与第二AS间的数据路径中还可能存在多个PSA，在此不再赘述。
当终端设备中存在proxy时，终端设备中的proxy在收到第四指示信息后，将缓存的上行数据通过步骤终端与第二AS间建立的链路发送给第二AS。终端设备中的proxy将终端设备中的应用发送的上行数据通过链路发送给第二AS。第二AS可以通过与该链路关联的应用层状态信息处理来自终端设备的上行数据。
实施例一至实施例三中，以AF是集中管理所有AS的网元为例进行描述，AF也可以是第一AS，下面通过图8的流程详细描述。
实施例四：
结合图4中的流程，实施例四中，第一网络设备为第一AS，第二网络设备为核心网设备，其中，核心网设备可以是SMF，或者，也可以是PCF、NEF以及AMF等，下面将详细描述。
如图8所示，图8中以第一AS为终端设备选择切换后的AS为例进行说明，图8中的ULCL也可以采用BP实现，在此不再赘述。
在步骤800之前，终端设备与第一MEC中的第一AS建立了连接，为终端设备提供服务的是第一MEC中的第一AS，终端设备通过第一ULCL、第一PSA将数据发送给第一AS。终端设备移动到第二MEC之后，需要从第二MEC中确定为终端设备提供服务的第二AS，下面将详细描述。
步骤800：SMF接收DNAI不变指示。
该步骤的具体内容可以参考步骤500所述，在此不再赘述。
步骤801：SMF选择第二ULCL和第二PSA，并在PDU会话路径中插入第二ULCL。
该步骤的具体内容可以参考步骤601所述，在此不再赘述。
步骤802：SMF向第一AS发送晚通知。
该步骤的具体内容可以参考步骤502所述，在此不再赘述。
需要说明的是，如果SMF在步骤801没有插入第二ULCL，则在该步骤中发送的可以 是早通知。
在该实施例中，可以由AF确定终端设备中的应用切换后的AS，具体可以参考步骤803的描述。这里，AF可以是第一AS，也可以是其他网元，如，MEC的编排器，下面以AF是第一AS为例进行说明。
步骤803：第一AS获取第二AS。
第一AS具体如何获取第二AS，可以参考步骤503中AF选择第二AS的过程，在此不赘述，即由第一AS选择第二AS。
或者，也可以由AF选择第二AS，并将所选择的第二AS发送给第一AS。
需要说明的是，步骤800至步骤803还可以采用步骤600至步骤603替换，具体可以参考图6所示，在此不再赘述。
在该实施例中，第一AS获取第二AS之后，第一AS可以通过SMF向终端设备指示第二AS，并指示终端设备停止发送所述应用的上行数据；当然第一AS也可以直接向终端设备指示上述信息，图8中以第一AS直接向终端设备指示为例进行描述。
步骤804：第一AS向终端设备发送第一消息，第一消息包括第二AS的地址信息。若应用有状态，则第一消息还包括第二指示信息。
可选的，第一AS还可以向终端设备发送关联标识，关联标识用于第二AS将终端设备与第二AS间建立的链路与从第一AS收到的应用层状态信息关联。终端设备通过终端与第二AS间建立的链路将关联标识发送给第二AS，并且第一AS在应用层状态信息中包括关联标识，第二AS基于此可将应用层状态信息与链路关联。
需要说明的是，与前面的实施例不同，该实施例中，终端设备中可以不包括proxy功能，可以由第一AS直接向终端设备发送第二AS的地址信息、第二指示信息。第一AS可以直接通过应用层消息发送第一消息。
步骤805：终端设备根据第二指示信息暂停发送上行数据。
该步骤的具体内容可以参考步骤507所述，在此不再赘述。
步骤806：终端设备根据第二AS的地址信息与第二AS间建立连接。
该步骤的具体内容可以参考步骤508所述，在此不再赘述。终端设备可将应用标识或关联标识通过该连接发送给第二AS。
步骤807：终端设备向第一AS发送响应消息。
终端设备可以将终端设备与第二AS之间的链路的链路信息在响应消息中发送给第一AS。可选的，响应消息中还可以包括应用对应的应用标识或前面收到的关联标识。
可选的，终端设备还可以将终端设备与第二AS之间的链路的链路信息、应用标识或关联标识直接通过建立的链路发送至第二AS。第二AS根据应用状态中的链路信息将应用状态与该链路关联。
步骤808：第一AS与第二AS间进行状态迁移。
该步骤的具体内容可以参考步骤511所述，在此不再赘述。
在该实施例中，第一AS还可以通过核心网设备指示终端设备恢复发送所述应用的上行数据，或者第一AS也可以直接指示终端设备恢复发送所述应用的上行数据，图8中以直接指示终端设备为例进行描述，具体可以参考步骤809的描述。
步骤809：第一AS向终端设备发送第二消息，第二消息包括第四指示信息。
其中，第四指示信息用于指示终端设备恢复上行发送。
可选的，第四指示信息也可以由第二AS发送给终端设备。
终端设备收到第四指示信息后，可以将上行数据通过与第二AS之间建立的连接发送给第二AS。需要说明的是，终端设备与第二AS间的数据路径为：终端设备、第二ULCL、第二PSA。当然终端设备与第二AS间的数据路径中还可能存在多个PSA，在此不再赘述。
实施例一至实施例四中，以AF或第一AS选择第二AS为例进行描述，本申请实施例中，还可以由SMF选择第二AS，下面通过图9的流程详细描述。
实施例五：
结合图4中的流程，实施例五中，第一网络设备为SMF，第二网络设备为AF，下面将详细描述。
如图9所示，图9中以SMF为终端设备选择切换后的AS为例进行说明，图8中的ULCL也可以采用BP实现，在此不再赘述。
在步骤900之前，终端设备与第一MEC中的第一AS建立了连接，为终端设备提供服务的是第一MEC中的第一AS，终端设备通过第一ULCL、第一PSA将数据发送给第一AS。终端设备移动到第二MEC之后，需要从第二MEC中确定为终端设备提供服务的第二AS，下面将详细描述。
步骤900：SMF接收状态指示信息。状态指示信息用于指示应用包括应用层状态信息。
SMF可以从AF或第一AS或管理AS的集中网元接收所述状态指示信息。SMF还可以接收所述应用的应用标识。
步骤901：SMF选择第二ULCL和第二PSA。
该步骤的具体内容可以参考步骤501所述，在此不再赘述。
需要说明的是，步骤901还可以采用步骤601替换，具体可以参考图6所示，在此不再赘述。
在该实施例中，可以由SMF确定终端设备中的应用切换后的AS，具体可以参考步骤902的描述。
步骤902：SMF选择第二AS。
若应用包括应用层状态信息，SMF选择第二AS。
SMF具体如何选择第二AS，本申请实施例并不限定。举例来说，SMF可以根据第二MEC中所部署的AS的信息选择第二AS，例如，AF(例如MEC平台)可以将第二MEC中所部署的AS的信息发送给SMF。或者，SMF也可以查询DNS获取第二MEC中所部署的AS的信息。当然，SMF还可以采用其他方式选择第二AS，本实施例对此不做限定。
步骤903：SMF发送第二AS的地址信息。
可选的，SMF可以向第一AS发送第二AS的地址信息，或者向第二AS发送第一AS的地址信息，也可以向AF发送第二AS的地址信息，本申请实施例并不限定，图9中以向AF发送第二AS的地址信息为例进行说明，其他情况不再赘述。
当SMF向第一AS发送第二AS的地址信息时，由第一AS将第二AS的地址信息转发至终端设备，当SMF向第二AS发送第一AS的地址信息时，在第二AS向第一AS获取应用状态时，触发第一AS将第二AS的地址信息发送给终端设备，具体过程不再赘述。
可选的，SMF也可以给AF发送第一AS的地址信息。
步骤904：AF向核心网设备发送第一消息。
该步骤中，核心网设备可以为SMF，也可以为AMF等设备。
该步骤的具体内容可以参考步骤504所述，在该步骤中，AF可以不发送第二AS的地址信息，在此不再赘述。
核心网设备不是SMF时，核心网设备还可以指示SMF在PDU会话路径中插入第二ULCL，具体如何指示，可以参考现有技术中的描述，本申请实施例对此并不限定。
步骤905：SMF在PDU会话路径中插入第二ULCL。
SMF可以由第一消息触发插入第二ULCL，或者，AF发送另外一条消息，由该消息触发SMF插入第二ULCL，不限定。
该步骤的具体内容可以参考步骤505所述，在此不再赘述。
步骤906：核心网设备向终端设备发送通知消息。
该步骤的具体内容可以参考步骤506所述，在此不再赘述。
步骤904和步骤906也可以采用步骤704替代，在此不再赘述。或者，步骤904和步骤906也可以采用步骤804替代，在此不再赘述。
步骤907：终端设备暂停发送上行数据。
该步骤的具体内容可以参考步骤507所述，在此不再赘述。
步骤908：终端设备根据第二AS的地址信息与第二AS间建立连接。
该步骤的具体内容可以参考步骤508所述，在此不再赘述。
步骤909：终端设备发送响应消息。
响应消息中包括的内容可以参考步骤509中的描述，在此不再赘述。
需要说明的是，图9中以终端设备通过SMF向AF发送响应消息为例进行说明，可以参考步骤509中的描述，在此不再赘述。
可选的，在实际应用中，终端设备也可以直接向AF或者第一AS发送响应消息，具体可以参考前面的实施例中的步骤707或步骤807中的描述，在此不再赘述。
步骤910：第一AS与第二AS间进行状态迁移。
该步骤的具体内容可以参考步骤511所述，在此不再赘述。
步骤911：终端设备接收第四指示信息。
其中，第四指示信息用于指示终端设备恢复上行发送。
需要说明的是，图9中以终端设备接收核心网设备发送的第四指示信息为例进行说明，具体可以参考前面的实施例中的步骤513中的描述。
可选的，在实际应用中，终端设备也可以接收AF或者第一AS发送的第四指示信息，具体可以参考前面的实施例中步骤709或步骤809中的描述，在此不再赘述。
可选的，第四指示信息也可以由第二AS发送给终端设备。
终端设备收到第四指示信息后，可以将上行数据通过与第二AS之间建立的链路发送给第二AS。需要说明的是，终端设备与第二AS间的数据路径为：终端设备、第二ULCL、第二PSA。当然终端设备与第二AS间的数据路径中还可能存在多个PSA，在此不再赘述。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
上述本申请提供的实施例中，分别从各个设备之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，终端设备与第一网络设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结 构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
与上述构思相同，如图10所示，本申请实施例还提供一种装置1000用于实现上述方法中终端设备或网络设备的功能。例如，该装置可以为软件模块或者芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。该装置1000可以包括：处理模块1001和通信模块1002。
本申请实施例中，通信模块1002也可以称为收发模块，可以包括发送模块和/或接收模块，分别用于执行上文方法实施例中终端设备或第一网络设备发送和接收的步骤。
以下，结合图10至图11详细说明本申请实施例提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
在一种可能的设计中，该装置1000可实现对应于上文方法实施例中的终端设备或者网络设备执行的步骤或者流程，下面分别进行描述。
示例性地，当该装置1000实现第一网络设备的功能时：
通信模块1002，用于确定终端设备的用户面路径的更新信息；
处理模块1001，用于当根据所述更新信息确定为所述终端设备的应用服务的应用服务器由第一应用服务器AS变更为第二AS，通过所述通信模块1002指示所述终端设备停止发送所述应用的上行数据。
在一种可能的实施方式中，所述通信模块1002还用于：
向所述终端设备发送所述应用的应用标识，所述应用标识用于指示需要切换应用服务器的应用。
在一种可能的实施方式中，所述通信模块1002具体用于：
向第二网络设备发送第一消息；所述第一消息包括第一指示信息，所述第一指示信息用于指示所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示所述终端设备停止发送所述应用的上行数据；
或者，通过所述第二网络设备向所述终端设备发送所述第一消息；所述第一消息包括所述第二指示信息；
或者，向所述终端设备发送第一消息；所述第一消息包括所述第二指示信息。
在一种可能的实施方式中，所述第一消息还包括所述第二AS的地址信息。
在一种可能的实施方式中，所述通信模块1002还用于：
指示所述终端设备恢复发送所述应用的上行数据。
在一种可能的实施方式中，所述通信模块1002还用于：
当确定所述第二AS获取到所述终端设备的应用层状态信息，则指示所述终端设备恢复发送所述应用的上行数据；所述应用层状态信息被用于处理所述终端设备的所述应用的信息。
在一种可能的实施方式中，所述通信模块1002具体用于：
向第二网络设备发送所述第二消息；所述第二消息包括第三指示信息，所述第三指示 信息用于所述第二网络设备向所述终端设备发送第四指示信息，所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；
或者，通过所述第二网络设备向所述终端设备发送所述第二消息；所述第二消息包括所述第四指示信息；或者，向所述终端设备发送所述第二消息；所述第二消息包括第四指示信息。
在一种可能的实施方式中，所述通信模块1002具体用于：
所述装置为管理所述第一AS以及所述第二AS的网元时，或者为所述第一AS时，接收来自所述第二网络设备的所述更新信息；
或者，所述装置为会话管理功能SMF时，对所述终端设备的用户面路径进行更新，并获得所述更新信息。
示例性地，当该装置1000实现终端设备的功能时：
通信模块1002，用于接收第二指示信息；所述第二指示信息指示所述终端设备停止发送所述应用的上行数据；
处理模块1001，用于根据所述第二指示信息停止发送所述应用的上行数据。
在一种可能的实施方式中，所述通信模块1002还用于：
接收所述应用的应用标识，所述应用标识用于指示需要切换应用服务器的应用。
在一种可能的实施方式中，所述装置还包括：
存储所述应用的上行数据。
在一种可能的实施方式中，所述通信模块1002还用于：
接收第四指示信息，所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；根据所述第四指示信息恢复发送所述应用的上行数据。
在一种可能的实施方式中，所述通信模块1002还用于：
接收第二应用服务器AS的地址信息；所述第二AS为新的为所述应用提供服务的AS；根据所述第二AS的地址信息与所述第二AS建立连接。
在一种可能的实施方式中，所述通信模块1002还用于：
通过所述连接向所述第二AS发送上行数据。
示例性地，当该装置1000实现第二网络设备的功能时：
通信模块1002，用于接收第一指示信息或第二指示信息，所述第一指示信息用于指示所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示终端设备停止发送所述应用的上行数据；
处理模块1001，用于当所述通信模块1002接收到所述第一指示信息时，生成所述第二指示信息；
所述通信模块1002，用于向所述终端设备发送所述第二指示信息。
在一种可能的实施方式中，所述通信模块1002还用于：
接收第二应用服务器AS的地址信息；所述第二AS为新的为所述应用提供服务的AS；
向所述终端设备发送所述第二AS的地址信息。
在一种可能的实施方式中，所述通信模块1002还用于：
接收第三指示信息或第四指示信息；所述第三指示信息用于所述第二网络设备向所述终端设备发送第四指示信息；所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；向所述终端设备发送所述第四指示信息。
在一种可能的实施方式中，所述通信模块1002还用于：
对所述终端设备的用户面路径进行更新，并获得更新信息；所述更新信息用于确定所述第二AS；向所述第一网络设备发送所述更新信息。
在一种可能的实施方式中，所述通信模块1002还用于：
向所述终端设备发送所述应用的应用标识。
在一种可能的实施方式中，通信模块1002还用于：
接收所述应用的应用标识。
如图11所示为本申请实施例提供的装置1100，图11所示的装置可以为图10所示的装置的一种硬件电路的实现方式。该通信装置可执行上述方法实施例中终端设备或者第一网络设备或者第二网络设备的功能。为了便于说明，图11仅示出了该通信装置的主要部件。
图11所示的装置1100包括至少一个处理器1120，用于实现本申请实施例提供的图2中任一方法。
装置1100还可以包括至少一个存储器1130，用于存储程序指令和/或数据。存储器1130和处理器1120耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1120可能和存储器1130协同操作。处理器1120可能执行存储器1130中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理电路(digital signal processor，DSP)、专用集成芯片(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态 随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
装置1100还可以包括通信接口1110，用于通过传输介质和其它设备进行通信，从而用于装置1100中的装置可以和其它设备进行通信。在本申请实施例中，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中，通信接口为收发器时，收发器可以包括独立的接收器、独立的发射器；也可以集成收发功能的收发器、或者是接口电路。
装置1100还可以包括通信线路1140。其中，通信接口1110、处理器1120以及存储器1130可以通过通信线路1140相互连接；通信线路1140可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信线路1140可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请实施例还提供一种系统，如图12所示，包括第一网络设备1201，终端设备1202以及第二网络设备1203。
第一网络设备1201，终端设备1202以及第二网络设备1203具体的功能，可以参考前面的实施例中的描述，在此不再赘述。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (30)

  1. 一种数据传输方法，其特征在于，包括：
    第一网络设备确定终端设备的用户面路径的更新信息；
    当所述第一网络设备根据所述更新信息确定为所述终端设备的应用服务的应用服务器由第一应用服务器AS变更为第二AS，指示所述终端设备停止发送所述应用的上行数据。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向所述终端设备发送所述应用的应用标识，所述应用标识用于指示需要切换应用服务器的应用。
  3. 根据权利要求1至2任一所述的方法，其特征在于，所述第一网络设备指示所述终端设备停止发送所述应用的上行数据，包括：
    所述第一网络设备向第二网络设备发送第一消息；所述第一消息包括第一指示信息，所述第一指示信息用于指示所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示所述终端设备停止发送所述应用的上行数据；
    或者，所述第一网络设备通过所述第二网络设备向所述终端设备发送所述第一消息；所述第一消息包括所述第二指示信息；
    或者，所述第一网络设备向所述终端设备发送第一消息；所述第一消息包括所述第二指示信息。
  4. 根据权利要求3所述的方法，其特征在于，所述第一消息还包括所述第二AS的地址信息。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备指示所述终端设备恢复发送所述应用的上行数据。
  6. 根据权利要求5所述的方法，其特征在于，所述第一网络设备指示所述终端设备恢复发送所述应用的上行数据，包括：
    当所述第一网络设备确定所述第二AS获取到所述终端设备的应用层状态信息，则指示所述终端设备恢复发送所述应用的上行数据；所述应用层状态信息被用于处理所述终端设备的所述应用的信息。
  7. 根据权利要求5所述的方法，其特征在于，所述第一网络设备指示所述终端设备恢复发送所述应用的上行数据，包括：
    所述第一网络设备向第二网络设备发送所述第二消息；所述第二消息包括第三指示信息，所述第三指示信息用于所述第二网络设备向所述终端设备发送第四指示信息，所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；
    或者，所述第一网络设备通过所述第二网络设备向所述终端设备发送所述第二消息；所述第二消息包括所述第四指示信息；
    或者，第一网络设备向所述终端设备发送所述第二消息；所述第二消息包括第四指示信息。
  8. 根据权利要求1至7任一所述的方法，其特征在于，所述第一网络设备确定终端设备的用户面路径的更新信息，包括：
    所述第一网络设备为管理所述第一AS以及所述第二AS的网元时，或者所述第一网络设备为所述第一AS时，所述第一网络设备接收来自所述第二网络设备的所述更新信息；
    或者，所述第一网络设备为会话管理功能SMF时，所述第一网络设备对所述终端设备的用户面路径进行更新，并获得所述更新信息。
  9. 一种数据传输方法，其特征在于，包括：
    终端设备接收第二指示信息；所述第二指示信息指示所述终端设备停止发送所述应用的上行数据；
    所述终端设备根据所述第二指示信息停止发送所述应用的上行数据。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述应用的应用标识，所述应用标识用于指示需要切换应用服务器的应用。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述终端设备存储所述应用的上行数据。
  12. 根据权利要求9至11任一所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收第四指示信息，所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；
    所述终端设备根据所述第四指示信息恢复发送所述应用的上行数据。
  13. 根据权利要求9至12任一所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收第二应用服务器AS的地址信息；所述第二AS为新的为所述应用提供服务的AS；
    所述终端设备根据所述第二AS的地址信息与所述第二AS建立连接。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述终端设备通过所述连接向所述第二AS发送上行数据。
  15. 一种数据传输方法，其特征在于，包括：
    第二网络设备接收第一指示信息或第二指示信息，所述第一指示信息用于指示所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示终端设备停止发送所述应用的上行数据；
    所述第二网络设备向所述终端设备发送所述第二指示信息。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收第二应用服务器AS的地址信息；所述第二AS为新的为所述应用提供服务的AS；所述第二网络设备向所述终端设备发送所述第二AS的地址信息。
  17. 根据权利要求15至16任一所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收第三指示信息或第四指示信息；所述第三指示信息用于所述第二网络设备向所述终端设备发送第四指示信息；所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；
    所述第二网络设备向所述终端设备发送所述第四指示信息。
  18. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备对所述终端设备的用户面路径进行更新，并获得更新信息；所述更新信息用于确定所述第二AS；
    所述第二网络设备向所述第一网络设备发送所述更新信息。
  19. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备向所述终端设备发送所述应用的应用标识。
  20. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收所述应用的应用标识。
  21. 一种系统，其特征在于，包括：
    第一网络设备，用于确定终端设备的用户面路径的更新信息；根据所述更新信息确定为所述终端设备的应用服务的应用服务器由第一应用服务器AS变更为第二AS，则向第二网络设备发送第一指示信息或第二指示信息；所述第一指示信息用于所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示终端设备停止发送所述应用的上行数据；
    所述第二网络设备，用于接收所述第一指示信息或所述第二指示信息；向所述终端设备发送所述第二指示信息；
    所述终端设备，用于接收第二指示信息；根据所述第二指示信息停止发送所述应用的上行数据。
  22. 一种通信装置，其特征在于，包括：
    通信模块，用于确定终端设备的用户面路径的更新信息；
    处理模块，用于当根据所述更新信息确定为所述终端设备的应用服务的应用服务器由第一应用服务器AS变更为第二AS，通过所述通信模块指示所述终端设备停止发送所述应用的上行数据。
  23. 根据权利要求22所述的装置，其特征在于，所述通信模块具体用于：
    向第二网络设备发送第一消息；所述第一消息包括第一指示信息，所述第一指示信息用于指示所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示所述终端设备停止发送所述应用的上行数据；
    或者，通过所述第二网络设备向所述终端设备发送所述第一消息；所述第一消息包括所述第二指示信息；
    或者，向所述终端设备发送第一消息；所述第一消息包括所述第二指示信息。
  24. 根据权利要求22至23任一所述的装置，其特征在于，所述通信模块还用于：
    指示所述终端设备恢复发送所述应用的上行数据。
  25. 根据权利要求24所述的装置，其特征在于，所述通信模块还用于：
    当确定所述第二AS获取到所述终端设备的应用层状态信息，则指示所述终端设备恢复发送所述应用的上行数据；所述应用层状态信息被用于处理所述终端设备的所述应用的信息。
  26. 根据权利要求24所述的装置，其特征在于，所述通信模块具体用于：
    向第二网络设备发送所述第二消息；所述第二消息包括第三指示信息，所述第三指示信息用于所述第二网络设备向所述终端设备发送第四指示信息，所述第四指示信息用于指示所述终端设备恢复发送所述应用的上行数据；
    或者，通过所述第二网络设备向所述终端设备发送所述第二消息；所述第二消息包括所述第四指示信息；
    或者，向所述终端设备发送所述第二消息；所述第二消息包括第四指示信息。
  27. 一种通信装置，其特征在于，包括：
    通信模块，用于接收第二指示信息；所述第二指示信息指示所述终端设备停止发送所述应用的上行数据；
    处理模块，用于根据所述第二指示信息停止发送所述应用的上行数据。
  28. 根据权利要求27所述的装置，其特征在于，所述通信模块还用于：
    接收第二应用服务器AS的地址信息；所述第二AS为新的为所述应用提供服务的AS；
    根据所述第二AS的地址信息与所述第二AS建立连接。
  29. 一种数据传输装置，其特征在于，包括：
    通信模块，用于接收第一指示信息或第二指示信息，所述第一指示信息用于指示所述第二网络设备向所述终端设备发送第二指示信息，所述第二指示信息用于指示终端设备停止发送所述应用的上行数据；
    处理模块，用于当所述通信模块接收到所述第一指示信息时，生成所述第二指示信息；
    所述通信模块，用于向所述终端设备发送所述第二指示信息。
  30. 根据权利要求29所述的装置，其特征在于，所述通信模块还用于：
    接收第二应用服务器AS的地址信息；所述第二AS为新的为所述应用提供服务的AS；
    向所述终端设备发送所述第二AS的地址信息。
PCT/CN2021/082455 2020-03-25 2021-03-23 一种数据传输方法、装置及系统 WO2021190513A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010218174.0 2020-03-25
CN202010218174.0A CN113453287B (zh) 2020-03-25 2020-03-25 一种数据传输方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2021190513A1 true WO2021190513A1 (zh) 2021-09-30

Family

ID=77807576

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/082455 WO2021190513A1 (zh) 2020-03-25 2021-03-23 一种数据传输方法、装置及系统

Country Status (2)

Country Link
CN (1) CN113453287B (zh)
WO (1) WO2021190513A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019101292A1 (en) * 2017-11-21 2019-05-31 Telefonaktiebolaget Lm Ericsson (Publ) Method and function for handling traffic for an application
CN110650513A (zh) * 2018-06-26 2020-01-03 电信科学技术研究院有限公司 一种用户面路径更新的方法、装置及计算机存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106909474A (zh) * 2015-12-23 2017-06-30 北京奇虎科技有限公司 一种移动终端上系统应用的恢复方法及装置
CN110383775B (zh) * 2017-03-30 2021-03-30 华为技术有限公司 数据传输方法和通信设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019101292A1 (en) * 2017-11-21 2019-05-31 Telefonaktiebolaget Lm Ericsson (Publ) Method and function for handling traffic for an application
CN110650513A (zh) * 2018-06-26 2020-01-03 电信科学技术研究院有限公司 一种用户面路径更新的方法、装置及计算机存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON, CATT: "Clarification and correction to AF response", 3GPP DRAFT; S2-1907633 CLARIFICATION AND CORRECTION TO AF RESPONSE IN TS 23.501 - V1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sapporo, Japan; 20190624 - 20190628, 18 June 2019 (2019-06-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051752598 *

Also Published As

Publication number Publication date
CN113453287B (zh) 2023-08-22
CN113453287A (zh) 2021-09-28

Similar Documents

Publication Publication Date Title
KR102389683B1 (ko) 통신 방법 및 통신 장치
US11246172B2 (en) Method for selecting session and service continuity mode in wireless communication system and device therefor
CN110662270B (zh) 通信方法及装置
CN109600802B (zh) 数据传输方法、相关设备及系统
EP3611904A1 (en) Data buffering method and session management functional entity
US11968565B2 (en) User plane information reporting method and apparatus
US11871273B2 (en) Systems and methods for user plane handling
ES2934316T3 (es) Método y aparato de comunicación
EP4088434A1 (en) Tsc-5g qos mapping with consideration of assistance traffic information and pcc rules for tsc traffic mapping and 5g qos flows binding
EP4221005A1 (en) Multipath transmission method and communication apparatus
CN114731557B (zh) 报文传输方法、通信装置和通信系统
CN110519809B (zh) 管理pdu会话的方法、网元、设备、装置、系统和存储介质
WO2019047935A1 (zh) 一种会话建立方法及装置
WO2020073899A1 (zh) 数据传输方法及装置
JP2019511880A (ja) データ伝送方法、装置及びセッション管理デバイス
JP2023534597A (ja) リロケーション時にエッジアプリケーションサーバへのシームレスなサービス継続性を調整するためのメカニズム
CN110138685B (zh) 一种通信方法及装置
CN116097751A (zh) 利用smf重新选择来重新锚定
CN112752297A (zh) 一种通信方法及设备
WO2022170798A1 (zh) 确定策略的方法和通信装置
TWI836328B (zh) 通信方法及裝置
WO2021190513A1 (zh) 一种数据传输方法、装置及系统
WO2020211538A1 (zh) 一种数据传输方法及装置
CN113163514A (zh) 会话处理方法及通信装置
WO2024164837A1 (zh) 一种信息处理方法及通信装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21776568

Country of ref document: EP

Kind code of ref document: A1