WO2020259428A1 - 用于传输业务报文的方法和装置 - Google Patents

用于传输业务报文的方法和装置 Download PDF

Info

Publication number
WO2020259428A1
WO2020259428A1 PCT/CN2020/097385 CN2020097385W WO2020259428A1 WO 2020259428 A1 WO2020259428 A1 WO 2020259428A1 CN 2020097385 W CN2020097385 W CN 2020097385W WO 2020259428 A1 WO2020259428 A1 WO 2020259428A1
Authority
WO
WIPO (PCT)
Prior art keywords
source
network element
target
message
indication information
Prior art date
Application number
PCT/CN2020/097385
Other languages
English (en)
French (fr)
Inventor
余芳
李岩
倪慧
李永翠
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20833223.9A priority Critical patent/EP3979531A4/en
Publication of WO2020259428A1 publication Critical patent/WO2020259428A1/zh
Priority to US17/561,190 priority patent/US11677492B2/en
Priority to US18/309,046 priority patent/US20230336269A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • This application relates to the field of communications, and more specifically, to a method and device for transmitting service messages in the field of communications.
  • the terminal device When the terminal device moves from the coverage area of the original access network equipment to the coverage area of the current access network equipment, it will trigger the air interface switch, that is, switch the access network equipment of the terminal device from the original access network equipment to the current access network equipment.
  • the access network equipment Because the location of the terminal device has changed, but the terminal device still accesses the original user plane network element, but in fact, the user plane network element closest to the terminal device may have changed at this time, but the terminal device is still the same as the original user plane network element. In this case, the transmission path is longer, and accordingly, the transmission delay of the message will increase. In order to reduce the transmission delay of the message, it is necessary to switch the transmission path from the original user plane network element to the new user plane network element. During the switching process, the uplink and downlink service packets that have not yet been transmitted are prone to packet loss. Cause the transmission performance to decline.
  • This application provides a method and device for transmitting service messages, which can improve transmission performance.
  • a method for transmitting service packets which includes: after a source mobile edge computing network element receives a second uplink service packet, the source mobile edge computing network element receives the data from the source user plane network element The first uplink service packet of the target user plane network element, where the second uplink service packet is the last uplink service packet sent by the source mobile edge computing network element to the source application server; the source mobile edge computing network Element sends a first uplink service packet to a target mobile edge computing network element; the source mobile edge computing network element sends first indication information to the target mobile edge computing network element, and the first indication information is used to indicate the The source mobile edge computing network element ends sending the first uplink service packet.
  • the source mobile edge computing network element after the source mobile edge computing network element sends the last second uplink service packet to the source application server, the first uplink service packet after the second uplink service packet passes through the target mobile edge
  • the computing network element sends to the target application server, which can avoid the loss of the first uplink service packet, thereby helping to improve the transmission performance.
  • the source mobile edge computing network element can send the first indication information to the target mobile edge computing network element to instruct the source mobile edge computing network element to send the first uplink service packet to end, which can prevent the target mobile edge computing network element from waiting to receive the source
  • the uplink service packet sent by the mobile edge computing network element helps the target mobile edge computing network element to send the uplink service packet.
  • the method before the source mobile edge computing network element sends the first uplink service packet to the target mobile edge computing network element, the method further includes: the source mobile edge computing network element receives the source user The second instruction information from the target user plane network element sent by the user plane network element of the plane function, where the second instruction information is used to instruct the target user plane network element to end sending the first uplink service packet.
  • the source mobile edge computing network element receives the second indication information sent by the source user plane network element after receiving the first uplink service packet sent by the source user plane network element, or the source mobile edge computing network element may At the same time, the second indication information and the first uplink service message sent by the source user plane network element are received.
  • the first indication information and the second indication information may be signaling between different network elements, but the first indication information and the second indication information may include the same information element, that is, the same information element may be It is the identifier of the end of the uplink service packet, that is, when the target user plane network element sends the second indication information to the source user plane network element, and the source user plane network element forwards the second indication information to the source mobile edge computing network element, the source The mobile edge computing network element can determine that the uplink service packet from the target user plane network element is over, that is, the source user plane network element will no longer send uplink service packets from the target user plane network element to the source mobile edge computing network element; After the source mobile edge computing network element sends the first indication information to the target mobile edge computing network element, the target mobile edge computing network element can determine that the uplink service packet from the source mobile edge computing network element ends, that is, the source mobile edge computing network element No more uplink service packets will be sent to the target mobile edge computing network element.
  • the method before the source mobile edge computing network element sends the first uplink service packet to the target mobile edge computing network element, the method further includes: the source mobile edge computing network element sends the source user The plane network element sends the first downlink service packet and third indication information, where the third indication information is used to indicate the end of sending the downlink service packet from the source application server.
  • the method before the source mobile edge computing network element sends the first downlink service packet to the source user plane network element, the method further includes:
  • the source mobile edge computing network element receives fourth indication information sent by the first network element, where the fourth indication information is used to indicate that the last downlink service packet from the source application server is the first downlink Business message
  • the source mobile edge computing network element sends the fifth indication information to the first network element, where the fifth indication information is used to indicate that the second uplink service packet is sent by the source mobile edge computing network element The last uplink service message to the source application server.
  • the fourth indication information is the sequence number of the first downlink service packet
  • the fifth indication information is the sequence number of the second uplink service packet.
  • the source mobile edge computing network element sending third indication information to the source user plane network element includes: the source mobile edge computing network element sends third indication information to the source user according to the fourth indication information The surface network element sends the third instruction information.
  • the method before the source mobile edge computing network element sends the first uplink service packet to the target mobile edge computing network element, the method further includes: the source mobile edge computing network element receives policy control A second relocation request message sent by a network element or a session management network element, where the second relocation request message is used to notify the data network access point identifier that the target data network access point identifier changes or is used to notify the user plane network element of the change,
  • the second migration request message includes the identification of the terminal device and the identification of the target data network access point;
  • the source mobile edge computing after receiving the second migration request message, sends a fifth migration request message to the source application server.
  • the fifth migration request message is used to request the application server to migrate the context of the terminal device. 5.
  • the migration request message includes the identification of the terminal device and the identification of the target data network access point.
  • the method further includes:
  • the source mobile edge computing network element sends a third migration request message to the target mobile edge computing network element, where the third migration request message is used to request the target mobile edge computing network element to perform the context of the terminal device
  • the third migration request message includes the identifier of the terminal device; the source mobile edge computing network element receives a response message to the third migration request message sent by the target mobile edge computing network element.
  • the source mobile edge computing after receiving the second migration request message, sends a fifth migration request message to the source application server.
  • the fifth migration request message is used to request the source application server to migrate the context of the terminal device.
  • the fifth migration request message includes the identification of the terminal device and the identification of the target data network access point.
  • the method further includes: the source mobile edge computing network element receives data from the source application server A context migration completion message of the server, the context migration completion message is used to indicate that the source application server and the target application server corresponding to the target target data network access point identifier have completed the context migration of the terminal device.
  • the method before the source mobile edge computing network element sends the first uplink service packet to the target mobile edge computing network element, the method further includes: the source mobile edge computing network element receives the PCF network
  • the second migration request message sent by the SMF network element or the SMF network element the second migration request message is used to notify the data network access point identifier that the target data network access point identifier has changed or is used to notify the user plane network element of the change.
  • the migration request message includes the identification of the first application instance and the identification of the target data network access point;
  • the source mobile edge computing after receiving the second migration request message, sends a first migration request message to the mobile edge computing application management network element, and the first migration request message is used to send the first migration request message to the mobile edge computing application management network.
  • the meta request is to migrate the context of the terminal device, and the first migration request message includes the identification of the first application instance and the identification of the target data network access point.
  • the mobile edge computing application management network element sends a response message of the first migration request message to the source mobile edge computing to indicate that the mobile edge computing application management network element can accept the migration of the context of the first application instance.
  • the method further includes: the source mobile edge computing network element sends the The target mobile edge computing network element sends a third migration request message, the third migration request message is used to request to the target mobile edge computing whether to accept the migration of the context of the first application instance, and the third context migration request message includes the first application The ID of the instance. If the target mobile edge computing can accept the migration of the terminal device context, it sends a response message of the third migration request message to the source mobile edge computing. The response message of the third migration request is used to indicate that the target mobile edge computing can accept the first application instance context Migration.
  • the method further includes:
  • the source mobile edge computing network element receives a context migration complete message from the mobile edge computing application management network element, where the context migration complete message is used to indicate the identity of the source application server and the target data network access point The corresponding target application server has completed the migration of the context of the terminal device.
  • a method for transmitting service messages which includes: a target user plane network element sends a first uplink service message to a source user plane network element, and the target user sends a first uplink service message to the source user plane. After the first uplink service message, no uplink service message is sent to the source user plane; the target user sends second indication information to the source user plane, and the second indication information is used to indicate that the target user plane moves The edge computing network element sending the first uplink service message ends.
  • the target user after the target user sends the first uplink service packet to the source user plane, it no longer sends the uplink service packet to the source user plane, and the target user plane may send the second uplink service packet to the source user plane.
  • the indication information indicates the end of sending the first uplink service message through the target user plane.
  • the target user plane can directly send the uplink service packets from the access network device to the target mobile edge computing network element without sending it to the source user plane network element. In this way, the target mobile edge computing network element determines the first uplink service After the message is sent, the uplink service message directly from the target user plane is sent, thereby avoiding the problem of disorder of the uplink service message.
  • the method before the target user plane network element sends the first uplink service packet to the source user plane network element, the method further includes: the target user plane network element receives from the source user The first downlink service packet and third indication information of the plane network element, where the third indication information is used to indicate the end of sending the downlink service packet from the source application server.
  • the target user plane network element sending second indication information to the source user plane network element includes: the target user plane network element sends the second indication information to the source user according to the third indication information The surface network element sends the second indication information.
  • the target user plane network element sending the second indication information to the source user plane network element includes: the target user plane network element receives from the session management network element or the target mobile edge computing network After the context migration complete message sent by the element, the target user plane network element sends the second indication information to the source user plane network element.
  • the method further includes: the target user plane network element moves to the target edge
  • the computing network element sends an uplink service message from the access network device.
  • the method further includes: when the first downlink service message is sent, the target user plane network The element sends a downlink service message from the target mobile edge computing network element to the access network device.
  • a method for transmitting service packets including: a target mobile edge computing network element receives a first uplink service packet from a source mobile edge computing network element, where the first uplink service packet is The received uplink service packet after the source mobile edge computing receives a second uplink service packet, the second uplink service packet being the last sent by the source mobile edge computing network element to the source application server application server An uplink service packet; the target mobile edge computing receives first indication information from a source mobile edge computing network element, where the first indication information is used to instruct the source mobile edge computing network element to send a first uplink service packet End; after the target mobile edge computing network element receives the first indication information, when the first uplink service message is sent, the target mobile edge computing network element sends the target user plane to the target application server An uplink service message sent by the network element to the target mobile edge computing network element.
  • the first uplink service packet after the second uplink service packet is passed through the target mobile edge computing
  • the network element sends to the target application server, so that the loss of the first uplink service packet can be avoided, and the source mobile edge computing network element can send the first indication information to the target mobile edge computing network element to instruct to send it through the source mobile edge computing network element
  • the end of the first uplink service message can prevent the target mobile edge computing network element from waiting to receive the uplink service message sent by the source mobile edge computing network element.
  • the target mobile edge computing network element After receiving the first indication information, the target mobile edge computing network element sends After the target application server sends the uplink service message from the source mobile edge computing network element, it sends the uplink service message from the target user plane network element, so as to avoid the problem of uplink service message disorder.
  • the method before the target mobile edge computing network element receives the first uplink service packet from the source mobile edge computing network element, the method further includes: the target mobile edge computing receives from the source mobile edge computing The third relocation request message of, where the third relocation request message includes the identifier of the terminal device.
  • the third migration request message is used to request whether to accept the migration of the context of the terminal device to the target mobile edge computing.
  • the target mobile edge computing can accept the terminal device context migration, and then sends a response message of the third migration request message to the source mobile edge computing.
  • the response message of the third migration request message is used to indicate that the target mobile edge computing can accept the terminal device context migration .
  • the method before the target mobile edge computing network element receives the first uplink service packet from the source mobile edge computing network element, the method further includes: the target mobile edge computing receives from the source mobile edge computing
  • the third migration request message of the third migration request message includes the identifier of the first application instance.
  • the third migration request message is used to request whether to accept the migration of the context of the first application instance to the target mobile edge computing. If the target mobile edge computing can accept the migration of the terminal device context, it sends a response message of the third migration request message to the source mobile edge computing.
  • the response message of the third migration request is used to indicate that the target mobile edge computing can accept the first application instance context Migration.
  • a method for transmitting service messages including: a source application server receives a first message, the first message is used to trigger the source application server to perform context migration of a terminal device, and The first message includes the target data network access point identifier; the source application server determines that after processing the first downlink service packet and the second uplink service packet, the source application server and the The target application server corresponding to the target target data network access point identifier performs the migration of the terminal device context, wherein the first downlink service packet is the last sent by the source application server to the source mobile edge computing network element A downlink service message, and the second uplink service message is the last uplink service message sent by the source mobile edge computing network element to the source application server.
  • the first message is the aforementioned fifth migration request message.
  • the method further includes: the source application server transfers the source application server to the source The mobile edge computing network element sends fourth indication information, where the fourth indication information is used to indicate that the first downlink service packet is the last downlink service packet from the source application server; the source application server receives The fifth indication information sent by the source mobile edge computing network element, where the fifth indication information is used to indicate that the second uplink service packet is the last message sent by the source mobile edge computing network element to the source application server An uplink service message.
  • the fourth indication information is the sequence number of the first downlink service packet
  • the fifth indication information is the sequence number of the second uplink service packet.
  • a method for transmitting service messages including: a mobile edge computing application management network element receives a first migration request message sent by a source mobile edge computing network element, where the first migration request message includes the first migration request message.
  • the mobile edge computing application management network element sends a first trigger message and a second trigger message to the target application server corresponding to the target target data network access point identifier and the source application server corresponding to the first application instance.
  • a trigger message includes the identifier of the first application instance, the first trigger message is used to trigger the target application server to migrate the first application instance, and the second trigger message is used to trigger the source application The server performs migration of the first application instance.
  • the mobile edge computing application management network element respectively identifies the target application server corresponding to the target data network access point and the first trigger sent by the source application server corresponding to the target application instance Message and the second trigger message
  • the method further includes: the mobile edge computing application management network element creates a virtual resource of the first application instance on the target application server, so that the target application server can The virtual resource migrates the first application instance.
  • the present application provides a device for transmitting service messages, which is used to implement the method in the first aspect and/or any possible implementation manners thereof.
  • the device may be a source mobile edge computing network element, a device in a source mobile edge computing network element, or a device that can be used in matching with network equipment.
  • the device may include a module corresponding to the method/operation/step/action described in the first aspect and/or any possible implementation manners thereof.
  • the module may be a hardware circuit, software, or It can be realized by hardware circuit combined with software.
  • the device may include a receiving unit and a sending unit, and the receiving unit and the sending unit may be one transceiver unit or different transceiver units.
  • the present application provides a device for transmitting service messages, which is used to implement the method in the second aspect and/or any possible implementation manner thereof.
  • the device may be a target user plane network element, or a device in the target user plane network element, or a device that can be matched and used with the target user plane network element.
  • the device may include a module corresponding to the method/operation/step/action described in the second aspect and/or any of its possible implementations.
  • the module may be a hardware circuit, software, or It can be realized by hardware circuit combined with software.
  • the device may include a sending unit.
  • the present application provides a device for transmitting service messages, which is used to implement the method in the third aspect and/or any possible implementation manner thereof.
  • the device may be a target mobile edge computing network element, or a device in the target mobile edge computing network element, or a device that can be matched and used with the target mobile edge computing network element.
  • the device may include a module corresponding to the method/operation/step/action described in the third aspect and/or any of its possible implementations.
  • the module may be a hardware circuit, software, or It can be realized by hardware circuit combined with software.
  • the device may include a receiving unit and a sending unit, and the receiving unit and the sending unit may be one transceiver unit or different transceiver units.
  • the present application provides a device for transmitting service messages, which is used to implement the method in the fourth aspect and/or any possible implementation manners thereof.
  • the device may be a source application server, a device in the source application server, or a device that can be used in a matching manner with the source application server.
  • the device may include a module corresponding to the method/operation/step/action described in the fourth aspect and/or any of its possible implementations.
  • the module may be a hardware circuit, software, or It can be realized by hardware circuit combined with software.
  • the device may include a migration unit and a transceiver unit.
  • the present application provides a device for transmitting service messages, which is used to implement the method in the fifth aspect and/or any possible implementation manner thereof.
  • the device can be a mobile edge computing application management network element receiving source mobile edge computing network element, or a mobile edge computing application management network element receiving source mobile edge computing network element device, or can be combined with a mobile edge computing application management network
  • the device may include a module corresponding to the method/operation/step/action described in the fifth aspect and/or any of its possible implementations.
  • the module may be a hardware circuit, software, or It can be realized by hardware circuit combined with software.
  • the device may include a receiving unit and a sending unit, and the receiving unit and the sending unit may be one transceiver unit or different transceiver units.
  • the present application provides a device for transmitting service messages.
  • the device includes a processor for implementing the method described in the first aspect and/or any possible implementation manners thereof.
  • the device may further include a memory.
  • the memory is used to store instructions.
  • the processor executes the instructions stored in the memory, the first aspect and/or any possible implementation manners thereof may be implemented. Described method.
  • the device may further include a communication interface for communicating with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, pin, or other types of communication interfaces.
  • the present application provides a device for transmitting service messages, the device including a processor, configured to implement the method described in the second aspect and/or any possible implementation manner thereof.
  • the device may further include a memory.
  • the memory is used to store instructions.
  • the processor executes the instructions stored in the memory, the above second aspect and/or any possible implementation manners thereof may be implemented Described method.
  • the device may also include a communication interface, which is used for the device to communicate with other devices.
  • the present application provides a device for transmitting service messages, the device including a processor, configured to implement the method described in the third aspect and/or any possible implementation manner thereof.
  • the device may further include a memory.
  • the memory is used to store instructions.
  • the processor executes the instructions stored in the memory, the above third aspect and/or any possible implementation manners thereof may be implemented. Described method.
  • the device may further include a communication interface for communicating with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, pin, or other types of communication interfaces.
  • the present application provides a device for transmitting service messages, the device including a processor, configured to implement the method described in the fourth aspect and/or any possible implementation manner thereof.
  • the device may further include a memory.
  • the memory is used to store instructions.
  • the processor executes the instructions stored in the memory, the foregoing fourth aspect and/or any possible implementation manner can be implemented. Described method.
  • the device may also include a communication interface, which is used for the device to communicate with other devices.
  • the present application provides a device for transmitting service messages, the device including a processor, configured to implement the method described in the fifth aspect and/or any possible implementation manner thereof.
  • the device may further include a memory.
  • the memory is used to store instructions.
  • the processor executes the instructions stored in the memory, the above fifth aspect and/or any possible implementation manners thereof may be implemented. Described method.
  • the device may also include a communication interface, which is used for the device to communicate with other devices.
  • this application provides a system for transmitting data, which includes the device provided in the sixth aspect, the device provided in the seventh aspect, the device provided in the eighth aspect, the device provided in the ninth aspect, and At least two of the devices provided by the tenth aspect; or
  • the system includes at least two of the device provided by the eleventh aspect, the device provided by the twelfth aspect, the device provided by the thirteenth aspect, the device provided by the fourteenth aspect, and the device provided by the fifteenth aspect. ;
  • this application provides a computer-readable storage medium with computer instructions stored in the computer-readable storage medium.
  • the computer instructions run on the computer, the computer executes the above aspects and any possible design methods. .
  • this application provides a chip including a processor.
  • the processor is used to execute the above aspects and methods in any possible implementation manners.
  • the chip further includes a memory, and the memory is coupled with the processor.
  • the chip further includes a communication interface.
  • this application provides a computer program product.
  • the computer program product includes computer program code.
  • the computer program code runs on a computer, the computer executes the above aspects and any possible design methods. .
  • Figure 1 is a schematic diagram of a system architecture provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • Fig. 3 is a schematic diagram of another application scenario provided by an embodiment of the present application.
  • Fig. 4 is a schematic diagram of another application scenario provided by an embodiment of the present application.
  • Fig. 5 is a schematic diagram of a method for transmitting service messages provided by an embodiment of the present application.
  • Fig. 6 is a schematic diagram of another method for transmitting service messages provided by an embodiment of the present application.
  • Fig. 7 is a schematic diagram of another method for transmitting service messages provided by an embodiment of the present application.
  • Fig. 8 is a schematic diagram of another method for transmitting service messages provided by an embodiment of the present application.
  • Fig. 9 is a schematic diagram of another method for transmitting service messages provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another method for transmitting service messages provided by an embodiment of the present application.
  • Fig. 11 is a schematic diagram of a downlink service packet transmission path provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a transmission path of an uplink service packet provided by an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of another apparatus for transmitting service packets according to an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of another apparatus for transmitting service packets provided by an embodiment of the present application.
  • FIG. 15 is a schematic block diagram of another apparatus for transmitting service packets provided by an embodiment of the present application.
  • FIG. 16 is a schematic block diagram of another apparatus for transmitting service packets provided by an embodiment of the present application.
  • FIG. 17 is a schematic block diagram of another apparatus for transmitting service packets provided by an embodiment of the present application.
  • FIG. 18 is a schematic block diagram of another apparatus for transmitting service packets provided by an embodiment of the present application.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE Time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • Fig. 1 exemplarily shows a schematic diagram of a communication system architecture provided by the present application.
  • the communication system architecture includes mobility management network elements, session management network elements, policy control network elements, authentication service network elements, data management network elements, and user plane network elements. Further, the communication system architecture also includes access network equipment, terminal devices (user equipment, UE), and data network elements (data network, DN).
  • the terminal device can be connected to the mobility management network element, the access network device can also be connected to the mobility management network element, the access network device can also be connected to the user plane network element, and the user plane network element can be connected to the session management network element, Data network connection, mobility management network element can be connected to session management network element, data management network element, policy control network element and authentication service network element respectively, session management network element is connected to policy control network element and data management network element respectively. Both the mobility management network element and the session management network element can obtain data from the data management network element, such as user subscription data, and both the mobility management network element and the session management network element can obtain policy data from the policy control network element.
  • the policy control network element obtains the user subscription data from the data management network element and sends it to the mobility management network element and the session management network element, and then the mobility management network element and the session management network element deliver it to the access network equipment and terminal Device and user plane network elements, etc.
  • the mobility management network element is mainly used for the registration, mobility management, and tracking area update procedures of terminal devices in the mobile network.
  • the mobility management network element terminates non-access stratum (NAS) messages, completes registration management, connection management, and reachability management, assigns track area list (TA list), and mobility management, etc., And transparently route session management (SM) messages to the session management network element.
  • NAS non-access stratum
  • TA list track area list
  • SM mobility management network elements
  • AMF core access and mobility management function
  • communication will be like the 6th generation ( In the 6th generation, 6G) communication, the mobility management network element may still be an AMF network element or have other names, which is not limited in this application.
  • the session management network element is mainly used for session management in the mobile network, such as session creation, modification, and release. Specific functions include, for example, allocating internet protocol (IP) addresses for users, selecting user plane network elements that provide message forwarding functions, and so on.
  • IP internet protocol
  • the session management network element may be a session management function (SMF) network element.
  • SMF session management function
  • future communications such as 6G, the session management network element may still be an SMF network element or have other names. This application does not Make a limit.
  • the policy control network element includes user subscription data management functions, policy control functions, charging policy control functions, quality of service (QoS) control, etc.
  • the policy control network element can be a policy control function (PCF) network element.
  • PCF policy control function
  • future communications such as 6G, the policy control network element can still be a PCF network element or have other names. This application does not Make a limit.
  • the authentication server network element is mainly used to verify service functions and store keys using an extensible authentication protocol (EAP) to realize user authentication and authentication.
  • EAP extensible authentication protocol
  • the authentication server network element can be an authentication server function (authentication server function, AUSF) network element.
  • AUSF authentication server function
  • future communications such as 6G
  • the user plane network element can still be an AUSF network element or have other names. This application does not Make a limit.
  • the data management network element is mainly used to store user data, such as contract information, authentication/authorization information.
  • the data management network element can be a unified data management (UDM) network element.
  • UDM unified data management
  • future communications such as 6G, the data management network element can still be a UDM network element or have other names. This application does not Make a limit.
  • User plane network elements are mainly used for user plane service processing, such as service routing, packet forwarding, anchoring functions, quality of service (QoS) mapping and execution, uplink identification and routing to the data network,
  • There can be multiple user plane network elements such as downlink packet buffering and notification triggering of downlink data arrival, connection with external data network, etc., among which the user plane network element connected to the application server (application service, AS) is called protocol data Unit session anchor (PDU session anchor, PSA), where PDU is called protocol data unit.
  • application service, AS application service
  • PDU session anchor PSA
  • user plane network elements can be user plane function (UPF) network elements.
  • future communications such as 6G
  • user plane network elements can still be UPF network elements or have other names. This application does not Make a limit.
  • Access network equipment which may also be called radio access network (RAN) equipment, is a type of equipment that provides wireless communication functions for terminal devices.
  • Access network equipment includes, but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (RNC), node B (node B) B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
  • next-generation base stations evolved node B, eNB
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved nodeB, or
  • a terminal device (user equipment, UE) is a device with a wireless transceiver function. It can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships); it can also be deployed on In the air (such as airplanes, balloons, satellites, etc.).
  • the terminal device can be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, virtual reality (VR) terminal, augmented reality (AR) terminal, industrial control (industrial control)
  • DN Network Data Network
  • operators services such as operator services, Internet access services, and third-party services.
  • third-party services such as operator services, Internet access services, and third-party services.
  • network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • the above-mentioned network elements or functions can be divided into one or more services, and further, there may be services independent of the network functions.
  • an instance of the above-mentioned function, or an instance of a service included in the above-mentioned function, or an instance of a service that exists independently of the network function may be referred to as a service instance.
  • each network element included in FIG. 1 is only a name, and the name does not limit the function of the network element itself.
  • the aforementioned network elements may also have other names, which are not specifically limited in the embodiment of the present application.
  • some or all of the above-mentioned network elements may use the terminology in 5G, or may be named in other ways, etc., which will be uniformly explained here and will not be repeated here.
  • each network element in Figure 1 does not necessarily exist at the same time, and which network elements are needed can be determined according to requirements.
  • the connection relationship between the various network elements in Figure 1 is not uniquely determined, and can be adjusted according to requirements.
  • This application is described by taking the user plane network element as the UPF as an example, for example, the source UPF and the target UPF.
  • the source UPF can be replaced with a source PSA
  • the target UPF can be replaced with a target PSA.
  • This application is described by taking the session management network element as an SMF network element as an example.
  • FIG. 2 shows a schematic diagram 200 of an application scenario of an embodiment of the present application.
  • Figure 2 simply shows a schematic diagram of a mobile edge computing (MEC) network element based on the architecture of Figure 1.
  • the MEC network element is deployed at the UPF, which can provide low-latency and high-bandwidth services for terminal devices.
  • Figure 2 shows three transmission paths.
  • the uplink service message transmission process of path 1 is: terminal device-access network equipment 1-UPF1-MEC1-AS1, and the downlink service message transmission process is uplink service message The inverse process.
  • the uplink service message transmission process of path 2 is: terminal device-access network equipment 2-UPF2-UPF1-MEC1-AS1, and the downlink service message transmission process is the reverse process of the uplink service message.
  • the transmission process of the uplink service message of path 3 is: terminal device-access network equipment 2-UPF2-MEC2-AS2, and the transmission process of the downlink service message is the reverse process of the uplink service message.
  • a terminal device for example, UE109 in FIG. 1
  • the location of the terminal device changes.
  • the access network device of the terminal device needs to be switched to the access network device 2, that is, the air interface is switched, and the path is adopted at this time 2 Transmit service packets.
  • the packets on path 2 reach UPF1 (also known as source UPF) through access network device 2, and then are finally transmitted to AS1 through the sinking MEC1.
  • Path 2 is The path with the longest distance among the three transmission paths, so that the delay of the message transmitted on path 2 is longer.
  • URLLC ultra-reliable low-latency
  • 2 cannot meet the low-latency requirements. Therefore, it is necessary to switch the transmission path of the message from path 2 to path 3, that is, it is necessary to migrate the context of the terminal device from AS1 to AS2.
  • the message being transmitted on path 2 may be lost due to the path switching operation, which will result in a higher packet loss rate, resulting in transmission performance Poor.
  • UPF2 (also referred to as target UPF) may receive uplink service packets from path 2 and path 3 at the same time.
  • the messages received by UPF2 appear out of order, which is a big problem for business types that have strict requirements on the order of messages.
  • the method for transmitting service messages uses the interaction between the source UPF, the source MEC, the target UPF, and the target MEC.
  • the specific interaction process refer to the description in the following embodiments.
  • the uplink service message on path 2 is accurately transmitted to AS2, and the downlink service message on path 2 is accurately transmitted to the terminal device 210.
  • the functions of the MEC network elements in the embodiment of this application include: on the one hand, it supports the forwarding of user plane messages, can detect the start and end of the service, and can sense Message sequence number; on the other hand, it can interact with PCF and SMF on the control plane, and the proxy AS or the application instance on the proxy AS subscribes to the network (SMF or PCF) for DNAI change notifications.
  • Fig. 2 simply shows a schematic diagram of MEC-based message transmission. In the actual transmission process, Fig. 2 may also have other network elements. Since it is not related to this application, there is no detailed description.
  • this application combines the transmission of uplink service messages with the transmission of downlink service messages, but the embodiments of this application do not impose restrictions on this. In the actual processing process, only uplink services may exist. For message transmission, there may also be only the transmission of downlink service messages.
  • UPF means UPF network element
  • SMF means SMF network element
  • the central data center controls one or more local data centers.
  • Figure 3 shows only two local data centers (also called local source data centers and local target data centers).
  • Data center the local source data center includes source UPF, source MEC, and source AS.
  • the local target data center includes target UPF, target MEC, and target AS.
  • SMF network elements There are no SMF network elements in each local data center.
  • the central data center includes SMF, PCF, and AMF.
  • the SMF is used to obtain policy data from the PCF and control the source UPF and the target UPF according to the policy data, and the source MEC and the target MEC and PCF interact to provide application requirements.
  • the terminal device switches the air interface from the source access network device to the target access network device.
  • AMF can obtain the access information of the terminal device sent by the target access device, and report the access information of the terminal device to SMF.
  • the access information includes the location information of the terminal device.
  • the access information determines that the user plane function network element of the terminal device needs to be switched.
  • the SMF or PCF determines the data network access point identifier (data network access point) of the target AS. access identifier, DNAI).
  • the SMF or PCF sends the DNAI of the target AS and the identification of the terminal device (optionally, the identification of the application of the terminal device) to the source MEC, so that the source MEC can forward the DNAI and the identification of the terminal device to the source AS.
  • the source AS determines the target AS according to the DNAI, so that the source AS and the target AS perform the context migration of the terminal device.
  • the SMF transmits signaling to the source AS and the target AS through the NEF.
  • the central data center may also include AF, SMF can interact with source AS and target AS through AF, and SMF can interact with AF through NEF. To avoid repetition, the embodiment of the present application is not shown.
  • the central data center controls one or more local data centers.
  • Figure 4 only shows two local data centers (also called local source data centers and local target data centers).
  • Data center the local source data center includes source UPF, source MEC, and source AS.
  • the local target data center includes target UPF, target MEC, and target AS.
  • SMF network elements There are no SMF network elements in each local data center.
  • Fig. 4 is basically the same as Fig. 3, the difference is that the MEC application management network element is introduced in Fig. 4.
  • the MEC application management network element may be a virtual network function manager (VNFM).
  • VNFM virtual network function manager
  • the MEC application management network element is used to manage the source AS and the target AS, including managing the life cycle of application instances on the source AS and the target AS, such as instantiating an MEC application instance and migrating an MEC application instance from the source AS to the target AS. Accept registration of application instances on the source AS and target AS.
  • the source MEC When the source MEC obtains the DNAI of the target AS and the identification of the application of the terminal device from the SMF or PCF, the source MEC can determine the identification of the application instance according to the identification of the application of the terminal device, thereby sending the identification of the application instance and the DNAI to the MEC
  • the application management network element of the MEC triggers the source AS and the target AS to perform the context migration of the application instance, and the context of the application instance can be migrated from the source AS to the target AS.
  • the central data center may also include the control plane network element AF of the AS.
  • the SMF can interact with the source AS and the target AS through the control plane network element AF of the AS, and the SMF can interact with the AF through the NEF.
  • FIG. 5 shows a method 200 for transmitting service packets provided by an embodiment of the present application.
  • the method 200 includes:
  • the target UPF sends a first uplink service packet to the source UPF, and the source UPF receives the first uplink service packet sent by the target UPF. After the target UPF sends the first uplink service packet to the source UPF, no longer sends the uplink service packet to the source UPF. That is, when the target UPF receives the uplink service message again, it can send the uplink service message directly to the target MEC. In this way, in S270, the target MEC sends the first uplink service message to the target AS after sending it to the target AS Uplink service packets directly from the target UPF.
  • the target UPF sends second indication information to the source UPF, where the second indication information is used to indicate that the target UPF ends sending the first uplink service packet.
  • the source UPF sends a first uplink service packet to the source MEC, and the source MEC receives the first uplink service packet sent by the source UPF.
  • S240 The source UPF sends second indication information to the source MEC, and the source MEC receives the second indication information sent by the source UPF.
  • the source MEC network element sends a first uplink service packet to the target MEC network element, the target MEC receives a first uplink service packet from the source MEC, and the first uplink service packet is received by the source MEC network element An uplink service packet received after the second uplink service packet, where the second uplink service packet is the last uplink service packet sent by the source MEC network element to the source AS.
  • the source MEC After the source MEC receives the second indication information, the source MEC sends the first indication information to the target MEC, and the target MEC receives the first indication information from the source MEC.
  • the first indication information is used to instruct the source MEC to send the first uplink service report.
  • the text ends, so that the target MEC can determine that the uplink service message from the source MEC is over.
  • the first indication information and the second indication information may be signaling between different network elements, but the first indication information and the second indication information may include the same information element, that is, the same information element may be It is the identifier of the end of the uplink service packet, that is, when the target user plane network element sends the second indication information to the source user plane network element, and the source user plane network element forwards the second indication information to the source mobile edge computing network element, the source The mobile edge computing network element can determine that the uplink service packet from the target user plane network element is over, that is, the source user plane network element will no longer send uplink service packets from the target user plane network element to the source mobile edge computing network element; After the source mobile edge computing network element sends the first indication information to the target mobile edge computing network element, the target mobile edge computing network element can determine that the uplink service packet from the source mobile edge computing network element ends, that is, the source mobile edge computing network element No more uplink service packets will be sent to the target mobile edge computing network element.
  • the target UPF first sends the second indication information to the source UPF to indicate the end of the first uplink service packet sent from the target UPF, the source UPF may forward the second indication information to the source MEC, and the source MEC sends the second indication
  • the information element in the information is sent to the target MEC as the information element of the first indication information, so that the target MEC can learn that the first uplink service message from the source MEC has also been sent.
  • the first indication information and the second indication information are used to distinguish the signaling between different network elements.
  • the first indication information and the second indication information may also be the same indication information, that is, the target UPF first Send the instruction information to the source UPF, the source UPF then sends the instruction information to the source MEC, and the source MEC sends the instruction information to the target MEC.
  • the first indication information or the second indication information can indicate the end of sending the uplink service message on the original path or the old path.
  • the original path or the old path is: target UPF-source UPF-source MEC-target MEC, regardless of If the source MEC receives the second indication information or the target MEC receives the first indication information, the source MEC and the target UPF can determine that there will be no more uplink service packets on the original path or the old path in the future.
  • the sequence between the second indication information and the first uplink service message (S210 and S220, or S230 and S240) and the sequence between the first indication information and the first uplink service message (S250 and S240) S260) is the same, that is, the first uplink service message in S210 is before the second indication information in S220, and the first uplink service message in S230 is also before the second indication information in S240, so the first uplink service message in S250 An uplink service message is also before the first indication information in S260; if the first uplink service message and the second indication information in S210 and S220 are sent at the same time, the first uplink service message and the second indication information in S230 and S240 The second indication information is also sent at the same time, and the first uplink service packet and the first indication information in S250 and S260 are also sent at the same time.
  • the following two situations are described:
  • the target UPF can send the first uplink service message in S210 and the second indication information in S220 to the source UPF at the same time.
  • the first uplink service message is the last uplink service sent by the target UPF to the source UPF Message
  • the second indication information may be encapsulated in the header of the first uplink service message and sent to the source UPF.
  • the source UPF can send the first uplink service packet in S230 and the second indication information in S240 to the source MEC at the same time.
  • the second indication information may be encapsulated in the header of the first uplink service message and sent to the source MEC.
  • the source MEC can send the first uplink service packet in S250 and the first indication information in S260 to the target MEC at the same time.
  • the first indication information may be encapsulated in the header of the first uplink service message and sent to the target MEC.
  • Case 2 The target UPF first sends the first uplink service message to the source UPF, and then sends the uplink service message carrying the second indication information.
  • the source UPF can first send the first uplink service packet to the source MEC, and then send the uplink service packet carrying the second indication information.
  • the source MEC can first send the first uplink service packet to the target MEC, and then send the first uplink service packet to the target MEC.
  • An uplink service message indicating information For example, the uplink service message carrying the first indication information or the uplink service message carrying the second indication information has the same data packet format as the first uplink service message.
  • the first uplink service message is General Packet Radio Service tunneling protocol (GPRS tunnelling protocol, GTP) data packet, where GPRS stands for general packet radio service, and GTP data packet includes user-level general packet radio service (GTP for the user plane, GTP-U) Header, then the uplink service message carrying the first indication information and the uplink service message carrying the second indication information are also GTP data packets.
  • the first indication information can be set in the specific identification bit of the GTP-U header, for example, The specific flag is set to "0" or "1". Except for the specific identification bit, the GTP-U headers of the uplink message carrying the first indication information and the uplink service message carrying the second indication information are exactly the same as those of the first uplink service message.
  • the target UPF sends the first uplink service packet and the second indication information to the source UPF, and after the target UPF sends the first uplink service packet to the source UPF, it no longer sends the uplink service to the source UPF Message, the source UPF forwards the first uplink service packet and the second indication information to the source MEC.
  • the source MEC After the source MEC sends the last second uplink service packet to the source AS, the first uplink service packet after the second uplink service packet An uplink service message is sent to the target AS through the target MEC, so that the loss of the first uplink service message can be avoided, and the source MEC can send first indication information to the target MEC to instruct the source MEC to send the first uplink service message to the end, This can prevent the target MEC from waiting to receive the uplink service packet sent by the source MEC. After receiving the first indication information, the target MEC sends the uplink service packet from the source MEC to the target AS, and then sends it to the target UPF. The uplink service packets of the target MEC can avoid the disorder of uplink service packets.
  • FIG. 6 shows a method 300 for transmitting service packets provided by an embodiment of the present application, including:
  • the source application server AS receives a first message, where the first message is used to trigger the source AS to migrate the context of the terminal device, and the first message includes the target DNAI;
  • the source AS may receive the first message sent by the source MEC.
  • the first message may be a context migration request message for requesting the source AS to migrate the context of the terminal device.
  • the source AS may receive the first message sent by the MEC application management network element.
  • the first message may be the second trigger message in the method 400.
  • the source AS and the target AS corresponding to the target DNAI perform the context migration of the terminal device, wherein
  • the first downlink service packet is the last downlink service packet sent by the source AS to the source mobile edge computing MEC network element
  • the second uplink service packet is the source MEC network element to the source AS The last uplink service message sent.
  • the source AS after the source AS receives the first message, it can determine that the context of the terminal device needs to be migrated. After determining that the context of the terminal device needs to be migrated, the source AS determines that the last downlink service packet (first After the downlink service message) and the last received uplink service message (the second uplink service message), the source AS determines the corresponding target AS according to the target DNAI in the first message, and migrates the context of the terminal device to The target AS, in this way, after the context of the terminal device is migrated to the target AS, the continuous transmission of the uplink and downlink service packets of the terminal device can be guaranteed.
  • the context migration of the terminal device in the present invention refers to the migration of the application instance or the context migration of the transport layer and the application layer of the terminal device. Specifically, it can be the overall migration of an application instance of the terminal device, for example, when an MEC When an application instance only serves one UE, context migration refers to the migration of the entire application instance related to the terminal device and the data network (DN) from one AS to another AS; it can also be the migration of the context of the transport layer and application layer of the terminal device. For example, when multiple terminal devices share an MEC application instance, the context migration of the terminal device refers to the migration of the transport layer and application layer context of the application that the terminal device needs to migrate from one AS to another AS.
  • DN data network
  • FIG. 7 shows a method 400 for transmitting service messages provided by an embodiment of the present application, including:
  • the source MEC sends a first migration request message to the MEC application management network element, and the MEC application management network element receives the first migration request message sent by the source MEC network element, where the first migration request message includes the identifier of the first application instance and The target data network access point identifies DNAI.
  • the application management network element of the MEC may be a VNFM.
  • the MEC application management network element determines the first application instance to be migrated according to the identifier of the first application instance.
  • the MEC application management network element sends a first trigger message to the target AS corresponding to the target DNAI, where the first trigger message includes the identifier of the first application instance, and the first trigger message is used to trigger the target
  • the AS performs the migration of the application instance.
  • the MEC application management network element sends a second trigger message to the source AS corresponding to the source application instance, and the source AS receives the second trigger message, where the second trigger message is used to trigger the source AS to perform the first application Migration of instances.
  • an application instance identifier corresponds to an application instance
  • the first migration request message sent by the source MEC to the MEC application management network element includes the identifier of the first application instance, so that the MEC application management network element can be based on the first application instance
  • the identifier of determines the first application instance to be migrated, and can determine the source AS where the first application instance is located, that is, the AS running the first application instance is the source AS, and the second trigger message is sent to the source AS to trigger the source AS to perform
  • the MEC application management network element may carry the identification of the first application instance in the first trigger message and send it to the target AS. In this way, the context of the first application instance can be migrated from the source AS to the target AS.
  • the virtual resource of the first application instance may be created in the target AS, so that the target AS can follow the The virtual resource migrates the first application instance.
  • FIG. 8 shows a method 500 for transmitting service messages provided by an embodiment of the present application, including:
  • the source MEC network element sends a first message to the source AS, and the source AS receives the first message sent by the source MEC, where the first message includes the target DNAI.
  • the first message may be the fourth migration request message mentioned below, which is used to request the source AS to migrate the context of the terminal device.
  • the application management network element of the MEC may send a first message to the source AS.
  • the first message may be the aforementioned second trigger message for triggering the source AS to migrate the first application instance.
  • the source AS After receiving the first message, the source AS determines that the last downlink service packet sent by the source AS to the source MEC is the first downlink service packet, the source AS sends fourth indication information to the source MEC, and the source MEC receives the source AS The sent fourth indication information, where the fourth indication information is used to indicate that the first downlink service packet is the last downlink service packet from the source AS.
  • the fourth indication information may be the sequence number of the first downlink service packet.
  • the source AS may send the first downlink service packet to the source MEC before sending the fourth indication information to the source MEC.
  • the source AS after sending the fourth indication information to the source MEC, the source AS sends the first industry service message to the source MEC.
  • the source AS sends the fourth indication information and the first downlink service packet to the source MEC at the same time.
  • the fourth indication information may be included in the header of the first downlink service packet. Regardless of the sending order of the fourth indication information and the first downlink service packet, the source AS will not send the downlink service packet to the source UPF after sending the first downlink service packet to the source MEC.
  • the source AS may pre-freeze the context of the terminal device, for example, interact with the target AS to prepare for the context migration of the terminal device, which can shorten the context migration time of the terminal device.
  • the source MEC After the source MEC receives the fourth indication information sent by the source AS, the source MEC sends fifth indication information to the source AS, and the source AS receives the fifth indication information sent by the source MEC, where the fifth indication information is used to indicate the second uplink
  • the service message is the last uplink service message sent by the source MEC to the source AS.
  • the fifth indication information may be the sequence number of the second uplink service packet.
  • the management network element of the source AS may send the fourth indication information to the source MEC.
  • the source MEC may send the fifth indication information to the management network element of the source AS, and then the management network element of the source AS forwards the fifth indication information to the source AS.
  • the source AS may determine that the second uplink service packet is the last uplink service packet from the source MEC, and the source AS determines the processing of the first downlink service packet and the second uplink service packet complete.
  • the source AS may determine that the processing of the second uplink service packet is complete after receiving the second uplink service packet and replying to the confirmation message of the second uplink service packet; it may determine that the processing of the second uplink service packet is complete; After receiving the confirmation message of the first downlink service packet, it is determined that the processing of the first downlink service packet is completed.
  • the source AS may also consider that the processing of the second uplink service packet is complete after receiving the second uplink service packet, and that the processing of the first downlink service packet is complete after sending the first downlink service packet.
  • S506 After the source MEC receives the first downlink service packet sent by the source AS, the source MEC sends the first downlink service packet to the source UPF, and the source UPF receives the first downlink service packet sent by the source MEC.
  • the source MEC sends third indication information to the source UPF, and the source UPF receives the third indication information sent by the source MEC, where the third indication information is used to indicate the end of sending the downlink service packet from the source AS.
  • the source MEC may first send the first downlink service message, and then send the downlink message carrying the third indication information.
  • the downlink message carrying the third indication information has the same characteristics as the first downlink service message.
  • the same data packet format for example, if the first downlink service packet is a GTP data packet and includes a GTP-U header, then the downlink packet carrying the third indication information is also a GTP data packet, and the third indication information can be set in The specific identification bit of the GTP-U header, for example, the specific identification bit is set to "0" or "1".
  • the GTP-U header of the downlink packet carrying the third indication information is exactly the same as that of the first downlink service packet; optionally, the source MEC may combine the first downlink service packet with the first downlink service packet.
  • the three indications are sent to the source UPF at the same time, for example, the third indication is encapsulated in the header of the first downlink service message.
  • the context migration between the source AS and the target AS may be performed simultaneously with the source MEC sending the first downlink service message and the third indication information to the source UPF or may be in a sequence. In other words, S504 and S505 can be performed before or after S506 and S507 or at the same time.
  • S508 The source UPF sends a first downlink service packet to the target UPF, and the target UPF receives the first downlink service packet sent by the source UPF.
  • the source UPF sends third indication information to the target UPF, and the target UPF receives the third indication information sent by the source UPF.
  • the source UPF may also send the first downlink service packet and then send it
  • the downlink message carrying the third indication information that is, S508 is performed first, and then S509; if the source MEC in S506 and S507 sends the first downlink service message and the third indication information to the source UPF at the same time, the source in S508 and S509
  • the UPF simultaneously sends the first downlink service message and the third indication information received from the source MEC to the target UPF.
  • the target AS may send a downlink service packet of the terminal device to the target MEC.
  • S511 The target MEC sends the downlink service message in S510 to the target UPF.
  • the target UPF If the target UPF receives both the first downlink service packet from S506 and the downlink service packet from the target MEC, the target UPF will immediately send the first downlink service packet from the source AS to the access network device Message, if the target UPF has a downlink service message from the target MEC before receiving the third indication information, the downlink service message from the target MEC is buffered, and when the target UPF receives the third indication information, it determines to After the access network device has sent the first downlink service message, it then sends the downlink service message from the target MEC to the access network device. In this way, the downlink service message from the source AS can be guaranteed to be transmitted first, and then from the target The downlink service packets of the AS can avoid the disorder of the downlink service packets.
  • the access network device sends the downlink service packet received in S512 to the terminal device through the air interface.
  • the terminal device does not perceive the switching of the network element on the network side, and the terminal device may also send an uplink service packet to the access network device while receiving the downlink service packet.
  • S515 The access network device sends an uplink service packet from the terminal device to the target UPF.
  • S515 only needs to be after S514. There is no sequence restriction on S515 and the other steps mentioned above.
  • S515 is executed without any sequence restriction.
  • the target UPF After receiving the uplink service packet sent by the access network device, the target UPF sends the first uplink service packet to the source UPF. Until the target UPF receives the third indication information, the target UPF no longer sends uplink to the source UPF. Business message.
  • the target UPF After receiving the third indication information, the target UPF sends second indication information to the source UPF, where the first indication information is used to indicate the end of sending the first uplink service packet through the target UPF, that is, the target UPF will no longer send to the source UPF Uplink service packets.
  • the target UPF after the target UPF receives the downlink service message from the target MEC or the context migration complete message sent from the target MEC, the target UPF sends the second indication information to the source UPF.
  • the target UPF can send the second indication information to the source UPF in two cases.
  • Case 1 The target UPF sends the second indication information to the source UPF after receiving the third indication information sent by the source UPF;
  • Case 2 The target UPF sends the second indication information to the source UPF after receiving the downlink service message of the target MEC or the context migration complete message sent from the target MEC.
  • the second indication information may be sent after the last first uplink service message, that is, the target UPF first sends the first uplink service message to the source UPF, and then sends the uplink message carrying the second indication information.
  • the uplink message of the second indication information has the same data packet format as the first uplink service message. For example, if the first uplink service message is a GTP data packet and includes a GTP-U header, then the one that carries the second indication information
  • the uplink service message is also a GTP data packet, and the second indication information may be set in a specific identification bit of the GTP-U header, for example, the specific identification bit is set to "0" or "1".
  • the GTP-U header of the uplink message carrying the second indication information is exactly the same as that of the first uplink service message.
  • the target UPF may also encapsulate the second indication information in the header of the last first uplink service packet and send it to the source UPF.
  • S518 When the source UPF receives the first uplink service packet from the target UPF, it forwards the first uplink service packet to the source MEC, and the source MEC receives the first uplink service packet from the source UPF.
  • the source UPF also forwards the second indication information from the target UPF to the source MEC, and the source MEC receives the second indication information from the source UPF.
  • the source MEC After sending the fifth indication information to the source AS, the source MEC forwards the first uplink service packet to the target MEC when receiving the first uplink service packet from the target UPF.
  • the source MEC After the source MEC receives the second indication information, the source MEC sends the first indication information to the target MEC, so that the target MEC can determine the end of the uplink service message from the source MEC through the first indication information.
  • the first indication information and the second indication information For related descriptions of the first indication information and the second indication information, refer to the description in the method 200.
  • the source UPF sends the first uplink service packet and the second indication information to the source MEC in order, that is, the source UPF sends the first uplink service packet to the source MEC according to the order in which the first uplink service packet and the second indication are received.
  • Message and second instruction information The source MEC sends the first uplink service packet and the first indication information to the target MEC in sequence.
  • the order relationship between the second indication information and the first uplink service packet is the same as the order relationship between the first indication information and the uplink service packet.
  • the source MEC After the MEC receives the first uplink service packet sent by the source UPF and then receives the second indication information sent by the source UPF, the source MEC first sends the first uplink packet to the target MEC before sending the first indication information, that is, the source MEC Send the first uplink service packet and the first indication information to the target MEC according to the order of receiving the first uplink service packet and the second indication information.
  • the target UPF After the target UPF sends the first uplink service packet and the second indication information to the source UPF, it no longer sends the uplink service packet to the source UPF. When it receives the uplink service packet from the access network device again, it needs to The target MEC sends.
  • the target MEC may send an uplink service message to the target AS.
  • the sending process is: first send the first uplink service message, that is, the uplink service message from the source MEC, and then send the uplink access message from the target UPF, in other words, send the first uplink service of S520 first Message, and then send the uplink service message of S522.
  • the target UPF determines according to the third indication information that it will no longer send uplink service packets to the source UPF, that is, the target UPF sends second indication information to the source UPF to indicate the end of the uplink service packets from the target UPF, and the target UPF sends to the target MEC in sequence Send message 4 and message 5.
  • message 1, message 2, and message 3 are the first uplink service messages, and the source UPF receives message 1, message 2, message 3, and the second instruction in sequence
  • message 1, message 2, message 3, and second instruction information are sent to the source MEC in sequence, and the source MEC receives message 1, message 2, message 3, and the second instruction information in sequence.
  • message 1, message 2, message 3, and message 4 are the first uplink service messages.
  • the source UPF sends message 1, message 2, message 3, and message 4 to the source MEC in sequence, and the source MEC sends the message to the target
  • the MEC sends message 1, message 2, message 3, and message 4 in order (the second indication information in message 4 is replaced with the first indication information at this time), and the target MEC decodes the message header of message 4
  • the target MEC decodes the message header of message 4
  • the first uplink service packet is an uplink service packet that has been sent to the source UPF or source MEC but has not been forwarded to the source AS during the context migration process of the terminal device, and has been sent to the source UPF or source MEC.
  • the message can also be called the old path or the message on the original path.
  • the message on the old path or the original path needs to be forwarded to the target MEC, and forwarded to the target AS through the target MEC to avoid upstream service packets. Lost.
  • the first indication information indicates the end of the old path or the message on the original path, so that the target MEC guarantees that after the uplink service message on the old path or the original path is sent, the uplink service message from the target UPF can be sent again. Avoid out-of-sequence problems in uplink service packets.
  • the following describes a method 600 for transmitting service packets in the scenario of FIG. 3 provided by an embodiment of the present application in conjunction with FIG. 9.
  • the method 600 includes:
  • the SMF or PCF determines that the DNAI of the terminal device needs to be changed after the UPF is switched, and determines that context migration or application relocation of the terminal device needs to be performed, and the SMF or PCF determines the target DNAI.
  • the SMF or PCF sends a second migration request message to the source MEC, the source MEC receives the second migration request message sent by the SMF or PCF, the second migration request message is used to trigger the migration of the context of the terminal device, and the second migration request message includes the target DNAI and the identification of the terminal device.
  • the identification of the terminal device may be the identity of the terminal device (identity, ID) or the internet protocol (IP) address of the terminal device, or it may be the generic public subscription identifier (GPSI) of the terminal device. Wait.
  • the source MEC After receiving the second relocation request message, the source MEC sends a third relocation request message to the target MEC.
  • the third relocation request message is used to request the target MEC whether to accept the relocation of the context of the terminal device.
  • the third relocation request message includes the terminal The identification of the device.
  • S604 If the target MEC can accept the transition of the terminal device context, send a response message of the third migration request message to the source MEC, where the response message of the third migration request message is used to indicate that the target MEC can accept the transition of the terminal device context.
  • the target MEC sends a fourth migration request message to the target AS, and the target AS receives the fourth migration request message sent by the target MEC.
  • the fourth migration request message is used to request the target AS whether the migration of the context of the terminal device can be accepted, or the first
  • the fourth migration request message is used to indicate the context migration of the target AS terminal device, and the fourth migration request message includes the identification of the terminal device.
  • the fourth migration request message further includes the source DNAI corresponding to the source AS.
  • the target AS If the target AS accepts the transition of the terminal device context, it sends a response message of the fourth request message to the target MEC.
  • the response message of the fourth transition request message is used to indicate that the target AS can receive the transition of the terminal device context.
  • the source MEC After receiving the second migration request message, the source MEC sends a fifth migration request message to the source AS.
  • the fifth migration request message is used to request the AS to migrate the context of the terminal device, and the fifth migration request message includes the identification and Target DNAI.
  • the aforementioned first message may be the fifth migration request message here.
  • the method 600 further includes: S608. After the source AS receives the fifth migration request message, the source AS pre-freezes the context of the terminal device to prepare for the context of the terminal device to be migrated.
  • S608 can be after S602, and there is no restriction on the order of S608 and S603.
  • the embodiment of the present application only uses the context of the terminal device to be migrated between the source AS and the target AS as an example.
  • the source AS and the target AS can also migrate application instances of the terminal device.
  • the second migration request message, the third migration request message, the fourth migration request message, and the fifth migration request message are also Including: the identification of the application or the identification of the application instance, so that the source AS and the target AS can migrate the application instance of the terminal device.
  • the source AS sends fourth indication information to the source MEC, where the fourth indication information is used to indicate that the first downlink service packet is the last downlink service packet from the source AS, that is, the source AS has finished sending the first downlink service packet. After the message, no more downlink service messages are sent to the source MEC.
  • the fourth indication information may be the sequence number of the first downlink service packet.
  • the source AS may send the first downlink service packet to the source MEC before sending the fourth indication information to the source MEC.
  • the source AS sends the first downlink service packet to the source MEC after sending the fourth indication information to the source MEC.
  • the source AS sends the fourth indication information and the first downlink service packet to the source MEC at the same time.
  • the fourth indication information may be included in the header of the first downlink service packet. Regardless of the sending order of the fourth indication information and the first downlink service packet, the source AS will not send the downlink service packet to the source UPF after sending the first downlink service packet to the source MEC.
  • the source MEC After receiving the fourth indication information, the source MEC sends fifth indication information to the source AS.
  • the fifth indication information is used to indicate that the second uplink service packet is the last uplink service packet sent by the source MEC to the source AS, that is After sending the second uplink service packet to the source AS, the source MEC no longer sends the uplink service packet to the source AS.
  • the fifth indication information may be the sequence number of the second uplink service packet.
  • the management network element of the source AS may send the fourth indication information to the source MEC.
  • the source MEC may send the fifth indication information to the management network element of the source AS, and then the management network element of the source AS forwards the fifth indication information to the source AS.
  • the source AS determines that the second uplink service packet is the last uplink service packet from the source UPF according to the fifth indication information, and the source AS determines the last transmitted first downlink service packet and the last received second uplink service packet The message is processed.
  • the source AS may determine that the processing of the second uplink service packet is complete after receiving the second uplink service packet and replying to the confirmation message of the second uplink service packet; it may determine that the processing of the second uplink service packet is complete; After receiving the confirmation message of the first downlink service packet, it is determined that the processing of the first downlink service packet is completed.
  • the source AS may also consider that the processing of the second uplink service packet is completed after receiving the second uplink service packet, and that the processing of the first downlink service packet is complete after sending the first downlink service packet.
  • the source AS determines the target AS according to the target DNAI, and completes the context migration of the terminal device with the target AS.
  • the first downlink service packet is the last downlink service packet from the source AS. After the source MEC receives the first downlink service packet sent by the source AS, the source MEC sends the first downlink service packet to the source UPF. The source UPF receives the first downlink service packet sent by the source MEC.
  • the source MEC After receiving the fourth indication information, the source MEC sends third indication information to the source UPF, and the source UPF receives the third indication information sent by the source MEC, where the third indication information is used to instruct the sending of a downlink service packet from the source AS End.
  • the third indication information may indicate that the downlink service message from the old path or the original path ends.
  • S615 and S616 can be performed simultaneously, that is, the source MEC can send the third indication information and the first downlink service packet to the source UPF at the same time, for example, encapsulate the third indication information in the first downlink service packet
  • S615 and S616 are after S609.
  • S616 is just after S609, and the sequence of S615 and S609 Not limited.
  • the source MEC receives the fourth indication information, it triggers the source MEC to send the third indication information to the source UPF.
  • the first downlink service message and the third indication information are sent at the same time, the first downlink service message and The third indication information is sent after S609; if the first downlink service message is sent before the third indication information, the third indication information can be sent after S609, and the order of S615 and S609 is not limited.
  • the source UPF sends the first downlink service packet from the source MEC to the target UPF.
  • the source UPF sends the third indication information from the source MEC to the target UPF.
  • the source UPF may also send the first downlink service packet and then send it
  • the downlink service message carrying the third indication information that is, S617 is performed first, and then S618; if the source MEC in S615 and S616 sends the first downlink service message and the third indication information to the source UPF at the same time, then S617 and S618
  • the source UPF simultaneously sends the first downlink service packet and the third indication information received from the source MEC to the target UPF.
  • S620 The target MEC sends the downlink service message in S619 to the target UPF.
  • the target UPF has received the first downlink service packet from the source UPF in S617 and the downlink service packet from the target MEC in S619, if the target UPF has received the first downlink service packet from the target MEC before receiving the third indication information
  • the target UPF determines to send the first downlink service message to the access network device before sending the first downlink service message to the access network device.
  • the network access device sends the downlink service message from the target MEC, so that it can ensure that the downlink service message from the source AS is transmitted first, and then the downlink service message from the target AS is transmitted, which can avoid the disorder of the downlink service message.
  • the access network equipment sends the downlink service message received in S621 to the terminal device through the air interface.
  • the terminal device does not perceive the handover on the network side, and the terminal device is also sending an uplink service packet to the access network device while receiving the downlink service packet.
  • S624 The access network device sends an uplink service message from the terminal device to the target UPF.
  • S624 only needs to be after S623. There is no sequence restriction between S624 and the other steps mentioned above.
  • S624 is executed without any sequence restriction.
  • the target UPF After receiving the uplink service packet sent by the access network device, the target UPF sends the first uplink service packet to the source UPF. Until the target UPF receives the third indication information, the target UPF no longer sends uplink to the source UPF. Business message.
  • the target UPF After receiving the third indication information, the target UPF sends second indication information to the source UPF, where the first indication information is used to indicate that the first uplink service packet sent through the source UPF ends, that is, the target UPF will not send any further information to the source UPF. Send uplink service packets.
  • the target UPF after the target UPF receives the downlink service message from the target MEC or the context migration complete message sent from the target MEC, the target UPF sends the second indication information to the source UPF. After S619, the target MEC may send a context migration complete message to the target UPF.
  • the target UPF can send the second indication information to the source UPF in two cases.
  • Case 1 The target UPF sends the second indication information to the source UPF after receiving the third indication information sent by the source UPF;
  • Case 2 The target UPF sends the second indication information to the source UPF after receiving the downlink service message of the target MEC or the context migration complete message sent from the MEC.
  • the second indication information may be sent after the last first uplink service message, that is, the target UPF first sends the first uplink service message to the source UPF, and then sends the uplink service message carrying the second indication information.
  • the uplink service message carrying the second indication information has the same data packet format as the first uplink service message. For example, if the first uplink service message is a GTP data packet and includes a GTP-U header, then the second indication is carried
  • the uplink message of the information is also a GTP data packet, and the second indication information can be set in a specific identification bit of the GTP-U header, for example, the specific identification bit is set to "0" or "1".
  • the GTP-U header of the uplink message carrying the second indication information is exactly the same as that of the first uplink service message.
  • the target UPF may also encapsulate the second indication information in the header of the last first uplink service packet and send it to the source UPF.
  • S627 When the source UPF receives the first uplink service packet from the target UPF, it forwards the first uplink service packet to the source MEC, and the source MEC receives the first uplink service packet from the source UPF.
  • the source UPF also forwards the first indication information from the target UPF to the source MEC, and the source MEC receives the first indication information from the source UPF.
  • S629 After sending the fifth indication information to the source AS, the source MEC forwards the first uplink service packet to the target MEC when receiving the first uplink service packet from the source UPF.
  • the source MEC After the source MEC receives the second indication information, the source MEC sends the first indication information to the target MEC, so that the target MEC can determine the end of the uplink service message from the source MEC through the first indication information.
  • the first indication information and the second indication information For related descriptions of the first indication information and the second indication information, refer to the description in the method 200.
  • the source UPF sends the first uplink service packet and the second indication information to the source MEC in order, that is, the source UPF sends the first uplink service packet to the source MEC according to the order in which the first uplink service packet and the second indication are received.
  • Message and second instruction information The source MEC sends the first uplink service packet and the first indication information to the target MEC in sequence.
  • the order relationship between the second indication information and the first uplink service packet is the same as the order relationship between the first indication information and the uplink service packet.
  • the source MEC After the MEC receives the first uplink service packet sent by the source UPF and then receives the second indication information sent by the source UPF, the source MEC first sends the first uplink packet to the target MEC before sending the first indication information, that is, the source MEC Send the first uplink service packet and the first indication information to the target MEC according to the order of receiving the first uplink service packet and the second indication.
  • the target UPF After the target UPF sends the first uplink service packet and the second indication information to the source UPF, it no longer sends the uplink service packet to the source UPF. When it receives the uplink service packet from the access network device again, it needs to The target MEC sends.
  • S632 After S613, it indicates that the target MEC has established a link with the target AS, and the target MEC can send uplink service packets to the target AS. Alternatively, after the target MEC receives the downlink service message from the target AS, the target MEC determines that a link is established with the target AS, and the target MEC may send the uplink service message to the target AS. Specifically, the sending process is: first send the first uplink service message, that is, the uplink service message from the source MEC in S629, and then send the uplink access message directly from the target UPF in S631.
  • the target MEC before the target MEC determines that it can send an uplink service message to the target AS, the target MEC will buffer the uplink service message sent directly from the target UPF.
  • the source AS registers with the source MEC, and the registration content includes an application identifier; optionally, the registered content may also include an application instance (application identifier). instance) identifier or service flow template (traffic filtering information, such as the five-tuple of the service). With this information, the source MEC can detect the beginning and end of the business.
  • the source AS registers with the source MEC, and the registration content includes a service identifier; optionally, the registered content may also include an application instance identifier or a service flow template. With this information, the target MEC can detect the beginning and end of the business.
  • the first uplink service packet is an uplink service packet that has been sent to the source UPF or source MEC but has not been forwarded to the source AS during the context migration process of the terminal device, and has been sent to the source UPF or source MEC.
  • the message can also be called the old path or the message on the original path.
  • the message on the old path or the original path needs to be forwarded to the target MEC, and forwarded to the target AS through the target MEC to avoid upstream service packets. Lost.
  • the first indication information indicates the end of the old path or the message on the original path, so that the target MEC guarantees that after the uplink service message on the old path or the original path is sent, the uplink service message from the target UPF can be sent again. Avoid out-of-sequence problems in uplink service packets.
  • the following describes a method 700 for transmitting service packets in the scenario of FIG. 4 provided by an embodiment of the present application in conjunction with FIG. 10.
  • the method 700 includes:
  • the SMF or PCF determines that the DNAI of the terminal device needs to be changed after the UPF is switched, and determines that the first application instance relocation of the terminal device needs to be performed, and the SMF or PCF determines the target DNAI.
  • the SMF or PCF sends a second migration request message to the source MEC, and the source MEC receives the second migration request message sent by the SMF or PCF.
  • the second migration request message is used to trigger the migration of the context of the first application instance, and the second migration request message Including the target DNAI and the identification of the first application instance.
  • the source MEC After receiving the second migration request message, the source MEC sends a third migration request message to the target MEC.
  • the third migration request message is used to request the target MEC whether to accept the migration of the context of the first application instance, and the third uplink migration
  • the request message includes the identification of the first application instance.
  • S704 If the target MEC can accept the migration of the terminal device context, send a response message of the third migration request message to the source MEC, where the response message of the third migration request is used to indicate that the target MEC can accept the migration of the first application instance context.
  • the source MEC sends a first migration request message to the MEC application management network element, where the first migration request message is used to request the MEC application management network element to migrate the context of the first application instance, and the first migration request message includes the context of the first application instance. Identification and target DNAI.
  • the MEC application management network element sends a response message of the first migration request message to the source MEC, which is used to indicate that the MEC application management network element can accept the migration of the context of the first application instance.
  • the MEC application management network element sends a second trigger message to the source AS, where the second trigger message is used to trigger the source AS to migrate the first application instance.
  • the MEC application management network element After the MEC application management network element determines the target AS corresponding to the target DNAI, it creates a virtual resource of the first application instance at the target AS, so that the target AS migrates the first application instance according to the virtual resource. For example, the MEC application management network element may instruct the target AS to install a virtual machine, and use the virtual machine to migrate the first application instance.
  • the MEC application management network element sends a first trigger message to the target AS, where the first trigger message includes the identifier of the first application instance.
  • sequence of S707 and S709 is not limited in any way, and can be performed simultaneously or in a sequence, which is not limited in the embodiment of the present application.
  • the method 700 further includes: S710. After the source AS receives the second trigger message, the source AS pre-freezes the context of the first application instance in preparation for migrating the context of the first application instance.
  • S711-S714 are the same as S609-S612.
  • sequence of S714 and S715 is not limited in any way, and can be performed simultaneously or in a sequence, which is not limited in the embodiments of the present application.
  • S717 The MEC application management network element sends a context migration complete message to the source MEC.
  • S718 The MEC application management network element sends an uplink completion message to the target MEC.
  • the target AS sends a service registration request to the target MEC.
  • the service registration request is used to request a service ID.
  • the service ID is used to identify an application.
  • One application can correspond to multiple application instances. In this way, one service identity can correspond to multiple applications.
  • the registered content can also include application instance identification or service flow template (traffic filtering information, such as the five-tuple of the service). With this information, the target MEC can detect the start and end of the service .
  • S719 can be after S715, and the order of S719, S717 and S718 is not limited.
  • S720-S737 is the same as S615-S632.
  • the transmission path of the downlink service message is: source AS-source MEC source UPF-source access network equipment-terminal device.
  • the transmission path of the downlink service message is: source AS-source MEC-source UPF-target UPF-target access network equipment-terminal device, this path is called the old path or the original path.
  • the transmission path of the service message on the old path or the original path becomes longer, resulting in a longer delay of the message on the old path or the original path.
  • Target AS-target MEC-target UPF-target access network equipment-terminal device it is necessary to switch the path of the downlink service message to the new path : Target AS-target MEC-target UPF-target access network equipment-terminal device.
  • the target UPF can simultaneously receive downlink service packets from the old path and the new path, that is, the target UPF can receive both the downlink service packets sent by the source UPF and the downlink service packets sent by the target MEC.
  • the source AS sends fourth indication information to the source MEC to indicate that the last downlink service packet sent by the source AS to the source MEC is the first downlink service packet, and the source MEC receives the first downlink service packet.
  • the source MEC sends third indication information to the source UPF, and the source UPF forwards the third indication information to the target UPF to indicate the downlink from the source AS The service message ends.
  • the target UPF Before receiving the third indication information, the target UPF sends the downlink service packets from the old path to the target access network device in sequence, and buffers the packets from the new path until the target UPF receives the third indication Information and ensure that the downlink service packets on the old path have been sent, and then the downlink service packets on the new path are sent. In this way, the problem of disorder of downlink service packets can be avoided. In other words, for the target UPF, it is necessary to ensure that the downlink service packets on the old path are all sent before the downlink service packets on the new path can be sent.
  • the transmission path of the uplink service message is: terminal device-source access network equipment-source UPF-source MEC-source AS.
  • the transmission path of the uplink service message is: terminal device-target Access network equipment-target UPF-source UPF-source MEC-source AS, this path is called the old path or the original path.
  • the transmission path of the service message on the old path or the original path becomes longer, resulting in a longer delay of the service message on the old path or the original path.
  • the transmission path of the uplink service packet that has been sent to the target UPF but has not yet reached the source AS during the path switching process may be: target UPF-source UPF-source MEC-target MEC-target AS.
  • the target UPF receives the third indication information sent by the source UPF, it indicates the end of sending the downlink service packet on the old road.
  • the target UPF When the target UPF sends the last uplink service packet to the source UPF, it can also send the first indication information to indicate the end of the uplink service packet from the target UPF, and the target UPF then receives the uplink service packet from the target access network device Send directly to the target MEC, and no longer send to the source UPF.
  • the source UPF forwards the uplink service packets and the first indication information received from the target UPF to the source MEC.
  • the source MEC sends the last uplink service packet (the second uplink service packet) to the source AS
  • the second The first uplink service message and the first indication information after the uplink service message are returned to the target MEC in order, that is, the messages on the old path during the handover process are forwarded to the new path.
  • the target MEC can determine the old path according to the first indication information. After sending the uplink service packets on the path ends, the target MEC ensures that the service packets on the old path have been sent to the target AS in order, and then sends the buffered uplink service packets (new path) from the target UPF. In this way, while avoiding the loss of uplink service packets, the problem of disorder of uplink service packets can be avoided. In other words, for the target MEC, it is necessary to ensure that the uplink service packets on the old path are all sent before the uplink service packets on the new path can be sent.
  • the method 600 includes the identification of the terminal device.
  • the terminal device may be running an application (application, APP).
  • the source AS and the target AS need to migrate the application context of the terminal device.
  • the method 600 may include the identification of the terminal device. And the logo of the application.
  • the terminal device may be running a certain PDU session. In this case, the source AS and the target AS need to migrate the context of the PDU session of the terminal device.
  • the method 600 includes the identification of the terminal device and the identification of the PDU session. In order to avoid repeating the description of the embodiments of the present application, no detailed examples are given.
  • the first downlink service message may be sent first and then the third indication information may be sent, or the first downlink service message and the third indication information may be sent at the same time.
  • a specific bit in the header of the first downlink service message may be set to a specific value, for example, a specific value. The value is 1 or 0, that is, when the specific value is 0 or 1, it means that the first downlink service packet is the last downlink service packet from the source AS.
  • the first uplink service message may be sent first and then the first indication information (or second indication information) may be sent, or the first uplink service message and the first indication information (or second indication information) may be sent at the same time .
  • the specific bit in the last service message header in the first downlink service message can be set as A specific value is used as the first indication information or the second indication information. For example, the specific value is 1 or 0, that is, when the specific value is 0 or 1, it means that the first uplink service message ends.
  • FIG. 13 shows a schematic block diagram of an apparatus 800 for transmitting service packets provided by an embodiment of the present application.
  • the apparatus 800 may correspond to the source MEC described in the foregoing method, or may correspond to the chip or component of the source MEC, and, Each module or unit in the device 800 can be used to execute each action or process performed by the source MEC in the above method.
  • the device 800 for transmitting service messages can include a receiving unit 810 and a sending unit 810. Unit 820.
  • the receiving unit 810 is configured to receive, after receiving the second uplink service packet, the first uplink service packet from the target user plane network element sent by the source user plane network element, where the second uplink service packet is the source The last uplink service message sent by the mobile edge computing network element to the source application server.
  • the sending unit 820 is configured to send the first uplink service message to the target MEC;
  • the sending unit 820 is configured to send first indication information to the target MEC, where the first indication information is used to instruct the apparatus 800 to end sending the first uplink service packet.
  • receiving unit 810 and the sending unit 820 may be the same transceiving unit or different transceiving units, which is not limited in the embodiment of the present application.
  • the receiving unit 810 is further configured to:
  • the sending unit 820 is further configured to: before sending the first uplink service packet to the target MEC, send the first downlink service packet and third indication information to the source UPF, where the third indication information is used for Indicates the end of sending the downlink service message from the source AS.
  • the receiving unit 810 is further configured to: before sending the first downlink service packet to the source UPF, receive fourth indication information sent by the first network element, where the fourth indication information is used to indicate the source AS The last downlink service packet of the device is the first downlink service packet; the fifth indication information is sent to the first network element, and the fifth indication information is used to indicate that the second uplink service packet is the last one sent by the device to the source AS Uplink service packets.
  • FIG. 14 shows a schematic block diagram of an apparatus 900 for transmitting service packets provided by an embodiment of the present application.
  • the apparatus 900 may correspond to the target UPF described in the above method, or may correspond to the chip or component of the target UPF, and, Each module or unit in the device 900 may be used to execute each action or processing procedure performed by the target UPF in the above method.
  • the device 900 for transmitting service packets may include a first transceiver unit 910 And the second transceiver unit 920.
  • the first transceiver unit 910 is configured to send the first uplink service packet to the source UPF, and no longer send the uplink service packet to the source UPF after the device sends the first uplink service packet to the source UPF;
  • the second transceiver unit 920 is configured to send second indication information to the source UPF, where the second indication information is used to indicate the end of sending the first uplink service packet by the target user plane network element.
  • first transceiving unit 910 and the second transceiving unit 920 may be the same transceiving unit or different transceiving units, which is not limited in the embodiment of the present application.
  • the first transceiving unit 910 or the second transceiving unit 920 is further configured to:
  • the source UPF Before sending the first uplink service packet to the source UPF, receive the first downlink service packet and third indication information from the source UPF, where the third indication information is used to indicate the end of sending the downlink service packet from the source application server AS .
  • the second transceiver unit 920 is specifically configured to:
  • the second transceiver unit 920 is specifically configured to:
  • the first indication information is sent to the source UPF.
  • the first transceiving unit 910 or the second transceiving unit 920 is further configured to:
  • the uplink service packet from the access network device is sent to the target mobile edge computing MEC.
  • the first transceiving unit 910 or the second transceiving unit 920 is further configured to: after receiving the third indication information, when the transmission of the first downlink service packet is completed, send the message from the target MEC to the access network device The downlink business message.
  • FIG. 15 shows a schematic block diagram of an apparatus 1000 for transmitting service packets provided by an embodiment of the present application.
  • the apparatus 1000 may correspond to the target MEC described in the foregoing method, or may correspond to the chip or component of the target MEC, and, Each module or unit in the device 1000 can be used to execute each action or process performed by the target MEC in the above method.
  • the device 1000 for transmitting service messages can include a receiving unit 1010 and a sending unit 1010. Unit 1020.
  • the receiving unit 1010 is configured to receive a first uplink service packet from the source mobile edge computing MEC, the first uplink service packet is the received uplink service packet after the source MEC receives the second uplink service packet, and the second uplink service packet is The uplink service packet is the last uplink service packet sent by the source MEC to the source application server AS;
  • the receiving unit 1010 is further configured to: receive first indication information from the source MEC, where the first indication information is used to indicate the end of sending the first uplink service packet by the source MEC;
  • the sending unit 1020 is configured to, after receiving the first indication information, send the uplink service message sent by the target user plane function UPF to the target MEC to the target AS when the first uplink service message is sent.
  • FIG. 16 shows a schematic block diagram of an apparatus 1100 for transmitting service packets provided by an embodiment of the present application.
  • the apparatus 1100 may correspond to the source AS described in the foregoing method, or may correspond to the chip or component of the source AS, and, Each module or unit in the device 1100 can be used to execute each action or processing procedure performed by the source AS in the above method.
  • the device 1100 for transmitting service packets can include a transceiver unit 1110 and a migration unit. Unit 1120.
  • the transceiver unit 1110 is configured to receive a first message, where the first message is used to trigger the transition of the context of the terminal device, and the first message includes the target data network access point identifier DNAI;
  • the migration unit 1120 is configured to determine that after processing the first downlink service message and the second uplink service message, the target application server AS corresponding to the target DNAI performs terminal device context migration, where the first downlink service message Is the last downlink service packet sent by the device to the source mobile edge computing MEC, and the second uplink service packet is the last uplink service packet sent by the source MEC to the device.
  • the transceiver unit 1110 is further configured to: before performing the terminal device context migration with the target DNAI, send fourth indication information to the source MEC, where the fourth indication information is used to indicate that the first downlink service packet is The last downlink service packet from the device; receiving fifth indication information sent by the source MEC, where the fifth indication information is used to indicate that the second uplink service packet is the last uplink service packet sent by the source MEC to the device.
  • FIG. 17 shows a schematic block diagram of an apparatus 1200 for transmitting service packets provided by an embodiment of the present application.
  • the apparatus 1200 may correspond to the MEC application management network element described in the foregoing method, or may correspond to the MEC application management network element. Chips or components, and each module or unit in the device 1200 can be used to execute each action or process performed by the MEC application management network element in the above method.
  • the The apparatus 1200 may include a transceiving unit 1210 and a processing unit 1220.
  • the transceiver unit 1210 is configured to receive a first migration request message sent by the source mobile edge computing MEC, where the first migration request message includes the identifier of the first application instance and the target data network access point identifier DNAI;
  • the processing unit 1220 is configured to determine the first application instance to be migrated according to the identifier of the first application instance
  • the transceiver unit 1210 is further configured to send a first trigger message and a second trigger message to the target AS corresponding to the target DNAI and the source AS corresponding to the first application instance, respectively, the first trigger message includes the identifier of the first application instance, and the first trigger message It is used to trigger the target AS to migrate the first application instance, and the second trigger message is used to trigger the source AS to migrate the first application instance.
  • the processing unit 1220 is further configured to: create a first application in the target AS before the first trigger message and the second trigger message are respectively sent to the target AS corresponding to DNAI and the source AS corresponding to the target application instance The virtual resource of the instance, so that the target AS can migrate the first application instance according to the virtual resource.
  • the device 800 of each of the above solutions has the function of implementing the corresponding steps performed by the source MEC in the above method; the device 900 of each of the above solutions has the function of implementing the corresponding steps of the target UPF in the above method; the device 1000 of each of the above solutions has the function of implementing the above method
  • the function of the corresponding steps executed by the target MEC; the device 1100 of the above solutions has the function of implementing the corresponding steps executed by the source AS in the above method; the device 1200 of the above solutions has the corresponding steps executed by the MEC application management network element in the above method
  • the function; function can be realized by hardware or software, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the sending unit can be replaced by a communication interface, the receiving unit can be replaced by a communication interface, and other units, such as the determining unit, can be replaced by a processor to execute each method separately Transceiving operations and related processing operations in the embodiment.
  • the communication interface of a device is used for the device to communicate with other devices.
  • the communication interface may be a transmitter, a receiver, a transceiver, a circuit, a bus, a module, a pin, or another type of communication interface, which is not limited in the embodiment of the present application.
  • the processor can be used to perform, for example, but not limited to, baseband related processing
  • the communication interface can be used to perform, for example, but not limited to, information exchange.
  • the above-mentioned devices may be respectively arranged on independent chips, or at least partly or fully arranged on the same chip.
  • the processor can be further divided into an analog baseband processor and a digital baseband processor, where the analog baseband processor and the communication interface can be integrated on the same chip, and the digital baseband processor can be set on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip.
  • a digital baseband processor can be combined with a variety of application processors (such as but not limited to graphics processors, multimedia processors, etc.) Integrated on the same chip.
  • application processors such as but not limited to graphics processors, multimedia processors, etc.
  • Such a chip may be called a system on chip (SOC).
  • SOC system on chip
  • an embodiment of the present application provides a schematic block diagram of an apparatus 1300 for transmitting packets.
  • the apparatus 1300 includes a processor 1310, a communication interface 1320, and a memory 1330.
  • the processor 1310, the communication interface 1320, and the memory 1330 are coupled to communicate with each other.
  • the memory 1330 is used to store instructions, and the processor 1310 is used to execute instructions stored in the memory 1330 to control the communication interface 1320 to send signals and/or receive signal.
  • 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 communication interface 1320 is configured to receive the second uplink service packet sent by the source user plane network element from the target user plane network element.
  • An uplink service packet the second uplink service packet is the last uplink service packet sent by the source mobile edge computing network element to the source application server, and the communication interface 1320 is also used to send the first uplink service packet to the target mobile edge computing MEC
  • An uplink service packet; the communication interface 1320 is also used to send first indication information to the target MEC, where the first indication information is used to indicate the end of sending the first uplink service packet by the apparatus 1300.
  • the communication interface 1320 is used to send the first uplink service packet to the source user plane function UPF, after the device 1300 sends the first uplink service packet to the source UPF
  • the uplink service packet is no longer sent to the source UPF; the communication interface 1320 is also used to send second indication information to the source UPF, and the second indication information is used to instruct the apparatus 1300 to end sending the first uplink service packet.
  • the communication interface 1320 is used to receive the first uplink service packet from the source mobile edge computing MEC, and the first uplink service packet is that the source MEC receives the second uplink service packet.
  • the second uplink service packet is the last uplink service packet sent by the source MEC to the source application server AS; the communication interface 1320 is also used to receive the first uplink service packet from the source MEC Indication information, the first indication information is used to indicate the end of the first uplink service packet sent through the source MEC; the communication interface 1320 is also used to send the first uplink service packet to the target after receiving the first indication information
  • the AS sends an uplink service message sent by the target user plane function UPF to the target mobile edge computing network element.
  • the communication interface 1320 is used to receive a first message, the first message is used to trigger the transition of the context of the terminal device, and the first message includes the target data network access point Identifies DNAI; the processor 1310 is configured to determine that after processing the first downlink service message and the second uplink service message, the target application server AS corresponding to the target DNAI performs terminal device context migration, where the first downlink service The message is the last downlink service message sent by the device to the source mobile edge computing MEC, and the second uplink service message is the last uplink service message sent by the source MEC to the device.
  • the communication interface 1320 is used to receive the first migration request message sent by the source mobile edge computing MEC, and the first migration request message includes the information of the first application instance. ID and the target data network access point ID DNAI; the processor 1310 is used to determine the first application instance to be migrated according to the ID of the first application instance; the communication interface 1320 is also used to send the target AS and the first application respectively to the target DNAI
  • the source AS corresponding to the instance sends a first trigger message and a second trigger message, the first trigger message includes the identification of the first application instance, the first trigger message is used to trigger the target AS to migrate the first application instance, and the second trigger message is used
  • the migration of the first application instance is performed on the trigger source AS.
  • the device in FIG. 13 or the device in FIG. 14 or the device in FIG. 15 or the device in FIG. 16 or the device in FIG. 17 of the embodiment of the present application can be implemented by the device 1300 in FIG. 18, and can be used
  • Each step and/or process corresponding to the target UPF network element, the source UPF network element, and the source AS in the foregoing method embodiment is executed.
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer executes the method in the above embodiment .
  • the various embodiments in this application can also be combined with each other.
  • the present application also provides a computer-readable medium with a program code stored in the computer-readable interpretation, and when the program code runs on a computer, the computer executes the method in the foregoing embodiment .
  • the foregoing method embodiments in the embodiments of the present application may be applied to a processor or implemented by a processor.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • the steps of the foregoing method embodiments can 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 processor (digital signal processor, DSP), an application specific integrated circuit (ASIC), an off-the-shelf 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 processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the memory in the embodiment 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 electronic 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 static RAM
  • dynamic RAM dynamic RAM
  • 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 direct rambus RAM, DR RAM
  • direct memory bus random memory Take memory (direct rambus RAM, DR RAM).
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, rather than corresponding to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the computer program product may include one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic disk), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

Landscapes

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

Abstract

本申请提供了一种用于传输业务报文的方法和装置，可以避免第一上行业务报文的丢失，从而有助于提高传输性能。该方法包括：源移动边缘计算网元接收到第二上行业务报文之后，源移动边缘计算网元接收源用户面网元发送的来自目标用户面网元的第一上行业务报文，第二上行业务报文为源移动边缘计算网元向源应用服务器发送的最后一个上行业务报文；源移动边缘计算网元向目标移动边缘计算网元发送第一上行业务报文；源移动边缘计算网元向目标移动边缘计算网元发送第一指示信息，第一指示信息用于指示源移动边缘计算网元发送第一上行业务报文结束。

Description

用于传输业务报文的方法和装置
本申请要求于2019年06月24日提交中国专利局、申请号为201910551336.X、申请名称为“用于传输业务报文的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及通信领域中用于传输业务报文的方法和装置。
背景技术
当终端装置从原来的接入网设备的覆盖范围移动至当前的接入网设备的覆盖范围时，会触发空口的切换，即将终端装置的接入网设备从原来的接入网设备切换到当前的接入网设备。由于终端装置的位置发生了变化，但是终端装置仍然接入的是原来的用户面网元，但实际上此时离终端装置最近的用户面网元可能已经发生了变化，但是终端装置仍然与原来的用户面网元进行报文的传输，这种情况下传输路径较长，相应地，报文的传输时延就会变大。为了降低报文的传输时延，有必要将传输路径从原来的用户面网元切换到新的用户面网元，切换的过程中，还没有完成传输的上下行业务报文容易丢包，从而导致传输性能下降。
发明内容
本申请提供一种用于传输业务报文的方法和装置，可以提高传输性能。
第一方面，提供了一种用于传输业务报文的方法，包括：源移动边缘计算网元接收到第二上行业务报文之后，源移动边缘计算网元接收源用户面网元发送的来自目标用户面网元的第一上行业务报文，所述第二上行业务报文为所述源移动边缘计算网元向所述源应用服务器发送的最后一个上行业务报文；源移动边缘计算网元向目标移动边缘计算网元发送第一上行业务报文；所述源移动边缘计算网元向所述目标移动边缘计算网元发送第一指示信息，所述第一指示信息用于指示所述源移动边缘计算网元发送所述第一上行业务报文结束。
因此，本申请实施例中，当源移动边缘计算网元向源应用服务器发送了最后一个第二上行业务报文之后，将第二上行业务报文之后的第一上行业务报文通过目标移动边缘计算网元向目标应用服务器发送，这样可以避免第一上行业务报文的丢失，从而有助于提高传输性能。并且源移动边缘计算网元可以向目标移动边缘计算网元发送第一指示信息来指示源移动边缘计算网元发送第一上行业务报文结束，这样可以避免目标移动边缘计算网元一直等待接收源移动边缘计算网元发送的上行业务报文，从而有助于目标移动边缘计算网元发送上行业务报文。
在一些可能的实现方式中，在所述源移动边缘计算网元向目标移动边缘计算网元发送第一上行业务报文之前，所述方法还包括：所述源移动边缘计算网元接收源用户面功能用户面网元发送的来自目标用户面网元的第二指示信息，所述第二指示信息用于指示所述目标用户面网元发送所述第一上行业务报文结束。
可选地，源移动边缘计算网元在接收到源用户面网元发送的第一上行业务报文之后再接收源用户面网元发送的第二指示信息，或者，源移动边缘计算网元可以同时接收源用户面网元发送的第二指示信息和第一上行业务报文。
需要说明的是，第一指示信息和第二指示信息可以是不同的网元之间的信令，但是第一指示信息和第二指示信息可以包括相同的信元，即该相同的信元可以是上行业务报文结束的标识，即当目标用户面网元向源用户面网元发送了第二指示信息，源用户面网元将第二指示信息转发给源移动边缘计算网元之后，源移动边缘计算网元可以确定来自目标用户面网元的上行业务报文结束，即源用户面网元不会再向源移动边缘计算网元发送来自目标用户面网元的上行业务报文了；当源移动边缘计算网元向目标移动边缘计算网元发送第一指示信息之后，目标移动边缘计算网元可以确定来自源移动边缘计算网元的上行业务报文结束，即源移动边缘计算网元不会再向目标移动边缘计算网元发送上行业务报文了。
在一些可能的实现方式中，在所述源移动边缘计算网元向目标移动边缘计算网元发送第一上行业务报文之前，所述方法还包括：所述源移动边缘计算网元向源用户面网元发送第一下行业务报文和第三指示信息，所述第三指示信息用于指示来自源应用服务器的下行业务报文发送结束。
在一些可能的实现方式中，在所述源移动边缘计算网元向源用户面网元发送第一下行业务报文之前，所述方法还包括：
所述源移动边缘计算网元接收第一网元发送的第四指示信息，所述第四指示信息用于指示来自所述源应用服务器的最后的一个下行业务报文为所述第一下行业务报文；
所述源移动边缘计算网元向所述第一网元发送所述第五指示信息，所述第五指示信息用于指示所述第二上行业务报文为所述源移动边缘计算网元发送给所述源应用服务器的最后一个上行业务报文。
在一些可能的实现方式中，第四指示信息为第一下行业务报文的序列号，第五指示信息为第二上行业务报文的序列号。
在一些可能的实现方式中，所述源移动边缘计算网元向源用户面网元发送第三指示信息，包括：所述源移动边缘计算网元根据所述第四指示信息向所述源用户面网元发送所述第三指示信息。
在一些可能的实现方式中，在所述源移动边缘计算网元向目标移动边缘计算网元发送第一上行业务报文之前，所述方法还包括：所述源移动边缘计算网元接收策略控制网元或者会话管理网元发送的第二迁移请求消息，所述二迁移请求消息用于通知数据网络接入点标识目标数据网络接入点标识发生变化或者用于通知用户面网元发生变化，所述第二迁移请求消息包括终端装置的标识和目标目标数据网络接入点标识；
在一些可能的实现方式中，源移动边缘计算接收到第二迁移请求消息之后，向源应用服务器发送第五迁移请求消息，第五迁移请求消息用于向应用服务器请求迁移终端装置的上下文，第五迁移请求消息包括终端装置的标识和目标目标数据网络接入点标识。
在一些可能的实现方式中，在所述源移动边缘计算网元接收策略控制网元或者会话管理网元发送的第二迁移请求消息之后，所述方法还包括：
所述源移动边缘计算网元向所述目标移动边缘计算网元发送第三迁移请求消息，所述第三迁移请求消息用于向所述目标移动边缘计算网元请求进行所述终端装置的上下文的迁移，所述第三迁移请求消息包括所述终端装置的标识；所述源移动边缘计算网元接收所述目标移动边缘计算网元发送的所述第三迁移请求消息的应答消息。
在一些可能的实现方式中，源移动边缘计算接收到第二迁移请求消息之后，向源应用服务器发送第五迁移请求消息，第五迁移请求消息用于向源应用服务器请求迁移终端装置的上下文，第五迁移请求消息包括终端装置的标识和目标目标数据网络接入点标识.
在一些可能的实现方式中，所述源移动边缘计算网元向源应用服务器发送所述第五迁移请求消息之后，所述方法还包括：所述源移动边缘计算网元接收来自所述源应用服务器的上下文迁移完成消息，所述上下文迁移完成消息用于指示所述源应用服务器与所述目标目标数据网络接入点标识对应的目标应用服务器已经完成了所述终端装置的上下文的迁移。
在一些可能的实现方式中，在所述源移动边缘计算网元向目标移动边缘计算网元发送第一上行业务报文之前，所述方法还包括：所述源移动边缘计算网元接收PCF网元或者SMF网元发送的二迁移请求消息，所述二迁移请求消息用于通知数据网络接入点标识目标数据网络接入点标识发生变化或者用于通知用户面网元发生变化，所述第二迁移请求消息包括第一应用实例的标识和目标目标数据网络接入点标识；
在一些可能的实现方式中，源移动边缘计算接收到第二迁移请求消息之后，向移动边缘计算应用管理网元发送第一迁移请求消息，第一迁移请求消息用于向移动边缘计算应用管理网元请求迁移终端装置的上下文，第一迁移请求消息包括第一应用实例的标识和目标目标数据网络接入点标识。移动边缘计算应用管理网元向源移动边缘计算发送第一迁移请求消息的应答消息，用于指示移动边缘计算应用管理网元能够接受第一应用实例的上下文的迁移。
在一些可能的实现方式中，在所述源移动边缘计算网元接收PCF网元或者SMF网元发送的第二迁移请求消息之后，所述方法还包括：所述源移动边缘计算网元向所述目标移动边缘计算网元发送第三迁移请求消息，所述第三迁移请求消息用于向目标移动边缘计算请求是否接受第一应用实例的上下文的迁移，第三上下文迁移请求消息包括第一应用实例的标识。若目标移动边缘计算能够接受终端装置上下文的迁移，则向源移动边缘计算发送第三迁移请求消息的应答消息，第三迁移请求的应答消息用于指示目标移动边缘计算能够接受第一应用实例上下文的迁移。
在一些可能的实现方式中，所述源移动边缘计算网元向移动边缘计算应用管理网元发送所述第一迁移请求消息之后，所述方法还包括：
所述源移动边缘计算网元接收来自所述移动边缘计算应用管理网元的上下文迁移完成消息，所述上下文迁移完成消息用于指示所述源应用服务器与所述目标目标数据网络接入点标识对应的目标应用服务器已经完成了所述终端装置的上下文的迁移。
第二方面，提供了一种用于传输业务报文的方法，包括：目标用户面网元向源用户面网元发送第一上行业务报文，在所述目标用户面向所述源用户面发送第一上行业务报文之 后不再向所述源用户面发送上行业务报文；所述目标用户面向所述源用户面发送第二指示信息，所述第二指示信息用于指示目标用户面移动边缘计算网元发送第一上行业务报文结束。
因此，本申请实施例中，目标用户面向所述源用户面发送第一上行业务报文之后不再向所述源用户面发送上行业务报文，并且目标用户面可以向源用户面发送第二指示信息来指示通过目标用户面发送第一上行业务报文结束。此后，目标用户面可以将来自接入网设备的上行业务报文直接发送给目标移动边缘计算网元而不需要发送给源用户面网元，这样，目标移动边缘计算网元确定第一上行业务报文发送完毕之后，再发送直接来自目标用户面的上行业务报文，从而可以避免上行业务报文的乱序问题。
在一些可能的实现方式中，在所述目标用户面网元向源用户面网元发送第一上行业务报文之前，所述方法还包括：所述目标用户面网元接收来自所述源用户面网元的第一下行业务报文和第三指示信息，所述第三指示信息用于指示来自源应用服务器的下行业务报文发送结束。
在一些可能的实现方式中，所述目标用户面网元向所述源用户面网元发送第二指示信息，包括：所述目标用户面网元根据所述第三指示信息向所述源用户面网元发送所述第二指示信息。
在一些可能的实现方式中，所述目标用户面网元向所述源用户面网元发送第二指示信息，包括：所述目标用户面网元接收来自会话管理网元或目标移动边缘计算网元发送的上下文迁移完成消息之后，所述目标用户面网元向所述源用户面网元发送所述第二指示信息。
在一些可能的实现方式中，在所述目标用户面网元向所述源用户面网元发送所述第二指示信息之后，所述方法还包括：所述目标用户面网元向目标移动边缘计算网元发送来自所述接入网设备的上行业务报文。
在一些可能的实现方式中，在所述目标用户面网元接收所述第三指示信息之后，所述方法还包括：当所述第一下行业务报文发送完毕，所述目标用户面网元向所述接入网设备发送来自目标移动边缘计算网元的下行业务报文。
第三方面，提供了一种用于传输业务报文的方法，包括：目标移动边缘计算网元接收来自源移动边缘计算网元的第一上行业务报文，所述第一上行业务报文为所述源移动边缘计算接收到第二上行业务报文之后的所接收的上行业务报文，所述第二上行业务报文为所述源移动边缘计算网元向源应用服务器应用服务器发送的最后一个上行业务报文；所述目标移动边缘计算接收来自源移动边缘计算网元的第一指示信息，所述第一指示信息用于指示所述源移动边缘计算网元发送第一上行业务报文结束；在所述目标移动边缘计算网元接收到所述第一指示信息之后，当所述第一上行业务报文发送完毕，所述目标移动边缘计算网元向目标应用服务器发送由目标用户面网元发送给目标移动边缘计算网元的上行业务报文。
因此，本申请实施例中，当移动边缘计算网元向源应用服务器发送了最后一个第二上行业务报文之后，将第二上行业务报文之后的第一上行业务报文通过目标移动边缘计算网元向目标应用服务器发送，这样可以避免第一上行业务报文的丢失，并且源移动边缘计算网元可以向目标移动边缘计算网元发送第一指示信息来指示通过源移动边缘计算网元发 送的第一上行业务报文结束，这样可以避免目标移动边缘计算网元一直等待接收源移动边缘计算网元发送的上行业务报文，目标移动边缘计算网元在接收到第一指示信息之后，向目标应用服务器发送完来自源移动边缘计算网元的上行业务报文之后，再发来自目标用户面网元的上行业务报文，从而可以避免上行业务报文乱序的问题。
在一些可能的实现方式中，在所述目标移动边缘计算网元接收来自源移动边缘计算网元的第一上行业务报文之前，所述方法还包括：目标移动边缘计算接收来自源移动边缘计算的第三迁移请求消息，所述第三迁移请求消息包括终端装置的标识。第三迁移请求消息用于向目标移动边缘计算请求是否接受终端装置的上下文的迁移。目标移动边缘计算能够接受终端装置上下文的迁移，则向源移动边缘计算发送第三迁移请求消息的应答消息，第三迁移请求消息的应答消息用于指示目标移动边缘计算能够接受终端装置上下文的迁移。
在一些可能的实现方式中，在所述目标移动边缘计算网元接收来自源移动边缘计算网元的第一上行业务报文之前，所述方法还包括：目标移动边缘计算接收来自源移动边缘计算的第三迁移请求消息，所述第三迁移请求消息包括第一应用实例的标识。第三迁移请求消息用于向目标移动边缘计算请求是否接受第一应用实例的上下文的迁移。若目标移动边缘计算能够接受终端装置上下文的迁移，则向源移动边缘计算发送第三迁移请求消息的应答消息，第三迁移请求的应答消息用于指示目标移动边缘计算能够接受第一应用实例上下文的迁移。
第四方面，提供了一种用于传输业务报文的方法，包括：源应用服务器接收第一消息，所述第一消息用于触发所述源应用服务器进行终端装置的上下文的迁移，所述第一消息包括目标数据网络接入点标识目标数据网络接入点标识；所述源应用服务器确定处理完第一下行业务报文和第二上行业务报文之后，所述源应用服务器与所述目标目标数据网络接入点标识对应的目标应用服务器进行所述终端装置上下文的迁移，其中，所述第一下行业务报文为所述源应用服务器向源移动边缘计算网元发送的最后一个下行业务报文，所述第二上行业务报文为所述源移动边缘计算网元向所述源应用服务器发送的最后一个上行业务报文。
在一些可能的实现方式中，第一消息为前述的第五迁移请求消息。
在一些可能的实现方式中，在所述源应用服务器与所述目标目标数据网络接入点标识进行所述终端装置上下文的迁移之前，所述方法还包括：所述源应用服务器向所述源移动边缘计算网元发送第四指示信息，所述第四指示信息用于指示所述第一下行业务报文为来自所述源应用服务器的最后一个下行业务报文；所述源应用服务器接收所述源移动边缘计算网元发送的第五指示信息，所述第五指示信息用于指示所述第二上行业务报文为所述源移动边缘计算网元向所述源应用服务器发送的最后一个上行业务报文。
在一些可能的实现方式中，第四指示信息为第一下行业务报文的序列号，第五指示信息为第二上行业务报文的序列号。
第五方面，提供了一种用于传输业务报文的方法，包括：移动边缘计算应用管理网元接收源移动边缘计算网元发送的第一迁移请求消息，所述第一迁移请求消息包括第一应用实例的标识以及目标数据网络接入点标识目标数据网络接入点标识；所述移动边缘计算应用管理网元根据所述第一应用实例的标识确定所要迁移的第一应用实例；所述移动边缘计算应用管理网元分别向所述目标目标数据网络接入点标识对应的目标应用服务器和所述 第一应用实例对应的源应用服务器发送第一触发消息和第二触发消息，所述第一触发消息包括所述第一应用实例的标识，所述第一触发消息用于触发所述目标应用服务器进行所述第一应用实例的迁移，所述第二触发消息用于触发所述源应用服务器进行所述第一应用实例的迁移。
在一些可能的实现方式中，在所述移动边缘计算应用管理网元分别向所述目标数据网络接入点标识对应的目标应用服务器和所述目标应用实例对应的源应用服务器发送的第一触发消息和第二触发消息之前，所述方法还包括：所述移动边缘计算应用管理网元在所述目标应用服务器创建所述第一应用实例的虚拟资源，以便于所述目标应用服务器根据所述虚拟资源迁移所述第一应用实例。
第六方面，本申请提供一种用于传输业务报文的装置，用于实现第一方面和/或其任意可能的实现方式中的方法。该装置可以是源移动边缘计算网元，也可以是源移动边缘计算网元中的装置，或者是能够和网络设备匹配使用的装置。一种设计中，该装置可以包括执行第一方面和/或其任意可能的实现方式中所描述的方法/操作/步骤/动作所对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该装置可以包括接收单元和发送单元，接收单元和发送单元可以是一个收发单元或者是不同的收发单元。
第七方面，本申请提供一种用于传输业务报文的装置，用于实现第二方面和/或其任意可能的实现方式中的方法。该装置可以是目标用户面网元，也可以是目标用户面网元中的装置，或者是能够和目标用户面网元匹配使用的装置。一种设计中，该装置可以包括执行第二方面和/或其任意可能的实现方式中所描述的方法/操作/步骤/动作所对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该装置可以包括发送单元。
第八方面，本申请提供一种用于传输业务报文的装置，用于实现第三方面和/或其任意可能的实现方式中的方法。该装置可以是目标移动边缘计算网元，也可以是目标移动边缘计算网元中的装置，或者是能够和目标移动边缘计算网元匹配使用的装置。一种设计中，该装置可以包括执行第三方面和/或其任意可能的实现方式中所描述的方法/操作/步骤/动作所对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该装置可以包括接收单元和发送单元，接收单元和发送单元可以是一个收发单元或者是不同的收发单元。
第九方面，本申请提供一种用于传输业务报文的装置，用于实现第四方面和/或其任意可能的实现方式中的方法。该装置可以是源应用服务器，也可以是源应用服务器中的装置，或者是能够和源应用服务器匹配使用的装置。一种设计中，该装置可以包括执行第四方面和/或其任意可能的实现方式中所描述的方法/操作/步骤/动作所对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该装置可以包括迁移单元和收发单元。
第十方面，本申请提供一种用于传输业务报文的装置，用于实现第五方面和/或其任意可能的实现方式中的方法。该装置可以是移动边缘计算应用管理网元接收源移动边缘计算网元，也可以是移动边缘计算应用管理网元接收源移动边缘计算网元中的装置，或者是能够和移动边缘计算应用管理网元接收源移动边缘计算网元匹配使用的装置。一种设计 中，该装置可以包括执行第五方面和/或其任意可能的实现方式中所描述的方法/操作/步骤/动作所对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。一种设计中，该装置可以包括接收单元和发送单元，接收单元和发送单元可以是一个收发单元或者是不同的收发单元。
第十一方面，本申请提供一种用于传输业务报文的装置，该装置包括处理器，用于实现上述第一方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括存储器，可选地，所述存储器用于存储指令，所述处理器执行所述存储器中存储的指令时，可以实现上述第一方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括通信接口，所述通信接口用于该装置与其它设备进行通信，示例性的，通信接口可以是收发器、电路、总线、模块、管脚或其它类型的通信接口。
第十二方面，本申请提供一种用于传输业务报文的装置，该装置包括处理器，用于实现上述第二方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括存储器，可选地，所述存储器用于存储指令，所述处理器执行所述存储器中存储的指令时，可以实现上述第二方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括通信接口，所述通信接口用于该装置与其它设备进行通信。
第十三方面，本申请提供一种用于传输业务报文的装置，该装置包括处理器，用于实现上述第三方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括存储器，可选地，所述存储器用于存储指令，所述处理器执行所述存储器中存储的指令时，可以实现上述第三方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括通信接口，所述通信接口用于该装置与其它设备进行通信，示例性的，通信接口可以是收发器、电路、总线、模块、管脚或其它类型的通信接口。
第十四方面，本申请提供一种用于传输业务报文的装置，该装置包括处理器，用于实现上述第四方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括存储器，可选地，所述存储器用于存储指令，所述处理器执行所述存储器中存储的指令时，可以实现上述第四方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括通信接口，所述通信接口用于该装置与其它设备进行通信。
第十五方面，本申请提供一种用于传输业务报文的装置，该装置包括处理器，用于实现上述第五方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括存储器，可选地，所述存储器用于存储指令，所述处理器执行所述存储器中存储的指令时，可以实现上述第五方面和/或其任意可能的实现方式中描述的方法。所述装置还可以包括通信接口，所述通信接口用于该装置与其它设备进行通信。
第十六方面，本申请提供了一种用于传输数据的系统，该系统包括上述第六方面提供的装置、第七方面提供的装置、第八方面提供的装置、第九方面提供的装置和第十方面提供的装置中的至少两方面的装置；或者
该系统包括上述第十一方面提供的装置、第十二方面提供的装置、第十三方面提供的装置、第十四方面提供的装置和第十五方面提供的装置中的至少两方面的装置；
第十七方面，本申请提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机指令，当计算机指令在计算机上运行时，使得计算机执行上述方面及其任意可能的设计中的方法。
第十八方面，本申请提供一种芯片，包括处理器。处理器用于执行上述方面及其任意可能的实现方式中的方法。
可选地，所述芯片还包括存储器，存储器与处理器耦合。
进一步可选地，所述芯片还包括通信接口。
第十九方面，本申请提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方面及其任意可能的设计中的方法。
附图说明
图1是本申请实施例提供的系统架构示意图。
图2是本申请实施例提供的应用场景示意图。
图3是本申请实施例提供的另一应用场景示意图。
图4是本申请实施例提供的又一应用场景示意图。
图5是本申请实施例提供的用于传输业务报文的方法示意图。
图6是本申请实施例提供的另一用于传输业务报文的方法示意图。
图7是本申请实施例提供的又一用于传输业务报文的方法示意图。
图8是本申请实施例提供的又一用于传输业务报文的方法示意图。
图9是本申请实施例提供的又一用于传输业务报文的方法示意图。
图10是本申请实施例提供的又一用于传输业务报文的方法示意图。
图11是本申请实施例提供的下行业务报文传输的路径示意图。
图12是本申请实施例提供的上行业务报文传输的路径示意图。
图13是本申请实施例提供的另一用于传输业务报文的装置的示意性框图。
图14是本申请实施例提供的又一用于传输业务报文的装置的示意性框图。
图15是本申请实施例提供的又一用于传输业务报文的装置的示意性框图。
图16是本申请实施例提供的又一用于传输业务报文的装置的示意性框图。
图17是本申请实施例提供的又一用于传输业务报文的装置的示意性框图。
图18是本申请实施例提供的又一用于传输业务报文的装置的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通信(global system for mobile communications，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、未来的第五代(5th generation，5G)系统或新无线(new radio，NR)等。
图1示例性示出了本申请提供的一种通信系统架构示意图。如图1所示，该通信系统 架构包括移动性管理网元、会话管理网元、策略控制网元、认证服务网元、数据管理网元和用户面网元。进一步，该通信系统架构还包括接入网设备、终端装置(user equipment，UE)和数据网络网元(data network，DN)。终端装置可与移动性管理网元连接，接入网设备也可与移动性管理网元连接，接入网设备还可与用户面网元连接，用户面网元可分别与会话管理网元、数据网络连接，移动性管理网元可分别与会话管理网元、数据管理网元、策略控制网元和认证服务网元连接，会话管理网元分别与策略控制网元和数据管理网元连接。移动性管理网元和会话管理网元均可从数据管理网元获取数据，例如用户签约数据，移动性管理网元和会话管理网元均可从策略控制网元获取策略数据。例如，策略控制网元从数据管理网元获得用户签约数据并发送到移动性管理网元和会话管理网元，再由移动性管理网元和会话管理网元下发到接入网设备、终端装置和用户面网元等。
移动性管理网元，主要用于移动网络中的终端装置的注册、移动性管理、跟踪区更新流程。移动性管理网元终结了非接入层(non access stratum，NAS)消息、完成注册管理、连接管理以及可达性管理、分配跟踪区域列表(track area list，TA list)以及移动性管理等，并且透明路由会话管理(session management，SM)消息到会话管理网元。在第5代(5th generation，5G)通信中，移动性管理网元可以是核心网接入和移动性管理功能(core access and mobility management function，AMF)网元，在未来通信如第6代(6th generation，6G)通信中，移动性管理网元仍可以是AMF网元，或者有其它名称，本申请对此不作限定。
会话管理网元，主要用于移动网络中的会话管理，如会话创建、修改、释放。具体功能比如包括为用户分配互联网协议(internet protocol，IP)地址、选择提供报文转发功能的用户面网元等。在5G中，会话管理网元可以是会话管理功能(session management function，SMF)网元，在未来通信如6G中，会话管理网元仍可以是SMF网元，或有其它的名称，本申请不做限定。
策略控制网元，其包含用户签约数据管理功能，策略控制功能，计费策略控制功能，服务质量(quality of service，QoS)控制等。在5G中，策略控制网元可以是策略控制功能(policy control function，PCF)网元，在未来通信如6G中，策略控制网元仍可以是PCF网元，或有其它的名称，本申请不做限定。
认证服务器网元，主要用于使用可扩展的身份验证协议(extensible authentication protocol，EAP)验证服务功能、存储密钥，以实现对用户的鉴权和认证。在5G中，认证服务器网元可以是认证服务器功能(authentication server function，AUSF)网元，在未来通信如6G中，用户面网元仍可以是AUSF网元，或有其它的名称，本申请不做限定。
数据管理网元，主要用于存储用户数据，如签约信息、鉴权/授权信息。在5G中，数据管理网元可以是统一数据管理(unified data management，UDM)网元，在未来通信如6G中，数据管理网元仍可以是UDM网元，或有其它的名称，本申请不做限定。
用户面网元，主要用于用户平面的业务处理，例如业务路由、包转发、锚定功能、业务质量(quality of service，QoS)映射和执行、上行链路的标识识别并路由到数据网络、下行包缓存和下行链路数据到达的通知触发、与外部数据网络连接等，可以存在多个用户面网元，其中与应用服务器(application service，AS)连接的用户面网元称之为协议数据单元会话锚点(PDU session anchor，PSA)，其中，PDU全称为protocol data unit。在5G中，用户面网元可以是用户面功能(user plane function，UPF)网元，在未来通信如6G中， 用户面网元仍可以是UPF网元，或有其它的名称，本申请不做限定。
接入网设备，也可以称为无线接入网(radio access network，RAN)设备，是一种为终端装置提供无线通信功能的设备。接入网设备包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
终端装置(user equipment，UE)，是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。终端装置可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
数据网络(Data Network，DN)，主要用于为用户提供业务，比如运营商的业务、互联网接入业务和第三方业务。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。上述网元或者功能可划分出一个或多个服务，进一步，还可能会出现独立于网络功能存在的服务。在本申请中，上述功能的实例、或上述功能中包括的服务的实例、或独立于网络功能存在的服务实例均可称为服务实例。
需要说明的是，图1中包括的各个网元的命名仅是一个名字，名字对网元本身的功能不构成限定。在5G网络以及未来其它的网络中，上述各个网元也可以是其他的名字，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能是其他命名，等等，在此进行统一说明，以下不再赘述。
需要说明的是，图1中的各个网元不是必须同时存在的，可以根据需求确定需要哪些网元。图1中的各个网元之间的连接关系也不是唯一确定的，可以根据需求进行调整。
本申请以用户面网元为UPF为例进行描述，例如，源UPF和目标UPF。可选地，可以将源UPF替换成源PSA，将目标UPF替换成目标PSA。本申请以会话管理网元为SMF网元为例进行描述。
图2示出了本申请实施例的一个应用场景示意图200。图2简单示出了基于图1架构下的移动边缘计算(mobile edge computing，MEC)网元示意图，MEC网元下沉部署在UPF处，这样可以为终端装置提供低时延高带宽的服务。具体地，图2示出了三条传输路径，路径1的上行业务报文传输过程为：终端装置-接入网设备1-UPF1-MEC1-AS1,下行业务报文的传输过程为上行业务报文的逆过程。路径2的上行业务报文传输过程为：终端装置-接入网设备2-UPF2-UPF1-MEC1-AS1，下行业务报文的传输过程为上行业务报文的逆过程。路径3的上行业务报文的传输过程为：终端装置-接入网设备2-UPF2-MEC2-AS2， 下行业务报文的传输过程为上行业务报文的逆过程。终端装置(例如可以为图1的UE109)采用路径1传输业务报文的过程中，终端装置的位置发生变化。当终端装置从接入网设备1覆盖的位置移动到接入网设备2覆盖的位置时，终端装置的接入网设备需要切换至接入网设备2，即空口进行了切换，此时采用路径2传输业务报文，路径2上的报文通过接入网设备2到达UPF1(也称为源UPF)，然后再通过下沉的MEC1最后传输到AS1，此时传输距离较长，路径2是三个传输路径中距离最长的路径，从而在路径2上传输的报文的时延较长，例如，对于低时延高可靠(ultra reliable low latency communications，URLLC)类型的报文，在路径2上无法满足低时延要求。因此有必要将报文的传输路径从路径2切换至路径3，也就是说有必要将终端装置的上下文从AS1迁移到AS2。但是在将报文的传输路径从路径2切换至路径3的过程中，在路径2上正在传输的报文有可能由于路径切换操作导致丢失，这样会造成丢包率较高，从而导致传输性能较差。并且在路径切换时，UPF2(也称为目标UPF)有可能会同时收到来自路径2和路径3的上行业务报文。从而导致UPF2收到的报文出现乱序，这对报文的顺序有严格要求的业务类型是一个很大的问题。
针对上述问题，本申请实施例提供的用于传输业务报文的方法，通过源UPF、源MEC、目标UPF以及目标MEC之间的交互，具体交互过程参见下面实施例中的描述，在路径切换过程中将路径2上的上行业务报文准确的传到AS2，将路径2上的下行业务报文准确的传到终端装置210。
需要说明的是，本申请实施例中的MEC网元，例如源MEC网元和目标MEC网元的功能包括：一方面支持用户面报文的转发，能够检测业务的开始和结束，并能感知报文序列号；另一方面在控制面能够和PCF、SMF交互，代理AS或代理AS上的应用实例向网络(SMF或PCF)订阅DNAI变化通知。
需要说明的是图2简单示出了基于MEC的报文传输示意图，在实际的传输过程中图2还可以存在其他的网元，由于与本申请无关，所以没有详细的描述。
需要说明的是，本申请是将上行业务报文的传输与下行业务报文的传输结合到一起描述的，但本申请实施例对此不作限制，在实际处理的过程中，可以只存在上行业务报文的传输，也可以只存在下行业务报文的传输。
需要说明的是，为了方便描述，去掉了“网元”，例如，UPF表示UPF网元，SMF表示SMF网元等。
下面结合图3和图4描述本申请实施例的两种应用场景。
如图3所示中央数据中心(central data center)控制一个或多个本地数据中心(local data center)，图3中仅示出了两个本地数据中心(也称为本地源数据中心和本地目标数据中心)，本地源数据中心包括源UPF、源MEC以及源AS。本地目标数据中心包括目标UPF、目标MEC以及目标AS。但本申请实施例不限于此。每个本地数据中心没有SMF网元。
具体地，中央数据中心包括SMF、PCF以及AMF，SMF用于从PCF获取策略数据，并根据策略数据控制源UPF和目标UPF，源MEC和目标MEC和PCF交互提供应用需求。例如，当终端装置的位置发生变化，从源接入网设备的覆盖范围移动到目标接入网设备的覆盖范围时，终端装置的进行空口的切换，从源接入网设备切换到目标接入网设备，此时AMF可以获取到目标接入设备发送的终端装置的接入信息，并将终端装置的接入信息上报给SMF，该接入信息包括终端装置的位置信息，SMF根据终端装置的接入信息，确定 终端装置的用户面功能网元需要切换，当发现需要切换到的用户面功能网元对应的AS也变化时，SMF或者PCF确定目标AS的数据网络接入点标识(data network access identifier，DNAI)。SMF或者PCF将目标AS的DNAI以及终端装置的标识(可选地，也可以发送终端装置的应用的标识)发送给源MEC，以便于源MEC向源AS转发DNAI以及终端装置的标识，以便于源AS根据DNAI确定目标AS，从而使得源AS与目标AS进行终端装置的上下文的迁移，例如，SMF通过NEF与源AS和目标AS传输信令。需要说明的是，图3中，中央数据中心还可以包括AF，SMF可以通过AF与源AS和目标AS交互，SMF可以通过NEF与AF交互。为了避免赘述，本申请实施例并未示出。
如图4所示中央数据中心(central data center)控制一个或多个本地数据中心(local data center)，图4中仅示出了两个本地数据中心(也称为本地源数据中心和本地目标数据中心)，本地源数据中心包括源UPF、源MEC以及源AS。本地目标数据中心包括目标UPF、目标MEC以及目标AS。但本申请实施例不限于此。每个本地数据中心没有SMF网元。
图4与图3基本相同，不同的是，图4中引入了MEC的应用管理网元，例如MEC的应用管理网元可以是虚拟化网络功能管理器(virtual network function manager，VNFM)。MEC的应用管理网元用于管理源AS和目标AS，包括管理源AS和目标AS上应用实例的生命周期，如实例化一个MEC应用实例，将一个MEC应用实例从源AS迁移到目标AS，接受源AS和目标AS上应用实例的注册等。当源MEC从SMF或PCF获取到目标AS的DNAI以及终端装置的应用的标识时，源MEC可以根据终端装置的应用的标识确定应用实例的标识，从而将应用实例的标识和DNAI发送给MEC的应用管理网元，MEC的应用管理网元触发源AS和目标AS进行应用实例的上下文迁移，将应用实例的上下文可以从源AS迁移到目标AS。
需要说明的是，图4中，中央数据中心还可以包括AS的控制面网元AF，SMF可以通过AS的控制面网元AF与源AS和目标AS交互，SMF可以通过NEF与AF交互。
图5示出了本申请实施例提供的用于传输业务报文的方法200，方法200包括：
S210，目标UPF向源UPF发送第一上行业务报文，源UPF接收目标UPF发送的第一上行业务报文。在所述目标UPF向所述源UPF发送第一上行业务报文之后不再向所述源UPF发送上行业务报文。即目标UPF再接收到上行业务报文时，将上行业务报文直接发送到目标MEC即可，这样，在S270中，目标MEC向目标AS发送完第一上行业务报文之后，向目标AS发送直接来自目标UPF的上行业务报文。
S220，目标UPF向源UPF发送第二指示信息，第二指示信息用于指示目标UPF发送第一上行业务报文结束。
S230，源UPF向源MEC发送第一上行业务报文，源MEC接收源UPF发送的第一上行业务报文。
S240，源UPF向源MEC发送第二指示信息，源MEC接收源UPF发送的第二指示信息。
S250，源MEC网元向目标MEC网元发送第一上行业务报文，目标MEC接收来自源MEC的第一上行业务报文，所述第一上行业务报文为所述源MEC网元接收到第二上行业务报文之后所接收的上行业务报文，所述第二上行业务报文为所述源MEC网元向所述源AS发送的最后一个上行业务报文。
S260，源MEC接收到第二指示信息之后，源MEC向目标MEC发送第一指示信息，目标MEC接收来自源MEC的第一指示信息，第一指示信息用于指示源MEC发送第一上行业务报文结束，这样，目标MEC就可以确定来自源MEC的上行业务报文结束。
需要说明的是，第一指示信息和第二指示信息可以是不同的网元之间的信令，但是第一指示信息和第二指示信息可以包括相同的信元，即该相同的信元可以是上行业务报文结束的标识，即当目标用户面网元向源用户面网元发送了第二指示信息，源用户面网元将第二指示信息转发给源移动边缘计算网元之后，源移动边缘计算网元可以确定来自目标用户面网元的上行业务报文结束，即源用户面网元不会再向源移动边缘计算网元发送来自目标用户面网元的上行业务报文了；当源移动边缘计算网元向目标移动边缘计算网元发送第一指示信息之后，目标移动边缘计算网元可以确定来自源移动边缘计算网元的上行业务报文结束，即源移动边缘计算网元不会再向目标移动边缘计算网元发送上行业务报文了。
换句话说，目标UPF先向源UPF发送第二指示信息来指示来自目标UPF发送的第一上行业务报文发送结束，源UPF可以将第二指示信息转发给源MEC，源MEC将第二指示信息中的信元作为第一指示信息的信元向目标MEC发送，这样目标MEC就可以获知来自源MEC的第一上行业务报文也发送结束。当然，第一指示信息与第二指示信息是为了区分不同网元之间的信令，在实际处理过程中，第一指示信息和第二指示信息也可以为同一个指示信息，即目标UPF先向源UPF发送该指示信息，源UPF再将该指示信息发送给源MEC，源MEC将该指示信息发送给目标MEC。换种方式理解，第一指示信息或第二指示信息可以指示原始路径或者旧路径上的上行业务报文发送结束，原始路径或旧路径为：目标UPF-源UPF-源MEC-目标MEC，不管源MEC接收到第二指示信息还是目标MEC接收到第一指示信息，源MEC和目标UPF就可以确定后续不会再有原始路径或者旧路径上的上行业务报文了。
可选地，第二指示信息与第一上行业务报文的之间的顺序(S210和S220，或者，S230和S240)与第一指示信息与第一上行业务报文之间的顺序(S250和S260)相同，即S210中的第一上行业务报文在S220中的第二指示信息之前，则S230中的第一上行业务报文也在S240中的第二指示信息之前，则S250中的第一上行业务报文也在S260中的第一指示信息之前；如果S210和S220中的第一上行业务报文和第二指示信息同时发送，则S230和S240中的第一上行业务报文和第二指示信息也同时发送，S250和S260中的第一上行业务报文和第一指示信息也同时发送。下面分两种情况描述：
情况1，目标UPF可以将S210中第一上行业务报文和S220中的第二指示信息同时向源UPF发送，例如，若第一上行业务报文为目标UPF向源UPF发送的最后一个上行业务报文，则可以将第二指示信息封装在第一上行业务报文的报文头中向源UPF发送。同样地，源UPF可以将S230中的第一上行业务报文和S240中的第二指示信息同时向源MEC发送，例如，若第一上行业务报文为源UPF向源MEC发送的最后一个上行业务报文，则可以将第二指示信息封装在第一上行业务报文的报文头中向源MEC发送。同样地，源MEC可以将S250中的第一上行业务报文和S260中的第一指示信息同时向目标MEC发送，例如，若第一上行业务报文为源MEC向目标MEC发送的最后一个上行业务报文，则可以将第一指示信息封装在第一上行业务报文的报文头中向目标MEC发送。情况2，目标UPF向源UPF先发送第一上行业务报文，再发送携带第二指示信息的上行业务报文。 同样地，源UPF可以向源MEC先发送第一上行业务报文，再发送携带第二指示信息的上行业务报文，源MEC可以向目标MEC先发送第一上行业务报文，再发送携带第一指示信息的上行业务报文。例如，该携带第一指示信息的上行业务报文或携带第二指示信息的上行业务报文与第一上行业务报文具有相同的数据包格式，比如，第一上行业务报文是通用分组无线服务隧道协议(GPRS tunnelling protocol，GTP)数据包，其中，GPRS表示通用分组无线服务(general packet radio service)，GTP数据包包括用户层面的通用分组无线服务(GTP for the user plane，GTP-U)的头，那么携带该第一指示信息的上行业务报文和携带第二指示信息的上行业务报文也是GTP数据包，第一指示信息可以设置于GTP-U的头的特定标识位，比如将特定标识位设置为“0”或“1”。除了特定标识位外，携带第一指示信息的上行报文和携带第二指示信息的上行业务报文的GTP-U头，与第一上行业务报文的完全相同。
S270，在所述目标MEC网元接收到所述第一指示信息之后，当所述第一上行业务报文发送完毕，所述目标MEC网元向目标AS发送由目标UPF网元发送给目标MEC网元的上行业务报文。
因此，本申请实施例中，目标UPF向源UPF发送第一上行业务报文和第二指示信息，并且目标UPF向源UPF发送了第一上行业务报文之后，不再向源UPF发送上行业务报文，源UPF将第一上行业务报文和第二指示信息向源MEC转发，当源MEC向源AS发送了最后一个第二上行业务报文之后，将第二上行业务报文之后的第一上行业务报文通过目标MEC向目标AS发送，这样可以避免第一上行业务报文的丢失，并且源MEC可以向目标MEC发送第一指示信息来指示源MEC发送第一上行业务报文结束，这样可以避免目标MEC一直等待接收源MEC发送的上行业务报文，目标MEC在接收到第一指示信息之后，向目标AS发送完来自源MEC的上行业务报文之后，再发由目标UPF发送给目标MEC的上行业务报文，从而可以避免上行业务报文的乱序问题。
图6示出了本申请实施例提供的用于传输业务报文的方法300，包括：
S310，源应用服务器AS接收第一消息，所述第一消息用于触发所述源AS进行终端装置的上下文的迁移，所述第一消息包括目标DNAI；
可选地，源AS可以接收源MEC发送的第一消息，例如，第一消息可以是上下文迁移请求消息，用于向源AS请求迁移终端装置的上下文。可选地，源AS可以接收MEC应用管理网元发送的第一消息，例如，第一消息可以是方法400中的第二触发消息。
S320，所述源AS确定处理完第一下行业务报文和第二上行业务报文之后，所述源AS与所述目标DNAI对应的目标AS进行所述终端装置上下文的迁移，其中，所述第一下行业务报文为所述源AS向源移动边缘计算MEC网元发送的最后一个下行业务报文，所述第二上行业务报文为所述源MEC网元向所述源AS发送的最后一个上行业务报文。
在本申请实施例中，源AS接收到第一消息之后，可以确定终端装置的上下文需要迁移，在确定需要迁移终端装置的上下文之后，源AS确定要处理完最后一个下行业务报文(第一下行业务报文)和最后一个接收到的上行业务报文(第二上行业务报文)之后，源AS根据第一信息中的目标DNAI确定对应的目标AS，并将终端装置的上下文迁移至目标AS，这样，将终端装置的上下文迁移至目标AS之后，可以保证终端装置的上下行业务报文的连续传输。
需要说明的是，本发明中终端装置的上下文迁移指的是应用实例迁移或终端装置的传输层和应用层上下文迁移，具体可以是终端装置的某个应用实例的整体迁移，例如，当一个MEC应用实例只服务一个UE时，上下文迁移是指将终端装置与数据网络(DN)相关的整个应用实例从一个AS迁移到另一个AS；也可以是迁移终端装置的传输层和应用层的上下文，例如，当多个终端装置共享一个MEC应用实例时，终端装置的上下文迁移是指将终端装置需要迁移的应用的传输层和应用层上下文从一个AS迁移到另一个AS。
图7示出了本申请实施例提供的用于传输业务报文的方法400，包括：
S410，源MEC向MEC应用管理网元发送第一迁移请求消息，MEC应用管理网元接收源MEC网元发送的第一迁移请求消息，所述第一迁移请求消息包括第一应用实例的标识以及目标数据网络接入点标识DNAI。
例如，MEC的应用管理网元可以是VNFM。
S420，所述MEC应用管理网元根据所述第一应用实例的标识确定所要迁移的第一应用实例。
S430，所述MEC应用管理网元向所述目标DNAI对应的目标AS发送第一触发消息，第一触发消息包括所述第一应用实例的标识，所述第一触发消息用于触发所述目标AS进行所述应用实例的迁移。
S440，所述MEC应用管理网元向源应用实例对应的源AS发送第二触发消息，源AS接收第二触发消息，所述第二触发消息用于触发所述源AS进行所述第一应用实例的迁移。
具体来说，一个应用实例标识对应一个应用实例，源MEC向MEC应用管理网元发送的第一迁移请求消息中包括第一应用实例的标识，这样MEC应用管理网元就可以根据第一应用实例的标识确定将要迁移的第一应用实例，并且可以确定第一应用实例所在的源AS，即运行第一应用实例的AS为源AS，向源AS发送第二触发消息，用于触发源AS进行第一应用实例的迁移，MEC应用管理网元可以将第一应用实例的标识携带在第一触发消息中向目标AS发送，这样，可以将第一应用实例的上下文从源AS迁移至目标AS。
可选地，在S430之前，所述MEC应用管理网元确定目标DNAI对应的目标AS之后，可以在所述目标AS创建所述第一应用实例的虚拟资源，以便于所述目标AS根据所述虚拟资源迁移所述第一应用实例。
图8示出了本申请实施例提供的用于传输业务报文的方法500，包括：
S501，源MEC网元向源AS发送第一消息，源AS接收源MEC发送的第一消息，该第一消息包括目标DNAI。例如，第一消息可以是下面提到的第四迁移请求消息，用于向源AS请求迁移终端装置的上下文。
作为S501的可替换的方式，MEC的应用管理网元可以向源AS发送第一消息，例如第一消息可以是前述的第二触发消息，用于触发源AS迁移第一应用实例。
S502，源AS接收到第一消息之后，确定源AS向源MEC发送的最后一个下行业务报文是第一下行业务报文，源AS向源MEC发送第四指示信息，源MEC接收源AS发送的第四指示信息，该第四指示信息用于指示第一下行业务报文为来自源AS的最后一个下行业务报文。例如，该第四指示信息可以是第一下行业务报文的序列号。
可选地，源AS可以在向源MEC发送第四指示信息之前，向源MEC发送第一下行业务报文。可选地，源AS在向源MEC发送第四指示信息之后，向源MEC发送第一下行业 务报文。可选地，源AS向源MEC同时发送第四指示信息和第一下行业务报文，例如第四指示信息可以包括在第一下行业务报文的报文头中。无论第四指示信息和第一下行业务报文的发送顺序如何，源AS向源MEC发送第一下行业务报文之后不会再向源UPF发送下行业务报文。
可选地，在S502中，源AS在接收到第一消息之后，可以预冻结终端装置的上下文，例如，与目标AS交互为终端装置上下文迁移做准备，这样可以缩短终端装置上下文迁移的时间。
S503，源MEC接收到源AS发送的第四指示信息之后，源MEC向源AS发送第五指示信息，源AS接收源MEC发送的第五指示信息，该第五指示信息用于指示第二上行业务报文为源MEC发送给源AS的最后一个上行业务报文。例如，该第五指示信息可以是第二上行业务报文的序列号。
可选地，S502和S503中，可以是源AS的管理网元向源MEC发送第四指示信息。可选地，可以是源MEC向源AS的管理网元发送第五指示信息，再由源AS的管理网元向源AS转发第五指示信息。
S504，源AS接收到第五指示信息之后，可以确定第二上行业务报文为来自源MEC的最后一个上行业务报文，源AS确定第一下行业务报文和第二上行业务报文处理完毕。
具体的，源AS可以在收到第二上行业务报文，并回复该第二上行业务报文的确认消息后即确定第二上行业务报文处理完毕；可以在发送完第一下行业务报文并收到该第一下行业务报文的确认消息后即确定第一下行业务报文处理完毕。源AS也可以在收到第二上行业务报文即认为第二上行业务报文处理完毕，在发送了第一下行业务报文后即认为第一下行业务报文处理完毕。
S505，源AS在处理完第一下行业务报文和第二上行业务报文之后，与目标DNAI对应的目标AS进行终端装置的上下文的迁移。
S506，源MEC接收到源AS发送的第一下行业务报文之后，源MEC向源UPF发送第一下行业务报文，源UPF接收源MEC发送的第一下行业务报文。
S507，源MEC向源UPF发送第三指示信息，源UPF接收源MEC发送的第三指示信息，该第三指示信息用于指示来自源AS的下行业务报文发送结束。
需要说明的是，源MEC可以先发送第一下行业务报文，然后再发送携带第三指示信息的下行报文，该携带第三指示信息的下行报文与第一下行业务报文具有相同的数据包格式，比如，第一下行业务报文是GTP数据包，包括GTP-U的头，那么携带该第三指示信息的下行报文也是GTP数据包，第三指示信息可以设置于GTP-U的头的特定标识位，比如将特定标识位设置为“0”或“1”。除了特定标识位外，携带第三指示信息的下行报文的GTP-U头，与第一下行业务报文的完全相同；可选地，源MEC可以将第一下行业务报文和第三指示信息同时发送给源UPF，例如将第三指示信息封装在第一下行业务报文的报文头中。也需要说明的是，源AS和目标AS进行上下文的迁移可以与源MEC向源UPF发送第一下行业务报文和第三指示信息同时进行或者可以有先后顺序。换句话说，S504以及S505可以在S506以及S507之前或者之后或者同时进行。
S508，源UPF向目标UPF发送第一下行业务报文，目标UPF接收源UPF发送的第一下行业务报文。
S509，源UPF向目标UPF发送第三指示信息，目标UPF接收源UPF发送的第三指示信息。
需要说明的是，如果S506和S507中源MEC先发送第一下行业务报文，再发送携带第三指示信息的下行报文，源UPF可以也发送第一下行业务报文，然后再发送携带第三指示信息下行报文，即先执行S508，再执行S509；如果S506和S507中源MEC将第一下行业务报文和第三指示信息同时发送给源UPF，则S508和S509中源UPF将接收自源MEC的第一下行业务报文和第三指示信息同时发送给目标UPF。
S510，当源AS与目标AS完成终端装置的上下文迁移之后，并且目标AS与目标MEC之间的链路建立好之后，目标AS就可以向目标MEC发送终端装置的下行业务报文。
S511，目标MEC将S510中的下行业务报文向目标UPF发送。
S512，若目标UPF既有接收到来自S506的第一下行业务报文也有接收到来自目标MEC的下行业务报文，目标UPF会立即向接入网设备发送来自源AS的第一下行业务报文，若目标UPF在接收到第三指示信息之前有来自目标MEC的下行业务报文时，将来自目标MEC的下行业务报文缓存，当目标UPF在接收到第三指示信息之后，确定向接入网设备发送完第一下行业务报文之后，再向接入网设备发送来自目标MEC的下行业务报文，这样，可以保证优先传输来自源AS的下行业务报文，再传输来自目标AS的下行业务报文，可以避免下行业务报文的乱序。
S513，接入网设备将S512中接收到的下行业务报文通过空口发送给终端装置。
S514，终端装置不感知网络侧的网元的切换，终端装置在接收下行业务报文的同时也可以向接入网设备发送上行业务报文。
需要说明的是，S514与前述的任何一个步骤都没有顺序的限制，终端装置需要发送上行业务报文时，即执行S514，并没有任何顺序限制。
S515，接入网设备向目标UPF发送来自终端装置的上行业务报文。
同理，S515只要在S514之后即可，S515与前述的其他步骤都没有顺序的限制，接入网设备接收到终端装置发送的上行业务报文，有需要向目标UPF发送上行业务报文时，即执行S515，并没有任何顺序限制。
S516，目标UPF在接收到接入网设备发送的上行业务报文之后，向源UPF发送第一上行业务报文，直到目标UPF接收到第三指示信息之后，目标UPF不再向源UPF发送上行业务报文。
S517，目标UPF接收到第三指示信息之后向源UPF发送第二指示信息，该第一指示信息用于指示通过目标UPF发送第一上行业务报文结束，即目标UPF不会再向源UPF发送上行业务报文。
作为S517可替换的方式，目标UPF接收来自目标MEC的下行业务报文或者接收来自目标MEC发送的上下文迁移完成消息之后，目标UPF向源UPF发送第二指示信息。
换句话说，目标UPF向源UPF发送第二指示信息可以是分两种情况，情况一：目标UPF在接收到源UPF发送的第三指示信息之后，向源UPF发送第二指示信息；情况二：目标UPF在接收到目标MEC的下行业务报文或者接收到来自目标MEC发送的上下文迁移完成消息之后，向源UPF发送第二指示信息。
可选地，第二指示信息可以在最后一个第一上行业务报文之后发送，即目标UPF先 向源UPF发送第一上行业务报文，再发送携带第二指示信息的上行报文，该携带第二指示信息的上行报文与第一上行业务报文具有相同的数据包格式，比如，第一上行业务报文是GTP数据包，包括GTP-U的头，那么携带该第二指示信息的上行业务报文也是GTP数据包，第二指示信息可以设置于GTP-U的头的特定标识位，比如将特定标识位设置为“0”或“1”。除了特定标识位外，携带第二指示信息的上行报文的GTP-U头，与第一上行业务报文的完全相同。可选地，目标UPF也可以将第二指示信息封装在最后一个第一上行业务报文的报文头中发送给源UPF。
S518，源UPF接收到来自目标UPF的第一上行业务报文时，则将第一上行业务报文转发给源MEC，源MEC接收来自源UPF的第一上行业务报文。
S519，源UPF也将来自目标UPF的第二指示信息转发给源MEC，源MEC接收来自源UPF的第二指示信息。
S520，源MEC在向源AS发送第五指示信息之后，接收到来自目标UPF的第一上行业务报文时，则将第一上行业务报文转发给目标MEC。
S521，源MEC接收到第二指示信息之后，源MEC向目标MEC发送第一指示信息，这样，目标MEC就可以通过第一指示信息确定来自源MEC的上行业务报文结束。第一指示信息与第二指示信息的相关描述参见方法200中的描述。
需要说明的是，源UPF按序向源MEC发送第一上行业务报文和第二指示信息，即源UPF根据接收第一上行业务报文和第二指示的顺序向源MEC发送第一上行业务报文和第二指示信息。源MEC按序向目标MEC发送第一上行业务报文和第一指示信息，第二指示信息与第一上行业务报文的顺序关系与第一指示信息与上行业务报文的顺序关系相同，源MEC先接收到源UPF发送的第一上行业务报文后接收到源UPF发送的第二指示信息，则源MEC先向目标MEC先发送第一上行报文再发送第一指示信息，即源MEC根据接收第一上行业务报文和第二指示信息的顺序向目标MEC发送第一上行业务报文和第一指示信息。
S522，目标UPF向源UPF发送第一上行业务报文和第二指示信息之后，不再向源UPF发送上行业务报文，当又接收到来自接入网设备的上行业务报文，则需要向目标MEC发送。
S523，目标MEC与目标AS建立好上行链路之后，目标MEC可以向目标AS发送上行业务报文。具体的，发送过程是：先发送第一上行业务报文，即来自源MEC的上行业务报文，再发送来自目标UPF的上行接入报文，换句话说，先发送S520的第一上行业务报文，再发送S522的上行业务报文。
为了更好的说明S515-S523，下面进行举例描述，假设S515中，接入网设备向目标UPF按序发送的业务报文为报文1、报文2、报文3、报文4和报文5，目标UPF按序接收这5个报文，下面分两种情况描述，情况一：当目标UPF接收到源UPF发送的第三指示信息时，目标UPF已经按序向源UPF发送了报文1、报文2和报文3。目标UPF根据第三指示信息确定不再向源UPF发送上行业务报文，即目标UPF向源UPF发送第二指示信息，来指示来自目标UPF的上行业务报文结束，目标UPF按序向目标MEC发送报文4和报文5，此时报文1、报文2和报文3为第一上行业务报文，源UPF按序接收到报文1、报文2、报文3以及第二指示信息之后，将报文1、报文2、报文3以及第二指示信息按 序发送给源MEC，源MEC按序接收到报文1、报文2、报文3以及第二指示信息之后，将报文1、报文2、报文3以及第一指示信息(第一指示信息的报文中的次序与第二指示信息在报文中次序相同)按序发送给目标MEC，目标MEC向目标AS按序发送报文1、报文2、报文3，目标MEC在接收到第一指示信息之后，并且在向目标AS按序发送完报文1、报文2和报文3之后，再发送来自目标UPF的报文4和报文5。情况二，当接收到源UPF发送的第三指示信息时，目标UPF确定最后向源UPF发送的业务报文为报文4，并将第二指示信息封装在报文4的报文头中向源UPF发送，目标UPF将报文5向目标MEC发送，此时报文1、报文2、报文3和报文4为第一上行业务报文。源UPF按序接收到报文1、报文2、报文3以及报文4之后，将报文1、报文2、报文3以及报文4按序发送给源MEC，源MEC向目标MEC按序发送报文1、报文2、报文3和报文4(此时报文4中的第二指示信息被替换为第一指示信息)，目标MEC解报文4的报文头中的第一指示信息之后，并且在向目标AS按序发送完报文1、报文2、报文3和报文4，再发送来自目标UPF的报文5。
需要说明的是，第一上行业务报文为在终端装置的上下文迁移过程中，已经发送到源UPF或源MEC但还没有转发给源AS的上行业务报文，已经发送到源UPF或源MEC的报文也可以称为旧路径或者原路径上的报文，此时需要将旧路径或者原路径上的报文转发到目标MEC，通过目标MEC转发至目标AS，以避免上行业务报文的丢失。并且通过第一指示信息指示旧路径或者原路径上的报文结束了，这样目标MEC保证旧路径或者原路径上的上行业务报文发送完成之后，再发送来自目标UPF的上行业务报文，可以避免上行业务报文出现乱序的问题。
下面结合图9描述本申请实施例提供的在图3场景下的用于传输业务报文的方法600，方法600包括：
S601，SMF或PCF确定终端装置的锚点UPF切换后DNAI要变化，确定需要执行终端装置的上下文迁移或者应用迁移(application relocation)，SMF或PCF确定目标DNAI。
S602，SMF或PCF向源MEC发送第二迁移请求消息，源MEC接收SMF或者PCF发送的第二迁移请求消息，第二迁移请求消息用于触发迁移终端装置的上下文，第二迁移请求消息包括目标DNAI以及终端装置的标识。
例如，终端装置的标识可以是终端装置的身份标识(identity，ID)或者终端装置的网络协议(internet protocol，IP)地址或者也可以是终端装置的通用公共签约标识(generic public subscription identifier，GPSI)等。
S603，源MEC接收到第二迁移请求消息之后，向目标MEC发送第三迁移请求消息，第三迁移请求消息用于向目标MEC请求是否接受终端装置的上下文的迁移，第三迁移请求消息包括终端装置的标识。
S604，若目标MEC能够接受终端装置上下文的迁移，则向源MEC发送第三迁移请求消息的应答消息，第三迁移请求消息的应答消息用于指示目标MEC能够接受终端装置上下文的迁移。
S605，目标MEC向目标AS发送第四迁移请求消息，目标AS接收目标MEC发送的第四迁移请求消息，第四迁移请求消息用于向目标AS请求能否接受终端装置的上下文的迁移，或第四迁移请求消息用于指示目标AS终端装置的上下文迁移，第四迁移请求消息 包括终端装置的标识。可选的，第四迁移请求消息还包括源AS对应的源DNAI。
S606，若目标AS接受终端装置上下文的迁移，则向目标MEC发送第四请求消息的应答消息，第四迁移请求消息的应答消息用于指示目标AS能够接收终端装置上下文的迁移。
S607，源MEC接收到第二迁移请求消息之后，向源AS发送第五迁移请求消息，第五迁移请求消息用于向AS请求迁移终端装置的上下文，第五迁移请求消息包括终端装置的标识和目标DNAI。
例如，前述的第一消息可以是这里的第五迁移请求消息。
可选地，方法600还包括：S608，源AS接收到第五迁移请求消息之后，源AS预冻结终端装置的上下文，为迁移终端装置的上下文做准备。
需要说明的是，S608在S602之后即可，S608与S603的顺序并没有任何限制。
需要说明的是，本申请实施例仅以源AS与目标AS要迁移终端装置的上下文为例描述。但本申请实施例不限于此，源AS与目标AS也可以迁移终端装置的应用实例，鉴于此，第二迁移请求消息、第三迁移请求消息、第四迁移请求消息和第五迁移请求消息还包括：应用的标识或应用实例的标识，这样，源AS和目标AS就可以迁移终端装置的应用实例。
S609，源AS向源MEC发送第四指示信息，第四指示信息用于指示第一下行业务报文为来自源AS的最后一个下行业务报文，即源AS发送完第一下行业务报文之后，不再向源MEC发送下行业务报文。例如，第四指示信息可以是第一下行业务报文的序列号。
可选地，源AS可以在向源MEC发送第四指示信息之前，向源MEC发送第一下行业务报文。可选地，源AS在向源MEC发送第四指示信息之后，向源MEC发送第一下行业务报文。可选地，源AS向源MEC同时发送第四指示信息和第一下行业务报文，例如第四指示信息可以包括在第一下行业务报文的报文头中。无论第四指示信息和第一下行业务报文的发送顺序如何，源AS向源MEC发送第一下行业务报文之后不会再向源UPF发送下行业务报文。
可选地，在S608之后，执行S609。
S610，源MEC接收到第四指示信息之后，向源AS发送第五指示信息，第五指示信息用于指示第二上行业务报文为源MEC发送给源AS的最后一个上行业务报文，即源MEC向源AS发送完第二上行业务报文后，不再向源AS发送上行业务报文。例如，第五指示信息可以是第二上行业务报文的序列号。
可选地，S609和S610中，可以是源AS的管理网元向源MEC发送第四指示信息。可选地，可以是源MEC向源AS的管理网元发送第五指示信息，再由源AS的管理网元向源AS转发第五指示信息。
S611，源AS根据第五指示信息确定第二上行业务报文为来自源UPF的最后一个上行业务报文，并且源AS确定最后发送的第一下行业务报文和最后接收的第二上行业务报文处理完毕。
具体的，源AS可以在收到第二上行业务报文，并回复该第二上行业务报文的确认消息后即确定第二上行业务报文处理完毕；可以在发送完第一下行业务报文并收到该第一下行业务报文的确认消息后即确定第一下行业务报文处理完毕。源AS也可以在收到第二上 行业务报文即认为第二上行业务报文处理完毕，在发送了第一下行业务报文后即认为第一下行业务报文处理完毕。
S612，源AS根据目标DNAI确定目标AS，并与目标AS完成终端装置的上下文的迁移。
S613，源AS与目标AS完成终端装置的上下文的迁移之后，源AS向源MEC发送上下文迁移完成消息。
S614，目标AS向目标MEC发送上文迁移完成消息。
需要说明的是，S613和S614的顺序并没有任何限制。
S615，第一下行业务报文为来自源AS的最后一个下行业务报文，源MEC接收到源AS发送的第一下行业务报文之后，源MEC向源UPF发送第一下行业务报文，源UPF接收源MEC发送的第一下行业务报文。
S616，源MEC接收到第四指示信息之后，向源UPF发送第三指示信息，源UPF接收源MEC发送的第三指示信息，该第三指示信息用于指示来自源AS的下行业务报文发送结束。换句话说，该第三指示信息可以指示来自旧路径或者原路径上的下行业务报文结束。
可选地，S615与S616可以同时进行，即源MEC可以将第三指示信息与第一下行业务报文同时发送给源UPF，例如，将第三指示信息封装在第一下行业务报文的报文头中发送，这种情况下，S615和S616在S609之后。可选地，先执行S615再执行S616，即源MEC可以将第一下行业务报文发送之后，再发送第三指示信息，这种情况下，S616在S609之后即可，S615与S609的顺序也不限定。换句话说，源MEC接收到第四指示信息之后触发源MEC向源UPF发送第三指示信息，若第一下行业务报文与第三指示信息同时发送，则第一下行业务报文与第三指示信息是在S609之后发送；若第一下行业务报文在第三指示信息之前发送，则第三指示信息在S609之后发送即可，S615与S609的顺序不限定。
需要说明的是，S616与S610-S614的顺序没有任何限制，S616只要在S609之后即可。
S617，源UPF将来自源MEC的第一下行业务报文发送给目标UPF。
S618，源UPF将来自源MEC的第三指示信息发送给目标UPF。
需要说明的是，如果S615和S616中源MEC先发送第一下行业务报文，再发送携带第三指示信息的下行报文，源UPF可以也发送第一下行业务报文，然后再发送携带第三指示信息下行业务报文，即先执行S617，再执行S618；如果S615和S616中源MEC将第一下行业务报文和第三指示信息同时发送给源UPF，则S617和S618中源UPF将接收自源MEC的第一下行业务报文和第三指示信息同时发送给目标UPF。
S619，在S612之后，目标AS与目标MEC已经建立好链路之后，目标AS就可以向目标MEC发送下行业务报文。
S620，目标MEC将S619中的下行业务报文发送给目标UPF。
S621，目标UPF既有S617中接收到来自源UPF的第一下行业务报文也有S619中接收到来自目标MEC的下行业务报文，若目标UPF在接收到第三指示信息之前有来自目标MEC的下行业务报文时，将来自目标MEC的下行业务报文缓存，当目标UPF在接收到第三指示信息之后，确定向接入网设备发送完第一下行业务报文之后，再向接入网设备发送来自目标MEC的下行业务报文，这样，可以保证优先传输来自源AS的下行业务报文， 再传输来自目标AS的下行业务报文，可以避免下行业务报文的乱序。
S622，接入网设备将S621中接收到的下行业务报文通过空口发送给终端装置.
S623，终端装置不感知网络侧的切换，终端装置在接收下行业务报文的同时也在向接入网设备发送上行业务报文。
需要说明的是，S623与前述的任何一个步骤都没有顺序的限制，终端装置需要发送上行业务报文时，即执行S623，并没有任何顺序限制。
S624，接入网设备向目标UPF发送来自终端装置的上行业务报文。
同理，S624只要在S623之后即可，S624与前述的其他步骤都没有顺序的限制，接入网设备接收到终端装置发送的上行业务报文，有需要向目标UPF发送上行业务报文时，即执行S624，并没有任何顺序限制。
S625，目标UPF在接收到接入网设备发送的上行业务报文之后，向源UPF发送第一上行业务报文，直到目标UPF接收到第三指示信息之后，目标UPF不再向源UPF发送上行业务报文。
S626，目标UPF接收到第三指示信息之后向源UPF发送第二指示信息，该第一指示信息用于指示通过源UPF发送的第一上行业务报文结束，即目标UPF不会再向源UPF发送上行业务报文。
作为S626可替换的方式，目标UPF接收来自目标MEC的下行业务报文或者接收来自目标MEC发送的上下文迁移完成消息之后，目标UPF向源UPF发送第二指示信息。在S619之后，目标MEC可以向目标UPF发送上下文迁移完成消息。
换句话说，目标UPF向源UPF发送第二指示信息可以是分两种情况，情况一：目标UPF在接收到源UPF发送的第三指示信息之后，向源UPF发送第二指示信息；情况二：目标UPF在接收到目标MEC的下行业务报文或者来自MEC发送的上下文迁移完成消息之后，向源UPF发送第二指示信息。
可选地，第二指示信息可以在最后一个第一上行业务报文之后发送，即目标UPF先向源UPF发送第一上行业务报文，再发送携带第二指示信息的上行业务报文，该携带第二指示信息的上行业务报文与第一上行业务报文具有相同的数据包格式，比如，第一上行业务报文是GTP数据包，包括GTP-U的头，那么携带该第二指示信息的上行报文也是GTP数据包，第二指示信息可以设置于GTP-U的头的特定标识位，比如将特定标识位设置为“0”或“1”。除了特定标识位外，携带第二指示信息的上行报文的GTP-U头，与第一上行业务报文的完全相同。可选地，目标UPF也可以将第二指示信息封装在最后一个第一上行业务报文的报文头中发送给源UPF。
S627，源UPF接收到来自目标UPF的第一上行业务报文时，则将第一上行业务报文转发给源MEC，源MEC接收来自源UPF的第一上行业务报文。
S628，源UPF也将来自目标UPF的第一指示信息转发给源MEC，源MEC接收来自源UPF的第一指示信息。
S629，源MEC在向源AS发送第五指示信息之后，接收到来自源UPF的第一上行业务报文时，则将第一上行业务报文转发给目标MEC。
S630，源MEC接收到第二指示信息之后，源MEC向目标MEC发送第一指示信息，这样，目标MEC就可以通过第一指示信息确定来自源MEC的上行业务报文结束。第一 指示信息与第二指示信息的相关描述参见方法200中的描述。
需要说明的是，源UPF按序向源MEC发送第一上行业务报文和第二指示信息，即源UPF根据接收第一上行业务报文和第二指示的顺序向源MEC发送第一上行业务报文和第二指示信息。源MEC按序向目标MEC发送第一上行业务报文和第一指示信息，第二指示信息与第一上行业务报文的顺序关系与第一指示信息与上行业务报文的顺序关系相同，源MEC先接收到源UPF发送的第一上行业务报文后接收到源UPF发送的第二指示信息，则源MEC先向目标MEC先发送第一上行报文再发送第一指示信息，即源MEC根据接收第一上行业务报文和第二指示的顺序向目标MEC发送第一上行业务报文和第一指示信息。
S631，目标UPF向源UPF发送第一上行业务报文和第二指示信息之后，不再向源UPF发送上行业务报文，当又接收到来自接入网设备的上行业务报文，则需要向目标MEC发送。
S632，在S613之后，表示目标MEC与目标AS建立好链路，目标MEC可以向目标AS发送上行业务报文。或者，在目标MEC接收到来自目标AS的下行业务报文后，目标MEC确定与目标AS建立好链路，目标MEC可以向目标AS发送上行业务报文。具体的，发送过程是：先发送第一上行业务报文，即S629中来自源MEC的上行业务报文，再发送S631中直接来自目标UPF的上行接入报文。
也就是说，在S632中，目标MEC确定可以向目标AS发送上行业务报文之前，目标MEC都会缓存直接来自目标UPF发送的上行业务报文。
可选地，在方法600中，在源MEC与源AS交互之前，源AS向源MEC进行注册，注册内容包括业务标识(application identifier)；可选地，注册的内容还可以包括应用实例(application instance)标识或者业务流模板(traffic filtering information，如业务的五元组)。有了这些信息，源MEC就可以检测到业务的开始和结束。可选地，在目标MEC与目标AS交互之前，源AS向源MEC进行注册，注册内容包括业务标识；可选地，注册的内容还可以包括应用实例标识或者业务流模板。有了这些信息，目标MEC就可以检测到业务的开始和结束。
需要说明的是，第一上行业务报文为在终端装置的上下文迁移过程中，已经发送到源UPF或者源MEC但还没有转发给源AS的上行业务报文，已经发送到源UPF或者源MEC的报文也可以称为旧路径或者原路径上的报文，此时需要将旧路径或者原路径上的报文转发到目标MEC，通过目标MEC转发至目标AS，以避免上行业务报文的丢失。并且通过第一指示信息指示旧路径或者原路径上的报文结束了，这样目标MEC保证旧路径或者原路径上的上行业务报文发送完成之后，再发送来自目标UPF的上行业务报文，可以避免上行业务报文出现乱序的问题。
下面结合图10描述本申请实施例提供的在图4场景下的用于传输业务报文的方法700，方法700包括：
S701，SMF或PCF确定终端装置的锚点UPF切换后DNAI要变化，确定需要执行终端装置的第一应用实例迁移(application relocation)，SMF或PCF确定目标DNAI。
S702，SMF或PCF向源MEC发送第二迁移请求消息，源MEC接收SMF或者PCF发送的第二迁移请求消息，第二迁移请求消息用于触发迁移第一应用实例的上下文，第二 迁移请求消息包括目标DNAI以及第一应用实例的标识。
S703，源MEC接收到第二迁移请求消息之后，向目标MEC发送第三迁移请求消息，第三迁移请求消息用于向目标MEC请求是否接受第一应用实例的上下文的迁移，第三上行文迁移请求消息包括第一应用实例的标识。
S704，若目标MEC能够接受终端装置上下文的迁移，则向源MEC发送第三迁移请求消息的应答消息，第三迁移请求的应答消息用于指示目标MEC能够接受第一应用实例上下文的迁移。
S705，源MEC向MEC应用管理网元发送第一迁移请求消息，第一迁移请求消息用于向MEC应用管理网元请求迁移第一应用实例的上下文，第一迁移请求消息包括第一应用实例的标识和目标DNAI。
S706，MEC应用管理网元向源MEC发送第一迁移请求消息的应答消息，用于指示MEC应用管理网元能够接受第一应用实例的上下文的迁移。
S707，MEC应用管理网元向源AS发送第二触发消息，第二触发消息用于触发所述源AS进行所述第一应用实例的迁移。
S708，MEC应用管理网元确定目标DNAI对应的目标AS之后，在目标AS处创建所述第一应用实例的虚拟资源，这样，所述目标AS根据所述虚拟资源迁移所述第一应用实例。例如，MEC应用管理网元可以指示目标AS安装一个虚拟机，利用虚拟机迁移第一应用实例。
S709，MEC应用管理网元向目标AS发送第一触发消息，第一触发消息包括第一应用实例的标识。
需要说明的是，S707与S709的顺序没有任何限定，可以同时进行，或者有先后顺序，本申请实施例对此不作限制。
可选地，方法700还包括：S710，源AS接收到第二触发消息之后，源AS预冻结第一应用实例的上下文，为迁移第一应用实例的上下文做准备。
S711-S714同S609-S612。
S715，源AS与目标AS完成第一应用实例的上下文的迁移之后，目标AS向MEC应用管理网元发送上下文迁移完成消息。
S716，源AS与目标AS完成第一应用实例的上下文的迁移之后，源AS向MEC应用管理网元发送上文迁移完成消息。
需要说明的是，S714与S715的顺序没有任何限定，可以同时进行，或者有先后顺序，本申请实施例对此不作限制。
S717，MEC应用管理网元向源MEC发送上下文迁移完成消息。
S718，MEC应用管理网元向目标MEC发送上行文完成消息。
S719，目标AS向目标MEC发送业务注册请求，该业务注册请求用于请求包括业务标识，业务标识用于标识一个应用，一个应用可以对应多个应用实例，这样，一个业务标识可以对应多个应用实例标识。可选地，注册的内容还可以包括应用实例(application instance)标识或者业务流模板(traffic filtering information，如业务的五元组)，有了这些信息，目标MEC就可以检测到业务的开始和结束。
需要说明的是，S719在S715之后即可，S719与S717和S718的顺序不作任何限制。
S720-S737同S615-S632。
下面结合图11和图12简要描述本申请实施例的下行业报文和上行业务报文。
对于下行业务报文，如图11所示，终端装置在移动之前，下行业务报文的传输路径为：源AS-源MEC源UPF-源接入网设备-终端装置。终端装置从源接入网设备的覆盖范围内移动到目标接入网设备的范围时，终端装置空口切换到目标接入网设备，此时，下行业务报文的传输路径为：源AS-源MEC-源UPF-目标UPF-目标接入网设备-终端装置，此路径为称之为旧路径或者原路径。在旧路径或者原路径上业务报文的传输路径变长，导致旧路径或者原路径上的报文的时延较大，因此，有必要将下行业务报文的路径进行切换，切换至新路径：目标AS-目标MEC-目标UPF-目标接入网设备-终端装置。但是在将下行业务报文的路径从旧路径或者原路径切换至新路径上时，旧路径上的下行业务报文容易乱序。本申请实施例中，目标UPF可以同时接收来自旧路径以及新路径上的下行业务报文，即目标UPF可以既接收源UPF发送的下行业务报文也可以接收目标MEC发送的下行业务报文。对于旧路径上的下行业务报文，源AS向源MEC发送第四指示信息，来指示源AS向源MEC发送的最后一个下行业务报文为第一下行业务报文，源MEC接收到第四指示信息之后，并向源UPF发送完第一下行业务报文之后，源MEC向源UPF发送第三指示信息，源UPF将第三指示信息转发给目标UPF，来指示来自源AS的下行业务报文结束。目标UPF在接收到第三指示信息之前，将来自旧路径上的下行业务报文按序向目标接入网设备发送，将来自新路径上的报文进行缓存，直到目标UPF接收到第三指示信息，并且保证旧路径上的下行业务报文都已经发送完毕之后，再发送新路径上的下行业务报文，这样，可以避免下行业务报文乱序的问题。换句话说，对于目标UPF需要保证旧路径上的下行业务报文都发送完毕之后才能发送新路径上的下行业务报文。
对于上行业务报文，如图12所示，终端装置在移动之前，上行业务报文的传输路径为：终端装置-源接入网设备-源UPF-源MEC-源AS。终端装置从源接入网设备的覆盖范围内移动到目标接入网设备的范围时，终端装置空口切换到目标接入网设备，此时，上行业务报文的传输路径为：终端装置-目标接入网设备-目标UPF-源UPF-源MEC-源AS，此路径为称之为旧路径或者原路径。在旧路径或者原路径上业务报文的传输路径变长，导致旧路径或者原路径上的业务报文的时延较大。因此，有必要将上行业务报文的路径进行切换，切换至新路径：终端装置-目标接入网设备-目标UPF-目标MEC-目标AS。但是在将上行业务报文的路径从旧路径或者原路径切换至新路径上时，旧路径上的上行业务报文容易丢失。本申请实施例中，在切换路径的过程中已经发送到目标UPF但是还没有到达源AS的上行业务报文的传输路径可以是：目标UPF-源UPF-源MEC-目标MEC-目标AS。具体地，当目标UPF接收到源UPF发送的第三指示信息，来指示旧路上的下行业务报文发送结束。目标UPF向源UPF发送最后一个上行业务报文的同时可以发送第一指示信息，来指示来自目标UPF的上行业务报文结束，目标UPF再接收到来自目标接入网设备的上行业务报文时直接发送给目标MEC，不再向源UPF发送。源UPF将从目标UPF接收到的上行业务报文以及第一指示信息都转发到源MEC，源MEC向源AS发送完最后一个上行业务报文(第二上行业务报文)之后，将第二上行业务报文之后的第一上行业务报文以及第一指示信息按序返回给目标MEC，即将切换过程中旧路径上的报文转发至新路径上，目标MEC可以根据第一指示信息确定旧路径上的上行业务报文发送结束，目标MEC确 保旧路径上的业务报文都已经按序向目标AS发送完毕之后，再发送缓存的来自目标UPF的上行业务报文(新路径)。这样，在避免上行业务报文丢失的同时可以避免上行业务报文乱序的问题。换句话说，对于目标MEC需要保证旧路径上的上行业务报文都发送完毕之后才能发送新路径上的上行业务报文。
需要说明的是，本申请实施例以源AS与目标AS需要迁移终端装置的上下文为例描述，例如，方法600包括终端装置的标识。但是本申请实施例不限于此，终端装置可能正在运行某个应用(application，APP)，这种情况下，源AS与目标AS需要迁移终端装置的应用的上下文，方法600可以包括终端装置的标识和应用的标识。终端装置可能正在运行某个PDU会话，这种情况下，源AS与目标AS需要迁移终端装置的PDU会话的上下文，例如，方法600中包括终端装置的标识和PDU会话的标识。为了避免赘述本申请实施例不详细举例说明。
也需要说明的是，本申请实施例中可以先发送第一下行业务报文再发送第三指示信息，或者可以同时发送第一下行业务报文和第三指示信息。在同时发送第一下行业务报文和第三指示信息的情况下，可以在第一下行业务报文的报文头中的特定的比特为设置为特定的取值，例如，特定的取值为1或0，即特定的取值为0或1时，表示该第一下行业务报文为来自源AS的最后一个下行业务报文。
本申请实施例中可以先发送第一上行业务报文再发送第一指示信息(或者第二指示信息)，或者可以同时发送第一上行业务报文和第一指示信息(或者第二指示信息)。在同时发送第一上行业务报文和第一指示信息(或者第二指示信息)的情况下，可以在第一下行业务报文中的最后一个的业务报文头中的特定的比特为设置为特定的取值作为第一指示信息或第二指示信息，例如，特定的取值为1或0，即特定的取值为0或1时，表示该第一上行业务报文结束。
以上结合图1至图12，详细得描述了本申请实施例提供的用于传输业务报文的方法，下面结合图13至图18，详细描述本申请实施例提供的用于传输业务报文的装置。
图13示出了本申请实施例提供的用于传输业务报文的装置800的示意性框图，该装置800可以对应上述方法中描述的源MEC，也可以对应源MEC的芯片或者组件，并且，该装置800中各个模块或者单元分别可以用于执行上述方法中源MEC所执行的各动作或处理过程，如图13所示，该用于传输业务报文的装置800可以包括接收单元810和发送单元820。
接收单元810，用于接收到第二上行业务报文之后，接收源用户面网元发送的来自目标用户面网元的第一上行业务报文，所述第二上行业务报文为所述源移动边缘计算网元向源应用服务器发送的最后一个上行业务报文。
发送单元820，用于向目标MEC发送第一上行业务报文；
发送单元820，用于向目标MEC发送第一指示信息，第一指示信息用于指示装置800发送第一上行业务报文结束。
需要说明的是，接收单元810和发送单元820可以是同一个收发单元，也可以是不同的收发单元，本申请实施例对此不作限制。
作为一个可选实施例，接收单元810还用于：
在向目标MEC发送第一上行业务报文之前，接收源用户面功能UPF发送的来自目标 UPF的第一上行业务报文和第一指示信息。
作为一个可选实施例，发送单元820还用于：在向目标MEC发送第一上行业务报文之前，向源UPF发送第一下行业务报文和第三指示信息，第三指示信息用于指示来自源AS的下行业务报文发送结束。
作为一个可选实施例，接收单元810还用于：在向源UPF发送第一下行业务报文之前，接收第一网元发送的第四指示信息，第四指示信息用于指示来自源AS的最后的一个下行业务报文为第一下行业务报文；向第一网元发送第五指示信息，第五指示信息用于指示第二上行业务报文为装置发送给源AS的最后一个上行业务报文。
应理解，装置800中各单元执行上述相应步骤的具体过程请参照前文中结合图5-图12的方法实施例的描述，为了简洁，这里不加赘述。
图14示出了本申请实施例提供的用于传输业务报文的装置900的示意性框图，该装置900可以对应上述方法中描述的目标UPF，也可以对应目标UPF的芯片或者组件，并且，该装置900中各个模块或者单元分别可以用于执行上述方法中目标UPF所执行的各动作或处理过程，如图14所示，该用于传输业务报文的装置900可以包括第一收发单元910和第二收发单元920。
第一收发单元910，用于向源UPF发送第一上行业务报文，在装置向源UPF发送第一上行业务报文之后不再向源UPF发送上行业务报文；
第二收发单元920，用于向源UPF发送第二指示信息，第二指示信息用于指示目标用户面网元发送第一上行业务报文结束。
需要说明的是，第一收发单元910和第二收发单元920可以是同一个收发单元，也可以是不同的收发单元，本申请实施例对此不作限制。
作为一个可选实施例，第一收发单元910或第二收发单元920还用于：
在向源UPF发送第一上行业务报文之前，接收来自源UPF的第一下行业务报文和第三指示信息，第三指示信息用于指示来自源应用服务器AS的下行业务报文发送结束。
作为一个可选实施例，第二收发单元920具体用于：
根据第三指示信息向源UPF发送第一指示信息。
作为一个可选实施例，第二收发单元920具体用于：
接收来自SMF网元或目标MEC发送的上下文迁移完成消息之后，向源UPF发送第一指示信息。
作为一个可选实施例，第一收发单元910或第二收发单元920还用于：
在向源UPF发送第一指示信息之后，向目标移动边缘计算MEC发送来自接入网设备的上行业务报文。
作为一个可选实施例，第一收发单元910或第二收发单元920还用于：在接收第三指示信息之后，当第一下行业务报文发送完毕，向接入网设备发送来自目标MEC的下行业务报文。
应理解，装置900中各单元执行上述相应步骤的具体过程请参照前文中结合图5-图12的方法实施例的描述，为了简洁，这里不加赘述。
图15示出了本申请实施例提供的用于传输业务报文的装置1000的示意性框图，该装置1000可以对应上述方法中描述的目标MEC，也可以对应目标MEC的芯片或者组件， 并且，该装置1000中各个模块或者单元分别可以用于执行上述方法中目标MEC所执行的各动作或处理过程，如图15所示，该用于传输业务报文的装置1000可以包括接收单元1010和发送单元1020。
接收单元1010，用于接收来自源移动边缘计算MEC的第一上行业务报文，第一上行业务报文为源MEC接收到第二上行业务报文之后的所接收的上行业务报文，第二上行业务报文为源MEC向源应用服务器AS发送的最后一个上行业务报文；
接收单元1010还用于：接收来自源MEC的第一指示信息，第一指示信息用于指示源MEC发送第一上行业务报文结束；
发送单元1020，用于在接收到第一指示信息之后，当第一上行业务报文发送完毕，向目标AS发送由目标用户面功能UPF发送给目标MEC的上行业务报文。
应理解，装置1000中各单元执行上述相应步骤的具体过程请参照前文中结合图5-图12的方法实施例的描述，为了简洁，这里不加赘述。
图16示出了本申请实施例提供的用于传输业务报文的装置1100的示意性框图，该装置1100可以对应上述方法中描述的源AS，也可以对应源AS的芯片或者组件，并且，该装置1100中各个模块或者单元分别可以用于执行上述方法中源AS所执行的各动作或处理过程，如图16所示，该用于传输业务报文的装置1100可以包括收发单元1110和迁移单元1120。
收发单元1110，用于接收第一消息，第一消息用于触发终端装置的上下文的迁移，第一消息包括目标数据网络接入点标识DNAI；
迁移单元1120，用于确定处理完第一下行业务报文和第二上行业务报文之后，与目标DNAI对应的目标应用服务器AS进行终端装置上下文的迁移，其中，第一下行业务报文为装置向源移动边缘计算MEC发送的最后一个下行业务报文，第二上行业务报文为源MEC向装置发送的最后一个上行业务报文。
作为一个可选实施例，收发单元1110还用于：在与目标DNAI进行终端装置上下文的迁移之前，向源MEC发送第四指示信息，第四指示信息用于指示第一下行业务报文为来自装置的最后一个下行业务报文；接收源MEC发送的第五指示信息，第五指示信息用于指示第二上行业务报文为源MEC向装置发送的最后一个上行业务报文。
应理解，装置1100中各单元执行上述相应步骤的具体过程请参照前文中结合图5-图12的方法实施例的描述，为了简洁，这里不加赘述。
图17示出了本申请实施例提供的用于传输业务报文的装置1200的示意性框图，该装置1200可以对应上述方法中描述的MEC应用管理网元，也可以对应MEC应用管理网元的芯片或者组件，并且，该装置1200中各个模块或者单元分别可以用于执行上述方法中MEC应用管理网元所执行的各动作或处理过程，如图17所示，该用于传输业务报文的装置1200可以包括收发单元1210和处理单元1220。
收发单元1210，用于接收源移动边缘计算MEC发送的第一迁移请求消息，第一迁移请求消息包括第一应用实例的标识以及目标数据网络接入点标识DNAI；
处理单元1220，用于根据第一应用实例的标识确定所要迁移的第一应用实例；
收发单元1210还用于分别向目标DNAI对应的目标AS和第一应用实例对应的源AS发送第一触发消息和第二触发消息，第一触发消息包括第一应用实例的标识，第一触发消 息用于触发目标AS进行第一应用实例的迁移，第二触发消息用于触发源AS进行第一应用实例的迁移。
作为一个可选实施例，处理单元1220还用于：在分别向DNAI对应的目标AS和目标应用实例对应的源AS发送的第一触发消息和第二触发消息之前，在目标AS创建第一应用实例的虚拟资源，以便于目标AS根据虚拟资源迁移第一应用实例。
应理解，装置1200中各单元执行上述相应步骤的具体过程请参照前文中结合图5-图12的方法实施例的描述，为了简洁，这里不加赘述。
上述各个方案的装置800具有实现上述方法中源MEC执行的相应步骤的功能；上述各个方案的装置900具有实现上述方法中目标UPF执行的相应步骤的功能；上述各个方案的装置1000具有实现上述方法中目标MEC执行的相应步骤的功能；上述各个方案的装置1100具有实现上述方法中源AS执行的相应步骤的功能；上述各个方案的装置1200具有实现上述方法中MEC应用管理网元执行的相应步骤的功能；功能可以通过硬件或软件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块；例如发送单元可以由通信接口替代，接收单元可以由通信接口替代，其它单元，如确定单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。在本申请实施例中，一个装置的通信接口用于该装置与其它设备进行通信。示例性的，通信接口可以是发射机、接收机、收发器、电路、总线、模块、管脚或其它类型的通信接口，本申请实施例不做限制。
在具体实现过程中，处理器可用于进行，例如但不限于，基带相关处理，通信接口可用于进行，例如但不限于，信息交互。上述器件可以分别设置在彼此独立的芯片上，也可以至少部分的或者全部的设置在同一块芯片上。例如，处理器可以进一步划分为模拟基带处理器和数字基带处理器，其中模拟基带处理器可以与通信接口集成在同一块芯片上，数字基带处理器可以设置在独立的芯片上。随着集成电路技术的不断发展，可以在同一块芯片上集成的器件越来越多，例如，数字基带处理器可以与多种应用处理器(例如但不限于图形处理器，多媒体处理器等)集成在同一块芯片之上。这样的芯片可以称为系统芯片(system on chip，SOC)。将各个器件独立设置在不同的芯片上，还是整合设置在一个或者多个芯片上，往往取决于产品设计的具体需要。本申请实施例对上述器件的具体实现形式不做限定。
可以理解的是，对于前述实施例中所涉及的处理器可以通过具有处理器和通信接口的硬件平台执行程序指令来分别实现其在本申请前述实施例中任一设计中涉及的功能，基于此，如图18所示，本申请实施例提供了一种用于传输报文的装置1300的示意性框图，装置1300包括：处理器1310、通信接口1320和存储器1330。其中，处理器1310、通信接口1320和存储器1330耦合以互相通信，该存储器1330用于存储指令，该处理器1310用于执行该存储器1330存储的指令，以控制该通信接口1320发送信号和/或接收信号。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。
其中，在一种可能的实现方式中，若该装置1300为源MEC，通信接口1320用于接收到第二上行业务报文之后，接收源用户面网元发送的来自目标用户面网元的第一上行业务报文，所述第二上行业务报文为所述源移动边缘计算网元向源应用服务器发送的最后一 个上行业务报文，通信接口1320还用于向目标移动边缘计算MEC发送第一上行业务报文；通信接口1320还用于向目标MEC发送第一指示信息，第一指示信息用于指示装置1300发送第一上行业务报文结束。
在一种可能的实现方式中，若该装置1300为目标UPF，通信接口1320用于向源用户面功能UPF发送第一上行业务报文，在装置1300向源UPF发送第一上行业务报文之后不再向源UPF发送上行业务报文；通信接口1320还用于向源UPF发送第二指示信息，第二指示信息用于指示装置1300发送第一上行业务报文结束。
在一种可能的实现方式中，若该装置1300为目标MEC，通信接口1320用于接收来自源移动边缘计算MEC的第一上行业务报文，第一上行业务报文为源MEC接收到第二上行业务报文之后的所接收的上行业务报文，第二上行业务报文为源MEC向源应用服务器AS发送的最后一个上行业务报文；通信接口1320还用于接收来自源MEC的第一指示信息，第一指示信息用于指示通过源MEC发送的第一上行业务报文结束；通信接口1320还用于在接收到第一指示信息之后，当第一上行业务报文发送完毕，向目标AS发送由目标用户面功能UPF发送给目标移动边缘计算网元的上行业务报文。
在一种可能的实现方式中，若该装置1300为源AS，通信接口1320用于接收第一消息，第一消息用于触发终端装置的上下文的迁移，第一消息包括目标数据网络接入点标识DNAI；处理器1310用于确定处理完第一下行业务报文和第二上行业务报文之后，与目标DNAI对应的目标应用服务器AS进行终端装置上下文的迁移，其中，第一下行业务报文为装置向源移动边缘计算MEC发送的最后一个下行业务报文，第二上行业务报文为源MEC向装置发送的最后一个上行业务报文。
在一种可能的实现方式中，若该装置1300为MEC应用管理网元，通信接口1320用于接收源移动边缘计算MEC发送的第一迁移请求消息，第一迁移请求消息包括第一应用实例的标识以及目标数据网络接入点标识DNAI；处理器1310用于根据第一应用实例的标识确定所要迁移的第一应用实例；通信接口1320还用于分别向目标DNAI对应的目标AS和第一应用实例对应的源AS发送第一触发消息和第二触发消息，第一触发消息包括第一应用实例的标识，第一触发消息用于触发目标AS进行第一应用实例的迁移，第二触发消息用于触发源AS进行第一应用实例的迁移。
应理解，本申请实施例图13中的装置或图14中的装置或图15中的装置或图16中的装置或图17中的装置可以通过图18中的装置1300来实现，并且可以用于执行上述方法实施例中目标UPF网元、源UPF网元以及源AS对应的各个步骤和/或流程。
可以理解的是，本申请实施例描述的各种设计涉及的方法，流程，操作或者步骤，能够以一一对应的方式，通过计算机软件，电子硬件，或者计算机软件和电子硬件的结合来一一对应实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件，比如，考虑通用性好成本低软硬件解耦等方面，可以采纳执行程序指令的方式来实现，又比如，考虑系统性能和可靠性等方面，可以采纳使用专用电路来实现。普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，此处不做限定。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行上述实施例中的方法。本申请中的各个实施例也可以互相结合。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读解释存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上述实施例中的方法。
在本申请实施例中，应注意，本申请实施例上述的方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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)。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本申请中出现的术语“第一”、“第二”等仅是为了区分不同的对象，“第一”、“第二”本身并不对其修饰的对象的实际顺序或功能进行限定。本申请中被描述为“示例性的”，“示例”，“例如”，“可选地”或者“在某些实现方式中”的任何实施例或设计方案都不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用这些词旨在以具体方式呈现相关概念。
在本申请中可能出现的对各种消息/信息/设备/网元/系统/装置/操作/等各类客体进行了赋名，可以理解的是，这些具体的名称并不构成对相关客体的限定，所赋名称可随着场景，语境或者使用习惯等因素而变更，对本申请中技术术语的技术含义的理解，应主要从其在技术方案中所体现/执行的功能和技术效果来确定。
上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品可以包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端装置或者其他可编程装置。所述计算机指令可以存储 在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁盘)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。在本申请实施例中，在无逻辑矛盾的前提下，各实施例之间可以相互引用，例如方法实施例之间的方法和/或术语可以相互引用，例如装置实施例之间的功能和/或术语可以相互引用，例如装置实施例和方法实施例之间的功能和/或术语可以相互引用。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (31)

  1. 一种用于传输业务报文的方法，其特征在于，包括：
    源移动边缘计算网元接收到第二上行业务报文之后，所述源移动边缘计算网元接收源用户面网元发送的来自目标用户面网元的第一上行业务报文，所述第二上行业务报文为所述源移动边缘计算网元向源应用服务器发送的最后一个上行业务报文；
    所述源移动边缘计算网元向目标移动边缘计算网元发送所述第一上行业务报文；
    所述源移动边缘计算网元向所述目标移动边缘计算网元发送第一指示信息，所述第一指示信息用于指示所述源移动边缘计算网元发送所述第一上行业务报文结束。
  2. 根据权利要求1所述的方法，其特征在于，在所述源移动边缘计算网元向目标移动边缘计算网元发送第一上行业务报文之前，所述方法还包括：
    所述源移动边缘计算网元接收源用户面网元发送的来自目标用户面网元的第二指示信息，所述第二指示信息用于指示所述目标用户面网元发送所述第一上行业务报文结束。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述源移动边缘计算网元向目标移动边缘计算网元发送第一上行业务报文之前，所述方法还包括：
    所述源移动边缘计算网元向源用户面网元发送第一下行业务报文和第三指示信息，所述第三指示信息用于指示来自源应用服务器的下行业务报文发送结束。
  4. 根据权利要求3所述的方法，其特征在于，在所述源移动边缘计算网元向源用户面网元发送第一下行业务报文之前，所述方法还包括：
    所述源移动边缘计算网元接收第一网元发送的第四指示信息，所述第四指示信息用于指示来自所述源应用服务器的最后的一个下行业务报文为所述第一下行业务报文；
    所述源移动边缘计算网元向所述第一网元发送所述第五指示信息，所述第五指示信息用于指示所述第二上行业务报文为所述源移动边缘计算网元发送给所述源应用服务器的最后一个上行业务报文。
  5. 一种用于传输业务报文的方法，其特征在于，包括：
    目标用户面网元向源用户面网元发送第一上行业务报文，在所述目标用户面网元向所述源用户面网元发送第一上行业务报文之后不再向所述源用户面网元发送上行业务报文；
    所述目标用户面网元向所述源用户面网元发送第二指示信息，所述第二指示信息用于指示所述目标用户面网元发送所述第一上行业务报文结束。
  6. 根据权利要求5所述的方法，其特征在于，在所述目标用户面网元向源用户面网元发送第一上行业务报文之前，所述方法还包括：
    所述目标用户面网元接收来自所述源用户面网元的第一下行业务报文和第三指示信息，所述第三指示信息用于指示来自源应用服务器的下行业务报文发送结束。
  7. 根据权利要求6所述的方法，其特征在于，所述目标用户面网元向所述源用户面网元发送第二指示信息，包括：
    所述目标用户面网元根据所述第三指示信息向所述源用户面网元发送所述第二指示信息。
  8. 根据权利要求5或6所述的方法，其特征在于，所述目标用户面网元向所述源用 户面网元发送第二指示信息，包括：
    所述目标用户面网元接收来自会话管理网元或目标移动边缘计算网元发送的上下文迁移完成消息之后，所述目标用户面网元向所述源用户面网元发送所述第二指示信息。
  9. 根据权利要求5至8任一项所述的方法，其特征在于，在所述目标用户面网元向所述源用户面网元发送所述第二指示信息之后，所述方法还包括：
    所述目标用户面网元向目标移动边缘计算网元发送来自所述接入网设备的上行业务报文。
  10. 根据权利要求6所述的方法，其特征在于，在所述目标用户面网元接收所述第三指示信息之后，所述方法还包括：
    当所述第一下行业务报文发送完毕，所述目标用户面网元向所述接入网设备发送来自目标移动边缘计算网元的下行业务报文。
  11. 一种用于传输业务报文的方法，其特征在于，包括：
    目标移动边缘计算网元接收来自源移动边缘计算网元的第一上行业务报文，所述第一上行业务报文为所述源移动边缘计算接收到第二上行业务报文之后的所接收的上行业务报文，所述第二上行业务报文为所述源移动边缘计算网元向源应用服务器发送的最后一个上行业务报文；
    所述目标移动边缘计算接收来自所述源移动边缘计算网元的第一指示信息，所述第一指示信息用于指示所述源移动边缘计算网元发送第一上行业务报文结束；
    在所述目标移动边缘计算网元接收到所述第一指示信息之后，当所述第一上行业务报文发送完毕，所述目标移动边缘计算网元向目标应用服务器发送由目标用户面网元发送给目标移动边缘计算网元的上行业务报文。
  12. 一种用于传输业务报文的报文，其特征在于，包括：
    源应用服务器接收第一消息，所述第一消息用于触发所述源应用服务器进行终端装置的上下文的迁移，所述第一消息包括目标数据网络接入点标识；
    所述源应用服务器确定处理完第一下行业务报文和第二上行业务报文之后，所述源应用服务器与所述目标数据网络接入点标识对应的目标应用服务器进行所述终端装置上下文的迁移，其中，所述第一下行业务报文为所述源应用服务器向源移动边缘计算网元发送的最后一个下行业务报文，所述第二上行业务报文为所述源移动边缘计算网元向所述源应用服务器发送的最后一个上行业务报文。
  13. 根据权利要求12所述的方法，其特征在于，在所述源应用服务器与所述目标数据网络接入点标识进行所述终端装置上下文的迁移之前，所述方法还包括：
    所述源应用服务器向所述源移动边缘计算网元发送第四指示信息，所述第四指示信息用于指示所述第一下行业务报文为来自所述源应用服务器的最后一个下行业务报文；
    所述源应用服务器接收所述源移动边缘计算网元发送的第五指示信息，所述第五指示信息用于指示所述第二上行业务报文为所述源移动边缘计算网元向所述源应用服务器发送的最后一个上行业务报文。
  14. 一种用于传输业务报文的方法，其特征在于，包括：
    移动边缘计算应用管理网元接收源移动边缘计算网元发送的第一迁移请求消息，所述第一迁移请求消息包括第一应用实例的标识以及目标数据网络接入点标识；
    所述移动边缘计算应用管理网元根据所述第一应用实例的标识确定所要迁移的第一应用实例；
    所述移动边缘计算应用管理网元分别向所述目标数据网络接入点标识对应的目标应用服务器和所述第一应用实例对应的源应用服务器发送第一触发消息和第二触发消息，所述第一触发消息包括所述第一应用实例的标识，所述第一触发消息用于触发所述目标应用服务器进行所述第一应用实例的迁移，所述第二触发消息用于触发所述源应用服务器进行所述第一应用实例的迁移。
  15. 根据权利要求14所述的方法，其特征在于，在所述移动边缘计算应用管理网元分别向所述目标数据网络接入点标识对应的目标应用服务器和所述目标应用实例对应的源应用服务器发送的第一触发消息和第二触发消息之前，所述方法还包括：
    所述移动边缘计算应用管理网元在所述目标应用服务器创建所述第一应用实例的虚拟资源，以便于所述目标应用服务器根据所述虚拟资源迁移所述第一应用实例。
  16. 一种用于传输业务报文的装置，其特征在于，包括用于执行权利要求1-4中任一项方法的单元。
  17. 一种用于传输业务报文的的装置，其特征在于，包括用于执行权利要求5-10中任一项方法的单元。
  18. 一种用于传输业务报文的装置，其特征在于，包括用于执行权利要求11所述方法的单元。
  19. 一种用于传输业务报文的的装置，其特征在于，包括用于执行权利要求12或13所述方法的单元。
  20. 一种用于传输业务报文的装置，其特征在于，包括用于执行权利要求14所述方法的单元。
  21. 一种用于传输业务报文的系统，包括权利要求16所述的装置、权利要求17所述装置、权利要求18所述的装置、权利要求19所述的装置、权利要求20所述的装置，或者包括权利要求14所述的装置、权利要求15所述的装置以及接入网设备中至少两种装置，所述接入网设备用于与权利要求17所述的装置传输业务报文。
  22. 一种计算机可读存储介质，其特征在于，包括计算机程序，所述计算机程序在计算机上被执行时，使得计算机执行如权利要求1-4中任一项所述的方法。
  23. 一种计算机可读存储介质，其特征在于，包括计算机程序，所述计算机程序在计算机上被执行时，使得计算机执行如权利要求5-10中任一项所述的方法。
  24. 一种计算机可读存储介质，其特征在于，包括计算机程序，所述计算机程序在计算机上被执行时，使得计算机执行如权利要求11所述的方法。
  25. 一种计算机可读存储介质，其特征在于，包括计算机程序，所述计算机程序在计算机上被执行时，使得计算机执行如权利要求12或13所述的方法。
  26. 一种计算机可读存储介质，其特征在于，包括计算机程序，所述计算机程序在计算机上被执行时，使得计算机执行如权利要求14所述的方法。
  27. 一种芯片，其特征在于，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如权利要求1-4中任一项所述的方法。
  28. 一种芯片，其特征在于，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如权利要求5-10中任一项所述的方法。
  29. 一种芯片，其特征在于，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如权利要求11所述的方法。
  30. 一种芯片，其特征在于，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如权利要求12或13所述的方法。
  31. 一种芯片，其特征在于，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如权利要求14所述的方法。
PCT/CN2020/097385 2019-06-24 2020-06-22 用于传输业务报文的方法和装置 WO2020259428A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20833223.9A EP3979531A4 (en) 2019-06-24 2020-06-22 METHOD AND DEVICE FOR TRANSMISSION OF SERVICE MESSAGE
US17/561,190 US11677492B2 (en) 2019-06-24 2021-12-23 Service packet transmission method and apparatus
US18/309,046 US20230336269A1 (en) 2019-06-24 2023-04-28 Service Packet Transmission Method and Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910551336.XA CN112134643B (zh) 2019-06-24 2019-06-24 用于传输业务报文的方法和装置
CN201910551336.X 2019-06-24

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/561,190 Continuation US11677492B2 (en) 2019-06-24 2021-12-23 Service packet transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2020259428A1 true WO2020259428A1 (zh) 2020-12-30

Family

ID=73849753

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/097385 WO2020259428A1 (zh) 2019-06-24 2020-06-22 用于传输业务报文的方法和装置

Country Status (4)

Country Link
US (2) US11677492B2 (zh)
EP (1) EP3979531A4 (zh)
CN (2) CN114884612A (zh)
WO (1) WO2020259428A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022270997A1 (en) * 2021-06-25 2022-12-29 Samsung Electronics Co., Ltd. Methods and apparatus for application service relocation for multimedia edge services

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI789255B (zh) 2022-02-25 2023-01-01 財團法人工業技術研究院 邊緣運算系統、邊緣運算裝置、用戶設備和使用者平面功能切換方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651971A (zh) * 2009-09-15 2010-02-17 新邮通信设备有限公司 一种下行切换方法及系统
WO2018206844A1 (en) * 2017-05-08 2018-11-15 Nokia Technologies Oy Routing and policy management at network edge
CN109788513A (zh) * 2017-11-13 2019-05-21 中国电信股份有限公司 边缘计算应用的数据同步方法、系统及控制器

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108235298A (zh) * 2016-12-21 2018-06-29 上海中兴软件有限责任公司 移动边缘计算中路径切换方法、移动边缘计算平台及网关
EP3592100B1 (en) * 2017-03-22 2020-11-25 Huawei Technologies Co., Ltd. Session migration method and device
WO2018199649A1 (en) * 2017-04-27 2018-11-01 Samsung Electronics Co., Ltd. Method and apparatus for registration type addition for service negotiation
EP3422767A1 (en) * 2017-06-26 2019-01-02 Panasonic Intellectual Property Corporation of America User equipment and base station participating in packet duplication during handover for nr
CN109673008B (zh) 2017-10-17 2022-04-22 华为技术有限公司 终端设备的状态的确定方法、装置及设备
US10440559B2 (en) * 2017-10-25 2019-10-08 Futurewei Technologies, Inc. Private mobile edge computing data center in a telecommunication network
US11258873B2 (en) * 2017-11-10 2022-02-22 Intel Corporation Multi-access edge computing (MEC) architecture and mobility framework
CN109842639B (zh) * 2017-11-24 2020-09-08 华为技术有限公司 实现切换过程中业务连续性的方法、设备及系统
CN112187643B (zh) * 2017-11-28 2021-12-10 华为技术有限公司 报文转发的方法、控制面网关和用户面网关
WO2019126931A1 (en) * 2017-12-25 2019-07-04 Nokia Solutions And Networks Oy Quality of service (qos) control in mobile edge computing (mec)
US10708716B2 (en) * 2018-10-16 2020-07-07 Cisco Technology, Inc. Methods and apparatus for selecting network resources for UE sessions based on locations of multi-access edge computing (MEC) resources and applications
US10813010B2 (en) * 2018-12-17 2020-10-20 Verizon Patent And Licensing Inc. Method and system for edge computing handover service
US11234204B2 (en) * 2019-02-12 2022-01-25 Intel Corporation Server selection for vehicle communications and applications
US20220167262A1 (en) * 2019-02-12 2022-05-26 Intel Corporation Server selection for vehicle communications and applications
US10999766B2 (en) * 2019-02-26 2021-05-04 Verizon Patent And Licensing Inc. Method and system for scheduling multi-access edge computing resources
US10856360B1 (en) * 2019-05-23 2020-12-01 Verizon Patent And Licensing Inc. System and method for sharing multi-access edge computing resources in a wireless network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651971A (zh) * 2009-09-15 2010-02-17 新邮通信设备有限公司 一种下行切换方法及系统
WO2018206844A1 (en) * 2017-05-08 2018-11-15 Nokia Technologies Oy Routing and policy management at network edge
CN109788513A (zh) * 2017-11-13 2019-05-21 中国电信股份有限公司 边缘计算应用的数据同步方法、系统及控制器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "S2-1901832:Discussion on SA2 Edge Computing Study.", 3GPP TSG-SA WG2 MEETING #131., 19 February 2019 (2019-02-19), XP051610423, DOI: 20200915155225A *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022270997A1 (en) * 2021-06-25 2022-12-29 Samsung Electronics Co., Ltd. Methods and apparatus for application service relocation for multimedia edge services

Also Published As

Publication number Publication date
US20230336269A1 (en) 2023-10-19
CN112134643B (zh) 2022-04-05
US11677492B2 (en) 2023-06-13
EP3979531A1 (en) 2022-04-06
US20220116134A1 (en) 2022-04-14
EP3979531A4 (en) 2022-08-03
CN114884612A (zh) 2022-08-09
CN112134643A (zh) 2020-12-25

Similar Documents

Publication Publication Date Title
US20170019945A1 (en) Dual Connectivity Re-Establishment
US11259344B2 (en) Network architecture and information exchange method and apparatus
KR102339053B1 (ko) 데이터 전달 방법, 장치, 및 시스템
WO2021057794A1 (zh) 配置业务的方法、通信装置和通信系统
US10893574B2 (en) Packet data unit session release method and network entity performing the same
WO2019196811A1 (zh) 通信方法和相关装置
US11968565B2 (en) User plane information reporting method and apparatus
EP4047987A1 (en) Method for dual connectivity establishment of iab node, and communication device
WO2018205114A1 (zh) 一种状态切换方法及装置
JP2019536342A (ja) 無線デバイスをハンドオーバするシステム及び方法
US11611501B2 (en) Apparatus, method, and computer program
WO2019192445A1 (zh) 一种组播组创建、组播组加入方法及装置
WO2022022014A1 (zh) QoS流控制方法及通信装置
WO2019029642A1 (zh) 通信方法、基站、终端设备和系统
WO2020259428A1 (zh) 用于传输业务报文的方法和装置
WO2021097858A1 (zh) 一种通信方法及装置
US9503393B2 (en) S-GW relocation and QoS change without mobility
WO2017193286A1 (zh) 移动性管理方法和装置
US20220116828A1 (en) Service packet transmission method and apparatus
CN111405625B (zh) 一种切换方法、基站、通信系统及存储介质
EP4117338A1 (en) Data transmission method and apparatus
WO2020042037A1 (zh) 无线通信方法和通信设备
US20230262790A1 (en) Method for releasing f1 connection and apparatus, and system
EP4021072A1 (en) Data processing method, apparatus, and system
WO2021160057A1 (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: 20833223

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020833223

Country of ref document: EP

Effective date: 20211229